Develop Bugs

[Debrick] How to recover the hard bricked phone?

Hello,
has anyone found a solution how to debrick the hard bricked FirePhone (64 GB)?
Currently the phone is recognized as QHSUSB_BULK -> Qualcomm HS-USB QDLoader 9008.
I tried the following tools for recovery:
ADB and FastBoot
- Cannot found device.
QFIL
QPST
- Which programmer can be used? (MPRG8974.mbn)
MiFlash
- Wrong programmer (error 0x8007000b).
BoardDiag
- How to prepare the partition.txt and extract the fw_image?
QBoot
- How to prepare the singleimage.bin?
QMSCT_DL_EMMC_TOOL
- Partitions are not recognized

Noone knows, Poke around and if you find anything, post here so we get to know too.

Little better situation for me ...
From TWRP Recovery, I restarted to system before flashing CM ROM and now I could not get to TWRP Recovery. Of course the phone is stuck at AMAZON logo while booting with no ROM installed. I could get into Fire's Recovery which is very constrained. I have just got access to ADB Sideload. Even when i tried to sideload the Fire OS Stock Rom, it failed at signature Verification. How do I toggle signature verification off when i give the command "adb sideload rom.zip" . Is anyone aware of any switch that I can append to toggle off the verification checking?? All Android Gurus out there... Kindly share your valuable suggestion... Thanks ..

manojvasanthram said:
Even when i tried to sideload the Fire OS Stock Rom, it failed at signature Verification. How do I toggle signature verification off when i give the command "adb sideload rom.zip"
Click to expand...
Click to collapse
The stock recovery doesn't support ZIP files, it's only for sideloading official BIN files released by Amazon.

Bingo Bronson said:
The stock recovery doesn't support ZIP files, it's only for sideloading official BIN files released by Amazon.
Click to expand...
Click to collapse
I did try the bin files. it threw up assert error for the device name "kodiak ,.. then i edited the relevant part of the script inside the bin file and rebuilt it and tried to side load, but the signature verification failed. Can you please let me know where can i get the signed versions of stock rom for Fire phone ?
Thanks

Any luck brother with this issue? We r on the same boat
BetaIQ said:
Hello,
has anyone found a solution how to debrick the hard bricked FirePhone (64 GB)?
Currently the phone is recognized as QHSUSB_BULK -> Qualcomm HS-USB QDLoader 9008.
I tried the following tools for recovery:
ADB and FastBoot
- Cannot found device.
QFIL
QPST
- Which programmer can be used? (MPRG8974.mbn)
MiFlash
- Wrong programmer (error 0x8007000b).
BoardDiag
- How to prepare the partition.txt and extract the fw_image?
QBoot
- How to prepare the singleimage.bin?
QMSCT_DL_EMMC_TOOL
- Partitions are not recognized
Click to expand...
Click to collapse
Ive read we need a system image of a running phone and flash it onto the bricked one to make it work, but I dont see any practical solution to this problem. I am a newbee, dont hae much knowledge. In experimenting, I have also deleted its eMMC paritions. Now, even the eMMC is not detected on the PC. Just connecting Qualcomm HS_USB QDLoad 9008 (Com4).

Oops! Erased laf_b - QFil no longer sees GPT table.

I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't get into fastboot to install TWRP and Lineage OS, so I ended up trying to erase laf_a and laf_b like it says to do in the V40 Qfil guide. Big mistake. Qfil and windows both recognize it as a 9008 device on Com3, but can't access the partitions. Basically I managed to accidentally erase laf_b from QFIL and this has corrupted my GPT. Now the QFIL partitioner can't see my partitions. Can you help? I may need a flat pack or something?

I got out of 9008 mode. I had to completely re-write the partitions using qfil. Now I'm on 20e and Pie, but my IMEI reads 0. Drat. Apparently it's forbidden to discuss it - so.... guess I'm out of luck.

CharFalco said:
I got out of 9008 mode. I had to completely re-write the partitions using qfil. Now I'm on 20e and Pie, but my IMEI reads 0. Drat. Apparently it's forbidden to discuss it - so.... guess I'm out of luck.
Click to expand...
Click to collapse
I got the same error as you when accidentally deleted the partition of LG G7. Now the phone stops at 9008. How can you get out of 9008, please guide me. Thank you very much!

Now your imei permanently gone there is only one option for single sim calling without volte stock VM only will work

Recover data from fastboot mode?

I have a redmi note 5 pro (whyred) device which is stuck at mi logo. I cannot go into recovery mode, but am able to enter fastboot mode. The device is locked and its usb debugging is also not enabled. So when I try to flash boot.img it says I need to unlock bootloader first. When I try to unlock bootloader, token error is shown. Any solutions to be able to get device files? Or at least to fix the device wiping it?
Thanks in advance!

Use test point method to force your phone go to EDL. Run QFIL, with "Flat Build" selected and then select a working programmer. Go to Tools-Partition Manager and wait for it reading GPT. Then select "userdata" partition, right click and select "Manage Partition Data". Click "Read Data.." and it will dump all data of userdata partition.
If you want to wipe all and clean flash your phone, go download the fastboot ROM you want, replace the original programmer and Flash it with QFIL.

Yuki1001 said:
Use test point method to force your phone go to EDL. Run QFIL, with "Flat Build" selected and then select a working programmer. Go to Tools-Partition Manager and wait for it reading GPT. Then select "userdata" partition, right click and select "Manage Partition Data". Click "Read Data.." and it will dump all data of userdata partition.
If you want to wipe all and clean flash your phone, go download the fastboot ROM you want, replace the original programmer and Flash it with QFIL.
Click to expand...
Click to collapse
Hi Yuki,
I have a Xiaomi MI 9T Pro with black screen (nothing shown on it), USB Debug is enabled but using adb I get only the unauthorized state, both in standard and recovery mode (I can recognized the boot method by checking if the phone's IP address is shown into the wifi router's client list, or by calling the SIM inside the phone).
Due to the unauthorized state, and because it isn't possible to connect an external keyboard via OTG cable (phone is the server) and a data cable (phone is the client) ad the same time, I cannot use adb to access the phone internal memory.
If I understood properly your explanation this can be done using the FASTBOOT option.
Can you courtesly explain me what is the EDL? And QFIL? Can you share with me one or more links to appropriate documentation?
Thank you very much for your help and attention.

Tamagnun said:
Hi Yuki,
I have a Xiaomi MI 9T Pro with black screen (nothing shown on it), USB Debug is enabled but using adb I get only the unauthorized state, both in standard and recovery mode (I can recognized the boot method by checking if the phone's IP address is shown into the wifi router's client list, or by calling the SIM inside the phone).
Due to the unauthorized state, and because it isn't possible to connect an external keyboard via OTG cable (phone is the server) and a data cable (phone is the client) ad the same time, I cannot use adb to access the phone internal memory.
If I understood properly your explanation this can be done using the FASTBOOT option.
Can you courtesly explain me what is the EDL? And QFIL? Can you share with me one or more links to appropriate documentation?
Thank you very much for your help and attention.
Click to expand...
Click to collapse
I've searched for this model and it's equipped with a Qualcomm SM8150 Snapdragon 855 chipset. As far as I know, there are no unlocked programmers available on the Internet for this phone. Please note that I do not own this phone. You can try searching the Internet extensively to find an unlocked programmer.
Please fully read my post before you take anything into action.
------------------------------
I may assume your bootloader is unlocked. Try to flash partitions without metadata and userdata. FLASH at YOUR OWN RISK. Only flash system partitions and try not to touch firmware partitions.
------------------------------
It's a lot easier to read your userdata if you have 3rd-party recovery installed. Boot to recovery and copy all your data to your computer.
------------------------------
It's possible to recover your userdata in EDL only if you reached the requirements listed below:
1. You must have a vaild programmer specified to "Qualcomm SM8150 Snapdragon 855" and should be signed with Xiaomi's private key. If this programmer is made for SM8150 but came from another OEM you can try it out but I can't guarantee it will work.
2. Your "userdata" partition MUST NOT be encrypted.
PS: On modern Android versions 11-13, it is impossible to decrypt data under strong encryption even if you have the key. In case of emergency maybe you can dump the data and key and turn to a professional data recovery company for further assistance.
------------------------------
Regards.

Thank you Yury, but unfortunately:
- the bootloader is loacked
- Android is v12 (so I assume that the userdata partitionm is encrypted)
- I found (thanks to alexc) a loader for Snapdragon 855 and I'll test it, but probably it will useless even if it will work by reading your notes... sigh!

