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
Related
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
HELP!!
My Sprint Galaxy tab seems to be soft bricked. I tried to install the CWM recovery using the bootstrap method and then rebooting into recovery, factory reset/data wipe, and cache wipe, then rebooting. Got stuck at samsung logo and the directions of the thread said to just hold power and volume up and that will reboot into recovery so the file convertion could continue, but its SCREWED! And the worst part is that I am on vacation and I use my tab for everything. I was planning on using all this trip and I only have a mac, not a PC so Odin is out. If someone could please help and get me back up and running I would really appreciate it. Like I said all the resources at my disposal are a macbook pro and a HTC Inspire 4g. TIA
do you have an sdcard installed? Yours is doing what mine did, and then i inserted the sdcard and it started working. basically, if you dont. the phone is trying to find it so it can convert it to ext 4 and just loops.
laxwillsch said:
...Got stuck at samsung logo and the directions of the thread said to just hold power and volume up and that will reboot into recovery so the file convertion could continue, but its SCREWED!
Click to expand...
Click to collapse
Actually the instructions are to power off the device, then hold vol up and power. This may be what you were trying to say, but if you indeed tried to do it exactly as you said then it would simply power off the device.
Yes that is what I was trying to say, I held volume up and power till the samsung logo came on
And mine had an sd card in the device, do you think it is worth it to take it out and put it back in? I am willing to try anything at this point. I really just want to get it back up and running, I bought it outright and don't use the sprint network, and I use my phone for gps so I don't need either of those. Just want to know how to flash back to stock, want to use it for an ereader and to watch movies.
Sent from my Desire HD using XDA App
How far into the CwM process did it get? Did you ever make it into CwM Recovery? If not, then the issue was with the kernel/recovery flash and that should be all you need to fix.
You have a few options for doing this if you can still get to DL mode (vol down and power to boot), the easiest being Heimdall GUI or Odin. You already said Odin is out due to your current situation, so how about Heimdall? I am not sure where to get a stock kernel/recovery for Sprint, but the KhasMek Voodoo Kernel with Recovery is working for Sprint users, but perhaps with some limitations that are outlined in the thread later on. Check out the Heimdall instructions in the OP to see what you need to do if you can use Heimdall. The same instructions should apply if you can find a reliable stock kernel/recovery zImage for the Sprint tab.
beestee said:
How far into the CwM process did it get? Did you ever make it into CwM Recovery? If not, then the issue was with the kernel/recovery flash and that should be all you need to fix.
You have a few options for doing this if you can still get to DL mode (vol down and power to boot), the easiest being Heimdall GUI or Odin. You already said Odin is out due to your current situation, so how about Heimdall? I am not sure where to get a stock kernel/recovery for Sprint, but the KhasMek Voodoo Kernel with Recovery is working for Sprint users, but perhaps with some limitations that are outlined in the thread later on. Check out the Heimdall instructions in the OP to see what you need to do if you can use Heimdall. The same instructions should apply if you can find a reliable stock kernel/recovery zImage for the Sprint tab.
Click to expand...
Click to collapse
Ok Thanks I just downloaded Heimdall and am going to give it a shot, what do I have to lose. If all else fails I can just wait till I get home where I have a PC with odin and I can just flash the almost stock rom that is floating around. If I successfully flash the zimage from the kernel thread will that just replace the current kernel that may be causing the issues?
Well I think I am screwed. Heimdall failed with a failure to get a response from device error and now all I have is the phone ! pc graphic. I really dont know what to do now. I think I am going to be screwed I dont know how to get out of this. No more download mode no recovery mode. NOTHING!
PLEASE ANYONE OUT THERE!!! I REALLY NEED SOME HELP WITH THIS!! I eard that if the battery goes dead while your at phone ! pc your screwed and have to tear it down. And because I dont have a windows computer I cant use the odin method just yet.
Well not that anyone cares because of the lack of activity on this thread, but I thought I would post what fixed it just in case someone else has this problem. I downloaded a stock Sprint Rom, that actually came with a modem that works I think (I don't use sprint service but my baseband is there) and with working GPS. I found it on this forum somewhere it was called Sprint_D30_Tab or something. I went and borrowed a windows 7 pc from a neighbor, plugged my tab in when it was in Phone ! Pc mode, let it download the drivers, then loaded odin up with no PIT no Repartition, and did the CSC and PDA slots, then let it run. It took alot longer than any odin did on my captivate but it worked. I have a fully functional Tab again!
Thats good news! The cwm bootstrapper sure seems volatile for some, likely why it has never left beta status. I would recommend avoiding it, and if you get the itch to install recovery again I would go straight for KhasMek kernel until a better solution for CDMA tabs comes around, if ever.
find one windows pc and flash the pit with rerepartition, dont know if it gona boot your tab but a least alow you to acces to the download mode! pm if you need the file.
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.
if your have issues with the update not finishing 100% this will work
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
download the zip using heimdall flash like normal
factoryfs-factoryfs.rfs
zimage-zimage
param.lfs-param.lfs
cache-cache.rfs
recovery-zimage
ignore the rest of the files
then before first boot wipe data and cache reboot
manually use update.zip or just let it download itself
install update and your done
you can verify by going to "about device" build number will be SCH-I800.EC02
use superoneclick for root z4mod not working keep getting f/c's
it seems like anybody who used z4mod to root or flashed recovery "back to stock" is having problems a 100% fix is just download the files from my post and flash like normal then use superoneclick for root
***for it to work you must download the recovery files from my post***
the files in my post are created using a temp. root so the files are a pure clone of unrooted rom 100% stock that is why you have to use superoneclick to root I tried everything and have done this to 6 tabs with no errors
EC02 stock ota update.zip download
http://www.4shared.com/file/qIHEta11/update.html
Thanks, I noticed you posted this on the other thread too. I have never used Heimdall so I was REALLY trying to avoid this but I guess I will have to take the plunge and figure it out.......
this works
I have tried every which way and this way has worked every time for me
Finally worked
works 100% just followed the steps and no problems finally updated!!!!!
It works, 100% Thank you so much for this
This does work, 100%, but please note that it DOES NOT WIPE THE DEVICE. It will boot up with all your stuff. This is not neccessarily practical, but it will probably be fine. If you have any root dependent mods, such as set cpu or lcd density, they wont work and it may operate funny/slow until you reroot and set them back up.
stock restore files download
http://dl.dropbox.com/u/21215221/Verizon-GTab-Stock.zip
or
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
Download Mode (Volume down and power)
Download Heimdall from Here:
http://www.glassechidna.com.au/products/heimdall/
Also just below version 1.1.0 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Launch download mode on your tab that is already connected to your PC.
unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device or might say it other ways
Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end leaving Tab plugged in and in download mode
Unzip the stock files.
the zImage goes in both the Kernel AND Recovery slot.
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs make sure you use param.ifs not param.rfs
and the cache.rfs goes in the cache slot.
ignore the rest of the files in the zip and just use these
After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
After this runs you will more then likely have to Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
then let update download install it and you can use superoneclick if you want root back
This worked!
Thank you lexriley! That seemed to work. I forgot to wipe data/cache before i applied the update.zip, it still worked anyway. I should probably have wiped the data/cache.
Thank you !!!!!! Great Work!
Thanks so much. I rooted using Z4 and the update failed. I used your instructions and got up and running again! You saved my Tab!
I'm happy its working for everyone like it worked for me
100% fully working!!!!!!!
thank you lexriley your guide is easy to follow and do your the man!!!!!!
This should be a sticky!!!!
Sent from my ADR6300 using Tapatalk
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
oldmacnut said:
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
Click to expand...
Click to collapse
Well let me tell you what I have noitced with the upgrade
1) Stock browser speed is faster, but I dont use the stock so that wasnt much help
2)There is now a item in the top of settings for you to activate your device through verizon (like you would using *228 or whatever it is from your phone)
3)The wifi searching thing. I often forget to turn wifi off so when I drive it drains battery searching, the drain is significantly less now.
4) BLUETOOTH HID SUPPORT! Sorry for the caps but I have been wanting this one for quite some time now. First thing I did was try my MX5500 at home and it paired up and worked perfectly.
5)Hyperlinks in emails issue. Constantly many hyperlinks were cut off and I wasnt able to click them, this has now been resolved.
If none of these things are appealing to you then by all means you have no need to upgrade. But I found that most of this was a welcomed change. The tab seems faster, but I believe that is just due to the fact that I do not have LCD density changing the density, which I find slows down many things on the tab.
lexriley said:
I'm happy its working for everyone like it worked for me
Click to expand...
Click to collapse
At first it didn't work for me. I got "failed to access device. Error: -12". But that was my fault. I had forgotten to load the zagdig drivers for Heimdall. So I did that following the instructions in this thread and tried again. First try, I simply got a "fail", second try worked like a charm. When finished the Tab rebooted on its own.
As soon as it rebooted, I got the message that an update was waiting to be installed (EC02). Since I had already wiped the cashe (twice) on earlier attempts, I just went ahead and let the update install. Worked like a charm and now I've got EC02 update.
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Now to begin the task of re-rooting, installing ADW, and putting my Tab back into shape the way I had it.
BIG THANKS goes out to lexriley!! (And by all means, make this thread a sticky.)
Robin
Excellent work! This worked perfectly.
Got it, installed the newest Keis for drivers.
i hate to be that guy but is it possible to get odin files too? i can never get heimdall to work but odin works just fine
Robin M said:
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Click to expand...
Click to collapse
So if I just restore the vcast stuff then I should be able to update without doing all the recovery stuff? I just renamed them all with a .bak at the end instead of deleting just incase I needed them again so I still have them all.
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
shiltz said:
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
Click to expand...
Click to collapse
You're welcome. ...Isn't it great when you answer your own questions? I find myself doing that more frequently now, as I learn more about Android and my Tab - mostly from this forum.
PS... Now that you've successfully updated, take a look at the recovery.log file in your /cashe/log folder. I was amazed at the number and the variety of files this upgrade patched.
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!!