Database Develop

[Q] Boot loop after ROM Install via CWM -w/VIDEO

Hi there!
Recently I've been trying to upgrade my SGS with a custom ROM, Darky's 4.0. After installing the ROM as instructed (using CWM and copying the ROM to the internal SD card), the ROM Installs, after the 1st boot it keeps looping, see video:
http://www.youtube.com/watch?v=kWrijyv-8PM (not edited, sorry for that)
Original SGS:
GT-I9000T
I9000TUBJG7
Product code: GT-I9000HKTPCW
kernel: 2.6.28
Build: eclair.ubjg5
The first upgrade I made was via Kies reg-hack to: GT-I9000HKDXEU, 'I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3, and it installed Stock Froyo update. The SGS worked fine with exception of the radio, which didn't lock my 3G over the 850 band.
Currently:
9000M running STOCK Australian I9000UGJG8 (due to radio issues, besides the Canadian ROM, this is pretty much the only ROM which modem.bin's works properly with my network, 3G 850MHz).
FW:2.1-update1
Kernel 2.3.29 [email protected] #2
Eclair.UGJG8
I tried with the following STOCK ROMs prior to the custom ROM install: I9000XWJM1, I9000XWJG5, I9000XWJM9 and I9000UGJH2.
I have ALLWAYS made an SD unmount and format, formatted the cache and factory reset. After it loops, the only way to get it back is using downloader mode and installing a STOCK ROM via ODIN (always do a .512 pit repartition)
Any suggestions to make this SGS get the ROM? maybe the kernel is bad?
Cheers!

Have u tried to format everything (exept for sd) and flash again?
Btw i love infected
Sent from my GT-I9000 using Tapatalk

Format everything? Using which app or program?
I've always used the recovery's wipe commands and the *2767*3855# command. Is that enough? or am I missing another cooler and invasive method ? A friend has suggested to use davlik.
Yeah! Infected rulz, that's what I listen when I'm in the bricking-mood lol

As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk

shrooms90 said:
As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I gave that a shot, still no cigar. I guess that it goes deeper than just a formatting... maybe that secret kernel u have might brick me... erhm! I mean help me
Shoot! and I'll try it.... this OEM sucky ROM aint working that good over the Australian ROM lol. now I lost access to my cam ! sucks.
Thanx!

Try any universal lagfix kernel with clockwork enabled. Since ur phone is still flashable and ur phone still has funktionality (cwm works) im pretty hopefull that it is software/sd format related. Thats one of those cases where servic centre sais a full flash is needed by now only they are able to do that:-( but till now i always found a way to work around that by trying everything in every way. I always thought my phone is bricked anyhow so it can just get better and by coincidence it worked all of a sudden
Sent from my GT-I9000 using Tapatalk

Ihave I900T with same rom image
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!

zevrosenthal said:
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!
Click to expand...
Click to collapse
Well, first thing is first. I've been a couple of weeks away from my SGS tweaking. I'm right know figuring a way to make a backup of my ROM (non-nandroid), in which I can extract the Kernel, Modem and CSC (I received a brand-new unit from my provider, so I will take advantage of it )
That way I can flash them back in case of a screw-up. I didn't have that much luck with modems offered in other ROMs, so I need to keep an OEM copy of my stuff.
Also make a good copy of your /efs folder in case you mess it up. It took me around 3 weeks of reading before I started making any changes to my phone, so I'll recommend doing the same; there's no "quick-start" or quickguide on how to start. You will en up with 6 different windows open reading from everywhere
The FWs from samfw are OEMs. Theres like "not much" of improvemente if you switch to those. Take special attention to the one you chose cause most likely you will lose your 3G and/or 850MHz band. I recommend using only Australian and Canadian ROMs(I9000UGJG8 and I9000UGJH2 worked for me, you might try also I9000UGJK3). Regarding custom ROMs, you will need to try and try until you get it right as our SGS model is not the most popular. This means endless flashing
Cheers.

Sgs froyo flash nam bands
Thanks for the advice. This project consumed my thanksgiving but I finally got a good working SGS in the ATT network. I bought an unlocked SGS from Negri Electronics with the USA 3G bands but it came without FROYO and didn't have the 3 button restore available. After reading and reading (your note about multiple open windows at the same time is all too true!) and trying and trying, I was finally able to get to download mode by installing all the Android SDK tools onto my PC then going in by way of ADB. Far more complicated than a simple registry hack and ODIN but it worked.
I installed the DOC BUJP8 v9 ROM with all the enhancements and AOSP Email (I tried and tried to get stock FROYO email to work with 2 exchange accounts but it was impossibly slow and didn't work) while AOSP is working fine.
It seems, because my SGS had the 850 bands to begin with, that it's working fine. I found this other post on XDA (#770041) that had some keycodes I was able to use (*#2263#) and confirm I still have the 850 band.
Needless to say, make a good backup and be prepared - as already warned - to flash several times and it was ultimately a "trial and error" process that worked.

does anyone have the original brazilian/latinamerican i9000T firmware? I flashed the SGS I got from Negri with spike speedy and it looks like I lost my 850 3G band.
I never did find out how to totally back up the SGS as in back up each PDA, PHONE, and CSC file so as to be able to truly factory default it.

[Q] Absolute 'super clean' install - a little help needed...

Anyone done an 'absolute' clean install...? A bit of help needed...
After flashing about 9 different roms over the past 12 months, I would like to achieve a TOTAL wipe of my phone and an install of stock or custom - I have a feeling something is not right in the system image part of the phone... I have used Darky 9.5, 10.2 F, EE, RE, Cericko lite, F1, Ficeko JVH base, Galaxian, dark core, etc etc.
But still i cant get the perfect situation - either bluetooth in car goes (touch handset for nissan) or process.phone FC's.Flashed stock JVR today and still phone FC's after using bluetooth.
I have flashed previously both by CWM and Odin, and you may just say that re-partition in Odin does what i want (wipes system image) but I am not sure - what about the bootloader files etc? Can the internal system image become corrupted? (especially if done ext4/rfs conversions on and off?)
To be fair, the only time it was 'perfect' was on froyo 2.2 BEFORE the .1 update - ever since there has been these niggling issues...
If anyone has got any great ideas please pass them on!! Thanks!!

grab yourself a stock froyo ROM, flash it with all 3 files and 512 pit
boot onto recovery and do a factory reset, wipe cache / dalvick cache then go into mounts and storage (CWM needed) and format cache again, data, and datadata.
format internal and external sd card.
completely clean !!

i'd have to have froyo bootloaders no? And then,flash chainfire cfroot to get cwm? Cann i then upgrade to gb 2.3.4 and believe my system is clean? Thanks so much for the,tips!

dwgalaxys said:
i'd have to have froyo bootloaders no? And then,flash chainfire cfroot to get cwm? Cann i then upgrade to gb 2.3.4 and believe my system is clean? Thanks so much for the,tips!
Click to expand...
Click to collapse
What ROM are you on now ? if you are already on a GB ROM then do the whole procedure with a 2.3.4 firmware, Save the hassle of all that flashing.
If you are on froyo now, you dont need to mess with bootloaders unless you upgrade to GB which states you need them..
hope that makes sense

yes sorry, should have stated am on XXJVQ already and changed yesterday to sensation 2.1 as i was getting probs with all others. This is at least stable after 36 hours so hopefully a working solution - but,if ihave to do superclean i wanted to know how to do. THANKS!!
EDIT - whoops - spoke to soon. Also loss of touch in car Bluetooth with this rom! Have now frozen with TB all BT settings - print/share/opp/bluetooth services etc etc... recovered in car BT touch for the time being - even without any BT entries running!??? shall monitor and see. This is what the issue has been with ALL 2.3.4, 2.3.3 gb versions/roms. I'm stumped if i know what is causing it!

see edit post, thanks!!

Please note that Sam (author of SURFACE ROM) gives a good guide about how to achieve that in this post:
http://forum.xda-developers.com/showpost.php?p=15382251&postcount=2

thats a great post too - i've also downloaded this surface rom in order to try next if the sensation one screws up! Thanks very much!

[Q] Speedmod + Stock Froyo, updating to Gingerbread

Hello guys.
Official Gingerbread is finally available on Portugal.
I have currently Stock Froyo + Speedmod installed on my Galaxy S, so how can i update to Gingerbread?
Can i just update and Speedmod will still work?
Or should i install a stock kernel, then update, then install the Speedmod (Gingerbread version)?
Or i shouldn't update at all?

i'm interested in this too,i'm in the same situation (froyo+speedmod) and i'm quite a noob
is there someone who can patiently give us an hint about that? also about a good battery life gingerbread rom?

This is what I did.
1. Disable any lagfix - convert back to rfs (very important).
2. Back up all apps, contacts, data, photos etc from internal memory. Use something like Titanium backup or Mybackup pro.
3. Update through Kies for an official update.
4. Install latest Speedmod kernel for gingerbread (not Froyo version). Use odin.
5. Install superuser from clockwork mod recovery.
6. From recovery, do a factory data reset (make sure you have everything backed up first!)
7. Restore previously backed up apps, data etc, sync with google calendar.
8. Redo lagfix from recovery (convert to ext4).
Battery life at first seemed all over the place but has now settled down and is similar to Froyo/speedmod.
The phone is smoother and faster to use.

Thank you a lot!
That's exactly what i'm going to do!

thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?

skeletonboy said:
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
Click to expand...
Click to collapse
If Kies is showing that there is an update available then I think you should be ok.
If not then it is a case of flashing the whole firmware with odin. Open phone dialer and enter *#1234# and you will see the firmware details you are on now. It is worth making a note of these so you can reflash your current firmware if there is a problem.

okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?

Everything is working better than ever, except for one little thing: The GPS.
Today i turned on GPS and tried to use my navigation software (CoPilot) and the GPS signal just didn't fix at all!
I ended by not using it, but i don't know why it doesn't work. It always worked wonderfully well before this update...

skeletonboy said:
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Click to expand...
Click to collapse
Still try kies first. If no luck there is a lot of info in this thread.
http://forum.xda-developers.com/showthread.php?t=723596
Make sure you can get into recovery mode first. Power button, volume up and home pressed all at once. Let go home button when Samsung logo appears.

ok thanks for the infos! i'll do it all when i can have a bit of relax,i am relocating so i need a working phone during these days

so i did it then!
flashed darky's resurrection 10.2 and then updated to doctorz rom jvt leaving ext4 enabled with no probs: another phone
just needs a good theme now..

[Q] !Complete! reset i9000

Hey guys,
i installed many different versions of android also custom roms, but since some time i noticed, that my phone gets buggy. I guess its due to many different installs, maybe incomplete resets or whatever.
I would like to hardly reset all in my mobile. (SD-Card) the system, the partitions... is there any option to really reset all and get rid of old leftovers?
kind regards.
mhoppi

Search google for hard reset.
Something like this
*#2767*3855# but im not sure.
It will do factory reset and erase sd card.
First install stock rom and then do this.it won't work on custom kernel.

Yes, im on Miui for now. Well I downloaded XWJW1 but the files are named in a - for me - new way.
APBOOT_I9000XWJW1_CL788890_REV03_user_low_ship.tar.md5
KERNEL_I9000XWJW1_CL788890_REV03_user_low_ship.tar.md5
CODE_I9000XWJW1_CL788890_REV03_user_low_ship.tar.md5
Which one is which one in odin?

Download latest jvu it's easier.

mhoppi said:
Yes, im on Miui for now. Well I downloaded XWJW1 but the files are named in a - for me - new way.
APBOOT_I9000XWJW1_CL788890_REV03_user_low_ship.tar.md5
KERNEL_I9000XWJW1_CL788890_REV03_user_low_ship.tar.md5
CODE_I9000XWJW1_CL788890_REV03_user_low_ship.tar.md5
Which one is which one in odin?
Click to expand...
Click to collapse
If you want JW1, download the official version released on Monday.
See this thread for the download with file names that are more appropriate for Odin:
http://forum.xda-developers.com/showthread.php?t=1102881&page=1

Few Galaxy S questions

Hello
I own a French Galaxy S for more than a year, it's an unlocked unbranded one bought in Pixmania
Model number is I9000 and PCode is GT-I9000HKYXEF
Installed firmware is 2.3.3 updated officially by Kies one year ago
PDA: I9000XWJVH
PHONE: I9000XXJVO
CSC: I9000XEFJV2
It seems to be the latest version released for my phone in France (CSC XEF)
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do

You could use this guide for rooting your phone:
http://www.theandroidsoul.com/fuguroot-galaxy-s-how-to/

Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.

albertocastillo2001 said:
Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.
Click to expand...
Click to collapse
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app

AlwaysDroid said:
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thank you.

why donn't you upgrade it to 2.3.6
for root use cf root kernel or semaphore kernel

I cant post in this thread for some reason. Ill try later

albertocastillo2001 said:
I am going to split this post in two cause there is alot...
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
- Being upgraded to 2.3.6 or whatever isnt really that great. A few changes were made, but really not much. Like some sgs devices have 2.3.4, mine came with 2.3.3 and you really cant tell the difference. here is a complete list of the changes if you want.
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
-I am to lazy to type how it works so go here. I learned off of that website. As for the other part, You can return to stock and never have samsung notice because we dont have a flash counter.
Click to expand...
Click to collapse
There you go. /Part 1
---------- Post added at 04:15 PM ---------- Previous post was at 04:01 PM ----------
albertocastillo2001 said:
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
-Technically all roms use root. The difference here is that what you are referring to is the user having root acess. And of course Samsung doesnt really want uneducated people messing with the phones software, so it is locked away from the user. But the system still has to use it. But you do not have to have a custom rom rooted, but fact is that almost all are. For example I tried out a new jellybean port early on and it had no root access. The only thing in this case is that you must flash anything via odin instead of CWM.
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
- I dont know where you heard this, but the bootloaders so not change on flashing a custom rom. Anyway, when you flash back to stock with odin, EVERYTHING goes. It will be 100% stock, not a single trace of you being rooted, having kernel and recoverys installed etc. Totally new.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
- Indeed, they tell odin how to partition your device. There is no advantage to either or. Read here.
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do
- Indeed each country seems to recieve a different version for some reason.
Click to expand...
Click to collapse
Part two. Hope that helped!

Hello
Thank you very much.
I'm at work but I will read it again when I get home. It really helped, the rooting technical guide was pretty clear, and the PIT file information as well.
About the other questions:
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
Click to expand...
Click to collapse
It's ok, the GPS is driving me nuts
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
Click to expand...
Click to collapse
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
Click to expand...
Click to collapse
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
Few more questions
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
What's the [Dump] option in Odin? Haven't seen that anywhere
I have to read some more info about the bootloaders first before being able to ask more.
Thanks

albertocastillo2001 said:
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
-I very much so agree, i dont know why you would want to use that. But Odin is the official samsung flash tool, so i bet that samsung uses it in their repair centers for something.
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
-Yes they are separate partitions
- This is not bad at all. Usually before i do nandroids in will do a /cache clear to make it smaller. I think it might actually be beneficial to clear it once and a while anyway. Sometimes i just clear it. Your phone will boot fine. Keep in mind that clearing cache does not clear the dalvik cache, as this is kept on /data and has to be cleared from the advanced menu. Also a word of caution, i wouldnt clear the dalvik while your phone is on, everything will force close. So just do it from recovery
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
-What more details so you want? and yes whenever you perform a factory reset, the dalvik cache, /cache and /data partitions are cleared. But just wiping /data will be the same, but the cached reminants will still be there, which isnt an issue, its just wasted, thats all.
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
-Ah i get it, and yes you are correct. Even though there will never be another update for your device.
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
-Yes, i believe that the 10mb is transfered between the two. But when you install cyanogenmod 9, it gets rid of /dbdata. There should NEVER EVER EVER be a risk of messing with /efs. It is a rare occasion for it to go corrupt. Possible though, so do your backups.
- As for being the most important partition, it is hard to say. Your phone will boot with no /efs, it will just lag like hell, have no service or imei. Kinda hard to explain that one to the repair center since nothing touches that partition, ever.
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
-I believe that the kernel parts are mainly stores in /sys, although there are pieces in other places as well. (ex: /data/local/devil for devil kernel settings)
-Also, unlike my old galaxy gio, the recovery is packaged with the kernel on galaxy s. So changing the kernel replaces the recovery as well. You cant do it individually.
-Yes, all aftermarket and stock roms come packaged with a kernel. For example, i use devil kernel with my cm9. But when i flash a new version of cm9, it replaces the kernel and i have to flash devil kernel again.
What's the [Dump] option in Odin? Haven't seen that anywhere
-DONT take my word on this, i am not 100 sure. But i think dump, performs a dump of all the partitions to your computer. Not sure, so i dont advise trying it without research.
I have to read some more info about the bootloaders first before being able to ask more.
-Okay, let me know!
Thanks
Click to expand...
Click to collapse
.......

Hello
Thanks again
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
I guess these are all the questions I need to ask to cover all doubts.
Thanks!

albertocastillo2001 said:
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
-Nothing unless otherwise stated messes with the bootloaders on most devices. But our bootloaders are unlocked, meaning the partitions arent signed and the bootloader doesnt check for sigantures, so it doesnt care if we have a custom recovery. When we use the three button combo, all it does is trigger the bootloader to boot into the recovery partition. But since they arent locked (bootloaders) and partitions arent signed the bootloader doesnt care whats there. Itll boot whatever is there. So no mods needed for custom recovery.
********NOTHING MESSES WITH BOOTLOADERS UNLESS OTHERWISE STATED ***********
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
- Yes everything you need to go **********100000000000000000000000000000000000000000000000000000% back to stock ************ is in there, even bootloaders. The primary bootloader isnt, cause nothing will ever touch it.
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
-The only thing you should backup is /efs
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
-Odin only will repartition /data /cache /dbdata and /system back. Removing things like /datadata in the process.
****************NOTHING EVER EVER EVER MESSES WITH YOUR EFS> EVER****************************
Except unlock attempts
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
-This is a question i wish someone had answered for me when i was new here. Odin wont format the /data and /cache and dbdata(i think?) when flashing back to stock, so if you try to boot, you will bootloop. Only the stock recovery can format to rfs and knows how to handle it, so you must do a factory reset to format the rest of the partitions back to RFS.
Click to expand...
Click to collapse
Hope that helps you out

Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added

Samsung stopped genuinely supporting this phone quite a while ago. The burden of updating the device has fallen onto the development community. Given that the I9000 is one of the most popular Android phones, LOTS of development has taken place since then.
The kernel on this device is part of the boot image, on its own partition. Recovery is coupled to that partition.
Rooting a device adds a new binary (su) to the system partition. This file is given permission to run as user 0 (root) and acts as a proxy for other processes to perform privileged actions (deleting system files, mounting partitions, accessing all data, etc).
Most custom ROMs come pre rooted since rooting is quite popular. Titanium Backup is the exemplar for what an application can use root privilege for.
Installing a custom ROM does not require the stock ROM to be rooted, it requires a custom kernel (with a cwm or twrp based recovery).
Most high quality custom ROMs (read CyanogenMod) have scripts to protect the efs partition while flashing.
As long as you can get into download mode on your phone you can always get back to stock firmware. The service centre won't know the difference.
The bootloaders are provided by Samsung, these are not replaced by custom ROMs.
Personally I run a modified build of CM10 and use a radio from the Nexus S (KJ1). I'm very happy with the overall battery life of my phone, signal quality is good in Australia (can't say with certainty for any other part of the world) and performance is quite snappy.
Sent from my Nexus 7 using Tapatalk 2

albertocastillo2001 said:
Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added
Click to expand...
Click to collapse
Jus read things that come up in the questions/answers forum. Learn from other peoples mistakes
Sent from my GT-I9000 using xda app-developers app

Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs

albertocastillo2001 said:
Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs
Click to expand...
Click to collapse
Baseband/modem (samething,)is the little piece of software that talks to the cellphone towers. And because each area uses a different frequency, there are many different ones.
Also good to note that it is not ATS all related to GPS or WiFi.
Sent from my GT-I9000 using xda app-developers app