Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me
Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon
Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing
hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha
KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files
I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.
KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?
yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot
Damn!! I hope you find some way to fix your device. Good luck.
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?
yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)
Related
Hi,
Recently purchased a Mi 9 Global version, got the OTA update to MIUI 11, and everything was well. It is a superb phone, but I like to have root on my phones (mostly for Adblocking and System2, better control overall). I tried to install TWRP (custom version for Mi9) because I wanted to install Magisk/Root or try a different rom eventually. Anyway... I made a huge mistake. After trying to reboot, I noticed things had gone wrong, and was stuck in a boot loop. I guess I panicked and tried to flash the phone back to the latest global MIUI rom (Version 11, Android 10, from official site), using the Xiaomi Flash App but I did not uncheck the "clean and lock bootloader" checkbox on the bottom right of the app, which is somehow enabled by default. The flash failed at that time, for unknown reason, but it seems like it succeeded in locking my bootloader, with an empty partition, except for fastboot access and Mi Recovery module. I have to admit I've always been pretty lucky with all my previous flashes on other devices, and I guess I got a little careless. That was pretty stupid of me, in retrospect.
Since then, I am stuck in either Mi Recovery or Fastboot, and it seems that my originally Global Mi 9 with unlock bootloader has now a locked bootloader. Any attempt at either using the Xiaomi Flash utility gives me an error message ("Erase boot error"), and if I boot into Fastboot and try to flash TWRP, I get the "Remote:Erase is not allowed in Lock State" error.
From what I understand, my options are pretty limited now. The phone is still powered on, stuck in Recovery mode and rebooting every 5 or 10 minutes by itself (probably a way to avoid screen burn-in?), but I can't seem to be able to shut it down in anyway, as there are no fastboot commands to send a shutdown signal. And no matter what button combination I press, the phone always ends up rebooting.
I tried the Xiaomi Unlocker utility, but it needs the phone to be out of recovery to check the credentials binding the phone to my account. All data on the phone has been wiped already, so that's not an option. Two options I have seen :
1. Open the battery cover (required a heat gun and risky), to short some pins and try to flash while there is a short to circumvent the security. I'm not that brave yet, and since the phone is still running and has probably about 80% battery, I don't want to use a heat gun on the device.
2. Shady stuff involving paying 30 or 40 Euros to a random guy who can somehow make everything work magically by remotely logging in on my computer via Teamviewer (Not happening in a million years).
I'm wondering if there is an alternative, other than bringing the device to an official Xiaomi store (I'm in Bangkok and they do have one official shop at Fortune Town), but even then, I don't know if they'll just tell me I got myself an expensive paperweight.
Any help/insight regarding this issue would be much, much appreciated!
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
g_seva said:
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
Click to expand...
Click to collapse
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Twomby said:
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Click to expand...
Click to collapse
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
g_seva said:
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
Click to expand...
Click to collapse
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
To enter fastboot mode, long press the volume down key and the power key. Then unlock bootloader with Xiaomi app.
zahdekar said:
To enter fastboot mode, long press the volume down key and the power key. Then flash stock rom.
Click to expand...
Click to collapse
I have managed to enter fastboot mode, as described in my initial post. The problem is that when I try to flash, I get the following error: "Flashing not allowed in lock state".
Twomby said:
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
Click to expand...
Click to collapse
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
g_seva said:
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
Click to expand...
Click to collapse
From what I understand, the "normal mode" needs the tool to be able to access the OS while it's running. I don't have an OS. I will give it a shot tomorrow (3 AM here, exhausted, and don't want to boot into Windows again!), but my hopes are not so high. Anyway, thanks for the help, much appreciated! Will let you know what happens! Cheers!
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
zahdekar said:
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
Click to expand...
Click to collapse
I've stumbled upon this link earlier today. But it's 404 on my end. Can you access it from where you are? Thanks!
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
zahdekar said:
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
Click to expand...
Click to collapse
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Twomby said:
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Click to expand...
Click to collapse
I have the same problem! "The system has been destroyed" (((
And mi unlock tool not work abount 2 days (authorization not passes)
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
zahdekar said:
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
Click to expand...
Click to collapse
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Twomby said:
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Click to expand...
Click to collapse
Hello @Twomby did you managed to get it working it the end?
Same issue here
Hi,
I am encouraging the same issue. Does someone found a solution to this?
tago4ever said:
Hi,
I am encouraging the same issue. Does someone found a solution to this?
Click to expand...
Click to collapse
I came across this Mi8 thread, not sure if it's possible on the Mi9, but he seems to have been able to flash it through EDL mode, you might ask him the question: https://xiaomi.eu/community/threads/mi-8-bricked-from-nowhere.55723/#post-543605
There's also this Mi9 thread: https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966
Something happened to my Google Pixel this morning. Everything was fine last night, woke up this morning and the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx SN:xxxxxxxx.
I did some searching around, and it sounds like the phone might be stuck in Emergency Download Mode (EDL)? Anyone has a solution on how to fix this issue?
(I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.)
BTW mine is Google Pixel 3,
Anyone has the solution !! Please help !!!
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
mindyabiznis said:
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
Click to expand...
Click to collapse
Yeah, but nothing happened! Its EDL mode.
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
mindyabiznis said:
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
Click to expand...
Click to collapse
Thanks for the reply...
I already did all of this but couldn't get the phone out of Emergency Mode,
and I already said (I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide and I'm not able to locate the QSPT Flashable Firmware File for my device Pixel 3.
It's very frustrating to saw that even a pixel phone has to go through this...
It was not rooted / not Bootloader unlocked / or any kind of modification wasn't done with it only an OTA update from Google was installed last wk.
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
mindyabiznis said:
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
Click to expand...
Click to collapse
Yeah, thinking of battery disconnect..
sifatrhmn said:
Yeah, thinking of battery disconnect..
Click to expand...
Click to collapse
Can you disconnect the cable and just let it run out of juice?
Give your information to this proposed lawsuit this office may pursue.
Google Pixel 3 Class Action Investigation - Chimicles Schwartz Kriner & Donaldson-Smith LLP
chimicles.com
When your device appears like this on your PC, it means it's stuck in QPST mode - Qualcomm Product Support Tool. The software is not freely available from Qualcomm, nor are the necessary files that would be required to reprogram the PROM.
Some users have had success leaving their phone to run out of battery. Failing that, there is unfortunately no way to recover the device beyond seeking repair.
After applying the lastest update which turns out is android 11 all google apps stopped working.
When trying to downgrade i ran into the anti rollback protection when using fastboot mode (with multiple different application)
So i figured i'd flash TWRP and see if i could downgrade the rom using TWRP.
When flashing TWRP the regular way wouldn't work (TWRP wouldn't start) i used this method: https://unofficialtwrp.com/twrp-3-4-1-root-xiaomi-redmi-10x-5g/
Which includes flashing vbmeta.img and misc.bin
After doing that my phone is in a bootloop and i cant get into recovery/TWRP of fastboot anymore. So if i hold down volume up or down it just keeps rebooting after seeing Redmi with the unlocked icon on the top. There is a little vibration and then the screen then kind of fades away and it starts again...
After running into a lot of trouble with this @##[email protected]#%@ China only phone, but always being able to recover it, did i really fully brick it this time?
Use this tool and flash fastboot ROM with sp flash
𝐆𝐒𝐌 𝐃𝐎𝐂𝐓𝐎𝐑𝐒 ™
FREE MTK SECURE BOOT DISABLE TOOL (Auth bypass) 💣💣💣💣💣💣💣💣💣 👉https://t.me/gsmdoctors
t.me
Thanks mate. I cant seem to download the file, but if i could, would i have to get my phone in EDL mode to get this working? And if so, does that mean taking of the backplate and connecting pins? Or is there another method?
EDIT: HOLY CRAPOLY! That worked!!! I googled the filename to download that file somewhere else. I had no idea how to use it, but i just ran the tool, clicked disable secure boot and plugged in my phone. It recognized my phone and i was able to flash using SP flask tool!!!! It's running atom_images_V12.0.6.0.QJHCNXM_20201217.0000.00_10.0_cn_ac1b4a7af4 again as i'm typing this!!!
Thanks so much man! I already orderd a POCO F3 because i was sick of dealing with all these kind of problems because of the China only rom and sideloading google apps. But at least it's working again!
Abducted23 said:
Thanks mate. I cant seem to download the file, but if i could, would i have to get my phone in EDL mode to get this working? And if so, does that mean taking of the backplate and connecting pins? Or is there another method?
EDIT: HOLY CRAPOLY! That worked!!! I googled the filename to download that file somewhere else. I had no idea how to use it, but i just ran the tool, clicked disable secure boot and plugged in my phone. It recognized my phone and i was able to flash using SP flask tool!!!! It's running atom_images_V12.0.6.0.QJHCNXM_20201217.0000.00_10.0_cn_ac1b4a7af4 again as i'm typing this!!!
Thanks so much man! I already orderd a POCO F3 because i was sick of dealing with all these kind of problems because of the China only rom and sideloading google apps. But at least it's working again!
Click to expand...
Click to collapse
your welcome
after flash your bootloader get locked?
Nope still unlocked
Abducted23 said:
Nope still unlocked
Click to expand...
Click to collapse
Thanks for reply.
Abducted23 said:
After applying the lastest update which turns out is android 11 all google apps stopped working.
When trying to downgrade i ran into the anti rollback protection when using fastboot mode (with multiple different application)
So i figured i'd flash TWRP and see if i could downgrade the rom using TWRP.
When flashing TWRP the regular way wouldn't work (TWRP wouldn't start) i used this method: https://unofficialtwrp.com/twrp-3-4-1-root-xiaomi-redmi-10x-5g/
Which includes flashing vbmeta.img and misc.bin
After doing that my phone is in a bootloop and i cant get into recovery/TWRP of fastboot anymore. So if i hold down volume up or down it just keeps rebooting after seeing Redmi with the unlocked icon on the top. There is a little vibration and then the screen then kind of fades away and it starts again...
After running into a lot of trouble with this @##[email protected]#%@ China only phone, but always being able to recover it, did i really fully brick it this time?
Click to expand...
Click to collapse
Hi guy, i hope you fine. I have a question about your downgrade, can you help me ? I wanna do downgrade to MIUI 11, my redmi 10x stay in MIUI 12.0.8 but with GAPPS blocks. Do you know if I can do downgrade with oficial Miflashtool ? Already bootloader unlocked. did you try this method ? tks a lot for any help.
vinassif80 said:
Hi guy, i hope you fine. I have a question about your downgrade, can you help me ? I wanna do downgrade to MIUI 11, my redmi 10x stay in MIUI 12.0.8 but with GAPPS blocks. Do you know if I can do downgrade with oficial Miflashtool ? Already bootloader unlocked. did you try this method ? tks a lot for any help.
Click to expand...
Click to collapse
Hi, i'm doing fine thank you
The tool Hsnmastoor linked to in this thread worked perfect for me and was quite easy to use (if you already have the other tools setup on you computer i guess)
After using that tool (to get my phone in EDL mode i think?) i was able to flash my phone back to "atom_images_V12.0.6.0.QJHCNXM_20201217.0000.00_10.0_cn_ac1b4a7af4" (fastboot image) using "SP_Flash_Tool_v5.2112_Win"
- Turn off you phone
- Start the "MTKSecBootDisableV1.0.0R001.ByMofadal" tool.
- Click "disable secure boot". It will say "waiting for bootrom usb device..." (after 1min 20 sec it will time out. click the button again)
- Hold volume up and connect your phone to your computer with the USB cable (while it's still off).
- You should see some phone info in the screen and at the bottom it says:
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
- Open SP_Flash_Tool_v5.2112_Win (flash-tool.exe)
- Download agent should already have "MTK_AllInOne_DA.bin" selected. If not select it from the SP flash tool folder.
- Under scatter-loading file Select the "MT6873_Android_scatter.txt" from "atom_images_V12.0.6.0.QJHCNXM_20201217.0000.00_10.0_cn\images" (i assume you have already downloaded and unpacked the files).
- Click download and let it flash.
BTW i did it this way because my phone didnt boot anymore at all. Not even into recovery or fastboot. Maybe there is another way to downgrade (but it's probably also hard because of the anti rollback protection)
So this method works (just tested it again on my phone now that it's working normally again) but might not be the easiest.
Edit: typo
Abducted23 said:
Hi, i'm doing fine thank you
The tool Hsnmastoor linked to in this thread worked perfect for me and was quite easy to use (if you already have the other tools setup on you computer i guess)
After using that tool (to get my phone in EDL mode i think?) i was able to flash my phone back to "atom_images_V12.0.6.0.QJHCNXM_20201217.0000.00_10.0_cn_ac1b4a7af4" (fastboot image) using "SP_Flash_Tool_v5.2112_Win"
- Turn off you phone
- Start the "MTKSecBootDisableV1.0.0R001.ByMofadal" tool.
- Click "disable secure boot". It will say "waiting for bootrom usb device..." (after 1min 20 sec it will time out. click the button again)
- Hold volume up and connect your phone to your computer with the USB cable (while it's still off).
- You should see some phone info in the screen and at the bottom it says:
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
- Open SP_Flash_Tool_v5.2112_Win (flash-tool.exe)
- Download agent should already have "MTK_AllInOne_DA.bin" selected. If not select it from the SP flash tool folder.
- Under scatter-loading file Select the "MT6873_Android_scatter.txt" from "atom_images_V12.0.6.0.QJHCNXM_20201217.0000.00_10.0_cn\images" (i assume you have already downloaded and unpacked the files).
- Click download and let it flash.
BTW i did it this way because my phone didnt boot anymore at all. Not even into recovery or fastboot. Maybe there is another way to downgrade (but it's probably also hard because of the anti rollback protection)
So this method works (just tested it again on my phone not that it's working normally again) but might not be the easiest.
Tks a lot for reply. But my phone is Miui 12 Android 11 with boot ok and entry in recovery and fastboot (i gues). Miuitool should work with bootloader unlocked to rollback android 10 v12.0.6.0.QJHCNXM right?
Click to expand...
Click to collapse
You can try. I think i got the anti rollback error when i tried that.
The method i described above works even if you pretty much mess up your phone completely, so it's a nice backup plan.
Abducted23 said:
You can try. I think i got the anti rollback error when i tried that.
The method i described above works even if you pretty much mess up your phone completely, so it's a nice backup plan.
Click to expand...
Click to collapse
Ok I will try to follow your steps. I just have to see for where to go because i dont find The tool Hsnmastoor linked and for me i will study how prepare de pc to do this...but thanks a lot for all explanation about this. I dont known what is EDL mode rs (is the same thing about fastboot ? lol)
The link above also didnt work for me, but if you google MTKSecBootDisableV1.0.0R001.ByMofadal you will find other sites that host the file like: https://androidfilehost.com/?w=files&flid=318638&sort_by=date&sort_dir=DESC
Same goes for SP_Flash_Tool_v5.2112_Win. Just google the name like that and you will find links.
Also "EDL stands for Emergency Download Mode, and it's an alternative boot-mode on all Qualcomm devices, existing even lower than the standard bootloader." So its way more basic than fastboot.
Abducted23 said:
The link above also didnt work for me, but if you google MTKSecBootDisableV1.0.0R001.ByMofadal you will find other sites that host the file like: https://androidfilehost.com/?w=files&flid=318638&sort_by=date&sort_dir=DESC
Same goes for SP_Flash_Tool_v5.2112_Win. Just google the name like that and you will find links.
Also "EDL stands for Emergency Download Mode, and it's an alternative boot-mode on all Qualcomm devices, existing even lower than the standard bootloader." So its way more basic than fastboot.
Click to expand...
Click to collapse
Tks for answers. Already read and really not so dificult with your guide lol. i wait 160 hours to unblock bootloader and finally try this... next week apear here to talk about this adventure. Tks a lot
There are methods/tools available to unlock bootloader without waiting. I never tried it because i also had time to wait the week.
Also i assume you can enter EDL mode and flash with the bootloader still locked. But not totally sure about this.
Abducted23 said:
There are methods/tools available to unlock bootloader without waiting. I never tried it because i also had time to wait the week.
Also i assume you can enter EDL mode and flash with the bootloader still locked. But not totally sure about this.
Click to expand...
Click to collapse
Hi, i did oficial upgrade to miui 12.5 and google apps work well without problems, without block. google play, play services, gboard, youtube, chrome works fine. essencial google apps already comes natively.
"comes natively"? Do you mean the ROM already has google apps installed?
Which ROM did you flash? You say upgrade, but you wanted to downgrade to android 10 again right?
Abducted23 said:
"comes natively"? Do you mean the ROM already has google apps installed?
Which ROM did you flash? You say upgrade, but you wanted to downgrade to android 10 again right?
Click to expand...
Click to collapse
yes first i wanted downgrade but my friend did update without problems. So after downgrade i upgrade official to miui 12.06, after 12.07 after 12.02 (Android 11) and finally show me the update to 12.5.2 and i upgrade. About gapps natively i see a video where a guy show that comes essencial google services
So 12.5.2 is android 11 but Google apps work for you? How did you install the Google apps? Can you link to the video?
Abducted23 said:
So 12.5.2 is android 11 but Google apps work for you? How did you install the Google apps? Can you link to the video?
Click to expand...
Click to collapse
yes in my case i already had google apps of version 12.0.2 (but without funcionallity), and when i upgrade to 12.5.2 the gapps works all. I dont known if i can post link of video here, but is here we go (in the case the user did a manual update, he explain in the video how to) Manually Update Redmi 10X / 10X Pro 5G to MIUI V12.5 Stable Rom (NO NEED FLASH) | For users: V12.0.2
Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
romanrsr said:
Hi friends, I currently have the version V405UA020f 00 USC US OP 0310 installed, and I need to go back to some version of ATT since I need it to ask me for the unlock network code. I have downloaded the backup of the user @AsItLies but I don't know how to restore it from QFIL, can someone guide me? I have tried loading only the .xml file but when pressing Download I immediately get an error.
Click to expand...
Click to collapse
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
AsItLies said:
I've not had much luck getting qfil to load a backup, but you could post a screenshot of what you have before it doesn't work, someone may be able to help.
2 ways that will definitely work; 1) do ea partition one at a time (yes, it's time consuming) 2) use bkerler edl utilities (these are python based and it's a command line interface).
So now you know of course, but for anyone else, crossflashing does not unlock the sim. If it's locked, stay on oem firmware until you get it unlocked. Or else u face the prob romanrsr is facing now.
cheers
Click to expand...
Click to collapse
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
romanrsr said:
Hi AsItLies, Thank you very much for sharing your knowledge!
I have been able to flash partition 0 with QFIL, there were no errors but now the phone does not turn on at all. I have put it to charge for more than an hour but it shows no signs of life. It is also not detected by the PC when I connect it. Do you know how I can solve it? Thanks again!
Click to expand...
Click to collapse
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
AsItLies said:
I can only guess, as that isn't usual. It may well still be in edl mode. To get out of edl, hold vol minuse and pwr button for at least 5 sec. And also, leaving it in edl mode, it will 'time out', but it doesn't auto boot by itself.
iirc, when flashing the 'luns' in qfil, after ea one it will reboot and u have to go back to edl mode again.
when you say you 'flash partition 0 with QFIL', is that with the xml? or you did all of slot A by hand (one by one)?
cheers
Click to expand...
Click to collapse
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
romanrsr said:
I do not think it is in EDL mode, since when I connect it to the PC it does not detect any port, and in the device manager it does not detect it either. I've already tried hold vol minuse and pwr button for several seconds, but nothing happens. Screen always black.
I have flashed from QFIL with the xml.
Click to expand...
Click to collapse
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
AsItLies said:
pretty sure that if edl mode 'times out' (because it hasn't been used or accessed), then it's not going to show up in device manager.
yes the flashing with qfil and the xml will need to go out of edl mode and back in for ea lun. Flashing the 0 lun alone isn't going to fix anything, have to do them all.
Your only option here is to keep trying. There's no magical 'press this button' to fix this. If you try and can't get it out of edl mode, try going back in edl mode. The device will go into edl mode from any screen, but in some cases you won't get any kind of a 'count down', you just have to count or maybe the screen will change, then spam vol up.
good luck
Click to expand...
Click to collapse
You were correct! I Press the volume down + power keys, and then pressing the up key several times the QFIL detected it again. I have already flashed your backup and boot OK.
Now I have the following problem, when I insert another SIM it does not appear to enter the unlock code, but I get the error "This phone is permanently locked and can not be unlocked", did you have any experience with this?
It occurred to me to try to update it to the latest version via FOTA and LG Software, but it tells me that the latest version is already installed. Can you think of something? Thanks!
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
AsItLies said:
Unfortunately I've no experience there at all, always buy phones that are unlocked, have never had a carrier locked phone.
check with at&t, if the device is eligible to be unlocked, I think they are obligated by law to help.
cheers
Click to expand...
Click to collapse
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
romanrsr said:
Many Thanks AsItLies, I ask you one last question. I have found some files in the forum (AT&T Android 10 (30b) .bin files), but they don't have the .xml files. Do you know how I can flash these files with QFILL or how to generate the .xml?
Click to expand...
Click to collapse
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
AsItLies said:
Which files exactly are you referring to? There are some files because of IMEI and serial number that you should not flash.
Click to expand...
Click to collapse
Check this:
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
File folder on MEGA
mega.nz
romanrsr said:
Check this:
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Use this xml. I created it to flash Q all at once, there aren't 0-6 luns, as the names are unique and not needed.
But just as a warning, it should work, I've used it, but it's only been tested on my device, which was originally at&t. And, I'd point out, doing this isn't going to unlock the sim.
cheers
Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English
Hi if you can open bootloader, flash stock rom
The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse
RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account