Edited OP to be shorter to the point:
I am stuck in fastboot but can not establish an adb connection to set the boot mode back to 4000.
Xplorer4x4 said:
I was tired and trying to update my KF to FFF1.3 and TWRP 2.1.0. I am now stuck at the new FFF boot logo(green android guy with KF text under neath). The update to FFF1.3 went smooth. Then I moved on to TWRP. So I tried flashing the img file via terminal emulator rather then using ADB over my computer. So first I set the boot mode to 4002. Success! Then I tried to flash the img file, but was getting errors(I think it was because I forgot to cd in to the downloads folder so Terminal Emulator knew where the file was). Well Due to not being able to flash I had to set up my PC again for the KF to use ADB as I had a system crash since then. So I got hung up with not being bale to use ADB and decided to reboot the KF, thinking it needed a reboot before the PC would recognize it. After rebooting I for stuck on the FFF 1.3 logo. I know ADB is fully functional now(forgot to install an API) but the KF Utility will not recognize the device to be able to reset the boot mode to 4000.
Any suggestions?
Click to expand...
Click to collapse
can't use term to flash like adb, gotta use the dd if= method.
might be I'm fastboot if its stuck at the startup logo.
Sent from my HTC Glacier using xda premium
Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D
DeadChex said:
Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D
Click to expand...
Click to collapse
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.
Xplorer4x4 said:
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.
Click to expand...
Click to collapse
opps, I lied... you cant issue idme from fastboot.... nor can you issue fastboot shell...
so, no adb at the very beginning of the KF boot? Does fastboot notice it
Try "Fastboot Reboot" if fast boot works... or 'Fastboot continue"
DeadChex said:
so, no adb at the very beginning of the KF boot?
Click to expand...
Click to collapse
Nope, not at all.
Does fastboot notice it?
Click to expand...
Click to collapse
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?
Xplorer4x4 said:
Nope, not at all.
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?
Click to expand...
Click to collapse
the boot process goes... Bright LED (first turning on) > Dim LED (Fastboot and Button input) > Bright LED (Normal Boot)
Where is it stuck?
Use "fastboot devices" to see if its listed in the beggining (when bright green)
but, if its going Bright, that means its not trapped in fast boot
(Fastboot is a diffrent program from ADB completly, just throwing that out there, I've attached it if you need it)
Something very enlightening I found somewhere around this great place:
"
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
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
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
"
Edit: You do need the file in the above post when doing this over usb.
Sent from my Amazon Kindle Fire using XDA
freefaling said:
Something very enlightening I found somewhere around this great place:
Click to expand...
Click to collapse
This is great information but totally useless with out a working ADB.
DeadChex said:
(Fastboot is a diffrent program from ADB completly, just throwing that out there)
Click to expand...
Click to collapse
I am aware, but thanks anyways.
fastboot devices does give an out put after the dim. Did not test before the dim.
Good News: I tried the "fastboot -i 0×1949 oem idme bootmode 4000" command again and got an unrecognized vendor ID. So despite following the instructions to modify the 2 .ini files, and accept the install driver warning, and selecting the location for the ini manually as you should, I realized something was wrong with adb. So I used the install driver bat from the KF Utility zip,and got adb working. Issued the 4000 boot command and back in business.
Thanks for all the help guys! I think you guys managed to provide the fastest responses to help I have ever needed, and it is rare I ask for help, so that makes the experience that much better.
Related
Hello, I'm Pyrostic and I alpha tested the Kindle Fire build of TWRP 2.0.
The build that was posted last night was that of an older version. The build has since been fixed and re-uploaded at: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
See @agrabren on twitter for the latest details on TWRP 2.0
For Kindle Fire TWRP 2.0 support please see the Kindle Fire RootzWiki forum. Team Win will not be providing support here.
During install when your device gets to the "Reboot" screen run
Code:
adb shell
idme bootmode 4000
If you did flash the old version and you find yourself stuck at the Kindle Fire screen you simply need to replace your twrp-blaze-2.0.0RC0.img and run the following snippet of code.
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if you haven't flashed yet. Please DO NOT FORCE install this new image using a dd command such as this:
Code:
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Simply follow the following instructions after downloading the image at http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img in an ADB prompt:
Code:
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
This will install both the FIREFIREFIRE U-boot and TWRP 2.0 .
FURTHERMORE if you did use the DD commands stated above you may not be able to get into ADB, and I hope fastboot still works for you. If it does, try :
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
If you are having problems please try the following. It has been reported that it is helpful to others.
If you LOVE TWRP 2.0 on your Kindle Fire. I suggest donating to @agrabren (<--- donation link) for his hard work and thanking me here for my testing .
I will not be replying to this thread. If you have issues please join us on RootzWiki for follow up support. I merely posted this here because I do care for my community in general.
There are so many different guides floating around and I've decided to simply follow this one. However, I get 'fastboot: not found' after the 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' command. All I've done is put the twrp-blaze-2.0.0RC0.img on my sdcard and run the following commands..
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Did I miss a step? Thanks.
Is there anything I can do since I used the dd command and am now stuck at the firefirefire screen?
Edit: Tried the "fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img" and all I got was < waiting for device >
Fix: I followed http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222 worked like a charm
i did the dd install... not having any adb issues though. are there any other problems with installing it that way?
I also used dd with no issues and can boot in and out of TWRP with no issues.
Sent from my Kindle Fire using xda premium
ags29 said:
There are so many different guides floating around and I've decided to simply follow this one. However, I get 'fastboot: not found' after the 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' command. All I've done is put the twrp-blaze-2.0.0RC0.img on my sdcard and run the following commands..
adb shell
su
idme bootmode 4002
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Did I miss a step? Thanks.
Click to expand...
Click to collapse
Yes a couple things, put the twrp-blaze-2.0.0RC0.img file in the folder where you have fastboot installed. and It doesn't sound like you have fastboot on your computer. Please look around.
borborpa said:
I also used dd with no issues and can boot in and out of TWRP with no issues.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
I also use dd method to install FIREFIREFIRE and twrp. After that I lost the ADB connection. Try to issue the comand:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
But it shows < waiting for device >...
My Solution:
Change the VID to 0x18D1 and issue the command:
fastboot -i 0x18D1 boot twrp-blaze-2.0.0RC0.img
The < waiting for device > msg will still be showed. Don't worry. Reboot you KF. During the reboot period, the twrp-blaze-2.0.0RC0.img will flash to your KF. After the twrp installation process is completed, you ADB will BACK~~~
my problem is that it booted into fastboot, installed, and now simply sits at the firefirefire screen. I do not have fastboot, nor will it go into recovery when the power button is pressed....I am running the new combo install, following the instruction posted above.
Is there a driver change in FIREFIREFIRE? Do we need to add it to the driver settings?
HELP!
pyrostic said:
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
Click to expand...
Click to collapse
i downloaded it about 2 hours ago (dunno what 9:30 am is for you.. its 8:51 for me right now so... yea) and it didn't cause any problems that I can notice. if I did flash the newer version what problems could I expect to see? fastboot works, firefirefire works, and adb works.
if it matters any I'm running CM7 not stock rom. Maybe that's why I haven't been having these issues.
MayfairDROID said:
my problem is that it booted into fastboot, installed, and now simply sits at the firefirefire screen. I do not have fastboot, nor will it go into recovery when the power button is pressed....I am running the new combo install, following the instruction posted above.
Is there a driver change in FIREFIREFIRE? Do we need to add it to the driver settings?
HELP!
Click to expand...
Click to collapse
This post saved my kindle when that happened to me
What's the advantage of using this one over the old one? Old one works fine for me.
Ok I've tried everything to get out of the yellow triangle screen and it won't budge lol.. O If I just reboot it just goes back to the same screen and with the fastboot commands it just stays on 'waiting for device'.
Edit: Trying solution in link by brian112.. annnnd it worked (but not before adding the 18D1 line to the .inf file and reinstalling the kindle drivers through Device Manager).
pyrostic said:
The new file was uploaded around 9:30am this morning. Anything from before then will not harm you using the DD method.
Click to expand...
Click to collapse
Now I'm totally confused. I dled it after 10. It worked just fine, I rebooted multiple times into it, did a backup and everything. Now I just rebooted, and I'm stuck at the FIREFIREFIRE screen, and can't see the device in adb. Windows won't even recognize the driver.
[FIXED] brian112358's post above fixed the problem.
Thanks..that worked
Now next time i need to get into the TWRP 2.0, I just hit the power button during reboot correct?
Thanks again!
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
ags29 said:
Ok I've tried everything to get out of the yellow triangle screen and it won't budge lol.. O
If I just reboot it just goes back to the same screen and with the fastboot commands it just stays on 'waiting for device'.
Edit: Trying solution in link by brian112..
Click to expand...
Click to collapse
Works like a champ...give it a shot
what is the 18D1 line? I'm trying sl0ttedpig's fix but it's not working, driver wont install
ckong1 said:
what is the 18D1 line? I'm trying sl0ttedpig's fix but it's not working, driver wont install
Click to expand...
Click to collapse
My fix unfortunately doesn't fix everything! There may some extra steps depending on what state you are in and how you got there. Did the device driver install, and can you see it listed in Device Manager as "Android Phone" > "Android Composite ADB Interface"? That is the most important step for this to work for you.
If you can see that try just doing the following:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
i can't seem to get driver to install, kindle comes up as unknown device
ckong1 said:
i can't seem to get driver to install, kindle comes up as unknown device
Click to expand...
Click to collapse
So what happens if you follow the same instructions. I just updated my OP to include it saying either kindle or unknown, as it could work in either state (as posted by other people)
"In device manager, you'll see a device just called "kindle" or "unknown" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone)."
Click to expand...
Click to collapse
when i select "Let me pick from a list..." "Android Phone" is not an option, only "Unknown Devices" is shown. I try clicking that and i get:
windows has stopped this devices because it has reported problems. (Code 43)
Tried updating vendor list and adding 18d1 to winusb, still cannot install driver
Update:
After restarting the kindle and connecting it, it comes up as "kindle" in devices manager. driver will install but it still is not recognized by adb...
I'm stuck on the Kindle File logo boot screen.
I used this client to attempt to root my Kindle. I am rather inexperienced, and tried to apply a permanent root with superuser before installing a custom bootloader. In the process, i think it tried to install FFF, but would take an unusually long time to download and install it. So naturally, as any frustrated noob would do, i tried to X out of the window and unplug my Kindle. Bad idea. Turned it on, and it was stuck on the boot screen.
I've tried using a MOTO factory cable to start it in fastboot, but it would not work. There is a sticky at the top of this section that has instructions on how to unroot it, but the link to download important files just leads to some internet propaganda thing multiupload is hosting or something; I can not download the files.
SOLUTION:
shift +right click on Kindle Fire Utilities tools folder, select open command window here. power off your device leave it unplugged, type "fastboot -i 0x1949 getvar product" (no quotations). when it says waiting for device, plug it in it will power on in the terminal. if you get a response "product: kindle" type "fastboot -i 0x1949 oem idme bootmode 4000", hit enter then type "fastboot -i 0x1949 reboot" it should then boot normal use a standard cable for this, not your moto factory cable
USB_boot with pokey9000's firekit
64_hit_combo said:
I'm stuck on the Kindle File logo boot screen.
I used this client to attempt to root my Kindle. I am rather inexperienced, and tried to apply a permanent root with superuser before installing a custom bootloader. In the process, i think it tried to install FFF, but would take an unusually long time to download and install it. So naturally, as any frustrated noob would do, i tried to X out of the window and unplug my Kindle. Bad idea. Turned it on, and it was stuck on the boot screen.
I've tried using a MOTO factory cable to start it in fastboot, but it would not work. There is a sticky at the top of this section that has instructions on how to unroot it, but the link to download important files just leads to some internet propaganda thing multiupload is hosting or something; I can not download the files.
Click to expand...
Click to collapse
Sounds like your booting to fastboot mode you need to download the drivers so you can set your bootmode back to system
Sent from my Galaxy Nexus using xda premium
Your KF is OK and you need to change the boot mode to normal by following the below commands
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Your KF is OK and you need to change the boot mode to normal by following the below commands
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Okay, I'm assuming i can do this through cmd.exe, but what commands do i need to type in to get to the point where i can type these in?
I've fixed it. Thanks to someone over in the Q&A section.
Turns out i was stuck in fastboot.
For anyone who discovers this thread in the future, here was the solution:
shift +right click on kfu tools folder, select open command window here. power off your device leave it unplugged, type "fastboot -i 0x1949 getvar product" (no quotations). when it says waiting for device, plug it in it will power on in the terminal. if you get a response "product: kindle" type "fastboot -i 0x1949 oem idme bootmode 4000", hit enter then type "fastboot -i 0x1949 reboot" it should then boot normal use a standard cable for this, not your moto factory cable
This worked for me, thank you very much.
I have this same problem, but I cannot get my computer to recognize that the Kindle Fire is plugged in. I have tried installing the KFU driver but that doesn't seemed to have worked.
Try the iso I made post 7 http://forum.xda-developers.com/showthread.php?t=1413358 or just run your own http://forum.xda-developers.com/showthread.php?t=1850038
in kfu imstaalled fff,but kfu error bootloaderis stuck
This should work:
If you have fff installed:
Copy the tools folder from KFU to your local disk.
Now power off your Kindle Fire all the way.(all doing)
Then open command prompt and type:
cd c:\tools
fastboot
fastboot getvar store
(now you should see <waiting for device>)
Now power on your Kindle. Now in cmd it should say finished and the time it took.(wating for device..... naver finishe)
Now copy TWRP to your local disk
Then type:
fastboot flash recovery c:\openrecovery-twrp-blaze-2.2.0.img(openrecovery-twrp-blaze certainly in to tool,)
fastboot oem idme bootmode 4000
fastboot reboot
Now as it boots up use your power button to boot into recovery and it should boot into TWRP.
naver ending wating for device~~~~~~~~~~~
cd c:\tools(recovery certainly into c
fastboot
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
(driver re-installing many times ,certainly driver install,well showing driver numbers)
don`t end ,naver ending~~~~~~~~~~wating for device
just uninstall fff commad is nothing??
I just wonder how many times you will rewrite the same post I have offered on several occasions to help assist you but the language barrier is so vast its terribly hard to understand what you need and how to properly assist you. there is no need to start over the same thread one is sufficiant. Also whatever you have done to your device is in no way shape or form the fault of xda or its members you have done everything of your own free will to your very own device
This problem is related to a 3.0 usb port anyone know how to get around that without the use of another computer?
but was rooted why now?I succeeded before why can I not now??please help with info:fingers-crossed:
I may have idea read pm
SOLVED
I was trying to root my kindle today and decided to use the kfu.
I installed the drivers etc and started the kfu
http ://i.imgur.com/qNQgD.png
This is what the screen looked like, so i pressed 1
and then i pressed 2
http ://i.imgur.com/aAHRM.png
and the window said sending something and the kindle rebooted.
but now its stuck at the kindlefire logo screen. and anything you do in the kfu says it cant find the device.
i tried to use the firekit hoping it would fix the issue with the normal_boot script but all it does is hang at "waiting for device"
I know i probably did something really stupid, but if anyone could help me fix this i would be very grateful.
Josepho1997 said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
i tried :
Getting out of fastboot mode
To get out of fastboot mode, make sure the bootmode is set to something other than 4002 and reboot the device. The examples below will set the bootmode to normal and reboot the device.
With the stock bootloader...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
but adb and fastboot don't recognize that a device is plugged in, in device manager it shows as Android Phone, Android ADB Interface
Hardware ids show
USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
i have no firefirefire, or twrp and am on unrooted stock 6.3 if that helps.
Disconnect the KF from the computer
Make sure the KF is off by pressing and holding the power button for around 20 seconds
Issue the first fastboot command and it will indicate that it's <waiting for device>
Connect the KF to the computer and it will turn on automatically
The first fastboot command should get sent to the device as it goes into fastboot mode
Issue the second fastboot command to reboot
rsuaomi Fasciculi
kinfauns said:
Disconnect the KF from the computer
Make sure the KF is off by pressing and holding the power button for around 20 seconds
Issue the first fastboot command and it will indicate that it's <waiting for device>
Connect the KF to the computer and it will turn on automatically
The first fastboot command should get sent to the device as it goes into fastboot mode
Issue the second fastboot command to reboot
Click to expand...
Click to collapse
when i use the 1st command this is what happens:
http ://i.imgur.com/h1TOg.png
Bleedslow said:
when i use the 1st command this is what happens:
http ://i.imgur.com/h1TOg.png
Click to expand...
Click to collapse
The fastboot executable you are using does not recognize the "-i" switch... notice it's not listed under options.
Download KFU and use the fastboot in that distribution.
kinfauns said:
The fastboot executable you are using does not recognize the "-i" switch... notice it's not listed under options.
Download KFU and use the fastboot in that distribution.
Click to expand...
Click to collapse
it works! ITS ALIVE! muahaha.
thank you so much!
Ok, so I have very eagerly jumped on and tried to root my Kindle Fire. I read a few things, thought "This is easy and didn't read everything (shocker) and now am looking at a white / orange kindle fire logo and "unknown device" in device manager
I have uninstalled and reinstalled the drivers provided by the kfu
I have tried the unbrick kit
I have downloaded the soupkit but gave up cuz my experience with Linux is celebrating that I can SPELL U-b-u-n-t-u right.
At this point, I realized I am jumping the gun and need to focus on drivers.
I have read that I need to know 'where' it's broken (huh?) in the bootloader or boot process.
I have also read I need to run adb or kfu or skd or ffff or twrp or my kf will remain f.u.b.a.r.
I have read http://forum.xda-developers.com/showthread.php?t=1644970
http://forum.xda-developers.com/showpost.php?p=23747567&postcount=1
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
& http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
and dunno where I got lost.
Please help! Thanks in advance!
Progress!!!
ok so I got drivers installed as I now have an "android phone --> Android ADB interface" in the DM.
Id suggest flashing bootloader + recovery manually in fastboot
Something like:
fastboot -i 0x1949 flash recovery "/home/mike/twrp.img"
fastboot -i 0x1949 flash bootloader " /home/mike/fff.bin"
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 rebootot
Alright, if you have the drivers working you should be able to root and manage everything. I wrote a detailed guide on getting it working. Have you attempted to root it yet?
OH NOES! Your device manager says "Unknown Device"! From my experience, it is caused by a faulty bootloader flash, which is probably why you couldn't connect after using the SoupKit.
In Linux, with the device plugged in and powered up, enter the following command...
Code:
lsusb -v
...and print the results here. Also, it is very important to know what bootmode you are in. The easiest way to tell is by looking at the boot screen at startup. kinfauns' fastboot guide will give you an idea of what you should look for.
http://forum.xda-developers.com/showpost.php?p=26435498
powerpoint45 said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 rebootot
Click to expand...
Click to collapse
worked and was able to run the kfu to root the device and install TWRP and FFFF and I think that's it.
Now, I see the TWRP screen can't do anything from there. I tried mounting USB Storage and doing an "adb push" and get " 'adb' is not a recognized as an internal or external command, operable program or batch file."
::edit:: figured the adb issue. now getting 'device not found' when trying to push a ROM
Still confused and thinking maybe it's not too late to turn back.