Develop Bugs

Mi Max bootloader issues

Hi guys.
I need help on a couple of different issues. I received my phone over the weekend - I got the 2/16 variant. I discovered I was on a vendor ROM and flashed the latest Global Stable. This worked fine, and I've had no issues.
I applied to unlock my bootloader yesterday and surprisingly recieved a text stating my request had been approved only a couple of hours later. When I've tried to unlock the bootloader though via mi unlock, it just gets stuck at 50% and can't verify my device.
I've installed the english and chinese version of mi suite in an attempt to ensure the correct drivers are installed, but given that I could flash via EDL method already, I'm pretty sure they are anyway. I then followed a guide on reddit last night whereby the recovery.img in a fastboot rom is replaced by that of the appropriate version of twrp and its all flashed via EDL method.
That worked, to an extent and I was able to boot into twrp but after I had given it the correct permissions I then attempted to boot into MIUI but it just hung at MI logo for a prolonged period - there was absolutely no movement or indication of it coming to life. Then reflashed again via EDL to the Global Stable and it's back to life.
So a few things I need help with:
How can I get this bootlaoder unlocked so I can install twrp an easier way e.g via ADB?
If I can't do that, what are my alternatives?
My phone takes at least an hour everytime I flash it via EDL - is that normal?

[help] [oneplus3] [stuck in boot logo] [softbricked] cannot boot into system [solved]

Hey boss., after flashing open beta 12, the phone started hanging now and then. I tried to contact oneplus forums and they asked me to send the log files. Since they took too long to respond, I went to oneplus service centre. They flashed my phone with old oxygen os and the phone didn't start. It went into bootloop
Then I asked them, they said motherboard is corrupted. I left the place and I requested online customer support from oneplus. They too flshed and concluded the same. Can I know whether flashing/sideloading openbeta created this issue? If so, can you provide me support to avail the warranty on the phone? or recover it via any other method or process?
Please respond as soon as possible. My communication with the world has become limited after this issue. I hope there is some sort of support.
Also note that, the phone can boot into fastboot mode, but bootloader is locked. It can boot into recovery. I tried wiping everything, but the phone is not rebooting.
When I start the phone, it stucks in the boot logo and after a while, the screen becomes blank and a white color notification LED is glowing.
Kindly help me.

i had the same issue last week after updating to 13..and i tried to flash the black theme..it went black..i had nothing....it was like it was bricked... here's how after many failed attempt's..i had to clean out all files including backups.wipe data i had to wipe system i had to clean out all previous files.from TWRP recovery.then i had to download the latest software release then put the zip file in my phone storage not in the download file ..then i had to flash stock recovery.then install the new system..and i made the mistake of trying to use some of my app backups like for one estrong file ..all of them were corrupt.so start fresh.

You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.

TimSchumi said:
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
Click to expand...
Click to collapse
It worked, but no network connection or wifi connection!
Is there a way to bring them back?

SivaMaxwell said:
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
Click to expand...
Click to collapse
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe

TimSchumi said:
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
Click to expand...
Click to collapse
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..

SivaMaxwell said:
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
Click to expand...
Click to collapse
No, reflash the OxygenOS package of the same Version that is installed by the Unbrick Tool (If you can still get itfrom oneplus.net) and then check if Network does work. Also, check your IMEI.

I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.

m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue

I think, I have solved it guys. I'll let you know once completely under control

So, Thank you very much for your support. With this little support from you and my previous Foresightedness helped me restore the phone.
So just in case if any one else faces the same or similar problem, this is the process:
STEP0: If there is any partition corrupted, the device don't boot properly. And, The customer care/ sevice centre guys state it as motherboard problem. Donot Panic. Always take TWRP backup whenever you change your ROM. This Backup helps you to restore whenever you're in trouble. In this particular case, ESF backup is required. So, take a complete backup (everything) in TWRP, it saves your ass.. keep the backup in your PC or any safe Storage (the complete TWRP Folder which is in Internal Memory) before flashing any custom ROM.
Step1: Follow method2 in this guide: https://forums.oneplus.net/threads/g...plus-3.452634/
Step2: if everything is alright, its done. Otherwise, The device boots up with some missing features and details. At this time, you have to unlock the bootloader. See The forum to know how to do it. Basic searching can give you the method.
If you can transfer the TWRP folder from PC to Phone, it's good. But the phone boots itself because of missing firmware. Even Bluetooth couldn;'t be used.
In my particular case, I couldnot copy from PC to mobile or viceversa. So, you cannot copy back your TWRP folder in this situation.
So, Unlock bootloader. Then reboot to system (without doing anything)
Step3: Reboot to bootloader and flash TWRP 3-0.2 version only. otherwise device will be encrypted.
Step4: download Ressurection Remix ROM version : ResurrectionRemix-M-v5.7.4-20161113-PUBLIC-ex-oneplus3 or you can experiment with any other custom ROM but only android 6 (*Marshmallow). Also make sure that you have universal adb drivers. install them if not (search in the forums.)
Step5: goto TWRP recovery, in this, goto wipe option. Drag the swipe to wipe button here. (normal wipe).
Step6: Now, in advanced options, select adb sideload option and select the two wipes in the next menu. Start ADB sideload in the TWRP.
Step7: Now, Start the adb sideloading the custom ROM from your PC. You donot Require Gapps for transferring a file. So donot flash Gapps.
Step8: After the sideload is complete, reboot into system. Now you can transfer files between phone and PC. Now, Copy the Complete TWRP folder into the internal memory. A pop-up asks for merging the folders. Allow the merging, even if you have another TWRP backup there. They don't overlap.
Step9: Now, Boot into TWRP and restore completely. The phone boots up properly, this time. Everything works as expected. every mysterious problem is solved. Now you will get update request if you are on previous version of OOS.
Last but not Least: Please do not use any app recovery tools. they may cause issues while following the above steps
Thank to every XDA member, helping us save the time and money we spend at service center.

m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
TimSchumi said:
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
Click to expand...
Click to collapse
Yes, boss. The EFS is corrupted. But, thanks to TWRP, it also has the option to backup EFS, modem. SO, I used my old backup from Jan2017 to restore it back.
But, TO place TWRP back in phone, the original OOS3.1.2, even after reflashing didn't support. I thought for a while and flashed the All loved RR (MM) . THen, it gave me the scope to t/f the folder to internal memory.
Now, I restored the EFS , Modem, sytem with data. and hell yea!! the phone is back to life.
Complete Backup, Atleast once for 3 months saves your ass..

I am glad it helped. That's the power of Xda.

My OP3 is stuck on the boot animation only while booting up Oxygen OS. At first I thought it was bricked but as I proceeded I found out that it isn't and i'm able to boot other OS on it. I've had Resurrection Remix which I had no problems flashing whatsoever. But I'm having this problem with Oxygen OS. Has anyone experienced this? What do I do? Please help.

[SOLVED] Trying to unbrick phone from "This MIUI version can't be installed on this device" after failed OFFICIAL OS update.

I have a bricked Redmi Note 5 Pro. Stock firmware, locked bootloader, did literally nothing that would cause this. Just updated firmware (it happened few years ago, just now decided to try and repair it), and after update It's stuck in Mi-Recovery 3.0, with options only for "Reboot", "Wipe Data" and "Connect with MIAssistant", with red text at the bottom "This MIUI version can't be installed on this device" (see photo). Tried everything form this menu, nothing solves the problem. I can boot into fastboot but can't use it as the bootloader is locked and debugging is off. I can go into EDL mode but can't flash as I need to log in into Mi Account, and my sister (this phone was hers) forgot the password and even the account which was connected to this device. I was looking for MiFlash that bypasses authorization but can't find any that is not marked as malware (anyone knows of any that is safe?). At was past the warranty and I've tried to ask few phone-repair shops but the said that is unrepairable.
Any ideas what I can check or try next to solve this problem?
BTW. Does anyone knows why all of this happened? As I already said, never did anything with OS, only updated it which caused brick. My only idea is, as this phone was bought not from official store, that it might be a phone that was bought cheaper in china, then flashed with modified global OS and after update it was replaced with official global OS which bricked the phone. No idea if something like this is possible.
Edit [Sep 19, 2021]: I got somewhere. Used Firehose file to flash whyred global image without authenitcation. Got into system. I can at least go into fastboot and it's detected correctly in windows. Now I'm trying to get root, flash TWRP and any non-stock OS. Couldn't flash directly via fastboot because of anti-rollback check. Tried to do "fastboot boot twrp_rn5pro.img" which resulted in FAIL in console (status read failed - too many links) and "The system has been destroyed - click the power button to shutdown".
Edit2 [Sep 19, 2021]: Looks like my bootloader is still locked and that's why I can't flash custom recovery. But when I look in the phone settings it says that my phone is already unlocked. Checking in fastboot via PC says otherwise. Enabled OEM unlocking, but fastboot still says "FAILED (remote: Token Verify Failed, Reboot the device". Can't unlock it using MiUnlock cause they say that I need to set my account as available to unlock in unlock status on my device, but I can't do it as my device says that it's already unlocked.
Edit3 [Sep 20, 2021]: I've tried other tool: XiaoMiTool V2 (by Francesco Tescari). As the option "My device works normally I want to mod it" didn't work I chose "My device is bricked I want to unbrick it". Selected option without unlocking bootloader (wouldn't work). And it actually auto-detected that it's chinese phone and flashed chinese OS (MIUI 10.3 Stable). At the boot I got a prompt that this device is locked and I need to log into my Mi account (the one I logged in in the last ROM - from first Edit), after logging in it let me go through setup (luckily there was English). But phone still says that it's unlocked while it's still locked in fastboot. So in the end it didn't got me anywhere, but at least I know that orginally it was a chinese phone.
Edit4 [Sep 20, 2021]: Finally solved the problem! Used this tutorial. Did everything like shown on video and at the end I have MIUI 12 with unlocked bootloader (this time it's actually unlocked - checked with fastboot). Managed to flash TWRP using dummy.img and flashing to recovery. Couldn't boot from img, but vol+ + power did the job. With working recovery I can do everything else I wanted to do.

I had the same issue, which I also managed to fix. I thought I'd share what I did here.
My phone was bricked with access to MIUI recovery and Fastboot. My phone was locked, however my phone was not linked to my Mi account, and so I couldn't unlock it using the Mi Unlock tool. The only way to get into EDL mode was via the testpoint method. It's not as scary as people may think.
Many of the YouTube videos on testpoint show that you have to touch the two terminals while pushing the cable into the phone. Several times I was able to activate EDL mode without doing both at the same time - i.e. I could just connect the cable and touch the two terminals (I used a paper clip) and the phone would enter EDL mode. I think it might have had something to do with me pressing the power button. In my case, I had to have the battery disconnected from the circuit to get into EDL mode.
I used the Xiaomi Flash tool. Always remember to select not to relock the bootloader. I think it's stupid that relocking is the default option and that the radio buttons are at the bottom of the program and sometimes not visible on a laptop. That's how I got into this mess in the first place!
One of the things that I think causes the "MIUI version" problem is attempting to install the incorrect stock ROM. The phones may be fussy about which stock ROM they will accept. In my case, I thought the phone was a global version, then worked out that it was probably a Chinese version.
I replaced the firehose files in all the ROMs I attempted flashing with the ones supplied on XDA. The Xiaomi Flash tool reported success several times, but when starting up the phone it would go into recovery with the "MIUI version" message. I tried about six different MIUI ROMs with the testpoint method, both global and Chinese, before stumbling on the one that worked (after replacing the firehose files): whyred_images_V11.0.2.0.PEICNXM_20191023.0000.00_9.0_cn
When I got back into MIUI, I linked the phone to my MI account and then attempted flashing the latest LineageOS (which was what I was trying to do in the first place), using the Lineage recovery. The phone wasn't accepting the Lineage recovery, so I flashed OrangeFox-R11.0-Stable-whyred. I had to boot to Orangefox in order to flash it. You copy the Orangefox zip file to your phone using your computer when you have MIUI up and running, then you enter Fastboot and run the following command from your computer:
fastboot boot recovery.img
From Orangefox, you then select the Orangefox zip file on your phone and swipe to install.
Once that was done, I rebooted to recovery and did a wipe of the phone. It wasn't enough for me to wipe Dalvik/ ART Cache and Cache (as recommended), I had to also wipe System, Vendor and Data. (I tried just the first two and the LOS installation was corrupt, even though it was reported as being successful.) I then copied LOS to a micro SD card, inserted it into the phone and mounted it, before flashing LOS by navigating to the zip file on the SD card, selecting it and selecting wipe to install.
Finally success!
I think the key with the testpoint method is to keep trying ROMs until you stumble on the one that works. If the Xiaomi Flash tool reports success, I think it means you are doing something right. I also wonder if a lot of people who have the "MIUI version" issue have a phone with the Chinese ROM and don't realise it.
Hope this helped someone!

by any chances how do you unlock bootloader if you just bypass the mi account?

yoshukii19 said:
by any chances how do you unlock bootloader if you just bypass the mi account?
Click to expand...
Click to collapse
No hacking ... Why did you bypass mi account???

drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
the reason is I got my phone Redmi Note 5 Pro on fb marketplace by swapping my old phone, when I'm using it there's no mi account logged in on my phone then I tried to install the latest MIUI 12 by flashing it on MiFlash but I didn't notice that I didn't change the setting on clean all so it locked my bootloader, after I manage to fix the issue about my phone because it doesn't open and it only boot on recovery with a message "This MIUI...." and make it boot by flashing cn official rom, it says that my phone is locked and I need to logged in the old mi account, I already ask the previous owner but he said he doesn't have an access on that account, even the number and email are already lost

drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.

Aurora333 said:
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Click to expand...
Click to collapse
Why did you quote me?!?

Question Soft brick no backup

Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope

check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com

I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.

historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here

RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know

You have to download the firmware and paste it into the platform tools folder and click flash all.bat

Xiaomi 10T Pro bootloop – possible to save data?

Hi guys,
I have a problem with a Xiaomi 10T Pro. It is in bootloop. The reason for that is unknown (it’s a friend’s phone). The phone settings are basically all standard, meaning the bootloader is locked, stock recovery and stock OS. I can access recovery and fastboot. Safe boot and repair boot out of recovery does nothing. It is just showing the MIUI logo as during the normal boot.
Is there any way to copy the data of the phone (photos would be enough)?
I read about flashing just the boot.img of the firmware but I don’t know which version is running. I am assuming the newest one that come with OTA updates.
I also read that some people wiped the data in recovery (only full wipe possible in stock recovery) and then used some android data recovery software to recover their data.
Not very satisfying options. I would really appreciate a different way. Any ideas?
My first idea was to boot into TWRP but because of the locked bootloader this is not possible.

sexler said:
Hi guys,
I have a problem with a Xiaomi 10T Pro. It is in bootloop. The reason for that is unknown (it’s a friend’s phone). The phone settings are basically all standard, meaning the bootloader is locked, stock recovery and stock OS. I can access recovery and fastboot. Safe boot and repair boot out of recovery does nothing. It is just showing the MIUI logo as during the normal boot.
Click to expand...
Click to collapse
Note that this may be a hardware problem.
As the bootloader is locked, you can only try to erase the data and see if the phone restarts, which is not certain and then try with recovery software, also not certain.
Or before erase the data, this tool:
https://www.xiaomitool.com/V2/
Choose "my device is bricked"
Also without warranty.

I have Ur same exact issue xD been like that for months

NOSS8 said:
Note that this may be a hardware problem.
As the bootloader is locked, you can only try to erase the data and see if the phone restarts, which is not certain and then try with recovery software, also not certain.
Or before erase the data, this tool:
https://www.xiaomitool.com/V2/
Choose "my device is bricked"
Also without warranty.
Click to expand...
Click to collapse
Thank you for your reply.
I haven’t found a different solution yet so despite the fact that this method is not certain I guess I’ll try it in the next couple of days. Before that I’ll also give this Xiaomi tool a try.
Do you know some good data recovery tools that I could use if the device will boot?

sexler said:
Thank you for your reply.
I haven’t found a different solution yet so despite the fact that this method is not certain I guess I’ll try it in the next couple of days. Before that I’ll also give this Xiaomi tool a try.
Do you know some good data recovery tools that I could use if the device will boot?
Click to expand...
Click to collapse
Never had to try to recover my data on a smartphone, sorry.