Database Develop

Install Dalingrin's OC kernel but no 1100 settings

Hi all, this is my first post here, I have just installed CM7 and it works flawlessly, but when I tried to install Dalingrin's OC kernel, everything seems installed fine, but when I go to the CM7 settings, the fastest CPU speed I can choose is 925, is there any one who experiences the same things and successfully solve the problem?
Thanks in advanced.

are you flashing with cwm 3.0.1.0 with the proper updated kernel to write to ext4 partitions?

First of all make sure that your downloading the corrent kernel the one for CM7.
Also, did you wipe your cache partition and clearn your dalvik cache?
If not then reflash.
*edit* Im sure you have it but here is the corrent link for froyo and cm7 builds: http://nook.handhelds.ru/dalingrin/kernels/

Hi, thank you for the replys, much appreciated!
Unfortunately, I redo the whole things again and pay extra attention to the things you mentioned, but it still didn't work.
I used CWMR 3.01 to remove cache partition and dalvik cache, although nook hangs after cleaning up dalvik cache, I force power off nook and reenter CWMR and install the Dalingrin kernel again, I did check the kernel version, SD/CM7...
No luck..
Any other thoughts?

The problem you describe is indicative of flashing the wrong kernel. If CM7 is installed on the internal memory, then you need the EMMC version of the kernel. Please confirm that this is what you are doing.

Thank you, you are right, I am using the wrong kernel, sorry for the stupidity, I follow several install guide, but I have no idea what I need is the emmc one.
Thanks.

cm7.0.2 to nightly 64 crash

Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim

Jimbo67 said:
Hey guys-
I just tried to update from cm7.0.2 emmc stable to the nightly 64, and after flashing it and rebooting my nc is locked. It boots to the word android on the left top side and the it goes to dark screen! I hope someone can help me!
Thanks In Advance,
Jim
Click to expand...
Click to collapse
Jim,
This question's been answered in other threads already, but here's the link to the one specifically regarding this problem. I included it in your response to this question on the other thread as well. Good luck....
http://forum.xda-developers.com/showthread.php?t=1068309

What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?

Jimbo67 said:
What a disaster!!! I am Bricked! I wish now, that I had Never left 7.0.2.
I cant even boot into CWR!
Any Ideas?
Click to expand...
Click to collapse
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.

First things first..... Don't panic. LOL
1. Power down.
2. Power up holding both the power button & the n button for 6 seconds.
Does that get you to recovery?

hockeyfamily737 said:
You're NOT bricked...... The Nook gives boot priority to your sd drive. Worst case scenario, you need to use a bootable recovery sd to reflash a stable version of CM7.
Click to expand...
Click to collapse
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!

Jimbo67 said:
I just put a new 3.0.2.8 .img file on my sd card should I put it in and see if it boots into CWR from the card? If it does, before I flash 7.0.2, what should I format? Just the cache?
Thanks!
Click to expand...
Click to collapse
First try booting into your EMMC recovery the way I just posted ( power & n button for 6 seconds).

If that works.... do a full wipe and restore your backup of 7.0.2 stable.

It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!

Jimbo67 said:
It won't boot into recovery with the power and N button. Tried it many times! I still get the android for a few, and then a small dot in the upper right!
Click to expand...
Click to collapse
Ok.....Now it's time to use your recover SD. Put it in, boot to recover and do a full wipe (System, Data, Cache, & Dalvik). Then reflash CM7.0.2. When you're done and booted into CM7, report back for follow up instructions, so this doesn't happen to you again.

Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!

Jimbo67 said:
Man, I got all the way to wipe dalvik cache and it locked up on the advanced and debugging menu??? oh my god!
Click to expand...
Click to collapse
Yeah that's perfectly normal. Hard shutdown and boot right back to recovery. Flash the rom and gapps (no OC kernel yet....I'll explain once you're up and running again).

Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!

Jimbo67 said:
Whew! I am back up on cm7.0.2! Seems that the nightly 64 and the 0424 OC kernel dont play well together!
Click to expand...
Click to collapse
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent CWM update requires the use of a kernel with an updated ext.4 script, explained in the following link.......http://forum.xda-developers.com/showthread.php?t=925451&page=239
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik) for safety's sake.
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab

just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"

Jimbo67 said:
just one more question--what is the best way to add the OC kernel to cm7.0.2 now, or should I update to 7.0.3 " Gasp"
Click to expand...
Click to collapse
I'd wait on 7.0.3 to see what's up with it..... Some people were reporting the MD5 sums not matching. Stick with 7.0.2, follow the threads to see what's up with any rom you run, and then once you know all's well (from reading the posts).....then flash the update. Keep in mind it's always easier to read first and flash after, then to freak out thinking you bricked your device and spend 2 hours in a panic trying to fix it.
For the OC kernel boot into recovery (the one you should have flashed to EMMC from Rom Manager), and flash the 4/24 kernel with the updated script for ext. 4

hockeyfamily737 said:
Make sure you go back to the market and re-download Rom Manager. Once you do that, flash recovery to your EMMC (device memory). Make sure you keep that recovery up to date. The SD recovery you just used did not flash your machine.....Your machine booted from it.
Now for your overclocking info. The recent nightly builds are Android 2.3.4 and require and ext 4 kernel..... available here in post 2382 of this thread......http://forum.xda-developers.com/showthread.php?t=925451&page=239
The stable builds are Android 2.3.3 which require the kernel you have been using right along (prob. the 4/24 1.3 GHz).
Going from stable to nightly requires only a Cache & Dalvik wipe + the flashing of the ext 4 OC kernel, however returning from nightlies to stable will require a full wipe (system, data, cache, & dalvik).
Always make back ups of good rom's, use titanium to back up your apps & data, keep your recovery up to date, read, read, read.......and if I helped you out click my thanks tab
Click to expand...
Click to collapse
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!

Jimbo67 said:
I would like to get on the Nightly band wagon, and use the ext4 OC kernel but this link does not work for me. Is there another place to get the 1.3 OC kernel that will work for nightly builds?
Thanks!
Click to expand...
Click to collapse
http://www.unvisible.org/files/ext4-...mmc-042411.zip
Here you go.

cpu stuck at 1Ghz [SOLVED]

i was using cm #8 and using profiles in setcpu and after applying Huexxx's kernel v0 setcpu shows that the device is lock at 1Ghz all the time except screen of which goes to 300mhz
and i'v noticed that the cpu uses only 2 frequencies (1000 , 300 )
so i'v flashed cm #9 with full wipe and the problem still here
i'v tried different the governor and the I/O Schedulers and nothing works
plz people ,how to fix it ?

Well,
if you install my kernel, but afterwards you make a full wipe and reflash another nightly, there wouldn't be any of my kernel in your OB.
In fact, flashing a new nightly without wipes will replace all my stuff.

Huexxx said:
Well,
if you install my kernel, but afterwards you make a full wipe and reflash another nightly, there wouldn't be any of my kernel in your OB.
In fact, flashing a new nightly without wipes will replace all my stuff.
Click to expand...
Click to collapse
thx bro i have flashed ur kernel v2 again ryt now and all frequencies work finally i think it was something wrong btw sometimes when i do full wipe and install new nightly i find my settings still the same :S
anyways ur new kernel (V2) is awesome

[GTP6800][ZSKL2] [3g] EzyKernel OC/UV + Deodex + PowerMenuMod

EzyKernel v1 - 23/02/2012
This Kernel is more geared towards functionality & real life user experience as opposed to benchmarks etc.
(Need to be running a ZSKL2 firmware - see installation instructions)
Update 23/02/2012 - Kernel Bluetooth fix.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Features:
1) Overclocking & Undervolting support
Added overclocking up to 1600 / 1800 mhz
Added sysfs uv interface for setcpu support.
Undervolts quite well
Set default max overclock to 1600 mhz.
1800 mhz is not stable for me causes freezes/lockups for me. I dont tend to use voltages higher than 1350mv but the option is there for anyone who feel the burning itch
(1.8 is not recommended - untill further tests)
2) init.d support for boot up scripts - place start up scripts in /etc/init.d/
3) support for boot animations - place bootanimations.zip in /system/media/
4) I have built in cifs / nls_utf8 support into kernel so no need for seperate modules
Tested ok. Not sure what nls_utf8 does but seems to be requested quite a bit. If problems of unmounting shares, try umount -l /path/to/mount normally does the trick.
5) Added ntfs read/write support for kernel - Not tested myself
6) Added udf / iso support to kernel -Tested ok - can mount bluray iso's etc.
7) Added support for Interactive governor
Tested seems bit of a cpu hog / not properly optimised enough so would not recommend using it.
Ondemand seems to work the best. May look into porting other governors but not anytime soon
8) Slightly modified touchscreen driver
decreased the tsp_threshold level for 50 to 20.
You can set this value manually by
echo "X amount" > /sys/class/sc/sec_touchscreen/tsp_threshold/
However the problem is that the value gets reset to 50 every time the screens switches off. Hardcoded 20 as the default value it changes to after screen turns off.
Also changed the default ontouch frequency from 500mhz to 800mhz. The voltages for each are roughly the same so should be a wee bit more responsive without impacting battery life. Can set higher if anyone wants this.
Other general stuff - removed some debug info from kernel.
----------------------------------------------------------------------------------------------------------------------------------------------------------
EzyKernel Download link
p6800_EzyKernel.zip
http://www.mediafire.com/download.php?5xkglbje6ndo2ge
----------------------------------------------------------------------------------------------------------------------------------------------------------
Additional Mods:
Kernel works fine with deodexed /odexed system. Theoretically odexed is faster but I cant notice much difference between the two.
1) Deodexed & Zip-aligned Stock System / App folders from the ZSKL2 firmware
Download Links:
(Use Hjsplit or another tool to combine the following into one
GTP6800DOX.zip.001
GTP6800DOX.zip.002
http://www.mediafire.com/download.php?2pqwdbcox5o7pdv
http://www.mediafire.com/download.php?6ykpook81both85
GTP6800DOX.zip.001 : D844D0F20CA5C5CA4EDDC2F4BE993FE3
GTP6800DOX.zip.002 : D0AF7C4B7C43D2F0974DA2E9C42EF5AC
2) Custom boot animation modified from
http://forum.xda-developers.com/showthread.php?t=985251(thanks to aph)
Download link:
bootanimation.zip
http://www.mediafire.com/download.php?yvpv0y1bgp5bcne
3) Custom init.d scripts for slighty better wifi /ram management.
There seems to quite a few of these ram/performance scripts flying about. Not tested myself properly as these are os level tweaks so needs some time to adjust for best values i presume.
literally cut&paste jobbie thanks to juwe for his ram tweaks.
slightly modified: thanks to joker.20 for his general / wifi tweaks http://www.android-hilfe.de/root-ha...imus-3d/145592-tweaks-scripts-collection.html
Download link:
S97Ramscript
http://www.mediafire.com/?k45pjvf083d8rp4
Mods for Deodexed system only:
1) Modified Black status bar & Power menu - added reboot / reboot recovery options.
The framework-res.apk contains my grey battery icons mod. You can easily change to blue stock by just copying over the grey icons with the blue ones using winrar for example. (all icons are ok now )
Download link:
http://www.mediafire.com/download.php?zmnbun90z9w0az9
If you found this useful for you please try using one of my apps such as EzyMount which is on the google market:
https://play.google.com/store/apps/d...zymountcontrol
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INSTALLATION:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit - it seems there maybe a problem flashing kernel through cwm recovery. Samsung are playing games again!! Flashing kernel through stock recovery works. Confirmed working by kazuni & does not increase binary counter You still may want to flash kernel via cwm first if you are already using it, then try stock recovery if it does not work for you.
Modified install steps below.
1) Need to be running ZSKL2 based firmware -if yes then just flash kernel in stock recovery
Otherwise follow the steps below
Download firmware from here:
http://www.filefactory.com/file/c2c681d/n/P6800ZSKL2_CSC_TGY.exe
Flash in odin
Thanks to xenix96 for this & see his thread for flashing instruction & other useful info
Fortunately, ZSKL2 firmware is not a full wipe firmware. It keeps you apps,settings. I was using ZSLA2 firmware and even after flashing the ZSKL2 firmware, i still had my settings, user data etc.
Once you change the default language to English you are good to go.
Off course in any event backup your sdcard contents to an external drive.
Make a full cwm recovery backup so you can always revert.
2) Root
(see respective threads on how to do so)
root - http://forum.xda-developers.com/showthread.php?t=1454112
3) Flash the kernel in stock recovery
Reboot- Finger Crossed everything should run ok
4) Flash cwm recovery
cwm - http://forum.xda-developers.com/showthread.php?t=1470896
Should be good to go !!
Install of ExtraMods:
1) System DEODEX - just flash deodex zip in cwm recovery
2) Modified Power menu - flash in cwm recovery
3) Boot animation - manually copy bootanimation.zip over to /system/media/
4) Tweaks script - manually copy over to /etc/init.d/. You may need to mkdir init.d if it does not exist. Set proper permissions (chown root.shell yourscript && chmod +x yourscript - google it!) for any script you place there.
Possible Issues:
(not issues for me - i should add)
1) Kies updates might be broken. If this is a problem for you dont flash.
Personally, until we get an ICS update, i am not bothered with kies or android 3.2 incremental updates.
2) CSC is not for my country. If this is a problem dont flash.
I am in the uk and the hongkong csc works fine for my mobile provider.
In any event, csc information is stored in cache.img of stock firmwares. You could possibly manually change csc info and see if stock recovery automatically picks its up after flashing cache.img taken from your stock firmware. Might work
3) Flashing custom kernels can increase binary counter
So far flashing in cwm or binary copying zImage does not / should not increase the flash counter. Flashing kernel in odin / download mode will do this. No guarantees. If this is a problem for you dont flash.
source diffs - available once everything has been tested reliably
Usual disclaimer - these mods are to be used at personal risk only !
cheers ezynow

Reserved for updates, bugs,issues, boootloops etc
1) 23/02/20012 - Kernel Bluetooth fix.
Main kernel downlink link update. Should be fine to flash in cwm recovery if not you may have to try stock recovery.
Some points:
1) I know browser is not the best. But to enable browser at full speed u need to remove cpu limit. Change settings after entering about:debug in address bar.
2) be very careful with setcpu dont apply settings at boot untill sure of settings. It seems to stick settings after freeze. U may have to manually delete setcpu xml files if it happens

6800 tabs only or will it work on 6810's?

Nice work, my friend. Looking forward to to trying this out...
Sent from my ADR6425LVW using XDA App

got556 said:
6800 tabs only or will it work on 6810's?
Click to expand...
Click to collapse
sk806 said:
Nice work, my friend. Looking forward to to trying this out...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
6800 only but changes should be easily ported to 6810.
Cheers sk806.

ZSKL2 variant or ZSKL2 only ?
nice works btw..

sg10 said:
ZSKL2 variant or ZSKL2 only ?
nice works btw..
Click to expand...
Click to collapse
ZKSL2 is only tested working - will change thanks.

just FYI, tried on DXLA2, bootloop.

Ezynow, the link you have provided for the firmware is P6800ZSLA2_CSC_TGY.exe. I'm assuming this is the ZSLA2 firmware. Is this the same as ZSKL2?

reiconol said:
Ezynow, the link you have provided for the firmware is P6800ZSLA2_CSC_TGY.exe. I'm assuming this is the ZSLA2 firmware. Is this the same as ZSKL2?
Click to expand...
Click to collapse
ZSKL2 is P6810 firmware csc zzt for asian countrys

xenix96 said:
ZSKL2 is P6810 firmware csc zzt for asian countrys
Click to expand...
Click to collapse
Not completely correct. Both ZSKL2 and ZSLA2 is available for 3G (P6800) and both are set to TGY (Hong Kong) for CSC.

I've installed as per instruction of yours, installing the ZSKL2 firmware through odin on my P6800 3G tab. Did a complete wipe in recovery (no custom recovery yet) and rebooted. The unit kept bootlooping with the samsung logo.
I wish I can do a logcat through adb but it seems like adb doesn't want to bridge into my unit.

xenix96 said:
ZSKL2 is P6810 firmware csc zzt for asian countrys
Click to expand...
Click to collapse
I mean the firmware link ezynow has provided points to the ZSLA2 (LA2) firmware but these modifications of his are for the ZSKL2 (KL2) firmware. So my question is whether the link pointing to the LA2 firmware is the same as KL2 firmware.
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
I've just noticed ezynow has updated the link to ZSKL2 firmware. Downloading this version now but will hold off install it. Seems some people are having problems...

kazuni said:
I've installed as per instruction of yours, installing the ZSKL2 firmware through odin on my P6800 3G tab. Did a complete wipe in recovery (no custom recovery yet) and rebooted. The unit kept bootlooping with the samsung logo.
I wish I can do a logcat through adb but it seems like adb doesn't want to bridge into my unit.
Click to expand...
Click to collapse
Updated the download link in main post.
will try reflashing to stock myself.
It could be samsung has properly prevented flashing of custom kernels through cwm etc.
will do some testing later today

ezynow said:
Updated the download link in main post.
will try reflashing to stock myself.
It could be samsung has properly prevented flashing of custom kernels through cwm etc.
will do some testing.
Click to expand...
Click to collapse
I believe you are right.
Scenario 1:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, reboot into recovery to wipe, reboot into normal, go into odin, flash recovery kernel,reboot into recovery and install root zip, rebootinto recovery and installed ezyNow kernel, bootloop.
Scenario 2:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, finish setup, reboot into recovery to wipe, reboot into normal, reboot into recovery and install root.zip, reboot into normal, reboot into recovery to install ezyNow kernel, boot fine.
Scenario 3:
Gonna try Scenario 2 with ZSLA2.
All in all, great job!
p.s. before scenario 3, i am actually wondering i should install recovery kernel now, but as far as i remember, the recovery kernel install will override your ezyNow kernel install perhaps (on new samsung devices, they do not distinguish kernel and recovery anymore i believe, as I have talked to tegrak about my korean Galaxy Note (SHV-E160S) it takes a lot longer time to create a recovery + kernel mod.)
p.s.2 screenshot of ezy installed:

Some updates:
1800Mhz freeze my tab (using SetCPU)
Not very stable with those uv rates. I'm gonna try to raise them by 50mV per setting, let's see if that helps.

kazuni said:
I believe you are right.
Scenario 1:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, reboot into recovery to wipe, reboot into normal, go into odin, flash recovery kernel,reboot into recovery and install root zip, rebootinto recovery and installed ezyNow kernel, bootloop.
Scenario 2:
installed ZSKL2, reboot into recovery automatically to apply CSC, reboot into normal screen, finish setup, reboot into recovery to wipe, reboot into normal, reboot into recovery and install root.zip, reboot into normal, reboot into recovery to install ezyNow kernel, boot fine.
Scenario 3:
Gonna try Scenario 2 with ZSLA2.
All in all, great job!
p.s. before scenario 3, i am actually wondering i should install recovery kernel now, but as far as i remember, the recovery kernel install will override your ezyNow kernel install perhaps (on new samsung devices, they do not distinguish kernel and recovery anymore i believe, as I have talked to tegrak about my korean Galaxy Note (SHV-E160S) it takes a lot longer time to create a recovery + kernel mod.)
p.s.2 screenshot of ezy installed:
Click to expand...
Click to collapse
kazuni said:
Some updates:
1800Mhz freeze my tab (using SetCPU)
Not very stable with those uv rates. I'm gonna try to raise them by 50mV per setting, let's see if that helps.
Click to expand...
Click to collapse
Good to see
So the second way of installed worked for you.
You should be able to flash cwm recovery now. Cwm recovery uses a seperate partition/kernel which should be fine. I am running it off course. I have flashed kernel using cwm afterwards fine but the first time might need be through stock recovery.
Please could you check if your binary counter has increased by going into odin download mode. Samsung may have been sneaky in different bootloaders
Oc to 1.8 was not stable for me at stock volts so this just experimental - may try lowering to 1.7 as max overclock or introducing an intermediate frequency step so the "jump" from low to high frequency is not that large but 1.6 undervolted is ok for the time being.
cheers

