Odin won't recognize soft bricked vibrant - Vibrant Q&A, Help & Troubleshooting

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!!!!!!
Btw I'm running on xp sp3 and can get Odin to recognize my vibrant on the samsung screen, but if I try to flash anything Odin stops at setupconnection. So do i have a software problem or USB cable needs replcement or another computer? I've already tried vista and xp no luck? Also I could get into stock recovery but if I press reinstall packages, phone will just reboot instead of going to clockwork recovery. For all I know my phone is 100% restorable but there's something going on. Someone please help!!

You need to Odin back to JFD (original 2.1 stock). Find it in the Vibrant Bible. Also read Odin instructions in the bible.
Turn on Odin before you plus USB into phone. When you get into Download mode (picture of Yellow Droid with shovel in Triangle) then Odin will recognize the COM port (i.e Com 5 ). When you see COM light up then you know Odin is ready to go.
Dont be scared, the vibrant is almost impossible to brick. You will be up and running in no time.

You may be able to avoid ODIN by doing this...
Since you can into the stock recovery screen, trying selecting "Reinstall packages" TWICE (once, then again after reboot) from the stock recovery screen to bring up clockwork. This is normal for my phone, it won't display CWM until I've done told it to show twice and don't know why. Once in CWM, either flash a kernel or entire ROM with voodoo support that you've previous stored on your internal SD. Don't worry, you'll be ok soon enough.

Related

Odin won't find Bricked Phone

So my friend who is completely clueless about phones, tried flashing his Vibrant and bricked it. So when you turn it on, it will go through all the boot up screens and then the screen will go blank and the buttons will only light up. I can get into both recovery mode which is the stock Samsung recovery, and the download mode.
Problem is Odin does not reconize the phone in download mode, only in recovery mode and when I try to flash it back to stock in recovery mode, Odin never goes past the first step, just says File Analysis .... am I doing something wrong? I have Odin3 V1.3
try using Odin 1.7, it will only work in Download mode. You may need to install the Samsung USB drivers
Had the exact same problem this past week. Zylograth gave me the same advice. Cleared my problem rite up.. and I was using the poopoo version of Odin 1.0 just make sure u have the correct drivers
Sent from my SGH-T959 using XDA App

[Q] No download mode?

