[Q] Vibrant booting indefinitely? - Vibrant Q&A, Help & Troubleshooting

I believe I'm running ICS Passion, I'm not sure what version
Last night I turned my Vibrant off. It wasn't anything special, just a boot because my messenger app wouldn't open. However, when I got home and tried to turn my phone back on the phone will take an unusually long time to get past the loader, and then the boot animation seems to run forever. I left it on overnight and my phone was not booted in the morning. The process seems to take up a lot of battery as well. I'd like to avoid flashing another rom because I haven't had preparation, but I need to update soon anyway so it's not completely out of the question. How can I attempt to fix this?

Odin back to stock

djquick said:
Odin back to stock
Click to expand...
Click to collapse
I figured I'd have to do this.
I used my home made jig to get into download mode (because the three button combo isn't working) however my computer is refusing to recognize the device when I open Odin. I'll try on my desktop when I get home, but for now I'm just going to let the phone boot and see what happens.
I'll post back if I still can't odin to stock.

Related

[Q] Won't boot past Vibrant screen; recovery works

I recently installed JAC's kernel, and today I was getting force closes on nearly all of my apps. Even market would FC. So I did a nandroid (the nandroid was with the stock kernel), and now the phone won't boot past the Vibrant Samsung screen. Recovery menu works however. I'm guessing the issue is that I shouldn't have flashed a nandroid that was non-JAC kernel.
I have absolutely no idea what to do in this situation. Can anyone help? I really appreciate it, thanks.
UPDATE:
I flashed the Official T-Mo ODIN images, and got the phone working again. I'm not sure if there was some other way without wiping the phone, but this way worked.
I did a nandroid recovery last night of my stock image and it took about 5 minutes to get past the Vibrant Samsung screen, but it ultimately made it past it.
Hm, I must have been not paitient enough. I didn't count but it felt like I waited 4-5 minutes.
I can NOT get past this screen or into download or recovery mode... All I get is a spinning wheel... tried to downgrade from CM7.... I tried everything Ive read to try to get into download mode...any ideas?
l0stcaus3 said:
I can NOT get past this screen or into download or recovery mode... All I get is a spinning wheel... tried to downgrade from CM7.... I tried everything Ive read to try to get into download mode...any ideas?
Click to expand...
Click to collapse
I was finally able to get into download mode..... I spent hours getting my google on reading all the different was to get into download mode...Now my phone would not boot past the "Samsung Vibrant" screen and all the different button combos wouldnt work... Here is what what worked for me..
1 I ungluged the phone from the laptop and removed the battery to make sure the phone was off...
2 I held down BOTH vol+ AND vol-
3 While holding down BOTH vol keys I plugged in the USB and BAMM!!!!!! download mode.....
I hope this helps someone.....
didnt think nandroid backed up the kernel
so doing nandroid to get back to the kernel you were on before wouldnt have done anything

Phone stuck on Phone-!-Computer screen.

So, I just got my phone back from Samsung for this issue. Start my newly returned phone up, it's running 2.2. I turn it off, hold volume buttons and plug in my USB cable - I get download mode instantly. I start up Odin 1.7, select the files and click start.
Nothing happens. Hangs up SetupConnection. I unplug the battery, then the USB cable, plug everything back in and I'm back at square one with this ****ing screen.
Last time I tried every single ****ing button combination posted on this website. I know my phone isn't hardware locked because I've never had a problem getting in to Download Mode before. Hell, I'd never had a problem with Odin not working properly before. What the hell is wrong? I have all the proper drivers installed. Why is this happening?
Now, Odin still sees my phone when I plug it in. If I click Start, sometimes it hangs on SetupConnection, sometimes it hangs on Initialization. I've read that you should still be able to flash while on this screen? Is this true? Either way, I think I'm ****ed again. Any help?
Also, I've read that maybe a jig will help get me in to download mode? Where can I buy a jig from?
you can go to stock jfd from that screen, it acts like download mode.
Once on jfd, download mode will work fine.
try the files in my going back to stock... also make sure to remove any other usb components (they can cause odin to hang).
I love you.
Something must be wrong with the files on my desktop, or perhaps the other USB cable I'm using is ****ed.
This is a bit embarrassing. For some reason I can't get root. I can get in to recovery and select reinstall packages, but every time it boots right back in to the OS. Any hints? Never had this issue before.
EDIT: So it looks like I have Superuser installed but since I can't get into Clockwork I can't flash any roms. What's going on? I can't find any other links where people couldn't get in to Clockwork.
EDIT2: Well, I installed ROM Manager and used it to "flash" CWM. Reinstall Packages worked this time it seems. Weird. Anyway, thanks for the help!
Cool, glad you were able to get it all sorted.

[Q] Odin is flashing several hours...

I've flashed my Galaxy S2 with Odin several times and it has worked fine until yesterday, when I tried to flash again, and everything just froze.
I followed the normal instructions for flashing and the phone just stopped at the "downloading" screen where it says, "Do not turn of target!!".
So it has been, for several hours now. The Odin window on my computer seems to be waiting... but for what? Will it ever time out?
Is it normal that a flash session can take several hours?
Is it safe to interrupt it?
fugy56 said:
I've flashed my Galaxy S2 with Odin several times and it has worked fine until yesterday, when I tried to flash again, and everything just froze.
I followed the normal instructions for flashing and the phone just stopped at the "downloading" screen where it says, "Do not turn of target!!".
So it has been, for several hours now. The Odin window on my computer seems to be waiting... but for what? Will it ever time out?
Is it normal that a flash session can take several hours?
Is it safe to interrupt it?
Click to expand...
Click to collapse
Odin will flash, takes less than 5 minutes.
Is there any data running that you can see? I mean at the bottom left. I would suggest you turn off the phone, battery pull, wait for 5 minutes, and reflash back.
If it semi bricked, use JIG to revive it.
Either way, you can't be letting the phone there for the next few days etc right?
Did you click Start in Odin??
Although i don't have an s2(will be getting one soon) did you try to reset your pc? When i was flasing my sgsl i was stuck in this situation where odin seems to freeze everytime. I restarted my pc and poof, flashed without a problem
Edit: was flashing successful? If so maybe you should follow the instruction from the post below.
Sent from my GT-I9003 using XDA Premium App
This might sound stupid but did you have 'auto-reboot' checked? It happened to me once even though I have flashed hundreds of times. Odin was still open after flashing a kernel and never reset.
Start was clicked - yes.
Re boot was checked - yes.
I reset my computer and restarted my phone and - now it's still frozen, but with an icon on the center showing three icons in a line. First is a phone, second is a exlamation mark and third is a computer. Yiipiiiee. It doesn't boot. I can't get into recovery mode. Download mode does work however, but still the same behaviour. It freezes if I try to flash it.
Now what? Where is that reset-button which resets the phone and clears its brain down to original mode? A simple "brain wash" would be nice.
Is there anyway out of this "freeze of death" ?
Flash CWM kernel, download CM7 rom, copy it on SDCard (mount USB storage in CWM, connect to PC via USB, copy ROM), flash ROM from CWM
fugy56 said:
Start was clicked - yes.
Re boot was checked - yes.
I reset my computer and restarted my phone and - now it's still frozen, but with an icon on the center showing three icons in a line. First is a phone, second is a exlamation mark and third is a computer. Yiipiiiee. It doesn't boot. I can't get into recovery mode. Download mode does work however, but still the same behaviour. It freezes if I try to flash it.
Now what? Where is that reset-button which resets the phone and clears its brain down to original mode? A simple "brain wash" would be nice.
Is there anyway out of this "freeze of death" ?
Click to expand...
Click to collapse
Try to go into recovery mode and factory reset and clear cache and try flashing again (make sure you are on download mode)
Sent from my GT-I9003 using XDA Premium App
Hold power button to off it (hold a lil longer for this).
Then Go into recovery mode (power, home button and volume up at same time). Try do wipe all data, cache and even dalvik. Reboot and see if that works.
Alternatively, at the same place, go into restore backup.
The man said: "I can't go into recovery mode"
...
Recovery mode doesn't work - nope. But thanks anyway. It's nice to see that people at least try to help. Big hugs to you all.
If I try to flash CWM, I come into the same freeze again. Mindbending stuff ala Samsung, huh. They clearly don't make idiot-safe products. I'm stuck. My next phone might be a StarTAC...
Has happened to me before. KIES was opened. I closed all KIES files and the flashing fun started again~
Good point, make sure Kies isn't running when using Odin!
Also, now that you've flashed CWM, can't you boot on it?
Kies is not running and whatever I flash - it freezes. The green progress bar in Odin reaches maybe 1 cm, but no blue progress bar is visible on the phone as usually happens when flashing. It just says, "Downloading... Don't turn off target!!"
Am I slowly heading towards the brutal-axe-method?
Sounds like the NAND is damaged to me, but I'm no expert...
"NAND" means? Why does it sound like it's damaged? How can it get repaired?
NAND is the flash chip (internal sdcard). Seems that its damaged because you're unable to fully flash it.
I don't think you can have that repaired (if the NAND is truly damaged, like I said I'm no expert), you'd have to get the phone replaced.
With all respect, let's hope you aren't an expert, but better. But has anyone else interrupted a flash process and went though a "freeze"?
I'm looking for a way to reset the phone to use only what was burnt into ROM from first delivery. I just can't accept that it is so easy to mess up a phone, and I doubt Samsung would be so crazy not to build it with a rescue kinda last savior. Am I totally naive? Is my baby dead? :'(
lol I hope for you that I'm wrong also!
fugy56 said:
With all respect, let's hope you aren't an expert, but better. But has anyone else interrupted a flash process and went though a "freeze"?
I'm looking for a way to reset the phone to use only what was burnt into ROM from first delivery. I just can't accept that it is so easy to mess up a phone, and I doubt Samsung would be so crazy not to build it with a rescue kinda last savior. Am I totally naive? Is my baby dead? :'(
Click to expand...
Click to collapse
Something similar had happened with me too. The phone was stuck b/w flashing with odin. And the startscreen was showing those 3 icons. It was soft bricked.
But I then finally fixed it by flashing CF and then a ROM

[Q] CinBell Vibrant 4g stuck on AT&T World Phone boot screen

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.

[Q] vibrant boot issue

I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
[email protected] said:
I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
Click to expand...
Click to collapse
I have Jtag solve for Hard brick phone
Please PM me or check out at my signature.

Categories

Resources