Ok here's what happened. When I flashed Nero v4, I rebooted into recovery and flAshed 2.2 stock kernel and jk6 modem without knowing that voodoo has been enabled. So I can get into recovery, but only the stock recovery not clock work. Also I'm using Odin v1.7 and Odin v1.00. Also when I put my phone in download mode Odin does not recognize it. By the way it sometimes recognizes it on the samsung boot screen. So what's the problem with this thing? I am SCARED!!!!!!
make sure ur fone is in download mode then unplug it from the usb and restart odin, then plug it back in.. if you can get to stock recovery then try using adb or something to install the clockwork recovery update.zip to your phone
This may be something you have done, but just in case. Do you have kies installed? Or at the very least the drivers?
I have also had times (today as a matter of fact) where I put it in download mode but the PC didnt make the eject/connect noise. I had to restart the phone again and put it in download mode again. (if you only unplug-plug in it may work, but its 50/50 chance itl just freak out)
I keep a copy of kies on my SDcard just for situations like today.
Ok seeing as I had this problem a few weeks ago ill just share my solution, in the case of windows 7. If you have windows 7 right click on odin and click compatability, then roll it back to windows xp sp 3. Next run odin in administrator mode. Next, when you power down your phone, connect the usb cable first, then quickly hold volume up and down, and don't release them. don't worry if it doesn't connect, because I usually have to do this 4or 5 times. Run your pit and ROM and click start, and its my experience that letting go of volume up and down will disconnect odin. I hope this was helpful just trying to be a productive member of the community.
Odin was able to find my vibrant, but when i press "start" the process gets stuck on "analyzing files..." and nothing happens. By the way, I'm trying to go back to stock ji6 from Axura. I'm new at this. I was able to root my vibrant and get Axura on it, but i need to do a warranty exchange on my phone, so have to go back to stock because I don't think they will cover it otherwise. If there is an easier way to go back to Android 2.1 ji6, please let me know. So far Odin is not processing it...please help
I was had similar problems as well and it turned out fine. See this link at reply #3 (mine). The final issue for me to overcome was to make sure I had the proper .tar and .pit files as well as the updated samsung drivers. I include a link to a file called all_in_one that should be helpful.
http://forum.xda-developers.com/showthread.php?p=10387163#post10387163
zedgar said:
I was had similar problems as well and it turned out fine. See this link at reply #3 (mine). The final issue for me to overcome was to make sure I had the proper .tar and .pit files as well as the updated samsung drivers. I include a link to a file called all_in_one that should be helpful.
http://forum.xda-developers.com/showthread.php?p=10387163#post10387163
Click to expand...
Click to collapse
I tried it everything that u posted and I still get windows could not recognize the device. I tried on both a vista machine and a xp machine. Nothing works!!!! Any ideas?
helikido said:
I tried it everything that u posted and I still get windows could not recognize the device. I tried on both a vista machine and a xp machine. Nothing works!!!! Any ideas?
Click to expand...
Click to collapse
Guys is there a way that I can adb clock work recovery and flash my voodoo soft bricked vibrant?
helikido said:
Guys is there a way that I can adb clock work recovery and flash my voodoo soft bricked vibrant?
Click to expand...
Click to collapse
Have you tried "adb reboot clockwork recovery" I remember when I had my first brick thats how I did it have you tried using odin 1.3 thats what I use and I have windows 7 64bit and it works all the time do you have the samsung drivers sorry I have to ask ?
Sent from my SGH-T959 using XDA App
AustinKnight45 said:
Have you tried "adb reboot clockwork recovery" I remember when I had my first brick thats how I did it have you tried using odin 1.3 thats what I use and I have windows 7 64bit and it works all the time do you have the samsung drivers sorry I have to ask ?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
well I'm using Odin v1.7. Also I have the Samsung drivers that were posted on this thread by a reply. Also how can i flash clockwork recovery through adb and what files do i need to do that.
helikido said:
well I'm using Odin v1.7. Also I have the Samsung drivers that were posted on this thread by a reply. Also how can i flash clockwork recovery through adb and what files do i need to do that.
Click to expand...
Click to collapse
Ok I dont know how to flash clockwork through adb have gone to the clickwirk recovery thread and checked there? Why can't you just select re install packages if you had clockwork before then thats all you do to get into it ?
Sent from my SGH-T959 using XDA App
AustinKnight45 said:
Ok I dont know how to flash clockwork through adb have gone to the clickwirk recovery thread and checked there? Why can't you just select re install packages if you had clockwork before then thats all you do to get into it ?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
because everytime i select that it reboots and doesn't take me to clockwork.
Related
Alright heres the catch. i installed nero v4. with voodoo enable (wich i forgot to disable), i flashed a stock 2.2 kernel on my phone and jk6 modem. Now my phone is soft bricked. Now i can get to the stock 2.2 recovery but when i select "reinstall packages" phone just reboots and does not go to cmw. It also says cant mount to "E". Also whenever i connect the phone to odin in download mode, odin does not recognize it but does if the phone is not in download mode and is just stuck at the samsung screen. Can anyone help me?
Is Nero still on ur SD card? Reflash through CWR maybe.
Sent from THE Vibrant......
Sorry just reread ur post. Try using a different usb port.
Sent from THE Vibrant......
have you figured it out?? what verstion of odin are you using??
kooksta said:
have you figured it out?? what verstion of odin are you using??
Click to expand...
Click to collapse
no i havnt figured it out. im using v1.7 odin 3 and i am getting nothin. i really need my phone.
Update the samsung drivers?
Sent from my SGH-T959 using XDA App
I had to reset my laptop one time when my drivers were failing it might help not sure though
i finally got odin to recognize my phone. what i did is got a windows 7 pc. installed the samsung drivers and put the phone in download mode and odin recognized it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! finally, my beloved phone is working. by the way im still flashing nero v5 in this, bricking doesn't scare me,lololol.
I have tried to update manually but cant. I have downloaded the file from samsung, put on root of card as update.zip and tried to install from clockwork. Is this the wrong way to do it.
I am on all stock and have clockwork installed. I downloaded from the link that has been provided from samsung It says E:Error in /sdcard/update.zip
Firmware version-2.1-update1
Build Number-SPH-D700 ECLAIR.DI18
So is there something I am doing wrong?
If you're using clockwork, you aren't on stock. Last resort is to use the flash utility that Samsung provided. It completely wipes your phone (not your sd card).
nubsors said:
If you're using clockwork, you aren't on stock. Last resort is to use the flash utility that Samsung provided. It completely wipes your phone (not your sd card).
Click to expand...
Click to collapse
Is there a way to remove clockwork besides going back to stock? Also since I do have clockwork installed, will I not get the ota update to work correctly?
I can tell you what I know.
1) The official OTA update does not work with non-stock roms. In your case, your rom became non-stock once you installed CWR.
2) The flash utility provided by samsung will take any epic and clear it of user data and the existing rom and then flashes the 2.2.1 official rom. Your SD card will be untouched, at least mine was.
3) You can always re-root after you've flashed the official release. Do a search in this forum and you can find threads that explain how.
Good luck sir.
Just go get the cwm flashable pre-rooted eb13 rom that dameon87 posted in the dev section. There's also a link to it in the wiki.
DiGi760 said:
Just go get the cwm flashable pre-rooted eb13 rom that dameon87 posted in the dev section. There's also a link to it in the wiki.
Click to expand...
Click to collapse
Any difference between that and the one you can download from samsung or what you would get from OTA?
mynewepic10 said:
Any difference between that and the one you can download from samsung or what you would get from OTA?
Click to expand...
Click to collapse
Need to know too.
DiGi760 said:
Just go get the cwm flashable pre-rooted eb13 rom that dameon87 posted in the dev section. There's also a link to it in the wiki.
Click to expand...
Click to collapse
That one did not work. Do I need to try to get the one that is not signed. I dowloaded the signed one and it did not work. After the install it tried to boot up, but went to the samsung screen and then into the official factory restore mode and tried to reboot and stuck on samsung screen.
Use the unsigned one. The only difference betwen the flashable and the one from samsung is the flashable is deodexed.
Sent from my SPH-D700 using Tapatalk
s9ortner said:
Use the unsigned one. The only difference betwen the flashable and the one from samsung is the flashable is deodexed.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks doing that now.
I had the same problem. Will try odin method when I get home, but I doubt that will work. Didn't work with the developers froyo.
Sent from my SPH-D700 using XDA App
I can't get the manual to work - mine is rooted and rommed, but my husband's is stock.
I have downloaded direct from Samsung 3 times. Once loaded on computer and opened, the Eula doesn't even have the Next button which is needed to proceed.
So strange, guess he will wait for the OTA and drain his battery at an inconvenient time!!
s9ortner said:
Use the unsigned one. The only difference betwen the flashable and the one from samsung is the flashable is deodexed.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I tried both of them and neither one of them worked.
nmoreman said:
I can't get the manual to work - mine is rooted and rommed, but my husband's is stock.
I have downloaded direct from Samsung 3 times. Once loaded on computer and opened, the Eula doesn't even have the Next button which is needed to proceed.
So strange, guess he will wait for the OTA and drain his battery at an inconvenient time!!
Click to expand...
Click to collapse
I'm getting the same problem with the samsung update software. I click yes to accept
And there is nothing that says next, just exit. I am getting errors using odin too. My computer
will see my phone just fine.....until I put it in download mode and try to connect with odin.
I keep trying to repair modem and restart computer to no avail. Its just weird how it all changes for the worse in DL mode. I don't know what to do....
Sent from my epic that is stuck forever on 2.1
funeralplanner said:
I'm getting the same problem with the samsung update software. I click yes to accept
And there is nothing that says next, just exit. I am getting errors using odin too. My computer
will see my phone just fine.....until I put it in download mode and try to connect with odin.
I keep trying to repair modem and restart computer to no avail. Its just weird how it all changes for the worse in DL mode. I don't know what to do....
Sent from my epic that is stuck forever on 2.1
Click to expand...
Click to collapse
If you are using odin try this.
Start odin on your PC first and have it up.
Put phone into download mode
Plug in your phone via usb and see if that helps.
It already sounds like you have the samsung drivers installed, but check to make sure.
mynewepic10 said:
If you are using odin try this.
Start odin on your PC first and have it up.
Put phone into download mode
Plug in your phone via usb and see if that helps.
It already sounds like you have the samsung drivers installed, but check to make sure.
Click to expand...
Click to collapse
Well I gave that a try. No go. I have tried everything I know. Two different computers, both xp. I can't even use the samsung utility because I keep getting the cant connect to usb. When it isn't in download mode i can connect to the computer, both computers just fine. It will tell me what phone I have and all. I just don't get it. Maybe I will just delete driver and install again. Is it a phone problem?
funeralplanner said:
Well I gave that a try. No go. I have tried everything I know. Two different computers, both xp. I can't even use the samsung utility because I keep getting the cant connect to usb. When it isn't in download mode i can connect to the computer, both computers just fine. It will tell me what phone I have and all. I just don't get it. Maybe I will just delete driver and install again. Is it a phone problem?
Click to expand...
Click to collapse
I have used a different version of odin with no issues at all. I have never used this one before.
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
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
futuralabs87 said:
So I've been messing around with android phones for a while now and I'm stuck. I was on the oxygen 2.1.6 Rom then decided to make a back up. However instead of going into CWR it just went into fast boot. When I go into recovery it just says fast boot mode no reboot or recovery img. I tried to odin back to stock like I usually do but adb wont recognize my device like it usually does. Please don't tell me I'm bricked and that I messed up bad. Any help would be appreciated. Thanks in advance.
I tried reinstalling drivers etc etc. Somebody help me lol
Click to expand...
Click to collapse
It sounds like you flashed a bad recovery. Download a new recovery , boot into fastboot, and
Code:
fastboot flash recovery yourrecoveryfile.img
adb wont recognize my device so how do I flash a new recovery
futuralabs87 said:
adb wont recognize my device so how do I flash a new recovery
Click to expand...
Click to collapse
Adb only works when the phone is booted normally, provided usb debugging is on.
Use fastboot. If you want to make sure it's working, boot into fastboot mode and
Code:
fastboot devices
If it's working, you will see your serial number.
If the other options can't help you get your problem solved try Odin.
www.samfirmware.com
get the right files for your device and Odin program itself. There are tutorials on here how to use it.
sorry I was being an idiot. I tried fastboot and it showed nothing connected. When I flashed a recovery it just hung waiting for device. I have all the drivers loaded on the computer but my device is still unknown and wont be recognized. I have all the odin files and I have used odin before. This sucks
btw appreciate the help guys
futuralabs87 said:
btw appreciate the help guys
Click to expand...
Click to collapse
Try installing pdanet, that will install all the drivers you need for fastboot and Odin.
Sent from my Nexus S using XDA Premium App
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
dreamsforgotten said:
Have you tried to run shabbys 1 click root to get the recovery in place? Assuming your on sprint that is
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Sorry I didn't say anything, it was a burp
Sent from my Nexus S 4G using Tapatalk
shabbypenguin said:
my one click works on both versions, as all it does it just gets you root. if you want cwm then use rom manager afterwards.
but for his problem no it relies on adb and fastboot
Click to expand...
Click to collapse
Maybe not, but it does include some handy files. ;-)
Download and unzip Shabby's OneClickRoot
Install pdanet. (See the readme for which one.)
Reboot your computer.
Then try using his version of fastboot.
I'm assuming you are in fastboot mode (it will say so) and that you're using the usb cable that came with the phone.
I will give it a go now I do have PDA installed too
No luck boys just bought a sensation but still wanna fix my nexus s
Sent from my HTC Sensation 4G using XDA Premium App
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.