trouble with ODIN - Fascinate General

Hey guys, been trying to recover my phone from a bad flash and am having some trouble getting past EB01.
So i heimdalled to EB01 and seem to be stuck there, I've done OTA updates and tried to Odin imnut's ED03 recovery but both seem to fail to update regardless midway through the update. During the OTA i get a triangle with a "!" in the middle and my phone reboots and during the ODIN my phone while in download mode - the bar will actually just stop at the 60% mark or so.
Any ideas?
Thanks

Could be a corrupt download, did you check the md5 of the file. Also I have two machines, and my Windows 7 x64 has issues with my fascinate and download mode, but my 7 x86 machine works like a charm. Also im sure you already did this but make sure your selecting PDA mode.
Sent from my SCH-I500 using XDA App

Try this:
http://forum.xda-developers.com/showthread.php?t=1212239

Thanks algorithm that worked!
Sent from my SCH-I500 using XDA Premium App

Related

Bricked my epic. Need help restoring it

Hi guys,
I know it's supposed to be virtually impossible to brick the epic but I don't know how to fix mine using the threads in this forum.
I originally rooted my phone, installed Clockworkmod and had the genocide Kernel installed.
This morning I tried to flash the Bonsai rom. Everything seemed fine and I got the message that the flash was successful. Upon reboot the phone just stays stuck at the Samsung screen.
I've tried to use Odin to reset my phone but Odin doesn't detect my phone and anything I try to do within the recovery screen gives me the message that says
E:Can't open /cache/recovery/log
Can anyone help me get my working again? And what do you think went wrong in my attempt to flash Bonsai? Could it have been that I already had Genocide kernel on there?
If Odin isn't detecting your phone, try rebooting PC and use a different USB port and cable, if possible.
Sent from my SPH-D700 using XDA Premium App
Are you in download mode when you are using Odin? If not... open keyboard while phone is off and hold down 1 and the power button. If that's not the problem try another cable.
Sent from my SPH-D700 using XDA App
I am in download mode. I will try to reboot my laptop and change the USB port. Hopefully that works. If not it won't be until tomorrow when I have access to different cables. Will let you know how it goes.
Have you successfully used Odin with this particular laptop and cable?
Sent from my SPH-D700 using XDA Premium App
As long as you can get to Download mode, you Epic shouldn't be bricked
Instead of using Odin, try the SWUPdate version of the EB13 update with the phone in download mode
xxmastermindxx said:
Have you successfully used Odin with this particular laptop and cable?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
When I used odin to flash to Froyo I was using my desktop. This was my first time using the laptop. Looks like it was a bad idea!
I rebooted the laptop and changed USB ports and still no cigar. When I plug the phone in Windows goes into it's plug n play routine trying to install drivers for the devices which unsuccessfully install. I've previously installed the Samsung drivers on the laptop in order to mount the SD card so I'm not sure why doesn't recognize the phone. Any idea on why this happens? Is it normal when the phone bricks?
It won't be until late tonight Pacific time or tomorrow that I will be home and able to try things out on my desktop where I previously used Odin successfully.
U should use your desktop for this since its worked for u in the past
Sent from my SPH-D700 using XDA Premium App
I think a PC reads the phone differently depending on what mode its in, someone correct me if I'm wrong. Mine has come up as a disk drive, an adb interface, a modem, and just plain phone. Not sure of the exact reason.
But yes, use the PC that's worked for you before. I'm sure your Epic just needs a little love
Sent from my SPH-D700 using XDA Premium App
Thanks guys, I'll try it on my PC as soon as I can and hopefully it'll all work out.
I had a similar situation where my netbook would not recognize my phone, but everything works normally on my desktop.
I had the same problem. I think to fix it I had to run the one click root for ext4 and then flash the rom. Hope this helps.
I had a similar problem but was able (eventually) to get cwm to boot and restored from nandroid
Swyped from my Epic on Bonsai
Thanks for the suggestions guys! It was as simple and unintuitive as using my desktop and the cable that came with the phone to get Odin to detect the phone. I'm now flashing back to stock before rooting and putting on a custom ROM
Glad to hear it went well
Sent from my SPH-D700 using XDA Premium App

[Q] Tried everything. Cannot reroot!

