Related
I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery
osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery
qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works
b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.
would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry
I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.
You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.
@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
When it says waiting for device, what happens when you unplug and plug in the device?
Hello people!
I'm having a hard time here.
I've rooted my device, and instaled a recovery method (not the TWRP, a red letter one), wiped cache and dalvik, flashed jandycane room and now i'm stuck on loop triangle boot.
In KFU my device are online and in normal boot (4000), but any options seems to work. He don't appear o pc and i'm already removed a re installed the drivers.
PS: I don't flashed GApps.
I tryied to enter in recovery mode but I get this:
I'm trying to but, but when I try to enter in recovery mode, i get this:
The system cannot find the drive specified.
Failed to Copy 'files\rcmode' to 'data/local/rcmode' : permission denied
unable do chmode /data/local/rcmode: no such file or directory
/system/bin/sh: data/local/rcmode: not found
I'm lost here, please help!
Install TWRP
soupmagnet said:
Install TWRP
Click to expand...
Click to collapse
There is another way to install without thr KFU? In KFU nothings happens too, stay trying to switch to fastboot and stuck in that.
Reinaque said:
There is another way to install without thr KFU? In KFU nothings happens too, stay trying to switch to fastboot and stuck in that.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1638452
Sent from my Nexus 7 using Tapatalk 2
The TWRP.img file that comes with KFU is not TWRP. If I had to guess, it probably uses wget to download the file, for legal reasons? Maybe? Who knows? Replacing it with one downloaded from the TWRP website would probably be the easiest route.
soupmagnet said:
The TWRP.img file that comes with KFU is not TWRP. If I had to guess, it probably uses wget to download the file, for legal reasons? Maybe? Who knows? Replacing it with one downloaded from the TWRP website would probably be the easiest route.
Click to expand...
Click to collapse
I'm already tryied that, but when the KF try to switch to fastboot in order to install the TWRP, he stuck in there and nothing happens.
Reinaque said:
I'm already tryied that, but when the KF try to switch to fastboot in order to install the TWRP, he stuck in there and nothing happens.
Click to expand...
Click to collapse
You're going to have to clarify that a bit. Stuck where? The Kindle Fire screen? If so what does it look like?
The situation changes.
I dunno ecxactly i did, but my KF begins to stuck in the KF logo Screen, not anymore on loop triangles and windows begin to see my device.
So I tried the fastboot commands, but choose wrong:
fastboot -i 0x1949 oem idme bootmode 4000
and now my KF stuck in triangles loop again and the windows can't se him anyomre.
What does your Kindle Fire logo look like?
soupmagnet said:
What does your Kindle Fire logo look like?
Click to expand...
Click to collapse
Kindle Fire wrote on White and Orange.
But don't stuck there, after the logo disapear the triangles begin to turn in loop.
Try to pay attention. You are in normal bootmode, with a corrupt file system caused by CWM. When the device is "stuck" at the boot logo it is in fastboot. Fastboot mode is needed to install TWRP and a host of other activities. All of this you would understand if you had read the Kindle Fire for Beginners guide stickied at the top of the Kindle Fire General forum. You would have been directed to that page if you had read the sticky at the top of this forum, labeled "Before Asking For Troubleshooting Help...". With the exception of CWM acting up (arguably), these are the most basic of Kindle Fire problems and it is a waste of time for people to have to go over them constantly, and unecessarily.
soupmagnet said:
Try to pay attention. You are in normal bootmode, with a corrupt file system caused by CWM. When the device is "stuck" at the boot logo it is in fastboot. Fastboot mode is needed to install TWRP and a host of other activities. All of this you would understand if you had read the Kindle Fire for Beginners guide stickied at the top of the Kindle Fire General forum. You would have been directed to that page if you had read the sticky at the top of this forum, labeled "Before Asking For Troubleshooting Help...". With the exception of CWM acting up (arguably), these are the most basic of Kindle Fire problems and it is a waste of time for people to have to go over them constantly, and unecessarily.
Click to expand...
Click to collapse
I undestand that, but i'm trying to switch to fastboot without sucesses. Tryied everething i've read here, but i'm stuck on that.
Use CWM to reboot to fastboot
soupmagnet said:
Use CWM to reboot to fastboot
Click to expand...
Click to collapse
When I try to install the CWR in KFU, I got this:
When I try to instal the FF in KFU, I got this:
***********************************************
* FireFireFire Installer *
***********************************************
fff.bin is missing.
So we will download it for you!
wget: missing URL
Usage: wget [OPTION]... ...
Try `wget --help' for more opt...ad 'recovery\fff.bin'
< waiting for device >
Reinaque said:
I've rooted my device, and instaled a recovery method (not the TWRP, a red letter one),
Click to expand...
Click to collapse
The "red letter one" is CWM. You already have it installed. (I shouldn't have assumed you had access to it)
Reinaque said:
So I tried the fastboot commands, but choose wrong:
fastboot -i 0x1949 oem idme bootmode 4000
Click to expand...
Click to collapse
As I said before, that put you in normal bootmode. And, as it is said in the KFFB, you can only issue adb commands in normal mode. Issue the adb command to change the bootmode to fastboot (4002) or recovery (5001).
[Edit:]Use your command line to change the bootmode. If your computer won't detect the device for adb, there is a problem with the device drivers (also covered in the KFFB) and need to be reinstalled.
soupmagnet said:
The "red letter one" is CWM. You already have it installed. (I shouldn't have assumed you had access to it)
As I said before, that put you in normal bootmode. And, as it is said in the KFFB, you can only issue adb commands in normal mode. Issue the adb command to change the bootmode to fastboot (4002) or recovery (5001).
[Edit:]Use your command line to change the bootmode. If your computer won't detect the device for adb, there is a problem with the device drivers (also covered in the KFFB) and need to be reinstalled.
Click to expand...
Click to collapse
Yeah, I undestand that. The problem is that I don't know what I exactly donne to KF acept my commands. The only thing i've donne for sure is that I change the USB port, but I tryed again with no sucess.
I am stuck also at the Boot Triangles in loop - I am having the exact same problems as you are Reinaque, so just know your not the only one.
I have tried all of the different tools, but I am still stuck in the CM10 boot logo. Also I am stuck on "Waiting for device". My kindle is recognized by my computer on 4000 boot mode through KFU.... It won't allow me to write any commands through ADB... Stuck with you!
EDIT
It will not for the life of it let me get into fastboot!
Well, I don't know what to do anymore.
I tryed with another PC, installed the correct drivers and try almost every fastboot command with no sucess, the KF still don't aceppt the commands.
I will try something with firekit.
Damm, I really think that I lost my new KF =[
Reinaque said:
Well, I don't know what to do anymore.
I tryed with another PC, installed the correct drivers and try almost every fastboot command with no sucess, the KF still don't aceppt the commands.
I will try something with firekit.
Damm, I really think that I lost my new KF =[
Click to expand...
Click to collapse
You didn't lose your Kindle. Check your messages.
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...
I read the guide and have been browsing the forums for similar situations.
First of all, many months ago I tried to root my KF with something named "doomlord"? I basically googled how to root, picked one, went at it. It ran fine, though I don't recall trying to do anything with the root. Most recently every time I powered it on, I was in the CWMR menu. I tried to install the latest kindle update from amazon (changed it to .zip, placed it in the folder, tried to install from cwmr menu), to get it back to stock. Didn't work, and the only way I was able to use my kindle was wiping everything and rebooting. I became frustrated and started to try anything I hadn't, I clicked fastboot mode. Now it's been stuck at the yellow triangle, does nothing when power is pressed, isn't recognized by my mac.
Many users had my similar situation but I truly am a newbie and went at this with no knowledge, though I do know some terms through the guide. It seems I'm stuck in a bootloop, and my kindle isn't truly broken for good.
What I want to know, in basic terms:
What do I need to download?
To send commands.. do I use terminal? Seems like I need to get 'fastboot' and 'adb'
I've also seen references to getting kindle fire utility- can I use this even though I used some random doomlord program and it's using CWMR?
How to 'flash' something?
Simple, step by step instructions would be SO APPRECIATED! I apologize for having a question everyone else has asked, but I feel so frustrated at this point.
Anybody?
So far, I have downloaded KFU, adb, fastboot, and FFF 1.2.
I've tried many commands to see if my kindle is in fastboot, it does not seem to be. All commands come back with "-bash: fastboot: command not found". I also am going into the directory of "android" where I put adb and fastboot. I think that is correct.
Not sure what to do with KFU, or FFF that I've downloaded.
Should I wait for the battery to drain? Though I don't think that will fix the problem at all.
Kindle still not being recognized by my mac.
At this point I will just pay somebody to help me successfully fix this or send it out. But if it's as easy as the solutions make it seem, I'd love to just do it myself. I think I'm just confused about what exact steps I need to make, whether that is flashing FFF or TWRP?
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
soupmagnet said:
Whatever you do, don't let the battery drain.
Make sure you have your driver installed and configured correctly:
Code:
cat ~/.android/adb_usb.ini
The only acceptable output is "0x1949".
Next, try to take advantage of the temporary fastboot mode that comes with FireFireFire (yellow triangle).
Hold the power button to shut the device down and enter the following:
Code:
fastboot getvar product
Restart the KF when you see "waiting for device".
Give it a second to boot and you should get an output of "kindle" in the terminal. If you do, repeat the previous step with the following commands:
Code:
fastboot oem idme bootmode 5001
fastboot reboot
That should boot you into recovery again. (but you're not quite finished yet, we'll see if you can get this far first)
If that doesn't work, you should get a Linux LiveUSB (if you have a PC to use) or a VM (only Parallels will work with fastboot) to run Linux, and install and run Firekit. Depending on your Mac, it is possible, albeit very tricky, to get it to boot to a LiveUSB...but I wouldn't count on it. You might need to use the shorting trick to temporarily put the device in USBboot so Firekit can install a new bootloader (see Firekit thread).
Click to expand...
Click to collapse
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
2hellwu said:
Thanks so much for trying to help out. No dice, though. Your directions seem fairly simple and straightforward. I'll tell you what I did step by step-
First I connected KF to my mac, the yellow triangle appears. I go into the directory where adb is. I'm not sure what you meant by which drivers should be installed properly, but I put in the following into terminal:
Code:
cat ~/.android/adb_usb.ini
As a result I got:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
This seems about right. I shut it down, and tried to input "fastboot getvar product". That is when I get the "-bash: fastboot: command not found". I feel really dumb right now. It really seems so simple but I'm just not getting it. I added a screenshot if that would give you any clue as to why even the first step isn't working. Thank you
Click to expand...
Click to collapse
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
soupmagnet said:
Put the fastboot binary in your home folder and enter 'cd' (without quotes). Then run the commands.
Click to expand...
Click to collapse
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
2hellwu said:
I am probably making this harder than it really is. Alright, both adb and fastboot now exist inside my home folder "/user/Lianna/"
Started with kindle on and plugged in, entered "cd" into terminal. Didn't do anything. Continued with "cat ~/.android/adb_usb.ini" got same response as before. Other commands were unrecognized/"not found".
Click to expand...
Click to collapse
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
soupmagnet said:
Ok try this:
Instead of typing the word "fastboot" into the terminal, drag fastboot into the terminal window and then type in the rest of the command.
[EDIT:] I almost forgot...you're not using fastboot from KFU are you? You need fastboot for Mac.
Click to expand...
Click to collapse
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
2hellwu said:
Again, command not found. Does the first step indicate that my fastboot is indeed functional?
Click to expand...
Click to collapse
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
soupmagnet said:
Are you using the fastboot.exe from the KFU folder or a Mac specific fastboot binary?
Click to expand...
Click to collapse
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
2hellwu said:
I used the two individual downloads for adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=1917237
I do have KFU in my downloads but I'm not using the fastboot.exe that comes with it. I am using the ones downloaded from above, which seems to be a "unix executable file". I'll show what happens when I open it.
Click to expand...
Click to collapse
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
soupmagnet said:
Ok let's simplify this. Put fastboot on your desktop and enter the following:
Code:
~/Desktop/fastboot getvar product
Click to expand...
Click to collapse
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
2hellwu said:
That did get me the <waiting for device> product:kindle! I then restarted and tried to input
Code:
fastboot oem idme bootmode 5001
fastboot reboot
which again, got "-bash: fastboot: command not found"
Click to expand...
Click to collapse
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
soupmagnet said:
LOL, pay attention now...
Code:
~/Desktop/fastboot oem idme bootmode 5001
~/Desktop/fastboot reboot
OR
Code:
cd ~/Desktop
fastboot oem idme bootmode 5001
fastboot reboot
...you follow?
Click to expand...
Click to collapse
ah yes. so, that worked. now at:
Code:
< waiting for device >
~/Desktop/fastboot reboot
at this point KF is still off. power on or no?
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
2hellwu said:
Ok, KF is on and back in recovery mode. "CWM-based recovery v5.0.2.7" I have the menu of reboot, install zip from sdcard, etc
Click to expand...
Click to collapse
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
soupmagnet said:
Okay, first you need to find and download the ROM of your choice. You'll also need to download recovery flashable versions of TWRP and FFF, found HERE and HERE.
With those three things downloaded, boot into recovery and find the "Mount" or "Mount to USB" option. I haven't used CWM in quite a while so I couldn't tell you exactly how to get to it. Look around and you will find it. What that does is mounts your sdcard to USB as if it were a USB flash drive. Do that and transfer the three files you downloaded earlier to your sdcard.
With them on your sdcard, install both FFF and TWRP. CWM is way outdated and will not work anymore...Use TWRP instead. You can update to COTR later if you choose as it has a nearly identical look and feel as CWM. The new version of FFF will give you an option at the boot logo to change bootmodes on the fly (makes entering recovery much easier).
With FFF and TWRP installed reboot the device. As the device is booting you will see the Kindle Fire logo in blue instead of orange. When you see it, hold the power button until the boot options appear at the bottom of the screen. Select Recovery.
When TWRP boots up, select "Wipe" then wipe system and factory reset (this step is very important).
Afterwards, select Install, navigate to your sdcard and select the ROM you downloaded then swipe the arrow at the bottom. Select reboot system and you should be all set.
One more thing to note: If the device keeps booting into recovery after subsequent reboots, select "reset boot mode" in the FFF boot options.
Good luck.
Click to expand...
Click to collapse
Before I start this- I should have clarified my main goal is to get my kindle back to stock. I don't have a need for anything extra, I really just use it to read books. From other guides, maybe it seems that my next steps should be to download the kindle update from amazon, and flash that?
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
soupmagnet said:
In that case, download the update from Amazon, change the ".bin" to ".zip" and use that in place of your ROM. All other instructions will be the same...especially when it comes to wiping
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
2hellwu said:
Ok I feel stupid, but how do I find where the sdcard folder is? Is it simply just dragging the update to "Kindle" or should I be putting it into a specific folder
Click to expand...
Click to collapse
Yes, the mounted volume "Kindle" is your sdcard. Just drag and drop everything into that folder. Be sure to eject the volume from your computer (right-click on it and select eject) before you unmount it in TWRP.
"That's a special kind of stupid. The kind that makes me laugh."
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.