Database Develop

[Q] Samsung Galaxy S: Black Screen after Flash

I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english

bump. can anyone help with this topic..
i am having some problem..
help us guys
thanks
Fixed... use odin 512

Thread moved in Galaxy S I9000 General.

I can definately help with this one, as I worked through it last night...
I found that if you're trying to flash the JG5 rom (as mentioned in Modaco's thread) with the 513 Pit file, then you'll get the black screen of despair!! For some reason the two combination of the two don't work.
However, if you do a google search for Odin PIT 512, then download this file
You will be able to download the 512 PIT file instead. Now use this in Odin3 to flash the JG5 rom and you should have no further issues....it worked for me.
I also discovered that Samsung have just released a later firmware, so I just flashed this one on top of the JG5 one...I have a nicely running phone now.
Hope this helps...it did me!
Mike

Mine was completely knackered. Couldn't get to recovery either. Flashed Modaco's MCR R3, after the JG5 flash, using all the files in the JG5 download. Working a treat...
Cheers,
BS...

blacksoul93 said:
I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english
Click to expand...
Click to collapse
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.

ash969 said:
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.
Click to expand...
Click to collapse
Same here.
I tried JS3 and going back to JP6....and always the same result.
I'm obviously missing something. Maybe my 512.PIT is corrupted. I get the black screen and the same /dev/block.st110 errors in recovery.

i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe

thanks for your find !
Rumble6059 said:
i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe
Click to expand...
Click to collapse
thanks mate ! after a huge scare sorted mine with this firmware as well, this after I tried several other newer firmware packages from samfirmware and was ,slowly but surely ,starting to lose hope ...
for some reason this particular firmware JP2 seems to fix this problem
cheers and thanks again for your find !

fix for black screen after flash with no recover or download mode working.
Hey All.
So like the subject says, you flash and then your phone restarts or whatever, and then you get the normal galaxy s startup, with the sound and the visuals, but then that's it. Henceforth you are greeted with the two lights (if its a Bell Vibrant) from your options and back keys.
To fix it use the attached file. Its called ADB or something - I just know it works. It was a fix for the galaxy s phones that didnt have the recovery/download mode stock.
so here is how it goes:
1. download adb to your desktop and unpack it (if its in winrar or zip or whatever) to a file folder named adb.
2. open a command prompt.
3. type "cd" and then the address of the "adb" folder. so for example it should be in C:\Users\your user name\Desktop\adb. where "your user name" is your user name a duh.
4. plug in your galaxy s via usb.
5. type "adb reboot download" in the command prompt. copy it using your mouse as well.
6. turn on your phone.
7. press enter in the command prompt, then keep copying and pasting and pressing enter until you see the download screen on your phone. each time you press enter it says device not connected or something but just keep trying.
the article i read:
can't post it but the thread is called "How to get the 3 button recovery mode working"
Credit to Goots from samsung galaxy s forums. Go Goots!

[Q] Odin and JPO

Hello everyone,
My current firmware version is:
PDA: I9000XWJM6
Phone: I9000XXJM3
CSC: I9000OXXJM1
It was the version that i updated after i bought the phone to unbrand it. Since i have no possible way of using Kies to update (belive me i sucked every thread about it and no way i am getting the MTP USB Device driver on win7x64) i used odin to update and all went well.
Now i am courious about the Froyo JPO firmware and decided to give it a try since it's finally announced from samsung, the thing is that using ODIN v1.3 with the s1_odin_20100803.pit file and following the BIG GALAXY S FAQ (forum.xda-developers.com/showthread.php?t=723596) it says and i quote
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
In step 2 when i first upgraded to my current firmware i had the PDA, Modem and CSC files now with the JPO downloaded from sam-firmware i have the current files:
cache.rfs
factory.rfs
modem.bin
params.lfs
zImage
Of those files only the modem.bin appears on the odin files section all the other files i can't choose them (PDA and CSC) have i downloaded the wrong firmare or something? what should i put in PDA and CSC files?

DsMobile said:
Hello everyone,
My current firmware version is:
PDA: I9000XWJM6
Phone: I9000XXJM3
CSC: I9000OXXJM1
It was the version that i updated after i bought the phone to unbrand it. Since i have no possible way of using Kies to update (belive me i sucked every thread about it and no way i am getting the MTP USB Device driver on win7x64) i used odin to update and all went well.
Now i am courious about the Froyo JPO firmware and decided to give it a try since it's finally announced from samsung, the thing is that using ODIN v1.3 with the s1_odin_20100803.pit file and following the BIG GALAXY S FAQ (forum.xda-developers.com/showthread.php?t=723596) it says and i quote
In step 2 when i first upgraded to my current firmware i had the PDA, Modem and CSC files now with the JPO downloaded from sam-firmware i have the current files:
cache.rfs
factory.rfs
modem.bin
params.lfs
zImage
Of those files only the modem.bin appears on the odin files section all the other files i can't choose them (PDA and CSC) have i downloaded the wrong firmare or something? what should i put in PDA and CSC files?
Click to expand...
Click to collapse
You don't unzip the tar file. instead you keep the tar file as a single file, apply it as "PDA", leave the other 2, phone and CSC blank then start flashing.

I came across this question yesterday. I downloaded JPA and it's a single tar file. I apply it as PDA and choose 512 pit file, after flash I found the firmware has been updated to JPA/JPP.

Thanks i did put the tar file in pda and all was going well odin said:
<OSM> All threads completed. (succeed 1 / failed 1)
<ID:0/015> Removed!!
the phone booted while the usb driver was connected and went straight to "home+ power+volup" screen saying
"E: can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:can't mount DBDATA:
your storage not ready yet, please use UI me nu for format and reboot actions.
copy default media content failed"
:S:S:S:S:S
I tried formating SD and said the same without getting out of that screen. Then i pressed wipe/factory reset, it reseted to factory and rebooted, then after the S logo went black and it's vibrating from time to time like "medium vibe, short vibe short vibe shortvibe" what do i do ? :S
Edited:

DsMobile said:
Thanks i did put the tar file in pda and all was going well odin said:
<OSM> All threads completed. (succeed 1 / failed 1)
<ID:0/015> Removed!!
the phone booted while the usb driver was connected and went straight to "home+ power+volup" screen saying it could not write to "something block" :S i tried formating SD and said the same without getting out of that screen. Then i pressed wipe/factory reset, it reseted to factory and rebooted, then after the S logo went black and it's vibrating from time to time like "medium vibe, short vibe short vibe shortvibe" what do i do ? :S
Edited: I still have the usb cable connected
Click to expand...
Click to collapse
I think after the flash completes you unplug the cable, do a factory reset, then wait for it to get into system. I read a post saying that it could take longer than 5 minutes to get into system for the first boot. Or if you like, you can try the JPA firmware I flashed. I guarantee it works 100%. Also someone said JPA is a bit better than JPO.
download link: http://www.megaupload.com/?d=SGI5ULX2

The thing is that it gived me that error after first boot :S
Updated on thread above
"E: can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:can't mount DBDATA:
your storage not ready yet, please use UI me nu for format and reboot actions.
copy default media content failed"

DsMobile said:
The thing is that it gived me that error after first boot :S
Updated on thread above
"E: can't mount /dev/block/stl10
(Invalid Argument)
E:copy_dbdata_media:can't mount DBDATA:
your storage not ready yet, please use UI me nu for format and reboot actions.
copy default media content failed"
Click to expand...
Click to collapse
Did you uninstall lag fix before update? this could be a problem.
remember to undo lag fix and flash again.
try the JPA rom I posted above.

Yes i did undo to the lag fix although i didn't erase the app was that the problem?? if so what do i do now?

Tell me something ehe12 you installed did you installed JPA using 512.PIT file? in sam-firmware it says it's 803.pit file.
Another thing, in this thread forum.xda-developers.com/showthread.php?t=828504 it says JPO it's for european countries and JPA is for Finland, i am from PT.

DsMobile said:
Tell me something ehe12 you installed did you installed JPA using 512.PIT file? in sam-firmware it says it's 803.pit file.
Another thing, in this thread forum.xda-developers.com/showthread.php?t=828504 it says JPO it's for european countries and JPA is for Finland, i am from PT.
Click to expand...
Click to collapse
I use 512 to flash JPA, no problem. I just did it again and this can be confirmed.
JPA and JPO are both new, I don't know much about their difference. I will flash JPO later to see if it's really different.

Ok this was completely my bad for not RTFM all the way in sam-firmwares it says
$ I9000XWJPO
Flashing way I9000XWJPO: First I9000XWJM8 with RE-Partition and 512.pit. Than I9000XWJPO without RE-Partion use 803.pit.
Click to expand...
Click to collapse
I did that and all went fine wufffffffffffffffffffff what a ride, i am still trembling :S
Many thanks for your help, i will now enjoy Froyo

DsMobile said:
Yes i did undo to the lag fix although i didn't erase the app was that the problem?? if so what do i do now?
Click to expand...
Click to collapse
Did you tick "repartition" at flashing?

When flashing JPM8 yes, when flashing JPO no.
But the first time with JPO yes re-partition was checked

DsMobile said:
When flashing JPM8 yes, when flashing JPO no.
But the first time with JPO yes re-partition was checked
Click to expand...
Click to collapse
ok can you flash to any 2.1 rom? if so you might want to flash back to 2.1, then flash 2.2 again.

DsMobile said:
When flashing JPM8 yes, when flashing JPO no.
But the first time with JPO yes re-partition was checked
Click to expand...
Click to collapse
Hi, I just flashed JPO to my phone, no problem at all.
FYI, I didn't flash the way they taught online,"flash to JPM then flash JPO". I straight forward from JF3 to JPO. also I didn't use 803, I use 512 as pit file. no Re-partition, only tick "auto reboot" and "reset time". durling flash, Kies must be closed, other it will keep connecting the phone and Odin won't be able to start flash.

Damn, My phone wont install stock rom!

Hi,
I was on darkys rom, I installed honeycomb theme on it.. which had some issues and my phone was in constant reboot loop after that. I couldnt go to recovery or anything. only the download mode was working.
So I flashed DDJP6 it gave me following error its giving me same error even if I flash using DDJPY or any other stock rom.
after I flash my rom this is what i get on 1st boot when it goes to recovery, please help.
============
Update media. please wait E:Cant mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:cant mount db data:
your storage is not prepaired yet. please use UI menu for format and reboot actions.
copy default media content failed.

