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

Root [Virgin Mobile] [VMOBI][ROM][KERNEL] Victorious ROM + VaeVictus OC kernel (Updated 7-30-13)

JerryScript said:
You have to use a root capable file manager (like Root Explorer from The Play Store), and set the directory to read/write (R/W), there is a toggle near the top of the directory structure. You then have to long press the apk after you have copied it over, and set it's permissions to the same as the other apks in that folder.
Click to expand...

MediaUploader.apk was already there. Moved shareshotservice.apk and set permissions. Video player still wont open. Says "unfortunately video player stopped working".
 
JerryScript said:
If you had wifi tether installed before, then your probably having data/cache issues. Try clearing data in app management, then clear dalvik-cache (either with TitaniumBackup or in recovery). Reboot and see if it will work. IF not, uninstall it and then download this apk and install it:
WifiTether_TrevE_Mod_11_22_2012.apk

I don't know about the boot-time password encryption, I haven't tried it, it could require the stock recovery. Do a backup in recovery, then test it out. If it messes things up, boot into recovery and restore your backup. Be sure to use TWRP, it appears as if CWM for the Victory has issues with the data partition, can't ever seem to restore the data backups.
Click to expand...
Sorry about the late reply, but just wanted to mention that this solved the issue perfectly. Installed the APK, followed the configuration instructions outlined in your other post, and I get faster internet than I do on my home connection (14mbps/2mbps on LTE) Thanks much!
 
Thanks for the logcats on the MMS issue everyone. I am not 100% certain, but it appears as if those logcats show your phones are not fully provisioned with VM. This can happen as the result of flashing things, though nothing from Victorious could have caused it unless you wiped system or data before flashing it. The logcats show mms being enabled, but then there is an authorization error. This can be either due to needing to be reprovisioned, or needing to have the CSC work it's magic on the badges again (restoring stock).

I would recommend restoring stock via TWRP, activating the phone, updating the PRL, profile, software, and firmware. Then test your incoming mms. If it still doesn't work, you'll need to call customer service while still on stock and tell them you have no incoming mms and need to reprovision your phone. Tell them it's happened before and that's what the previous rep did to fix it.

WARNING: Be sure to install the stock recovery before you call them!

Once you have MMS working, you should be able to flash Victorious again and it should still work. I just sent an MMS to my sister, and had her send me one back. Both worked fine on 3G running Victorious-0.1.4.

I have had issues with MMS after using a bad backup that was posted in these forums, and all I had to do was restore stock, and update things like I mentioned above, I did not have to call customer service.

Note- This very well could be an issue with 4G, but I seriously doubt it. ;)
 
Madbat said:
MediaUploader.apk was already there. Moved shareshotservice.apk and set permissions. Video player still wont open. Says "unfortunately video player stopped working".
Click to expand...

Hmm, I'll have to check a logcat to try to figure out what's still missing. Don't worry about posting one, I can do it on my end. ;)
 
TeachMe said:
I just noticed I didn't have a navigation app does this phone not come with one ?
Click to expand...

Navigation is built into Google Maps now. I removed most of the Google apps you can download from the Play Store, so you'll have to install them yourself.

Anything to make the downloads smaller, stock goghvmu firmware is almost a full gig, though I can compress it to about 650mb in an update.zip. Victorious's update zip is compressed to only 255mb, much easier for hosting and downloading, and makes it possible for people without an external sdcard to install via the internal sdcard if necessary! ;)
 
BTW- Who wants more space for apps? :ciao:

I've finally got a mount script to work via links2sd to make a 2nd partition on your sdcard usable and accessible, without being overly complex, and ensuring the proper timing so everything mounts properly.

Before using this script, I had three games installed along with about 30 other apps total, and had just under a gig of application storage space left using the extsd2internalsd script included in Victorious and links2sd. After replacing 11extsd2internalsd with this merger of it and links2sd's script, I was able to install a dozen more games, link everything over to the 2nd partition on my sdcard, and now have 1.4gigs available in application storage. ;)

Note- I undid all links2sd linkages before rebooting after making the changes, then redid them after rebooting with the new changes.

This replaces /etc/init.d/11extsd2internalsd:
PHP: 
#!/system/bin/sh

#the following is a combination of extsd2internalsd and links2sd mount scripts

# Wait for the system to mount the internal media and remout it as r/o
# this should prevent the system from writing to it until we make the 
# switch, yet keeps the /data/media r/w, so at the end it won't be r/o
for i in $(seq 1 1 3000)
do
    if ( grep -c "/storage/sdcard0" /proc/mounts ); then
        mount -o remount,ro /storage/sdcard0
        break;
    fi
    usleep 100000
done

# now wait for the external media and remount
for i in $(seq 1 1 3000)
do
    if ( grep -c "/storage/extSdCard" /proc/mounts ); then
   
        # create new temporary mount point 
        mount -o remount,rw /
        mkdir /storage/tmpmnt
        mount -o remount,ro /  

        # do the rebinding using the temporary mount point
        mount -o bind /data/media /storage/tmpmnt
        mount -o bind /storage/extSdCard /storage/sdcard0
        mount -o bind /storage/extSdCard /data/media
        umount /mnt/extSdCard
        mount -o bind /storage/tmpmnt /storage/extSdCard
        umount /storage/tmpmnt
        
        # make bind for ums mode
        mkdir -p /storage/extSdCard/external_sd/sdcard1
        touch /storage/extSdCard/external_sd/.nomedia
        mount -o bind /storage/sdcard0 /storage/extSdCard/external_sd/sdcard1
    
        # done
        break;
    fi
    usleep 100000
done

#added by link2sd
#modified by JerryScript for Victorious ROM
#mounts the 2nd partition on the sdcard to /data/sdext2
#only ext4 is supported at this time, ext3 may work
LOG=/data/link2sd-install-recovery.log
echo "$(date) mounting..." > $LOG
mount -t ext4 -o rw /dev/block/vold/179:34 /data/sdext2 1>>$LOG 2>>$LOG

mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG

mount >> $LOG
echo "$(date) mount finished" >> $LOG

exit
This replaces /etc/install-recovery.sh (just in case it's been modified otherwise)
PHP: 
#!/system/bin/sh
export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d
To take advantage of this, you must create a 2nd partition on your sdcard. It must be a primary partition formatted to ext4. I used a new 32gig sdcard, and partitioned it in TWRP to have a 2nd partition of 10gigs. It said it failed, but it in fact worked, TWRP just doesn't know how to mount it after partitioning it (will have to contact the TWRP team). You will also need to create a folder in /data called sdext2 and set it's permissions to rwxrwx--x. I will add this to the next release of Victorious. ;)

Screenshot_2013-07-21-06-13-04_zpsfb29215f.png


Screenshot_2013-07-21-06-13-15_zpse526da1f.png


Screenshot_2013-07-21-06-13-59_zps9436f61a.png
Screenshot_2013-07-21-06-25-32_zpsc19aaeab.png


Screenshot_2013-07-21-06-15-18_zpsc1ef4ba0.png
Screenshot_2013-07-21-07-56-33_zpsf35b629b.png


Screenshot_2013-07-21-07-58-50_zpsbd295735.png
 
It takes a bit to boot the first time. Shouldn't take anymore than 5 but I'd give it 10 to make sure.

When you installed did you just wipe cache and dalvik cache in recovery?
 
JerryScript said:
Thanks for the logcats on the MMS issue everyone. I am not 100% certain, but it appears as if those logcats show your phones are not fully provisioned with VM. This can happen as the result of flashing things, though nothing from Victorious could have caused it unless you wiped system or data before flashing it. The logcats show mms being enabled, but then there is an authorization error. This can be either due to needing to be reprovisioned, or needing to have the CSC work it's magic on the badges again (restoring stock).

I would recommend restoring stock via TWRP, activating the phone, updating the PRL, profile, software, and firmware. Then test your incoming mms. If it still doesn't work, you'll need to call customer service while still on stock and tell them you have no incoming mms and need to reprovision your phone. Tell them it's happened before and that's what the previous rep did to fix it.

WARNING: Be sure to install the stock recovery before you call them!

Once you have MMS working, you should be able to flash Victorious again and it should still work. I just sent an MMS to my sister, and had her send me one back. Both worked fine on 3G running Victorious-0.1.4.

I have had issues with MMS after using a bad backup that was posted in these forums, and all I had to do was restore stock, and update things like I mentioned above, I did not have to call customer service.

Note- This very well could be an issue with 4G, but I seriously doubt it. ;)
Click to expand...

