Database Info

[HACK] (Updated 5/25/10) UNIVERSAL OVERCLOCK for ANY ROM-- Wifi Fixed Version 2.0.1

Update to the universal overclock. I've tested it working on several ROMS... seems to be better than my first one. Based off dumfuq's latest OC kernel for CM5 which is based off the latest cyanogenmod. Instructions are the same as below. Let's set some G1s on fire!
EDIT WIFI FIXED NOW
UNIVERSAL OVERCLOCK VERSION 2.01 WIFI FIXED
This can be flashed right over what you have now
EDIT IT DOES WORK ON 1.5-1.6 ROMS !!!!!
Below you'll find a link to an overclock update.zip ... all you have to do is flash it, regardless of your ROM and use set cpu to tweak your settings. It will allow you to clock the CPU up to 825mhz!!! Anything over 768mhz locks up the phone so you may want to set a max value via userinit.sh. 652mhz seems to be stable for me
WARNING: Overclocking can shorten battery life and kill the PROC on your phone. I'm in no way responsible for your phone getting hotter than the sun and exploding.
NANDROID BEFORE FLASHING THIS
I'm not a DEV... i just like to tinker. All I did was notice this and throw it all together--------CREDIT GOES TO Dumfuq, Koush and Pershoot for making this possible
Instructions:
----------------------
INSTRUCTIONS HAVE BEEN CHANGED
*Download and install setcpu.
*Select auto detect (ensure it is set at 528mhz) make sure "set on boot" and "ondemand" are selected
*Download and flash THIS update.zip up to 652mhz Stable or this stable 576mhz overclock from Pershoot from recovery and reboot
*Go back into setcpu... hit "menu" and select autodetect again ...you'll notice you now have frequencies for up to 825mhz
*Configure min and max frequency to your liking (652mhz seems to be best for me) (you may want to set a sleep profile of 245min/245max since you won't need OC while you aren't using the device)
*Enjoy
TESTED AND WORKING ON Cyangenmod 5.0.7 / KingKlick's ERIS2G1 / ZXHero 1.5 / ZXHero 2.1 / KingKlick's Legend2G1 / NoSense 1.5 / HTC CLay's Superfast / ALL CSDI ROMS !

ive been waiting on something like this thanxxxxxx
but installation aborted it said something like E: kernal

mccurt29 said:
ive been waiting on something like this thanxxxxxx
but installation aborted it said something like E: kernal
Click to expand...
Click to collapse
What ROM are you flashing this on top of?

Agreed, the zip isn't signed correctly. Here's a working version.
Might want to thank Koush and Pershoot for the kernel script too.

This sounds awesome, it could make many sense roms much more usable as a daily!! Will flash and test later tonight when I get home from work. Thanks!

carl2990 said:
i get
E: Wrong digest:
Kernal/zImage
E:Verification failed
using cannon v2.0
Click to expand...
Click to collapse
Sorry for the confusion I did not sign the zip properly. SHOULD BE WORKING NOW.

Would you be willing to talk about how this works and how it can work on any Rom. I would be interested in knowing that.
EDIT ... Actually I found some info in the overclock thread. Thanks.

billquinn1 said:
Would you be willing to talk about how this works and how it can work on any Rom. I would be interested in knowing that.
Click to expand...
Click to collapse
Uses Anykernel.zip created by Koush
updater-script runs and extract the boot.img from your current ROM.
It unpacks the boot.img into kernel and ramdisk.
It repacks newboot.img with the new kernel and the same ramdisk.
It flashes the newly created boot image.
I got the source HERE

infinitybiff said:
Uses Anykernel.zip created by Koush
updater-script runs and extract the boot.img from your current ROM.
It unpacks the boot.img into kernel and ramdisk.
It repacks newboot.img with the new kernel and the same ramdisk.
It flashes the newly created boot image.
I got the source HERE
Click to expand...
Click to collapse
This is very clever. Thanks.

0o koush's anykernel from github nice thinking

sunsean said:
This sounds awesome, it could make many sense roms much more usable as a daily!! Will flash and test later tonight when I get home from work. Thanks!
Click to expand...
Click to collapse
makes Eris2G1 fly!!!!!!!!!!

So if I'm reading this right, your using koush's anykernal method (which pershoot uses on his kernals) with dumfuq's patch. Good ****.
You might want to let people that dumfuqs kernal defaults to 8xx at boot, so a lot of people won't boot if they don't set default boot after flashing. This can be done with userinit.sh or in /system/banner or something like that if u don't have an ext partation w/userinit.sh. its explaind how to push the line in other theard. Id copy and paste here, but I'm driving right now, lol.
You also might want to give pershoot xtra kernal a shot also. It maxes at 576, but also has other optimasations included and if stable on all g1's.

fastludeh22 said:
So if I'm reading this right, your using koush's anykernal method (which pershoot uses on his kernals) with dumfuq's patch. Good ****.
You might want to let people that dumfuqs kernal defaults to 8xx at boot, so a lot of people won't boot if they don't set default boot after flashing. This can be done with userinit.sh or in /system/banner or something like that if u don't have an ext partation w/userinit.sh. its explaind how to push the line in other theard. Id copy and paste here, but I'm driving right now, lol.
You also might want to give pershoot xtra kernal a shot also. It maxes at 576, but also has other optimasations included and if stable on all g1's.
Click to expand...
Click to collapse
Thanks for the heads up. I've edited the instructions to install set cpu first so when they flash the update it will still boot up at 528 and they can change accordingly

Can we use an alternative other than SetCPU?

flexnix said:
Can we use an alternative other than SetCPU?
Click to expand...
Click to collapse
I'm pretty sure you can set the max speed via userinit.sh.... something like
"#!/system/bin/sh
echo 633600 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq"

in other news i just got this to work on a 1.5 sense ROM!!!!!!

Thanks, I'm about to test this out

Thanks bro!

Does anyone know if I can just flash this ota with just my phone? I downloaded the zip ota, and astro shows that it's on my sd card, but when I go to recovery to flash zip, it's not showing up...?
Just impatient to try this cuz it sounds sweet, lol, but I know if I can't do it ota I can do it later tonight at home...

sunsean said:
Does anyone know if I can just flash this ota with just my phone? I downloaded the zip ota, and astro shows that it's on my sd card, but when I go to recovery to flash zip, it's not showing up...?
Just impatient to try this cuz it sounds sweet, lol, but I know if I can't do it ota I can do it later tonight at home...
Click to expand...
Click to collapse
move the file to the root of your sdcard if you downloaded OTA its probably in sdcard/downloads or something

[Q]Android Revolution HD - Is this ROM really for Asus EeePad Transformer TF101 ?

Hi
I have been reading the "Android Revolution HD™ 1.2.1 | High Quality & Performance | O/C | Legendary" by mike1986.
I have even tried it on my Asus Transformer - and everything seems to be working Ok - but in the first message and the related FAQ for this ROM there are repeated mentions of 'Phone'.
But Asus Transformer TF101 is NOT a phone - and there is mention of HTC as well - am I missing something major here? Is this ROM really for Asus EeePad Transformer TF101 ?

Maybe because he copy/pasted from his other threads where he has phone roms. There is not source so everyone is tweaking the same asus rom.

[Q]Revolution HD and/or Clemsyn Kernel?
I am new to this forum though not new to Android.
I am a Embedded Linux developer actually so I am a bit embarrassed to ask the following question:
Having rooted my Asus TF, I installed this Android Revolution HD - ROM.
But now I understand that to be able to connect my TF using its HDMI port to my Panasonic TV, I should use the kernel from "Clemsyn-Blades-CPAjuste-supercurio OC kernel for 3.2 elite ver 18"
I have read pages and pages of messages of the thread in Dev threads but I am unable to understand how to use this kernel.
Do I overwrite the Revolution HD ROM with what is available as Clemsyn kernel in that thread or do I need to do something more?
I also read that if one is using certain ROMs then some modifications are required to some files in '/system' directory etc.
So I am a bit confused.
What I am looking for is a TF that is rooted and can connect over the HDMI to my Panasonic LCD TV - and presently I used BRK's method to root it and then installed the Revolution HD ROM.
What is my next step please? Please help.

download the kernal and put it onto your microsd card then just flash it using cwm in the recovery menu.
you need to use install zip from sd card option not update zip.
if it doesnt work just reflash the stock kernal or rom.

vlbaindoor said:
I am new to this forum though not new to Android.
I am a Embedded Linux developer actually so I am a bit embarrassed to ask the following question:
Having rooted my Asus TF, I installed this Android Revolution HD - ROM.
But now I understand that to be able to connect my TF using its HDMI port to my Panasonic TV, I should use the kernel from "Clemsyn-Blades-CPAjuste-supercurio OC kernel for 3.2 elite ver 18"
I have read pages and pages of messages of the thread in Dev threads but I am unable to understand how to use this kernel.
Do I overwrite the Revolution HD ROM with what is available as Clemsyn kernel in that thread or do I need to do something more?
I also read that if one is using certain ROMs then some modifications are required to some files in '/system' directory etc.
So I am a bit confused.
What I am looking for is a TF that is rooted and can connect over the HDMI to my Panasonic LCD TV - and presently I used BRK's method to root it and then installed the Revolution HD ROM.
What is my next step please? Please help.
Click to expand...
Click to collapse
To use the Cleysyn kernel just pick the one you want. Say 18b since you probably don't want voodoo support. Download it and put it on your SD card. Then using Clockwork Recovery flash it just like you did the rom. The rom and kernel are 2 different things and flashing the kernel by itself will not remove RevHD rom.
The reason you need the Clemsyn kernel is because he uses the latest nvidia code which has better hdmi support. Also you an overclock the SOC if you want with this rom but it is optional.
If you don't have roaches Clockwork mod installed you may want to consider it.
EDIT: salbalboa beat me too it.

salbalboa said:
download the kernal and put it onto your microsd card then just flash it using cwm in the recovery menu.
you need to use install zip from sd card option not update zip.
if it doesnt work just reflash the stock kernal or rom.
Click to expand...
Click to collapse
So do you mean this Kernel alone itself would replace what was done by installation of Android Revolution HD - ROM.
Or may be I should try this "Revolver 3.2 by Gnufabio [Sept 14] [HC 3.2 - 8.6.5.9] & Revolver Parts 2.7" - which I believe is a completely different ROM itself?
What do you think?
This whole confusion comes because the rest of the file system can remain same while kernel alone is changed - in a standard desktop PC scenario - but if the ROM itself represents the entire File System including the kernel - may be that is how the built in flash is written - erase all in one go and write entirely new stuff?

vlbaindoor said:
So do you mean this Kernel alone itself would replace what was done by installation of Android Revolution HD - ROM.
Or may be I should try this "Revolver 3.2 by Gnufabio [Sept 14] [HC 3.2 - 8.6.5.9] & Revolver Parts 2.7" - which I believe is a completely different ROM itself?
What do you think?
This whole confusion comes because the rest of the file system can remain same while kernel alone is changed - in a standard desktop PC scenario - but if the ROM itself represents the entire File System including the kernel - may be that is how the built in flash is written - erase all in one go and write entirely new stuff?
Click to expand...
Click to collapse
The rom and kernel are seperate in android not like desktop. Android is actually a sandboxed layer running on top of the linux core.
You can run any kernel you want with and rom you want as long as they are for the same version of Honeycomb. For instance I use Revolution HD 1.2.1 and Clemsyn's kernel 18b.
When you flash roms they include the kernel they think you should run, which is typically the stock kernel. But you can go ahead and flash over that with a new kernel whenever you want and it will not touch your files or applications.

Solved - Now using Revolver ROM and Clemsyn's kernel 18b
Bjd223 said:
The rom and kernel are seperate in android not like desktop. Android is actually a sandboxed layer running on top of the linux core.
You can run any kernel you want with and rom you want as long as they are for the same version of Honeycomb. For instance I use Revolution HD 1.2.1 and Clemsyn's kernel 18b.
When you flash roms they include the kernel they think you should run, which is typically the stock kernel. But you can go ahead and flash over that with a new kernel whenever you want and it will not touch your files or applications.
Click to expand...
Click to collapse
salbalboa said:
download the kernal and put it onto your microsd card then just flash it using cwm in the recovery menu.
you need to use install zip from sd card option not update zip.
if it doesnt work just reflash the stock kernal or rom.
Click to expand...
Click to collapse
vlbaindoor said:
So do you mean this Kernel alone itself would replace what was done by installation of Android Revolution HD - ROM.
Or may be I should try this "Revolver 3.2 by Gnufabio [Sept 14] [HC 3.2 - 8.6.5.9] & Revolver Parts 2.7" - which I believe is a completely different ROM itself?
What do you think?
This whole confusion comes because the rest of the file system can remain same while kernel alone is changed - in a standard desktop PC scenario - but if the ROM itself represents the entire File System including the kernel - may be that is how the built in flash is written - erase all in one go and write entirely new stuff?
Click to expand...
Click to collapse
Thanks salbalboa and Bjd223,
I decided to use the Revolver ROM which seemed more tailored for Asus TF and then using the Revolver Parts add on, I installed the Clemsyn's kernel 18b.
Now I am able to connect the TF over the HDMI to my Panasonic LCD TV and it all seems to work - but while HDMI is connected I found that the Wi-Fi connection dropped.
This is a different problem and probably needs looking into seperately.

ICS will load with 1.1 bootloader

for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.

Possible other solution.
I had the same experience. Installed ICS bootloader 1.2 just fine. Then couldn't download any apps from anywhere. Went back and researched some more, downloaded 3DGtab-GAppZ- 8.3.zip, installed it the same way as ICS and everything fixed itself. Been using ICS for several weeks. Never going back! :good:

I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?

jjewell said:
for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.
Click to expand...
Click to collapse
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
Dymondy2k said:
I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?
Click to expand...
Click to collapse
yes it was the Fr0z3n 1c3 build. it was due to a bad upload so users had a bad download, but it has been fixed

Jamcar.. It seems to be running great for me now.. much faster speeds in both wi-fi and opening apps...

jamcar said:
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
Click to expand...
Click to collapse
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.

rajeevvp said:
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.
Click to expand...
Click to collapse
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?

jamcar said:
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?
Click to expand...
Click to collapse
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.

I used gtab.nvflash.1.2.branch.20110508 with cwmv3028 To go to BL 1.2 and then flashed G_Harmony_ICSv1.5(120)(SuperCharged)
It went smooth, works great, and I am very happy with my GTAB

rajeevvp said:
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.
Click to expand...
Click to collapse
For cm9 I'm honestly not 100% sure, but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Sent from my SPH-D710 using xda app-developers app

jamcar said:
... but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Click to expand...
Click to collapse
Check this again: Official CM7 installs just fine with 2.x for these 2 reasons:
1. All official CM7 releases (even the latest 7.2) come with a kernel built for a 1.1 bootloader. This means that they expect to run on a 1.1 bootloader, which, in turn, means that recovery image must also necessarily have a 1.1 kernel.
2. All the versions of CWM v3.x that I've seen on this board have a 1.2 kernel in the recovery image.
This means that if you were planning to install any of the official CM7 builds, then you would not be able to do it by using any of the CWM-v3.x versions built by roebeet--CWM-v3.x just wouldn't boot. You would need to be running one of the 2 CWM versions for a 1.1. bootloader: CWM-v2.5.1.x or CWM-4.0.1.5.
Note:
CWM >= 3.x officially dropped support for "Amend" scripting. CWM-2.5.x supports both the old "Amend" and the newer "Edify" scripting.
There are unofficial CM7 repacks and RCs which have a 1.2 kernel and so will run on the 1.2 bootloader.
You could also insert a 1.1 kernel into a 1.2-based recovery image and get more choices of CWM versions--I'm running CWM-5.5.0.4Beta15 on my 1.1 right now, for instance.
These last 2 are the exceptions rather than the rule-- but, really, there's no need for any ambiguity in any of this. The fact that ICS ROMs and CM7.x can be installed using any version of CWM >= 2.5.1.x can easily be checked.

That's interesting. Wish I knew that before I switched over to 1.2
Sent from my VS910 4G using xda premium

About installing custom ROM

Hi guys,
I've created this topic, because I have some questions, I'm new at android. I want to install a custom ROM(CyanogenMod 9.1) and want to make sure I'll do everything right. Here is the installation instructions:
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM9 ZIPs to your SDCard
- Boot into Recovery
- Flash CM9 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore data using Titanium Backup! they might cause FC's
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
1. When I go to Recovery mode, it shows "Pico CMW-Based Recovery v5.0.2" and below it shows "Pico recovery by bbs.anzhi.com Ext(2, 3, 4) support by Yannou90". Am I running proper working ClockworkMod-Recovery? I get it from this rooting tutorial.
2. Saying "Flash CM9 zip from SDCard" it means "install CM9 zip from SDCard"(because in recovery mode there is "install zip from sdcard", nothing about flashing)?
3. How can I do "DO A DATA WIPE / FACTORY RESET"? Just simply choose "wipe data/factory reset" option from recovery mode?
4. After installing CM9 ROM, will it support overclocking? Or I'll have to install another kernel? If I'll have to, then which kernel should I install?
Thanks a lot. I know, very stupid questions, but please answer them .

1 From what I understand the recovery that you have installed derives from original cmw. Do not worry it will work fine
2 Yes, it means "install zip from sd card"
3 Go to wipe data/factory reset and confirm
4 Overclocking depends on the kernel you have installed, not the rom. Usually, the default cm kernel has overclocking (however, be sure to check this by going to settings in the rom)

