Background is, I was flashing JAC's latest kernel onto my phone, which I had done twice before. Unfortunately, ODIN was getting stuck at zimage. After trying a few times, I decided to go back to the version of the kernel I was running previously, which I knew worked. I tried to flash the kernel but odin kept getting stuck on zimage again.
I tried restarting the computer, battery pulls on the phone, different usb ports and nothing has worked.
In desperation I tried to flash the stock firmware back, but ODIN gets stuck at cache.rfs.
Did I brick my phone?
Which version of windows are you using? Try from a different computer.
the3dman13 said:
Which version of windows are you using? Try from a different computer.
Click to expand...
Click to collapse
Windows 7 32bit. I've also tried a computer running xp home.
My main pc runs windows 7 64 bit, but odin doesn't work on it, even in compatibility mode.
The phone is f'ed. Im going into the tmo store this morning, I hope they dont give me a hard time.
ArbitrageMan said:
My main pc runs windows 7 64 bit, but odin doesn't work on it, even in compatibility mode.
Click to expand...
Click to collapse
BS! Heh, I restored my phone using ODIN flasher. I have windows 7 64 bit. I don't have to do anything special, just followed directions and it worked. Make sure you have 64 bit Samsung Drivers.
zaduma said:
BS! Heh, I restored my phone using ODIN flasher. I have windows 7 64 bit. I don't have to do anything special, just followed directions and it worked. Make sure you have 64 bit Samsung Drivers.
Click to expand...
Click to collapse
Done. The phone is detected by odin in 7 - 64, but when I try to flash, odin throws up a couple of messages in chinese and then sits there doing nothing. It never starts the flashing process.
hey did you fix your phone...im having the same issue
You guys try flashing anything via clockwork recently? There are recovery images for stock inside the odin thread from jac and stock I images for a kernel in his kernel thread... That's if you can even get into recovery now.....
Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...
on the same boat any other solutions
have you guys tried the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Here is another good thread to check out.
http://forum.xda-developers.com/showthread.php?t=1013967
Flag eugenes froyo that doesn't brick. Look it up it will fix it
Sent from my SCH-I500 using XDA App
No idea if this will help, but make sure you are using a later version of Odin (1.7 or above).
Also might try flashing with Heimdall. Works very well in my experience.
Related
So just so I could see how the whole process worked I decided to SBF. Well, it seems to have failed. It gets to a point in the flash process where it says "Switching phone to BP pass through". It fails on this step at 99% then says FAIL on the process. So now the only way to turn it off is to pull the battery. As soon as I put the battery back in it goes to the bootloader screen and says "Code Corrupt" but down on the other part it says "OK to Program"
anyone know anything I can try? Different computer perhaps?
can you get into recovery mode?
dekend said:
can you get into recovery mode?
Click to expand...
Click to collapse
Nope, only to the bootloader.
what OS are you using? 32bit?
Have you tried another comp yet?
possible driver corruption.
I'm assuming you've tried to reflash it again. In the past back flashing Moto flip phones I've had RSD Lite fail like that also. Just took flashing it again until it finally took and was good to go. Heck I remember I was flashing a v3c to Telus software and the darn power went out in the middle of it. Took me about 10 flashes after that to get it to take as something got corrupted because the power went out in the middle of the flash. Kinda why I always flash with my laptop nowdays....lol.
dekend said:
what OS are you using? 32bit?
Have you tried another comp yet?
possible driver corruption.
Click to expand...
Click to collapse
I was using 64bit Windows 7, but I was using it in VMware. I've got 32bit XP up and running on a new machine now (not virtual) and I'm about to try with that.
Never had a problem flashing with VMs before but that may be the problem. Who knows.
mrnosox said:
I was using 64bit Windows 7, but I was using it in VMware. I've got 32bit XP up and running on a new machine now (not virtual) and I'm about to try with that.
Never had a problem flashing with VMs before but that may be the problem. Who knows.
Click to expand...
Click to collapse
VM is definitely the problem -- I had the same issue with my D1. I think it's not loading the drivers correctly when the USB mode switches between ADB Flash interface and whetever comes next. I was able to re-SBF it using native XP 32-bit, so hopefully you can, too.
The same exact thing happened to me. Turned out the problem was that i was using an old version of RSD Lite. You NEED 4.7 for it to flash correctly. I was using 4.6. As soon as I updated, I plugged in via usb while in "Code Corrupt" bootloader and reflashed. Worked fine after that.
Sent from my DROIDX using XDA App
btdownloads7 said:
VM is definitely the problem -- I had the same issue with my D1. I think it's not loading the drivers correctly when the USB mode switches between ADB Flash interface and whetever comes next. I was able to re-SBF it using native XP 32-bit, so hopefully you can, too.
Click to expand...
Click to collapse
Yep, I loaded XP on my MBP in a bootcamp parition and it flashed the first time. It's Alive!
mrnosox said:
Yep, I loaded XP on my MBP in a bootcamp parition and it flashed the first time. It's Alive!
Click to expand...
Click to collapse
Nice, glad to hear you got it back going again.
I have a question...ok my phone is rooted used easy root....ok then I download boot strap now I want go back top stock what I have to do
Sent from my DROIDX using XDA App
If you still want to use some sort of virtual software on your mac, I recommend Parallels. I have the 5.0 version and running XP on the newer generation MBP.
SBF works like a charm. I don't use Boot Camp simply because I want access to both OS's at the same time.
If you can setup a Linux box, I'd use sbf_flash. Sooooo much easier.
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.
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.
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.
Hey guys I installed the rom Super.Fast&LolliFamous™ (don't remember the exact version, but i can find this out), but a few days ago my phone started bugging out. It started lagging, vibrating and replaying sounds when going into lags, forcing me to reboot it. this helped the first time but an hour later it started again and now i can't boot it properly at all. I am able to get it into download mode and recovery with luck and a few tricks, but odin wont recognize the phone when connected to a pc (tried with 2 pc's and 6 different usb ports). I was able to flash another rom, but this did not fix the problem a bit (Alliance 2.2). With the same problem still there I tried flashing the stock rom over Odin, but as mentioned Odin won't recognize the phone. I have tried Installing/uninstalling Kies as well as Installing/uninstalling the samsung drivers on both pc's. Any help would be very appreciated!
croulder said:
Hey guys I installed the rom Super.Fast&LolliFamous™ (don't remember the exact version, but i can find this out), but a few days ago my phone started bugging out. It started lagging, vibrating and replaying sounds when going into lags, forcing me to reboot it. this helped the first time but an hour later it started again and now i can't boot it properly at all. I am able to get it into download mode and recovery with luck and a few tricks, but odin wont recognize the phone when connected to a pc (tried with 2 pc's and 6 different usb ports). I was able to flash another rom, but this did not fix the problem a bit (Alliance 2.2). With the same problem still there I tried flashing the stock rom over Odin, but as mentioned Odin won't recognize the phone. I have tried Installing/uninstalling Kies as well as Installing/uninstalling the samsung drivers on both pc's. Any help would be very appreciated!
Click to expand...
Click to collapse
try to remove the drivers, and let windows find the drivers.
i never installed the drivers myself, windows does it for me
I already tried this...
I have tried connecting my old Galaxy S2 to see if it was the pc which was the problem. Odin recognized my old S2, but not my Note 4. Any ideas? Can i flash something in recovery which makes Odin able to register the Note 4? Help is greatly appreciated!
try a different version of odin, remember to run it as admin, and check the cable
I have already tried all this...
Damn you still have not fixed this? Maybe try another computer?
Sent from my SM-N910F using XDA Free mobile app
No I miss my note 4 I have tried 2 different PCs (see my first post) I believe i have tried anything I can by playing with Odin
I am able to get into recovery though. Does anybody have an idea what i could flash in recovery that might fix the problem? Thanks in advance
croulder said:
I am able to get into recovery though. Does anybody have an idea what i could flash in recovery that might fix the problem? Thanks in advance
Click to expand...
Click to collapse
Yeah man! Download cyanogenmod 12.1 or another rom and flash it! Then you should try it via Odin again
Sent from my SM-N910F using XDA Free mobile app
I already tried with Alliance 2.2. Would it be worth a try with Cyanogenmod 12.1? Link to the exact version? The newest nightly? Thanks!
When this has happened to me in the past Samsung's recovery software does the trick. Give it a try.
Sent from my SM-N910T using XDA Premium HD app
Thanks! Where can i install this? Do you mean the samsung recovery which you can boot into?
I got it to boot for some seconds but then it just turned off. I believe the battery to be the problem. Does anybody know how to test this? Else i'll just google
Have you tried install stock ROM ( or other ) via ADB sideload from recovery?