Hi, my wife gifted me that Chopin phone form China, after a wrong "flash and lock" global firmware now my phone is stuck on bootloader.
According to this thread:
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
I have all the files needed to setup sp flash and try to put again the Rom in the phone, which is now not unlocked and no usb debugging on.
Can someone please give me a tutorial on how to use those files? My phone still not recognised in sp flash com port, I don't know how to do.
If anyone will help me it will be so appreciated, thanks!
If you need to disable authorisation, did you run the MTK Auth Bypass tool and get the message "Protection disabled"? That's what I had to do before SP Flash Tool would flash the phone (without disconnecting it or rebooting), and I also had to set the baud rate to 921600, although that was all under Linux, and the phone was still unlocked.
it's complicated. with phone locked fastboot commands don't work. with my hold mi a3 fastboot flashing unlock command work. but with miui and mtk chipset probably it's useless. but u can try. if u boot into bootloader with mediatek driver the pc should recognize your phone also if it's blocked
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Bonscia said:
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Click to expand...
Click to collapse
1. Check your device driver for USB, suggest you re-install the MTK usb driver.
2. First run the program, select the Auth by pass then press start.
3. Make sure phone is in "power off" state, press Vol+, Vol- and power (all three at the same time), and don't release it, plug in USB cable and wait.... Don't release these three buttons until it is Auth by pass OK.
During this process, take a look at device manager, there must be one item like portable device - USB ( Com 3). keep flashing.
sure u add reinstall mtk driver
Tried many drivers, always same result:
Driver says the device can't start. Tried to install lisbus too but no changes.
Bonscia said:
Tried many drivers, always same result:
View attachment 5499127
View attachment 5499129
Driver says the device can't start. Tried to install lisbus too but no changes.
Click to expand...
Click to collapse
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
kirinin said:
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
Click to expand...
Click to collapse
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Bonscia said:
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Click to expand...
Click to collapse
is a win10 problem that i also haved. hard to solve. u can try windows 7 via virtualbox (solved a lot of my problems in the past) or format and install a modded version of win10 (but i dont suggest this)
Virtual box looks no longer available, I'll install a fresh copy of win 7 in another partition, never give up lol
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
wetito said:
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
Click to expand...
Click to collapse
? I've just told you I've tried to download virtual box for win 10 but it's not avaible now or server was temporarily down for the download, so my only way it's to set up a fresh copy on win 7 on my pc, I can't understand your hanger answer.
kirinin said:
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
View attachment 5498521
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
View attachment 5498523
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Click to expand...
Click to collapse
Hi, can you share this Zip file with link drive or mega?
Thanks in advance
Which zip file? I have only this one
https://forum.xda-developers.com/attachments/mtk_bypass_final-rar.5444529/I
finally flashed the Rom with so flash but now the phone reboot in assistance mode sayings "NV data corrupted" I'm about to cry
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Link with files is this, I've seen other link don't work
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
Download MTK Universal Tool V5 | MediaTek All in One Tool Latest Free
MTK Universal V5 Tool is a small MediaTek All in One Tool designed to disable user locks, bypass FRP, Auth Bypass, Format Data (user data format),
www.gadgetsdr.com
Bonscia said:
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Click to expand...
Click to collapse
try wipe data. also u can control the active slot. try change it and reboot
Hi, finally I can install the Recovery V12.5.16.0.RKPCNXM rom and the engineering rom but have no baseband and no IMEI. Tried many times to put my IMEI codes with no luck, looks I need the mt6893 modem file to use sn writer but no way to find them on net, can someone share those files please? Thanks
Related
Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
QFIL recognized the device correctly as Qualcomm HS-USB QDLoader 9008, but I kept receiving this error:
02:20:14: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
02:20:14: ERROR: function: sahara_main:854 Sahara protocol error
02:20:14: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
So I followed this guide that recommends to use MiFlash instead of QFIL.
After few unsuccessful updates (it wasn't able to open the port) it finally finished downloading the ROM (2.0.057 ST) with this message at the end: The operation completed successfully.(0x00000000: ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value CRC32(NUM_DISK_SECTORS-1.,92), size 4)
It took about 55s.
However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. Since the update the screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Multiple times with the "successful update" message, but nothing happens.
EDIT: Now, after few tries the of the same process it is not even updating the ROM at all. It says "Open serial port failed" and afterwards "Missing hello packet, try to recover" (I waited about 5 min, but the message didn't change).
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I will do it.
Thank you!
Creshaw said:
Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
After few unsuccessful updates (although it recognized the device correctly as Qualcomm HS-USB QDLoader 9008, it wasn't able to access it via the relevant port) it finally updated the ROM (2.0.057 ST) with successful message at the end (the flash itself took about 55s). However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. The screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Still successful update, but nothing happens.
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I would do it.
Thank you!
Click to expand...
Click to collapse
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
syedtahir16 said:
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
Click to expand...
Click to collapse
Yes, everything step by step. I even have the same version of QFIL (QPST is build 437 instead of suggested 434 - I suppose that won't be causing any problem). I tried to reboot my PC, different USB ports, reinstall drivers (as I previously had Lenovo USB driver and before the flash I installed the ZUK driver as well as without the ZUK drivers it wasn't recognized as QDLoader).
Zukfans.eu
Btw I'm unable to sign up to zukfans.eu to place my question there as well as. It asks for CAPTCHA verification, however there is no CAPTCHA shown, only the verification question "what zuk have you ?". I filled in there 'ZUK Z2 Pro', copied the question in there etc., used 4 different broswers on 2 devices and networks, no luck. And it is not possible to log in via FB as well.
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Creshaw said:
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Click to expand...
Click to collapse
I'm not sure about Miflash. I used QFIL.
Also, I wrote a small tutorial. See if that helps:
http://zukfans.eu/community/threads...rom-zuk-z2-pro-z2121-only.57/page-8#post-7282
If you are unable to use that link. Below is an extract:
"The QFIL zip contained the ROM twice. so you can load the contents.xml from the parent folder or the other folder within the zip too.
Make sure you extract the ROM in a short part i.e. "C:\Z2Pro\
1) Firstly, the tricky part having the tool recognize the qualcomm port.
Solution: Uninstall the tool, USB drivers (i.e. Zuk drivers), any existing qualcomm drivers.
Reboot.
Install Zuk drivers.
Install the tool. (According to the guide, the tool will also install the drivers for qualcomm, but for some reason it did not)
Install the qualcomm drivers.
2) Fortunately, my phone was not bricked. So I could easily get into edl mode using "adb reboot edl"
3) While trying to get this to work, some RELINK driver was installed instead of qualcomm. Uninstall that if you see that.
4) Anyway, back to our troubleshooting. So you would think that you are all set and your qualcomm port should be recognized, but no. It failed to recognize. So try this:
Reboot PC.
Reboot Phone.
5) Now Proceed. Hopefully by now you have see your qualcomm port. Great.
6) This is the trickiest part. You need to click on the "Download Content" "IMMEDIATELY" "AS SOON AS" you hit enter on "adb reboot edl".
[Image]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7) Yay. You see very nice progress in the little progress section on QFIL. You think you'ved nailed it.. But no, you could again end up getting another error. (Unfortunately I forgot to get a screenshot). Anyway, you would see this multiple times, that the "File access is very slow"; I'm not sure if only I received that error or if it is generic.
8) When you get an error at this point. Try a different port. Luckily, I got it to work on my second attempt on another attempt.
My review on the stock ROM:
Honestly, the custom ROM installed by the seller worked way better for me. This stock ROM had a lot of chinese apps (which of course I can uninstall). But somehow, the custom ROM from the seller felt better. Luckily I had a nandroid backup and I went back to it. The only drawback apart from OTA, being on the latest etc etc is that I cannot use the heartrate sensor (which is no big deal for me).
I guess I'll wait for another AOSP or another custom ROM or probably something with Android N before I upgrade again.
Hope this helps."
Thanks for getting back to me. I remember reading this before, however I cannot apply it to the current situation (but I tried anyway).
However there is an update to share. After some time I was able to go through the full download via MiFlash as before (with the 'successful' message) and moreover, flashing via QFIL finally started to produce something promising, however at the end it showed this message (no change to the state of the phone):
View attachment 131237287087498319.log
Next try showed the same error message as before:
View attachment 131237297946525488.log
SOLVED!
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Creshaw said:
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Click to expand...
Click to collapse
Glad you got it figured out! Enjoy your Z2 Pro
Hello there, I'm having a similar problem that the owner of this thread had, but the difference is that the adb doesn't detects my device.
I've tried to reinstall all the drivers, and downloaded the Android SDK tools, but still doesn't works...
Any idea about what to do? The device is with the screen in black, no led blinks or anything like that, and when connected to the PC, only detrects the Qualcomm 9008 port...
Thank you in advance.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
--
Thanks to valuable help from Emmaus and DanRO from zukfans.eu I managed to render my phone operable once more and now it runs flawlessly. This recovery is a life-saver for anyone experiencing bricking or malfunction issues:
https://yadi.sk/d/DfTYl-jz3Cxg76
_The first thing to do is to enter fastboot menu (pressing vol rockers will help)
_Then you will need to unlock bootloader with the dedicated commands:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
For noobs or newcomers: Be informed that you will need the OEM bootloader image from ZUK website through giving your credential and phone's serial number for unlocking, you can see the instructions on the forum or by googling it.
_After unlocking your bootloader you should flash the aforementioned and link-given recovery with the following commands:
fastboot -i 0x2b4c flash recovery twrp_name.img
(Replace "twrp_name" with the name of the downloaded image and without quotes)
_Once you successfully enter TWRP Recovery menu, you can either flash a TWRP-flashable file or else, by tapping reboot button you can select EDL (9008) option to open 9008 port on QPST for being able to flash any official firmware.
_Check your internal storage on flashing TWRP-flashable ROMs. In my case, after I flashed recovery and then a CM-based ROM (AICP), I saw that the phone had only a 9GB-size as internal storage. If you happen to face the same issue, just flash an official firmware on QPST, as this problem occurs due to bad partitioning, at least that is what it seems.
Ask anything for any further details.
Thanks.
Can't power off....help!
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Also I am Now Bricked
When Z2Pro was hung up during QFIL connection with EDL mode, It cannot but wait until battery empty because it does not reaction to the reboot with the VOL PowerBtn's switch either.
if Disassemble the Z2pro then remove buttery,maybe re-QFIL.
Anyone,want you to tell me if you know the method for reboot z2pro.whthout Disassemble it.
maofedeli said:
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Click to expand...
Click to collapse
Have you figured out a way?
Hi all,
received a Z2 pro, flashed with multi language rom, without OTA upgrades. When sim inserted, there was no connection to the network. After several attempts, i decided to send it back.
Ordered from another shop a new 2 ro, ( i know, very stupid to try twice) and this time, when tried to flash it from multi language rom, with an official one, it was bricked. Deep flash trick and.....
Tried several times to open HS-USB QDloader 9008 and once every 20 times it was a success. But, Sahara error all the time in qfil and hallo packet error in miflash. I'm out of ideas,.... Do you hve any?
Guys,
My ZUK Z2 Pro (bootloader unlocked) after finish loading the entire system (android) and appear the home screen, it reboots itself. When its boot it connected to PC, it does not reboot and after 5s I can remove cable and use it without problems. If the cable is in charge adapter, it also has the same problem.
Summary: I always need to turn on it connected in PC (with drivers installed) and wait 5s after finished loading all OS + startup APPs to not reboot alone. I install TWRP for good but no change to install custom ROM as it comes in loop after loading bootloader. Only ROMs that are stock, installed using QFIL works.
Do you have any idea?
Btw: I was using Mokee Rom without problems but after starting somes Frameworks apps te rom bricked out.
No 9008
Hello, i am new here and posted a reply in a different place. I think the wrong thread, so i will write here too.
I have a Zuk Z2 Pro. Unlocked bootloader, TWRP (twrp-3.2.1-0-z2_row.img) and installed several roms to try out. Then i read about a new ZUI and wanted to flash it. But, i made a mistake and now my phone is bricked. I read all about unbricking and flashing wit QFIL, but (and like others) my pc does not recognize my phone anymore. I can not work with adb (windows commands) and in QFIL i can not get the needed 9008 port. I installed all the needed stuff, but nothing.
Can someone help me out please. I already followed all the stept in some tutorials, but i get stuck with this 9008, which will not appear.
Phone does not start up. Recovery is gone, only menu with fastboot, recovery etc. is there. And the ZUI screen (from the rom i wanted to install) but the screen does not respond anymore, so i can not begin with setting the phone.
Is there a solution so i can flash with QFIL?
Or another solution?
Thanks,
Alex
Update 18-03-2018
This worked for me to get the needed 9008 port for flashing with QFIL:
- Open QFIL
- Phone must be off
- Connect usb cable to pc (not to phone yet)
- press volume up + power button and immediately connect usb cable to phone
- phone will vibrate 3 time (screen stays black/off)
- pc recognizes phone (there is this familiar sound of your pc)
- In QFIL you wil see port 9008
- just flash and wait till it's done
Off course you must have drivers etc installed on your pc, all the needed stuff for flashing. Don't forget to charge you phone.
I bricked my lenovo z2 plus, it is not booting to ROM or fastboot, it only vibrates after I hold the power button, and keeps vibrating every 10 sec, can anybody help me??
[GUIDE] Unbrick Tool for OnePlus 5 with OOS 9.0.9 & OOS 9.0.11 (Untouched full stock)
Hello Everyone !!
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD
This method is easy to use and flashes OxygenOS 5.1.7 and OxygenOS 9.0.9 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :-
OOS 9.0.9: https://mega.nz/file/O4dGFI4b#mbqq8VqUiPwoN85ajTV-H2pDNccD58-ccejQnTQHIBE
OOS 9.0.11:https://mega.nz/file/ekUURaII#FPoezmYL1hPJUkb2Hf90ZqW07iEaCza6etnTPSKJOos
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/file/4aqwyi3g1d6wc67/Qualcomm+1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
P.S.: I found the fix for bootloader menu which was changing after flashing through this tool. Just flash the zip in the recovery from the link below after flashing the rom through this tool, and you are good to go.
Please boot your device, set it up then go back to recovery and flash this file.
https://mega.nz/file/n10kkKCQ#LmCm_TDDyZ9cdZPf2pk0mSSV1bgvZflENQG0ubl15SY
NOTE: When the tool gives the "Sahara error", DON'T DISCONNECT THE PHONE from your PC, and press vol up and power button. It maybe seem stupid as a fix but generally it works.
IMP NOTE: There is a quick update, recently I also got stuck at param processing while flashing my device. So uploading the tool which works well. Here is the link. https://mega.nz/file/C1Nw3Cyb#znHfATPuRN4rAy1ZnDO4kMcftEkQ1P6enGxRGSiBh2E
IMP NOTE: There is a quick update, the tool is updated with latest TREBLE OS.
CREDITS @vasu97 - for helping and motivating me to create this thread
@Mar-cel - for bootloader fix zip
Click thanks IF i helped you
Where did you get this file, after I restored it, the bootblock unlock menu changed, is that normal?
Yes it is normal, mine also changed. May be they changed something in latest tool
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
cidsantiago said:
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
Click to expand...
Click to collapse
hv u tried running this tool as administrator abd ur fone shud not turn on any of the led while flashing.. if u r on twrp try format data .. and then try flashing it thru tool.. or may be its bad download at ur side. redownload again.. and try
cidsantiago said:
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
View attachment 4445915
View attachment 4445916
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
Click to expand...
Click to collapse
Don't worry about green led light while flashing with tool its normal behavior, and about error...maybe because of bad download for sure,try attaching your phone again or check the drivers again...and look at the firs comment - seems like tool is working fine.
djnim said:
hv u tried running this tool as administrator abd ur fone shud not turn on any of the led while flashing.. if u r on twrp try format data .. and then try flashing it thru tool.. or may be its bad download at ur side. redownload again.. and try
Click to expand...
Click to collapse
Yes, i ran it as administrator. M phone was totally bricked, i only got signal in him when i connected at the PC. But i always had this error :T I downloaded it at least 5 times, and got always the same results.
vasu97 said:
Don't worry about green led light while flashing with tool its normal behavior, and about error...maybe because of bad download for sure,try attaching your phone again or check the drivers again...and look at the firs comment - seems like tool is working fine.
Click to expand...
Click to collapse
I did it all, believe me. Reinstalled the drivers multiples times, differents PCS, differents USB ports... I think it was a hardware problem.
I already sent my phone to RMA, so i think it was solved, one way or another But thanks for your replies
cidsantiago said:
Yes, i ran it as administrator. M phone was totally bricked, i only got signal in him when i connected at the PC. But i always had this error :T I downloaded it at least 5 times, and got always the same results.
I did it all, believe me. Reinstalled the drivers multiples times, differents PCS, differents USB ports... I think it was a hardware problem.
I already sent my phone to RMA, so i think it was solved, one way or another But thanks for your replies
Click to expand...
Click to collapse
ohh.. i got tensed as it is my very first thread .
best method to return sotck complete
Thanks for the clear instructions, you have just saved my phone
Dude, thanks for the guide. But kindly check your links in the post. Some are dead ( especially : the mediafire link you gave at last )
Hi
Thank you so much !
AnDrOiDnEoV said:
Dude, thanks for the guide. But kindly check your links in the post. Some are dead ( especially : the mediafire link you gave at last )
Click to expand...
Click to collapse
That's correct. The right link is this: http://www.mediafire.com/file/4aqwyi3g1d6wc67/Qualcomm+1.00.11.rar
Hi, thanks for making this guide with such clear instructions!
I've done every step according to the guide, but I keep facing this issue:
Just to clarify I did run it as administrator.
Are you going to update (5.1.2)?
esedix02 said:
Are you going to update (5.1.2)?
Click to expand...
Click to collapse
If i Get it then yes for sure
Op updated with the bootloader fix, which helps to revert to old bootloader menu.
Op updated with new tool which includes OOS 5.1.2.
Mate she worked a charm! I wasn't bricked but wanted to restore to full stock after issues with open beta rims, firmware and AOSP roms. Was the simplest way to achieve a fresh start
it downloads the ROM while flashing? Or ROM is included in given link by OP?
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
assistance... you have lost warranty. anyway you can try this metod (work with my old mia3 but have a qualcomm chipset)
first: CLOSE YOUR PHONE!
install mi pro flash tool https://www.androidfilehost.com/?fid=14943124697586360238
PRESS power+ vol up+vold -
connet to pc via USB
OPEN MIflash tool pro
if your phone will be recognized you can flash stock firmware
with miflash pro you can install all drivers you need (but i'm not sure, test by yourself)
good luck.
if this procedure don't work go to an assistance point. you have damaged the bootloader
before mod devices with a/b partitions is very important read guides with attention. if you don't want trash a new device
you can also try sp flash tool, specific for mtk devices
How-to flash or install Stock ROM (Firmware) using SP Flash Tool
Step-by-Step guidelines to flash or install Stock ROM (Scatter Firmware) on Mediatek devices using the SP Flash Tool.
androidmtk.com
tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
did you even open it? tannedcan in every single post where there are instructions how to root/unlock/change rom
there is a DISCLAIMER for a reason.
that msg remark that you can brick your device if you dont know what you are doing or if you have doubts!
most of times things can be recovered but NEVER open a device in warranty.
simika said:
did you even open it? tannedcan in every single post where there are instructions how to root/unlock/change rom
there is a DISCLAIMER for a reason.
that msg remark that you can brick your device if you dont know what you are doing or if you have doubts!
most of times things can be recovered but NEVER open a device in warranty.
Click to expand...
Click to collapse
yes, i'm 100% agree with you
tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
I was exactly in same trouble, use This guide that solve the issue.
How to flash an MTK secure boot device without a custom DAThis is a step by step guide showing how to flash a Mediatek (MTK) secure boot device without using a custom download agent (DA). A little history Secure Boot M
forum.hovatek.com
Press mobile three buttons and connect cable to pc (use USB 2.0) to enter BROM mode (are like ERL mode in Snapdragon models). Because mtk models don't have test point. So don't need to disarm mobile.
Did you find the solution?
please any solution? i am into same problem. need stock rom for
Redmi Note 10 5G choppin
Zaiserr2 said:
I was exactly in same trouble, use This guide that solve the issue.
How to flash an MTK secure boot device without a custom DAThis is a step by step guide showing how to flash a Mediatek (MTK) secure boot device without using a custom download agent (DA). A little history Secure Boot M
forum.hovatek.com
Press mobile three buttons and connect cable to pc (use USB 2.0) to enter BROM mode (are like ERL mode in Snapdragon models). Because mtk models don't have test point. So don't need to disarm mobile.
Click to expand...
Click to collapse
this really helped, thanks but only with usb 3.0
tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
same issue sir my device show handshake failed during flashing
wetito said:
assistance... you have lost warranty. anyway you can try this metod (work with my old mia3 but have a qualcomm chipset)
first: CLOSE YOUR PHONE!
install mi pro flash tool https://www.androidfilehost.com/?fid=14943124697586360238
PRESS power+ vol up+vold -
connet to pc via USB
OPEN MIflash tool pro
if your phone will be recognized you can flash stock firmware
with miflash pro you can install all drivers you need (but i'm not sure, test by yourself)
good luck.
if this procedure don't work go to an assistance point. you have damaged the bootloader
before mod devices with a/b partitions is very important read guides with attention. if you don't want trash a new device
you can also try sp flash tool, specific for mtk devices
How-to flash or install Stock ROM (Firmware) using SP Flash Tool
Step-by-Step guidelines to flash or install Stock ROM (Scatter Firmware) on Mediatek devices using the SP Flash Tool.
androidmtk.com
Click to expand...
Click to collapse
is it okey or I'm the only one whose phone just keeps getting recognized and unrecognized by the PC every 5-10 sec ????
even though i have tried same with diffrent PCs and diffrent cables
PLEEEEEEEEEEEEASE HELP because this is by far the biggest obstacle I had in this precedure
It is not OK, you are the only one
Start from BROM mode and proceed from there.
viktak said:
It is not OK, you are the only one
Start from BROM mode and proceed from there.
Click to expand...
Click to collapse
I appreciate your response but
i did it all
i already have python the last version
i downloaded the MTK driver
i pressed the whole 3 buttons in the phone connected to PC (the phone didn't give any output at all)
i did set it up (which does appear and dissapear in every 5secs so I had to be quick)
then for the main.py file didn't capture the phone (obviously because I constantly hear the devices get recognized and unrecognized and nor the cable nor the PC are the cause
the theeere I am, stuck in the very 1st step.
please I would be so thankful if you could diagnose the problem just for me to know what to do.
personally I don't think it's a phone hardware problem because back in the days lol i unlocked bootloader and installed recovery, all was very functional and everything responded smoothly
if you wanted to know any other detail i would be so pleasured to tell you
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
viktak said:
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
Click to expand...
Click to collapse
alright, appreciate it
thank you
pardon my abbreviations knowledge but I really don't know what a PM is
Did anyone found the way to back the phone to life???
If anyone can respond me quickly I will apreciate it.
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
Ok, I will see
viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
I have a problem, I can't make it work, not even the fastboot or MTK tools
viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
post a link to your blog
viktak said:
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
Click to expand...
Click to collapse
i need help on this very issue pls help meee
Few things to keep in mind before starting the process:
If you are on ColorOS12 make sure you are flashing OxygenOS12 and NOT OxygenOS 13; similarly if you are ColorOS13 you will have to use OxygenOS13 zip.
You must ALWAYS use OxygenOS newer than the ColorOS you have currently installed.
[English] Written Instructions:
(Note this is for 10pro, steps are the same but DON'T use any firmwares mentioned there)
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
[Chinese] Written Instructions:
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
Video Tutorial:
Downloads Links:
80W_C.15_OOS_Android13
150W_C.15_OOS_Android13
You can also follow the same instructions if you wish to convert to ColorOS. Just make sure you use ColorOS zip in that case.
Download link for ColorOS:
150W_ColorOS_C.17_Android13
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-cow partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 3.
If you completed step 3, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
I
6cdh said:
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-com partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 2.
If you completed step 2, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
Click to expand...
Click to collapse
In the Step #7, it should be *-cow partitions, No?
yashaswee1708 said:
I
In the Step #7, it should be *-cow partitions, No?
Click to expand...
Click to collapse
Ah, yes, it's a typo. edited.
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sSjBlueVN197 said:
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.View attachment 5876919
Click to expand...
Click to collapse
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
yashaswee1708 said:
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
Click to expand...
Click to collapse
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
sSjBlueVN197 said:
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
Click to expand...
Click to collapse
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
yashaswee1708 said:
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
Click to expand...
Click to collapse
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
sSjBlueVN197 said:
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
Click to expand...
Click to collapse
Try factory reset from recovery?
sSjBlueVN197 said:
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Click to expand...
Click to collapse
If you can boot in fastboot do the process again. I'll share the zip once again
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
after flashed OOS, can I re-lock bootloader?
sSjBlueVN197 said:
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
Click to expand...
Click to collapse
Let me know if the issues are fixed
sSjBlueVN197 said:
after flashed OOS, can I re-lock bootloader?
Click to expand...
Click to collapse
You can but the process is a bit complicated, on recent updates some time the phone is bricking when we run the query fastboot flashing lock.
So I won't recommend it. Until we can find a easier way.
yashaswee1708 said:
Let me know if the issues are fixed
Click to expand...
Click to collapse
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
sSjBlueVN197 said:
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
Click to expand...
Click to collapse
So currently everything is okay?
yashaswee1708 said:
So currently everything is okay?
Click to expand...
Click to collapse
yup, everything is OK
80W_C.15_OOS_Android13 it's for Ace racing bro?
MIFLASHPRO PROCEDURE
The MiFlashPro procedure is easier (and the easiest to recover your hard-bricked device), as you do not require the installation of any other external program (like python used in MTK Client for example (expect, of course, the drivers)
MTK Client is a more complicated installation as it requires the installation of Python and Git, which can be harder to use commands for people that don't or never used Python and Git, but gives you access to lock and unlock your bootloader with no 168 HOURS wait
In general, newer MTK chips are really easy to unbrick, even from a hard-brick, as it does not requires to open your phone and test-point it (especially this forum MTK 6833), compared to Snapdragon chips, which is the opposite and even costs 25€ to have a "Authorized Mi EDL Account". Keeping that out of the way, lets get to it
FIRST OF ALLInstall the MTK Preload/BROM VCOM drivers for your computer to recognise your phone in BROM state and follow the instructions given in the installation. Attached at the end of the thread
And download any MIUI ROM version from any trusted website (my favorite is mifirm.net, it downloads faster)
INSTALL MIFLASHPRO Attached at the end of the threadThere's two different Mi Flash(es). Mi Flash and Mi Flash Pro.
Mi Flash is only used to flash MIUI in your device, nothing special, probably everyone knows about it.
Then theres Mi Flash Pro (MFP for short). It's an All-In-One (AIO) tool, as shown below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We got the some tabs, but let's focus on the "Recovery" and "SP Flash" tabs, as we do not need the other ones.
Recovery - Recovery flashing. If your device is only booting to Recovery (which can be possible, since someone here has got a case that couldn't boot to fastboot neither system, only to recovery), by writing both your device IMEI's on the spaces, then clicking "Refurbish" leads to a more advanced factory reset than just wiping your data normally. This can get you out of recovery and go back to MIUI however. If it's not your problem, then follow on.
SP Flash - The famous SP Tool. SP Tool is a easy tool to use, may be confusing at first, but then first time a charm and you can get used to it, easily, or after some times. SP Tool is famous for recovering many MTK devices from hard bricks, and thats what we will use to recover your device.
OPEN SP FLASH UP
Here you are, greeted by a nice interface. There's nothing, but I will explain you to it.
There's 3 blank spaces, called Download-agent (DA for short), Scatter-loading file & Authentication file.
DA is to have access to the devices internal storage to be able to do the flashing;
Scatter-loading shows you the mapping of the partitions it will flash on the MTK;
Authentication is just the MTK protection for newer mtk devices that you need to be able to flash (*its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
Now, fill the blanks up:
To find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
To find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
Finally, to find the scatter-loading file, it is in the ROM folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). The scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Done?
Don't flash it yet, as we need to fix a issue with "combo_partisize_check".
Open up the scatter-loading file with Notepad or any text editor, so the text file named "MT6833_Android_scatter.txt".
Now, use the locate function to locate the following:
combo_partsize_check: true
After finding the first one, replace the "true" to "false", and the following one, and so on, till every line of them is set to "false" and isn't able to locate any set as "true".
We are done and finished setting up SP Tool!*Now, we need to bypass the Authentication of our device. Why? Just as the Snapdragon chips, Xiaomi has also implemented a security layer where you need to log in with a "Authorized Mi Flashing Account", which costs money (generally only on Snapdragon devices, I am not sure if we can find any paying service for it), which is really easy to bypass due to BROM.
Download the file "mtkauthbypass.zip" attached in the thread below.
Extract it, open it up, and it looks like this:
Now, press the "Disable Auth" button, you will have 60 seconds to get ready, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompt appearing in the blank space. Should be similiar as this:
(thanks to chopwell20 for image)
After that, immediately open up SP Tool, and press "Download" as fast as possible.
Let it flash, from 5 to 15 minutes.
After it finishes, a blue window with a checkmark appears, disconnect your phone, and just press down the POWER button to boot it up.
And thats it! You have recovered your phone!If you have any issues or it didn't work out, please reply so someone can help you out
(Simplified image to understand better without explanation)
ISSUESCONNECTIONS ISSUE is completely normal!
It is when you try to connect your phone in BROM mode to your computer, but it always shows the error symbol over it.
From what it seems, this should be a issue from the phone and not your computer or the drivers itself
It doesn't mean that it makes you unable to unbrick it, but a lot of patience, as with this issue you will require to keep trying over and over again to bypass it.
So, if you can't bypass the Auth, this is probably it. Just keep trying and trying over again till you get it. There's (probably) no workaround rather than having patience to do it
(This also happens to me every time, so I consider it normal, and with some users such as bg0169 having this same issue, I just considered this was important to address it out, but if you think its not this issue, then reply, better safe than sorry)
I made this thread due to some users bricking their devices, and for every new user that hard-bricks their device to hopefully make this to help them
Amazing guide.
Thanks. and missing screenshot where Authbypass gives you prompt.
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
1lopes said:
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
View attachment 5895435
Click to expand...
Click to collapse
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.
Reelin said:
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.
Click to expand...
Click to collapse
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
1lopes said:
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
Click to expand...
Click to collapse
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
Reelin said:
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
Click to expand...
Click to collapse
I dont know how to recover IMEIs since I always back my NVRAM and write it via MTK Client.
You can try this guide:
Thread '[QUICK GUIDE][HOW TO] Unbrick Camellia/Camellian and restore IMEI' https://forum.xda-developers.com/t/quick-guide-how-to-unbrick-camellia-camellian-and-restore-imei.4502077/
Alternatively, which I am not sure, try looking up a IMEI writer program somewhere in the web for MTK
---------- full quote removed ----------
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking
TheZian said:
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking
Click to expand...
Click to collapse
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
1lopes said:
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
Click to expand...
Click to collapse
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
TheZian said:
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
Click to expand...
Click to collapse
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
I get the same error, anybody know how to fix?
And there is a "MediaTek Preloader USB VCOM" displayed in the Windows Device Manager.
Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
I did have an issue but did not really go through all these stress...I also unbricked it using Brom and my original stock ROM files
Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
Shilze said:
I get the same error, anybody know how to fix?
Click to expand...
Click to collapse
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
1lopes said:
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Click to expand...
Click to collapse
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
Shilze said:
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
Click to expand...
Click to collapse
if your phone is displaying the 3 boot modes in the edge, then yes you are in bootloader*
you should restart to any mode, then right as it reboots you shall boot into BROM immediately and redo the same process
I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader