Root System update

[Droidula]

Download the OTA but don't start the update process. Open the OTA zip file which is in your sdcard/download directory. I recommend copying the file to your PC and opening it on your PC with 7zip. There is another zip file in it called framework.zip. Open firmware.zip and you will find recovery.img in it. Copy that recovery.img to either your sdcard or your PC. If you use PC, you can use the fastboot command "fastboot flash recovery recovery.img" with USB connection to fastboot. Or, if you install Flash Image GUI on your phone, you can copy the recovery.img file to your sdcard and flash directly from your phone using Flash Image GUI.

I will try this within the next few days, thank you! Hoping this will improve my reception a bit, I seem to get a lot of voicemails without the phone ever ringing.

So this was odd.

I followed your instructions per your post. When I flashed that recovery.img that I pulled from the OTA, and booted to recovery, I had gone from TWRP 2.x to the old version of TWRP. I tried flashing the recovery.img a few times, and it stayed as TWRP. I then tried flashing it through Flash Image GUI, and when I rebooted into recovery, it was a red exclamation point I think? So I flashed it through fastboot again.

I then tried flashing the OTA zip through TWRP 1.x. It gave me an error for the plusOne apk, which I took from a stock RUU and put back, and then again with Polaris Office, which I replaced as well. The last error was for the file "libgcomm_jni.so," from "system/lib," which I put into the folder too. After that, the patch seemed to install successfully.

When I rebooted, I realized that WiFi was broken and would not turn on any longer. I lost root too, so I flashed SuperSU again, as well as TWRP 2. I then noticed that although when I updated, my software number had changed to the latest, on the bootloader screen, I still had the 1.57 hboot, as well as a radio I had flashed myself (0706), and the old PRI.

I'm not sure what happened, and can't mess around with it more tonight. I need to be able to connect to WiFi, so I restored the recovery I'd created beforehand. I'm now back to 1.14.652.0 710RD.

Any ideas why the radio, PRI, and hboot didn't flash?

 

[mrg666]

So this was odd.

I followed your instructions per your post. When I flashed that recovery.img that I pulled from the OTA, and booted to recovery, I had gone from TWRP 2.x to the old version of TWRP. I tried flashing the recovery.img a few times, and it stayed as TWRP. I then tried flashing it through Flash Image GUI, and when I rebooted into recovery, it was a red exclamation point I think? So I flashed it through fastboot again.

I then tried flashing the OTA zip through TWRP 1.x. It gave me an error for the plusOne apk, which I took from a stock RUU and put back, and then again with Polaris Office, which I replaced as well. The last error was for the file "libgcomm_jni.so," from "system/lib," which I put into the folder too. After that, the patch seemed to install successfully.

When I rebooted, I realized that WiFi was broken and would not turn on any longer. I lost root too, so I flashed SuperSU again, as well as TWRP 2. I then noticed that although when I updated, my software number had changed to the latest, on the bootloader screen, I still had the 1.57 hboot, as well as a radio I had flashed myself (0706), and the old PRI.

I'm not sure what happened, and can't mess around with it more tonight. I need to be able to connect to WiFi, so I restored the recovery I'd created beforehand. I'm now back to 1.14.652.0 710RD.

Any ideas why the radio, PRI, and hboot didn't flash?

Apparently, OTA still had more conflicts with your ROM to complete the update. At this point, it would be more straightforward to restore RUU and take the first OTA and second OTA after that.

 

[narutoninjakid]

I don't see a kernel update anywhere in the zip file, nor was there anything in the November OTA. All the ROM related changes seem to be new files or patches to modules in the /system partition.

Edit: NVM. I just noticed that there is a boot.img file in the firmware zip file.

ramjet73

what does this do ? improve performance. Im on CM 10.1 Dastin 4.2.2 So can i flash this ?

 

[xstefen]

Just got this SMS

8682: VMFreeMsg Terms & Conditions and key service items will change in early 2013 due to a system update. This may impact your service. Info at http://msg4u.us/mpve

Havent clicked on it. Assuming its the same stuff that other people have got recently about the system updates and data caps/monitoring. Just thought it was interesting to randomly get this

 

[favelarx]

Just got this SMS



Havent clicked on it. Assuming its the same stuff that other people have got recently about the system updates and data caps/monitoring. Just thought it was interesting to randomly get this

I got that text a while ago too, it's the VM system update stuff

 

[ron scubadiver]

I have seen a lot of speculation that the March 2013 VM OTA will make achieving S-Off impossible. One should take note that the file package for S-Off on the Evo 3d (Sprint) contains hboot 1.58.5858 which is supposed to be a modified stock hboot 1.58 and others around here have observed the hboot 1.58 in the March 2013 VM OTA is the same as the Sprint 1.58.

This leads me to believe that Evo V 4G's that have the March 3013 VM OTA could achieve S-Off, but probably with the Sprint Control Bear package.

This is speculation on my part. Just wondering...

 

[Droidula]

Apparently, OTA still had more conflicts with your ROM to complete the update. At this point, it would be more straightforward to restore RUU and take the first OTA and second OTA after that.

Yeah I figured I might as well just do that. I think I'll try flashing the PG86IMG ramjet73 posted first, and later on try to do the full RUU/OTA.

Just to reiterate, I don't have to relock/unlock bootloader anymore before RUU, since I'm S-off?

Thanks for the help along the way!

 

[Brian706]

I have seen a lot of speculation that the March 2013 VM OTA will make achieving S-Off impossible. One should take note that the file package for S-Off on the Evo 3d (Sprint) contains hboot 1.58.5858 which is supposed to be a modified stock hboot 1.58 and others around here have observed the hboot 1.58 in the March 2013 VM OTA is the same as the Sprint 1.58.

This leads me to believe that Evo V 4G's that have the March 3013 VM OTA could achieve S-Off, but probably with the Sprint Control Bear package.

This is speculation on my part. Just wondering...

I (and others) have thought the same thing. It's just that nobody knows for sure unless someone does it... Unfortunately, unlimited has now removed all windows versions from their site... They have officially stopped supporting windows which sucks in my opinion because I'd say that the majority of users are on windows.

 

[mrg666]

Yeah I figured I might as well just do that. I think I'll try flashing the PG86IMG ramjet73 posted first, and later on try to do the full RUU/OTA.

Just to reiterate, I don't have to relock/unlock bootloader anymore before RUU, since I'm S-off?

Thanks for the help along the way!

Last time I had done RUU, I had relocked the bootlocker. I can't say based on my own experience but many posts in several forums claim it is necessary to relock the bootloader before RUU. It is very easy to unlock again anyway. Time consuming part is restoring your apps and settings.

 

[ramjet73]

Last time I had done RUU, I had relocked the bootlocker. I can't say based on my own experience but many posts in several forums claim it is necessary to relock the bootloader before RUU. It is very easy to unlock again anyway. Time consuming part is restoring your apps and settings.

I can guaranty with 100% certainty that there is no need to lock the bootloader before flashing the RUU if you are S-OFF. I don't recommend it as it requires an extra step when returning to 100% stock to lock it again. S-OFF users are better off flashing a custom hboot like JBear, Revolutionary or ENG than unlocking the stock hboot to be able to run additional fastboot commands.

If you want to run the RUU and keep the stock ROM it's worth trying a restore of the data partition from a nandroid backup of the stock ROM done before the RUU but you should still backup your apps, data and settings with an app like Titanium Backup or MyBackup Root just to be safe. If you're not planning to keep the stock ROM you can just restore a nandroid or fresh flash a custom ROM after running the RUU and flashing a custom recovery.

ramjet73

 

[ramjet73]

I (and others) have thought the same thing. It's just that nobody knows for sure unless someone does it... Unfortunately, unlimited has now removed all windows versions from their site... They have officially stopped supporting windows which sucks in my opinion because I'd say that the majority of users are on windows.

