Develop Bugs

rooting trouble

I've rooted and unrooted kindle fires a couple times before but have had trouble this time around. Like before, I used the Kindle Fire Utility but as it went though the process, I was notified that the md5 check on twrp recovery failed and it asked me to press any key to continue. After I did, the utility shut down with only the firefirefire bootloader installed. Upon rebooting the kindle, which still works fine, I tried to run the utility from the top but it keeps failing when it tries to boot into fastboot to install twrp, always saying waiting for device. I also tried resetting the kindle to get rid of firefirefire and start again but resetting the kindle through stock settings won't get rid of the custom bootloader.
So my main problem appears to be trouble installing twrp. I have adb setup and working and was wondering if anyone could point me in the right direction.

Attach your device run option for twrp if it hangs <waiting for device> hold the power button down while attached till its off then simply power it on at that point it should send twrp.
Edit: make sure you have allowed installation from unknown sources.

Thepooch said:
Attach your device run option for twrp if it hangs <waiting for device> hold the power button down while attached till its off then simply power it on at that point it should send twrp.
Edit: make sure you have allowed installation from unknown sources.
Click to expand...
Click to collapse
I enabled installation from unknown devices but its still "waiting for device" to boot into fastboot. I've also tried rebooting it multiple times and re-installing the drivers as the utility suggests but I'm getting the same problem.

Do your drivers indicate android composite adb interface? Does KFU show your device online boot mode 4000? Lastly did you do as I suggested?

Not sure why, but I tried a different computer and that ended up working. Thanks for the help.

[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.

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.

Bricked Fire TV, what are the options?

Well this day has been a long time coming and it finally happened
In short I had reflashed my device with RBox prerooted rom via TWRP without any issues. In order to use certain applications I was using "hide my root" only to find once the su binary was hidden the application was unable to restore.
When I shouldve reflashed the rom I decided to take a short cut and install Super Su directly via TWRP, big mistake.
Device is now stuck on the Amazon logo (not the colourful splash screen) I've attempted to access the system recovery menu via the keyboard hotkey but the keyboard is unresponsive, in fact there seems to be no power coming from the USB. Which got me thinking, this is more than likely related to drivers, perhaps using an older keyboard with P/S2 and a USB adapter would work. I am yet to try this.
Any advice?
Would opening the device and unsoldering certain components perhaps initiate a reset of some kind?
Just throwing ideas around at I'm stuck with a paper weight
Any suggestions?

http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
This should help. The shorter option didn't work for me. I've used you the longer on mine and two other peoples ftv. It's worked every time.

I have a Fire TV 1, do you know of there are any recovery images available for this edition

Amazon fire phone stuck at boot logo and cant access to recovery mode.

I was recently planning to install Miui 7 on my Fire Phone. So, i installed safestrap 4.01.
1. I opened safestrap recovery mode
2. I wiped (First screen of Safestrap recovery mode)
3. I installed Cleansystempartition.zip
and then i don't know why, but i lost my mind and decided not to install Miui 7 and i went back and clicked on reboot.
So, now my Amazon Fire phone is stuck at boot logo and i can't even enter recovery mode.
It doesn't respond when connected to PC. It is charging and again when i boot again get stuck on boot logo.
Please reply ASAP.

Erictic67108 said:
I was recently planning to install Miui 7 on my Fire Phone. So, i installed safestrap 4.01.
1. I opened safestrap recovery mode
2. I wiped (First screen of Safestrap recovery mode)
3. I installed Cleansystempartition.zip
and then i don't know why, but i lost my mind and decided not to install Miui 7 and i went back and clicked on reboot.
So, now my Amazon Fire phone is stuck at boot logo and i can't even enter recovery mode.
It doesn't respond when connected to PC. It is charging and again when i boot again get stuck on boot logo.
Please reply ASAP.
Click to expand...
Click to collapse
What you need:
1 x USB Cable, 1 x PC, 1 x Fire Phone update bin, adb and correctly installed drivers. GOOGLE
How too:
1. Ensure phone is turned OFF
2. Plug the USB cable into your phone.
3. Press and keep held the Volume UP (+) button only
4. Now plug the other end of the USB cable into the PC. (keeping the Volume UP held)
5. The phone will now boot into recovery and you can let go of the volume button.
6. Select "apply update from ADB"
7. type
Code:
adb sideload your-firmware-version.bin
Use google or search the Fire Phone threads on how to install adb and drivers etc etc.

bigrammy said:
What you need:
1 x USB Cable, 1 x PC, 1 x Fire Phone update bin, adb and correctly installed drivers. GOOGLE
How too:
1. Ensure phone is turned OFF
2. Plug the USB cable into your phone.
3. Press and keep held the Volume UP (+) button only
4. Now plug the other end of the USB cable into the PC. (keeping the Volume UP held)
5. The phone will now boot into recovery and you can let go of the volume button.
6. Select "apply update from ADB"
7. type
Code:
adb sideload your-firmware-version.bin
Use google or search the Fire Phone threads on how to install adb and drivers etc etc.
Click to expand...
Click to collapse
Thanks for your time, but i couldn't understand how ADB is used. I installed adb drivers (tried bunch of times) but can't figure out how to do steps you suggested.
Could you please elaborate in detailed step-by-step, or provide me some revalent link so that I (noob) could understand easily. Once again thanks for help !
Code:
Is there any way i can ensure that proper drivers are installed for my Fire Phone?

Since i understood how adb is used, I categorized further remaining problem into two type:-
1. If I hadn't installed right drivers...
I tried installing driver from different source but i failed (i guess).
So anyone can provide me link for Drivers for Fire Phone?
2. If i have installed right drivers then :
I tried steps as you suggested but my phone won't boot into recovery mode. When i connect Phone to my pc holding volume + , It shows charging symbol as usual.
If i am doing the process in wrong way, please correct me. I will be waiting for helps...:crying:

@Erictic67108
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62768812
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62844581
Firmware for sideload you can download from Amazon. Your need last version.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550

Kramar111 said:
@Erictic67108
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62768812
https://forum.xda-developers.com/fire-phone/help/cm-11-to-fire-os-question-t3198620/post62844581
Firmware for sideload you can download from Amazon. Your need last version.
https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.

Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
If Fire Phone detected in Windows Device Manager with PID 9008 you can't do anything (as i know). PID 9006 give you a little chance.

Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
Talk with amazon for warranty, if you are from europe, talk with amazon.de, you will get a new one, but u must return to amazon germany the bricked fire phone.

Erictic67108 said:
I cannot go to recovery mode. I tried many times/ways but i couldn't access. Please help.
Click to expand...
Click to collapse
Your only hope to revive this phone is to get into the stock recovery.
If you wiped the stock recovery or messed with it then your screwed as there is no PC flashtool like odin, spflashtool, etc etc that works on the fire phone that I am aware of so you need the stock recovery to be functional.
To get into recovery re-read post #2 HERE very carefully on how to do it. :fingers-crossed:
There is no need to PM me just simply quote me in this thread and I will then get notified.
You also need to provide as much info as possible things such as screenshots, photo's, Videos, logs etc etc as these will help when people try to assist you.
Once you are in stock recovery we can move on.

I quit guys. I just can't get that thing on recovery mode. I tried several times, tried other ways but nope. My phone is not giving a damn ****. Its just gets stuck on boot screen logo. That's all. I guess, i won't get my phone returned/exchanged since had i rooted it which violates its warranty.

Am having thee same issue
Erictic67108 said:
I quit guys. I just can't get that thing on recovery mode. I tried several times, tried other ways but nope. My phone is not giving a damn ****. Its just gets stuck on boot screen logo. That's all. I guess, i won't get my phone returned/exchanged since had i rooted it which violates its warranty.
Click to expand...
Click to collapse
i also quit gyz i tried almost every thing but its stuck on amazon logo

Weirdly enough -my gfs fire phone started exhibiting the same exact issue just yesterday(amazon logo blinks on start up and doesnt go any further no matter how long you wait) and this is the first link google gave on the problem. Did anyone find a resolution to this? She loves this phone and I already replaced battery once few months ago.