Develop Bugs

[Q] Need some direction...

Hey guys. I'm pretty tech savy when it comes to computers and all, but for some reason all this "root", "radio", etc. is all mish mosh to me. I'm pretty sure I have my phone rooted (followed a tutorial). I just got the prompt for froyo from Verizon, and I read somewhere i shouldn't install it from Verizon if my phone was rooted. What I want is to just reset my phone without the root, and be able to install 2.2 just as if I never rooted my phone, because I know I'm going to screw something up that's going to end up costing me. So any help??

you sound like me a few months ago
The OTA will update your OS to 2.2 and will update your radio along with alot of other things.
If you hold optical button and power at the same time (after the phone is off) it will boot to the Hboot screen. on the top of that screen you will see S-ON. This is the security toggle for the phone. I cant tell you what or why it does what it does. but it essentially makes its so you cant flash custom roms without rooting. Before you update your phone to the OTA, you want to google "unrevoked3" . download it, and run it. This will give you the Clock Work Recovery which will load instead of the phones built in recovery console. as soon as you do that, then you run "unrevoked forever" this will set the phone to S-OFF.
once you get S-OFF. Revert your phone back to stock by updating with a stock pb31gm.zip (you should be able to find that all over). this will make your phone stock again (by removing the root you did to it by running unrevoked3) but keep the S-oFF setting.
so by the end of the process you will be totally stock, no root, and have S-OFF. then boot up, install OTA, and then load the update with clock work recovery and you will be all set.
its all kinda confusing if you dont read along the forums. but once you get it, its pretty simple.
Another poster in another thread already addressed this. here it is in simplistic form
use google to look up anything you dont understand.
Assuming you have a truly stock Incredible (meaning you didn't force any third party roms or leaked radios), then you follow this order:
1. Unrevoked Flash/Recovery - Adds Clockwork Mod and Superuser permissions to your phone
2. Unrevoked Forever - Adds S-OFF functionality, which means that the HBOOT startup will no longer check for updates that are signed with HTC's super secret signature... Meaning you can flash anything to the phone.
3. Flash Original Stock Recovery - Removes the Clockwork Mod recovery console. Since you have S-OFF, you can return CWM to the phone whenever you damn well please. The original stock recovery is necessary for the OTA to commence, because it is developed to rely on the stock recovery console.
4. Wait for OTA
5. Upon receiving OTA, flash Clockwork Mod to the phone via HBOOT (using a PB31IMG.zip containing it)
6. Flash the root payload via Clockword Mod recovery console.
7. Go to bed and make love to your wife after beating on your chest in victory like tarzan.
8. Reboot phone, bask in Official Froyo coupled with Superuser permissions.
9. Download the busybox installer from the market and install busybox to the system.
10. Make love to your wife again.

Keyboards said:
Hey guys. I'm pretty tech savy when it comes to computers and all, but for some reason all this "root", "radio", etc. is all mish mosh to me. I'm pretty sure I have my phone rooted (followed a tutorial). I just got the prompt for froyo from Verizon, and I read somewhere i shouldn't install it from Verizon if my phone was rooted. What I want is to just reset my phone without the root, and be able to install 2.2 just as if I never rooted my phone, because I know I'm going to screw something up that's going to end up costing me. So any help??
Click to expand...
Click to collapse
I didnt read your post all the way before i responded... sorry
since you are rooted already, just get unrevoked forever to get S-off.
your rooted and you got the OTA , so that answers some questions for people right there, there has been much confusion about rooted phones will get the update. I guess you did
People say not to update because it will remove your root and not allow you to re-root. By flashing S-OFF you can re-root anytime you please because the phones security check is off.
The problem is, you need root to get S-off. If you flash first, with S-ON you wont be able to re-root to get S-off, make sense? lol. At this point in the game you can only get S-off while using 2.1. if you got to 2.2 with s-on your stuck for a while with no root.
If that doesnt matter to you, then dont worry about it

If you only rooted your phone and did nothing else, you can safely apply the update. Doing so will remove root.
If you installed a custom recovery you will wanted to install the stock recovery before doing the upgrade.
If you plan on keeping root you will need to install unrevoked forever to enable security off (S-OFF) before starting the upgrade process.
Hope that helps a little anyway.

I never did anything to the phone after the root. The only thing that changed on the phone was superuser was put on my app screen, and I don't even know what that does. I don't care for root that much anymore, it sounded cool, but I'm not the kind of person who knows how to use it to it's full potential. So all I have to do is hit install now on the 2.2 from Verizon and I should be good to go?

Keyboards said:
I never did anything to the phone after the root. The only thing that changed on the phone was superuser was put on my app screen, and I don't even know what that does. I don't care for root that much anymore, it sounded cool, but I'm not the kind of person who knows how to use it to it's full potential. So all I have to do is hit install now on the 2.2 from Verizon and I should be good to go?
Click to expand...
Click to collapse
well you will have to run a stock pb31img.zip to remove the clockwork recovery , or the update will fail
lemme look around and see if i can find you a stock image. 1 sec
here it is
http://d01.megashares.com/index.php?d01=CHoQD3B
once you get it downloaded, you need to rename it to PB31IMG.zip, place it on the root of your SD card (meaning dump it on the sd card , not in a folder on the SD card)
hold optical button and power button until you get the hboot screen
with "bootloader" selected hit the power button to select it
the phone will look for the PB31IMG.zip file and load it. wait a few min and when it asks you to reboot, say yes. It may or may not ask you to update again , if it does, say yes, if not let it reboot the phone.
once that is done, run the OTA update you got and your all set.
doing this will retain your stock image, and remove root. THIS WILL WIPE YOUR PHONE. so if you have anything you wanna save do it before you proceed

msticlaru said:
doing this will retain your stock image, and remove root. THIS WILL WIPE YOUR PHONE. so if you have anything you wanna save do it before you proceed
Click to expand...
Click to collapse
Thank you. Will my Market history remain?? Meaning if I bought an app, I can just redownload it??

Keyboards said:
Thank you. Will my Market history remain?? Meaning if I bought an app, I can just redownload it??
Click to expand...
Click to collapse
yup, anything you bought is saved to your google account. you just open the market, hit menu, and then hit "downloaded" and its all there

msticlaru said:
yup, anything you bought is saved to your google account. you just open the market, hit menu, and then hit "downloaded" and its all there
Click to expand...
Click to collapse
That's great, thanks again. I'm going to give it a shot now.

Keyboards said:
That's great, thanks again. I'm going to give it a shot now.
Click to expand...
Click to collapse
Ok I did it and it looks like it's going smooth! One thing I noticed is that after I formatted my card to FAT32, it said my capacity was only 200MB? Is this normal?
It's a 16GB card.

Keyboards said:
Ok I did it and it looks like it's going smooth! One thing I noticed is that after I formatted my card to FAT32, it said my capacity was only 200MB? Is this normal?
It's a 16GB card.
Click to expand...
Click to collapse
interesting... windows says its 200mb or the phone does? see what it says after the update. Maybe it created a 200mb partition?

msticlaru said:
interesting... windows says its 200mb or the phone does? see what it says after the update. Maybe it created a 200mb partition?
Click to expand...
Click to collapse
Phone also says 200MB. Phone is back to stock and ready to roll. Still haven't recieved a prompt for froyo yet, checked about phone, still running 2.1 update 1.

Keyboards said:
Phone also says 200MB. Phone is back to stock and ready to roll. Still haven't recieved a prompt for froyo yet, checked about phone, still running 2.1 update 1.
Click to expand...
Click to collapse
I think i read somewhere that when you don't accept the update it will wait like 20 min or so before it prompts you again. I don't know the exact time limit tho. you could do the *228 update just to make sure its registered right. i don't really know if that will help push the update or not.. but may as well do it.
as far as the card. after the update try formating it again. kinda of an odd issue. could try googling it

msticlaru said:
I think i read somewhere that when you don't accept the update it will wait like 20 min or so before it prompts you again. I don't know the exact time limit tho. you could do the *228 update just to make sure its registered right. i don't really know if that will help push the update or not.. but may as well do it.
as far as the card. after the update try formating it again. kinda of an odd issue. could try googling it
Click to expand...
Click to collapse
Still no prompt. Restarted, did *228, nothing. This card problem is also an issue now. It's showing only 200MB on Mac, PC, and the Incredible.

Keyboards said:
Still no prompt. Restarted, did *228, nothing. This card problem is also an issue now. It's showing only 200MB on Mac, PC, and the Incredible.
Click to expand...
Click to collapse
as far as not getting the prompt, you got me. I cant pretend to know how verizon does their business. Their website says if you ignore the update, it will continue to big you until you get it.
As far as the memory card goes. Thats not really a phone issue. My experience with formatting memory cards stops at the format. Never had it format it wrong. If it was happening to me, i would format it again with a format tool. I dont know your experience when it comes to troubleshooting problems like this. I would start by using multiple format tools on my PC, you said you have a mac, you can try formatting it with the mac. It seems like a simple fix, as it was reporting the right size prior to the format.
Did you format it in windows? did you just right click on it and hit "format" ? try using the disc management built into windows. It should show you the total size of the disc formatted or not. Its possible it somehow was formated as a 200MB partition. if that happened, then you have a 200MB logical partition, and the rest is unformatted and therefor un readable by anything other than a disc management type tool.
depending on your Operating System, your mileage will vary, but google how to open "disc management" for your OS. Stick the SD card in your card reader, then use the tools in disc management to format it to the correct size.
hope that helps.
Also, check your phone. settings > about phone > system information. Ensure you are running 2.1 update 1. and baseband 1.x. If you are, then its a waiting game. also, in the same screen click on "system update" and see if it has an update available. if not... you can always call verizon and play dumb. "ya i got the update, but i had to reboot my phone, when it booted back up i didnt have the update anymore!" see if maybe they can push it to you.
if all else fails you can load the RUU manually.

[Q] Reflashing to Stock on Incredible with occassional boot loop?

A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?

kmandel said:
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
Click to expand...
Click to collapse
You can reflash the phone to stock with what incredible users call an ruu (rom update utility), however flashing older versions or downgrading the os is not allowed with s-on (security on). His best bet in my opinion would be to root and s-off the phone, and then flash a custom rom. However if hes not into all of that he can try to do an ruu and see if it fixes things. Doing so will wipe the phone compleetly and he will loose all of his apps and data. A pc running windows xp or newer is required.
1. Download the ruu http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, and place it somewhere on your pc.
2. Download and install HTC Sync http://dinc.does-it.net/HTC-Sync/3.0.5606/setup_3.0.5606.exe.
3. On the phone go to menu - settings - applications, uncheck fastboot if it is checked and then select development, and make sure usb debugging is checked.
4. Connect the phone to the pc with the usb cable, and wait for any drivers to install on the pc. The phone should be in charge only mode.
5. On the pc run the ruu file and follow the instructions it gives you.
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.

cmlusco said:
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
Click to expand...
Click to collapse
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.

kmandel said:
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
Click to expand...
Click to collapse
Well not like it originally came from the factory 2 years ago (with froyo), but if they were still selling them today or you get a replacement, that is how it would come from the factory. The last update 4.08.605.2 fixed all the major issues and shouldnt give any major trouble. The only other option would be to root.
Verizion is pretty good with customer service, you may have to find a knowledgable employee but they can do it for you.

We tried the "ruu" approach without success. The drivers installed on the PC, the phone goes into debug mode, and we can even run "adb" manually and talk to the phone. However, when either "ruu" or "Ht Sync" try to talk to the phone they just say the phone is not connected.
If we run the task manager on windows we can actually see "ruu" invoking "adb" and there is no long timeout. It appears that ruu just doesn't like the answers.
Again running adb manually for example with the shell option seems to do all you expect adb to do. This is with both the versions linked above and the updates they end up offering.
Any ideas?

OK, found a mistake. I didn't realize that to do the ruu flash I needed to turn off the phone and vol-down/power it into htboot mode.
With that done the update program sees the phone notices it has lastest firmware and offers to update it to the same version. I say yes, and the phone reboots and the PC tells me it will take 10 minutes to flash, then 2 seconds later tells me it succeeded and the phone reboots.
Obviously it did not flash anything. Am I missing something?
Also any pointers on how to flash an earlier stock rom (and where to find it)?

Rooted S-off and still getting ota update

My Dinc is rooted S-off and I'm still getting ota update notification. I tried to run the update and it does nothing....

If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.

PonsAsinorem said:
If you're on a stock (even rooted) ROM, you'll get the ota notification. But it requires stock recovery to flash. I haven't looked into the actual zip, so I don't know if it'll flash via CWM or not. It used to not, and I doubt it's changed.
Click to expand...
Click to collapse
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.

I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app

Richard6292 said:
I need to get the latest OTA update, but can I only get it through a new Rom or can I just gets new OTA update to work with my current Rom?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You have to be complete stock to sucessfully update ota. Just flash the stock 4.08.605.15 rom in the dev section. You'd be getting the same thing, without all the hastle of ruu'ing, updating ota, and then rerooting.

Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app

Richard6292 said:
Thanks for the info! But after that, if I were to relfash my current Rom I'd just be back in the same situation right?:/ I wish my current Rom would be update but the dev'r went away..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Right, if your current rom is not based on 4.08.605.15, then you will get the ota notification. Even if you got the actuall ota to install, it would more than likley mess up the rom, and then you would have to reflash the rom and you would be right back where you started. If you want to stay on your current rom but stop the ota notification, do as i said a couple posts above and edit the build.prop file to make the update server think you already have the latest ota. What rom are you currently on?

Ok, thanks for the help!!
Sent from my PC36100 using xda app-developers app

I am using TOB so can I install the update without messing things up?

joeyz400 said:
I am using TOB so can I install the update without messing things up?
Click to expand...
Click to collapse
No tob has stock apps removed and is deodexed. The ota checks to make sure all original apps and files are present and unchanged. If you wabt to get the actuall ota tou need to ruu to stock 4.06.605.3 and then ota to 4.08.695.2 and then ota to 4.08.605.15. However tob V2.1 has been updated to 4.08.605.15 already.

Experience with this OTA update
I can't post yet to the development forums and I saw that cmlusco was on here so just wanted to share my experience. I have an SMOLED Droid Incredible and I'm rooted, S-OFF on the latest CWM recovery and I was using wildstang's stock ROM from the last update back in November 2011. I got the notification, searched the forums, and ended up installing cmlusco's stock deodexed ROM, after doing all the requisite wipes and checking the md5. My initial experience was great, apart from once when the phone simply died with a black screen and was completely unresponsive. Battery pull solved that. After I was done getting all my apps back on there (mostly via downloading and then for some of them just restoring the data from Titanium Backup), I did a Titanium Backup and a nandroid backup in the recovery. After all of these were done, I started having quite a few freeze issues. I think I had three in a row before I had one while in the process of connecting the phone to my computer. Had to do the battery pull method each time but the last time, the phone must have been right in the middle of mounting to my laptop because all of my downloaded apps were "gone". As in, they were not in the app drawer and all the icons were the default Android icon on the home screens. I think something happened with the freeze in the middle of the mount. If I reinstalled an app from the market and tried to restart it, it force closed. Then, if I uninstalled and reinstalled it, it did work. But I was still getting some force closes so I figured it might just be easier to flash the ROM again, which is what I did.
So now I'm back up and running, and mostly everything is okay. I did get another freeze while installing an app and waited for a while but since the phone was still unresponsive, I did the battery pull again. Stuff is working but I thought I'd share my experience and see if anyone else had something similar happen. Oh, by the way, I also updated to the latest radio but hadn't the first time I used this ROM. And cmlusco, thanks a lot for posting that and being very patient in the forums. If this ROM fails again, I might try Touch of Blue.

cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
Thanks, I changed that line and the annoying system update is gone

cmlusco said:
That is correct, the ota will not work unless you are complete stock. Meaning stock recovery, all original and unmodified apps and framework files, and you must still be odexed.
If you just want to stop the update nag you can go to /system with a root file explorer and open for editing the build.prop file. Look for a line that starts like this " ro.build.fingerprint= ", change the whole line to look like this without the quotes " ro.build.fingerprint=verizon_wwe/inc/inc:2.3.4/GRJ22/389630.15:user/release-keys ". This tricks the update server into thinking you already have the latest update.
If you want a rom with the new update, there is the Stock 4.08.605.15 Rom and Touch of blue. One is pure rooted stock, and TOB is mostly stock but debloated and lightly themed.
Click to expand...
Click to collapse
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks

ggoodman1022 said:
So, I edited the "ro.build.fingerprint" line, and I'm still getting the notification... I've tried the "fix" of renaming the /etc/security/otacerts.zip file to otacerts.zip.bak, which some suggest. Hell, I even ended up deleting the whole file. When that didn't work, I froze /system/app/updater.apk. Still nothing, so I deleted that file as well. Nothing is listed in my /cache folder, where some people have noted that the download stores itself. I had the 4.08.605.15 update before, and it caused my phone to freeze a lot, and randomly reboot over and over for hours. During those reboots, half my apps got deleted as well.
Needless to say, I don't want the stupid update!! But nothing I can find on any forum is stopping my phone from getting the notification every 15-20 minutes. I've tried flashing a few different ROMs, but my phone gets stuck in a boot cycle with any of them. Just the other day, I went to flash the newest CyanogenMod through CWM, and it just kept showing the blue android guy on a skateboard for (no joke) about 3 hours. I ended up pulling the battery and flashing my stock recovery.
Please let me know if there's anything else anyone can think of that might stop the notification. I'm still 3 months out from being eligible to upgrade my phone, and I'd rather not deal with the notification popping up over and over and over for that time
Thanks
Click to expand...
Click to collapse
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.

nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
Also you must be s-off, or adb pull edit and push the file while in recovery.

Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...

nschiwy said:
make sure your file explorer is in r/w (read/write) mode or the changes that you made will not save. there is a button in the upper right part of root explorer if that is that app you are using.
Click to expand...
Click to collapse
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
cmlusco said:
Also you must be s-off, or adb pull edit and push the file while in recovery.
Click to expand...
Click to collapse
I've had s-off since a few days after I got the phone last year.
omniatic said:
Try flashing this. Got rid of the nagging when I was on GB. Should take care of it.
http://db.tt/zPhTShuA
sorry...I was on the phone...
Click to expand...
Click to collapse
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well

ggoodman1022 said:
It is definitely in r/w mode. I restarted the phone, cleared cache, then checked the file again to make sure the edit was still there. And it was...
I've had s-off since a few days after I got the phone last year.
I restored from a prior backup to undo all the changes I made, so I'm going to try each of the methods again, and if nothing works, I'll flash this.
Thank you all. I've been relying too much on "one-click" solutions in the past, but I'm now trying to get more into the actual dev side of things, so I can help out with this kind of stuff as well
Click to expand...
Click to collapse
I retried all the methods, and flashed the file mentioned above. Still no luck
Stupid notification pops up over and over and over... Guess I may either have to update, or deal with the notification until October when I can upgrade my phone. Or try flashing a custom ROM, even though I like the stock ROM

You could always flash cmlusco's touch of blue ROM which is an optimized version of the latest OTA, so you wouldn't have to worry about update notifications on that one for sure (at least on the latest version).
http://forum.xda-developers.com/showthread.php?t=1492720
but there are lots of options here
http://forum.xda-developers.com/forumdisplay.php?f=638

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

Ota security update 9/29/15

Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.

andygold said:
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
Click to expand...
Click to collapse
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.

wildbean98 said:
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
Click to expand...
Click to collapse
I took the update against my better judgement and sure enough soft bricked and now phone wont go into DL mode...grrrr

Major issues here as well. My SD card is now blank and doesn't want to mount. Big slowdowns as well. Any way to remove this update ?
Sent from my SHIELD Tablet using Tapatalk

Was finally able to DL apps, but at a crawl. I cleared the cache including dalvik, and everything is back to normal. And I'm still rooted!
I used Cache Cleaner NG from the play store

Soft bricked
I have bricked my phone after accidentally accepting it. Got back the phone again with lg flash tool. Once restarted the phone, rooted it, used titanium backup apk to freeze the software updater.

I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.

Actually guys, its most likely that malware piece that was making its way around. Didnt anyone else read about it a few days ago? Let me hunt it down and see if i can post a link here. Standby....
Update: hold the phone, i may have been mistaken. Standby...
Now im soo broke i cant even pay attention!

ThaHawk said:
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Click to expand...
Click to collapse
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.

sdivk said:
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
Click to expand...
Click to collapse
I stand corrected, your absolutely right!

ThaHawk said:
I stand corrected, your absolutely right!
Click to expand...
Click to collapse
Thanks. If you have a rooted lg e980 without custom recovery, you can use quickboot apk to enter stock recovery, which has limited features.
The problem with unlocking bootloader and use custom recovery is, if there is an update, there is no way to relock the bootloader and flash stock recovery. If sombody can shed the light on this matter, i really appreciate it.
I am looking for a way to relock the bootloader and install stock recovery without using lg flash tool.
Not that i am expecting an update from AT&T anytime soon.

+1

its better its included on CM based ROMs also