[HellFire Rom] Stuck at boot [ HELP ] - Kindle Fire Q&A, Help & Troubleshooting

So I tried to load HellFire rom on my kindle with Clockwork Recovery. I flashed the rom and did all the resetting and clearing of cache.
What happens when I now load my kindle is this.
1.) It loads the kindle fire logo
2.) loads the hellfire animation for a split second
3.) goes back to the kindle fire logo
4.) loads this blank screen
my computer cannot find the device when it is loaded in this blank screen. It can only find it when it is on the kindle fire logo and then it's named as "Amazon" (in my device manager) and I cannot do anything after that because it only stays on the kindle fire logo for maybe 5 seconds. Once the logo is gone from my kindle, my computer cant find the kindle connected.
If there is some way that I can just get into the Clockwork Recovery I can then just put a diffrent rom on. This HellFire rom of there's is defective and shouldn't be allowed to be out there in the public.
Any help will be amazing.
Thanks.

Which clockwork mod recovery? Also I have found when flashing hellfire in twrp that system and data had checks in them under mount simply by unchecking them I could get it to boot I really dont know how this applies to cwmr my suggestion though is to do a full wipe and flash a rom other than hellfire . Another thing I have noticed is this tends to happen when gapps are prebaked into the rom IMO the kindle needs this mount and unmount of system while flashing gapps to truly have a good clean flash...

Thepooch said:
Which clockwork mod recovery? Also I have found when flashing hellfire in twrp that system and data had checks in them under mount simply by unchecking them I could get it to boot I really dont know how this applies to cwmr my suggestion though is to do a full wipe and flash a rom other than hellfire . Another thing I have noticed is this tends to happen when gapps are prebaked into the rom IMO the kindle needs this mount and unmount of system while flashing gapps to truly have a good clean flash...
Click to expand...
Click to collapse
well right now I cant even get my computer to recognize my kindle. It's stuck in this loop..

No access to recovery?

Thepooch said:
No access to recovery?
Click to expand...
Click to collapse
I dont know how I could access recovery without it being recognized by the computer.

You have no yellow triangle or white kindle with blue fire then your kinda missing out on something its a bootloader that gives you access to recovery without that its very difficult indeed somewhere along the way we need to get you a bootloader but because at this point drivers are an issue I suggest using Linux I will help you with a setup that will rule drivers out of the equation and hopefully we will be able to flash a bootloader to your device in order that you can obtain access to recovery and clean up your broken system issue by flashing a rom that your kindle will like more pm me and we can get that sorted for you

Thepooch said:
You have no yellow triangle or white kindle with blue fire then your kinda missing out on something its a bootloader that gives you access to recovery without that its very difficult indeed somewhere along the way we need to get you a bootloader but because at this point drivers are an issue I suggest using Linux I will help you with a setup that will rule drivers out of the equation and hopefully we will be able to flash a bootloader to your device in order that you can obtain access to recovery and clean up your broken system issue by flashing a rom that your kindle will like more pm me and we can get that sorted for you
Click to expand...
Click to collapse
Alright. Thanks!

I have the same problem, any solution?

Related

Root Kindle Fire 6.3.1

Sorry for the newb question here. But I have a kindle fire and the version is 6.3.1 i would like to root the device. My os is osx 10.7.x I was wondering if i could use a version of super one click or if any one had any suggestions. I also have my computer boot camped so if super one click isnt an option can you please direct me in the right way thank you.
Read this first:
http://forum.xda-developers.com/showpost.php?p=23747567
Error while rooting kindle fire with 6.3.1 leads to error while flashing JB 4.2.1
Hello,
I need help to understand the process to install the root and Jelly Bean in my KF
I attached the message I get
What I did was:
restore the KF to factory settings
install the ADB drivers on my PC
connect the KF and verify the 4000 status
install permanent root and super user (please check the log)
While rebooting, it enters into the recovery boot screen and that's it. I don't see that the process is complete
I reboot the KF and the KFU, after that I can install the extras from the KFU but not superuser app
In the recovery boot screen I can do backups, which I did and flash the JB ROM
after rebooting with the JB installed I got stuck in the waving triangles animation and from time to time it tells me that Android is updating apps
I reboot the KF and go back to the waving lines animation and sometimes I see errors of starting the apps and got stuck in the animation
I've downloaded the ROM over 5 times in 2 different PCs with the same results.
I can restore the KF into the last backup I made any time.
Please advise.
I really appreciate the attention and support.
Thanks
Mike E.
In recovery, did you wipe system and factory reset before installing the ROM?
"That's a special kind of stupid. The kind that makes me laugh"
Okay for one don't use that kfu again something is wrong with it. To flash a rom wipe factory reset, wipe cache, wipe dalvik, wipe system in that order then flash rom.zip then gapps.zip select reboot and then system. You have a bootloader and a recovery you're done with kfu for now leave extras alone that is for stock purposes not jelly bean.
Thepooch said:
Okay for one don't use that kfu again something is wrong with it. To flash a rom wipe factory reset, wipe cache, wipe dalvik, wipe system in that order then flash rom.zip then gapps.zip select reboot and then system. You have a bootloader and a recovery you're done with kfu for now leave extras alone that is for stock purposes not jelly bean.
Click to expand...
Click to collapse
Thank you very much, the order of the wipes did the trick, I'm happy with JB 4.2.1!

[Q] Kindle Fire Boot loop

Okay, I have a kindle fire and ive tried all the utilitys to fix this but none of them work.
The kindle boots up, and says the following processes stopped unexpectedly
com.android.providers.calender
and android.process.acore and then the device shuts off and loops over again
Its on the stock rom and i have no idea how to fix it
thanks in advanced
Do you have root, bootloader, and recovery? It seems your calendar or contacts are corrupted and require deleting some files, but unless you stop the reboot you won't be able to do that. I would recommend using recovery to wipe the cache and factory reset.
BTW, does the stock ROM include Google Calendar?
Its completely stock, I can't get the Kindle fire utility to flash the boot loader because it reboots itself and it keeps saying "waiting for the device". I've installed the drivers and nothing is working. No root.
Unfortunately to fix this problem you'll need access to fastboot to install custom recovery. You'll be able to revert back to stock afterwards but you'll lose some data in the process.
The easiest way to do this is with the Kindle Fire Utility but you run the risk of running into some trouble (but not much). It's unnecessary and potentially dangerous to install a bootloader if you plan to revert back to stock so don't even try it.
You absolutely have to make sure your drivers are in order to get past the "waiting for device" problem. Make sure you've read and understand the following tutorial on device drivers:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Once you have recovery installed you'll be able to reinstall the stock 6.3.1 update which will fix your original problem and revert your device to a pure stock state (no root, no recovery, etc.)
Okay, I've double checked the drivers for the device, can you post a thread with exactly how I use fast boot and install a custom recovery? And I plan to revert to stock and then use install a custom recovery image and then cyanogenmod 7 over that. Does the device have to be powered off or on to access fast boot and install a custom recovery image? The issue I have is the device powers on and stays on for only about 15 seconds, and then it dies on my again. Also, thanks for the quick response
If your drivers are in order you can use KFU to install custom recovery as it does everything for you.
If you want to do it manually you need to read the following posts:
http://forum.xda-developers.com/showpost.php?p=23747567&postcount=1
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
http://forum.xda-developers.com/showthread.php?p=24124828
Just remember to skip the bootloader.
[Edit:] The manual method also requires working drivers.
hunterhk said:
Do you have root, bootloader, and recovery? It seems your calendar or contacts are corrupted and require deleting some files, but unless you stop the reboot you won't be able to do that. I would recommend using recovery to wipe the cache and factory reset.
BTW, does the stock ROM include Google Calendar?
Click to expand...
Click to collapse
Thanks for this suggestion. :good::good: My kindle went into a boot loop after I hid the SU account with Voodoo OTA Rootkeeper. It took several tries to get it to go into recovery, but managed to get in. Wiping the main cache fixed the boot loop for me.

Kindle back to stock

I have rooted my kindle fire and installed twrp and fff using kindle fire utility. With twrp I flash a jelly bean rom and now i am wanting to go back to how my kindle was out of the box. so i got an update off the internet and downloaded it to my kindle, but when i rebooted my kindle it didnt go into fff. i am just wondering is there any other way to install roms on the kindle since i cannot get into twrp. also tried to reinstall twrp and fff on kindle fire utility but it says adb status offline and will not change. please help!
Brunde22 said:
so i got an update off the internet and downloaded it to my kindle, but when i rebooted my kindle it didnt go into fff.
Click to expand...
Click to collapse
Do you get a blue kindle fire logo?
When you flash with stock rom it wipes out FFF bootloader and replaces it with one from amazon.
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
p4trykx said:
Do you get a blue kindle fire logo?
When you flash with stock rom it wipes out FFF bootloader and replaces it with one from amazon.
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Click to expand...
Click to collapse
No i just get the original orange kindle fire logo.
Brunde22 said:
No i just get the original orange kindle fire logo.
Click to expand...
Click to collapse
But the system boots or is it stuck at this logo?
After system boot you should be able to run this command
Code:
adb devices
adb is somewhere in kfu directory
Look here http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
Brunde22 said:
I have rooted my kindle fire and installed twrp and fff using kindle fire utility. With twrp I flash a jelly bean rom and now i am wanting to go back to how my kindle was out of the box. so i got an update off the internet and downloaded it to my kindle, but when i rebooted my kindle it didnt go into fff. i am just wondering is there any other way to install roms on the kindle since i cannot get into twrp. also tried to reinstall twrp and fff on kindle fire utility but it says adb status offline and will not change. please help!
Click to expand...
Click to collapse
Your problem, besides not having a clue what you're doing, is you didn't wipe the necessary partitions before trying to install a new ROM. Most of the time, that results in sort of a Frankenstein of an OS that the system cannot boot normally.
Typically, with FFF installed, you can tell pretty easily what mode your device is in by looking looking at your screen. If the device hangs at the boot screen, you know it is in fastboot, or if it continues on to the boot animation, you know it's in normal mode. With the stock Kindle Fire software installed, both the bootloader's splash screen and the boot animation are the same (with the exception of brightness), so you have to use the adb to determine what state the device is in. In your case, the device is in normal boot mode, so the typical "fix" for "stuck at kindle fire logo" wouldn't apply to you.
Unfortunately, by reinstalling the Kindle Fire update.zip, you also overwrite not only the custom bootloader, but custom recovery as well, which is required to fix your problem. Reverting back to stock, simply to re-root or install a different ROM is unnecessary and a complete waste of time. Now you have to get back into fastboot mode so you can reinstall custom recovery, wipe the necessary partitions and reinstall a ROM.
If any of this sounds foreign to you, it's because you're in WAY over your head. Before you go any further, educate yourself in how and why the Kindle Fire/Android works. Doing so will greatly increase your chances of success and decrease the chances of finding yourself in another situation like this one.
http://forum.xda-developers.com/showpost.php?p=23747567
first three posts
http://forum.xda-developers.com/showpost.php?p=25730650
first two posts
http://forum.xda-developers.com/showpost.php?p=26435498
Brunde22 said:
No i just get the original orange kindle fire logo.
Click to expand...
Click to collapse
i had this problem but i have a kf2 (non hd)....i also used hashcodes otter2 bootloader files....but what i did was re flash his bootloader files and it gave me twrp back........then i sideloaded my cm10.1 rom and it fixed it where i could get back to cm10.1 then i put gapps back in and everything was fine again.....but as far as me putting it back stock i'm still working on that.....youll have to get it into fastboot mode with a fastboot factory cable to reflash your bootloader files again....it worked for me but i am using a kf2 though.....

Flashed cm10.1, stuck on boot screen

