Database Users

[GUIDE] Perka´s And flip360´s Clean Install Guide And Package

Perka´s And flip360´s Clean Install Guide And Package.
Warning!
If you do not follow the guide exactly you might brick your phone!
This guide is only for Samsung Galaxy S GT-I9000
If you do not know what 3 button combo or recovery is, read this please.
If you have Captivate Here you have a guide.
We are not responsible for bricking anybody’s phone!
If it happens we will try to help you, but remember we are doing this for free!
You do not have to do all Sections, please read what each Section is for.
IMPORTANT! – You need to read the guide before doing it, and use the files provided.
​
Section A If you have 2.1, 2.2, 2.2.1
Section B is for flashing stock 2.1, to get a fresh clean install.
Section C is for flashing our update.zip from 2:e recovery (It is a renamed Kitchen Rom) Log here.
Section D Another way to get to Kitchen Rom from stock 2.1 with 2e recovery, does not work with Stock Froyo 2.2 or 2.2.1.
Section E is a guide to Magical Rom Kitchen.
Section F is a How to CWM update.zip guide, (to get CWM, only works in 2e recovery 2.1 Eclair)
​
Before you begin with the flashing process, make sure that you:
Samsung drivers installed on your computer.
Have backups.(When you restore your backups, DO NOT restore system settings.)
Do not have any lag fix applied.(If you are going to flash stock with pit, no need to disable lag fix)
Phone battery is fully charged.
You don´t have Kies running.
We strongly urge you to read through the whole guide first before attempting any of this,
and sticking to our reference, here is the files that you will need before attempting to flash your Samsung Galaxy S GT-I9000.
​
Download Section.
Odin v 1.3
Samsung USB Drivers.
Driver x64
Driver x86
For Section A
Speedmod Kernel K13b
For Section B
GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM_Odin_Csc_Pit.512.zip
or
GT-I9000_I9000XWJM9_I9000XXJM4_CODE-MODEM_Odin_Csc_Pit.512.zip
For Section C
The renamed Kitchen Rom (update.zip) Log file This is used if you get stuck on GT screen.
For Section D
Z4Root
Sgs Kernel Flasher
Speedmod Kernel choose the CWM.
Qr codes in Post 2
For Section E
Cook your favourite Kitchen Rom in Magical ROM Kitchen
For Section F
ClockWorkMode update.zip
​
Preparations
To begin with, download and extract all these files mentioned above to a convenient location, preferably on your desktop. Once you have all the files in place, launch Odin as administrator. On your device end, make sure that you have disabled any lag fix, if applied earlier.
Ensure that the drivers for your SGS are installed on your computer.
If you have Kies already installed on your machine, the drivers are already in place. If Kies is running shut it down.
Power off your phone.
Put your Galaxy S in download mode by pressing and holding the Volume Down + Home + Power keys at the same time.
You will see a yellow symbol and the words ‘Downloading’ once the phone has gone into download mode. That’s it, we’re ready to begin the flashing sequence.
​
Section A
Before flashing the Speedmod Kernel, put your Kitchen Rom on your internal sd card.
Flashing a Speedmod Kernel Guide here.
When flashing on 2.1, you get stuck on GT-screen, dont worry its normal, just pull battery and enter recovery.
Now go to Section E
​
Section B
Flashing stock firmware
Make sure you don´t have Kies running, and your phone is off, do not connect it now.
1.Start Odin
2.In PIT, load the 512.PIT file.
3.For PDA, select the CODE file.
4.For PHONE, select the MODEM file.
5.For CSC select the CSC file.
6.Make sure that the Re-partition box is checked.
7.Put your phone in download mode. (Volume down + power button + home button )
8.Connect your phone to your PC via the USB cable. It will install the drivers, or if they are already installed, you will see ‘Added’ in Odin’s message box . A COM port will also become visible.
9.Again make sure that all the selections in Odin’s interface are correct. Press the Start button when verified.
The flashing sequence will begin, and you will see several messages in Odin. Make sure that the phone does not disconnect during this time, as it may brick your device permanently. Once the flashing sequence has completed, Odin will give a ‘Completed’ message in the Message box, and a green PASS will appear on top.
Your device will automatically reboot at this point.
Congratulations! You have successfully completed stage one of the process, and now you’re running the XWJM8 or JM9 2.1 Éclair firmware.
Section A is useful if you just want to revert back to factory stock 2.1 (warranty, repairs, etc.)
Now you can do Section A ,D or F
​
Section C
Flashing the update.zip, this is used if you have problems installing your Kitchen Rom
Copy the update.zip (it is a renamed Kitchen Rom Log) to your Internal Sd card.
Shut off the phone and reboot to recovery (Volume UP + Home + Power) and do a FACTORY RESET.
Then choose Install update.zip from the recovery, let it install and reboot. When the phone has booted, shut the phone off and enter recovery (Volume UP + Home + Power) and then choose Install update.zip from the recovery, let it install and reboot.
It´s not a typo you need to do it twice.
All done! Now you have a basic Kitchen Rom containing CWM and all you need to flash a custom ROM.
If you want to stay with this Rom, you can enter the Magical ROM Kitchen and make a update.zip with the apps you want to add, and flash it in cwm. If you want to uninstall something you can do it with Titanium.
Now you can go to Section E
​
Section D
Another way to get to Kitchen Rom from stock 2.1 with 2e recovery, does not work with Stock Froyo 2.2 or 2.2.1.
When you have the apps and the Kernel needed for this Section,
1.Install the apps.
2.Cook your Kitchen Rom and put it on your internal sd card. (see section E how to do that)
3.If you did not download the kernel with your phone,(qr codes in post 2) put it on your internal sd card.
4.Root with Z4Root.
5.Flash the Speedmod Kernel with Sgs Kernel Flasher (only v1.5.9 or newer)(Atm you will get stuck on GT screen due to mismatch between kernel/firmware versions if you try normal booting)
6.Enter recovery
7.Factory reset
8.Install zip from sd card
9.Choose zip from sd card
10.Install the Kitchen Rom
11.Reboot
​
Section E
Flashing a Kitchen Rom if/when you have clockworkmode
Here you have a app guide made by marcedli Xda
And here you have a nice Kitchen walk-trough with screens: Link.
This is the steps you need to do.
1.Place Kitchen Rom on internal sd card
2.Enter recovery
3.Factory reset (if you install new base Rom OR the previous Rom had a voodoo kernel AND you want to wipe)
4.Install zip from sd card
5.Choose zip from sd card
6.Install the Kitchen Rom
7.Reboot
​
Section F
How to get CWM with CWM update.zip (only works in 2e recovery 2.1 Eclair)
1.Place your Kitchen Rom on your internal sd card, that you generated in the Kitchen
2.Place the CWM update.zip on your internal sd card that you downloaded from download Section
3.Power down your phone and enter recovery (Volume up + power button + home button )
4.Choose apply sdcard:update.zip, now you will end up in recovery again, so choose apply sdcard:update.zip and you will have CWM.
5. Now go to Section E step nr 3.
​
If you still have any questions please log in to Kitchen`s Irc support channel. (in irc type !help)
Webchat!
​
Please rate or comment.
​
This guide was made and tested by,
flip360 Xda
Perka Xda
Beerfund
​​

Links and QR codes.
Do you need a file? Perka´s File Stash!
Black Android Theme by Pele78 (imo the best out there!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you need help with modem, csc, and other stuff, please go to Doc´s Irc channel and type !help and you will find what you are looking for, Click this text.
Guide in PDF
Perka´s File Stash
Adobe Reader
Z4Root
Sgs Kernel Flasher
Speedmod Kernel
Credit Goes To The Doc Team!
Do you want free dropbox cloud space? Use this link to sign up and you get 2gig + 250mb space for free (and I get 250mb) Thx.

gday.. just to clarify...does this suggest therefore to flash back to jm8 2.1 prior to flashing to a Doc Rom??
i have asked this in another post, but say for example you are already running another ROM that comes with all the bells & whistles (eg cwm, optional lagfix, root, sgs tools themes etc)..
would the user need to go back to jm8?
cheers

skuzy said:
gday.. just to clarify...does this suggest therefore to flash back to jm8 2.1 prior to flashing to a Doc Rom??
i have asked this in another post, but say for example you are already running another ROM that comes with all the bells & whistles (eg cwm, optional lagfix, root, sgs tools themes etc)..
would the user need to go back to jm8?
cheers
Click to expand...
Click to collapse
If you have problems flashing, use this guide, if you already have cwm recovery and can flash custom roms you dont need to do this guide.

thanks for confirming.!

Can this be used to flash all modded CWM ROMs? I think so. You can check & modify the topic accordingly.

ragin said:
Can this be used to flash all modded CWM ROMs? I think so. You can check & modify the topic accordingly.
Click to expand...
Click to collapse
i think so. We will test this out and give feedback

flip360 said:
i think so. We will test this out and give feedback
Click to expand...
Click to collapse
You mention 502 pit. Did you mean 512 or 503?

ragin said:
You mention 502 pit. Did you mean 512 or 503?
Click to expand...
Click to collapse
yes 512pit file. sorry typo

Huh? Isn't Doc's rom a CWM Rom? You can't flash those as a update.zip can you?

snapper.fishes said:
Huh? Isn't Doc's rom a CWM Rom? You can't flash those as a update.zip can you?
Click to expand...
Click to collapse
Yes Doc`s rom is coupled with CWM yes, but stock 2.1 also. try it

