yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] skillz398:
hey i got hard bricked and followed the directions correctly(i think) i followed the command correctly and received a error message "Failed to detect compatible device" and also my PC does recognize it as a usb because it alerts me that a malfunctioning device is connected :confused: im in desperate need of help cause i dont have a back up phone :(
[Samsung Galaxy S (4G Model)] RaverX3X:
try in linux as that was the test system i did it on... I have not tried it in windows well if your pc detects it at least download some linux and try there u can also try front end
[Samsung Galaxy S (4G Model)] skillz398:
thanks for the help im currently downloading linux rught now but whats front end ? i googled it but came up with nothing and on a side note i forgot to mention that my screen is just blank and stays that way i cant even put it in download mode and when i went to the usb device list to try to install the drivers my phone was listed as unknown and couldnt be updated, am i in a deep hole right now ? cause i feel like i am :mad:

nvm MY PHONE IS ALIVE!
[Samsung Galaxy S (4G Model)] jzun223:
Will this work on the vibrant because I have a hard brick one that the screen doesn't even turn on at all?

I don't have linux installed though
[Samsung Galaxy S (4G Model)] RaverX3X:
well that means it worked = phone not working before even if it says it cant detect in windows theres the chance it stil flashes cause the program will still send the files even if the pc says otherwhise hince why its very causious when u flash with this eg if You flash the wrong zimag etc and then causes your phone to soft brick cause it does flash :P

well glad it worked for you
[Samsung Galaxy S (4G Model)] RaverX3X:
try it... worst thing that can happen it doesnt work
[Samsung Galaxy S (4G Model)] leemobaii:
Di you ever make that jig?
[Samsung Galaxy S (4G Model)] RaverX3X:
Yep

Sure did
[Samsung Galaxy S (4G Model)] wizardslovak:
Best guide ever.....works like charm....if it doesn't work for someone make sure u install drivers from heimdall not from odin.....cd to heimdall folder...works ...I brick myne every time I am updating to other gb
[Samsung Galaxy S (4G Model)] itsallen:
thank you for posting this guide, you saved my phone :D
[Samsung Galaxy S (4G Model)] AdamOutler:
this thread is a waste of space and dangerous.

Let me count the problems:

1. If you're flashing with heimdall, then your bootloaders are fine. You have problems with other partitions.

2. Being that you have download mode accessible, you would need to flash a kernel or modem, not a bootloader. It's safer

3. to clear the Phone--!--PC screen the user needs no firmware. Simply

heimdall close-pc-screen

4. No firmware is provided. This leaves it up to the user. Without firmware provided, they will likely find the wrong ting searching for bootloaders.. maybe a motorola one?

5. There is no links, no pictures, no complete explanation, and no credits given.

6. This does not belong in the development section. NONE OF THIS IS HIS ORIGINAL WORK. It's user operations of heimdall, and it's only partial. Put this in General.

7. I'm reporting this thread. It needs to be moved and users need to be warned before following this advice.
[Samsung Galaxy S (4G Model)] RaverX3X:
you have no clue what were even using this for? If you would have read the gasp title. were not talking a bout soft debricking where u can still recover though software when someone GASP FLASHES THE WRONG BOOTLOADERS TO THE DEVICE . IF YOU THINK I AM TALKING BOUT SOFT BRICKING HERE let me get you another devices bootloaders to flash to your phone .... before you report a thread and post something thats purly senceless figure out and GASP READ..
[Samsung Galaxy S (4G Model)] dsexton702:
seriously adam why did you post this? people posting above you clearly have used this method and it works, you probably dont even know the situation with the sgs4g at all so why chime in?
[Samsung Galaxy S (4G Model)] AdamOutler:
If you can use heimdall, you can use Odin, and you are soft bricked.

Heimdall does not have provisions for hard bricked devices nor damaged partition tables. I know this because I have been working with it extensively for months. Scan my avitar barcode and click on heimdall one-click... or go to oneclick.adamoutler.com

Best case scenerio, this is horrible advice. Worst case, you will ACTUALLY hard brick peoples phones.
[Samsung Galaxy S (4G Model)] RaverX3X:
once again you have no idea what this thread is even about. NORE THE TESTING THAT WAS DONE TO RECOVER IT. AND NO ODIN WOULD NOT HAVE HELPED HERE. I HARD BRICKED A PHONE 4 TIMES TO TEST THIS AND RECOVERED IT EVERY TIME. AND YES I KNOW WHAT A HARD BRICK IS I HOPE A MOD DOES COME TO THIS THREAD TO IF ANYTHING PLEASE REMOVE YOUR WASTEFULL AND MEANINGLESS POSTS..

question for you since u seem to like to hyjack posts for no apprent reason?

how can you even call yourself a developer when you dont even understand the diffrence between hard and soft bricks?
[Samsung Galaxy S (4G Model)] AdamOutler:
Heimdall utilizes well documented Odin Protocols. That's it. It can do no more then odin does.

If you have a valid set of bootloaders on your device, then you have download mode. You are not hard bricked. You are soft bricked. You likely have flashed something which has destroyed your param.lfs and replaced Phone--!--PC with a black screen.

Believe me. You cannot flash using Odin protocol with a hard brick.

here, next time try this: http://xdaforums.com/showthread.php?t=1153310

The boot sequence relies on SBL ( the final bootloader) to use the Odin Protocol which is used by Heimdall. If you are able to use heimdall, then you have loaded IROM>IBL>PBL>SBL. That is the entire bootloader set.
[Samsung Galaxy S (4G Model)] RaverX3X:
ya i know i read your thread 1 click debrick...

YOU just mad ur not going to get your 30 dollers for jtag services bra? oh while were at it mabe we should report your one click thread as it gives the instructions how to clear the water damage tabs for insurance replacement? can we say phone insurance fraud?

and it does work genious.. I FLASHED THE VIBRANT PHONES BOOTLOADERS OVER THE SGS4G'S WHICH CAUSES GASP A HARD BRICK AND WAS ABLE TO RECOVER. WHAT PART OF THAT ARE YOU NOT COMPREHENDING. (i also own a riff box so testing this before posting this posed no great risk to me at all..) I WOULDNT HAVE POSTED IT IF IT WOULD HAVE NOT WORKED AND RISKED MORE DAMAGE TO THE SGS4G DEVICE..

i guess you should tell the people that had TRUE HARDBRICKS AND RECOVERED THAT THIS DIDNT WORK.... i think there running phones and them may just laugh at you..
[Samsung Galaxy S (4G Model)] AdamOutler:
Quite the contrary... I'm looking out for the end user. I always have. You sound like you had good intentions... but its not executed properly. There's nothing wrong with the bootloaders if you can use heimdall. Trust me.

I'm working on a way to ACTUALLY cure hard bricks now. It takes one wire for any hummingbird processor. Check out "How to unbrick the unbrickable captivate"

Tell you what... ill replace every post in this thread with "insert your phrase here" and make a $20 donation to you if your method works under one of the following conditions which will cause an actual hard brick.... where you need to download bootloaders

Note: Please do not try this on a production device.

1 delete sbl by using UART on SBL prompt.

erasepart 0
erasepart 1
erasepart 3
erasepart 4
erasepart 5
savepart

Have an efs backup first.

Or

2. Make a text file the same length as the sbl and pbl and flash it instead of the sbl and PBL.

This must be entirely captured on video.

Either way this will actually ruin your bootloaders and there will be no download mode/Loki/heimdall/Odin. If you have download mode, your bootloaders are fine. If you require flashing bootloaders you need JTAG or UnBrickable (the newest method of DIY recovery of bootloaders.)

I'm willing to bet if you started flashing a modem then disconnected mid flash you would see a black screen. You are in phone--!--pc screen but your parameters.lfs is ruined.
[Samsung Galaxy S (4G Model)] RaverX3X:
dude this had nothing to do with the modem.. here ill put this more simply..

go get yourself a sgs4g flash vibrant bootloaders to it... CONGRATS you now have a brick...

sorry if you feel im takeing away from what you are trying to do this does how ever in fact work on the sgs4g which happens to be alot diffrent then any other samsung phone...

at this point im going to agree to disagree with you... Have a good day please refrain from cluttering my thread with posts thanks..

this was for people that accidently bricked there device by flashing another devices bootloaders to the sgs4g....
[Samsung Galaxy S (4G Model)] AdamOutler:
The reason I mentioned modem is because it's non-critical and will force your phone to phone--!--pc without damaging any critical partitions. Also, flashing anything sucessfully will release bootlocks and cause phone--!--pc to go away. The params.lfs has the phone--!--pc graphic contained within. I've had that graphic messed up before.

This will work under certain conditions.. like flashing any Hummingbird bootloader set... You're softbricked. It's not hard bricked. The title is completely wrong.

You can use heimdall or odin. either will work.

You need to include official bootloaders before people go flashing the wrong ones. If you do not, then you are contributing to bricking. People may flash an unmatched PBL with the SBL and the device will require JTAG.

You need to specify the --PIT in heimdall. it is an extra level of protection. If the pit and the bootloaders are matched, then you use --pit part.pit --repartition. If not then you are contributing to bricking... If the wrong partition table is written to the device, and you flash 3/4 of a SBL onto the device, it's dead. Will require JTAG.

Please revise the OP, and don't forget to give credit to Benjamin Dobell for creating heimdall... the open source alternative to Odin. Link to his thread or glassechidna.com.
[Samsung Galaxy S (4G Model)] RaverX3X:
There I updated the OP To give credit to the author of The flashing software..

and noted they will need to flash the correct boot and sbl files again... Happy now
[Samsung Galaxy S (4G Model)] willverduzco:
OK, let's keep our anger and egos in check guys. You are obviously both very knowledgeable developers who just want to help as many end users as possible.

AO brings up a good point about the mechanics of heimdall. However, many seem to have good luck with this technique. Since this is more of a guide rather than development, I am moving this to general.
[Samsung Galaxy S (4G Model)] RaverX3X:
thank you...
[Samsung Galaxy S (4G Model)] nazcalito:
it worked!!

Except that I had been trying to install Whitehawkx's Valhalla when the phone went dead and the only bootloaders I had was from the KC1 cleanup rom. It now boots with rainbows into Valhalla.

but after some hassle I'm now installing KC1 cleanup via Odin. I shouldn't have followed Whitehawkx's instructions but should have gone the long way to begin with. I just didn't want to have to spend the time. Oh well...

"Valhalla" is the place heroes go when they die, not the best name to give a 4G rom considering the problems we've had with the phone...
[Samsung Galaxy S (4G Model)] AdamOutler:
RaverX3X I submit this for your approval. I've never tried a flash with ONLY bootloaders... this may be interesting.

Download beta 10: http://www.mediafire.com/file/49f3lbl0q789i7r/RaverX3X-Unbrick-One-Click.jar
[Samsung Galaxy S (4G Model)] RaverX3X:
you do realize if you just flashed bootloaders to the device

example would be cause apparently you cannot comprehend anything in this thread at all...

flashing from froyo to gingerbread's bootloaders so when you gasp install gb you dont wind up with locked out recovery mode since the froyo ones do not work....

and say you were drunk and downloaded and flashed the wrong devices bootloaders welp there you have it paperweight

you can use this to get out of it.......

apprently you do not understand this device at all and for someone that claims there a dev and you run mobile tech videos your lack of maturity speaks in volumes....

fyi if you post after this and i dont reply no im not ignoring you i just have you blocked...

grats on makeing that one click no i wont be downloading it sorry i dont download other peoples stuff you can remove it along with your post.. If i wanted to make a 1 click id do it myself..

instead of wasteing your time here why not go gasp finish one of your roms or work on the many other 1 click wonders you are so admittedly doing...
[Samsung Galaxy S (4G Model)] AdamOutler:
no. I fully understand it. If it works, then it works. 75% of the time if you flash a bootloader from a different device you're going to end up hard bricked. However, this is not the remedy for all bricks..

Use my app. It will flash once with a param.lfs which will cure all soft-bricks and the partition is non-critical, but contains visuals. Then if further action is required, then it will flash bootloaders and partition table at the same time.

I'm just showing you a better way.

I realize I came off as a **** at first, because I didn't understand that you didn't understand what a hard brick was. I thought you thought you were flashing with heimdall on a true hardbrick.. one that you would normally take in for JTAG.

I packaged your method into a one-click to try to make it up to you. It's safer then the original method, easier to use, and it's got your name, this thread for the website and your donation link.
[Samsung Galaxy S (4G Model)] RaverX3X:
well then thanks no it was only for bootloaders i know theres other ways to hard brick a device and well kill it with out a riff box :P well then i accept your apology..
[Samsung Galaxy S (4G Model)] hechoen:
Settle down boys.

If I knew more about this I would choose a side. As far as harbricking this phone goes I've tried. Right after rooting I decided to install a Rom from rom manager. Well the closes phone the had was the vibrant so I went with it. Bootloops galore. Read xda odin new firmware. Phone boots.

It's all trial and error. Since then I've f'd this thing up more times than I can count. I've never actually not been able to recover it. Most recently I tried ripping the zimage out of whites new rom so as to be able to do a nandroid restore. Let's just say that didn't go so well. After about 27 tries on odin(not that I counted) odin recoginized the phone and I was able to flash honks kg4 kernal. Now all is well and good.

I guess the moral of this long winded account is maybe things can work out if you just keep trying. On that note fight on!
[Samsung Galaxy S (4G Model)] RaverX3X:
also updated the post to reflect what is going to be accomplished.. As not to confuse passerby's like yourself i guess i can see why you thought i was mad ... But i did update the op to reflect this is for boot loaders only. Hope that helps u
[Samsung Galaxy S (4G Model)] AdamOutler:
Flashing bootloaders is always risky. even during a repair.

You really should include the bootloaders to be used in the OP. If you unzip the jar (instead of executing it), you'll find a heimdall 1.3 tar.gz package which contains the bootloaders. This will reduce the risk of the end user flashing some random bootloader to correct the problem and ending up with a hard brick.

You have to lay out unbricking threads very basic. I think of someone trying to unbrick as someone who is in a panic, looking for quick information, trying anything they find and whatever is easiest is what they will try first. They don't know what's wrong, just that their $600 device does not work and it's based on linux and like noone knows linux.

Btw..

Softbrick=software fix

Hardbrick=hardware fix

UnBrickable=pre hardware fix... Not sure on this definition.. just came up with it in the last few days... the ones above are set in stone.
[Samsung Galaxy S (4G Model)] RaverX3X:
ya ill do that update for people that want to learn and do it themselfs with the bootloaders that they should be using also give them the jar if they just wanna click and go on with there lifes..
[Samsung Galaxy S (4G Model)] willverduzco:
Glad to see that some kind of consensus was reached. I knew that two well-regarded and knowledgeable developers could never stay on bad terms.
[Samsung Galaxy S (4G Model)] jdgonzal:
Thanks for your guide but I can't hear any sound regarding my phone drivers are present or activated also didn't see any lights like you said on your post. Any other help?
[Samsung Galaxy S (4G Model)] RaverX3X:
You can load the driver via the exe file you have to list all its samsung composit
[Samsung Galaxy S (4G Model)] Carlos2200:
Hello. Happy to see there is an alternative to jtag now. I had the unfortunate of hardbricking my vibrant some time back(wrong bootloaders). I wish this info was out then but glad its here just incase I happen to forget a step and do it again. Keep up the good work and nice walkthrough.
[Samsung Galaxy S (4G Model)] jdgonzal:
Can you explain me how to do that. By now I found difficult to make this program run OK. Thanks.
[Samsung Galaxy S (4G Model)] RaverX3X:
in the hemdaell suite that you downloaded theres a directory called drivers double click that click list all at the top pick the samsung composite hit install driver.....
[Samsung Galaxy S (4G Model)] AdamOutler:
Benjamin Dobell: Two things... Here's odin documentation, http://h1.pargon.nl/wiki/index.php?title=Odin_protocol

Also, this thread claimed to recover "Hard Bricked" phones. It's been changed quite a bit before you viewed it.
[Samsung Galaxy S (4G Model)] RaverX3X:
the op title changed but the underlining documentation has not been altered except for adding credit to the auther of the program... i did state in the op and its still there about people flashing the wrong boot loaders.... please do not try and add to what is clearly spelled out....

please unless you have anything constructive to add.. this has been done to death .....
[Samsung Galaxy S (4G Model)] connexion2005:
OK I've just got to point out that Adam has no affiliation with MobileTechVideos. Raver, I run MobileTechVideos. I'm not sure where you crossed that one up... ;)