Yuki1001 said:
I've searched for this model and it's equipped with a Qualcomm SM8150 Snapdragon 855 chipset. As far as I know, there are no unlocked programmers available on the Internet for this phone. Please note that I do not own this phone. You can try searching the Internet extensively to find an unlocked programmer.
Please fully read my post before you take anything into action.
------------------------------
I may assume your bootloader is unlocked. Try to flash partitions without metadata and userdata. FLASH at YOUR OWN RISK. Only flash system partitions and try not to touch firmware partitions.
Click to expand...
Click to collapse
Unfortunately it isn't, so I cannot flash anything!
Yuki1001 said:
------------------------------
It's a lot easier to read your userdata if you have 3rd-party recovery installed. Boot to recovery and copy all your data to your computer.
Click to expand...
Click to collapse
The phone is running the original Android 12 and OEM recovery, I haven't the 3rd-party recovery installed...
Yuki1001 said:
------------------------------
It's possible to recover your userdata in EDL only if you reached the requirements listed below:
Click to expand...
Click to collapse
The phone switch to fastboot, the devices cmd lists the serial number in fastboot mode, but there is no way to switch it in EDL:
- fastboot oem edl returns FAILED (remote: 'Error Invalid Parameter')
- $ ./fastpwn oem edl from https://github.com/bkerler/edl get the same remote error
- reboot.bat from https://forum.xda-developers.com/t/...boot-no-more-test-point-method-kenzo.3398718/ reboots the phone in default mode (I can find it's IP address on wifi client's list and adb returns its serial followed by unauthorized)
Any another method to switch this piece of hardware in EDL mode?
Yuki1001 said:
1. You must have a vaild programmer specified to "Qualcomm SM8150 Snapdragon 855" and should be signed with Xiaomi's private key. If this programmer is made for SM8150 but came from another OEM you can try it out but I can't guarantee it will work.
Click to expand...
Click to collapse
Thanks to alexcs, I downloaded a programmer for 855 SOC: it is untested, but I cannot try it until the phone doesn't switch to EDL mode.
If you have other idea I'll test it.
Many thanks
Yuki1001 said:
2. Your "userdata" partition MUST NOT be encrypted.
PS: On modern Android versions 11-13, it is impossible to decrypt data under strong encryption even if you have the key. In case of emergency maybe you can dump the data and key and turn to a professional data recovery company for further assistance.
------------------------------
Regards.
Click to expand...
Click to collapse

Tamagnun said:
Thanks to alexcs, I downloaded a programmer for 855 SOC: it is untested, but I cannot try it until the phone doesn't switch to EDL mode.
If you have other idea I'll test it.
Click to expand...
Click to collapse
Congratulations, you're in luck! Once you've loaded the programmer, you can send a <read> command to test whether it can be used. If successful, you'll be able to access all sectors and possibly engage a professional data recovery service to help you decrypt all the data.
DO NOT send any command like <program> <erase> or your data may be lost forever!

Ok Yuri, many thanks for your encouragement.
At the moment I've tried to replace the AMOLED display and the flat cable a second time, but it was useless, the issue is on the mainboard, the display driver is burned because the previous shortage inside the flat connector.
Yuki1001 said:
Congratulations, you're in luck! Once you've loaded the programmer, you can send a <read> command to test whether it can be used. If successful, you'll be able to access all sectors and possibly engage a professional data recovery service to help you decrypt all the data.
Click to expand...
Click to collapse
Do you know someone that can help me to decrypt the userdata partition?
Yuki1001 said:
DO NOT send any command like <program> <erase> or your data may be lost forever!
Click to expand...
Click to collapse
Sure! I'll follow your suggestion!

Question My oneplus 9 pro got stuck in edl mode

Hi there, I am encountering the following issue.
It is a hindi op9 pro
The situation:
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
Any ideas or advice? Plz help

If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).

Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
it keeps on cycling back to 9008 so what you meant by xbl or abl is broken? Any solution ?

Renate said:
Can you locate the Firehose loader?
Click to expand...
Click to collapse
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
My msm tool from that

