rooting trouble - Kindle Fire Q&A, Help & Troubleshooting

I've rooted and unrooted kindle fires a couple times before but have had trouble this time around. Like before, I used the Kindle Fire Utility but as it went though the process, I was notified that the md5 check on twrp recovery failed and it asked me to press any key to continue. After I did, the utility shut down with only the firefirefire bootloader installed. Upon rebooting the kindle, which still works fine, I tried to run the utility from the top but it keeps failing when it tries to boot into fastboot to install twrp, always saying waiting for device. I also tried resetting the kindle to get rid of firefirefire and start again but resetting the kindle through stock settings won't get rid of the custom bootloader.
So my main problem appears to be trouble installing twrp. I have adb setup and working and was wondering if anyone could point me in the right direction.

Attach your device run option for twrp if it hangs <waiting for device> hold the power button down while attached till its off then simply power it on at that point it should send twrp.
Edit: make sure you have allowed installation from unknown sources.

Thepooch said:
Attach your device run option for twrp if it hangs <waiting for device> hold the power button down while attached till its off then simply power it on at that point it should send twrp.
Edit: make sure you have allowed installation from unknown sources.
Click to expand...
Click to collapse
I enabled installation from unknown devices but its still "waiting for device" to boot into fastboot. I've also tried rebooting it multiple times and re-installing the drivers as the utility suggests but I'm getting the same problem.

Do your drivers indicate android composite adb interface? Does KFU show your device online boot mode 4000? Lastly did you do as I suggested?

Not sure why, but I tried a different computer and that ended up working. Thanks for the help.

Related

I bricked my KF GOOOOD this time

I have had a Kindle Fire since they day they came out. I immediately disliked the stock Rom so I ran the kindle fire utility and installed Fire Fire Fire and TWRP, rooted it, and installed CM7 Rom which has been working great. Transferred files and programs between my PC and Kindle with no issue for months. Now with all the ICS roms available and working I decided to try and upgrade to one of those and thats when everything went wrong. Its in a bootloop and the triangle appears, fades, lights up again and immediately boots to TWRP. I have flashed the entire kindle using TWRP trying to get everything off of it. Upon plugging it into my PC BRIEFLY when the triangle logo pops up I get a "USB device not recognized" on my PC. I have tried using KFUtility to reinstall drivers, tried uninstalling n reinstalling drivers but the same thing happens. I cannot use TWRP to mount at all, nothing happens. Kindle Fire UTility keeps saying adb offline, CMD adb devices also results in 0 devices found. I have tried putting it on normal boot using both ADB and KFUtility and it says "wait for device" and nothing ever happens. Any idea? Not even sure if I have a rom installed on my kindle anymore but my PC wontread it so I cannot push another image to it. Got a plane trip on Saturday and would love to have this working to kill the bordom lol. Any advise would be greatly appreciated.
It sounds like your bootmode is set to recovery. An easy way to fix this is download FFF1.4 to your computer and use the mount function in recovery to place it on your sdcard.
Flash it in recovery as you would a rom except don't wipe anything. When you reboot, hold the power button like you're trying to enter recovery and you'll be given the option to reset the bootmode.
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
anomiefaunus said:
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
Click to expand...
Click to collapse
Generally, the only thing that would prevent adb/kfu from communicating with the device is the drivers. Make sure they're installed properly. You may have to uninstall them (delete if applicable) and reinstall them.
Follow the instructions in this guide to install and verify your drivers.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
anomiefaunus said:
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
Click to expand...
Click to collapse
Get your device drivers working so you can use adb. Follow the instructions in the post below...
http://forum.xda-developers.com/showpost.php?p=26144447
That is excellent advice and I wish it would work but I cannot pull up ADB once in TeamWin. Keeps saying no devices. As i said my PC detects it and ADB will detect it for .5 seconds on the orange triangle. Once the orange triangle disappears and it either boots to blackness or boots to TeamWin ADB stops recognizing my device. But I will play around with your suggestions once I get off work and let you know what i find out. Thanks again for everyones support.
Frozen screen during rooting
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
peredexter said:
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
Click to expand...
Click to collapse
Don't hijack the threads please. If you have a problem or question, post it in the Q&A section.

KF stuck at Kindle Fire white/blue logo; tried a few ways including Linux