I just wanted to make sure that any feelings you have towards Adam does not effect the way you think of me or my work as we are two different people (Adam and I) and it appeared you thought he ran MobileTechVideos. Another worthless post to the thread but hopefully you see why I made it.
[Samsung Galaxy S (4G Model)] reynaldo acevedo:
this may work in the vibrant Tmobile?, and if so could someone provide me the files (boot.bin) and (sbl.bin)

thanks

if this fails it will send to the JTAG connexion2005
[Samsung Galaxy S (4G Model)] RaverX3X:
The one click video lol sorry mate no hard feelings
[Samsung Galaxy S (4G Model)] connexion2005:
No big deal I just wanted to get that out in the open... ;)
[Samsung Galaxy S (4G Model)] Benjamin Dobell:
Really delayed response, sorry I've been busy.

However again I think it's best that I correct the misinformation in this thread. The Odin protocol used for Galaxy S devices is not the protocol you linked to, unfortunately it's totally different. That document is an incomplete description of the original Odin flashing protocol (or possibly version 2). To my knowledge there are 3 major versions. Galaxy S devices use the 3rd version.

So as I stated, the protocol used by Heimdall is not documented in any way other than the Heimdall's source code, and that was obtained by reverse engineering.
[Samsung Galaxy S (4G Model)] raghav.datta25:
My phone is dead. Doesn't show on the usb or any such response. Will this help me??
[Samsung Galaxy S (4G Model)] RaverX3X:
try it :P

10chr
[Samsung Galaxy S (4G Model)] raghav.datta25:
The Raver doesn't detect my phone. Any hopes??
[Samsung Galaxy S (4G Model)] ursubpar:
just to clarify, flashing wrong bootloaders does not mean its a brick

if your using the right combination of bootloaders (i.e.)

i9000 sbl + i9000 pbl = no problem but

T959v sbl + i9000 pbl = Hardbrick/jtag needed

:D
[Samsung Galaxy S (4G Model)] RaverX3X:
did u do from windows or linux? second did u try odin or hemadell.... just trying to get an idea of what steps u did or didnt do...
[Samsung Galaxy S (4G Model)] johnlaqua:
holy crap the wierdest thing happened!!

so i tried doing the root method for the gb kg4 i think by flashing zimages via odin...well maybe i had them crossed not sure i thought i made sure i used the right ones going by the file sizes cuz the save file names werent the same anyways...

after all was said and done it soft bricked couldnt get into recovery or download the only screen that appeared was somethin about "error while updating firmware connect to kies in recovery...."

well i have kies, kies would recognise it i tried everything, then by chance i looked at the odin window....i didnt reset it and it didnt clear out...and the id:com was yellow with a number or whatever and there was also a SECOND one as well with a different number....lol i dont know how

well i figured why not, so i loaded the tar, csc, pda, and phone files in and clicked on start....keep in mind my phone is not in download mode just that wierd kies error screen

