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.

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.

[Q] Please help. Bricked/boot loop

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/

Trying to Install TWRP on a SM-G960F

Hi
Been trying to install twrp-3.5.2_9-0-starlte.img.tar to my S9.
First i succesfully unlocked bootloader. Then installed twrp through Odin v3.14.1.
Then the phone succesfully boots into twrp recovery. Then i flashed and tried to install no-verity-opt-encrypt.. 6.1 didnt work so i flashed and tried all down to 4.0. Nothing worked. Just got the error 1 all the time.
Then i tried the read somewhere that i could try the multidisabler. Ref this thread: XDA link. This succsefully installed. Then i rebootet through twrp with the option to install twrp app. The phone got stuck in a start up screen for 10 min and took me right back to start.
After again logging in and setting up the phone Nothing seems to have changed. Only that the bootloader is still unlocked.
Am i doing something wrong? Is it suppose to boot up again to stock OS?

Wheelx said:
Hi
Been trying to install twrp-3.5.2_9-0-starlte.img.tar to my S9.
First i succesfully unlocked bootloader. Then installed twrp through Odin v3.14.1.
Then the phone succesfully boots into twrp recovery. Then i flashed and tried to install no-verity-opt-encrypt.. 6.1 didnt work so i flashed and tried all down to 4.0. Nothing worked. Just got the error 1 all the time.
Then i tried the read somewhere that i could try the multidisabler. Ref this thread: XDA link. This succsefully installed. Then i rebootet through twrp with the option to install twrp app. The phone got stuck in a start up screen for 10 min and took me right back to start.
After again logging in and setting up the phone Nothing seems to have changed. Only that the bootloader is still unlocked.
Am i doing something wrong? Is it suppose to boot up again to stock OS?
Click to expand...
Click to collapse
All you've done is installed custom recovery over stock. This by it's self doesn't effect stock system firmware. The only thing is because knox is trip you lose knox related apps functions.

spawnlives said:
All you've done is installed custom recovery over stock. This by it's self doesn't effect stock system firmware. The only thing is because knox is trip you lose knox related apps functions.
Click to expand...
Click to collapse
Hi and thank you.
Knox is trip?
So how do i know that this worked and twrp is succesfully installed?

Wheelx said:
Hi and thank you.
Knox is trip?
So how do i know that this worked and twrp is succesfully installed?
Click to expand...
Click to collapse
Knox is a Samsung thing. Once tripped it stays tripped and there is no cure for it. As said you will loose knox related apps functions like secure folder,samsung pass,Shealth etc.
To enter twrp is the same process as entering download (odin) mode except you use to volume up button ( power/bixby/vol up ) while device is starting up.

spawnlives said:
Knox is a Samsung thing. Once tripped it stays tripped and there is no cure for it. As said you will loose knox related apps functions like secure folder,samsung pass,Shealth etc.
To enter twrp is the same process as entering download (odin) mode except you use to volume up button ( power/bixby/vol up ) while device is starting up.
Click to expand...
Click to collapse
Yeah it says warranty something 1 on download screen.
I tried to shut down phone and start in recovery mode, but i loded into the stock recovery, not twrp. Am i doing something wrong?

Wheelx said:
Yeah it says warranty something 1 on download screen.
I tried to shut down phone and start in recovery mode, but i loded into the stock recovery, not twrp. Am i doing something wrong?
Click to expand...
Click to collapse
Without knowing your exact steps it a bit hard to say.
I would say that the multidisabler zip you tried didn't work. The zip you tried is for the S10 series. It's also a common problem on latest version of android that the no-verity-opt-encrypt.. 6.1 fails. Very basically this zip, after format data stage,
will prevent phone from re-encrpyting itself when booting into the system.
Try using this zip when installing twrp
Edit:
Installing the twrp app i leave up to you. Can be install later by twrp or playstore and not necessary for installing twrp recovery.

spawnlives said:
Without knowing your exact steps it a bit hard to say.
I would say that the multidisabler zip you tried didn't work. The zip you tried is for the S10 series. It's also a common problem on latest version of android that the no-verity-opt-encrypt.. 6.1 fails. Very basically this zip, after format data stage,
will prevent phone from re-encrpyting itself when booting into the system.
Try using this zip when installing twrp
Edit:
Installing the twrp app i leave up to you. Can be install later by twrp or playstore and not necessary for installing twrp recovery.
Click to expand...
Click to collapse
I have the same problem. Im Gonna try it out
EDIT: i got the write error. gonna try flashing stock again
edit2: flashing stock didnt work. gonna try turning off bootloader and turning it back on. if it does not work then im just gonna install normal XEO instead of PLS
EDIT3: yeah didnt work. just gonna install XEO now