Related
My Redmi Note 6 Pro Global version just rebooted itself out of nowhere and now its showing MI logo and rebooting every 3-5 seconds. I didn't unlock bootloader and had MIUI 10 latest stable version installed. I can still enter fastboot mode. What can I do to fix this?
UPDATE
Over the last few days, these are the things that I've tried:
I can enter Fastboot mode and connect to my PC, but can't enter recovery mode.
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
I tried flashing fastboot rom with MiFlash, but when MiFlash causes phone to reboot towards the end of flashing, the bootlooping problem occurs again and it cannot complete flashing.
I also tried flashing TWRP from fastboot, it says that it's successful, but when I try fastboot boot twrp.img, the same problem: MI logo and constant reboots.
I also tried to use fastboot oem edl mode and my phone is recognized as Qualcomm device, but MiFlash can't flash in this mode, saying that hello packet is not received.
At this point, I don't know what else to do and wondering if this is a hardware problem. Any ideas?
Did you tried to press VOL UP + POWER BUTTON after you flash TWRP? If flashing TWRP doesn't work Try to flash Official MIUI RECOVERY 3.0 That's all you can do. Otherwise you should give it to Mi customer service for faster solution.
I have the same problem, did you manage to solve this issue?
hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.
MI stuck at boot logo
m1s3rys1gn4l said:
hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.
Click to expand...
Click to collapse
Hello all ! same problem here !
i reinstall the last version in EDL mode every week !!
I can not handle it anymore !
sometime he match 1 day sometime 3 week ... everytime he stuck on menu and i can't reboot .
the only version i can use its 10.3.2 global ... all other version don't match !
Sorry for my english (i'm french) and thanx you for your help
hi my redmi note 6 pro is stuck on mi logo its not getting over it .
i dont have any pc or laptop at my home how can i solve this issue
during this lockdown ,and now its showing charging in shutdown mode?
Hello All i have the same problem stuck on MI logo
I have tried to wipe through Mi recovery but no use
I cant flash anything because the bootloader is locked
and i dont want to use EDL mode cuz i am stuck at home and dont have necessary tools for that
My question is can we flash anything using Fastboot command or can we ON usb debugging through fastboot be cause Mi flash wont work until USB debugging in On
Please help
Try another flash tool i.e. Qfil_flash_tool
Hi, I have even tried EDL mode to flash latest rom (android 9,miui11.0.4) using Mi flash tool,still facing the same issue.
It constantly reboots while on charging, and it doesn't turn on otherwise(2 Sec of that logo and then it fades away).
Please Help
any one find solution for this?
Hi, my problem is simpler, so is there any suggestion.
after last official update, due to the internal partition was encrypted, update wasn't finished and I am stuck on MI logo when restarted the phone.
bootloader is unlocked and I can enter to (orangefox) recovery, yet I am not sure what is the best way just to return phone to the bootable state? I presume some wiping is to be done, which is not the problem, just to have as short procedure as possible, preferably without need to re-flash clean ROM from recovery?
regards
mertcanekiz said:
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
Click to expand...
Click to collapse
Hi, i'm in the same situation as you. How did you solve it? with the miunlock app I can't unlock it because it tells me that I have to select something on the phone first, but if the phone doesn't start I can't select anything ..
Try to remove hardware buttons from board and try
redmi 6 pro (bootloader locked)
same problem...
tried methods :
1) using mi flah tool ( error occurred : )
2) edl method (showing: device is locked)
........still stuck on miui logo .........
Hlw all.
Sorry for late to write this post. I will write this post in several parts. So Don't angry if i am late.
PART 1:
HOW TO UNLOCK BOOTLOADER
Click to expand...
Click to collapse
First add a xiaomi account on your device.
Now
1. Go settings
2. My Devices
3. All Specs
4.Miui Version
Tap 5 times to activate Developer Option.
Now return settings menu
And Scroll down
Go
1. Additional Settings
2. Developer option
3.OEM Unlocking [ On This]
Now turn on your phone's internet connection through personal data pack.
Now go Mi unlock status and press add account .
Your Device will be added successfully.
You have to wait 10 days for unlock your bootloader.
Xiaomi privacy policy
Click to expand...
Click to collapse
Now Go xiaomi website and Download xiaomi unlock tool .
You will need a pc or laptop with internet connection for this process.
Extract that zip and open Xiaomi unlock.exe
Login your Xiaomi account.
Backup important Documents on your phone.
Click to expand...
Click to collapse
Power off your Phone
Press "Power button + Volume down"
for fastboot mod .
Connect your phone through usb cable
Now press unlock
When it will complete 100%, Your device will unlocked and Reseted.
PART 2:
INSTALL TWRP
Click to expand...
Click to collapse
First you have to Download TWRP. Official twrp is not release. So you have to download unofficial twrp. it is safe and 100% well for Mi cc9. Because i am using this.
Download this from here:
https://androidfilehost.com/?fid=6006931924117916679
And Also download
adb usb driver version 1.4.3.exe
Install this software .
Next you have to enable usb debugging in your device.
Connect via usb cable to your pc or laptop.
Now unzip the twrp file and go that folder .
See many cmd command file in this zip inside.
Just open last one
Now write
adb devices
Click to expand...
Click to collapse
Screen on your phone and Ok the demon they ask.
Next write
adb reboot bootloader
Click to expand...
Click to collapse
Now write
fastboot flash recovery (copy full name of twrp and paste here).img
Click to expand...
Click to collapse
fastboot boot recovery (copy full name of twrp and paste here).img
Click to expand...
Click to collapse
Twrp will install successfully. just disconnect your phone and press power button + volume up.
Twrp will appear which one you install.
Any help you need just comments here if you failed.
Thats all for today.
Hi, I unlocked the Boot Loader but now I get a screeen in chinese which I am assuming is asking for my Mi account,phone number or email but every time I type any of those a red messege showes under the box which I am assuming meanes that something is wrong. Does anyone had the same problem and solution because I am pretty sure I know my Mi account and my phone number and they are tiped in correct.
dragokanev said:
Hi, I unlocked the Boot Loader but now I get a screeen in chinese which I am assuming is asking for my Mi account,phone number or email but every time I type any of those a red messege showes under the box which I am assuming meanes that something is wrong. Does anyone had the same problem and solution because I am pretty sure I know my Mi account and my phone number and they are tiped in correct.
Click to expand...
Click to collapse
Use those phone number and password which one you sing in for unlock bootloader.you need internet connection to complete this process.
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
majigs said:
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
Click to expand...
Click to collapse
Yes. You have to write:
fastboot boot recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img
easier to rename the file to twrp.img .....
Please help to restore CC 9
Please help me bring my Xiaomi CC 9 back to life. I updated it with MIUI 11.3.3.0.PFGEUXM and my device does not boot normally. My bootloader is locked and an account is not installed in the developer settings. Does anyone know what to do ???
I got error -1 on my smartphone when I added account and device in the '' mi unlock status '' menu.
How to solve
--
Edit:
resolved: I logged out and logged into the Mi account on the device and gave no error
I have to wait 168H to unlock
Tks
GSI's are quite good. I have good SOT with ArrowOS GSI: 12h - 13 h. I think it's more interesting to use Pie GSI's for now.
Where can I get this ArrowOs GSI rom?
Unlock tool stops at 50%
What should I do when the Unlock Tool stops at 50% and reports: couldn't verify the device. Is it because I haven't waited the 10 days yet?
You have to wait to unlock bootloader.
majigs said:
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
Click to expand...
Click to collapse
you dont have to boot the image if you flashed it first, if you did 'fastboot flash recovery recoveryname.img', no reason to do the boot part, just do fastboot reboot-recovery
if you dont want to flash twrp over your stock recovery, then use the fastboot boot recoveryname.img and then mess around with twrp, backup everything and flash a new rom and reboot, next time you reboot to recovery, stock will still be there
Hello. I'm having problems unlocking my new phone. When i open Mi unlock tool, unlock option is greyed out.
I installed drivers through unlock app and option "install drivers" Also installed adb drivers that I got with ulock app through device manager - add legacy hardware
But something is wrong. Someone please help me.
axlina said:
Hello. I'm having problems unlocking my new phone. When i open Mi unlock tool, unlock option is greyed out.
I installed drivers through unlock app and option "install drivers" Also installed adb drivers that I got with ulock app through device manager - add legacy hardware
But something is wrong. Someone please help me.
Click to expand...
Click to collapse
In this unlock tool folder ( Install Drider) one file exist.
You must install it. Then your device will connect.
someone please help me. I unlocked bootloader and trying to install TWRP but everytime I try it's stuck at sending recovery. I've waited for 10 minutes and then I qut. What am I doing wrong?
Commands adb devices and fastboot devices recognize my phone.
axlina said:
someone please help me. I unlocked bootloader and trying to install TWRP but everytime I try it's stuck at sending recovery. I've waited for 10 minutes and then I qut. What am I doing wrong?
Commands adb devices and fastboot devices recognize my phone.
Click to expand...
Click to collapse
Unfortunately I can't help you with that but I have a question did you wait 10 days or not cause my phone just refuses to cooperate with the unlock tool. Sometimes the fastboot logo just disapears and it says press any button to shutdown.
Edit: Just to clarify the flash tool does not say anything about the waiting period. If someone can help me or clarify the situation I would greatly appreciate it.
Alright so it appears to either be a USB gen limitation or just my plain ass stupidity for not installing adb drivers. Hell if I know but either way now it says how many days I have to wait so nice.
TelumLetiferum said:
Unfortunately I can't help you with that but I have a question did you wait 10 days or not cause my phone just refuses to cooperate with the unlock tool. Sometimes the fastboot logo just disapears and it says press any button to shutdown.
Edit: Just to clarify the flash tool does not say anything about the waiting period. If someone can help me or clarify the situation I would greatly appreciate it.
Alright so it appears to either be a USB gen limitation or just my plain ass stupidity for not installing adb drivers. Hell if I know but either way now it says how many days I have to wait so nice.
Click to expand...
Click to collapse
Download 15 seconds adb installer and answer question with three yyy.
I waited 43 hours to unlock bootloader.
I have performed all the steps successfully, but unable to boot into twrp by pressing power + vol up, still booting in stock one, anybody facing the same issue?
kingofmb said:
I have performed all the steps successfully, but unable to boot into twrp by pressing power + vol up, still booting in stock one, anybody facing the same issue?
Click to expand...
Click to collapse
It's power button +volume down... Try again
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)
Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse
I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works
Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer
Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.
Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop
As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?
My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.
Hi guys,
so after I got my xiaomi with a global ROM and wanted to update and that is when I accidentally relocked the bootloader. The version of ROM was invalid apparently and wouldn't let me boot and now I'm stuck in fastboot mode.
My problem is as follows:
-can't enter recovery, stuck at fastboot no matter how many times I try and reboot
-adb not working since I didn't enable it
-bootloader locked (miflash says so and it can't unlock it since I didn't check 'oem unlock enable' and I cannot boot ROM so I can't enable it)
-fastboot flashing says 'not allowed in lock state'
-edl mode not available
I've seen tutorials where people opened their phones to force the phone into edl mode via the testing points but is that the only way`?
Any suggestions on how I could unbrick it?
Much appreciated
yes, it is the only way.
koniv90 said:
Hi guys,
Any suggestions on how I could unbrick it?
Much appreciated
Click to expand...
Click to collapse
you can use this tool to flash the phone on fastboot mode
Xiaomi King Tool - Home.
xiaomikingtool.com
its cost you only 5 credit
Can you flash files by fastboot? if so, flash the global rom images one by one, then reboot
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
I need help please my phone redmi k50 gaming is no recovery and . bootloader is locked
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
This what I'm facing
Dims_Camper said:
yes, it is the only way.
Click to expand...
Click to collapse
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
kskksks said:
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
Click to expand...
Click to collapse
Nope, only very old devices.
NOSS8 said:
Nope, only very old devices.
Click to expand...
Click to collapse
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
kskksks said:
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
Click to expand...
Click to collapse
Have you tried to flash stock rom?
I mean, if you have Chinese rom before, just flash with latest Chinese rom.
Ghanaba said:
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
Click to expand...
Click to collapse
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
jholfran3 said:
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
Click to expand...
Click to collapse
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
flashing is possible with modified firehose programmer (no auth factory loader) or with authorized xiaomi account. both solutions are paid service and cannot advertised here.
please -as always- read the thread you posted in. I can see useful information shared already. wait for other replies.
letsgofly said:
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
Click to expand...
Click to collapse
Hi, try to flash the .img files from the fastboot stock rom whit cdm in fastboot, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
example:
fastboot flash boot boot.img
fastboot flash cust cust.img
etc.
jholfran3 said:
Hi, try to flash the .img files from the fastboot stock rom, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
Click to expand...
Click to collapse
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
NOSS8 said:
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
Click to expand...
Click to collapse
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
jholfran3 said:
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
Click to expand...
Click to collapse
To install a recovery, the bootloader must be unlocked.