Develop Bugs

[Q] New OS update bricked my Fire. Any quick fixes?

My rooted KF got bricked by the new OS update that was released last night. It boots as normal, gets to the locker screen, and whether you unlock it or not, reboots about 15 seconds later to a screen showing the Android guy and an exclamation point in a yellow triangle. Then, if you start touching the screen, 4 buttons will show up on the side, up/down, select, and back... but they do nothing. Reboot again and it takes me to TWRP.
I know how to wipe my KF and reinstall everything, but I was hoping that someone might know of a fix for this. Especially because I just got a new computer and am still in the process of getting my normal apps installed, let alone Android SDKs that I use once in a blue moon. Plus, I have a few games that I would rather not lose my progress on.
BTW, I rooted my dad's KF the exact same way as mine and his just lost root access with the update, everything else is fine. Kinda weird.
TIA

What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S. You may also get lucky and be able to flash modaco if you`re on rooted stock or previously rooted stock 6.3.1 without wiping.

Thepooch said:
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S.
Click to expand...
Click to collapse
About 3am last night, I found my KF bricked after just using it about 30 minutes before (the wifi was on and it was hooked up to the charger). Today, I checked on my dad's KF and he has his wifi turned off. I turned it on and it instantly rebooted to just a "command line" screen saying that it was installing an update. Took about 10 minutes and then rebooted and worked fine, except that it was unrooted. I read somewhere in the Amazon Forums today that they did roll out an update and plan on spending 2 weeks doing it to keep from bogging down their network. Granted, their Software Update page doesn't say anything about it yet.
BTW, thanks for the other info, I'll have to check it out. Sounds like I'll have to wipe it (or at least restore from a 2-3 month old backup and see how the update goes again). But that's cool that I won't need to install the Android SDK.

Explains why some are instantly being unrooted or like in your case bricked strange thing is that it doesn`t change the system version it`s still 6.3.1 figures that Amazon would pull something like this.

Hey, I did manage to find a quick fix!
In the recovery mode, I decided to try using the Fix Permissions option. Still had the same problem.
I then just used the Clear Cache option and my KF was back up and running... and still rooted.
The only issue I have found so far is that I had to change the permission to allow changing the wallpaper, just uncheck the "write" permissions, (which was probably reset by the Fix Permissions option I ran). Other than that 2 second fix, everything is fine.
Granted, I'm waiting for Amazon to do an auto-check for some file that was in the cache that told it that it had installed the latest upgrade, and since I wiped that, it may install it again. If it does, I'll post it in this thread that my quick fix didn't work. But so far so good.

It turns out that my quick fix is only a temp fix.
Twice tonight I had to clear the cache again via the recovery menu. The first time it happened, I had just finished reading and hit the power button to put it in sleep mode, which caused it to instantly reboot and then do the same thing as I mentioned above. It boots up, and within 5 second of getting the locker screen, whether you unlock it or not, it starts shutting down and reboots ending up with the screen in the attached pic (those dots are just dust that appear super bright for some weird reason because you can't see them except in the pic).
So I cleared the cache again, everything was fine, and then about an hour later I found it sitting on that screen again. Clearing the cache fixed it again, but obvious this is a reoccurring problem.
Anyone have any ideas?
I'm reluctant to do a reinstall yet because I'm afraid I'll just end up with the same problem... along with none of my apps installed.

I have the same issue my temp solution is turn off wifi asap after lock-screen appear, wait abt 1-2 minutes then I can turn on wifi and use as normal.
Everything will fine for few hours. Any permanent solution plz? I remember that it occurred after i update something from Amazon app store, maybe : apps...
Sent from my Kindle Fire using xda premium

The permanent solution is to flash another rom preferably modaco if you want the stock experience. Full wipe, your apps can all be redownloaded that is the least of your worries at this point. probably a really good time to upgrade your bootloader and recovery if you haven`t flash both of these zips as zips in twrp if are behind the curve http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 and http://forum.xda-developers.com/showthread.php?t=1632375 only get them from where I`m directing you or use smirkit http://forum.xda-developers.com/showthread.php?t=1500935.