IT FREAKIN WORKED!! how, i dont know, why still dont know

i figure maybe someone would know why and it may help someone somewhere along the line?
[Samsung Galaxy S (4G Model)] raghav.datta25:
JTAG didn't work man. :( Any other hope for me?? Please say Yes!

---------- Post added at 07:19 PM ---------- Previous post was at 07:19 PM ----------

Did it on Windows. And ODIN. Please help me man.
[Samsung Galaxy S (4G Model)] RaverX3X:
if you tried a real j tag and it dont work yes ur phone is dead done need to replace it..
[Samsung Galaxy S (4G Model)] Kyndig66:
I'm vexed. Bricked my sgs4g when I wanted to flash a ROM, couldn't get CWM Red to install, and ended up flashing i9000 bootloaders like a noob. Tried the steps outlined here several times with no luck. Also, I can't get linux to run on the computer I'm using (long story) so I'm unable to do the heimdall/linux combo. I'll be sending my phone in for repair tomorrow and am wondering if there's something I'm missing. I apologize in advance if this was supposed to be posted somewhere else.
[Samsung Galaxy S (4G Model)] Kyndig66:
Now I'm looking for suggestions on who i can send my phone to for jtag repair. Any and all will be appreciated. Thanks.
[Samsung Galaxy S (4G Model)] johnlaqua:
I sent mine in to mobiletechvideos.com
[Samsung Galaxy S (4G Model)] Kyndig66:
Sent it to them Thursday. Thanks!
[Samsung Galaxy S (4G Model)] funda439:
Phone is DEAD

