Not starting up correctly. Background flashing - Fire Q&A, Help & Troubleshooting

Kindle 7 rooted from 5.0.1 was working fine the other day but turned it in tonight and the background just keeps flashing up. When I turned it on it quickly flashed up that it was installing an update and that's when the issues started

james_dean1986 said:
Kindle 7 rooted from 5.0.1 was working fine the other day but turned it in tonight and the background just keeps flashing up. When I turned it on it quickly flashed up that it was installing an update and that's when the issues started
Click to expand...
Click to collapse
Could try factory reset in Stock recovery
or reflashing firmware, but if it updated
it would be whatever the newest firmware version is

Try loading TWRP using supertools, if it's still on 5.0.1 twrp will boot. If it boots into twrp, then you could (1) sideload Fire OS 5.0.1 from adb and re-root using supertools or (2) better still if TWRP boots just wipe the system and install the latest nexus rom. It's a massive improvement over fire OS

I can get to the fastboot screen but the supertool isn't picking my kindle up.
I did the data clear/factory reset and now I keep getting the 'installing latest software' screen but it never completes. Left it running all last night..

Sorry for the delay, when the fire is connected to your pc in fastboot what does it show as under device manager.

Related

[Q] Kindle Fire Rebooting Constantly

At some point i had my kindle fire rooted with a jelly bean rom, with twrp recovery installed. I wanted to get rid of my fire, so i decided it was time to go back to the stock rom. In my infinite wisdom, I ended up wiping my factory backup by mistake. I went onto the kindle update site and downloaded the latest official version 6.3 bin file. I then renamed the .bin to .zip and updated it through twrp. When my kindle restarted, the factory OS came up, except I started getting android.acore errors along with another calendar process error. If that wasn't bad enough, it now randomly reboots whenever it feels like it. Luckily I can still usb mount it to my pc and can copy files back and forth. I tried using the kindle fire utility to root it again and install twrp, but no luck. Any ideas? Thanks in advance.
Pretty sure you're in the wrong forum - this is for the KF HD, not the original Fire.
Try your luck here: http://forum.xda-developers.com/forumdisplay.php?f=1306
oops, my bad. Thanks for the heads up.

[HELP] No OS and Phone Reboots when flashing

Hi All,
My phone decided to put itself into an infinite reboot loop today for no reason. It was running Android Revolution HD 31 fine before this point (S-On).
I could not get it to start so I wiped in recover and tried re-flashing, and it rebooted during flashing
I have tried uploading smaller roms to it, but it reboots during the adb sideload or adb push, so currently I am stuck, I also download the RRU but it does not detect my phone
Any help would be much appreciated!
Update it finally flashed everything is crashing will try a wipe and flash again.....
make sure it is charged before flashing, at least 30%.
never change a rom without a full wipe.

XT1092 Update Unsuccessfull No Changes were made

Hi Guys
I have the XT1092 with the GB ROM installed and I am having some serious trouble getting it to update to android 5.0 I have unlocked the bootloader.
I must have downloaded and tried to install the update for 5.0 about 6-7 times now. I have tried clearing the cache and installing afterwards, this did nothing and also doing a factory reset and installing it after and I get the same problem.
The phone reboots, thers a screen with the android on his back with 'system update installing' and then it gets about 25% through, briefly an exclamation mark appears and the phone reboots.
It goes back into the 4.4.4 and then a screen appears saying 'Software update unsuccessful sorry there was a problem updating your Motox, No changes were made'.
Is there anything else I can try?
I did try to flash the EU ROM on not long ago and I gave up, is there anyway I can put a fresh GB Rom and flash everything back on again from scratch?
Any help is appreciated
Cheers
Alex
Ok I have flashed the EU 4.4.4 rom found on another thread, Now I am struggling with ADB.
When I run System update it shows that the EU 4.4.4 rom is now installed all good and proper but it
says I am all up to date, The liar!
So I am trying to sideload the 5.0 update to my device using adb. The strange thing is, that when the phone is powered on in the 4.4.4 and I run a 'adb devices' command I can see the phone there in the list of devices.
But when I put it into recovery and select the adb sideload option it is not coming up on the 'adb devices' command
Anyone know why?

Updated to CM 12.1, no recovery mode, everything else seems fine

Today I've updated from CM 11 (KitKit 4.4.4) to CM 12.1 (Lollipop 5.1.1). I made a backup, a factory reset and then flashed the latest nightly and Google apps. Everything was fine so I continued installing apps, restoring data etc. When everything seemed to be finished and the phone was as I want it to be, I wanted to make a new backup.
But now I can't enter recovery mode. When I boot the phone and press the volume button, the LED turns yellow as it's supposed to, but the screen stays black and nothing more happens. If I press the power button the phone reboots. So everything seems fine, the phone is working and I've got root access, but I can't enter recovery mode. I've tried to use ADB and fastboot but I can't connect to my phone so I can't flash a new recovery image. I can boot into fastboot mode with the LED turned blue but ADB stays on <waiting for device>. I've tried to update drivers etc and also tried another computer but with the same result so it seems there's something wrong with the phone.
In developer settings there's an option for CyanogenMod to update the recovery when flashing a new nightly - but I don't know if I can flash a new nightly when I can't enter recovery mode.
Any advices?
Update: With the CM Updater I downloaded todays nightly and applied it. The phone rebooted, apparently into recovery (yellow LED but still black screen). I left it in a few minutes, then it automatically rebooted and when it was ready to use, the nightly was updated.
So maybe there is some kind of recovery working on the phone - but I still can't access it...
Try this
http://forum.xda-developers.com/showpost.php?p=62296602&postcount=1037
Thank you, but as mentioned in my first post I can't get a connection to my phone with fastboot, so I can't flash a recovery image through ADB. I've also tried different apps to flash a new recovery like TWRP Manager, Rashr and Flashify but even if most of them reboot the phone into recovery mode, nothing more happens.
Is it safe to flash and older nightly e.g. the one from 8th August when I'm now running with a newer version?
Even if your answer in the first way didn't seem to help me, it guided me in the right way, and now finally it seems to be working
First I tried another computer. I thought fastboot really should be working and it did on the other computer, so the next thing is to fix a driver issue on my own - but that's another story... With fastboot working I flashed a TRWP recovery. The only difference now was that when booting in recovery mode the Sony text didn't disappear, but still a black screen and no recovery...
Then I followed your link, downloaded an older nightly and flashed boot.img, and now finally it seems that everything is fine.
So thank you :good:
Did you not use flashtool?
I' m back to stock..
Maybe later CM again
Sent from my C6903 using Xda portal
No I downloaded drivers from Sony and then flashed with ADB.

Installing SuperSU causes black screen

I just updated my phone from 6.0 to 6.1. I had it rooted before with SU and TWRP installed. After installing 6.0.1 it works great. I then installed the latest TWRP as well, and that worked fine. However once I install the latest SU binary and attempt to boot into the phone, I get nothing but a black screen.
I can boot back into the bootloader with the power button + volume down to flash system, and then the phone will boot again. But as soon as I put SU back on there, I see nothing but the black screen. Also, after updating to 6.0.1 I started getting the "This device can't be trusted" screen when turning on the phone. It still boots after that, but it wasn't happening before.
Any ideas besides wiping and starting from scratch?
Is that SuperSU 2.62? Just asking because you haven't said. I haven't bothered rooting my N6 this time, since my only real need was a firewall and Netguard does the job perfectly, but I understand from general reading that Marshmallow is choosy about the SuperSU version.

Categories

Resources