Database Develop

How to revert to stock kernel

I have a Bell SGS, GT-I9000m. I'm considering installing hardcore kernel only, i.e. no custom ROM. If later I want to revert to the stock kernel, how would I do that?
Thanks for your help.
Sent from my GT-I9000M using XDA App

I'm not quite sure if it is possible with the stock-kernel but if you can make a full backup (like with CWM) you could restore it later. But why do you want to get back to stock-kernel?
If the backup-possibility does not work you have to find the stock-kernel for downloading and flash it via Odin or you have to flash the whole stock-ROM with Odin.

Thanks for your answer. I can't make a Nandroid backup while I'm on stock (because I can't install CWM recovery because I'm on 3e stock recovery, not 2e)
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong? I guess I just wanted to know if it was possible.
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Sent from my GT-I9000M using XDA App

I should add, the site/repo question is for kernels and stock ROMs...
Thanks.
Sent from my GT-I9000M using XDA App

site1ca said:
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong?
Click to expand...
Click to collapse
Well, then just flash the whole stock-ROM and flash it (look at samnfirmware.com for firmwares).
site1ca said:
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Click to expand...
Click to collapse
Don't know if you'll find it anywhere cause nobody needs it.

Possible scenario
Alright, thanks for your help. I guess the one scenario that is bothering me is as follows:
1) Bell - FINALLY - releases their official Gingerbread update.
2) I've installed Hardcore kernel, which according to - http://forum.xda-developers.com/showthread.php?t=822756 - "works on all 2.2 and 2.2.1 ROMs".
3) Would I be able to install the Bell Gingerbread update with Hardcore kernel?
This is why I keep asking how I would revert from Hardcore because I obviously don't want to lock myself out of Bell updates forever.

It doesn't matter which kernel you are using when you are flashing with Odin. And Bell releases the updates later than Samsung, so you'd have the advantage of getting updates earlier with a 'free' firmware.

One solution to flash back the stock kernel is to extract the zImage (the kernel) from the stock rom and flash that with Odin or Heimdall.
But as far as I know having a custom kernel would not cause problems with installing a stock upgrade.

Done
I've installed Hardcore's kernel. Everything seems to be working fine, phone started up and picked up service.
I booted into recovery, enabled lagfix, turned on all of the recommended tweaks and then ran the Quadrant Standard. Things seem a bit faster, so I guess it's all good.
Next step, Darky's 10.1.
Thanks for your help, everyone.

One more question:
I did a Nandroid backup of everything (so data, dbdata, cache AND system). The restore option says "Be careful!". What's up with that? I mean, what's the caveat?
Thanks.

I've already made some NANDROID-backups, but never seen 'Be careful!'.
If the backup was succesful I wouldn't care about that.

*sigh*, I hate to keep adding questions on to this thread, but I must.
After installing the hardcore kernel and enabling tweaks and lagfix, I'm running into exactly this problem: http://forum.xda-developers.com/showthread.php?t=851970
My phone was extremely hot for a while, then I got a warning indicating that my internal phone storage was running low, etc.
Eventually, I found this file (/data/local/tsprsp) to be the culprit. I deleted it and rebooted and now my phone is fine. However, vibration just doesn't work at all!
Any ideas? Has anyone else run into this problem?

I was told that if you do a 'full' backup, in some cases restoration will fail with some error. But it depends on the version of the ROM you are using.
That is the reason why it is recommended to backup only data and if you want to restore, then first reflash your rom, then restore the data.

Thanks, zsori. That explains the "Be careful!".
Sent from my GT-I9000M using XDA App

After trying MIUI, a stock ROM will never touch my SGS again.

meresis said:
After trying MIUI, a stock ROM will never touch my SGS again.
Click to expand...
Click to collapse
you will have to flash back a stock rom via odin if anything wrong happen during the flashing of custom roms, although chances are low if you follow the instructions carefully.
good luck and have fun flashing custom roms!

Which Gingerbread?
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.

