• 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)

25 GB is WAY to huge for links to SD. I have a 4 gb partition and that's way too big. Honestly, I wouldn't do over a GB. Link2SD only links .apks, .dex, and .libs, which does't add up to much. The big files are obb files, and app data
I use 10gb just so I can say nah nah to my friends with an SGS4! ;)
 
I am on first version of this rom i would like to update to the latest but ihave all my apps and stuff setup the way i want them. i have bought titanium backup pro so id like to see instructions on upgrading from first version to current and using the new apps on sd i have a SanDisk 16GB MicroSD HC Mobile Ultra Class 10 Memory Card ill be using. thanks so much for all the support here for this phone i am really loving it.
Always do a backup of all your apps with TitaniumBackup before flashing anything. Once it loads, press menu and select Batch actions, then Backup all user apps. Batch actions are what you paid for, it makes it so much easier to back everything up or restore everything at once!

Copy everything from your sdcard to your computer, partitioning will erase it! You will need to copy it all back after your are done.

Follow the instructions I've posted, I would suggest a max 4gb 2nd partition for your sdcard. If you have any trouble, post here and we will help! ;)
 
Might have been asked be fore but, how long does it take to boot the first time? Been sitting here waiting for over 10 minutes now watching the flashing Samsung logo.

Edit - Ok, been almost 30 minutes now is this normal? If not what should I do?
This is my first time doing this stuff and just want to make sure I'm doing it right.
 
BUG WARNING
bootanimation2

Do not use the /system/media/bootanimation.zip I included in the 0.2.1 update if you switch to bootanimation2!
There is a bug that will cause your phone to be stuck at boot, and the only way out of it without reflashing is to wipe dalvik-cache. The weird thing is it removes my wallpaper?!?

I believe the issue is with non-looping bootanimations, the included SolarFlare bootanimation should not loop according to it's desc.txt, but it does, and this is either a symptom of the problem, or the problem itself (needs testing with other non-looping bootanimations). This bootanimation2 binary I've included was built to replace the stock Samsung bootanimation binary, which calls for multiple files, so the bootanimation2 binary may expect multiple folders in the zip file (just a hunch at this time).

I have tested with three other looping bootanimation.zip files, and have had no issues with them.


What am I talking about? Victorious-0.2.1 has a second bootanimation binary located in /system/bin called bootanimation2. If you rename the original bootanimation to bootanimation.bak and rename bootanimation2 to bootanimation, you can then use standard zip files instead of qmg files. This allows you to google android bootanimations and find thousands of options! Just download them and use a root file manager to move them to /system/media, and be sure they are named bootanimation.zip

Remember, all you are doing is renaming the files so the system can find the one you want to use, named bootanimation. ;)
 
Might have been asked be fore but, how long does it take to boot the first time? Been sitting here waiting for over 10 minutes now watching the flashing Samsung logo.
If you are watching the flashing Samsung logo, you did not successfully flash Victorious. Be sure you download from here this link (and check the md5 after downloading):
http://jerryscript.vmobi.us/Victorious/Victorious-0.2.1.zip
md5 244e5b53db41014c565f2685f8d7e297

Once you have flashed Victorious, you will see a non-animated Samsung logo for a few seconds, then the Victorious ROM logo, then the bootanimations, then the Android is updating... popup, then a Starting apps message, then you will boot to your lockscreen. You should never see a flashing Samsung logo after flashing Victorious (unless you replace the bootanimations with the stock ones). Total time should be less than 5 minutes.
 
Just do bootanimation2 and put the zip in /data/local/ it'll override the /system/media/ boot animation and if u loop u can adb delete it while looping then another reboot and your fixed :)
 
If you are watching the flashing Samsung logo, you did not successfully flash Victorious. Be sure you download from here this link (and check the md5 after downloading):
http://jerryscript.vmobi.us/Victorious/Victorious-0.2.1.zip
md5 244e5b53db41014c565f2685f8d7e297

Once you have flashed Victorious, you will see a non-animated Samsung logo for a few seconds, then the Victorious ROM logo, then the bootanimations, then the Android is updating... popup, then a Starting apps message, then you will boot to your lockscreen. You should never see a flashing Samsung logo after flashing Victorious (unless you replace the bootanimations with the stock ones). Total time should be less than 5 minutes.
I wiped cache and dalvik cache, no factory reset, when it finished I had a box pop up that said SuperSU needed to be fixed and TWRP wanted to know if it should fix it, I said yes.
I used the link posted at the top of this page for the download.
 
Just do bootanimation2 and put the zip in /data/local/ it'll override the /system/media/ boot animation and if u loop u can adb delete it while looping then another reboot and your fixed :)
Good trick!

Looks like it's due to the bootanimation.zip I included having only one part folder. I've tested with three other bootanimations, all with at least two part folders, and they all worked fine. I had tested with this SolarFlare bootanimation.zip, and did not have this issue, so it may have been borked in the packaging of Victorious (I use AndroidKitchen to zipalign and sign). Will have to test a bootanimation.zip with a single part folder to see if I can reproduce the issue.

Still puzzled over my homescreen wallpaper returning to the default image as a result of this bug?!?
 
