Related
Hey guys. I have my kindle fire over a year now and recently it started sticking a lot and certain things i would press would open something else. I decided to basically format it by using Kindle Fire Utility. I got into TWRP Recovery and made a backup; wiped Cache and Davlik and so on, then I tried installing an update from the update.zip I uploaded and from there, I have had this boot screen. I cannot get into the device, but when I plug it into the computer, it tells me the device is Online but the Status is unknown. Please help me out!
Thanks a Million!
silentarts said:
Hey guys. I have my kindle fire over a year now and recently it started sticking a lot and certain things i would press would open something else. I decided to basically format it by using Kindle Fire Utility. I got into TWRP Recovery and made a backup; wiped Cache and Davlik and so on, then I tried installing an update from the update.zip I uploaded and from there, I have had this boot screen. I cannot get into the device, but when I plug it into the computer, it tells me the device is Online but the Status is unknown. Please help me out!
Thanks a Million!
Click to expand...
Click to collapse
This is from not doing a "factory reset" in recovery before flashing the update.zip.
In testing the new version of SoupKit, I attempted to break the shell intentionally by installing the update.zip without doing a factory reset in the hopes that I would receive the typical "- exec '/system/bin/sh' failed: No such file or directory (2)" error that is usually accompanied with trying to change the bootmode over a missing or corrupted shell. After several attempts to intentionally put myself in that situation, I could never actually make it happen. However, after leaving the KF alone for a minute or two while it tried to boot and sat at the Kindle Fire log, it would usually boot into the Kindle Fire stock recovery and give me the option to factory reset.
You could try that out to see if it works for you, but there's still a good chance that you'll need to acquire a factory cable to get into fastboot so you can reinstall FireFireFire and custom recovery to fix the problem.
Thanks!
Ok. My question now is. When I launch KFU, I press 1 and then what do I press 2 or 3? then leave it let to do it's thing?
My main issue though is this message:
- exec '/system/bin/sh' failed: No such file or directory (2) -
is there no way to fix permissions?
Stress
I tried what you told me on all boot modes, but I keep getting this error.
Anyways. I tried pushing a file to the system via adb and this is what it shows...
adb push zergRush /
failed to copy 'zergRush' to '/zergRush': Read-only file system
Is there any way to push a folder with the correct permissions?
Please help me...
Got something
Hey. I am running through some adb commands and I tried
adb pull / /fadil
Click to expand...
Click to collapse
It actually copied some files...
I am not sure if it is possible, but can you delete folders or push folders through adb?
I also did adb root and it told me that adbd cannot run as root in production builds
Thanks!
Yeah, that error means your shell actually is screwed and you need a factory cable.
This is a cross-post, sorry but I need the help...
Hello Forum Lords, I hope that I found the proper thread for my problem.
I was simply trying to get Jelly Bean onto my wife's replacement KF1 after the first KF1 suffered some sore of hardware malfunction and would no longer take a charge. Somehow, somewhere I went horribly wrong this time around. I got stuck at the KF1 logo and eventually I got it to boot, but only to recovery (TWRP).
My predicament is this: My KF1 is stuck booting into TWRP. Device manager on Win Vista recognizes the KF1 as Android Composite ADB Interface. When I try to use the KFU to boot the device into Normal Mode it says "cannot find the drive specified".
At the KFU starting menu, it says ADB Status: Online, Boot Status: 0x5003.
My ultimate goal is to get this thing running with Jelly Bean (like I accomplished with the first one before it broke) again. I am painfully noob at all of this. Please speak as you would to an escaped chimp who will not let go of the keyboard and mouse.
Thank you, anybody?
Do you see the blue kindle fire logo when it boots?
No. Normal Boot logo
Can anyone help me out? Please?
silentarts said:
Can anyone help me out? Please?
Click to expand...
Click to collapse
Can anybody else help me out?
Can anybody else help me out?
silentarts said:
Can anybody else help me out?
Click to expand...
Click to collapse
Pay attention to the instructions given to you. Get a factory cable.
Don't live in America.... I'm from Trinidad and Tobago
silentarts said:
Don't live in America.... I'm from Trinidad and Tobago
Click to expand...
Click to collapse
You have two options. You can make or acquire a factory cable or you can usbboot. The factory cable is the easiest and safest option for you. If you decide to usbbot, you'll need Linux, Firekit, good eyes, and a steady hand. It will require you to open the device and short a point that is slightly larger than a grain of sand. It's significantly more difficult than using a factory cable and puts you at risk of doing permanent damage to your device's hardware.
Thanks a lot... Will see what happens....
A couple weeks ago i rooted my Kindle fire. Sadly I had no idea what I was doing. I have gone throught countless troubleshooting forums, programs, KFU, Kindle Fire unbricker. I cant access the SD or much less anything in the device. When i turn it on all that happens is the "Kindle Fire" logo pops up. When i run KFU It says ADB is online but boot status is unknown. I can NOT RUN ADB SHELL and get the error message
- exec '/system/bin/sh' failed: No such file or directory (2) -
I also get the occasionaly running other commands.
Please help me I have no idea what I'm doing.
I have original kindlke fire
I now have a FACTORY CABLE.
Make sure the device is powered down and plug in your factory cable. Then use fastboot to install custom recovery.
What were you doing before this happened?
Hi,
I had my kindle rooted and a few weeks back the OS got updated automatically to a new version and my Home screen went black and I was unable to change the wallpaper. So I ran Stunts Wallpaper Fix but something must have gone wrong and I am now stuck in the:
Kindle Fire System Recovery
Your kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
The choices I have are:
Reboot your kindle
Reset to Factory Defaults
Choosing any of the two options eventually leads back to the above. So I purchased the fastboot cable but that apparently does not help either, as soon as I plug it into the kindle it will go back to the Kindle Fire System Recovery screen. I have ADB installed on my PC, however when starting the Kindle, my PC only recognizes the driver for about 2 seconds and displays it as "Jem-PVT-Prod-04" in the Device Drivers then that disappears as well.
I read many, many threads on this forum but don't seem to find anyone with this particular problem. Help very much appreciated.
Where did you get your factory cable?
I got it from the "EARLYBIRD SAVINGS 3ft USB to Micro USB Factory Cable for Amazon Kindle Fire Motorola Xoom/Phones" from Amazon.
eandjon said:
I got it from the "EARLYBIRD SAVINGS 3ft USB to Micro USB Factory Cable for Amazon Kindle Fire Motorola Xoom/Phones" from Amazon.
Click to expand...
Click to collapse
And before plugging it in, did you make sure your device was completely powered down (held the power button for 10-15 seconds)?
Yes, absolutely. Tried it several times always returning to the System Recovery Screen.
eandjon said:
Yes, absolutely. Tried it several times always returning to the System Recovery Screen.
Click to expand...
Click to collapse
You may have a bad factory cable, or the "factory cable" you have is not a factory programming cable.
If you can install the driver in my signature on the jem device before it disappears, then you should be able to use the fastboot command like this and not have to use a factory cable:
fastboot -i 0x1949 getvar product
Run that command and after it says waiting for device, plug your kindle in while powered off, it should go into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed your instructions and it seems to be working.
I am now receiving after rebooting the Kindle a dark screen saying "fastboot mode" in yellow.
In order to not screw things up again, what would be the best way forward?
I would suggest using kindle fire first aide and reflashing the stock system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed the steps mentioned for the Kindle First Aide and did a complete restore. My Kindle is now up and running!
Thank you sir for your excellent advice!
On another note if you try my wallpaper fix again, if it has some kinda error and bricks again, could u report the error to me? I always try to make it as safe as possible, and would like to know why my safeties didn't help in your case. Who knows, it might actually work this time since your os is closer to stock than before possibly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I installed your wallpaper fix and it worked without any issues at all. Thank you!
My kindle fire hd 8.9" rooted is doing the same
stunts513 said:
If you can install the driver in my signature on the jem device before it disappears, then you should be able to use the fastboot command like this and not have to use a factory cable:
fastboot -i 0x1949 getvar product
Run that command and after it says waiting for device, plug your kindle in while powered off, it should go into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My kindle is stuck in the exact same loop. What do you mean by 'install the driver...on the jem device'? ...I'm pretty green
Basically it means open the device manager on your PC, and plug you kindle in while its off, if it is indeed an 8.9" model, after it powers on you should see a device pop up briefly in the device manager called jem something, if it instead makes the noise like something connected an you don't see a jem device popup, then you probably have the drivers installed already. If you see the device pop up then quickly right click it and hit update drivers and point it to where you extracted my drivers and let them install. After that you should be able to use the fastboot command I mentioned to get I to fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It says "Windows encountered a problem...The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
Sent from my SGH-T999 using xda app-developers app
You must be on windows 8, you need to disable driver signature enforcement. Google it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It's rebooting now...fingers crossed!!!
IT WORKS!!!
Thank you so much Stunts!!! I'm now trying to do your programming, and I'm having a bit of a problem. The dos is telling me 'Could Not Find ...system32\framework-res.apk.orig doing prelim check...' followed by 'Your system partition is too low...' what am I doing wrong?
OK well the cannot find time isn't an error, its just extra output that I haven't disabled, that file it can't find is basically the cleanup process running to delete any files from a previous attempt, and if they aren't there you see that error. As for the disk space error, you should check your system partition to see how much space it has left on it, you will need around 40mb to use the wallpaper fix. You can attempt to disable the check if you are sure you have enough space, but if it doesn't have enough space you will end up with a softbrick'd device stuck in a boot loop until it has its system partition reflashed. Try either over adb shell or in a mobile terminal running "df /system" and tell me how much space it has free.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try either over adb shell or in a mobile terminal running "df /system" and tell me how much space it has free.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app[/QUOTE]
Ok, recap...system is still rooted. I did a full system reboot, and the only other os that I had was go launcher. To try and get the script to run, I deleted Go launcher, along with widget picker, and live wallpaper. I tried to run "df/system" through COMMAND under administrator, and I tried the same command on my kindle through a terminal emulator and it said "not recognized" on pc, and "not found" on kindle. I'm sorry if this is annoying, and I appreciate the help.
---------- Post added at 05:32 AM ---------- Previous post was at 04:55 AM ----------
n/m, just found the df. on system it says 37M. What can I do for the other 3M?
---------- Post added at 05:49 AM ---------- Previous post was at 05:32 AM ----------
Ok...I realized I was asking stupid questions that I should resolve myself. For nOObs (like me) I went to this http://forum.xda-developers.com/showthread.php?t=619153 to get help with the adb shell. In doing so I was able to find my available space. I typed the command "df" and it showed all my available and used storage. I then went in to X-plore (root file management app) where I was able to change my user status to SU and go in to the systems folder and remove apps that were invaluable. Thanks for all the help stunts, if it wasn't weird I would send you some Christmas cookies lol.
I was stuck for some reason on Kindle fire logo so I installed a stock rom and now I am stuck on Kindle Fire logo. KFU doesn't recognize it no matter what i do but i does say"exec '/system/bin/sh' failed: No such file or directory (2)", I do have drivers installed btw. Kindle unbrick utility doesn't recognize it either. I tried Soupkit but I get error "Unable to open MTP device" when I select most of the option then the terminal goes has a infinite seizure. I was thinking of buying a factory cable but I am not so sure it will work anymore...
Same problem with me what does a factory cable do?
Sent from my C6903 using XDA Premium 4 mobile app
So I was being stupid and I moved a system file... Which not surprisingly crashed it. When I rebooted, It started to flash the "Kindle Fire" logo for about 30-45 seconds before becoming a red triangle and telling me I should do a system restore, which did nothing.
I searched around and found that I needed to get into fastboot to flash my backed up copy of the partitions back on to undo what I did. So I ordered a cable off ebay, which arrived from china yesterday. Sadly, when I plug my kindle into my computer via this cable it does nothing. When I run any fastboot commands, they hang at "< waiting for device >".
Is there anything that I can do that might help? I plan on soldering my own cable tomorrow to see if that's the problem.
Additional information:
- OS: Windows 7
- Kindle Fire 2
- I changed a file in "/system/framework/framework-res.apk"
- Used Kindle FirstAide to make backups
- adb drivers don't show up in device manager
You didn't see any devices with a yellow triangle next to them when the kindle is in fastboot mode? On wait your kindle never shows the fastboot logo?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You didn't see any devices with a yellow triangle next to them when the kindle is in fastboot mode? On wait your kindle never shows the fastboot logo?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It never showed fastboot logo despite being plugged in with a factory cable. And no, the triangle was red.
Lemonilla said:
It never showed fastboot logo despite being plugged in with a factory cable. And no, the triangle was red.
Click to expand...
Click to collapse
sounds like a bad fastboot cable. i have heard horror stories of people buying them and then using them and having the usb port fried on the kindle, so i guess yours was the lucky side of a bad fastboot cable. Lately i think people have been going for this nice adapter i think hashcode mentioned in his post by blackhat or something, it goes between the microusb plugs on the kindle and cable. Feel free to make one though, thats usually pretty easy to do.
stunts513 said:
Feel free to make one though, thats usually pretty easy to do.
Click to expand...
Click to collapse
One would think so. I managed to break the connection wire (the little one that goes into the micro_usb). Then while trying to solder to the broken stub, I wedged some molten solder to cross between ping 3 and 5's wires. I think I'll open up the one I bought for a second try. If that doesn't work I'll look into buying one of the adapters.
So I finally found time to try making a new one with the Chinese one that they sent. You were right about it being a bad cable. I took it apart and it was missing pin 5 altogether. Where would you recommend buying one from? I saw a neat little adapter head somewhere, but don't want to buy another one that doesn't work. I've been looking at this one: shop. teamblackhat .info (won't let me post the link )
If that's the one I'm thinking it is, its the same one hashcode mentions in his 2nd bootloader + twrp installation tutorial, I recommend it.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
If that's the one I'm thinking it is, its the same one hashcode mentions in his 2nd bootloader + twrp installation tutorial, I recommend it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So it came in the mail, and it works. It flashes everything but system.img, which I believe it says is too large to flash. The problem is that I believe this is the partition that is messed up. Do you know how to bypass this?
Code:
C:\Users\Lemonilla\Documents\System Files\Backups\KindleBackup1>fastboot -i 0x19
49 flash system system.img
target reported max download size of 486539264 bytes
Invalid sparse file format at header magi
sending sparse 'system' (463367 KB)...
OKAY [ 10.661s]
writing 'system'...
FAILED (remote: : Sparsed Write)
finished. total time: 10.716s
I'm guessing the system.img is just corrupt, I see it happen on occasion and it causes this error, try redownloading the system.img using kffa but I think kffa's links are down for its system images. Hopefully this situation isn't the same as a situation I'm having with someone else's kindle that is reporting that issue when it shouldn't be unless I make the actual partition smaller.
Sent from my Amazon Tate using Tapatalk
It worked, now all I have to do is get it to find my router. Thanks a ton!
EDIT: For some reason it is not letting me enable Wi-Fi. Is this common, I can't find anything on it.
Oh boy... Check to see if you can enable bluetooth
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Oh boy... Check to see if you can enable bluetooth
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I managed to fix it. I re-flashed the system and downloaded the boot and launcher from kffa and flashed those over my backups as well and that seemed to fix it. Thank you so much for your help!
OK glad to hear that that fixed it, I was worried it might be the boot0block, but thankfully it was not.
Sent from my Amazon Tate using Tapatalk
It might have been, that is one of the one's that I flashed with kffa's files.
The boot0block isn't flashed by kffa because its unique to every device, its basically the nvram with your serial number, WiFi mac address, Bluetooth mac address and such in it. You probably saw it flashing the bootimg (kernel + intramfs).
Sent from my Amazon Tate using Tapatalk