I recently used Odin to update to froyo 2.2 from my eclair 2.1, and it "pass"ed but now my phone goes into recovery mode. Boot screen then recovery, even when its off and begins charging goes straight to recovery.
At recovery it says:
"update media, please wait
E: Cant mount /dev/block/mmcblk0p1
(Invalid argument)
E;copy_dbdata_media: Cant mount SDCARD:
your storage not prepared yet. please usee UI menu for format and reboot"
But UI menu doesnt work, doesnt let me select anything, and download mode wont load so Odin gets stuck at "Setup Connection".
Help?
Thanks!
- try different versions of Odin's this is the most common issue.
- Make sure your using the correct Eclair 2.1 files the ones by Eugene the unbrickable one.
Mostly, try a different ODIN, and the one that works, don't switch from it.
Odin is the only thing keeping my phone good as new, and i dont need any updates on that.
xrider is correct, I would recommend the 1.7 Odin. You can then Odin back by first flashing Eugenes Froyo that does not brick, then back to JFD2.1
you can get all you need in the Stickies
From there you can root and then flash away
good luck,
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Dark619Cloud said:
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Click to expand...
Click to collapse
Wait, if you can't get into Download mode, then how are you getting COM6 on ODIN?
I have no idea. Phone just sits in recovery, I plug in USB and it says
<ID:0/006> Added!!
But when I try flashing anything, it stays at SetupConnection.
When I WAS able to get into download mode, it was COM8.
Wait for more replies, idk the solution. Sorry
Maybe new version of odin?
I really appreciate your help though.
I think it's just bricked. The froyo which I had updated to was probably faulty, causing this to occur. I mean, even the recovery menu is messed up. Up and down are inverted, and power button does nothing. Phone doesn't show charging screen(well it does for a second then go straight to recovery).
I'll just call T-mobile tomorrow. I wouldn't get charged right? I tried updating to THEIR firmware, had they made it OTA this wouldn't have occurred, right?
The fact it sees com 6 or com8 or com 4 really isn't important, sometime mine say com2 sometimes it say 6......... this is unimportant.
Follow this ...this should work, the only other thing I can think of is to get into factory recovery and wipe, cache, and memory, go into advanced and wipe the dalvik, then back to Odin and perform the following:
1. Odin 1.3 or higher I use 1.7 but not real important
2. Have the original JFD Vibrant rom
3. You will need the .pit file (this is for mapping)
4. You will Eugene froyo that does not brick rom.
The order is as follows:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! You will have flashed back to the original software. From there, you can do anything !!!
Next root the phone if you are confused about this go to youtube and look up the video by unlocker.com they do a great job showing how it is done.
After all this you can now flash a new rom.
The reason he's getting a COM port without being in D/L mode is because of the secondary bootloader in the sbl.bin. You may just be able to flash JI6.tar without a pit file and get past the Setup Connection
Whoa, nice feedback.
Downloading both Eugenes "Froyo that does not brick" and the JI6.tar.
Will try both methods and reedit my post.
Thanks a lot.
I can't press "Thanks" more than 5 times a day...
UPDATE:
Eh still nothing...Odin gets stuck at SetupConnection.
I believe this will persist until I find a way into download mode. Odin recognizes phone, hence the COM6, but doesn't fully connect since it does not go beyond SetupConnection. The recovery menu also isn't functioning properly, since I can't select anything.
Losing patience with this phone...
I called T-mobile and their sending in a new one.
Told them I was updating and this happened. Do you think I'll get charged?
Well, while you still got time with it...try a different version of ODIN and see if that works... 1.0, 1.3 or 1.7 dunno if there are more
All three versions get stuck at SetupConnection.
I looked into making a JIG, but I only have one USB cord and don't wanna go through the hassle. A JIG would put my phone into download mode, right? Even though it's not really bricked, just completely messed up.
Just now I was messing around with phone, and I got to a different screen!
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
(and some other stuff like that)
Then " POWER RESET OR UNKOWN UPLOAD MODE"
It shows up as COM7 in ODIN But still stuck at SetupCOnnection...grrr
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Dark619Cloud said:
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Click to expand...
Click to collapse
if you look at ODIN while you plug the phone in with that screen you'll notice it giving you a COM port....weird...but you can still ODIN the phone while on that screen. Flash back to JFD from there.
Yeah I know ODIN should recognize it, because it happened before and it did. But this time it's not. I tried different versions of ODIN as well.
tsk tsk ;P lol
u fixed it? or it remains broken ?
I did fix it, partially. It loaded and everything, but sound wasn't working, and volume rocker was inverted, I guess the rom I flashed was corrupted. So I did "adb reboot download" which took me to download mode to go back to JFD stock, and I did ODIN and everything but it stayed at SetupConnection again. I removed battery to put in download mode manually, and now it's bricked. PHONE /!\ PC. PC doesn't recognize it, and I tried every combo to get into download mode.
So no, it's not fixed.

[Q] ! Accidentally formatted boot Vibrant !

