Bricked Fire TV Stick V1 - Fire TV Q&A, Help & Troubleshooting

Hi,
I think I have bricked my Fire TV stick in a weird way.
I tried to root it using this tutorial:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
I managed to get root and su command working (used the chinese PC version of KingRoot, worked on the 3rd attempt). Next, on step 10, "Install TWRP custom recovery by running the command:sh /data/media/0/montoya_recovery_v1.zip" I stopped, because the adb shell showed the message "device read only or busy" or something similar.
I decided to eject the device and reboot it to try again. After this, the device boots into a splashscreen (Teamwin Recovery Project 3.0.0.7) where I have the choice to press left to boot normally and right to launch recovery. There also is a timer that after 5 seconds will boot into the selected choice.
The problem is that the remote left or right are not working and I cannot choose anything. After 5 seconds (the default choice is boot normally so it should work ok) the device boots into an amazon splashscreen and remains this way.
When I connect it to the computer via usb cable and start adb it recognizes the device, but only on the period that the 5 second timer runs. And some weird characters appear, SU is not working. The reboot command works in adb, but not much use. Also, if I list the adb devices, the serial number appears followed by "Recovery".
I tried plugging it into a normal charger (i do not have the genuine amazon one anymore) and no luck.
I have attached pictures of what appears on the tv with the connected device and on the command prompt console.
Thank you in advance!

b3cks89 said:
Hi,
I think I have bricked my Fire TV stick in a weird way.
I tried to root it using this tutorial:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
I managed to get root and su command working (used the chinese PC version of KingRoot, worked on the 3rd attempt). Next, on step 10, "Install TWRP custom recovery by running the command:sh /data/media/0/montoya_recovery_v1.zip" I stopped, because the adb shell showed the message "device read only or busy" or something similar.
I decided to eject the device and reboot it to try again. After this, the device boots into a splashscreen (Teamwin Recovery Project 3.0.0.7) where I have the choice to press left to boot normally and right to launch recovery. There also is a timer that after 5 seconds will boot into the selected choice.
The problem is that the remote left or right are not working and I cannot choose anything. After 5 seconds (the default choice is boot normally so it should work ok) the device boots into an amazon splashscreen and remains this way.
When I connect it to the computer via usb cable and start adb it recognizes the device, but only on the period that the 5 second timer runs. And some weird characters appear, SU is not working. The reboot command works in adb, but not much use. Also, if I list the adb devices, the serial number appears followed by "Recovery".
I tried plugging it into a normal charger (i do not have the genuine amazon one anymore) and no luck.
I have attached pictures of what appears on the tv with the connected device and on the command prompt console.
Thank you in advance!
Click to expand...
Click to collapse
While the stick is plugged into your computer and it boots to the TWRP selection screen in your ADB / command terminal (with the weird character's you see) using your keyboard type in mouse.
Then use press d then enter. This will highlight recovery and allow you to boot into recovery. You use key presses on your keyboard to navigate in TWRP.
While your in recovery and if you have not pushed the previous rooted zip over do this now.
Make sure you read exactly what your next steps are very close on how to proceed with flashing a pre rooted rom.
If you make a mistake doing this you will brick your stick.

What he said. Welcome to rooting FTV sticks...

Michajin said:
What he said. Welcome to rooting FTV sticks...
Click to expand...
Click to collapse
It worked, my stick is now up and going. Thank you very much, you are a genius!
:highfive:

Hey I got a question. Which fireOS version was on your stick while rooting it? Because I can't wait for a rooting method for 5.2.1.1

Pottkopp said:
Hey I got a question. Which fireOS version was on your stick while rooting it? Because I can't wait for a rooting method for 5.2.1.1
Click to expand...
Click to collapse
I think many of us updated to 5.0.5 and stayed there when news of root methods hit.

Yep. I missed that point and looked for any progress on rooting when my stick already updated itself to 5.2.1.1... But now I won't let it update anymore. Hopefully someone will find a new method soon.

Sorry for the late reply. 5.0.5. is my version

Related

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

[Q] bootloop stuck, can't fastboot, need case open short instruction

Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
lob455 said:
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
Click to expand...
Click to collapse
Does it show up in Device manager? as kindle, android phone, or something else...?
sd_shadow said:
Does it show up in Device manager? as kindle, android phone, or something else...?
Click to expand...
Click to collapse
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
lob455 said:
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
Click to expand...
Click to collapse
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Thepooch said:
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Click to expand...
Click to collapse
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
lob455 said:
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
Click to expand...
Click to collapse
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Thepooch said:
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Click to expand...
Click to collapse
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
lob455 said:
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
Click to expand...
Click to collapse
Android adb interface alone is a detection of fastboot composite is normal boot. This could be due to a partially broken shell try while the device is in recovery not at the bootloader your bootmode is iffy.
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x http://techerrata.com/browse/twrp2/blaze
sd_shadow said:
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x ..................
Click to expand...
Click to collapse
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
lob455 said:
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
Click to expand...
Click to collapse
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.
sd_shadow said:
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
Click to expand...
Click to collapse
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Just place a Rom on your Sdcard and flash it.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Try the mount option in twrp again
sd_shadow said:
Try the mount option in twrp again
Click to expand...
Click to collapse
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.

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.

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.

Categories

Resources