There´s an update coming to you soon from me and flip360
Teaser
http://www.swedroid.se/forum/showthread.php?p=428217#post428217

Updated enjoy.

Sorry, but to quote DocRambone's words:
"Wrong Section to post".
Edit: Thread reported.

Nice guide, thanks!
Is it also valid if you want to upgrade from an older Froyo rom like Doc 6.0 ?
If you start directly from stage 2 beeing on a stock rom, you have recovery 3e which won't let you flash unsigned packages (like the renamed DocRom "update.zip".
Or as I missing something ?

-Loom- said:
Nice guide, thanks!
Is it also valid if you want to upgrade from an older 2.1 rom like Doc 6.0 ?
In Docs own installation guide he stated to install a clean JP9 base before, do the usual CWM install through update.zip etc ..
And if you start directly from stage 2 beeing on a stock rom, you have recovery 3e which won't let you flash unsigned packages (like the renamed DocRom "update.zip".
Or as I missing something ?
Click to expand...
Click to collapse
If you are on a Doc rom do stage 3.
2.1 has 2:e recovery so it can flash unsigned zips.
Does not work if you have 3e recovery.

Doc advised to install a clean JM9 base rom before upgrading to a romkitchen rom.
But in stage 3 you wrote to just install the kitchen rom from CWM. Regardless what DocRom was in use before ?

-Loom- said:
Doc advised to install a clean JM9 base rom before upgrading to a romkitchen rom.
But in stage 3 you wrote to just install the kitchen rom from CWM. Regardless what DocRom was in use before ?
Click to expand...
Click to collapse
yes my good man

flip360 said:
[FONT=Book Antiqua, serif]For Stage 2[/FONT]
[FONT=Book Antiqua, serif]The renamed Doc Rom [/FONT][FONT=Book Antiqua, serif](update.zip) [/FONT][FONT=Book Antiqua, serif]Log file[/FONT]
[FONT=Book Antiqua, serif]Samsung USB Drivers.[/FONT]
[FONT=Book Antiqua, serif]Driver x64[/FONT]
[FONT=Book Antiqua, serif]Driver x86[/FONT]
Click to expand...
Click to collapse
Got these drivers package ... But which one is used for my SGS on W7 x64 please ? It doesn't find it by istself ?

Wendigogo said:
Got these drivers package ... But which one is used for my SGS on W7 x64 please ? It doesn't find it by istself ?
Click to expand...
Click to collapse
the x64 one, i think it does throught win driver management.

[REQ] Stock Kernel 2.3.4

can anybody deliver the stock 2.3.4 kernel as an image to reflash via recovery if one wants to go back from a custom kernel?
would be easier, than using an old backup or reflash the whole ROM due to lost data, apps, sms, etc.

Second to that....maybe someone can help us.
Best Regards

Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.

evlevl said:
Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.
Click to expand...
Click to collapse
do a nandroid backup. it saves kernels

Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .

Bandis710 said:
Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .
Click to expand...
Click to collapse
excellent, thanx mate! i don't want to flash a whole rom just to get back on stock kernel, because all the backing up and restoring if not necessary is boring...
and does that really set back all changes, a custom kernel does on my phone? aren't there also always some folders in the zip-files of customs?

Well, now I see a reason why there is no "default kernel".
It's because all these custom kernels consist not only from "boot.img", but also from a number of "init.d scripts", "*.so modules", etc, which are obviously different from kernel to kernel. So because of that you cannot have an universal "stock" kernel, but rather a whole stock ROM.
Thanks a lot for all of you who comment that request, now the situation with kernels is more clear.

While all the above is sensible, it should be possible with a modicum of planning to go back and forth between a custom kernel and the stock one. I feel the question is more: is it worth the trouble versus flashing again? Probably not.
1 - Nandroid backup.
2 - Examine the scripts and files included in the custom kernel's zip.
3 - Back up what is replaced, patched or deleted outright from stock.
4 - Note what is added by the custom kernel.
When you want to revert to stock, reflash boot.img from stock, and either adb push the stock backup files back, or create your own update zip with a proper script to finish the job.

Kernel/bootloader/recovery

Hi guys,
1. What is the advantage/disadvantage of flashing a custom kernel?
2. I recently flashed Cyanogenmod. It automatically installs a custom kernel right?
3. Using the Nexus 7 toolkit I reverted my N7 to stock recovery (from CWM) How should I make sure that it's been reverted to the latest stock version?
4. What does N7's stock factory image contain? (Stock ROM + Stock recovery + Stock kernel?) (found here: https://developers.google.com/android/nexus/images)
5. Is this correct? You can install a custom ROM without changing the kernel but in order to have more customization you have to flash a different kernel than the stock one.
6. Is this the correct order? Unlocking bootloader>rooting>Flashing custom recovery>Flashing custom kernel>Flashing custom ROM>...?
7. Difference between unlocking bootloader and rooting.
8. How to find out N7's latest stock kernel version.
Many thanx
Sent from my Nexus 7 using Tapatalk 4 Beta

valapsp said:
1. What is the advantage/disadvantage of flashing a custom kernel?
Click to expand...
Click to collapse
Same as those for a stock kernel. That is to say, every kernel has advantages and disadvantages. Some trade performance for battery life, others do the reverse. Some are more feature-heavy and potentially more unstable, others are feature-light but designed to be rock solid. With custom kernels on a Nexus device, you avoid one of the biggest dangers of custom kernels (instability due to lack of kernel source for developers to base their work on), but you still need to be careful. You don't necessarily know how proficient the author of a given kernel is, and the wrong one can make your device unusable/kill it.
valapsp said:
2. I recently flashed Cyanogenmod. It automatically installs a custom kernel right?
Click to expand...
Click to collapse
I believe it does. I don't remember which one though, since I don't use CM.
valapsp said:
3. Using the Nexus 7 toolkit I reverted my N7 to stock recovery (from CWM) How should I make sure that it's been reverted to the latest stock version?
Click to expand...
Click to collapse
You need to be more specific-- the latest stock ROM, or the latest stock recovery? If you're wondering about the ROM, you can check in Settings > About tablet > Status. When it comes to determining recovery version, I'm not so sure.
valapsp said:
4. What does N7's stock factory image contain? (Stock ROM + Stock recovery + Stock kernel?) (found here: https://developers.google.com/android/nexus/images)
Click to expand...
Click to collapse
I believe it contains stock ROM and kernel.
valapsp said:
5. Is this correct? You can install a custom ROM without changing the kernel but in order to have more customization you have to flash a different kernel than the stock one.
Click to expand...
Click to collapse
Generally correct. There's a subset of features that are kernel-dependent, not ROM dependent, so you should think of it as ROM customizations vs. kernel customizations. Some examples of the former include PIE menus and Paranoid Android's Halo feature. Examples of the latter might include tap2wake (double tap on a powered-off screen to turn it on), NTFS drive support for OTG, and so on.
valapsp said:
6. Is this the correct order? Unlocking bootloader>rooting>Flashing custom recovery>Flashing custom kernel>Flashing custom ROM>...?
Click to expand...
Click to collapse
Yes and no? It's one way of going about it, save for the last two things, which should be reversed. Since some ROMs include custom kernels, flashing a kernel and then a ROM runs the risk of having your kernel choice overwritten.
If all you need to do is flash a different ROM, you can go straight form unlocking the bootloader to flashing a recovery. You can also flash ROMs and kernels independently, so long as whatever kernel/ROM you're running initially doesn't have known incompatibilities with your new ROM/kernel.
valapsp said:
7. Difference between unlocking bootloader and rooting.
Click to expand...
Click to collapse
Unlocking your bootloader is like getting the key to a house. Rooting is getting permission from the landlord to do whatever the heck you want to the house. A locked bootloader means that the device is checking to ensure no unauthorized code is running at boot time, which prevents custom recoveries from being installed. Rooting only really matters when the device is booted up.
valapsp said:
8. How to find out N7's latest stock kernel version.
Click to expand...
Click to collapse
Google. Sorry, can't help you with this one.

That was a great answer @Rirere

Rirere said:
Same as those for a stock kernel. That is to say, every kernel has advantages and disadvantages. Some trade performance for battery life, others do the reverse. Some are more feature-heavy and potentially more unstable, others are feature-light but designed to be rock solid. With custom kernels on a Nexus device, you avoid one of the biggest dangers of custom kernels (instability due to lack of kernel source for developers to base their work on), but you still need to be careful. You don't necessarily know how proficient the author of a given kernel is, and the wrong one can make your device unusable/kill it.
I believe it does. I don't remember which one though, since I don't use CM.
You need to be more specific-- the latest stock ROM, or the latest stock recovery? If you're wondering about the ROM, you can check in Settings > About tablet > Status. When it comes to determining recovery version, I'm not so sure.
I believe it contains stock ROM and kernel.
Generally correct. There's a subset of features that are kernel-dependent, not ROM dependent, so you should think of it as ROM customizations vs. kernel customizations. Some examples of the former include PIE menus and Paranoid Android's Halo feature. Examples of the latter might include tap2wake (double tap on a powered-off screen to turn it on), NTFS drive support for OTG, and so on.
Yes and no? It's one way of going about it, save for the last two things, which should be reversed. Since some ROMs include custom kernels, flashing a kernel and then a ROM runs the risk of having your kernel choice overwritten.
If all you need to do is flash a different ROM, you can go straight form unlocking the bootloader to flashing a recovery. You can also flash ROMs and kernels independently, so long as whatever kernel/ROM you're running initially doesn't have known incompatibilities with your new ROM/kernel.
Unlocking your bootloader is like getting the key to a house. Rooting is getting permission from the landlord to do whatever the heck you want to the house. A locked bootloader means that the device is checking to ensure no unauthorized code is running at boot time, which prevents custom recoveries from being installed. Rooting only really matters when the device is booted up.
Google. Sorry, can't help you with this one.
Click to expand...
Click to collapse
First of all many many thanx to you because of your help. Yes I meant stock RECOVERY in question 3 also the way you explained question #7 is awesome.
Now I'm running stock ROM on CWM recovery and Franco kernel. My question is that will I be able to upgrade to Android 4.3 with this recovery and kernel? Or I have to flash the stock kernel or stock recovery or both?
Also how can I extract the stock kernel from the factory stock image file?
Thanx again.

