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.
Related
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?
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.
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
resplin said:
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
Click to expand...
Click to collapse
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Still no stock recovery
wantabe said:
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Click to expand...
Click to collapse
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
resplin said:
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
Click to expand...
Click to collapse
I'm sorry about the link, not that it does any good now but the link is corrected. Using fastboot to flash the images is correct, I too often use adb as a generic term for both. When you boot into the stock recovery you will see the android with the exclamation mark and that is normal. Finally got the new 2012 N7 I bought as a gift and was updating it. Been a while since I've booted into a stock recovery. So... Boot into stock recovery, when the Android with the red exclamation mark appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. Whoop, Whoop! :laugh:
It works!
Thank you very much for your patient explanation. That helps a lot.
I hadn't realized that there was an additional step after the display of the warning android in order to enter stock recovery. All that time I spent trying to fix something that wasn't broken! <sigh>
I was unable to get the device to display the stock recovery menu, because it appears to require a very precise timing (I just keep rebooting it back to the system by accident). However, encryption did work fine. My confusion with the encryption was compounded by the fact that encryption of the Nexus 7 in 4.4 doesn't always work the first time (see this thread at android central: forums.androidcentral.com/google-nexus-7-tablet-2013/337078-experiencing-difficulty-encrypting-my-2013-n7-after-4-4-build-krt16s-upgrade.html). After trying 4 times in a row, the device encrypted. I was then able to put Team Win Recovery back on the device, and everything works perfectly.
Thank you again for your help. I don't see how to mark the thread as solved, but I am glad that everything appears to work now.
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?
HELP: I have CWM 6.0.5.1.4a and installed the latest rooted rom. Now I have a bricked device in boot loop. I am able to get into CWM with the ALT+i+prt scrn method.
I have tried installing varoius roms but my device does the same every time. It is just stuck in the color Fire TV logo.
Since I don’t have SU from CWM I cannot get ADB to upgrade to kernel boot menu or downgrade to stock firmware.
What should I do? Any help greatly appreciated!
I also tried the factory reset from CWM but with no result…
henningdalgaard said:
HELP: I have CWM 6.0.5.1.4a and installed the latest rooted rom. Now I have a bricked device in boot loop. I am able to get into CWM with the ALT+i+prt scrn method.
I have tried installing varoius roms but my device does the same every time. It is just stuck in the color Fire TV logo.
Since I don’t have SU from CWM I cannot get ADB to upgrade to kernel boot menu or downgrade to stock firmware.
What should I do? Any help greatly appreciated!
I also tried the factory reset from CWM but with no result…
Click to expand...
Click to collapse
Install 51.1.4.0 from CWM to fix it. Then follow all the instructions/requirements for the latest.
thanks! I installed 51.1.4.0 pre-rooted rom CWM and it worked. I thougt it failed and started the loop again but after a wile it booted into the amazon software.
I used the same one...
SSAPIR11 said:
I installed 51.1.4.0 to un-brick. i followed the guide to install su and busybox, verifited rom. I installed custom rom 51.1.5.0_515030720, rebooted and now stuck at amazon fireTV logo. any suggestions?
Click to expand...
Click to collapse
Seems you followed part of the guide but did you take all precautions? You need boot menu and unlocked bootloader for that fw. If you have these and confirmed they work, plus you checked mdsums...I can't imagine why it's in bootloop.
henningdalgaard said:
I am able to get into CWM with the ALT+i+prt scrn method.
Click to expand...
Click to collapse
What is that method exactly?
Alright, got a question, tried to find an answer everywhere.
Went to update to the newest version through CWM (51.1.5.0_515030720). Forgot to re-install Boot Menu, am now in a brick/bootloop. Despite what I've read, no amount of wiping the data/cache/dalvik cache gives me back the option to simply "reboot." In addition, all the guides tell me that I need to downgrade by installing 51.1.4.0_514006420. That's all well and good, but I have no way to get 51.1.4.0_514006420 onto my Fire TV to install it. Sideloading doesn't work, as ADB isn't functioning properly through CWM. Fastboot doesn't let me install roms or push files on.
Can someone please help me figure out what to do next? I can get to recovery, I have a keyboard, and I don't know how to get this older rom onto the Fire TV.
Neo3D said:
What is that method exactly?
Click to expand...
Click to collapse
there is a guide here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/