Related
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
I'm using the stock ROM rooted (don't know who distributed this one) and I'm getting a T-Mobile Update Service New Firmware Is Available message.
How do I not make this pop-up every day? Is the procedure different for each ROM? I thought most, if not all custom ROMs blocked these updates by default.
Searched but couldn't find a solution. Thanks.
For me it got to a point where I wasn't allowed to click cancel. I had to click download and after it downloaded it rebooted the phone and went to the flashing screen. Of course, not wanting to lose root, I didn't want it to apply. So I held down the Power button on the top of the phone and the update did not apply, but I would suggest you do it quick because it's not a very large update to apply. I don't know if the Power button to cancel an update is a real thing or if it just happened to work with me. But after I booted up my phone, the update notice was gone and I was worried that I had lost root as well, but I still have superuser permissions.
Go into Applications/ running services/ kill Htc Update and Tmobile update
Gets rid of it most of the time until reboot.
Anyone know how to make it not come up after rebooting? mines at the same point with the not letting me postpone but I rather not risk it and update and postpone
I'm assuming you guys are on SMR5 or 5r1...all you hafta do is get CR's OTA mod, its basically SMR5r1 with the OTA incorporated into it, so you'll never get that notfication cus you'll already have the OTA, and still have root and a2sd on the latest stock espresso. Plus bootanims work!
-BMFC
Sent from my T-Mobile myTouch 3G Slide using XDA App
by stock ROM rooted I thought he ment just that . the stock rom rooted ..meaning we just did the first root process ever and didnt flash anything over that
try updating the radio (check 3rd post in the slide rom bible; its the 8-5-10 one), that might work
there is also a new OTA coming up so there might be a new radio with that.
to flash radio... dload and put into sd card. boot into clockwork. DO A NANDROID BACKUP. then "apply to sd card". install zip from sd. click the zip for radio. install and reboot. there'll be an awkward image before reboot (normal).
also, next time PLEASE use the Q&A section.
Hey my evo doesnt want to update it!!?? why??? it reboots.. then i get the loading thing that is starting to do it. but then i get the TRIANGLE WITH THE EXCLAMATION MARK.. with the little Android bOY.. LOL.. Could it be because its rooted? :/
HOPE ITS NOT BECAUSE OF THAT!! :/ HELP PLEASE
You don't need to install the latest 3.70 release...it is just a maintenance upgrade and has no improved functionality ...I hope you made a nandroid bc you can restore that to get back to your previous state. Good luck
Sent from my PC36100 using XDA App
Im new to all this man.. i dont really know anything.. like whats nandroid?? sorry for a stupid question.. but it says is has the Swype typing thing..
One more question.. what happens if i reset the Whole phone? like with the option it has to reset it to its FACTORY DATA RESET.. WILL IT WORK? OR WILL IT JUST NOT BOOT ANYMORE? OR WILL I STILL BE ROOTED? TH \ANKS
never accept a sprint upgrade with a rooted phone, it will mess your phone up...since you dont know what a nandroid is, im assuming you never made one..you are going to have to restore the phone back to original out of the box and a factory data reset is not the way to do it...
try this ...download the 3.30 release from this site and put in root of sd card http://shipped-roms.com/index.php?category=android&model=Supersonic
EDIT...in order for your phone to see this ..boot into bootloader..when phone is off, hold the volume button down and then hold the power button...the phone will see it and flash and update it...you will be back to stock and not rooted...you will have to re root the phone and then create a nandroid...
read this for more info on nandroid backup http://www.simplemobilereview.com/android-rooted-what-is-nandroid-backup/
to recap..never accept a sprint ota upgrade with a rooted phone, you will mess your phone up (as you already know) and once rooted, always create a nandroid...if you ever mess something up, you can restore that nandroid and restore your phone to working condition
also..once you are rooted and you want to update to the latest sprint over the air updates, search this forums for rooted stock RUU and you can then flash the lastest rom from sprint which is rooted...instead of trying to accept the OTA like you did
good luck
oK.. I WILL DO THAT WHEN I HAVE TIME.. LUCKLY MY PHONE DIDNT MESS UP TRYING IT.. LOL..
oK so installing the ROOTED STOCK RUU.. it will already be rooted, and i can still install sprints updates and upgrades with no problem correct?
THANKS FOR THAT BUD! SOUNDS EASY TO FACTORY RESET THE PHONE THANKS!!
drummer2780 said:
oK.. I WILL DO THAT WHEN I HAVE TIME.. LUCKLY MY PHONE DIDNT MESS UP TRYING IT.. LOL..
oK so installing the ROOTED STOCK RUU.. it will already be rooted, and i can still install sprints updates and upgrades with no problem correct?
THANKS FOR THAT BUD! SOUNDS EASY TO FACTORY RESET THE PHONE THANKS!!
Click to expand...
Click to collapse
Once you restore to factory non rooted and then re root...you have install the rooted ruu to get the latest sprint upgrades ...you don't accept any ota updates ever...just flash the most current rooted ruu and you will have the latest sprint updates
Sent from my PC36100 using XDA App
Oooh ok ok.. i think i get it.. THANKS! I APPRECIATED!!
weaselp1 said:
Once you restore to factory non rooted and then re root...you have install the rooted ruu to get the latest sprint upgrades ...you don't accept any ota updates ever...just flash the most current rooted ruu and you will have the latest sprint updates
Click to expand...
Click to collapse
Self confessed complete Android/Evo newbie here... I didn't even know how to access the settings on the phone until about 30 minutes ago. I've been working with iPhones since day one and have jailbroken many releases, so I get the general idea. It's actually my wife's "work" Android, and a co-worker of hers rooted the phone at some point. She tried to install the auto-download 3.70.651.1, it failed, and she gave it to me. Pulling the battery and resetting seemed to get things back to working, but now I'm taking over management of this phone and getting things right.
Here is where the phone is:
Nag screens about updated software seen. Update now selected. Update seemed to fail with a triangle/exclamation point, phone locked.
Pulling battery gets a normal reboot. Still get nag screen about "do you want to update"
Settings/aboutphone/software info shows "Software number 3.29.651.5" after failed update
Here's what I've done so far:
On software update screen, chose to "delete update". Rebooted. No more nag.
Turned off "scheduled check" for system software updates in Settings menu.
Figured out how to boot into the recovery menu. Looks like "Clockwork backup" was already installed. (ClockworkMod Recovery v2.5.0.1)
Created a nandroid backup using clockwork.
Rebooted phone
Mounted the SD card to my Mac, backed up the SD card including hidden files.
Verified creation of clockworkmod nandroid.md5 file
A few questions:
Once you restore to factory non rooted and then re root...you have install the rooted ruu to get the latest sprint upgrades Is this really necessary? Can I not just find a latest/greatest "rooted ruu" and overlay it on top of my current configuration?
I see some threads with titles like "[ROM] joeykrim-SDX-original-5.1 Odex *Stock Rooted 3.70.651.1* Dec 15th 2010". Is this an example of a "rooted ruu"?
This thread says I need to install "unrevoked 3.2.1" and "unrevoked forever". I'm guessing these are different tools than whatever was originally used to root my phone. Any chance installing them will conflict?
If I go back to a stock 3.3 ruu, what happens to all the applications and info already on the phone? Does it just overlay the software, or wipe everything clean?
TIA for helping an Android/Evo newbie out!
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
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.