site1ca said:
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
Click to expand...
Click to collapse
you got it wrong.
PIT is for mapping the partitioning of the phone. In most cases you should only use 512 pit file. and only use it when you want to wipe the phone.
the three parts is "pda" (which is the rom), "phone" (which is the modem), and "csc" (which is the carrier customization and apns)
the kernel is in the part of pda (the rom)
check the thread in xda of the kernel to see if its a gingerbread kernel or froyo kernel.
hope this clear things up

Yes, that helps. That's really good to know. So now, in Darky's guide to flashing Flash Ficeto_JVH_Odin, I see that only PIT and PDA are specified. This is reassuring, knowing that the modem and carrier stuff isn't touched.
Many thanks.

There are firmwares with three parts (Phone, PDA, CSC, including bootloader) and with only one part (PDA, no bootloader(?)). The one-part-FW is just an 'update', the one with three parts an 'upgrade'.

[Q] I9000M 2.2 UGKC1 to 2.2.1 XXJPY questions

OK, so I've been reading guides, FAQs, how-tos, and various forum posts, and thought I had a pretty good handle on how to flash FW to this machine. So, last night I backed up everything important, and downloaded from here ( http://forum.xda-developers.com/showthread.php?t=1102881 ) the following:
2.2 UGKC1/UGKC1/BMCKC1/Sbl. This is the stock FW as currently installed on my I9000M from upgrading through Kies.
2.2.1 XWJS8/XXJPY/OXXJS5 (MultiCSC) (no sbl)
So just as a sanity test I first tried flashing the UGKC1 PDA file over to my I9000M using Odin. This worked as expected, since it's the same kernel.
Next, I tried to flash over just the XXJPY PDA file over to my I9000, using Odin. No re-partition, no PIT, no modem or CSC. No go - it just repeatedly displays the GT-I9000M screen and never boots the kernel. Couldn't get into recovery mode from this state, but was able to access 3-button download mode.
So, tried flashing over the 2.2.1 XXJPY PDA, Phone and CSC files. Same as before - no actual boot.
I flashed it back to the 2.2 UGKC1 PDA, phone and CSC files, and did a factory data reset and cache clear, and everything was fine running 2.2 again.
From reading here it appears that others have successfully installed 2.2.1 or even 2.3.x kernels on Bell Canada GT-I9000M phones. So, what important step did I miss?
Do I need to re-partitiion? Do I need to use a 2.2.1 FW that includes the boot loader?
For now I'm OK running 2.2, but would eventually really like to be on 2.3.x and don't want to wait for Samsung to make 2.3.x (what happened to 2.2.1) available to GT-I9000M phones. I'll leave it alone for now as I'm going on vacation in a couple of weeks and don't want a hosed phone.

What happens if you flash just a kernel like CF root or speedmod? My only other thought is to redownload jpy and try again as maybe the download was corrupted.
Also with another kernel like speedmod you could download and install a custom rom on cwm (clockwork mod) via recovery that is 2.2.1
I've had some problems with 2.3.4 (never tried 2.3.3) so I am back on Froyo for a bit until things get sorted out a bit more.
G

