Good day! So I have an SGH-I757M locked to bell thats been sitting in my closet for quite a while now. when I pulled it out and turned it on it would splash to SAMSUNG and then the model number ( i later found out that was the beginning splash screen) and then stall out completely. I hooked it up to ODIN and used a version of the stock bell rom found on XDA and after it loaded up I could get to the beginning of the rom, but it would become glitchy and freeze.
I figured that I could now through a custom rom on it since I had gotten past the splash screen. having put the latest CWM Philz touch i started trying to customize the phone. I had to put a new modem set on there because the one one there was a gingerbread one and the roms wouldnt take. now when I put a rom on there i feel the phone vibrate when I turn it on but its a black screen. I can still get to download mode and CWM no problem. kinda at a loss here.
Related
I just flashed the Frankin Final rom on my vibrant and all was going well until I rebooted it and now the damn thing seems to be in a boot loop of some sort, but this is different than all others I have seen cause it goes to the samsung screen like normal and then it goes to a totally different screen that is only half size and is jumbled up and not a damn thing is readable. When I plug in my USB to the computer not only is it seen by the computer but it goes to the battery icon and then back to that screwed up - half sized screen. Please someone help.
Go back into recovery and reflash the rom you had installed previously. Or do a nand backup. You did back it all up before you flashed v4 as you should have, right?
I do have it backed up from v3 but it wont even get recognized by adb nor odin. Its the strangest friggin boot loop I have ever seen. When the vibrant screen goes blank then the strange unreadable screen comes on for about 2 seconds and then the vibrant screen comes on and thats over and over. I do have a hardware locked phone so I guess I will have to screw with it when I get home. I did have it in download mode but now I can't even get it to that. Is that USB that came with the phone the only usb that can be used when getting into download mode as I had no troubles at home but I am using my USB from my nexus one at work and its all screwed up.
Did you mean DON'T have a hardware locked vibrant?
I got it about a 2 months ago so I don't know if its locked or not.
Heres what happened in detail.
I rebooted via Rom Manager into the stock recovery.
I installed packages as I have the clockworkmod recovery as update.zip in my 14G sd
I backed up my current Frankin ver3 rom
I erased all userdata and such like I should when flashing a new rom.
I installed the Frankin Final Update
I rebooted the phone like normal and the BAM.
A never ending boot loop that wont even get recognized by my computer.
I cant even plug it into charge as it won't stop bootlooping. the
battery charging icon comes up but then it goes to that funky ass
screen and back to the charging icon. when I unplug the charger it
switches to the Vibrant screen and then the messed up screen. I
really think its bricked as its gotta be the boot image that is
screwed up.
I am very sorry if I am wasting your time on this as I do know how to
properly flash a rom on a phone but this phone is not like my G1 nor
my Nexus. Its about as flaky as a phone can get in my opinion and had
I known it was this flaky I never wouldve gotten the damn thing. I
guess I am going to Tmobile and tellin them the OTA update did this as
there is no way in hell to tell. Not even the splash screen comes up.
Its really bricked.
I just wanted to say that this website and you all developers are the BEST people I have ever followed. This is the very first post I have made and I really do think I f--ked big time. No matter, what you all have done for the G1 and Nexus blows my mind. I never owned a iphone and never will and I think I might say the same about this vibrant. Getting the Nexus bricked is nearly impossible but this Vibrant is to damn confusing and with the lag fixes and crap that I am leary about goin to the store and replacing mine with a new one. Wish me luck.
You may want to try loading Eugene's Froyo Rom that does not brick. Once that is done, try and install Frankin Twiz.
I tried and when the computer won't even read the connection all is bricked. good news though, I went to the tmobile store last night and showed the guy what happened after a OTA Update. he was totally understanding about it. He said it was the white screen of death and that I will have another shipped out the following day. Thanks again for all your help and especially the moderator for putting up with my crap. You all are the bomb-diggity.
I always just boot into recovery and flash say Vibrant7 that always seems to work for me. From there I flash whatever other rom I want.
Recovery meaning
Hold down your Vol + and -
Push Power.
Actually I get scared that I might screw things up by entering recovery through clockwork ( laugh at that now huh) so I always went to the stock recovery and updated my packages with the clockwork recovery file that was named update.zip. I think I had a issue with my phone from the get go as it never would enter download mode unless I was connected to only my samsung charger and no others. I tell ya it was a strange phone and to top it all of the tmobile dude showed me a g2 they had in stock. Nice phone I tell ya but it ain't no Nexus one. Thanks again for all your help guys. Keep the little green dude alive.
I just got a new samsung vibrant and I hate the Stock UI so I wanted to root and drop a mod on it. Rooted no problem then remembered a friend with a Galaxy S phone told me he really loved this one Rom. so I snagged it and flashed it without even thinking about the fact that his phone is a Captivate.
That went awful, screen orientation, home, menu, return buttons were all screwy. But I used ODIN to return to stock as per the Development forum here in XDA. Now however, my phone says ATT World Phone as the first thing during boot sequence. Even putting on a new rom with a custom boot animation doesn't change a thing.
Any suggestions how I might go about fixing this?
TheDejos said:
I just got a new samsung vibrant and I hate the Stock UI so I wanted to root and drop a mod on it. Rooted no problem then remembered a friend with a Galaxy S phone told me he really loved this one Rom. so I snagged it and flashed it without even thinking about the fact that his phone is a Captivate.
That went awful, screen orientation, home, menu, return buttons were all screwy. But I used ODIN to return to stock as per the Development forum here in XDA. Now however, my phone says ATT World Phone as the first thing during boot sequence. Even putting on a new rom with a custom boot animation doesn't change a thing.
Any suggestions how I might go about fixing this?
Click to expand...
Click to collapse
did you ODIN fully? does the bootanimation INCLUDE the ATT world phone part?
Helpin another guy with basically the same problem...
read this ..... http://forum.xda-developers.com/showthread.php?t=849028 -To understand the basics
and
that... http://forum.xda-developers.com/showthread.php?t=848737 - To Get you back to stock..
you probably used AT&T stock file when u Odin'ed....read those (well mostly the bottom one) and it should get u back to T-Mobile stock
@xrider Can you define fully? I used the Pit file and the Tar file, attached my phone in dl mode. Clicked start and let it go till it rebooted my phone and told me it was done.
@fearless That second link is what I've been working from, I've been using the T959UVJFD.tar
Here's the exact boot up process,
1) ATT World Phone logo
2) Vibrant / Samsung logo
3) T-mobile sound and animation
4) Swirly Galaxy S logo
5) at main locked screen going through media checks and aquiring signal
something in that Captivate ROM must have really screwed up stuff....i'm thinking the playlogos file got tampered with when you flashed that Captivate ROM....but ODIN would've restored it back to normal....i'll do some more searching....
Thanks, if it helps any, this is the ROM I flashed the first time http://forum.xda-developers.com/showthread.php?t=856877
I have an international version of the Samsung GS2 that i am using on At&t. A few weeks ago i noticed that my phone would suddenly turn off while in my pocket or just left alone. Then, one time i tried turning on the phone and saw that the phone got stuck on the boot animation screen with blue markings all around it. I took out the battery and put it back in a few times and was finally able to get the phone to work.
Today, the same thing happened. The phone turned off i tried to restart it and it got stuck on the boot animation screen (Galaxy S logo). It has these blue markings around it and it can't get past it. The phone isn't rooted and i have not tampered with the system files. I've only updated it once, from 2.3.3 to 2.3.4. I tried factory resetting it but nothing changed and its still has the same problem.
I have a suspicion that it might be caused by the fact that i've dropped the phone a few times. What do you guys think could be the problem and what are my choices in getting it fixed? Would flashing a stock rom help fix the problem?
I would suggest flashing the Stock Rom Through Odin as i once has an issue with massive yellow streaks kind of like what you are getting after a flash before.
I went ahead and flashed a few roms from http://forum.xda-developers.com/showthread.php?t=1075278. The flashing worked fine but it still can't get past the bootup screen and the blue marks are still there.
Would calling Samsung and asking for support get me anywhere?
How long did you wait after flashing the rom? The worst way you could have messed up is by choosing the wrong files in Odin. Did u check that again?
Sent from my GT-I9100 using xda premium
I flashed the rom and rebooted and saw that it was still the same. Does it matter which rom i chose? I tried two or three different roms from the thread. I though they were all stock roms...
ok so i was running 4.0.3 with no problem until i decided to update to 4.1.2, so after updated finished with no errors i booted the device
the galaxy s2 logo appears the BLACK SCREEN
no boot animation
what i have tried
return to 4.0.3
wipe data
use custom recovery that matches the os version
us custom recovery to format all the partitions
flash using pit file
different version of odin
and thats pretty much all
now even when i return to 4.0.3 it stil wont boot, please help
If the phone won't boot & PC/phone don't recognise each other in Odin, you're pretty much boned. Possibly JTAG, if not service centre (or local mobile shop if no warranty).
it goes into download mode, and recovery, and it boots up, but after the SGS2 logo i get a black screen on any firmware, even gingerbread
and i can still flash using odin and cwm
If it were me, I'd keep trying Odin flashes (even trying random stock roms); often in these situations the first 6 flashes don't work but the 15th actually fixes the problem (I'm using these numbers as an example) for whatever reason.
That's the only way you're fixing it, unless the NAND is borked, which you won't be able to fix. Try Hopper8's 'Odin won't work' thread, there's stuff in there which might help.
Simply_Android said:
ok so i was running 4.0.3 with no problem until i decided to update to 4.1.2, so after updated finished with no errors i booted the device
the galaxy s2 logo appears the BLACK SCREEN
no boot animation
what i have tried
return to 4.0.3
wipe data
use custom recovery that matches the os version
us custom recovery to format all the partitions
flash using pit file
different version of odin
and thats pretty much all
now even when i return to 4.0.3 it stil wont boot, please help
Click to expand...
Click to collapse
Hey this is exactly what happened to my phone, I flased stock 4.1.2, it was working fine but somehow freezing randomly. So I installed latest cwm hoping to fix the freezing problem, the boot animation won't show up after the logo, though I can hear from the speaker sound of the boot animation, and the screen won't seem like turning on (touch buttons not lighting up). Any luck on fixing this problem?
it turns out its was the usb data cable connector, surprised. i dont even know what one has to do with the other, anyways, i had it replaced and it works perfectly
Simply_Android said:
it turns out its was the usb data cable connector, surprised. i dont even know what one has to do with the other, anyways, i had it replaced and it works perfectly
Click to expand...
Click to collapse
Well I re-flashed the stock android 4.1.2 using odin, and everything got back to normal, the screen is working again. Though the phone is still freezing randomly, even after a couple of minutes after booting the phone. However I'm glad to get my phone with the screen working again!
Ok, first up I know there are many posts out there about this issue because I've looked at most of them and tried them so please bear with me.
I have a Samsung Galaxy GT-N8010, about 4 years old. I have never rooted or done anything to the firmware in all that time except OTA updates & the occasional factory reset to clean things up.
Couple of months ago it was on, i had been using it and put it down and when i came back it was on the Samsung logo screen and has been ever since.
Since i could get into the download page even though it was already bricked I figured i'd try rooting to see if i could fix the problem. Now possibly i should have attempted to get into recovery mode first but I attempted to install CWM (as per posts here). It appeared to install fine. But no recovery partition, screen blinks and goes back to the logo.
I've tried flashing stock firmware, TWRP, CWM - all 'appear' to install successfully according to ODIN, but nothing changes, still stuck on the logo screen.
So does this sound like a hardware issue or am i missing something? The Tab A 10.1 with s-pen looks great, would be a perfect replacement, but is not available in NL
Thanks guys (& gals)
Darren