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.
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]
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]
Hi
This e tutorial for the ones who are stock at FFF Blue logo, stuck at booting... And does not enter on recovery or system
This could happen maybe if you change the boot.img before flashing a new Rom like CM10 example
Also this guide is for the ones who dosent have a fastboot cable like me andalso does not have fastboot
So here we go...
-open a terminal command on fastboot folder
-download the file down
-type fastboot -i 0x1949 flash boot otter2-freedom-boot.img
-and hit enter....
-let it stay on "waiting for device"...
-now whit the kindle turned off, connect to computer whit a cable
-press power botton 1time
When the kindle boot into FFF it will immediately flash the boot.img
It will stuck on any moment and obviusly don't boot so look at the terminal command.
If it says sending.....OKEY
Writting......OKEY
-press power botton 10s and reboot normally an let it turn on the system, recovery will not work
If it dosent say OKEY and says FAIL. Try again like 2 times it will work
---Recovery---
On system
-Type adb shell
Su
Reboot bottloader
Type fastboot -i 0x1949 flash recovery (recoveryname)
Wait until saiys okey
-type fastboot -i 0x1949 reboot
-press power botton on FFF to enter recovery finished
If recovery dont work flash again the bootloader
If it help you can use thanks Botton
I WILL UPLOAD FILES TOMORROW BUT ALSO YOU CAN SEARCH FOR THEY ON XDA
Hello guys I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command". So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img". Everything ok, the screen resumes, 3 minutes later it died. This is hard brick?
FrancescoPtr said:
Hello guys I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command". So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img". Everything ok, the screen resumes, 3 minutes later it died. This is hard brick?
Click to expand...
Click to collapse
You are not supposed to flash the image. Make sure you have the latest version of sdk tools. AND if you are new to this kind off stuff READ careful before executing random commands not specific to your device. You might be better advised asking in twrp thread. That would also help keeping the forum clean.