Root [Kernel]OptimusM OC stock 2.2.1

thunderkiss65 · Jun 4, 2011

TheAmazingDave said:
So when mine bootloops (as it still does occasionally when it crashes due to OC) I can get it to reboot normally by wiping only Dalvik cache.

I know I sound like a broken record, but what I see consistently from those of you with bootloops is that you're reflashing the kernel at the same time, it seems.

Try this; when your phone crashes and begins bootlooping, remove the battery.

After removing the battery for a few seconds, put it back on.

Use the hardware keys to enter recovery (Vol Down + Home + Power).

Once in recovery, only wipe Dalvik cache and reboot.

Unless my phone is different (which I guess it could be) this fixes the bootloop every time. No need to reflash anything.

Yes dave i dont think theyre rebooting after doing the first flash.

TheAmazingDave · Jun 4, 2011

somedood81 said:
I have booted into recovery cleared ALL, flashed CM7, cleared both caches then flashed kernel and it still boot loops.

I've wiped both caches, flashed rom, reboot, wipe both caches, flash kernel, boot loop.

Heck I cant even flash the supposedly stock kernel posted in this thread without boot loop.

But after a bootloop, did you try exactly what I said? That is, pull battery, recovery, wipe only Dalvik, and try to boot again?

I experienced the constant bootloop you describe, and what I posted has been working for me each time the bootloop has come back.

thunderkiss65 · Jun 4, 2011

TheAmazingDave said:
So when mine bootloops (as it still does occasionally when it crashes due to OC) I can get it to reboot normally by wiping only Dalvik cache.

I know I sound like a broken record, but what I see consistently from those of you with bootloops is that you're reflashing the kernel at the same time, it seems.

Try this; when your phone crashes and begins bootlooping, remove the battery.

After removing the battery for a few seconds, put it back on.

Use the hardware keys to enter recovery (Vol Down + Home + Power).

Once in recovery, only wipe Dalvik cache and reboot.

Unless my phone is different (which I guess it could be) this fixes the bootloop every time. No need to reflash anything.

And i wish i would have thought about removing the battery and going into recovery the first time it happened to me,, I havent had one boot loop or crash yet, but will remember this post lol.

ehall8702 · Jun 4, 2011

first attempt on fresh cmod 7 flas everything works perfect running at 800 mhz using cpu mater (free) wifi works also about to send a mms to see if that fix worked correctly too. first thing i noticed is that my wired headset mic doesnt work sucks cause i use it daily but worth the trade off for oc'd cyanogen! reppard...lemme know where to send a headset so u can get that working! also, any one know of a good stability tes to run on this thing so i can find my highest stable sppeed?

somedood81 · Jun 4, 2011

TheAmazingDave said:
But after a bootloop, did you try exactly what I said? That is, pull battery, recovery, wipe only Dalvik, and try to boot again?

I experienced the constant bootloop you describe, and what I posted has been working for me each time the bootloop has come back.

I'm never getting one clean boot with the OC kernel.

I just did this:

recovery, wipe both cache, flash rom, reboot, recovery, wipe both cache, flash kernel, boot loop, remove battery, recovery, wipe only dalvik cache, boot loop, boot loop, boot loop, boot loop....

ehall8702 · Jun 4, 2011

i spoke too soon i guess the screen started getting laggy so i bumped down to 787.2mhz then to 600 and it still had a laggy screen i uninstalled cpu master and cleared cache and its fine now but no way to manipulate freq. n/m that just rebooted might just run stock kernel till bugs r ironed out

thunderkiss65 · Jun 4, 2011

somedood81 said:
I have booted into recovery cleared ALL, flashed CM7, cleared both caches then flashed kernel and it still boot loops.

I've wiped both caches, flashed rom, reboot, wipe both caches, flash kernel, boot loop.

Heck I cant even flash the supposedly stock kernel posted in this thread without boot loop.

Wipe everything but SD ext. Then flash rom. Then go into recovery and wipe dalvik cache and cache. Then flash kernel
It worked for me!

thunderkiss65 · Jun 4, 2011

somedood81 said:
I'm never getting one clean boot with the OC kernel.

I just did this:

recovery, wipe both cache, flash rom, reboot, recovery, wipe both cache, flash kernel, boot loop, remove battery, recovery, wipe only dalvik cache, boot loop, boot loop, boot loop, boot loop....

Even the first time it worked for me without flashing to updated cm7. I just wiped dalvik cache and cache. The only reason I flashed to rom was because of boot loop. Dave had the answer to that lol

blaxican25 · Jun 4, 2011

it's working now yeah lol

thunderkiss65 · Jun 4, 2011

blaxican25 said:
it's working now yeah lol

How you get it bro

nomorefear · Jun 4, 2011

none of this has worked for me.... boooo

TheAmazingDave · Jun 4, 2011

somedood81 said:
I'm never getting one clean boot with the OC kernel.

I just did this:

recovery, wipe both cache, flash rom, reboot, recovery, wipe both cache, flash kernel, boot loop, remove battery, recovery, wipe only dalvik cache, boot loop, boot loop, boot loop, boot loop....