Renate said:
Have you tried various USB problem solving, different cables, different ports?
Click to expand...
Click to collapse
Yes I think it is no issues with my cable

Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
FOR MORE DETAILS
I tried upgrading my device using fastboot firmware according to the following according to this article
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
when I reached to put commands in cmd and wrote
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
then reboot by
fastboot reboot fastboot
it gets stuck in edl mode and no anything showing just " Qualcomm HS-USB QDLoader 9008" showing in the device manager, appearing and disappearing about every five seconds
so the situation is
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in the device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always

I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.

Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Click to expand...
Click to collapse
Fastboot commands already worked and I used them to upgrade my phone according to the article above, so when finished, I put a reboot command, and then it got stuck on EDL mod, so I tried to repair it using MSM tool it always says Sahara communication failed, any way to fix it plz my phone is new
Click to expand...
Click to collapse

You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.

Renate said:
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Click to expand...
Click to collapse
thank you but is there a video explaining it bcz I am a noob in this stuff plz.
or you can contact my device using TeamViewer and try to fix it plz.

I don't know your partitions well enough.
If it wants a two stage reflash with 1/2 by (abl) fastboot and 1/2 by (recovery) fastbootd then you need a working recovery and I'm not sure that you have one.
The original post didn't indicate that you were able to reach/use fastboot.
I jumped on this because it seemed to be about USB/Sahara which I know something about.
We need the advice of somebody who knows more about your model.
Sorry

Can you tell how you ended up in this state? If you are a noob, why did you start wipe stuff from your phone without knowing how to what you are doing?
I would guess you thought a custom rom sounded nice but you don't have a clue what to do when things are starting to go south..
Edit: We, as a community always try to help out as much as we can but (and there is a BIG but) you have to understand the basics before you even start to do stuff or you will learn the hard and in some cases expensive way.
Read and do research at least for a few month, like reading most of the threads here and try to figure out how things work.

recovered my noodlep a week ago using this:
How to recover your device after flashing incorrect DDR xbl images
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now... Even I was aware which DDR model was my device, yes.. I did it :D - flashed by mistake DDR4 xbl.img to my DDR5 noodlep...
forum.xda-developers.com
You may want to check it out....
Best luck. and don't worry. Just follow the steps and you'll recover your device.

Hardbricked Redmi 7. Locked Bootloader. How do I install Stock ROM?

I was using LineageOS on my Xiaomi Redmi 7. I wanted to give my device for a phone exchange so wanted to install the stock ROM. I erased my device completely using twrp. Then I started installing the stock ROM using MiFlashTool. I chose the `clean & lock` option. The flashing process failed. My phone started showing `System destroyed...`. I suspect that this is a hard brick caused by the use of `clean & lock` option, which might've locked my bootloader. I cannot flash the orangefox recovery.
I have acces to fastboot mode but when I ran:
Markdown (GitHub flavored):
fastboot oem unlock
shows:
Markdown (GitHub flavored):
fastboot oem unlock
FAILED (remote: 'Token verification failed, reboot the device')
fastboot: error: Command failed
&
Markdown (GitHub flavored):
fastboot flash recovery orangefox.img
too shows a similar error
I tried using "Franseco Yates - XiaomiTool-V2" in which I chose the "unbrick" option and proceeded. I have forgotten my Mi Account ID. Although, I have my phone number & Email, it wouldn't send me the code on my phone number. So I couldn't sign in as I've also forgotten my password to my Mi Account.
Is there any method to fix this? Hopefully an unpaid one?

you have tagged that question EDL so you already know the answer. on locked bootloader you can flash only in EDL mode. try one of these commands.
Code:
fastboot oem edl
fastboot reboot-edl
https://forum.xda-developers.com/t/...tboot-no-more-test-point-method-kenzo.3398718
then install the Qualcomm HS-USB QDLoader 9008 Driver and flash with MiFlash or XiaomiTool-V2

alecxs said:
you have tagged that question EDL so you already know the answer. on locked bootloader you can flash only in EDL mode. try one of these commands.
Code:
fastboot oem edl
fastboot reboot-edl
https://forum.xda-developers.com/t/...tboot-no-more-test-point-method-kenzo.3398718
then install the Qualcomm HS-USB QDLoader 9008 Driver and flash with MiFlash or XiaomiTool-V2
Click to expand...
Click to collapse
Even EDL didn't work for me. It can now only be done with an authorised account. Mi stores are asking for 450 rupees to fix it. It is still a cheap repair. But I bought a new phone so idc anymore.

you still can repair it. all you need is No Auth Firehose (Loader)