Develop Bugs

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

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

Unable to Enter Recovery

I am trying to change my recovery but have been unable to reboot into the stock recovery. When I try and reboot into recovery the system just hangs at the first Amazon logo. I didnt have any problems when I first received the unit and manually updated it but it is a no go now. Is there a way to repair recovery if something has gone wrong with it? I can still boot into the device fine. Any help you can provide is appreciated.
Thanks

Deleted... Understood it the wrong way.

Kalhua said:
I am trying to change my recovery but have been unable to reboot into the stock recovery. When I try and reboot into recovery the system just hangs at the first Amazon logo. I didnt have any problems when I first received the unit and manually updated it but it is a no go now. Is there a way to repair recovery if something has gone wrong with it? I can still boot into the device fine. Any help you can provide is appreciated.
Thanks
Click to expand...
Click to collapse
I figured it out. I used Fire TV Firmware Restore Tool V3. It must repair the recovery because everything worked as usual once I used it.
Thanks

Newly bricked

So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?

ugabuga said:
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
Click to expand...
Click to collapse
If it failed to flash... you rebooted because... The only way to get back to recovery is the printscreen method, but because you have a corrupt system, it's not going to be easy to trigger it.

ugabuga said:
So after a few months of being on a older fw that i rooted i decided to update. Downgraded fw, re-rooted, unlocked bootloader, installed clockworkmod recovery. Finally the last step - adb latest custom rom and reboot. Did the install via cwm and it failed.
Rebooted and now stuck at the amazon logo. I tried the usb keyboard trick a few times( printscr,alt,i) but mine seems to boot very fast directly to black screen with amazon logo. So at this point not sure if any way to recover....any ideas?
Click to expand...
Click to collapse
I had this same issue, I attempted to install using the sideload command and it kept failing. To get the update to install, I pushed the update to the /sdcard/0 and installed from there, and it installed with no dramas.
No help on recovering your device though, just my experience in case it happens again.

Thanks for replies... I guess I'll try to get back into recovery again tonight. When pressing the 3 kb buttons... is it press and hold immediately after plugging the ftv on or is it repeatedly pressing all 3 buttons? If I do trigger recovery and restore, what actually gets restored? Is the the prior working version? Do I need to worry about it updating an losing root?
Btw I did push the rom to /sdcard/0 so not sure why it failed maybe bad download.

Possible brick in bootloader recovery // Please help !

I just received my brand new FireTv and luckily it was on firmware 51.1.0.1. I was able to properly root the device but cannot upgrade or downgrade the firmware using any manual methods or tools/scripts. Every time the FTV tries to boot into recovery it just FREEZES at the white Amazon logo and sits there forever. If I end up unplugging it, it reboots back into the original firmware. Doing a factory reset via the settings menu or remote button combo has the same effect where the FTV again gets stuck on the Amazon logo....
The 2 update addresses are blocked via DNSMasq since the beginning. I've also tried with and w/o PM Disable, loading up a custom bootloader and reinstalling the stock bootloader. Tring to enter recovery by using the keyboard key combo just reboots the device and freezes it again at the Amazon logo. There is also no powered usb hub connected....
Is there any way I can :
1) manually restore the device using ADB (ie. By deleteing folders)
2) force a manual update on the recovery menu
3) correct any recovery boot errors
4) or update firmware without the need of the recovery menu
Willing to try pretty much anything....
Any help would very appreciated.
UPDATE:
Figured out how to manually restore. Unfortunately no impact on the recovery boot freeze:
adb shell
su
wipe data

Over 100 views and no one can help with this? Really?!? Rbox?

qwertywarez said:
Over 100 views and no one can help with this? Really?!? Rbox?
Click to expand...
Click to collapse
did you try with the 2 urls unblocked while using pm disable method ? probably wont help but i thought those urls need to be unblocked on a factory reset?

nhumber said:
did you try with the 2 urls unblocked while using pm disable method ? probably wont help but i thought those urls need to be unblocked on a factory reset?
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried without the 2 URLs and it still hangs at the white Amazon logo when rebooting to recovery. Any other ideas?

qwertywarez said:
Thanks for the suggestion. Just tried without the 2 URLs and it still hangs at the white Amazon logo when rebooting to recovery. Any other ideas?
Click to expand...
Click to collapse
so your rooted and you can boot normally fine, just cant boot into recovery? did you unlock your device prior to installing the newest cwm?

nhumber said:
so your rooted and you can boot normally fine, just cant boot into recovery? did you unlock your device prior to installing the newest cwm?
Click to expand...
Click to collapse
yes I'm rooted and unlocking the bootloader was successful. Just can't get into recovery. I also get the freeze when doing a factory reset from the device. Even on stock recovery.
Seems that the bootloader freezes the command to send to recovery....

qwertywarez said:
I just received my brand new FireTv and luckily it was on firmware 51.1.0.1. I was able to properly root the device but cannot upgrade or downgrade the firmware using any manual methods or tools/scripts. Every time the FTV tries to boot into recovery it just FREEZES at the white Amazon logo and sits there forever. If I end up unplugging it, it reboots back into the original firmware. Doing a factory reset via the settings menu or remote button combo has the same effect where the FTV again gets stuck on the Amazon logo....
The 2 update addresses are blocked via DNSMasq since the beginning. I've also tried with and w/o PM Disable, loading up a custom bootloader and reinstalling the stock bootloader. Tring to enter recovery by using the keyboard key combo just reboots the device and freezes it again at the Amazon logo. There is also no powered usb hub connected....
Is there any way I can :
1) manually restore the device using ADB (ie. By deleteing folders)
2) force a manual update on the recovery menu
3) correct any recovery boot errors
4) or update firmware without the need of the recovery menu
Willing to try pretty much anything....
Any help would very appreciated.
UPDATE:
Figured out how to manually restore. Unfortunately no impact on the recovery boot freeze:
adb shell
su
wipe data
Click to expand...
Click to collapse
From your post above your where at 51.1.0.1_user_510055620 (all my FTV's have been at this FW out the box) all you had to do was ROOT following the AFTV Rooting Guide then then install CWM. Downgrading was not needed. And upgrading was only for after installing CWM. Then you would upgrade with the PreRooted FW.

Y314K said:
From your post above your where at 51.1.0.1_user_510055620 (all my FTV's have been at this FW out the box) all you had to do was ROOT following the AFTV Rooting Guide then then install CWM. Downgrading was not needed. And upgrading was only for after installing CWM. Then you would upgrade with the PreRooted FW.
Click to expand...
Click to collapse
Yes, CWM after my initial root was the first thing I tried but I went back to stock recovery to do a manual upgrade to 51.1.0.2 because CWM recovery wasnt working. i figured CWM preferred stock 51.1.0.2 but could not even upgrade to that on stock recovery due to the recovery freeze.

qwertywarez said:
Yes, CWM after my initial root was the first thing I tried but I went back to stock recovery to do a manual upgrade to 51.1.0.2 because CWM recovery wasnt working. i figured CWM preferred stock 51.1.0.2 but could not even upgrade to that on stock recovery due to the recovery freeze.
Click to expand...
Click to collapse
CWM prefers anything 51.1.0.2 or lower. It makes no difference to it installing it. Are you sure you had rooted it correctly ? I would try to reflash the "recovery-stock-51.1.0" with the AFTV Utility & and after that reflash the 51.1.0.1_user_510055620. DO NOT rename them to update.zip if you are using the AFTV Utility. After that you will need to reRoot again.
Which version of CWM where you trying to install ??

Y314K said:
CWM prefers anything 51.1.0.2 or lower. It makes no difference to it installing it. Are you sure you had rooted it correctly ? I would try to reflash the "recovery-stock-51.1.0" with the AFTV Utility & and after that reflash the 51.1.0.1_user_510055620. DO NOT rename them to update.zip if you are using the AFTV Utility. After that you will need to reRoot again.
Which version of CWM where you trying to install ??
Click to expand...
Click to collapse
Thanks for the assistance.
I rerooted, flashed stock recovery and stock Fw 51.1.0.1 all using the AFTV utility and the re-flash process of the original stock Fw does not complete since it still stays stuck on the white Amazon screen. PS: AFTV utility v0.30 requires the renaming to update.zip else it give an error.
When flashing CWM recovery, I use the latest 6.0.5.1.4a but also tried older versions.

qwertywarez said:
Thanks for the assistance.
I rerooted, flashed stock recovery and stock Fw 51.1.0.1 all using the AFTV utility and the re-flash process of the original stock Fw does not complete since it still stays stuck on the white Amazon screen. PS: AFTV utility v0.30 requires the renaming to update.zip else it give an error.
When flashing CWM recovery, I use the latest 6.0.5.1.4a but also tried older versions.
Click to expand...
Click to collapse
For 6.0.5.1.4a you would of had to unlocked the bootloader first. Try again to do the keyboard reset again.. See if this time it comes thru...

Y314K said:
For 6.0.5.1.4a you would of had to unlocked the bootloader first. Try again to do the keyboard reset again.. See if this time it comes thru...
Click to expand...
Click to collapse
Yes, forgot to mention. The bootloader was unlocked. Still the same problem.

Any other ideas?