i downloaded the oclf and fixed my lag. later i hit a button called kernals and it was one on there that said voodoo something so i hit it and my vibrant went through some process. where a broad was counting and stuff. then when it was finished my phone rebooted but never went pass the first screen that said vibrant samung but the sound still sounds. how do i go back to normal. call me if you want MOD REMOVAL
sirford1 said:
i downloaded the oclf and fixed my lag. later i hit a button called kernals and it was one on there that said voodoo something so i hit it and my vibrant went through some process. where a broad was counting and stuff. then when it was finished my phone rebooted but never went pass the first screen that said vibrant samung but the sound still sounds. how do i go back to normal. call me if you want MOD REMOVAL
Click to expand...
Click to collapse
ODIN is your friend.
And you've just been added to every CALL SPAM list in the world. (not by me, probably by some 12yr old kid on here)
Never give out your phone number over a public forum.
sorry to hear about the flash, but sometimes it takes a long while on first boot after the voodoo....but ODIN is a lifesaver
Don't worry, you can still completely fix your phone like it was brand new.
Have a look here:
http://forum.xda-developers.com/showthread.php?t=849028
http://androidforums.com/vibrant-tips-tricks/223806-guide-fixing-bricks-odin-errors.html
also here on how to do the simple process of using Odin:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
I've done probably half a dozen resets/flashes using Odin and I must say, it can be temperamental sometimes, requiring you to restart the process a few times before it doesn't get stuck and hang at a certain portion. It should only take a few seconds to get the process on your phone going, so if you are waiting for several minutes and your phone is still sitting in download mode, you need to restart. HOWEVER, it has always gotten me back to stock in the end. Sometimes I just have to start the process 2-3 times.
If you need to get your phone back into download mode after a failed start, power off the phone (remove the battery if necessary and replace it) just hold the volume buttons and plug in the data cable and it should do so allowing you to restart the process.
Wow I totally don't see prank calls coming your way lol
Still flashing , thanks to odin & tw
Replaced phone number with MOD REMOVAL Please post in the right section next time too
i went ahead and tried to put that t something and s1 something but now its just stuck at the black screen its been like that for a half hour and ive done it about 5 times im just about to do an insjob
Related
First off this is my first post, and I gotta thank everyone cause I've been able to do some cool stuff with my phone and without the support of the community and the vast knowledge some of the guys (and gals) have on xda, I would be just another average consumer. And I'm still learning.
So a few days ago I tried to update my rooted Vibrant (with the lag fix) through Tmobile, like a noob, without unrooting my phone and everything was going great until the phone rebooted and got stuck on the "Samsung" startup screen.
I was able to fix that after reading through the odin3 fix and got the phone up and running again. Decided I didn't need froyo that bad and just reinstalled all my old stuff with Titanium backup.
Then after reading through the forums a little more I got the itch to try 2.2 again, so I was a little smarter this time, undid the lagfix, unrooted the phone and started the update. But once again, frozen at the "Samsung" screen...
Odin to the rescue again. But this time as odin was doing its thing, the power went out in my house, ughhh! Got everything back up and running and when I tried to turn the phone on it goes to a screen I haven't seen before, with a "phone" icon, two dots, a "triangle caution" icon, two dots, and a "computer" icon, and it wont get out of it. It won't connect to my computer so it won't connect to odin.
I'm usually decent at finding the solutions on the forums and I could have sworn I read somewhere about this type of problem, but I guess I'm wording my searches wrong so nothing is coming up.
So how do I get my phone out of this mode? Or is it bricked?
Also does anyone now why the phone would freeze like that after the update? I probably should have just flashed one of the froyo roms, but I figured it would be easier to return if the OS was from Tmobile.
steambrick said:
First off this is my first post, and I gotta thank everyone cause I've been able to do some cool stuff with my phone and without the support of the community and the vast knowledge some of the guys (and gals) have on xda, I would be just another average consumer. And I'm still learning.
So a few days ago I tried to update my rooted Vibrant (with the lag fix) through Tmobile, like a noob, without unrooting my phone and everything was going great until the phone rebooted and got stuck on the "Samsung" startup screen.
I was able to fix that after reading through the odin3 fix and got the phone up and running again. Decided I didn't need froyo that bad and just reinstalled all my old stuff with Titanium backup.
Then after reading through the forums a little more I got the itch to try 2.2 again, so I was a little smarter this time, undid the lagfix, unrooted the phone and started the update. But once again, frozen at the "Samsung" screen...
Odin to the rescue again. But this time as odin was doing its thing, the power went out in my house, ughhh! Got everything back up and running and when I tried to turn the phone on it goes to a screen I haven't seen before, with a "phone" icon, two dots, a "triangle caution" icon, two dots, and a "computer" icon, and it wont get out of it. It won't connect to my computer so it won't connect to odin.
I'm usually decent at finding the solutions on the forums and I could have sworn I read somewhere about this type of problem, but I guess I'm wording my searches wrong so nothing is coming up.
So how do I get my phone out of this mode? Or is it bricked?
Also does anyone now why the phone would freeze like that after the update? I probably should have just flashed one of the froyo roms, but I figured it would be easier to return if the OS was from Tmobile.
Click to expand...
Click to collapse
Email me [email protected]
Thegreat520 said:
Email me [email protected]
Click to expand...
Click to collapse
That's nice of ya GreatOne
+1 vote for personalized help...
~SB
i was doing my first flash of a rom last night and i didnt notice a status bar letting you know what processes were going on or if it was even installing the rom. So... i left it sitting on the vibrant screen for like 20 minutes and i saw absolutely nothing going on and became concerned it bricked. so i whipped out the old trusty backup iphone and went to downloading android sdk and supporting programs so i could adb in and make it reboot. i got tired around 1am and called it a night. put the vibrant on the charger and noticed the battery charging display popped up and it was half full. left it to charge all night and left the laptop updating and downloading all the sdk tools and stuff. got up next morning and plugged the vibrant into the laptop and the vibrant screen popped up as usual when u plug it in to a computer. i paid no attn and brought up my cmd line and was fixing to adb reboot recover and low and behold i heard the tmo jingle and saw the galaxy s icon start going. so long story short would it be a big deal to put a status bar to let someone know its actually doing something other than just sitting there? just a thought... and what length of time does it usually take to flash a rom and reboot the system?
HaCkEdUpViB said:
i was doing my first flash of a rom last night and i didnt notice a status bar letting you know what processes were going on or if it was even installing the rom. So... i left it sitting on the vibrant screen for like 20 minutes and i saw absolutely nothing going on and became concerned it bricked. so i whipped out the old trusty backup iphone and went to downloading android sdk and supporting programs so i could adb in and make it reboot. i got tired around 1am and called it a night. put the vibrant on the charger and noticed the battery charging display popped up and it was half full. left it to charge all night and left the laptop updating and downloading all the sdk tools and stuff. got up next morning and plugged the vibrant into the laptop and the vibrant screen popped up as usual when u plug it in to a computer. i paid no attn and brought up my cmd line and was fixing to adb reboot recover and low and behold i heard the tmo jingle and saw the galaxy s icon start going. so long story short would it be a big deal to put a status bar to let someone know its actually doing something other than just sitting there? just a thought... and what length of time does it usually take to flash a rom and reboot the system?
Click to expand...
Click to collapse
regularly for me, the average is about 5-7 minutes, not including the time it takes to download the ROM itself on computer and transfer.
Probably because i have everything set up, i have a file called FIX BRICK and all the files i need in there to "fix" the "brick"
I'm used to it, and don't mind odin'ing so its all quite short.
but most of the time IS taken up by the phone reformatting everything, then rebooting, the first boot is ALWAYS the longest.
Were you installing a ROM with a Voodoo kernel baked in? If so it takes about 15 min to reformat the file system.
CrazyCharlie said:
Were you installing a ROM with a Voodoo kernel baked in? If so it takes about 15 min to reformat the file system.
Click to expand...
Click to collapse
does it?
I just flashed AXURA with voodoo in it, and it took me like 6 minutes.... o god, lemme confirm i have it enabled or something lol
i heard linda talking and telling me the confirm time, but.......
brb gonna check!
nvm its already enabled lol... guess my phone's awesome?
also i went to stock using odin then flashed so my previous voodoo has nothing to do with this
If it was already enabled when you flashed Auxura then it was probably because the rom you were having trouble with already reformated the file system. Voodoo can be tricky with some of the older rom's but with the ability to enable and disable through clockwork it's much easier to deal with. Remember when flashing new rom's to disable the lagfix first. If the new rom uses a non voodoo kernel you'll get a soft brick.
CrazyCharlie said:
If it was already enabled when you flashed Auxura then it was probably because the rom you were having trouble with already reformated the file system. Voodoo can be tricky with some of the older rom's but with the ability to enable and disable through clockwork it's much easier to deal with. Remember when flashing new rom's to disable the lagfix first. If the new rom uses a non voodoo kernel you'll get a soft brick.
Click to expand...
Click to collapse
na i did it on purpose.
When i want to use a rom for a long time, i odin back, so there are no ghosts what so ever left, and then flash the rom, so its fast just as good as new.
and i checked re-format on odin, so the ext4, was turned back to RFS or RTS what ever that is.
The longest it ever took for my phone was when I went from 2.1 to 2.2 for the first time. Wasn't more than 10 minutes but noticeably longer. Patience is key.
Whether you break your phone now or later, go ahead and get all things necessary to fix. Just sayin...
Agreed. Odin is you're friend.
[ROM] Vibrant AOSP ish JK2 1.1 Official FROYO (Working GPS, WiFi Calling) this is the rom i used. idk if it has a voodoo kernel. i wouldnt think so. it was asthetically pleasing to my eye when i saw the screen shots and i noticed all the bloatware was gone so thats y i chose it. i like it so far. kinda glitchy at the first restart/reboot ( moved all of my widgets back to where they were on first start up after i placed them where i wanted them, and i had to load my google acct twice and my FB contacts twice) but since then it seems like everything has settled down and i am very pleased. kudos to the rom maker. its 10 times better than eclair. thanks for the input guys
btw im really diggin the car section. does it pair via bluetooth?
does anyone know how long it should take for odin to finish flashing my phone back to stock? Also has anyone seen this screen? It's black, with a white cell phone and a white computer with a yellow triangle with an "!" in the middle between them....? that's all i can get my phone to do. Odin is taking a really long time and i'm not sure everything's working right.
it should take 5-15 minutes at max.
I get that sign every time i do odin, but unlike others i just click the power button and reboot and its good... try that?
well how do i know when odin is finished? becuase it's been stuck on step: chache.rfs for about 20 minutes now and i don't know if it's just frozen up or what. I don't want to unplug it if i'ts still doing something.
hate to sound like a **** head but when that happened to me this last go around (getting stuck on the chache part) i unplugged which gave me the computer ... ! thingy i put it back into download mode and opened odin then plugged my phone back in. hit start after putting my pit and tar files in their respective spots and it worked. took less then 6minutes i'd say.
There are ways to dl mode your phone from computer ... ! screen just find them. im leaving for a puppy otherwise i would have linked it. gf getting angry RAWR!! <(*-*t)
thats her giving me the bird and ready to kill. LOL
That happened to me also, and it was my very first flash on the Vibrant. It soft-bricked, but I just kept at it... got back into download mode... and tried again. It worked. As far as I can gather, as long as you can still get to download mode, you are golden, even if it takes a try or two. It seems that Odin is sometimes temperamental. It only takes a couple of minutes to flash via Odin, but when you are sitting there waiting for the PASS notification, it does seem like an eternity the first time you do it.
I got a FAIL the first two times on the very first attempt. It's a bit unnerving when you aren't sure it'll come back.
vballrkc said:
does anyone know how long it should take for odin to finish flashing my phone back to stock? Also has anyone seen this screen? It's black, with a white cell phone and a white computer with a yellow triangle with an "!" in the middle between them....? that's all i can get my phone to do. Odin is taking a really long time and i'm not sure everything's working right.
Click to expand...
Click to collapse
Are you running window's 7?
If you are run as admin , also that happened to me to couple days ago at the 5th time trying it finally worked
theronw68 said:
Are you running window's 7?
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
I am currently downgrading back to stock on my T959 using Odin 3 and it keeps hanging at the very first part when it says file analysis. I have been at this part for a good 30 mins. any suggestions? just keep retrying until it works?
Just keep at it...ODIN likes to be picky.
mine normally takes like 2-4 min
mine froze on factory reset.rfs or something yest for like 10 min so i unplugged and got the 'phone ! pc screen', took me like 2 hours to get it to connect to odin again
aecabanaboy said:
I am currently downgrading back to stock on my T959 using Odin 3 and it keeps hanging at the very first part when it says file analysis. I have been at this part for a good 30 mins. any suggestions? just keep retrying until it works?
Click to expand...
Click to collapse
could redownload odin and the pit/tar files again and try that
It takes about about 3 minutes to get my Vibrant from any custom to JFD. I just Odin 3 v1.81, s1_odin_20100512.pit, can T959UVJFD.tar files only. Total time is about 2:20-2:35 seconds.
Mine takes about 2-3 minutes
i am now flashing with odin and its stock on catche is this a problem ?
mine hasnt moved from the downloading screen - its been about 39min.
Yesterday my battery died half way through playing a game (not entirely unexpected, I'd been playing on my phone quite a bit that day and it still lasted 22-23 hours), I connected the charger that came with the phone and left it to charge while I got on with some uni work.
The phone vibrated to tell me the charge was complete so I disconnected the charger and turned the phone on as usual. After the samsung galaxy S2 splash screen, the screen lock appears and when I move it there are several error messages saying that various applications have had to stop (the main one seems to be TwLauncher but when I force close it, many others also force close). This continues for several seconds until the phone decides to restart itself and repeats the process ad infinitum until I can shut down the phone (I can manage this by not trying to get rid of the screen lock and just holding the power button until the menu appears).
I've had this phone a week (one of those days being today where it did not work at all) so it's still well within the return period but I was wondering if there is an obvious fix that I'm missing.
If not, I'll be ringing Samsung on Monday (I have coursework due for friday so I'll be devoting my samsung office hours time to that) and if they can't give me an easy fix I'll be ringing the place I bought it from and asking for an exchange.
So, has anyone else had similar issues and managed a simple fix?
Bump, I take it everyone else's phone is working then?
Giving this another bump in the hopes there's someone with a simple solution.
I don't want to have send my phone off and wait for the place to get stock.
there have been 2 firmware releases from samsung in the last couple of days, i assume you are running the latest firmware?
I can't even get the phone to stay on long enough for Kies to recognise it. It keeps restarting. Even when it was working I couldn't get Kies to work with it properly (I couldn't copy the contacts from the phone to the computer).
It's running the firmware it came with, but I can't check which version it is.
I was going to try flashing the new firmware via ODIN but I've been busy with coursework. Is this likely to solve the issue or will I just be giving the retailers ammo to reject my return?
go into recovery and do a factory reset
psp888 said:
go into recovery and do a factory reset
Click to expand...
Click to collapse
this is what I was looking for.
after googling, this sorted it out.
I just assumed download mode was the only other non-normal mode.
Thanks
Basic FAQs on the SGS1 forum mostly apply to SGS2 .Worth a look there before Google .
jje
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.