[Galaxy S I9000 Q&A, Help & Troubleshooting] vindiablo:
Really need your help here guys...

Wanted to flash stock firmware back on to my i9000 on O2 UK, after its overall performance and stability had degraded over recent months. My phone was rooted and was running 2.3.6 on XXJVU I believe.

Downloaded stock firmware via samfirmware.com (can't post as actual link as I haven't posted more than 10 times) from this URL:

www .hotfile. com/dl/155165253/45ea7e1/I9000XWJVH_I9000O2UJV3_O2U.zip.html

The downloaded file I9000XWJVH_I9000O2UJV3_O2U.zip, when extracted, gave me:

SS_DL.dll

jvh_jv3_jv2.tar​

When I extracted this .tar file, the following files appeared:

boot.bin

cache.rfs

factoryfs.rfs

modem.bin

param.lfs

Sbl.bin

zImage​

I'd read that Sbl.bin was the bootloader, and I knew that 'modem' was another name for the PHONE element (a.k.a. 'baseband' I think?), so....

I used Odin3 v1.82 and selected .pit file 803, then selected jvh_jv3_jv2.tar for all four of BOOTLOADER, PDA, PHONE and CSC, and also checked Re-Partition, Auto Reboot and F. Reset Time.

The flash failed, with the following message in Odin:

<ID:0/007> Added!!

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Set PIT file..

<ID:0/007> DO NOT TURN OFF TARGET!!

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> boot.bin

<ID:0/007> cache.rfs

<ID:0/007> factoryfs.rfs

<ID:0/007> modem.bin

<ID:0/007> param.lfs

<ID:0/007> Sbl.bin

<ID:0/007> zImage

<ID:0/007> boot.bin

<ID:0/007> cache.rfs

<ID:0/007> factoryfs.rfs

<ID:0/007> modem.bin

<ID:0/007> param.lfs

<ID:0/007> Sbl.bin

<ID:0/007> zImage

<ID:0/007> boot.bin

<ID:0/007> Transmission Complete..

<ID:0/007> Now Writing.. Please wait about 2 minutes

<ID:0/007> Receive Response form LOKE

<ID:0/007> cache.rfs

<ID:0/007> Transmission Complete..

<ID:0/007> Now Writing.. Please wait about 2 minutes

<ID:0/007> Receive Response form LOKE

<ID:0/007> factoryfs.rfs

<ID:0/007> Transmission Complete..

<ID:0/007> Now Writing.. Please wait about 2 minutes

<ID:0/007>

<ID:0/007> Receive Response form LOKE

<ID:0/007> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)​

So I read around a bit more about the LOKE problem and it getting stuck on factoryfs.rfs, and someone had managed to get around it by flashing the individual elements separately, i.e. first the .pit file, then the BOOTLOADER, then the PDA, etc, followed by updating the phone via Kies.

So I thought I'd give gave that a try. After unplugging and forcing then phone to restart Download mode, first I flashed the .pit file (803), after which the phone just switched off, but Odin said this was a success.

Then for each subseqent stage, again I selected jvh_jv3_jv2.tar each time, only this time flashed BOOTLOADER, PDA, PHONE and CSC separately.

According to Odin, this worked for BOOTLOADER. The Odin message was:

<ID:0/007> Added!!

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> boot.bin

<ID:0/007> cache.rfs

<ID:0/007> factoryfs.rfs

<ID:0/007> modem.bin

<ID:0/007> param.lfs

<ID:0/007> Sbl.bin

<ID:0/007> zImage

<ID:0/007> RQT_CLOSE !!

<ID:0/007> RES OK !!

<ID:0/007> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/007> Removed!!​

However, when the phone then auto-rebooted into Recovery mode, it spewed out this:

E:copy_dbdata_media:Can't mount /dbdata

your storage not prepared yet, please use UI menu for format and reboot actions.

Media files copy failed.

-- Deleting files...

E:failed to mount /dbdata (File exists)

E:delete_data_files:Can't mount /dbdata

your storage not prepared yet, please use UI menu for format and reboot actions.

-- Updating filesystem...

E:failed to mount /dbdata (File exists)

E:discard_filesystem_for_rfs:Can't mount /dbdata

-- Wiping cache...

Formatting /cache...

Cache wipe failed.

-- Applying Multi-CSC...

Installing Multi-CSC

Can't access to '/system/csc/KOR/system/'.

Successfully applied multi-CSC.​

So, reacting to the parts in bold above, I first selected wipe data/factory reset, and got this message:

-- Wiping data...

Formatting /data...

Formatting /dbdata...

E:format_volume: rfs format failed on /dev/block/stl10

Deleting Meta Data

Formatting /cache...

Data wipe complete.​

Is the bold/italic bit crucial?

I then selected wipe cache partition, and got:

-- Wiping cache...

Formatting /cache...

Cache wipe complete.​

I then thought I'd better try a reboot. The phone went through the standard shining Galaxy S logo bootload animation, but then just kept repeating it. I'm presuming this is what others have referred to as their phone being stuck in a bootload loop?!

I then forced it back into Download mode, and flashed jvh_jv3_jv2.tar as the PDA, to which Odin said:

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> boot.bin

<ID:0/007> cache.rfs

<ID:0/007> factoryfs.rfs

<ID:0/007> modem.bin

<ID:0/007> param.lfs

<ID:0/007> Sbl.bin

<ID:0/007> zImage

<ID:0/007> RQT_CLOSE !!

<ID:0/007> RES OK !!

<ID:0/007> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/007> Removed!!​

The phone then auto-rebooted into Recovery mode again, and gave me the exact same series of messages as it did after flashing the new bootloader. So, again, I did a wipe data/factory reset and wipe cache partition (same output messages as before), and then rebooted.

Phone got stuck on boot animation again, so I forced it back into Download mode, and flashed jvh_jv3_jv2.tar as the PHONE.

But I just got a similar error message from Odin as when I tried flashing all 4 elements plus the .pit file together:

<ID:0/007> Added!!

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> boot.bin

<ID:0/007> Transmission Complete..

<ID:0/007> Now Writing.. Please wait about 2 minutes

<ID:0/007> Receive Response form LOKE

<ID:0/007> cache.rfs

<ID:0/007> Transmission Complete..

<ID:0/007> Now Writing.. Please wait about 2 minutes

<ID:0/007> Receive Response form LOKE

<ID:0/007> factoryfs.rfs

<ID:0/007> Transmission Complete..

<ID:0/007> Now Writing.. Please wait about 2 minutes

<ID:0/007>

<ID:0/007> Receive Response form LOKE

<ID:0/007> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)​

It always seems to be when Odin is trying to flash factoryfs.rfs that it fails. I have to unplug my phone when the flash has failed, and when I try to reboot, all I get is an icon with a mobile phone on the left, a PC on the right, and a dotted line running between them with an exclamation mark on an orange triangle in the middle of it. I presume this is supposed to prompt me to reconnect my phone to the PC, but until I can get the stock firmware to flash successfully, there's no point!!

I can still force the phone into Download Mode, but not into Recovery mode.

PLEASE can somebody tell me where I'm going wrong!?!

- is it a dodgy download of the firmware in the first place? If so, can anyone direct me to a reliable one that contains PDA: I9000XWJVH, PHONE: I9000BWJV2, CSC: I9000O2UJV3?

- shouldn't the PDA/PHONE/CSC files be extracted from the download as separate .tar files, and then selected individually in Odin... rather than the same .tar file being selected for each element in Odin?

- do I need to leave the .pit file and BOOTLOADER elements out of it, and just flash the PDA/PHONE/CSC?

Help!! I can't find an alternative download for the stock firmware, every other download link takes me to a page where it says 'This file is either removed due to copyright claim or is deleted by the uploader.'

Any advice/assistance you can give would be a massive help.

Thanks :D