• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root System update

Custom recovery can't install the OTA...and custom recovery can't flash it. You need the stock recovery. Or to be S-Off and flash the firmware.zip ramjet posted.
 
Prinny said:
Custom recovery can't install the OTA...and custom recovery can't flash it. You need the stock recovery. Or to be S-Off and flash the firmware.zip ramjet posted.
Click to expand...

I did did it through the regular settings/system updates..let it download then install and when the phone restarted it went into custom recovery. I'm not running a custom ROM, just rooted (with regular virgin mobile stock)..is it because the bootloader is unlocked?

Can I just lock the bootloader..install the update then unlock the bootloader again?
 
Well, before you update...if you're planning on S-Off ever. I would recommend NOT doing the OTA. We can't confirm or deny if the S-Off works with the new Hboot
 
circleoflife said:
I did did it through the regular settings/system updates..let it download then install and when the phone restarted it went into custom recovery. I'm not running a custom ROM, just rooted (with regular virgin mobile stock)..is it because the bootloader is unlocked?

Can I just lock the bootloader..install the update then unlock the bootloader again?
Click to expand...
You don't need to lock the bootloader but you do need to flash the stock recovery before installing the OTA as prinny said already. See this post by mrg666 who was in a similar situation and note that if you have installed any mods that affect system files the installation may not be successful.

If you have modified any system files and flashing the stock bootloader fails it might be easier to just flash the RUU and take both OTA updates. Also note that if you take the latest OTA with S-ON you will not be able to use the JuopunutBear wire trick to get S-OFF, at least in a supported configuration.

ramjet73
 
Prinny said:
Well, before you update...if you're planning on S-Off ever. I would recommend NOT doing the OTA. We can't confirm or deny if the S-Off works with the new Hboot
Click to expand...
But thanks to brian706 ;) we do know that the 1.58 hboot installed by the OTA is not supported by unlimited.io for VM users to do the JBear wire trick. :(

ramjet73
 
ramjet73 said:
You don't need to lock the bootloader but you do need to flash the stock recovery before installing the OTA as prinny said already. See this post by mrg666 who was in a similar situation and note that if you have installed any mods that affect system files the installation may not be successful.

If you have modified any system files and flashing the stock bootloader fails it might be easier to just flash the RUU and take both OTA updates. Also note that if you take the latest OTA with S-ON you will not be able to use the JuopunutBear wire trick to get S-OFF, at least in a supported configuration.

ramjet73
Click to expand...

I read the post and I still seem confused. I only root the phone so I can use some rooted apps and disable some sound notifications.

I can flash the phone with this and it'll have the new OTA update? Which one should I use? deodexed or odexed?
http://androidforums.com/evo-v-4g-a...ota-2-95-652-5-un-rooted-odexed-deodexed.html

Thanks once again. I'm not too familiar with all this stuff. Just know how to do basic rooting without installing a custom ROM.
 
circleoflife said:
I read the post and I still seem confused. I only root the phone so I can use some rooted apps and disable some sound notifications.

I can flash the phone with this and it'll have the new OTA update? Which one should I use? deodexed or odexed?
http://androidforums.com/evo-v-4g-a...ota-2-95-652-5-un-rooted-odexed-deodexed.html

Thanks once again. I'm not too familiar with all this stuff. Just know how to do basic rooting without installing a custom ROM.
Click to expand...
Yes, I think we got confused when you mentioned flashing the OTA.

Just wipe and flash one of the rooted ROM's in the OP then restore your apps, data and settings with whatever backup program you use. I recommend the deodexed version since it's easier to add mods and themes to that if you want any in the future. Also, the warnings about S-OFF don't apply if you just flash one of the rooted ROM's in the OP since your firmware won't be updated.

ramjet73
 
ramjet73 said:
Yes, I think we got confused when you mentioned flashing the OTA.

Just wipe and flash one of the rooted ROM's in the OP then restore your apps, data and settings with whatever backup program you use. I recommend the deodexed version since it's easier to add mods and themes to that if you want any in the future. Also, the warnings about S-OFF don't apply if you just flash one of the rooted ROM's in the OP since your firmware won't be updated.

ramjet73
Click to expand...


Thank you!!!! :) Just curious what does virgin mobile ship with odexed or deodexed?
 
mrg666 said:
I don't think so. Even the "real" stock ROM couldn't take the OTA due a bunch of modified files. Additionally, stock recovery needed as well. See my post in the previous page.
Click to expand...

