(Keep in mind all of this is happening without a OS on it after the sentence where i decied to format) New to the forums and still noobish at flashing roms and the like. But here is my delima, I had a kindle fire HD that i got years ago and flashed properly with the 2nd boot loader, TWRP ( I think at the time the version was like 2.7.0.0), and Pac-Rom, well wanting to try the Cyanogenmod and other roms, being a complete idiot I decided that I would format the device completely and flash a new rom and gapps because I have just had more success flashing that way. Anyway, I finish and was looking at roms on XDA and noticed that TWRP finially got updated to 3.0 so I assumed that I would finially get mass storage support over usb, like a flash drive. well that didn't end up working still, oh well no biggie i have used ADB a few times to push some roms over. So I find out ADB had a message to the extent of when I did the ADB devices command , the device was unauthorized. So I thought crap something must have gone wrong when I was updating to the new version, so ended up fastbooting into a version of TWRP 2.8.something, and that worked but my device was still unauthorized, so restarted, and now its in some odd boot loop, like the kindle fire logo will only stay up for a few seconds then shut down immediately, and just keep repeating like that, the blue logo won't show up and I cant boot into fastboot or into TWRP.
Does anyone know what went wrong or how to fix it. Huge thanks if you can!
Related
Hey guys, I've been working on this all day, finally got cm10.2 and gapps installed. I was in stuck booting into TWRP, but then sideloaded cm10.2 and gapps, I thought I was finally done... then when it loads up it has the orange kindle Fire logo, then has a brief "noise" sort of affect on part of the screen, then after that it just has a vertical sort of flashing line of blue down the center. Anyone have any idea whats going on? I've been doing some research and I cant find anything about that... if there is already an established issue and thread, please point me there, but otherwise...anyone know whats going on? I'd really rather not have to get the factory cable, mainly just because of the shipping time, but can if thats needed.
EDIT 1: It wont actually do anything when its stuck after the kindle fire logo, its just black w/ the line. Lately it hasnt even been displaying the blue line (more like whatever color it feels like though). I cant use either ADB or fastboot commands using KF First Aid either.
EDIT 2: Just realized I forgot to say some important info, sorry. I have a KFHD7". I followed some XDA tutorials and only really had trouble right after I sideloaded my CM10.2 rom, and thats the problem I'm having right now.
EDIT 3: I did some more testing. I think I sort of got into fastboot mode, but no "Fastboot" logo like I'm used to. I have the kindle off and unplugged,then tried fastboot -i 0x1949 getvar product, and got "Bowser-04". From what I can see, there is really nothing on Google about this so I'm assuming thats not supposed to be there. I tried to take this one step further and flash the right TWRP recovery 2.6, but it just hangs on <waiting for device>. So it seems like it is ALMOST there...but not.
FINAL EDIT: Fixed. For anyone else having this problem, I used the little bit of actual fastboot mode I had to give the fastboot command to load into fastboot (reboot-bootloader) and then it would load me into actual fastboot w/ the "Fastboot" logo on the screen, but that would only last a couple of seconds. I was then able to use the http://forum.xda-developers.com/showthread.php?t=1951254 and restored img/boot/etc, then installed stock recovery and cleared data/cache. Now it actually loaded up and I have a normal kindle again! I'm going to reinstall the RIGHT stuff and not have this happen again now.
Hi!
Device Info:
I have a rooted Kindle Fire HD 7" running CM11 with TWRP 2.7 running as a recovery. I have had the tablet for approximately a year and a half, so hardware issues from age wouldn't be overly unexpected, but not necessarily expected either.
Background Knowledge:
(Note: The following has happened before in CM10.2, but disappeared upon updating to CM11)
One week ago...
-Fully functioning tablet running CM11 with TWRP 2.7 recovery set up.
Four days ago...
-Device begins to randomly shut down about once an hour
-Later in the day it begins to shut down soon after I reboot it (as soon as 5 minutes)
Two days ago...
-Death
-Not really, but the device shut down a couple seconds after fully turning back on
My Response:
My first discovery upon looking into this problem was that fastboot was fully functioning and seemed to be unaffected by the shutdowns (I assume they were caused by maxed out RAM). I attempted to boot into recovery, only to find that it was unavailable, and booted into system instead. I then decided to flash TWRP again. I made the stupid mistake of deciding to use a brick-fix tool instead of just doing it myself. Unfortunately, I just opened the first file that looked right in my Android directory, which happened to be a tool designed for Kindle Fire HD 1st gen. I am not entirely sure what happened, but I assume it wiped everything it could get its hands on and put in an incorrect replacement.
The Actual Issue:
The kindle is now throwing a fit. Now,when I turn it on, it launches the stand Kindle Fire logo, shifts to the Fastboot logo, then turns off.. or at least the screen does. When I press the power button after this, nothing happens. I must hard shutdown in order to even activate the pathetic turn on and fade action. Next, I plugged it into the computer, planning to fall back on my amateur knowledge of fastboot, only to find that the fastboot logo means nothing (probably). When I plug the device into the computer, I head the plugged in chime, then exactly 3 seconds later, the disconnect chime. This is the only indication I have that anything is happening, as the screen is off. The fastboot logo either means nothing, or the three seconds is not long enough to establish a connection to the computer.
Help? Anyone?:
I apologize to come on here acting like a noob who panics the moment he feels discomfort and does no research of his own.
Before I posted I searched the best I could to find any issue similarish to my issue and come up with two, only one sounding similar at all:
http://forum.xda-developers.com/showthread.php?t=2729536 - Similar issue, but not really the same symptoms. The only real similarity is the device.
http://forum.xda-developers.com/showthread.php?t=2421487 - More similar, even kind of used my same description. The symptoms are not the same, the major problem is that I cannot establish fastboot connection. (And device is not the same)
Thanks for any help that can be offered!
I would save a "fastboot -i 0x1949 flash boot boot.img" and flash the boot.ing from the cm 11 zip, it should attempt to flash as soon as the kindle kicks into fastboot. If anything it might help fastboot from freaking out.
Sent from my LG-P769 using Tapatalk
Thanks, I'll try that. I'll update after I try it.
Update:
Thanks! That worked perfectly! It stops the device from fading, allowing me to flash a new ROM. To note to anyone else who might have this issue, the command will only send upon the initial boot. Any of the following connects/disconnects will not work.
Sent from my Nexus 5 using Tapatalk
Follow-Follow Up:
Flashing the boot img from CM11 works great at pausing the bootloop allowing me to communicate with fastboot. Unfortunately, upon flashing stock amazon system img and TWRP recovery, I am still unable to launch into either of them. Whenever the kindle reboots, the "extreme bootloop" begins again, forcing me to flash the boot img again.
Should I be trying to get a hold of the stock bootloader from Amazon? (And if so, would you have any suggestions as to where I can grab it? I have thus far been unable to find it)
Thanks for any help!
Sent from my Nexus 5 using Tapatalk
Its probably from the selinux xattribs left over on /data from cm 11, Amazon's kernel doesn't have selinux support and crashes/freaks out when it sees them. You would have to do a internal storage wipe to get rid of them if flashing back to amazon os.
Sent from my Amazon Tate using Tapatalk
Would erasing userdata/system effectively remove it?
(Sorry for my ignorance)
Sent from my Nexus 5 using Tapatalk
No need to wipe system, only user data hence why I said if twrp is still acessable to do a internal storage wipe, it wipes userdata.
Sent from my Amazon Tate using Tapatalk
Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
Regards
KP
kpugh162 said:
Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
Regards
KP
Click to expand...
Click to collapse
i have the same problem and there seems to be no way to get the kindle in any state to do anything, all I've found out so far is that its stuck trying to factory reset and there should be a way to reverse this, i hope someone can give us a solution or i might as well call my kindle a paperweight.
laharl_chaos said:
i have the same problem and there seems to be no way to get the kindle in any state to do anything, all I've found out so far is that its stuck trying to factory reset and there should be a way to reverse this, i hope someone can give us a solution or i might as well call my kindle a paperweight.
Click to expand...
Click to collapse
Thanks for letting me know, I purchased a factory cable today. Seems to be recognised by my laptop, but the kindle doesnt go into fastboot. There seems to be a few people with this problem. I've not seen any help offered yet. I'm not holding out much hope, doesn't seem any way to communicate with it.
Where did you get your info?
kpugh162 said:
Thanks for letting me know, I purchased a factory cable today. Seems to be recognised by my laptop, but the kindle doesnt go into fastboot. There seems to be a few people with this problem. I've not seen any help offered yet. I'm not holding out much hope, doesn't seem any way to communicate with it.
Where did you get your info?
Click to expand...
Click to collapse
i've found out a lot about bootloop issues and in most cases it seems like the first thing needed to fix the problem is a factory cable, i didn't get mine yet so i can't see if it will work but since your pc can see your kindle now you can try out kindle fire first aid 4.1.88-beta.
let me know if it works for you.
laharl_chaos said:
i've found out a lot about bootloop issues and in most cases it seems like the first thing needed to fix the problem is a factory cable, i didn't get mine yet so i can't see if it will work but since your pc can see your kindle now you can try out kindle fire first aid 4.1.88-beta.
let me know if it works for you.
Click to expand...
Click to collapse
I'd already tried that. Seems because the kindle is not fully booting up then kindle fire first aid doesnt recognise it. Unless what i've been sent is actually a normal usb, then I dont see any way of sorting this. I'll wait to see if you have better luck
kpugh162 said:
I'd already tried that. Seems because the kindle is not fully booting up then kindle fire first aid doesnt recognise it. Unless what i've been sent is actually a normal usb, then I dont see any way of sorting this. I'll wait to see if you have better luck
Click to expand...
Click to collapse
OK I may have cracked it here. I am no expert ( I wouldnt be in this mess if I was) i was playing with the adb commands with the factory cable connected.
Typed:
ADB devices
showed a device called D025A0A024540SF0 recovery
Typed:
ADB Reboot-Bootloader
Kindle fire boots into FASTBOOT screen. YEY ME!!!
Now i'm not really sure where to go, never used fastboot before.
After using kindlefire recovery tool, doing a wipe then option 2 my kindle booted up into TWRP.
I tried rebooting from here and now I get a flashing kindlefire logo.
occasionally i manage to get it into fastboot with the factory cable, but it doesnt stay there long enough to do anything. I hoping this is maybe a power issue so I'm leaving it plugged in overnight to attempt to charge it.
hope this info helps you, I feel like I was at a point to simply re flash a rom but messed up by rebooting from twrp.
I did it!!!!
Managed to get it to stay in fastboot mode and ran kindlerecover tool again. now have a working kindle running APEX launcher. Have to read up tomorrow and get cyanogenmod back.
kpugh162 said:
OK I may have cracked it here. I am no expert ( I wouldnt be in this mess if I was) i was playing with the adb commands with the factory cable connected.
Typed:
ADB devices
showed a device called D025A0A024540SF0 recovery
Typed:
ADB Reboot-Bootloader
Kindle fire boots into FASTBOOT screen. YEY ME!!!
Now i'm not really sure where to go, never used fastboot before.
After using kindlefire recovery tool, doing a wipe then option 2 my kindle booted up into TWRP.
I tried rebooting from here and now I get a flashing kindlefire logo.
occasionally i manage to get it into fastboot with the factory cable, but it doesnt stay there long enough to do anything. I hoping this is maybe a power issue so I'm leaving it plugged in overnight to attempt to charge it.
hope this info helps you, I feel like I was at a point to simply re flash a rom but messed up by rebooting from twrp.
I did it!!!!
Managed to get it to stay in fastboot mode and ran kindlerecover tool again. now have a working kindle running APEX launcher. Have to read up tomorrow and get cyanogenmod back.
Click to expand...
Click to collapse
Grats i'm glad it worked out for you man, i'll try out the same when i get my cable lol i ended up buying a new tablet thinking no one would solve this problem and now i just may have two if i get mine working also if you try loli pop again make sure you install gapps for it, that was my first mistake that led to me messing up my kindle the second being the factory reset, the devs should either disable or warn people not to try it since your screwed once you do anyways i'll give an update once i try to recover my kindle, cheers.
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app
I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?
smvsmv said:
I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?
Click to expand...
Click to collapse
bootloader was always locked, but 5.0.X allows booting a custom Recovery
if it will not boot to recovery nor rom/system, nothing can be done
fastboot cable doesn't work with 5th gen fires
Sent from my DROID Turbo using XDA Labs
Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?
smvsmv said:
Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?
Click to expand...
Click to collapse
Thoughts:
- you can still flash a custom ROM but if something goes wrong during the upgrade you're screwed without a recovery environment.
- recent versions of FlashFire have the ability to preserve and rewrite the recovery environment; not certain if the process works on this device and potential side effects (if any).
- several months ago another contributor claimed to have resurrected the stock recovery environment via adb which created quite a stir at the time. Have not seen much since so I suspect the solution was not generically applicable.
- I'm of the belief that most recovery access issues are actually a booting problem vs a damaged recovery partition. Your situation may be a little different as you attempted to rewrite the recovery partition by flashing TWRP.
oh well.. I'll just wait for you brainy guys to figure a way out. Not messing with the device anymore for now. Thank you!