Develop Bugs

[Q] Stuck "Kindle Fire" Spash screen after unrooting

Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.

Does KFU recognize it? If it does you are good to go.

Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.

http://forum.xda-developers.com/showthread.php?t=1644970

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!

Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.

All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!

nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.

Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon

Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.

nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?

[Q] Tried to put Fire back to Stock and now bricked

I looked at almost every thread I could see that sounds like my case but in every one the device is at least being recognized by USB on the computer, in my case it has absolutely no recognition.
I had custom gedeROM. gf didn't like it and so I decided to go back to stock.
within TWRP I did Factory reset, then installed the stock bin file that i renamed to update.zip. Install went through properly so I restarted.
Now it is frozen on Kindle Fire boot screen, and it won't go further. Attaching it to a computer with USB will power the Kindle on but the computer will not detect it, tried on 3 computers, Windows 7 and Linux. I have tried to use all forms of unbricking, everything except opening the Kindle. But since the device isn't being recognized by USB at all on any system I don't know what to do.
With a Factory cable help with this?
Thanks for any help.

slyphin said:
I looked at almost every thread I could see that sounds like my case but in every one the device is at least being recognized by USB on the computer, in my case it has absolutely no recognition.
I had custom gedeROM. gf didn't like it and so I decided to go back to stock.
within TWRP I did Factory reset, then installed the stock bin file that i renamed to update.zip. Install went through properly so I restarted.
Now it is frozen on Kindle Fire boot screen, and it won't go further. Attaching it to a computer with USB will power the Kindle on but the computer will not detect it, tried on 3 computers, Windows 7 and Linux. I have tried to use all forms of unbricking, everything except opening the Kindle. But since the device isn't being recognized by USB at all on any system I don't know what to do.
With a Factory cable help with this?
Thanks for any help.
Click to expand...
Click to collapse
In Linux type lsusb and see if your device is shown. It my be named something weird.
Sent from my Amazon Kindle Fire using xda app-developers app

Did you have adb and fastboot setup on linux when you tried?

I'm pretty sure I did, I used the firekit and that didn't work as well. how do I check if adb and fastboot are for sure running when in linux?

powerpoint45 said:
In Linux type lsusb and see if your device is shown. It my be named something weird.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
when i lsusb, it just sees my usb stick i booted ubuntu from

Installing Amazon's stock update.zip gets rid of FFF and TWRP, so at this point, your only choices are either getting a factory cable (recommended) or cracking open the case and resorting to the USB short trick + firekit.

OK, I have an order for the Factory cable coming so hopefully that will do the trick. Thanks

KF Stuck at Logo - Sorry

