[How-To] Wi-Fi Tether AND 600MHz! This has been confirmed working! It also fixes some automatic brightness bugs! I've added a tutorial of how to do it, as well as all the files needed. Here is another "do it all" kernel. http://www.sendspace.com/file/sz98ny Please test this first and post if it works. Thanks to CKyle22 It's recommended that you do a nandroid backup before doing this, its a good practice to get in to. Download these two .img's and flash_image from the following links. Or go to the bottom and download the .zip of all of them. Wifi kernel boot-new.img OC kernel (thanks to tasmanian_droid) boot.img Flash_Image (New mirror, mediafire was not working) http://www.megaupload.com/?d=3DKHNCD6 Place the two .img's in your sdcard root, and flash_image in /system/bin/, which is done by first putting flash_image in your /sdcard, then doing Code: adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system adb shell cat /sdcard/flash_image > /system/bin/flash_image adb shell chmod 755 /system/bin/flash_image then boot into recovery mode. From recovery mode, go to mount options and mount both /system and /sdcard, then run from adb Code: adb shell /system/bin/flash_image boot /sdcard/bootwifi.img reboot into Android, run the Wifi tether program (http://www.droidforums.net/forum/dr...d-wifi-tether-wireless-tether-root-users.html) once, then reboot back into recovery mode and run Code: adb shell /system/bin/flash_image boot /sdcard/boot.img now reboot your phone into Android, use SetCPU (http://forum.xda-developers.com/showthread.php?t=505419 or in Market as donate version for $.99) to overclock your CPU to 600MHz, and reboot into recovery mode again, go to mount options and mount both /system and /sdcard, now execute through adb Code: adb shell /system/bin/flash_image boot /sdcard/bootwifi.img reboot again and you have both wifi tethering, a working wifi card, and 600MHz!! EDIT: I've ran benchmarks, as well as had SetCPU read the CPU freq, it's definitely running at 600MHz!! I can also scale it down to 500MHz and then back up to 600MHz, so it doesn't need to stay at 600MHz to keep this strange "glitch" applied.