remanifest said:
Thank you for your useful post. Per this guidance, you'll have to flash a stock recovery and restore backups of any modified system files before taking the OTA.

When I took the OTA, I first ran the RUU, then OTA, then OTA (was going to provide a stock+updates nandroid, but someone else uploaded first). That's where I was confused, so thank you for clarifying that.
Click to expand...
Does rooting and S-off qualify as modified files? I haven't touched anything else...other than doing that, it's completely stock. Can I flash the stock recovery, take the OTA, then flash TWRP back?
 
So what's the status quo; is the update useful?

Also I am rooted and s-off running WFTN and BT on hboot 1.04.2 using 4ext. Essentially I can just flash the zip Ramjet made in bootloader and then flash back to hboot 1.04.2 right.

Edit: well technically I have to flash a rom that supports hboot 1.58 I think.
 
Hedied4me said:
Also I am rooted and s-off running WFTN and BT on hboot 1.04.2 using 4ext. Essentially I can just flash the zip Ramjet made in bootloader and then flash back to hboot 1.04.2 right.
Click to expand...
No need for that as the hboot, recovery and boot.img were removed from the original firmware zip file.

ramjet73
 
Droidula said:
Does rooting and S-off qualify as modified files? I haven't touched anything else...other than doing that, it's completely stock. Can I flash the stock recovery, take the OTA, then flash TWRP back?
Click to expand...
That should be fine.

You might also want to flash a custom hboot afterwards to replace the stock 1.58 version that gets installed with the OTA. If you do that before flashing your recovery it won't be necessary to unlock your bootloader to run the fastboot "flash" command.

ramjet73
 
ramjet73 said:
No need for that as the hboot, recovery and boot.img were removed from the original firmware zip file.

ramjet73
Click to expand...

So I flashed the new firmware correctly but it caused me to go into booploop. Should I just reflash my rom? Should have backed up but I didnt...lol.

Maybe the new firmware is not compatible with WFTN or buttered toast or something. Any info would be greatly appreciated.
 
ramjet73 said:
That should be fine.

You might also want to flash a custom hboot afterwards to replace the stock 1.58 version that gets installed with the OTA. If you do that before flashing your recovery it won't be necessary to unlock your bootloader to run the fastboot "flash" command.

ramjet73
Click to expand...
I guess I could flash back to the 1.57 hboot after. Any idea where I could find the stock recovery file to flash? I can't seem to locate it.
 
Hedied4me said:
So I flashed the new firmware correctly but it caused me to go into booploop. Should I just reflash my rom? Should have backed up but I didnt...lol.

Maybe the new firmware is not compatible with WFTN or buttered toast or something. Any info would be greatly appreciated.
Click to expand...

That's normal if you flash a new hboot that's incompatible with your rom. Reflashing the rom won't help. You either need to flash a compatible rom or flash the old hboot back. Also to avoid bootloops in the future when changing hboots, please read my instructions. I will copy/paste them here:
Brian706
Senior Member

Thread Author (OP)
*

*
Join Date: Jul 2012
Location: Washington
Gender: Male
Posts: 3,058
*
Device(s): Evo 3D (CDMA) Rom: P.A.C.man v20.0.0 Kernel: Buttered Toast 16.1 Recovery: 4EXT
Carrier: Sprint

Thanks: 1,392
Thanked 1,665 Times in 1,140 Posts
Radios, Hboot & Firmware - All Downloads
Radios & Wimax for (CDMA) Sprint Evo 3d & Virgin Mobile Evo V

Warning: For CDMA phones only!!!
Do not use on GSM phones!
Will work on Sprint and Virgin Mobile.
S-off Required.


How to use a PG86IMG.zip file!


First let me start by stressing something important! Verify the integrity of the download by checking the file against its md5 checksum that I provided for each file. You can use a free software such as MD5 Checker to do the job. Or if you'd like to check on your phone without a pc, download MD5 Checker for android from the play store. If for whatever reason your download gets corrupted, using a corrupted file can brick your phone! So use an md5 checker to verify the integrity of the file, it's quick and easy and can keep your phone safe!

1. Download File. Check md5 for a match

2. Place the file on the root of your sd card (not in any folders).

3. Rename the file to PG86IMG.zip

4. Reboot into bootloader.

5. When asked to update, say yes by hitting volume up.

6. When it's all finished, hit power button to reboot.

7. *Important! After booting up, immediately rename or delete the file.