I flashed my device with "[KERNEL][UVKJ6][BETA2c] Subtly Modified Stock with CWM + Voodoo Lagfix [12/10/2011]-bhundven". The flashing went fine and the phone restarted. However I was not able to enter recovery mode using the volume buttons and power combo.

Reset the phone to factory setting, compete reset and now the phone does not boot. I tried this thread, but Hemidall does not detect my device to install the driver. I am struck there. Can experts please help me?

Thanks a bunch.

-- Funda
[Samsung Galaxy S (4G Model)] dsexton702:
I'm not sure if your doing it correctly

Have the phone off

Hold volume up + volume down+ power until you see the sgs4g sign brighten

Once it brightens let go of the power button but continue to hold volume up+ volume down until you enter recovery
[Samsung Galaxy S (4G Model)] funda439:
Thank you all.

A big thanks to all, I was able to unbrick my device install hemdall based ROM on it now. Works great. Awesome guys. Thanks once again.
[Samsung Galaxy S (4G Model)] Xtrifer:
very hardbricked sg4g

My brother installed a vibrant Rom into my sgh-T959v, so wrong bootloaders, I wanted to try this method but I dont know how to install the heimdall drivers, because the phone is dead and the computer does not recognize it, not even as unknown device, please help me what should I do
[Samsung Galaxy S (4G Model)] lumin30:
Look at the heimdall one-click guide in the second link of my signature. When trying to get phone recognized read the op of this thread. Hopefully you can get it working.