Really WEIRD reboot issue T959 Vibrant T-Mo - Vibrant Q&A, Help & Troubleshooting

So I was using Odin to flash the stock JFD to fix a soft brick. Everything went through and flashed just fine, no issues. I've done this dozens of times before, on several different devices, so I'm pretty familiar with the process. After the phone flashed, the screen switches to some weird distorted screen for a couple seconds and then it boots. It boots up fine, and when I get to the home screen, it'll just shut off and go back to the distorted image, then another boot. This will repeat 20 times if I let it. Any ideas of what might be the issue? Let me know. Thanks.
-Harris

Did it have the gingerbread bootloaders?

I really couldn't tell you. I'm just helping out a friend who said he tried to flash a ROM using Odin but screwed up. I'm pretty sure he tried to flash a SGS4G ROM, thus the soft brick.
EDIT: Just flashed the stock bootloader and no more issue. Guess I overlooked that. Thanks for the tip!

Related

[Q] Captivate Splash Screen on Vibrant Boot

Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Rareutu said:
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Click to expand...
Click to collapse
Have you tried using Odin to go back to JFD? with re partitioning checked?
Tried JK2?
The splash screen is usually controlled by the kernel, you could also just try re flashing a stock vibrant kernel to see if that works.
I'm having the same issue. Just got a used Vibrant yesterday and I'm not sure what version it was on. I downloaded a bunch of apps and all was well - it worked great. I went to bed and when I woke up this morning it was stuck on the Samsung Vibrant screen. I tried using Odin with the 512.pit and the JFD.tar but that did nothing. I then found a one-click fix, not realizing it was only for the Captivate and used it. So now my T-Mobile Vibrant is stuck on the AT&T World Phone screen.
I can get into Download mode just fine and I have re-loaded the JFD in Odin several times, including doing so with the re-partition box checked but to no avail. I'm downloading the JKT rom now, though I have little hope that that will do the trick after all I've already done.
Any suggestions?
PS - I also tried downloading the All_In_One.zip and flashing to the Original.tar, then the T959UVJI6.tar. No dice. Nothing seems to work.

Phone no longer boots past Verizon logo.

Hey all. I've been running a rooted fascinate lately. Yesterday I tried installing Cyanogenmod 6.2 beta from jt, and had no luck. I flashed back to dl09 using one of the all-in-one odin files. Now today I tried different flashing routines in another attempt to get CM6 working, but to no avail. Now my phone will no longer boot past the Verizon logo. It goes to an all-black screen, and the capacitive buttons at the bottom light up, but other than that it is completely non-functional. Is there anything I can do? I've tried odin'ing just about everything other than the stock di01 files. Any help is greatly appreciated!
Ahodson1985 said:
Hey all. I've been running a rooted fascinate lately. Yesterday I tried installing Cyanogenmod 6.2 beta from jt, and had no luck. I flashed back to dl09 using one of the all-in-one odin files. Now today I tried different flashing routines in another attempt to get CM6 working, but to no avail. Now my phone will no longer boot past the Verizon logo. It goes to an all-black screen, and the capacitive buttons at the bottom light up, but other than that it is completely non-functional. Is there anything I can do? I've tried odin'ing just about everything other than the stock di01 files. Any help is greatly appreciated!
Click to expand...
Click to collapse
Details, details, details please. The more info, the easier it is for everyone here to help. What other flashing routines did you try? Please give details on each of those so everyone has an idea of what has been done. Thanks.
Okay, apparently the last flash I did, something didn't quite take. Don't know if it didn't completely format the data partition after booting when odin was done. I flashed again and it's back to normal. I was really worried for a second that maybe I over-odin'ed my phone. Thanks anyways!
it happens sometimes, the only thing ive found that works is just re flashing it to stock or some other ROM that wipes data when it installs.

Bricked Vibrant