I know this has been covered thoroughly in this forum multiple times, and I have really tried to read as many threads as possible before asking.
I rooted my device months ago and finally got a Nexus 7 and want to give my KF to my kids but wanted it stock first. I must have done something in TWRP that removed my bootloader.
I have tried the unbrick tool, I ordered a factory cable from Skorpn (awesome work btw) and by using KFU, my PC can finally see my Kindle.
The problem I'm having is that none of the commands are working and it looks like the bootloader is either bad or completely gone.
It used to turn on and the logo stayed bright. After I used the factory cable it now turns on, blinks, and goes dim.
All the drivers loaded correctly and KFU see's it online.
When I try to reinstall TWRP through KFU it downloads, but is stuck at waiting for device.
***********************************************
* Activating Fastboot (4002) *
***********************************************
2433 KB/s (510876 bytes in 0.205s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
After reading further, I think I formatted too much and wiped the SD card partition. It doesn't seem like there is a bootloader at all.
Did I miss something in all the reading?
Thanks.

So after doing even further reading I found
http://forum.xda-developers.com/showthread.php?t=1638452
I connected the factory cable and the logo is now staying brightly lit, so I assume it's in FB Mode.
I downloaded TWRP based on the link and FFF, but now I don't know what to do with them.
I went to ADB's site and installed SDK, but I'm not sure how to get the cmd portion to sideload TWRP and then FFF.

I'm doing my best to following along in the instructions and went to the ADB site and installed SDK.
I saved it to my C drive but when I try to do the following, along with "adb devices,
c:\Android\android-sdk-windows>
I get:
'adb' is not recognized as an internal or external command,
operable program or batch file.
Update:
NVM, I had it in the wrong directory.
Once I got that figured out, I did an "adb devices" and no devices came back. Of course I have the factory cable connected and I'm not sure if that matters.
Update:
Ok, now I used a standard USB and it sees my device, but now the logo went back to going dim after reboot.

So it looks like my problem is fairly common, however forum searches don't seem to be helping.
It looks like I wiped too much in TWRP.
Now that I finally figured out ADB, I'm confused about the factory cable.
When it's connected ADB does not see my device but the logo is lit bright yellow. When I use a standard cable ADB sees the device but the turns on and goes dim but the logo is still there.
I've downloaded the ZIP files for TWP and FFF, but I can't seem to figure out how to side load them no matter what I do.

I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.

Copcheck said:
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Click to expand...
Click to collapse
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.

leroy329 said:
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
Click to expand...
Click to collapse
No luck with adding persistence.
I get everything to to boot in Linux, followed all the instructions, but Soupkit still does not see my Kindle.
I've tried my factory cable and a regular cable. No luck
Some has changed though because now my Kindle logo light is solid bright whereas before it would blink and dim.
Good luck to you!

Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.

Copcheck said:
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Click to expand...
Click to collapse
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck

Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
When I unplugged the factory cable from the PC and the KF, I could have done 1 of 2 things. Powercycle the KF and hold the power button down to get into TWRP or use a regular USB to side load a ROM and then load it.
Good luck to you, I hope you get it figured out.

Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
If you're getting the Kindle Fire orange and white, you haven't installed the new bootloader. Rerun KFU with the Kindle in Fastboot (using Cable) and select install FireFireFire. This will give you the bootloader to reboot to recovery.
Edit: You might as well reinstall TWRP while you're at it, just to be safe.

[Q] Kindle Fire bricked, have factory cable but can't boot recovery, please help!

Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail

farkuldi said:
Hi. I am really in a jam here. I have read a lot of documentation and still am not getting anywhere. I bought my sister a Kindle Fire for her birthday, and after reading the Kindle Fire for Beginner's Guide, I was able to successfully install Cyanogenmod 10.1 It was working fine, but I gave it some thought and decided she would be better off with the stock software, so I followed the instructions here to revert.
However, somewhere in that process I bricked the device. I went through the installing the Amazon software again in TWRP and told the device to reboot, but it is now stuck on the boot screen and will not respond to adb commands I send it.
I used the Kindle Fire Utility to install TWRP again, and it said it was successfully installed. I tried to boot into it through the Kindle Fire Utility menu, but it is still stuck.
It just so happens that I have a fastboot cable for this, so I plugged it in and tried to boot into recovery by issuing
C:\kfu\tools>fastboot oem idme bootmode 5001
It just says:
<waiting for device>
and nothing happens.
I don't know what else to do. I do think this factory cable put me in fastboot mode because the Windows device manager is showing "Android ADB Interface" (which according to Kindle Fire for Beginners is what it is supposed to say if the drivers are good and I am in fastboot mode), but I do not know how else to make use of this.
I am really stuck here, and I hope someone will take the time to help. My sister's birthday is in two days and I need to get this Kindle fixed and in the mail
Click to expand...
Click to collapse
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.

Socially Uncensored said:
First, welcome to Xda-developers
OK. So lets cover the basics.
http://forum.xda-developers.com/showthread.php?t=1428428
^ Download and run that tool. Its very useful for un-bricking your Kindle
Once that is done, reboot into recovery and wipe every things. (sorry, we're going to start you from fresh start)
I'm going to suggest you try to install this ROM
http://forum.xda-developers.com/showthread.php?t=2103278
The reason being that this one will give you the option to also wipe a few other places (including boot)
Now assuming you still want to keep with stock
http://forum.xda-developers.com/showthread.php?t=2211872
This is basically the stock ROM by its rooted.
Click to expand...
Click to collapse
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!

farkuldi said:
Thank you for your reply! I ran the Kindle Fire unbrick tool with the option "Stuck at logo," and it said "Congratulations, your Kindle should be unbricked. However, nothing had changed. So I ran it with the option "Other . . ." It said:
Code:
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
This part might take a while . . .
< waiting for device >
I have left it like that for ten minutes now and nothing is happening. Do you think it is working? I'll leave it alone for an hour or so I guess but I'm wondering.
BTW, for this I just used a regular USB cable and not the factory one. Is that right?
Thanks!
Click to expand...
Click to collapse
The unbrick program didn't work. It just stayed there t <waiting for device>. How can I use the fastboot cable to fix it?
Thanks.

I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC

ezproxy said:
I had the same problem before. It always says no device found. I tried different PC, finally in my XP PC it is detected and new ROM flashed in
Maybe you should try different PC
Click to expand...
Click to collapse
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.

farkuldi said:
I was thinking the same thing. Unfortunately I don't have another PC running Windows. All my others are running Linux, and I don't know how to get the drivers working.
I think I will borrow a laptop from a friend tomorrow and see if it works. It is my sister's 17th birthday today and her present is late!
In the meantime, though, does anyone know how I am supposed to use this fastboot cable? I have looked around and I see a lot of tutorials about how to unbrick without a fastboot cable, but none saying how to do it WITH one. I thought the cable was supposed to make it easier?
Thanks for the help.
Click to expand...
Click to collapse
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159

ezproxy said:
First of all, Happy Birthday to your sister!
I think you may need install the firefirefire utility first to help you out of bootmode sucking. After you successfully reinstall the TWRP using unbrick utility, you need change the fastboot mode to normal boot, the firefirefire can help you choose,
here is the information may help you : http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
I'd say you didn't read the previous posts.

Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.

farkuldi said:
Well, now the Kindle Fire is no longer being recognized by my computers. I borrowed another Windows computer like I said I would, but when I plug in the Kindle, the Device Manger does not even register it. Also, usually when I plug it in, the computer will realize I have plugged in a usb device and respond with that little pop up at the task bar, i.e. to let me know it sees a usb device and is trying to install driver, was not able to install drivers, or whatever. But now nothing. The computer doesn't even see it.
I have tried it on two different computers with three different cables and it's the same thing. I have restarted the computer and reinstalled the drivers over and over again and there is no difference. What is going on? It was seeing the Kindle fine before I tried the Unbricking Utility.
Click to expand...
Click to collapse
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.

Socially Uncensored said:
I'm assuming you know for sure this was a 1st Generation Kindle, right?
I had this problem once and basically formatted my computer. The driver was the issue and I couldn't uninstall it completely. Using my drivers solved this. I get the feeling you're still trying to use the drivers that came with the utility (don't they're often trouble)
However, assuming you are using the correct drivers (the ones I linked for you).... Boot into TWRP and wipe everything. Don't just use the general, click the advance options and wipe everything (selecting all options manually).
No connect your Kindle and don't worry about it not showing up yet....
Mount your SSD (should suddenly find your kindle) and upload this ROM
http://forum.xda-developers.com/showthread.php?t=2211872
Now if you can't even load TWRP (when you turn on the Kindle, you'll need to hold the power button to bring up the menu, then quickly hit it a few times until its on recovery).... But if you can't load TWRP at all, its time to get a factory cable.
If you have a factory cable and still can't find the device (and assuming you're using the right drivers, on a fresh install) .... As someone else who knows how to do this. Because past that, all hope is lost.
Click to expand...
Click to collapse
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?

