Related
This guide will allow you to install the new OTA 3.29.651.5 when you have clockwork installed and will guide you into re-rooting the phone afterwards. (This does NOT wipe your data)
I am sorry if someone already posted this.
Requirements
1. Froyo 2.2 version 3.26.651.6 (Stock)
2. Clockwork
3. S-OFF
Files to Download (If you have a file manager on your phone you can just direct download them with the EVOs browser)
1. OTA_Supersonic_3.29.651.5 This is the new OTA update
2. ClockworkMod recovery for EVO 4G Clockwork (I know you already have it. This is to reinstall it)
3. su-2.3.6.1-ef-signed.zip Superuser (This is also to reinstall)
Step one
Place OTA_Supersonic_3.29.651.5 on your SD cards root folder. Power off and reboot holding Volume down. Once the bootloader is up goto recovery so clockwork loads up. Choose apply zip from sd card. Choose select zip on sd card. You will see the OTA file on the list flash it. Just wait for it to install it will reboot the phone show a progress bar reboot again they show a percentage etc it takes a few minutes.
Now you have the update installed, but the update removed clockwork and root.
Step two
Place ClockworkMod recovery for EVO 4G on your sd card root folder. Power off and reboot holding Volume down. The bootloader will scan the new will and ask you to press Volume up to install. Install it.
Now you have clockwork installed again. Please remove the clockwork file from the root of your SD card before going to step 3.
Step Three
Place su-2.3.6.1-ef-signed.zip on the SD cards root folder. Power off and reboot holding Volume down. Once the bootloader is up goto recovery so clockwork loads up. Choose apply zip from sd card. Choose select zip on sd card. You will see the SU file on the list flash it.
Now you are updated and rerooted. (I have been told it is possible to just rerun unrevoked instead of doing step 2 and 3. I did not test that method. I am simply showing a different method.)
Update
I am now getting 53 FPS with FPS 2D
Nice, similar to what I did, thanks for posting this guide. Saves time, I will refer people to this thread.
-CC
Good guide...but have you seen http://forum.xda-developers.com/showthread.php?t=790342 Apparently there is issue at present after the OTA that prevents S-On so you can return your phone, if necessary.
Guide would be even more helpful if you put in the Amon RA option for those that prefer it, then retitle thread.
Jim
Just get the stock rooted rom it is easy as that!
stealth-twinturbo said:
Just get the stock rooted rom it is easy as that!
Click to expand...
Click to collapse
Agree with you but look at some of the other threads on rooting, etc. and it's amazing how many folks are determined to do the OTA...this gives a good reference link to use for them.
Jim
jelive said:
Good guide...but have you seen http://forum.xda-developers.com/showthread.php?t=790342 Apparently there is issue at present after the OTA that prevents S-On so you can return your phone, if necessary.
Guide would be even more helpful if you put in the Amon RA option for those that prefer it, then retitle thread.
Jim
Click to expand...
Click to collapse
Amon RA gets more difficult as it requires you to flash the engineering bootloader 0.76.2000 to have it work properly...
-CC
So if we have the Eng bootloader this will work? ie, it's not just for unrevoked users?
Do you have to make a nandroid backup or anything before doing this? Also when you flash back the clockwork mod will it gives full root access s-off again? Thanks
I'm seeing alot of posts saying we have to wipe before we flash the rooted ROM. How come the OTA doesn't require losing all your settings/data, but flashing the update does? That's the only thing holding me back...
Ingenium13 said:
So if we have the Eng bootloader this will work? ie, it's not just for unrevoked users?
Click to expand...
Click to collapse
No it will not, you will lose root if you have not run unrevoked forever to set s-off permanently. The eng boot loader's s-off would be overwritten and root would be lost.
Ingenium13 said:
So if we have the Eng bootloader this will work? ie, it's not just for unrevoked users?
Click to expand...
Click to collapse
I used the Amon_RA with 0.76.2000 engineering bootloader PC36IMG.ZIP found in the forums. Then just reflashed the su app, coming from the 3.26 stock rooted via unrevoked 3.21.
-CC
greyopaque said:
I'm seeing alot of posts saying we have to wipe before we flash the rooted ROM. How come the OTA doesn't require losing all your settings/data, but flashing the update does? That's the only thing holding me back...
Click to expand...
Click to collapse
This does NOT I repeat NOT wipe the phone.
This is not a rooted ROM. This is the official update. (This is why you don't have to wipe the phone)
The issue is with clockwork installed you cant install the official update unless you install it through clockwork. This is what step 1 in the guide tells you how to do.
Step 2 and 3 tell you how to get clockwork and root back after the update removes them. (Note you must have S-OFF or step 2 and 3 will not work)
Perfect for us unrEVOked users. The only change I saw was the superuser icon/interface is slightly different than the little ninja guy that unrEVOked gives us.
Thanks!
tws101 said:
This does NOT I repeat NOT wipe the phone.
This is not a rooted ROM. This is the official update. (This is why you don't have to wipe the phone)
The issue is with clockwork installed you cant install the official update unless you install it through clockwork. This is what step 1 in the guide tells you how to do.
Step 2 and 3 tell you how to get clockwork and root back after the update removes them. (Note you must have S-OFF or step 2 and 3 will not work)
Click to expand...
Click to collapse
I understand now... that makes sense. If that's the case, then I'm thinking updates are cumulative.. I'm still on 1.47, since the original Froyo broke audio streaming. I was waiting for that fix to be officially pushed down before I update (by the way, does this update officially fix that?). I'm assuming I have to install the previous update first, before I do this one.
skbgiants said:
Perfect for us unrEVOked users. The only change I saw was the superuser icon/interface is slightly different than the little ninja guy that unrEVOked gives us.
Thanks!
Click to expand...
Click to collapse
Ya the superuser file I used is probably more up to date. I got it from the superuser thread.
Link
http://forum.xda-developers.com/showthread.php?t=682828
greyopaque said:
I understand now... that makes sense. If that's the case, then I'm thinking updates are cumulative.. I'm still on 1.47, since the original Froyo broke audio streaming. I was waiting for that fix to be officially pushed down before I update (by the way, does this update officially fix that?). I'm assuming I have to install the previous update first, before I do this one.
Click to expand...
Click to collapse
Yes you must have the previous update. (to make sure no one messed up I made sure to state that in the requirements)
What audio streaming is broken? I am not having any issues on this update or original Froyo?
Wish I saw this before I flashed the rooted version. Oh well, I know now for next time.
Good guide.
tws101 said:
What audio streaming is broken? I am not having any issues on this update or original Froyo?
Click to expand...
Click to collapse
Pandora and Lastfm audio quality bit-rates were downgraded pretty badly. I use those alot. Google created a patch, and the devs here jumped on it, but it seemed that every implementation was breaking something else, so I wanted to wait for an official HTC push.
Failed to install update from SD card
so I've tried this w/ ROM Manager, boot to recovery, select OTA zip, blah blah blah
when it goes to precheck for update it fails w/ something similar to:
Finding...
Opening...
Installing...
Verifying current system...
assert failed: apply_patch_check("/system/app/HtcFootPrints.odex", "14a8............", "b67e214............")
E:Error in /sdcard/OTA_Supersonic_3.29.651.5.zip
(Status 7)
Installation aborted.
I'm guessing this is because I previously removed some of the stock apps it's trying to update...
Any workaround?
Great guide, thanks for the contrib.
did not work for me, apparently because i don't have flicker and some other system apps installed the update fails, i get an error when it verifies the system.
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
I don't think you can apply the su zip file from the stock recovery, but you can try. If it were that easy, there'd be news of it all over the net!
I think you're going to have to unlock the bootloader and then do the fastboot install of CWM.
I'm on stock Gingerbread, but rooted. I prefer CWM to stock recovery...more options, and especially nandroid backup. I got my 2.3.2 update faster than most, because I was still able to push it manually rather than wait for OTA to someday show up, so no issue there, you just have to wait for someone to post its url.
The 2.3.1 and 2.3.2 updates have a script that rewrites stock recovery on top of CWM if you're on either of those, so you get back to stock with each reboot.
If you're running Android 2.3.1 then use http://forum.xda-developers.com/showthread.php?t=882333 to root.
Android 2.3.0 will be GRH55. Paul hasn't updated SuperBoot for Android 2.3.2.
This method definitely works. I performed it while I was testing the device for any hardware defects. I was able to be rooted without changing the recovery. Make sure you have ADB drivers and 2.3 SDK for the Nexus S installed.
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
First and foremost, you should understand that installing a custom recovery will do nothing to block your ability to receive updates from Google nor will it affect your system in anyway. However, if you follow one of the root methods like this one you will install the custom recovery needed to fix permissions to gain root access but if you ignore the step that has you change the name of a file through root explorer, the next time you reboot your custom recovery will be overwritten by the stock one and you will retain root.
Again, its important to know that having a custom recovery allows you to do a lot more than just flash roms. You can do back ups of your NAND memory that allow you to save all of your data, files, settings, et cetera in the case of catastrophic failures or the need to get a replacement handset. If you do a backup maybe once a month and keep them on your computer, you will always be able to restore your phone exactly back to how it was before issues arose.
There is really no downside to having a custom recovery like Clockwork Recovery Mod, but if you are really against it for moral reasons (that is literally the only reason you would not want to install it) then use the method I described and you will be rooted without CWM.
Agreed with what Kenvan said, the Nexus S is a 'unlocked' bootloader phone and considered a "developer phone." The phone is meant to be altered with a bunch of modifications and hacks.
Not sure why you want to cripple your phone by not flashing custom ROMs. They're created to fascinate the Android experience with improvements made to it. But everybody has their reasons, and are entitled to them right?
Just pointing out my 2 cents. Especially when you're on a forum where a large % of the community are here to modify their phones to the highest extent.
zephiK said:
Not sure why you want to cripple your phone by not flashing custom ROMs. They're created to fascinate the Android experience with improvements made to it. But everybody has their reasons, and are entitled to them right?.
Click to expand...
Click to collapse
LOL. Not flashing custom ROMs is hardly "crippling your phone".
That's like saying not installing a turbo-charger is crippling your porsche...
But I agree, once the custom stuff out there is into actual full public-release, I'll be testing it, but meanwhile a Nexus S on Gingerbread stock is a fine experience...BEST experience on any Android I've had, even supercharged Nexus One and Galaxy S i9000 ROMs.
distortedloop said:
LOL. Not flashing custom ROMs is hardly "crippling your phone".
That's like saying not installing a turbo-charger is crippling your porsche...
But I agree, once the custom stuff out there is into actual full public-release, I'll be testing it, but meanwhile a Nexus S on Gingerbread stock is a fine experience...BEST experience on any Android I've had, even supercharged Nexus One and Galaxy S i9000 ROMs.
Click to expand...
Click to collapse
you both make good points. My point was that there its no reason not install a custom recovery, even if one is staying stock
Sent from my Nexus S
I agree. No reason to not use CWM recovery. Google should buy rights to it from him.
IDtheTarget said:
I don't want to run custom ROMs, I like the Gingerbread from Google and want to easily continue to receive updates.
That being said, I want to be able to run DroidWall and AdFree, and have to have root to do so.
Is there a way to get root, without installing a custom recovery or Clockwork or anything? And still easily receive updates to Gingerbread?
Click to expand...
Click to collapse
I'm wondering the same thing myself.
I just found out that it's possible to boot into the Clockwork recovery without flashing it first. I managed to do this by booting into fastboot mode (power + volume up) and then do
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
This was on a stock but rooted 2.3.2, and the bootloader was locked. I didn't try to apply any update.zip, but nandroid backup seemed to work perfectly.
If you don't remove/delete the "/etc/install-recovery.sh" file once you've flashed a new recovery then you *should* find that the default/stock bootloader is re-applied on the first reboot.
As others have mentioned though, there are plenty of benefits to applying a custom recovery although I do understand the reasons you may not want to.
Thanks, all! Okay, maybe I *will* do the Clockwork Recovery then.
The reason I don't want custom ROMs: I had a Vibrant, and was using Team Whiskey's ROMs, and got "Compulsive ROM disorder". Every TW ROM was better than the last, and I found myself flashing every time they came out with a new one.
I'm going to Afghanistan in a couple of months (leaving for some training on Tuesday), and if I can get Internet at all, I won't have the bandwidth to be constantly downloading the newest, coolest ROM. The stock Gingerbread is good enough for me, and I want to keep it. Plus, that way if my wife has problems with her Nexus S while I'm gone, I have another just like it with me to figure out what's wrong with hers.
I just need root to run DroidWall and AdFree so that if I *do* manage to get a data plan out there, I won't run up huge fees because somebody wants me to buy Viagra or something.
Thanks again!
shrivelfig said:
This was on a stock but rooted 2.3.2, and the bootloader was locked. I didn't try to apply any update.zip, but nandroid backup seemed to work perfectly.
Click to expand...
Click to collapse
Wow, that's a great find.
IDtheTarget said:
Thanks, all! Okay, maybe I *will* do the Clockwork Recovery then.
The reason I don't want custom ROMs: I had a Vibrant, and was using Team Whiskey's ROMs, and got "Compulsive ROM disorder".
Click to expand...
Click to collapse
I fully understand that about the Compulsive ROM flashing disorder. I developed a bit of a case of it with the DocRambone ROMs on my Galaxy S i9000. It became a full time job just keeping up with the forum posts in the thread there. Hundreds of posts per day...ugh! But a sweet ROM.
As I'm sure you've ascertained by our other replies to you, having custom recovery is a benefit whether you flash roms constantly or not.
The ability to do a Nandroid and have a nice working backup of your entire system to fall back on is a major plus, as is the ability to wipe dalvik-cache if you're having issues.
Good luck in Afghanistan!
Thanks!
Yes, I've decided to do the recovery for the Titanium backup as well.
Now if I can only get it to work!
I manually updated to 2.3.2 yesterday, then just now started to try rooting using the directions here: http://forum.xda-developers.com/showthread.php?t=895545
But I keep getting a signature error on the SuperUser flash. I'm guessing it has something to do with the new update.
IDtheTarget said:
Thanks!
Yes, I've decided to do the recovery for the Titanium backup as well.
Now if I can only get it to work!
I manually updated to 2.3.2 yesterday, then just now started to try rooting using the directions here: http://forum.xda-developers.com/showthread.php?t=895545
But I keep getting a signature error on the SuperUser flash. I'm guessing it has something to do with the new update.
Click to expand...
Click to collapse
No, the su file should flash just fine, many of us no problems with it rooting on 2.3.2.
Which version of clockwork recovery did you flash? That post was linking to 3.0.0.0, but that one is buggy, and you want to get 3.0.0.5.
Try this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Push via fastboot.
distortedloop said:
No, the su file should flash just fine, many of us no problems with it rooting on 2.3.2.
Which version of clockwork recovery did you flash? That post was linking to 3.0.0.0, but that one is buggy, and you want to get 3.0.0.5.
Try this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Push via fastboot.
Click to expand...
Click to collapse
No, the problem was that I'm an idiot who hasn't had enough sleep.
I'd flashed that image but wasn't getting into Clockwork recovery. I downloaded ROM Manager and flashed that recovery and was able to update Super User.
Now my problems are (1) I can't rename /etc/install-recovery.sh because it's a read-only file system, and (2) I can't re-install my Astro Pro file manager until Google fixes the market to recognize the new update...
Thanks for the help!
IDtheTarget said:
No, the problem was that I'm an idiot who hasn't had enough sleep.
I'd flashed that image but wasn't getting into Clockwork recovery. I downloaded ROM Manager and flashed that recovery and was able to update Super User.
Now my problems are (1) I can't rename /etc/install-recovery.sh because it's a read-only file system, and (2) I can't re-install my Astro Pro file manager until Google fixes the market to recognize the new update...
Thanks for the help!
Click to expand...
Click to collapse
Try root explorer.
You don't have Titanium Backup to restore Astro...? Every root user should grab that.
You could rename it via adb shell.
Hook up to adb, connect.
run su
remount /system as writable.
use linux mv command to rename it.
I believe you can connect as su to the phone with adb while booted into CWM recovery. Then use CWM menu to mount /system, then do the commands from your computer's terminal or dos shell. Only advantage to this way is you don't have to figure out the proper syntax for remount of /system.
distortedloop said:
You don't have Titanium Backup to restore Astro...? Every root user should grab that.
You could rename it via adb shell.
Hook up to adb, connect.
run su
remount /system as writable.
use linux mv command to rename it.
I believe you can connect as su to the phone with adb while booted into CWM recovery. Then use CWM menu to mount /system, then do the commands from your computer's terminal or dos shell. Only advantage to this way is you don't have to figure out the proper syntax for remount of /system.
Click to expand...
Click to collapse
Couldn't use Titanium backup until I rooted...
Thanks! I used the following command to change permissions:
mount -o remount,rw /dev/block/mtdblock3 /system
Then I:
cd \etc
mv install-recovery.sh install-recovery.sh.000
Looks like I'm set! Although there are still those few apps that aren't showing up yet after the update. Updating the market should be part of Google's checklist when pushing updates...
I've used the SuperBoot method twice and it's exactly what you're looking for. Stock ROM, Stock Recovery, and a rooted device with superuser permission.
when i try to get to the bootloader by holding the power and volume down it automatically takes me into hboot and starts loading PG05IMG.zip. I had previously gained root access with s off and downloaded superuser and rom manager. etc. i saved my old rom on rom manager and attempted to flash a new one, but now it says that i dont have root access when i install superuser. i was trying to factory reset but like i said it automatically goes to hboot when i try to get into the bootloader. in the bootloader it still says i have s-off
1. Change the name of PG051MG.zip to something like PG051MG-1.zip so it doesnt try to update every time.
2. Did you download BusyBox onto your phone?
yeah it still shows that superuser and busybox are on my phone when its mounted in disk drive mode. i had full root access im not quite sure how i ****ed it up
Always remove the pg05 file when done. Did you let it complete the update? That can screw up root.
i let it complete the update yes. but i also let it complete the update after i had already rooted and forgot to take it off, when it had gone into hboot
Ok so maybe I dont fully understand your problem. You are able to boot up your phone normally correct? When is your phone telling you that you dont have root access, when you try to access Rom Manager?
yes it boots up normally and when i try to access rom manager, and when i used root checker it says that it cannot find the superuser file where it is supposed to be. but i can see the superuser file when i mount the phone in disk drive. would changing the location of the su zip file do anything? or should i unroot my phone and start the process all over again. the problem with the bootloader was that i was trying to do a factory reset and it kept going into hboot and loading pg05img.zip. i changed the name of the file so it is no longer doing that and i did a factory reset from the bootloader but i am still having the problem of it saying i have no root access. the problem arose when i backed up my current rom on rom manger and attempted to flash a new rom from the ones on the list of the app
Ok well Superuser and BusyBox are not supposed to be just zip files sitting on your SD card, they are supposed to appear just as normal apps do in your app drawer. I suggest finding both of them on the Market and installing them to your phone. Go to the BusyBox one first after the download and run the installation process for it. Then go to the Superuser app to make sure it opens up properly. Then try to access Rom Manager. It will ask you for superuser permission, hit yes. Make sure to pay attention cuz the request will time out after 5 seconds.
when i attempt to use the busybox app it just says that it cannot find the su binary on my phone and that it is not rooted
But if you start the phone in the bootloader it says S-OFF?
go download titanium backup in the market, then start it and hit the problems button at the bottom and let it download the newest busybox.
yupp.. and i didnt put the su zip file on my sd card. and since apparently i no longer have root access i cant "unroot" my phone and put s on, to start back over again. i feel that i most likely have done something very unintelligent while thinking i was doing everything right.? im just confused as to why all of a sudden i dont hve root access
the busybox download through titanium failed because it says i dont have root access. it said something on titanium backup though that caught my eye about the current rom i have not having root access? and since the problems started when i backed up my old rom on clockworkmod and attempted to flash a new one i feel like this is where the root of my problem is. lol
Did you install superuser from the market also and check to see if thats working?
Its not your current ROM because you can have the stock ROM and still be rooted.
i know that, i had the stock rom rooted and then backed it up and attempted to flash a new one, or what i though would flash a new one by just selecting it out of clockworkmod. but no, superuser from the market also says that i do not have root access. i have the backed up rom, from clockwork before i tried flashing the new one, saved in a folder on my sd card but i cant flash it back to that because i dont have root so clockworkmod recovery isnt working
That is weird, I guess its possible that your phone automatically flashing the radio you had left on your SD card caused some negative effects. If you want to play it super safe you can follow the instructions here to return safely to stock and try the rooting process all over again.
You may also try to redirect your question in the development section, there are much more knowledgeable people there that may not check this general section out that can help you out.
see the problem is that i cant even do that because it doesnt recognize the phone as being rooted so i am not granted the super user permissions i need to flash the misc.img in the first steps of the un root process.
sooooo i just want to return my phone to stock but im not sure how
You shouldn't need to have root to complete the first portion of the instructions to return to stock. Its basically the same as the first steps to gaining root you see here. All your doing is pushing files to your phone using ADB. The link I just posted should have the files you need to return to stock as well if you no longer have them saved on your pc.
kingbenjamin said:
see the problem is that i cant even do that because it doesnt recognize the phone as being rooted so i am not granted the super user permissions i need to flash the misc.img in the first steps of the un root process.
sooooo i just want to return my phone to stock but im not sure how
Click to expand...
Click to collapse
I'm not exactly sure what you did however just follow the manual method and you'll be ok. there is not a problem with doing it over again. of course this will give you root then from there you can do whatever you like. just be sure after you flash each of the ruu's which you name PG05IMG.zip as soon as you flash them delete them off the SD card. or it will keep prompting you to flash it again any time you go into your bootloader.
Beastclaw said:
You shouldn't need to have root to complete the first portion of the instructions to return to stock. Its basically the same as the first steps to gaining root you see here. All your doing is pushing files to your phone using ADB. The link I just posted should have the files you need to return to stock as well if you no longer have them saved on your pc.
Click to expand...
Click to collapse
Yes you are correct as he will be stock. only problem is he will be stock with the downgrade. Don't think that is what he has in mind.
so sadly im still running 1.28.531.10 and want to update to 1.63.531.2, i got a file - OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip but it fails to flash - as a non-developer I came across http://forum.xda-developers.com/showthread.php?t=1624516 and think i need to somehow get Modaco CWM ? i currently have titanium backup and rom manager apps with - CWM 5.0.2.7 flashed.
Might be stupid question but how exactly do i load in this new update, without messing up my current setup (using trimmed stock rom rooted with s-off)?
I see the article reference calls out some "PG59IMG.zip" file
but cant i simply use my "OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip" that got downloaded?
I guess i need a bit more help - as feeling pretty out of it and certainly dont want to mess up my phone. I got too much other stuff going on but would like to do the update - can someone please provide a list of instructions on how to update the phone without loosing all my stuff? - like where do i get this Modaco CWM and what version i need. and if i can use my ota.zip file
i tried flashing my ota.zip via cwm 5.0.2.7 but it just errors out
Any and all help would be greatly appreciated
You can only install manufacturer ota updates with a stock recovery.
Doing the update can equate to a factory reset, at the very least will lose root - you'll have to re-root it.
Installing a PG59IMG.zip file will wipe your system.
Sent from a digital distance.
steve_77 said:
so sadly im still running 1.28.531.10 and want to update to 1.63.531.2, i got a file - OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip but it fails to flash - as a non-developer I came across http://forum.xda-developers.com/showthread.php?t=1624516 and think i need to somehow get Modaco CWM ? i currently have titanium backup and rom manager apps with - CWM 5.0.2.7 flashed.
Might be stupid question but how exactly do i load in this new update, without messing up my current setup (using trimmed stock rom rooted with s-off)?
I see the article reference calls out some "PG59IMG.zip" file
but cant i simply use my "OTA_Doubleshot_TMOUS_1.63.531.2-1.28.531.10_release_245284jzymhpvbi39cqj18.zip" that got downloaded?
I guess i need a bit more help - as feeling pretty out of it and certainly dont want to mess up my phone. I got too much other stuff going on but would like to do the update - can someone please provide a list of instructions on how to update the phone without loosing all my stuff? - like where do i get this Modaco CWM and what version i need. and if i can use my ota.zip file
i tried flashing my ota.zip via cwm 5.0.2.7 but it just errors out
Any and all help would be greatly appreciated
Click to expand...
Click to collapse
Id say backup apps with titanium backup and flash the pg5 zip
Sent from my RubiX NonSense using Tapatalk 2
edited
update
UPDATE:
finally got root:
used:
http://forum.xda-developers.com/showthread.php?t=1532809
to get CMR flashed - then downloaded su-2.3.6.3-efgh-signed.zip
and flashed it through CMR...
for some reason other root methods just didnt work (i tried about 5 ) and at some point did have superuser.apk on phone but it said bad permissions, and i downloaded a "root checker" and it said i still did not have root..
but kudos to hasoon2000 -- for making the program - still dont know if i should "relock-bootloader" (i already has s-off, but used his program to flash CMR, then CMR to flash the su.zip ) but dont know what "unlock bootloader" did and if i should relock it, now that i got root up and going...
One thing I'd do is--
I apologize for being late to this thread; I would have listed a more straightforward method with source links had I referenced the conversation earlier. Be that as it may...
steve_77 said:
to get CMR flashed - then downloaded su-2.3.6.3-efgh-signed.zip and flashed it through CMR...
Click to expand...
Click to collapse
That's an older version of Superuser. And while it may be adequate, I recommend you flash the newer version from AndroidSU.com: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
From my experience, it sometimes doesn't want to install unless you follow these steps:
Boot into CWM recovery
Connect your phone to PC via USB
Choose "mounts and storage," then "mount USB storage"
When your phone directory shows up on your PC, copy the Superuser zip to the root of your SD card
Unmount USB storage and go back to the main CWM menu, then choose "install zip from sdcard"
Scroll down to the Superuser zip and select it. Installation should go without problems.
steve_77 said:
but kudos to hasoon2000 -- for making the program - still dont know if i should "relock-bootloader" (i already has s-off, but used his program to flash CMR, then CMR to flash the su.zip ) but dont know what "unlock bootloader" did and if i should relock it, now that i got root up and going...
Click to expand...
Click to collapse
Erm, no. You most definitely do not want to relock the bootloader. If you have root/s-off, updating Superuser is the only thing I'd recommend. You're golden for everything else.
Hope the above info proves helpful --
--
KingCheetah
KingCheetah said:
That's an older version of Superuser. And while it may be adequate, I recommend you flash the newer version from AndroidSU.com: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
KingCheetah
Click to expand...
Click to collapse
I tried that the other day, however If i flash that version v3.0.7 (41) -
I no longer have "root" and my "rom manager" and "titanium backup" will not work
- the new su app did look nicer but - defeats the point if it doesn't function, im still trying to find a way to revert my phone and get the old version back in there(have to start all over). Im hoping there is a workaround for this behavior (perhaps there should be a separate thread on getting a working version of superuser 3.0.7 - as it installed fine)?
HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.
setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.
No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.
With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.
DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM