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
Related
I have an i9000M running UGKG3, rooted. I still have the stock kernel and have no modifications. I'm trying to get a CWM or 2e recovery that will let me install update.zip files that aren't signed.
I have tried kernel after kernel, getting bootloops with every one.
I tried signing the CWM update.zip myself but it only managed to remove one of the two errors I get about it not being signed in 3e Recovery. I tried signing it multiple ways, nothing.
I tried replacing some of the recovery files with Root Explorer, to no avail.
I also tried flashing JVQ and JVR so I could use CF-ROOT, but they didn't even get to the "Galaxy S" boot logo before it looped.
Does anyone have a solution?
Anything that works, really. A signed update.zip, a i9000m compatible kernel, a successful replacement method, anything that will install a usable recovery.
Thanks in advance,
Getinaf
I'm in the same situation as you. I have UGKG3 installed, with the rooted stock kernel via Odin. I have tried almost every custom kernel I can think of, and they all boot loop. I've tried Rom Manager to install CWM, and it doesn't work either. I haven't tried any JVR roms yet, but from what I read they should work, so I'm surprised you're getting bootloops there too.
I guess there is something different with gingerbread compared to froyo that makes the kernel more picky. On froyo I had the stock JL2 rom, and was able to install the speedmod k13e kernel to get CWM without any problems at all.
I guess we'll have to beg and plea for a dev to make a modified KG3 kernel with root and CWM recovery. I would be happy with that. I don't care about lagfixes or any other mods to the kernel. I just want root and CWM
I totally agree, that or I'll try and cook us one. I hear there are tutorials for things like root and cwm. I'm really actually trying to install juwe's smart rom, and for the life of me nothing is working. I'm sure there are more people like us out there too, it will be worth it to find a solution.
Sent from my GT-I9000M using XDA App
Getinaf said:
I totally agree, that or I'll try and cook us one. I hear there are tutorials for things like root and cwm.
Click to expand...
Click to collapse
I am very tempted to make own kernel. Nice and simple: root, and cwm. That's it. Now to find a tutorial
has anyone figured this out yet?i'm in the same situation...
Just flash this kernel on top of whatever you have, it'll work... trust me!
http://forum.xda-developers.com/showthread.php?t=1112908
I've been running that kernel for months back then when I was still running official Gingerbread KG3 from Bell and it's the best one there is.
Installation steps :
- Download kernel
- Start Odin, make sure Kies' services are all shut down
- Select Kernel as PDA in Odin
- Put phone in download mode
- Connect through USB ... Odin should detect phone
- Hit start, reboot phone
- Enjoy, you're done!
If you have problems like FC after that:
- reboot to recovery
- "wipe cache"
- Advanced menu --> Wipe Dalvik cache
- reboot (be patient, it'll take a few minutes to reconstruct dalvik cache)
- you're done!
Did all this and nOw in a boot loop. Can't reflash as debugging is off. I flashed first tIme frOm mObile Odin ?
What ROM did you have installed when you flashed Semaphore kernel?
Please help
HiKsFiles said:
Just flash this kernel on top of whatever you have, it'll work... trust me!
http://forum.xda-developers.com/showthread.php?t=1112908
I've been running that kernel for months back then when I was still running official Gingerbread KG3 from Bell and it's the best one there is.
Installation steps :
- Download kernel
- Start Odin, make sure Kies' services are all shut down
- Select Kernel as PDA in Odin
- Put phone in download mode
- Connect through USB ... Odin should detect phone
- Hit start, reboot phone
- Enjoy, you're done!
If you have problems like FC after that:
- reboot to recovery
- "wipe cache"
- Advanced menu --> Wipe Dalvik cache
- reboot (be patient, it'll take a few minutes to reconstruct dalvik cache)
- you're done!
Click to expand...
Click to collapse
Hi,
Please help... i have samsung i9000 and had stock rooted the phone. Tried to install the above kernel and now the phone is stuck on the bootloop, not booting up... Please help
Hey everyone, my phone is running 2.3.5 of Android and it is branded to Orange. My build number (and kernel version) is BVJVC. I cannot find the right cf root for me. There doesnt seem to be any for JVC. Can anyone help?
TarnWilliamson said:
Hey everyone, my phone is running 2.3.5 of Android and it is branded to Orange. My build number (and kernel version) is BVJVC. I cannot find the right cf root for me. There doesnt seem to be any for JVC. Can anyone help?
Click to expand...
Click to collapse
Are you planning on rooting to then flash a custom rom or do you just need root access?
If you are planning on changing roms then just flash a pre rooted firmware or one that has a root solution available.
What do you want cf-root for? If you want root to you can flash a custom ROM it doesn't really matter which one you use. If you want it to run you current stock ROM with root then it is better to run the correct one. I cannot find that one either. Good luck.
Sent from my GT-I9000 using xda premium
There's no cf-root for JVC. I've only found a french forum with a very tricky way to root... far easier to flash another ROM that has cf-root. But come on, let's have a little more fun... ICS!
I want to change rom. Can I just flash any rom compatible with galaxy s i9000 or do you have to have compatible kernels? I have seen tutorials where it says to flash to something specific before flashing to the final one. If it's possible can someone send me a link to a custom pre-rooted rom which I can flash straight away onto my phone?
Sent from my GT-I9000 using XDA App
most of the roms come with a kernel. You can then flash other kernels but these do need to be comparable. I have team oceans 4.2 for example. This comes with its own kernel but I have installed semaphore 0.9.1 which sheet a lot of testing has been the best fit for my use. Hope that makes sense. If you have something particular inn mind let us know and we can help more
Sent from my GT-I9000 using xda premium
TarnWilliamson said:
I want to change rom. Can I just flash any rom compatible with galaxy s i9000 or do you have to have compatible kernels? I have seen tutorials where it says to flash to something specific before flashing to the final one. If it's possible can someone send me a link to a custom pre-rooted rom which I can flash straight away onto my phone?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1533327.
This is a stock firmware and the Odin 512.pit that I use when going back to stock and root is easily applied. It is a good idea to save these on your computer if (or when) things go wrong .
Can I just flash a rom with its custom kernel over my orange stock rom and it's kernel? They don't have to be similar in any way? Also, so I don't need root access to flash a custom rom.
Sent from my GT-I9000 using XDA App
You will need root access to flash custom roms as most have to be flashed by cwm(which you will get when you root your phone)
This brings me back to my original problem, people told me to flash a rom with compatible CF-root, but to flash i need to root? So i am stuck in a little circle?
Or does this only apply to custom roms and not flashing stock roms?
You flash Cf-root with Odin. This gives you root. You then flash custom ROM through recovery on your phone. As mentioned above if you want root to flash custom ROM then you need root it does not really matter which cf-root you use. Just follow instructions in Cf-root thread then follow instructions from ROM thread you want to flash.
If you want to use stock ROM with cf-root then it needs to be compatible.
Sent from my GT-P7500 using xda premium
CF-Root info here: http://forum.xda-developers.com/showthread.php?t=788108
From thread:
Instructions (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Help! I don't know which file to pick! The filenames confuse me!
First thing: don't panic! It's all rather easy, and you won't easily do something bad! I am personally attentive to use the exact same version as the ROM I am running, but it's not that important.
First, go to Settings -> About phone -> Build number. It should say something like FROYO.xxJPy. It's primarily the JPy that we are interested in. Try to match that with a download link available in this (and the next few) posts. Some of the downloads dont just have JPy file name format, but are called xx_xxx_JPy.
Find the one that is closest to yours, if yours is not present, and flash that one.
If you are just installing CF-Root to flash a custom ROM like Darky, make sure you have ROM Manager already installed, ClockworkMod flashed, then simply install the latest CF-Root, reboot once normally, then reboot in recovery and run the Darky update.zip. In this case it does NOT need to be a near match at all!
Before you start it is a good idea to download your stock rom or another one for your phone from here. http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9000&r=-1#modelsa Then where it says region click your country.
I recommend getting everything you need before you start. So make sure you Odin, a 512 pit file & your stock rom with the PDA, Phone & CSC files. There are plenty instructions for getting back to stock if you search.
Next get the ROM you want & the kernel you want.
Now that you have everything you are ready to go.
My process is as follows.
1. Remove SD Card, some say to remove sim but I have never done this.
2. Turn on phone & turn on USB debugging.
3. Connect phone to usb & copy everything on my internal sd card onto my pc. (I have a samsung folder & create a folder with the date and put everything in there - just in case)
4. (USB) Disconnect your phone from your computer
5. shut down phone.
6. Follow cf-root thread instructions.
7. Unzip the attached CF-Root-xxx-vX.X.zip
8. Start ODIN
9. Click the PDA button, and select CF-Root-xxx-vX.X.tar
10. Put your phone in download mode (power on, volume down, home button)
11. (USB) Connect the phone to your computer
12. Make sure repartition is NOT checked
13. Click the START button
14. Wait for the phone to reboot
15. Done (if it took you more than 30 seconds, you need practise!)
Now you have root & cf-root. Restart phone. Next step is generally as follows.
1. Start phone.
2. Connect phone to pc.
3. copy files you wish to flash onto root of internal sd card. in my case team icssgs 4.2 & semaphore 0.9.1
4. (USB) Disconnect your phone from your computer
5. restart phone into recovery.
NB. Make sure to do a backup at this point and ensure you have a copy of your efs folder somewhere!!! - if for some reason your IMEI number is corrupted you will need this
6. factory reset & clear cache
7. advanced button -> clear dalvik cache.
8. back & choose install zip from sd card
9. choose zip from sd card.
10 .select the zip file (in my case team icssgs 4.2)
11. Choose yes- install... zip name
12. repeat steps 8-11 and select semaphore kernel.
13. factory reset & clear cache
14. advanced button -> clear dalvik cache.
15. reboot phone. Reboot can sometime take a while. sometimes you may need to do this twice.
Semaphore: http://forum.xda-developers.com/showthread.php?t=1468795
Team ICSSGS: http://forum.xda-developers.com/showthread.php?t=1398223
If no luck then reinstall stock rom using odin making sure to use all three files & pit file with repartition checked.
Please note I am still fairly new at this so it may not be perfect & you should always rather follow instructions from the thread of the ROM you wish to flash
Hopefully that's it. Don't think I left anything out.
TarnWilliamson said:
This brings me back to my original problem, people told me to flash a rom with compatible CF-root, but to flash i need to root? So i am stuck in a little circle?
Or does this only apply to custom roms and not flashing stock roms?
Click to expand...
Click to collapse
Ok, let's clear things up a little. Every rom has its own kernel, let's say the default kernel of that ROM. There are stock Roms, which are those official of Samsung. Those come with its own kernel, but not rooted.
Now: there are some stock roms, of which some guys have managed to modify its kernel just to be able to have root access, and to have a modified version of the recovery: ClockWorkMod recovery.
There are other kernels, though. Kernels that people develope to improve those default kernels that come with stock kernels. But improve performance comes with (perhaps) less stability (actually that's not completely true, as cooked kernels also improve stability, and are in general far better than stock ones). What is true is that not every cooked kernel works with every rom, you have to make sure it works with what you want.
You definitely don't need to have root access to flash, but you do in order to make those highly important security backups! You can have root without flashing kernel.
Now, what are those roms that flash over other roms...? Generally cooked roms are stock roms modified to improve them. But they still use a lot of the stock roms system, that's why cooked roms have to be flash only over that rom they are based on. You still don't need to be root to flash those roms, but generally you do need ClockWorkMod recovery, that's why you need to flash cf-root kernel prior flashing a cooked rom. Or perhaps the cooked rom do not come with a modified/rooted kernel and you still needs to change the kernel (but usually they already come with a rooted kernel)
Hope that helps you even a little to know what do you want to do!
Thanks for the help everyone. I am going to flash an unbranded stock rom to get out of this orange rom. Would this tutorial work to debrand my phone?
http://droidangel.blogspot.com/2012/01/i9000xxjvu-android-236-upgrade-for.html?m=1
Sent from my GT-I9000 using XDA App
Tutorial is fine...
Sent from my GT-P7500 using xda premium
Hi people.
I have a question.
When my Note goes to deep sleep mode, the screen blinks back on on it's own as if it's awaking from a bad dream!
It's frustrating, how can i make it stop?
Try jbroid kernel cleaning then reflash your kernel
Sent from my GT-N7000 using xda premium
mention your ROM and KERNEL....and its funny...i mean the Title of your thread
It's true! it's waking up from deep sleep and then all day it has a foul mood. I've tried doctors, i've tried everything, you are my last hope guys!
My Rom is N7000XXLA4, kernel is:2.6.35.7-N7000XXLA6=CL907341 [email protected]#2(Do i really need to write all this when people ask me what kernel i have or would a shorter version suffice?)
I am on gingerbread.
Now i just noticed a thread registering the same problem i have under the title: Deep Sleep Problem
I have the same issue.
adamskoc said:
Try jbroid kernel cleaning then reflash your kernel
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Can you tell me how to flash a kernel?
Do i need to download a file or something?
Android 4.9 Marshmallow said:
Can you tell me how to flash a kernel?
Do i need to download a file or something?
Click to expand...
Click to collapse
you have to read. AND READ A LOT. especially the sticky threads.
after reading and UNDERSTANDING, whatever file you need is usually mentioned on those threads.
Zapped through server hops to XDA forums
Android 4.9 Marshmallow said:
Can you tell me how to flash a kernel?
Do i need to download a file or something?
Click to expand...
Click to collapse
ReFlash Kernel means you on the custom Kernel already, and if you on the stock, it's not applicable. You can just download the PC-odin 1.85 or 1.87, then flash the right official ROM for your country from the sammobile.com site, with hard reset before. OR, you can go to the custom ROM. OR, you can try just hard reset.
I am on official rom and i have just gotten the phone back from a logic board replacement.
I want to install a custom ROM and eventually go to ICS but first i have to fix those deep sleep hiccups.
I am trying to determine the best course of action.
In the following hours i am going to root my device and the reflash my rom based on this guide: http://forum.xda-developers.com/showthread.php?t=1462309
and then i am going to install CMW and titanium backup so i won't lose my apps(i really don't want to install them from the beginning.)
The rom i have will not update to ICS as it's brand new. Do you think i should wait or change ROM and get ICS?
About the kernel now, why is it important to flash the kernel other from this particular situation?
Also can you provide a few links where i can safely learn how to flash the kernel?
Thank you all in advance
Android 4.9 Marshmallow said:
I am on official rom and i have just gotten the phone back from a logic board replacement.
I want to install a custom ROM and eventually go to ICS but first i have to fix those deep sleep hiccups.
I am trying to determine the best course of action.
In the following hours i am going to root my device and the reflash my rom based on this guide: http://forum.xda-developers.com/showthread.php?t=1462309
and then i am going to install CMW and titanium backup so i won't lose my apps(i really don't want to install them from the beginning.)
The rom i have will not update to ICS as it's brand new. Do you think i should wait or change ROM and get ICS?
About the kernel now, why is it important to flash the kernel other from this particular situation?
Also can you provide a few links where i can safely learn how to flash the kernel?
Thank you all in advance
Click to expand...
Click to collapse
Unfortunately i cannot provide the links, because i'm "new member". I'm only reading here, before today.
But, the course of action for you:
1) If you will flash the custom ROM with the custom kernel you do not need to deal with the sleep mode, because the kernel is controlling modes/clocks and ither vital parts of life of your phone. Kernel is the main part of the "soft" in your phone.
2) Remember the one most important thing: DO NOT USE wipe cache/format data, on the samsung official 4.0 - 4.03 in CWM. If you need to wipe, you need to install the Abyss kernel 3.9-4.2
How to:
You need to find PC-Odin 1.85 or 1.87, and the rooted ROM with CWM in *.tar format. Close all kies services with "task manager".
Connect your phone in download mode (home+vol. down+power and when is powerd on and asking you about flashing, vol. up), launch Odin. You will see yellow quadrant in odin. Then you need to click on "PDA", then selecting the downloaded ROM file, and do not forget the "pda" checkbox. Do not touch the other checkboxes, then Start.
Wait before it's flashed.
This is the basic guide, as i said, i cannot provide you with the links, so if you need something more - ask, i'll try to help you.
QA:
What is CWM? CWM is advanced recovery program. It's built-in in kernel. You can enter in CWM by pressing in powerd off phone home+vol.up+power.
Wht is kernel? Kernel is the core component of the phone ROM. You can flash it separate from other parts of ROM.
You can also flash separately the Modem (phone), CSC and UMS parts. Remember, some kernels do not support some ROMs, for example: If you'll flash the Cyanogen Mod, and then some Franco kernel, your phone will cannot start properly. Ofc. you can use CWM in this case.
This is scary to flash my phone? No, if you read all instructions, you can "breack it" in the only one case: you'll wipe it from the CWM builded in official samsuung 4.0 - 4.0.3 RoM.
What is "wipe/format user data"? This is the way to clear your personal data, and the other trash in your system. You need to wipe before installing new ROM.
What happens if i flash new ROM without it? Nothing, but some of your apps can work incorrect in this way.
How to flash kernel from CWM? Download the kernel in *.zip file, copy it to the SD-card, restart in CWM, install zip file. If you have *tar file, use the PC-Odin.
Shmong said:
Unfortunately i cannot provide the links, because i'm "new member". I'm only reading here, before today.
But, the course of action for you:
1) If you will flash the custom ROM with the custom kernel you do not need to deal with the sleep mode, because the kernel is controlling modes/clocks and ither vital parts of life of your phone. Kernel is the main part of the "soft" in your phone.
2) Remember the one most important thing: DO NOT USE wipe cache/format data, on the samsung official 4.0 - 4.03 in CWM. If you need to wipe, you need to install the Abyss kernel 3.9-4.2
How to:
You need to find PC-Odin 1.85 or 1.87, and the rooted ROM with CWM in *.tar format. Close all kies services with "task manager".
Connect your phone in download mode (home+vol. down+power and when is powerd on and asking you about flashing, vol. up), launch Odin. You will see yellow quadrant in odin. Then you need to click on "PDA", then selecting the downloaded ROM file, and do not forget the "pda" checkbox. Do not touch the other checkboxes, then Start.
Wait before it's flashed.
This is the basic guide, as i said, i cannot provide you with the links, so if you need something more - ask, i'll try to help you.
QA:
What is CWM? CWM is advanced recovery program. It's built-in in kernel. You can enter in CWM by pressing in powerd off phone home+vol.up+power.
Wht is kernel? Kernel is the core component of the phone ROM. You can flash it separate from other parts of ROM.
You can also flash separately the Modem (phone), CSC and UMS parts. Remember, some kernels do not support some ROMs, for example: If you'll flash the Cyanogen Mod, and then some Franco kernel, your phone will cannot start properly. Ofc. you can use CWM in this case.
This is scary to flash my phone? No, if you read all instructions, you can "breack it" in the only one case: you'll wipe it from the CWM builded in official samsuung 4.0 - 4.0.3 RoM.
What is "wipe/format user data"? This is the way to clear your personal data, and the other trash in your system. You need to wipe before installing new ROM.
What happens if i flash new ROM without it? Nothing, but some of your apps can work incorrect in this way.
How to flash kernel from CWM? Download the kernel in *.zip file, copy it to the SD-card, restart in CWM, install zip file. If you have *tar file, use the PC-Odin.
Click to expand...
Click to collapse
Your post has been most helpful
But i still have questions.
1st: What if i don't want to flash a custom ROM just yet? how can i get rid of the deep sleep hiccups without going off the official roms?
2nd: What will happen if i wipe my cache during ICS in CWM?
3rd: I recently flashed the CSC from KOR to EUR(I did it because i couldn't access Kies, and i chose EUR because it's corresponding to my country). My current ROM didn't offer DBT as an option. So if i flash it again and find an N7000XXLA4 Rom with DBT offered will i have the ICS update available through official channels?
4th: What does UMS stand for, what does it do?
Thank you in advance
Come on mate follow the instructions and flash rocket rom v6 the most stable one and enjoy it
Sent from my GT-N7000 using xda premium
Android 4.9 Marshmallow said:
Your post has been most helpful
But i still have questions.
1st: What if i don't want to flash a custom ROM just yet? how can i get rid of the deep sleep hiccups without going off the official roms?
2nd: What will happen if i wipe my cache during ICS in CWM?
3rd: I recently flashed the CSC from KOR to EUR(I did it because i couldn't access Kies, and i chose EUR because it's corresponding to my country). My current ROM didn't offer DBT as an option. So if i flash it again and find an N7000XXLA4 Rom with DBT offered will i have the ICS update available through official channels?
4th: What does UMS stand for, what does it do?
Thank you in advance
Click to expand...
Click to collapse
1. You need to switch off your device, than remove the battery for ~10 sec. Then switch it on, and do not touch it before it's switched to standby, then wait about 35 minutes for deep sleep. But if it doesn't work, u can flash it with official firmware with Odin. Sammobile have all official roms. You didn'g get the yellow triangle this way.
2. You will brick your device. And loose some int. memory in advance (~4gb). Why? Because official samsung rom have an error, and it's rewriting your NAND memory again and again with full speed of your CPU and memory dying in the few seconds (about 100-200k rewrites supported).
3. What for do you need the OTA??? You can flash china, korean, even russian official roms through odin without fear. And then you can get OTA's. Custom kernels do not support OTA in any form. Just think: if you flashing custom rom, how you can get official over it?
4. Don't know ))) UMS - usb mass storage, i think, but i'm not sure in this. And i do not know what for we can use it.
Hi. I noticed I had the exact same problem yday on my note. I turn off the screen, 5 seconds later the screen turns on again (on the lockscreen), stays for 2 seconds and then turns off. Then another 20 seconds later repeat. My phone definitely was going to deep sleep (checked with CPU spy), but this "nightmare" thing was annoying. I was on RR v6 with Speedmod k3. I dunno what the reason was for this, so I just simply changed my kernel to Goku v1. The issues seems to have gone away now. I dunno what was causing it, but I am just sharing what I did to get rid of this.
I rooted my device(with CF-Root) and then flashed a kernel and then returned to my original one.
The problem is still here.
Later today i am going to try and return to a CMW friendly kernel and then flash the jBroid Kernel Cleaning Script that adamskoc mentioned in his post.
I will be posting results.
By the way even with the custom Kernel my activity from last night is summarized by this picture:
All night the phone was restless...
Yupp I've had this problem also before. The no deep sleep bug. To get rid of this follow this:
Put the phone in airplane mode.
Turn off the phone.
Take out the battery.
Wait for like a minute and put the battery back in and turn on the phone.
Wait for the phone to completely reboot and be stable (scanning usb etc).
Now turn off airplane mode.
I dunno whats the relation but I never had the no deep sleep issue after following these steps.
dp4c said:
Yupp I've had this problem also before. The no deep sleep bug. To get rid of this follow this:
Put the phone in airplane mode.
Turn off the phone.
Take out the battery.
Wait for like a minute and put the battery back in and turn on the phone.
Wait for the phone to completely reboot and be stable (scanning usb etc).
Now turn off airplane mode.
I dunno whats the relation but I never had the no deep sleep issue after following these steps.
Click to expand...
Click to collapse
I did that yesterday. Didn't work.
I have just finished flashing the jBroid.
I will be keeping you posted.
/Edit: it's not working... I tried flashing a new kernel, i tried the jBroid script, i tried the airplane mode trick... Nothing. What the hell is going on here? Could this be a hardware issue? I just got my logical board replaced due a previous faulty one, could they have replaced it with a used one that might also have problems? I don't know what to make. Does that happen?
This is so screwed up...
I was on stock ICS, i flashed the latest notecore kernel after i got root, and then flashed another kernel, and now when i rebooted it it decided not to start, i cannot get into recovery however i can get into download mode, i however do not know how to use this, i have drivers installed to my computer, but am unsure if i need kies aswell. could somebody please help me as its really really late here but i am unable to sleep as i need my phone in the morning! thanks.
killarhye said:
I was on stock ICS, i flashed the latest notecore kernel after i got root, and then flashed another kernel, and now when i rebooted it it decided not to start, i cannot get into recovery however i can get into download mode, i however do not know how to use this, i have drivers installed to my computer, but am unsure if i need kies aswell. could somebody please help me as its really really late here but i am unable to sleep as i need my phone in the morning! thanks.
Click to expand...
Click to collapse
Safest way is to flash stock GB or pre-rooted GB firmware using PC odin.
killarhye said:
I was on stock ICS, i flashed the latest notecore kernel after i got root, and then flashed another kernel, and now when i rebooted it it decided not to start, i cannot get into recovery however i can get into download mode, i however do not know how to use this, i have drivers installed to my computer, but am unsure if i need kies aswell. could somebody please help me as its really really late here but i am unable to sleep as i need my phone in the morning! thanks.
Click to expand...
Click to collapse
Flash this pre rooted GB Rom using PC Odin
http://d-h.st/HJM
Your phone must be in Download mode and don't change any settings in PC Odin. Just select the file under PDA tab and Hit Start
Easiest way you can try first, otherwise go long way as above said by jeetu & sahil
Flash Notecore kernel (.tar vesion)with PC odin (for PDA tab)
Later reset flash counter with Triangle Away.
This thing happened to me today as well, from my other post:
I installed CleaNote ROM and it worked fine (restored all my apps via titanium backup) then I rebooted to recovery and installed NoteCore 14 kernel and 15toggle zip which was recommended for the ROM. Now i am stuck in white boot up GT-N7000 screen and cannot go back to recovery mode. I can only go to download mode.
Any links to the TAR version of notekernel and flash counter? Thanks
UPDATE: ITWORKS! Thanks dr.ketan, I flashed the Notecore kernel TAR and now it boots up. Used triangle away from Google play to remove triangle. Again, thanks a lot
gx3k said:
This thing happened to me today as well, from my other post:
I installed CleaNote ROM and it worked fine (restored all my apps via titanium backup) then I rebooted to recovery and installed NoteCore 14 kernel and 15toggle zip which was recommended for the ROM. Now i am stuck in white boot up GT-N7000 screen and cannot go back to recovery mode. I can only go to download mode.
Any links to the TAR version of notekernel and flash counter? Thanks
Click to expand...
Click to collapse
hold 3 button home+up+power when GT-7000 logo on dont release its keep holding until screen go blank that time release 3 button.its will put you back to CWM. Happen to me couple time and its what i did..good luck
aha look like you back on track now.Everywhere should be fine when had Dr.Ketan,,,,,
try to flash pre-rooted GB firmware using PC odin.
gx3k said:
This thing happened to me today as well, from my other post:
I installed CleaNote ROM and it worked fine (restored all my apps via titanium backup) then I rebooted to recovery and installed NoteCore 14 kernel and 15toggle zip which was recommended for the ROM. Now i am stuck in white boot up GT-N7000 screen and cannot go back to recovery mode. I can only go to download mode.
Any links to the TAR version of notekernel and flash counter? Thanks
UPDATE: ITWORKS! Thanks dr.ketan, I flashed the Notecore kernel TAR and now it boots up. Used triangle away from Google play to remove triangle. Again, thanks a lot
Click to expand...
Click to collapse
and u got 15 toggle or stock toggle?
gx3k said:
This thing happened to me today as well, from my other post:
I installed CleaNote ROM and it worked fine (restored all my apps via titanium backup) then I rebooted to recovery and installed NoteCore 14 kernel and 15toggle zip which was recommended for the ROM. Now i am stuck in white boot up GT-N7000 screen and cannot go back to recovery mode. I can only go to download mode.
Any links to the TAR version of notekernel and flash counter? Thanks
Click to expand...
Click to collapse
Exactly same thing happens to me this morning. So something is up with the NoteCore 14 kernel Recovery. Its fine till you try to access it.
oalex said:
Exactly same thing happens to me this morning. So something is up with the NoteCore 14 kernel Recovery. Its fine till you try to access it.
Click to expand...
Click to collapse
V14 took a long time to launch CWM, approximately 30 seconds, but it does launch eventually and does work as normal.
So it doesn't get stuck it just takes time...... Patience is all you need.
This is fixed in v14.1.
I upgraded from v14 to v14.1 last night without any problems and can confirm that the CWM launch delay is now fixed.
I have installed all NoteCore kernels since v3 and never had a major problem.
Sent from my GT-N7000 using xda premium
killarhye said:
I was on stock ICS, i flashed the latest notecore kernel after i got root, and then flashed another kernel, and now when i rebooted it it decided not to start, i cannot get into recovery however i can get into download mode, i however do not know how to use this, i have drivers installed to my computer, but am unsure if i need kies aswell. could somebody please help me as its really really late here but i am unable to sleep as i need my phone in the morning! thanks.
Click to expand...
Click to collapse
Exactly had the same problem ...
http://forum.xda-developers.com/showpost.php?p=30561024&postcount=2276
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
simplelife said:
hold 3 button home+up+power when GT-7000 logo on dont release its keep holding until screen go blank that time release 3 button.its will put you back to CWM. Happen to me couple time and its what i did..good luck
aha look like you back on track now.Everywhere should be fine when had Dr.Ketan,,,,,
Click to expand...
Click to collapse
If it works ... this can be the only saviour. other than download mode.
gx3k said:
This thing happened to me today as well, from my other post:
I installed CleaNote ROM and it worked fine (restored all my apps via titanium backup) then I rebooted to recovery and installed NoteCore 14 kernel and 15toggle zip which was recommended for the ROM. Now i am stuck in white boot up GT-N7000 screen and cannot go back to recovery mode. I can only go to download mode.
Any links to the TAR version of notekernel and flash counter? Thanks
UPDATE: ITWORKS! Thanks dr.ketan, I flashed the Notecore kernel TAR and now it boots up. Used triangle away from Google play to remove triangle. Again, thanks a lot
Click to expand...
Click to collapse
I found the same trying to install the 15toggle zip, you could try your original method without the 15toggle zip and it will most likely work.
Hi all. Please note that the NoteCore V14.0 has a delay of about 30 to 60 seconds before it enters recovery. Just sit and hold your breath until your fact turns blue and voila, you are in recovery. V14.1 solves the problem of this long delay.
Hi Guys,
V14 had the issue with CWM... once u boot to recovery donot do anything,, wait for the screen to load.. it will do it eventually.
New notecore
Changelog
v14.1
- Fixed laggy CWM
- Removed JRCU switched to a differently configured standard fanout RCU
- TinySHMEM instead of full SHMEM
- Added, and enabled KSM page merging
- Memory compaction optimised
- ARM optimised RWSEM algorithm
- Switched back to a *slightly* altered SLQB heap allocator
- Kernel scheduler latencies reduced
- Some .config changes
- Some initramfs changes
- Improved responsiveness at low frequencies with ondemand governor
- Touchscreen sensitivity tweaks
- Compiled with googles standard toolchaing, but with all linaro's optimisation flags
- Improved performance!
arinsms said:
and u got 15 toggle or stock toggle?
Click to expand...
Click to collapse
Yes, the recommended 15 toggle which was originally for LRK now works with CleaNote5 ROM, although I went back to the default ROM (NoteCore 12.3)as the newer versions of NoteCore kernel seems to be buggy for me
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.