Related
I was trying to go back to stock os from cm11 on the Amazon fire phone. Downloaded a stock rom and tried to install using safestrap.
After I pressed reboot the phone turned off but didn't turn back on. It's not responding to anything , not even goes into recovery , but when I connect it to computer by cable , six partitions show up , five of which it says are in need of format , and one contains a folder named image , which has a lot of files.
I'm new to this , got cm by following a simple guide , help pls
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. Ialready disconected the battery- did not work out
Does any of you have any idea?
Thanks
How come no one answered to this issue since 2016
Good day everyone,
I wonder why this issue was not replied to since 2016 on a professional forum. Is it because its not fixable?
I just bought an Amazon Fire Phone 64GB, the AT&T version. I already knew the phone was a complete disaster, but I still bought due to my low budget. Its the SnapDragon 800 series processor which I considered for such a small budget phone. Anyways, I rooted it via KingRoot, installed Safestrap-Kodiak-4.0.1-B01. I then downloaded the Unlocked version of the Fire phone Fireware "update-kindle-35.4.6.6_user_466000820" (since I wanted to avoid AT&T bloatware. I reside outside the States so cant use AT&T, so no use keeping it running all the time and sacrifice my battery) and flashed that. It flashed alright but got stuck after the welcome screen after selecting English (United Sates or UK). I then thought of of reverting it back to its original state Fire OS Ver 3.5, so downloaded "update-fire-phone-121_1.0.1_user_101012120" and now it has no life what so ever. Now it in the same state as mentioned by 2 others on this thread. It shows total 6 partitions with only 1 partition with an "Image" named Dir and a few files around 53MB or so residing in it.
I have snapshots of the Image folder files and the "QHSUSB_Bulk" status shown in Device manager, but I cant seem to find an option here to attach my jpg's here. Gosh! It doesnt get dumber than this.
Requesting help from someone who can help me out with anything at all, links, text, vdo's.
I've already downloaded the following files, but dont have a clue what to do with any one of them
QPST.2.7.460
Qualcomm_Flash_Image_Loader_v1.0.0.3
SRKtool_2.1_droidth
Qualcomm HS-USB QDLoader 9008 Driver Qualcomm HS-USB QDLoader 9008 Driver2.1.0.4
Qualcomm HS-USB QDLoader 9008 Driver Ver8.5
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Now deleted the 29 partitions of the phone.
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
No life in the phone except for QDLoader 9008 (COM4)
Android# said:
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Click to expand...
Click to collapse
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
SohailAzeem said:
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
Click to expand...
Click to collapse
*****Sorry, just realized that you can't get into stock recovery anymore please disregard the following as obviously that would only help if you could enter recovery*****
I am sure you already tried but what i meant to say was if you tried power + volume up button, you end up in stock recovery and that's where you gotta go, and select "apply update from ADB" from the recovery menu.
But even before all this, first make a new folder on your desktop, then download the ADB drivers for windows from here: https://developer.android.com/studio/releases/platform-tools.html
Extract the ADB drivers into the new folder you just made. Now, go to https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550 and download the 4.6.6.1 bin file for Amazon Fire Phone, either version will work with AT&T phone, and also put the bin file in the new folder you made earlier. Rename the bin file to just 'fire' or something short and easy. Now on an empty space in that folder press Shift + Right Click together, and select 'open command prompt or windows powershell from here' depending on your computer OS.
Now make sure your phone is powered off, then press power + volume up together to get into stock recovery, and you will see option "apply update from ADB", select that and when phone is ready, connect it to the computer via usb cable. In the command prompt window on the computer, type 'adb devices' and press enter. It should show the amazon phone in adb devices list. Next, type 'adb sideload fire.bin'. If you named the bin file something else make sure you replace 'fire' with that. It will take about 5-10 minutes and once done it should be able to boot normally. You can use kingroot 4.1 and then replace the kinguser with SuperSU using the supersume app. You can download supersume app by searching online or from google appstore, either one works. Hope this helps.
SohailAzeem said:
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
Click to expand...
Click to collapse
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
bigrammy said:
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
Click to expand...
Click to collapse
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
SohailAzeem said:
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
Click to expand...
Click to collapse
If your able just return the phone as said then they will likely send you a replacement or refund. :good:
Nearly all phones are brickable if you try hard enough but this fire phone is very very easy to brick :laugh:
(In My Opinion only) If you want a cheap almost unbrickable phone then go with the cheap china brands using the MediaTek CPU's. Stay away from the flag ship brands like sony htc lg samsung which use MediaTek CPU's as these manufacturers locked their devices down by removing the MediaTek flashing method and installing their own.
SPFlashTool is the PC software and the Swiss Army knife used for MediaTek so ensure you research :good:
Team MAD (MediaTek Android Developers) Have quite a few devices they support so choose any of those depending on your budget and it will ensure you get some decent updates and running the Latest Android Version. :good:
Do your research by reading the associated threads before you choose.
https://github.com/MediatekAndroidDevelopers
i think you don't read carefully what the Problem is.
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. The Phone is not working not getting ON. The phone is in Dead Condition but if you Connect with PC it shows its Memory Partations. if any phone not getting ON than how can enter to ADB Mode...???
I have searched around for this, but I have not found anyone describing my exact situation. I don't have all of my release versions of everything readily available, but I will describe what my situation is. Please, if you have any input, please help me.
I have a P2XL, unlocked. I've had it rooted for quite a while, but my banking app decided that it now sees my root access and will no longer work. I do just about all of my banking on my phone, so the logical step was to unroot. (By the way, the computer I am using is a MacBook Pro which won't dual-boot windows for some reason, so MacOS it is...)
To be completely up front, I can't tell you every step I took in attempting to unroot. I apologize.
What I do know is that I had it rooted with Magisk and I had TWRP as my recovery. As of right now, I am unable to boot into the OS. Every time I try to boot it goes straight to recovery. (after the boot loader unlocked message). Apparently my TWRP data is encrypted(I don't know the password), and about 75-80% of the time TWRP's touch response is non-existent. Terminal doesn't see my phone at any stage (including fast boot mode when I'm able to boot to fast boot... also a roll of the dice)
I think that if I transfer the correct image files to a USB stick and use the included adapter I might be able to get something to work, but I'm at a loss right now. Please, please help me.
other piece of information: when I have it in fast boot, and connected to my computer the "./fastboot devices" command does return a result showing my phones S/N
sljames0724 said:
other piece of information: when I have it in fast boot, and connected to my computer the "./fastboot devices" command does return a result showing my phones S/N
Click to expand...
Click to collapse
Download latest April image from Google and flash back to stock (Oreo 8.1.0): https://dl.google.com/dl/android/aosp/marlin-opm2.171019.029-factory-96b864b3.zip
Go here for detail guide https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hi there. Sorry for that weird LG device model. I really want to unbrick it as I need a secondary device.
This device have not been use for a long time now, and the EMMC chip inside of it probably degraded and the kernel and boot data is all gone too. The only thing accessable is Qualcomm 9008 flash mode and a mode that cannot be identified by Windows.
I tried to search online to find 9008 Firmwares for this device and got none as this is a uncommon device and most of it is for H810 or H815.
I also want to request for a developer who can make firmwares please make me one. I don't want to use SD card to unbrick since I don't have the SD card larger then 32GB that is Class 10.
I tried to make my own firmware and it didn't work as I missed a file and I don't know what it is.
If you have successfully made a firmware, thank you first of all. Then you can PM me or just spam it on those firmware sharing site and then send a link to me.
Thank you, I hope you understand.
Also, the device cannot boot into any other mode.
I have fixed it. Apparently, a CyanogenOS device's firehose worked fine for this device. So there we go.
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate
chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.
Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..
After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!
I have been following this forum for years and thanks to all the geniuses here through their guides I have always managed to make all the modding I needed.
But not this time, I'm going crazy.
As the title suggests I have a Samsung Galaxy Tab S3 SM- T825 Qualcomm MSM8996 Snapdragon 820 to which I want to root by mounting twrp recovery and magisck.
I've been trying for days but to no avail.
I state that I have adb fastboot odin latest versions, updated drivers etc.
The problem that occurs is this, adb recognizes the device in normal mode.
I flash twrp and everything is fine I go to twrp, I do the steps of ext2 ext4 file system otherwise it will not read the data and again, all is ok.
But as soon as I reconnect the tablet to the usb cable for adb sideload, my windows 10 no longer reads the device, it does not even emit the classic usb sound ... So it does not read it or adb of course, but neither does the pc.
Just flash with odin rom stock android 9 pie, review the tablet both pc and adb again.
Obviously all the procedures with oem unlocked and usb debugging active in file transfer mode.
I've been going crazy for six days to complete the operation, but I can't ....
I have no idea how many guides, tutorials, videos, possible resolutions I have consulted and applied but to no avail
Can someone please help me sort out or figure out what the hell is wrong ...?
I'm about to set fire to my tablet and pc ....
Thanks in advance and sorry for the not perfect English