[Q] Semi-bricked? HELP!? - Vibrant General

So I began playing around with "rooting," my Vibrant. I'm a computer engineer, but relatively new to the whole "smart phone," thing. Loaded a few different ROMs, played around a bit. No problem. At some point tonight, I tried to load a new ROM, and after clockworkmod, the vibrant screen took FOREVER. That's about the time my cats went crazy. Long story short, I dropped the phone. Cover popped off, battery fell out.
Now, the phone is sitting at the Vibrant screen for hours, will not boot into recovery mode, and if I plug it in, it just shows a gray battery.
I've tried the 3-button recovery mode over and over, with no success. Nothing at all. I CAN get to "download," mode, where I get the droid icon, and it says "Downloading...Do not turn off Target!!!" That said, I have no idea what, if anything, I can do from this screen. I have no idea what to do, but I know I can't afford another 500.00 phone. Please help!!
--SFGAirborne

http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Sent from my Vibrant running Bionix-v 1.2.1 in GingerRED

Probably you will need a couple of things in your tool kit.
You will need Odin 1.3 or higher
Pit file (there are 512 and 831) Guessing you will need the 512pit
Original JFD stock file 2.1
Eugenes froyo that does not brick
Remove the sim and the sd card, remove the battery have Odin up on the computer> then hold down the 3 buttons and plug in the phone to the usb connected to computer. If this works and Odin sees the phone (does not matter if it says com5 or 6 etc.) then you can go from there, If not then you will need a jig, people here sell them, i saw connextion2005 sells them but there are others (like 8bucks) or you could make it is 301k resistors tied to one 2 pins of the usb (do a search if you are interested).
Then the sequence for the fix is to flash the Froyo first that does not brick (do not check repartition) once it begins to reboot pull the battery out (does not need to reboot) then flash the JFD on top and this time check the repartition
Let this finish reboot> then use super one click root or other of your choice. Then download CWM and Titanium backup...... flash your new rom and you are back in business.
Hope that helps

Thanks a ton! Open-source research indicates Odin is a proprietary tool used by Samsung techs, correct? I'm not at home right now, so I can't do anything with it, but I will download and run when I get home. Does it have to be run from Windows? I'm a Linux user. If necessary, I can build a VM, but if Odin will work easily in Wine, that's better for me.
Again, thanks for the help!

Odin is your one way stop to guarantee that your phone will always work, unless it's hardware issues.
I have used Odin to go back to stock so many times to clear data, to reflash ROMs or to recovery from splash screen loops or soft bricks. Always works like a charm.
You should check out CyanogenMod forums under Galaxy S and there is a step by step guide how to do it. That's what I use. Works always!
Sent from my SGH-T959 using XDA App

sfgairborne said:
Thanks a ton! Open-source research indicates Odin is a proprietary tool used by Samsung techs, correct? I'm not at home right now, so I can't do anything with it, but I will download and run when I get home. Does it have to be run from Windows? I'm a Linux user. If necessary, I can build a VM, but if Odin will work easily in Wine, that's better for me.
Again, thanks for the help!
Click to expand...
Click to collapse
I have a friend running fedora and odin works fine for him, if you have problems with Odin there is another application out there called heimdall, you will have to excuse me as i have no experience with it, but have heard that it plays well with linux and unix systems when odin doesnt.

sfgairborne said:
Thanks a ton! Open-source research indicates Odin is a proprietary tool used by Samsung techs, correct? I'm not at home right now, so I can't do anything with it, but I will download and run when I get home. Does it have to be run from Windows? I'm a Linux user. If necessary, I can build a VM, but if Odin will work easily in Wine, that's better for me.
Again, thanks for the help!
Click to expand...
Click to collapse
Try Heimdall: Here is a post I did last week:
http://forum.xda-developers.com/showthread.php?t=944598
maybe you will get better results with this, there also is a linux version as well

The Bible is also a good reference:
http://forum.xda-developers.com/showthread.php?t=771111

Restoring via ODIN, as we speak. No idea how long it'll take, but I'll let you know the outcome. Again, thanks a ton!
And, I've definitely learned my lesson. Being a "computer guru," does not necessarily translate to being a "technology guru." I should probably RTFM before playing with things I don't know next time. If I can ever off you all any network security advice/assistance, please feel free to ask.

You all rock! Fully restored, back up and running!!

Related

restore from ROM manager bricked my phone

I did a search and couldn't find much help.
I recently dropped my phone and the screen got a slight crack, so the insurance company sent me a new one.
I figured I'd use ROM manager to backup my old phone, and restore it on my new phone.
New phone restores, reboots, and gets stuck at the black Vibrant screen.
I can get back into recovery mode fine, but nothing seems to work.
I let it sit at the Vibrant screen for about an hour before I try again.
Its attempt 3 when I decided to come on this site for some help.
Specs:
Stock
Rooted
Launcher pro
Nothing too much to be confusing and brick, so wtf?
Oh and I understand I could use odin to reflash my phone, please please please don't suggest odin, because I don't own a PC, I own a mac. Please don't tell me to go out and buy a PC or to download a program that costs $50 to use PC programs on a mac. I could have told myself that kind of information.
HELP, my brand new phone is destroyed wahhhh
From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App
a400meter said:
From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...
yelowbottlecaps said:
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...
Click to expand...
Click to collapse
The only way I can think of that a nandroid restore would soft brick you, is because you have restored a version of android with a different kernel.
If the original phone had the original firmware (JFD), and the replacement had the most recent (JI6), this is what would be expected to happen.
Since you seem unable and unwilling to use Odin, your going to have to tell us more details (i.e. which versions of the firmware as related above were actually in play) before we can begin to help. If you don't know, well....
You can also simply take it back to a local T-Mobile store and do another swap, or you can find a friend with a Windows PC and Odin (or Samsung's Mini KIES with JI6). These are your only real options...
both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.
so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?
yelowbottlecaps said:
both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.
Click to expand...
Click to collapse
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
[PROGRAM] Heimdall - Cross-Platform Open-Source Flashing Software (1.0.0 Available)
Heimdall's Website, with downloads...
XDA Dev Thread with JI6 Odin .tar file....
Best of luck!
s15274n said:
so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?
Click to expand...
Click to collapse
True that...Why didn't I think of that obvious ploy. If he can get into Recovery, and bounce over to clockwork...Well now's a good a time as any to try Bionix or Bionix Fusion...or a few other of the CW Recovery installable builds...Definitely easier than Heimdall or working out Odin on a mac....and definitely preferable to staring at a Vibrant logo...
{{facepalm}}
masterotaku said:
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
Best of luck!
Click to expand...
Click to collapse
If there was a step by step walkthrough, I have no problem trying this out.
But I downloaded it and have no idea what I'm doing. Therefore, still SOL
^ are you? You didn't answer my questions.
I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL
I just tried using Odin on my roommates PC. An error happened and now the phone is showing a picture of a phone, a couple dots, an exclamation mark, a couple dots, and a computer.
Nothing I can do is taking it out of this screen. Unplugged from computer, took out battery, took out sd card, put it back in... nothing
Am I bricked for good now?
This is a terrible day.
edit: i managed to be able to get the phone into download mode.
No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.
All~G1 said:
I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL
Click to expand...
Click to collapse
If someone can back this up with some instructions that would be amazing.
All~G1 said:
No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.
Click to expand...
Click to collapse
Thank you for the motivation!
yelowbottlecaps said:
Thank you for the motivation!
Click to expand...
Click to collapse
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.
All~G1 said:
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.
Click to expand...
Click to collapse
and in the midst of a roommate that needs his pc back.
I still need a fix that would work for macs... if not, I'd have to wait for my roommate to let me bum his pc again
Do my posts not show up or something? wtf.
s15274n said:
Do my posts not show up or something? wtf.
Click to expand...
Click to collapse
/me pats s15274n on the back....don't get mad...get even! =P
Honestly, sounds like yelow's focusing on getting all the help s/he needs from All~G1. I wouldn't worry about it.
~SB

Bricked epic4g using odin

I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.
Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...
Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...
At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."
Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...
Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.
After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!

How To Recover Your Fascinate From Any Brick, And Rooting Methods

HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. Sorry but the links to some of the files are gone I don't have them anymore so I suggest you look through the comments someone will have someplace to get what you need. Your recovery methods may have changed but this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.​
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
This is a great source of information. The formatting could be a little better though. Perhaps break up those great giant paragraphs a bit. It would be easier to follow along. Especially for noobs in a panic state after "bricking" their phone.
Great work though. This should be stickied.
I will Update thread to an easier format over the next few days. Thanks for the tip, i looked good to me but now i see what you are talking about. It took hours today to gather all the info, pull up each program ans walk through it. I guess I was in mental overload.
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You were that guy.
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Oops, but at least i was consistant on the typo...LOL. I will fix it this weekend.
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Figured out this morning I wasnt using my factory usb cable switched cables odin'd stock eb01 worked perfectly now I feel retarded.
Sent from my SCH-I500 using XDA App
Excellent write up. Thanks a bunch.
What are some other differences in Odin 1.7 vs 1.3? I have used 1.3 many times and never had any issues. Any improvements?
Thanks so much Dale! headed to work now, but will try this tonight
Rayn1328 said:
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
More reasons as to why you should never fear bricking your phone and testing new kernels and ROMs. Thank you for the thorough tutorial.
cbalt said:
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
Click to expand...
Click to collapse
I prefer what i think is a much simpler method. Just go to this link and follow Post 2. I don't believe I have ever had it so easy to root a phone:
http://forum.xda-developers.com/showthread.php?t=948722
nice write up, thanks for posting. I hope I never have to use it
netwalker0099 said:
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Click to expand...
Click to collapse
Got that once cause i didn't install the drivers in zadig. I installed it, didn't reboot PC, worked fine. If you had the CSC unchecked then you didnt install a cache or database, so no your phone wont work like that. Unless you ran into something new, follow this guide step by step, and it should work. I would also make sure you get the files from here, they are tested and known to be good. There are some incomplete, and bad files out there, these work.
Heimdall is officially the greatest piece of software ever created and DaleV is my hero!!! FINALLY have my phone up and running again! Was serious contemplating dropping around $300 for a new phone on Craigslist.
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Oxirane said:
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Click to expand...
Click to collapse
after it failed did you unplug then replug and go back into download mode? also I updated the OP with a superuser.zip file it works better than the one in the market for showing you have root access, I have no idea why.
Also you might try a different usb port, sometimes that does the trick.
I've unplugged and replugged and rebooted it a dozen times... it first goes to 2e recovery, then I reinstall packages and it reboots to the simplified download mode with just basic little icons. Doesn't get recognized by the computer though. :/
Wont boot into anything but 2e, and from there into oldschool download mode.

Stock DL17 ODIN Image With Root

I notices a few users have mentioned that they're dealing with trying to restore or unbrick their Continuum after flashing incompatible kernels and other problems.
I made this backup immediately after I got root, before I did anything else, to make absolutely sure I wouldn't be SOL if anything went awry. I've made absolutely certain this works, by unzipping and flashing on my own Continuum prior to uploading. It contains the system, recovery, and kernel partitions.
This file is also helpful if you need to get back to stock for warranty purposes, in which case you can manually un-root by using your favorite file explorer (I happen to prefer ES File Explorer), grant root permissions, mount system as rw, then manually delete SuperUser from /system/apps, su from /system/bin, and busybox from /systen/xbin. I hope this helps some of you who have been stuck.
You don't need to be rooted to flash this. Simply unzip, flash the .tar.md5, and you're golden. If you end up in restore mode after flashing, you probably need to do a hard reset, but this is unlikely as I tested it by flashing this a few times after installing various programs from the Market and never had to do a hard reset.
Don't forget to put your phone in Download mode by removing the battery, then holding the vol down button while inserting the usb cable. Good luck!
http://www.mediafire.com/?a897dbakz4j7k4f
Thanks for this. I had been messing around with the phone. I was able to get it back to stock.
Kay I try to flash this and it's telling me it's an invalid image type
Never mind, I got it. Thanks
Not a problem, glad I could help!
My phone was soft-bricked. This worked like a charm. Thank you so much!
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
kingtuk1 said:
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
Click to expand...
Click to collapse
Yup, gotta wipe! At first it's so easy to forget this step. When you get to customizing your installation, you'll get to used to having to wipe it'll become second nature!
I'm so glad to hear this is coming in handy for you all! Now that you got this done, get yourself froyo, courtesy of imnuts: http://forum.xda-developers.com/showthread.php?t=1197415
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Native89 said:
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Click to expand...
Click to collapse
Read the OP from pastorbennett here: http://forum.xda-developers.com/showthread.php?t=1203597 and try the unbrick process. You can do a search for pastorbennett and trailblazer. Both have posted "recovery processes", or at least links to others that have posted recovery processes. They've saved my butt a couple of times... Except on my first phone that wouldn't go into DL or Recovery Mode. It would just flash the Samsung logo, over, and over, and over again... That happened before pastorbennett posted the unbrick info. Oh well, Verizon replaced it under the hardware warranty. Thankfully.
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Native89 said:
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Click to expand...
Click to collapse
Okay, if you can, grab a different computer (either Windows XP or Windows 7) and install the samsung drivers from this post: http://forum.xda-developers.com/show....php?t=1203597. The hint here with ANY Windows computer is to install the device drivers FIRST! (I've been a system administrator for about 20 years.) Then plug in the hardware. It usually makes the installations go MUCH smoother.
If you have to use your computer, try installing the Samsung drivers first, then plug the phone in.
zzir said:
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Click to expand...
Click to collapse
The key to odin seems to be this:
1. Start odin.
2. Click the PDA button and select the odin TAR or MD5 file. (You can only do one. Not both.)
3. Make sure the phone is not plugged into the computer.
4. Make doubly sure the phone is not plugged into the computer.
5. Put your phone into download mode. (With the phone off, hold the Volume Down button and turn the phone on.)
6. Then plug the phone into the computer.
7. Start the odin flash and you should be good to go. Also, before unplugging the phone, make sure it says either success or failed. If it doesn't say anything, or says loading (or something like that), WALK AWAY! Go get yourself a cup of coffee, a soda, a nice cup of tea... Something. I recommend waiting at least 10 minutes. If the progress bar has not moved, in that time, okay, then pull the cable and the battery and start again.
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Tarheel487 said:
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Click to expand...
Click to collapse
Did you flash the CWM Recovery in Odin? (cwm_recovery_test4_adryn.tar) Can be found here if not http://forum.xda-developers.com/showthread.php?t=1230072
is it possible to flash this with heimdall or only odin?
ntien said:
is it possible to flash this with heimdall or only odin?
Click to expand...
Click to collapse
I don't know, however, pastorbennett posted this http://forum.xda-developers.com/showpost.php?p=16600453&postcount=29. It might help? I use Linux at home to build most of this stuff, then use my wife's Windoze machine to flash. It just seemed easier.
Yes, you can use heimdall, you just need to extract this .tar and put the extracted files in the corresponding location in heimdall xD
Sent from my SCH-I400 using xda premium
yeah i saw that but in heimdall 1.3 the UI is different. i don't know where to put any of the stuff. i have the .tar but i dont know where to put the other stuff. here's a screenshot

Need Urgent Fascinate Help

I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
want a droid said:
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
Click to expand...
Click to collapse
Odin the proper clockwork,reboot straight to it, wipe data and then flash CM7 from the SD card.
Please give me step by step instructions with links. I'm an HTC Thunderbolt guy myself so I am having a hard time finding all the right links and stuff. I really appreciate your help!
First sticky in this forum has all the links and steps.
Sent from my SCH-I500 using Tapatalk
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
want a droid said:
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
Click to expand...
Click to collapse
Really? did you look at the sticky?
Code:
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. All of the files, I cant guarantee links to other OP's, will still be available, I wont take them down. Your recovery methods have not changed, nor have the PIT files, so this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1026746
odin...
atlas_v2.2.pit
CI500_VZW_ED05_FROYO_REL.tar.md5
check repartition
then follow the CM wiki
I don't understand why I'm getting this: http://imgur.com/WkDsK
Sorry for rotated picture.
I'm in the process of flashing the verizon firmware but it's taking forever to download. I thought I could just odin the CWM?
You better do some research before u brick ur ****...there are guides all over the place on how to get back to stock/flash roms. And last but not least all questions should be posted in the q&a section...that's what its there for...seriously use it!
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
When I try to connect it to my mac it says it can't read what I'm trying to connect. When I connected it to windows laptop it says its a CD drive that is write protected.
I can't move any files in or out. Also when I try to flash a rom zip in recovery it doesn't work.
I'm in the process of trying to restore her MIUI backup. Here's to hoping that works.
EDIT: Supposedly the restore worked, but here is part of the error that showed when trying to flash a zip (top text): http://imgur.com/X1RQL
Oh and I'm stuck on the Samsung screen now...what do I do?
want a droid said:
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
Click to expand...
Click to collapse
fail.
if you did CM Wiki, you have CWM 4.X, not 2 or 3
you need to flash back to stock like i said
I did flash back to stock. Anyways in the broken clockwork recovery I decided to try and install MIUI again and when I clicked it it took me to an orange recovery.
Then I flashed her backup and it loaded up fine. Hopefully everything is back to the way it was. I'm not sure what ever went wrong in the first place.Thanks for your help.
Dude...sounds like you just made it hard. Its actually quite simple.
Pull battery, put in download mode.
Odin the Verizon firmware with atlas.pit and repartition checked.
let it boot, then shut it back down and go back into download mode and Odin the fixed recovery for CM7. Then flash MIUI and profit.
It shouldn't take but about 15 minutes out so for the whole process
Swyped via Tapatalk
Well I wish you had been here last night. I was told to do the heimdall thing and then after all that the phone wouldn't be recognized in odin.
It was a frustrating 3 hour long process (granted ~1h was waiting for the 441MB file to download).
so I found this thread searching through the fascinate forums and i gotta say, it saved my ass. I used heimdall 1.3.1 and it wasn't working right for the flash. IDK why but when I tried 1.1.1 it worked first try to flash back to stock after brick. I used the eh03_full_odin.zip file in heimdall and it quick and easy to get back to stock =] this forum rox!!

Categories

Resources