I don't know if there is a suitable version of CF Root for the UGKC1 firmware - they mostly seem to be oriented to the more international versions. As usual, in Canada we get something a little weird. Don't know about speedmod.
I don't think there should have been any problem with the downloads, as the files themselves are in md5 format, which means they are getting verified by Odin 1.8 when it goes to use them, as I understand it. If they were corrupted Odin should complain about it.
With the announcement ( http://forum.xda-developers.com/showthread.php?t=1158492 ) that Gingerbread is supposed to get an official release to Bell phones soon (which mine originally was), I might just let this lie, for now.

There is a gentleman on youtube by the name of AndroidGalaxyS (original, I know) that has some excellent and detailed walkthroughs and reviews of various ROMs for the I9000M.
youtube.com/user/AndroidGalaxyS
Specifically in your case, you'll want to watch this one that shows how to install 2.3.4 JVP:
youtube.com/watch?v=cLXQn0gOBuA&feature=feedu
Good luck.

I agree that the source maybe lacking. I just found out that the JL2 firmware from samfirmware.com is missing db_data file so I would always get an error after flashing that. KC1 would also not always boot for me so it might be missing something too.
That said what are you trying to accomplish? If you are just trying to go to another stock rom I'd just leave it and put a custom kernel on to give you root and CWM recovery.
Most any other Froyo rom is flashable from CWM in recovery and you do not need to worry about odin except to recover from bad things and it looks like you can do that. Gingerbread is different because they changed the bootloaders and that means Odin.
Of course its getting harder to dig back and find those Froyo roms since the rest of the i9000 world has been on GB for a while.
G

Thanks for the replies, so far. Mostly I was just experimenting, and trying out XXJPY was just a first step in my experimentation before moving on to GB. Part of the reason for this is that it seems like a lot of the modified kernels and so on are meant to be flashed over certain versions of the firmware, and those versions don't include the Bell/Virgin-specific ones. Or maybe I've misunderstood how this stuff works.
Yes, while my attempts to install XXJPY have been a complete failure, even when re-partitioning with a PIT file, when I re-flashed back to the stock UGKC1 FW everything was fine.
At this point I'm just trying to get a better understanding of where this went wrong. I've never specifically updated the SBL - the JPY package I installed didn't include it, and I didn't check off the "Update boot loader" box when re-installing KC1.
I've seen a number of posts here from people who updated I9000Ms to other FW, but unfortunately they don't seem to have detailed exactly where they started from, or exactly what they installed, or how.

[Q] Roms with GKG3 based firmware

Hey everybody,
Im kinda new to droid development, and have played around with it a little (flashing roms, kernels, rooting etc) however, im curious why there are roms based on pretty much every other firmware other than GKG3. I might sound like a n00b for asking about this but its mainly for my knowledge. I figured KG3 would be fairly common as it is one of the North American firmwares, but I must be incorrect? Anyways any insight on this would be great. Also a quick question, seeing as I am a Bell I9000m SGS owner does it matter if I put firmware from say Europe on my phone? I have noticed that my signal decreases when I put a rom on that is JVR based? Curious if this causes my phone, seeing as the modem is being changed to JVR, to think that I am out of country and will inflict long distance charges. This probably sounds like a dumb question, and I dont really believe LD charges will apply, but some confirmation would be nice as google didnt really help me out on this one.
Thanks!

KG3 is 2.3.3 and although it was just issued to Bell and other N.American customers, the rest of the Anfroid world has been using 2.3.4 for 6 months and some have moved to 2.3.5. The roms you see here are cutting edge and most use the latest firmware. The last official and stable release was JVR a 2.3.4 firmware and there are many good roms for JVR. It is easy to keep your KG3 modem in place and the KG3 CSC file and just upgrade your system to a custom JVR kernel and JVR rom.

I tried flashing galaxian's jvr kernel and it just bootlooped so maybe I'm doing this wrong? I kept my stock modem and CSC, flashed kernel using oden, factory reset was done as well as a cache clear prior to the flash and all I'm getting is a bootloop so I'm not entirely sure what I'm doing wrong any advice would be appreciated! And again thanx for the info in the previous post!
Sent from my GT-I9000M using XDA App

yes you flashed just the kernel, you must first flash the stock rom and then any custom kernel for the same firmware -- you need the stock rom to install the correct bootloaders prior to flashing the custom kernel
so in odin, flash JVR stock in pda, KG3 in phone and CSC
tick auto re-boot
then flash the custom kernel of choice in odin under pda

Awesome thanks for the tips! Will give this a try

Hi guys - you guys might be able to help with a wee problem.
upgraded FW today via kies to 2.3.3 KG3 from froyo 2.2 with speedmod kernel.
in the process though i lost root but worse is i now don't have 3BR, when i used to. I still have 3 button download mode though.
I want to root again and flash a different kernel (for root but also for performance/tweaks) but worried to without 3BR ie. how will I access tweaks/enable root etc without it!?
Any ideas/advice please? Thanks

first flash a complete 2.3. firmware, either 2.3.4 JVR or 2.3.5 JVT. This should re-install basic 3BR functionality. I think you have not got the necessary bootloaders in the jump from froyo to GB and a complete stock install should correct this. Do tick re-partition and use 512 pit, do check auto-boot: let the phone boot and right itself. Check for 3BR and do a system reset.
Then flash KG3 modem and CSC. Your phone should then be functional.
Then flash a kernel with root inbuilt to it.
If you use the GTO Tornado kernel you can also clean your system completely as this stage instread. If you use another kernel, do the factory reset, davlik cache clean etc. prior to flashing the kernel as suggested above.
Do the clean prior to re-installing your apps.

lgsshedden said:
first flash a complete 2.3. firmware, either 2.3.4 JVR or 2.3.5 JVT.
Click to expand...
Click to collapse
Thanks! will give this a go but have only ever really flashed a kernel before with odin so want to be doubly sure about these steps if that's ok? apologies for my noobish ignorance
- only found a 2.3.4 JVR at samfirmware - getting this and the 512pit file. This should be fine?
- then flash a KG3 modem and CSC - any idea where I get those files from? - the ones i've got now i only got through kies (and when i do get em, when i do this in odin do i only use the phone/csc boxes and leave pit empty/uncheck re-partition?
thanks again mate.
Edit: forgot to say my reason for questioning the JVR is because the one i have is listed as European...where as I have a bell mobility but in australia - does this matter? latest FW for aus/america is JVN 2.3.3

no problem: always better to ask for help first then assitance fixing a problem when it all goes pear shaped.
There is a thread on the KG3 firmware with lots of these questions answered: http://forum.xda-developers.com/showthread.php?t=1211939 and also the basic resource for firmware posted by Ramad here: http://forum.xda-developers.com/showthread.php?t=1102881 -- scroll down and you will find KG3 under N.American, he also has a nice set of illustrations for using odin.
You can also source a cwm zip for the KG3 modem from perka's stash here and on the market (free app) -- useful to havce the modem in cwm zip form as then you can just install a new stock firmawre such as JVR or JVT and add the modem in recovery.

lgsshedden said:
no problem: always better to ask for help first then assitance fixing a problem when it all goes pear shaped.
Click to expand...
Click to collapse
Thanks so much again - that looks like a hefty bit of reading to be done there via your links so before I do that, just one more Q please - and apologies if the answer for this is somewhere in the links you've provided.
i was just trying to read up about why the samfirm file extracts only to a single .tar file called JVR_JVR_JVR and how to use that in Odin and came across this thread:http://forum.xda-developers.com/showthread.php?t=1075278
my Q is - in this thread he makes a strong point of stating not to tick repartition and not to put the .pit file...but you say to do so.
am i missing something obvious?

well different people different perspectives on re-partition and pit.
Tick re-partition and flash the pit file. Leave it un-ticked and do not flash pit file. That's the only key: do one or the other.
As I understand it, the reason to re-partition is that it re-sets the base file system upon which you are now flashing the stock firmware -- seems a basic step whenever you move firmware versions e.g. 2.2 to 2.3, 2.3.3 to 2.3.4 to 2.3.5 -- not so much if you are installing a rom or kernel within that family of firmware.
Since I always then convert the file system to ext2 to speed up the system and I use damain's kernel to clean the system, I do use the pit file whenever I flash a new stock firmware to clear the basic file system and further aid removal of legacy files that could complicate the install.
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
BTW the samfirmware files do extract using 7zip into the component parts for use in odin: pda (rom) phone (modem) and CSC. You then flash a custom kernel in the pda section if you use one for performance and root.

thanks lgssheddon, for the info here and in the PM.
Will crack on now with reading all the links you provided.
I just have to say a big fat D'oh! - why oh why could I not find the answer to what was bothering me most ie. apparent loss of recovery mode. The very first post in the first thread you linked gave me the answer - that it is now a 2BR (and tried it on my phone et voila, by magic I can get into recovery again!). Don't know how I could not find this thread even when I searched "KG3"!!
Thanks again for your help. i'l llet you know how i get on once i digest all this info

doktorV said:
Hi guys - you guys might be able to help with a wee problem.
upgraded FW today via kies to 2.3.3 KG3 from froyo 2.2 with speedmod kernel.
in the process though i lost root but worse is i now don't have 3BR, when i used to. I still have 3 button download mode though.
I want to root again and flash a different kernel (for root but also for performance/tweaks) but worried to without 3BR ie. how will I access tweaks/enable root etc without it!?
Any ideas/advice please? Thanks
Click to expand...
Click to collapse
The 3 button recovery has changed for KG3. I believe it used to be upvol home and power. I do believe now it is volup, voldown, and power. This should work for you to get you into recovery to flash whatever you like. Also the samfirmware for JVR is branded with Swisscom and doesnt work very well for using it with a KG3 modem and CSC, with my experience anyway. I would recommend to go to a JVQ PDA and use KG3 for your Phone and CSC. Also after you have installed this make sure to check what your country code is and install it. Hope this helped

lgsshedden said:
[/COLOR]BTW the samfirmware files do extract using 7zip into the component parts for use in odin: pda (rom) phone (modem) and CSC. You then flash a custom kernel in the pda section if you use one for performance and root.
Click to expand...
Click to collapse
The firmware that he is referring to doesn't. It is only one file meant for the PDA section of ODIN. Not entirely sure why they did this but i was running into problems with it as well. If you know how to play around with the core files you could in theory extract it to its root and put multiple files into .tar files (ex. select factoryfs.rfs, param.lfs etc. and place it under one .tar) but thats a lot of playing around and potentially dangerous if not done correctly.

not sure which download you are referring to but there was a branded version of JVR and a generic one on samfirmware: I have the one that does not have the swisscom logo and it certainly was extracted by 7zip into its component files (pda/phone/CSC) as they are still on my pc in that format.
You can also source stock firmware from Ramad's thread.
And I stand by my comment that for anyone using KG3 as a modem, JVR is the most stable official release available, much better than JVQ. JVT has a lot of promise and will be a better firmware than JVR but it is not yet had all the bugs sorted and while there are Gold Rom version for JVR any JVT rom is still at a beta stage and should not be used yet by someone just starting to flash custom firmware (IMO).

Hi again,
Q for lgssshedden really but if anyone can help i'd appreciate it!
have had 2 crashes now with Tornado Aureus RC1 - few little bugs/glitches eg with ringtone changing etc then on a reboot it won't go past the Tornado start screen with the big flame.
First time I just reflashed stock KG3 then reflashed the Tornado kernel, no problem. This time when I try to flash the Tornado kernel (either Aureus RC1 or Gold) it just bootloops at startup even though the flashing seems to go ok.
So now i'm back to (yawn) stock KG3 2.3.3. Really just want to root it again but with Tornado not seeming an option i'm finding it hard where to turn to root.
Thanks in advance!

[Q] General Bootloader and Kernel Questions

Hello all,
I have a few general questions that I would really like some help with:
1.) I understand some bootloaders are not compatible with some ROMs. How do you know which bootloader you are running? How do you change your bootloader, must you use ODIN?
2.) How does the kernel come into all this, are some kernels not compatible with certain ROMs and bootloaders? When you flash a new ROM, does it sometimes come with a new kernel?
The main reason I am curious about this, is because I wish to flash the new Cyanogenmod 7.1 and want to be sure I am successful and do not brick my captivate. I am currently running Serendipity VII Build 2 and want to be as safe as possible when flashing Cyanogenmod 7.1.
Would the safest way be to flash to stock first using the following Odin one click method: http://forum.xda-developers.com/showthread.php?t=731989
Then from there, follow the instructions normally?
All help is greatly appreciated.