ezynow said:
Good to see
So the second way of installed worked for you.
You should be able to flash cwm recovery now. Cwm recovery uses a seperate partition/kernel which should be fine. I am running it off course. I have flashed kernel using cwm afterwards fine but the first time might need be through stock recovery.
Please could you check if your binary counter has increased by going into odin download mode. Samsung may have been sneaky in different bootloaders
Oc to 1.8 was not stable for me at stock volts so this just experimental - may try lowering to 1.7 as max overclock or introducing an intermediate frequency step so the "jump" from low to high frequency is not that large but 1.6 undervolted is ok for the time being.
cheers
Click to expand...
Click to collapse
got custom recovery working. was gonna do a full nandroid but i can't because the kernel isn't stable enough for me.
the counter hasn't increase, but then i was planning to make a jig cable to reset it anyway
I believe you are right - the jump from 1.6 is a big gap. I've placed both 1.6 and 1.8 at 1400 and it seems to be a bit more stable.

kazuni said:
got custom recovery working. was gonna do a full nandroid but i can't because the kernel isn't stable enough for me.
the counter hasn't increase, but then i was planning to make a jig cable to reset it anyway
I believe you are right - the jump from 1.6 is a big gap. I've placed both 1.6 and 1.8 at 1400 and it seems to be a bit more stable.
Click to expand...
Click to collapse
Good news. Be aware setcpu can be buggy it can set voltages / max frequency at boot even though you say not too after a freeze/lockup
Once I had to boot into cwm recovery (no overclocking here), use adb shell to delete the setcpu.xml files in /data/data/com.mhuang.overclocking, just to clear all the setcpu stuff.
Been running 1.6 undervolted solid for a couple of days no problems

ezynow said:
Good news. Be aware setcpu can be buggy it can set voltages / max frequency at boot even though you say not too after a freeze/lockup
Once I had to boot into cwm recovery (no overclocking here), use adb shell to delete the setcpu.xml files in /data/data/com.mhuang.overclocking, just to clear all the setcpu stuff.
Been running 1.6 undervolted solid for a couple of days no problems
Click to expand...
Click to collapse
Thanks for the advice, I managed to reset set CPU back to stock by deleting the files under data data com.mhuang.overclock, because I didn't know that its the xml file actually contains boot time configurations.
After maximizing the clock and set it to 1400, the unit still randomly reboots. Anyway I'm still keeping your kernel because I like the under voltage
Sent from my GT-P6800 using xda premium

[I9000] Which ROM do i install?

For me the perfect combination is:
1. Stable CM10.2.1 rom
2. Kernel Semaphore 3.3.0 (avoid version 3.3.0s because it gives problems with Netflix, besides version 3.3.0 is perfect and you can activate bigmem with Semaphore Manager App, so 3.3.0s is nonsense) (NOTE: You need odin for installing it, follow this instruction)
3. Gapps: gapps-jb-20130813-signed.zip
4. Semaphore manager app. Settings for Semaphore Manager:
- Smartassv2 Governor: Awake ideal freq 900000 / Up rate 10000 / Down rate 99000 / Max CPU 50 / Min CPU 20 / Ramp up 300000 / Ramp down 300000 / Sleep ideal freq 300000 / Sample rate jiffies 2.
- Deep Idle: Enable
- Lock min freq to 100Mhz: Disable
- Active Scheduler: CFQ
- Bigmem: Enable
5. My build.prop to be placed within /system/ (remember to set for this file rw-r--r-- permissions and change owner to root).
6. A launcher like Zeam Launcher or Lightning Launcher
7. And finally an installed App Cache Cleaner Pro to erase the cache every now and them.
Best.

Just tried to install that rom but the Galaxy remains stuck during installation from SD: installation starts but soon hangs with open robot and red triangle, than reboot etc.
This the sequence I'm following:
1) install stock ROM I9000XWJW7_ITA_ValuePack_Gingerbread-236 with Odin, everything ok
2) install ClockWorkROM recovery CF-Root-XX_OXA_JW4-v4.4-CWM3RFS via Odin, everything ok
3) start with recovery, wipe cache, data etc
4) launch CM10 installation from SD card
5) red triangle...
I'm rather desperate as before I also tried other CM and got stuck in the same way.
Any idea?

Zed The Bot said:
Just tried to install that rom but the Galaxy remains stuck during installation from SD: installation starts but soon hangs with open robot and red triangle, than reboot etc.
This the sequence I'm following:
1) install stock ROM I9000XWJW7_ITA_ValuePack_Gingerbread-236 with Odin, everything ok
2) install ClockWorkROM recovery CF-Root-XX_OXA_JW4-v4.4-CWM3RFS via Odin, everything ok
3) start with recovery, wipe cache, data etc
4) launch CM10 installation from SD card
5) red triangle...
I'm rather desperate as before I also tried other CM and got stuck in the same way.
Any idea?
Click to expand...
Click to collapse
i9000 developers always recommend upgrading from Gingerbread to 4.x custom ROMs and rooting with appropriated kernels depend on the stock rom you are using. I think your are using a JW7 over a JW4 CF-Root kernel, tried this stock rom version "GB 2.3.6. oxajw4 csc openeurope", it is the one I used with your CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.
And/Or, you can find a good tutorial for your CF-root kernel for your italian stock JW7 rom on this post.
And follow this thread: [FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO]

kuskro said:
i9000 developers always recommend upgrading from Gingerbread to 4.x custom ROMs and rooting with appropriated kernels depend on the stock rom you are using. I think your are using a JW7 over a JW4 CF-Root kernel, tried this stock rom version "GB 2.3.6. oxajw4 csc openeurope", it is the one I used with your CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.
And/Or, you can find a good tutorial for your CF-root kernel for your italian stock JW7 rom on this post.
And follow this thread: [FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO]
Click to expand...
Click to collapse
Thanks a lot for your help but... does not work! :crying::crying::crying:
I tried both your suggestions, the "GB 2.3.6. oxajw4 csc openeurope" + "CF-Root-XX_OXA_JW4-v4.4-CWM3RFS" and the linked Italian procedure.
They all end up in the same way!
The only hint I have is that during installation of the stock ROM I see a message like "Cannot access /system/CSC/ITV/system" followed by "Successfully installed multi CSC"... does it mean anything for you?
Anyway the stock ROM and the Recovery usually install and apparently work properly...

Zed The Bot said:
Thanks a lot for your help but... does not work! :crying::crying::crying:
I tried both your suggestions, the "GB 2.3.6. oxajw4 csc openeurope" + "CF-Root-XX_OXA_JW4-v4.4-CWM3RFS" and the linked Italian procedure.
They all end up in the same way!
The only hint I have is that during installation of the stock ROM I see a message like "Cannot access /system/CSC/ITV/system" followed by "Successfully installed multi CSC"... does it mean anything for you?
Anyway the stock ROM and the Recovery usually install and apparently work properly...
Click to expand...
Click to collapse
No idea, sorry.
Maybe this Spanish link could help you, I normally follow this thread when I forgot how to come back to android 2.3.6: http://www.htcmania.com/showthread.php?t=292984 (Italian translation).
Best.