Database Develop

[Q] How to: Root and flash Custom ROM

Hi!
1st of all, I'm new to the Samsung rooting world, and might be under influence of procedures from the HTC proces. So I just want to get verified a couple of things, before rooting my SGS
I want to root and flash Darky's custom ROM.
So, going through the forum, I found the guide about root/flash/ADB... and so on. http://forum.xda-developers.com/showthread.php?t=723596
The 1st step (underneath), is this the same as rooting? And can I flash any custom ROM after this, or should I proceed with step 2 and flash the update.zip, or is this unneccesary?
1.Flash Firmware using Odin.
Note: This will in (almost) all cases erase all your data and applications (includind root!). It will NOT touch the internal or external SD card.
Note: It appears now, that in some newer batches (originally only in Canada, but reports have come in from Australia and Germany), the phone has the three-button combination for download-mode disabled (VolumeDown+Home+Power or alternatively Home+Power on some phones). Check if the download-mode combo works BEFORE flashing! Please refer to FAQ#A12 and T&T#23 for a fix for the download mode if it doesn't work on your phone!
Requirements:
-Odin3 version 1.0 or version 1.3 (Note: Odin should be on the system partition (the partition where windows is installed) to avoid possible issues)
-".PIT" file for the Samsung Galaxy S (See FAQ#B9 for the version to use!)
-USB cable
-Desired firmware package
Procedure:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (.PIT and PDA are required. CSC and Modem are HIGHLY recommended. They may be necessary depending on the PDA! Try flashing all three BEFORE reporting bugs, if you only used one initially!)
3.Check the "Re-Partition" checkbox.
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.When the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
Click to expand...
Click to collapse
2nd - I was currious about the 3-button fix... can I test this? And what is the dealio with this? Would I be unable to get into custom revocery, if I don't flash this at first?
WHen the phone is turned off, I can't get into download mode, by pressing VolDown+Home+Power. Nothing happens when the phone is on either
The phone is updated to 2.2 using Kies and registry patcher
thanks in advance
best regards Lars
Edit:
It seems that i can't get into recovery, nor download mode.
Is there any relativily "safe" way to get along from here?
I was thinking about installing ROM manager and flash ClockWorkRecovery from here, and get into recovery mode this way. But I still ned to flsah the firmware. How do I do this?

So, now I will provide my own answer, after several days of research...
found this app via google - Z4root (google it if you want to follow the next part)
downloaded the zip-file, unpacked it, copied it to phone, installed the app. pressed the root-button. Phone rebooted, and I was now rootet. Easy

larsn84 said:
So, now I will provide my own answer, after several days of research...
found this app via google - Z4root (google it if you want to follow the next part)
downloaded the zip-file, unpacked it, copied it to phone, installed the app. pressed the root-button. Phone rebooted, and I was now rootet. Easy
Click to expand...
Click to collapse
Yes it work if you not on froyo 2.2.1.
Then you need an other way to root.
Is your 3button combo don't work you need to fix that first before you start flashing stuff.
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**

DamianGto said:
Yes it work if you not on froyo 2.2.1.
Then you need an other way to root.
Is your 3button combo don't work you need to fix that first before you start flashing stuff.
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**
Click to expand...
Click to collapse
Thanks... Im currently reading about the 3 button fix... thought it might be a good idea to get that working too Im on android 2.2, so lucky I couldnt get Kies to update to 2.2.1 with registry patcher...
do you know how to flash custom recovery?
I tried ROM manager and clockwork mod recovery, but it still boots into android recovery

larsn84 said:
Thanks... Im currently reading about the 3 button fix... thought it might be a good idea to get that working too Im on android 2.2, so lucky I couldnt get Kies to update to 2.2.1 with registry patcher...
do you know how to flash custom recovery?
I tried ROM manager and clockwork mod recovery, but it still boots into android recovery
Click to expand...
Click to collapse
Yes you need to fix that.
Well you can flash a custom kernel.
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**

DamianGto said:
Yes you need to fix that.
Well you can flash a custom kernel.
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**
Click to expand...
Click to collapse
finally... got the 3 button fix to work with odin, and can move on... but it seems im need to revert to android recovery (2e) to get on from here and flash a custom ROM/update.zip that is compatible with Clockworkmod.
when i try to flash update.zip it says the whole file-name, or something was unknown. so I guess 3e wont work for me :/

larsn84 said:
finally... got the 3 button fix to work with odin, and can move on... but it seems im need to revert to android recovery (2e) to get on from here and flash a custom ROM/update.zip that is compatible with Clockworkmod.
when i try to flash update.zip it says the whole file-name, or something was unknown. so I guess 3e wont work for me :/
Click to expand...
Click to collapse
Well if you have the phone rooted and have installed busybox 1.7 then you can try out my kernel. Just dl the app and you flash a kernel. Try it out first.
Then you can try some rom. You can flash them with that kernel you did install.
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**

[Q] Cant flash custom firmware all of a sudden

Hello, sorry if this has been posted before but the search function is awful.
I have a UK i9000 (SGS) on Vodafone
I had my phone working great with some custom rom, Tayutama edition was my favourite. I dropped the phone on top of my computer, it went haywire and started resetting every few minutes. It would do it if you flicked it or jolted it so I assumed that it was probably a connector in the battery. It was not something I could fix so I prepared to phone so I could send it back as a warranty job. With a lot of work, I managed to return it to a stock firmware 2.1 (via ODIN), I have sucessfully updated it (via ODIN) to XXJPY and I am using kernel 2.6.32.9 hardcore_speedmod-k12r-500hz #6. My Phone is rooted with ch root.
I can get into clockworkmod recovery fine (by installing ROM Manager), i can install a custom rom no problem (it flashes correctly), but it refuses to boot after the flash process is complete. It just gets stuck at the 2nd boot screen (whether this is custom or the standard SGS gleam logo). It does this with various custom rom's and I was wondering what the problem might be. As I said, I could flash custom roms at my leisure until i dropped the phone, now it wont work. I am sure that it is not the phone that is phsyically broken as this sounds likely, but probably my flashing root.
To get the phone working, after flashing a problem rom, I must always use ODIN to flash JM6 with 512 pit and the XX CSC. Then I can flash JPY with ODIN (using an all in one package, so no CSC/modem etc), then root, speedmod kernel etc.
Anyone got any suggestions as to why?

do you have lagfix enabled on your speedmod kernel ? that can cause issues..
also how long are you letting it boot for ?? after a flash my phone can take upto 15mins to get past the boot screen.

last few times i had it disabled i think.
I did a full wipe of the SD card and the internal SD card, then flashed from download with odin successfully. Therefore the lagfix cant have been enabled as I understand it. I have disabled it the proper way (cant remember how) and still unsucessful.
In my experience it normally takes between 3-5 mins for the first boot, I had left it well over 2 hours once (to prove to myself that it was not my lack of patience) with out any change. I have tried taking out the battery, re-inserting it and booting again (for another 2 hours) and no success.
Is there a foolproof way to ensure the lagfix is disabled? Last time I tried a custom rom, I was coming from a totally stock firmware phone. No lagfix applied, no custom kernel, only rooted to allow clockwork recovery to install, should I try it again without rooting the phone, IE just using clockworkmod's update.zip at recovery?
miles

http://www.multiupload.com/PUSOOBQ8K5 download that and flash it with odin using the pit included and CHECK REPARTITION.. then when thats done flash JPY thru odin and then you could flash speedmod kernel thru odin..
when all that is done it will leave you with CWM and in there you can root / unroot You will be un rooted as default, also you can enable lagfix / disable lagfix you will have lagfix disabled by default too.
you are right about lagfix being removed when going back to stock.
so when all that is done your phone will be stock except the kernel, if all that works you should be good to start again..
just one more thing, when you are flashing a rom thru CWM you are choosing install update from sd card >> chose update from sd card right ??? you dont need to be rooted to flash speedmod kernel

[Q] Installed Speedmod kernel, shows new boot screen but no change to about phone

EDIT : Just checked and found Speedmod tweaks in recovery. Assuming this means it has installed successfully? Does anyone know why it won't update the kernel info in about phone?
EDIT : Just switched to Suckerpunch so I can OC but again, no confirmation of the kernel being updated in the about phone settings page. I can see the new boot image but I'm worried that if it didn't properly install the kernel it won't be safe to OC.
Searched and couldn't find anything related.
Just installed Speedmod through CWM and although it changed the boot screen at startup it did not change the kernel # in about phone.
- SpeedMod K13C with HZ=500 CWM
Tried installing with Odin after and same problem.
- SpeedMod K13C with HZ=500
Yes btw I am a noob.
Running Cognition 4.1.1 (2.2)
Is there another way to check? I'm running Quadrant Standard to benchmark, before I ran the install I had a benchmark of 1484, after the install it went down to 1323 (worse). And I was expecting speedmod to bring it up to around 2000+ so I'm convinced it has not installed correctly.
Did not get any error notifications in CWM or in Odin.

[Q] Boot loop when flashing Froyo/GB/Anyhing non Eclair over stock Eclair JM8 with 2e

Evening,
I'm trying to upgrade from a stock Eclair 2.1 to Froyo.
Recovery is 2e.
I've spent the better part of the last two days reading endless threads here and trying any remotely relevant solutions that were discussed.
The phone simply refuses to boot anything other than Eclair.
Won't run any recovery other than it's stock 2e either.
So far I've tried:
- Stock 2.2 JPC / JPU and 2.3 JPK / JVK with repartition and wipe, using Odin v1.3, 1.52, 1.7, 1.82 and correct pit file.
- 2.3 JPK / JVK with above Odin versions.
- speedmod, CF-Root, darkcore, damianGTO and a few others with Odin and SGS kernel flasher app.
- CWM recovery with SGS kernel flasher app and rom manager app.
- Manually flashing the GT-I9000 2.5.1.2 CWM recovery, which seems to let me into the CWM recovery menu if I "apply update.zip" twice, but recovery is still stock 2e on reboot.
- WIPE versions of popular roms that include a kernel with Odin/CWM.
With all of the above the result is the same. Just shows a the Galaxy S logo for hours and hours. It will not go into recovery mode either, only download mode.
If I flash any stock eclair such as JM4, JM8 or JD4, the phone boots Eclair just fine and I can get 2e recovery again.
I've checked that it's not sim locked with the *#724....# code, which said that everything was unlocked.
Not many hairs left to pull. Hopefully some of the gurus that hang around here would be kind enough to point me in the right direction.
Thank you for your time,
oldseeker

http://forum.xda-developers.com/showthread.php?t=847765
use this to successfully upgrade to Froyo..
cheers

Backup your internal sd storage. (Photo's, music etc.)
Then give it a format. Then try to flash again. Do not worry about restoring all the android folders and such after the format. All of the needed folders will be re-created.

Try taking it to a service centre and ask them to update it to Froyo for you. They might know something we don't.

Dear oldseeker,
Quite a coincidence but I've had a similar problem today with my dad's SGS.
The phone would go into a bootloop if I'd flash froyo or gingerbread.
He had eclair on it and needed an update badly to use his apps.
How I eventually fixed it was, by flashing Eclair JM8 with the pit file from samfirmware (with repartition ticked), and after that was finished, I flashed Darky's
Ressurect Edition 10.1 again with repartition ticked, and everything works now as it should.
Hope this works for you!
Greetz,
h4run_

[Q] [SOLVED] Continuum v5.4.1 Installation

Can someone please post a more detailed set of steps for installing Continuum v5.4.1 from stock. I've been using FireFly for the last 3 months and really want to try out this rom. I've restored back to stock using ODIN one click and have done a master clear. There are no details on how to install the new bootloaders and the kernel using ODIN. Please don't slam me as I am new to this. I've read the entire first post. I've watched the MobileTechVideos video on youtube, but it appears to differ from what is posted in Icezar's post: http://www.youtube.com/watch?v=n9PKsk32Y0s (appears to be one file that gets bootloaders, kernel and ROM).
I've downloaded the ROM to my internal SD card. I have the talon kernel TalonDEV-0.1.2.tar file and the galaxys-bootloader-JVB.tar.md5 file on my computer. I used the ODIN3 v1.3 that was listed in the thread using the bootloader file in the PDA field. The installation fails; my phone is in download mode and connected to the USB on the motherboard. I end up having to pull the battery and have a soft brick (I have to use a jig to get download mode again and one click to get back). I've tried ODIN3 v1.82 doing the same steps, but in that version I put it in the bootloader field; it fails as well. One thing I noticed is the bootloaders linked in the thread say JVB and the ROM now says JVH; is there an error in the post? Does the version of ODIN matter? Do I need Galaxy S windows drivers? Right now I'm staying on stock until I can figure out what I'm doing wrong. Thanks for your time...

Follow Mobile tech videos Samsung Captivate (How To Install Gingerbread ROM's) video instead, it's how I installed Continuum. Just install continuum instead of whatever he installs at the end. Same process.

For what it is worth, the version of ODIN you use is very important. There are a few versions of the one click download version that are specifically meant to return you to a stock rom. You want to make sure that you are using the full version such as ODIN 3. I have ODIN 3 version 1.7 and have used that several times to install Continuum and other stuff like different kernels.
The latest version of Continuum comes with the proper kernal already packaged. For the sake of playing it safe, when I was flashing 5.4.1 over stock 2.1, I installed an older version of the talon kernel first. I don't know if that was necessary, but it didn't hurt the situation either.

Thanks for the replies; I really appreciate it. So continuum v5.4.1 has the kernel bundled. I still have to do the bootloaders first using the pda field and not the bootloader field in ODIN3 v1.82?

Another question that came to mind; is there a way to get out of download mode without using 1 click back to stock. If I am in download is there a key combo that will reboot the phone normally? Thanks!

So I successfully installed the gingerbread bootloaders. I used the new key combo to get into download again and used ODIN to install the talon 1.2 kernel linked in the continuum post and it completed and the phone starts to boot and I battery pull. I then used the new recovery mode combo which works, but when I try to find the rom on my sdcard I get an error that it cannot mount /sdcard along with a bunch of other mount errors. My screen is similar to this post: http://forum.xda-developers.com/showthread.php?t=1076670&highlight=cannot+mount+/sdcard. In my case Odin completed successfully for the loaders and kernel. Please tell me what I missed. I used one click to get back to stock after I couldn't get past this error. Thanks...

icezar's instructions are probably the most complete you'll ever see for a custom rom ----- by far the best and most thorough, just follow them.
Best I can say is to just start over - one click back to stock, download mode, then flash continuum (first one - bootloaders).
I let everything boot up and then move updates to sdcard.
Flash kernel you want - I like Talon's (I'm on test 13 I think - OC'd at 1.2 -50,-50,-50,-75,-75-75 - all tweaks disabled)
Flash update zips via recovery .... 5.4.1 ---- I usually wipe Dalvick just to be sure, though it does it on its own.

Subv3rsion said:
Another question that came to mind; is there a way to get out of download mode without using 1 click back to stock. If I am in download is there a key combo that will reboot the phone normally? Thanks!
Click to expand...
Click to collapse
On stock from download - just hold down all of the buttons, if it goes to recovery (which it should), just select reboot.
On GB loaders, it's different for the key combos, but still manageable.

I know exactly what you are going through. The instructions are very detailed. However, for those of us coming from 2.2 without having to understand Odin, the instructions are confusing. I think your confusion stems from there being multiple pit files. I have minimal knowledge of odin, but here is what I did to get GB Continuum from FF 3.0.
First off, I restored to stock using JV6 file without bootloaders per Icezar's link. I then downloaded each of the odin 1.3 rar files and extracted EACH (with 7zip) to a different folder. Then I ran the relevant odin file for each step.
Here is what I have gleaned from the process. The pit file in each rar is different, so normally you would select the relevant pit and pda file. The reason this worked without selecting the pit is because the pit and relevant pda were the only files in the directory as the instance of odin I ran. This may be wrong, but odin did not work if separated from the pit/pda.
Hope this helps because after tinkering with tweaks and UV settings I was at 40%battery after 1 day without charging.
---SGS i897 Captivate using:
Continuum 5.41 w/ Talon 1.7 [rfs all, OC/UV, TW4, no theme, no tweaks enabled, & NETFLIX!)

I have found I can UV 1000/800 150, but 100/200 only by 50 & 400 by 75 before boot looping. However I kept io deadline and tweaks above that selection on. With rfs it has been smooth and fast. But sd write speed no matter what is slow... Have you had any luck?
-- SGS i897 Captivate using:
Continuum 5.41 w/ Talon 1.7 [rfs all, OC/UV, TW4, no theme, no tweaks enabled, & NETFLIX!)

Thanks guys. I'm waiting on a JIG I ordered this weekend before I try again. It sucks sticking resistors in trying to get dowload mode after a soft brick. Does anyone know the techincal reason my sd card wouldn't mount after I flashed the bootloaders and the talon 1.2 kernel? From what I am reading I just do the gb booloaders then install continuum from recovery as it contains a newer talon kernel. Fyi my build number is 1009.

So I did my upgrade tonight to Continuum 5.5. This time I had my JIG from MTV; thanks Josh! It made it a hell of a lot easier. I did the GB bootloaders and did a battery pull after ODIN 1.82 completed and the galaxy s screen came up. Then I installed the old talon 1.2 kernel which I'm not sure if I needed to do. This time it worked and I believe my error was in the video he doesn't un check the Auto Reboot; in the ROM post it said to un check it. After the kernel completed I did a battery pull. I used the volume up + power combo to hit recovery. I did a clear cache and D Cache. Then installed the ROM. Thank you for all your help. I really appreciate it!

Good deal! Glad the jig worked for you. I have had an amazing battery life and modem/GPS functionality with 5.41 while keeping lagfix/extra 4 disabled.
Re: your 1.2 Q. Go to settings > about phone > kernel version. It should say 1.7 from the flashing of 5.5.
-- SGS i897 Captivate using:
Continuum 5.5 w/ Talon 1.7 [rfs all, OC/UV, TW4, no theme, no tweaks enabled, & NETFLIX!)