thanks for your help. This is done with the below solution
1) Copy the update bin file to the /sdcard as update.zip
Download stock ROM : https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.1_D01E_4107920.bin
copy update-kindle-6.3.1_D01E_4107920.bin into Kindle Fire and re-name to update.zip
2) From the main menu of CWM, "Wipe cache from partion" to remove the existing files in the data and cache partitions
3) From the main menu of CWM, press the "Install update.zip" button to flash the stock software onto your device.
no data/application lost accept FFF and CWM

Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.

Thanks for the info guys.
Considering the post in the Amazon Forums said this update was being pushed out over a 2 week period, I'm just going to keep my WiFi off (unless needed) and wait until everyone should have received the update and then see how it plays out. Considering it doesn't change the software version number, I'm thinking that this update may be just targeting rooted Fires. And BTW, it appears that the post was removed, because I can't find it again. Maybe they remove any that mention rooting? I just stumbled upon it via a Google search... 99% of the question in their forum are just idiotic.
Directv used to pull this stunt all the time to bust people with hacked cards that allowed them to get all their channels for free (usually a few hours before some big PPV event). They finally completely stopped the ability to hack cards by rolling out parts of their code over a long period of time, a year or so. When the final piece was put in place, the previous parts of their code had already been integrated into the hacked card software, because it appeared safe, and along with upgrading the type of cards they used during that same period of time, pretty much eliminated the ability to cheat Directv. I'm not saying that Amazon is going to those lengths to stop people from rooting their KFs,.. but who knows? It may be costing them too much with people bricking their KFs by trying to root them. Plus, they may also be losing revenue by people getting their free apps (with ads) from the Playstore instead of Amazon. And considering they pretty much sell their Fires for cost, they definitely rely on revenue generated by buying and using things via a stock KF.
BTW, this whole issue had almost perfect timing... I was planning on wiping my KF because it definitely is slower than when I first got it (which was day 1 of its release). I've read that Gingerbread doesn't clean up after itself too well, especially not as good as ICS (kinda like a Windows registry just gets filled with junk over time, and no cleaner beats a fresh install). It also appears that the ICS roms are actually working reliably these days, compared to the last time I checked. So, in a couple weeks, I'll get to have some fun. I am a Windows/Cisco System Engineer, so this kinda stuff is fun for me.

F.Y.I.
It seems that Amazon did do a incremental update on the Original Kindle Fire version
6.3.1_user_4107720, April 30 build to 6.3.1_user_4107920, November 27 build.
I looked thru the update and the only things I found changed are to do with the
Wifi driver, launcher icons, boot animation, and boot.img; attached the changed file below.
I have not tried to update mine, will attempt this weekend.

Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.

Thepooch said:
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Click to expand...
Click to collapse
It seems they increased the resolution of the images in the file, but for me I can not see the difference.
For me I wonder what they changed in the WiFi driver file, tiap_drv.ko.

Kindle Fire Reboot Problem Solved - Install MoDaCo Rom
Thepooch said:
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Click to expand...
Click to collapse
I took Thepooch's advice and installed MoDaCo rom on my KF. It was a snap. I had FireFireFire installed with TWRP. Just downloaded MoDaCo to PC copied to KF. Rebooted to FireFireFire Installed with Install Zip utility. Took a few minutes. Rebooted didn't loose any data , apps or functionality. Its still rooted. THANKS!

No problem you can find the entire uncomplicated method here http://forum.xda-developers.com/showthread.php?t=1923010 or at least a synopsis of the concept.

Can't install any ROM's. Stuck on Samsung Galaxy Note II Screen

Hey all,
I have read all over the place on how to get this working but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is LJ2.
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.