*The presence of the file on your sd card will prevent you from entering recovery in an emergency situation. It's nothing to panic about, but if you get caught in a bootloop, you will have to manually remove the file using a pc and card reader or another phone. That said, to avoid bootloops and being stuck with no way to boot up and no way to enter recovery, plan ahead. If you are on a rom that requires hboot 1.58 and you flash hboot 1.5, you will hit a bootloop and not be able to access recovery. You would then need to remove the file or flash a compatible rom through fastboot connected to a pc.

Okay. Now with instructions and warnings out of the way, I will give you my personal preference on how to flash a different hboot that will be incompatible with your current rom without getting a bootloop and having to use a pc to fix the situation.

Follow steps 1-3 above. Stop! Now, instead of rebooting into the bootloader, we are going to bypass the bootloader by rebooting directly into recovery. Some roms have this feature built in. I recommend downloading something like ROM TOOLBOX from the play store. It's a great app to have if you are rooted. Rom Toolbox has a built in rebooter menu (with widgets) that allows this function. Alternatively go get QUICK REBOOTER from the play store. So once in recovery, wipe and flash the rom normally. Once finished, continue to steps 4-7.

This will allow you to do everything completely from your phone and avoid getting stuck. Remember, this is just for when you are changing hboots that will be incompatible with the rom you are already using (ie: ICS to GB). Just following steps 1-7 normally is fine for just flashing radios or switching between different GB hboots etc.
Click to expand...
 
Droidula said:
I guess I could flash back to the 1.57 hboot after. Any idea where I could find the stock recovery file to flash? I can't seem to locate it.
Click to expand...

Not sure exactly why you want the stock recovery but if you have the ruu, you can pull it from that. If you can't get it, I'll pull it from my copy and upload it for you. Just let me know.
 
Jaxmoto said:
I was bored so I felt like going ahead and getting the full update....

Started S-Off and unlocked and rooted.

Follow standard RUU procedure, lock bootloader, install RUU.

Installed the OTA small update, then the current one here and the voicemail update.

Re-unlocked bootloader with my previously saved .bin key file from HTC (you don't need a new one).

Re-installed TWRP via fastboot.

Re-installed superuser via TWRP. (Superuser and TWRP were the same files I used in previous install before this update).

(phone resets to initial settings and setup on boot due to unlocking the bootloader)

Go to play store and search for "Superuser" and update it (it will not find it automatically, you have to search and go to the app on the play store).

Now the easiest way to get apps back on the phone is to use a PC to go to the Play Store and got to "My Android Apps" which has everything you installed previously, just browse through and click on install for anything you want back on the phone... The Play store will send it to your phone automatically.

So far I have tested root, superuser, wifi tether for root users.... no problems and everything works.

I tried the partial file for S-Off and it seemed to install but my files did not update to the correct versions and things like the address bar in the default browser were not fixed, they ARE correct numbers and fixed browser bar after this process. That leads me to think there is far more going on than just a few firmware updates.
Click to expand...


where can I get the RUU file?
 
Brian706 said:
That's normal if you flash a new hboot that's incompatible with your rom. Reflashing the rom won't help. You either need to flash a compatible rom or flash the old hboot back. Also to avoid bootloops in the future when changing hboots, please read my instructions. I will copy/paste them here:
Click to expand...

Thanks for the advice. But I only flashed the firmware so my hboot did not change. I can confirm this by checking bootloader. Maybe Im misunderstanding something.
 
Brian706 said:
Not sure exactly why you want the stock recovery but if you have the ruu, you can pull it from that. If you can't get it, I'll pull it from my copy and upload it for you. Just let me know.
Click to expand...
Because it was mentioned that even though I'm stock, I can't take the OTA because I have custom recovery, and stock recovery is needed for accepting the OTA. So I wanted to flash stock recovery back, take the OTA, and then flash my TWRP back.

I have an older RUU.exe file that I used to go back to stock at one point. I'm not sure how to pull a recovery though.
 
Droidula said:
Because it was mentioned that even though I'm stock, I can't take the OTA because I have custom recovery, and stock recovery is needed for accepting the OTA. So I wanted to flash stock recovery back, take the OTA, and then flash my TWRP back.

I have an older RUU.exe file that I used to go back to stock at one point. I'm not sure how to pull a recovery though.
Click to expand...

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'm coming from a stock-like rooted rom. Can I just RUU and re-lock back then take the updates and root again and use the phone with the updates or do I have to flash a rom?
 
You must log in or register to reply here.
Back
Top Bottom