Flash a 2.1 version with repartition on! (maybe 2 times if first time don't work)
Then flash a 2.2 or 2.2.1 version without repartition on...
PS: Everytime before flashing with odin put off the battery once first!
Good luck!
Sent from my GT-I9000 using XDA App

Did u have lagfix on with darkys rom when u flashed with stock rom?
Sent from my GT-I9000 using XDA App

Now do a wipe and if problem still not fixd flash a full rom with 3 file and pit

Hannibal226 said:
Flash a 2.1 version with repartition on! (maybe 2 times if first time don't work)
Then flash a 2.2 or 2.2.1 version without repartition on...
PS: Everytime before flashing with odin put off the battery once first!
Good luck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think the point is not 2.2/ 2.2.1 .. The OP needs an odin flash with separated csc, modem and pda files plus a corresponding pit file plus repartition ticked.
I believe that this error happens after a odin flash with repartition ticked AND there s only 1 pda file (without the modem and csc things).
(is there a way to post in the android development without having to post > 10times @ other subforums ...? -_-)

m2677086 said:
I think the point is not 2.2/ 2.2.1 .. The OP needs an odin flash with separated csc, modem and pda files plus a corresponding pit file plus repartition ticked.
I believe that this error happens after a odin flash with repartition ticked AND there s only 1 pda file (without the modem and csc things).
(is there a way to post in the android development without having to post > 10times @ other subforums ...? -_-)
Click to expand...
Click to collapse
I don't understand your prob because the 2.1 versions i think "all" are 3 sepereated files, so that what I said!
Sent from my GT-I9000 using XDA App

I don't understand your prob because the 2.1 versions i think "all" are 3 sepereated files, so that what I said
Not true .
jje

[Q] I9000 soft bricked

I need some help... Please!
I have a I9000T galaxy S phone and I soft bricked it. This is the story:
I flashed my phone using Odin with ROM JPY_JPY_JPY (downloaded form samfirmware, only file: PDA), and then flashed supermod-kernel-k13d-500hz...then I uploaded Modem UGJL2 for Froyo as an update.zip file (to get band 850 mhz for my country) and applied successfully!
My phone worked as a charm. No bricking.
Then I realized that there was a newer ROM: I9000XWJS5 with the XEN thing.
Since the ROM has the 3 files (MODEM, CSC, and PDA) and I read that it needed a different PIT, I flashed with the re-partition checkbox checked and with the 803 pit file.
It didn't get through. It got stuck at flashing sbl.bin
I had to unplug it after several minutes and I realized that it was soft bricked. It didn't work but download.
I tried to go back to JPY. After many tries and errors (changing PIT to 512 and repartitioning), finally I could flash back to JPY ROM. At the end of the process it reboots and the system get into Android system recovery <3e>. I can read at the bottom the following signs:
E: Can't mount /dev/block/stl10 (invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
If I reboot the system, it boots and I see the splash "S" moving theme, and it seems that it is booting but then it stops and it starts vibrating from time to time... then the screen goes black and nothing happens (but vibrating from time to time). It never appeared the "login screen"
Reading here and there, some advised to flash first the speedmod-kernel with the PIT 512 file and re-partitioning. I did so, and then, after boot I was able to get into Clockworkmod recovery screen. The menu is green and the version is 2.5.1.0
Someone suggested to flash to JPU ROM (that way it fixed a similar problem) but when I did so, it takes me to the beginning (the process hung at sbl.bin)...
I've been flashing and reflashing with different options these 3 ROMs (JPU, JPY, JS5) the only one that completes the flashing successfully is JPY, and eventhough it tries to boot, it fails to present the logon screen (dots for password)... JPU and JS5 hang at sbl.bin and after that, no boot... freeze. I have to flash back to JPY.
I have read tons of forums, I have learned a lot, but I believe I need deeper advices.
Thanks in advance!

Some further information. JPU, JPY, JS5 are ROMs that were downloaded from samfirmware.com... I guess that is what you mean when you advice to flash any stock ROM. Am I right?

Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!

droilfade said:
Guessing you have a I9000m. If yes, Flash JPC with 512 PIT and repartition ticked. You will still be in a boot loop. Take out battery and then load JL2 into PDA of ODIN and flash. You could try it even if you do not have an i9000m but at your own risk! Advice is free, phone isn't!
Click to expand...
Click to collapse
No... I don't have a I9000m, I do have a I9000T
When I flashed the JPY it turned a I9000, but I applied the Modem UGJL2 which adds the 850mhz band (which is the only difference between the I9000T and I9000.
Someone suggested going to JM8 (Eclair 2.1), but I have read that in some cases it produces hardbrick... what do you think?

Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.

froysm said:
Oh, been there! I can give you some advice... First, i will recommend heimdall for flashing, it allows a little bit more of control with the files you want to flash. Then, i had this problem with the dbdata... i think it's becacause of the repartition thing, honestly i'm not sure but do not worry, if you can enter download mode it's recoverable.
So, let's try something. Download heimdall, install it, install your drivers and then download the rom in this post (it's and old build of Darky's Rom), the thing here is that you <<have>> to flash this with the command line client, so you can specify the order of the files to flash leaving at the very end the Sbl.bin and modem.bin (Both files can't be flashed neither with heimdall nor Odin in my Galaxy i9000T). Obviulsy the heimdall flash will fail with the Sbl.bin file, so you just pull out your battery and power up your phone. That should do it... it have failed a couple of time for me, so if it fails for you (It gives you a boot loop) tell me so i can share my other method. If this works you should be able to enter CWM and flash a custom ROM or be able to flash another stock rom but be careful, do not flash bootloaders, modems or do a repartition (That's why i prefer Heimdall over Odin).
I hope you could have your phone back.
Click to expand...
Click to collapse
Thank you froysm... What I see in your post is that we are going to try to flash a Darky's ROM in order to have CWM so we can flash a custom rom?
If that is so... I already have CWM... It is version 2.5.1.0 with its menu in green.
What is custom rom? are they the roms from samfirmware? I tried JPU and JS5 and they hang at slb.bin... the only one that flashes successfully is JPY, and eventhough it "runs", somehow it is not working.

In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?

Well, if you have CWM try one of the roms of the world famous romkitchen Cook a rom, download it, enter recovery mode, go to mounts & storage (and connect your phone to the computer) and select mount USB storage, put the donwloaded zip file in your phone. Then unmount, go bak to the main CWM menu, select install zip from sdcard, the choose zip from sdcard, find your rom and flash it! However... as far as i can remember i could never mount my phone with CWM 2.x so may need to flash Darky's Rom just to be able to mount your phone, put the zip file there and then reflash with the new ROM viw CWM...

jdelagarza said:
In regard heimdall... Do I have to have ubuntu in order to install it? Is there a heimdall for windows?
Click to expand...
Click to collapse
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.

froysm said:
Yes, heimdall is available for Windows here It's pretty straight forward, just put your phone in Download mode, select the files you want to flash and hit start.
Click to expand...
Click to collapse
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?

jdelagarza said:
Thank you... believe it or not you poured some light into my darkness.
I have 3 issues and I hope you can clarify...
How would you order flash methods, in order of importance? Odin, CMW, heimdall? Which one is better, which one is worse?
I'm able to flash speedmod-kernel-k13d-500hz... that is what brings me the CMW v2.5.1.0.... should I try to install a newer version of CMW? or should I stick with heimdall option?
Flashing ROMs such as Darky's rom can be potentially harmfull? I mean, can my phone end with a hardbrick?
Click to expand...
Click to collapse
Don't worry, that is exactly why we are here to learn from other people experience and share what we have learned.
About your issues,
I only have access to my Linux machine and heimdall says this when i ask for help (with the command
Code:
heimdall help
Usage: heimdall <action> <arguments> [--verbose] [--delay <ms>]
action: flash
arguments:
--repartition --pit <filename> --factoryfs <filename>
--cache <filename> --dbdata <filename> --primary-boot <filename>
--secondary-boot <filename> --param <filename> --kernel <filename>
--modem <filename>
So, what you have to do is navigate to the location of your files and write something like this
Code:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --dbdata dbdata.rfs --cache cache.rfs --param param.lfs --kernel zImage --primary-boot boot.bin --secondary-boot Sbl.bin --modem modem.bin
See how i reordered the files to flash leaving at the very end Sbl.bin and modem.bin?
As i told you before this will fail because of the last files, but it will allow to flash everything else. Remove your battery, put it again and try to boot your phone.
I forgot to tell you something really important!! Since the flash in going to fail it will give you the <<scary>> "Connect phone to PC" screen, but don't worry, heimdall can take care of that. Again, asking heimdall for help in the command line says something like this:
action: close-pc-screen
description: Attempts to get rid off the "connect phone to PC" screen.
And that is exactly the next step to take, write down in your command line (with the pone connected to the pc and in download mode)
Code:
heimdall close-pc-screen
And that's it, wait for the phone to boot.
This method is the one i advise when you just can enter Download Mode or when you really need to repartition.
Better? Worse? Nah, they are just really different approaches, Odin is the Samsung standard, Heimdall came to the game because it's OS X and Linux compatibility and CWM allows you to control your phone, custom kernel settings, flash updates packages with modems, boot animations , even whole roms without the need of a cable to connect your phone to a PC and other really cool stuff. Generally, since i've been in custom roms (like darky's, romkitchen, ultimate, etc) since i got this phone, i only use CWM, and when i have a big problem or i need a stock rom i use Heimdall (because i'm on Linux).
The CWM version is just fine, not all the roms are compatible with CWM 3 at the moment, so just make sure you can mount your phone in your pc with CWM. Try first the CWM option, if you can't mount it or it just don't works try the heimdall option.
The last question, I'm not saying it's 100% safe because it is not, but not only custom roms, this also can happen flashing a rom with Odin or Heimdall. Honestly i haven't heard of someone who bricked a phone in the whole thread of the romkitchen or darky's rom. I mean, it could happen, even with a perfectly stable stock rom. but it's not so common, at most, the worst thing you will encounter in your custom rom experience is a lot of Force Closes in applications (if you mix data and apps from incompatible versions) maybe a couple of boot loops, but nothing to be really scared about, just make sure you can enter Download Mode and everything will be fine.
Phew! The longest post if ever written in any forum. I hope i made everything clear, if you happen to have any other question i'll be happy to answer it (But it will have to wait for tomorrow... you know, it's midnight).

Thanks...
I'm downloading darky_heimdall.zip. As soon as it is downloaded, I will try it.
Just for your information, with CMW I tried to mount the USB and it worked!
So, now I am at a dilemma... Should I flash darky with CMW or heimdall?
Oh, if you wanted to know how I managed to install a WORKING STOCK ROM with froyo... here is the tutorial that I followed:
http://neosystm.com/2010/12/actuali...000t-a-froyo-2-2-1-xxjpy-de-forma-no-oficial/
It worked as a charm... I had Froyo 2.2.1 with JPY ROM.
The problem began when I tried to update it to JS5 ROM.
Cheers!

I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...

OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers

Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?

Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?

jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?

Hey, sorry i didn't answer sooner, let's see...
jdelagarza said:
I just finished downloading darky's rom...
I noticed that it has 3 .bin files: boot.bin, modem.ini and slb.bin
I was curious about the content of my previous working ROM (JPY) and the not working ROMs (JPU and JS5).
I found that JPY has only the modem.bin file.
and JPU & JS5 have boot.bin and slb.bin (but no modem.bin).
Question: Since you advised to install darky's rom and but the sbl.bin file at the end, so my phone can get flashed with everything but slb.bin, can I do the same with the JS5 ROM?
I look forward to your response...
Click to expand...
Click to collapse
Yes, you can.
jdelagarza said:
OK... I tried to flash darky's rom with CMW... it said:
"Installing: SDCARD: darky_heimdall.zip
Finding update package...
Opening update package...
Installing update..."
And it hung... I guess this was expected due the slb.bin...
I'm gonna try the heimdall method.
So, what do you think? Should I try it with JS5 or with darky's rom?
Cheers
Click to expand...
Click to collapse
That specific version of Darky's rom is intended only for heimdall, so it will obviously fail. You'll see, some files can just be flashed via CWM and some can just be flashed with Odin and Heimdall, be careful and read with which tool can be flashed.
jdelagarza said:
Ok... I flashed with heimdall.
This is the result:
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading PIT file
PIT file upload successful
Uploading factory filesytem
100%
Factory filesytem upload successful
Uploading cache
100%
Cache upload successful
Uploading data database
100%
Data database upload successful
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading secondary bootloader
100%
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
The last two sentences appeared when I unplugged the phone after a 10-minute wait.
I removed the battery, and put it back again. Turned my phone on, and I've got the picture of the cell phone - computer hazard. I'm able to enter download.
What's next?
Click to expand...
Click to collapse
As I told you on my last post, heimdall can take care of that. Just put your phone in Download Mode and write heimdall close-pc-screen. That should solve your problem.
jdelagarza said:
Froysm, do you know what's the original ROM that telcel uses to ship our Galaxy' S?
Click to expand...
Click to collapse
Nope, i've never found it (actually i've never needed it).
jdelagarza said:
I've found a thread that says that they fixed it going back to JM8 ROM, and then moving back to Froyo 2.2.
Does anyone know any potential damage of such flashing?
I read this post http://forum.xda-developers.com/showthread.php?t=780867
And it seems that downgrading can lead to corruption and hard bricking.
Does anyone know?
Click to expand...
Click to collapse
Try my methods first, I've tested them a lot and never had a real problem. If you want to try this, go ahead. As i told you before it's very rare to hear a phone really bricked, most of the times it's recoverable.

Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?

jdelagarza said:
Oh, I forgot the heimdall close-pc-screen.
Ok... I tried it twice.
The first time my command prompt was busy trying to upload sbl.bin, so I opened another command prompt and I threw the command. The result: "Failed to access device. Error: -3"
The second time I waited until the flashing ended with error, and then I threw the command (within the same command prompt). The result: "Failed to retrieve config descriptor"
Hmmm... what was the other method that you mentioned in your first post?
In the other hand, can you read the following post, and could you go through all the comments after the post. Pay special attention to Jedi and GSCATIL...
http://foro.neosystm.com/f19/androi...00xxjvk-%96-beta-para-el-samsung-galaxy-s-69/
Jedi describes my exact problem (about the phone vibrating), and GSCASTIL is from Puebla, so he is with Telcel as well...
My problem didn't happen updating to gingerbread... It happened updating to JS5 (Froyo).
Hope this helps... what do you think?
Click to expand...
Click to collapse
Always, after any task completed successfully or unsuccessfully either with Heimdall or Odin, unplug your phone, reboot it, put it again in download mode and connect it. So do that again, flash, wait for the fail, unplug, reboot, download mode again, connect again and try to remove the error screen with heimdall.
I will read that post and see what i can find (I can't read it right now, sorry).

[Q] Stuck after flashing Semaphore_2.7.4.tar as preparation for CM10

Hello!
I have SGS I900 which has GB 2.3.4.
I was following instructions as per http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Which for some stupid reason neglected to mention I should enable USB Debugging before the process!
Anyway, after flashing this kernel using heimdall 1.3.1 on Ubuntu, I found out I cant do adb push to place the zip file on the phone.
I tried to mount the SDCARD throguh usb using CW recovery - it worked, but I tried twice, each time transfer speed drops at the last 20mb (out of 158 mb), but eventually after like 10 minutes it finished copying.
However in both attempts, it failes to open the zip file when I try to install.
I am also unable to boot the phone as its in endless loop on the logo.
What do you suggest I do now to get it running properly?
Thanks!

Can you get into download mode?
If you can, flash in a stock rom. Root it using CF-Root.
Sent from my GT-I9000 using xda premium

Soryuu said:
Can you get into download mode?
If you can, flash in a stock rom. Root it using CF-Root.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yes I can, but how to flash a stock rom, if I cant properly transfer the update.zip file?
I would also appreciate a link to stock kernel, because I havent been able to find one.. since I dont now what to flash now.

Carmageddon1984 said:
Yes I can, but how to flash a stock rom, if I cant properly transfer the update.zip file?
I would also appreciate a link to stock kernel, because I havent been able to find one.. since I dont now what to flash now.
Click to expand...
Click to collapse
Go onto sammobile.com and under the Firmware section download a stock 2.3.6 rom.
Then download Odin (its not that hard to get online), any version should do.
Unzip the rom you downloaded. Leave the files as they are (you should get two files, a .tar file and a dl or something like that. We only want the .tar file).
Note that for this you don't need to put anything on the SD. You just need to have things on your computer.
Open Odin. Put the phone into Download mode by using the 3 button method (Vol. Down + home + power button). Once you get the "Downloading!" logo, onnect the phone to the computer (with Odin open) via USB. One of the boxes in Odin should light yp saying ID:COM: with a number next to it. That means Odin's read the device.
Select PDA, click on the .tar file you unzipped from the download. DON'T touch anything else.
Select Start and it should flash in.
That should fix your problem hopefully
Sent from my GT-P7510 using Tapatalk HD

Soryuu said:
Go onto sammobile.com and under the Firmware section download a stock 2.3.6 rom.
Then download Odin (its not that hard to get online), any version should do.
Unzip the rom you downloaded. Leave the files as they are (you should get two files, a .tar file and a dl or something like that. We only want the .tar file).
Note that for this you don't need to put anything on the SD. You just need to have things on your computer.
Open Odin. Put the phone into Download mode by using the 3 button method (Vol. Down + home + power button). Once you get the "Downloading!" logo, onnect the phone to the computer (with Odin open) via USB. One of the boxes in Odin should light yp saying ID:COM: with a number next to it. That means Odin's read the device.
Select PDA, click on the .tar file you unzipped from the download. DON'T touch anything else.
Select Start and it should flash in.
That should fix your problem hopefully
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
Thank you!
After much trouble since heimdall complains about something like "firmware.xml is missing from the package." , tried those steps:
First, on my Ubuntu desktop:
Code:
heimdall flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --modem modem.bin --param param.lfs --kernel zImage --no-reboot
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
26%
ERROR: Failed to send file part packet!
FACTORYFS upload failed!
Ending session...
ERROR: Failed to send end session packet!
Re-attaching kernel driver...
Then after further troubles on setting up the Samsung driver on my Windows 8 laptops ( it worked only on one of them!), I get Cpomplete(Write) operation failed line, after param.lfs line.
Any help would be hot :good:

Another updatE:
after a second try on the working laptop, Odin flashed it!! waiting for the device to boot now, hopefully after this, I can get back to flashing the target rom
Thanks!