So, a friend of mine just came to me with a Zenfone 8 that doesn't react to any command. Plugging it into a PC makes it show up as QUSB_BULK_SN######. A quick Google search turns up a bunch of hits regarding a similar issue with Google's Pixel 3 line after a failed update, suggesting the phone was stuck in EDL mode, needing a factory image and a "firehose" file to reflash it. Can anyone point me in the right direction? Thanks in advance
There are no factory fw files that fixes the "QUSB_BULK" bug, only repair centers can fix it for now
Related
Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
I dont think there is way to get the pictures but you can fix the phone tho
_matze__ said:
Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
Click to expand...
Click to collapse
the photos has not synchronized with the google account?
maybe you can try with some tool like this
https://www.wondershare.net/ad/dr-fone/dr-fone-android.html
(it is difficult but you can try)
to reset the device in stock etc you can try with test points & edl mode ...If you have guarantee, send it to service but the photos will be lost of course...
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
_matze__ said:
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
Click to expand...
Click to collapse
Really IDK....Can work may or may not.Not all devices in the list,the list is updated but many users do not add their devices
there are other such applications.hit on google search for example : "recovery data from android phone"
and you will see and others like that
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
_matze__ said:
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
Click to expand...
Click to collapse
Reboot on edl mode & flash stock rom via miflash tool
if your device can boot on fastboot
"fastboot reboot edl" (need unlocked BT)
https://forum.xda-developers.com/showpost.php?p=78963902&postcount=6
from test points > edl > miflash tool (not needs unlocked BT)
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
(the better solution? If you have a warranty send it to service...All this needs some experience)
Hi everyone,
I have bricked nexus 6. It has a locked bootloader plus no bootloader, no recovery, no system no nothing.. If i boot up the phone it goes into bootloader kind of thing and pc can recognize it as a fastboot device but since it has locked and corrupt bootloader there is no command i could get it to run anything.
I know most of you think its simple bricked and cant work it again but refuse to believe that just because the simple fact that i couldnt get any answers from anyone relavent to this. I have been using android for years, basically from the beginning, i know i am not a developer but i think i know few things and i been in similar situations before but this is the first time i got stuck. I know it can be done since its a qualcomm device. There should be a way to put the device in edl mode flash with qfil or something. I know all the post about these kind issues i read them all. Whenever somebody asks about how to put it in edl mode the answer is always go check that post about how to recover from edl mode. Please understand i need to put it in edl mode first to get it out of there.
So if anyone knows a way to put this device in edl mode please help so i can try to recover from there..
I already tried modified fastboot so it can run "fastboot reboot-edl command" it doesnt work for me.
I also tried a custom cable for triggering edl mode on xiaomi devices. But it doesnt work either.
The only other way i know is the short test points on the board or on the chips legs itself.
Like i said there may be no way because the lack of information out there if it is please say so so i can rest
Thank you for your time patience.
The best I can do is point you to [FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1
If memory serves, there was a point when the adb reboot edl was patched in an upgrade. That was rather late in the device's supported lifetime. Maybe when Pie came out?
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! My phone became bricked out of nowhere and i have no idea how to get it to boot again. I am not sure what exactly could have caused it, it happened when i unlocked my phone in the morning and the phone shut off when i touched the screen, it tried to reboot for some time then it went straight into fastboot and i have tried everything i could to get it out but i didn't succeed. The phone responds to some fastboot commands, unless they involve writing, in which case it either returns: "command write failed (no error)" or gets stuck at the writing phase and does nothing. I tried QFIL and MiFlash and both failed as well (MiFlash also reads different physical memory usage in every log), i will include screenshots for refference.
Or is there any chance that the issue is caused by the flash? The phone is around 2 months old so i could try and get it repaired. The phone was running Resurrection Remix 8.6.9 with Englezos kernel and Magisk. It is the first time i faced such a severe issue so if there is any information i left out, feel free to point it out and i'll provide what i can.
Thanks in advance for any help!
Hi, same goes happened to my 9T, ive tried so many flash toos but didn't works,
Last flasher i tried is xiaomi flash tools but its required user id and password account that only available for service center.
Finally i sent my phone over, that is the best option
Good afternoon,
I had bricked this Redmi Note 9 and it was stuck on bootloop, I tried to sort this a while ago and gave up.
After looking through the forum i followed instructions how to place a new ROM onto the device, Once i was doing this someone unplugged my phone and now it is stuck on dm-verity corruption.
The Fastboot does no longer show the bunny it only states FastBoot.
I need major help on this urgently can anyone advise
Try this:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
I have looked at your information but this does not help me.
It seems that whilst it was trying to flash it was unplugged which has switched the USB Debugging off, Therefore i cannot get into the phone via USB
Unless someone can advise otherwise i believe this phone is now finished and will never work again.
Gutted!
BigR1992 said:
I have looked at your information but this does not help me.
It seems that whilst it was trying to flash it was unplugged which has switched the USB Debugging off, Therefore i cannot get into the phone via USB
Unless someone can advise otherwise i believe this phone is now finished and will never work again.
Gutted!
Click to expand...
Click to collapse
No one device is "finished" while their parts are working fine.
Damage due to misuse are totally reversible.
What would you suggest then?
Just flash any stock miui rom.
I managed to get past the corruption.
However i am now met with two bootloops, Followed by safemode and then the error NV DATA CORRUPTED
Just format/erase nvdata.
How do you do that?
BigR1992 said:
Good afternoon,
I had bricked this Redmi Note 9 and it was stuck on bootloop, I tried to sort this a while ago and gave up.
After looking through the forum i followed instructions how to place a new ROM onto the device, Once i was doing this someone unplugged my phone and now it is stuck on dm-verity corruption.
The Fastboot does no longer show the bunny it only states FastBoot.
I need major help on this urgently can anyone advise
Click to expand...
Click to collapse
I had the same issue. This video is what fixed my phone from hard bricked. Don't forget that volume up + volume down must be pressed together, and it must be plugged in whilst pressing the buttons. It's also used to detect the driver. You have to be quick when you see MediaTek. Follow the instructions and you'll see. Python must be installed from the Microsoft Store as the version provided is outdated. Good luck bro. Sorry you had to wait months for someone to experience the same problem. I'm fighting with dmverity right now. lol.