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
Related
Hey Com,
I got some problems with my u20i x10 Mini Pro. It was stuck in some boot loop like 1 month ago and I tried to reflash it with SEUS and this flaher App thing thousands of times. I did not have a little bit of success so i gave it up 3 weeks ago. Since then i had my phone laying under my desk without the battery. Today I decided to try it again and, GOD KNOWS WHY, it started up normally. So i finished the startup wizard and everything worked fine. Then i rooted it with superoneclick (my phone had A.0.6 FW), rebooted and everything worked just fine. Then I wanted to sign in to my wireless network and for some reason it did not work, but whatever. After like half an hour my phone started lagging really hard and suddenly the screen went black. I tried to push all the buttons and the screen went bright for a very little while and went black again. And this point it was like it was turned off. So i tried to turn it on and, guess what, its stuck in a boot loop! YAY! Now my phone is lying in front of me and all i can see is the only white SONY ERICSSON logo.
Seriously what has happened? Anyone knows how to fix that?
Thanks in advance, Martin.
UPDATE:
Now I am facing a new problem. My device turns "on", I can see the white SE logo, then the screen goes black but for some odd reason the touchscreen is reacting at the lower left and right parts of the screen. I can even dial a number (i hear the beeps) when I press twice at the lower left corner and then tapping at the display. But well, i guess thats not how the phone should work. So did any one also face this problem? Do you have a solution for that?
Anyway, Thanks in advance.
Kind Regards, Martin.
thing is..
Your posting skills are zero..
Using profanity is one thing, but using it in the topic? Surely a 99% ignore from most members!
Id go back and edit your posting if you are actually capable of using better language!
Nochances,
Wow, you must be one big loser, your first post is to criticise someone the way the lay out a question script.
nochances said:
thing is..
Your posting skills are zero..
Using profanity is one thing, but using it in the topic? Surely a 99% ignore from most members!
Id go back and edit your posting if you are actually capable of using better language!
Click to expand...
Click to collapse
I'm sorry if i offended you in any way but at the time posting this i was really stressed out. And i apologize for my bad English, I'm not a native English speaker since I'm from Austria.
Have a nice Day, Martin.
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
Hi People of the world! As you can see im new to here so yeah i just might be in the wrong section...
So, I just got my shiny android a week ago, and know it sits on my desk, lifeless, like a brick. Like literally its dead! I don't know if I can fix it or the BIOS (if theres one in Samsung Galaxies) is fried, or maybe the motherboard is fried, or the battery overcharged, etc. But I just cant do anything! I'm totally out of ideas!
Heres the problem, I first rooted my android successfully, and played around with my android a while. But as you expect I just coudn't wait for the jelly bean update! So, I desided I would give a try to take the Russian firmware instead. That was already a bad idea, but I read on some threads that it would work fine, so I downloaded one from Sammobile.com. The real mistake? I downloaded the wrong phone. I own a Samsung Galaxy S Advance NFC Version;GT-I9070P The one I downloaded was UnNFC version; GT-I9070. Well, I didn't realize that, and proceeded with entering download mode and eventually flashing the PDA file from Sammobile with ODIN. So I pressed start. It started the process, and after 5 min it said in blue: RESET. I saw the phone rebooting. Now, another big mistake: I started touching the power button, which I shouldn't have done. Then, instead of waiting, as soon as seeing the thing wasnt booting, I took out the battery and unplugged the USB cable. Then after a while the PASS appeared in green. So it went successfully? NONONO Now it wont boot! More specifically, it wont TURN ON! like it wont whow any sign of life. As if it had no battery or USB.
Today I discovered, If I hold Vol UP+Power+Home when its connected to my PC, it makes the beep, shows that it failed to install the driver for "U8500 USB ROM" What the (*^&(&%*(&^&* is that??? Also, in 5 seconds, the device disappears, meaning that I must hold the button combo for another 20 seconds.
So, I've got no connectivity to ODIN, nor Kies, and I cant go into download mode, nor recovery mode.
Any Help?
Pleeaase if you can help youre a super god of androids!
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
MikeSome1 said:
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
Click to expand...
Click to collapse
Exactly. Nothing at all.
The only evidence that its not fried is that the computer detects it as U8500 USB ROM for 5 seconds whenever i hold the power button or any combination. Nothing on the phone though.
Hey
Hey man got the same problem... I have put mine to a service center i will see what the'll do
pafiking said:
Hey man got the same problem... I have put mine to a service center i will see what the'll do
Click to expand...
Click to collapse
Yeah i think I should take it to service too, but I want to try at least first:cyclops:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Lynnfield4000 said:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Click to expand...
Click to collapse
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
Please help! I also bricked my Samsung S Advance I9070P after downgrading from JB to GB, since JB was updated for India I9070...but the phone bricked after downgrade. Everything was successful and it had auto-rebooted after the downgrade and stuck with Start up screen. When I removed battery and tried again..it bricked! No recovery mode, No download mode, no power on.
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
So you find any solution? I have a similar problem right now.
Hi all,
Got a Rogers HTC one off of craigslist a few months ago which was already flashed to stock 4.3... worked great. Just yesterday I got a prompt on my phone asking me if I wanted to update to 4.4. "Sure, it cant be too hard?" I thought. Maybe its that I'm novice, but it didn't end up looking so simple. Soon the device asked me if I wanted to continue, saying this is not reversible so I said yes, then another message, I said yes again.. the device then turned off, then back on and there was a black screen with white letters and a loading bar.. when it finished i think it asked me another question about backing up the ruu or something like that and I said no... the phone turned off and tried to reboot, first the white with HTC quietly brilliant, then the google logo for half a second and then right to a light plue pixelated screen with little lines in it.. every time I hold the power button to turn off it turns back on and same thing. Is this whats called a boot loop? Did I do something wrong? At one point I tried turning off and then holding power and volume buttons to get into bootloader and it worked.. I didn't really know what to do so I just told it to reboot and it did but with same blue screen. I've been reading a lot of threads on here but I didn't see anything quite like this. Sorry for the long post. I'd really appreciate it if someone would help me out here.
Thank you.
Hi all, thanks in advance for any assistance you can provide me. I have looked for similar posts but could not find any (maybe I just don't know what my issue is called). I bought an HTC EVO 4g LTE from a friend that had put meanbean on it (I assume it was the latest). I went through all sorts of steps loading twrp and getting s-off and whatever else I needed to do to load cyanogenmod 10.2. I was able to do this fine but the gapps I loaded would not show. I tried it together and separately and nothing would work. So I loaded (I believe) 3.16.651.3_stock_rooted_odex_CPTB.zip so that I could use my phone again with the gapps while I was waiting for some assistance on the cyanogenmod forums, which never came unfortunately. Everything was fine for about the past 10 days.
Today I used my phone all day and had no problems (extra info: I installed one app to access my bank info which went fine), but hours later and all of a sudden my screen basically got stuck. It looks like millions of randomly chosen colors for each pixel. The screen will turn on and off if I hit the top button (or let the display "timeout"), and I can hear the tones when I press the up and down volume buttons. This is telling me it's not bricked, but it is completely useless to me as is. When I reboot the phone, I don't see anything on the screen until the colors come up (which is after the vibration during the bootup sprint screen as far as I know). I was able to get fastboot to see it once but haven't been able to get back into the bootloader (there's nothing on the screen so I don't know what I'm doing).
Basically, nothing on my screen while it is booting up until it gets to the point where my laptop detects the USB connection, and the crazy colors comes on. BTW, as random as it seems, it's the same colors in the same exact position each time and it never changes. I haven't tried flashing any roms with fastboot because it seems my issues is bigger than a rom... I can't even see anything when I had it in the bootloader... This is my only phone and I use it every day. I'm really quite desperate and could use any and all help you're willing to provide. I've attached a zip with a picture of my screen so you all can see what I'm talking about. Thanks in advance...
just an update, got my laptop to see my device with fastboot so I'm gonna leave it hooked up. Could really use some advice on how to proceed because I'm at a loss. Thanks...
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
So can you say with any certainty that my issue is not due to the programming on the phone?
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
I just thought I would see a similar screen in the bootloader if it were a physical hardware issue.
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Magnum_Enforcer said:
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Click to expand...
Click to collapse
Okay great thanks for the reply... the touchscreen portion of the phone still works (I was able to answer a phone call today even though I couldn't see where I was touching). I saw some videos online so I'll watch carefully and order a new screen/digitizer or whatever. Thanks again