valapsp said:
First of all many many thanx to you because of your help. Yes I meant stock RECOVERY in question 3 also the way you explained question #7 is awesome.
Now I'm running stock ROM on CWM recovery and Franco kernel. My question is that will I be able to upgrade to Android 4.3 with this recovery and kernel? Or I have to flash the stock kernel or stock recovery or both?
Also how can I extract the stock kernel from the factory stock image file?
Thanx again.
Click to expand...
Click to collapse
The OTA updates are normally only applied to the rom/system, so in theory you should be able to just run the OTA update with the stock rom, the worst that would mainly happen is losing rooting because the system partition gets replaced with a fresh install of the newest operating system (but your /data retains your settings and user data).
I use TWRP recovery instead of CWM, and TWRP when you're bout to exit it will detect if your system has Supersu or not and will offer to install it for you (from there once you boot into the system you can use it to install the su binary for you thus re-rooting).
In the end it's a personal choice. With custom roms like I'm using, there's no real "OTA" update (just a notice that the rom creators use to notify you of new versions which are downloaded to the device, and you just reboot into recovery to flash them). Custom roms typically get updated a few days to a few weeks after google updates if they're AOSP based.
The stock kernel would normally be the boot image, I don't know how you would do it with clockwork mod, but in TWRP you can simply make a backup of the boot partition to retain the original stock kernel. (It will of course only work on AOSP-based roms if you choose to just flash the stock kernel, but the ones that are made for the rom, or custom kernels tend to offer optimizations over the original stock one).

Thanks, I meant extracting the stock kernel from factory image file found here:
https://developers.google.com/android/nexus/images
By the way I don't have the stock kernel anymore to back it up.
Sent from my Nexus 7 using Tapatalk 4 Beta

valapsp said:
Thanks, I meant extracting the stock kernel from factory image file found here:
https://developers.google.com/android/nexus/images
By the way I don't have the stock kernel anymore to back it up.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ahh I see, well if your's is the Wifi-only version then would be something like this https://developers.google.com/android/nexus/images#nakasijdq39
The firmwares are basically gzipped tarballs (in a linux system tar zxvf would normally unpack em, otherwise 7zip for windows does a good job of unpacking it into a folder).
Alternatively you can just download the kernel itself (Post #3) http://forum.xda-developers.com/showthread.php?t=2151154
Edit: Yes if you un-gzip/untar the original firmware, then unpack image-nakasi-jdq39.zip inside of that, there will be a boot.img that's where the kernel lives. The boot.img can be flashed via fastboot to the boot partition (I'd advise reading up on this first before actually doing it). Though like linked above, there are some recovery-flashible versions of the stock kernel you can use instead.

kbeezie said:
Ahh I see, well if your's is the Wifi-only version then would be something like this https://developers.google.com/android/nexus/images#nakasijdq39
The firmwares are basically gzipped tarballs (in a linux system tar zxvf would normally unpack em, otherwise 7zip for windows does a good job of unpacking it into a folder).
Alternatively you can just download the kernel itself (Post #3) http://forum.xda-developers.com/showthread.php?t=2151154
Edit: Yes if you un-gzip/untar the original firmware, then unpack image-nakasi-jdq39.zip inside of that, there will be a boot.img that's where the kernel lives. The boot.img can be flashed via fastboot to the boot partition (I'd advise reading up on this first before actually doing it). Though like linked above, there are some recovery-flashible versions of the stock kernel you can use instead.
Click to expand...
Click to collapse
thanks, I actually did unzip the stock firmware seconds ago and was posting the results then I saw your edit.
Just there are some confusions here: what is that userdata.img? also what is bootloader-grouper-4.18.img

valapsp said:
thanks, I actually did unzip the stock firmware seconds ago and was posting the results then I saw your edit.
Just there are some confusions here: what is that userdata.img? also what is bootloader-grouper-4.18.img
Click to expand...
Click to collapse
bootloader img would be the original stock bootloader for the Nexus 7, chances are you never replaced it, you only unlocked it. There's usually no reason to replace the bootloader with a custom one since all you need to do is unlock it.
userdata.img would be the /data partition. The firmware download basically has a image for all of the partition in the original out-of-the-box stock state. Technically you don't even to flash it, as long as you wiped /data before rebooting (since that would be the same as a clean install if you instead flashed the system and boot partition).
Edit: If I were messing with it to get back stock rom (but not messing with recovery, cuz custom recovery is still handy to have), I would only flash the boot.img and system.img , then log into Recovery and wipe data (ie: factory reset which wipes cache and /data but doesn't touch /data/media), Then I would be able to reboot into a clean stock install of the rom.
(from there I could just make a backup from recovery so I wouldn't have to do a fastboot flash again).

kbeezie said:
The OTA updates are normally only applied to the rom/system, so in theory you should be able to just run the OTA update with the stock rom, the worst that would mainly happen is losing rooting because the system partition gets replaced with a fresh install of the newest operating system (but your /data retains your settings and user data).
I use TWRP recovery instead of CWM, and TWRP when you're bout to exit it will detect if your system has Supersu or not and will offer to install it for you (from there once you boot into the system you can use it to install the su binary for you thus re-rooting).
In the end it's a personal choice. With custom roms like I'm using, there's no real "OTA" update (just a notice that the rom creators use to notify you of new versions which are downloaded to the device, and you just reboot into recovery to flash them). Custom roms typically get updated a few days to a few weeks after google updates if they're AOSP based.
The stock kernel would normally be the boot image, I don't know how you would do it with clockwork mod, but in TWRP you can simply make a backup of the boot partition to retain the original stock kernel. (It will of course only work on AOSP-based roms if you choose to just flash the stock kernel, but the ones that are made for the rom, or custom kernels tend to offer optimizations over the original stock one).
Click to expand...
Click to collapse
Unfortunately, how many times does should matter? Theoretically, you should be able to do OTAs while rooted by downloading the ZIP and flashing in recovery, but if you've made changes to /system (uninstalling a system app, or adding a helper), you might get the stupid script_assert error. Of course, you could just push the whole /system back to your device...although that can be just as annoying.
I wish there were away to turn off the script_asserts safely, but they do exist for a reason.

@valapsp
Small but important clarification.
valapsp said:
5. Is this correct? You can install a custom ROM without changing the kernel but in order to have more customization you have to flash a different kernel than the stock one.
Click to expand...
Click to collapse
Essentially 100% of custom ROMs install a kernel. (Actually, a kernel plus a ramdisk packaged together as a single ("bootable image") file, typically named "boot.img".) So your preexisting boot image containing the kernel is always overwritten during a ROM installation. See next answer.
valapsp said:
6. Is this the correct order? Unlocking bootloader>rooting>Flashing custom recovery>Flashing custom kernel>Flashing custom ROM>...?
Click to expand...
Click to collapse
Almost, but not quite. If you want to use a different kernel than what ships with a given ROM, you flash it after you have installed the ROM, not beforehand. See prior answer.
One more thing. Since you are new to this stuff, I'll make a suggestion:
Learn how to create and restore full Nandroid backups (using the custom recovery) immediately. And get in the habit of copying them off your tablet to your PC. You will thank me later for this advice.
have fun

Rirere said:
Unfortunately, how many times does should matter? Theoretically, you should be able to do OTAs while rooted by downloading the ZIP and flashing in recovery, but if you've made changes to /system (uninstalling a system app, or adding a helper), you might get the stupid script_assert error. Of course, you could just push the whole /system back to your device...although that can be just as annoying.
I wish there were away to turn off the script_asserts safely, but they do exist for a reason.
Click to expand...
Click to collapse
Hi, Rirere...
This is my understanding as well... (sort of! - I've always been a bit hazy on this topic).
My take on it is this...
The OTA would only fail, if it found files in /system that SHOULD BE THERE, but have been removed, modified, or replaced by the user (or via some app run by the user).
Logically (one would think), the OTA can't check for files THAT SHOULDN'T BE THERE (How would it know what to look for?) but have been ADDED by the user... like the su binary that confers root.
So, an OTA on pure ROOTED (but in all other regards, unadulterated) stock you would expect to succeed... you'd just lose root (and from what I've read elsewhere, your Custom Recovery). Both of which are trivial to recover.
Is my understanding correct... or have I missed something?
Rgrds,
Ged.

GedBlake said:
Hi, Rirere...
This is my understanding as well... (sort of! - I've always been a bit hazy on this topic).
My take on it is this...
The OTA would only fail, if it found files in /system that SHOULD BE THERE, but have been removed, modified, or replaced by the user (or via some app run by the user).
Logically (one would think), the OTA can't check for files THAT SHOULDN'T BE THERE (How would it know what to look for?) but have been ADDED by the user... like the su binary that confers root.
So, an OTA on pure ROOTED (but in all other regards, unadulterated) stock you would expect to succeed... you'd just lose root (and from what I've read elsewhere, your Custom Recovery). Both of which are trivial to recover.
Is my understanding correct... or have I missed something?
Rgrds,
Ged.
Click to expand...
Click to collapse
I believe you are correct! Theoretically, the script could rather easily check for added files by checksumming the entire /system partition before running the update (using a fast hash algorithm-- you're only looking for the presence of any changes, afterall). And I did have one OTA that went fine, other than losing root back on my Galaxy Nexus.
Again though, it's a classic case of should versus real life. Some root methods might alter things in /system without your knowing, or root actions might alter permissions. Either way, it's a tricky, nasty little game.
So far as recoveries go: yeah, OTAs have a nasty habit of trying to do that. Some of the more advanced recoveries can resist being overwritten though/slipstream a root ZIP into the update process.

GedBlake said:
The OTA would only fail, if it found files in /system that SHOULD BE THERE, but have been removed, modified, or replaced by the user (or via some app run by the user).
Click to expand...
Click to collapse
Typically the OTAs also update the boot image, so the boot partition (LNX) is also checked. The stock recoveries almost always use the same kernel (with a different ramdisk) as the boot image, so they are usually rewritten too.
Owners of tilapia N7 devices have reported successful flashing of everything but radio firmware images when they used a custom recovery to process the OTA bundle. Not a disaster, as their devices will still function with old radio firmware, but it puts them in an unusual position of being unable to use the OTA to subsequently update the radio, even if they restore the stock recovery (the system files and boot images will have been changed, so almost all of the checksums will fail). At that point, using fastboot is an alternate option, but then the newbs will need to read about OTA images, unpack them, yadda yadda yadda.
IMO it is just a dumb idea applying OTAs to anything but a pure stock device. And when I say pure stock, I mean including the stock recovery. The boot loader can be left unlocked, but that's about it.
There are a lot of ways to skin the cat, but IMO the best way to proceed is to operate with two parallel but independent tracks of Nandroid backups/restores: one track is a sequence of pure stock, and the other your customized ROM du jour.
Let's presume you have a Nandroid backup of the pure stock ROM. Make a backup of your current (customized) ROM & get it copied off the tablet (in the event of a disaster), restore the pure stock ROM nandroid backup, flash the stock recovery back to the tab, and then take the OTA.
At this point:
[ unlocked bootloader ] soft-boot (no flashing) a custom recovery using fastboot, and then make yet another Nandroid backup of the newly updated stock ROM including the recovery image. (This becomes the new baseline for future OTAs)
[ locked bootloader ] re-root with motochopper, capture the (new) stock recovery partition using 'dd', flash a custom recovery ('dd' or other method), make a Nandroid of this. (These two backups become the new baseline for future OTAs)
Then, repeat any rooting customizations (if you are a "lightly customized rooted stock" kinda person), and restore apps (Market apps only!) with TiBu.
This may seem like a great deal of work, but it is the only way to insure that you can revert to a prior starting position. Look: after going down a road like this you can even restore the old customized ROM backup to make TiBu app backups after the fact, simply because you can return to any point in time if you have made a backup (and kept a copy of it off the tablet).
Everybody makes mistakes - even the experts. But the lazier folks are (read: toolkit user) the more likely is a disaster. Everybody needs to make backups.

What will happen if I change some values in build.prop editor? I won't be able to install stock ROMs anymore? Or what?
Sent from my Nexus 7 using xda app-developers app

valapsp said:
What will happen if I change some values in build.prop editor? I won't be able to install stock ROMs anymore? Or what?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Depends on how you mean "install", you can always install via .img or recovery flashing method, but course that will overwrite your build.prop with the provided version and you would just have to re-edit the values again.
Did you mean OTA wise? If the update doesn't check for the hash of the build.prop, it will likely just replace it with a newer version if anything has changed from the last version to the new version.
As others have said, worse case scenario, the OTA fails to proceed due to errors and you would just have to manually update it yourself, as you could just flash a new boot.img and system.img from google's site (just have to remember anything you added on top of system or custom kernels will of course be reverted, so they will need to be reapplied).
Settings and user apps and such all live in /data , so it should just simply boot up as an upgraded system but with everything else intact (course I always make a backup via my custom recovery just in case).

kbeezie said:
Depends on how you mean "install", you can always install via .img or recovery flashing method, but course that will overwrite your build.prop with the provided version and you would just have to re-edit the values again.
Did you mean OTA wise? If the update doesn't check for the hash of the build.prop, it will likely just replace it with a newer version if anything has changed from the last version to the new version.
As others have said, worse case scenario, the OTA fails to proceed due to errors and you would just have to manually update it yourself, as you could just flash a new boot.img and system.img from google's site (just have to remember anything you added on top of system or custom kernels will of course be reverted, so they will need to be reapplied).
Settings and user apps and such all live in /data , so it should just simply boot up as an upgraded system but with everything else intact (course I always make a backup via my custom recovery just in case).
Click to expand...
Click to collapse
Thanks, and does backing up thru cwm also back up the build.prop?

valapsp said:
Thanks, and does backing up thru cwm also back up the build.prop?
Click to expand...
Click to collapse
Yes, but not in the way you're thinking. If you back up the whole system, CWM will package each partition up (/system /data , etc), so when you flash a new rom or system on, you can't just selectively restore build.prop since restoring in CWM Would also restore the entire system partition.
You can while in recovery, mount /system and do something like
adb pull /system/build.prop , and save a copy of it on your computer, so you can go back in and change the affected values back if for some reason you needed to.
If you're familiar with ghosting, nandroid backups (what CWM and most others do, minus some variations), are basically exact clones of all the files on each partition. Older recoveries actually took an image snapshot, newer ones basically pack all the files in a compressed archive (With some kind of note of what partition type it was, ext4, etc). The latter can easily be unpacked with tar, or 7zip, etc, but disk images are a different matter.
I can't remember which one CWM does exactly since on my DZ I use 4EXT, and on my Nexus devices I use TWRP.

kbeezie said:
Yes, but not in the way you're thinking. If you back up the whole system, CWM will package each partition up (/system /data , etc), so when you flash a new rom or system on, you can't just selectively restore build.prop since restoring in CWM Would also restore the entire system partition.
You can while in recovery, mount /system and do something like
adb pull /system/build.prop , and save a copy of it on your computer, so you can go back in and change the affected values back if for some reason you needed to.
If you're familiar with ghosting, nandroid backups (what CWM and most others do, minus some variations), are basically exact clones of all the files on each partition. Older recoveries actually took an image snapshot, newer ones basically pack all the files in a compressed archive (With some kind of note of what partition type it was, ext4, etc). The latter can easily be unpacked with tar, or 7zip, etc, but disk images are a different matter.
I can't remember which one CWM does exactly since on my DZ I use 4EXT, and on my Nexus devices I use TWRP.
Click to expand...
Click to collapse
Thanks, an easier way is to copy the build.prop thru a file manager.
But since I'm on my geek mood today I wanna know if it's possible to extract the backed up (Nandroid) file and find the build.prop somewhere there.
Sent from my Nexus 7 using xda app-developers app

valapsp said:
Thanks, an easier way is to copy the build.prop thru a file manager.
But since I'm on my geek mood today I wanna know if it's possible to extract the backed up (Nandroid) file and find the build.prop somewhere there.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If it's a backup done with 4EXT or TWRP most certainly since it's just a tarball package (or tar+gzipped if you enabled compression) and can be easily unpacked by tar, or any popular archive utility like 7Zip for windows. (restoration generally just looks at the file info to see what partition type it's supposed to be, formats the partition as such, and then just un-tars the content, with the permissions and such retained).
If it's older where it's an actual jaffs (may have spelled that wrong) disk image, I'm not sure off the top of my head how you would mount it as a disk , and then mount the ext4 or ext3 partition in order to get to it. I would assume ClockworkMod would have upgraded their backup method to the same as TWRP or 4EXT, but it's possible that they didn't for compatibility reasons.

[Tutorial] How to flash Jelly Bean on Samsung Korean Galaxy S / SHW-M110S

How to upgrade from Gingerbread WF07 to a Jelly Bean ROM on the SHW M110S
Basic Considerations that will help you to restore your current ROM ​
First make a Backup of your current ROM, such that you can return to it, IF the Jelly Bean ROM is not what you expected it to be. How?
a) When Using a tegrak Kernel on the M110S , you can get this done on the bootup screen , by entering it and making a system and also a dbdata/data backup of your phone, which can be restored by using the terak kernel again IF WF07 ROM is what suits you best.
Your backup will be placed in the Tegrak Folder in the Internal SD card...so save this to your PC or external SD card for safe keeping.
b) When using a Speedmod kernel, you need to enter recovery first to make a nandroid backup of your system and data
Your Backup will be placed in the ClockWorkMod Folder of your SD card. Which can be restored by using the speedMod kernel again IF WF07 ROM is what you desire.
None of these Kernels can be used for Jelly Bean ROM, and you need to use a Version 5 CWM (ClockWorkMOD) recovery, to flash the Jelly Bean or ICS ROM direct from your SD card...as such the first thing you need to do is change the Recovery on your M110S to a version 5 ClockWorkMOD.
Second Backup your efs folder, why? read this. How? read this
What you should know about this Jelly Bean ROM on the M110S​
a) It may take from 3 to five minutes for the ROM you flashed to stabilze, so try to be patient or you will have a non responsive phone in your hands, even when the ROM is stable.
b) When ever certain functions do not seem to work initially...like unable to connect to your WIFI, network etc just reboot phone.
c) Poor response may be due to settings or permissions that need to be fixed, which can be done on your settings menu or in the advanced menu of your recovery ...so you must have ample knowledge of the numerous features the Jelly Bean settings menu has.
The Jelly Bean ROM's for Korean Galaxy S (SHW M110S) that have little to NO issues at the moment are​
Common Issue in Jelly Bean being having NO Ringtone only vibration
Typhoonoid aokp verion 2.1.2 or here
Typhoonoid paranoid version 1.1
CM 10 All Fixed
Provisionmod All Fixed
JBean 4.2 under construction here only for testers to verify bugs
Reminder, What you do with your Phone is your own responsibility, so do it at your own risk. Always ensure your Battery is fully Charged prior to flashing any phone​
This is the basic procedure for Jelly Bean upgrade​​
1) Download the CWM Recovery.tar ( Attached below), the ROM's come in .zip format ( it can be as many as you wish, for you to test them out, one after the other) and Place them in a Folder (create and name it as you wish) on your SD Card Also Download the Gapps.zip (Google apps) File that need to be flashed after flashing the ROM. ( So it will always be two packages to flash, in order to get your phone functioning)
Download:-
a) CWM Version 5.0 Recovery attached below
b) Rom of your choosing from here or here or here Zip file includes ROM & Kernel (do not unzip)
c) Gapps Here (do not unzip)
d) Ringtone Fix here (Tested not working on M110S)
e) New 4.1.2 Kernel use Odin to flash when using older ROM
2) Flash the version 5 and up CWM recovery on your Phone, How?
Put your phone into download mode, Fireup Odin3 on your PC, connect to Odin3 with USB cable, select CWM Ver.5.0 recovery.tar under PDA and Flash it. Ensure you do not reboot the phone by "UNTICK" reboot in Odin3 such that it will not power ON after Flashing, in case it does power ON, just pull out Battery , press power button for 30 seconds and insert battery again
3) After flashing recovery with Odin, You can enter " Recovery Mode" by press VolumedownKey+PowerKey+HomeKey. You do this every-time you want to switch to a JellyBean or iCS ROM or to utilize the many features this recovery has, like Backup/restore/fix permissions and mostly to do the full wipes (NEEDED to be done every time you want to SWITCH ROMS) etc
4) Once in CWM Recovery you do the Full wipes (use your volume keys to move up or down in the recovery menu to select and the power key to execute that command).
The undermentioned wipes need to be done and will constitute a FULL Wipe of your Phone but your SD card will not be fully formatted as such your Images and other non system files will remain as is.
a) Wipe data / Factory reset
b) Wipe cache
c) Enter advanced and wipe dalvic Cache
Once the full wipes are done,
5) You now choose the ROM you placed in your SD card by selecting "Install zip from sdcard" which will lead you to "choose zip from sdcard", which will take you to all the folders you have on your SD Card..scroll down to where you placed the downloaded files and select it
Once selected the ROM will be Flashed on to your phone, so wait till it says "install completed" Now you do the same selection process again (Step 5) to select the Gapps file and wait till it says "Install completed"
6) That's it, Now select "Reboot system Now".
Now the ROM has been installed on your phone, so let it boot up and you can repeat this procedure to switch again and again till you have the best ROM of your choosing.
Solutions to solve problems, if any
In the event that it fails to boot-up or you placed a wrong ROM that caused a boot loop or any other problem, just look in My Android Solutions , IF you cannot enter Recovery mode to flash another ROM.
or ​
You can also use Odin3 to Flash a Gingerbread ROM in Download mode and use your First backup ( made by Tegrak or speedMod) to return your phone to its original state.
Ringtone Codec from this post unfortunately it seems to fail in fixing the Ringtone issue but no harm done in installing this codec
atrix4g18 said:
This is the fix for Audio/Sound on any Jelly Bean ROM on any device.
JB needs this file "/system/etc/media_codecs.xml"
This file is missing, but simply copying the file there using Root Explorer or any file explorer with root access works. This does not require a permissions change. The file is not there originally so you won't be overwriting anything. I did this fix on my Atrix 4G and it worked perfectly. It is universal and will work on any Jelly Bean ROM on any device with this issue.
Here is a link to the file:
http://forum.xda-developers.com/attachment.php?attachmentid=1207669&d=1342668760
Steps:
- Extract "media_codecs.xml"
- Copy it to /system/etc/
- Make sure to mount system as R/W (read/write) before pasting the file
- Reboot
- Sound Fixed!
Click to expand...
Click to collapse
Final Advice
IF you like the ROM you had just installed and after doing all the tweaks and adjustments you would like to try another ROM, just get back into your CWM recovery , scroll down to "backup and restore" and back it up. Such that you can restore it, if your next selection is below expectations. or you wish to tweak it further at some other time. You can have many ROM's backed up and restored whenever you like...just remember on what date you backed it up.
You , YES! you are an " Android ".
You Must watch this documentary concerning your privacy Terms & Conditions we agree to
If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Screen Shots of Typhoonoid aokp

