Develop Bugs

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] recovery mode on stock rom?

Ok, a friend of mine dropped my Epic 4G Touch and cracked the screen. Screen is totally black and as far as i can tell, the touch interface doesnt work. The phone turns on fine and i can hear it boot up and receive email, etc, but i cant figure out how to access its internal memory. I know that you have to turn on storage mode to get the usb mount option to work and i have adb installed on my mac, but it never sees the device. I was told I could start the phone in recovery mode by holding the volume up button, then hitting the power button, but it doesnt seem to make a difference and it just boots regularly. Am i missing something? Is there even a recovery mode with the stock firmware/rom from Sprint?
Any help is appreciated. Thanks!

If it is already rooted and usb debugging is enabled. You should be able to use program such as Android Commander to pull the files from the phone. Another option is to odin into an ICS rom, I believe on those MTP is enabled by default on ICS builds and the phone should mount as a drive immediately when you plug it in. It should be possible to odin with just using the power and volume keys.

As i mentioned, its stock, so its not rooted and its using gingerbread since ICS isnt out from Sprint yet for it (not OTA at least). What does ODIN mean? Am i doing the keys wrong to get into recovery mode? I mentioned the method with the volume up key and power and not getting anywhere with that. Did you actually read my entire post?

First off, wrong section but anyways there is a recovery mode when running stock which you can access by 1. Turn off phone 2. Hold volume up and power button at the same time probably for about 5-10 seconds.
Sent from my SPH-D710 using Tapatalk

Woo hoo! Thanks! Guess i just wasnt holding both buttons down long enough. Did a 10 second count and let go. Then waited about 10 seconds and plugged in usb. Then ran "adb devices" and it showed my device. Then i simply ran "adb pull / phonebackup/" and now I have all my files. Thanks again!

MACscr said:
Woo hoo! Thanks! Guess i just wasnt holding both buttons down long enough. Did a 10 second count and let go. Then waited about 10 seconds and plugged in usb. Then ran "adb devices" and it showed my device. Then i simply ran "adb pull / phonebackup/" and now I have all my files. Thanks again!
Click to expand...
Click to collapse
No problem, glad I could help.
Sent from my SPH-D710 using Tapatalk

Shoot, so i guess i cant access the /data folder when in recovery mode? Thats pretty much the most important section as far as i know as that contains text messages and call logs, etc. hmmm. Any suggestions? Is it possible to root the phone from just adb while in recovery mode?
This is what i gest for not having my backup app setup on my phone. I installed, it, just never set it up. Doh!

MACscr said:
Shoot, so i guess i cant access the /data folder when in recovery mode? Thats pretty much the most important section as far as i know as that contains text messages and call logs, etc. hmmm. Any suggestions? Is it possible to root the phone from just adb while in recovery mode?
This is what i gest for not having my backup app setup on my phone. I installed, it, just never set it up. Doh!
Click to expand...
Click to collapse
You probably can using some commands in adb but a bit too much for what I know. I'd suggest going to the e4gt irc channel. Go to webchat.freenode.net channel is #ics-dev-e4gt hopefully a dev is in the channel and can help you out or someone can stop by this thread before then.
Edit: try the command "su" then enter and then "adb devices" see if that helps with anything.
Sent from my SPH-D710 using Tapatalk

Simply odin just the el26cwm kernel only that should be enough to allow root commands since it's an rooted "insecure" kernel. It should not touch your data.

[Q] manually reinstall the OTA update.zip?

Here's my situation and why I ask, everything was up and running fine. Side loaded some apps and had wireless adb working. I got the OTA update the other day and it wiped out some system side loaded apks. So I got everything back the way I want it (same as the first time...), still working fine. Then wanted to get wireless adb woking again so just push an edited copy of build.prop I had from before the update. Since then I cannot get any video output and the control will not pair (all lights just blink a few times). tried power cycling a few times, different hdmi cable, ect...nothing. The good news is that I can still connect with adb over usb. Since this issue started when I pushed the old build.prop I tried pushing the correct build.prop but still no luck.
Is there any way to manually re-run the OTA update? maybe push it to a directory and reboot? press and hold power for 30 sec?... Or any other ideas?

So I am trying to get into stock recovery by "adb reboot recovery". but don't have any video to see where im at. I then pushed RC-OUYA-1.0.248-r1_ota.zip to the sdcard, then copied over to /data/ and tried to use "recovery --update_package=DATA:RC-OUYA-1.0.248-r1_ota.zip" but looks like im not actually booting into recovery as I get recovery not found...

Here's my best instructions on how to fly blind on this, good luck...
1. unplug the console
2. plug it in and turn it on, the light will come on. make sure adb works
3. adb reboot recovery. the light should flash
4. adb will not work at this point, you have to put it in sideload mode first. on a usb keyboard press the "home" key, wait 2 seconds, press the down key, then press enter.
5. if you have a plug in sound you should hear it now, and "adb devices" should return the device id and say "sideload" beside it.
6. type "adb sideload <ota.zip path>" and hit enter.
7. wait plenty long. like a really long time just to make sure. like 10 minutes at least, even though it should only take 2.
8. Once it's had enough time to complete the flash, you can pull the power plug, plug it back in and power on.
again, good luck.

professorpoptart said:
So I am trying to get into stock recovery by "adb reboot recovery". but don't have any video to see where im at. I then pushed RC-OUYA-1.0.248-r1_ota.zip to the sdcard, then copied over to /data/ and tried to use "recovery --update_package=DATA:RC-OUYA-1.0.248-r1_ota.zip" but looks like im not actually booting into recovery as I get recovery not found...
Click to expand...
Click to collapse
Check out this thread on the ouya dev forums that says how to boot into recovery . I think you just have to hold down print screen as ouya starts but not sure
forums(dot)ouya(dot)tv/discussion/1380/recovery-mode
Also the reason why skywalkers method night not work is because ouya changes the default key layout ("Generic.kl" in /system/usr/keylayout/) to map the home button on keyboards to "move_home" which navigates to the top of a page rather than the android home function. In order to fix this, you can pull the kl file using adb and edit it and put it back or copy the kl from another android device. The android command is "HOME" for most devices but might be "HOME ALT" for ouya because they changed it to work with a double press of the button.
I hope this helps sorry for the weird link I never post on xda and don't have permission to post links...

Thanks for the extra info, i just posted what worked for me

after looking at post at http://forums.ouya.tv/discussion/1380/recovery-mode it sounds like the device might already be in recovery mode. they described it as sometimes having the red triangle but most of the time a just black screen. Sounds like mine, at first I would get no inuput on the tv, now I'm not getting no input on the tv, just a blank black screen. I tried just hitting home to see if a menu would come up but it didn't. tried the sysrc+i for a minute and then home again... just a black screen still. O well were would the fun be if it just worked! lol. I will have to play with it more after work. thanks for the tips,
*should the num lock led work? I used an old dell usb keyboard but num and caps lock leds didn't work, so not sure if the board was working at all...

It Works!
Got it working! I pushed the edited Generic.kl with the "HOME" fix and I was getting tired of running back and forth from the computer to the TV so I hooked it up to an hdmi monitor and as soon as I did rebooted into recovery the red exclamation come up and I was able to then read the recovery menu and just adb sideload the OTA. I wonder if its some kind of resolution issue with the TV? O well off to break it again! Thanks for the help!

Awesome! Glad you fixed it. If you want to break it again a couple of us are working on a recovery and could use beta testers eventually.

professorpoptart said:
Got it working! I pushed the edited Generic.kl with the "HOME" fix and I was getting tired of running back and forth from the computer to the TV so I hooked it up to an hdmi monitor and as soon as I did rebooted into recovery the red exclamation come up and I was able to then read the recovery menu and just adb sideload the OTA. I wonder if its some kind of resolution issue with the TV? O well off to break it again! Thanks for the help!
Click to expand...
Click to collapse
Sick. I'm glad that worked for you.. another tip if you want to use a keyboard with your ouya more often. on ouya the "HOME" function also opens the menu (they did this so that they could have one button do both(tap/double tap)) if you want the actual "HOME" function, you need to remap to kl to "HOME ALT".

sonofskywalker3 said:
Awesome! Glad you fixed it. If you want to break it again a couple of us are working on a recovery and could use beta testers eventually.
Click to expand...
Click to collapse
Sure hit me up when you're ready. I've been following the other CWM thread...

Thanks for the information I used a few days ago to reinstall OTA because i had problems with android drivers.

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

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.