Hi All.
I’ve rooted my Kindle device successfully before (during v6.2 – have the driver installed from this and cable worked successfully )
Now with the 6.3.1, I used the KFU v0.9.6 to do it – option 2 ‘Install Permanent Root with Superuser’
Followed the instructions as per http://forum.xda-developers.com/showthread.php?t=1399889
- On my XP machine, it detected my Kindle initially but it stopped and my Kindle Fire was showing the stock welcome screen but kept on rebooting.
- Then I tried on a Win 7 machine and ran option 2 again – it did something and now my Kindle is stuck on the FFF screen (Kindle Fire logo in blue and white – v1.4a).
- Now when I run ‘ran.bat’, pc it shows ‘waiting for device’
- The FFF screen was blinking initially but now it’s permanently on.
- I can off my Kindle by pressing the on button for about 20 seconds and when I connect my Kindle in the off state to the pc, it turns on and remain on the FFF screen
1. Installing the driver
So I figured the above is due to the driver.
- However, the Kindle is not appearing in the Device Manager with a yellow ! – hence can’t manually install the drivers.
- Tried install_drivers.bat – it says ‘Google, Inc. (WinUSB)…..Install failed (Unsigned)’
​- I ensured that the ‘Driver Signing Options’ is set to ‘Ignore – Install the software and don’t ask for my approval’ and ‘Make this action the system default’.
- So next, I tried to force my XP to install the drivers (Kindle unplugged), by using ‘Add Hardware’ and installing drivers from c:\kfu\drivers –
​- Installed all 3 drivers – Android ADB Interface, Android Bootloader Interface & Android Composite ADB Interface.
​- Received this message at the end – ‘The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)’
​- But when I plugged in my Kindle and run KFU it still says ‘waiting for device’.
I tried the above steps with:-
- 3 XP machines and 1 Win 7, and
- on different USB ports (tried both USB 2.0 and 3.0)
- and tried using 4 different usb cables
- Same results ‘waiting for device’
- One exception though – for the Win 7 machine – when I ‘install_drivers.bat’, it says ‘Google, Inc. (WinUSB) ….Ready to use’ – but still shows ‘waiting for device’, when running KFU.
2. Delete old drivers
Followed this (http://forum.xda-developers.com/showthread.php?t=1459116) to uninstall the drivers (including the Microsoft support page).
- But XP and Win 7 still did not detect the Kindle in ‘Device Manager’
- Tried to force install the 3 drivers again and still ‘waiting for device’
Additionally tried to download the Google Usb driver from Android SDK - same issue - no yellow !
And tried to connect via 'c:\KindleAdb\adb devices' (learned from the previous root exercise) - no devices appears.
3. Kindle Fire Unbrick Utility
Tried this next - http://forum.xda-developers.com/showthread.php?t=1428428
Tried the many options available. When it is executed, its says ‘error’, despite saying Kindle unbricked at the end.
4. Firekit LiveUSB repair kit 1.1
Finally decided to use the Linux method (http://forum.xda-developers.com/showthread.php?t=1430038)
- Created a USB Ubuntu and ran the program but suprisingly still the same problem – stuck at ‘waiting for device’ (see snapshot attached).
So I’m a bit confused right now. From the above it seems to me that the Kindle is not talking to the PC.
- But if in Linux, it doesn’t work (which from what I read doesn’t require a driver?) then it could possibly be my cable.
- But the cable did work when I rooted in 6.2 and it also worked initially when I used KFU. And also, I tried with 4 different cables.
​- Am not sure if the cables are ‘factory cable’ – but it did work initially.
I’m stuck here. Any help/advice would be deeply appreciated. Thank you.
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Thank you kinfauns for your immediately reply.
kinfauns said:
A few things that might help you...
1) If you have FFF 1.4a, you can access its boot menu and have the device boot normally or into recovery. As it boots up, look at the power button LED and watch as it goes from a bright green to a dim green. As soon as it goes dim, press and release the button to bring up the menu on the screen. You can then flip through the menu options by repeatedly pressing and releasing the power button. Leave it alone for a few seconds and it will continue to boot using the selected option.
Click to expand...
Click to collapse
Unfortunately this doesn't happen on my KF. The power button is bright green. And the bootlogo is persistent and remain bright on the display.
I've tried repeatedly pressing and releasing the power button but didn't work.
2) If you don't know whether or not you have a factory cable, you probably don't have one...
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
Just bought a USB factory fastboot mode cable online .
3) For the computer to issue fastboot commands to the device, it must already be connected to the computer before booting into fastboot mode. That is... you cannot boot the KF into fastboot mode and then connect it to the computer. If the computer is <waiting for device>, try turning the KF off by pressing and holding the power button for around 20 seconds to shut it down completely, then turning it back on again. For more information on fastboot....
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I tried this method but nothing changes - when I turn it back on, it goes back to the bootlogo. KFU still says <waiting for device>.
Also tried 'Temporary fastboot mode' - 'fastboot getvar product' - still <waiting for device>.
If the above suggestions don't work for you, make sure you are getting the expected hardware IDs shown in the previous link.
Click to expand...
Click to collapse
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
ivanovicch said:
My KF doesn't show up on 'Device Manager' - no yellow question mark or whatsoever.
When I manually installed 'Android ADB Interface' - it shows an yellow ! and even after I connect the KF it still shows the yellow !.
Current hardware ID (for 'Android ADB Interface' with yellow !): usb\vid_0bb4&pid_0c01
Device status: This device cannot start. (Code 10)
So I guess, I will wait for my factory cable, unless you have any other suggestions? Thank you.
Click to expand...
Click to collapse
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Thepooch said:
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
I pressed power button for more than a minute - tried 2 ways:-
- with the KF on - it switches off and remains switched off.
- with the KF off - it switches on for a bit and then switches off and remains switched off.
I'll just give the factory cable a try when it arrives - will update here again. Hopefully I don't have to open up the case.
Thanks kinfauns and Thepooch.
I have no idea what that ID number is, but it's definitely not the one you should see for fastboot. That means you have those drivers installed on the wrong interface. I also suspect your bootloader might be corrupt or otherwise not functioning correctly. Using the factory cable will give you a better idea what's going on since you can (almost) be certain that the device has put itself into fastboot mode. Then you can focus on getting the drivers installed properly for the interface that appears in the device manager. As a last resort, you might have to open up the case and use USB boot (in Firekit) to flash a new bootloader.
Click to expand...
Click to collapse
Just quickly skimmed over your thread but have you tried holding down the power button for a minute or so and then powering it on? I would tend to agree with kinfauns that somehow your bootloader is broken if so a factory cable will do nothing only firekit will remedy a broken bootloader that's why I ask about the long press power off attempt...
Click to expand...
Click to collapse
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Please help me My Kindle is stuck at black screen after Kindle Fire logo. I have Android Composite ADB Interface driver installed, but when I plugged my Kindle Fire to my PC, it detected as a USB Mass Storage, and won't connect as an Android device so I couldn't do anything with adb commands or KFU...
See it in my topic for more information: http://forum.xda-developers.com/showthread.php?p=30542544#post30542544
ivanovicch said:
Just to update - the factory cable didn't do the trick. KF still stuck at KF blue/white logo - the bootloader must be corrupted.
Hence am going to try opening the case and flash a new bootloader. Wish me luck - will update again soon. Thanks.
Click to expand...
Click to collapse
Dear All. My KF is ALIVE! Had to open my back case and do the short point trick - http://forum.xda-developers.com/showthread.php?t=1405052.
Worked like a charm.
Thanks pokey9000, kinfauns and mainly the Thepooch - thank you for guiding me through this.
your welcome I`m quite pleased its fixed myself
same issue not unable to solve
i have exact same issue but i am having a problem to fix it. i wonder if anyone can help me here. i am trying to short the test point but in device manager its shoing usb not recognized again and again. please guide me whats wrong i am doing. using windows 7 (64bit)
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
hasanalikhattak said:
I have kfhd7 (tate) and i updated it from cm12.1 to cm13 but after the reboot it is now stuck on white-blue "kindle fire" logo. everytime i reboot it shows the white-yellow logo and then gets stuck on the blue one. moreover, i cant get to twrp3 using keys as it gets stuck and device gets hot. Tried fastboot and adb but the devices is shown offline. I dont have access to a fastboot cable and even dont hope that i will get one shipped sooner. kinldy help
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs

[Q] stuck at yellow triangle, can't install drivers. I hope I haven't bricked it.

I'm going to preface this with: I am a visual learner and kind of an idiot, so I went with the option I found that seemed the simplest.
Okay, I tried to root my kindle fire using the method found here: (rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire-6-3-1) because I wanted to try and flash CyanogenMod onto it, and now it's stuck at the yellow triangle push power for recovery mode screen. From what I've read when you push the power button to boot into recovery it's supposed to turn orange, but mine has never done that it's always either had the green power light on or the kindle is totally off.
For a while it was showing up like the picture in the Kindle Fire for Beginners thread (second post) but now it shows up like this (i.imgur.com/MKioa.png) went to delete the device to try and reinstall the drivers. I was told from several of the other yellow triangle threads here on xda that there was supposed to be an option to delete all the drivers when you go to uninstall, and there was the first time I tried to do it but now it doesn't give me that option (i.imgur.com/Ofcg2.png) also KFU tells me that ADB isn't installed (i.imgur.com/y3TkE.png)
For a while my computer wasn't even recognizing that it was connected at all; thankfully a reboot of the computer fixed that problem, but now it's only showing up as a USB Composite Device and I can't install any drivers onto it (i.imgur.com/yHSJV.png)
I've tried power cycling it, rebooting my computer, reinstalling the drivers (before it quit letting me do that), and reading every single related forum post I can find. So far nothing has worked.
I can't figure out how to use TWRP (because I will freely admit to being stupid.) Can anyone give me some suggestions on what I should do to make my fire work again?
You probably have the device in fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
You may or may not have the drivers installed correctly for this mode. It's hard to tell from your description. In this mode, KFU will always tell you ADB is offline because you cannot use adb commands in fastboot mode. KFFB explains why. You need try sending a command like "fastboot getvar product" and see how it responds. KFFB's third post explains how you do this...
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
The device and the host computer must be able to see the other the moment it goes into fastboot mode. If the command shows it is waiting for device, force the device off by pressing and holding the power button until it shuts down and turn it back on again. If you can confirm that the device is in fastboot mode using the 1st link above, but cannot send fastboot commands to it, you need to look at your drivers again. Start over by disconnecting the device and reinstalling from KFU's device driver installer. Follow the directions in the 2nd post of KFFB again to uninstall/reinstall drivers if necessary... the particulars are shown in parenthesis for the manual installation procedure.
Once you can send fastboot commands, you will need to change bootmodes to recovery or normal (KFFB's 3rd post). Use this guide to install a ROM...
http://forum.xda-developers.com/showthread.php?t=1638452
okay, well I went to bed and when I woke up it was blinking the 5 second boot loop (from what I found in the forum) so I'll read those links while it's charging on its wall charger. Hopefully they'll explain my problem.
You may or may not have the drivers installed correctly for this mode. It's hard to tell from your description.
Click to expand...
Click to collapse
Is there a way that I can see if I installed them incorrectly? Usually I just have windows 7 do the installing for me.

[Q] Bricked Kindle Fire (first gen.) computer won't recognize

I have had my Kindle Fire for over a year and I have used various ROMs. Most recently, I was using the HellFire ROM and it crashed out on me. I decided to go back to stock for a while but noticed a new version of FFF (v1.4a) so decided to install that. Now, it boots to the FFF screen but nothing else. I cannot enter the boot menu. My computer does not recognize the device (no sound from the computer recognizing that it was plugged in) with either a regular or factory USB cable (I've used the factory cable before to unbrick the device).
I have read through the other posts regarding similar problems but all of those posts were resolved with either a driver problem or with a factory cable. None of the utilities or terminal commands are useful since the device is not recognized.
I have let the battery completely drain (letting it sit in a drawer while I take a break from the problem). It does recharge with the factory charger, but one thing of note is that the LED stays green during the charge. It never turns amber either on the charger or when it is connected to the computer.
Anyone have any ideas? I've been scratching my head lots over this. Many thanks for anyone willing to scratch along with me.
So have you tried Soupkit? How did you flash your bootloader?
Thepooch said:
So have you tried Soupkit? How did you flash your bootloader?
Click to expand...
Click to collapse
First of all, thanks for replying and trying to help. I have tried SoupKit and the Macintosh utilities but I keep getting the same response "Your device appears to be offline."
I originally rooted the kindle by manually entering adb commands. I installed the bootloader with KFU.
Is the bootloader splash static or does it blink on and off? Are you able to accces the boot menu to reset bootmode or enter recovery or select normal boot?
Thepooch said:
Is the bootloader splash static or does it blink on and off? Are you able to accces the boot menu to reset bootmode or enter recovery or select normal boot?
Click to expand...
Click to collapse
The bootloader splash is static. I am unable to access the boot menu at all.
I have been playing with the "short the point" install TWRP over USB but to no avail. I get "waiting for OMAP44xx device" and that's all.

[Q] Kindle Fire HD 8.9 - 8.4.6 - stuck on blue logo, or fastboot screen.

Hello, sorry for my bad english.
Im a noob and have been looking and trying different things for days now and can't fix my KFHD8.9", I would greatly appreciate any help. Sorry if this have been asked, but ive tried everything and nothing seems to work or match the same problems.
I rooted my kindle fire hd 8.9" (8.4.6) and tried to install the 2nd bootloader + twrp (to eventually install CM10.2) using this guide (http://forum.xda-developers.com/showthread.php?t=2277105), but stupidly, I didn't back up on step 2. I attempted to flash the bootloader using fireflash and, as long as I could make it I did everything that was needed. I rebooted and pushed the volume up while booting, and it went to the blue logo and then into fastboot screen and then stoped there.
My pc (Windows 8) didn't recognized the device while in the fastboot screen as a kindle but as a portable device called "jem-PVT-prod-04"
I rebooted my KFHD pressing power button, and when starting again, I saw the orange logo, then the blue logo and it just got stuck there.
So now I just can get to the fastboot screen (by pressing volume up while its booting) or get stuck in the blue kindle fire logo if i dont press anything.
I would like to add also that while on the fastboot screen , My PC wont communicate with my device. I have the Android SDK installed and could use ADB before this happened.
I have tried the commands -i 0x1949 getvar product and -i 0x1945 reboot as suggested on many posts, but both of them stays in "waiting for device" for ever.
Then i tried using Kindle Fire First Aide as suggested on other posts but after downloading everything it gave me an error about something not matching with my device and what i was trying to do.
In top of that, somewhere I got the impression that I just got stuck in the middle of the procedure and that I could still install TWRP or flash a rom,
So now I don't know if my device is bricked, or stuck in the middle of the procedure or what, but if anyone could help me get back to the stock firmware or to twrp or something other than this two screens (blue logo or fastboot screen) it would be spectacular
thanx in advance.
I'm having the same exact issue more or less, but I can't pass the orange Kindle logo. My computer will recognize the Kindle for about all of 2 seconds, but only as Jem_.... then disconnects so I can't enter fastboot or move forward at all. I'm hoping that someone can help with this.
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Recd msg alert stunts513 to the error while using wallpaper fix 2.1
I am having a terrible time with this Kindle HD 2nd generation table I tried to root. I was following this guys post on You tube and got it rooted but something when wrong when I tried installing the 2nd bootloader and twrp. I ended up stuck with a blue kindle logo. I tried turning it on with the volume button pushed to the left and it went from orange to blue and then to the twrp recovery menu. That was a few days ago, Its been stuck in that mode ever since, there are no back up folders and I think was making the problem worse, as it seems I could do the adb push and now I cant, well at least i couldnt before running your wallpaper fix 2.1 I ran it once and it wouldnt take I dont remember the error, but my table was at the blue logo screen. I remembered reading about running something while you powered the device on because there was an few seconds of access to something, I cant remember so I tried that and unknown to me It appears from these notes i found that I suscessfully installed it - then tried again -then something about the backup??? I am going to cut and paste it here and not do a thing until I hear from you, as I dont want to mess it up. I didnt know the fix worked cause i was watching the command screen and not the side of the file where i have your tool on my desktop.
Here is everything from that run. in the attached file
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes somehow I have twrp and I think when I first got into the bootloop I had adb access but in fumbling around trying to fix it I lost adb access.
If I turn the kindle off, and then push power and do nothing it powers up with the yellow logo and in 4 seconds that log turns blue and it stays that way until i turn it off. In this state checking device manager it shows the device as an android phone, Android ADB interface. If I unplug the device the device manager no longer shows it - If I power up the device and while the logo is still yellow push the volume button to the left it boots to twrp
I re did the notes in a new pdf file I hope you can access them now. I tried looking at them from my post on my pc and got that same access code error. I cant win on this thing tonight,
Thanks for getting back to me so quickly
John
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Click to expand...
Click to collapse
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Click to expand...
Click to collapse
Hope this helps... someone.
pitcrawler said:
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Hope this helps... someone.
Click to expand...
Click to collapse
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Jdoki said:
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Click to expand...
Click to collapse
Yeah, I know there's a lot of information. It took me a long time and a lot of research before I attempted it as a noob myself. An important thing is to follow the tutorials word for word and skip nothing, and cross your fingers.
Got fastboot comunication between PC and KFHD
stunts513 said:
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanx a lot for the quick response! :good: I was finally able to install your great drivers. I had to be quick as you said in some other posts, because the pc only detects it for a little while, when the logo it's still orange on the kindle, I think. After that, and while on fastboot screen, my device manager would detect a Jem-something device, but could not install any drivers on it. So I had to install the drivers really fast while in the orange logo, oh, and had to disable the drivers signature check on windows 8 also.
Now I can use fastboot commands to reboot the kindle, but I can still only get to the blue logo or the fastboot screen.
I guess this means I now can use the kindle first aide to go back to stock and try again for the TWRP and 2nd bootloader. I'll post if I can't make my kindle boot normal again later.
Do you know if this was my kindle being bricked or was it something else?
Thanks a lot again, I was very worried that i wasn't getting anywhere. .:laugh:
Stuck on blue logo!
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
EricMitjans said:
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
Click to expand...
Click to collapse
You need to push a ROM onto TWRP. You should still be able to access TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 be glad you did not hard brick it.

Categories

Resources