Thanks so much for checking on this, Jerry. I restored a stock backup I had made with TWRP, and I then proceeded to do all the available system updates. However, incoming mms still fails (I've been testing this by sending mms to my own number. I've been able to send them, but the message download fails every time). So, it looks like I'll have to go the customer service route.. :frown: Unfortunately, I don't have a stock recovery img/tar to flash, and I haven't had any luck searching the forums! Does anyone here have the stock recovery file? :s:

EDIT: Whoaaa! I found this digging around in the forums:

http://androidforums.com/virgin-mob...stock-virgin-mobile-victory-07-04-2013-a.html

g60madman talked about his mms not working since he rooted his phone before activating it (i did too!). I'm going to try flashing this stock backup and seeing if I can't get my mms working as well.

EDIT: That did the trick! Restoring to g60madman's stock rom brought my mms back online. Apparently it was from rooting the phone before i activated it...who knew :dontknow:
 
Hey Jerry I was just wondering do you think it would be possible to port that Ubuntu Touch OS to the victory? (sorry a little off topic here)
 
TriumphLance said:
so I just flashed it and the first boot has been going for about 8 minutes..how long is LONG?
Click to expand...

There are two reasons it would not boot:

  1. You have a bad download, check the md5 to be sure
  2. You wiped system or did a factory reset, restore stock then flash Victorious again, and only wipe cache and dalvik-cache per the installation instructions
There could be other issues, but most likely it's one of the above.
 
zajajo said:
Thanks so much for checking on this, Jerry. I restored a stock backup I had made with TWRP, and I then proceeded to do all the available system updates. However, incoming mms still fails (I've been testing this by sending mms to my own number. I've been able to send them, but the message download fails every time). So, it looks like I'll have to go the customer service route.. :frown: Unfortunately, I don't have a stock recovery img/tar to flash, and I haven't had any luck searching the forums! Does anyone here have the stock recovery file? :s:

EDIT: Whoaaa! I found this digging around in the forums:

http://androidforums.com/virgin-mob...stock-virgin-mobile-victory-07-04-2013-a.html

g60madman talked about his mms not working since he rooted his phone before activating it (i did too!). I'm going to try flashing this stock backup and seeing if I can't get my mms working as well.
Click to expand...

I have flashed around 20 different packages to my Victory, and a few times I had borked radios, wifi, or mms. Each time, I simply restored the stock backup posted by g60madman, rebooted and updated PRL and Profile, then flashed Victorious, and all has been well.
 
Looks like everything is coming together for the next release! I'm curious if there has been any movement on finding the calendar widget.
It sounds like I'm just going to reformat everything, start from scratch with stock, get my mms working again properly (activate and update), flash TWRP again/ reroot, flash the new victorious (when it is released with the link2sd built in), and then reinstall all my apps from scratch. Sounds like a fun project when I get the time (prolly next weekend). No rush on that update! But do let me know if there is anything I can do to help test anything, since I'm planning to reflash, I may as well ;)
 
I finally grew a set and flashed this ROM. Install went great, and phone works flawlessly. I tested incoming calls and MMS with no issues and the only game I play on it (Candy Crush) works way faster. I am going to wait until a build comes out to help with storage issues. Some of this is a tad bit over my head.

Thanks for this ROM bro!!!!
 
I just wanted to add, FWIW, that once I flashed this ROM, using TWRP, it said that I lost root privileges and ask if I wanted to have it fixed, I said no and had to re-root once the phone restarted (this part was not mentioned in the install instructions). It re-rooted just fine. Not sure if I missed a step or did something I shouldn't have, but just wanted to mention it.

I found out that I lost root (for lack of a better term) because I wanted to adjust the governor and run it OC'd at 1.350Ghz to see how things would work, but I could not change it from 1.5Ghz.

I am just complaining :D just reporting.
 
If I am understanding it right the processors are un governed allowing it to run up to 1.5 as it sees fit not actualty set the speed.
 
You are correct, the processor will run anywhere between 384mhz to 1.51ghz depending on load. I rarely see mine clock above 918mhz
 
Coming from the Motorola Triumph which has a 1Ghz single core processor there was talk of some users OC'ing it to 2.0Ghz safely. While I would never attempt something like that, I wanted to decrease to 1.350Ghz in an attempt to find a sweet spot where I would get better performance and still get decent battery life.

I am going to try a battery I found on Ebay that SAYS it is 3160mAh. This is a one half increase over the stock battery if true.
 
You must log in or register to reply here.
Back
Top Bottom