The real question is which version of the JuopunutBear Windows utility should a VM user run? The Sprint ICS version is already setup for the 1.58 hboot whereas the VM ICS version includes the 1.57 hboot. My bias would be to try the VM ICS version first and if that doesn't work try the Sprint ICS version since the controlbear.exe utility may be checking the CID which for Sprint is SPCS_001 and for VM is SPCS_002.

We just won't know for sure until somebody tries it with S-ON and the full March OTA installed.

ramjet73

 

[Brian706]

The real question is which version of the JuopunutBear Windows utility should a VM user run? The Sprint ICS version is already setup for the 1.58 hboot whereas the VM ICS version includes the 1.57 hboot. My bias would be to try the VM ICS version first and if that doesn't work try the Sprint ICS version since the controlbear.exe utility may be checking the CID which for Sprint is SPCS_001 and for VM is SPCS_002.

We just won't know for sure until somebody tries it with S-ON and the full March OTA installed.

ramjet73

Yep, you might be right about the CID check, but I think I would put my money on the Sprint 1.58 hboot version for the first shot. They made different software for different hboots so I would worry about damaging my bootloader using software for a different version. And you're pretty much screwed without a bootloader....

 

[Droidula]

Unfortunately, unlimited has now removed all windows versions from their site... They have officially stopped supporting windows which sucks in my opinion because I'd say that the majority of users are on windows.

Oh wow...I think I have a copy of the Windows tool on my PC still. I hope. They should just keep the Windows version up and say it's unsupported.

Last time I had done RUU, I had relocked the bootlocker. I can't say based on my own experience but many posts in several forums claim it is necessary to relock the bootloader before RUU. It is very easy to unlock again anyway. Time consuming part is restoring your apps and settings.

When I ran RUU last time I relocked it as well, but since I'd seen it mentioned here that it's not required, I thought I might as well cut a step out of the process. It isn't a huge deal though, either way.

I can guaranty with 100% certainty that there is no need to unlock the bootloader before flashing the RUU if you are S-OFF. I don't recommend it as it requires an extra step when returning to 100% stock to lock it again. S-OFF users are better off flashing a custom hboot like JBear, Revolutionary or ENG than unlocking the stock hboot to be able to run additional fastboot commands.

If you want to run the RUU and keep the stock ROM it's worth trying a restore of the data partition from a nandroid backup of the stock ROM done before the RUU but you should still backup your apps, data and settings with an app like Titanium Backup or MyBackup Root just to be safe. If you're not planning to keep the stock ROM you can just restore a nandroid or fresh flash a custom ROM after running the RUU and flashing a custom recovery.

ramjet73

Ok so, you're saying it's not required to unlock the bootloader initially, but it is required to relock it before running the RUU, if it is already unlocked?

I would be keeping the stock ROM (for a while anyway). Restoring the data partition should put all my apps back after? I have everything backed up with Titanium anyway, but it could save time.

 

[ramjet73]

Yep, you might be right about the CID check, but I think I would put my money on the Sprint 1.58 hboot version for the first shot. They made different software for different hboots so I would worry about damaging my bootloader using software for a different version. And you're pretty much screwed without a bootloader....

That a reasonable argument too. If it's doing a CID check it should error out pretty fast anyway.

It's really up to the first "guinea pig" to decide which makes more sense to them.

ramjet73

 

[ramjet73]

Ok so, you're saying it's not required to unlock the bootloader initially, but it is required to relock it before running the RUU, if it is already unlocked?

Let me make this as simple as possible.

Once you get S-OFF with the wire trick you should forget about ever unlocking the bootloader again. It's just not necessary as long as you use a custom hboot.

ramjet73

 

[ramjet73]

I would be keeping the stock ROM (for a while anyway). Restoring the data partition should put all my apps back after? I have everything backed up with Titanium anyway, but it could save time.

Yes, as long as your nandroid backup is from the pre-OTA version of the stock ROM doing an advanced restore of only the data partition should restore your apps, data and settings. I don't recommend that if you are coming from another ROM in which case you should use one of the backup/restore utilities only.

ramjet73

 

[Droidula]

Let me make this as simple as possible.

