Phhusson (Toastcfh) Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Search This thread

Sik-1

Senior Member
Oct 28, 2009
1,429
553
Brooklyn
I think there were some MAJOR kernel changes by zinx to fix the battery issue, so I think your probably experiencing a placebo effect

sorry no placebo ova here buddy, still getting my same 4.1 linpack, SINCE I INSTALLED TEST2 AT 50% 3 hours ago, ive been surfing and making calles and im only down to 39% at i write this, so go figure, o yea stock battery:D since i bout my g1 about a year and some change ago
 

zimphishmonger

Senior Member
Jun 4, 2009
3,890
729
sorry no placebo ova here buddy, still getting my same 4.1 linpack, SINCE I INSTALLED TEST2 AT 50% 3 hours ago, ive been surfing and making calles and im only down to 39% at i write this, so go figure, o yea stock battery:D since i bout my g1 about a year and some change ago

Glad to hear it, guess some things were changes elsewhere as well.

I'm personally still waiting for the test2 recompile :D
 

dumfuq

Retired Recognized Developer
May 23, 2009
542
42
same as last kernel i posted except updated the source for test2.

Just like my last one, this kernel defaults to 672 so you better set it in userinit.sh if you want it to boot unless your one of the lucky ones.

oc-cm-5.0.7-test2-boot.img
 

ceas909

Senior Member
Oct 8, 2009
310
2
Re: ToAsTcfh Overclock Kernel Patch

same as last kernel i posted except updated the source for test2.

Just like my last one, this kernel defaults to 672 so you better set it in userinit.sh if you want it to boot unless your one of the lucky ones.

oc-cm-5.0.7-test2-boot.img

so if this is cm latest git source... i take it supports mt3g fender/1.2?

update: i can confirm it supports mt3g 1.2/fender


Sent from my HTC Magic using the XDA mobile application powered by Tapatalk
 

Mumps

Senior Member
Aug 10, 2009
141
3
Toledo
same as last kernel i posted except updated the source for test2.

Just like my last one, this kernel defaults to 672 so you better set it in userinit.sh if you want it to boot unless your one of the lucky ones.

oc-cm-5.0.7-test2-boot.img
//EDIT: Now I see, oc-cm-5.0.7-test2-boot.img would be the image for the Kernel 2.6.33.3 – OC-FP – Dream/Sapphire (32B) and not the JIT – CM5.0.7-T1 – Dream/Sapphire, right? I leave the original post just in case:

Tried this with fastboot boot, OC Hack runs fine, but JIT is not working, doing a dalvikvm -h, extracted from the says:

Configured with: debugger profiler hprof show_exception=1

But no metion to "with_jit". Also Linpack scores are still ~2.6.

It also says "Unrecognized option '-h'"

Any ideas? Could it be because I'm running it through fastboot? Thanks in advance.
 
Last edited:

infinitybiff

Senior Member
Jan 27, 2010
467
201
fromhindsight.com
same as last kernel i posted except updated the source for test2.

Just like my last one, this kernel defaults to 672 so you better set it in userinit.sh if you want it to boot unless your one of the lucky ones.

oc-cm-5.0.7-test2-boot.img

THANKS! also hosting on my server. I've bundled in a userinit.sh in the zip that sets max to 633mhz . You will need to adb push these to your device if don't know that already. Instructions are posted on my blog.:D

http://fromhindsight.com/crap/ocboot_test2.zip

EDIT: you need to kill all tasks that you can or you will get out of memory errors when flashing ocboot.img
 
Last edited:

zender2k

Senior Member
Sep 12, 2007
106
7
Runs very smooth @ 672mhz:) Drains the battery like a mofo though.
 
Last edited:

Mumps

Senior Member
Aug 10, 2009
141
3
Toledo
While I wait for all the issues with test2 to be solved, I'm using test1 with JIT – CM5.0.7-T1 – Dream/Sapphire.

JIT is running, but the OC won't work somehow. Flashed the zip over test1 without wipe, but SetCPU won't go past 528, even with setcpu.txt on the sdcard root with values up to 614400 and 633000.

So now I can either choose between test1 with JIT and test2 with OC... any idea when will be available the JIT – CM5.0.7- T2?

Thanks for all your work!
 

infinitybiff

Senior Member
Jan 27, 2010
467
201
fromhindsight.com
While I wait for all the issues with test2 to be solved, I'm using test1 with JIT – CM5.0.7-T1 – Dream/Sapphire.

JIT is running, but the OC won't work somehow. Flashed the zip over test1 without wipe, but SetCPU won't go past 528, even with setcpu.txt on the sdcard root with values up to 614400 and 633000.

So now I can either choose between test1 with JIT and test2 with OC... any idea when will be available the JIT – CM5.0.7- T2?

Thanks for all your work!

I have JIT running with OC on test 2. ..... Flash test 2.. then flash the OCboot.img and userinit http://fromhindsight.com/crap/ocboot_test2.zip following the instructions from http://fromhindsight.com/?p=329... then flash JIT... tested working and stable on my g1.... getting 4.1ish on linpack

