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

Root [Virgin Mobile] Firmware Update

i forgot that one was up, i have a thread for it now, but the one in the other thread works for any MC1 rom including Victorious. Just the speed tweaks to the mg5 update (including official wont work until VaeVictus update comes or late when i release the stock kernel. i forgot to package it in :P sorry
 
rbheromax said:
i forgot that one was up, i have a thread for it now, but the one in the other thread works for any MC1 rom including Victorious. Just the speed tweaks to the mg5 update (including official wont work until VaeVictus update comes or late when i release the stock kernel. i forgot to package it in :P sorry
Click to expand...

So I should just wait until its updated into the Vaevictus
 
Honestly it's already merged into the next release, so it's really not a problem...I just didn't want anyones bootloader to get locked it that was something VM was trying to do. I checked out the bootloader files and they're clean. So were safe...for now
 
rbheromax said:
Honestly it's already merged into the next release, so it's really not a problem...I just didn't want anyones bootloader to get locked it that was something VM was trying to do. I checked out the bootloader files and they're clean. So were safe...for now
Click to expand...

When will the new release be out
 
I felt adventurous so I decided to install the entire firmware update.

I accomplished this by restoring g60's stock backup, installing CWM recovery and removing the getprop ro.secure=1 line from updater-script (I tried some edits but couldn't get past this so I just removed the line.)

Here is it's progress:

Checked system
Patched system files
Patched NON-HLOS
Patched Boot Image
Extracted New Recovery
Extracted New Files
Extracted sbl2
Updated sbl2
Extracted sbl3
Updated sbl3
Extracted aboot
Updated aboot
Extracted rpmfw
Updated rpmfw
Extracted tz
Updated tz

Upon reboot it did some "Finalizing Update"

The only obvious changes I saw for the little bit I was on stock was an updated baseband to version L300VPAMG5 and kernel version and recovery was back to stock.

So next i reflashed twrp using odin. I let it boot up to stock rom after flashing recovery and upon rebooting to recovery I found stock recovery had been rewritten. So I reflashed twrp again but this time booted right into recovery after flashing. I then rebooted to rom and then rebooted to recovery to see if it had been overwritten again. To my surprise twrp was still there

I then restored my Victorious backup I made before starting this adventure. Backup restored fine and everything works as before with the new baseband.

It does seem like my signal and data speeds are a bit better but it could be in my head. I guess the new baseband could have helped a bit.

Other than that I see no other differences in phone.

I don't recommend any else trying this as things could go wrong and I don't see any reason to do it. I was just curious as to what the update did and wanted to see if it locked bootloader or blocked root.. Neither of which it did...

Just a fun experiment
 
I still haven't gotten the update OTA. But with your experience going well, I may do the the update from the one you posted... especially now that I cant get mms, I might as well go for it.

So to reiterate, the root method still works? Just flash TWRP with odin?

Do I need to install CWM before doing the update as well?
 
I took it out for fear of bootloader lock and private tested bootloader, its clean, and you confirmed, so I put this zip up, thanks
 
insanelycool said:
I still haven't gotten the update OTA. But with your experience going well, I may do the the update from the one you posted... especially now that I cant get mms, I might as well go for it.

So to reiterate, the root method still works? Just flash TWRP with odin?

Do I need to install CWM before doing the update as well?
Click to expand...

Try the zip rbheromax posted for the baseband update to see if it helps first!!

I had to use CWM to flash the update but had to edit updater-script cause 1 line kept erroring out. Root worked, twrp flashed fine.

It updates a lot of important partitions so if it doesn't go well you could brick your phone. Custom recoveries usually don't do ota updates very well so maybe I was lucky.
 
kwknott said:
Try the zip rbheromax posted for the baseband update to see if it helps first!!

I had to use CWM to flash the update but had to edit updater-script cause 1 line kept erroring out. Root worked, twrp flashed fine.

It updates a lot of important partitions so if it doesn't go well you could brick your phone. Custom recoveries usually don't do ota updates very well so maybe I was lucky.
Click to expand...

I'm about to do that, I'm just stuck making a backup atm... which is a good thing anyways ;) I will report back in a bit once it finishes and I flash the zip.
 
I woke this morning to the prompt about update now. Is it the zip file thats in /cache/ labeled update? Oh well, I'm not installing it or anything, just wondering if that's what that file is. Cuz its dated 3a.m. last night.
 
Should be
fe9c01d8369008d498d76ddbcc966cf746.update_SPH-L300_MC1_to_MG5.zip
although the random crap at beginning might be different
 
kwknott said:
I felt adventurous so I decided to install the entire firmware update.

I accomplished this by restoring g60's stock backup, installing CWM recovery and removing the getprop ro.secure=1 line from updater-script (I tried some edits but couldn't get past this so I just removed the line.)

Here is it's progress:

Checked system
Patched system files
Patched NON-HLOS
Patched Boot Image
Extracted New Recovery
Extracted New Files
Extracted sbl2
Updated sbl2
Extracted sbl3
Updated sbl3
Extracted aboot
Updated aboot
Extracted rpmfw
Updated rpmfw
Extracted tz
Updated tz

Upon reboot it did some "Finalizing Update"

The only obvious changes I saw for the little bit I was on stock was an updated baseband to version L300VPAMG5 and kernel version and recovery was back to stock.

So next i reflashed twrp using odin. I let it boot up to stock rom after flashing recovery and upon rebooting to recovery I found stock recovery had been rewritten. So I reflashed twrp again but this time booted right into recovery after flashing. I then rebooted to rom and then rebooted to recovery to see if it had been overwritten again. To my surprise twrp was still there

I then restored my Victorious backup I made before starting this adventure. Backup restored fine and everything works as before with the new baseband.

It does seem like my signal and data speeds are a bit better but it could be in my head. I guess the new baseband could have helped a bit.

Other than that I see no other differences in phone.

I don't recommend any else trying this as things could go wrong and I don't see any reason to do it. I was just curious as to what the update did and wanted to see if it locked bootloader or blocked root.. Neither of which it did...

Just a fun experiment
Click to expand...

how did you remove that line? Did you unzip it on your pc and remove it? And curious how you installed it. Just install it when the update asks you to, or did you boot into cwm recovery to install? Hope these aren't annoying questions, I just wanted to try it. I'm having fun trying stuff on this phone.:D
And after you did that were you stock with no root and stock recovery? Because I think a few ppl want that from what I've read.
 
I actually did it all on phone..

Unzipped update
Edited updater-script
Rezipped
Signed Zip
Rebooted to recovery and flashed

I'm sure it'd be easier on pc but my wife had our laptop so I just used phone.
 
What did you use to unzip, rezip, and sign? Just a root file explorer? Im kinda new to alot of this. But a fast learner.
 
The reason your recovery gets overwritten is in the update zip, look under recovery for the install-recovery.sh file. If you replace that file with the one from Victorious, and remove the line in the updater-script about ro.secure, you should have a working update zip that will not replace recovery. We may need to remove the check lines as well, since deodexed system files probably don't match the signatures.

I'm pulling a double shift today, if someone else doesn't get around to fixing the zip, I'll do it tomorrow. ;)
 
You must log in or register to reply here.
Back
Top Bottom