There are basically 2 types of bootloaders, Eclair/froyo and Gingerbread bootloaders. GB bootloaders are compatible with preatty much everything (not counting cm7 or MIUI).
Kernels are specific with a type of rom, example Boogs KH3 kernel worked with any rom that was based on KH3 (2.3.4). Some are tweaked specifically for a rom.
On CM7 and MIUI from what I can make out you can run it on either eclair/froyo bootloaders or GB bootloaders but some kernels are specific for bootloaders.

If you are on Serendipity then I am sure you used ODIN to flash i9000 boatloader (BL).
As the above person said there are eclair/froyo BL and GB BL....in GB BL we have captivate BLs and i9000 BLs. earlier GB roms used i9000 BL...then Samsung leaked captivate specific roms...so we have captivate BLs now..
All the one click Odins are used to flash captivate specific BL...
To go to CM7, many people flash it over GB bootloader and have no problem....but the safest way is to odin back to eclair/froyo stock...then go from there.....

viny2cool said:
If you are on Serendipity then I am sure you used ODIN to flash i9000 boatloader (BL).
As the above person said there are eclair/froyo BL and GB BL....in GB BL we have captivate BLs and i9000 BLs. earlier GB roms used i9000 BL...then Samsung leaked captivate specific roms...so we have captivate BLs now..
All the one click Odins are used to flash captivate specific BL...
To go to CM7, many people flash it over GB bootloader and have no problem....but the safest way is to odin back to eclair/froyo stock...then go from there.....
Click to expand...
Click to collapse
Thank you for the help guys, I really appreciate it.
I will be flashing back to stock using the following method:
http://forum.xda-developers.com/showthread.php?t=731989
Then I will simply flash CM&.1 on top of that.
I will report back to let everyone know how it goes.