Gon Rouge said:
Hi, My name i Jonah and i have a Kindle fire (5th generation) That came stock with Amazon's Fire OS Bellini 5.1.1. I tried to flash Cm12 with the app FlashFire (https://www.youtube.com/watch?v=NaCBSuUuhRE&spfreload=10) and during the installation i noticed it stopped for a while and didnt do anything. So i waited then 10 minutes later i decided to turn it off and turn it back on to fix it, when it started to boot up it showed the Cm logo just like as if it was running Cm12. So i waited, maybe 5 min at the most and it still would not turn on. So i turned it off, went online to see ho to get out of a bootloop. Rootjunky said to Turn your Kindle off and run ADB and Fastboot as a command from where you installed your drivers. Then he said he said to enter Recovery mode by pressing vol down and the power button. It is suppose'd to say Recovery-Mode in the corner but it just kept showing the Amazon logo. Im worried i screwed up and broke my new tablet, i can't return it because it's against Amazon's policy to root or mod any content of Amazon's, Plus ADB isn't working i can only access fastboot. I tried fixing it with the stock charger also but how do i know what kind of Android charger should i use?
Click to expand...
Click to collapse
post in correct forum
Fire Index: Which Amazon (Kindle) Fire Do I have?

"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.

jerry777888 said:
"Failed - Virus detected" Chrome wouldn't let me open it - if you're for real, please re-post the software.
Click to expand...
Click to collapse
Repost what?
Sent from my ocean using XDA Labs

