[Q] i9000 halts after Semaphore CWM installation - Galaxy S I9000 Q&A, Help & Troubleshooting

So I have this old Samsung i9000 lying around and I wanted to give it a new life with an update (ran Android 2.2, so it was pretty useless).
I started by looking up all installation instructions I could find (took me a whole day to make sure I had it right) and the procedure was:
Update to CM9 first, then update to newest CM.
Pretty simple I thought. But as usual I ran into some troubles I can't get myself out of. That's why I'm asking you guys to help out.
What I did: set up all the drivers and downloaded the Heimdall suite and Semaphore 2.7.4 CWM. Then ran the "heimdall flash --kernel zImage --no-reboot" command. It uploaded the zImage to the phone. Pulled the battery, booted with Vol Up & Home & Power. At this point I'm stuck on the GALAXY S GT-I9000 SAMSUNG boot thingie. When I press Vol Up & Vol Down & Power it seems as if it bootloops. The boot thingie flashes.
I can't get into the system, I can't get into recovery, I can however set it up to download stuff (the yellow under construction Android sign), so I'm guessing there is a possibility to upload something else that works in stead...

Lex_Michdeandroid said:
I can't get myself out of. That's why I'm asking you guys to help out. .
Click to expand...
Click to collapse
Just to let you know what you did wrong.
when you have a 2.2 froyo ROM, you cannot flash a gingerbread kernel on it and hope to get it booting.
The solution is , just follow this guide and flash the gingerbread ROM as mentioned after that you can chose what custom ROM you want on it .
Check this out! You , YES! you are an " Android ". Not your phone but U.​

Lex_Michdeandroid said:
So I have this old Samsung i9000 lying around and I wanted to give it a new life with an update (ran Android 2.2, so it was pretty useless).
I started by looking up all installation instructions I could find (took me a whole day to make sure I had it right) and the procedure was:
Update to CM9 first, then update to newest CM.
Pretty simple I thought. But as usual I ran into some troubles I can't get myself out of. That's why I'm asking you guys to help out.
What I did: set up all the drivers and downloaded the Heimdall suite and Semaphore 2.7.4 CWM. Then ran the "heimdall flash --kernel zImage --no-reboot" command. It uploaded the zImage to the phone. Pulled the battery, booted with Vol Up & Home & Power. At this point I'm stuck on the GALAXY S GT-I9000 SAMSUNG boot thingie. When I press Vol Up & Vol Down & Power it seems as if it bootloops. The boot thingie flashes.
I can't get into the system, I can't get into recovery, I can however set it up to download stuff (the yellow under construction Android sign), so I'm guessing there is a possibility to upload something else that works in stead...
Click to expand...
Click to collapse
First of all flash XXJVU official and its root. You will surely get out of the problem.
Read my post in the below link. I tried the process easy as much as I could.
forum.xda-developers.com/showthread.php?p=47034690#post47034690

Of course... I'm an idiot... I thought I would have the newest update from OTA, but didn't check what was the latest official OTA...
Anyway, back to the lab, will update as soon as possible.
Edit: filerio is really ****ty... I'm going to try to find other downloads...
Edit2: got files from Rohitdahiya's post, now waiting for downloads to complete
Something else, the yellow thing isn't coming up in Odin, so I guess that will be my next problem. I can't put the phone in 'debug mode' because the main system doesn't start. Also something that occurred to me was that when charging the big green battery doesn't come on screen anymore. It just shows a static circle of bars...
Heimdall could connect to the phone no problem... Downloaded the Heimdall rescue kit, but I'm not sure how to use it...
Edit3: And indeed the Odin software doesn't recognize the damn thing... Trying to find an install for this KIES.exe to make sure I have the right drivers installed...
Edit4: Awesome. KIES starts "Installing device drivers. This may take several minutes." and never stops... Now my device isn't detected anymore... Just great.
Edit5: I reinstalled drivers with Zadig. Found out Heimdall rescue was just a .bat file... I already said I am an idiot right? Anyway, now trying the rescue kit again...
Edit6: Using the Heimdall rescue was all there was to it... I'm retarded! Had this rescue kit sitting there for a week and it didn't occur to me to JUST USE THE GAWDDAM BATCHFILE INSIDE THE GAWDDAM FOLDER...
Anyway! After running the "Restore.bat" file and choosing the 1. option (Flash and repartition) it went on doing all kinds of good stuff and now I'm running 2.3.6... Now for the next step, getting it to run the latest CM (or a variant).
Edit7: Okay, good things come to those who wait. Started all over after getting the 2.3.6 on the device. Followed CM instructions:
-USB Drivers through Zadig
-Put the phone in download mode (Vol Down + HOME + Power), plug in USB
-Extracted the zImage from the .tar into the folder that holds heimdall.exe
-Run "heimdall flash --kernel zImage --no-reboot"
-Make sure he's done, take battery out, reboot into recovery (Vol Up + HOME + Power)
Find out it's working fine! THANK YOU!
Now I'm going to see if I can get the latest CM running. Again, thanks!

Related

[MOD] Fix for hardware locked phones / cant access recovery without adb.

NOTICE 10/18/2010:
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47
I can vouch for this. It worked exactly as described.
Thanks!
Just to make sure after I do this I can flash any rom through odin without problem?
bobby915 said:
Just to make sure after I do this I can flash any rom through odin without problem?
Click to expand...
Click to collapse
I have flashed JFD, JI6, JI6 unofficial, JI6 OTA after flashing this and have had
no problem's
in general these files are written to parts of the phone that are usually never
written again after manufacturing and are responsible for getting the hardware
ready to load the kernel and then loading the kernel and booting the phone and
should not have any issues loading any ROM you care to flash.
Right now I can access download mode intermittently (maybe 1/10 times) by holding vol-up-down + power with usb plugged in. I cannot access recovery mode at all. Will this flash ruin my ability to access download mode? I feel like download mode is more important than recovery in case of a brick, but I would like the ability to go to recovery without adb or rom manager.
I've tried this 5 times, ODIN says failed everytime,EDIT Apparently 3rd times the 3rd time is the charm cause the 9th time it worked, Second Edit, The 9th time it started but its been 10 minutes so I assume it froze, Dammit.
Persanity said:
I've tried this 5 times, ODIN says failed everytime, Apparently 3rd times the 3rd time is the charm cause the 9th time it worked
Click to expand...
Click to collapse
So your recovery works now? Can you also get into download mode?
I'll add my Vibrant to the list of previously hardware locked phones, fixed by this.
I'd like to send out a HUGE thanks. Recovery and Download mode work every single time now. I can start playing around with roms safely.
Thank you so much
STEP BY STEP GUIDE
**UPDATE**10/14/10
STOCK RECOVERY VERSION OF HWLOCK FIX
untermensch has created a UPDATE.ZIP version of the fix
1) Download UPDATE.ZIP from OP or here http://www.megaupload.com/?d=2R2XOZ0X
2) Place UPDATE.ZIP in root of /sdcard not /sd
(If you have a previous UPDATE.ZIP file in root of /sdcard move it to another folder untill you have unlocked)
3) Use ADB to get into recovery
(use step posted below if you dont know how to use ADB)
(use command "adb reboot recovery")
4) Use vol down to navigate to reinstall packages press power to select
ODIN VERSION OF HWLOCK FIX
**NEW**
untermensch test file
(download from OP)
Everything you need minus drivers(or download individually in steps below)
http://www.megaupload.com/?d=66SSG9VR
step 1) go here and get the drivers and install them
http://forum.xda-developers.com/showthread.php?t=728929
step 2) download this zip file
http://forum.xda-developers.com/attachment.php?attachmentid=415810&d=1286579010
(load tar file from this zip in PDA section of odin after step 4)
step 3) go here download and follow guide to setup adb
http://forum.xda-developers.com/showthread.php?t=502010
(use "adb reboot download" to get to download mode)
step 4) go here get odin v 1.3
http://forum.xda-developers.com/showthread.php?t=790026
(run odin load tar in PDA make sure com4 or similar pops up click start)
FOR THOSE WHO NEED ADB HELP
REBOOT TO DOWNLOAD MODE WITH ADB
*must have drivers installed*
1) download androidSDK from here http://developer.android.com/sdk/index.html
2) extract the folder to root of your harddrive and rename it something short like ADB
3) on phone go to settings , applications , development and click USB debugging
then plug your phone into the computer
4) open windows command prompt and type this (hit enter after each line)
cd c:\
cd ADB\ (or whatever you renamed the folder in step 2)
cd tools\
adb reboot download
5) flash tar with odin
Sent from my SGH-T959 using XDA App
No, It did not work, The 9th time it actually started instead of saying failed immediately, But after 20 minutes nothing had changed and then odin cr5ashed and now my phone is soft-bricked/bricked whatever it is. All I know is im ****ing pissed. Can somebody point me in the direction of a complete restore thread? EDIT: Yeah I finally got it, Thank god I have never had a problem getting into download mode, When I say got it I mean restoring my phone to work not getting recovery to work, If I flash J14 first then J16 am I gonna lose the ability to go into recovery mode if the J14 update does actualy let my phone go into recovery?
untermensch said:
The leaked JI4 firmware contained the files needed to get the our phones unlocked
attached is an odin flashable tar with sbl.bin, boot.bin when flashed your phone wont ignore
the vol up + vol down + power buttons and you will be able to access recovery.
if you haven't used odin before follow AgentFour20's instructions http://forum.xda-developers.com/showpost.php?p=8541107&postcount=35
note:
1. the port wont be com4 for everyone as long as odin shows a com port you should be fine.
2. you might not need adb this method worked on my locked phone http://www.youtube.com/watch?v=rqxearzXrVY
you can flash this over any ROM or firmware and will probably never have to flash it again because boot.bin, sbl.bin are rarely included in firmware.
as usual use caution when flashing your phone, I am not sure if you can get back into download mode if this flash fails, So flash at your own risk!
for more info check out the I9000 thread:
http://forum.xda-developers.com/showthread.php?t=785201
and the original thread:
http://forum.xda-developers.com/showthread.php?t=802763&page=3
Good Luck!
md5 for tar file = d18f9d23d3060260a4e7edc1b6321941
Click to expand...
Click to collapse
Gonna put in my vote for one recommendation for you people who have a dickens of a time getting into download mode and are afraid of Odin3 leaving you stranded.
Try using Odin3 v1.30 instead of Odin3 v1.00 (it's linked in the Bible thread). My failure rate on flashing with v1.30 so far is zero. My failure rate when I was flashing with v1.00 was more to the tune of 50% of the time. I'm not hardware locked, so this is less scary for me than it is for you.
Just a safety tip...Best of luck!
sounds like solution is simple, but why did this occur on some vibrants in the first place?
SamsungVibrant said:
sounds like solution is simple, but why did this occur on some vibrants in the first place?
Click to expand...
Click to collapse
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Awesome....used odin 1.3 and this took a few seconds and worked flawlessly
if you follow the instructions in the posts above, don't see how you can go wrong
I can now access download mode and recovery...and I can sleep a lot easier knowing that if something happens I can fix it now
Yes! Masterotaku thank you so much for posting about odin3 v1.3, 1st time it work for J14 over J16, I can now boot into download and recovery mode. Sweet.
masterotaku said:
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Click to expand...
Click to collapse
hmmm interesting, seems like samsung isn't consistent with their screen tints also. They need to get quality control under quality control
Wanted to add that this worked for me as well. Thanks for the info.
Worked on first try, Odin 1.3. Thank you so much for this fix! I knew holding out on replacing my vibrant would pay off =)
Now I got into recovery by both vol + power then release power, but how do you guys get into download mode? I used to be able to get there occasionally by doing that same key combo, but with usb attached.
EDIT: Wow that was easy.
RECOVERY MODE: Hold both volume buttons and power, once vibrant logo shows up, release power.
DOWNLOAD MODE: Hold both volume buttons (no power) and plug in USB. Instant!
EDIT: Honestly I can't thank you enough. This is so amazing!
Thanks so much, this really works, my 1st time ever using odin 1.3
and finally figure out what adb is. Before even pulling the battery would
not get me into download,and the only way to get into recovery was using
clockworkmod. This really works!!! thanks you thanks you.
Everything is not as good as it seems. I managed to flash the fix all right and now I have download mode. But my friend had done the same steps as myself but odin FAILED to flash the fix. It just said:
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
And his phone is totally bricked now.
It is really dangerous to use ODIN on hardware locked phones... Too high chance of failure to flash. ((

Odin successful, but still stuck in boot loop

TL;DR - Stuck in boot loop, can't enter recovery mode, but can enter download mode. Odin says it is successful, but the phone is still in the boot loop.
I've had Cognition 2.3 for a few months now and decided to update to Cognition 4.3. I used the AIO toolbox 2.5 to Odin one-click back to stock, rooted, and flashed to 4.3. Everything went well and I restored all my apps with Titanium and loaded some music.
At some point later the screen was completely blank and the only way I could get any response out of it was to hold the volume buttons and power buttons. Instead of going into recovery, though, it would boot to the Cognition boot screen and hang indefinitely.
I was able to get it into download mode by removing the sim and battery and holding the volume buttons while plugging it into USB and replacing the battery. I ran Odin one-click again, it said it was successful, but the phone was stuck in either a battery screen or AT&T screen boot loop (depending on whether or not it was plugged into USB).
I've tried using regular Odin with both the ROM included with AIO 2.5 (JF6*) and JH2 (from http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36) to no avail. Every time Odin shows that it is successful, but it always ends up in a boot loop with no ability to enter recovery mode.
What can I do? Will getting a jig help me in any way?
*Edited for correct ROM
Use the normal ODIN (v1.7 or v1.8), a full stock JF6 ROM and PIT file. Make sure "repartition" is selected and if possible, do a master clear with ODIN first (though shouldn't be critical.........then start over with Cog 4.3 if that's your ROM of choice (good choice by the way).
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
bharden said:
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
Click to expand...
Click to collapse
Are you using the PIT file and selecting repartition?
When I get home today, I will upload the ROM and PIT that I use to flash to stock and see if that helps but you do need to use the PIT and repartion which will only help if you have a FULL copy of JF6 that reloads the bootloaders.
Just out of curiosity, what is your build number?
I am using the PIT and selecting repartition. I've done this every time I've tried Odin (besides when using one-click of course) Is the PDA.tar listed in that link not a full copy of JF6?
My build number is 1008.
May sound crazy, but you could try using a different computer. I ran into a lot of problems using odin on my pc. Switched to laptop (more ram and windows 7 64 bit ) with great success. Also make sure you have the right drivers. Your build# should allow you to use odin one click.
Sent from my GT-I9000 using XDA App
I've actually already tried it from both my PC (Windows 7 x64, 4 GB ram) and my laptop (Windows Vista x86, 2 GB ram). In both cases I used the drivers in the AIO toolbox 2.5 (http://forum.xda-developers.com/showthread.php?t=944418)
Are those the correct ones? If not, could you point me to a resource with the latest drivers? There are quite a few versions floating around and I'm not sure which ones I should be using.
Any other suggestions?
Those should be the correct drivers
Also, make sure odin is completely open before connecting your phone.
That'd all I can think of.
Sent from my GT-I9000 using XDA App
I definitely did that.
Since I'm able to get into download mode, I should be able to un-brick it right? I can't figure out why Odin says it's successful but I still can't boot.
Does anyone else have any ideas?
You may have to give it a few minutes or so as I am uploading now but the link for the PDA and PIT is:
http://dl.dropbox.com/u/24576569/ATT%20ROM%202.1.rar
Try using this version of ODIN:
http://dl.dropbox.com/u/24576569/Odin3%20v1.7.rar
Hope this helps otherwise I am out of ideas except flashing a kernel with a recovery included through ODIN, going into the recovery and formatting and wiping absolutely everything and then reflashing JF6. But try the files I linked first.
Good luck.
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
bharden said:
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
Click to expand...
Click to collapse
Drop box seems to be running slow. So the JF6 that I am uploading may take a bit. The version of ODIN that You are running should be fine.
Try this Kernel. It's not a complete ROM just the kernel. If it works, you will have to flash a ROM too. Cognition is a good start. You can find it in the Dev section and actually, even if it's not the recommended way of flashing, I moght try flashing a custom ROM anyway just to rule out ODIN and your phone. If you can successfully flash a custom ROM then it's probably the version of JF6 that you are using.
Anyway, let's start with the kernel first:
Onix by existz:http://forum.xda-developers.com/showthread.php?t=930679
make sure you download 2.0.3 "tar" file for ODIN
you know how to get into recovery after you flash right? From powered off, hold the up and down volume buttons and then power all at the same time for about 5 second......
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
bharden said:
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
Click to expand...
Click to collapse
The three button combo should work to reset the phone when it's stuck as well as getting into recovery. It sounds like you aren't holding the buttons for long enough. If the phone is frozen, you have to hold the button combo for quite a while to get the phone to reset. Weh trying to get into recovery, push both volume buttons and then hold down the power button and don't let go till yoiu get past the AT&T screen.
If that still doesn't work, then try and load up the ROM and see if at least you can get a working phone back in the meantime. Like I said, I recommend Cog 4.3 but serendipity is a good choice too.
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
bharden said:
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
Click to expand...
Click to collapse
OK, so I've never had to mount SD from those options so not too familiar with this problem but, i am going to guess that we shouldn't have to play with this right now. Onix will let you install a zip from your external SD, so i recomend finding a recovery flashable ROM (almost all custom ROMs come this way....it'll be a ZIP file) Again I recomend using Cog 4.3 or serendipity (both of these may change your kernel but it's ok because they will both have a custom recovery).
Follow these steps:
1. Remove your external SD and insert it into your computer.
2. Remove any files you want to keep and place them somewhere on your computer for future recovery (Titanium backups, music, pics, etc....)
3. Format your sd (FAT32 should be default)
4. Download the ROM of your choice, copy it to the root of your external SD using your computer
5. Replace the SD into your phone power up into recovery
6. From the Onix recovery menu select "advanced options"
7. Pick wipe dalvik/cache and confirm
8. Select go back untill you get to the first recovery menu
9. Select install zip from SD and NOT "install update.zip"
10. Navigate to your external SD (it should look something like "/extsd" in the file menu
11. Pick the zip you put on the external SD and confirm
12. Wait till the recovery indicates instalation done
13. Navigate back to the first recovery menu and select reboot phone
14. Sit back and relax, your phone will likely take 3-5 min to boot up the first time
If after 10 min of waiting you get no response from your phone, use the 3 button reset to get into the custom recovery and select advanced features again, format absolutely everything you can format (you'll have to do it one at a time) and do that. Then repeat the steps above.
Installing a custom ROM isn't normally this complicated but I am trying to eliminate as many variables as possible here that might cause complications with instalation.
Let me know how it turns out.
FYI: Continuum v4 has the Onix kernel in it (recovery is a blue color)
ROM Files
This is the link to the good JF6 stock ROM. You will have to download it and the ODIN version. All you need is the PDA.tar and the PIT that comes with the ODIN package in the thread. You can still use ODIN 1.8 once you get the PIT file out of the ODIN ZIP.
So, after all is said and done. When you feel like trying this:
1. Open ODIN
2. Phone into download mode (with phone off hold down both volume buttons and plug in USB)
3. Make sure phone is recognised by ODIN
4. Select PIT file that you downloaded
5. Select PDA file that you downloaded
6. Make sure "repartition" IS selected
7. Hit start and sit back and relax
http://forum.xda-developers.com/showthread.php?t=818439
Again, let me know how it all works out.......
Ok, I'll try flashing Cog 4.3 after I get off this afternoon. I'll have to buy an external SD, but that's better than buying a new phone.
I skimmed those threads on the internal SD problem and it looks like there's either some corruption on the SD or it's not formatted correctly or something. How can I fix this problem? Doesn't the ROM need that internal SD card space? Or can it use the external SD card as a replacement? If it does need the internal SD card then won't the ROM fail to install if that SD is corrupted?
Thanks for all your help by the way. When Odin wasn't fixing the problem I was afraid it was completely bricked.

[Guide]How to flash a ROM on a 2.2 Captivate

Introduction
I've put together a video on how to flash a rom. It includes Rooting, Backing up data, Flashing a kernel, Flashing a rom, and troublehooting bad flashes.
Warning
Before you go and flash a ROM for the ultra-fast speeds, kick-butt graphics and awesome sound upgrades... Realize that the risks are real, it is possible for you to black-screen-brick (hard brick) your phone. Here is a real-world example:phone won't turn on. At this point, only JTAG recovery will be effective. I will be posting a video on JTAG soon enough.
You may feel more comfortable stopping after rooting and titanium backup, and not installing a ROM at all, that's OK.
How-To
If you are installing a ROM, then select the ClockWork Mod flashable zip you want and copy it to your phone's internal memory before you watch the video. I did not cover this in the video as there are many options. Team Komin recommends Andromeda3, but you may select any Captivate ROM.
Here is the video which I have prepared on flashing a custom ROM.
Flashing Toolbox
Windows Drivers - select the proper driver for your setup
32 bit: http://www.mediafire.com/?0b45zo7o75rc5d5
64 bit: http://www.mediafire.com/?3dh4d6up72me9re
Files
*SuperOneClickV1.7 - http://files.teamkomin.com/Andromeda/Tools/SuperOneClickv1.7-ShortFuse.zip or http://www.mediafire.com/?kr649t97dd116cd
*Odin3 1.7- http://files.teamkomin.com/Andromeda/Tools/Odin3 v1.7.exe or http://www.mediafire.com/?dy2ix2icags19qr
*Ursa Minor - http://files.teamkomin.com/Andromeda/Tools/UrsaMinor.tar or http://www.mediafire.com/?a1i0boby6em54eo
*Andromeda3 - http://files.teamkomin.com/Andromeda/Andromeda3-Final.zip or http://www.mediafire.com/?vpu22j478j4542a
Recovery Software
*Odin3 one-click 1.0- use only in case of emergency, this can damage your phone -http://www.multiupload.com/XAZUYNXSC1
Tips, Tricks, Good to know
If you have a standard computer setup and you see your phone connected to a port higher then COM6, reboot your phone and your computer before flashing anything.
Phone--!--PC is just a download mode. If the computer does not recognize the phone, reinstall drivers, reboot and pull the battery out, then try again.
Odin is only used for initial and/or recovery modification. After using odin to flash a new kernel sucessfully, you will only need ClockWorkMod (CWM) to flash most kernels and ROMs. CWM is accessed by pressing and holding the 3 button combo.
If your phone displays Phone--!--PC and does not register a COM port on your computer follow the directions below
1. remove the usb cable, battery, sdcard, SIM.
2. wait 10 seconds, then insert the USB cable.
3. press and hold the 3 button combo while you insert the battery
4. continue to hold until phone's screen goes black twice and release power button.
5. timing is critical, it may not work the first time. Keep going until you see the COM port is connected properly.
Disclaimer: All materials presented are for informational purposes. This video is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.
Thanks for the guide adam, I'll be using this tonight. Could you possibly update this with a section on how to go back to a stock kb1 build? That would be great.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
AdamOutler said:
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
Click to expand...
Click to collapse
Thats JF6, not KB1.....
Stock 2.2 you get from the update using kies mini.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dead Links
Hey could you repost the download links because none of them work anymore? Thanks
Sorry, Team Komin's server is down right now, there are other sources on the internet. I will mirror on mediafire as soon as I can
In a boot loop - Moved from Andromeda thread
Hi Adam, Just to get up everyone where we are. I had a flashing issue with Andromeda which resulted in the phone continuously rebooting; i.e. white screen Ursa Minor screen disembodied voice which I now think says missing operation, it definitely doesn't say backup operation, I've listened to it soooooooo many times. . .anyway I put the phone in download mode as you said - BTW this phone with phone off vol+vol then plug in USB and download appears. Holding the power button takes you -when the phone isn't loopiing of course- into recovery mode. I had already restarted the computer, - not a VM - restarted Odin 3 and tried to reflash. Pass! Reset and unfortunately I'm still in that loop can't get to recovery mode.
I removed the battery and USB. Held down all three buttons and with the USB cable connected put the battery back. I held through 2 screen goes black circuits. Second time up the screen shows a gray battery then goes black then I get the ATT screen followed by Ursa Minor and my now less than favorite voice. Doing the same without the USB cable I don;t get the battery but I do get the ATT splash screen between the two black screen and then that darling voice again. So that's where I am. Ideas please
Personally I would One-Click back to Stock. ROOT. Install CWM using Rom Manager. And then install Andromeda via CWM. (I usually skip re-rooting and just install from CWM via the update.zip from ROM Manager) See if that doesn't work... If it does, finish up by installing Ursa Minor #2 (or is it just Ursa Minor now?)
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
^^ It can be tricky to get it into download mode, but there are several ways to do it on all phone. The important thing is that you get a sane COM port like COM8 or less on Odin3 1.7, and that you have download mode activated on the phone. Good to see that everything is working properly.
BWolf56 said:
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Click to expand...
Click to collapse
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
fireboss said:
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
Click to expand...
Click to collapse
OK well I've confirmed that Odin One Click won't restore on this phone unless it is open on the Windows machine when I connect the USB port tot throw the phone into download.
I restored then went through the flashing process again. This time when when it rebooted it didn't loop but it wouldn't go into recovery. I used droid explorer to flip it to recovery mode. Inoted then that there was no adndromeda.zip package on the sd card. I assumed Ursa was supposed to pull that over because in the video it says to find it and install. In any case I drug it from the computer to Droid Explorer and then was able to find it and install the Rom. The unpack looked normal enough the system rebooted. I unplugged USB,gave it the three button fix roputine, and was back in the loop. No matter what I did it looped. The loop was slower this time and the voice clearly said Restore Operation. Not knowing enough to wander farther and unable to get into recovery now because Droid Explorer couldn't see the phone anymore I let Odin restore it. That's where I am now.
Suggestions?
AdamOutler said:
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
Click to expand...
Click to collapse
Thanks! I'll try that out once I get home from work. The only thing I can say is that I wish that would've been up when I got my 1st cappy - would've saved me the trouble of having to Odin3 1 click
Once again, Great work!!
EDIT: This should be Stickied!
fireboss: redownload all links above, it is possible that something went wrong with the download process and a bit is missing somewhere.
-copy the rom of your choice to your SDCard (Team Komin recommends Andromeda3, but any will work)
-put the phone into download mode and flash ursa minor tar file using Odin3 1.7
-let it run though it's operation until it boots normally.
-remove the usb cord, press and hold 3 buttons to reboot into recovery
-select zip from SDCard- Andromeda3.zip
i dont see a link, or file attachment or any mention of 3e recovery in OP
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Might already be in Ursa Minor? (correct me if I'm wrong Adam)
fireboss said:
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after.
Thanks
Click to expand...
Click to collapse
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Right Bwolf
No need to mess with 3e recovery. UrsaMinor.tar overwrites 3e recovery and gives you CWM so you can begin flashing immediately.
mxracer101 said:
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Click to expand...
Click to collapse
That works. The biggest thing is that you are in download mode and you have a sane COM port like COM5 or 6, not COM14. As shown in the video, COM14 lead to Phone--!--PC..
I may do this video again with heimdall. it worked well.
mxracer101, any chance you can generate a pit file? I'd like to make Andromeda3 into a full heimdall flash where you simply put the phone into download mode, select the files, hit start, and let the stock phone boot into Andromeda3.

[Q] Have I ruined my in law's phone? Can anyone help me please?

My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work. After looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on many times, I also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you
I was never a fan of EZ-stuff.
That said, think you can easily solve that flashing your phone with odin and a proper rom. At this point i am unclear about what bootloaders you have on your phone since you've tried a downgrade.
Without getting into further details (sorry, at work atm). You can get tutorials easy for all of this around this forum.
I'd get Odin, get a proper stock rom from samfirmware with bootloaders included and flash it fresh from start with that. Doesn't really matter if it's froyo or ginger as long as it includes bootloaders.
You'll be left with a working phone at this point.
From here, if you still want to try to unlock it, i'd flash a kernell that would get me root (like the ChainFire one) since i find this the safest and easiest way of getting root on your phone and do a backup of your EFS partition (preferably saved in your computer or wherever outside your phone). This is very important, if you lose of mess up with this part of your phone it will be a pain.
Now, there are several ways of unlocking this phone, the only one i found to be most reliable (but not the easiest one) is to manually edit the nv_data.bin file (located in your EFS partition in hexadecimal.
There's a tut right here
http://forum.xda-developers.com/showthread.php?t=761045&highlight=unlock
Thank you so much for taking the time to reply although you are working!!! Really appreciate it.
I'll try your suggestion but I don't know how to choose the right stock rom with bootloader from samfirmware. I went to the website and registered but don't really know what to do.
I know you are working so might not be able to help me, may be someone else?
Here's where I am. Update. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.
Download Jvt From sammobile. com, you need Odin on your PC (1.7 or 1.8) plus Samsung drivers. Read there flashing guides carefully, check you have download
Mode, battery charged > 50% etc
There is also a video on youtube which shows you how to upgrade to jvt.
Sent using TCP/IP
Sounds like you've got the boot-loop problem, which means that you most likely "soft-bricked" the phone. Don't worry, this isn't that big of a deal and can be fixed with relative ease. I agree with the posters above, a clean flash with Odin will probably fix your problem and get you out of the boot-loop.
I'll go into a bit more detail with some steps (feel free to correct me if I missed anything)
1. Download Odin 1.85 here.
2. Head over to Samfirmware.com and grab the latest firmware for the phone. I recommend Gingerbread 2.3.5 (JVT).
3. Make sure your computer has the proper drivers installed so it can communicate with your Samsung Galaxy GT-I9000. If you've flashed the phone before with your computer then you probably have the drivers installed, but here's a link for them just in case: Samsung USB Drivers
4. Enter download mode on your phone, depending on your firmware, it could be Vol down + power + home OR Vol up + power + home. Pull the battery out, pop it back in, and hold those three buttons until the phone turns on.
If you can't enter download mode with the 3-button hold method, then you might have to do so via ADB with the command "reboot download".
Getting into download mode is pretty critical, as you cannot progress further without it.
5. Once you're in download mode (should see a triangle with an Android shoveling stuff in it), plug your phone into your computer's USB port and open Odin. In Odin, press "Reset" on the right hand side. Odin should be able to detect your phone (this is indicated by a yellow box on the left side). I'm using a PC, so inside the yellow box I see something like this: 0:[COM9]. On a Mac it probably says something different, but as long as you see the yellow box appear then it's all good.
If you don't see the yellow box, then there's no communication between your phone and the computer, which means that you may have to reinstall the Samsung USB drivers.
6. With the contents in the firmware package that you downloaded from Samfirmware.com extracted, load them onto Odin accordingly.
PIT: use s1_odin_20100512.pit
PDA: JVT (sometimes the PDA is labeled CODE instead)
PHONE: JVT (sometimes labeled as MODEM instead)
CSC: use HOME-MULTI-OXAJVT (should be about 9.5 MB in size)
Since your father-in-law's phone was originally 2.3.3, you shouldn't have to alter the bootloader with Odin, so leave the bootloader field empty.
7. Once you've loaded up all the necessary files, make sure Re-partition and Auto-reboot is checked. Leave the rest of the checkboxes as it.
8. Press Start. This should initialize the flashing of the new firmware. After the phone has been flashed, it should reboot automatically and should hopefully be able to get past the Galaxy S black and white logo (aka. boot loop).
9. The phone should be in working order now. I used this method to unlock my SGS: SIM Unlock on the SGS. With this method, your phone needs to be rooted, so head on over to ChainFire's thread here to install his kernal which is already rooted.
Flashing firmware can be pretty scary since nobody wants to end up with a brick that costed $400 and it seems like so much can go wrong, but hopefully the steps I've provided helped. Good luck!

[Q] HELP PLEASE Bootloop problem

I was trying to install the Teamhacksung's ICS for Captivate but when i was trying to select the rom, it gave me the status 7 problem. So then i found the Q&A Post about the rom, in which it said that if i had that status 7 problem i should install a kernel that was linked there. So i download it, and as i read on another post, i flashed the kernel the same way I would do with any ROM. The problem came when, once it had finished, I rebooted the phone, and then, the initial screen which says GALAXY S and SAMSUNG below, then a screen that says GALAXY S and below Cyanogen Mod, and finally a quick screen that looks as if the clockwork recovery mod is doing something( impossible to read), and then it takes me to the initial screeen and it repeats over and over. Someone please please help me, I can't get into the recovery mode with the three button mode aswell, Help!!!
Can you get to download mode? If so, you can flash back to a stock rom and try again.
You may also want to check the items in the "Captivate connection issues" thread in my signature.
No, I can't get to download mode, I can't even get into the home screen, I only see the first screens that enter in loop, and that is as far as I get.
EDIT: Yes! At least i made it into the download mode thanks to your post. What's next ?
Look in the development section for the sticky referring to Odin and Heimdall one-clicks. Grab one of those (preferably a bootloader-free version) that has the same setup as you had before you flashed ICS (in other words, flash a Froyo one if you had froyo, Gingerbread if you had gingerbread).
That should put you back in a clean state where you can start again.
(You can also grab the Heimdall UCKH3 one in my signature if you were on Gingerbread - one less search step.)
Thanks for answering. Just a few things. First, the download link of the Heimdall UCKH3 on your signature is broken, but i found on this thread http://forum.xda-developers.com/showthread.php?t=1348392 the onelink.jar file. That's what you meant when you said to grab a 'Heimdall one-click' ? Also, I have entered download mode and it shows the android digging up. But now that i have to open the Heimdall before connecting the phone, should i pull off the battery to exit this screen, open the oneclick and then connect the phone to enter the download mode ?
Thanks for catching that - guess it went down with the whole Megaupload thing.
I would grab this one. It's Odin-based, but should do the same thing, and it's Captivate-specific.
I wouldn't get out of download mode just yet. Unhook your phone from the computer, start the one-click, and reconnect it. With luck, you should be able to flash. If not, then do your battery pull / restart to download and try again.
Thanks for the link. I've downloaded it, unhooked the phone(the download screen didn't changed), started the one click and reconeccted it. A message appeared that said:
ID:0/006 Added!
Then I touched start button, and three more messages showed,
Odin v.3 engine(ID:6), File Analysis, Setup Connection.. and is still there. Have I done it right ? Do you know how much time is estimated to take, or I should have done something else ? I am asking all these questions, because, as you may see, i don't understand most things. Thank you
Thank you so much jmtheiss it worked fine now i'm running the stock version.
Glad to hear it worked for you.
I was wondering if you could help me with a similar problem. My Cappy is operating just fine on a ROM I flashed about 6 months ago, but I am not wanting to flash back to Stock. When I plug my cappy in to the computer (I'm running Ubuntu 11.10), the computer recognizes it and I'm able to transfer files just fine; however when I enter the cappy into Download mode, the computer will not recognize it anymore. Any help is much appreciated.
Are your libusb drivers installed, and are you using heimdall?

Categories

Resources