I got myself a bricked Vibrant from someone and trying to fix it.
I'm guessing the dude tried to flash captivate stuff on it, because the boot image is AT&T.
Anyway, I was able to odin back to stock 2.1, which seemed to make the power button work again because it would start up and show the AT&T logo but that's it.
Then I tried odin'ing a vibrant bootloader, which got me to replace the AT&T logo with a green andy logo, but same thing, stuck.
So I tried reflashing 2.1 with odin again. Now the boot logo is back to the stock i9000 > Vibrant, but then it stops here. I can't seem to be able to enter the 2e(or 3e?) stock recovery.
Any idea on what else I can try flashing to it?
Update: I tried flashing the froyo bootloader, which did get me to the stock recovery, but again - i can't seem to get this phone past this stage, doesn't boot into the OS.
wonshikee said:
I got myself a bricked Vibrant from someone and trying to fix it.
I'm guessing the dude tried to flash captivate stuff on it, because the boot image is AT&T.
Anyway, I was able to odin back to stock 2.1, which seemed to make the power button work again because it would start up and show the AT&T logo but that's it.
Then I tried odin'ing a vibrant bootloader, which got me to replace the AT&T logo with a green andy logo, but same thing, stuck.
So I tried reflashing 2.1 with odin again. Now the boot logo is back to the stock i9000 > Vibrant, but then it stops here. I can't seem to be able to enter the 2e(or 3e?) stock recovery.
Any idea on what else I can try flashing to it?
Update: I tried flashing the froyo bootloader, which did get me to the stock recovery, but again - i can't seem to get this phone past this stage, doesn't boot into the OS.
Click to expand...
Click to collapse
So what is your desired ROM after flash?
I suggest that you should flash it to LidDroid with Vibrant bootloader. From that, you can upload the phone to 2.3, 3.0 or ICS 4.0 ROM.
On mobile now so I cannot giive you the download links for needed files. If you need them, just post a reply in the thread.
Thanks, I tried LidDroid
http://forum.xda-developers.com/showthread.php?t=1058802
And flashed Froyo and GB bootloaders, nothing is working. It just shows boot screen then still shuts down.
Update: Well I'm not sure what the issue is, I was able to get it to boot to the lock screen once, but then it shut down right after. Now I can only get it back to boot image before shutting down.
The thing I noticed is that the phone gets hot really fast, so maybe it's drawing too much power somewhere and its shutting down as a protection. Also the stock batteries don't seem to work for it, just this particular battery that it came with, which the contacts on the battery are flush with the edge of the battery instead of indented like the stock ones.
What you should do is take out your sim card and external sd card if you have one, use odin to flash back to stock rom (either 2.1 or 2.2), wait for it to load up as it might take a few minutes after you see the Vibrant logo (just be patient). If you get this far and you see the operating system, flash clockwork recovery on it.
If you can get this far, let us know then we'll talk about custom roms. The main purpose now is to get it running stock, we can worry about the custom stuff later.
Here's a couple of links to help:
http://forum.xda-developers.com/showthread.php?t=848737 -- try this one first!
http://forum.xda-developers.com/showthread.php?t=954509

[Q] AT&T splash screen loop

