Post Reply

[Q] bootloop stuck, can't fastboot, need case open short instruction

OP lob455

9th July 2014, 02:20 AM   |  #11  
sd_shadow's Avatar
Recognized Contributor
Flag South Dakota
Thanks Meter: 1,770
 
4,406 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Quote:
Originally Posted by lob455

Thanks @sd_shadow for the reply.

In recovery mode, TWRP reports that it is version 2.6.3.1

I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.

If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.

I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
The Following User Says Thank You to sd_shadow For This Useful Post: [ View ]
9th July 2014, 03:34 AM   |  #12  
Thepooch's Avatar
Recognized Contributor
Thanks Meter: 1,060
 
2,466 posts
Join Date:Joined: Mar 2012
More
When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.
9th July 2014, 10:32 PM   |  #13  
OP Junior Member
Thanks Meter: 0
 
7 posts
Join Date:Joined: Jul 2014
Quote:
Originally Posted by sd_shadow

I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot

@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.

My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
9th July 2014, 11:10 PM   |  #14  
Thepooch's Avatar
Recognized Contributor
Thanks Meter: 1,060
 
2,466 posts
Join Date:Joined: Mar 2012
More
Quote:
Originally Posted by lob455

@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.

My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.

Just place a Rom on your Sdcard and flash it.
The Following User Says Thank You to Thepooch For This Useful Post: [ View ]
10th July 2014, 12:19 AM   |  #15  
sd_shadow's Avatar
Recognized Contributor
Flag South Dakota
Thanks Meter: 1,770
 
4,406 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Quote:
Originally Posted by lob455

@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.

My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.

Try the mount option in twrp again
14th July 2014, 04:01 AM   |  #16  
OP Junior Member
Thanks Meter: 0
 
7 posts
Join Date:Joined: Jul 2014
Quote:
Originally Posted by sd_shadow

Try the mount option in twrp again

@sd_shadow @Thepooch

Thanks both of you for your help. But not all stories have a happy ending.

Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.

I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.

At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
14th July 2014, 08:12 AM   |  #17  
Thepooch's Avatar
Recognized Contributor
Thanks Meter: 1,060
 
2,466 posts
Join Date:Joined: Mar 2012
More
Quote:
Originally Posted by lob455

@sd_shadow @Thepooch

Thanks both of you for your help. But not all stories have a happy ending.

Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.

I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.

At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.

The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck
14th July 2014, 05:51 PM   |  #18  
sd_shadow's Avatar
Recognized Contributor
Flag South Dakota
Thanks Meter: 1,770
 
4,406 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Quote:
Originally Posted by lob455

@sd_shadow @Thepooch

Thanks both of you for your help. But not all stories have a happy ending.

Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.

I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.

At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.

I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Kindle Fire Q&A, Help & Troubleshooting by ThreadRank