Related
I have just bought Kindle. So i try to root and install TWRP recovery for my Kindle. After installing TWRP, because don't look Super User icon in Kindle; I took hard-reset my device in Settings. And Now My Kindle boot Logo Kinder Fire stuck on here.
What problem ???? Please help me....... i don't know i had just done nothing. Thanks guys !
I try to text in command dos: "add shell" but it show may Laptop Screen:
- exec '/system/bin/sh' failed: No such file or directory (2) -
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
I'm having this same problem. It's apparently stuck in fastboot. I can't even figure out how to type in adb commands or fastboot commands (meaning I could before and now when I tried it says command not found, but I didn't change anything. It won't recognize my device and when I try installing the android-winusb.inf it says it won't let me. I don't know what else to do. Any help would be appreciated. My Kindle is listed as unspecified device.
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Serinety said:
it sounds like you are stuck in fastboot.
when you plug in your kindle, does device manager see it? if so, can you tell me what it recognizes it as?
Click to expand...
Click to collapse
g1no23 said:
Had this issue last night when I tried to TWRP my friends Kindle Fire. Plugged it in and typed:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But Boot Status show: Unknow, so when i type this text comandos show: waiting device
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
lovejoy777 said:
turn off kindle then try running the command before pluging in kindle to usb then plug in kindle and press power button once.
edit: if that doesn't work try installing kindle fire unbrick utility its very simple to use and normally sorts most bootloops etc.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
thanks guy much. But i tried all, i used KFU to try installing Recovery ( CMW, or TWRP), try to plug in USB Kinlde, press power button, etc. But It'S seem not working, all show: " exec- system/bin/sh failed ; not such file orr folder "
i also use tool KF Unbrick on XDA, but it's too. Reply show: " -exec- "system/bin/sh"...
Can U know that what problem in "system/bin/sh" of Kindle Fire ???????
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
works perfectly for me too! awesome!
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
feistygoat10 said:
This worked for me, but you have to be able to boot to TWRP:
http://rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
Click to expand...
Click to collapse
thanks but my kindle don't have TWPR recovery after i've just flashing office room 6.2.1 from Amazon. Now it stuck in my logo Kindle
tunglx1988 said:
when I plug in my Kindle, KFU Show:
- ADB: Online
- Boot Status: Unknow
Now I try to install CMW recovery or TWRP, but I can't do this . All show: - exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Serinety said:
You are only soft bricked. When I asked what happens when u plugged it in, I mean in device manager not in the kfu. Device manager needs to ee the the kindle as adb composite device. If it does not, then you need to get the right driver.
You are stuck in fastboot. You simply need to issue the right reboot code and you will be fine
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
thanks for repl. But My Kindle Logo is Stuck in here. open KFU then show : Boolloader: UnKnow. So i don't know it bootmod ??? ( recovery, Normal, or fastboot).
b63 said:
if you get this error message to the command "adb shell" then the system shell is messed up
sorry - but you'r only way to recover is a factory cable
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
he is absolutely right, this happened to me and nothing would work until I got a factory cable
This is a typical problem with KFU.
You need to go to your device manager and uninstall both the adb and android drivers then reinstall them manually. Sometimes it helps to restart your computer and Kindle afterwards. Make sure your device manager says both "Android Phone" and "Android ADB Interface" NOT "Other Device" and "Kindle".
When you are stuck at the boot screen it means you are in fastboot mode. In fastboot mode your device will only recognize fastboot commands. If your device doesn't recognize fastboot commands (KFU uses fastboot commands to change boot modes), 99 times out of 100, it's a driver issue.
A factory programming cable, while nice to have, is not usually necessary. A factory programming cable does two things. It provides power directly to the device instead of the battery AND forces the device into fastboot mode (stuck at boot logo). Since most of you with this problem are ALREADY in fastboot mode, a factory cable would be pointless.
Make sure you are 100% certain that you have the correct drivers installed and configured properly and then use the command prompt to change your bootmode to 4000.
In command prompt, navigate to the folder that contains fastboot.exe and enter the following commands...
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Sent from my Amazon Kindle Fire using xda premium
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
soupmagnet said:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
(or hold power button for 30 seconds)
Click to expand...
Click to collapse
jingcleovil said:
This samething happen to me.
I try this command but command prompt says. <wating for the device> and nothing happen
Click to expand...
Click to collapse
i have the same problem as you it fills good to not be the only one
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've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Background/How I 'Bricked' It: I have a Kindle Fire 2 and was able to successfully unroot/flash Cyanogenmod 10 onto it. Worked perfectly for about 6 months, when I decided that it would be a good idea to flash back to stock so that I could give it to a relative. I have TWRP 2.3.3.0, so I used a guide on xda to do the following:
I used a guide from xda and followed these instructions
-Download latest KF2 stock software from amazon. Re-name the file to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
Unfortunately, wiping the system seems to have wiped the CM10 OS (ROM) that I had installed, and there was a failure in installing the amazon stock:
Installing '/sdcard/download/update.zip...
assert failed: is_substring ("Otter2 , file_getstring("/proc/product_name"))
E: Error in /sdcard/download/update.zip
(Status 7)
Error flashing zip '/sdcard/download/update.zip'
Updating partition details...
Trying to reboot the system from TWRP results in a message that states: "No OS installed! Are you sure you wish to reboot?"
Investigating using ADB: So it looks like I have no OS on the Kindle Fire 2. This seems to be a problem because without an OS, I am unable to use adb (from what I've read, no OS = no way to accept/authenticate the computer RSA fingerprint to whitelist the kindle and allow adb to function). Trying to use KFU, KFFirstAide, or the Kindle UnBrick Utility results in Error: Device offline or Error: Device not found types of messages (I am assuming due to the fact that I can't "turn" adb on by accepting the RSA fingerprint prompt)
What does Device Manager tell me? My computer can 'see' the Kindle Fire in device manager [as I stated earlier: My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles] but going to My Computer and looking under mass storage devices, the computer doesn't seem to recognize the device as a USB storage device, which is a problem because I can't drag/drop or push/pull files to the SD card so I can't try to flash anything *other* than the original file that failed.
Fastboot Mode...? From what I can tell (http://forum.xda-developers.com/showthread.php?t=1668159), my device is in fastboot mode. My Kindle screen hangs on the blue/white Kindle Fire logo screen, which from what I understand is hashcode's bootloader/fastboot screen. However, when I look at the Hardware IDs in the device manager, it tells me that my hardware IDs are:
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
So...my kindle seems to be stuck on the blue/white fastboot screen, but register on my computer as the stock kindle fastboot? I'm not really sure what's going on there, and couldn't find too many people with the same discrepancy that I have...
I tried plugging in my cord (making sure to use a USB 2.0 port), going into Command Prompt and using some fastboot commands. (ie: fastboot flash bootloader \path\update.zip) but all I get is a <waiting for device> for a LONG time. As in, a few hours. Some basic googling/investigation seems to indicate that I don't have fastboot drivers installed, OR that I wasn't running fastboot in an 'elevated mode' but I haven't been able to find too many details about how to fix those, IF that is the problem.
TWRP 2.3.3.0: I can get into TWRP recovery just fine, although I can't seem to figure out how to get files onto my device. So I've tried re-installing the original update.zip file that failed the first time several times, with no success. trying to 'Mount' the device doesn't seem to do anything (at least, my computer doesn't see the device as USB storage regardless of whether it's mounted or not) I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the adb sideload <filename> command just gets me an Error: Device not Found message. I thought maybe I could try Advanced --> Terminal Command, but have no idea how to do that or what it does, and most sites are very vague about the step-by-step details, so I didn't really touch it.
Not sure if this is relevant or not, but when my KF2 is plugged into (attached) to my computer with the cord and is in TWRP, device manager shows the device under 'Other Devices' --> Amazon Kindle Fire2, and there is a yellow triangle on it. Not sure why...going back to 'fastboot' mode gets rid of yellow triangles and is recognized as a Kindle Fire again.
At this point - I'm pretty much stumped and have (hopefully) demonstrated that I've done my best to do my own research/read through threads/done due diligence. Is there anyone out there that might have any suggestions? Or do I now have a very large paperweight?
ANY input/suggestions/encouragement is welcome! I absolutely and sincerely appreciate your time in reading through this thread and trying to help noobs like me!
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
...tried those, but maybe am doing them incorrectly?
mindmajick said:
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Trying to use the ADB sideload feature to push CM or another ROM over doesn't seem to be working for me (unless I'm doing it wrong?)
I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the "adb sideload C:\users\Name\update.zip command just gets me an Error: Device not Found message". Could I be using the command incorrectly?
Trying to use any fastboot command in Windows Command Prompt results in <waiting for device> to hang for hours, with no changes to command prompt and no changes to the kindle (still sits at the blue/white boot logo).
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fastboot Drivers
mindmajick said:
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Are there difference drivers for fastboot and adb? I don't get a 'yellow triangle' and my device manager identifies the device as a Kindle Fire [Android ADB Interface], so I thought I was okay.
Should I be looking for fastboot drivers?
And btw, thanks so much for your willingness to help and input!
ME TOO
Just purchased a KF from someone...thay had rooted it...I tried to unroot...got stuck...now mine is doing the same as yours. I hope someone has a fix for you as I too have a large paperweight.
Follow Up
tessa33 said:
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Click to expand...
Click to collapse
tessa33,
I just sent you a response. Call me at 707-774-5923 when you have a moment.
Solution?
I figured I could post in this thread before staring my own because I am having a very similar issue trying to revert my Kindle Fire 2 back to stock from cyanogen so I can sell it. I downloaded the official software from Amazon but every time I try to flash it through TWRP I get the exact same error you were getting. Did anyone ever figure out how to resolve the issue for you?
Had the same problem, so I chatted with an Amazon associate, told him I turned it on one day and it showed the grey triangle and he sent me a new Kindle Fire 2nd Gen for free. Try that...
Sent from my iPhone using Tapatalk
Hello
I have rooted KF2 and I did factory reset I lost TWRP&Os I can see the device as ADB device, Howeverm when the device in fastboot the pc not recognize it.
issuing fastboot devices command return nothing.
I used ubuntu and windows still the same issue. any idea?
Hi,
I accidentally deleted everything through TWRP. I wanted the kindle fresh for my new ROM, and thought that deleting everything would make for a cleaner install. I was wrong and now all my kindle is good for is TWRP.
When in TWRP, windows doesn't recognize the kindle. Because of this, I cannot mount it. Windows and the kindle fire utility recognizes it as adp when i boot regularly (which is just a black screen) but cannot do anything since it will not enter normal or fast mode.
I don't know what to do, nothing is working. When I restart the kindle it says superuser is not installed, and asks if I would like to install it. I say yes, and it fails. Super user WAS installed before I deleted everything.
Any ideas?
Some more info
1. shell doesn't work
2. it looks like the bootmode is stuck in fastboot, but KFU won't recognize it, even though windows does.
3. Windows does not recognize the kindle when in TWRP recovery mode. If It did i could simply transfer files over and flash it...
4. If I try to boot normally, I get a black screen, but FKU recognizes ADP. It does not recognize what bootmode it's in though.
I believe FFF is working as I have the blue kindle logo and options in the bootloader, but no matter what I do I can't figure it out.
I REALLY need some help from you more experienced guys
thanks for reading
I'm making some progress, I'm in fastboot command prompt and have access. But what do I do from here?
How can I install a system from fastboot? It looks like all the guides say to install twrp and go from there but I have twrp and it wont communicate with my pc!!!
ADB
llmercll said:
Some more info
1. shell doesn't work
2. it looks like the bootmode is stuck in fastboot, but KFU won't recognize it, even though windows does.
3. Windows does not recognize the kindle when in TWRP recovery mode. If It did i could simply transfer files over and flash it...
4. If I try to boot normally, I get a black screen, but FKU recognizes ADP. It does not recognize what bootmode it's in though.
I believe FFF is working as I have the blue kindle logo and options in the bootloader, but no matter what I do I can't figure it out.
I REALLY need some help from you more experienced guys
thanks for reading
Click to expand...
Click to collapse
Do you have adb and fastboot intstalled on your PC??
lj50036 said:
Do you have adb and fastboot intstalled on your PC??
Click to expand...
Click to collapse
Yes, I've been using them at the command level
Feedback
llmercll said:
Yes, I've been using them at the command level
Click to expand...
Click to collapse
Boot into recovery and type
adb devices
copy and paste the output of this so I can see!!!
I went to boot and at the black screen tried to push the stock kindle FW. it failed for some reason
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>adb push C:\update.zip \tmp
failed to copy 'C:\update.zip' to '\tmp': Read-only file system
c:\kfu\tools>
Here is me trying adb devices in recovery mode
c:\kfu\tools>adb reboot recovery
c:\kfu\tools>adb devices
List of devices attached
Interestingly, rebooting into recovery just brought me to the bootloader. it wouldnt boot into recovery by itself, I have to manually do it through the bootloader. Immediately, booting into recovery disconnects my kindle from the pc, and I hear the sound in windows and the kindle dissapears from device manager.
llmercll said:
I went to boot and at the black screen tried to push the stock kindle FW. it failed for some reason
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>adb push C:\update.zip \tmp
failed to copy 'C:\update.zip' to '\tmp': Read-only file system
c:\kfu\tools>
Here is me trying adb devices in recovery mode
c:\kfu\tools>adb reboot recovery
c:\kfu\tools>adb devices
List of devices attached
Interestingly, rebooting into recovery just brought me to the bootloader. it wouldnt boot into recovery by itself, I have to manually do it through the bootloader. Immediately, booting into recovery disconnects my kindle from the pc, and I hear the sound in windows and the kindle dissapears from device manager.
Click to expand...
Click to collapse
So you can boot into recovery yes??
What is this KFU if that some kindle stuff we need to get rid of it and get the fastboot and adb from google... The SDK
make sure you open your CMD window as admin and try putting that file in the /sdcard not the /tmp
lj50036 said:
So you can boot into recovery yes??
What is this KFU if that some kindle stuff we need to get rid of it and get the fastboot and adb from google... The SDK
make sure you open your CMD window as admin and try putting that file in the /sdcard not the /tmp
Click to expand...
Click to collapse
I can boot into recovery, yes. KFU is kindle fire utility. I have the sdk and fastboot and adb.
could putting it in tmp be why the push failed?
Admin
llmercll said:
I can boot into recovery, yes. KFU is kindle fire utility. I have the sdk and fastboot and adb.
could putting it in tmp be why the push failed?
Click to expand...
Click to collapse
Or maybe you did not open you CMD window as admin....but twrp should see your devices in adb and let you push things to the /sdcard for sure... I have one right in front of me, but I am running linux which is much better for these kinds of things... Here is my output of that command and than a push of a zip file
Code:
[email protected] ~ $ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected] ~ $ adb push cmb_kkgapps_20131209.zip /sdcard
6121 KB/s (126216099 bytes in 20.135s)
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
feedback
llmercll said:
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
Click to expand...
Click to collapse
Move everything to the root of your c drive fastboot.exe, adb.exe, update.zip, all of it and than when you open your CMD windowas admin type
cd /
This will move you to the root of your c drive in you CMD window... Than type dir to make sure u can see your fastboot and adb and your update zip
than type
adb push update.zip /sdcard
llmercll said:
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
Click to expand...
Click to collapse
It's been a long time since I looked at this, but I seem to remember the windows adb client wanting a trailing slash if the push destination is a directory. That is... you want to use "/sdcard/" instead of "/sdcard" in that command to indicate that you want to push a file into that directory rather than replace the directory with a file (which it won't allow). Alternatively, you can use "/sdcard/update.zip" to remove any ambiguity from the command.
The output of your "adb devices" command is also a concern. It doesn't look to me as if you've booted the device into TWRP because it should output "recovery" and not "device" at the end there. One way or another, you'll have to get it to boot into TWRP if you want to flash that update.zip.
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
C:\>adb devices
List of devices attached
0123456789ABCDEF device
C:\>adb push update.zip /sdcard
failed to copy 'update.zip' to '/sdcard': Is a directory
C:\>adb push update.zip /sdcard/
failed to copy 'update.zip' to '/sdcard//update.zip': Permission denied
C:\>adb push update.zip /sdcard/update.zip
failed to copy 'update.zip' to '/sdcard/update.zip': Permission denied
C:\>
Click to expand...
Click to collapse
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
llmercll said:
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
Click to expand...
Click to collapse
Try to use the "mount" function in TWRP to mount the /sdcard partition on your computer. It should work with the generic drivers already on your Windows PC and you can copy the update.zip over to it that way. If you can't get that to work, you are going to have to try reinstalling the drivers to get your PC to recognize TWRP. There are detailed instructions on how to do this in my guide.
The only other thing I can think of is to try reflashing an older version of TWRP. Those directions are available in one of my guides as well.
Recovery
llmercll said:
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
Click to expand...
Click to collapse
I would if it were me, install a recovery you dont plan on using... Than flash the one you would like to us.... I know it sounds funny but.. Ive be here before and that seems to work everytime... Than flash ROM and Gapps....
Here is the link to TWRP the first gen fire is an 'otter'... Make sure you get the otter.img....Than rename the .img file to twrp.img than put it with fastboot.exe and open CMD window as admin...and type
Code:
fastboot -i 0x1949 flash recovery twrp.img
Than
Code:
fastboot -i 0x1949 reboot
Let me know if that works for you or if you have any questions along the way... Thx as always lj
I didn't see the link for the older TWRP, but I went to the website and tried this one
http://techerrata.com/browse/twrp2/blaze
openrecovery-twrp-2.4.2.0-otter.img
I successfully flashed it and rebooted, but when the kindle went into recovery mode it once again disconnected from the computer. In recovery, which was clearly the older TWRP version, I attempted to mount but nothing happened. Of course it can't happen if it isn't communicating with my pc =/
Can I flash a ROM directly through fastboot? That would probably solve the issue, no?
What about that other recovery program, COTR?
llmercll said:
I didn't see the link for the older TWRP, but I went to the website and tried this one
http://techerrata.com/browse/twrp2/blaze
openrecovery-twrp-2.4.2.0-otter.img
I successfully flashed it and rebooted, but when the kindle went into recovery mode it once again disconnected from the computer. In recovery, which was clearly the older TWRP version, I attempted to mount but nothing happened. Of course it can't happen if it isn't communicating with my pc =/
Can I flash a ROM directly through fastboot? That would probably solve the issue, no?
What about that other recovery program, COTR?
Click to expand...
Click to collapse
2.6.3.1 Give that one a try!!!
I was able to get TWRP recognized by windows by using the earliest blaze edition. I mounted, copied the files, and then flashed back to 2.6.3.1 otter.
Then I wiped whatever data may have been in system data and cache and installed a new rom...
Only problem is it seems to be hanging on "updating partition details.."
I have the option to reboot, but am not sure if I should...
I think I got it!!
Hello,
I have a original stock Kindle Fire and just recently it won't boot all the way up. It just shows the Kindle Fire screen and flickers every 20 seconds or so like it is stuck in a reboot loop. I tried to do a hard reset, run the battery all the way down and recharge but that didn't help. I even took the case apart and unplugged the battery hoping that might help but it didn't.
I then decided to install KFU (0.9.9) to see if I could get it in Fastboot and wipe the data from it. That didn't work as it throws an error: failed to copy 'files\fbmode' to '/data/local/fbmode': No space left on device. I then decided to install Android SDK for ADB and see how much space is left in that folder. Turns out there is only 28K left, which seems like it is basically full. I cannot delete anything from that folder as it is currently read-only. I cannot basically do anything to it since all files/programs that need to be downloaded to root it require copying files to that directory which doesn't have space.
At this point, I would be happy if I could somehow factory reset the device. I don't care about anything on it and just want it to work. Any suggestions for doing this without buying the special cable that will put it in Fastboot mode automatically?
Thanks!
jsyphon said:
Hello,
I have a original stock Kindle Fire and just recently it won't boot all the way up. It just shows the Kindle Fire screen and flickers every 20 seconds or so like it is stuck in a reboot loop. I tried to do a hard reset, run the battery all the way down and recharge but that didn't help. I even took the case apart and unplugged the battery hoping that might help but it didn't.
I then decided to install KFU (0.9.9) to see if I could get it in Fastboot and wipe the data from it. That didn't work as it throws an error: failed to copy 'files\fbmode' to '/data/local/fbmode': No space left on device. I then decided to install Android SDK for ADB and see how much space is left in that folder. Turns out there is only 28K left, which seems like it is basically full. I cannot delete anything from that folder as it is currently read-only. I cannot basically do anything to it since all files/programs that need to be downloaded to root it require copying files to that directory which doesn't have space.
At this point, I would be happy if I could somehow factory reset the device. I don't care about anything on it and just want it to work. Any suggestions for doing this without buying the special cable that will put it in Fastboot mode automatically?
Thanks!
Click to expand...
Click to collapse
Could try
Code:
adb shell recovery wipe_cache
adb shell recovery wipe_data
adb reboot
or
Code:
adb shell
recovery --wipe_cache
adb shell
recovery --wipe_data
adb reboot
not sure if they work with stock Kindle
also see [UTILITY] Kindle Fire Unbrick Utility V1.1
The unbrick utility alone may or may not work.
sd_shadow said:
Could try
Code:
adb shell recovery wipe_cache
adb shell recovery wipe_data
adb reboot
or
Code:
adb shell
recovery --wipe_cache
adb shell
recovery --wipe_data
adb reboot
not sure if they work with stock Kindle
also see [UTILITY] Kindle Fire Unbrick Utility V1.1
The unbrick utility alone may or may not work.
Click to expand...
Click to collapse
Thanks for the suggestions but unfortunately still stuck at logo. The unbrick utility is a cool idea but looks like everything is for a rooted device, most commands it does are either permission denied or says this is read-only device.
Anyone have any other suggestions for how I can at least delete/clear space in the /data folder so I can get into fastboot mode?
jsyphon said:
Thanks for the suggestions but unfortunately still stuck at logo. The unbrick utility is a cool idea but looks like everything is for a rooted device, most commands it does are either permission denied or says this is read-only device.
Anyone have any other suggestions for how I can at least delete/clear space in the /data folder so I can get into fastboot mode?
Click to expand...
Click to collapse
the unbrick utility includes an older root method (zergrush). try [How To][Root] Kindle Fire 1 update 6.3.3 [2014]
another option is Soupkit
but if none of the above worked, I'm guessing you will need a Fastboot cable.