[Q] How to: Root and flash Custom ROM - Galaxy S I9000 Q&A, Help & Troubleshooting

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**

Related

[Q] PLEASE HELP! phone booting then black screen

this is what happened
i installed sgs tools...tried the hacked camera.apk
since that was not working, i tried reverting it by running the restore script....
when i opened camera, my screen became black and it has stayed ever since...
i restart my phone and it shows the boot screen, the s shimmers for a long time and then black screen again....
and i cant seem to get into recovery mode.... i have tried many times...
EDIT:got into recovery mode after 100 tries....what do i do now?
i have tried wiping data, and clearing the cache....doesnt solve the issue...
my phone is rooted.....i dont think i'll have warranty..
please help!!!!!
if you have 3 button combo working (download mode working) find some rom which you want to install and do it by odin.
best to find middle package (Richtchofen ones with his instructions, they quite plain and simple)
you could try put only pda part of the rom without repartition
if it will be stock room the same as you have now in your phone your warranty will be untouch
Sent from my GT-I9000 using Tapatalk
If you were on froyo flash back stock rom (2.1) but first flash 512 pit file with pit, then the phone is,only startable in download mode, then flash stock rom with repartion and,everything ticked..
btw i had oclf by ryan installed...
what should i do?
i do not wanna brick my phone
i downloaded samsung's latest froyo firmware to install?
should i refrain from installing that?
sidh10 said:
btw i had oclf by ryan installed...
what should i do?
i do not wanna brick my phone
i downloaded samsung's latest froyo firmware to install?
should i refrain from installing that?
Click to expand...
Click to collapse
just wipe cache and memory then flash to stock rom not froyo it will not help so go eclair then froyo
Ajjter said:
just wipe cache and memory then flash to stock rom not froyo it will not help so go eclair then froyo
Click to expand...
Click to collapse
i tried flashing froyo....it didnt work...just as you said it wouldnt...it starts up and vibrates randomly.......will try eclair now...hope it works....finally...
there wont be any problems flashing now will there?
i tried eclair...
it has three files....
i am stuck on partition since 15 mins...what to do?please please help.
No make sure you flash the stock fw and use the 512 pit and have all options,ticked
Just find and read instruction how to proper repartition phone and flash it in Richtrofen posts (short and simple) which include links to roms.
do as it said and your phone will be working fine. mine was exactly on the same state few times and repartition with stock rom always helped
sent from my i9000 running stock 2.2.1 froyo using tapatalk
it finally worked!!!!!!!!!!!!!yes yes yes!
thank you thank you! though i did have to start with chinese....and i took a long time to boot...
Hehe dont use oclf use voodoo lag fix on 2.2 instead mate

[Q] Kernel flashing confusion with speedmod and Voodoo

Hi everyone, it's my first post here and I'm majorly confused.
What's going on? In a nutshell, I somehow can't fully flash the voodoo kernel.
Let me first describe my setup:
Samsung Galaxy S GT-I9000 with 2.2.1 FROYO.XWJS5 firmware.
For flashing I'm using Odin v1.7 running on a Sony Vaio Win 7 laptop and the Samsung supplied USB cable directly from the USB port, no hub or anything.
With that setup (unflashed kernel, no tweaks) my phone scored between 950 and 1050 points with Quadrant.
I am root
So what did I do?
After reading about the audio improvements that voodoo can make, I wanted to flash the Voodoo kernel from dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-unsigned-update.zip
When I enter recovery mode (up+home+power) all I get is the < 3e > recovery mode which doesn't have any other useful option than run update.zip. When I rename the kernel's zip file to update.zip it of course won't let me run it since it's unsigned.
So I used Odin with dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda.tar
I put the phone in download mode (down+home+power), start Odin v1.7, add the .tar as PDA and the only(!) boxes checked are Auto Reboot and F. Reset Time.
I then connect the phone via USB, the box saying something like 0:COM9 turns yellow and I start the flashing.
It seems to flash and reboots, but I get no options and it obviously doesn't convert anything since the boot time is normal. Entering "mount | grep -i ext4" in the terminal doesn't return anything and the Quadrant score stays the same.
Booting into recovery gives the same old < 3e > recovery. BUT the settings->about tells me that I have 2.6.32.9 curio carton #Voodoo_stable_5.4.1 running. So I install the Voodoo Control App 0.8.4 and it seems to work since I can set force analog vol. key and set the analog output level with it.
But seemingly no lag fix. So I enter IRC project-voodoo and ask for help. Among others, phalanger takes care of me. After trying various methods (ROM Manager, Odin, SGS Kernel Flasher) I flashed the speedmod-kernel-k13c-500hz-CWM kernel (dl from xda) with Odin. This worked flawlessly, and I now can boot into CWM recovery.
Here it get's weird. I applied the lagfix (converted to ext4), which worked smoothly. Quadrant scored 1300 points, "mount | grep -i ext4" returned something and the system was snappier. Cool, I thought, let's see what happens if I now run the Voodoo .zip from the CWM recovery, which I did without reverting to rfs. It worked, but it reset my firmware.
So I again flash speedmod with Odin, revert to rfs (data, cache and dbdata are now rfs) and restore a backup from before the lagfix (all this in CWM recovery). The phone is back to "normal", I have all my apps and the speedmod kernel, but of course no ext4! And now Quadrant still scores around 1200 points, how is that possible? I now again used SGS Kernel Flasher to flash the Voodoo Kernel to give me the audio options, what seemingly works, but I'm very confused.
Why can't I run the Voodoo lagfix, why do I still have < 3e > recovery and why isn't the phone running faster?
Davestar2000 said:
Hi everyone, it's my first post here and I'm majorly confused.
What's going on? In a nutshell, I somehow can't fully flash the voodoo kernel.
Let me first describe my setup:
Samsung Galaxy S GT-I9000 with 2.2.1 FROYO.XWJS5 firmware.
For flashing I'm using Odin v1.7 running on a Sony Vaio Win 7 laptop and the Samsung supplied USB cable directly from the USB port, no hub or anything.
With that setup (unflashed kernel, no tweaks) my phone scored between 950 and 1050 points with Quadrant.
I am root
So what did I do?
After reading about the audio improvements that voodoo can make, I wanted to flash the Voodoo kernel from dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-unsigned-update.zip
When I enter recovery mode (up+home+power) all I get is the < 3e > recovery mode which doesn't have any other useful option than run update.zip. When I rename the kernel's zip file to update.zip it of course won't let me run it since it's unsigned.
So I used Odin with dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda.tar
I put the phone in download mode (down+home+power), start Odin v1.7, add the .tar as PDA and the only(!) boxes checked are Auto Reboot and F. Reset Time.
I then connect the phone via USB, the box saying something like 0:COM9 turns yellow and I start the flashing.
It seems to flash and reboots, but I get no options and it obviously doesn't convert anything since the boot time is normal. Entering "mount | grep -i ext4" in the terminal doesn't return anything and the Quadrant score stays the same.
Booting into recovery gives the same old < 3e > recovery. BUT the settings->about tells me that I have 2.6.32.9 curio carton #Voodoo_stable_5.4.1 running. So I install the Voodoo Control App 0.8.4 and it seems to work since I can set force analog vol. key and set the analog output level with it.
But seemingly no lag fix. So I enter IRC project-voodoo and ask for help. Among others, phalanger takes care of me. After trying various methods (ROM Manager, Odin, SGS Kernel Flasher) I flashed the speedmod-kernel-k13c-500hz-CWM kernel (dl from xda) with Odin. This worked flawlessly, and I now can boot into CWM recovery.
Here it get's weird. I applied the lagfix (converted to ext4), which worked smoothly. Quadrant scored 1300 points, "mount | grep -i ext4" returned something and the system was snappier. Cool, I thought, let's see what happens if I now run the Voodoo .zip from the CWM recovery, which I did without reverting to rfs. It worked, but it reset my firmware.
So I again flash speedmod with Odin, revert to rfs (data, cache and dbdata are now rfs) and restore a backup from before the lagfix (all this in CWM recovery). The phone is back to "normal", I have all my apps and the speedmod kernel, but of course no ext4! And now Quadrant still scores around 1200 points, how is that possible? I now again used SGS Kernel Flasher to flash the Voodoo Kernel to give me the audio options, what seemingly works, but I'm very confused.
Why can't I run the Voodoo lagfix, why do I still have < 3e > recovery and why isn't the phone running faster?
Click to expand...
Click to collapse
OK for me, you are confusing the hell out of yourself by doing too much at once.
If you are willing, then I would try the darkys resurrection method, I KNOW this will install the kernel and also initiate lagfix, as you indicated, you should hear it talking to you during the long boot.
With you doing so many things at once, not sure where the issue may be, but try the above and see if you get the same results as most people do.
Heh, that's true, too many things at once.
I looked at the Darky's ROM Resurrection Edition tutorial and noticed something. The attached image is from said tutorial, and when I flash a kernel with Odin it says Removed! before Completed...
Is that an issue?
Davestar2000 said:
Heh, that's true, too many things at once.
I looked at the Darky's ROM Resurrection Edition tutorial and noticed something. The attached image is from said tutorial, and when I flash a kernel with Odin it says Removed! before Completed...
Is that an issue?
Click to expand...
Click to collapse
THAT threw me as well, I 'think' all it is referring to is the fact it has 'removed' the serial port interface (USB) when it does the reboot.
The reason for suggesting darkys, is the lagfix thing, if you don't need to use it (I don't, mine is fine without it) then you can also try this one
http://forum.xda-developers.com/showthread.php?t=926399
This fixed me up when I did a boo boo, learnt me a few things in the process as well.
At some point, I will make my own install and instructions, I used to write technical instruction manuals, maybe I need to do some for here LoL
I tried the resurrect ROM, didn't work as planned. Step1 worked fine (basic ROM) but it wouldn't install the CWM recovery with the Voodoo kernel, and as a consequence it of course wouldn't let me run the resurrect.zip in the second step.
I now reverted to JPY (2.2.1) from Samfirmware, installed the speedmod kernel via Odin and will shortly flash the Darky v9.2 from the internal SD. We'll see how that works.
I think the whole trouble is caused by the JS5 bootloader, maybe?!
The fresh JPY scored 1326 points in Quadrant...
Okay, with the CWM recovery (thanks to speedmod kernel) installing the v9.2 Rom from the SD worked fine. I'm now running 2.2.1 I9000XXJPY with the 2.6.32.9 Voodoo_stable_5.4.1 kernel.
Now I again have the problem that I don't have the CWM recovery. When I enter the recovery it's plain old <2e>. What's going on here?!
Davestar2000 said:
Okay, with the CWM recovery (thanks to speedmod kernel) installing the v9.2 Rom from the SD worked fine. I'm now running 2.2.1 I9000XXJPY with the 2.6.32.9 Voodoo_stable_5.4.1 kernel.
Now I again have the problem that I don't have the CWM recovery. When I enter the recovery it's plain old <2e>. What's going on here?!
Click to expand...
Click to collapse
reflash the kernel
Tried that, maybe 20 times, to no avail. Different methods, from withing speedmod CWM recovery, SGS kernel flaser and Odin. Nothing.
Now back to JPY with speedmod and lagfix. Scoring around 1300 with Quadrant. I Don't think I'll flash anything till 2.3 comes out...
Davestar2000 said:
... I Don't think I'll flash anything till 2.3 comes out...
Click to expand...
Click to collapse
Dang: http://forum.xda-developers.com/showthread.php?t=974117
Edit: The irony...had I checked samfirmware maybe an hour later...

