Related
I am having a few problems with rooting my Galaxy S.
I have looked for hours at different threads about different root methods and different kernels but I am not sure which root method and kernel to use.
I am running Gingerbread 2.3.3 XVJVH. Can somebody give me some advice and provide me with a link to rooting instructions with your preferred method please?
Thanks
RobWill116
Hy!
I'm using already rooted kernel's like SpeedMod.You can try with this---> http://forum.xda-developers.com/showthread.php?t=1044519(but this is for 2.3.4 but should work on 2.3.3)
I have tried all root versions with JVP, almost to the point to brick the phone and I came to the following conclusion why do all the kernels remove the bootanimation sound????
I reinstalled the original stock JVH because JVP has a huge battery drain not explicitely on the usage settings but with the same usage of applications on a daily routine the phone wouldn't last 14 hours. With JPY and now JVH, the battery last almost 48 hours.
I just want to have root to install the daily briefing from JVP and to calibrate the GPS but there is no rooting method nor kernel which stick to stock rom implementing only root, busybox and su and the rest to remain untouched....either the bootanimation sound is removed or you get extra tweaks when you are not using it...so anynone for a minimalist rooting?
Try fuguroot.
Tried it. it removes the boot animation sound, so all the other root method...
You could try with one-click root but i'm not sure that will work on 2.3.3
Sent from my GT-I9000 using XDA App
it doesn't work either...see my desperation?
Flash speedmod kernel
Apply root from recovery
Flash stock kernel
Or flash ramad's deodexed jph with's pre rooted
Sent from my GT-I9000 using XDA App
just put the boot sound back yourself!
Thanks for all the replies! I think I'm going to give fuguroot a go sounds the easiest haha
Just wanted to check firstly, is there.no root with JVH? Just the fact a lot of people have said it has the best battery life
RobWill116
Sent from my GT-I9000 using XDA App
Hmm I'm using Chainfires CF-Root. It works perfectly with jvh. Although you need to use odin to flash the kernel. But I don't think it's a problem for you if you know how to flash stock rom.
Sent from my GT-I9000 using XDA Premium App
Thanks I might give that a go as well. I new to SGS flashing, had X10 but O2 couldn't fix it and didn't have anymore in stock so gave me SGS instead! I'm sure I'll find some instructions anyway - unless you want me help me out further and post a link
With pleasure.
RobWill116 said:
Thanks I might give that a go as well. I new to SGS flashing, had X10 but O2 couldn't fix it and didn't have anymore in stock so gave me SGS instead! I'm sure I'll find some instructions anyway - unless you want me help me out further and post a link
Click to expand...
Click to collapse
Note! You really should be sure that you are on JVH and please read the thread I linked to you carefully. In cause you would brick your phone. I bricked my phone a couple of times already by doing something else stupidly. However here in Finland Samsung is kind enough to fix it for me always. Even I explained that I bricked it by flashing some other roms myself
Again If you are indeed on JVH. then:
1st. head to this thread by ChainFire himself.
http://forum.xda-developers.com/showthread.php?t=788108&highlight=CF-ROOT
2nd. search for "CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.zip" to download.
3rd. Unzip the file.
4th. open odin and load this file as PDA.
5th. put your phone into download mode and then connect to your computer.
6th. flash and done.
One thing you might want to know. ChainFire Root removed the booting sound as well. But it keeps the original boot animation.
I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
tamaleddon said:
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
Click to expand...
Click to collapse
I just flashed the RE version and it's making some progress. Definitely no weird colors.
PROBLEM:
-the boot screen is still flashing when trying to boot my phone, only this time it's with the "Darkcore & Darky's ROM" logo on it. The flashing is at a slower pace this time around.
ALSO:
I can get into the stock recovery screen, I hope this can somehow help
what should I doo!!?!
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
gfacer said:
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
Click to expand...
Click to collapse
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
As far as i read on the Darky Site you have to activate Lagfix to install 10.2
Do you?
In other case.
Install Resurrection 9.2 FW:
(sorry. new member no links outside allowed: Go darky forum, stable roms, darky resurrection 9.2)
If that works your bootloader if for Froyo and afterwards you can go on to flash Darkys 10.2 like written in the Darky Forum.
But i would suggest to stay on Darky´s 9.5 with 2.2.1
It is the stable version with no bugs at all. This gingerbread sucks a lot with Akku Drain, Light sensor and other thing. Also no call records.
I will stay on 9.5 so far. Best solution at the moment...
The thing with installing 10.2 you installed without installing 2.3.3 rom before could be, that is maybe possible to install Darkys 10.2 Theme on a 2.2.1?
But no guarantee...
roma17 said:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
Click to expand...
Click to collapse
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
sxi200 said:
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your response! Greatly appreciated. But at the time, I'm just looking to get my phone to work. It still doesn't work, it's still only stuck flashing the bootscreen, nothing else.
From my other post:
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Could be that you have a lagfix enabled and the stock ROM can't read the EXT4 file system. If so, try flashing another custom ROM via Odin (e.g. GingerReal), disable the lagfix to go back to RFS, then from there you can go back to the stock ROM.
gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Well CM7 forum is down but here is the most of the link, you can google this and look at the cached pages. cyanogenmod topic/15707-how-to-restore-to-stock-on-your-gt-i9000m/
You should be able to click to the multi upload link too.
Now - you are aware of course that our i9000m models can suck and die fairly readily, especially when flashing certain roms. Has yours even been returned yet? Mine has and they replaced the motherboard. You may actually have a warrenty job and in any regard they won't likely fight too hard (just flash it to one of the jl2 or kc1 rom first).
If you want to find out for sure. look for the i9000m threads where they install eclair and use the external sd to boot and then look at the memory (internal then shows as external I think - its in the thread). Basically if it shows 0 available you're hooped.
gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
I'm downloading the ROM from this link, could you verify it?
http://forum.xda-developers.com/showthread.php?t=883568
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
there is a I9000UGJL2_homebinary_add_param.tar
and a SS_DL.dll
so All i would have to do is just put that .tar file in PDA field and get a regular .pit file and check off the re-partitions
gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Great!
My advice would be to pretend it never happened, but read all the instructions for the rom you are interested in and start from scratch.
Generally I would go custom froyo kernel from odin which will root you and give cwm generally, update bootloader to gb via a stock rom or ezbase, then flash 10.2 via cwm.
Darky has excellent guides also look at ezbase thread.
Sent from my GT-I9000M using XDA Premium App
roma17 said:
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Click to expand...
Click to collapse
To load Darky 10.2 successfully on your phone, you have to flash JVP or JVQ bootloader over your phone. The best solution is flash Stock Rom with bootloader over your phone. Then, flash Darky rom over your phone.
OK I have spent about 2 weeks now looking through roms, kernels, root methods etc etc.
I have come to one conclusion. IT SUCKS owning a Verizon tab on this forum.
Most of the guides are accurate, but often miss one little detail that anyone who knows this stuff would think "duh" about, but a noob will miss, and end up reflashing stock from heimdall 10 times over because of.
Long story short, I would like to see a Verizon guide here on the development section that is kept up to date and has proper links to working roms as well as IDIOT PROOF walk throughs.
I would be willing to do this, or someone else can, I do not care. I will edit this very post so that it can serve said purpose if it gets made a sticky, or added to a sticky thread.
In this spirit I will later edit this post but I have a few questions/requests first.
1. I have never had the need to host files for large numbers. I use my own server to host things, but I know I cannot do that for this. Can someone PM me with what would be the best method to host files for people (IE It seems one service somewhere will add links through direct downloads, Megaupdload, Rapidshare etc at the same time).
2. Correct me if I am wrong. Heimdall seems to be the best root method. Heimdall + the ec02 files = the most stable and fully robust and stable rom for the VSTG (Verizon SGT).
3. The Verizon SGT Bootstrapper will convert to Ext4 and add CWM, but results in a broken camera and rotation, the latter of which I have a fix for, but not the camera. Dos any other way of adding CWM work better?
4. Sprint has a completely working update to GB, that works on the VSGT as well, minus radio function. I read somewhere what steps had to be taken to get the 3g radio working as well, but have since not been able to find it. If someone who reads this knows, could you please post or PM me where to begin fixing the radio on the sprint rom to work with the VSGT?
Morkai Almandragon said:
3. The Verizon SGT Bootstrapper will convert to Ext4 and add CWM, but results in a broken camera and rotation, the latter of which I have a fix for, but not the camera.
Click to expand...
Click to collapse
Please tell me how you fixed the rotation? I can deal with no camera, the one in my phone is better anyway.
I am not the greatest help in the world....but have a VSGT and will help where i can.
Sent from my SCH-I510 using XDA Premium App
mnpolock said:
I am not the greatest help in the world....but have a VSGT and will help where i can.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8
There is the thread that will fix the rotation bug... Now if I can get the camera working... LoL
Oditius said:
http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8
There is the thread that will fix the rotation bug... Now if I can get the camera working... LoL
Click to expand...
Click to collapse
Do not run a kernel that requires Ext4 and both work perfectly.
IE use Heimdall and install the ec02 firmware, then stop. Everything seems to work, without any fix required.
Morkai Almandragon said:
Do not run a kernel that requires Ext4 and both work perfectly.
IE use Heimdall and install the ec02 firmware, then stop. Everything seems to work, without any fix required.
Click to expand...
Click to collapse
Man, I wish I spoke french... Because that is what the above looks like to me. My camera doesn't work, and I didn't do anything but root it, and install that Verizon Bootstrapper. Well at least the rotation works, still don't know what to do about the camera.
I used the verizon bootstrapper after restoring to completely stock ec02 and rooting with super one click. Then used heimdall to flash psirens kernel and then flash psirens rc 2.5. From here http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw
and my camera and rotation work great after replacing the sensors.so file to fix rotation. Currently I am overclocked to 1.4ghz with voltage control and all is running flawlessly and fast.
ticklemegavin said:
I used the verizon bootstrapper after restoring to completely stock ec02 and rooting with super one click. Then used heimdall to flash psirens kernel and then flash psirens rc 2.5. From here http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw
and my camera and rotation work great after replacing the sensors.so file to fix rotation. Currently I am overclocked to 1.4ghz with voltage control and all is running flawlessly and fast.
Click to expand...
Click to collapse
How exactly did you install the kernel and rom? can you post a step by step
?
Morkai Almandragon said:
How exactly did you install the kernel and rom? can you post a step by step
?
Click to expand...
Click to collapse
Step by step and with links on everything that you need. Written so easy to understand so a person with no experience can knock it off with no problem.
Me, I'm on a stock but rooted VSGT, and I'm fine with it really. Only thing I do wish for is a 2.3 update from VZW. I don't care about OC'ing, Tab is very snappy enough for me and battery life is very good.
I looked into flashing the Sprint update but thought against it because I need 3g.
Recently got a Nexus S4G and running MIUI on it, and boy, I wish we could get a MIUI port on our tab. Those guys are just dang good and crazy.
Sent from my SCH-I800 using Tapatalk
Ok here is what I did.
1. Get the stock un-rooted un-updated firmware from here http://forum.xda-developers.com/showthread.php?t=1136587&highlight=verizon
2. Follow this guide to flash the files you got in step 1 http://forum.xda-developers.com/showthread.php?t=967175&highlight=verizon+stock+firmware
3. After you have flashed back to stock and booted up into android then update through android to ec02.
4. Download super one click from here http://forum.xda-developers.com/showthread.php?t=803682 and follow the instructions on that page.
5. You now should be rooted. Now download the verizon bootstrapper off the market and run it.
6. After that has completed download the rom/kernal and follow the instructions on this page http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw.
7. Alright now you should be rooted with a custom kernal and rom installed your camera should work. If your rotation doesn't work then get the sensors.default.so from here http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8 and follow the guide.
That's exactly what I did and my camera/rotation work fine.
If you want to overclock use voltage control from the market.
So, I have to go back to square one, where I started. and do everything all over again?
The use SOC to root it.
Then run the program that knocked out my camera/rotation again.
So I will be right back where I am now.
Then I have to update the kernel.
Then install a new rom.
And it should work.
OK, thanks...
Never mind, if I go back to square one, I will just stop and not go any farther. My GT was fast enough without doing all that. So I will wait, maybe someone will come up with a fix for the camera that was as easy to fix as the rotation. I don't video chat and my Mesmerize has a better camera and easier to use.
Yes that is what i did after trying to flash a voodoo kernel and getting stuck at the Samsung logo many times. I flashed back to stock and started over. Not sure when the camera started working in the process, I had checked after everything was installed. Also im not sure if psirens rom even flashed or not because everything looked exactly the same and still had the Verizon bloatware installed which I just removed with titanium backup. Im not sure if i have ext4 or not would there be a way to check?
The thing is I never flashed the voodoo kernel. I rooted the GT last week. Yesterday I was reading around, obviously not as well or completely as I should have. But I was going to flash a new rom and it stated I had to do the Bootstrapped first. So I downloaded it and that was when all heck broke loose. I read later on in the thread that the camera stopped working and so did the rotation. Well the rotation had a fix, but the camera doesn't. Oh well, I will keep looking, maybe if I just start at #6 because that is where I stopped.
ok What I am finding is this. Flashing the EC02 files through Heimdall result in a rooted Froyo rom that runs stable and decent, but without CWM.
You can then use the Verizon Bootstrapper on the market which flashes a new kernel that includes CWM. The new kernel breaks the camera and rotation though. Flash the better than life kernel and camera is fixed, followed by the rotation fix and you are now back to close to stock with root, and CWM...
Here is where I lose my way though. The Psirens rom looks JUST like the EC02 Heimdall install I have. I will post the files I am using once I get a host I am happy with.
Morkai Almandragon said:
ok What I am finding is this. Flashing the EC02 files through Heimdall result in a rooted Froyo rom that runs stable and decent, but without CWM.
You can then use the Verizon Bootstrapper on the market which flashes a new kernel that includes CWM. The new kernel breaks the camera and rotation though. Flash the better than life kernel and camera is fixed, followed by the rotation fix and you are now back to close to stock with root, and CWM...
Here is where I lose my way though. The Psirens rom looks JUST like the EC02 Heimdall install I have. I will post the files I am using once I get a host I am happy with.
Click to expand...
Click to collapse
This is exactly what I think except that the ec02 files I linked will take you back to full unrooted stock where as the files from the tutorial for flashing ec02 I linked will leave it rooted but with stock ec02. I also cannot tell a difference between stock ec02 and psirens ec02 they look exactly the same. I almost wonder if cwm is not flashing the rom correctly. But even if it didn't you get a stable ec02 experience with a overclockable kernel which is all I was really looking for in the first place. I also could not get the voodoo kernal to work period I flashed it several times and always got stuck at the samsung screen on boot. My tab is much faster now and im pretty happy with it. Now if we could just get a stable gingerbread or maybe even honeycomb ill be all over that.
http://forum.xda-developers.com/showthread.php?t=1178414
Just saw this after my last post, looks like we will have gingerbread with working 3g (which I require) very soon. So we should be seeing some performance improvements whenever we get gingerbread.
If you guys want a stock ROM, converted to ext4, just ODIN Boushh's kernel then (if you're on the newest VZW update EC02) replace the file in that thread that fixes auto rotation.
Coolsaber57 said:
If you guys want a stock ROM, converted to ext4, just ODIN Boushh's kernel then (if you're on the newest VZW update EC02) replace the file in that thread that fixes auto rotation.
Click to expand...
Click to collapse
Boushh's kernel will not work for me I always get stuck at the samsung boot screen. Im flashing with heimdall though because I only use linux and i do not think there is a version of odin for linux.
I am writing this because I know nobody has the time to go through all the threads.
People don't use the SEARCH button (there is no alternative to that..neither my rant here)
So tried to sum up all that I can here. Do let know below in comments if anything else is to be added or removed.I urge everyone to go through this complete post and I am sure you will find something interesting or something worth for you. If not then I am sorry for your 5 mins wasted !!
For all the members who are about to get their hands dirty or are already in the dirty waters! Welcome!
Just make yourself double sure that you are here and you are comfortable about playing with your device. Be okay with bricking it (yeah had to say this because whining and pointing fingers at others is not acceptable here)
Please avoid asking questions about rooting and stock roms in a particular rom thread. Let there be talk about that rom development and not rooting.
You want to root your device. Here you go – Rooting Guide by Dr Ketan
You want stock Roms – Here you go – Stock Roms by Dr Ketan again
You want Stock Prerooted Roms – Here you go – Stock Odex Prerooted Roms by Bodivas
PS - If you are using the Prerooted Stock Roms from the above link then after PC ODIN flash of the stock rom of your choice just download the corresponding CF Root Kernel (i.e. if you flashed LC1 Rom, download LC1 CF-Root kernel) and flash it through Mobile Odin to inject CWMR. Done.
You want all the Safe kernels - Here you go - [ICS][GB] Kernel Repository
So you are now rooted. Now as per Samsung your warranty is now void. Congrats. Remember you only did it and you only wanted it. So cheers!! Pour yourself and me a beer
Now go flash any GB custom rom you like choosing from here – GT N7000 Development Thread
Okay remember to read the changelog and the Features. Don’t crib for the features that are not included. You don’t like the rom and features move on. Don’t curse the developer for it.
Very Famous Example- asking for touchwiz features like SMemo, SPen gestures in APOKP/AOSP roms. Blasts on your way. Better reading about them here by Chasmodo - Flash ICS and Survive
Who wants GB now. All wants the cool IceCream!
Okay so WAIT.
Now remember there are much serious repercussions in getting to ICS than doing all the above stuff with GB.
Here this is to be read very first – Hard Bricking Kernels Public Announcement by Entropy
NEVER perform any sort of WIPE or FACTORY RESET when on Stock ICS Kernel/Rom (rooted or non-rooted)
DO NOT try to go to any CM9 or CM10 based rom from the Samsung ICS rom/kernel. Sure shot BRICK.(those who haven't got bricked by doing this consider your self lucky...huh) Best way is to - Go to GB > root > then flash any CM9 based rom.
Only These roms are termed completely safe till now and are build on safe kernels till the time Samsung doesn’t release the source code and we have plethora of kernels like in GB.(will keep adding to the list)
CM9 Nightlies
Asylum ICS
MIUI
ParanoidAndroid
HALF-ILLUSION
All other ROMs that are based on the CM9 source.(info about it in the OP of each ROM thread...must read always)
The stock ICS roms which are on custom kernels like Franco / Speedmod etc which have MMC_CAP_ERASE command disabled.
There are many ROMs in the dev section which are based on LPY kernel. They too work perfect but still have the volatility and the warnings applied as the LPY is not that safe. So flash on your own risk and don't pester the Devs of those roms about question of safety and security. Read the above Public Announcement and decide which way you want to go!
Now some more info. Always before doing any of the flashing
Check your current kernel from
Settings > About Phone > Kernel Version .
Do NOT flash from the following kernels:
i9220ZCLP1
i9220ZCLP5
i9220ZCLP6
N7000XXLPY
Some most asked questions.
Q1 –Man m already on one of these kernels. Now waaahhhat?
Don’t panic. If you are on the rom which includes any of these kernels then refrain from flashing anything in the CWM. If the rom you are on presently is good for you just be there and don’t go on experimenting on the unsafe kernels. Wait for the stable safe kernls to come out.
Or
Switch to any of the above safe roms.
Before going to any of the safe roms go back to stock GB. Use PC Odin.
Here we have another complication. Check this thread. LPY to GB via PC Odin = super brick? This might be the fix of these Superbricks - Here
Now best way is always PC odin. And it still is unless your EMMC is not already damaged by using the wipe function . Check Here Above case happened to some users but most of the users whent back successfully. Now always remember to use PC odin when you have installed all the drivers. If you use Windows 7 PC then always check for the Online Searching for Drivers in the notification bar on your PC. This should be stopped or completed before doing any PC odin activity.
IMP - You can use Mobile Odin. But make sure first that the rom you are on and using the Mobile Odin that is having complete root by pasting any file in the root folder which is /system (use any file explorer with root privileges)
Once on GB, root it. If you going for the Pre Rooted Stock Roms remember you will have to inject the CWM using the CF Root zip from Chainfire’s thread for any subsequent flashing you want to do or use Mobile Odin (remember to check complete root status before using it)
Q2 - I am already on CM9 or Asylum or MIUI can I try the stock ICS German release?
Sure you can try but with no CWM. It sucks so recommendation is don’t try. Be on the safe roms and wait. And I bet they are much better and smoother than the stock. There are some cases of bricks with LPY having root when flashing in CWM or doing intensive I/O tasks.
There is no reported harm to flash ics without cf root(stock kernel + root no cwm) Check the Official ICS Flashing guide by Dr ketan again (Man this guy helps the Note community a lot )
Q3 – Man I am on GB and it sucks. I want ICS.
GB doesn’t suck in this case. At least you have your device working. If you are not comfortable enough with all the cautions and thin lines to tread its better to stay on GB a little longer. If you daring enough go tread on the lines of ICS but don’t cry over the brick you might achieve if you are not careful enough.
Q4 – I cant paste into /system folder nor can change DPI.
You have lost root. Kindly PC ODIN (only and only PC Odin) back to GB and then get it rooted (or flash pre rooted rom then inject CWM or use mobile odin now after flashing the pre rooted rom) and then flash the ICS rom of your choice (better stick to the safe ones…if not your wish)
Q5 – Am Senior Member I Know my way in and out and daring enough to tinker. All Warnings Applied
So you don’t want the Odin back to GB. Well then you have the Abyss Note 4.2 Kernel with Redpill Touch recovery. You are on any unsafe kernel ICS Rom and you want to go to safe rom then do one last CWM flash of Abyss kernel reboot recovery and then flash the safe roms. This keeps your root intact. You can even acieve root though this if you have lost it. Just flash Abyss 4.2 go to GB. Check root there and then flash the ICS rom. No need of repack. If any of this gets struck or brick then you know your way out already…..you told that in the question. My little guide here. Link for Abyss 4.2 Kernel in the guide.
Q6 - Most asked in the rom threads – I want the LP5 and LP6 modems. Here please.
Q7 - I want to go to LPF or whatever stock kernel ICS. And is it safe?
PLEASE dont go that route. Better stay on GB or root it and flash any of the CM9 kernel based rom. Please humble request!! :angel: Ask why in the comments if you don't get it by reading all the info in this post.
Q8 - The ICS source code is out. Where are the new kernels?
Yeah the SGN ICS sources are out. Check HERE
Wait for the developers to wield their magic and you will have the awesome kernels out for you in no time! Patience is the key
Q9 - I seriously want the safe CM9 kernel. Where is it?
Search for it in the CM9 thread. But i know many of you wont do that. So just to make this OP a lil more lengthy and one stop kind of shop m attaching the file below. Thanks Xplodwild. Flash the extracted zImage using mobile odin. Its a safe kernel so you can use its CWM anytime you want.I cant say with what all roms it will work. Might break some features in some roms so flash at your OWN RISK.
Q10 - What about the new ICS kernels??
Well the safest kernel CM9 is attached and the other one by Entropy's DAFUQ kernel got updated too. Franco and Speedmod kernels are build on the latest ICS Sources and have the formatting of MMC is blocked. So you are safe from damaged MMC bricking bug but not sure about the any other bricking bug on that as two users (AFAIK) reported bricks in the Franco kernel thread.
Also look for as Entropy told here - "install CPUSpy and make sure you don't see "se.infra" anywhere - that's the buildhost of Samsung's own kernels which are dangerous"
Be safe, Play safe. Check their change-logs...what works and what not and where and what roms you can install them on!
Q11 - I want to jump off from the unsafe kernels. How ???
A quick guide from Chasmodo - Here And lil Info about Mobile Odin Here
Q12 - Brick! Brick Brick!! What Man everywhere i read this on ICS!! Why is it so happening??
Well, as very well explained by Entropy -
"We now know there are three things that are ALL needed for this to happen:
1) A recovery (can be the recovery itself OR it can be the update-binary in a ZIP you flash!) that performs ERASE commands in addition to formatting. (GB recoveries and update-binaries don't do this, ICS ones do)
2) A kernel that allows those ERASE attempts to actually go through. (Disabling MMC_CAP_ERASE prevents this.)
3) Buggy eMMC firmware
Basically:
In Gingerbread, condition 1 was not met (However, this isn't guaranteed - if a Gingerbread ROM developer happens to accidentally grab an ICS update-binary in his installation ZIP, this COULD brick!)
In I9100 ICS releases, condition 2 was not met due to MMC_CAP_ERASE being removed
Condition 3 is true for nearly every GT-I9100, SGH-I777, SPH-D710, and GT-N7000 ever sold."
So got it ? Wanna get your minds more widen with the knowledge on this aspect - Visit HERE
Q13 - Got Brickbug ???
CHECK HERE - Thanks Chainfire
Q14 - I want to have CM10 on my rom!! How to??
Check on what kernel you are on. Any Stock ICS kernel or any kernel based on stock ICS sources then go PC odin back to GB (just read the above conditions on wiping and factory restoring first). Now get root on your GB. Install a CM9 based rom and after that install CM10 rom. For people being extra adventurous you can use the CM9 safe kernel to switch between roms. :angel: And never forget doing full wipe before coming to CM10
Don’t use any repacks now please. LP1 is a NO NO ! And don’t even think about the other one!
To Devs – If you find this guide or rant useful then please link in your OP. Thanks for your great work and time you invest you us. You are providing all this awesomeness free of cost. Hats off to you all !!
Respect them people. Or read this - Show your Support, Don't Whine by toxicthunder
To All Members – If you find this useful kindly hit the thanks button. And remember to read OP of each rom thread!!
Happy Flashing and Enjoy your Notes !I would like to quote+edit from toxicthunder post.
If something goes wrong, cry yourself a river.
But then don't forget to build a bridge and get over it.
A highly recommended and awesome and handy extension for you all (Thanks Toxicthunder)
*Galaxy Note Toxic Toolbar* - Check it out
Lastly thanks to Chainfire , Entropy512 , Xplodwild , Dr Ketan , Original_Ganjaman , Chasmodo , Antiochasylum , Matius44 , Tremerone , Toxicthunder , Androidindian , Geo.Samuel for all the help and support you guys have provided to me and the community.
And just in case you thought this have helped you save your precious time and device and you have some pennies to spare , Then you are most welcome todonate here This will encourage me more
Reserved for some future addons
For Mac Users - read Heimdall instead of PC Odin
Thanks for this it will be very use full to many who choose to take the time to read fine work thanks
Will be linking this in my OP.
As long as people READ it, very very good info.
Looks great brother!
.....like Anti said....hopefully people will READ it and understand. It's pretty crystal clear if you ask me.
Good summary!
Impeccable. Must read for every user.
If I had my way, this post should flash on each and every user's screen before he clicks on the "Post Quick Reply" button.
Many thanks for this!!
A good summary of our current and somewhat unfortunate ICS situation.
So the new LPF firmware/kernel is it safe? Because I saw some members wipe etc. and say it works fine except it doesnt restore. but is it safe from bricks?
androidindian said:
So the new LPF firmware/kernel is it safe? Because I saw some members wipe etc. and say it works fine except it doesnt restore. but is it safe from bricks?
Click to expand...
Click to collapse
It's early days yet. Be patient and we'll see.
Good one dawg!!
But if everybody had an habit of reading.............
Great work mate, added to the sticky list
Thanks Friends for all the support!! Yeah the only effort one has to do is to read. I made an effort to bring as many things as possible under one thread/OP. If not 100 threads then at least read this one. Yeah it still has so many threads linked but at least most of the info that is strewn in many threads i have tried to catch up here with direct linking. Will keep updating as new things keep popping. The first on the list being the LPF. Update in a couple of hours
Hope it helps all !!
Ah...and thanks OG for the sticky
Awesome thread.... for the awesome phone
Sent from my GT-N7000 using XDA
Great thread.
With so much information flowing these days, it's hard to keep track of what's going on.
Also, I had no idea that going back to GB from LPY may hard brick.. **** this.
Very well written post mate might recommend you as an editor trainee under the supeevision of our guru chas
Seriously though, very helpful thread and I really wish more and more members read it first.. Congrats on the sticky, well deserved
Cheers mate
Nice and concise.... Much appreciated
Sent from my GT-N7000 using xda premium
I found this threat very usefull..thanks mate
Sent from my GT-N7000 using Tapatalk 2
First off GREAT POST ABHISAHARA!!! A thanks is coming your way . Soooo..... after reading your initial post, the the LPY to GB via PC Odin = super brick? thread, and THEN the how to revert back to gb from lpy ics View Single Post thread. I have a "decent" grasp on where I'm at. I was one of the gunslingers that jumped on board the LPY on day 1. I was on rooted (GB or ICS Repack, can't remember honestly) and installed LPY Stock unrooted via PC odin. It did NOT wipe all my data so i'm assuming that means I did not do a full wipe (seems like a good thing from what I read), I really would feel better if I got off of this and went back to GB. I understand if my phone works fine I should sit tight, but I do deal with large movie files on a reg basis. The steps are where it gets grainy.
What I plan to do:
1: Connect via pc odin and flash only the abyss kernel 4.2
2. Connect and flash the 3 file Rooted GB rom
3. Finally wipe everything
Could someone just tell me if a: I am being flat out stupid and should really stick with what I got, or b: let me know if what I plan to do is a best course of action for taking this plunge. Thanks in advance guys!!!
A very nice piece of work that should be read by every member.
Sent from my GT-N7000 using XDA
Galaxy Note N7000.
Was running stock ICS-ROM Samsung.
Always wanted to install and use a custom ROM but was always afraid of BRICKS..
But yesterday ended up being sucessfully running CM9.
Steps I undertook were as follows:
1. Installed Samsung Kies.
2. Check for update from Samsung Kies and updated Kies.
3. Connected my phone to Kies and checked if Kies detected the phone properly.
After sucess, exit Kies.
4. Downloaded PC Odin from this link
http://forum.xda-developers.com/attachment.php?attachmentid=815370&stc=1&d=1323799721
password:samfirmware.com
5. Download pre rooted GingerBread ROM
SGN_XX_OXA_KJ1_FACTORYFS.zip (thx dr.ketan)
http://d-h.st/HJM
6. Run PC odin
7. Reboot Note in download mode
vol. down+home+power buttons
8. Connect Download mode note to PC
9. PC odin ID:COM turns yellow:
(ALL THE BEST NOW)
10. In PC ODIN
Auto Reboot and F.Reset Time ---> Ticked
Others --> Unticked
10. Click PDA and select the SGN_XX_OXA_KJ1_FACTORYFS.zip you had downloaded.
Click start.
Wait for 10minutes.
Your phone will restart.
11. WOW..!!! now ur on a GB Rom
And its a safe kernel
Now you can play around
Plus already rooted
12. Now to get this GB Rom working
go to recovery mode (vol up + home + power)
clean dalvik cache and wipe data and factory reset
13. Time to install CM9
14. Download
CM9 latest nightly:
http://get.cm/?device=n7000
Googleapps:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
15. Copy these 2 files in the internal SD card anywhere (do not rename)
16. Reboot into recovery mode:
vol up + home + power
17. Flash the 2 files from where you saved them:
"install zip from sd card" option in recovery mode
now flash cm9 file
then flash gapps file
18. DO A DATA WIPE / FACTORY RESET
19. Reboot
And wow..
Enter the world of custom ROMS
[[[to switch to another ROM, follow steps 1 to 17, and after that flash the ROM of your choice]]]
Steps 6 and 9
it shud be PC Odin Not Mobile
sorry dr. ketan
my mistake
corrected
thanks
So...
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.
dr.ketan said:
Steps 6 and 9
it shud be PC Odin Not Mobile
Click to expand...
Click to collapse
Noticed that u are very experienced contributor, so mybe u can answer on my question, does the step by step guide is safe for galaxt note with brickbug? I realy want to flash, but i want to do it if i am on the safe side
Latvianization said:
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.
Click to expand...
Click to collapse
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!
SirRhor said:
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!
Click to expand...
Click to collapse
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?
Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.
I installed rom before 2 days and had similar doubts.
Just want to share what problem I faced :
The mobile should be in ON state when rooting CF I was doing it in OFF download mode
Latvianization said:
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?
Click to expand...
Click to collapse
CyanogenMod 9 is based on ICS, CM7 is based on Gingerbread. There wasn't a CM8 because Google never released the source code for Honeycomb.
And what you need is a safe kernel, because the kernel is what sends a erase command to a chip inside the phone and that's when you brick it (I think). That happens when you do a factory reset.
Now, what I always do when I want to change ROMS is to use AbbysNote 4.2 as a safe GB kernel so I can then flash the ROM/Kernel of my choice.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1362424&highlight=abyssnote
So let's say you want to go from CM9 to LiquidSmooth (or pretty much any other), which is the one I use now:
You go to CWM recovery, from there you flash AbyssNote.
Once the flashing is completed, you DO NOT exit CWM, instead you go to "Advanced" and then "Reboot to Recovery" so the phone will restart but it will go directly to CWM again, but now with AbyssNote installed.
AbyssNote has a TOUCH based recovery, so it is easier to use. Don't use the physical power and volume buttons to navigate.
From there you can safely do a factory reset, format cache, format Dalvik, flash a new ROM and Kernel.
AbyssNote will then disappear because it will be overwritten by the new Kernel of your choice. So every time I want to change to a new ROM, I repeat the steps above I haven't had any problems whatsoever.
I hope I'm right with my technicalities, but the procedures the OP and I describe are safe to try as long you follow the exact instructions, so before you try anything, read and re-read and you will be just fine.
---------- Post added at 12:38 PM ---------- Previous post was at 12:34 PM ----------
tribalkg said:
Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.
Click to expand...
Click to collapse
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360
Thanks for the useful information and for putting to rest some of my safety concerns.
Now you've wetted my appetite and I have to give it a go soon.
Sent from my GT-N7000 using xda premium
Thanks for this great guide! I haven't gotten my Note yet as I just ordered it yesterday but I have been lurking around the forums already and trying to understand how flashing roms and kernels works around here. Like someone already said before some of the guides / threads are 'a little' confusing for newcomers. I was really confused with the brick bug that people were writing about. This thread clarified things a lot for me and I believe it will help many more Note-newbies!
So, new Note community member reporting to duty here! :highfive: It's gonna be pretty neat upgrade considering from what phone I come from. Well, the Huawei at least was great step stone to android world gotta admit. I just got somewhat bored with the not so great custom scene.
SirRhor said:
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!
tribalkg said:
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!
Click to expand...
Click to collapse
Dont worry about AbyssNote, is safe in both respects. That's the one I always use to do anything that is flashing related.
If, for some reason, you start seeing that dreaded triangle at boot, you can use TriangleAway from Chainfire on Google Play.
Sent from a GNote, hell yeah!
Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.
tribalkg said:
Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.
Click to expand...
Click to collapse
Dont worry, I'm glad I can help you.
You can try Marker and Jotter as well, they work well.
Sent from a GNote, hell yeah!
thanks
thanks for the guide.
I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2
maddog2727 said:
I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
If you are on GB already, you just have to root the ROM and flash CWM because the brick bug is present only on ICS kernels. 99% sure.
There are some GB Stock ROMs that you cannot root directly, so it depends.
OTA updates from Samsung to ICS I'm not sure, you should ask someone else. When I got my Note it already had ICS, so I never did an OTA update. I don't use Kies at all.
I was very weary at first too, but with the instructions above you will be fine.
Sent from a GNote, hell yeah!
I've followed the guide from OP and now I'm rockin' CM9! No problems at all.
My content on the internal memory was intact (apps data, games data, etc), it's all there and I've flashed Indian ROM and then CM9. Have I made a mistake or what?