Brick! Brick! Heimdall vs Odin

[youngblack]

ODIN:

okay the last rom I had installed was through a clockwork a DK05, then I flashed the modem.bin (or leaked beta modem bin) with ODIN successfully. Now I wanted to flash back to the original Di18 stock rom using ODIN.. Since using stock and froyoDJ29 I always use ODIN to flash back to stock Di18 Rom with no issues... This time with DK05 Im unable to flash back... in the process it stopped at factoryfs.rfs for at least 10minutes.. I unplugged it.. battery pull.. start over again with odin.. Same thing.. So now I've got a brick realizing that ODIN doesn't play nicely flashing back from DK05.. I wanted to go back to stock. Now I'm...trying to revive the damn phone...

Heimdall:

There's still hope... working with heimdall in my new folder in my desktop and the tar file extention md5..renamed to zip to convert the file and everything within is extracted and included in the new folder. I've got the phone in downloading mode...I verified having all needed files... according to the readme instructions in the same folder as Heimdall:
s1_odin_20100512.pit
factoryfs.rfs
cache.rfs
dbdata.rfs
boot.bin
Sbl.bin
param.lfs
zImage
modem.bin

If you do have all the above files: i.e. You're performing a full flash.

6. Run flash.bat.


7. Done.


EDIT: Nothing happened!!! (Failed... TO DETECT DEVICE)

Oh by the way... when instructed to update the drivers... I get "the best driver software for your device is already installed"... This is what i tried to do after that... delete/uninstall the driver so that when plugged in... it'll show up unidentified.. still get the same results.. I don't see Under Universal Serial Bus Controllers right click on "Heimdall Galaxy S Driver" anywhere...just Samsung usb composite device. That's it. it DID NOT detect any new drivers from the Heimdall drivers folder.

[austin420]

odin returned me back to stock just fine from dk05 modem. i flashed the rom via clockwork and the modem via odin. i ran it all day and went back with odin a few hours ago. i didnt restore to di18 though. i restored to dg27 then re rooted with the newest root exploit that includes cwm. from there i restored my last backup and was up and running.

[youngblack]

Here's the problem... apparently this new Heimdall guy has driver issues that's not supporting a wide variety of Galaxy phones so if you're wanting to make it work by getting the correct drivers for your phone... better post up the driver hardware id here...

[REF] Heimdall - Hardware IDs & Supported Devices - xda-developers

What a shame.

EDIT: WTF... Can you believe this....

http://forum.xda-developers.com/show...3&postcount=43

If we're in download mode why didn't windows detect new drivers for Heimdall?

[gTen]

With Odin, when your flashing back to stock..are yo flashing only the rom or the radio and kernel as well?

[youngblack]

Originally Posted by gTen

With Odin, when your flashing back to stock..are yo flashing only the rom or the radio and kernel as well?

According to this:

[How To] Return to Stock / Fix Bricked Epic - xda-developers

I use 2 files

SPH-D700-DI18-8Gb-REL.tar.md5

and

s1_odin_20100512.pit

to do a complete wipe and restore to stock.

Edit: now instead of using DI18, I'm gonna grab me a dg27 and try to restore it like Austin420 said... to see if it works then I'll report back later. Downloading the file now.

[austin420]

if your file has the extention .md5 then thats not correct. the displayed name should end with REL and the accual file ext should be .tar

[gTen]

Originally Posted by youngblack

According to this:

[How To] Return to Stock / Fix Bricked Epic - xda-developers

I use 2 files

SPH-D700-DI18-8Gb-REL.tar.md5

and

s1_odin_20100512.pit

to do a complete wipe and restore to stock.

Edit: now instead of using DI18, I'm gonna grab me a dg27 and try to restore it like Austin420 said... to see if it works then I'll report back later. Downloading the file now.

And I was jsut abotu to give you the link for it:
http://firon.net/xda/SPH-D700-DG27-8Gb-REL.tar

lol

[youngblack]

Originally Posted by austin420

if your file has the extention .md5 then thats not correct. the displayed name should end with REL and the accual file ext should be .tar

Dude I don't know what you're talking about. Odin can read file ext .md5, if it didn't then how come it has worked for me before...? This time when I started it made it past the boot.bin and stopped halfway at the bar while in the process it stopped at factoryfs.rfs for at least 10minutes..

But I'm gonna take you up on that suggestion.. are you saying I should rename the extension to tar file?

[darren.wlsn1]

Originally Posted by youngblack

Dude I don't know what you're talking about. Odin can read file ext .md5, if it didn't then how come it has worked for me before...? This time when I started it made it past the boot.bin and stopped halfway at the bar while in the process it stopped at factoryfs.rfs for at least 10minutes..

But I'm gonna take you up on that suggestion.. are you saying I should rename the extension to tar file?

you bash him then take his advice plus ask a question? were all here trying to help so maybe be nice or say thankyou.

[austin420]

just stick with the dg27 your downloading. stick it in the pda box on odin.
the name of the file should look like this.

SPH-D700-DG27-8Gb-REL.tar

i dont know if the acual name of the file really matters because when you go to browse for the file to put in the pda box it will only let you select the proper type. i know what an md5 file is and i know mine doesnt have .md5 in the title. left click the file your trying to load as the .tar and look at the properties. is it similar to what i typed above?