I can't reproduce that. I'm sorry.

thunderkiss65 · Jun 4, 2011

TheAmazingDave said:
I can't reproduce that. I'm sorry.

Dave I noticed before when I cranked it up towards 900 I got the boot loop instantly. Do you think if I toy with it again and go higher into the 800's and it takes me back to the boot loop can I just do as you said take battery out wipe dalvik and I can get it back. Wondering does that lower the CPU or not.

TheAmazingDave · Jun 4, 2011

It may also be worth trying to flash from a new SD card. They can/do wear over a certain number of read/write cycles. It's possible your SD card has bits that aren't operating correctly, which may normally go unnoticed, but could also cause failures in these mission-critical operations where data integrity is the highest priority.

blaxican25 · Jun 4, 2011

well i went the long way lol re did the LG-LGNPST update re rooted flashed the recovery and downloaded the updated cm7 rom flashed it, flashed the mms fix, then flashed the kernel and it worked lol weired but all works lol and i added my boot sound too.

TheAmazingDave · Jun 4, 2011

thunderkiss65 said:
Dave I noticed before when I cranked it up towards 900 I got the boot loop instantly. Do you think if I toy with it again and go higher into the 800's and it takes me back to the boot loop can I just do as you said take battery out wipe dalvik and I can get it back. Wondering does that lower the CPU or not.

Every time I crash my phone with too high of a clock, I get a bootloop. When I reset with the procedure I posted above, the phone boots normally.

I am very careful to leave the set on boot box unchecked so I do not know what is causing the bootloop after an overclock-related crash. Regardless, if you did not check the box and you are bootlooping after an OC-related crash, I believe the chances are good that clearing the Dalvik cache will clear up the trouble without any other action.

reppard's default max clock with no SetCPU (or similar program) intervention appears to be 800 MHz. This isn't a valid clockspeed for the CPU's stock multipliers, so it appears to be defaulting to a max of 787 MHz. The next valid clock is 806 MHz, and it (the phone) won't failsafe to a higher clock unless you set it yourself. I'm going to wager that most of our phones are stable enough at this speed (787 MHz) to boot, so I don't think it's overheating during boot and causing the loop.

nomorefear · Jun 4, 2011

I have switched my sdcard and yet nothing still

thunderkiss65 · Jun 4, 2011

blaxican25 said:
well i went the long way lol re did the LG-LGNPST update re rooted flashed the recovery and downloaded the updated cm7 rom flashed it, flashed the mms fix, then flashed the kernel and it worked lol weired but all works lol and i added my boot sound too.

lol been awhile since I seen LGNPST. Well good to hear you got it. I wouldn't go above that 806. I was noticing some heat. So I set it to ondemand. That fixed that and I still see the better performance.

Seirren · Jun 4, 2011

Look guys Reppard is already suspecting what the problem is and why it wont work on certain phones. It is because he changed the stock max speed on this Kernel and right from boot its to high for certain phones. SO on certain phones NO MATTER WHAT YOU DO unless you change the kernel yourself you will not be able to boot in the kernels current state. Reppard is at the moment working on a new version of the Kernel that has a lower default max speed. This will hopefully solve the boot loading issue.

The new lower default max speed will not limit your overclocking capabilities as you can exeed it using Set CPU. The only limitation in this case would be your hardware, and you cant do anything about that, short of getting a new phone.

So just be patient guys and the problem should be fixed soon. Thanks guys.

I hope this has helped some of you with questions on what is going on at the moment.

blaxican25 · Jun 4, 2011

stress tested mines at 806 mhz and running stable when i went higher then that i got the boot loop.

new optimus · Jun 4, 2011

Very good post.

TheAmazingDave · Jun 4, 2011

for those in my boat who are having crashes and subsequent bootloops:

YouTube - ‪Overclocked Optimus M on 2.3.3 bootlooping after crash‬&rlm;

thunderkiss65 · Jun 4, 2011

blaxican25 said:
stress tested mines at 806 mhz and running stable when i went higher then that i got the boot loop.

Are you noticing the difference. I sure am

thunderkiss65 · Jun 4, 2011

TheAmazingDave said:
for those in my boat who are having crashes and subsequent bootloops:

YouTube - &#x202a;Overclocked Optimus M on 2.3.3 bootlooping after crash&#x202c;&rlm;

That sums it up

Seirren · Jun 4, 2011

Again TheAmazingDave's video will only work if your phone crashed due to you overclocking the kernel to much. Meaning it originally worked. But if you boot loop right after flashing the ROM without ever being able to even see the android its not going to work for ya. So now you know and don't have to post asking about it

Thanks Dave.

Root [Kernel]OptimusM OC stock 2.2.1

Well-Known Member

Android Expert

Well-Known Member

Newbie

Newbie

Well-Known Member

Well-Known Member

Android Expert

Well-Known Member

Member

Android Expert

Well-Known Member

Android Expert

Android Expert

Android Expert

Member

Well-Known Member

Newbie

Android Expert

Android Expert

Android Expert

Well-Known Member

Well-Known Member

Newbie

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads