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...
okay, this is to try to simplify the install for most windows users...
for starters get over to the teamwin website and download the official rc0 which comes with firefirefire bootloader so you can easily get into recovery with our 1 power button.
after youve downloaded the recovery file, put this file in the directory that your adb and fastboot is in, connect your device and open a cmd window
cd to the directory adb and fastboot is in, for me i typed
cd c:\sdk_tools (enter)
c:\sdk_tools becomes the directory, so now
adb shell (enter)
su (enter)
idme bootmode 4002 (enter)
so now your bootmode is set. now type in:
exit (enter)
exit (enter)
adb reboot (enter)
it should reboot to the splash screen of kindle fire in fastboot mode, now type in
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img (enter)
it should install, show team wins image, then reboot to the yellow triangle of firefirefire...
this is okay. from here, on windows, my computer did NOT read the device anymore and it was stuck in fastboot and wouldn't take commands. this issue is related to the drivers for some reason... what i did was reboot my pc, reconnected my device and it came up as a unknown device. this is okay!
go to devices and right click the one with an xclimation mark and click update drivers. choose manually and then choose out of available drivers. you need to select android phone or something android related depending on what drivers you had installed previously. i chose my asus android device since thats what i had when i first got adb working. after u choose android device choose adb generic and it should install fine.
after this get back in ur cmd prompt, cd to the proper directory and type this in
fastboot devices (enter)
u should get a listed device.
from here you can then change bootmode to properly reboot ur device
fastboot oem idme bootmode 4000 (enter)
fastboot reboot (enter)...
should be done! enjoy!
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
krelvinaz said:
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
Click to expand...
Click to collapse
when using apps to boot to recovery, can u get out of recovery without issue? someone said it gets stuck in the wrong bootmode?
Sent from my HTC Glacier using xda premium
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
krelvinaz said:
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
Click to expand...
Click to collapse
Yep, if you do everything right and have FFF and TWRP installed correctly, you should be able to flip between ROMS without too much trouble, and without have to use fastboot again.
Hmm...while attempting to reinstall the drivers for the Fire, I'm at a road block.
I see the kindle in device manager, and am informed that it's not installed correctly, but while manually choosing the drivers I'm greeted with the following (attached).
This is after choosing Android Phone from the available drivers.
Any ideas, guys?
reboot ur device and reconnect to ur PC.
Sent from my HTC Glacier using xda premium
Bricked?
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
leglerreddin said:
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
Click to expand...
Click to collapse
when the device is in fastboot it is unrecognizable with adb, just enter the fastboot commands and you'll be fine.
smirkis said:
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I wish that was the case, i have tried a million different fastboot and adb commands, ive rebooted, used another os, the drivers are installed as an android composite adb interfaced, its still not registering as an adb or fastboot device.
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
CrackMonkey91 said:
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
Click to expand...
Click to collapse
I still had issues installing drivers after it booted to the yellow fire triangle (on Win7 x64 - even after adding the other device id to both x86 and x64 sections of the inf and ini of the drivers). Rebooting my computer with the Kindle plugged in caused the Kindle to reboot normally after which I used a terminal to set the boot mode to 4000:
Steps I took after doing step 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' (enter):
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
- Open the terminal app. (I used Terminal Emulator)
- Type 'su', press enter. (Superuser will pop-up - select allow)
- Type 'idme bootmode 4000', press enter.
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
uunnzz said:
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
Click to expand...
Click to collapse
this my friend, is interesting.
First off, thanks to everyone on here who's posted numerous help guides that have helped me in the past. I've rooted several phones in the past and figuered I'd try to root and install Jelly Bean on a Kindle Fire I won at a work event (woohoo!).
The problem right now is the kindle is stuck in fastboot (no root, twrp installed) it boot into the non-animated white and orange "kindle fire" logo screen and stays there.
What I did to put it there:
On a Windows 7 machine, I used KFU 0.96. After reading instructions, I installed TWRP.
Since then, it is not repsonding to adb commands. It will mount the drive to the computer, and the drivers show it's using the correct one from Google Composite device.
After researching, I found someone who mentioned that after several restarts, and smashing "normal boot" commands thru adb while the kindle was starting up (and before it went unresponsive) he was able to move along. When I did this (with KFU), Kindle went into TWRP. From there I followed instructions on flashing pre-rooted 6.2.2 (as the guide indicated, doing wipes) but the flash always failed.
Assuming something wasn't working with Windows, I've gone home to my macbook running Ubuntu 12.04, and while installing SDK from Google, I can not figure out how to get the google sdk running. I followed this guide http://forum.xda-developers.com/showthread.php?t=1550414 but I can't get to step 5, I cannot get the Android SDK Manager to run!!
I have access to dozens of Windows computers, I'm fine with going back to them, but everything I've read makes me think I've got a better shot with Linux due to driver problems on windows.
Also, when I had TWRP loaded on the Kindle, and connected it to KFU 0.96 it said my boot mode was 0x5003.
fastboot commands will not execute. I'm sending them like this:
(Devices list)
[email protected]:~/Android/KR$ ./adb-linux devices
List of devices attached
???????????? no permissions
fastboot:
[email protected]:~/Android/KR$ fastboot getvar product
fastboot: command not found
Someone had a similar problem here- http://forum.xda-developers.com/showthread.php?t=1765546 but I want to see if I should follow that thread or try something else instead, before I go making more changes.
Thanks for reading! Will gladly send pizza to someone who can help
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
veeman said:
I'm not an expert at fastboot and adb stuff but I can try to help.
As far as I know, the Kindle needs to be in fastboot mode for you to be able to use fastboot commands. The boot mode has to be 4002.
Are you still able to connect to your Kindle using KFU?
Click to expand...
Click to collapse
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Josepho1997 said:
Try uninstalling and reinstalling the drivers. If your in fastboot mode, adb wont work. After reinstalling the drivers, type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If the drivers installed correctly, these commands should work and get you out of fastboot(which it seems your stuck in)
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
drivers installed. command input. no response. Id like to install screenshots, but I'm new user.
hardware driver reads Google ADB interface 4.0.0
c:\KFU\tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
.....nothing?!
wheelzr said:
yes. but it also spits out "-exec '/system/bin/sh' failed: No such file or directory (2) -" when I send the command to reboot into fastboot 4002, the kindle then reboots, and has the white and orange "kindle fire" logo.
also: C:\KFU\tools>fastboot devices
returns blank, goes back to prompt. so I try
C:\KFU\tools>fastboot devices
< waiting for devices >
and does nothing
Where to now?
Click to expand...
Click to collapse
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
kinfauns said:
"-exec '/system/bin/sh' failed: No such file or directory (2) -" means your system software is broken, so it probably won't boot. In addition, either the "sh" binary doesn't exist there or the KF is not mounting the system partition to let you execute "sh" to run "adb shell" commands. To clarify, you need "/system/bin/sh" to run any "adb shell" commands. Because you don't have access to it, you cannot change the bootmode this way. There is no "command to reboot into fastboot 4002"... you have to set the bootmode to fastboot (4002) and reboot it. Because you cannot run "adb shell" commands, you cannot change the bootmode. Your next reboot just boots into whatever the bootmode happened to be at the time you tried (but failed) to change the bootmode. All of this is spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
It's very likely that you'll have to get a factory cable to force the device into fastboot mode... that is unless you want to open the back cover up and tinker with the motherboard.
Also, you have permission problems when you try to run adb. You either have to run adb as root, or use this guide...
http://forum.xda-developers.com/showthread.php?t=1475740
and set things up so a regular user won't need root privileges to access the USB ports.
Click to expand...
Click to collapse
So, witout popping the cover and screwing with the mobo this thing is bricked?
wheelzr said:
So, witout popping the cover and screwing with the mobo this thing is bricked?
Click to expand...
Click to collapse
</thread>
Just sold the kindle on craigslist for $40 as a bricked device.
wheelzr said:
Just sold the kindle on craigslist for $40 as a bricked device.
Click to expand...
Click to collapse
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
kinfauns said:
Oy vey... I'd give you $50 for the "brick" to be used to help others here.
Click to expand...
Click to collapse
for real, I probably would have paid $50-60 too, it should be an easy fix with a factory cable. (which I already have one of after I bricked my kindle once)
Also, as a side note - Amazon will replace it for $100 "not under warranty" because you bricked it through the tinkering process.
Actually, it turned out better than I could have planned. I told the company whom gifted to me t did not work, they sent a bike ,messenger to exchange it for me! Naturally the first thing I did with the new one was fire up kfu .96 and it worked perfectly this time. Stoked on this hashtaag jelly bean ROM. Hate the keyboard tho. And Google cards are fc'ng.
Love life.
Sent from my Amazon Kindle Fire using xda app-developers app
This is my gf's kindle fire and she wanted it rooted to have the google play store. This is completely untouched Kindle and on windows 7 pc. So I downloaded the KFU latest release 0.9.6 and proceeded w/ option 2 to install permanent root. Let it sit for about an hour with the please wait and waiting for device messages at the bottom of the screen. I wasnt sure how much longer this would be so i just let it sit. Couple minutes later my gf comes and let me know that she unplugged it accidentally while vacuuming. Im now stuck on the TWRP screen and will not reboot at all. If it try to reboot i get a message saying " E: System in not installed - preventing reboot! " which makes me think that the OS got wiped somehow. All I can do is let it run out of battery. Now in the KFU abd status: Offline and boot status: Unknown. Although that Windows will recognize the device as its showing up in device manager under Adroid Phone: Android ADB interface. What can I do?
not showing up.
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
soupmagnet said:
Letting your battery run out would be one of the worst things you can do. I don't know where people get the idea that running the battery out of a device is a miracle cure, but it's ridiculous.
First, use the "Mount" function that comes with TWRP and mount your sdcard. Choose a ROM and transfer it to your sdcard to be flashed in TWRP. Once you have a ROM installed, select Reboot > Reboot System.
If you want the stock based software, install MoDaCo. No need to root or install Google Play Store.
Click to expand...
Click to collapse
Mount function not working either. I hit the button and never shows up on my comp as a storage device.
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
soupmagnet said:
Yep, that's a problem. In order to fix it, you'll need the command line. To use the command line, you can either fix the Windows driver problem that is causing the "adb offline" error, which could be a very painful process, or set up a LiveUSB to run Linux (recommended).
Click to expand...
Click to collapse
Could I just remove and reinstall the driver? Weird thing is that its still showing up on the device manager Adroid ADB interface.
In a perfect world, yes, that would work every single time.
soupmagnet said:
In a perfect world, yes, that would work every single time.
Click to expand...
Click to collapse
Well i managed to get the driver working and got to flash the latest update from amazon on and renamed it update.zip to get it to flash. Now it seems like its in a bootloop just showing kindle fire in the orange letters. Connecting it to KFU it shows ADB status: online , but still showing bootstatus as unknown.
You need to fix your drivers again.
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
neemo6 said:
Now i cant get into anything other than the kindle fire screen. I just made a Factory cable but not sure as to what that is supposed to do as i dont notice anything different when i plug it in other than it powers up by itself instead of having to press the power button. I cant get into twrp anymore. Trying a few other things i keep getting a - exec '/system/bin/sh' failed: No such file or directory (2) error message.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1668159
kinfauns said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
Thanks kinfauns great info!
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
neemo6 said:
Well even though im in fastboot im still getting nowhere. Im trying to use this adb command
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
To try and flash twrp and get an error cannot load C:\kfu\software ' message.
Also when trying this command
adb shell su -c 'idme bootmode 4002'
I get device cannot be found message even though Device manager showing up w/ Android Phone ADB Interface
Click to expand...
Click to collapse
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
soupmagnet said:
You're in fastboot so adb commands won't work. You can only use fastboot commands in fastboot mode. As for installing TWRP, go to the TWRP website and download the actual TWRP.img file. The file that comes with KFU is nothing more than a broken link (2kb I think?) and it doesn't work. Put the file you downloaded into your KFU folder and rename it twrp.img, just to make things easier. Then "Shift" + "right-click" on the folder containing the newly downloaded twrp.img and select "Open command window here". In the window that opens up enter the following commands:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 oem idme bootmode 5001
then hold the power button until the device shuts off and start it up again. It will then boot into recovery.
Click to expand...
Click to collapse
Awesome thanks for the help Soupmangnet!! I got it in twrp recovery now. I would like to just have it back to stock at this point and have the latest update downloaded from amazon on the sd card. Im just worried that this will put me back into the same problem as before. Do need to download or fix something else?
Make sure you change the file's extension to .zip as before, and above all else, wipe System and "Factory Reset". Everything should go well for you.
You sir are awesome! Everything works great! Now to get play store.
You could have simply just flashed modaco instead of going through all he hassle of flashing update.zip and wiping out fff and twrp...
Hi All
I was in the process of rooting, installing TWRP, and eventually attempting to get to CM10.1. I was able to get the TWRP but now stuck and cannot proceed further. When my Kindle boots it comes up with the orange and then switches to the blue logo and does not proceed. I can only get it to jump into TWRP mode and will then pull up the cmd prompt from there to try and troubleshoot.
When I run adb devices it will state that daemon is not running and then start it on port 5037. It will also note the serial number as well as state 'recovery' rather than 'device'. I have attempted to return it to the factory boot but it will only say that it is waiting on the device without any change. I can get it into fastboot mode by starting the server.
How do I get out of recovery mode? I have tried many different ways without any luck. Please help.
Thanks
Matt
When I get into fastboot mode I attempt to enter fastboot oem idme bootmode 4000. However it will then state waiting on device. I am stuck.
Fastboot commands need to have "-i 0x1949", also you should be able to push a new ROM onto the kindle in twrp to flash using "adb push filename.zip /sdcard/filename.zip" and install from there, you either don't have an is right now or the kindle os isn't booting because its a newer version that detects twrp and doesn't let it boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for responding.
I am now attempting to use adb sideload to push the ROM but it isn't working. I start the sideload feature within TWRP and then code in cmd prompt. I am getting 'error: closed'. Maybe I have a driver error? I have Android Phone>Android ADB Device.
Don't bother with side load if it errors, just let twrp load and run the adb push command I mentioned above, it should put the zip onto your sdcard so u can flash it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
So I think I am on the right track for the sideload. Yet still stuck. I have adb sideload running in TWRP and when I put in adb devices in cmd prompt it now gives me the serial number and notes sideload. Trying to push the zip folder, cm-10.1-20130812-UNOFFICIAL-jem, to the device. I have tried to use the full path, C:/users/name/file/etc. followed by /sdcard/filename but still coming up short.
got it!!
Thank you!