EDIT, for test1... follow the instructions and download the file from http://fromhindsight.com/?p=329
 
Last edited:

Mumps

Senior Member
Aug 10, 2009
141
3
Toledo
I have JIT running with OC on test 2. ..... Flash test 2.. then flash the OCboot.img and userinit http://fromhindsight.com/crap/ocboot_test2.zip following the instructions from http://fromhindsight.com/?p=329... then flash JIT... tested working and stable on my g1.... getting 4.1ish on linpack

EDIT, for test1... follow the instructions and download the file from http://fromhindsight.com/?p=329
Many thanks! Tried that but somehow my recovery 1.6.2G doesn't have full adb support as announced (last week a simple adb remount worked, now says "remount failed: Invalid argument").

And when I try to "flash_image boot /sdcard/ocboot.img" it says "error opening /sdcard/ocboot.img", and it's there (confirmed). Either I tried "mount -o rw,remount auto /sdcard" from recovery also says "mount: mounting auto on /sdcard failed: Invalid argument", the same without auto: "mount: mounting remount on /sdcard failed: No such file or directory" when I can perfectly do "cd sdcard and then ls" and shows ocboot.img is there.

Any ideas? because not having adb support in recovery is becoming a nightmare :D
 
Last edited:

infinitybiff

Senior Member
Jan 27, 2010
467
201
fromhindsight.com
Many thanks! Tried that but somehow recovery 1.6.2G doesn't have full adb support (last week a simple adb remount worked, now says "remount failed: Invalid argument").

And when I try to "flash_image boot /sdcard/ocboot.img" it says "error opening /sdcard/ocboot.img", and it's there (confirmed). Either I tried "mount -o rw,remount auto /sdcard" from recovery also says "mount: mounting auto on /sdcard failed: Invalid argument", the same without auto: "mount: mounting remount on /sdcard failed: No such file or directory" when I can perfectly do "cd sdcard and then ls" and shows ocboot.img is there.

Any ideas? because not having adb support in recovery is becoming a nightmare :D

You need to do it with the phone booted live. it prolly won't work from recovery. NOTE: you need to kill all running tasks that you can, or you'll get an out memory error.
 

Mumps

Senior Member
Aug 10, 2009
141
3
Toledo
Ok I booted from fastboot boot ocboot.img and it works, I'm going to flash from fastboot. I was just asking because I'd like to have full adb support inside recovery, comes in handy.

I just tried to do it from recovery because it recommended having all the apps closed, so I thougth it would be better from recovery.

I asked a friend and he can't do an adb remount from recovery, is that how it should be or am I just imagining it worked for me last week?
 

infinitybiff

Senior Member
Jan 27, 2010
467
201
fromhindsight.com
Ok I booted from fastboot boot ocboot.img and it works, I'm going to flash from fastboot. I was just asking because I'd like to have full adb support inside recovery, comes in handy.

I just tried to do it from recovery because it recommended having all the apps closed, so I thougth it would be better from recovery.

I asked a friend and he can't do an adb remount from recovery, is that how it should be or am I just imagining it worked for me last week?

I'm sure it can be done from recovery somehow or another,

"try mount -o rw /dev/block/mmcblk0p1 /sdcard ".... then you'll be able to "adb push" to /sdcard that ought to get you there. I'd follow the instructions on my blog tho, as thats how i did it successfully
 

tnpapadakos

Senior Member
Dec 20, 2009
3,053
1,103
Pittsburgh, PA
Many thanks! Tried that but somehow my recovery 1.6.2G doesn't have full adb support as announced (last week a simple adb remount worked, now says "remount failed: Invalid argument").

And when I try to "flash_image boot /sdcard/ocboot.img" it says "error opening /sdcard/ocboot.img", and it's there (confirmed). Either I tried "mount -o rw,remount auto /sdcard" from recovery also says "mount: mounting auto on /sdcard failed: Invalid argument", the same without auto: "mount: mounting remount on /sdcard failed: No such file or directory" when I can perfectly do "cd sdcard and then ls" and shows ocboot.img is there.

Any ideas? because not having adb support in recovery is becoming a nightmare :D

try dropping the "/" before "sdcard" same thing happened to me till i did that
 

Booker-T

Senior Member
Jun 12, 2009
425
9
In other post, someone says he is using a 59xmhz kernel for 5.0.7 test2.

Could someone give me a link and teach me how to apply it?
 

Mumps

Senior Member
Aug 10, 2009
141
3
Toledo
infinitybiff: mounting with your method it's now working, many many thanks :)