alkaroth said:
Hey all,
I have read all over the place on how to get this working but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is 4.3 (I think; I go to About Device and I see the android version 4.3)
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Try this method flash the odin version and update the bootloader ne5 and you should be fine
http://forum.xda-developers.com/showthread.php?t=2802189

210
Thanks man. That post brought a lot to light. So I have the MK6 firmware but the LJ2 bootloader. I'll try doing what Zen Arcade says there but unfortunately I cant download his files. The website he's hosting the files from has severe lag and the files stop downloading.
I'll get back to you on how this goes once I'm able to download them.

terpin32 said:
Try this method flash the odin version and update the bootloader ne5 and you should be fine
http://forum.xda-developers.com/showthread.php?t=2802189
Click to expand...
Click to collapse
Finally downloaded it. Installed it and got that particular operating system working. I will try to get some customs roms installed. Thanks for the help man!

[fixed] Flashed wrong TWRP, possible hard brick? Please help :'(

I've had a horrible run of luck these past couple weeks.. Deep 2nd degree burns, two broken s6 edges from sliding off surface, and a drop all at short Heights, even with case on.. So now that I was laid up in bed recovering from work accident I decided to get my tmobile p607t I just picked up and my edge all sorted out.. This is what I did:
Downgraded from 4.4.4 to 4.4.2
Towelroot and supersu
Installed titanium backup
Decided to install custom rom and make nandroid backup
Installed flashify
Erroneously installed twrp for nexus 6 (it's a real ****ty mistake I wasn't paying enough attention, probably pain killers had something to do with it and didn't realize that for all the mentions of the note in the article that they were actually linking to nexus 6 twrp)
Flashed twrp with flashify, reboot, and would only boot into download mode
Booted into odin tried flashing the same stock 4.4.2 knowing it probably wouldn't fix problem, errored out, unsuccessful
Read something about flashing twrp with odin so tried that, it didn't work, heard cwm may work with odin, Unplugged tablet from pc, power cycled, started up with black screen.
Found out it was on by plugging back into pc and odin showed "Added"
Power cycle odin shows removed and added again.
Installed adb/fastboot and drivers via installer (win7 x64)
Just so see what was going on with tab figured I would try to flash stock again to see what error was, so I would be able to mention it in this post, says no pit partition and screen is still black..
This is the point where I decided to post, during all that I did read a lot and did try searching around for something model specific, but am really concerned about doing anything else without advice.. Not really sure if it's even fixable, but hoping that because odin still sees it, maybe it's not a lost cause.. Even if it is just pointing me in the right direction it'd be helpful. I'd be willing to donate to xda's server costs if it takes really in depth help, I've benefited a lot from the site over many years and never really had to post before because I've never had any real issues, usually much more thorough with reading things. Thanks in advance.
I have family coming over so will more than likely be back to working on it tonight..
Edit:
Jesus in doing a horrible job at life.. Posted in wrong sub.. Should be in note 10.1 2014 forum, please move to correct forum.. Sorry
Edited to add:
It's fixed, I located pit partition file, loaded that and stock rom in odin, attempted to flash but it failed, power cycled and download mode appeared on tablet, without error and odin automatically began flashing, everything is back to normal..

defcomexperiment said:
I've had a horrible run of luck these past couple weeks.. Deep 2nd degree burns, two broken s6 edges from sliding off surface, and a drop all at short Heights, even with case on.. So now that I was laid up in bed recovering from work accident I decided to get my tmobile p607t I just picked up and my edge all sorted out.. This is what I did:
Downgraded from 4.4.4 to 4.4.2
Towelroot and supersu
Installed titanium backup
Decided to install custom rom and make nandroid backup
Installed flashify
Erroneously installed twrp for nexus 6 (it's a real ****ty mistake I wasn't paying enough attention, probably pain killers had something to do with it and didn't realize that for all the mentions of the note in the article that they were actually linking to nexus 6 twrp)
Flashed twrp with flashify, reboot, and would only boot into download mode
Booted into odin tried flashing the same stock 4.4.2 knowing it probably wouldn't fix problem, errored out, unsuccessful
Read something about flashing twrp with odin so tried that, it didn't work, heard cwm may work with odin, Unplugged tablet from pc, power cycled, started up with black screen.
Found out it was on by plugging back into pc and odin showed "Added"
Power cycle odin shows removed and added again.
Installed adb/fastboot and drivers via installer (win7 x64)
Just so see what was going on with tab figured I would try to flash stock again to see what error was, so I would be able to mention it in this post, says no pit partition and screen is still black..
This is the point where I decided to post, during all that I did read a lot and did try searching around for something model specific, but am really concerned about doing anything else without advice.. Not really sure if it's even fixable, but hoping that because odin still sees it, maybe it's not a lost cause.. Even if it is just pointing me in the right direction it'd be helpful. I'd be willing to donate to xda's server costs if it takes really in depth help, I've benefited a lot from the site over many years and never really had to post before because I've never had any real issues, usually much more thorough with reading things. Thanks in advance.
I have family coming over so will more than likely be back to working on it tonight..
Edit:
Jesus in doing a horrible job at life.. Posted in wrong sub.. Should be in note 10.1 2014 forum, please move to correct forum.. Sorry
Edited to add:
It's fixed, I located pit partition file, loaded that and stock rom in odin, attempted to flash but it failed, power cycled and download mode appeared on tablet, without error and odin automatically began flashing, everything is back to normal..
Click to expand...
Click to collapse
Really unlucky but in my country we use to say good end everything good. I hope to have better days from now on.
Sent from my GT-N7100

Thank you, yes things are starting to look much better. Burn is healed, my devices are working as they should..

New to flashing/upgrading

Hi folks,
I'm after some information. My Nexus 4 is about kaput now with the battery lasting about 4 hours or so with a full charge so I am looking to move over to my S4 mini for a while before buying an upgrade.
However i don't fancy rolling back to 4.4.2 from 5.1.1 as have got accustomed to it now. so there for I am looking to upgrade/flash it or whatever.
I am quite the novice and have not done this on any phone before so I am looking for a bit of help,
I have looked over xda and read some bits but think someone just telling me would be better, i'm not a tech dunce but I am not 100% confident in this at the moment as there seems to be more than one way of doing this.
What do i need to do first and foremost to make the process go as planned?
I take it I need to "root" the phone first (what does this do ? give me access to the firmware level? is that it?) using a "recovery tool" as they are called (is that right?)
Then after I have done that I can install a fresh ROM onto the phone and basic app's etc.
I have seen these guides:
http://forum.xda-developers.com/showthread.php?t=2364980
and
http://forum.xda-developers.com/gal...i9190-i9195-cyanogenmod-13-0-s4-mini-t3276141
Is it just a matter of following them or are there other things I need to do first, in between or after?
I am not bothered about anything being saved on the s4 mini it can be wiped clean and start a fresh, I don't need any of my data on it backed up
A quick bullet guide or acknowledgement of the two threads above or pointing me towards some better ones would be great and any pointers or descriptions of the acronyms or places in menu's which may have had their names changed or have been moved.
Many thanks Everyone,
Dahools

Hi!, you dont need to worry about anything, the only thing that you need is follow these guides, but make sure if you have the correct variant.

First Install Kies and connect your phone to it( For correct phone drivers). And after phone connect wells, Close kies from task manager.
You Need Odin to install a recovery software in your phone(TWRP, Clock Recovery, Philip). I only used twrp now.
Here is link below with instruction. Download recovery for your variant(i9190,i9192 or i9195 base on your model).
http://forum.xda-developers.com/showthread.php?t=2678420
Suppose if you install TWRP. Boot into recovery, And click Wipe, Do a factory reset , Clear Devil cache, Then go back and install your Firmware(cm12.1 or cm13 for your intended model). And flash Gapps as well. Then reboot. And you are done.
I have tried TWRP for both i9190 and i9192 model. and installed custom roms. Work fine.
Good Luck.

thanks fellas
I went for it with the original links and it worked. (eventually) A bit of user error on my part missing recovery mode on reboot first time and thinking it was done when it wasn't. Only putting the first bit in (root kit v2) then not realising how to flash the next parts. A bit of persistence paid off.
I have a I9195 model and rooting with that clockwork worked then loading the CM13 and then the Gapps. All one after the other in one go finally worked for me! so so far so good, just getting used to Android 6 now I think everything is working though, not put my sim in yet. will do that tomorrow.
If anyone was to follow what I did the big tip I would say is copy everything onto the SD card before you start anything, not as I did at first just putting the first bit on then thinking I can copy the next bit on later . . .

Bootloop, how to download stock for TWRP

Hello, I recently tried to root my device, I succeed in doing so but it was systemless root, I didn't know anything at the time so I tried different versions of supersu, now my phone won't boot, only fastboot and recovery works,
I visited a thread https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but I don't know which one is my stock and I'm afraid to mess it up even more,
image uploaderG]
Can you please advise me how to recover my basic stock system :F
I remember that my installed android before it stopped working was 6.01 afaik

Your Stock is 6.12.111.4
option 1:
TWRP backup - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
on post #3
Make sure to use TWRP 3.x.x.x not your current one as it seems you use the outdated version.
option 2 :
RUU - https://www.androidfilehost.com/?fid=24399965296001026
follow this guide but use the above RUU - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

Thank you, my TWRP is the latest one now because my system sort of worked when I first rooted it but when I noticed that it's systemless I tried to flash system one and my phone didn't work as intended (couldn't download things on it and some other things didn't work) that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop. Downloading that recovery, wish me luck .
Edit: it works now, thanks

One additional issue arose - my folders seem to be really wrecked, can't download anything from updates to system apps to downloading apps from playstore and even downloading apps regularly, when I made sd card my internal card I was able to download opera and wanted to select default download folder but couldn't pick any/make any and the folders were not recognizable for me (no data folder for example)
edit 2: I probably fuked up permissions too last time, fix context in twrp seems to have fixed the issue

Radenz said:
that's when I flashed newest twrp and newest super su and factory reset stopped working as of now and it's stuck on bootloop.
Click to expand...
Click to collapse
Couple words to the wise:
1) Always state exact versions numbers (TWRP, SuperSU, etc.) instead of just saying it the "latest". I've seen a lot of cases, where folks ensure us they are on the "latest" and it turns out when prompted for the actual version number, they are using something from 2 years ago!
In general when posting here, it's always best to give as much detail and specific info as possible. Vague descriptions, lack of details, and assumptions are always going to hinder more than help.
2) Always make a TWRP backup of your stock ROM before doing any mods like root or custom ROM. As you now see why, things don't always go as intended. Luckily, ckpv5 maintains a collection of stock backups. But you should already know how to revert to stock and be equipped to do so, before doing the mods. Not waiting for that "panic" moment when you need it, and can't figure it out.
I'm surprised how many folks here jump into rooting, flashing custom ROMs without leaving themselves an "escape plan" of knowing how to get back to stock. Maybe it's just my personality, but I can't fathom doing any of these things without knowing beforehand how to fix them, restore stock, etc.

Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.

Radenz said:
Thanks for advice, to be honest 3 days ago I didn't know what rooting was and searched for "root htc one m8" and got it done by a site from 2014 with a multitool that had outdated soft. What I lacked then was big red uppercase notice how to do backup because most first time rootings end up badly.
Click to expand...
Click to collapse
Yeah, completely understand if you are new to this; and we all had to start somewhere, at some time. Consider it lessons learned for next time.
A lot of folks skip the step of making a backup (before root, etc.). And also a lot of guides, YouTube tutorials, etc. neglect this step (which is something I cannot understand). So it's an honest mistake, and I'm definitely not saying that it's your fault that it wasn't done.