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

ok so i want to partition my sd card now that i have the victorious rom, after i do that using mini tool, and i put it back in my phone, is there anything i need to do so i can use access that partition for games or whatever, like create a path to it
 
Okay, first of all I want to say a Big Thank You to you JerryScript for all the dev work you have put into making Victorious and VaeVictus.

With that said, I am having a lot of issues trying to upadate from 0.1.4 to 0.2.1 or even 0.2.2-r1. I am able to get to the boot animation screen but then it just hangs there at the boot animation screen until I power off or pull the battery.

I have a few questions here:

1. What is the best way to update from 0.1.4 to 0.2.2r1 or current update when you release it?

Please keep in mind that I do have link2sd on all my apps that i possibly can and would not like to unlink all of my apps. I have already made a backup of 0.1.4 and can restore from that backup.

2. I would like to update to the current Victorious Rom when will you release the next update without the animation?

3. Can you send me a link to get rid of the annoying sound that my phone is going to self-destruct also?

I just don't want to go somewhere, turn on my phone and then quickly be escorted out of the building (you know what I mean?).


Thanks again man, you are the best!

Patiently waiting a reply,

-FM
 
Ok so I just wana say thanks to all the great people here and for putting up with my incessant banter on how to get all this stuff to work, its greatly appreciated, I'm a chef so I'm not to familiar with a lot of this stuff, although I learn fast, but I do like to ask questions just to make sure, phone are an investment, so I wouldn't want to mess anything up, on that note victorious rom works great with the new kernel, and my screen seems sharper too, I'm looking forward to more updates in the future...thank you :D
 
flashmania123 said:
Okay, first of all I want to say a Big Thank You to you JerryScript for all the dev work you have put into making Victorious and VaeVictus.

With that said, I am having a lot of issues trying to upadate from 0.1.4 to 0.2.1 or even 0.2.2-r1. I am able to get to the boot animation screen but then it just hangs there at the boot animation screen until I power off or pull the battery.

I have a few questions here:

1. What is the best way to update from 0.1.4 to 0.2.2r1 or current update when you release it?

Please keep in mind that I do have link2sd on all my apps that i possibly can and would not like to unlink all of my apps. I have already made a backup of 0.1.4 and can restore from that backup.

2. I would like to update to the current Victorious Rom when will you release the next update without the animation?

3. Can you send me a link to get rid of the annoying sound that my phone is going to self-destruct also?

I just don't want to go somewhere, turn on my phone and then quickly be escorted out of the building (you know what I mean?).


Thanks again man, you are the best!

Patiently waiting a reply,

-FM
Click to expand...

Did u clear cache and dalvik cache after the rom was successfully flashed, I had the same issue and I cleared them again and it works awesome now
 
zacharynasty said:
Did u clear cache and dalvik cache after the rom was successfully flashed, I had the same issue and I cleared them again and it works awesome now
Click to expand...
Yeah, I wiped the cache and dalvik cache. It just stays at the boot animation screen for more than 10 minutes. The only thing I can think of is to just start all over, but since I have over 300 apps on my phone It would take up a lot of my time just to update to the newest Victorious 0.2.2-r1 rom update.

I am currently on Victorious 0.1.4, I have ext2sd installed and link2sd installed. I also noticed after I tried to update to 0.2.2-r1 that I couldn't even update to 0.2.1 or any of the other newer VaeVictus Kernels after the VaeVictus-Governors update.

So, I can't even update my kernel on 0.1.4 to any of these at the moment:
VaeVictus-GPU-FastCharge
VaeVictus-0.2.1

I haven't tried any of the other kernels in between, but I may just do that to see where the rom breaks down at the boot animation screen.

These are the kernels I may try to test to see where it broke:

  1. VaeVictus-Overclocked
  2. VaeVictus-OC-Fixed
  3. VaeVictus-Freq-Fixed
  4. VaeVictus-Voltage-Fixed
  5. VaeVictus-OC-GPU
But, Yeah I am pretty sure the rom breaks down for those who are updating from 0.1.4 to 0.2.2-r1 and I think it breaks in the kernels most likely and not the boot animation. If not, It may be that I have to unlink all my link2sd apps and uninstall link2sd and or ext2sd.

Maybe if the stock or VaeVictus-Uncapped/VaeVictus-Governors kernel was temporarily put back into a 0.2.2-r2 ;)

I could then update my phone to the current Victorious rom, and then flash the newest kernel. :D


-FM
 
flashmania123 said:
Yeah, I wiped the cache and dalvik cache. It just stays at the boot animation screen for more than 10 minutes. The only thing I can think of is to just start all over, but since I have over 300 apps on my phone It would take up a lot of my time just to update to the newest Victorious 0.2.2-r1 rom update.

I am currently on Victorious 0.1.4, I have ext2sd installed and link2sd installed. I also noticed after I tried to update to 0.2.2-r1 that I couldn't even update to 0.2.1 or any of the other newer VaeVictus Kernels after the VaeVictus-Governors update.

So, I can't even update my kernel on 0.1.4 to any of these at the moment:
VaeVictus-GPU-FastCharge
VaeVictus-0.2.1

I haven't tried any of the other kernels in between, but I may just do that to see where the rom breaks down at the boot animation screen.

These are the kernels I may try to test to see where it broke:

  1. VaeVictus-Overclocked
  2. VaeVictus-OC-Fixed
  3. VaeVictus-Freq-Fixed
  4. VaeVictus-Voltage-Fixed
  5. VaeVictus-OC-GPU
But, Yeah I am pretty sure the rom breaks down for those who are updating from 0.1.4 to 0.2.2-r1 and I think it breaks in the kernels most likely and not the boot animation. If not, It may be that I have to unlink all my link2sd apps and uninstall link2sd and or ext2sd.

Maybe if the stock or VaeVictus-Uncapped/VaeVictus-Governors kernel was temporarily put back into a 0.2.2-r2 ;)

I could then update my phone to the current Victorious rom, and then flash the newest kernel. :D


-FM
Click to expand...
I will be releasing a new Victorious in the next couple of days (probably tomorrow nite). I will include the stock kernel uncapped to 1.5ghz with no overclocking, and then users can flash the kernel of their choosing. I will also revert some of the changes in the updater-script that I made in the 0.2.2 releases that may have been causing issues.

Thanks for the bug-report! ;)
 
flashmania123 said:
Yeah, I wiped the cache and dalvik cache. It just stays at the boot animation screen for more than 10 minutes. The only thing I can think of is to just start all over, but since I have over 300 apps on my phone It would take up a lot of my time just to update to the newest Victorious 0.2.2-r1 rom update.

I am currently on Victorious 0.1.4, I have ext2sd installed and link2sd installed. I also noticed after I tried to update to 0.2.2-r1 that I couldn't even update to 0.2.1 or any of the other newer VaeVictus Kernels after the VaeVictus-Governors update.

So, I can't even update my kernel on 0.1.4 to any of these at the moment:
VaeVictus-GPU-FastCharge
VaeVictus-0.2.1

I haven't tried any of the other kernels in between, but I may just do that to see where the rom breaks down at the boot animation screen.

These are the kernels I may try to test to see where it broke:

  1. VaeVictus-Overclocked
  2. VaeVictus-OC-Fixed
  3. VaeVictus-Freq-Fixed
  4. VaeVictus-Voltage-Fixed
  5. VaeVictus-OC-GPU
But, Yeah I am pretty sure the rom breaks down for those who are updating from 0.1.4 to 0.2.2-r1 and I think it breaks in the kernels most likely and not the boot animation. If not, It may be that I have to unlink all my link2sd apps and uninstall link2sd and or ext2sd.

Maybe if the stock or VaeVictus-Uncapped/VaeVictus-Governors kernel was temporarily put back into a 0.2.2-r2 ;)

I could then update my phone to the current Victorious rom, and then flash the newest kernel. :D


-FM
Click to expand...

I havent had any issues flashing any versions of rom or kernal. Are any of your 300 something apps kernal controls? Maybe you have some conflicting settings somewhere.
 
Simple enough to tell if it's the kernel I packaged in 0.2.2-r1 that is causing some people issues, just flash another kernel right after flashing Victorious. If it boots, it was the kernel, if it doesn't boot to the homescreen, it is something else.

Note- if it gets past the Victorious logo to the bootanimation, it's most likely script related.
 
Can I flash this with the new Samsung firmware update, I know the vae victus kernel can be flashed with new firmware update, but I don't want to softbrick my phone for the 20th time im serious I need authentification before I flash this with new firmware update, please respond, but thanks in advance.
 
JerryScript said:
I will be releasing a new Victorious in the next couple of days (probably tomorrow nite). I will include the stock kernel uncapped to 1.5ghz with no overclocking, and then users can flash the kernel of their choosing. I will also revert some of the changes in the updater-script that I made in the 0.2.2 releases that may have been causing issues.

Thanks for the bug-report! ;)
Click to expand...

Sounds awesome. Any word yet on how to change the boot animation or do you have a .zip file that I can flash back to the stock boot animation?

Thanks JerryScript,

-FM
 
Madbat said:
I havent had any issues flashing any versions of rom or kernal. Are any of your 300 something apps kernal controls? Maybe you have some conflicting settings somewhere.
Click to expand...

The only app I used was Kernel Tuner, but I may just uninstall that temporarily to see if that helps at all.

Thanks for the tip Madbat.


-FM
 
flashmania123 said:
The only app I used was Kernel Tuner, but I may just uninstall that temporarily to see if that helps at all.

Thanks for the tip Madbat.


-FM
Click to expand...

Kernel Tuner worked fine for me until a couple updates ago of it. I wouldn't reccomend using it simply because it's designed for HTC phones, and it was giving me issues personally, locking frequencies too high and not letting other apps control anything. I posted about it and how I dealt with it here: http://androidforums.com/virgin-mob...ed-1-8ghz-updated-8-8-13-a-3.html#post6047106
 
For what its worth I have latest victorious and vaevictus with no issues. Thats one of the reasons I donated to vmobi. To keep the great stuff coming. I hope the rest of you have donated too! It can only help it keep on getting better.:D
 
So today my phone kept prompting me to update Android, I know doing this will mess up my root right? So my next question is there a way to turn off this constant reminder to upgrade the Android?
 
Thank you again, you were correct. I clicked on install update like you said and it failed and has not bugged me all day to try again. Also I finally used the steps listed in the OP and I am happy to say it seems I have all sorts of space now that link2SD works perfectly! You guys have been great in helping this newbie in the world of rooting. I can not wait to see what else is in store!
 
So question why doesn't my tethering work? Here are some screenshots of the settings.
i.imgur[dot]com/NSHY5rE.png
i.imgur[dot]com/BctzfLz.png
i.imgur[dot]com/FCN0i8Y.png
i.imgur[dot]com/zPBpkhI.png
i.imgur[dot]com/d11HReT.png
 
MattB92 said:
So question why doesn't my tethering work? Here are some screenshots of the settings.
i.imgur[dot]com/NSHY5rE.png
i.imgur[dot]com/BctzfLz.png
i.imgur[dot]com/FCN0i8Y.png
i.imgur[dot]com/zPBpkhI.png
i.imgur[dot]com/d11HReT.png
Click to expand...


your pics werent enough to show if you followed all steps in post 2 of this thread so here they are again.



Open Wifi Tether-TrevE Mod in your app drawer
Press your Menu key and select Settings
Select Change Device-Profile and scroll down to select Samsung Galaxy Nexus (CDMA/LTE)
Check Send Netd Max Client Cmd
Optional : Enable WiFi-Encryption (recommended)
If you enabled WiFi-Encryption, select Change Passphrase and enter a password at least 8 characters long
Optional: Change SSID (recommended change the name to something you like, after all there's lots of AndroidPhones!)
Optional: Change Channel (try till you find the best results)
Check WiFi-driver reload (tested and works)
Press your back button
Press the large white WiFi symbol to start tethering, it will turn yellow once tethering is active, (note- you will have to grant SuperUser rights the first time)
Now you can connect to your phone using the SSID and passphrase you entered
Press the large yellow WiFi symbol to turn off tethering, then exit the app
 
hello there, I have come across a problem. So the other day I installed this rom (Victorious-0.2.2-r1) to my Samsung Galaxy Victory using TWRP. It installed correctly and worked just fine for a few hours. then my phone would suddenly freeze up and the screen will go blank. after about a minute the phone will reboot itself. then the phone will work for about 5 seconds and freeze up and restart aging. I need my phone to work, so I went in to TWRP and tried to uninstall, reinstall this rom or another rom, or just simply wipe my phone and start fresh with a new rom. Every time I tried to do the TWRP would run for a few seconds, and then say failed, Updating Partition Details. but it just stops there. Can you please help me. I tried out this rom for a few hour before it froze, but this rom is great. please tell me how to can my phone working again. it is probably just a rookie mistake.
 
Download the stock recovery from Jerry and stock backup from G60. Install the recovery with Odin, then flash the stock backup.

If that doesnt work your SD card may be kaputski.

Are you using twrp 2.5? Rumor has it that it is 'broken', though I can't recall how.
 
You must log in or register to reply here.
Back
Top Bottom