tnpapadakos: tried without / "mount -o rw,remount auto sdcard" > Invalid arguments, "mount -o rw,remount sdcard" > mount: can't find sdcard in /proc/mounts. Anyway thanks, the other method is working now :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Edit: It was actually coded by phhusson, in conjunction with toastcfh and others. See thread here: http://xdaforums.com/showthread.php?t=665515



    This thread is about a new overclock kernel patch for the MSM7K, which includes the G1 and Magic.

    Devs working on overclock kernels. If you want your overclock kernel in OP (here) send me a PM and I'll consider linking to it.


    For devs, the original patch is here, and an updated commit to allow for scalable frequencies is here
    There's also an autodetection patch for SetCPU by coolbho3000 himself here
    pershoot's github for the lazy: http://github.com/pershoot/ds-kernel

    Downloadable Kernels to Flash for the Rest of Us
    These kernels are not officially endorsed by Cyanogen for his ROM, so use at your own risk and do not file any bug reports to the ROM owners. pershoot has done some good things to this for Cyanogenmod including some extra frequencies to choose from.

    EBI0 version = 32B Magic or G1 on 1.x or 2.x radio
    EBI1 version = 32A Magic or G1 on 3.x radio

    2.6.33.3 for any rom EBI0/EBI1 by pershoot
    Has lots of tweaks and goes up to 576 MHz



    Verification:
    This works. Read the thread.

    Video proof of 614 MHz: http://www.youtube.com/watch?v=9Oaesb0OX8k

    FAQ:
    A) How do I try this without flashing this to my phone?
    If you want to try this without flashing your phone, download the zip file for your phone. First turn OFF wifi. Then turn your phone off.

    Now go into fastboot. Extract boot.img, probably in the same folder as your fastboot application. Then use:
    Code:
    fastboot boot boot.img
    (replace boot.img with the name of the img file)

    This will make the kernel run temporarily on your phone up till your phone is restarted again. Do NOT turn your wifi on at this time, because it will freeze your phone. If you want to keep it, flash the whole zip file from recovery. Otherwise just restart your phone and you will be back to whatever you had before.

    B) Ramhack?
    What is known as the ramhack is done by modifying the kernel source code with a patch and making a new kernel to flash. Hence you see a boot.img in the zip files you flash.

    This overclock kernel patch modifies the source code of the kernel. If you want both ramhack together with the overclock, you need a kernel that contains both the ramhack AND the overclock patch. If not explicitly stated, you can assume that the overclock patched kernel does not contain the ramhack patch and thereby does not have ramhack.

    C) What phones does this work on?
    All HTC Dream/G1 and myTouch/Magic, not including Fender or 1.2 editions of the Magic for the precompiled kernels in this thread.

    If you are applying the patch yourself it should work on any MSM7K device.

    D) What are some prerequisites I need to flash this?
    Custom recovery compatible with test keys, or root with working adb/fastboot.

    And you need a compatible phone (see C)

    E) My wifi doesn't work after I flashed x.img file!
    YOU MUST FLASH THE CORRESPONDING WIFI MODULE WHENEVER YOU FLASH THE KERNEL.

    The .img file contains the kernel, which requires a patching wifi module to be recompiled (wlan.ko located in your system volume) with that kernel.

    If wlan.ko was not provided, wifi will simply not work. Ask whoever compiled that kernel to provide a wlan.ko file for you to flash.

    F) Is this stable?
    Stability seems to vary, but at the moment I do not recommend using 614 MHz for day-to-day use.

    This kernel does not even run stable at 614 MHz right now for me, or at least when I try to just plug in my usb cable. Not sure what can be done there. I threw in the 653 MHz EBI1 kernel that wouldn't boot for me for kicks.

    My gut feeling of being unable to boot at 653 MHz and being unstable at even 614 Mhz leads me to think that the G1 is a pretty hopeless overclock. The 32B Magic might have better luck. CDMA Heros are getting up to 700 MHz easily on the other forum. It is not surprising that HTC designed the phones to have higher clock tolerances than the G1 designed to run at 384 MHz.

    (DEVS/COOKS) Original kernel patch to overclock from 528 MHz to 711 MHz, but that wouldn't boot. Boots fine at 614 MHz on my G1 with 3.x radio. Probably more stable at lower speeds.
    For all MSM7K devices including the Hero, Dream, Magic

    Credits:
    phhusson for sharing
    ToAsTcfh for coming up with it
    Cyanogen because it's his kernel source
    benbuchacher for Super D
    farmatito for EBI0 compile
    coolbho3000 for SetCPU
    pershoot for some great compiled kernels

    Notes:
    I am not a dev!

    This patch performs more changes the kernels source in acpuclock.c and involves the software modification of the way PLL is handled to allow for the overclock.

    It is different than the previous OC patch that only modified the frequency table.

    This patch adjusts the 528 MHz clock to 711 MHz, and can be modified by changing the patch file. Acceptable clocks are multipliers of TXCO (19.2MHz).

    710.4 MHz = 19.2 * 37

    Should work on 2.6.27 and 2.6.29, and maybe more.

    Some devs have already added this to their CDMA Hero ROMs with reports of success.
    1
    Yes...Compare it to 528, you arent running JIT so you dont have some crazy number. Dont be to concerned with these #'s if things are faster than you know the OC is good to go.

    thanks.. pulling 4.079 with jit now