So, SGH-177 had been rooted and installed CM7, then Unnamed, then AOKP. All were pretty buggy. We wanted to bring it back to factory (with root if possible). Not for a warranty claim, just so it would be somewhat stable.
Anyway, I found a one click ODIN solution for UCKH7 stock. I used that, it passed. then the phone just looped through the AT&T "Rethink Possible" splash screen. I tried to get into recovery mode, but it wouldn't load, so I flashed the Siyah kernel to get CWM on there. Still I can only get into download mode and the phone loops the splash screen.
I hoped that it was just taking some time to load up the first time, so I left it overnight. Still stuck on the splash screen this morning.
I spent hours on here last night and found lots of people saying that if you have access to download mode, or recovery mode, you should be able to fix it. I wasn't able to find any answers as to how.
Help?!
I've had this same problem before. what always fixes it for me is to get into the factory 3e recovery to do a reset. I know you said you couldnt get there but make sure (while the phone is off; remove battery if you have to before this) you are holding down both Volume buttons and the power button at the same time until you see the "Samsung Galaxy SII" screen, then release the buttons.
factory reset, then it should be fine.
If you can't get to recovery, read some more on here. I'm sure something is out there, but I don't know what it is.
Here are two posts that might help you out. I've been doing the same research since my "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII is due to arrive today or tomorrow.
http://forum.xda-developers.com/showthread.php?t=1451590
http://forum.xda-developers.com/showthread.php?t=1580885
Best of luck to you!
UnNamed buggy?
Out of curiosity how did you root and flash, cause that is probably one of the most stable builds we have with minor changes to stock.
Anyways good luck getting back to stock.
So, for some reason, the next time I tried booting into recovery, it worked. I got a couple errors, but then it booted up just fine. Don't know why it wouldn't get into recovery before.
Everything seems to be working as it should so far.
I'm guessing this may be why some of the threads I had seen didn't really offer a solution. Sometimes it finally works if you just hold your head right.
Thanks all!
Regarding UnNamed... I don't recall the method I used to root, it's been a long time and I've done various work on this (my wife's phone) and my Nexus One. Easy to get it confused. I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Major Wood said:
I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Click to expand...
Click to collapse
Did you also wipe cache and dalvik? May have been the problem...
I don't recall, but would be surprised if I hadn't done that
A year ago. When I first started flashing roms. I spent an entire week just reading the atrix forums and learning. I planned. I schemed. I asked questions. Through pm. And googled a LOT. Then when I had learned enough I did it. Point is....if yer not willing to have patience and learn as much as u can before u jump into this. Then its maybe not for you.
Sent from my SGH-I777 using Tapatalk 2

Interesting story regarding a Fascinate I bought off craigslist...

I bought a fascinate from good ol craiglist for a friend. When I bought it I noticed the original user had already rooted it and installed CM7.
Because I didnt know what he had done to it I decided to start from scratch and used Odin and flashed powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit
After that I flashed cwm4_fixed_for_cm7-ODIN.tar and began getting ICS on this baby (teamhacksung-ota-eng.BUILD2.zip followed by build 11 at the time).
Everything was gravy and I gave the phone to my friend who was a happy panda. Several weeks later he calls and tells me the phone is stuck in recovery, I assume he borked something so I headed over thinking I will just Nandroid the ICS ROM that I set up before I gave it to him.
Funny thing was after rebooting from the Nandroid, the phone goes back to recovery! I was a little confused but assumed that maybe the Nandroid went bad when I backed it up. So I decided to just reflash build 11 again, after the flash was successful i reboot and.... back to recovery?
At this point I was pretty confused, CWM appeared to be working but it wasnt. Nothing was working, not even flashing CM7. The only way I got it to work again was to Odin the powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit again. So that was what I did and got him back to ICS (build 13 this time).
Thinking it was a freak occurence I didnt pay it any mind, until he called me again several weeks later saying its stuck in CWM again!? So I check it out and sure enough it keeps booting to recovery and not able to nandroid or flash anything (even tho it says it does successfully).
At this point I assume its a hardware issue but dont understand what exactly, I bought another on craiglist and will swap with him and further investigate the issue.
I looked around the forums to see if anyone had a similar issue but have not seen anything like this. Anyone have any ideas??
This is most likely caused by doing the three finger reboot on the newer ICS roms. Tell them to pull the battery instead the next time their phone locks up. Also, there is boot loop breaker in the development section.
Sent from my SCH-I500 using xda premium
I assumed that as well, however my friend has no experience with these devices and would never hold down all three buttons for any reason. Both times he had reported that the phone randomly went into recovery on its own.
He could be BSing me of course, but I'll be testing it when I get it back tomorrow and see if I can recreate the scenario.
But I will be including the boot loop breaker file in the SD card and see if that at least makes this phone usable again instead of having to use ODIN every time. So thanks for that info!
Check kernel settings. Sleep Of Death, maybe?

Categories

Resources