Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.
thequietone said:
Okay, I have been through this board several times and googled it, but maybe I am not searching for the right thing and I would find it hard to believe that my situation is unique. Anyways I am hoping someone can point me in the right direction.
On to the issue, I connected my kindle fire tried to install TWRP, but it froze and I was stuck on the Kindle Fire Logo so after exhaustive searching I went with the USB Shorting Trick, so then I was able to get TWRP up and running. The only issue is that now I can only get the kindle fire to boot up when connected via USB and using Firekit LiveUSB. One out of 25 times I can actually get it to go into ICS, but as soon as I power it off, then there is no power light and it won't reboot unless using Firekit LiveUSB.
Anybody have any ideas or solution that has worked.
Thanks in advance.
Click to expand...
Click to collapse
Are you opening up the case each time you use usbboot?
What Firekit script are you using to boot the device?
What happens when it fails to fully boot in to the system?
Is your battery charged?
usbboot only loads a bootloader into memory temporarily. Once you've got the device booted, you need to flash a new bootloader permanently onto the device. I suggest FFF 1.4a...
http://forum.xda-developers.com/showthread.php?t=1632375
usb boot only
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.
Get it booted temporarily disconnect the battery then reconnect it let it continue to charge via usb maybe it will correct your problem. Or replace your system with something stock like without going fully stock paul has a new release http://forum.xda-developers.com/showthread.php?t=1439916 good luck
usb boot only
So unplugging the battery while plugged in via USB doesn't work, however I am able to get it to boot into ICS I just have to unplug the USB right after the script says Flash FFF... That would lead me to believe it's a problem with the boot loader, but I have tried several times to flash it with fff-u-boot_v1.4a.zip with no luck.
thequietone said:
Nope I only opened the case the one time, now it's closed and it won't boot without being plugged in and executing usb_install_fff_twrp or usb_boot_twrp. I have tried flashing with TWRP several times fff 1.4a to no avail when it goes to reboot, it won't show anything on the screen and there is no power light on, yet I know the device is working because I can connect the USB and run one of the usb scripts and it works.
I am using Firekit LiveUSB 1.1.
I am not sure how to answer the fully boot into the system since nothing happens, no power light and nothing on the screen when I attempt to turn it on.
I have flashed it several times with TWRP and I would have thought that a reboot when TWRP says it's done would have worked.
The battery is fully charged.
Click to expand...
Click to collapse
The fact that you are able to use those scripts indicates you are in usbboot mode (4003) or the hardware is defaulting to usbboot on its own which probably indicates that something about your bootloaders is a little off...
Try using the "fix all" script (I don't recall the exact name). This will return your partition table back to stock and then flash both the 1st and 2nd stage bootloaders.
Also try flashing FFF 1.4a again with TWRP and take note of the output it gives you if it fails.
usb boot only
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB
thequietone said:
Successfully ran the usb_fix_parts_and_install_fff_twrp
Then installed fff 1.4a and the output was
finding update package...
opening update package...
installing update...
FireFireFire 1.4a Originally By Pokey9000 and Modified by Hashcode
Checking sha1sum of boot loader file...
Check passed.
Attempting to Write Bootloader...
Done!
E:Cannot load volume /misc!
Did a reboot and it still only will boot back up with the USB
Click to expand...
Click to collapse
See if you can set the bootmode back to normal and reboot it. Running as root...
Code:
usbboot /root/firekit/aboot.bin /root/firekit/u-boot.bin; fastboot oem idme bootmode 4000; fastboot reboot
usb boot only
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)
thequietone said:
Tried connecting to PC running UBUNTU and ran the USBBOOT command and got nothing, so I powered off and ran the command and then reconnected the cable and ran the USBBOOT command and got the <waiting for device> after the sending image to target, then few seconds later got the FAILED (remote failure)
Click to expand...
Click to collapse
Did you ever have Hashcode's CWM recovery installed on your device or have you always used TWRP?
Have you run those Firekit scripts again after you installed FFF 1.4a?
The only other thing I can think of is that your device's bootmode is set to USB boot and that's why it doesn't load up the bootloader already installed on your Kindle Fire. It's seems to be waiting for you to use usbboot to send it a bootloader. Get to TWRP again, flash FFF 1.4a and run these adb command to set the bootmode to 4000 and reboot...
Code:
adb shell idme bootmode 4000
adb reboot
The problem is I can't get FFF 1.4a installed. When I try to do it via TWRP which is the only utility I have tried it appears to load successfully, but when I do the reboot, the screen won't come on and there is no power light. So I hold down the power button for the 20 seconds then run the FireKit commands hook up the USB and it boots back up, but won't boot on it's own.
Have you found a fix yet? I may have a solution from my experience with mine, which was bricked beyond imaginable (don't ask how ). I was able to install FFF+TWRP and restore to stock perfectly fine.
It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.
thequietone said:
It boots into ICS if I connect the USB cord. From there I am able to run everything, including ADB commands etc, however from trying to flash FFF 1.4a to resetting the boot mode has failed. Was even able to boot from USB with FFF 1.4a.
So the short story it's still not working. If you power off, it won't come back without the help of doing a usb boot.
Click to expand...
Click to collapse
You didn't answer the question of whether or not you've used Hashcode's CWMR.
From TWRP, run these commands...
Code:
adb shell idme ?
adb shell parted /dev/block/mmcblk0 unit b print
and paste the output here.
Also, if you can load ICS, download/install smirkit...
http://forum.xda-developers.com/showthread.php?t=1500935
and try to install FFF 1.4a that way. Using smirkit will raw write the bootloader image directly onto the partition.
Here is the screen shot. Couldn't get smirkit installed.
Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!
Still Unresolved
Nope I am still having the same issue. Right now, I just try to keep it charged hoping it won't die, because if it does then I have to USB boot to get it back up and running
dmp2007 said:
Did this ever get resolved? I am in the same boat. The only way I could get my KF to boot up was to use the USB short trick, but now, it won't let me go back to turning it on the normal way. It requires USB boot every time. Please help!!!
Click to expand...
Click to collapse
shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.
I haven't heard of it responding to touch. Mine works perfectly except for always having to USB Boot if it dies or if someone holds down the power button too long.
QUOTE=dmp2007;28967427]shoot, I was going to flash the bootloader tonight hoping that would fix it, but it looks like you've already tried that and it didn't work. Did your, or anyone else's, happen to stop responding to touch after the usb short as well? Using USB boot, i can get to the unlock (or recovery, touch doesnt work there either), but the screen doesn't respond to my touch. I know it isn't freezing because the clock still updates.[/QUOTE]
I too get this, I've been through what feels like every thread on here about this, only a few of these show up as the 'usb boot only' though and they all end in no answer. I have tried all forms of partitioning up to and including dd'n the p1.img over top of xloader and p2.img on top of bootloader.
With usb, i can go back fully stock (however, even fully stock wont boot without usb boot.. so its got to be busted xloader or bootloader), i can get TWRP installed, any ROM and its all usable.. until as OP said.. power out or reboot needed. It's bothering me enough just wanting to fix it I keep rebreaking perfectly good installs thinking some nugget I found/missed re-reading endless posts is the one.. just in case someone else comes through with this, here are my findings:
happened to me as originally I bricked to the point had to crack it open and short it to get it to boot via usb, finally working well using liveUSB firekit. However, from that point on, would NEVER boot on its own, and would NEVER shutdown/reboot without needing 20-30s of power button molestation. perhaps this is left over issue of the pin short... dunno
Once i figured out I could usbboot, basically went on with everything as normal. recovery, roms, back to stock, back to rom, etc etc. What seemingly never works, or simply oui can never get to, is the bootloader. All indications that I have known/been able to check seem to think its iinstalling, perhaps we are just never making it to it (xloader death)
So then I went crazy and tried everything from adb/fastboot raw on Mac, windows and linux, setting bootmode to 4000 every way with every tool listed on this site possible.. no joy.. usbboot is a must. Tried zeroing the mmcblk0p1/p2 and writing good versions on top, nothing.
Current state.. if I, via adb/fastboot/twrp/recovery do a reboot or shutdown.. the kindle shuts down screen and led's only (sometimes even leaving the green power light on, but almost ALWAYS just all black, but not off) .. dmesg notes that its stuck in a usb connect/disconnect loop, with an error:
new high-speed USB device number 33 using ehci_hcd
unable to get BOS descriptor
New USB device found, idVendor=0451, idProduct=d00f
New USB device strings: Mfr=33, Product=37, SerialNumber=0
Product: OMAP4430
Manufacturer: Texas Instruments
USB disconnect, device number 33
rinse, repeat, about every 3 seconds.
As you can see, BOS descriptor can't be found.. which is just a little stupid because the port its plugged into is 2.0
bcdUSB 2.00
but maybe there is still something there? not changing any port though, usbboot has no problem.
I sniffed the traffic of the usb bus while plugging in the USB cable after shutting down via 30 second hold, and its pretty much the same thing, just bouncing the connection before it has time to get started.. so it seems to be hitting this "issue" both on shutdown/reboot and startup. As I can't really tell, with usb being the only way for me to talk to the KF, I can only assume after a hard shutdown when I push the button again its probably doing the same thing (no lights, no screen), but I can confirm once I plug in the usb and it tries to boot itself.
Only sort of difference is sometimes it can go down into the dark reboot and I am able to run usbboot and it comes back up (usb never unplugged) but its been sporadic so I haven't chased it.
At this point I just want to figure out exactly what bit needs flipped in the front somewhere so I can reboot my KF like all the cool kids so I'll probably keep hacking on this issue until I really really brick it or hopefully help comes along or I figure it out myself. One good sign is I know have completely working dev/hack environments on OSX, win7, liveusb ubuntu AND linux mint debian so, I guess that is something.
YOU ARE NOT ALONE USBBOOT ONLY PEOPLE!! one love. =P
Hi and greetings to all
Before I mention my issue I would like to state..
I have read most of the KF posts like beginers guide,Before asking for troubleshooting help,The 5 second bootloop! aka: Don't let your battery die! etc and it is only because I cannot find a specific answer to my problem that I am posting
I would like to thank people like pokey9000 , kinfauns and all the clever people that have given us KF life saving posts and those that came up with things like FFF, TWRP etc etc, props to you all These have been valuable in the past when I have been stuck in loading roms, rooting etc
Background
for some reason my KF got stuck in the yellow triangle boot loop, rebooting every few seconds...
The battery died before I could get round to hooking it up to my computer and run the necessary scripts...
I tried the usual adb and fastboot scripts - no response, the power didnt come on and the device was not detected.error:device not found
I left it to charge with the AC POWER pack over night...still no life or detection
I tried the
Resorted to the ubuntu memeory stick method...
Ordered a case opener and waited for it to be delivered...
few days later it arived and I opend the KF - didnt break anything
tired the shorting trick - No joy, terminal showed still waiting for device and no power light on the KF :crying:
left to charge again, still no joy
tried adb and fastboot on windows again... no joy.. error:device not found
I think the only thing I havent tried so far is a factory usb cable but I cant see how that will help me here unless ofcourse someone can tell me otherwise
fyi I had FFF and twrp installed and running an ICS 4 ROM
When your not working on it keep it charging via usb note that your battery may charge very slowly also try some of the usb scripts powering your device fully down send the command start and keep the short and plug in when it says waiting for omap you may find better success keep trying till you find a script that works likely usb fix parts install fff twrp youll know when you get it right or usb boot fff
I want to wipe everything off my Kindle including the recovery and bootloader, is there a command I can issue to do this? (I'll be using firekit /w the short trick and adb push to reinstall my rom/bootloader/recovery)
I can't even begin to tell you why that's a bad idea and completely unnecessary.
Do you mind me asking what you are trying to accomplish with this and why you think it's necessary?
I had the old version of TWRP and bricked my Kindle, I got it to load the new version of TWRP with firekit and it unbricked my Kindle. Next, I set boot mode to normal because I wanted to flash a new rom, however then I got the blinking yellow triangle of death again, I ran usb_fix_parts_and_install_fff_twrp (how I unbricked it before) and shorted it but this time it didn't work and I got the blinking triangle again. So I though if it worked before with new version of TWRP maybe if I removed it completely and the re-ran "usb_fix_parts_and_install_fff_twrp" it would unbrick my Kindle again
Sorry for the long explanation
Oh I forgot, The reason I put it back in normal mode is because I thought I fixed everything and thought the battery would begin to recharge again, so I figured just downloading the rom to kindle itself would be easier than using adb push to transfer it from my computer, but then I couldn't even get back to twrp after the first time
The blinking triangle is due to a dead battery, not the bootloader installation.
Unplug the device and hold the power button until it shuts down completely.
Plug the device into your computer's USB (2.0) port and immediately hold the power button until it shuts off again.
If you can get it to shut down without starting up again, leave it plugged in for at least half a day to let it charge.
aullys and
I'll try that, thank-you
I have come into my possession a Kindle Fire 1st generation. When I got it, the youngster said it was “hacked for the Amazon App Store”… and the battery was dead. I traded an older laptop for it. I put it on a charger for a day or so and left it. It would boot to the “Stock” logo for several seconds, then the backlight would go slightly brighter and it would shut off.
I started reading up about some of the power-on issues around the web. I found most of my answers on “xda-developers.com” for my TF101 so I gravitated here.
Here is what I’ve done so far:
1. Acquired a factory cable... SO useful.
2. Flashed FFF v1.4a and TWRP v2.4.4.0
3. Played around with fastboot.exe commands -update, flash, erase, getvar, reboot, help
4. Flashed a stock bootloader and recovery… trying to get it to charge.
5. Disassembled and tested battery voltage… 4.10VDC on a 3.7V battery. That sounds good to me.
6. Tried the firekit boot from Live-USB. Won’t stay powered on.
Right now, I’ve flashed the FFF 1.4a and TWRP v2.5. What happens is, in normal boot, the fire boots to the FFF logo (White &Blue) goes to “Booting” and the power switch LED gets slightly brighter, then the backlight goes slightly brighter and the whole thing shuts off. If I push power to go to recovery, the fire shows “Booting.” Then, the power switch goes orange, then it goes off, then the whole thing shuts down. I cannot do any ADB commands because the Fire will not stay powered on in that mode. The factory cable keeps it powered on, but I’m stuck with fastboot.exe commands in that mode.
I do not have a stock charger. I’ve been using my charger from my TF101 and a cable from my phone or the factory cable. I’ve been futzing around with this thing for a few weeks and would like some input. I haven’t found an identical issue so I’ve decided to create a thread.
I’m wondering if I have a bad gate on the memory chip… I’ve seen desktops and laptops shut down with bad memory in the past. I’m reasonably savvy with a command prompt and not afraid to crack a box.
Hold the power button until the device shuts off completely. Plug it in to your USB cable power source (not the factory cable), and let it power on automatically. Immediately after it starts to power on, hold the power button to shut it off again. Let it charge in this state for a few hours and try to boot into recovery again.
soupmagnet said:
Hold the power button until the device shuts off completely. Plug it in to your USB cable power source (not the factory cable), and let it power on automatically. Immediately after it starts to power on, hold the power button to shut it off again. Let it charge in this state for a few hours and try to boot into recovery again.
Click to expand...
Click to collapse
Thank you Soupmagnet. I've done this and let it sit for a weekend... sorry I didn't mention it before. With a voltage reading of 4.1, I think I have a full charge (by the way, it doesn't drop over a day or so). You can be assured that I've tried most everything before posting. Please be gentle if I didn't state it previously
One of my issues is I can't get to anything on the fire itself. Even with the factory cable, is shuts off if I choose to continue... hold the power button and choose recovery, normal, reset boot mode. Is it supposed to be able to go to recovery when the factory cable is connected? It only stays powered if I leave it at the FFF logo.
pmrmx774 said:
Thank you Soupmagnet. I've done this and let it sit for a weekend... sorry I didn't mention it before. With a voltage reading of 4.1, I think I have a full charge (by the way, it doesn't drop over a day or so). You can be assured that I've tried most everything before posting. Please be gentle if I didn't state it previously
One of my issues is I can't get to anything on the fire itself. Even with the factory cable, is shuts off if I choose to continue... hold the power button and choose recovery, normal, reset boot mode. Is it supposed to be able to go to recovery when the factory cable is connected? It only stays powered if I leave it at the FFF logo.
Click to expand...
Click to collapse
What command did you use to install TWRP?
soupmagnet said:
What command did you use to install TWRP?
Click to expand...
Click to collapse
Fastboot -i 0x1949 flash recovery c:\KFU\recovery\twrp.img.
This is after I renamed the v2.4.4.0 file to old_twrp.img and downloaded the v2.5 that I found last Friday. Previously, i'd used the KFU. Last week I played around with flashing different bootloader and recovery to see if I could get it past the FFF or stock. At this point it's a challenge to get it to go further than FFF.
pmrmx774 said:
Fastboot -i 0x1949 flash recovery c:\KFU\recovery\twrp.img.
This is after I renamed the v2.4.4.0 file to old_twrp.img and downloaded the v2.5 that I found last Friday. Previously, i'd used the KFU. Last week I played around with flashing different bootloader and recovery to see if I could get it past the FFF or stock. At this point it's a challenge to get it to go further than FFF.
Click to expand...
Click to collapse
Use fastboot to flash this to your system partition and see if you can boot normally.... http://d-h.st/NzN
Perhaps it is hardware, not software
Just had a very similar issue. Turned out to be stupid simple.
Use spudgers to gently take the back off the case (a small flathead screwdriver should do the trick). then check the connection between the battery and the motherboard. In my case, my daughter had dropped it enough times that the connection was not all the way out but not enough in. This caused the exact behavior you are describing. Took me 2 minutes to fuss with once I got motivated.
Jon