Related
I recently used ODIN to flash my T-mo Vibrant back to stock and then upgrade to Froyo. I was unimpressed by Froyo and wanted to flash a custom rom so I rooted and tried to flash a custom rom and it wouldn't work. I then used Odin to try to flash back to stock....got my vibrant stuck on the phone -triangle- computer dl screen after multiple tries it still wouldn't flash in an act of frustration I dl'd another ODIN and one clicked flashed my Vibrant I then find out that this particular ODIN was made to flash a stock captivate rom so now my Vibrant boots to the at&t world phone screen and loops. I tried button combos to get to dl mode and haven't succeeded.....HELP PLEASE! -also will the dl mode usb jig help in this case?-
Can you get into download mode? If not a jig is probably your last stop.
Best guess (all it is)
You are going to have to try just about every different button combo to try and get to download mode (if no jig). Since you flashed a non vibrant rom the keys make be remapped. Try different 2 button combos also.
I can't get into dl mode at all whenever I try it either loads the at&t screen and starts to loop or just shows the battery logo
Thx for the replies tho i just ordered a jig from ebay so hopefully that works.
Just wondering - you said you tried every button combo
Was that after you pulled the battery? Did you get into download mode for Odin via batterypull/button combo/usb pull in or rebooting from the rom?
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
It's not bricked. Probably just in a boot loop. Just need to play around and get into download mode.
speedy11131 said:
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
that doesnt make a difference, i've been on simply honey like 2 month on froyo bootloaders and works fine apart from rainbow on boot and not being able to see recovery
speedy11131 said:
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
That happened to me before, I used and tried a different cable and got into download mode with functioning odin. Also, try removing battery, then put the battery back in. then with pressing volume up and down with power switch plug in usb. Hope this helps. Vibrant is hard to brick.
Sent from my GT-I9000 using xda premium
It is not dead yet, follow the steps as follow thread to go back in beginning and flash rom you want again.
http://forum.xda-developers.com/showthread.php?t=734475
Depending on which version of ODIN you are using the sequence works best like this:
1) Get the phone into a download acceptable mode with use of a usb cable (JIG is most appropriate)
2) Have ODIN running BEFORE connecting the phone
3) Now connect your phone and attempt the flash. Version prior to 1.7 were extremely picky with following this sequence. As of 1.7 POST ODIN seems to not bug so much the sequence of when the phone was plugged in.
Report back with your results...
speedy11131 said:
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
1) take your battery out
2) plug your phone a laptop/desktop
3) hold volume up and volume down + put the battery in
...should be in download mode...I am assuming u have a froyo bootloader...
If that don't work then on step three instead of holding both volume buttons only hold volume up..that works for GB bootloader...
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
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.
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