So I bricked my phone. This time couldn't recover. Warranty replaced it, got my replacement the next day. I've never had a problem rooting before, but this time I can't seem to get anything to work. I'm wondering if they sent me a phone with some type of root protection, if that's even possible. Please help, this really sucks. Tried Superoneclick repeatedly, different versions. Univ Androot doesn't support Sammies (at least not ours). Z4Root doesn't work. Tried Oclf and in the recovery menu I get E:signature verification failed Installation aborted. What do I do?
Last resort (well, actually first resort too): flash adrynalyne's clean rom... That has root built in...
of course you need cwm working to do so....
Sent from my SCH-I400 using XDA Premium App
Hmmm
Ok, I have only previously installed CWmod (once rooted) via Rom manager. Now, not having root, I dl'd cwmod_v08 and dropped the recovery and update.zip on my sdcard. I reboot, holding volume up/volume down. I select apply sdcard:update.zip, and I'm still getting a signature verification error, just like I got when I attempted this via OCLF. I read online that it is a problem with Android System Recovery <3e>, and to revert to 2e to remove the signature verification, but I already show 2e. WTF? I'm about to retrieve my hammer and root this piece Thor-style!
Haven't used Odin, but I guess it's time...
First off, lol @ the Thor thing.. haha
Second, yeah it is definitely time... just make sure you are flashing just the adryn_cwm_recovery4 ( something like that) file in the guide in this thread xP
And make sure you use pda, not phone....
If you still can't get it working, just ask here....
Also, before I'm done... i highly suggest not flashing a full dump in Odin.... just saying xP there is a corrupt version out there ( not on purpose)
Sent from my SCH-I400 using XDA Premium App
Ok, I'm using Odin 4.28 and it looks different than all the vid tutorials I'm finding...cwm_recovery_test4_adryn.tar is on my desktop, but when I hit PDA and try to select it (the tar file) it says "Invalid Image Type"...
Newer definitely doesn't always mean better xP i suggest downloading another, older, version...
Sent from my SCH-I400 using XDA Premium App
Ok, DL'd Odin3, it seems to be working better...What did you mean by you recommend not flashing a full dump? Sorry, still learning this stuff...I appreciate the help...
The link is bad for the update.zip file in the *Official* Clockwork Recovery thread. I flashed using odin3 and it seemed to work but when I attempt to apply the update.zip My little android turns into a caution sign-holding android error screen. Don't know if I did something wrong with Odin or if the update.zip files I am able to find online are wrong for loading clockwork with this particular recovery image (the tar is the image, correct? lmao) Help! Please! I'll send you good vibes and spiritual cookies!
Lmao, i love you xP
I would say first trying to push all of the soft keys and see if it pops up then...
That has happened to me before, and I didn't know what was going on either xP
Try that though... If not, then yeah... Your Zip is bad... I'll upload mine
Sent from my SCH-I400 using XDA Premium App
[recovery] clockwork Mod recovery....
Download from that thread... XD
Sent from my SCH-I400 using XDA Premium App

HELP phone, yeild, computer sing! (BRICKED?)

PLEASEEE!!! help me out i tried upgrading from kies mini to froyo. I did this with success earlier in the past on my old vibrant but had it replaced to a referbished one and i tried upgrading it now.. but my vibrant was stuck at downloading the uprade on kies mini at 1% for half an hour... and the vibrant had the android shoveling yellow sign saying do not turn off target... for half an hour as well.. I knew something was wrong there because it didnt take even close to that long last time..
NOW I tried unplugging the usb wire restarting the phone in emergency mode still nothing... now all i have is a cellphone...yeild sign... computer icon showing..
PLEASE HELP!!!
Dont worry you totally didnt brick your phone. Its pretty common, can you get your phone into download mode? If you can then just odin to stock.
1.Take your battery, sim card and SD card out
2. Plug in USB Cable
3. Hold volume up/down and plug in battery (There are a few ways of doing download mode and I believe its phone specific, or if you have bootloaders installed its different as well, google around a bit...
4. Start odin and presto, your phone works again!
hey thanx... I just did that.. I never used odin but i installed odin with all the files... I believe my vibrant is hardware locked because i was trying to get into download mode for 2 hours with different techniques.. such as just volume keys and power button... taking out the battery holding volume keys then putting it back in.. but nothing put me into a downlaod mode... somehow odin still found my phone while i was still stuck under that picture...
I loaded the .pit file without the jfd image.... becuase i didnt know what window i was suppose to load the jfd image from... like pda.. or etc???
anyway so i just loaded the .pit file and clicked start it reset the phone and the phone went into restart mode and it turned on fine i checked it works fully... lol.
It makes no sense... was i suppose to load the jfd file somewhere?????
i still want to upgrade my vibrant to 2.2... but now whenever i turn on the keis mini it promps me to emergency recovery upgrade... so i tried doing that and went into download mode since now i can.. and plugged in my phone but the progress bar on my computer for upgrading never moved from 0%... its odd... am i doing something wrong?
so again i disconnected and "bricked" my vibrant again lol... went into odin followed the same steps just loading the .pit file and it reset the vibrant back to normal again lol...
Im so confused yet happy that i have my phone working but i still want my froyo... i love the fact that i can use yahoo video messaging on it with froyo and have flash and other benefits..
any advice?
Thanx again
try this...........
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
put pit in pit and tar in pda on odin
Connect it to the PC and see if ODIN recognizes it.
If it does, you are safe, flash stock.
EDIT: nvm, didn't notice the third post was yours.
Anyways, if ODIN can STILL recognize it, get the first from the link on the post above, FOLLOW INSTRUCTIONS and enjoy your again-useful phone.
I had that same issue once.
Try a JIG. And do a search, I see like 50 posts a week like this.
First.
Thank you all for taking your time to help. I have one last question... since I used Odin but it just reset my phone and I didn't flash the old firware on it..... ever since that now I tried to update my phone with kies mini and it says phone unregistered... in that place before it used to say new firmware available and showed old forward numbers/letters.
So if I use odin all the way will this resolve "unregistered device" problem?
Thanx again
Sent from my SGH-T959 using XDA App
AlexSochi8 said:
First.
Thank you all for taking your time to help. I have one last question... since I used Odin but it just reset my phone and I didn't flash the old firware on it..... ever since that now I tried to update my phone with kies mini and it says phone unregistered... in that place before it used to say new firmware available and showed old forward numbers/letters.
So if I use odin all the way will this resolve "unregistered device" problem?
Thanx again
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It should.
Sent from my GT-I9000 using XDA Premium App
Bricked
I have a similar issue, was soft bricked, Odin to stock then, while using Mini Kies to upgrade back to Froyo the phone turned off and never came back on. I cannot get any response from the phone as far as light's or sounds. Checked a few batteries and still no use. I'm curious if anybody else has had a similar experience?
so if it should solve the unregisted problem... where I put in the pda file... is it possible to put in the last froyo there so odin could flash froyo on my phone so basically i wont have to go through kies process?
odin back to 2.1 then root and then flash a 2.2 rom way better then a stock 2.2 rom
Dan_Brutal said:
Try a JIG. And do a search, I see like 50 posts a week like this.
Click to expand...
Click to collapse
I might be late to the party but I've built a jig and I can't believe how quickly this thing saved my ass...
Sent from my GT-I9000 using XDA Premium App
dsuycott said:
I might be late to the party but I've built a jig and I can't believe how quickly this thing saved my ass...
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yeah man. Jigs are the balls. Saved my ass this morning with a bad bootloader flash. I got lucky though.....
Sent from my GT-I9000 using XDA Premium App
Make sure you have the right odin files, once you have gotten back to normal just do a factory reset on your phone if that is possible. Then root, flash, and do whatever you want to do. Without your proper files for odin you'll get bricked or get something different.
How screwed am I? Odin doesn't recognize phone, vibrant aio toolkit can't adb phone into recovery or download mode. Flashing different rom screwed up during kernal phase and I stupidly rebooted phone. I CAN use a jig I bought to get into download mode but computer Odin doesn't 'see' it.
Sent from my GT-I9000 using XDA Premium App
dcboi said:
How screwed am I? Odin doesn't recognize phone, vibrant aio toolkit can't adb phone into recovery or download mode. Flashing different rom screwed up during kernal phase and I stupidly rebooted phone. I CAN use a jig I bought to get into download mode but computer Odin doesn't 'see' it.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Do you have the drivers installed on your PC?
Sent from my GT-I9000 using XDA Premium App
Dan_Brutal said:
Do you have the drivers installed on your PC?
Yes, not sure what changed but I plugged the phone in again and Odin recognized it, the file I loaded is PDA_T959UVKB5.tar.md5, the process has hung up at SetupConnection...
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA Premium App
id keep trying it odin is finicky! maybe try different usb ports
ok guys i know i aksed for a lot of help.. but i have a newly discovered problem.. when i connect my vibrant thru the original usb port to transfer files back and forth it never lets me transfer even the smallest picture image... on both internal 16gb or sd... the phone computer just constantly shows transferring animation.... i tried many times.. i even scanned the phones hard drive and sd card for errors... nothing... could it be i messed something up with kies? or thats why kies in general never went with the upgrade past 1%?
its a refurbished phone.. when i got it.. i uploaded my old pics without a problem with the same usb cable..... its weird.... i dont know what to do? what is it likely the phone itself or i messed it up with kies upgrade????
please help.. its frustrating me

Can't update after soft brick recover

So I just recovered from a softbrick using the Heimdall method. I'm stoked because I'm no longer bricked but I cannot flash anything via Odin now, even after I have re-installed my Samsung USB drivers. It always gets to SetupCS connection or something like that and just stays there. Is there something I'm missing?
What driver is on your system? Is it the fascinate or the nexus s? If you're coming back to some level of stock from a GB rom you might still have the GB (nexus s) drivers. You might have to reload the froyo fascinate drivers for odin to work.
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
So I just recovered from a softbrick using the Heimdall method. I'm stoked because I'm no longer bricked but I cannot flash anything via Odin now, even after I have re-installed my Samsung USB drivers. It always gets to SetupCS connection or something like that and just stays there. Is there something I'm missing?
Click to expand...
Click to collapse
as long as you get the yellow "com" with a number underneath the box in odin, drivers are not the issue.......try re-downloading the odin package and then flashing it again
kidserious said:
as long as you get the yellow "com" with a number underneath the box in odin, drivers are not the issue.......try re-downloading the odin package and then flashing it again
Click to expand...
Click to collapse
That was my thought as well but its doing it with 3 different Odin packages. This is where I get lost but am I supposed to put the atlas.v2.2 pit in with everything now? I'm at a loss I guess. Phone is functional on ED03 currently but I'm stuck at stock it seems...
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
That was my thought as well but its doing it with 3 different Odin packages. This is where I get lost but am I supposed to put the atlas.v2.2 pit in with everything now? I'm at a loss I guess. Phone is functional on ED03 currently but I'm stuck at stock it seems...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
the atlas 2.2 pit file goes in the "PIT" section at the same time as the tar.md5 file goes in the "PDA" section and re-partition checked......when those two files are placed in their respective slots and re-partition is checked, THEN you hit start on odin. If that doesn't work, place this file on the root of your SD card and rename it "update" but without the quotation marks lol: http://forum.xda-developers.com/attachment.php?attachmentid=556632&d=1301538910 Once you do that, boot in the stock blue recovery using the 3 finger method and select "apply SDcard/update.zip" and let me know what happens
Many thanks to you sir. I'm at work currently but ill try this out as soon as I get home.
Sent from my SCH-I500 using XDA App
By the way... what file is that? I'm just curious
kidserious said:
the atlas 2.2 pit file goes in the "PIT" section at the same time as the tar.md5 file goes in the "PDA" section and re-partition checked......when those two files are placed in their respective slots and re-partition is checked, THEN you hit start on odin. If that doesn't work, place this file on the root of your SD card and rename it "update" but without the quotation marks lol: http://forum.xda-developers.com/attachment.php?attachmentid=556632&d=1301538910 Once you do that, boot in the stock blue recovery using the 3 finger method and select "apply SDcard/update.zip" and let me know what happens
Click to expand...
Click to collapse
Alright so I just tried adding the PIT, repartition checked, and added my ODIN package, but still had the same problem. About to install the CWM All file you gave me and try that out.
*edit* Well something just happened. My SD card just got corrupted and I cant even format it now. What the hell is going on?!
*edit 2* OK so the SD card issue fixed itself. Just had to hit format a billion times. I'm now running an OTA update to my phone from Verizon as I had to go all the way back to DI09.
*edit 3* I'm now sitting on ED04 fully stock but away from my computer. I will try again once I get home later on tonight. Just out of curiousity... has anyone else other than kidserious and the other guy had this problem or have experience in dealing with it?
So checking in again. I am still freezing at "SetupConnection..." in Odin. No luck at all with flashing the CWM ALL file as "update". I'm completely out of options at this point. Help?
MR H3LLMAN said:
So checking in again. I am still freezing at "SetupConnection..." in Odin. No luck at all with flashing the CWM ALL file as "update". I'm completely out of options at this point. Help?
Click to expand...
Click to collapse
Let me rack my brain and think........I will get back to you.
RESOLVED
Alright so I finally figured out my own way around this. It was actually fairly simple and I'm a bit ashamed I didn't think to try this earlier.
Hopefully this will be of assistance for any future issues. Thanks Kidserious for your help.
*edit* So I just found some instructions for uninstalling the Heimdall driver from your phone. I'm booting up after a fresh flash of DI01 and hopefully this will work. I'm guessing that even though I'm installing the samsung usb drivers back to my computer, they arn't reaching my phone, and this may be the issue I've been facing. *pauses for a bit to test theory* Yep. That was all it was. Sorry for taking up so much room on here... just FYI to everyone though. If you soft brick and recover via Heimdall you HAVE TO UNINSTALL THE HEIMDALL DRIVER OR NOTHING WILL WORK.
FML. So it didnt work as I had planed. After I flashed my edify rom I samsung bootlooped. And Odin still isnt working for me.
I'm giving up for tonight. Functioning on DI01 stock ): at least it works...
Alright so I'm fairly certain I've narrowed it down to one fix but I seem not to be able to fix it. I need to install the samsunflg husband drover back to my phone and uninstall the heimdall driver. I've tried it twice and or hasn't worked either time
Sent from my SCH-I500 using XDA App
---actually resolved----
Sorry for spamming this thread everyone, even though I've really been the only person posting in it anyways.
I have found my fix. So I was never able to fully uninstall the Heimdall drivers so Odin wouldn't recognize my phone and would hang at "Initalization."
So I took a weird strategy and actually purposely soft bricked my phone. Scary to do but the outcome was well worth it. Here is what I did.
1.) Puropsely soft bricked phone
2.) Put it in to download mode
3.) Went to device manager
4.) Contrary from Heimdall Uninstall instructions phone will now show up under the general usb devices areas. Find this area, expand, and right click on Samsung Composite USB Device.
5.) Go through the options of manually picking the usb driver you want to use.
6.) Install chosen standard samsung USB driver. You may get many options in the list but pick the Digitally Certified one.
7.) I didnt unplug the phone after I flashed the new driver so open up Odin and flash your DI01 Stock Recovery with Atlas v2.2 PIT and Repartition checked.
8.) Once finished phone will be on DI09 fully bloated stock and should work with Odin for any further flashes.
*edit* It appears as if you need to flash the samsung driver to phone evrytime you want to flash something via Odin.

[Q] Boot Loop of sorrow

I need Major help with my phone. So here's the run down.
Starting on a Tuesday my phone started acting funny, it would get to the AT&T logo and stop, but then if I removed the battery and hold down the power button for roughly 20 seconds and start it up it would come on without any problems that I could see. Through the week it got worse, and by that I mean that it would restart on it's own, randomly. By that Sunday pulling the battery and holding the power button no longer did anything and from what I understand it is stuck in a boot loop.
I should have started by asking all of you, but unfortunately for me I tried fixing it myself by searching for the answers.
This is where my phone sits. It was rooted, but there is no back up. I can get to the Android system recovery. I foolishly did a reset and cleared my phone (I have all of my info and pics backed up so I'm not worried about that). My computer does not recognize my phone unless I go into the ADB setting in recovery mode and as far as I can tell the computer just knows that something is connected through USB but can't quite tell what it is. Kies has been installed on said computer recently so I have the newest Samsung drivers. I have a 32 gb sd card for my phone if that helps any. I forgot to mention that my phone is running Version 4.3 of the S4 software.
I am a total noob when it comes to these types of problems so please help me.
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Re:
jd1639 said:
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Bulk like Hulk said:
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Click to expand...
Click to collapse
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm running Windows 7. I'll try that when I get home. I'll let you know what happens.
jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry I haven't logged in for a while. This worked very well, thank you.:good:

Categories

Resources