Hi! I recently replaced the lcd and touch (front) of a Xiaomi mi 6 and all went apparently ok, but when i tried to power it on again it got stuck on a boot loop with no access to recovery menu and only fastboot. I tried things like "fastboot oem unlock" but of course this device isn't that easy to unlock specially when it doesn't boot. So there was I with a locked bootlooping device with no recovery menu access, also tried edl (volume up + down) and all sort of combinations.. only fastboot was available and I couldn't flash twrp.
Then I saw the test point method using the xiaomi mi flash tool, and did it with the fastboot global room and the chine fastboot rom, and some dev roms too, all returned sucess using the flash_all.bat None made the device boot up. At least is no longer bootlooping but if i press the power button it shows the mi logo and goes off again. I can still access the fasboot menu but not the recovery or edl. I tried using a tool called MiUnlock too but returns an error that i should go to settings and developer mode and.... I can't because the phone doesn't boot....
So what I'm left with to try out? Is there a way to run a hardware diagnoses or check any logs with fastboot? How do I confirm the motherboard health? Is there any guide to Jtag this phone, force bootloader unlock?
Related
What happened was that I tried to update via Mi Suite
Everything completed nicely but it just wont boot at all
Is there anyway to wipe data without waiting for the unlocking procedure from xiaomi?
There's no recovery menu apparently
Edit: Managed to solved it by booting into EDL mode
How did you boot it in EDL mode? Just curious... I've tried couple of methods but it wouldn't enter EDL.
nijel8 said:
How did you boot it in EDL mode? Just curious... I've tried couple of methods but it wouldn't enter EDL.
Click to expand...
Click to collapse
Power off or restart
press both vol+ and vol-
insert usb while pressing
should viberate at this point
then it should request to install qualcomm drivers
with the current setup of Max, you cannot boot into EDL from adb? or maybe you are doing it wrong.
what i did was to boot on fastboot mode, then issue the command
Code:
reboot oem edl
the command is different for Mi Max.
I have exactly the same problem. But I'm not experienced on Fastboot, as my second phone is a S3 which is way easier to unlock.
Could you describe in more detail how you have accessed the EDL mode? The only thing I can use is "The Fastboot-Bunny" which does not help at all.
When I use the Vol+/- method my screen stays black and my phone connects to the pc. But how did you continue now?
Could you provide a link to the software?
Thank you very much in advance.
(Can not use my phone since update, exactly the same situation...)
When I do as you told, my phone shows a black screen. I don't know whether the phone is really on or off. I hear the "connect-sound" of windows, it seems to be connected as I can see it as "Qualcomm HS-USB QDloader 9008 (COM10),
but what do I have to do now??
Survivor1990 said:
I have exactly the same problem. But I'm not experienced on Fastboot, as my second phone is a S3 which is way easier to unlock.
Could you describe in more detail how you have accessed the EDL mode? The only thing I can use is "The Fastboot-Bunny" which does not help at all.
When I use the Vol+/- method my screen stays black and my phone connects to the pc. But how did you continue now?
Could you provide a link to the software?
Thank you very much in advance.
(Can not use my phone since update, exactly the same situation...)
When I do as you told, my phone shows a black screen. I don't know whether the phone is really on or off. I hear the "connect-sound" of windows, it seems to be connected as I can see it as "Qualcomm HS-USB QDloader 9008 (COM10),
but what do I have to do now??
Click to expand...
Click to collapse
If you see Qualcomm HS-USB QDloader 9008 (COM10), run Mi Flash and flash the ROM again.
MiFlash won't work due to locked bootloader. I already tried it. Flashing Rom with MiSuite does not help too.
Ooopps no way you can do it yourself. The only chance is the unlocked bootloader. From there you can install twrp then supersu(newer super su fixes the boot for my case)
We have the same problem. But mine is unlocked bootloader.
What i did is boot to fastboot. Flash the rom with miflash. Then i turned it off because its still useless if i wait it still stock at mi logo so i boot fastboot again and flash twrp. from there adb i reboot to twrp then flash supersu. I wait like 10 mins only and yes it boot to normal
You can install TWRP on it follow this guide even if the bootloader is locked:
http://forum.xda-developers.com/mi-max/how-to/installing-twrp-locked-bootloader-t3406501
Survivor1990 said:
MiFlash won't work due to locked bootloader.
Click to expand...
Click to collapse
MiFlash can work both in FastBoot or EDL modes. In FastBoot mode, locked bootloader prevents FastBoot server to execute "flash" command. But in EDL mode, MiFlash works with any bootloader state.
Anyone can help me?
My phone was dead, no fastboot no edl mode. My pc just show me hs-usb diagnostic 900e instead of the qloader.
Maybe any solution please
did you tried test point ?
http://en.miui.com/thread-308092-1-1.html
abhye_x said:
Anyone can help me?
My phone was dead, no fastboot no edl mode. My pc just show me hs-usb diagnostic 900e instead of the qloader.
Maybe any solution please
Click to expand...
Click to collapse
Its driver problem i faced same issue then i tried it on another pc it worked
emuzychenko said:
MiFlash can work both in FastBoot or EDL modes. In FastBoot mode, locked bootloader prevents FastBoot server to execute "flash" command. But in EDL mode, MiFlash works with any bootloader state.
Click to expand...
Click to collapse
So in EDL mode with a locked bootloader will it unlock the bootloader? I am confused abt whether this is the case if I choose "delete all" which will prob incl data & bootloader.
It also seems in fastboot mode, mi flash can only work with unlock bootloader. Any reasons why unlocking is required?
Rgds
Hey guys, My moto Z Play died on me, and it doesn't budge from the AP Fastboot Flash Mode.
I can do the selections using the volume keys but nothing happens when I try to select one of the mode, including the Start, Recovery Mode, QCOM, Bootloader logs. It just gets stuck there until I restart the phone again to this mode using the power and volume down keys.
Only option that works in here is the restart bootloader option which pushes it back to the same screen.
The problem here is I the USB debugging was not enabled before this happened, so I am not able to detect the phone in either the Adb fastboot or in RSD lite.
Looks like its been hardbricked or the internal storage has been corrupted.
Any suggesstions to be able to flash the stock firmware to my phone.
PS: Its a verizon phone.
thanks
azeem.droid said:
Hey guys, My moto Z Play died on me, and it doesn't budge from the AP Fastboot Flash Mode.
I can do the selections using the volume keys but nothing happens when I try to select one of the mode, including the Start, Recovery Mode, QCOM, Bootloader logs. It just gets stuck there until I restart the phone again to this mode using the power and volume down keys.
Only option that works in here is the restart bootloader option which pushes it back to the same screen.
The problem here is I the USB debugging was not enabled before this happened, so I am not able to detect the phone in either the Adb fastboot or in RSD lite.
Looks like its been hardbricked or the internal storage has been corrupted.
Any suggesstions to be able to flash the stock firmware to my phone.
PS: Its a verizon phone.
thanks
Click to expand...
Click to collapse
The question is what did you do to the Verizon "unlocked bootlader" phone to get you to this point?
Hi,
I'm after some advice, how do I place the Moto G5 in Qualcomm mode or EDL mode.
I have entered the bootloader by holding down and turning the phone on, this allows me to use fastboot.
From there I can scroll down to QCOM, but when I press the power button it boots into the normal system instead of EDL mode.
I have also attempted from within fastboot to use:
fastboot oem edl
fastboot oem qcom-on
fastboot reboot emergency
and
fastboot reboot-edl
Although non of these have been sucessful.
I also have access to an EDL cable, although, when I plug the phone in, then flick the switch 10 seconds later, it does not enter EDL mode, it just charges.
The phone sometimes shows as File Storage Linux USB Gadget in device manager, although it is inaccessible, I have updated the laptop to use the qualcomm drivers, although I don't think it will ever recognise it if I can't put the phone into qualcomm mode to begin with.
Any help would be much appreciated.
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
TheFixItMan said:
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
Click to expand...
Click to collapse
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
jameswstubbs said:
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
Click to expand...
Click to collapse
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
TheFixItMan said:
Sounds dodgy to me - sounds like your trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
It's not dodgy, but I fully understand.
Thank you anyway.
try fastboot -i 0x2b4c oem reboot-edl (it's working for LENOVO ZUK Z1 and ZUK Z2)
You can try (if you can/have the TWRP image) to flash TWRP and in reboot options select EDL.
In case the bootloader isn't unlocked you can also use fastboot boot [TWRP image name] to boot directly into TWRP without flashing and then repeat, go into reboot options and select edl.
Not sure if it works for you, if it does let me know that I have helped!
TheFixItMan said:
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
Update: After waiting a few minutes the touch screen started responding for a few inputs, and then stops. Toggling the lock screen a few times allows additional inputs for a few presses.
A couple of months ago the phone started displaying issues with touch input. Locking and unlocking the screen would correct the issue for a while. However, as time progressed the issue got worse.
Today I did a factory reset and since then I have been unable to input any operations. The phone is stuck on the "Hi there" welcome screen and I cannot press "Start". Power and volume buttons work fine, so I attempted to use "adb" to flash a new ROM, or a stock ROM from before July/August.
My PC won't detect the phone when in "fastboot"
What options are left?
Can I dump the stock ROM to an SD-Card and attempt to flash that from the bootloader?
Or do I need to unlock the phone prior to any ROM manipulation?
thanks for any advice
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
mindstorms911 said:
Update #2: I've been able to connect the A2 to my PC and can detect it when in fastboot mode with the "adb/fastboot" tools and with the MiFlash utility. I attempted to flash an earlier version of a ROM but I can't. MiFlash gives:
"Erase boot_a error"
I then attempted to unlock the device with the "Mi Unlock" tool but get "Sorry, your MI ID is not associated with a phone number"
Any suggestions on how to unlock the bootloader?
Click to expand...
Click to collapse
Boot your phone in system (normally).
Find build number in settings, about phone. Tap 7 times or until you've unlock developer options.
Turn on OEM Unlock and USB Debugging.
Turn off phone and boot fastboot mode.
Type 'fastboot oem unlock' and wait until it finish wipe phone.
And it's done.
RFD80M-75679 said:
Boot your phone in system (normally).
Find build number in settings, about phone. Tap 7 times or until you've unlock developer options.
Turn on OEM Unlock and USB Debugging.
Turn off phone and boot fastboot mode.
Type 'fastboot oem unlock' and wait until it finish wipe phone.
And it's done.
Click to expand...
Click to collapse
Thanks, that worked. I am now able to flash an earlier ROM, will see if that fixes the screen input issue.
Flashed an earlier version of the ROM and still had issues, so I finally managed to flash an alternative ROM - HavocOS - and that experienced the issue as well. Looks like the phone has a hardware issue somewhere.
I was using my oneplus 7T normally without root and with bootloader locked when it decided, out of nowhere, to fall into "Qualcomm Crashdump Mode". When I tried to reboot it, it just went into "Qualcomm Crashdump Mode" again. So I went into fastboot mode, unlocked it, and flashed an european ROM from here: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T/ . However when the device tried to boot up it just went to "Qualcomm Crashdump Mode" again, so I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) ( https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/ ) and it worked, but this time when the device attempted to boot up it went into EDL mode and the bootloader was locked and when I tried to unlock it, it gave me an error related to "OEM unlock" not being enabled in developer options. So I tried using "MsmDownloadTool" (hotdogb_14_E.21_201105) again, and somehow this time it actually booted up. Still, after 10 seconds it went into EDL mode AGAIN (note: at this point, I couldn´t get out of EDL mode, I could only boot into anything else after the battery died, in the first boot). So I downloaded another ROM for msm but this time it gave me the error: Firehose GetUsInfo Failed, and the phone seems to disconnect and reconnect. From here I tried multiple ROMs for msm and always received the same error, even using the one I used originally. (Note: I have been waiting for my battery to die for 5 days, and it still has power; also tried removing the battery )
Commands I tried to unlock bootloader:
fastboot oem unlock; fastboot oem unlock-go; fastboot flashing unlock; fastboot flashing unlock_critical
Can someone help me with this issue?
Sorry if the description was too confusing, long, or had any mistakes in terms of English. I am just trying to be as complete as possible.