Root Droid Overclock Not applying at Boot? (.595)

[Raryn]

After upgrading to .595 is anyone else having trouble with their undervolting not being applies at boot? I have a custom setting thats preset to apply, but I have to manually enable it anytime I reboot my phone.

 

[cougar214]

Funny, I'm on the 595 and my droid overlock does the opposite. It wont apply the settings at all until I tell it to apply them at boot.

 

[Airmaxx23]

After upgrading to .595 is anyone else having trouble with their undervolting not being applies at boot? I have a custom setting thats preset to apply, but I have to manually enable it anytime I reboot my phone.

I've had to do the same thing starting with the first GB leak and continuing with this one. I really don't mind doing it manually, it only takes a few seconds.

 

[Raryn]

I've had to do the same thing starting with the first GB leak and continuing with this one. I really don't mind doing it manually, it only takes a few seconds.

That might actually explain my really inconsistent battery life.

Has Jrummy posted anything about a potential fix yet?

 

[gtixpress]

My overclock doesn't want to load at all and I'm on the odexed version of .595. it complains that BusyBox isn't installed and then fails when it tries to install it. Although Titanium Backup reports that Busybox is correctly installed. I'm going to try the deodexed version of .595 to see if that helps.

 

[cougar214]

Did you try getting busybox from the market?

 

[gtixpress]

Turns out there is a problem with the odexed version of .595. I could never get Busybox to install correctly and when I used D2 recovery to create a backup, it got stuck in a boot loop. I had to SBF back to .340 and make my way back to .595 again. THis time I used the deodexed version and all is working.

 

[caveritt]

Any update on the OC set at boot? I am running .595 rooted deodexed and experiencing the same issues. Keep forgetting after reboot to set it back.

 

[quickaudi]

Turns out there is a problem with the odexed version of .595. I could never get Busybox to install correctly and when I used D2 recovery to create a backup, it got stuck in a boot loop. I had to SBF back to .340 and make my way back to .595 again. THis time I used the deodexed version and all is working.

yup, this seems to be my problem as well with busybox

can't get it to install, busybox installer faults out, so I'm going to probably end up following your steps

ugh, SBF time again, all for an incorrect file

 

[bouchigo]

yup, this seems to be my problem as well with busybox

can't get it to install, busybox installer faults out, so I'm going to probably end up following your steps

ugh, SBF time again, all for an incorrect file

If you have root explorer, just take a copy of busybox and move it to system/xbin and set permissions, and you should be fine after a reboot

 

[caveritt]

yup, this seems to be my problem as well with busybox

can't get it to install, busybox installer faults out, so I'm going to probably end up following your steps

ugh, SBF time again, all for an incorrect file

Couldn't you just install the deodexed update over the odexed version already on the phone? I would try that before SBF'ing.

 

[ylexot]

I'm running 595 deodexed and am not having the problem. I did get the "busybox not installed", but I was able to install it.

 

[caveritt]

I'm running 595 deodexed and am not having the problem. I did get the "busybox not installed", but I was able to install it.

And the overclock is sticking after the reboot?

 

[bouchigo]

If you don't want to apply the deodexed version of .595 over your current setup, you can apply this deodex zip I made instead:

GB_2.3.3_4.5.595_Deodexed.zip

 

[ylexot]

And the overclock is sticking after the reboot?

Yes.

 

[quickaudi]

Couldn't you just install the deodexed update over the odexed version already on the phone? I would try that before SBF'ing.

possible - would it be best to wipe data/cache before doing this? maybe no need?

the other problem is that I can't seem to get D2 bootstrapper to download onto my phone - don't understand why

so, if I disable USB debugging, will DX bootstrapper actually work? or would it be better to use the ROM Manager to boot into Clockwork Recovery?

 

[quickaudi]

If you don't want to apply the deodexed version of .595 over your current setup, you can apply this deodex zip I made instead:

GB_2.3.3_4.5.595_Deodexed.zip

differences between this deodex and TBH deodex?

 

[caveritt]

possible - would it be best to wipe data/cache before doing this? maybe no need?

the other problem is that I can't seem to get D2 bootstrapper to download onto my phone - don't understand why

so, if I disable USB debugging, will DX bootstrapper actually work? or would it be better to use the ROM Manager to boot into Clockwork Recovery?

Have read a few post in different forums of people going stright to deodexed without a wipe. I would probably make a backup first then just try. If it don't work wipe and try again.

Wonder why D2 bootstrap won't install. Have not seen any other issues with it. I have tried the DX bootstrap in .588 and it worked once I turned off debugging, but have not tried it since .595.

Lettuce know

 

[quickaudi]

Wonder why D2 bootstrap won't install.

I'm sure it installs fine. I just can't get it to download to my phone. Might just be the link that I have. At work right now, so no way to d/l to computer and put it on my phone (thanks, IT.)

Gonna d/l bouchigo's deodex file and give 'er a shot through DX bootstrapper. Will post back in a few hours, lol. (Bad service here, too.)

 

[quickaudi]

oh good grief, unchecked USB debugging and still bootlooped

 

[caveritt]

oh good grief, unchecked USB debugging and still bootlooped

Did you get my PM?

 

[quickaudi]

Did you get my PM?

did, thank you sir!

in a bad bootloop now - won't even let me get to stock recovery after I tried the above.

will SBF when I get home.

 

[quickaudi]

so, to add to this thread, after coming back through the process again, Droid Overclock is applying at boot on its own on bouchigo's .595 deodexed file.