As a disclaimer, I've searched for this question, but have only found when the question is asked as a much broader topic and goes unanswered.
That being said, I can't seem to get TWRP 2.0 installed through using "fastboot boot", the Kindle Fire Utility, or the technique using dd to rewrite the contents of the parttitions.
The closest I've come is getting FIREFIREFIRE to start up using the "dd" technique, but TWRP still will not start when I hit the power button for recovery. And yes, I did use "dd" on the TWRP image file as well.
Also, I even tried using fastboot to flash u-boot.bin onto the bootloader partition, and twrp onto the recovery partition. Still, I can get to the yellow, but no further into starting TWRP.
Any help would be appreciated. At current time, I have the stock bootloader and recovery partitions on the Fire and it is rooted.
Thanks.
maybe your in fastboot mode and hopefully your drivers are installed correctly you can use:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
this should bring you to normal bootmode
I've tried that in case there was an issue. In fact, if I don't press the power button during the yellow triangle, the Kindle Fire OS will start as normal after 10-15 seconds. So, it looks like the bootloader is working right and I'm in the correct bootmode. But, if I hold down the power on the yellow triangle (which is supposed to start TWRP), I just get stuck and nothing starts.
That being said, I think I'm in the correct bootmode.
if i don't remember wrong there is an issue with installing twrp with dd
i think you could retry the installation or simply use KFU (but don't use the drivers of kfu if you have working ones)
Thanks.. I'll give it another shot tonight, and then.
when the device starts and the Triangle appears, are you just pressing the power button once? or are you pressing it until it turns orange?
I have to press it a few times before it changes color to orange and then just let it alone. A long press doesn't work for me.
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
not possible - had the same - rooted with superoneclick on 6.2 then updated
i think your twrp install failed - would retry
I finally figured out my problem. For whatever reason (which is still unknown to me), the Kindle Fire Utility was not able to properly download the twrp.img. The file that was downloaded was 8K (which I'm guessing was some sort of error web page). Anyway, I went straight to teamw.in and downloaded the latest version that clocked in at around 10MB, installed it via the "fastboot -i 0x1949 boot twrp.img" command and all is well now.
If anybody is having similar problems, you might want to check the size of the twrp.img file. 10M = good, 8K = bad.
vaporofnuance said:
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
Click to expand...
Click to collapse
It turns orange the second it starts booting recovery. That's when you should let go. Holding the power button for ~30 seconds for any reason is a hard signal to the PMIC chip to power off.
good that it works again ...
please mark the subject of the topic (edit first post) to [Solved]
Related
edit: Kindle Fire fastboot working. Allows for reflashing ROMs and booting over USB.
Recommended that you have your kindle already opened so that you can get to the battery cable to hard reset if necessary.
Instructions to follow.
transfuntioner said:
<posting here as i dont have access to devel forum yet>
Looking at the bootloader & the u-boot source, it looks like there's 2 ways to get to fastboot. The bootmode nvram setting, and a special usb cable.. I think I'll go the nvram route though I havent investigated how to set it yet.
Just to be prepared I'm going to add usb driver's inf.
%SingleBootLoaderInterface% = USB_Install, USB\VID_1949&PID_0FFF
So .. anyone else working on this?
Click to expand...
Click to collapse
I dont have a gingerbread build handy, is there another dev that can build me a fastboot.exe to include 0x1949?
I think my fire is stuck in fastboot mode.
transfuntioner said:
I dont have a gingerbread build handy, is there another dev that can build me a fastboot.exe to include 0x1949?
I think my fire is stuck in fastboot mode.
Click to expand...
Click to collapse
NVM on the fastboot.exe request, I have a working one.
fastboot mode is confirmed .. i have a fastboot talking to the fire. It shows up in 'fastboot devices' (the id is 0123456789abcdef), and responds to reboot & boot commands.
Now trying to boot out of fb mode, I should have set the 'other' nvram bootmode
NOTE: Instructions are terse and intended towards developers for now.
Standard disclaimer, I am not liable if you brick your fire.
Requisities:
- working adb, (on windows) with the additional %SingleBootLoaderInterface% entry mentioned
- working fastboot binary that recognizes / allows specifying the vendor id (0x1949)
- root. it may work without, but you probably want or have it already
Also recommended:
- boot.img from the latest sw update.
Procedure:
- get a adb shell
- use the '/system/bin/idme' command to set the bootmode. I suggest you first run 'idme ?' and write down your default, mine is "4000 0".
- if you set bootmode to 0x4002, the fire will stay in fastboot mode when it reboots
- if you set bootmode to 0x4003, it's supposed to timeout from fastboot mode, but I did not have much luck getting a normal boot after the timeout (did not play too much here).
- if you decide you dont want fastboot mode, run 'idme bootmode "4000 0"' to reset back to default for normal booting.
WARNING:
IF YOU REBOOT AT THIS POINT THE FIRE WILL BE IN THE FASTBOOT MODE. I HAVE NOT FOUND A WAY TO EXIT THIS MODE AND RETURN TO THE NORMAL OS WITHOUT A WORKING FASTBOOT CLIENT.
REPEAT:
YOU MAY BE BRICKED IF YOU DONT HAVE WORKING TOOLS.
When you boot into fastboot mode, it will show the "Kindle Fire" logo. The power button does not appear to do anything; therefore, if you boot a bad kernel/image it may get stuck and require a hard reset (pulling the battery cable).
You should now have access to the standard flashboot functionality (update, flash, usb boot, etc). Note that reboot-bootloader will bring you back to fastboot.
I currently use 'fastboot boot boot.img' (from the sw update) to get back to a working state. Once booted, use idme to disable fastboot.
Now, on to recovery's & custom roms!
so any more information on the "special usb cable" like what size resistor on pin 4?
death2all110 said:
so any more information on the "special usb cable" like what size resistor on pin 4?
Click to expand...
Click to collapse
I dont have hardware handy to determine this, but having a cable will definitely make things easier going forward.
Brief updates..
Unlike previously mentioned, it looks like long press power button typically should work.
The idme command is available in the bootloader. So you can set normal bootup mode from fastboot, then reboot. eg.
fastboot oem idme bootmode 4000
fastboot reboot
How to get latest update pack ?
Sent from my SAMSUNG-SGH-I777 using XDA Premium App
any idea what tools i can use to check what amount of resistance i need? I may just go out to the garage and grab 3 100k resistors and try the numerous SGS2 methods (specifically 3 resistors twisted together and jumping pins 4 & 5
Stuck in fastboot
Hello,
I followed these steps including adding the %SingleBootLoaderInterface% line mentions to the usb inf. I was able to get the Kindle Fire to set bootmode to 0x4002.
I downloaded fastboot from here, 32-bit only?
http://forum.xda-developers.com/showthread.php?t=463627
Tried to get fastboot 64-bit via this route, no good:
http://rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems/
Now that it's in bootmode, neither my x64 PC or x86 Mac can see the device via a recent fastboot.exe and fastboot-mac application using a standard mini-USB cable. Suggestions? Is there a different fastboot.exe that I should be using?
transfuntioner said:
NOTE: Instructions are terse and intended towards developers for now.
Standard disclaimer, I am not liable if you brick your fire.
Requisities:
- working adb, (on windows) with the additional %SingleBootLoaderInterface% entry mentioned
- working fastboot binary that recognizes / allows specifying the vendor id (0x1949)
- root. it may work without, but you probably want or have it already
Also recommended:
- boot.img from the latest sw update.
Procedure:
- get a adb shell
- use the '/system/bin/idme' command to set the bootmode. I suggest you first run 'idme ?' and write down your default, mine is "4000 0".
- if you set bootmode to 0x4002, the fire will stay in fastboot mode when it reboots
- if you set bootmode to 0x4003, it's supposed to timeout from fastboot mode, but I did not have much luck getting a normal boot after the timeout (did not play too much here).
- if you decide you dont want fastboot mode, run 'idme bootmode "4000 0"' to reset back to default for normal booting.
WARNING:
IF YOU REBOOT AT THIS POINT THE FIRE WILL BE IN THE FASTBOOT MODE. I HAVE NOT FOUND A WAY TO EXIT THIS MODE AND RETURN TO THE NORMAL OS WITHOUT A WORKING FASTBOOT CLIENT.
REPEAT:
YOU MAY BE BRICKED IF YOU DONT HAVE WORKING TOOLS.
When you boot into fastboot mode, it will show the "Kindle Fire" logo. The power button does not appear to do anything; therefore, if you boot a bad kernel/image it may get stuck and require a hard reset (pulling the battery cable).
You should now have access to the standard flashboot functionality (update, flash, usb boot, etc). Note that reboot-bootloader will bring you back to fastboot.
I currently use 'fastboot boot boot.img' (from the sw update) to get back to a working state. Once booted, use idme to disable fastboot.
Now, on to recovery's & custom roms!
Click to expand...
Click to collapse
I had the same issue....but i fixed it!
Code:
fastboot -i 0x1949 oem idme bootmode 0x4000
fastbooot -i 0x1949 reboot
Played with the 0x4003 fastboot "countdown" mode a bit. Seems like it is timing out of fastboot, but not continuing to boot up the rest of the way. After a few seconds the kindle fire logo goes away and the device no longer responds to fastboot commands. Waited maybe a minute or so after it left fastboot and it didn't boot. Though since you found that we can set the bootmode value from fastboot it doesn't really matter.
Also have been playing around with attempting to get my fire to boot a modified boot image. So far I've simply extracted the kernel/initrd from the 6.1 update boot.img and repacked it without modifications. Unfortunately the Fire refused to boot the resulting image.
Going to continue fiddling.
Well managed to successfully repack a boot.img.
The problem i was facing was caused by 2 issues while running mkbootimg.
1) Derped and didn't specify the correct page size (4096)
2) Needed to include a base address of 0x80000000.
wait i'm stuck in the phase where it times out after the kindle logo and it doesn't respond to fastboot commands... what did you do to get out of that?
any help would be GREATLY appreciated before my battery dies. i have my clockwork port saved on the sdcard!
or if somebody can upload their fastboot binary
edit: got it, i needed to specify the vendor id as mentioned on the bottom of page one
thanks to those who were trying to help me (although probably nobody as it's 3am...)
JackpotClavin said:
wait i'm stuck in the phase where it times out after the kindle logo and it doesn't respond to fastboot commands... what did you do to get out of that?
any help would be GREATLY appreciated before my battery dies. i have my clockwork port saved on the sdcard!
or if somebody can upload their fastboot binary
Click to expand...
Click to collapse
I did a long press of the power button and it turned off. Then before turning it back on i ran:
Code:
fastboot oem idme bootmode 4000
Let it sit in "waiting for device" and powered the kindle back on.
Attached my fastboot binary for linux if it's useful for you. It's compiled from AOSP with the 0x1949 vendorid added in.
I don't have the -i option on my version of fastboot. Could you post a windows version of the one you're using?
Edit: found version of fastboot.exe that supports -i in SDK_r07.
I can't post outside links yet, but here's the URL:
code.google.com/p/softy-warely/downloads/detail?name=android-sdk_r07-windows.zip&can=2&q=
Thanks death2all110. Got it to reboot to break out of the fastboot cycle.
New question:
I did fastboot -i 0x1949 boot recovery.img (from the Kindle 6.1 update) and now I can't fastboot back in to break out of the fastboot cycle again:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
I'm giving CM7 a shot right now. Gonna fastboot flash the system.img generated as well as the boot.img although I doubt this will work
death2all110 said:
any idea what tools i can use to check what amount of resistance i need? I may just go out to the garage and grab 3 100k resistors and try the numerous SGS2 methods (specifically 3 resistors twisted together and jumping pins 4 & 5
Click to expand...
Click to collapse
I dont think it'll hurt to try.. FWIW I didnt see anythign obvious in the source or from quick googling for the specs. Didnt spend a lot of effort on it though.
JackpotClavin said:
I'm giving CM7 a shot right now. Gonna fastboot flash the system.img generated as well as the boot.img although I doubt this will work
Click to expand...
Click to collapse
Yeah I am going to play with existing gingerbread builds as well because I dont think ICS will ever finish building on my machine!
I am planning on just flashing system.img and then usb boot with the stock kindle kernel / boot.img.
It didnt do anything, I found a Micro USB for LG Devices with selectable resistance. But I might buy an actual USB jig for the SGS2 but i dont want to waste my money on it if it doesn't work...
Hmm. Theres gotta be a way...
careful flashing
This may be known to experienced android devs but I thought I'd mention as I am not & just ran into it.
When you flash an individual partition you're limited by the ram, in this case the image size needs to be less than the value reported.
fastboot getvar downloadsize
downloadsize: 1d0000000
So around 486 megs.. just some extras steps needed if you're working with the 512M system partition.
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Do you have fastboot access? Try running the following...
fastboot -i 0x1949 oem idme bootmode 4000
Try this: http://forum.xda-developers.com/showthread.php?t=1422832
Thanks guys, ill try those and post back w the results.
so i tried fastboot -i 0x1949 oem idme bootmode 4000
and it seems to have been successful, in that it is now back to its original boot loop state. however, it is still not booting fully.
it seems that adb commands are now working, i can do adb shell, and navigate root folders (system etc).
zombie, i havent had much luck with that route, i had tried that earlier.
I've seen people mentioning that the cause for their brick had something to do with permissions, so i did ls -l in the adb shell, here are the permissions for some of the relevant folders. if there are any others that might be helpful, let me know.
root -> drwx------
system -> drwxr-xr-x
sdcard -> lrwxrwxrwx
oh and framework-res.apk -> -rw-r--r-- (same as all other files in that directory)
i did modify the framework-res to change the background image. it successfully booted at least once after the modification - i used metamorph, i loaded the file, then rebooted for it to take effect. this was successful, but i believe it was the next reboot which did my kindle in, so possibly related.
i rambled a bit, but maybe if i replaced the current framework-res.apk with the stock framework-res.apk, that might be worth trying? are all stock framework-res.apk files the same at stock? because i don't have a copy of the original that came with my kindle.
i would go back into fastboot and then flash over TWRP... and then reinstall your os from scratch. it would probably be easier than trying to root around fixing it from the inside.
Thanks xrishox, I might do that. Is there a thread detailing how to do that?
When I tried doing fastboot I lost the ability to use adb commands so I'm not sure how to go about flashing twrp.
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
jackofaiitrades said:
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Click to expand...
Click to collapse
Howdy!
I recently just dealt with this same issue. My KF was stuck in boot loop and wouldn't be recognized by my computer. I left it in bootloop until it ran out of battery. Once it was completely drained, I connected it to my computer and my computer recognized it, I then reinstalled the drivers. Right after that I used KFU to change bootmode to normal boot and let it fully charge! Good to go! Hope this helps someone.
from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and here is a note from vashypooh - the op of kfu
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
maybe it helps someone ...
Thanks guys, I won't be near a computer until tonight but will try these out as soon as I get back
lmntone said:
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
Click to expand...
Click to collapse
Tone you're a life saver, thanks. I'm up and good to go.
good that it's working again !
have you seen this one in the dev section - could save a lot of handwork:
http://forum.xda-developers.com/showthread.php?t=1428428
Also, when I get back to my computer again, ill update my OP to include the solution so that others might benefit. its like a 20 minute fix but took me days to resolve it (largely due to lack of comp access but that's beside the point).
I have rooted a few phones and even two kindle fires but I messed up my fathers.. Rooting went fine, I was able to install the google framework and vending.apk.
On reboot kindle fire logo kept repeating.
Where I think I went wrong wrong was changing the permissions on vending.apk I might have changed permission on system/apps.. I ran the unbrick application but didn't know what the right issue so I ended up going a little hog wild trying "stuck at logo", "recovery" and "modded system/application"
now it only boots to press power for recovery page.
It is correct that I need to get adb shell working to have a shot here? I decided (a little to late) to slow it down but the shell didn't seem to be working at the point I stopped..
the kf is in fastboot mode - adb ist'n working in this mode
what tells your device manager? it should be "android adb interface" under "android phones" - if not update your drivers
then you can issue:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
if it says <waiting for device> to the first command let the command open and power off the kf by holding pwr button ~20sec - power on again - the command should be picked up and finished - pwr off/on again
Thanks... Will try this in a few hours when I get home
Thanks... After that I was able to get the ADB shell and find the issue with my permissions...
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
I just did a restore setting in the CM7 option after that I cannot boot into the CM7 but only the TWRP...
Can anyone tell me how to reinstall the TWRP...
I tried to use the kindle fire utility to re-install it, however it doesn't connect...
always shows offline..
please help
thanks
Did you restore bootloader, recovery and system from your backup using TWRP? If so you should have TWRP installed.
Please provide detail info what you have done to give further help.
You may need to update your USB diver to get adb working and to be able to install recovery software.
Sent from my Amazon Kindle Fire using Tapatalk
i think you said boot to recovery in cm7 - now you'r in a recovery bootloop - means it boots allways to recovery by itself - right ?
if so (if it is booted to twrp) use kfu option1 - bootmode normal
or issue manually:
adb shell idme bootmode 4000
adb reboot
an other method is to use fastboot commands:
fastboot oem idme bootmode 4000
fastboot reboot
in the case it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if commands don't work check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Can anyone tell me what the befits are to running cm7 vs a lunched like adw ion the fire?
Hey guys,
I'm sorry I couldn't figure out what to do next simply by searching your forum, so I will try to be both as brief and as descriptive as possible.
I started here (http://forum.xda-developers.com/showthread.php?t=1568340) trying to root my fiancee's KF 6.3. I didn't feel comfortable using KFU or similar because those programs are built for Windows and I am using Linux. The Kindle Fire seems to be stuck in a recovery loop. When plugged into USB (using the cable that's actually for my LG Optimus phone), it boots to FireFireFire (yellow triangle) then reboots constantly. At no point is it accessible via adb devices or fastboot, and it doesn't show up under lsusb, which would be the equivalent to not showing up in Device Manager in Windows. (The driver should be fine because all of this was working fine originally when I started the process.)
So I guess my question is what now? I've read a few things about needing a "factory cable" which may set it back into fastboot mode, and I'm pretty sure I could get going again from there. Is that what I need to do? TIA for any help.
PS - I've successfully rooted my LG Optimus S and flashed custom ROMs, so I'm not totally inexperienced. I use Arch Linux and I'm comfortable on the command line. If you have a solution for Windows, I *might* be able to translate it into Linux speak, so don't hold back. Same goes for Ubuntu/Debian - those are totally different than Arch Linux, but I might "get it" enough to translate it.
PPS - I have intentionally omitted information relating to what I was doing when I caused this for brevity, but I would be happy to discuss what steps I took in following the above linked thread if some guru believes it's relevant or someone wants to know.
A factory cable is a last resort kind of thing so I wouldn't jump the gun quite yet, although it doesn't hurt to have one in the first place.
It would be helpful to know which step in the rooting process things went awry. The constant rebooting/restarting isn't typical. Did you make sure you had enough battery before trying to root?
FIREFIREFIRE loads in a temporary fastboot and with the version you are using it lasts for about ten seconds (before the green light goes dim). You can issue fastboot commands during this time without the need of a factory cable.
See if you can get...
fastboot devices
...to be recognized during this time.
Sent from my Amazon Kindle Fire using xda premium
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
It would be helpful to know which step in the rooting process things went awry.
Click to expand...
Click to collapse
OK, let's start with that.
From the thread I linked in the first post:
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
Click to expand...
Click to collapse
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
Howto flash by hand
Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. Currently KFU or fbmode is the easiest
flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
reboot: "fastboot -i 0x1949 reboot"
Click to expand...
Click to collapse
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
pbailey212 said:
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I think the problem here is the he can't get past the bootloader and stuck in an ACTUAL bootloop. In which case, adb commands are useless.
One thing that could be causing problems is the USB cable being used. If the device only experiences these symptoms when plugged in then I would say that's most likely the case.
Sent from my Amazon Kindle Fire using xda premium
I suggest you build a firekit USB for Linux. Search for firekit for Linux thread in the development section.
Sent from my Amazon Kindle Fire using Tapatalk 2
palintropos said:
OK, let's start with that.
From the thread I linked in the first post:
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/showthread.php?t=1475740
Installing TWRP 2.0.0 is different than installing TWRP 2.1.0. I think the instructions on the TWRP site is for the old version, but they link the new one.
http://forum.xda-developers.com/showpost.php?p=24732291&postcount=1298
Your OP sounds suspiciously like a dead battery, but you say you've corrected that. You might want to connect to your OEM charger for a while anyway and see if that helps
Also, in my experience, fastboot on linux required elevated privileges. Try running it as root.
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/show....php?t=1475740
Click to expand...
Click to collapse
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
palintropos said:
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
palintropos said:
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
Click to expand...
Click to collapse
Have you tried setting the bootmode to normal and rebooting?
fastboot oem idme bootmode 4000
fastboot reboot
Like I said before, it would probably be best for you to try this as root.
EDIT: It's also possible your system is broken and the KF can't complete its boot process. When you start up the device, the boot logo will first come up. Does the display go black after that and come back with a dimmer yellow triangle logo? Because if it's doing that, it's not in fastboot any more.
kinfauns said:
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
Click to expand...
Click to collapse
Ditto. If you can get the device to be recognized even for a second, it's still enough time to issue...
fastboot -i 0x1949 oem idme bootmode 4000
Just keep trying
[Edit:] or what he said
Sent from my Amazon Kindle Fire using xda premium
Yay! I played around and got my udev rules working, and I got a reading on (sudo) fastboot devices, so I was finally able to set the bootmode to 4000 and reboot. Everything seems to be back to normal now. The Kindle appears to be working fine though not rooted.
Please let me know:
if there is anything else I should know to make sure the KF is normal
if there is any additional info I should post to benefit other users who might have this same problem
or if I should mark this thread SOLVED/RESOLVED or equivalent and how to do so.
if your fastboot ever stucks in waiting for device mode and you are on linux
try once with either root user or using sudo command.
thats one of the thing people forget most of the time and get stuck there.
http://forum.xda-developers.com/showthread.php?t=1576675
Try the above with the kindle switched off you should see waiting for devic, then press power once ( fast boot should kick in when you power on)
Sent from my Amazon Kindle Fire using xda premium