I wiped cache and dalvik cache, no factory reset, when it finished I had a box pop up that said SuperSU needed to be fixed and TWRP wanted to know if it should fix it, I said yes.
I used the link posted at the top of this page for the download.

Check the md5sum, and if it's ok, try reflashing.

To check md5sum on windows, google will help you find a program that will do it.

To check md5sum on Linux, in terminal:
cd <path-to-file-to-check>
md5sum <name-of-file-to-check>

To check md5sum on Android, using terminal emulator (Play Store):
cd <path-to-file-to-check>
md5 <name-of-file-to-check>
 
You can set default by placing image in ramdisk (nice little mod) or I think /system/media/ too
What I'm planning on doing is writing a small tools package for Victorious as an app. It will allow you to adjust various settings that are particular to Victorious. Turning on/off sdcard swapping and sdext2 storage, switching between bootanimation binaries, previewing and selecting bootanimations, etc. Just a matter of wrapping the shell commands in a class with root access, won't even need separate scripts as they can all be built into the classes. I'll probably use the settings menu theme to keep it in sync with JB style. Did similar things with the OptimusV, but was building CM7.2 from source and was able to include it in the CyanogenMod settings menus without borking the main source or messing with smali edits (god I hate smali). ;)
 
BTW- I still haven't given up on the Video Player app! I tried adding several of the stock apks back in, but I still haven't found the magic combo. And unfortunately, logcat is not being helpful in this instance. :(
 
I re-downloaded the file, ran a md5 check it's green, reflashed after I wiped the caches again, still comes up with a box on the reboot that superuser has lost root access and wants to fix it so I tell it yes fix it and it reboots. What I see is a non-animation Samsung logo, then victorious rom, then the virgin mobile tone (not the animation) and at the same time the Samsung flare animated logo.
 
BTW- I still haven't given up on the Video Player app! I tried adding several of the stock apks back in, but I still haven't found the magic combo. And unfortunately, logcat is not being helpful in this instance. :(

I've tried for a bit and couldn't figure it out. I just removed the stock app and installed mxplayer. I'll mess with it this weekend unless you figure it out
 
Awesome work bro thanks so much updated to newest and used link2sd great instructions and awesome rom thanks Jerry and all those involved!!!!!! Not missing my galaxy s2 at all now.
 
Do we have to keep the system galley and camera apps? (Sorry if someone already asked this.. )

You can remove them, but the new camera is not 100% compatible (it was built for Android4.3). If you do remove them, I would suggest you use TitaniumBackup to back them up, then freeze them. That way if you have issues down the road, you can always defrost them and be right back to stock. ;)
 
FYI - to anyone attempting to get the Video Player working, it has something to do with multiwindow. It fails trying to launch it's multiwindow view:
PHP:
unable to resolve static method 656: Landroid/sec/multiwindow/MultiWindow;.createInstance (Landroid/app/Activity;)Landroid/sec/multiwindow/MultiWindow;

And has an error connecting to the cloud (though that may be a result of the above error):
PHP:
E/VideoCloudUtil( 4870): checkCloudAgentExistence() - NameNotFoundException 
W/dalvikvm( 4870): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/sec/android/app/videoplayer/videowall/MscEngine;

And this may be at the root of the issue:
PHP:
E/VideoCloudUtil( 4442): checkCloudAgentExistence() - NameNotFoundException

I don't remove any library files in Victorious, so it's gotta be one of the missing apps, or a permissions issue.
 
FYI - to anyone attempting to get the Video Player working, it has something to do with multiwindow. It fails trying to launch it's multiwindow view:
PHP:
unable to resolve static method 656: Landroid/sec/multiwindow/MultiWindow;.createInstance (Landroid/app/Activity;)Landroid/sec/multiwindow/MultiWindow;

And has an error connecting to the cloud (though that may be a result of the above error):
PHP:
E/VideoCloudUtil( 4870): checkCloudAgentExistence() - NameNotFoundException 
W/dalvikvm( 4870): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/sec/android/app/videoplayer/videowall/MscEngine;

And this may be at the root of the issue:
PHP:
E/VideoCloudUtil( 4442): checkCloudAgentExistence() - NameNotFoundException

I don't remove any library files in Victorious, so it's gotta be one of the missing apps, or a permissions issue.


i added 2 missing library files and set permissions and video player is working.

1. download attachment and extract files to sd card on phone
2. copy both files into system/lib folder
3. set permissions to match picture below on both files
4. Enjoy your videos.

Screenshot_2013-07-26-12-13-39.png
 

Attachments

i added 2 missing library files and set permissions and video player is working.

1. download attachment and extract files to sd card on phone
2. copy both files into system/lib folder
3. set permissions to match picture below on both files
4. Enjoy your videos.

Screenshot_2013-07-26-12-13-39.png


Thanks! I love this forum, everyone helping each other out! :)

I'll add those into the next release of Victorious. Strange, I never removed them, where did you get them from?

Edit: I just checked the stock backup, and those lib files are not there. But I can confirm the fix works, THANKS!
 
I was digging through some videoplayer ports found one with lib files included check my lib files noticed 2 in folder I didnt have so.figured its worth a shot and it worked.
 
Back
Top Bottom