Bricked my Kindle cannot figure it out - Kindle Fire Q&A, Help & Troubleshooting

Ok so, my brother gave my parents a kindle that had TWRP, FFF, and Cyanogen mod on it (not sure what version). My mom tried to use it one day, but it wouldn't go past the FFF yellow triangle thing so she gave it to me to try and fix. I went into TWRP and wiped the cache and did a factory reset and that didn't do anything. I found this thread (http://forum.xda-developers.com/showthread.php?t=1638452) to try and revert it to the stock software, now this is where I think I messed something up. After I installed the update onto the kindle with TWRP I rebooted the device and now, it will boot onto the normal white and orange KF screen but won't go anywhere past that. I can't get back into TWRP or anything it just stays at the logo screen. I can control is using ADB but not fastboot. With certain ADB commands though it says - exec '/system/bin/sh' failed: No such file or directory <2> -
I've been trying to fix it for 2 or 3 days now and cannot figure it out, I've been looking through these forums and have tried numerous things but nothing seems to work. Please help me haha

You need a fastboot cable & Soupkit my dude. I just started tinkering with it not too long ago after I let it set for almost a year lol. Here, I'll like you to the one I got.
Also get ready to put Linux on your PC. Here is my previous thread that I had to figure out how to fix myself.
Thread
Fastboot Universal USB

Related

[Q] Bricked Kindle Fire 6.3

I'm in bad shape and need some help. I rooted my kindle fire with KFU. All went well but I beleive SU didn't install. I read to flash TWRP and then just install a custom ROM which would have SU.
I flashed TWRP which said it was successful (never saw the yellow triangle though). At that time I made a backup of the stock rom. That went ok as well. I then wiped everything/factory reset from TWRP and tried to install CM7. That was unsuccessful. Once I rebooted I am stuck at the Kinle Fire logo.
I've tried the unbrick utility and it doesn't work. I've uninstalled/reinstalled the driver numerous times and windows does recognize the fire and TWRP sees the device as online. I think I may be stuck in fastboot mode so I tried TWRP to change to normal. No dice. It gets stuck saying waiting for device.
I must say that when the kindle is plugged in to the compter I think it's connecting and disconnecting quickly because it's in a bootloop. Windows is dinging and donging. I also cannot boot into TWRP.
Any thoughts would be greatly appreciated. My daughters are going to kill me. I've rooted many devices and don't consider myself a noob by anymeans so I'm willing to try anything. Thanks in advance.
I forgot to mention that basically anything I try in TWRP I receive these two messages
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
1 Are you able to power it down completely and reboot it to the fff logo?
2 When you plug it in do you have light on the power button?
Sounds like a boot loop yes
But I don't think your completely sunk
You might want to look into getting a factory cable I did a bit of reading on this last night here http://forum.xda-developers.com/showthread.php?t=1392693
But since its dinging and donging in windows open device manager up and see how its being listed there and what drivers its using.
Try plugging it to AC maybe you can break the loop that way
If you can get to twrp try factory restore then reboot system
If it didn't push superuser when you rooted it that could be a problem it took me twice sorry to say
Did you not create a backup before flashing cm7?
Restoring your backup is followed by the error you mentioned above?
Also with kf utility open try plugging and unplugging the USB maybe you will get a split second to hit a key choose manage boot modes if it stabilizes there are options for stock update zip and such or retry root http://forum.xda-developers.com/showthread.php?t=1392693
---------- Post added at 10:51 AM ---------- Previous post was at 10:06 AM ----------
Also look here this was posted yesterday http://forum.xda-developers.com/showthread.php?t=1593493
Thepooch said:
1 Are you able to power it down completely and reboot it to the fff logo?
2 When you plug it in do you have light on the power button?
Sounds like a boot loop yes
But I don't think your completely sunk
You might want to look into getting a factory cable I did a bit of reading on this last night here http://forum.xda-developers.com/showthread.php?t=1392693
But since its dinging and donging in windows open device manager up and see how its being listed there and what drivers its using.
Try plugging it to AC maybe you can break the loop that way
If you can get to twrp try factory restore then reboot system
If it didn't push superuser when you rooted it that could be a problem it took me twice sorry to say
Did you not create a backup before flashing cm7?
Restoring your backup is followed by the error you mentioned above?
Also with kf utility open try plugging and unplugging the USB maybe you will get a split second to hit a key choose manage boot modes if it stabilizes there are options for stock update zip and such or retry root http://forum.xda-developers.com/showthread.php?t=1392693
---------- Post added at 10:51 AM ---------- Previous post was at 10:06 AM ----------
Also look here this was posted yesterday http://forum.xda-developers.com/showthread.php?t=1593493
Click to expand...
Click to collapse
1. I can power down completly and upon rebooting is when I am stuck at the Kindle fire logo.
2. When plugged in I do have a light on the power button.
3. I've briefly looked in to the factory cable and that is an option
4. I see in device manager the Android Phone
5. Plugging it into AC all night didn't help.
6. I did create a backup but I can no longer boot in to TWRP
7. TWRp does see the kindle as online and I can make the selection for boot mode but whatever I choose it comes back with
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
I have the same problem...
I didn't didn't install FireFireFire (I'm a noob so I didn't know what it was for until now)
I rooted my device (I think. KFU said it was rooted)
I wanted to install CM7.
I went into TWRP and wiped everything I was supposed to. (Got into TWRP through KFU.)
Tried to install Cyan7 and failed.
I booted down my kf and now whenever I try to turn it on it stays stuck on the "kindle fire" screen and won't change. I think I permanently bricked it unless someone has an answer to this problem.
I've also tried the above and I get the same error.
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
My problem sounds the exact same as yours nchevaux
Yep.....that sounds like the exact process I did. I have yet to find anything that will help us out. My last resort is to get the factory cable unless someone pulls through here.
If you figure something out let me know. I'll keep you posted on my progress.
Try this:
From KFU:
press 1 - for boot mode menu
press 1 - for Choose NORMAL MODE (4000)
waiting for device ......
DO NOT STOP KFU !!!!!
shutdown device (press button for 10-20 sec)
start AGAIN
DO NOT STOP KFU !!!!!
killgore said:
Try this:
From KFU:
press 1 - for boot mode menu
press 1 - for Choose NORMAL MODE (4000)
waiting for device ......
DO NOT STOP KFU !!!!!
shutdown device (press button for 10-20 sec)
start AGAIN
DO NOT STOP KFU !!!!!
Click to expand...
Click to collapse
KFU doesn't say "waiting for device"
Also the ADB status is online but the Boot Status is "Unknown"
If you figure something out let me know. I'll keep you posted on my progress.
Click to expand...
Click to collapse
Most definitely. I'll be trying as many different methods I can find. I'll keep you posted as well.
This...
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
is adb telling you that your system is broken. My guess is when you restart your KF, you see the boot logo, the display blacks out, then the boot logo comes back a little bit dimmer this time. It might even brighten up again, but that's where it gets stuck.
If this screen ever blacks out like this at the start of the boot process, you are not in fastboot mode. The KF is continuing to boot into the system, but failing. If you can get back into fastboot mode, flash a new recovery. If you can get into TWRP, I would try reflashing the system. If what I just said makes no sense to you, read this...
http://forum.xda-developers.com/showthread.php?t=1552547
and make sure your drivers are working before you continue.
Fixed
thommyyy said:
KFU doesn't say "waiting for device"
Also the ADB status is online but the Boot Status is "Unknown"
Most definitely. I'll be trying as many different methods I can find. I'll keep you posted as well.
Click to expand...
Click to collapse
Fixed it! I made a factory cable and that put me right in to fastboot. At the point you can flash. I know what I did to put my KF in that state, it was just a lack of patients really. There wasn't anything wrong with the KFU, driver, etc...just the user. I'm sure a factory cable would work for you as well and have you up and running in no time.
This is a really good read http://forum.xda-developers.com/show....php?t=1552547
nchevaux said:
Fixed it! I made a factory cable and that put me right in to fastboot. At the point you can flash. I know what I did to put my KF in that state, it was just a lack of patients really. There wasn't anything wrong with the KFU, driver, etc...just the user. I'm sure a factory cable would work for you as well and have you up and running in no time.
This is a really good read http://forum.xda-developers.com/show....php?t=1552547
Click to expand...
Click to collapse
Link doesn't work. Also I'll try to check that factory cable out. I'm not too sure if I am able to get or make one (currently studying abroad).
Still, is there any way around this w/o the factory cable?
Edit: I looked around and so far the only solution is a factory cable... (no soldering skill at all whatsoever)
thommyyy said:
Link doesn't work. Also I'll try to check that factory cable out. I'm not too sure if I am able to get or make one (currently studying abroad).
Still, is there any way around this w/o the factory cable?
Edit: I looked around and so far the only solution is a factory cable... (no soldering skill at all whatsoever)
Click to expand...
Click to collapse
Look on Ebay. I saw you can purchase factory cables there. I know there are some people in the XDA community making them. You may want to search the forum for factory cable and see if anyone can help you out.
I didn't have soldering skills either, just determination. My cable isn't pretty but it did the job. Search Google for "mini USB breakout board". If you order one of these you probably don't need the precision soldering skills. The breakout board offers much more room to work.
Edit: here is the breakout board you would want. http://www.sparkfun.com/products/10031

I bricked my KF GOOOOD this time

I have had a Kindle Fire since they day they came out. I immediately disliked the stock Rom so I ran the kindle fire utility and installed Fire Fire Fire and TWRP, rooted it, and installed CM7 Rom which has been working great. Transferred files and programs between my PC and Kindle with no issue for months. Now with all the ICS roms available and working I decided to try and upgrade to one of those and thats when everything went wrong. Its in a bootloop and the triangle appears, fades, lights up again and immediately boots to TWRP. I have flashed the entire kindle using TWRP trying to get everything off of it. Upon plugging it into my PC BRIEFLY when the triangle logo pops up I get a "USB device not recognized" on my PC. I have tried using KFUtility to reinstall drivers, tried uninstalling n reinstalling drivers but the same thing happens. I cannot use TWRP to mount at all, nothing happens. Kindle Fire UTility keeps saying adb offline, CMD adb devices also results in 0 devices found. I have tried putting it on normal boot using both ADB and KFUtility and it says "wait for device" and nothing ever happens. Any idea? Not even sure if I have a rom installed on my kindle anymore but my PC wontread it so I cannot push another image to it. Got a plane trip on Saturday and would love to have this working to kill the bordom lol. Any advise would be greatly appreciated.
It sounds like your bootmode is set to recovery. An easy way to fix this is download FFF1.4 to your computer and use the mount function in recovery to place it on your sdcard.
Flash it in recovery as you would a rom except don't wipe anything. When you reboot, hold the power button like you're trying to enter recovery and you'll be given the option to reset the bootmode.
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
anomiefaunus said:
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
Click to expand...
Click to collapse
Generally, the only thing that would prevent adb/kfu from communicating with the device is the drivers. Make sure they're installed properly. You may have to uninstall them (delete if applicable) and reinstall them.
Follow the instructions in this guide to install and verify your drivers.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
anomiefaunus said:
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
Click to expand...
Click to collapse
Get your device drivers working so you can use adb. Follow the instructions in the post below...
http://forum.xda-developers.com/showpost.php?p=26144447
That is excellent advice and I wish it would work but I cannot pull up ADB once in TeamWin. Keeps saying no devices. As i said my PC detects it and ADB will detect it for .5 seconds on the orange triangle. Once the orange triangle disappears and it either boots to blackness or boots to TeamWin ADB stops recognizing my device. But I will play around with your suggestions once I get off work and let you know what i find out. Thanks again for everyones support.
Frozen screen during rooting
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
peredexter said:
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
Click to expand...
Click to collapse
Don't hijack the threads please. If you have a problem or question, post it in the Q&A section.

[Q] Bricked Kindle, bad. Please help me! Please! :(

Okay so I had TWRP and I was going to flash a different Rom. However I accidentally while not looking managed to wipe EVERYTHING, including my old Kindle OS (I reformatted it back to stock OS for some reason before I was going to flash another rom). I deleted everything, system, SD data, cache and delvec. Factory reset and whatever else was there, I didn't think it would do anything, there were no warnings. Now I believe my kindle is completely bricked for good and it makes me wanna cry
So far when I turn it on, it shows the original Kindle Fire screen and flashes to black quickly like it's rerunning the animation every 15 or so seconds. I'm afraid to keep it on and continue anything due to the battery last I saw was 30 person and the charging is already messing up on it.
If I could get it to connect to my computer I could reinstall TWRP and manae to flash it to whatever I want but when connecting it doesn't pick up and TWRP won't reconize it either. I've tried to use JDK or whatever it's called to ADB or something (you computer people get me!) and it gives me the error - exec '/system/bin/sh' failed. No such file or directory.
I'm not sure what I'm doing either, I've been watching a video on youtube and cannot get any farther in it due to this error.
Please, someone help me I'll worship you, I am completely lonesome without my Kindle
exec '/system/bin/sh' failed. No such file or directory
If you have FireFireFire installed (blue & white Kindle Fire logo) that error is not much of a problem. If it is not installed, however, you will need a factory cable.
Try to run Kindle Fire Utility 0.99 first and wait for KF reboot
ADB is also nightmare for me since my PC recently never recognizes my Fire in adb mode (always failed with KF tool .096 and 0.99). Therefore my TWRP version was stacked with 2.2.2.6 version for a long time, and the method to update it through the soft in Google Play store was also failed. However, I accidently find a good way to update TWRP to 2.6 versions by run KF tool and select Install TWRP. Then with the KF still connect to PC, I restart it and it take a seconds to install latest TWRP while my Fire still in boot status (blue Kindle Fire logo)
lifegap said:
ADB is also nightmare for me since my PC recently never recognizes my Fire in adb mode (always failed with KF tool .096 and 0.99). Therefore my TWRP version was stacked with 2.2.2.6 version for a long time, and the method to update it through the soft in Google Play store was also failed. However, I accidently find a good way to update TWRP to 2.6 versions by run KF tool and select Install TWRP. Then with the KF still connect to PC, I restart it and it take a seconds to install latest TWRP while my Fire still in boot status (blue Kindle Fire logo)
Click to expand...
Click to collapse
Okay! I ordered a cable off ebay and it just got here today, please tell me what to do I feel like you guys can help me unbrick it.

[Q] Kindle Fire HD 8.9 - 8.4.6 - stuck on blue logo, or fastboot screen.

Hello, sorry for my bad english.
Im a noob and have been looking and trying different things for days now and can't fix my KFHD8.9", I would greatly appreciate any help. Sorry if this have been asked, but ive tried everything and nothing seems to work or match the same problems.
I rooted my kindle fire hd 8.9" (8.4.6) and tried to install the 2nd bootloader + twrp (to eventually install CM10.2) using this guide (http://forum.xda-developers.com/showthread.php?t=2277105), but stupidly, I didn't back up on step 2. I attempted to flash the bootloader using fireflash and, as long as I could make it I did everything that was needed. I rebooted and pushed the volume up while booting, and it went to the blue logo and then into fastboot screen and then stoped there.
My pc (Windows 8) didn't recognized the device while in the fastboot screen as a kindle but as a portable device called "jem-PVT-prod-04"
I rebooted my KFHD pressing power button, and when starting again, I saw the orange logo, then the blue logo and it just got stuck there.
So now I just can get to the fastboot screen (by pressing volume up while its booting) or get stuck in the blue kindle fire logo if i dont press anything.
I would like to add also that while on the fastboot screen , My PC wont communicate with my device. I have the Android SDK installed and could use ADB before this happened.
I have tried the commands -i 0x1949 getvar product and -i 0x1945 reboot as suggested on many posts, but both of them stays in "waiting for device" for ever.
Then i tried using Kindle Fire First Aide as suggested on other posts but after downloading everything it gave me an error about something not matching with my device and what i was trying to do.
In top of that, somewhere I got the impression that I just got stuck in the middle of the procedure and that I could still install TWRP or flash a rom,
So now I don't know if my device is bricked, or stuck in the middle of the procedure or what, but if anyone could help me get back to the stock firmware or to twrp or something other than this two screens (blue logo or fastboot screen) it would be spectacular
thanx in advance.
I'm having the same exact issue more or less, but I can't pass the orange Kindle logo. My computer will recognize the Kindle for about all of 2 seconds, but only as Jem_.... then disconnects so I can't enter fastboot or move forward at all. I'm hoping that someone can help with this.
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Recd msg alert stunts513 to the error while using wallpaper fix 2.1
I am having a terrible time with this Kindle HD 2nd generation table I tried to root. I was following this guys post on You tube and got it rooted but something when wrong when I tried installing the 2nd bootloader and twrp. I ended up stuck with a blue kindle logo. I tried turning it on with the volume button pushed to the left and it went from orange to blue and then to the twrp recovery menu. That was a few days ago, Its been stuck in that mode ever since, there are no back up folders and I think was making the problem worse, as it seems I could do the adb push and now I cant, well at least i couldnt before running your wallpaper fix 2.1 I ran it once and it wouldnt take I dont remember the error, but my table was at the blue logo screen. I remembered reading about running something while you powered the device on because there was an few seconds of access to something, I cant remember so I tried that and unknown to me It appears from these notes i found that I suscessfully installed it - then tried again -then something about the backup??? I am going to cut and paste it here and not do a thing until I hear from you, as I dont want to mess it up. I didnt know the fix worked cause i was watching the command screen and not the side of the file where i have your tool on my desktop.
Here is everything from that run. in the attached file
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes somehow I have twrp and I think when I first got into the bootloop I had adb access but in fumbling around trying to fix it I lost adb access.
If I turn the kindle off, and then push power and do nothing it powers up with the yellow logo and in 4 seconds that log turns blue and it stays that way until i turn it off. In this state checking device manager it shows the device as an android phone, Android ADB interface. If I unplug the device the device manager no longer shows it - If I power up the device and while the logo is still yellow push the volume button to the left it boots to twrp
I re did the notes in a new pdf file I hope you can access them now. I tried looking at them from my post on my pc and got that same access code error. I cant win on this thing tonight,
Thanks for getting back to me so quickly
John
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Click to expand...
Click to collapse
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Click to expand...
Click to collapse
Hope this helps... someone.
pitcrawler said:
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Hope this helps... someone.
Click to expand...
Click to collapse
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Jdoki said:
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Click to expand...
Click to collapse
Yeah, I know there's a lot of information. It took me a long time and a lot of research before I attempted it as a noob myself. An important thing is to follow the tutorials word for word and skip nothing, and cross your fingers.
Got fastboot comunication between PC and KFHD
stunts513 said:
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanx a lot for the quick response! :good: I was finally able to install your great drivers. I had to be quick as you said in some other posts, because the pc only detects it for a little while, when the logo it's still orange on the kindle, I think. After that, and while on fastboot screen, my device manager would detect a Jem-something device, but could not install any drivers on it. So I had to install the drivers really fast while in the orange logo, oh, and had to disable the drivers signature check on windows 8 also.
Now I can use fastboot commands to reboot the kindle, but I can still only get to the blue logo or the fastboot screen.
I guess this means I now can use the kindle first aide to go back to stock and try again for the TWRP and 2nd bootloader. I'll post if I can't make my kindle boot normal again later.
Do you know if this was my kindle being bricked or was it something else?
Thanks a lot again, I was very worried that i wasn't getting anywhere. .:laugh:
Stuck on blue logo!
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
EricMitjans said:
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
Click to expand...
Click to collapse
You need to push a ROM onto TWRP. You should still be able to access TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 be glad you did not hard brick it.

Bricked my Fire TV Stick 1?

Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "
bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.
Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.
One last bump for ideas before putting it into the trash.

Categories

Resources