Develop Bugs

[Q] Upgrading to stock 2.2 rom with rooted phone (unrevoked 3)

Hi guys
I rooted my desire with unrevoked 3, and now I want to install stock froyo 2.2 update and it doesnt seem to work. It stops unpacking update after restart and shows exclamation mark and the droid, pressing menu from there brings up clockwork recovery. Is there any way to easily get this working or are the two options to either unroot or install custom rom?
In case of unroot, do I have to reflash the whole device loosing all settings and apps?
Hope someone has an answer for me, starting to get anxious to try the new rom out

Am having exactly the same issue. First I thought there was something wrong with the download as the Clockwork Mod says 'failed to verify full file'. Can someone help?

There are many stock roms with root access on this forum. Can't you just use one of them? If you flash the official upgrade, it will overwrite HBOOT as well, making it impossible to root the phone again until someone finds a new rooting method.

snowroller said:
Hi guys
I rooted my desire with unrevoked 3, and now I want to install stock froyo 2.2 update and it doesnt seem to work. It stops unpacking update after restart and shows exclamation mark and the droid, pressing menu from there brings up clockwork recovery. Is there any way to easily get this working or are the two options to either unroot or install custom rom?
In case of unroot, do I have to reflash the whole device loosing all settings and apps?
Hope someone has an answer for me, starting to get anxious to try the new rom out
Click to expand...
Click to collapse
Ok first of all since you have rooted your phone, did you make a backup? Did you use nandroid? Have you made a gold card? Okay this what I did with my phone. Use the stock ROM from UK 1.21.405.2 WWE version and flash that to your phone (rooted of course with gold card).
Once you have flashed the UK ROM you should get a system software update. BUT......you have to make sure you download one of the rooted Froyo that can be found in xda.
DON"T DO WHAT I DID AND USED A STOCK (unrooted) Froyo! Because now I can't root my phone until someone in here finds a way and shares it.

Ok, how do I flash one of the rooted roms and how do I go about installing it and still keeping the data on the phone? I know there are guides all over this place, but I find them a bit hard to understand a lot of the time...

Happy to use a custom Rom. There are so many here though - any suggestions?

rahul77 said:
Happy to use a custom Rom. There are so many here though - any suggestions?
Click to expand...
Click to collapse
Try them all It's fun and addicting.

But will flashing a custom rom wipe the device, and how do I go about getting all apps, sms'es and so on back on the device? I guess nandriod backup has something to do with it, but how do I use it right?

Titanium backup in market. Restor all data and apps. thet use all.

Titanium backup won't run...
Hmm, titanium backup is installed but it won't run claiming I don't have root or busybox is not installed. Installed busybox installer, it says I have root, but stops saying it might not have enough privileges or it is unable to mount...
What next? Anyone got any bright ideas? Thinking more and more about wiping device with a clean RUU and getting the stock 2.2 update, but would like to keep all my info, sms's and so on...

EVO 2.2 UPDATE (Froyo), HELP !!!

Guys,
My Evo says Froyo 2.2 is avail for download when I check HTC Updates... I hit accept, it downloads, then asks if I want to install NOW... I HIT YES, and it takes me to the boot loader page, THEN DOES NOTHING.. It doesn't boot into recovery mode like it is supposed to, and it just sits on the Boot loader screen, NO TRIANGLE, NO BAR on the bottom showing the progress, IT JUST SITS THERE on the boot loader page with the 3 Androids on the bottom... I have already tried to hard reset the phone, BUT that didn't work... PLEASE HELP !!! Is there a way to HARD reset my EVO BACK to BEFORE ALL OF THE UPDATES??? IS THERE A WAY TO Force boot into recovery to apply the "update.zip" ??? Please advise...

Mine did'nt go no where near the bootloader screen...
I hit the download...then it just installed like any other app...except it brought me to a bar progress page a couple of times. Then the phone rebooted and whala...froyo.
I must say this...I was previosly rooted but unrooted to do it!!!
Are you rooted or unrooted to start off with?

Was rooted, but then I did the "update of June 29th" and ruined ALL of my fun... Is there even a way for me to root my phone now??? How do I get it to go into recovery?

Same issue
My EVO ISN'T ROOTED, and I'm having the same exact problem

You're hosed root wise until someone cracks the rom, if they crack the rom. Most likely you'll need to update to the official version once HTC releases an upgrade as they claimed they would eventually do on Twitter.

im not trying to root my phone, i just want froyo

right, I WAS rooted, the update in JUNE fixed that for me =(... NOW I just want FROYO which is available from Sprint/HTC OTA, it just wont install?????????? I think I can install it as an update.zip if I could get my phone into RECOVERY mode... When at the bootloader, if I hit Recovery, it just boots back to the BOOT LOADER????

I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!

This is a great recommendation, but I haven't done any ROOT or ROMing to my phone since I've owned it, I've stayed true to the true image they released, and I'm not comfortable downgrading it to some other image that wasn't on the phone. I attempted to do the instructions outlined and I was unable to get pas the stage of pushing the:
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
to the phone. It says USB error, and I have debugging mode enabled.

cardiox said:
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
Click to expand...
Click to collapse
I RE-Loaded this version, as the other "older" versions would not work (re-loaded, as this is what I already HAD on my phone)... It wiped the system, and ALL of my info/apps (make sure you back up) and then I was able to do the Froyo Update... YES !!!! Thanks...
http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe

I did the same, thank you !

No prob...have fun!!!

Froyo Update Won't Install
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick

Nick,
Please read the earlier posts, and follow the link from Cardiox... He said the following...
"I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-...urn-stock.html
This is the route I took and was just like you...I had no probs this way!"
Then read my posts, and you will see that I had the SAME problem you are having, and this worked for me... I posted the thread... It is pretty easy if you follow the instructions... Let me know if it works for you... Good luck !!!

wolverinexc said:
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Click to expand...
Click to collapse
I am not a genius by no means thus I am only sharing info that I have from personal trial and error. If you are going to a bootloader screen during this update process and your SD card is mounted then you most likely will need to bite the bullet and either do a factory reset or follow the link instructions so given. For some reason this update can not find the original factory code or RUU that it is trying to update. Sounds like your SD card is mounted but it can't find it...I would strongly consider just starting over with that link program. It does not root you it just puts you back square one with factory code. Then the update will have something to build off of...which you apparently don't have for whatever reason.

Ok, this is what I needed to know. I'm backing up my stuff with bitpim and will just do this. Thanks for all the help and the speedy responses!
-Nick

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

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

Android update!

Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend

Throws a signature verification failed error.

Try again with the new method

Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.

Why go to 2.3.6? It´s better than 2.3.5 customized?

Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara

AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.

narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.

narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.

Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.