did your phone come with froyo on it/what is the build number of your phone? its a 4 digit number on a sticker under the battery, for example mine is 1010, meaning oct. 2010. many phones built later than this, and/or came from the factory tend to bootloop from jf6 (the firmware containedin that one click) and have also been known to lose button combos for recovery/download mode which would need both if you were bootlooping and for cm7.
if you have a later build phone it would be better to flash a leaked gingerbread firmware with bootloaders included and then flash a custom kernel with cwm included so that you can then flash cm7 from there.

studacris said:
did your phone come with froyo on it/what is the build number of your phone? its a 4 digit number on a sticker under the battery, for example mine is 1010, meaning oct. 2010. many phones built later than this, and/or came from the factory tend to bootloop from jf6 (the firmware containedin that one click) and have also been known to lose button combos for recovery/download mode which would need both if you were bootlooping and for cm7.
if you have a later build phone it would be better to flash a leaked gingerbread firmware with bootloaders included and then flash a custom kernel with cwm included so that you can then flash cm7 from there.
Click to expand...
Click to collapse
I purchased my phone at the end of August in 2010. The only 4 digit number I can see reads " 0168", it is the largest number located behind where the battery is held. And yes, I have lost my three button combo for recovery/download mode. It stopped working, and I bet it was because I used that one click method you mentioned.
Do you recommend I flash this one:
http://forum.xda-developers.com/showthread.php?t=1129821
It says Cyanogen Mod users stay away, why is that?
or one from the official list, and if so, which one:
http://forum.xda-developers.com/showthread.php?t=1300843
Also, I am a bit unclear. After I flash one of the stock ROMs with the bootloaders, how can I then flash a kernel with CWM. Can I do it through ODIN?
And just out of curiosity, why can you not use these stock ROMs for everyday use? It seems we always flash other ROMs on top of these?
I know I asked a lot, I would appreciate the help!

rcllcr said:
I purchased my phone at the end of August in 2010. The only 4 digit number I can see reads " 0168", it is the largest number located behind where the battery is held. And yes, I have lost my three button combo for recovery/download mode. It stopped working, and I bet it was because I used that one click method you mentioned.
Do you recommend I flash this one:
http://forum.xda-developers.com/showthread.php?t=1129821
It says Cyanogen Mod users stay away, why is that?
or one from the official list, and if so, which one:
http://forum.xda-developers.com/showthread.php?t=1300843
Also, I am a bit unclear. After I flash one of the stock ROMs with the bootloaders, how can I then flash a kernel with CWM. Can I do it through ODIN?
And just out of curiosity, why can you not use these stock ROMs for everyday use? It seems we always flash other ROMs on top of these?
I know I asked a lot, I would appreciate the help!
Click to expand...
Click to collapse
You can use the bootloaders in the first link. At the time of that thread's opening, cm7 didn't support GB bootloaders. But, if your not sure how your phone will work with a1 click, I would recommend using the ones linked in my sig.
As for how to flash those roms, there are directions in the first post of their respective for flashing.
You can use a stock ROM everyday, most just prefer not to.

mrhaley30705 said:
You can use the bootloaders in the first link. At the time of that thread's opening, cm7 didn't support GB bootloaders. But, if your not sure how your phone will work with a1 click, I would recommend using the ones linked in my sig.
As for how to flash those roms, there are directions in the first post of their respective for flashing.
You can use a stock ROM everyday, most just prefer not to.
Click to expand...
Click to collapse
Which kernel would you recommend I flash before I flash CM7.1?

