Database Users

[Q] Bricked Epic - tried everything

Well first off, ive been at this for 2 days and its frustrating. I am new to this flashing and rooting business and ended up bricking my phone from using the wrong files in metamorph and never backing my stock files up. It would give me a blank screen with the red LED lit up and all my home buttons on the bottom lit up. I followed the Odin directions and actually got my phone to stock. But it was extremely laggy and and i had no service and my SD card just kept connecting and reconnecting. Well i followed the flashing kernel threat because someone told me to try that so i can get the stock kernel or whatever on the phone. That failed and now im sitting here with my phone displaying a phone icon and a computer icon, then a caution symbol in the middle. Someone pleaseeee help me fix this.

l2,
I've been there 3 times this morning already as I hadn't flashed a new zImage to this particular device yet until this morning. What you need to do is get the stock files from http://rapidshare.com/files/415661977/SPH-D700-DG27-8Gb-REL.tar.html and s1_odin_20100513.pit (it must be 13, not 12). Boot into Download mode (hold 1 when powering on). Start Odin 3, check Auto Reboot and Debug En. Choose your PIT file, and under PDA choose the SPH-D700-DG27-8Gb-REL.tar. Plug in your phone, once it is recognized in Odin click Start. This takes about 10 minutes, I know it looks like it hangs up a couple of times but it should keep going. Let me know if that helps.

khalaan said:
l2,
I've been there 3 times this morning already as I hadn't flashed a new zImage to this particular device yet until this morning. What you need to do is get the stock files from http://rapidshare.com/files/415661977/SPH-D700-DG27-8Gb-REL.tar.html and s1_odin_20100513.pit (it must be 13, not 12). Boot into Download mode (hold 1 when powering on). Start Odin 3, check Auto Reboot and Debug En. Choose your PIT file, and under PDA choose the SPH-D700-DG27-8Gb-REL.tar. Plug in your phone, once it is recognized in Odin click Start. This takes about 10 minutes, I know it looks like it hangs up a couple of times but it should keep going. Let me know if that helps.
Click to expand...
Click to collapse
okay ill try all of that but Where can i get the 13 pit file?

It can be downloaded from this link.
http://www.4shared.com/get/6aSCPmEf/s1_odin_20100513.html

khalaan said:
It can be downloaded from this link.
http://www.4shared.com/get/6aSCPmEf/s1_odin_20100513.html
Click to expand...
Click to collapse
thanks so much man ill try it out. One question though. I already started this odin thing and its doing its thing. its about half way done but its using the 12...can i just shut my phone off and put it in download again when its done and use the 13 and it will work?

If you have it going with the 12 already I'd give that a try, if it doesn't work you can always get back into download mode and do it with 13. I couldn't get 12 to ever start it would always sit for 20m and do nothing.

khalaan said:
If you have it going with the 12 already I'd give that a try, if it doesn't work you can always get back into download mode and do it with 13. I couldn't get 12 to ever start it would always sit for 20m and do nothing.
Click to expand...
Click to collapse
okay yeah ill try. but its been sitting for like 10 min at half way on the status bar...

That is way the devil too long, go ahead and unplug your phone, hit reset in odin, set it up like I instructed, reboot your phone to download mode, and give it another go.

yeah lol okay i thought so. haha

Alllll fixed. Thank you guys soooo much for helping out. Im going to root again but i'm not gunna mess with metamorph this time lol, whats a good root? Im learning all this stuff and idk what one i should do.

http://forum.xda-developers.com/showthread.php?p=8628341#post8628341
>_>

Please Modify Title of Thread add
" Solved - Bricked Epic - tried everything "

I bricked my Epic last weekend and am feelin' ya on all the stuff you did to unbrick it. Glad to hear that all is well~

I screwed my setup up and had to do the Odin method yesterday. I didn't read this post before hand, and I used the ****12.pit instead of the 13. What is the difference in the two? My phone seems to be working just fine with the 12. One problem I found I don't believe I had before is theming the dialer_tab_activity.apk FCs the phone on hangup, but when I put another one in unthemed, it works fine.

help
I cannot get phone to load any tar completely.. they all stop and phone's screen goes purple. Most the time it hangs in odin at the zImage and then sometimes it gets a few bars going .. and hangs at factoryfs.rfs. Any help

