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

Root [Virgin Mobile/Sprint] overclock kernel V4 !

Thanks for the quick update. I haven't tried v4 yet but I have a few questions.

1. Is the gpu capable of handling an overclock that high?

2. Does this require the phone to be on v5 like the old one?

3. On v2 I noticed that the stock speed of 400mhz had been replaced by the overclock. Is there any chance of having the stock speed in addition to the overclock in case of instability?

For example 192, 320, 400, 450 and 544 as frequency options for the max gpu frequency.
 
Thanks for the quick update. I haven't tried v4 yet but I have a few questions.

1. Is the gpu capable of handling an overclock that high?

2. Does this require the phone to be on v5 like the old one?

3. On v2 I noticed that the stock speed of 400mhz had been replaced by the overclock. Is there any chance of having the stock speed in addition to the overclock in case of instability?

For example 192, 320, 400, 450 and 544 as frequency options for the max gpu frequency.

1. Yes
2. No, neither did the old.
3. Not at this time.

This also includes any fixes in the stock V6 update kernel.
 
This only affects stock launcher. Nothing else... but if you can't fix it is okay. BTW what rom should i use for this particular kernel??
 

Attachments

  • 20140505_163621.jpg
    20140505_163621.jpg
    24.6 KB · Views: 122
This only affects stock launcher. Nothing else... but if you can't fix it is okay. BTW what rom should i use for this particular kernel??

I use the stock launcher. It works fine. You need a lower limit on your max frequency.
 
This looks awesome so far. I'll probably wait til the next version to actually start using it. You can flash this in recovery, right? Or GUI flash kernel?
 
Can not find your file when I go to flash it through recovery... What am I doing wrong???? I see it's a .lok file and not a zip.
 
uh, easiest way for rooted vm720 is probably:
-->install android terminal emulator (play store)
-->download/save V4 boot image to root directory of external sd
-->in android terminal emulator type:
su <hit enter to become root>
cd /storage/external_SD/

dd of=ls720.original.img if=/dev/block/platform/msm_sdcc.1/by-name/boot

to save a copy of the existing boot image, and then the following to install the V4 overclocked boot image

dd if=ls720.overclockV4.lok of=/dev/block/platform/msm_sdcc.1/by-name/boot

---------
you can do it all on your rooted phone w/o PC....so easy! thanks, Robaho :-)
 
robaho

Just wanted to say thank you for sharing your Dev work and help with the F3 community and for not abandoning us due to a few bad apples.

Thanks!
 
Did I do this right I'm not seeing any thing but this after typing in what I need to.
 

Attachments

  • 1399386963813.jpg
    1399386963813.jpg
    55.4 KB · Views: 112
Hi Androidninja, looks good to me. *Just reboot and V4 should be running.* I also use Playstore's 'System Tuner' in conjunction with 'Quick CPU Lite' and 'Pimp my Rom' (beta). Specifically, I enable universal init.d with 'Pimp my Rom' (beta), then I use cpu mgr section within 'System Tuner' to set 1836max/384min for *init.d*. 'Quick CPU Lite' works on boot, so there is redundancy but it is effective. I cannot recommend 'Pimp my Rom' (beta) strongly-enough and you can see your cpu speeds extremely well in the app's cpu section; it is my all-time favorite tweak app....you'll see why. Good luck! :-)
 
Hi Androidninja, looks good to me. *Just reboot and V4 should be running.* I also use Playstore's 'System Tuner' in conjunction with 'Quick CPU Lite' and 'Pimp my Rom' (beta). Specifically, I enable universal init.d with 'Pimp my Rom' (beta), then I use cpu mgr section within 'System Tuner' to set 1836max/384min for *init.d*. 'Quick CPU Lite' works on boot, so there is redundancy but it is effective. I cannot recommend 'Pimp my Rom' (beta) strongly-enough and you can see your cpu speeds extremely well in the app's cpu section; it is my all-time favorite tweak app....you'll see why. Good luck! :-)


Well I did and I got stuck in a boot loop and can not do any thing because I do not have a back up and my phone is useless at this point until I flash the stock rom again or whatever.... My fault for not having a back up but I didn't think a boot loop would happen with just doing a overclock kernel
 
Flash it again. It may not of flashed correctly. You flashed a modified boot.img, anytime you flash anything you can soft brick your phone.

Boot to the recovery to access adb
 
Flash it again. It may not of flashed correctly. You flashed a modified boot.img, anytime you flash anything you can soft brick your phone.

Boot to the recovery to access adb

I can not do anything it stays stuck at the lg boot logo when i power on. I factory reset/hard reset my phone and that did not help... I can not get into recovery now so what am i to do??
 
I can not do anything it stays stuck at the lg boot logo when i power on. I factory reset/hard reset my phone and that did not help... I can not get into recovery now so what am i to do??

If you can't get into recovery then you really messed things up some how. Recovery uses its own kernel so it is unaffected by the overclock.

Sounds like you messed up the aboot - like installing the V6 version so now it won't boot a lokified image.

You'll need to use the unbrick method....
 
If you can't get into recovery then you really messed things up some how. Recovery uses its own kernel so it is unaffected by the overclock.

Sounds like you messed up the aboot - like installing the V6 version so now it won't boot a lokified image.

You'll need to use the unbrick method....

To be clear, lokified images only work with the V5 aboot !!!
 
I can not do anything it stays stuck at the lg boot logo when i power on. I factory reset/hard reset my phone and that did not help... I can not get into recovery now so what am i to do??
A factory reset does not touch the recovery partition (image). Factory reset only wipes (formats) the /data and /cache partitions. Not boot, not recovery, just what you have added to the phone since you personalized it. Android OS and it's apps are not wiped. So this leave you with a phone almost like it was when you got it. I say almost because all the bloatware you may have removed is still gone. Updated system apps are still updated. It's just everything that made the phone "You" is gone. If you can't enter recovery and you can't boot the system the only alternative is to use sammyz's unbrick method. I just can't figure out how the recovery image got involved in this problem. :confused:
 
I can only get into android system recovery not download mode. I can not figure out how i got in a boot loop just i went to restart and that happened. I done all the steps and used adb teminal emulator to do the process so i dont see ho i could of effed things up but im mad at myself honestly. I didnt flash any thing just tried to use the oc and i thought i done things right until i get stuck in a boot loop which is lame. I guess ill try the unbrick method which hopefully works because i need my phone and all today i needed it most because shit was happening lol go figure...
 
I can only get into android system recovery not download mode. I can not figure out how i got in a boot loop just i went to restart and that happened. I done all the steps and used adb teminal emulator to do the process so i dont see ho i could of effed things up but im mad at myself honestly. I didnt flash any thing just tried to use the oc and i thought i done things right until i get stuck in a boot loop which is lame. I guess ill try the unbrick method which hopefully works because i need my phone and all today i needed it most because shit was happening lol go figure...

The way i go into download mode is not as instructed. You will need to:
1.Remove battery
2.Connect USB cable with computer and the phone
3.Press only the VOL + (Volume up) key
4.Insert Battery holding the volume up key
5.You should be in Download mode aka dl
 
I can only get into android system recovery not download mode. I can not figure out how i got in a boot loop just i went to restart and that happened. I done all the steps and used adb teminal emulator to do the process so i dont see ho i could of effed things up but im mad at myself honestly. I didnt flash any thing just tried to use the oc and i thought i done things right until i get stuck in a boot loop which is lame. I guess ill try the unbrick method which hopefully works because i need my phone and all today i needed it most because shit was happening lol go figure...

To get into download mode you need the cable connected to the computer when you power on while holing volume up.
 
Back
Top Bottom