Screen Shots of Paranoid

Typhoonoid by ODIN? Tegrek after Typhoonoid?
oh my god, your post is amazing. thank you thank you!
Question:
your post suggests using CWM Version 5.0 to do the ROM flashing. can i use just ODIN to flash Typhoonoid? or do i have to use CWM?
also, i believe that Tegrek kernel only supports stock ROM on the M110S, which is gingerbread. after flashing Typhoonoid, is it possible to flash Tegrek kernel again? can Tegrek lagfix be applied to Typhoonoid?

md11980 said:
oh my god, your post is amazing. thank you thank you!
Question:
your post suggests using CWM Version 5.0 to do the ROM flashing. can i use just ODIN to flash Typhoonoid? or do i have to use CWM?
also, i believe that Tegrek kernel only supports stock ROM on the M110S, which is gingerbread. after flashing Typhoonoid, is it possible to flash Tegrek kernel again? can Tegrek lagfix be applied to Typhoonoid?
Click to expand...
Click to collapse
Nope, you MUST use the Version 5 CWM recovery to flash ICS or Jellybean ROM's and Nope you cannot use tegrak anymore, and lag fix (sort of ) can be done with seeder app already included in the ROM

soft bricked
xsenman said:
Screen Shots of Paranoid
Click to expand...
Click to collapse
My phone turned to Upgrade Boot Logo after failed flashing of CWM 5.0 in my phone, is there a solution for this?