I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When you plug in the usb to the computer do you get any change in windows device manager? like an unrecognized kindle fire (yellow triangle) under usb or similar?
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
seecay said:
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
Click to expand...
Click to collapse
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
stewtang said:
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's a strange problem. Have you tried to reinstall the drivers or use a different PC? If it can get into the boot animation, you should theoretically be able to get into recovery/TWRP... Sounds like a bad flash may have happened so try a newer/older build. I hope it goes ok...
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Thepooch said:
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Click to expand...
Click to collapse
I replaced the file and still shows ADB status as offline and boot status as unknown. The computer makes the noise that a device is connected once the kindle reaches the CM screen but the that is it, ADB is still offline. Also, the kindle fire logo at start up is no longer blue, it has reverted to the stock orange color.
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Click to expand...
Click to collapse
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
guruizzy said:
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
Click to expand...
Click to collapse
Any luck getting into recovery? If so, how did you do it?
stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
I have always been able to get into recovery. However, I did find that my /system/bin/sh file and all other system files are completely missing. I have yet to fix this, as this could be some of my problems. I don't know I'm still a noob at this. I have reflashed TWRP 2.2.2.1 while in fastboot mode using a factory cable. I just bought one for $6 on ebay from a US seller. Using this cable I find that the KFU works more like it should. It actually tells what boot mode status is currently instead of just saying unknown.
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether? Again, uber noob here.
guruizzy said:
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether?
Click to expand...
Click to collapse
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
jma9454 said:
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
Click to expand...
Click to collapse
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Sent from my Galaxy Nexus using xda premium
stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
Looks like you may not have FFF so you probably can't get into TWRP... Have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1428428
stewtang said:
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Click to expand...
Click to collapse
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
jma9454 said:
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
Click to expand...
Click to collapse
Yes that is what I see, but before I flashed it the kindle fire logo was blue.
Sent from my Galaxy Nexus using xda premium
I had the same thing happen to me when I flashed my kindle fire demo unit with CM10.1, it turned out to be some sort of an issue with the twrp recovery when I reflashed it with the cotr recovery that the kindle fire utility program also has as a alternate this worked just fine. I did notice that when I tried to use twrp to wipe my unit it didn't seem to fully wipe the unit. doing the same thing under cotr took longer.
The reason I think it was twrp is that no matter what version of CM10.1 I used be it a nightly or the M3 experimental build, it would still just show the distorted logo and never finish booting. this happened even after I wiped the /system and cleared cache and dalvik cache.
After I flashed cotr recovery I did the same thing again using the exact same zip files for CM10.1 and gapps and it worked this time.
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
andreasS2 said:
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
Click to expand...
Click to collapse
yadspi said:
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
Click to expand...
Click to collapse
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
soupmagnet said:
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
Click to expand...
Click to collapse
I did, I was going to sell it with CM10, I rebooted, did a factory reset, reinstalled cm.zip and gapps.zip and rebooted....lost firefirefire and stuck on CM logo. If I buy or make the factory cable, will it be easy to "revive"?
Edit: Saw it on eBay for $4.45 free shipping

[Q] Flashed Kindle Fire boots to a strange screen with rotating triangles

Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Bad download/corrupted file?
Wait my reading caught up with me. You say it is still booting into stock? That doesn't sound like bad firmware download after all. Sorry... I don't know then! Someone else should have a thought.
I read it once again and realize you restored stock. Lol I go with my original suggestion. Redownload and reflash.
Sent from my GT-p511x
gordonj56 said:
Hi, I have an original KF that was running v6.3.2, I am trying to get it to run JB 4.2.
I successfully (I think) rooted it using SuperOneClick
I installed FFF and TWRP using KF Utilities
It can boot into TWRP
I try to flash Hashcode's 4.2.2_r1 and TWRP seems to complete although it does stick on "Updating partition details"
When I restart it it just goes to a screen covered in weird rotating triangles.Only thing I can do is hard shut down.
I did do backup and can restore it to original Amazon 6.3.2 KF firmware. Interestingly when I do this TWRP asks me to install SuperSU, which I do.I then boots as if its a new KF, except with SU app installed.
Can anyone give me any pointers as to where I might be going wrong?
Thanks
Gordon
Click to expand...
Click to collapse
The "weird rotating triangles" is the stock AOSP boot animation. 9 times out of 10, when your device gets stuck on the boot animation, it is from not wiping data in recovery before flashing the ROM. Boot into recovery, factory reset, then reboot to see if it fixes the problem.

Categories

Resources