[Q] Galaxy S i9000 softbricked; won't enter recovery or reflash from download mode

Similar to Masterslackers issue.
The phone was originally a stock Optus Éclair 2.1. About 6 months ago I decided to customize the i9000 with a custom Froyo 2.2.1 Rom (Doc's Rom Docs_XWJS3_Wipe-v9_1) from “The ROM Kitchen”. It worked really well and was much faster and responsive..
Yesterday, I decided to look at a move to Gingerbread and cook another ROM @ the ROM Kitchen, this time a Gingerbread 2.3.4 iteration.
The phone was rooted so I used Rom Manager to get into recovery mode where I could flash my new, Doc's JVR_No_Wipe-v8-00-08-22-10-09-4e6a8e4e86718.zip Rom.
All seemed to go well, but after the Flash, as the phone booted the first screen became filled with 100s of random coloured lines, then it transitioned to the normal Samsung start animation, but soundless.
After booting, I noticed that I no longer had a notification bar where battery, time, signal strength etc. was normally displayed atop the screen. I tried several different launchers to see if that was the issue, but to no avail. I tried to enable the notification bar using Go Launchers gesture setting (no go)
I tried rebooting the phone over and over, the notification bar would not return.
I was starting to lament my decision to flash when the following occurred.
I tried to re-enter recovery mode via ROM Manager to install a different ROM, but the phone bypassed it and then hung @ the Samsung I9000 logo screen. I then had to power the phone off before it would reboot into its UI. I could no longer reach recovery mode by any means.
Because I was getting nowhere and I had read that after flashing a new rom, root would often be lost, so I tried rerooting with "XXJVP-Complete-Rooting-Package" from
http://androidadvices.com/how-to-root-galaxy-s-on-android-2-3-4-xxjvp-firmware/ This also failed but it has also left me with a soft bricked phone.
The phone will not boot up or boot into recovery now, however It would still boot into (3 button) download mode.
I have tried various versions of Odin from v1.0 to v4.28 to ReFlash the phone back to life but with no success yet.
Using Odin, the phone hangs with no sign of progress and reports the following when left for 30minutes or so.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
Anyone have any suggestions that might help to get the phone back.
Thanks, TeZ
So you didn't flash stock gingerbread before flashing custom rom? so you should first flash stock jvr and do hard reset after booting. Then you are safe to flash cwm capable kernel and custom rom.
For the odin problems, maybe you have kies running in background? Kill all kies processes and try again.
And I'd suggest reading all guides found in romkitchen thread..it saves lots of trouble. Hope that can fix your phone
Sent from my GT-I9000 using xda premium
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Thanks for that, I did install kies after I bricked it, in the hope (probably missguided) that it would somehow help. Uninstalling
bigmadpete said:
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
Click to expand...
Click to collapse
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Your post looks promising, I'm going to try this method out and see where it leads. I'll reply back with the outcome, many thanks
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
bigmadpete said:
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
Click to expand...
Click to collapse
Thanks for the info, running out of time today, will try for tomorrow
When moving from a froyo (2.2) rom to gingerbread, (2.3), you need the gingerbread bootloaders or you'll get all sorts of crap when turning on your phone (ie what you have).
Use odin to flash back to froyo, or flash a gingerbread firmware that comes with bootloaders. (I would recommend going back to froyo first to make sure everything is ok, since flashing bootloaders is a bit risky, as messing it up can permanently brick your phone)
cobrasixtysix said:
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
Click to expand...
Click to collapse
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Ok, here's where I'm at:
For the sake of simplicity I will detail what gave positive results rather than a tirade of what didn't.
Uninstalled Kies, rebooted
As instructed, went to:
http://forum.xda-developers.com/showthread.php?t=1102881
downloaded: Odin v1.82
downloaded: Gingerbread 2.3.3 (Australia and New Zealand)
XWJVN/XXJVQ/XSAJV5/Sbl (CSC: XSA): Download (150 MB) (Build date: Sun Jul 10 11:30:54 KST 2011)
Loaded up Odin and followed instructions.
Flash went ahead as normal and I now have a working phone again, thanks to you DSGE, I'm a very happy man
So I now have Gingerbread 2.3.3 installed and running.
My only issue's now is, that.
1. Half my apps dont work now or force close even after a reinstall.
2. Some apps won't install at all IE; my fav launcher; Go Launcher
3. I no longer have root access so Rom Manager and Titanium backup wont work.
4. My Backup Pro, works after I rewrote the correct path to the External Sd, but do I want to do that just yet? and just how much data should I reinstate so I don't corrupt the new system?
What should I do now?
Install busybox?
do a hard reset?
Flash a different Rom that will work for me?
Thanks so very much for all the good advise.
Cheers
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
bigmadpete said:
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
Click to expand...
Click to collapse
OK, latest update:
Everything is working fine including all my progs.
Like you say, I just need to root it now.
Can you point me to the correct files to root?
Thanks
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
bigmadpete said:
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
Click to expand...
Click to collapse
Seems to relate to 2.1 to 2.2.1 didn't see any mention of 2.3.3. I'm afraid I'll stuff the phone if I use the old root files.

[Q] Captivate ODIN doesnt see Cappy, in DL mode too

In normal running mode ODIN sees the Cappy, but when I switch to download mode it doesn't see it any more. I am trying to put my phone back to factory default so I can install CM7 but running into all kinds of problems. I did get the base system reinstalled using a One Click JAR that I found here on XDA. The phone seems to be ok with that.
ADB doesnt think there are any devices attached either when I am in download mode.
I did also try the Heimdall install methods and used their drivers, but that doesnt work either
All I am trying to do so far is get CWM installed
Any ideas?
Did you ever use Heimdall?
MarkWorsnop said:
In normal running mode ODIN sees the Cappy, but when I switch to download mode it doesn't see it any more. I am trying to put my phone back to factory default so I can install CM7 but running into all kinds of problems. I did get the base system reinstalled using a One Click JAR that I found here on XDA. The phone seems to be ok with that.
ADB doesnt think there are any devices attached either when I am in download mode.
I did also try the Heimdall install methods and used their drivers, but that doesnt work either
All I am trying to do so far is get CWM installed
Any ideas?
Click to expand...
Click to collapse
If you used a one-click jar file, I believe you used Heimdall, as Odin-based one-clicks would be .exe files. That being the case, if one of the one-click heimdalls worked, other ones should work as well.
If you don't mind me asking, which one-click did you use? What rom were you on when the other one worked, and what rom are you on now?
I installed this "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" to get it to work in what I think is a factory default.
I am now trying to get the downloading to be recognized by Odin or Heimhall or anything/.
They all see the phone in normal mode but when in download they do not see it
Have you tried all of the USB ports on your computer? If you're on a desktop, make sure it's one of the ones in the back (directly attached to the motherboard). Also, if you haven't rebooted your computer, do that, and then see if the UCKB2 one-click sees your device.
You can also try the full heimdall package, as that has a tool that will quickly check to see if it sees a device in download mode.
ODIN doesnt see Cappy
Looks like the drivers from Heimhall mess up the ODIN drivers. I removed the drivers from System Drivers that the Heimhall installed and now the ODIN seems to see the device again.
Now I need to figure out what I need to put on the device to make it work
MarkWorsnop said:
I installed this "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" to get it to work in what I think is a factory default.
I am now trying to get the downloading to be recognized by Odin or Heimhall or anything/.
They all see the phone in normal mode but when in download they do not see it
Click to expand...
Click to collapse
einstall the Samsung drivers. The zadig driver you installed for Heimdall causes problems with dl mode if you then try to use Odin.
mrhaley30705 said:
einstall the Samsung drivers. The zadig driver you installed for Heimdall causes problems with dl mode if you then try to use Odin.
Click to expand...
Click to collapse
I just figured this out. Now what CWM file does ODIN want? After all of this I am lost! I will start back at the first post on adding CWM I guess...!!
It's going to want a kernel with CWM baked into it, or you can flash the JF6-based one click file to get back to stock without the 3e recovery error. From there you can just root, then copy the rom you want to install to your internal SD card. Rename it "update.zip", and flash that.
If memory serves me correctly, that's the simplest way to flash from Eclair. You can also try to Odin in a CWM-friendly Froyo kernel, or copy the cwm file out of the AIO captivate toolbox (copy it out, don't directly use the tool).
To get cwm, use a kernel with cwm as jimtheiss said, in a tar format. Older Talon kernels were in tar, as was Speedmod, and I think xcal's reoriented kernel had a tar version.
Open Odin, use the pda slot for the kernel, uncheck reboot. Connect phone. When the yellow box lights up, hit start. When completed, pull the battery,reinsert battery, use button combo to get in recovery.
jmtheiss said:
It's going to want a kernel with CWM baked into it, or you can flash the JF6-based one click file to get back to stock without the 3e recovery error. From there you can just root, then copy the rom you want to install to your internal SD card. Rename it "update.zip", and flash that.
If memory serves me correctly, that's the simplest way to flash from Eclair. You can also try to Odin in a CWM-friendly Froyo kernel, or copy the cwm file out of the AIO captivate toolbox (copy it out, don't directly use the tool).
Click to expand...
Click to collapse
I can't seem to find Eclair with CWM. I did find a I897UCJF6-final-OCD-REV0 EXE with ODIN built into the EXE but whatever happens on that version ODIN didnt see the phone.
The ODIN 1.85 sees the phone, but I do not know what to download and what there downloaded file goes in ODIN.
I also ran the JAR file again and it did get back to 2.2 but then I dont seem to be able to get CWM working.
All I wanted to do it put CM7 on the phone. I guess I have to have Eclair or Froyo first to get the CM7? I think that is what I read. I havent tried it from GB
I would suggest following mrhaley's directions about flashing the kernel.
And here is the speedmod kernel.
MarkWorsnop said:
I can't seem to find Eclair with CWM. I did find a I897UCJF6-final-OCD-REV0 EXE with ODIN built into the EXE but whatever happens on that version ODIN didnt see the phone.
The ODIN 1.85 sees the phone, but I do not know what to download and what there downloaded file goes in ODIN.
I also ran the JAR file again and it did get back to 2.2 but then I dont seem to be able to get CWM working.
All I wanted to do it put CM7 on the phone. I guess I have to have Eclair or Froyo first to get the CM7? I think that is what I read. I havent tried it from GB
Click to expand...
Click to collapse
My 2 cents....if you have so much difficulty using Odin/Heimdall, I would highly recommend staying away from CM7 or MIUI until you are really comfortable flashing stuff without hiccups. CM7 and MIUI are quite different beasts, compare to the ROms ur flashing.
chappatti said:
My 2 cents....if you have so much difficulty using Odin/Heimdall, I would highly recommend staying away from CM7 or MIUI until you are really comfortable flashing stuff without hiccups. CM7 and MIUI are quite different beasts, compare to the ROms ur flashing.
Click to expand...
Click to collapse
The only thing he needs to flash with Odin/Heimdall is the kernel to get cwm. Its the same for most other GB roms. After you get cwm, its just flashing from cwm, with an extra factory reset and ROM flash.

[Q] Download mode menu missing

Hi guys. Recently I bought a used I896 with I897UCKF1 2.3.3 firmware. I cannot root it or upgrade it to ICS cos I have a problem: when I press vol down button plus power button to enter download mode the phone boots normally. When I press vol up plus power button instead of recovery mode my phone enters "Android system recovery <3e>". Any advice what to do?
The combination for recovery is vol up/down+power. You will need to flash a kernel with ClockworkMod recovery baked in.
Why didn't you also tell him the proper dl mode combo?
Anyway... Its both volume buttons only, no power at all, and inserting a USB cable that boots into download mode.
[QUOTEAnyway... Its both volume buttons only, no power at all, and inserting a USB cable that boots into download mode.[/QUOTE]
Thans a lot man. My Cappy is now rooted and having 2.3.5. Right now I'm looking for a stable ICS rom. Any suggestions will be appreciated.
korockinout13 said:
The combination for recovery is vol up/down+power. You will need to flash a kernel with ClockworkMod recovery baked in.
Click to expand...
Click to collapse
Can you recommend me a kernel with cwm recovery? In my Samsung recovery menu 3e I do not have "install zip from sd card" option. Or may I use Rom Manager Premium to install ICS .zip rom?
If you are on Gingerbread and an i897 rom (KF1 would meet that requirement), you can flash boog's kernel, which will have CWM baked in.
You'll need to use something like Odin or Heimdall to get there, which boog includes in the files listed above.
The other option is to flash a stock rom with a CWM kernel included, like the one in my signature.
I'm on UCKK4 - 2.3.5. Is it ok to flash that kernel? And I ask you guys who have ICS on your Cappy is it worth to install it now or should I wait for more stable versions?
You should be able to use Boog's kernel. If you want to be 100% sure of a match, you can try corn kernel KK4.
ICS is pretty great, but be aware there is a risk (although small) of the internal SD card being messed up. Look for "Encryption Unsuccessful" in the development forum - if you flash ICS, just know what to do if that situation happens.
Hmm, you made think about it. I'm not so sure anymore about ICS. I think it's better waiting for a while. I also have a i9000 and installed ICS on it and there was a problem with external sd.
Finally I installed a 4.0.3 rom and I have to admit it was a mistake. Now I'm looking forward to get back to UCKK4 2.3.5 but I don't really know how to do it. On my internal memory I have the backup of the 2.3.5 version made before getting to 4.0.3 and I tried to restore it from the recovery menu but it doesn't work. I think I'm missing something. Can you help me? Thankx.
erycx said:
Finally I installed a 4.0.3 rom and I have to admit it was a mistake. Now I'm looking forward to get back to UCKK4 2.3.5 but I don't really know how to do it. On my internal memory I have the backup of the 2.3.5 version made before getting to 4.0.3 and I tried to restore it from the recovery menu but it doesn't work. I think I'm missing something. Can you help me? Thankx.
Click to expand...
Click to collapse
You'll need to flash back to the 2.3.5 rom you had before flashing to ICS (whatever rom you were using when you made the backup), then restore the backup in recovery.
jmtheiss said:
You'll need to flash back to the 2.3.5 rom you had before flashing to ICS (whatever rom you were using when you made the backup), then restore the backup in recovery.
Click to expand...
Click to collapse
Can you be more specific please? What are the steps I need to follow?
AOKP build 32 is very stable for me if your looking to give ics another chance. Make sure you do all the proper wipes before flashing.
Sent from my glitched ICS Captivate using XDA App
erycx said:
Can you be more specific please? What are the steps I need to follow?
Click to expand...
Click to collapse
Grab an Odin or Heimdall one-click to get back to stock KK4, and flash that. Once you've flashed back to stock KK4, if you were using any custom rom (anything non-stock), flash that to your phone. (The idea is to be as close to your previous setup as you can be.)
Once you've done those steps, reboot into recovery and go to "backup/restore". In the restore options, look for the backup you made and restore it.
cmilldrummin said:
AOKP build 32 is very stable for me if your looking to give ics another chance. Make sure you do all the proper wipes before flashing.
Click to expand...
Click to collapse
Ok, if you say so, I'll try it. It crossed my mind to give ICS the second chance but I didn't know exactly what rom to try. I supose I need to do a wipe cache from recovery mode and after this I have to use the option install from sd card? Am I right?
What ROM are you coming from before ics?
Sent from my glitched ICS Captivate using XDA App
jmtheiss said:
Grab an Odin or Heimdall one-click to get back to stock KK4, and flash that. Once you've flashed back to stock KK4, if you were using any custom rom (anything non-stock), flash that to your phone. (The idea is to be as close to your previous setup as you can be.)
Click to expand...
Click to collapse
Till now I used only Odin. I have this file on my pc: I897UCKK4_I897UCKK4_I897UCKK4_HOME.tar.md5. Is this ok to flash this with Odin in "pda" or "phone" section?
cmilldrummin said:
What ROM are you coming from before ics?
Sent from my glitched ICS Captivate using XDA App
Click to expand...
Click to collapse
I897UCKK4
erycx said:
Till now I used only Odin. I have this file on my pc: I897UCKK4_I897UCKK4_I897UCKK4_HOME.tar.md5. Is this ok to flash this with Odin in "pda" or "phone" section?
Click to expand...
Click to collapse
I'm not sure what that file is - it may be fine, but I don't want to say "flash away!" and leave you with a messed up phone.
I would suggest going here and grabbing the non-bootloader Odin one-click (assuming one-clicks have worked for you in the past). Flash that, and you should be good to go with KK4.
erycx said:
Till now I used only Odin. I have this file on my pc: I897UCKK4_I897UCKK4_I897UCKK4_HOME.tar.md5. Is this ok to flash this with Odin in "pda" or "phone" section?
Click to expand...
Click to collapse
that is safe to flash. that is the kk4 stock.
that is all i have to add to this discussion.

Categories

Resources