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.
Related
I did my search before posting this, so I'm sorry if this has been already resolved but I couldn't find solution to this.
I've a Kindle HDX 8.9 64GB wifi model, it was rooted installed SU, installed safestrap on it and had google play store and gapps working on it., I was too busy so left it device as it is and never used it. Recently got free and noticed it was downloading update. I remembered reading that update breaks Root so switched off device as I panicked and then turned it on in airplane mode. I came here and saw what could be done to prevent update. Tried firewall with IP tables that didn't help as download of update resumed after I turned airplane mode off. Then I did more search did below changes
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
along with above changes I made changes suggested in this thread http://forum.xda-developers.com/showthread.php?t=2678600
"edit build.prop
ro.build.version.number=999999999"
After doing all these changes, update stopped and started giving me error of unable to check update. I was all happy. Started using device normally and everything was fine till I rebooted device and that's when it messed up.
Tablet starts normally with Kindle fire logo and then comes Safestrap menu with options to continue or go into recovery. I clicked continue as usual and it just sits there with grey screen. Doesn't do anything at all from there on. I rebooted again and was able to go into recovery mode but I never took backup (I know dumb of me) so there was nothing I could do there. I tried to turn on adb sideload in recovery but it kept attempting to turn on but never did. When kindle is in grey screen its been detected on Laptop. In device manager device is detected 2 places as shown in picture attached, One under other devices with shows android device with yellow triangle on it and also under portable devices as MTP usb device. Though I'm unable to see it detected in file system. I've kindle drivers already installed.
I'm not sure renaming those files messed my system up or changing build prop messed it up. But I'm unable to find solution to fix this mess.
I would really appreciate help as I'm in pretty tight position here. Device can't be returned to amazon as I'm in India now. So only option I got is to repair it somehow or its $500 down the drain
UPDATE : ADB detects Kindle as emulator-5554 device. May be its a good sign? :\ again any help would be appreciated.
arvinchugh said:
I did my search before posting this, so I'm sorry if this has been already resolved but I couldn't find solution to this.
I've a Kindle HDX 8.9 64GB wifi model, it was rooted installed SU, installed safestrap on it and had google play store and gapps working on it., I was too busy so left it device as it is and never used it. Recently got free and noticed it was downloading update. I remembered reading that update breaks Root so switched off device as I panicked and then turned it on in airplane mode. I came here and saw what could be done to prevent update. Tried firewall with IP tables that didn't help as download of update resumed after I turned airplane mode off. Then I did more search did below changes
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
along with above changes I made changes suggested in this thread http://forum.xda-developers.com/showthread.php?t=2678600
"edit build.prop
ro.build.version.number=999999999"
After doing all these changes, update stopped and started giving me error of unable to check update. I was all happy. Started using device normally and everything was fine till I rebooted device and that's when it messed up.
Tablet starts normally with Kindle fire logo and then comes Safestrap menu with options to continue or go into recovery. I clicked continue as usual and it just sits there with grey screen. Doesn't do anything at all from there on. I rebooted again and was able to go into recovery mode but I never took backup (I know dumb of me) so there was nothing I could do there. I tried to turn on adb sideload in recovery but it kept attempting to turn on but never did. When kindle is in grey screen its been detected on Laptop. In device manager device is detected 2 places as shown in picture attached, One under other devices with shows android device with yellow triangle on it and also under portable devices as MTP usb device. Though I'm unable to see it detected in file system. I've kindle drivers already installed.
I'm not sure renaming those files messed my system up or changing build prop messed it up. But I'm unable to find solution to fix this mess.
I would really appreciate help as I'm in pretty tight position here. Device can't be returned to amazon as I'm in India now. So only option I got is to repair it somehow or its $500 down the drain
UPDATE : ADB detects Kindle as emulator-5554 device. May be its a good sign? :\ again any help would be appreciated.
Click to expand...
Click to collapse
try rebooting the device and go into safestrap recovery and when you hear the driver try to load in windows go to device manager,it should be listed as mtp under portable devices,uninstall that driver do not reboot,,unplug device and then plug it right back in it should try to load the driver as kind fire hdx but fails,when it is done check device manager for the kindle fire with the triangle on it and click update driver,then click browse my computer for driver software,then click let me pick from a list of device drivers on my computer,then scroll down until you see kindle fire click it and then click ADB ANDROID user interface and the click next,if a box pops up saying something about drivers might not be compatible just click yes to install,when its done you will have kindle fire in device manager and in adb it should say what ever you device is and then RECOVERY after in adb then you can push the files needed
which i would use this one
https://mega.co.nz/#!WlQliIgZ!-SxzW77e4m0S5e520uxvwf6EYrbDNb-yL7O5ElnrO5c
from this thread
http://forum.xda-developers.com/showthread.php?t=2665683
when the bin file is done downloading make a copy of it and put it in your
platform-tools folder with adb and change the .bin to .zip,,then push it to your sdcard (adb push update-kindle-14.3.1.0_user_310079820.zip /sdcard)
THIS WILL TAKE A WHILE! so let it do it's thing and when adb says it is done and the file is pushed press on the screen,(which has blacked out by now),, swipe to unlock and press install, you should see the
update-kindle-14.3.1.0_user_310079820.zip file on the sdcard now,,if so great lets move to the next step...
now hit the back button and go to the home screen,,,press wipe and swipe to wipe it (just do the regular wipe and thats it) DO NOT REBOOT YET
hit the back button or home button to go back to the home screen,,,now press install press the update-kindle-14.3.1.0_user_310079820.zip file and swipe it
it will say checking md5 no md5 found skipping modem update, installing and when it says finished successfully reboot system and it will be back to stock needing rooted and the whole works again except safestrap will still be there when it boots back on,,just let it continue or press continue it may take a few minutes to load the color kindle fire screen like any new rom would take to boot the first time,, KEEP WIFI OFF AFTER REBOOT,,,safestrap will stay installed but you will not see the app in the app draw and you dont need it because it is still installed ,so just root it using this http://forum.xda-developers.com/showthread.php?t=2542456
dont worry about the errors just do what it says and then install busy box and supersu then do this http://forum.xda-developers.com/showthread.php?t=2618158 and reboot the device one or twice,,after that download this http://android.mydedibox.fr/thor-gapps-installer-1.zip put it on your sdcard and then reboot to safestrap and press install and press thor-gapps-installer-1.zip and swipe when its done just reboot
then you will need to change the build.prop to keep it from updating
hope this helps you, it is what i had to do when the same thing happened to me so i know it will work!! good luck if you need any help let me know
jjrizzelcincy said:
try rebooting the device and go into safestrap recovery and when you hear the driver try to load in windows go to device manager,it should be listed as mtp under portable devices,uninstall that driver do not reboot,,unplug device and then plug it right back in it should try to load the driver as kind fire hdx but fails,when it is done check device manager for the kindle fire with the triangle on it and click update driver,then click browse my computer for driver software,then click let me pick from a list of device drivers on my computer,then scroll down until you see kindle fire click it and then click ADB ANDROID user interface and the click next,if a box pops up saying something about drivers might not be compatible just click yes to install,when its done you will have kindle fire in device manager and in adb it should say what ever you device is and then RECOVERY after in adb then you can push the files needed
which i would use this one
https://mega.co.nz/#!WlQliIgZ!-SxzW77e4m0S5e520uxvwf6EYrbDNb-yL7O5ElnrO5c
from this thread
http://forum.xda-developers.com/showthread.php?t=2665683
when the bin file is done downloading make a copy of it and put it in your
platform-tools folder with adb and change the .bin to .zip,,then push it to your sdcard (adb push update-kindle-14.3.1.0_user_310079820.zip /sdcard)
THIS WILL TAKE A WHILE! so let it do it's thing and when adb says it is done and the file is pushed press on the screen,(which has blacked out by now),, swipe to unlock and press install, you should see the
update-kindle-14.3.1.0_user_310079820.zip file on the sdcard now,,if so great lets move to the next step...
now hit the back button and go to the home screen,,,press wipe and swipe to wipe it (just do the regular wipe and thats it) DO NOT REBOOT YET
hit the back button or home button to go back to the home screen,,,now press install press the update-kindle-14.3.1.0_user_310079820.zip file and swipe it
in will say checking md5 no md5 found skipping modem update, installing and when it say finished successfully reboot system and it will be back to stock needing rooted and the whole works again except safestrap will still be there when it boots back on,,just let it continue or press continue it may take a few minutes to load the color kindle fire screen like any new rom would take to boot the first time,, KEEP WIFI OFF AFTER REBOOT,,,safestrap will stay installed but you will not see the app in the app draw and you dont need it because it is still installed ,so just root it using this http://forum.xda-developers.com/showthread.php?t=2542456
dont worry about the errors just do what it says and then install busy box and supersu then do this http://forum.xda-developers.com/showthread.php?t=2618158 and reboot the device one or twice,,after that download this http://android.mydedibox.fr/thor-gapps-installer-1.zip put it on your sdcard and the reboot to safestrap and press install and press thor-gapps-installer-1.zip and swipe when its done just reboot
then you will need to change the build.prop to keep from updating
hope this helps you it is what i had to do when the same thing happened to me so i know it will work good luck if you need any help let me know
Click to expand...
Click to collapse
Thanks so much for reply, I've been busy so Haven't had time to try this out. however I've downloaded file just incase it goes offline. I'll reply here again if I've any trouble setting it up. Again thanks for taking time out to reply and posting such a detailed procedure for me to follow. Really appreciate it. :good::good:
arvinchugh said:
Thanks so much for reply, I've been busy so Haven't had time to try this out. however I've downloaded file just incase it goes offline. I'll reply here again if I've any trouble setting it up. Again thanks for taking time out to reply and posting such a detailed procedure for me to follow. Really appreciate it. :good::good:
Click to expand...
Click to collapse
No problem ,,,hope it all works out ,,,let me know how it goes
it does not help, because adb does not work after editing build.prop
amazonhdx said:
it does not help, because adb does not work after editing build.prop
Click to expand...
Click to collapse
what type of problem are you having and what did you do to get that problem
jjrizzelcincy said:
what type of problem are you having and what did you do to get that problem
Click to expand...
Click to collapse
just edit build.prop and save without normal permission. and kindle fire hdx: soft bricked! :victory:
tablet start step: 1. grey logo 2. black screen
adb not working.
after connect factory cable device view on "qhsusb bulk"
Safestrap not installed
amazonhdx said:
just edit build.prop and save without normal permission. and kindle fire hdx: soft bricked! :victory:
tablet start step: 1. grey logo 2. black screen
adb not working.
after connect factory cable device view on "qhsusb bulk"
Safestrap not installed
Click to expand...
Click to collapse
try a factory reset through stock recovery
even though im reading a lot on here not to do that with certain issues but if yours is just build.prop that may help you but read around before wiping though
jjrizzelcincy said:
try a factory reset through stock recovery
even though im reading a lot on here not to do that with certain issues but if yours is just build.prop that may help you but read around before wiping though
Click to expand...
Click to collapse
reset from default recovery not help
amazonhdx said:
reset from default recovery not help
Click to expand...
Click to collapse
Sorry wish I could be more help for you buddy
amazonhdx said:
just edit build.prop and save without normal permission. and kindle fire hdx: soft bricked! :victory:
tablet start step: 1. grey logo 2. black screen
adb not working.
after connect factory cable device view on "qhsusb bulk"
Safestrap not installed
Click to expand...
Click to collapse
i would only use ROOT EXPLORER to edit any files like build.prop
try to reboot oem from there
can you see it in fastboot with the factory cable ???
if so try fasboot reboot oem
then press enter
jjrizzelcincy said:
try rebooting the device and go into safestrap recovery and when you hear the driver try to load in windows go to device manager,it should be listed as mtp under portable devices,uninstall that driver do not reboot,,unplug device and then plug it right back in it should try to load the driver as kind fire hdx but fails,when it is done check device manager for the kindle fire with the triangle on it and click update driver,then click browse my computer for driver software,then click let me pick from a list of device drivers on my computer,then scroll down until you see kindle fire click it and then click ADB ANDROID user interface and the click next,if a box pops up saying something about drivers might not be compatible just click yes to install,when its done you will have kindle fire in device manager and in adb it should say what ever you device is and then RECOVERY after in adb then you can push the files needed
which i would use this one
https://mega.co.nz/#!WlQliIgZ!-SxzW77e4m0S5e520uxvwf6EYrbDNb-yL7O5ElnrO5c
from this thread
http://forum.xda-developers.com/showthread.php?t=2665683
when the bin file is done downloading make a copy of it and put it in your
platform-tools folder with adb and change the .bin to .zip,,then push it to your sdcard (adb push update-kindle-14.3.1.0_user_310079820.zip /sdcard)
THIS WILL TAKE A WHILE! so let it do it's thing and when adb says it is done and the file is pushed press on the screen,(which has blacked out by now),, swipe to unlock and press install, you should see the
update-kindle-14.3.1.0_user_310079820.zip file on the sdcard now,,if so great lets move to the next step...
now hit the back button and go to the home screen,,,press wipe and swipe to wipe it (just do the regular wipe and thats it) DO NOT REBOOT YET
hit the back button or home button to go back to the home screen,,,now press install press the update-kindle-14.3.1.0_user_310079820.zip file and swipe it
it will say checking md5 no md5 found skipping modem update, installing and when it says finished successfully reboot system and it will be back to stock needing rooted and the whole works again except safestrap will still be there when it boots back on,,just let it continue or press continue it may take a few minutes to load the color kindle fire screen like any new rom would take to boot the first time,, KEEP WIFI OFF AFTER REBOOT,,,safestrap will stay installed but you will not see the app in the app draw and you dont need it because it is still installed ,so just root it using this http://forum.xda-developers.com/showthread.php?t=2542456
dont worry about the errors just do what it says and then install busy box and supersu then do this http://forum.xda-developers.com/showthread.php?t=2618158 and reboot the device one or twice,,after that download this http://android.mydedibox.fr/thor-gapps-installer-1.zip put it on your sdcard and then reboot to safestrap and press install and press thor-gapps-installer-1.zip and swipe when its done just reboot
then you will need to change the build.prop to keep it from updating
hope this helps you, it is what i had to do when the same thing happened to me so i know it will work!! good luck if you need any help let me know
Click to expand...
Click to collapse
Can confirm this worked just as stated, thanks again for taking your time out and making and excellent easy to follow guide to unbrick my device. Really really appreciate it.
Thanks again
arvinchugh said:
Can confirm this worked just as stated, thanks again for taking your time out and making and excellent easy to follow guide to unbrick my device. Really really appreciate it.
Thanks again
Click to expand...
Click to collapse
no problem man
sorry wrong device
?
Rallypig31 said:
So after reading and watching videos i attempted to root my Kindle Fire 7 (1st gen) ( I have jail broken iphones no problem, rooted my galaxy s4 no problem) kept having issues getting it rooted so i kept I trying on both my laptop and desktop pc's finally got SuperSU on it thought it was rooted but its not. Apps to check for root says its rooted but Es File manager wont give me root access, one app says busy box IS installed another says it isn't. I attempted root with Bin4ry root method. Kindle itself runs fine and boots up fine.
Also when i open SuperSU it says that the SU Binary needs to be updated I hit Continue and no matter which option i choose (Normal or TWRP/CWM) it says installation failed. I've tried re-rooting/Un-rooting, updating SuperSU, I've tried Kindle Fire First Aid tool. I Have a factory cable now. But KFFT wont put kindle into fastboot, Even if turn the kindle on with the factory cable the kindle will boot in fastboot mode, I try option 3 in KFFT (restore) say no when it asks if I want KFFT to put it into Fastboot mode KFFT will flash a screen, then on the bottom it says it downloaded 3 images and then just says waiting for device and thats it. I've even tried the built in option on the kindle to factory reset just to try but after rebooting SuperSU app is still there.
At this point all im trying to do is get it back to how it was out of the box.
I have the android SDK installed and im completely clueless on ADB, when I open CMD its at C:\users\my name\desktop> and if i try any of the fastboot commands nothing works.
Click to expand...
Click to collapse
This is the kindle fire HDX forum.
oops sorry obviously not paying attention
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.
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset
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.