polimeno said:
1 From what I understand the recovery that you have installed derives from original cmw. Do not worry it will work fine
2 Yes, it means "install zip from sd card"
3 Go to wipe data/factory reset and confirm
4 Overclocking depends on the kernel you have installed, not the rom. Usually, the default cm kernel has overclocking (however, be sure to check this by going to settings in the rom)
Click to expand...
Click to collapse
Thanks. I knew that "Overclocking depends on the kernel you have installed", so kernel is in rom(isn't it?). Two more questions:
1. There was mentioned "- Don't restore data using Titanium Backup! they might cause FC's", so how can I do that anyway? Maybe use another application, so which should I use?
2. How can I backup my current ROM? So if I'll do something wrong, I'll just simply install stock ROM(which I was backuped).

All android roms have a kernel. It is a fundamental component for the operating system
1 Regarding the backup, there are two great programs: MyBackup ( https://play.google.com/store/apps/...wMiwiY29tLnJlcndhcmUuYW5kcm9pZC5NeUJhY2t1cCJd) and rom toolbox (https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=it)
2 You can do a nandroid backup from recovery ("backup and restore")

Thanks. I need fast reply, which Gapps should I download from there? The one with version "CyanogenMod 9.0.x"? I don't know, because I'm going to install 9.1 version, but there isn't 9.1 version.
EDIT: found a topic, downloaded a CyanogenMod 9.0.x version...

Both cm9 and cm9.1 are based on the same system version (4.0.4) so the gapps for 9.0 will work fine on 9.1

polimeno said:
Both cm9 and cm9.1 are based on the same system version (4.0.4) so the gapps for 9.0 will work fine on 9.1
Click to expand...
Click to collapse
Thanks, but I've found solution. I think the last question, I've successfully installed CM9 ROM and I want to overclock CPU. Using the original kernel, max clock speed is 600Mhz(I'm using setCPU), so it looks like default CM9 kernel doesn't support overclocking. There is two kernels, which support overclocking(first, second). So which one should I choose(I think Cranium Kernel will be better decision)? And how can I know what will be max clock speed on Cranium Kernel?
And does
High undervolting- 600 Mhz now runs @ the same voltage as 480 Mhz,480 Mhz-> 500 Mhz @same voltage, 320 Mhz->340 Mhz @same voltage --> Better performance with better battery!
Click to expand...
Click to collapse
means, that if I'll make the clock speed lower, it won't save battery?
Thanks. I know, stupid questions...

The second one is for Gingerbread Sense Rom, you should install the first one
---------- Post added at 10:21 PM ---------- Previous post was at 09:55 PM ----------
If you have problem with the kernel, reflash the rom and gapps without make wipe

Okay, I want to install this kernel, but I don't really understand the instructions(there is something about clean-update.zip, then something about zImage.7z, modules.7z and etc). Can someone post the instructions, that should I use(I mean like "1. do that thing 2. do another thing")? These instructions are very complicated .
Thanks.
EDIT: Cranium Kernel says "Based on Htc French(telefonica) sources-Will work on all roms", so it meant to all GB ROMS, nothing about ICS?

zgintasz said:
Okay, I want to install this kernel, but I don't really understand the instructions(there is something about clean-update.zip, then something about zImage.7z, modules.7z and etc). Can someone post the instructions, that should I use(I mean like "1. do that thing 2. do another thing")? These instructions are very complicated .
Thanks.
EDIT: Cranium Kernel says "Based on Htc French(telefonica) sources-Will work on all roms", so it meant to all GB ROMS, nothing about ICS?
Click to expand...
Click to collapse
Those additional informations are for developers, ignore them. Normally install the kernel from recovery (after cleaning the cache and the Dalvik cache)
and restarts device. If you have problem just reflash rom

polimeno said:
Those additional informations are for developers, ignore them. Normally install the kernel from recovery (after cleaning the cache and the Dalvik cache)
and restarts device. If you have problem just reflash rom
Click to expand...
Click to collapse
Thanks, so which file should I download(there are 5)? And what about the edited part("EDIT: Cranium Kernel says "Based on Htc French(telefonica) sources-Will work on all roms", so it meant to all GB ROMS, nothing about ICS?")?

I had a look at the kernel thread .. It does not seem stable, many users have had problems with reboots. I would recommend you not to install it, maybe wait for it to update
About the cranium kernel, it only works with Gingerbread
---------- Post added at 02:39 PM ---------- Previous post was at 02:31 PM ----------
However, If you are looking for better performance, look at this thread http://forum.xda-developers.com/showthread.php?t=1924745

polimeno said:
I had a look at the kernel thread .. It does not seem stable, many users have had problems with reboots. I would recommend you not to install it, maybe wait for it to update
About the cranium kernel, it only works with Gingerbread
---------- Post added at 02:39 PM ---------- Previous post was at 02:31 PM ----------
However, If you are looking for better performance, look at this thread http://forum.xda-developers.com/showthread.php?t=1924745
Click to expand...
Click to collapse
Maybe I should try this kernel, but if something will be wrong, I'll restore previous(using method which you said)? You said, that I won't need to use wipe data/factory reset, so I won't loose any data, no risk(isn't it?). If you agree, say which file I should download.

You should download the file named "zImage.7z". Yes, the reinstallation of rom will overwrite the stock kernel of cm9

Hm, when I try to install zImage.7z, it's like "invisible", I've put that file in sdcard, but when I click "choose zip from sdcard" and browsing, I can't see it. Looks like it doesn't read that file. So what should I do?
By the way, did I understood your instructions correctly?
1. Wipe cache partition(didn't do it yet)
2. Advanced -> Wipe Dalvik Cache(didn't do it yet)
3. Install zip from sdcard -> choose zip from sdcard -> zImage.7z

Why did you try to do that read the instructions
Download the revised versioned build.prop
Rename it as build.prop
& Now follow the same instruction as you did for the last one
Download the build.prop
Open es file explorer>tab on favourites > "/">system
Den replace the build.prop (Yeah u need to overwrite )
REBOOT(IMPORTANT)
Done!

shortyoko said:
Why did you try to do that read the instructions
Download the revised versioned build.prop
Rename it as build.prop
& Now follow the same instruction as you did for the last one
Download the build.prop
Open es file explorer>tab on favourites > "/">system
Den replace the build.prop (Yeah u need to overwrite )
REBOOT(IMPORTANT)
Done!
Click to expand...
Click to collapse
How is it related with the Yannou90 kernel? build.prop wasn't mentioned in the instructions.

I get messed up becose of a previous link in the thread sorry, here's the kernel http://www.mediafire.com/?6v87qg0xdamxttp . Sorry again
Oooops again, when flashing just mount /system and /data, only one was required but i forgot which one, anyway there are no issues if you mount both.

shortyoko said:
I get messed up becose of a previous link in the thread sorry, here's the kernel http://www.mediafire.com/?6v87qg0xdamxttp . Sorry again
Oooops again, when flashing just mount /system and /data, only one was required but i forgot which one, anyway there are no issues if you mount both.
Click to expand...
Click to collapse
Thanks, can someone tell full instructions? Little bit confused now .

EASY WAY to Install alternative kernel w/ TWRP Touch-based Recovery

Just wanted to share this for those not in the know - mostly noobs like me.
With the exception of Alliance ROM, practically all custom JB Roms here are using Philz kernel with Philz's CWM Touch Recovery. There is of course Speedmod kernel but without the Touch recovery interface. If you are having issues with any of the above kernels and/or recoveries, maybe you would like to try Robbie's awesome AllianceROM but if you prefer to use another ROM or are using your own custom ROM like I do and would like to try Alliance custom kernel with TWRP recovery - also touch-based interface like Philz's kernels - without having to download the whole AllianceROM and extract the kernel zimage file and trying to figure out how to flash it, then the easiest way to get and flash/install it is:
Requires a rooted TW JB 4.1.2 ROM:
1. Install ROM Customizer app from Play Store
2. Run Rom Customizer and grant superuser/root permissions.
3. Click on "Browse OTA Content" and there you will see the kernel, modems and various bootanimations compatible for most JB 4.1.2 TW Roms. (I tried it with LSZ, LSC, LM5, LSF & LSE and it works great.)
4. Just browse thru the kernel category, choose "Alliance-XXLSZ" and click start to download.
5. After download, click the disk button/icon at the top right corner
6. then on the next page click on the arrow button/icon at the top right corner and it will ask you to flash
7. just click YES and it will install the kernel with TWRP recovery
8. after install, app will ask to reboot, just click reboot and you are done.
9. To check how TWRP looks like and if it was installed, just boot into Recovery mode using Rom Customizer or via Extended Power Menu.
10. Enjoy a so far no-bootloop (for me) with great a very simple touch interface recovery.
11. You can always go back to Philz or speedmod kernels/recovery if you want by flashing their respective files.
BIG THANKS to ficeto.

I think xperiacle addresses some moot issues specially in connection with our Touchwiz JB experiences and shows us alternatives.
Stay Hungry. Stay foolish as always

yep stay hungry stay foolish
good going..
by the way anyone can give me a method for reverse of the same..
i mean kernel with TWRP change to same kernel with CWM, with touch options like slim bean 2.5 in note if possible.
sorry for the troll question but since it relates to me, i asked.
regards