I was on Miui rom, but I wanted to go and try Simpley Honey, so I went to CWM and wiped everything like it said, and I accidently formated the boot too. Is this why I'm stuck at the screen? i tried everything` Odin,Heimdall,Aio toolbox and all drivers for vibrant,but pc dont recognize my phone and there are only show <unknown device>
PLEASEEEEEE HELP TO FIX MY VIBRANT
Couple of things to try.
First, if you want to Odin, then I usggest going into your device manager on your PC and uninstalling your drivers. Then reinstall them manually of with the Toolbox.
Second, (Rule #1-Always make a back up)- Hopefully you made a nandroid back up of your MIUI that you were on. If so, you should be able to restore that and then wipe properly.
Third, if you can get into Recovery and you don't have a back up, then try to flash a ROM (2.3.x or higher since you were on MIUI) and see if that gets you back up and running.
Pretty sure that if you wiped Boot.img your phone is still recoverable. It isn't like you wiped out the bootloader or anything. Those are not touchable from CWR, so don't fret that part.
i uninstalled all drivers then installed again but odin dont recognize my phone(unknown device) in download mode,and i can not acces to CWM(((
do uninstall those drivers again and just download and install samsung kies mini it will automatically recognize and install drivers for you.. hope this will help you...JFD by odin will be the best way after that...
NB:for future reference---
always remember two things before flashing any rom...
** do nandroid backup
** get back to stock by odin then proceed any rom you want...
Haha, I did this before (about 2 weeks ago). I just placed it in download mode, then flashed back to stock using ODIN.
I tried everything but pc dont recognize my vibrant(((
dont freak out man, like everybody has said you did not brick your phone. when you click format boot, you only wipe the boot media (the startup image/video). you're boot-loaders are still in tact. this is all about getting your pc to recognize your phone. try to connect on another computer and try different variations of connecting to the computers, try a different usb port. Once I thought I bricked my vibrant as in I couldn't get into download mode or anything. I stupidly unplugged it while it was installing factory.rfs on odin, I thought it was stuck. Nothing would come up with any button combo pressed. then nine hours later and a change of usb ports, I got it into download mode an odined to stock.
but ive already tried it in many computers and usb ports,but still no success(((

[Q] So what kind of brick do I have here?

I was in the process of flashing back to GB in ODIN when it froze on flashing the Modem. Now the phone does nothing. Black screen. Plug USB in and computer doesn't know its there, Download mode will not work, nothing works.
Will a usb jig get it back into download mode so I can try flashing again or is this thing straight gone?
Thanks.
Yes, a USB jig will work.
MultipleMonomials said:
Yes, a USB jig will work.
Click to expand...
Click to collapse
Well I built one and tried it... No go. Nothing happened. Blank screen.
BTW the battery was fully charged right before it bricked so I know the battery isnt dead.
Was the phone on when you plugged it in?
I fixed it. Had to do the Unbrickable Mod. Was a pain in the butt getting the contact pads jumped. Once I got it I was able to get into download mode with the supplied programs and flash back to stock.
Nicely done.
Well I jinxed myself. I went to flash a new ROM and now im stuck on the Samsung Logo. Using the previous method does no good. Just stuck on Sammy logo. I found a different Heimdall One-Click now but it fails to flash Modem and now it vibrates 3 times when the sammy logo is shown.. over and over... so its in a boot loop I take it? If I 3 finger it it shows the stock recovery but I am unable to move up or down in recovery. It just stays on the reboot device selection.. im able to select that with the menu softkey thats it. The vol up and down and power buttons do not respond in recover. Updating the Modem is what started this whole mess for me. When I originally was flashing this the other day ODIN froze on flashing Modem, that put me in a hard brick state requiring me to do the Unbrickable Mod. I got it out of that with ED05 Heimdall Once-Click but since then I have not been able to get it out of this soft brick. My galaxy just wont let me win. :-(
Have you tried using One-Click Resurrector?
MultipleMonomials said:
Have you tried using One-Click Resurrector?
Click to expand...
Click to collapse
Ya, thats how I get it into Download Mode... its the Only way I can get it into download mode actually.
Both Odin and Heimdall are having trouble flashing the phone in windows. Both recognize the phone and connect but will not flash anything. They just sit at uploading PIT/Setting Partitions.
The ED05 Heimdall One-Click in linux flashes the phone with success's accross the board but the phone just sits there on the samsung logo... no vibrating, no recovery, and unable to charge the battery. If I use the EH03 Heimdall One-Click in linux it will flash all the way til it gets to flashing Modem but then fails and the phone is stuck in bootloop on the samsung logo vibrating 3 times over and over. It can also get into the stock recovery but im unable to move up or down the menu. Volume buttons have no effect. The phone will now charge though. Full battery as of right now.
I tried using Odin and Heimdall on another windows computer and they will not move past setting Partitons/uploading PIT either. SO I know there isnt a conflict with my computer.
I would like to try a manual flash in Heimdall Front-End in linux but I have no clue how to install it in Linux. I hate that command line stuff. I guess I have to figure it out though if Im going to try it.
OK, success!
I am now back to stock. I was able to run Heimdall in linux and flash CWM recovery. I was able to get into the recovery and make selections in recovery with the volume buttons. I selected reboot in download. I went to Odin and tried flashing a stock EH03 rom and it worked.... I think the reason I couldnt do that before was because i was holding the power button down to keep it in download mode since that is what is required when in download mode via the unbrickable mod.
The windows based programs must not have liked me holding that power button. Weird. Anyways its working.. now on to getting this thing updated.
im having a similar issue, i can get into cwm, can use download, but when i try using Odin for the stock eh03 it instantly says all threads completed succeeded 0 failed 0. when i reboot in cwm it just takes me to samsung logo wont go any further
Try heimdall.
Ya Heimdall in linux will surely give you a win.

Phone Not Starting After Flashing new CWM

Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
jpasher said:
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
Click to expand...
Click to collapse
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Epications said:
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Click to expand...
Click to collapse
Many usb cables will work just fine. The original cables are known to be of good quality. Odin3 v1.85 is recommended for this phone, although any version of Odin should work.
Did you open Odin on the desktop before putting the phone into download mode? Sometimes the problem is as simple as wrong sequence.
If you have a USB jig, use that to put the phone into download mode. Then connect it to the computer while Odin is open on the desktop.
Make sure you have the correct driver installed. You should have "SAMSUNG USB driver for mobile phones" in your add/remove programs dialog in windows. If not, install it. If so, uninstall it, reboot, reinstall it.
Try different cables, different usb ports, even different pc's.
I'll try not to butt in too much, since creepyncrawly obviously has a lot of experience.
(at this point, I'm assuming you're on Windows)
Like he said, it's sounds like it's most likely a driver issue. When you first plugged in the phone, did you get a Windows balloon notification saying "Installing drivers"? If you open up device manager, do you have any devices with an exclamation point next to them, indicate a device that failed to start? If so, make sure the Samsung drivers are installed.
A USB jig is definitely nice to have handy. I use this one (as long as you can wait a few weeks on shipping). If you can get into download mode, your bootloaders are probably safe (meaning you should be able to recover easily).
I actually installed that CM11 ROM yesterday on my SGH-I777 (I can't say anything specific about your model and how it may differ, but it seems to basically be the same phone as the I777). I was running stock non-rooted JB 4.1 with stock recovery, so I had to take a little more of a convoluted route to get there.
In the end, here's the thread for you. Once you can get ODIN download mode working again, you should be well on your way to fixing it (flash CWM 6.0.4.5 from ODIN, boot into recovery, then try the ROM install again).
Well, I've tried flashing CWM again using Odin. While I actually can USE Odin this time, it just isn't working... My phone still only turns on and goes blank after the Galaxy S II screen.
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Hi - I don't know if it is a completely outdated method, but this worked on my father's SII skyrocket yesterday when I was encountering a similar softbrick issue:
Get zadig (http://zadig.akeo.ie/), start zadig, get the phone in download mode, hit Options -> List All Devices, select the Samsung or similar device from the dropdown and replace the default USB driver.
Then use heimdall (http://forum.xda-developers.com/showthread.php?t=755265) to flash in a replacement recovery.
Double check that your phone is detected in download mode: heimdall detect
Then flash the recovery: heimdall flash --RECOVERY recovery.img (try CWM for your phone version)
(some places will have you add --no-reboot. that didn't work for me. let it auto reboot)
After it powers down, quickly disconnect the USB cable and put your fingers on the +/- buttons to get into recovery mode. From there push over whichever ROM via adb, etc. etc.
jpasher said:
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Click to expand...
Click to collapse
It says Odin is successful, but still nothing happens. And I cannot get into recovery no matter how many times I try.
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Epications said:
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Click to expand...
Click to collapse
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
SteveMurphy said:
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
Click to expand...
Click to collapse
I'm having difficulties booting into recovery.
Epications said:
I'm having difficulties booting into recovery.
Click to expand...
Click to collapse
If you have the stock boot animation you should have recovery. Take the battery out, then put it back in and hold power+volume +/- until you get recovery. I have sometimes had to do this extra step after restoring stock.
Make sure your phone isn't plugged in while you're trying this, btw.
grand quattro CWM TRAPPED
Epications said:
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
Click to expand...
Click to collapse
HI BROOOO I M A GRAND QUATTRO USER EVERYTIME I SWITCH ON MY CELL MY CELL DIRECTLY GOES IN CWM MOD M WORRIED ALOT HELPPPPPPPPPPP ME

Categories

Resources