rcllcr said:
Which kernel would you recommend I flash before I flash CM7.1?
Click to expand...
Click to collapse
No one said you cannot use stock leaked rom as dialy driver, i actually used KH3 for some times and it was very good.
You should flash the kernel according to the rom you have flashed. For example, For KH3, there is a Boog's KH3 kernel with CWM. For all leaked stock rom, there is one click Odins and compatible kernels with CWM injected.
To go to CM7.1, u shud be on stock (Eclair/Froyo or GB) and should have CWM....

rcllcr said:
....Also, I am a bit unclear. After I flash one of the stock ROMs with the bootloaders, how can I then flash a kernel with CWM. Can I do it through ODIN?....
Click to expand...
Click to collapse
I need help too please. I have a Cappy that was originally on eclair 2.1 rooted. froyo 2.2 Kies mini update and rooted but didn't like it's battery use and slow action. I reflashed an Odin 1 click stock 2.1 back, rooted and then did a Gingerbread 2.3.5 I897UCKJ3_withBL_ Odin 1 click flash and am liking that quite a bit more. The only trouble I am having is rooting 2.3.5. I want to do the fugu kernal swap method with Odin3 zimage-root.tar then flash boog_KJ3_kernel3.tar. I can get into DL mode and hit the start button ok.
Here is the question I have. Where in Odin3 v1.83 do you load the kernal path? PIT,BOOTLOADER, PDA, PHONE or CSC. I can't seem to find a comprehensive Odin3 tutorial on my own and I don't want to flash the kernels to the wrong place. I don't think the first 3 options are right based on their names or info I have found. Can't use CWM till I get rooted so Odin or possibly Hiemdall are my only choices. I have Odin3.
HELP and TYIA
Bud

Kernels go in pda

When flashing a single file, unless its a modem or csc file, it will usually go into the pda slot. Modems go into the phone slot. Csc file is a no brainer. I've never saw anything that uses the bootloader slot on a captivate. Pit slot must have a pit file AND repartition must be checked. If you are flashing a kernel to get cwm just to flash a custom ROM, kernel goes into pda slot. If you want to user Odin to flash a modem, it goes into the phone slot. All files flashed in Odin must be a tar or tar.md5 file. Don't change the name of a tar.md5, it can cause a md5 check sum error.
There you go, cliff notes for Odin.
Edit
If I missed something or messed up something, please correct me.

Found Odin3 Answers. Yeah!!!
Studacris,
Thanks for that. Didn't see it before I found the below.
Sorry for the Noob impatience but there is a lot of info that won't show in a search right away. Anyway there is a cool little short video by 4-2ndtwin here on xda with a link here. http://forum.xda-developers.com/showpost.php?p=17788928&postcount=6 The system won't let me post outside links yet.
viny2cool
Hope this helps you.
Bud

I Flashed and unbricked and reflashed and restored so many roms now, i have no idea what bootloader I am on. Is there any way for me to tell either through ADB or on the phone directly?

Pechkin000 said:
I Flashed and unbricked and reflashed and restored so many roms now, i have no idea what bootloader I am on. Is there any way for me to tell either through ADB or on the phone directly?
Click to expand...
Click to collapse
When ur phone boots up and u see the i9000 bootsplash, then u have i9000 Gingerbread bootloaders (we didn't have eclair/froyo i9000 Bls). Also, button combo to get into recovery or download mode is different with the i9000 gb bootloaders.
And if u try and flash an i897 gingerbread rom (and don't see the i9000) but u have a "pixelated" screen, then u have i897 eclair/froyo bootloaders. If ur flash to a gingerbread rom is successful and u see the i897 (att world phone) bootsplash, then u have i897 Gingerbread bootloaders.
Sent by XDA Premium App

Gingerbread it is then, THANKS 4-2ndtwin

Samsung Galaxy S i9000m bricked after installing wrong Clockwork Mod!

Alright, so this is my first time posting as I can usually find my questions in another thread... Haven't been able to find this one however.
So I rooted my phone earlier today and have been trying to get the Clockwork Recover Mod on it. I followed a tutorial and made a bad mistake... It seems I downloaded a CF-root made for the i9000 as opposed to the i9000m. Now when my phone tries to boot, it cycles between displaying the start-up screen for each, but it never boots. I can still access download mode, which I understand means I can still change it... But what am I supposed to do?
Further info: Running Android 2.3.3 on Bell.
Thanks!!!

Ditch the i9000m stock rom (which is UGKG3 2.3.3, the one you're probably using) and flash JVT (2.3.5) stock rom, then flash CF-root for JVT. The Bell i9000m will run on the International i9000 firmware and this should get you out of the bootloop.

adslee said:
Ditch the i9000m stock rom (which is UGKG3 2.3.3, the one you're probably using) and flash JVT (2.3.5) stock rom, then flash CF-root for JVT. The Bell i9000m will run on the International i9000 firmware and this should get you out of the bootloop.
Click to expand...
Click to collapse
I hate to sound super uninformed, but how should I go about doing that? Where do I get the stock rom for 2.3.5?
Thanks so much for the help though, I might just need a few extra steps to help get me there...
EDIT:
Would I just use this?
http://forum.xda-developers.com/showthread.php?t=1259240

http://forum.xda-developers.com/showthread.php?t=1102881
Follow the instructions on here. Use the JVT 2.3.5 PDA, KG3 modem, and csc...its the canadian one. And you might as well repartion with 512 pit. All this can be downloaded on the link above. After you do all that you will have the latest gingerbread firmware. Now you can root with a JVT kernal like semaphore or CF root. There are also a bunch of custom roms you can use on JVT not much if anything for I9000m . The only thing you need from I9000M is the modem and csc....otherwise your cell coverage will suck. I assume you already have odin, if not its available on the above link aswell.

vanisleryan said:
http://forum.xda-developers.com/showthread.php?t=1102881
Follow the instructions on here. Use the JVT 2.3.5 PDA, KG3 modem, and csc...its the canadian one. And you might as well repartion with 512 pit. All this can be downloaded on the link above. After you do all that you will have the latest gingerbread firmware. Now you can root with a JVT kernal like semaphore or CF root. There are also a bunch of custom roms you can use on JVT not much if anything for I9000m . The only thing you need from I9000M is the modem and csc....otherwise your cell coverage will suck. I assume you already have odin, if not its available on the above link aswell.
Click to expand...
Click to collapse
good advice. One other idea, since CF root tripped you up the first time, reduce your anxiety level and root using Hardcore's kernel for JVT or something similar -- one that is robust and also has good step by step instructions.

Question on which files to pull from the site for kernels, modem and csc files...
lgsshedden said:
good advice. One other idea, since CF root tripped you up the first time, reduce your anxiety level and root using Hardcore's kernel for JVT or something similar -- one that is robust and also has good step by step instructions.
Click to expand...
Click to collapse
I have a Bell Samsung Galaxy S I9000M also and am trying to install the Clockworkmod 2.5 hardcore kernel also and got into this boot loop...fortunately, I had the kg3root.tar with the kernel in it to re-flash and get operational again.
For us newbies, perhaps you could direct us to the specific set of files that we need to flash (with links to them) and the instructions to apply them.
I think to have a rooted gingerbread with clockworkmod recovery functional...at this point the ICS update should be able to be done using the instructions on the web. (hopefully)
thx.
W. MacKenzie