asukaragnaboy said:
My phone turned to Upgrade Boot Logo after failed flashing of CWM 5.0 in my phone, is there a solution for this?
Click to expand...
Click to collapse
means still in download mode and needs a full flash of ROM or Kernel or recovery you had earlier attempted to flash
upgrade screenshot http://forum.xda-developers.com/attachment.php?attachmentid=2147778&d=1374970741

On provisionmod ram swap is not working is there any cm 10 with swap support
Please can i get lidroid rat9 wc13 screenshots.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
On provisionmod ram swap is not working is there any cm 10 with swap support
Please can i get lidroid rat9 wc13 screenshots.
Click to expand...
Click to collapse
Not too sure, the others can achieve swap support, but give it a try, it pretty easy to change ROMS and test out, which can do what lidroid screen shots may be on their website here http://bbs.lidroid.com/forum.php?mod=viewthread&tid=110092&highlight=lidroid+wc13

http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Please tell me this rom is for m110s because in all roms its written galaxy s no model no it's quite confusing.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Please tell me this rom is for m110s because in all roms its written galaxy s no model no it's quite confusing.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
yup, it works, seems there was a ver 5 too..but ver 2 was much smoother, anyways you should test it out, since my trials where way too short and incomplete

xsenman said:
yup, it works, seems there was a ver 5 too..but ver 2 was much smoother, anyways you should test it out, since my trials where way too short and incomplete
Click to expand...
Click to collapse
Sorry for asking again but i want a cm 7.2
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/[Fixed] [GALAXY S] Typhoonoid Aokp Ver. 4.1.zip
Is this cm 7.2 is this rom has bugs
Please tell the bugs.
Thanks for helping bro.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
Is this cm 7.2 is this rom has bugs
Click to expand...
Click to collapse
NO. its ver 4.1, meaning Jelly Bean, CM 7.2 is gingerbread/ICS combo, try looking in the links given in OP, you need to go into their parent directory and it will clearly state CM 7.2. CM 9 would be ICS , CM 10 would be Jelly Bean.
unfortunately I Have not tested them , so unable to tell you the bugs in each of them.

