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

Root [Kernel]OptimusM OC stock 2.2.1

For those of you with the know how until I get a flashable kernel update with working wifi you can unpack the boot.img of a rom and just replace the zImage file with the one from the kernel update. Repack it, drop it in your rom's zip and flash. You will have functioning wifi. This may fix any boot loop problems. I still don't know why some people have boot loops while others don't :/
 
For those stuck in a boot loop did you by chance wipe your data along with your cache? If so try flashing a working rom, boot up, reboot into recovery and wipe only your cache and dalvik cache, then flash the kernel. Let me know if this helps.
 
reppard said:
For those of you with the know how until I get a flashable kernel update with working wifi you can unpack the boot.img of a rom and just replace the zImage file with the one from the kernel update. Repack it, drop it in your rom's zip and flash. You will have functioning wifi. This may fix any boot loop problems. I still don't know why some people have boot loops while others don't :/
Click to expand...

i was reading some articles on building the kernels and they suggest that you may have to recompile the wifi module separately for it to work.

so like... why the 4311 can't I repack the kernel into the boot.img!!!

what offset are you using to do this??

i've tried doing it manually with mkbootimg, with the upack and repack scripts and liquidmkbootimg... i've even unpacked a working boot.img and repacked it... and no luck?!... i need a drink!
 
reppard said:
For those stuck in a boot loop did you by chance wipe your data along with your cache? If so try flashing a working rom, boot up, reboot into recovery and wipe only your cache and dalvik cache, then flash the kernel. Let me know if this helps.
Click to expand...

I only wiped the two caches mentioned in the first post.
 
new optimus said:
hey how did you get into recovery to do a nand restore?

having the same issue I can not get the phone to go into recovery
using anreboot it just restarts using adb reboot recovery it just restarts.
Click to expand...

take the battery out put it bak in ...hold those buttons while u power on ..tahts how i did it,...power+down+home ..try holding home n volume down than power
 
Hello guys, i tried using this kernel on both Team Chicken Eaters and the UI ROM for 2.2.1 before i flashed i wiped both caches. And on both occasions got the same result upon my reboot. It got suck on the LG screen and wouldn't move on past it.....

I really want to get that solved so i can OC and enjoy the most bad ass android phone for its price range :D
 
reppard said:
For those of you with the know how until I get a flashable kernel update with working wifi you can unpack the boot.img of a rom and just replace the zImage file with the one from the kernel update. Repack it, drop it in your rom's zip and flash. You will have functioning wifi. This may fix any boot loop problems. I still don't know why some people have boot loops while others don't :/
Click to expand...
could it be the kernel zip size,using fire fox my file size is 3.2mb an it boot loops (lg logo) Rom GB_CM7_OPTMBETA
 
I don't know if this will help, but...

I bought SetCPU and flashed the OC kernel back in. I don't know how it's related, but the OC kernel causes my live wallpaper to chop up and not play smoothly. I already mentioned that, though. What's new; I ran my stress test stable at 787 MHz, but it crashed pretty quick at 806 MHz. Once it crashed at 806, it would not come back. It would only bootloop. Pulled the battery to reset it, went to recovery, and put my nandroid backup back on no issue.

At 787 MHz, the Live Wallpaper remained choppy, but ADW's screen animations and other menu scrolls were beautiful smooth on the otherwise-stock ROM.
 
hemmy.c said:
take the battery out put it bak in ...hold those buttons while u power on ..tahts how i did it,...power+down+home ..try holding home n volume down than power
Click to expand...
Thank you, I actually just was able to use the power button to power off then do the key press, had to do it 3 times though must have slipped on a key the first 2 lol.

TheAmazingDave said:
I don't know if this will help, but...

I bought SetCPU and flashed the OC kernel back in. I don't know how it's related, but the OC kernel causes my live wallpaper to chop up and not play smoothly. I already mentioned that, though. What's new; I ran my stress test stable at 787 MHz, but it crashed pretty quick at 806 MHz. Once it crashed at 806, it would not come back. It would only bootloop. Pulled the battery to reset it, went to recovery, and put my nandroid backup back on no issue.

At 787 MHz, the Live Wallpaper remained choppy, but ADW's screen animations and other menu scrolls were beautiful smooth on the otherwise-stock ROM.
Click to expand...
One thing to remember when you are using set cpu and overclocking DO NOT check the box to set on boot. If you do it will try to set the last speed before reboot and if it is not stable it will crash and reboot again, Probably all the problems with the boot loop. because this overclock kernel tells setcpu that the max of the cpu is higher, it adjusts it up to the max on boot, when it is needed to speed it up you know.

Every cpu is different sometimes you get the lucky side and have a cpu that can go higher 845mhz is I think the highest I heard of though I could be wrong.
Sometimes you get the short end of the stick and have one that cant got 40mhz over though I bet the short end on these phones is 747mhz or so not 640-80 some.

My phone was able to run stress test for 5 mins, all the time I let it, at 806mhz that is not enough time to tell if it is stable though. at 825mhz it ran the test for 5 seconds and rebooted.
 
Tried to play Speedx 3D with the OC kernel, and the game won't play. The graphics are seriously screwed.

So I played with the different clock speeds again. I definitely, 100% sure, had the set on reboot box unchecked, and I'm sitting here watching my phone bootloop after it crashed again at 806 MHz.

And now, after about 10 loops and the time it took to type this, it's stuck on the LG screen.

edit: got phone to boot without a restore by clearing the caches again.
 
noob question... so if i already have my cyanogen mod installed all i have to do is clear cache and flash this like normally, as in no wiping? just making sure before i give this a try
 
reppard, same result boot loops then freeze's on 2nd lg logo im a restore my nad an try again wit balls crossed



edit:Nand restore, kernel load results same.Rebooted(cm7 a2sd-Rom),restored an it 2 is boot loopin so here i wait
 
Dubtee I get the same problem as you.... I posted a thread on it so as to not contaminate this one. Maybe someone can post some help there i would appreciate it.
 
wiped cache and dalvik cache.
boot past white lg logo,
reboots after about 1 second of second lg
after white logo again it got stuck at second boot screen for a minute of so,
then rebooted to white logo and stuck on second for for an extended amount of time.
no response to adb

pulled battery, booted and stuck at second lg screen. but atleast responding to adb... if only an error!
Code: 
t3084@uFREEDOM:~/android/tools/bootimages$ adb logcat
- exec '/system/bin/sh' failed: No such file or directory (2) -

it rebooted after awhile, goes to second screen amd rebooted a couple times. now adb doesn't even give an error.

over and over and over >.<
 
i must say I like being able to update with the boot.img i couldn't restore my previous kernel with the first download.

if you can't boot up the oc kernel in this boot.img, instead of flashing the whole rom, you can flash 221kernel_CM07ramdisk.zip to go back to the stock kernel.
 
blaxican25 said:
i bet if you guys download the kernel with internet explorer you wont get the boot loops.
Click to expand...


You flash the new one with no problems? If so I don't know what the hell these guys are doing :p. I tested by flashing the gbrom to revert to the old kernel and the flashed the updatem. Worked like a charm. Maybe it's something in the kernel that some people's phone doesn't like...
 
You must log in or register to reply here.
Back
Top Bottom