I'm reasonably new to the whole Samsung scene. Needless to say, Odin absolutely bewilders me. I bought this Vibrant, the dude said he tried to flash a bootanimation, and when he did, he bricked his phone. When you turn the phone on, you see the Samsung Vibrant splash screen, it goes through the bootanimation he flashed, and when it gets to where the homescreen should be, you see blackness. However the capacitive keys are lit up. From what I read this is a sort of soft brick. I'm not too sure. Anyhow, I bought it for two hundred bucks because I knew if I could get it into recovery, or connect it to adb, I'd be golden. The problem is I can't.
For the life of me I cannot get adb to recognize my Vibrant, also, when I try and put the phone into download mode I get nothing. Phone Will boot up, go through the bootanimation, and once I get to the home screen everything goes black with the capacitive keys lit up.
Any suggestions would be greatly appreciated.
On a side note: I had an Epic not too long ago and had nothing but problems with the Drivers. 32 bit.
Thanks in advance.
It sounds like the rom is corrupt/missing. Can you get into clockworkmod recovery? If so you can then push a rom.zip with ADB and flash it. He should have done a nandroid backup before flashing and if he did its as simple as getting into clockwork and doing a nandroid restore.
If you cannot get into recovery, try the instructions here: http://forum.xda-developers.com/showthread.php?t=741027&highlight=unbrick
Thanks for the suggestion, man. Just clarifying, not being able to get into recovery mode or download mode, and not being able to get adb to recognize the phone entails a legitimate brick, correct?
Related
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
So on Thanksgiving my phone freaked out. blah blah blah. Used Odin and went back to stock. Since then i can not enter recovery mode at all. Not by pressing correct buttons or by using Rom Manager.
What it does is it boots up and goes to the first vibrant screen and will just sit there until I pull the battery.
I used to be able to get in to recovery mode with no problem... my phone was not hardware locked before. I just did not know if by flashing to stock would cause it to become hwl, or if anyone knew what the hell was going on with it! I also pushed in a button combo into the phone and wiped it to a factory fresh state also.
EDIT:
Now my phone would just not go past the first vibrant screen. Had to use odin to go back to stock once again... accept when it was done it did that error where i get red font at the bottom.... i was able to get it in to clockwork recovery... then i just flashed a zip that i had on it.. took a while but its working
ironically, and i stress.
IRONICALLY.
as soon as 2011 rolls around, i suddenly loose service?
and i figure it's a problem with the rom that conflicting with the radio, so i restore using Clockwork ROM Manager.
upon doing so, I first get a Yellow Exclamation point, so I restart my phone.
it goes through the process, and then it stays at the "Vibrant" screen for a good 20 minutes.
did I do something wrong? :/
Were you going from froyo to an eclair backup? Backup's don't restore the kernel, hence hanging.
Most would suggest to odin back to stock.
no, it was from Eugene's 2.3 clone to stock.
and I already backed up my stock rom, but I think I used the wrong method of restoring.
like, I went to ROM Manager, Restore Backup, and I had a big exclamation point.
I let it sit for 5 minutes, nothing happened so I restarted.
It restored and everything, and then it just bricked at the Vibrant screen.
to be more specific, i used this rom:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=144
i backed up using both nandroid and rom manager.
i hope this can be restored.
because it's not a critical brick.
but just a soft one.
it won't boot into download mode with the power button/vol trick because I tried it before.
it just flashes on a black screen, and i usually use cmd to do it.
but because it's possibly hardware locked, i cannot do anything from cmd because it says "the device is not ready" even though it's plugged in to my computer.
please tell me someone can help me.
i think it's unfixable because of two reasons:
1. i am hardware locked, and i cannot boot it with the power key trick.
2. cmd can't find the device, even though it's recognized by my computer and odin.
primarily, my computer sees the drive i need to access, but i cannot connect to it because my phone won't get past the vibrant screen.
so, i think it might be full bricked and there isn't anything i can do to fix it.
but it's weird, because ODIN sees my phone, but there is no way to download the stuff i need from odin on my phone.
sorry to spam like this, but i really need the help.
I've had this problem in the past but I got my phone back in september/october so my vibrant isn't hardware locked
I would keep trying, last night I bricked my phone while flashing a rom and I was barely able to get it into download mode...
Try this combo:
1. Hold power + 2 volume buttons while plugged into computer
2. Keep holding until vibrant logo flashes 3 times
3. Right before the vibrant logo shows for the fourth time RELEASE VOLUME UP BUTTON
4. Odin back to stock
This always works for me, but liked I said, my phone is not hardware locked this may or may not work
Sent from my SGH-T959 using XDA App
it's not going to work because my phone is hardware locked.
but i'll try. :/
Try pulling the battery and sim and try odin again...should be working if you see a com port in odin.
no it didn't work.
would i be able to call t-mobile and tell them that upon a soft reset, the phone stopped booting?
Are you sure it's a hardware locked? Even before you flashed a custom rom you can't access the recovery through the 3 buttons?
Sent from my SGH-T959 using XDA App
Edit: see following post
You went from eugene r2 to stock? Stock meaning 2.1 that came with your phone? It definitely sounds like a soft brick due to kernel mismatch...
So I tried rooting my T-Mobile Samsung Vibrant T959 successfully and tried flashing a ROM. In the middle of the loading, my phone reboots and gets stuck at the vibrant loading screen. Now it won't turn on.
I've rooted my old phone before and for some reason this time it didn't work. I followed instructions but now I guess it's broken.
*I used the oneclick root program. Followed instructions and what not.
Is my phone completely broken now? Or there's still a chance?
Not sure if this is what they call a hard brick or not.. I'm hoping it's not. Don't have time or will to search the forums. I'm panicking.
It's stuck on the Vibrant screen and doesn't do anything even if I wait.
Need a fast response asap please.
Any help would be very much appreciated!
Thank you!
Well first I think you are rooted, if you were able to put a ROM on the root of your phone and then use cwm recovery to install.....you are rooted.
Now pull the battery and put it back, hold vol up/vol down and power, it should take you back to recovery then reflash the ROM. You are not hard bricked.
sent from my magic box to yours
samsgun357 said:
Well first I think you are rooted, if you were able to put a ROM on the root of your phone and then use cwm recovery to install.....you are rooted.
Now pull the battery and put it back, hold vol up/vol down and power, it should take you back to recovery then reflash the ROM. You are not hard bricked.
sent from my magic box to yours
Click to expand...
Click to collapse
I have been trying to get back to recovery but it takes long and doesn't do it. I'll keep trying though.
I'll report back in a few.
EDIT: After a few minutes of trying.. I think it finally worked. Got to recovery and was able to flash the rom.
Hopefully everything will be stable.
Thank you so much!
All,
I have a Verizon 16gb S4 that was already rooted and using CleanRom. I decided I was not happy with the 16 and have picked up a 32GB. In turn, I was going to format the old one using the Recovery mode and sell afterwards. During the wiping process the screen went black. Now, it just reboots to the Samsung S4 splash screen and reboots, over and over and over. It never goes past the S4 screen. If I hold POWER and VOL UP to go into recovery mode, it shows that it is going, reboots, and does that same crappy rebooting over and over. I can get into ODIN mode with success, but was unsure how/what to even do at this point.
Am I just screwed? I sure hope not.
boot loop
SimpleAtheist said:
All,
I have a Verizon 16gb S4 that was already rooted and using CleanRom. I decided I was not happy with the 16 and have picked up a 32GB. In turn, I was going to format the old one using the Recovery mode and sell afterwards. During the wiping process the screen went black. Now, it just reboots to the Samsung S4 splash screen and reboots, over and over and over. It never goes past the S4 screen. If I hold POWER and VOL UP to go into recovery mode, it shows that it is going, reboots, and does that same crappy rebooting over and over. I can get into ODIN mode with success, but was unsure how/what to even do at this point.
Am I just screwed? I sure hope not.
Click to expand...
Click to collapse
after reading stories on here and other sites, I am assuming based on the fact I cannot get to the recovery mode that I am bricked for good. Correct? Anyone?
If you can get to Odin mode, you should be OK
If you can get into Odin mode, you should be able to get your phone back to a usable state. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?p=41986600&postcount=1
SimpleAtheist said:
after reading stories on here and other sites, I am assuming based on the fact I cannot get to the recovery mode that I am bricked for good. Correct? Anyone?
Click to expand...
Click to collapse
thanks!
maxyoda said:
If you can get into Odin mode, you should be able to get your phone back to a usable state. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?p=41986600&postcount=1
Click to expand...
Click to collapse
That is what I needed
good thing to do before flashing any rom is to research on how to get back to stock in case anything goes wrong. usually if you can get into download and/or recovery it should be easy to fix most problems.