Kindle Fire HD 7 bootloop and no ADB

Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!

Maric98 said:
Hi guys,
First of all I am new to this forum but i have read almost every thread about this subject but i can't seem to find my exact situation.
So yesterday I decided I wanted to root my kindle fire HD 7 and put Cynangonmod on it. So i found this video of a guy explaining it and I downloaded the files he provided and I followed his steps.
That is when the first problem came up. He wanted me to install the ADB drivers which I couldn't get done. It told me something like '' could not install the drivers, please install them manually ''.
Thats is when I came to you guys and I noticed there were a lot of people having the same problem. I had to download some other replacement drivers and install those but even that didn't work so I was basically out of luck.
After a couple hours I managed to get the drivers functioning after deleting them and installing them again. I was surprised this actually worked because I did try that before.
But anyway the drivers were working and my kindle responded just like in the video. I followed the steps in the video and I was happy to see some progression. So my device basically was rooted at this point. So just like in the video I transferred the recovery files, CM-11 and the GAPPS I downloaded to my Kindle while strictly following the steps in the video. Next up I used ES file manager to open up the APK file and install it. At this point I exactly followed the tutorial by selecting the right files and checking the right boxes in the Fire Flash menu. Everything looked OK.
I flashed and installed the script like in the tutorial and pressed rebooted into recovery. Unfortunately this is when the party was over.
Instead of the device booting up and saying Kindle Fire with Fire being orange and turning Blue after a couple seconds, my device just booted without turning blue and was basically looping the hole time.
This was a real bummer since I was so happy that I luckily passed the hole ADB driver issue.
Now when I connect my Kindle to my computer nothing happens....just nothing...my computer doesn't even recognize my Kindle at all. So I decided to search the web for this bootloop problem and I downloaded several utility's which should unbrick my Kindle. But since my computer doesn't even recognize my Kindle actually being plugged in these tools will never work anyway.
I have no idea what is going on but it seems like it's the ADB drivers not functioning again? and what I should do now? Or can I just throw my Kindle in the trash?
This is the video I used on YouTube. You might want to watch this to understand my situation.
/watch?v=PVuvR-hHOLE
The files I downloaded are in the description of the video. I do not have the unbrick utilities and the replacement drivers anymore. But that doesn't matter now anyway since my computer doesn't recognize my device.
Please help me guys!!
Thanks!
Click to expand...
Click to collapse
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.

stunts513 said:
Have you tried getting into recovery manually? Turn the device on, immediately hold down volume up while the logo is still yellow, keep holding until a few seconds after it turns blue, it should go into twrp if you flashed twrp correctly. If worse comes to worst you can always use a fastboot cable to recover from this. Also adb is not supposed to work when you are at a bootloader screen, at most you probably could access fastboot if the logo turns blue, because the device may breifly show up as a tate device with second bootloader installed, normally it wouldnt. You would have to isntall the drivers in that brief moment or run a ubuntu live cd to do it. Anyways tell me if you can get into recovery.
Click to expand...
Click to collapse
Thanks for your reply!
I have actually tried to holding down the volume button when it turns on but it doesn't do anything. It's like the device is ignoring me and just keeps looping.

Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Could be the recovery partition is screwed up but that would only happen if you had a bad recovery image. This is going to get a bit complicated. I recommend using a Ubuntu live CD for this because you won't run into a very annoying driver issue if you use Ubuntu, though they just released a update and I don't know for sure if the package names are the same. Use the latest Ubuntu if you choose to do this or you could simply get a fastboot cable or the blackhat fastboot adapter that goes in between the kindle and the cable. You simply need to try to flash a recovery IMG through fastboot. It should be pretty straight forward, no need to return to stock kindle os to fix this assuming my theory as to why its doing this is correct.
If you wanna use Ubuntu then grab the latest version from their site(think its 14.something) and either burn it to a CD or make a bootable USB using either their instructions, or my preferred utility unetbootin, then boot up into Ubuntu live os and open the settings and look for something about software update. I haven't upgraded to the latest distro so this bit of info is a bit guess and check. If you find software update then make sure all the download from internet boxes are checked then hit close, if it asks to reload choose yes and ignore the first command i'm about to mention. Open a terminal, run these commands in order:
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot android-tools-adb
sudo fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in with the power off, it should then go into fastboot since you have 2nd bootloader installed. Normally this method wouldn't work without a second bootloader unless you are on the 8.9". From there you can open the 2.7 zip of twrp and extract the img file from it to your home folder and run:
Code:
sudo fastboot -i 0x1949 flash recovery recovery-image-name-here
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
That actually sounds really difficult.
Just to be clear there is no way to do this on just Windows 7 or OSX? Instead of installing Ubuntu ( which I am not familiar with ). Also could you explain a bit more about the functions of those fastboot cables / adapters because I don't really understand what they do and are you sure those will work with the status of my device? I assume as soon as I get that cable / adapter I Need to plug my device in to the computer and have to get it working via some commands? But anyway is there a way I can stick to windows or mac OSX ( Which I did not use before in the rooting process )

, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
, mac os, normally I would hate mac os just because its a bit nooby and i don't agree with apples policy towards open source(or the lack of) and finding loopholes in whatever the license the unix kernel was under, but this time it may actually be useful, mac is is based on a Unix kernel, which is in a manner similar to the Linux kernel that Ubuntu uses. If you have used a mac then using Ubuntu would be easy, but in this case you shouldn't need to because it should load the drivers up immediately like in Ubuntu. Just grab the android SDK for mac os since i don't think the Linux binaries are compatible. Try placing the extracted android SDK on your desktop, and put previously mentioned recovery img file in the same folder as the fastboot command, open a terminal from applications>utilities and CD into the directory on the desktop that fastboot is in, and try running the fastboot commands I mentioned. Not sure if sudo is needed or not on a mac.
OK as to fastboot cables/adapters, basically you plug your kindle into it and the PC, and your kindle immediately kicks into fastboot mode. You could easily repair it fro windows in this manner since the Tate device would hang around so you could update it's driver without much difficulty. Tech locally you could try the same on windows without a fastboot cable but the device would only appear for a few seconds before it disappears making it hard to install the drivers in that time frame.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks I hope my mac will get the job done. It would make it a lot more easier than going linux I think.
Ok. Ill try it on my mac. I will now download Android SDK and place the extracted file on my desktop. I guess I install all tools and all that. And keep you up-to-date.
I downloaded the SDK and placed the folder to my desktop and opened the SDK manager by going to sdk / tools / android and installed SKD tools and SDK platform Tools. Although when i downloaded it it gave me a log that told me something like '' Stopping ADB server failed (code -1). '' And now I get a red checkmark. I don't know if getting a red checkmark is actually good. And i don't know if it's installed now and if the error message matters.