Once you get S-OFF with the wire trick you should forget about ever unlocking the bootloader again. It's just not necessary as long as you use a custom hboot.

ramjet73

I'm sorry, I'm not trying to needlessly complicate things. ☕ I understand that the bootloader doesn't need to be unlocked, once you're S-off and using a custom hboot.

I already am unlocked, though. And from you post, I had understood that once you were unlocked, it would then require you to relock before running the RUU.

"I can guaranty with 100% certainty that there is no need to unlock the bootloader before flashing the RUU if you are S-OFF. I don't recommend it as it requires an extra step when returning to 100% stock to lock it again."

Sorry for the confusion.

Yes, as long as your nandroid backup is from the pre-OTA version of the stock ROM doing an advanced restore of only the data partition should restore your apps, data and settings. I don't recommend that if you are coming from another ROM in which case you should use one the backup/restore utilities only.

ramjet73

Great, I will try that then.

 

[ramjet73]

I already am unlocked, though. And from you post, I had understood that once you were unlocked, it would then require you to relock before running the RUU.

Sorry for the confusion.

No, that's my mistake. I meant that there is no need to lock/relock if you are S-OFF and want to flash the RUU and have fixed the original post to reflect that.

Since you are S-OFF and unlocked already if you ever want to go back to 100% stock you can use the "lock_bootloader.zip" file from this post. Thank scotty85 and brian706 for creating and testing those files and they also available in one the forums here on androidforums.com but I don't have that link handy.

ramjet73

 

[ron scubadiver]

I (and others) have thought the same thing. It's just that nobody knows for sure unless someone does it... Unfortunately, unlimited has now removed all windows versions from their site... They have officially stopped supporting windows which sucks in my opinion because I'd say that the majority of users are on windows.

I think Unlimited is trying to only support a very narrow range of possibilities, in effect a single set of variables for each device to make their life simple and avoid testing different possibilities. I also noticed a USB boot Linux "will not work". That is annoying.

My Evo V was a good deal @ $150 and the support here is great, but these HTC devices are a bit of a beach to open up completely. Life was much simpler when I had an OV, even if it was a toy.

 

[Cartman90045]

Here's a firmware only zip file from this OTA for any S-OFF users that want to flash just that portion of the update. The 1.58 hboot, which is already available separately, and the boot.img file have been removed...ramjet73

Thanks again for all of your help ramjet73!

Does this firmware only zip file work for both Sprint and VM? Is the firmware basically the same between the two models?

 

[ramjet73]

Thanks again for all of your help ramjet73!

Does this firmware only zip file work for both Sprint and VM? Is the firmware basically the same between the two models?

Different firmware. The VM version has more modules updated.

I have a thread in the Evo 3D development forum on XDA with a firmware only file for the March Sprint OTA.

ramjet73

 

[bobylopo]

i need help!!!!!!! ever since I got the phone I had problems with it so I called the company and they said that they can fix it I just need to uptade my phone but the problem is that my phone is rooted and I don't know if I should uptade it should I? BTW the phone is s-on right now

 

[OverByter]

Being rooted won't affect your ability to update the phone, having a custom recovery will though. Also if you do take the update you'll have to re root your phone.
OB

 

[MortalBizkit]

This is my first forum post ever. I have just bought the HTC EVO V and switched to virgin mobile. I registered the phone and took the 2 updates. Can I root with this method?

How to Root the HTC EVO V 4G (Virgin) - TheUnlockr

I want to stay S-ON and use the stock rom.

Thanks!

 

[Brian706]

This is my first forum post ever. I have just bought the HTC EVO V and switched to virgin mobile. I registered the phone and took the 2 updates. Can I root with this method?

How to Root the HTC EVO V 4G (Virgin) - TheUnlockr

I want to stay S-ON and use the stock rom.

Thanks!

Should be able to. S-off is totally worth it. When you change your mind and decide to go s-offp), check out this guide: http://androidforums.com/evo-v-4g-all-things-root/695161-s-off-root-fix-everything-all-in-one.html