You don't need the pit file when flashing a tar rom. It's only for modems and kernals. I have used Odin and haven't used the pit. Works just fine.

Okay, i just joined. Sorry if i sound ignorant (most likely cause I am) but i am fairly certain i semi-bricked my Epic, okay so it started when i flashed the CyanogenMod it was very laggy so i figured i did it wrong, quickly using clockwork i flashed VIPERrom (FRoZeN) DK28 all looked fine but then my phone's service started acting up, so i tried to re-flash CyanogenMod. This ***** it up worse it got stuck at the Samsung boot logo, now i am trying to revert to Stock but Odin nor my Cpu recognize the Device.
Extra info that might help, I have the Stock Tar, Odin 1.6 with Pit, can get into both download and CW recovery...
Help this ignorant fool please T_T

The Boxinator said:
Okay, i just joined. Sorry if i sound ignorant (most likely cause I am) but i am fairly certain i semi-bricked my Epic, okay so it started when i flashed the CyanogenMod it was very laggy so i figured i did it wrong, quickly using clockwork i flashed VIPERrom (FRoZeN) DK28 all looked fine but then my phone's service started acting up, so i tried to re-flash CyanogenMod. This ***** it up worse it got stuck at the Samsung boot logo, now i am trying to revert to Stock but Odin nor my Cpu recognize the Device.
Extra info that might help, I have the Stock Tar, Odin 1.6 with Pit, can get into both download and CW recovery...
Help this ignorant fool please T_T
Click to expand...
Click to collapse
You forgot to flash the EXT4 or RFS Kernel
http://android.stolenrobot.com/Epic4G/epic.htm
that comes with cyanogen it looks like just put either on your sd card then flash after you flash cyanogen in Cwm
Here is some more info
http://forum.xda-developers.com/showthread.php?t=935060&highlight=tutorial

iSaint said:
You forgot to flash the EXT4 or RFS Kernel
http://android.stolenrobot.com/Epic4G/epic.htm
that comes with cyanogen it looks like just put either on your sd card then flash after you flash cyanogen in Cwm
Here is some more info
http://forum.xda-developers.com/showthread.php?t=935060&highlight=tutorial
Click to expand...
Click to collapse
I did flash EXT4 "CM6EXT4kernel-1-2-2011" this one to be specific.

The Boxinator said:
I did flash EXT4 "CM6EXT4kernel-1-2-2011" this one to be specific.
Click to expand...
Click to collapse
did you wipe x3 ?

[Q] So I think I just bricked my phone :(

Was trying to install clockworkmod and instead of using "PDA" in Odin3, I used "Phone" to flash stuff...
My phone boots to android now but will not get a signal period.
Any ideas?

Nimhlan said:
Was trying to install clockworkmod and instead of using "PDA" in Odin3, I used "Phone" to flash stuff...
My phone boots to android now but will not get a signal period.
Any ideas?
Click to expand...
Click to collapse
You killed modem.bin. We have not been able to recover from this yet. Exchange the phone.

Man. Oh man. Definitely take it n
It's a goner. Im
they call me...kick ass

hahahaha i gotta laugh
because i did the exact same thing --

Would the modem.bin be in the system dump? If so, could that be flashed to fix the problem?
The reason I ask is because I've done the samething, but I've seen on the Vibrant forums that it can be done.

If you flash over modem.bin on a Fascinate, as of today (and probably until Verizon/Samsung posts an official firmware) you're screwed.
There is no magic solution. I'm not even going to bother explaining how much time has gone into trying to fix this problem. If we could fix it, we would've done it already.
1 - DO NOT FLASH ANYTHING IN ODIN'S "PHONE" BOX.
2 - DO NOT FLASH ANYTHING NAMED MODEM.BIN

Modem.BIN

OOPS! I messed up in odin when flashing my first rom, with my new $200 phone my dad bought me two days ago. As you can imagine I am extremely sad, and I need some help. Anyways, I think I did something in Odin that messed up my modem.bin, which explains why i have a circle with a line throught it on my notification bar where the signal status would usually be. So, I thought, the DJ05 update has modem.tar, and I flashed that with Odin, but I still have that same circle with a line through it. Plz Help

Flash in PDA. Not phone.
Good luck.
Sent from my SCH-I500 using XDA App

yes, if you are lucky PDA will work... Try it and if it doesn't work, there are other things you can do.
But if you're not going to read and respond to this thread. I'm just wasting my time typing this out for you.

Been doing
Thats what I've been doing, I flashed it in PDA before flashing the rest of DJ05. I have read, and Im not just posting this without looking.
-Dan
Edit:
Do I need a PIT file to flash the modem, because I haven't been using one.

No, you don't need a PIT file with the modem. What did you flash initially that started this problem? There may not be anything you can do.

Sign up for the extra insurance. Step on your phone, pay the $80 deductible and get a new phone. Cancel insurance.

Well, I rooted it, installed clockwork mod, and then the SuperClean Rom. Then I decided to go back to my Nandroid backup, but that was unsuccesful so I went to do something in Odin (I think I was trying to restore to DJ05 again). Please tell me all of my options. Im already extremely upset, and the phone was bought off Ebay N.I.B so there is no option of that insurance.

Do you know exactly what it was that you flashed via Odin and how you did it? Was it something in this forum, another forum? Was it something for the Telus Fascinate? Did you use the phone button or pda button when flashing?

To be honest, I really cant remember what I was flashing, I as probabley trying to re-install DI01. It wasn't anything from Telus or the Vibrant, it was specifically for Verizon. And I always did it in PDA. Except today I flashed the DJ05 modem.tar using phone. Hope thats not bad.

dandog96 said:
Except today I flashed the DJ05 modem.tar using phone. Hope thats not bad.
Click to expand...
Click to collapse
That would be the problem, and there isn't a fix as far as I'm aware.

Ok, well even without that, my point is I did this about an hour ago. And even before every flashing in phone I had this problem. I am so upset.

Please post in the relevant forum next time.
Thank you.

nir36 said:
Please post in the relevant forum next time.
Thank you.
Click to expand...
Click to collapse
My apologies. Any Updates?

If you flashed via the Phone button at any point, your phone is no longer usable or fixable unless someone has found a fix that I haven't seen yet. Whether the problem started before you used the phone button or not, using the phone button pretty much guaranteed there is no way to fix it.

Im a NOOB so I might not be right, but here is my argument. There have been people with the same prob. that pressed the phone button before. Theyre solution has been to flash a new modem.bin. I just want to know WHY after having the same problem as other people, and taking the same solution my phone still doesnt work. I don't know, maybe im just not willing to take a broken phone as an answer.... but...

dandog96 said:
Im a NOOB so I might not be right, but here is my argument. There have been people with the same prob. that pressed the phone button before. Theyre solution has been to flash a new modem.bin. I just want to know WHY after having the same problem as other people, and taking the same solution my phone still doesnt work. I don't know, maybe im just not willing to take a broken phone as an answer.... but...
Click to expand...
Click to collapse
As far as I know, no one has recovered their phone after flashing the modem via the Phone button. Any links to support that?

imnuts said:
As far as I know, no one has recovered their phone after flashing the modem via the Phone button. Any links to support that?
Click to expand...
Click to collapse
http://www.droidforums.net/forum/samsung-fascinate-development/97808-modem-bin-no-signal-fix.html
Right now Im going to Odin restore DI01 stock to my Fascinate and then try and OTA update via Wi-Fi if that is possible.

You can't update OTA via wifi... That contradicts itself. And if you are flashing to stock DI01, what are you hoping to update to? DL09 isn't available yet.

Have you tried flashing the all in one di01 by adrynalyne? That may be you only option.
Also, samsung gives a warranty, you might be able to take it to vzw in worst case scenario.

Kevin Gossett said:
You can't update OTA via wifi... That contradicts itself. And if you are flashing to stock DI01, what are you hoping to update to? DL09 isn't available yet.
Click to expand...
Click to collapse
Welk as I read on x.d.a today dl09 was officially released for download by ota. Im 90% sure

Psa\\\\\ important - must read ! ! ! !

Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,

have you tried using odin with the repartition checked

Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks

a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader

not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.

I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.

I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.

Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk

STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.

I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?

I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.

This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend

Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.

black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!

If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.

Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.

drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.

jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?

SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,

Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk

\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.

Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!

you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY

Yep, updated, thanks!

Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.

Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???

sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse

on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!

icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?

sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?

icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?

sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.

icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.

Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.

Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.

WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK

Has anyone flashed the three button fix? I really want to. just wanna verify its ok.

likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here

double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard