Hi All，
I do believe here is the god place who will settle my problem~~ really need help.
my hdx7 is good and no any damages physically, but afte I tried many times for flashing CM13 and different root tools, finally the last time when I flash CM11 rom, the Startrap showing Sucessful, but when I click reboot device, my hdx7 there is no longer boot again, even there is a system already done.
now my hdx is bricked and also stuck by white Kindle Fire logo, I can use the combination key（vol+ and power） boot up Fire System Recovery, but only reboot and factory setting can be selected.
As described above, here is the key about my HDX7, if I want to apply any operations for my devices, this HDX7 cannot connect to computer no matter what kind of computer or different cable, all ADB, root tool, device manager.........there is no HDX7~~
tips: before last failed work I had 4 times flash CM11 system successed but the 4th time computer also cannot find device.
So god please help me~~ Thanks a lot
ydrz said:
Hi All，
I do believe here is the god place who will settle my problem~~ really need help.
my hdx7 is good and no any damages physically, but afte I tried many times for flashing CM13 and different root tools, finally the last time when I flash CM11 rom, the Startrap showing Sucessful, but when I click reboot device, my hdx7 there is no longer boot again, even there is a system already done.
now my hdx is bricked and also stuck by white Kindle Fire logo, I can use the combination key（vol+ and power） boot up Fire System Recovery, but only reboot and factory setting can be selected.
As described above, here is the key about my HDX7, if I want to apply any operations for my devices, this HDX7 cannot connect to computer no matter what kind of computer or different cable, all ADB, root tool, device manager.........there is no HDX7~~
tips: before last failed work I had 4 times flash CM11 system successed but the 4th time computer also cannot find device.
So god please help me~~ Thanks a lot
Click to expand...
Click to collapse
How were you trying to flash CM13? If you device does not have an unlocked bootloader (a CM13 prerequisite) there is no recovery. Given you are getting the factory recovery menu vs TWRP it sounds like Safestrap was installed.
Related
Hello, I am new to the forums and new to rooting, flashing and installing OS' and ROMs on phones.
So, I followed a tutorial from mid 2014 on PCAdvisor (I can unfortunately not share links as I am new to the forums).
I am stuck on step 7 where I have to use
Code:
adb reboot bootloader
. The phone turns of as expected, but when it turns on again, it gets stuck on the booting screen, only showing the Huawei logo.
The I did do a factory reset, and enabled USB debugging. After the first try failed, I went to the bootloader (Volume Up + Power Button) and did a factory reset from there, and tried
Code:
adb reboot bootloader
again, but without luck and still stuck in the boot screen.
I do have an average knowledge to the Ubuntu terminal on computers, and Ubuntu is what I use (and misuse) every day, so such things shouldn't be a problem.
I know the specifications of this phone aren't the recommended ones for use of Ubuntu Touch, but I still wanted to give it a try. If it bricks, I'll have an excuse to buy the Bq Aquaris E4.5 Ubuntu Edition (The cases looks so neat!).
So, with all this, has anyone managed to get past this step? Has anyone managed to install Ubuntu Touch on this model? If not, has anyone managed to install a custom ROM or something similar on this model?
Thanks in advance.
-Inuit Viking.
THANKS
Hello
I got my HDX rolled back today, rooted it using Towelroot, all worked fine
Installed FLASHR and there was an image I had for TWRP, I tried mounting it as recovery but failed, then there was a Kernel option which I did install it with (The same TWRP Image), when the device rebooted it was stuck in Grey Kindle Fire screen,
I read around for methods and found some, the problem is that my device is not seen by ADB and when connected to USB there is no response.
Can this device be unbricked? Do I need the fastboot cable?
I also have taken a backup using FLASHR and it stayed on the device, is this useful?
Thanks for your time
TWRP is not compatible with 3.2.8. Try powering up by holding the on/off and volume-up buttons together. It's possible Amazon's (crippled) recovery is still intact. From there you may be able to reset your device. If successful read through the forums to determine what is possible. Options with 3.2.8 are limited.
Davey126 said:
TWRP is not compatible with 3.2.8. Try powering up by holding the on/off and volume-up buttons together. It's possible Amazon's (crippled) recovery is still intact. From there you may be able to reset your device. If successful read through the forums to determine what is possible. Options with 3.2.8 are limited.
Click to expand...
Click to collapse
Thanks for your reply, I did try power + volume up still got the grey Kindle Fire logo, I did read a lot in this forum but didn't succeed in finding a good solution
I got the factory Cable
The device was recognised as USB, a black screen was showing.
I tried ADB it said device not found
also fastboot -i 0x1949 etc keeps waiting for a device
any hint? is the device dead?
mrewen said:
Hello
I got my HDX rolled back today, rooted it using Towelroot, all worked fine
Installed FLASHR and there was an image I had for TWRP, I tried mounting it as recovery but failed, then there was a Kernel option which I did install it with (The same TWRP Image), when the device rebooted it was stuck in Grey Kindle Fire screen,
I read around for methods and found some, the problem is that my device is not seen by ADB and when connected to USB there is no response.
Can this device be unbricked? Do I need the fastboot cable?
Click to expand...
Click to collapse
No, this device is bricked for good assuming that your device was on FW xx.3.2.8:
- you writed incompatible twrp image on recovery and also on boot partition, the second flash was deadly
The only option for custom rom for FW xx.3.2.8 is to use safestrap and nexus for safestrap 1.0.1.
Hello fellows!
I'm afraid, I bricked my kindle.
I wanted to check out the permissions for /app using ES-File Explorer. My screen went instantly black and stuck. I didn't change anything, I just clicked on "details". I killed the device (holding down power button) and afterwards it doesn't boot. The kindle logo stays gray and it reboots 1 time. This reboot ends in the Fire System Recovery, where I can reboot the device or do a factory reset.
Factory reset didn't help.
I have one problem fixing the device:
- The device is only recognized as MTP-Device while it tries to boot the first time. And this is not very long. It isn't named Kindle, but Android in "Devices and Printers". Unfortunately I can't uninstall or "update" the driver, while the kindle tries to boot.
---> ADB tells me: "error: device '(null)' not found" .
Do you have any idea how to save my kindle?
What I wanted to do before killing the device:
- Get the kindle to show Wallpapers (Totally worth to brick the device! -.-)
EDIT: I tried a second Factory Reset. Now it is fully stuck at the grey boot logo. But my system detects the kindle now correctly.
Next problem: adb shell command end in: "- exec '/system/bin/sh' failed: Permission denied (13) -"
EDIT EDIT: Getting the kindle into real bootloop is not always possible. It happened once and now I'm stuck in the System Recovery again and can't connect to the device :/
You might have to reroot the tablet. I think you can do it with ADB, or HDX toolkit might work. Or maybe you don't have to root at all, I recommend to reinstall ADB.
GodsMistake said:
Hello fellows!
I'm afraid, I bricked my kindle.
I wanted to check out the permissions for /app using ES-File Explorer. My screen went instantly black and stuck. I didn't change anything, I just clicked on "details". I killed the device (holding down power button) and afterwards it doesn't boot. The kindle logo stays gray and it reboots 1 time. This reboot ends in the Fire System Recovery, where I can reboot the device or do a factory reset.
Factory reset didn't help.
I have one problem fixing the device:
- The device is only recognized as MTP-Device while it tries to boot the first time. And this is not very long. It isn't named Kindle, but Android in "Devices and Printers". Unfortunately I can't uninstall or "update" the driver, while the kindle tries to boot.
---> ADB tells me: "error: device '(null)' not found" .
Do you have any idea how to save my kindle?
What I wanted to do before killing the device:
- Get the kindle to show Wallpapers (Totally worth to brick the device! -.-)
EDIT: I tried a second Factory Reset. Now it is fully stuck at the grey boot logo. But my system detects the kindle now correctly.
Next problem: adb shell command end in: "- exec '/system/bin/sh' failed: Permission denied (13) -"
EDIT EDIT: Getting the kindle into real bootloop is not always possible. It happened once and now I'm stuck in the System Recovery again and can't connect to the device :/
Click to expand...
Click to collapse
You didn't indicate if your device was rooted (assume yes), Safestrap installed, FireOS version, etc. But in the end it really doesn't matter. With a locked bootloader there is nothing you can do to recover from this type of failure. Even if the device is detected you will not have adb access. Nor will fastboot commands work (most are disabled). Native factory reset only clears the data partition; it does NOT fix errors in the system partition. If still under warranty contact Amazon about a replacement.
Davey126 said:
[/HIDE]
You didn't indicate if your device was rooted (assume yes), Safestrap installed, FireOS version, etc. But in the end it really doesn't matter. With a locked bootloader there is nothing you can do to recover from this type of failure. Even if the device is detected you will not have adb access. Nor will fastboot commands work (most are disabled). Native factory reset only clears the data partition; it does NOT fix errors in the system partition. If still under warranty contact Amazon about a replacement.
Click to expand...
Click to collapse
It was/is rooted.
So even a Fastboot cable won't work?
GodsMistake said:
It was/is rooted.
So even a Fastboot cable won't work?
Click to expand...
Click to collapse
Fastboot cables are useless on a HDX as 1) device interface does not support alternative pinout; and 2) fastboot environment is crippled.
Davey126 said:
Fastboot cables are useless on a HDX as 1) device interface does not support alternative pinout; and 2) fastboot environment is crippled.
Click to expand...
Click to collapse
Oh man! **** Amazons Bootloader!
I called them and they told me, that there are no Tablets to replace mine. They'd give me a kindle 8.9 for 303€ and that's all.
Thank you for answering. I'm going to throw my kindle away
GodsMistake said:
Oh man! **** Amazons Bootloader!
I called them and they told me, that there are no Tablets to replace mine. They'd give me a kindle 8.9 for 303€ and that's all.
Thank you for answering. I'm going to throw my kindle away
Click to expand...
Click to collapse
Well, I wouldn't toss it just yet. Stick it on a shelf and move on. Possible (albeit unlikely) a future unbrick method or bootloader exploit will become available.
Davey126 said:
Well, I wouldn't toss it just yet. Stick it on a shelf and move on. Possible (albeit unlikely) a future unbrick method or bootloader exploit will become available.
Click to expand...
Click to collapse
I hope so. Someone said they found how to get direct eMMC access.
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
dgindra said:
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A section in order to get expertise help.
-Vatsal
Have you ever tried to connect your tablet to another computer?
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
dgindra said:
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
Click to expand...
Click to collapse
I got the same message yesterday after I returned to stock kernel from a custom one. What I did to get rid of that warning message was to flash all img file(boot, cache, recovery, system, vendor) in MMB29K factory image. (Bootloader is optional) [After that I also performed a factory reset but this step might be unnecessary, do it if the message still exist after flashing stock images] If you don't like that warning you can try these procedures.
My HDX 7 64GB is stuck in a boot loop after 4.5.5.3 update (I did not believe amazon would offer another update so i did not block OTA updates). It was fully Stock except for King root.
Now after the first boot loop it boots always the Fire System Recovery.
Is there any possibility to fix this?
MxUltra said:
My HDX 7 64GB is stuck in a boot loop after 4.5.5.3 update (I did not believe amazon would offer another update so i did not block OTA updates). It was fully Stock except for King root.
Now after the first boot loop it boots always the Fire System Recovery.
Is there any possibility to fix this?
Click to expand...
Click to collapse
Not likely short of placing the device in 'bulk' mode and taking a series of rather technical steps to erase and then rebuild your device. Entering bulk mode may be tricky if it is unstable during boot.
How would I place my HDX 7 into 'bulk' mode?
MxUltra said:
How would I place my HDX 7 into 'bulk' mode?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Ok. I tried to get my HDX 7 into bulk mode, by using a fastboot cable. But it only enters 9008 QDL mode, how do I get from there to the buk mode?
As I tired different things. My HDX 7 is now stuck with the grey kindle fire screen, but I can see the device in adb. The problem is that I can not execute any command, because it is shown as unauthorized. Is there a way to still boot fastboot?
MxUltra said:
Ok. I tried to get my HDX 7 into bulk mode, by using a fastboot cable. But it only enters 9008 QDL mode, how do I get from there to the buk mode?
Click to expand...
Click to collapse
MxUltra said:
As I tired different things. My HDX 7 is now stuck with the grey kindle fire screen, but I can see the device in adb. The problem is that I can not execute any command, because it is shown as unauthorized. Is there a way to still boot fastboot?
Click to expand...
Click to collapse
A fastboot (aka 'factory') cable is ineffective on this device. Being stuck at the bootloader logo with no connectivity is generally fatal. Details matter; how did the device and up in this state?
@draxie - thoughts?
I wanted to unlock the bootloader and rooted it via Kingroot, but had no time that day to get further. Some days later I discovered the HDX 7 was booted to the stock recovery.
I tried to reboot it, but it always tries to boot the rom and start over and boots the stock recovery.
Then I called amazon, and they told me that my HDX tried to update to 4.5.5.3 and that they can not help me.
Then I tried the factory reset, but it did not help either.
Through experimentation I noticed that if the tablet booted while connected to my linux notebook, it would sometimes stop at the grey kindle fire logo and offer a adb connection, that I sadly could not use because i don't have the necessary ADB_VENDOR_KEYS.
MxUltra said:
I wanted to unlock the bootloader and rooted it via Kingroot, but had no time that day to get further. Some days later I discovered the HDX 7 was booted to the stock recovery.
I tried to reboot it, but it always tries to boot the rom and start over and boots the stock recovery.
Then I called amazon, and they told me that my HDX tried to update to 4.5.5.3 and that they can not help me.
Then I tried the factory reset, but it did not help either.
Through experimentation I noticed that if the tablet booted while connected to my linux notebook, it would sometimes stop at the grey kindle fire logo and offer a adb connection, that I sadly could not use because i don't have the necessary ADB_VENDOR_KEYS.
Click to expand...
Click to collapse
I am not aware of any method to reliably force a device into 'bulk' mode via button pushes, etc. The member referenced in a previous post has the most experience in this area; see if he responds.
FWIW - accepting a FireOS 4.x OTA update on a rooted HDX device is almost always fatal.
Hopeless...
Davey126 said:
A fastboot (aka 'factory') cable is ineffective on this device. Being stuck at the bootloader logo with no connectivity is generally fatal. Details matter; how did the device and up in this state?
@draxie - thoughts?
Click to expand...
Click to collapse
Condolences, perhaps...
If the bootloader is unlocked, Power+VolDn won't enter fastboot
(although that doesn't hurt trying), and I don't know of any exploits
that would get adb executing commands on an unauthorized device.
(Of course, trying "adb reboot bootloader" won't do any harm, either.)
If adb used to work before, there _could_ be an absolutely minuscule
chance that whatever host was used still has adb keys in the .android
folder of the relevant user account's home directory, but given that factory
reset was performed, the corresponding public key(s) on the device are
probably gone... Still, if there are keys in .android (and, especially, if there
are different versions on different hosts and/or under different user accounts),
then testing them all may be worth a try. Just in case...
The steps involved are
Stop the current instance
Code:
adb kill-server
Copy the keys to try to .android
(on the test host in the test user's home directory)
See if "adb" manages to connect:
Code:
adb shell
(This needs to be run as the "test" user.)
And, the above steps should be repeated for each set of keys....
I would NOT hold my breath, but one might get lucky.