Develop Bugs

Mi Max Bootloop

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

Recover bricked Mi 6, tried test point method but still nothing

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?

Touch Screen Not Responding

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.

Oneplus 7T bricked in EDL mode (Firehose GetUsInfo Failed)

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.

Bootloading Kyocera DuraXV Extreme

Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?

jonas.sj said:
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
Click to expand...
Click to collapse
My comments below are based on the belief that you are trying to unlock the bootloader.
I am not familiar with this phone but generally the two steps mentioned by you are not enough to unlock the bootloader. After those steps, you'll have to issue a command via adb to unlock the bootloader and if successful, then you can boot into it for further operations. The command will vary between devices, so search and profit.

Thanks, this cleared it up a bit, you are right, I'm trying to unlock it.
I'm trying the command fastboot flashing unlock but only getting the message < waiting for any device >. I read somewhere that I might need some USB drivers but I don't know where to find them. I have the latest version of the standard USB drivers for the phone, but as I understand it I need special drivers for this?

I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock

jonas.sj said:
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
Click to expand...
Click to collapse
It should be a driver issue. When the phone is on and you connect it to the PC/laptop and send the command 'adb devices', does it show an alphanumeric value? Likewise, when you are booted into the bootloader by key combination and send the command, 'fastboot devices', does it show the same alphanumeric response? If so, the drivers are installed properly. If not, either you don't have the correct drivers or they are not installed properly. Try installing the drivers again after disabling driver signing in Windows on your PC (search for it on Google).

Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.

jonas.sj said:
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
Click to expand...
Click to collapse
Are you sure that the key combination for booting into bootloader is what you described in the first post?
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
Click to expand...
Click to collapse
I see Power plus Volume Up as the suggested one from a Google search. Try that.
If you can't even boot into the bootloader with the correct key combination, I don't know how to help you further since we are starting to go in circles. I am sorry.

Hello, thank you so much for trying to help me. It seems I can't boot into bootloader. Volume up + power gives the same result as what I did before.: It opens a "Recovery" menu where I can choose reboot to bootloader, but this option just reboots the phone.
I've been in contact with Kyocera and they say:
Thanks for contacting the Kyocera Customer Support. We will be more than happy to assist you with your concern
In this case allow us to inform you that since this device is a basic phone , it doesn't have the option to activate fastboot mode. By installing something that will change the way the phone works , that will void the warranty that came with the phone. We as manufacture can not help you to modify the software that came with the phone.
So the phone's fastboot mode has been deactivated. But since it's an android I guess it should still be possible with some workaround. I just don't know whee to start, I've been researching for a week with no result.

Something interesting ehre, maybe someone with more coding knowledge can tell what's going on.
I found the source code for the phone and located a file called recovery.c which I guess handles the menu I see when I press volume up + power button. Maybe some clue to why the phone isn't going into fastboot mode?