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

Root Overclock Droid X 2.2 via Update.zip

installed update.zip and i have done the old version of this back in the 2.1 days so it was nice and simple and thanks!

My Question is back on 2.1 when i want into quadrant it would tell me current freq was whatever i OC'ed it to... now it says current freq somewhere between 400 and 700 then max freq 1380 and min 300... anyone no why that is??

Is there some sort of script in the update.zip file that when the phone is doing certain things it will change the current freq??
 
Ok I have read and followed the instructions carefully ...I downloaded the zip file and installed it in clockwork then when I reboot I go to terminal emulator and go.to write the.script but every time I get to finish the insmod/system/lib/modules/overclock.no line this pops up ..insmod/system/lib/modules/overlock.no:not found....am I doing something wrong? Also once this is installed properly how can I tell if I am overclocked?

You didn't copy and paste i see. there is a space after insmod.


insmod /system/lib/modules/overclock.ko


and its KO, not NO.
 
Ok I have read and followed the instructions carefully ...I downloaded the zip file and installed it in clockwork then when I reboot I go to terminal emulator and go.to write the.script but every time I get to finish the insmod/system/lib/modules/overclock.no line this pops up ..insmod/system/lib/modules/overlock.no:not found....am I doing something wrong? Also once this is installed properly how can I tell if I am overclocked?

I did this the very first time to it is hard to see in the instructions and it should be insmod(SPACE)/system/lib/modules/overclock.ko or basically insmod /system/lib/modules/overclock.ko . Hopefully this helps.
 
ok its all typed in but theres no way to like cinfirm it persay.....or how do i know its actually overclocked?
 
FYI my x is on fire with this much oc... way more of an impact than the 2.1 oc. i used the update.zip and left as is. If its not broke dont fix it!

quadys giving me 1800's and everythings flying.

woop!
 
First off Beesley A HUGE THANKS for this!! I am still on the leak with Rubix 1.0 and pulling 19+ on Linpack and 1800+ on Quadrant.

For anyone this app makes it VERY easy, I made two new files one called Overclock On and one Overclock Off. I just copied and pasted the terminal commands and then saved, a long press on the file you create allows you to edit the scripts or save them to the SD card.

From Beesley:
recommend you get the app called GScript and then make the following scripts (very easy!)


To turn OC On

Code:
insmod /system/lib/modules/overclock.ko
setscaling100.sh
To turn OC Off

Code:
rmmod overclock.ko

This will allow pushbutton OC enabling upon reboot. Also makes for easy testing of new values if you edit the setscaling100.sh via root explorer.

Hope this makes it a little easier!
 
Quick question to the lucky ones that got this working are you running any rom and deodexed? Or do you need to be odexed?
 
Ive been running this for about 6 hours or so, with no hiccups, freezes, or reboots. I am on Apex RC2 with the Apex NexTheme. It doesnt really matter what ROM you might be on, each device takes to over/underclocking differently. You just have to find what works for yours and enjoy it!
 
Alrighty then, time for Bootstrapper to earn it's stripes or so it seems. I went into ROM manager and pulled up Beesley's Build.props to try to install this and somehow my phone got a factory reset. Now the good news is that all of my apps got redownloaded off the market immediately thanks to Google. The bad news is I have to start from scratch getting all my home screens back to where they were before and all my settings just right, etc... so I assume this is where the recovery part of the equation factors in. So I went to ROM Manager, chose restore, found my last restore point, started it and it began to do it's thing. Got to the end, said something about shm mismatch (or something like that) and sent me right back to square one.

So then I pulled up the Droid X Bootstrapper Recovery, found my last backup made on it, and when I went into recovery it had a list of things I could do... restore the boot, restore the system, restore the cache, etc... I clicked on restore the boot and it asked me if I was sure I wanted to do this because it was irreversable... so, I figured I'd better check it out on here and make sure that's what I want to do, because I've never had to do this before and don't know forsure which one I want to restore.

So I ask, which door is the free car hiding behind?
 
well been running at 1380 just fine all day now! quadrant in 1800 on Rubiks 1.0. I made no changes in setCPU
 
Ok everything is back to normal on my phone now thanks to Bootstrapper. Thank GOD for Bootstrapmod Recovery!!! Now my question is, and it's been asked a few times on here already and I haven't seen it answered, does the phone need to be deodexed before running Beesley's ROM in ROM Manager?

Just trying to figure out what I did wrong.
 
so with Rubix blurry 3.0 I could only overclock to 1.2 but if I charged my phone it would freeze up. Now with stock 2.2 deodexed its running at 1.38 but I haven't charged it yet
 
Alrighty then.... well don't worry about the deodexed question, I figured it out. I'm not deodexed and this worked fine for me. As soon as I finished installing it I hit a 1731 on Quadrant (previous high was around 1380), and an 18.49 Linpack (previous high.... uh 15ish as far as I can remember). So yes, much faster than before.

Other than that I must say I don't notice a night and day difference in my phone from before. I'd always considered it fairly peppy anyhow, so maybe there wasn't a whole lot to improve upon? I dunno, haven't done a whole lot with it yet, so I may still notice a difference later on.

Question, are you supposed to go into SetCPU and change any value's after doing this? I know if you want to change the actual speed you're supposed to do that in Root Explorer, but I wasn't sure about the settings in SetCPU... do I just keep the max value at 1000000? Or set it higher now?
 
Back
Top Bottom