Root [Virgin Mobile] [New Update] Patience Please

[JerryScript]

Edit: See below for original post, the following has been added:

Good News!!!

I finally got the time to fix the update!

Working:

1. Phone
2. SMS
3. MMS
4. PRL update
5. Profile update
6. Samsung software update
7. Firmware update (just checks of course)
8. 3G
9. 4G
10. Samsung apps
11. Virgin Mobile apps
12. Camera & Video Recorder
13. Gallery & Video Player
14. Haven't tested NFC yet

I finally got the update on my phone (wanted an original copy). I changed the updater-script to not check the props, but did leave the assert patch checks, and changed install-recovery.sh to run init.d instead.


I booted into TWRP and made a backup, then I restored the stock backup from g60madman, then rebooted into the system and did all updates.


I booted into TWRP again, and installed my modified MC1-MG5-no-props.zip, install went flawlessly, no errors, takes about 5 minutes.


I rebooted into the system, and did all updates again, tested everything, then booted back into recovery to make a new backup.


I am now rebuilding Victorious from this update.


Steps to update safely (Note-- If you are already running stock, no need to restore g60madmans backup, but you MUST BE RUNNING STOCK FOR THE PATCH CHECKS TO WORK, INCLUDING THE KERNEL!!!):

1. Download g60madmans's TWRP backup unzip it, and put the date/timestamp folder on your sdcard in the TWRP/BACKUPS/<random-number> folder
2. Download update_SPH-L300_MC1_to_MG5-no-props.zip and put on your sdcard
3. Backup all your apps with TitaniumBackup (just in case)
4. Boot into recovery
5. Make a backup (this one is more important!)
6. Restore g60madman's TWRP backup
7. Reboot into the system and do updates in settings
8. Boot into recovery again
9. Install the update_SPH-L300_MC1_to_MG5-no-props.zip
10. Wipe cache and dalvik cache
11. Optional - Install VaeVictus-MG5-OC-Rv3 kernel
12. Reboot system
13. Say yes if prompted to fix root
14. Update everything in settings again
15. Install Superuser (Koush's) and Busybox from the Play Store

After a few minutes, you should get a popup saying your install was succesful:

Note : I've pulled a backup after installing this, and have rebuilt Victorious-0.3.1 from it.


Original Post:

I know everyone gets excited about new updates to our phone. However, flashing things willy-nilly without being certain of what will happen is never a good idea (unless you understand how to fix a soft-bricked phone, in which case, ignore this post)!

I am currently working a lot of hours while the owner of the restaurant I manage is on vacation in Greece. I will only have limited time for the next three weeks for dev work. I do my best to test everything before I post it, and attempt to create problems as I do test it in hopes of anticipating issues you may have. This normally means running any new build for at least a full day before releasing it to the public, and I also usually have a couple of testers try things out as well.

Rather than flash this and that, and then ask for help fixing what you don't understand (taking up more of my limited time), please be patient. I can assure you that by the end of the weekend, we will have an easy to install and 100% safe method of updating your phones to the latest firmware release.

I apologize if any part of this post appears rude, condescending, or is in any way unpleasant. I'm writing this at the end of a 16 hour shift with 3 hours sleep.

Have a great weekend, and look forward to new packages to flash at the end of it!

 

[JerryScript]

A bit more information:

This update only does one thing when all is said and done, installs KVM (google KVM android). KVM is not necessary to have a fully functional phone, so this update is not a "must have." KVM is a virtualization machine that will help our phones run a bit smoother and have a bit more battery life, but it will not make drastically noticeable differences. It also gives the carriers the ability to use the same kernel/firmware across multiple networks, and even with multiple phone numbers on the same phone (say goodbye to sim cards).

Those who were running Victorious and attempted to flash the update posted here for the new firmware had issues at first because that update overwrote one of my scripts used to enable the sdcard swapping and use of the 2nd ext4 partition on your sdcard. You can easily fix this by copying the /system/etc/install-recovery.sh from the Victorious zips to the same place on your phone. Be sure to set it's permissions!

Those who have had bootloops with Victorious 0.2.2-r1, it's due to either my updater-script (which was too agressive), or due to the overclock being to high at boot. I will be fixing both of those issues in the next releases.

Those who have had issues with VaeVictus kernel, it may be due to the overclock being too high at boot. This also will be fixed in the next release.

Those who cannot wait till Sunday for my new releases, jump on the dev bandwagon and help out! If you don't feel you can help with coding, you can help by encouraging patience amongst your fellow users.

Anyone who thinks they have bricked their phone, are having trouble with wifi or mms, or are stuck in a bootloop, please restore the stock firmware, then wait till Sunday for some new updates!

 

[mudflap2020]

A bit more information:

This update only does one thing when all is said and done, installs KVM (google KVM android). KVM is not necessary to have a fully functional phone, so this update is not a "must have." KVM is a virtualization machine that will help our phones run a bit smoother and have a bit more battery life, but it will not make drastically noticeable differences. It also gives the carriers the ability to use the same kernel/firmware across multiple networks, and even with multiple phone numbers on the same phone (say goodbye to sim cards).

Those who were running Victorious and attempted to flash the update posted here for the new firmware had issues at first because that update overwrote one of my scripts used to enable the sdcard swapping and use of the 2nd ext4 partition on your sdcard. You can easily fix this by copying the /system/etc/install-recovery.sh from the Victorious zips to the same place on your phone. Be sure to set it's permissions!

Those who have had bootloops with Victorious 0.2.2-r1, it's due to either my updater-script (which was too agressive), or due to the overclock being to high at boot. I will be fixing both of those issues in the next releases.

Those who have had issues with VaeVictus kernel, it may be due to the overclock being too high at boot. This also will be fixed in the next release.

Those who cannot wait till Sunday for my new releases, jump on the dev bandwagon and help out! If you don't feel you can help with coding, you can help by encouraging patience amongst your fellow users.

Anyone who thinks they have bricked their phone, are having trouble with wifi or mms, or are stuck in a bootloop, please restore the stock firmware, then wait till Sunday for some new updates!

Does.the.kvm.make.the.graphics or cpu faster?

 

[buzzcon]

I know everyone gets excited about new updates to our phone. However, flashing things willy-nilly without being certain of what will happen is never a good idea (unless you understand how to fix a soft-bricked phone, in which case, ignore this post)!

Words to live by!!!!!!

If you don't feel you can help with coding, you can help by encouraging patience amongst your fellow users.

As a forum member that falls into this category, all I can say is there is nothing more annoying than an impatient friend/acquaintance that you are helping for FREE. Let us all be patient and let Jerry do his magic.

Carry on Jerry, I got your back, LOL.

Seriously, thanks for your work, it is truly appreciated by us grunts!

 

[llamadon]

I looked at support for the phone before I got it and saw JerryScript so knew it would be fine. Thank you for all you do for us.

 

[insanelycool]

Thanks again for everything Jerry! I was going to flash the firmware with Kwknott's method, but have decided to wait so I can be a guinea pig for your fix when you are finished. Since I won't be able to tell if it flashed the baseband properly if I already do it now. So I will probably jump on IRC after midnight tonight. (I haven't been on there in ages!)

I will be out all evening at a concert, but when I return I will be glad to help out testing stuff!

 

[zacharynasty]

A bit more information:

This update only does one thing when all is said and done, installs KVM (google KVM android). KVM is not necessary to have a fully functional phone, so this update is not a "must have." KVM is a virtualization machine that will help our phones run a bit smoother and have a bit more battery life, but it will not make drastically noticeable differences. It also gives the carriers the ability to use the same kernel/firmware across multiple networks, and even with multiple phone numbers on the same phone (say goodbye to sim cards).

Those who were running Victorious and attempted to flash the update posted here for the new firmware had issues at first because that update overwrote one of my scripts used to enable the sdcard swapping and use of the 2nd ext4 partition on your sdcard. You can easily fix this by copying the /system/etc/install-recovery.sh from the Victorious zips to the same place on your phone. Be sure to set it's permissions!

Those who have had bootloops with Victorious 0.2.2-r1, it's due to either my updater-script (which was too agressive), or due to the overclock being to high at boot. I will be fixing both of those issues in the next releases.

Those who have had issues with VaeVictus kernel, it may be due to the overclock being too high at boot. This also will be fixed in the next release.

Those who cannot wait till Sunday for my new releases, jump on the dev bandwagon and help out! If you don't feel you can help with coding, you can help by encouraging patience amongst your fellow users.

Anyone who thinks they have bricked their phone, are having trouble with wifi or mms, or are stuck in a bootloop, please restore the stock firmware, then wait till Sunday for some new updates!

yes please be patient, its not easy doin this stuff, on top of how busy jerry is, i mean its common sense, its only 1 day then we can all be happy with a new release, if i see one person being rude or ignorant about this, ima chew you out...so act like an adult and let him work his magic, i would help but im not a coder..so patience is a virtue..

 

[zacharynasty]

Thanks again for everything Jerry! I was going to flash the firmware with Kwknott's method, but have decided to wait so I can be a guinea pig for your fix when you are finished. Since I won't be able to tell if it flashed the baseband properly if I already do it now. So I will probably jump on IRC after midnight tonight. (I haven't been on there in ages!)

I will be out all evening at a concert, but when I return I will be glad to help out testing stuff!

whats irc

 

[kwknott]

Internet Relay Chat

What's the connection info for irc.? I briefly looked back but didn't see em

 

[mudflap2020]

Blast proccessorization

 

[comps]

freenode Web IRC (qwebirc)
channel: #victory-recon

 

[mudflap2020]

Nobody home?

 

[JerryScript]

New flashable update zip that works with TWRP posted in the OP^

You MUST be stock, no Victorious, restore g60madman's stock backup if you are not running stock!

I have not tested with CWM.

 

[zachallen]

New flashable update zip that works with TWRP posted in the OP^

You MUST be stock, no Victorious, restore g60madman's stock backup if you are not running stock!

I have not tested with CWM.

After I do all this will I be able to reflash old victorious or will I have to wait for new one? And I will still be rooted right?

 

[JerryScript]

After I do all this will I be able to reflash old victorious or will I have to wait for new one? And I will still be rooted right?

You should wait for new Victorious, othewise you're downgrading.

 

[zachallen]

You should wait for new Victorious, othewise you're downgrading.

OK just making sure. I'm making backups right now then I'm updating!

 

[zachallen]

You should wait for new Victorious, othewise you're downgrading.

Do i have to flash stock kernal as well or is that included in the zip?

 

[JerryScript]

Do i have to flash stock kernal as well or is that included in the zip?

When you restore g60madman's backup, you will be restoring the kernel, it's in the boot.img

You can then flash the latest VaeVictus kernel if you want to overclock. I'll build an uncapped to 1.5ghz kernel from the official Samsung source for those who don't want to overclock soon.

 

[zachallen]

When you restore g60madman's backup, you will be restoring the kernel, it's in the boot.img

You can then flash the latest VaeVictus kernel if you want to overclock. I'll build an uncapped to 1.5ghz kernel from the official Samsung source for those who don't want to overclock soon.

Awesome! But doesn't latest VaeVictus kernel have issues with MMS?

 

[comps]

Awesome! But doesn't latest VaeVictus kernel have issues with MMS?

no it was the bad update2.zip

confirming mms, call, text, 3g, 4g(portland has 4g)
all working
prl updates, profile, and so did virgin mobile apps triggered

 

[zachallen]

no it was the bad update2.zip

confirming mms, call, text, 3g, 4g(portland has 4g)
all working
prl updates, profile, and so did virgin mobile apps triggered

Your able to receive MMS not just send it correct?

 

[zachallen]

Your able to receive MMS not just send it correct?

Can u post link to make sure I'm getting the right kernel plz

 

[JerryScript]

Awesome! But doesn't latest VaeVictus kernel have issues with MMS?

No, sms and mms works fine, both sending and receiving!

Here's the kernel link:
http://www.mediafire.com/download/alw7zyrmh73r7n8/VaeVictus-MG5-OC-Rv3.zip

 

[zachallen]

No, sms and mms works fine, both sending and receiving!

Here's the kernel link:
VaeVictus-MG5-OC-Rv3.zip

Thanks jerry! And everyone else for making me feel right at home!

 

[zachallen]

I'm up to date and flashed! Thanks guys. And jerry when you get around to working on victorious is there any way you can put the visual vmail back? Because unless it was just me I wasn't getting no notifications of my voice mails. Unless you have already came up with a fix...