Hi everyone, Apologies for the message I'm about to write as I'm very new to Samsung and not overly sure what to do here.
Basically I'm use to having a simple Jailbroken iPhone and got told this was the same when rooted, me and a friend of mine THOUGHT we rooted my edge, I ended up factory restoring it back to normal and setting all my phone up again.
But since then, I've had the 150.49mb Update come up a few times, It downloads fine but when I go to install it, It restarts my phone, then It comes up with the blue screen with the Galaxy & Android Logo for about 15 seconds.. Then the Yellow Triangle appears on top of it, and the Android logo looks like it dies lol
Does anyone know what I have to do to update my phone? I really shouldn't have touched my phone in the first place as I wasn't too sure what I was doing, I only done it to get this Certain UI Theme that didn't even work anyway!
Sorry to be a pain, very new to Samsung like I said. I'm learning as quick as possible
Thanks alot,
Courtney
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
Hey guys, so I just updated my att galaxy s2 via kies to android ICS however after that I've ran into some problems.
After updating however I encountered a period where the screen went black and the phone kinda just died on me. After restarting I began to encounter some problems. For some reason, whenever the phone goes to sleep and and then wakes up, my screen gets flipped upside down and the screen gets really bright. Despite that, I still have to press the screen like usual. Which means that if the call button is at the top after flipping, I still have to press the bottom of my screen. Also the screen isn't perfectly flipped and there is space above the top bar.
However, the phone does work fine on bootup, and only fails after it sleeps. Also, very recently my phone just went through a screen repair after the screen cracked under the glass, but otherwise that I have no clue what's going on.
Is this just a poor repair and a hardware problem or is their another problem here?
Also I've tried a factory reset and that didn't help.
Thanks for any help you can give.
(Hopefully I got the right board)
Kovath said:
(Hopefully I got the right board)
Click to expand...
Click to collapse
considering this board is all about CUSTOMIZING devices... I dunno about that. Maybe try the AT&T site?
Maybe one of our divas will be kind enough to help anyway.
Yes, I mean divas, also referred to around here as devs. I <3 u all!
Clay
Sent from my SGH-I777 using XDA
Yeah I kinda got that gist =P
but, after searching through the web, there weren't really a lot of sites that I came across detailing about my problem, but this was one of the sites that came up a lot so I was just hoping if anybody, just anybody could help me out with this.
Kovath said:
Hey guys, so I just updated my att galaxy s2 via kies to android ICS however after that I've ran into some problems.
After updating however I encountered a period where the screen went black and the phone kinda just died on me. After restarting I began to encounter some problems. For some reason, whenever the phone goes to sleep and and then wakes up, my screen gets flipped upside down and the screen gets really bright. Despite that, I still have to press the screen like usual. Which means that if the call button is at the top after flipping, I still have to press the bottom of my screen. Also the screen isn't perfectly flipped and there is space above the top bar.
However, the phone does work fine on bootup, and only fails after it sleeps. Also, very recently my phone just went through a screen repair after the screen cracked under the glass, but otherwise that I have no clue what's going on.
Is this just a poor repair and a hardware problem or is their another problem here?
Also I've tried a factory reset and that didn't help.
Thanks for any help you can give.
(Hopefully I got the right board)
Click to expand...
Click to collapse
There are alot of things that could go wrong when flashing ROMs.
All of the custom ROMs here have built in safeguards which allow users to recover from issues involved with flashing. The same cannot be said about stock builds.
Unfortunately, your options are limited if you're going to stay stock. You can either try a factory reset and re-installing the update via KIES or you can call AT&T. That's pretty much it.
Personally, i'd Mobile Odin a rooted package with CWM and start flashing some of the wonderful work the developers have graciously allowed us to partake.
BROKKANIC said:
Personally, i'd Mobile Odin a rooted package with CWM and start flashing some of the wonderful work the developers have graciously allowed us to partake.
Click to expand...
Click to collapse
OP, I agree with the sentiment here, but you can't use mobile odin until your are already rooted. One option you could follow the guide linked in my signature to root the phone and go from there.
My personal suggest is that if you're running stock ROM, updating an official stock ROM and having problem, I call the provider for help.
My download and install went fine but I incounterd some unusual problems afterwards. My phone doesn't always keep a data signal while browsing the internet and a phone reboot makes it return. Setting browsers home to Google instead of default AT&T doesn't stick. I also had few dropped calls and very low signal bars in status bar at my house which gingerbread gave me full ones.
same here
Kovath said:
Hey guys, so I just updated my att galaxy s2 via kies to android ICS however after that I've ran into some problems.
After updating however I encountered a period where the screen went black and the phone kinda just died on me. After restarting I began to encounter some problems. For some reason, whenever the phone goes to sleep and and then wakes up, my screen gets flipped upside down and the screen gets really bright. Despite that, I still have to press the screen like usual. Which means that if the call button is at the top after flipping, I still have to press the bottom of my screen. Also the screen isn't perfectly flipped and there is space above the top bar.
However, the phone does work fine on bootup, and only fails after it sleeps. Also, very recently my phone just went through a screen repair after the screen cracked under the glass, but otherwise that I have no clue what's going on.
Is this just a poor repair and a hardware problem or is their another problem here?
Also I've tried a factory reset and that didn't help.
Thanks for any help you can give.
(Hopefully I got the right board)
Click to expand...
Click to collapse
I just got my screen replaced and have the exact same problem, factory reset did not help either.
Did you managed to fix it?
Any help would be greatly appreciated
First off, I'd like to say my S2 is the Virgin Mobile version (model i9210) so I'm not sure if it's okay for me to post this in this forum or not. Feel free to move it where it should be, I won't be offended.
Edit: Originally had posted this in the Samsung Galaxy S2 forum, but it was nicely moved to this forum in hopes that it would be seen more~ So to clarify, my phone is the Virgin Mobile Samsung Galaxy S2, running Android 4.1.2, model number SPH-D710.
The ROM I have is BiftorROM-V8-JB-XWLSN-NoWipe.
Onward. This is my first Samsung phone AND my first Galaxy, and when I decided to root my phone, I had no idea how much different it would be from my past phones. How I didn't completely brick this phone, is nothing short of a miracle. I had trouble with some ROMs so someone eventually linked me to a Sprint stock ROM, saying it was compatible with my phone.
Since then I've been using that ROM, despite having a Virgin Mobile phone, with no problem. Recently I noticed an app I use (SD Maid) was listing my phone as unrooted. It was weird but I ignored it, because the app still worked. Even later, I noticed other apps that require root access were not working correctly, so I decided to download a root checker.
Status: Unrooted
Well, then. I'm not sure how this happened, or what's going on, but I figured again, it was no big deal because my ROM was running perfectly and I had no desire to change my ROM or anything else soon. Last night my phone started acting completely different. Lagging like crazy, and when I tried to unlock my phone, it would take a good 15 seconds just for the screen to turn on and my lock screen to start functioning normally. Then another 20 seconds or so for the screen to register my touch and actually unlock my phone. I tried disabling all lockers, but my screen would just turn black and I would still have to wait.
A friend suggested that I simply go through the process of rooting as though my phone really were unrooted and just hope that fixes it, but I'm not sure if that would be a good idea. If my phone wasn't operating so slowly this wouldn't be as big of a problem, but it is, and I'm pretty afraid that I'll mess my phone up somehow.
I once found a forum with the topic the same as mine but I haven't been able to find it since, so I'm hoping someone here could point me in the right direction. Do I go through the root process, maybe try just reflashing my current ROM? I've also thought about just doing a system restore on my phone and see if that helps. Thanks in advance.
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk
Hello, all! I recently got a brand new Samsung Galaxy S7 Edge AT&T Model (SM-935A) from Best Buy, and I somehow decided to root it (Me being an iPhone user, I don't know anything about Android). Anyway, I ended up rooting the phone, and later, a Samsung Update popped up. Right after I denied it, my main apps (Caller ID Name, and Google Play Store) began to crash and fail to start up at all. Nothing was working as all apps were crashing. When I pushed restart on the phone, it booted through the 'custom' logo, then to the AT&T logo, where it stayed like that for hours. I noticed how hot the phone turned and put it in the refrigerator (After all, the phone is waterproof, right? ;_. I searched on the internet, and there I found that I could full-wipe the phone out, which seemed reasonable to me, as I had not completely decked out the phone, yet. So after full-resetting the phone, I still saw the 'custom' logo, and all of my content was gone. As usual, I downloaded, and put back all of my accounts, and soon enough, another update came round, and my phone broke down... Again. So I repeated that step of wiping out my phone again. This happened about 3 more times until I decided to flash-fix my phone, or something akin to that term. I downloaded the required files of ODIN and software from this website, but instead, it still failed with the 'ODIN protocol version failed!' error. I do not understand this issue nor do I know how to fix it. I hear that XDA is the world's best developers at Android or something so I have come here as a FINAL RESORT! Thank you for reading, and to whoever may know, please help! (If you need pictures, I will be happy to post them!)