Related
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
Hi,
Recently purchased a Mi 9 Global version, got the OTA update to MIUI 11, and everything was well. It is a superb phone, but I like to have root on my phones (mostly for Adblocking and System2, better control overall). I tried to install TWRP (custom version for Mi9) because I wanted to install Magisk/Root or try a different rom eventually. Anyway... I made a huge mistake. After trying to reboot, I noticed things had gone wrong, and was stuck in a boot loop. I guess I panicked and tried to flash the phone back to the latest global MIUI rom (Version 11, Android 10, from official site), using the Xiaomi Flash App but I did not uncheck the "clean and lock bootloader" checkbox on the bottom right of the app, which is somehow enabled by default. The flash failed at that time, for unknown reason, but it seems like it succeeded in locking my bootloader, with an empty partition, except for fastboot access and Mi Recovery module. I have to admit I've always been pretty lucky with all my previous flashes on other devices, and I guess I got a little careless. That was pretty stupid of me, in retrospect.
Since then, I am stuck in either Mi Recovery or Fastboot, and it seems that my originally Global Mi 9 with unlock bootloader has now a locked bootloader. Any attempt at either using the Xiaomi Flash utility gives me an error message ("Erase boot error"), and if I boot into Fastboot and try to flash TWRP, I get the "Remote:Erase is not allowed in Lock State" error.
From what I understand, my options are pretty limited now. The phone is still powered on, stuck in Recovery mode and rebooting every 5 or 10 minutes by itself (probably a way to avoid screen burn-in?), but I can't seem to be able to shut it down in anyway, as there are no fastboot commands to send a shutdown signal. And no matter what button combination I press, the phone always ends up rebooting.
I tried the Xiaomi Unlocker utility, but it needs the phone to be out of recovery to check the credentials binding the phone to my account. All data on the phone has been wiped already, so that's not an option. Two options I have seen :
1. Open the battery cover (required a heat gun and risky), to short some pins and try to flash while there is a short to circumvent the security. I'm not that brave yet, and since the phone is still running and has probably about 80% battery, I don't want to use a heat gun on the device.
2. Shady stuff involving paying 30 or 40 Euros to a random guy who can somehow make everything work magically by remotely logging in on my computer via Teamviewer (Not happening in a million years).
I'm wondering if there is an alternative, other than bringing the device to an official Xiaomi store (I'm in Bangkok and they do have one official shop at Fortune Town), but even then, I don't know if they'll just tell me I got myself an expensive paperweight.
Any help/insight regarding this issue would be much, much appreciated!
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
g_seva said:
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
Click to expand...
Click to collapse
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Twomby said:
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Click to expand...
Click to collapse
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
g_seva said:
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
Click to expand...
Click to collapse
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
To enter fastboot mode, long press the volume down key and the power key. Then unlock bootloader with Xiaomi app.
zahdekar said:
To enter fastboot mode, long press the volume down key and the power key. Then flash stock rom.
Click to expand...
Click to collapse
I have managed to enter fastboot mode, as described in my initial post. The problem is that when I try to flash, I get the following error: "Flashing not allowed in lock state".
Twomby said:
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
Click to expand...
Click to collapse
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
g_seva said:
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
Click to expand...
Click to collapse
From what I understand, the "normal mode" needs the tool to be able to access the OS while it's running. I don't have an OS. I will give it a shot tomorrow (3 AM here, exhausted, and don't want to boot into Windows again!), but my hopes are not so high. Anyway, thanks for the help, much appreciated! Will let you know what happens! Cheers!
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
zahdekar said:
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
Click to expand...
Click to collapse
I've stumbled upon this link earlier today. But it's 404 on my end. Can you access it from where you are? Thanks!
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
zahdekar said:
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
Click to expand...
Click to collapse
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Twomby said:
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Click to expand...
Click to collapse
I have the same problem! "The system has been destroyed" (((
And mi unlock tool not work abount 2 days (authorization not passes)
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
zahdekar said:
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
Click to expand...
Click to collapse
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Twomby said:
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Click to expand...
Click to collapse
Hello @Twomby did you managed to get it working it the end?
Same issue here
Hi,
I am encouraging the same issue. Does someone found a solution to this?
tago4ever said:
Hi,
I am encouraging the same issue. Does someone found a solution to this?
Click to expand...
Click to collapse
I came across this Mi8 thread, not sure if it's possible on the Mi9, but he seems to have been able to flash it through EDL mode, you might ask him the question: https://xiaomi.eu/community/threads/mi-8-bricked-from-nowhere.55723/#post-543605
There's also this Mi9 thread: https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966
Just bought a used Mi A2 from a guy. He dosent know what Android version it is and its probably locked. Ive been out of the Android game for many years now, but managed to install ADB and Fastboot on my Mac.
The problem is that the device is boot looping on the Android One logo. Managed to get into Fastboot, and the device shows up in ./fastboot devices. Tried to run this quickie, but only get a "Device is already locked!" message.
So please, point me in the right direction as both the Internet and forums here are loaded with information.
In the end I would like to have a custom ROM, LinageOS or something maybe.
Thanks in advance.
joachimvadseth said:
Just bought a used Mi A2 from a guy. He dosent know what Android version it is and its probably locked. Ive been out of the Android game for many years now, but managed to install ADB and Fastboot on my Mac.
The problem is that the device is boot looping on the Android One logo. Managed to get into Fastboot, and the device shows up in ./fastboot devices. Tried to run this quickie, but only get a "Device is already locked!" message.
So please, point me in the right direction as both the Internet and forums here are loaded with information.
In the end I would like to have a custom ROM, LinageOS or something maybe.
Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
1st try to reboot numerously with external power On (if there is a valid Android One ROM in one of two slots, sooner or later bootloader is to boot into this valid ROM).
In case phone does not have a valid Android One ROM, then next step would be MiFlash'ing via EDL (search for TestPoint Guide in "Guides, ....")
Aerobatic said:
1st try to reboot numerously with external power On (if there is a valid Android One ROM in one of two slots, sooner or later bootloader is to boot into this valid ROM).
In case phone does not have a valid Android One ROM, then next step would be MiFlash'ing via EDL (search for TestPoint Guide in "Guides, ....")
Click to expand...
Click to collapse
Like just boot loop it or hold the power to reboot?
I think the EDL pinout opiton is the way to go after some searching, but Im in a desperate need of a torx driver..
joachimvadseth said:
Like just boot loop it or hold the power to reboot?
Click to expand...
Click to collapse
Some people reported that phone rebooted just itself while bootlooping with external power, others recommended to enter fastboot mode and reboot, others recommended to enter stock recovery mode (note that there is a gotcha of "no command" -> press "Power" and then "Vol-") and then "try again: ....
Aerobatic said:
Some people reported that phone rebooted just itself while bootlooping with external power, others recommended to enter fastboot mode and reboot, others recommended to enter stock recovery mode (note that there is a gotcha of "no command" -> press "Power" and then "Vol-") and then "try again: ....
Click to expand...
Click to collapse
In Fastboot the device only displays "fastboot", no options what so ever. Tried powering on the device without power cable 20 times and no go, boot looped on external power for about 10 minutes, no go.
joachimvadseth said:
In Fastboot the device only displays "fastboot", no options what so ever. Tried powering on the device without power cable 20 times and no go, boot looped on external power for about 10 minutes, no go.
Click to expand...
Click to collapse
Sure there is no options in fastboot mode, "enter fastboot mode and reboot" means just that -> enter fastboot mode and then reboot (either long-pressing power on phone or with "fastboot reboot" command from PC.
I gave you clues, please don't tease me to dictate step-by-step, I do not own your phone.
Aerobatic said:
Sure there is no options in fastboot mode, "enter fastboot mode and reboot" means just that -> enter fastboot mode and then reboot (either long-pressing power on phone or with "fastboot reboot" command from PC.
I gave you clues, please don't tease me to dictate step-by-step, I do not own your phone.
Click to expand...
Click to collapse
Ye sure, thats fine mate
did 'fastboot reboot' about 10 times now and still no go.
Found a Xiaomitool for macOS that has an option for "unbrick my device", but need the previous owners Mi account probably, so Ive asked if he did have a Mi account.
joachimvadseth said:
Found a Xiaomitool for macOS that has an option for "unbrick my device", but need the previous owners Mi account probably, so Ive asked if he did have a Mi account.
Click to expand...
Click to collapse
Most probably that's a false path, as MiFlash, Mi Account, Mi Unlock and other such stuff are for owners of "native" Xiaomi MIUI phones, while Mi A2 boarding Android One is regarded as stepchild. Better search for Android One solutions (in these forums of in developer.android.com)
Aerobatic said:
Most probably that's a false path, as MiFlash, Mi Account, Mi Unlock and other such stuff are for owners of "native" Xiaomi MIUI phones, while Mi A2 boarding Android One is regarded as stepchild. Better search for Android One solutions (in these forums of in developer.android.com)
Click to expand...
Click to collapse
Maybe. I think the phone is stock, just bricked after some update.
Just need to get the bloody torx driver!
EDIT: when I do manage to find a tiny tiny torx driver and open up the phone, disconnect the battery a bit, connect it back up, and its time to connect the two EDL pins, how long do I hold? USB cable plugged in?
Yes I have same issue, I dont understand, why Xiaomi dont do anything with this ridiculous problem, I dont login with mi account because no paid attention to that, and when I install this update the phone get in bootloop
joachimvadseth said:
..., and its time to connect the two EDL pins, how long do I hold? USB cable plugged in?
Click to expand...
Click to collapse
Disclamer: Have not done it myself, but according to numerous sources the needed Steps (here with Windows PC) are:
1. Open (partially disassemble) Phone to reach 2 contact Test Point spots
2. Connect stock USB cable to USB2.x port on MB of PC, but not to phone, start Device Manager (to see that no USB-phone-related devices are connected and later to see that phone will be connected in EDL)
3. Download desired stock fastboot ROM https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 and MiFlash, start MiFlash selecting ROM
4. Span the two contacts with something metal and in this state connect USB cable to phone; Device Manager must show newly connected device detected, then contacts may be open
5. Press "Refresh" in MiFlash, same new device must be displayed
6. MiFlash -> clean all, MiFlash -> flash
7. Assemble phone back and reboot
MHO Notes:
a. when EDL/TestPoint method was forced due to soft-bricking, after unbricking it is better to: (1) fully unlock phone and (2) clean-reflash stock ROM via fasboot
(Reason: this particular specimen is subject to OTA soft -bricking)
b. if EDL/TestPoint method fails with Pie (10.0.17.0 or 10.0.2.0), retry using Oreo 9.6.17.0 or 9.6.9.0.
---------- Post added at 01:01 PM ---------- Previous post was at 12:52 PM ----------
Onilink90 said:
..., and when I install this update the phone get in bootloop
Click to expand...
Click to collapse
Xiaomi is just repacking Google's Android One updates, and, obviously, does not spend much money for testing OTAs (as AndroidOne phones are not their main market items). From the other hand, Google's Android One A/B Slots feature was developed for so called friction-less ( muhaha ) reverting to previously working ROM when updated ROM fails to boot. So, an Android One phone bootlooping after OTA MUST reboot to previous version of ROM sooner or later (supposed to be 7 retries), sure if phone is not compromised / tampered by previous user actions.
Aerobatic said:
Disclamer: Have not done it myself, but according to numerous sources the needed Steps (here with Windows PC) are:
1. Open (partially disassemble) Phone to reach 2 contact Test Point spots
2. Connect stock USB cable to USB2.x port on MB of PC, but not to phone, start Device Manager (to see that no USB-phone-related devices are connected and later to see that phone will be connected in EDL)
3. Download desired stock fastboot ROM https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 and MiFlash, start MiFlash selecting ROM
4. Span the two contacts with something metal and in this state connect USB cable to phone; Device Manager must show newly connected device detected, then contacts may be open
5. Press "Refresh" in MiFlash, same new device must be displayed
6. MiFlash -> clean all, MiFlash -> flash
7. Assemble phone back and reboot
MHO Notes:
a. when EDL/TestPoint method was forced due to soft-bricking, after unbricking it is better to: (1) fully unlock phone and (2) clean-reflash stock ROM via fasboot
(Reason: this particular specimen is subject to OTA soft -bricking)
b. if EDL/TestPoint method fails with Pie (10.0.17.0 or 10.0.2.0), retry using Oreo 9.6.17.0 or 9.6.9.0.
---------- Post added at 01:01 PM ---------- Previous post was at 12:52 PM ----------
Xiaomi is just repacking Google's Android One updates, and, obviously, does not spend much money for testing OTAs (as AndroidOne phones are not their main market items). From the other hand, Google's Android One A/B Slots feature was developed for so called friction-less ( muhaha ) reverting to previously working ROM when updated ROM fails to boot. So, an Android One phone bootlooping after OTA MUST reboot to previous version of ROM sooner or later (supposed to be 7 retries), sure if phone is not compromised / tampered by previous user actions.
Click to expand...
Click to collapse
Managed to get hold of a torx set - phone is now open, battery disconncted. USB-C cable ready (dont have USB-A-C, only USB-C-C). Installed MiFlashTool on my PC and tried to get hold of the drivers. MIFlash is giving me a hard time whineing about drivers. Giving me a erorr message, something about JIT-debugging. Only got it in norwegian.
Edit: managed to flash the stock ROM I think. Fuzzed around a bit with the qualcom driver. Now I have a white screen with a rainbow passing over it..
Edit 2: and we're there! MIUI is in - now time to get rid of it!
Edit 3: think I managed to flash TWRP now - do I need root? Can I just flash a Pixelexperience ROM now or do I need to do something else? Used the Android 9 fastboot image earlier, if that has anyting to do with anything.
Something happened to my Google Pixel this morning. Everything was fine last night, woke up this morning and the phone won't turn on or reboot. Power button isn't responsive, Power button + Volume down to get into recovery mode is also not responsive. When I connect my phone to my PC I also get QUSB_BULK_CID:xxxx SN:xxxxxxxx.
I did some searching around, and it sounds like the phone might be stuck in Emergency Download Mode (EDL)? Anyone has a solution on how to fix this issue?
(I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide: https://forum.xda-developers.com/t/guide-how-to-return-to-stock-flash-images-with-qfil.3901510/.)
BTW mine is Google Pixel 3,
Anyone has the solution !! Please help !!!
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
mindyabiznis said:
Have you tired holding volume up + power together for more than 10 seconds?
That's a hard shut off, should get you out of whatever mode you're in.
Click to expand...
Click to collapse
Yeah, but nothing happened! Its EDL mode.
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
mindyabiznis said:
From what I've read it looks as though your only option is to flash some firmware
How to fix a phone that’s stuck in emergency mode - Smart Mobile Phone Solutions
Is your cell phone stuck in Emergency Mode? Did your phone turn on but all you can see on the screen is “Emergency Mode!!”? Don’t panic! This article will
smartmobilephonesolutions.com
If you can't find a way of getting out of it then it says you should file a warranty claim and get a replacement phone.
Apparently it's very rare but it can happen when recently rooted or having recently flashed a custom ROM.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
This website shows you how to get into it using adb commands or fastboot commands, that could work to get you out of it.
Click to expand...
Click to collapse
Thanks for the reply...
I already did all of this but couldn't get the phone out of Emergency Mode,
and I already said (I can't locate the firehose (.mdn of .elf?) files to complete the steps in this guide and I'm not able to locate the QSPT Flashable Firmware File for my device Pixel 3.
It's very frustrating to saw that even a pixel phone has to go through this...
It was not rooted / not Bootloader unlocked / or any kind of modification wasn't done with it only an OTA update from Google was installed last wk.
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
mindyabiznis said:
Have you had the phone long? Can you make a warranty claim?
Seems as though mdn and elf files are used by the android Web installer, so maybe try flashing to stock from the Google Web installer website.
Failing that you would have to open it to disconnect the battery, that would fix your problem.
Click to expand...
Click to collapse
Yeah, thinking of battery disconnect..
sifatrhmn said:
Yeah, thinking of battery disconnect..
Click to expand...
Click to collapse
Can you disconnect the cable and just let it run out of juice?
Give your information to this proposed lawsuit this office may pursue.
Google Pixel 3 Class Action Investigation - Chimicles Schwartz Kriner & Donaldson-Smith LLP
chimicles.com
When your device appears like this on your PC, it means it's stuck in QPST mode - Qualcomm Product Support Tool. The software is not freely available from Qualcomm, nor are the necessary files that would be required to reprogram the PROM.
Some users have had success leaving their phone to run out of battery. Failing that, there is unfortunately no way to recover the device beyond seeking repair.
Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English
Hi if you can open bootloader, flash stock rom
The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse
RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account