Oops i am sorry posted wrong link.
I know that that cm 10 is jb and 9 ics
http://main.develoid.com:82/samsung/Galaxy/Galaxy S/Sayanogen/M110S CM7.2(TOUCHWIZ4.0).tar
This is cm 7.2 touchwiz 4 tar want to know bugs.
Thanks in advance.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
This is cm 7.2 touchwiz 4 tar want to know bugs.
Thanks in advance.
Click to expand...
Click to collapse
like i said earlier , have little knowledge about its current development or bugs, as far as I know, they stopped short of fixing bugs when CM 10 came into the picture. So best you test it out.
visit PIT STOP for 7.2 version 3 plus guide (click on original post to see screenshots and latest info) and 7.2 perfect version download from here

It means there are no bugs in 7.2cm sms fixed.zip
And there is swap support.
Sent from my GT-I9070 using xda app-developers app

shaikhsumair99 said:
It means there are no bugs in 7.2cm sms fixed.zip And there is swap support.
Click to expand...
Click to collapse
I hope so, that's what perfect should mean but may mean different in Korea so check it out.

xsenman said:
I hope so, that's what perfect should mean but may mean different in Korea so check it out.
Click to expand...
Click to collapse
Thanks for support.
Just one thing I have to flash cm7finalkernel.tar and gapps also.
There are 2 kernel tar files cm7.2oc.tar something like that help.
So there is no kernel in the zip.
Or these kernel have special features.
Thanks.
Sent from my GT-I9070 using xda app-developers app

hey bro. i'm just a little confused, what kernel should i use for a jellybean rom?

shaikhsumair99 said:
Thanks for support.
Just one thing I have to flash cm7finalkernel.tar and gapps also.
There are 2 kernel tar files cm7.2oc.tar something like that help.
So there is no kernel in the zip.
Or these kernel have special features.
Thanks.
Click to expand...
Click to collapse
looks like provision made a new kernel even for Jellybean, so it can flashed using odin3 after flashing ROM & gapps. oc means its an overclocked version
swiftcity1305 said:
hey bro. i'm just a little confused, what kernel should i use for a jellybean rom?
Click to expand...
Click to collapse
you use the one that is included in the ROM package. and can be updated with new version of that kernel later, you cannot use gingerbread kernels like (tegrak or speedmod)

[Q] Backup Kernel How To question

Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,

youpiyo said:
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
Click to expand...
Click to collapse
What type of ROM are you using? You have to be using a compatible kernel. AOSP ROM's won't work with a stock kernel, and you can't cross Android version between system and kernel. Using any custom kernel developed for your phone with this guide will work okay however.

Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?

youpiyo said:
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
Click to expand...
Click to collapse
My best guess is find out which partition it is and use the dd command OR download the ODIN of your firmware version and extract the boot.img. However, it would be easier to just use a custom kernel designed for your phone as if you back it up like that you either have to make it into a flashable zip or use heimdall to restore it every time.
Sent from Black<3's I337 running Foxhound ROM

Thanks for your answer.
That's weird as a nandroid is doing the job,that is hard to find how to backup a kernel.
anyway, I guess my best chance is to download a custom kernel and apply it after installation of the cutom rom. At first boot re apply a backup kernel with an app as flashify.
thanks youpi