1. 2015 is going to be a great year for Android! Why wait??
    Samsung Galaxy Note 5 | Samsung Galaxy S6 | HTC One M9
  2. New Forum Created: Samsung Gear VR!

[How-to] Overclock that survives a reboot


  1. D13

    D13 Well-Known Member

    Warning, this process may cause our phone to become unstable if you clock it at the wrong speed. I advise that you do not continue onto steps 2 and 3 until you find the settings that work for YOUR phone best.

    All credit goes to Fab for his how-to post, Elkay for the original mod of the milestone overclock and to Hilbe for his install-recovery.sh and setscaling.sh files as well as figuring out where to add on these commands. And also Airmaxx23 for helping me refine the commands. As well as FreeWELL for his Root Explorer guide and his stop overclocking commands

    I am not responsible for anything that happens to your phone.

    First, things first download the attachment at the bottom of this post
    Now on to how to overclock that survives a reboot,
    1. First follow Fabolous's guide to overclocking,
    http://androidforums.com/all-things-root-droid-x/145209-how-overclock-your-droid-x.html
    Here is his OP, also the overclock.ko and overclock.sh files are both in the attached Zip file at the bottom.
    2. Next put the setscaling.sh file and the install-recovery.sh into your tools folder or where ever your adb.exe is located, then open up cmd and point it at that folder.

    3.In adb run
    -"adb push setscaling.sh /sdcard"
    -"adb push install-recovery.sh /sdcard"
    -"adb shell"
    -"su"
    -"mount -o remount,rw -t yaffs2 /dev/mtd/mtdblock4 /system"
    -"cp /sdcard/setscaling.sh /system/bin"
    -"chmod 755 /system/bin"
    -"cp /sdcard/install-recovery.sh /system/etc"
    -"mount -o ro,remount -t yaffs2 /dev/mtd/mtdblock4 /system"

    The whole thing can also be done with Root explorer, credit to FreeWELL for the guide

    1. Download file "Survive the boot.zip"
    2. Fire up Root Explorer
    3. Navigate to /sdcard/downloads
    4. Long press on "Survive the boot.zip" and select Extract All
    5. Navigate to /sdcard/extracted/Survive the boot/
    6. Long press on install-recovery.sh and select Copy
    7. Navigate to /system/etc
    8. Hit the Mount R/W button
    9. Hit Paste
    10. Hit the Mount R/O button
    11. Navigate back to /sdcard/extracted/Survive the boot/
    12. Long press on "overclock.ko" and select Copy
    13. Navigate to /system/lib/modules (all the way at the end of ../lib)
    14. Mount R/W
    15. Hit Paste
    16. Mount R/O
    17. Navigate to /sdcard/extracted/Survive the boot/
    18. Hit the Menu botton and choose Multi-select
    19. Select "overclock.sh" & "setscaling.sh" (green check mark)
    20. Hit "copy"
    21. Navigate to /system/bin
    22. Mount R/W
    *23. **Think about what you're doing!!!* You are now at the end of the road. My X will not run stable with the "setscaling.sh" as supplied... my X does run well set to 400@23/700@28/900@33/1100@40... I don't think 1150@34 is stable for everyone... 1100@40 should be... i also think 400/700 is more useful than 300/600 when creating profiles with SetCPU...

    24. Hit "Paste" because your setscaling.sh is edited with settings that are stable for your X and you know because you thoroughly testified this before editing/copying install-recovery.sh to overclock at boot...
    25. Mount R/O


    Also to disable overclocking, credit to FreeWELL

    Disabling Overclock at Boot with Root Explorer:
    1. Open Root Explorer
    2. Navigate to /system/etc
    3. Mount R/W
    4. Long press on "install-recovery.sh"
    4. Select Rename
    5. Change to "install-recovery.oc" or whatever works for you, and then hit Ok
    6. You can now Mount R/O or continue messing around with editing you setscaling.sh file

    Command Line Stop boot overclock:
    $ su
    # mount -o rw,remount -t yaffs2 /dev/mtd/mtdblock4 /system
    # cd /system/etc
    # mv install-recovery.sh install-recovery.oc
    # mount -o ro,remount -t yaffs2 /dev/mtd/mtdblock4 /system

    And to re-enable overclocking:
    With RE just change the name back to install-recovery.sh
    With Cmd
    $ su
    # mount -o rw,remount -t yaffs2 /dev/mtd/mtdblock4 /system
    # cd /system/etc
    # mv install-recovery.oc install-recovery.sh
    # mount -o ro,remount -t yaffs2 /dev/mtd/mtdblock4 /system



    Thats it, let me know if it works and to check if it worked try rebooting your phone.

    Attached Files:


    Advertisement
    :
  2. Paycer

    Paycer Well-Known Member

    What if we're on the fly, aren't near a computer terminal, and want to use SetCPU or something similar instead? Is there a way for us to do everything from the phone, or not?

    Sorry. I'm not quite this technologically adept when it comes to electronics, especially something this new to me, but I just had to ask. I usually just follow the instructions that are written and given and try to learn from them as best as I can.

    Thanks for writing this up though. I'll probably try it when my phone arrives.
  3. PJ.

    PJ. Member


    Get Better Terminal from the market. adb on the fly basically.

    Good writeup, thanks a lot.

    Just got this score at 1.15/34

    [​IMG]

    Battery at 40 percent, after watching Transformers 2 at full brightness and light sms/emailing.
  4. Paycer

    Paycer Well-Known Member

    Yeah I suppose I can use the mobile terminal emulator. I don't know why I didn't realize that. Though, I was thinking more along the lines of a user-friendly way to accomplish the same results. I realize that if someone doesn't know how to do each step manually, then maybe they shouldn't be messing with the clock speeds and voltages, but still. Sometimes user-friendly methods are a way for those of us who know what we're doing to just be lazy. :D
  5. Airmaxx23

    Airmaxx23 Well-Known Member

    So what would the commands be to undo this? I want to do some more tinkering without it.
  6. D13

    D13 Well-Known Member

    I think if you deleted all the files that we pushed
    overclock.sh
    overclock.ko
    install-recovery.sh
    setscaling.sh

    You should be good.
  7. Airmaxx23

    Airmaxx23 Well-Known Member


    Yes that worked and I did the whole install process again and everything works fine.
  8. Hilbe

    Hilbe Well-Known Member

    Good writeup.
  9. LexusBrian400

    LexusBrian400 Well-Known Member

    Worked great for me. Thank you guys for the work and write up :) Much appreciated.
  10. FreeWELL

    FreeWELL Well-Known Member

    *warning* proceeding could be potentially very hazardous to you X

    1. Download file "Survive the boot.zip"
    2. Fire up Root Explorer
    3. Navigate to /sdcard/downloads
    4. Long press on "Survive the boot.zip" and select Extract All
    5. Navigate to /sdcard/extracted/Survive the boot/
    6. Long press on install-recovery.sh and select Copy
    7. Navigate to /system/etc
    8. Hit the Mount R/W button
    9. Hit Paste
    10. Hit the Mount R/O button
    11. Navigate back to /sdcard/extracted/Survive the boot/
    12. Long press on "overclock.ko" and select Copy
    13. Navigate to /system/lib/modules (all the way at the end of ../lib)
    14. Mount R/W
    15. Hit Paste
    16. Mount R/O
    17. Navigate to /sdcard/extracted/Survive the boot/
    18. Hit the Menu botton and choose Multi-select
    19. Select "overclock.sh" & "setscaling.sh" (green check mark)
    20. Hit "copy"
    21. Navigate to /system/bin
    22. Mount R/W
    *23. **Think about what you're doing!!!* You are now at the end of the road. My X will not run stable with the "setscaling.sh" as supplied... my X does run well set to 400@23/700@28/900@33/1100@40... I don't think 1150@34 is stable for everyone... 1100@40 should be... i also think 400/700 is more useful than 300/600 when creating profiles with SetCPU...

    24. !!!MULTIPLE CHOICE!!!
    a. Realize you don't know what the he'll you're doing and "Cancel"
    b. Realize that if you just hit Paste now, you will like cause your X to run at boot with settings that are unstable. Hit "Cancel"
    c. Hit "Paste" because your setscaling.sh is edited with settings that are stable for your X and you know because you thoroughly testified this before editing/copying install-recovery.sh to overclock at boot...
    25. Mount R/O
    D13 likes this.
  11. PJ.

    PJ. Member

    Yeah, I had to edit the setscaling.sh file as well. I was getting reboots during video playback and every time I received a text message over 1 page.

    Checking it out at 1.1/34 now.

    Bam!

    [​IMG]
  12. FreeWELL

    FreeWELL Well-Known Member

    mv /system/etc/install-recovery.sh /system/etc/install-recovery.oc
  13. bosox2k1

    bosox2k1 Well-Known Member

    Awesome, used the set scaling script and worked great. Don't want to shut it off now!
  14. bosox2k1

    bosox2k1 Well-Known Member

    OK, I am getting some issues.

    I am in debugging mode and Mass storage setting.

    I follow steps 2 and 3 in the OP as stated and get no errors while issuing them thru ADB.

    I reboot, but none of the settings stick. So I check my sdcard (while unplugged) and the install and setscale docs are not in there.

    I plug back in to the computer (debu/mass storage) and I look on astro and boom! the install and setscale docs are on the sdcard now, but disappear when I disconnect from computer.

    I am doing something wrong, obviously, but I don't know how to make it stick to the sdcard after I unplug from computer....
  15. itsTee

    itsTee Well-Known Member

    man i keep getting reboots, anyway to fix this?
  16. PJ.

    PJ. Member


    Remove the setscaling.sh file. You're going to have to find the settings correct for you. I would reboot at 1.15/34, so i changed it to 1.1/34 in the setscaling file and im running GREAT now.
  17. D13

    D13 Well-Known Member

    When do the reboots happen? You can easily edit the setscaling.sh to lower the clock speed and change the voltages. Do you have Root explorer?
  18. D13

    D13 Well-Known Member

    Actually you can it survives a reboot.:D
  19. D13

    D13 Well-Known Member

    I think this could be helpful to alot of people, do you mind if I add it to the OP?
  20. bosox2k1

    bosox2k1 Well-Known Member

    If anyone could help me with my problem (post #14 in this thread), I would really appreciate it. I am at a loss.
  21. Airmaxx23

    Airmaxx23 Well-Known Member

    I had to do all of it in charge only mode. You may want to try that.
  22. bosox2k1

    bosox2k1 Well-Known Member

    Thanks Airmaxx, will try tonight after work.
  23. Retrokid223

    Retrokid223 Well-Known Member

    well now my phone is stuck at the M symbol :( thank god for that spf
    EDIT:NVM fixed it
  24. mazz0310

    mazz0310 Well-Known Member

    Is this after a successful copy all files and what not, or during?
  25. FreeWELL

    FreeWELL Well-Known Member

    Droider13: I don't mind. Just add the filollowing as well...

    Disabling Overclock at Boot with Root Explorer:
    1. Open Root Explorer
    2. Navigate to /system/etc
    3. Mount R/W
    4. Long press on "install-recovery.sh"
    4. Select Rename
    5. Change to "install-recovery.oc" or whatever works for you, and then hit Ok
    6. You can now Mount R/O or continue messing around with editing you setscaling.sh file

    Command Line Stop boot overclock:
    $ su
    # mount -o rw,remount -t yaffs2 /dev/mtd/mtdblock4 /system
    # cd /system/etc
    # mv install-recovery.sh install-recovery.oc
    # mount -o ro,remount -t yaffs2 /dev/mtd/mtdblock4 /system
    D13 likes this.
Loading...

Share This Page