Related
Hello,
I don t have recovery anymore,
and my new room crash on startup...
I m stock, what should I do please.
gatinho75 said:
Hello,
I don t have recovery anymore,
and my new room crash on startup...
I m stock, what should I do please.
Click to expand...
Click to collapse
More info needed.
Which ROM, what did you do?
Sent from my Nexus 7 using XDA Premium HD app
Hello, It is impossible to brike a device, so worry no more.
And regarding your Room crashing, I'm not sure what that means but please go to the relevant home improvement forums to discuss it.
chrisjcks said:
More info needed.
Which ROM, what did you do?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Its was a rooted phone on ICS, I think it was a stock rom, I was unable to change the rom or make OTA update (installation aborted)
then I try to reinstall CWN, but then when I lance back I have a message like : the bluid is for developement process only
When I try to reinstall I have installation failed
on One X ON Click I try to change ROM with RUU - advence table, same issue
gatinho75 said:
Its was a rooted phone on ICS, I think it was a stock rom, I was unable to change the rom or make OTA update (installation aborted)
then I try to reinstall CWN, but then when I lance back I have a message like : the bluid is for developement process only
When I try to reinstall I have installation failed
on One X ON Click I try to change ROM with RUU - advence table, same issue
Click to expand...
Click to collapse
Bootloader locked, relocked or unlocked? (Hold power and volume down till your bootloader screen shows)
Also, I'm right in saying you have the tegra3 quad core international HOX, right?
Sent from my Nexus 7 using XDA Premium HD app
gatinho75 said:
Its was a rooted phone on ICS, I think it was a stock rom, I was unable to change the rom or make OTA update (installation aborted)
then I try to reinstall CWN, but then when I lance back I have a message like : the bluid is for developement process only
When I try to reinstall I have installation failed
on One X ON Click I try to change ROM with RUU - advence table, same issue
Click to expand...
Click to collapse
You must have stock recovery for OTA updates. You also probably need to be unrooted.
Sent from my Inspire 4G using Tapatalk 2
chrisjcks said:
Bootloader locked, relocked or unlocked? (Hold power and volume down till your bootloader screen shows)
Also, I'm right in saying you have the tegra3 quad core international HOX, right?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
The bootloader was unlocked butt I relocked using fastboot oem lock .
yes I have a international HOX
gatinho75 said:
The bootloader was unlocked butt I relocked using fastboot oem lock .
yes I have a international HOX
Click to expand...
Click to collapse
Either install a RUU
Or
Unlock the bootloader, and flash the correct boot.img for the Rom you tried to install
Sent from my HTC One X using XDA Premium HD app
chrisjcks said:
Either install a RUU
Or
Unlock the bootloader, and flash the correct boot.img for the Rom you tried to install
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
I trying with a RUU now but the battery is to low for the moment
i try to flash to manytime with onex click but evrytime failed
[29-08-2012 08:02:30] Booting Into RUU
[29-08-2012 08:02:53] Flashing Zip
[29-08-2012 08:04:22] sending 'zip' (570044 KB)...
OKAY [ 76.367s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 76.569s
[29-08-2012 08:04:22] Clearing Cache
[29-08-2012 08:04:30] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.001s
Process Took 2 Minutes And 24 Seconds
[29-08-2012 08:05:00] Booting Into RUU
[29-08-2012 08:05:23] Flashing Zip
[29-08-2012 08:12:07] sending 'zip' (563907 KB)...
OKAY [ 75.738s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 75.949s
[29-08-2012 08:12:07] Clearing Cache
[29-08-2012 08:12:15] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.000s
Process Took 7 Minutes And 40 Seconds
gatinho75 said:
I trying with a RUU now but the battery is to low for the moment
i try to flash to manytime with onex click but evrytime failed
[29-08-2012 08:02:30] Booting Into RUU
[29-08-2012 08:02:53] Flashing Zip
[29-08-2012 08:04:22] sending 'zip' (570044 KB)...
OKAY [ 76.367s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 76.569s
[29-08-2012 08:04:22] Clearing Cache
[29-08-2012 08:04:30] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.001s
Process Took 2 Minutes And 24 Seconds
[29-08-2012 08:05:00] Booting Into RUU
[29-08-2012 08:05:23] Flashing Zip
[29-08-2012 08:12:07] sending 'zip' (563907 KB)...
OKAY [ 75.738s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 75.949s
[29-08-2012 08:12:07] Clearing Cache
[29-08-2012 08:12:15] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.000s
Process Took 7 Minutes And 40 Seconds
Click to expand...
Click to collapse
Charge the phone then.
Unplug cable from PC.
Enter bootloader on phone
Select power down
Plug phone into mains (not pc)
Sent from my HTC One X using XDA Premium HD app
chrisjcks said:
Charge the phone then.
Unplug cable from PC.
Enter bootloader on phone
Select power down
Plug phone into mains (not pc)
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
actually I can't when I select power off and put on charge then the phone boot again,
when I put on charge and I try to select power off is not working, its still under 30, I ll will cheek tonight
Thank for your help
gatinho75 said:
actually I can't when I select power off and put on charge then the phone boot again,
when I put on charge and I try to select power off is not working, its still under 30, I ll will cheek tonight
Thank for your help
Click to expand...
Click to collapse
I try to recharge the phone all day, no I can't power on anymore.
and when I put on charge nothing happen even the red light..
This thread might be your only solution, I made it pretty simple for that guy to understand.
It requires doing a fastboot charging using a script.
http://forum.xda-developers.com/showthread.php?t=1840156
from my HTC One X using XDA Premium HD app
chrisjcks said:
This thread might be your only solution, I made it pretty simple for that guy to understand.
It requires doing a fastboot charging using a script.
http://forum.xda-developers.com/showthread.php?t=1840156
from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Can I assume that this is working for you?
Let it charge, (Don't be impatient) then run the RUU whilst in fastboot usb. (which you should already be in for the fastboot charging script)
Sent from my HTC One X using XDA Premium HD app
Hi guys I got 3HT7G model and I am trying to root it so I can install CM. I am having problem with getting device in to fastboot mode. I have several HTC phone and new Nexus 7 and my fastboot works perfectly, SDK is installed and all tools under C:\sdk\platform-tools
Now this is my first Kindle but from what I understand from before I had to always get in to bootloader/fastboot mode manually and only then ADB start to work. In here I see if "waiting for device" is active unit will automatically will get in to fastboot, well it does not for me. Any adias on wtf is going on here this is driving me mad. I have this Kindle drivers installed and adb is checked on in security. I am starting to think my 8.4.6 version is somehow diffirent from other. Anyone please help.
Thank you, once again other devices like Nexus 7 works and getvar command gives me needed answer ......
More details on what you have done would be nice, but basically you turn your kindle off, leave it u plugged, and on the PC run "fastboot -i 0x1949 getvar product", once it says waiting for device you plug your kindle in and it should go into fastboot. If you hear windows make a noise like something connected and disconnected very fast but it doesn't enter fastboot then you need to try to install the driver in my signature for the device as it appears on windows so you can successfully run the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
More details on what you have done would be nice, but basically you turn your kindle off, leave it u plugged, and on the PC run "fastboot -i 0x1949 getvar product", once it says waiting for device you plug your kindle in and it should go into fastboot. If you hear windows make a noise like something connected and disconnected very fast but it doesn't enter fastboot then you need to try to install the driver in my signature for the device as it appears on windows so you can successfully run the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah sorry should of known.
1. I tried adb devices
List of devices attached
B0C9100424551JHB device
2. I tried bin4ry tool v31 and instead of usual download/sending I got an path error ....
I was about to copy from prompt ...and it looks like for some reason this time it worked, I do see superuser app now but I did got an error there in the middle , don't know if it matters. I'll report if anything is messed up later on with ROM installation. Anyway to check ROOT status from stock system ? So I know this app is not just pretty face ?
managed to get everything installed here are last few output code:
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
bootloader kfhd8-u-boot-prod-8.1.4.bin
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.019s]
writing 'bootloader'...
OKAY [ 0.035s]
finished. total time: 0.055s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
boot kfhd8-freedom-boot-8.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.445s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.009s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
recovery kfhd8-twrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.445s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.014s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>[/CODE]
After reboot for about 30 mins now I see kindlefire logo (fire is blue in logo) It does not reboot or anything it just sits there. Oh man I hope I haven't screw something up. I tried to boot in to recovery, I could. I restarted again, and again I am on blue kindlefire logo. What's going on ? Anything I should try ? I don't have any roms inside device memory yet. In device manager I see Kindle with yellow mork on it (odd)
You have to put the ROM on the sdcard so you can flash it when it does this, use my tutorial to get a ROM on it, also try updating the drivers again for the device with an exclamation using the ones in my signature. http://forum.xda-developers.com/showthread.php?t=2459498
Technically you can also boot the device into stock rooted os, but you need to flash an older version from before they started making sure the boot loader was the same version as the os, otherwise when they don't match the end result is well, what you have before you right now.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I always do this to myself, ALWAYS. I panic and think this is the problem I and only I could possibly have and about 3 posts later I found like 10 more people with exact same problem that think this is first in the world just like me, anyhow I did sideload feature and loaded cm .zip and installed sideload.zip from install. I am looking at CM logo booting, so far so good.
P.S.
I was looking at that logo for sometime now, I had to do wipe data and restart once again. All good now.
Thank you !
Q&A for Kindle Fire 2 7" Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kindle Fire 2 7" Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Gen2 Kindle stock restore - stuck in a boot loop - following overlode's doc
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Myth421 said:
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Click to expand...
Click to collapse
EDIT: (a day or so later) Hey.. Nevermind. I was able to finally figure things out and downloaded KindleFireFirstAid and was able to wipe it out back to stock using my factory cable. The boot loop was limiting my options. Thanks Anyway.
Fastboot
What would be stopping Fastboot from recognizing my device? I have a fastboot cable for my kindle fire 2, I plug it into my computer then into the kf2, the kf2 boots up into fastboot mode my computer see the kindle and it has the proper drivers installed, but fastboot can't see it for some reason.
I had this problem before when I installed CM10 onto my kf2 but that was a year ago and for the life of me I don't remember how I got fastboot to see my kf2.
All i want to do is downgrade my kf2 back to stock and sell it on ebay. PLEASE HELP! I'm dying here
Any other options?
Overlode-My wife;s KF2 was stuck in boot loop so I tried your stock restore method with a factory cable. Everything seemed to work fine. The drivers were installed, fastboot commands worked on the device, etc. When I did the last reboot step, the device never turned back on. Now the device will not power up with the factory cable or USB cable. Is there anything I can do to fix this KF2 or is it permanently screwed? Thanks.
Kindle Fire 2 - Bricked
Today I tried the procedure in post http://forum.xda-developers.com/kindle-fire-hd/fire-2-development/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
KF2 - hardbricked and restored.......almost!!!
Hi,
I have a KF2, which I had previously rooted and installed CM10 custom ROM. Had no problems with it, but decided to try a few more custom ROMS. Forgot about NOT using the KFU program as it was for KF1 devices, and for some stupid reason went ahead and flashed the wrong bootloader.
Result is fairly predictable - HARD BRICKED KF2!!
Thought that was it - searched the forums and everyone was saying the same - no way back from that! Then I came across Kurohyou's post and brilliant guide about hacking a card reader and attaching direct to motherboard. Followed his guide and voila - managed to boot up into recovery (TWRP). However after pushing the ROM files etc to try and install CM ROM again just kept getting "error flashing ROM" . I left the thing after trying various methods and different PC's etc to push the files across and gave up. When I went back to it this morning I couldn't get it to boot into recovery - which I thought was a bit strange. However FASTBOOT mode is ok - I have made a fastboot cable myself which works fine. Kindle was booting up with orange logo, quick flash, orange kindle logo again and repeat. It would not boot into recovery even though I had flashed the correct files via fastboot.
Again almost giving up when I came across Overlode's instructions. Followed them to the letter, and what I am left with now is the standard Kindle Fire logo (orange) which blinks after about 5 seconds and just stays there - left it for about an hour just in case....
I can post screenshots of me flashing the files as per Overlode's instructions if it helps. I get a few errors when using the wipe command, response is "erase successful, but not automatically formatting. File system type not supported" everything else is ok.
I still have the hacked card reader attached which through Ubuntu can see the EMMC directly so don't know if might be worth copying the files directly instead of flashing via fastboot?
Any suggestions gratefully received...... I'm at my wits end with this thing - I know I should have left well alone!!! but I feel like I have run a marathon with this thing only to have fallen flat on my face 5 metres from the finish line!!
Thanks in advance for any help.
lmayala said:
Today I tried the procedure in post http://forum.xda-developers.com/kin...opment/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
Click to expand...
Click to collapse
Hi - see my last post - I too have a hard bricked kindle. if you're handy with a soldering iron you can try it - I can confirm it does work.
details here -
http://forum.xda-developers.com/showthread.php?t=2415870
I managed to get my kindle from nothing (not even charging light) to back up and running with TWRP installed. I couldn't get a custom ROM installed, kept getting errors - but I think my board has other issues. While I was putting it back together I managed to stick my screwdriver through the battery (don't ask!!!) Since then I think I have caused other damage and it was never the same again I think I may have damaged the memory or the EMMC..... on the hunt for new motherboard at present!
Good luck!
registered an account just to thank you. You saved my KF2.
Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!
sotrite5 said:
Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!
Click to expand...
Click to collapse
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?
sotrite5 said:
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?
Click to expand...
Click to collapse
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot bootloader and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot fastboot and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Although I did have ADB enabled on my Kindle, I am no longer able to communicate with it via ADB since using FireFlash11 to install the 2nd-bootloader, TWRP and CM. The Kindle now does not appear when I type adb devices (although it always had before using FireFlash).
Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?
sotrite5 said:
Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?
Click to expand...
Click to collapse
I wouldn't give up just yet. Try repeating the same directions I gave you, expect from Linux (Ubuntu) this time as opposed to Windows.
Sent from my Amazon Jem using XDA Labs
*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s
sotrite5 said:
*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s
Click to expand...
Click to collapse
Many years later and I find this post still helpful and it saved my KFHD8.9. I had this same issue with a KFHD 8.9 that I had repurposed to a photo frame. I flashed a new ROM to it, thinking it my photo frame app might run better on a different ROM. Only I hadn't flashed a ROM for a few years and got sloppy with the flashing sequence and wound up stuck at the Kindle Fire orange logo. I spent hours reading XDA posts and trying things to get fastboot and adb to get into the device during the roughly 2 or 3 second bootup window before it gets stuck. The problem is that the way windows 10 and windows 7 handle the USB drivers makes it almost impossible. I made an Ubuntu USB stick to boot from and loaded up fastboot, adb and the android usb drivers and was able to get my KFHD into fastboot mode instantly. Once there, it was simply a matter of running the fastboot commands above and I then I was in recovery and able to restore from a backup.
Many thanks!!!
---Delete----
I'm really hoping that someone here can help me. I'm using a Mac. I'm using a fastboot cable. I have a Kindle Fire HD 8.9" (2nd Gen) (Model #: 3HT7G). One day I left it charging. I came home and found the screen was completely red. I restarted it by holding down the power button for 40 seconds. That brought it back to normal. I used it for a couple of weeks and now I can't get it out of the red screen.
I called Amazon and they won’t help me because it’s out of warranty. They want to sell me a new one at a discounted price. I can’t get a new one because it can’t be shipped outside of the US. I’m in Vietnam.
I want to unbrick it by installing CyanogenMod 12.1. I am following the steps on the CyanogenMod wiki for “jem”.
I'm done with -
Step 1: Test your...
Step 2: Download the files...
When I get to Step 3 (Use fastboot to apply...), the first step is ok:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin (see below for my Terminal window)
The screen on my Kindle changed. It says in yellow text "fastboot mode" with a blue arrow pointing down. In the upper left in white text it says "writing bootloader...done".
The next step (step 2) is NOT ok:
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
It just says:
sending 'recovery' (8173 KB)...
I waited for about 40 minutes and then it came back with:
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
I'm a newbie and I have no idea what I'm doing. I'm just following the steps on the CyanogenMod wiki and praying that it will unbrick my Kindle Fire.
Here's my Terminal window:
Last login: Sat Sep 17 06:12:59 on console
Seans-MacBook-Pro:~ sean$ cd Desktop/android
Seans-MacBook-Pro:android sean$ ls
adb kfhd8-freedom-boot-8.4.6.img
cm-12 kfhd8-twrp-2.8.7.0-recovery.img
fastboot kfhd8-u-boot-prod-8.1.4.bin
Seans-MacBook-Pro:android sean$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
-bash: fastboot: command not found
Seans-MacBook-Pro:android sean$ ./fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.975s]
writing 'bootloader'...
OKAY [ 0.156s]
finished. total time: 1.131s
Seans-MacBook-Pro:android sean$ ./fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
sending 'recovery' (8173 KB)...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
You don't want to use the Jem instructions. You have an hdx. Try http://forum.xda-developers.com/kindle-fire-hdx and good luck!
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
You don't want to use the Jem instructions. You have an hdx. Try http://forum.xda-developers.com/kindle-fire-hdx and good luck!
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm pretty sure it's a Kindle Fire HD. Not an HDX. On the back it just says "kindle". My KF doesn't have the shape of an HDX. It looks like the KF on love my fire dot com; "2012 Kindle Fire HD 8.9" (2nd Generation)". I posted already in the HDX forum (by mistake) before I posted here. Davey126 said I have a HD (not an HDX).
onwithsean said:
I'm pretty sure it's a Kindle Fire HD. Not an HDX. On the back it just says "kindle". My KF doesn't have the shape of an HDX. It looks like the KF on love my fire dot com; "2012 Kindle Fire HD 8.9" (2nd Generation)". I posted already in the HDX forum (by mistake) before I posted here. Davey126 said I have a HD (not an HDX).
Click to expand...
Click to collapse
If you have a Jem then you don't need a fastboot cable. I would get a different cable and use http://forum.xda-developers.com/showthread.php?t=2128175 as a guide to install custom firmware, not the wiki you are using.
Sent from my SGH-T999 using XDA-Developers mobile app
Shack70 said:
If you have a Jem then you don't need a fastboot cable. I would get a different cable and use http://forum.xda-developers.com/showthread.php?t=2128175 as a guide to install custom firmware, not the wiki you are using.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
When I had my KF connected to my Mac with the fastboot cable I typed in this:
./fastboot -i 0x1949 getvar product
It returned with this:
product: Jem-PVT-Prod-04
That means I have a Jem, right? Is a Jem a Kindle Fire HD?
onwithsean said:
When I had my KF connected to my Mac with the fastboot cable I typed in this:
./fastboot -i 0x1949 getvar product
It returned with this:
product: Jem-PVT-Prod-04
That means I have a Jem, right? Is a Jem a Kindle Fire HD?
Click to expand...
Click to collapse
Yes! OK, try doing what's in this video: https://m.youtube.com/watch?v=eSpTxlpumMY
I have a Mac.
onwithsean said:
I have a Mac.
Click to expand...
Click to collapse
Sorry no Mac experience. Can't you emulate or dual boot windows?
Shack70 said:
Sorry no Mac experience. Can't you emulate or dual boot windows?
Click to expand...
Click to collapse
I'll try it with a friend who has a Windows computer. I'll post back with the results.
onwithsean said:
I'll try it with a friend who has a Windows computer. I'll post back with the results.
Click to expand...
Click to collapse
Good luck