Has anyone else experienced a screen issue where a line all the way across the screen goes white, with some odd colors blended in? It also blinks from time to time.
If I press the power to turn off the screen and then turn it on again, it comes back normal.
I have only seen this happen twice and its been while temp rooting the phone? I cant imagine that this has anything to do with it - So Im probably going to return it to the store and get a replacement.....
PensFan66 said:
Has anyone else experienced a screen issue where a line all the way across the screen goes white, with some odd colors blended in? It also blinks from time to time.
If I press the power to turn off the screen and then turn it on again, it comes back normal.
I have only seen this happen twice and its been while temp rooting the phone? I cant imagine that this has anything to do with it - So Im probably going to return it to the store and get a replacement.....
Click to expand...
Click to collapse
has something to do with the exploit, mine does it too, only while running the root though...
WOW! I thought for sure I was just nuts thinking it was the exploit causing the issue ... I would rather not take the phone back, I have way too much work in it from setups/etc ....
Wonder if we can get more confirmations
Mine too, at the bottom of the screen multi color single line
My friends does this and he has never done any messing around with root or anything.
Sent from my PG86100 using Tapatalk
Thanks for the replies, so it happened to someone who didnt root - Now I really need to decide if I want to deal with taking it back or not ... Im not sure they even will since I cant reproduce it at will.
**EDIT** OK, So I can reproduce this 100% of the time on this phone. Im using the newest Fre3vo assist tool (Easy Fre3vo) and during the ADB portion and the exploit that line appears. If I Control-C the script, the line goes away - and it also goes away after it completes the script. I started the script again and it comes back, etc, etc .... So I feel better thats its not the phone in this case - ADB and rooting does that. I have no idea why ...
i believe the temp root process does something w/ a 0 degree rotation of the screen. pretty sure that's what causing it. don't worry about it and go enjoy your temp root!
shad0w77 said:
i believe the temp root process does something w/ a 0 degree rotation of the screen. pretty sure that's what causing it. don't worry about it and go enjoy your temp root!
Click to expand...
Click to collapse
Thanks ... Its nice to know its not the phone ....
mine was doing this before the root i thought it was just a jacked up widget.
The root exploit was discovered through bug in the Qualcomm video drivers so what you are seeing could be a by-product of this.
Related
My Atrix 4g was working fine and then I set it off the the side while I worked on some homework and when I came back and tried to unlock it, nothing happened, the screen remained black although I could flick the volume up and down switch and get a vibration and a sound, it seemed to me like the device was still on and working just the screen was black. I pulled the battery and when I put it back the phone refused to boot and showed a red LED. I waited 5 min and pulled the battery again and this time the phone booted up perfectly and is still working right now, is this something I should be worried about? Should I bring it back to the store for an exchange?
Definitely bring it back for an exchange
neer2005 said:
Definitely bring it back for an exchange
Click to expand...
Click to collapse
Do you happen to know the exchange policy at AT&T? I have no warranty, but I've only had it for a week or so.
Also how do you know its just not a small software glitch or something that is insignificant and was a one time thing? Or do you think I should bring it back just in case.
m0n3y0n7r335 said:
Do you happen to know the exchange policy at AT&T? I have no warranty, but I've only had it for a week or so.
Also how do you know its just not a small software glitch or something that is insignificant and was a one time thing? Or do you think I should bring it back just in case.
Click to expand...
Click to collapse
If you bought it from AT&T then you have 30 days to return/exchange it. Tell them there is a software issue where it forces your phone to turn off. To be safe, you could call their corporate customer service at "611" and tell them the situation and they will note your account about the situation that way the reps in the store cannot turn you away.
live4nyy said:
If you bought it from AT&T then you have 30 days to return/exchange it. Tell them there is a software issue where it forces your phone to turn off. To be safe, you could call their corporate customer service at "611" and tell them the situation and they will note your account about the situation that way the reps in the store cannot turn you away.
Click to expand...
Click to collapse
What if I bought it from RadioShack though? They had a sale where it was only $150.. xD
Btw mine is rooted and everything, how do they check for root anyways? And in order for me to exchange it I'm guessing I have to factory reset, would that undo the root?
m0n3y0n7r335 said:
What if I bought it from RadioShack though? They had a sale where it was only $150.. xD
Btw mine is rooted and everything, how do they check for root anyways? And in order for me to exchange it I'm guessing I have to factory reset, would that undo the root?
Click to expand...
Click to collapse
Radioshack should have a similar policy. You should be able to check it online.
No, a restore will NOT remove root. Which root method did you use? I believe SOC and aRoot both have unroot options. I had to return my first Atrix as well and I used Root Explorer to uninstall SU before I ran the unroot script to make sure it would be removed.
I returned my bricked atrix to radio crap and they swapped no problem
live4nyy said:
Radioshack should have a similar policy. You should be able to check it online.
No, a restore will NOT remove root. Which root method did you use? I believe SOC and aRoot both have unroot options. I had to return my first Atrix as well and I used Root Explorer to uninstall SU before I ran the unroot script to make sure it would be removed.
Click to expand...
Click to collapse
I used aRoot, out of curiosity what was wrong with your first Atrix?
I did a quick google and no one seemed to have experienced the problem that I had with the blank screen, although there seem to be no other issues and its snappy as usual. If I decided just to keep this Atrix and not go through the hassle of returning and then downloading everything and setting my theme back up and a million other personalization things I did, do you think I would regret it later?
Oh and do you think it would have anything to do with the fact I dropped my phone? I was just chilling in class and it fell out of my pocket. Lol it was like a 2 foot drop onto tile face first, although there are no visible damages aside from a scratch in the corner thats minuscule and took me like 5 min to find.
Also, the issue didn't occur until like a couple hours after I dropped it.
m0n3y0n7r335 said:
I used aRoot, out of curiosity what was wrong with your first Atrix?
I did a quick google and no one seemed to have experienced the problem that I had with the blank screen, although there seem to be no other issues and its snappy as usual. If I decided just to keep this Atrix and not go through the hassle of returning and then downloading everything and setting my theme back up and a million other personalization things I did, do you think I would regret it later?
Oh and do you think it would have anything to do with the fact I dropped my phone? I was just chilling in class and it fell out of my pocket. Lol it was like a 2 foot drop onto tile face first, although there are no visible damages aside from a scratch in the corner thats minuscule and took me like 5 min to find.
Also, the issue didn't occur until like a couple hours after I dropped it.
Click to expand...
Click to collapse
I brought mine back because of software issues like the battery monitor displaying the phone as charging even though it was unplugged, screen brightness was changing even though I had the auto turned off, little things that I haven't experienced on my second phone.
With yours, if you feel comfortable enough to hold onto it for awhile longer I don't see any harm in that. Radioshack gives you 30 days. There have been random reboot issues on some of the Atrix's so it might not be anything serious. I've had a couple issues with the screen freezing on me, which what could have happened on yours.
live4nyy said:
I brought mine back because of software issues like the battery monitor displaying the phone as charging even though it was unplugged, screen brightness was changing even though I had the auto turned off, little things that I haven't experienced on my second phone.
With yours, if you feel comfortable enough to hold onto it for awhile longer I don't see any harm in that. Radioshack gives you 30 days. There have been random reboot issues on some of the Atrix's so it might not be anything serious. I've had a couple issues with the screen freezing on me, which what could have happened on yours.
Click to expand...
Click to collapse
Well mine didn't randomly reboot, and the screen didn't freeze, it just blanked for awhile, I don't think its serious enough to constitute my phone as a "lemon". I'll probably end up holding on to it and seeing if anything else happens and if not then just keep it. Thanks for all the help though! :]
And if anyone else has experienced this issue or something similar, it would be awesome if you could share your experience.
I have a very unusual problem that i just googled and have not come across. I woke up this morning and found that my display wasn't turning on, as if the phone was off. I had encountered this problem before and a battery pull worked fine. Im on MR2 btw... but this issue is different, my diplay is completely dead, D-E-D, dead... after the battery pull i held the power button to start up again but all i got was the vibration on start up, no lcd screen response.
i know the issue is the lcd screen and i can replace it myself, if it had just been that. i have the total protection plan set up and can replace it, but my only issue is that the TB is rooted. upon fixing it they will realize it once the CM7 animation comes up. i need advice on how to handle this situation.
i cant bootload neither, display is completely off... i can hear sound going on so i know its on. Help please!
i had CM7 rc1.2, mr2 radio, clocked up to 1.6.. i was on bamf for a while but switched to cm7 2 days ago.
You cant boot into recovery mode? Try booting into hboot see if the screen works. If it doesnt just take it to VZW and when they fix it be like "What the heck! You guys rooted my phone?!"
alluzzion2o9 said:
I have a very unusual problem that i just googled and have not come across. I woke up this morning and found that my display wasn't turning on, as if the phone was off. I had encountered this problem before and a battery pull worked fine. Im on MR2 btw... but this issue is different, my diplay is completely dead, D-E-D, dead... after the battery pull i held the power button to start up again but all i got was the vibration on start up, no lcd screen response.
i know the issue is the lcd screen and i can replace it myself, if it had just been that. i have the total protection plan set up and can replace it, but my only issue is that the TB is rooted. upon fixing it they will realize it once the CM7 animation comes up. i need advice on how to handle this situation.
i cant bootload neither, display is completely off... i can hear sound going on so i know its on. Help please!
i had CM7 rc1.2, mr2 radio, clocked up to 1.6.. i was on bamf for a while but switched to cm7 2 days ago.
Click to expand...
Click to collapse
Have you tried running a RUU (ROM update utility) to return your phone to stock? Download one of the .exe RUU's (not the zip) to your computer from this page http://dougpiston.com/ThunderBolt/RUU/ and run it from your computer with your phone plugged in and turned on. With any luck it will return your phone to stock.
i cannot multi quote for $hit, anyways no i cannot get into bootloader because my display wouldn't boot up... but out of sheer luck i finally got it to work!!! and heres what i found! the screen has water damage! then i remembered this morning before getting my phone i tipped over a cup of tea my son left there. im lucky the phone even boots up! i guess facing the phone downwards saved my phone but not the screen... ill hit up VWM and see what they have to say.
nucher said:
Have you tried running a RUU (ROM update utility) to return your phone to stock? Download one of the .exe RUU's (not the zip) to your computer from this page http://dougpiston.com/ThunderBolt/RUU/ and run it from your computer with your phone plugged in and turned on. With any luck it will return your phone to stock.
Click to expand...
Click to collapse
does it matter which one i pick? of the RUU i mean?
[edit]
nevermind i got it, the process seems similar to updating touchpro2, half way through updating.. thanks man! although i got my phone working im going to be bothered with the watered down screen. i can simply open it up and clean it but that'll waste my total protection plan i have with VWM =P
alluzzion2o9 said:
i cannot multi quote for $hit, anyways no i cannot get into bootloader because my display wouldn't boot up... but out of sheer luck i finally got it to work!!! and heres what i found! the screen has water damage! then i remembered this morning before getting my phone i tipped over a cup of tea my son left there. im lucky the phone even boots up! i guess facing the phone downwards saved my phone but not the screen... ill hit up VWM and see what they have to say.
does it matter which one i pick? of the RUU i mean?
[edit]
nevermind i got it, the process seems similar to updating touchpro2, half way through updating.. thanks man! although i got my phone working im going to be bothered with the watered down screen. i can simply open it up and clean it but that'll waste my total protection plan i have with VWM =P
Click to expand...
Click to collapse
Glad you were able to get the RUU to work. I didn't specify one RUU because I figured you would use any one of them just to get your phone to stock, then you can take it to Verizon or mail it to asurion for replacement.
nucher said:
Glad you were able to get the RUU to work. I didn't specify one RUU because I figured you would use any one of them just to get your phone to stock, then you can take it to Verizon or mail it to asurion for replacement.
Click to expand...
Click to collapse
ye i already set up the order... cost $99 in deductables or some $hit... hopefuly it will be here tues/wednes.. thanks a whole lot for the help
alluzzion2o9 said:
ye i already set up the order... cost $99 in deductables or some $hit... hopefuly it will be here tues/wednes.. thanks a whole lot for the help
Click to expand...
Click to collapse
You're welcome. When you get the new phone don't hesitate to put CM 7 back on after you're rooted. I feel its they most flexible and up to date ROM you can put on an Android phone.
nucher said:
You're welcome. When you get the new phone don't hesitate to put CM 7 back on after you're rooted. I feel its they most flexible and up to date ROM you can put on an Android phone.
Click to expand...
Click to collapse
will come in tomorrow, i have 15 days to mail my damaged one or its 300 ;P. CM has always been my fav. its super fast. my favorite part is how fast booting up can be, unlike bamf sense 3.0. only problem i had with cm7 was that when it rings it rings once.. and when i get a voicemail notification it goes ape $hit.
other than that its still my fav.
alluzzion2o9 said:
will come in tomorrow, i have 15 days to mail my damaged one or its 300 ;P. CM has always been my fav. its super fast. my favorite part is how fast booting up can be, unlike bamf sense 3.0. only problem i had with cm7 was that when it rings it rings once.. and when i get a voicemail notification it goes ape $hit.
other than that its still my fav.
Click to expand...
Click to collapse
I had the same problem with the phone only ringing once, I changed the ringtone from Digital Phone to Bell Phone and that solved my problem. I read that certain ringtones don't work properly with CM7 and there is fix in the next update.
Hello,
I'm looking to figure out if anybody has found a software fix for the issue of screen backlight flickering on our phones. I've hunted down some threads through Google, but found nothing except 'go replace your phone and hope for the best.'
As a reminder, when grays are displayed onscreen (as in Play store loading screen), it seems as though the screen refresh rate can't 'keep up' with those colors. To me, the problem is even more noticeable when viewing pictures in the Gallery - seriously, I feel like I'm watching one of those 3D movies, and my eyes and head start to hurt! It's just enough that it drives me crazy, but other people do also seem to notice it, so I'm not just ACTUALLY going nuts. This problem showed up on stock before I rooted and went MeanROM, so I know it's not my fault. The problem is worse at higher brightness levels, and persists even with manual brightness settings on.
So yeah, anyone else have this problem? Any stories of successfully resolving it? I'm still within my Sprint 30-day replacement period, but already got 3rd-party insurance on my phone, so it'll be interesting to try to get a replacement phone insured under the same policy...
Yep have had this problem for a while now and actually got tired of it this morning and will take my phone back for a replacement whenever I have time! Gets so annoying especially noticing it in the littlest of places.
Sent from my EVO using xda premium
Hmm.. I never really noticed it until you pointed it out..
Sent from my EVO using xda app-developers app
drmclove69 said:
Yep have had this problem for a while now and actually got tired of it this morning and will take my phone back for a replacement whenever I have time! Gets so annoying especially noticing it in the littlest of places.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Whoa, please let me know if your replacement is any better after a day or two of playing with it. I will probably do the same if there's an improvement.
Was on meanROM 4.2 until today, when I relocked and unrooted in preparation for getting a replacement at Sprint (I'm still within my 30 days). I was going to replace the phone because of this exact problem - a weird, barely-perceptible strobe effect when viewing grays and looking at certain photos in the gallery. And now - after all the hard work of finding an RUU for 2.13, figuring out the android SDK, learning how to use ADB (not to mention the whole initial unlock/twrp bootloader shebang) - I find that the screen flicker has dropped off. OK, sometimes there's an extremely brief (~150ms) hint of it all on a gray screen, but absolutely nothing compared to the headache that it was before. I'd recommend completely unrooting/relocking your phone and pushing the correct RUU. QBking77's the best for it - look up his youtube vids on android sdk intstallation/usage, then relocking your bootloader, then unrooting/installing an RUU. Remember to clear your Google Wallet first, and set your fastboot to off (under power settings). After relocking your bootloader, you might notice that you cannot boot past it. That's fine; just push your RUU with fastboot USB. You'll know what I mean after watching the vids.
After all that, if your results were like mine, you'll know it actually had something to do with your custom ROM. I have no idea how that is possible, as I seem to recall a flickering in my stock ROM, too, but I guess I was wrong. Perhaps it has something to do with my charge status, and I'll see the issue come back... who knows?
For relocking/unrooting
Step 1: Android SDK setup
Step 2: Relock the bootloader
Step 3: Unroot/Push RUU (for some reason, I had to go straight to pushing RUU from step 2 without booting into any ROM).
From all my scouring online, though, I've noticed that the people most consistently hammered with this problem (especially on screens other than photos in the Gallery or gray colors in the battery histogram of power settings) have build issues with their screens. These include light leak seeming to emanate in bands fanning up out of the home 'button' or graphical issues. These people usually report a fix to the problem once they receive a replacement; the ones with my problems typically complained of having received up to 3 (!) phones in a row with the maddening flicker, suggesting a software issue. It seems that the HTC One X itself was plagued with these problems, with graphical glitches also entering the mix, but an OTA fix a month ago or so minimized issues.
Lemme know how things go... I still have 4 days or so to return my phone if the flicker comes back, haha.
I had to get my phone replaced. sadly for me it was a hardware failture. check google maps and see if it the graphics flicker there, of if the background on minecraft main screne flickers in and out
Spyderekz said:
I had to get my phone replaced. sadly for me it was a hardware failture. check google maps and see if it the graphics flicker there, of if the background on minecraft main screne flickers in and out
Click to expand...
Click to collapse
Yeah, woke up this morning and problem was back in full force. I think it might be charge-dependent or temperature dependent (which makes sense if its an analog hardware component like a voltage regulator that's being futzy). I ended up replacing it, too, but Sprint charged me a bull**** $35 because I bought the phone at third-party reseller instead of a corporate store (god... damn... it). Anyway, my new (and refurb, btw) unit has absolutely no problems. Zero. Rooting and reinstalling meanROM now, haha. At least the store people acknowledged that they could also see the problem. Software scans turned up absolutely nothing, although Sprint says HTC does not allow them to open things up because it's a unibody phone, so it's still possible that my regulator was faulty.
Anyway, seems to me that it's a hardware problem having to do with a particular batch of phones. Strange, since my new phone is a 0003 hardware revision, just like my last...
Went today for my 3rd time trying to get a replacement because of this issue and not to mention I got denied a replacement when I was in my 14 grace day period I went in 2 times after that today being the 2nd and I asked for a replacement, I then have to wait for the "tech" to look at it...waited 1 hour to get told it phone has no problems we ran all the tests and passed, me really confused asked her do you even know what the problem is? She replies no....I then am like WTF. I tell her about my issue and try shwowing her and somehow doesn't notice it. Then asks 5 other people and they notice it and then they replace my screen? After I wait another hour (caused me to be late to work) then once done it actually fixed the problem completely, go home to find out she broke my speaker and my sd card won't mount! Drop it off and picked it up and all is fixed. I know want to terminate my contract cuz sprint has been giving me Shi**y customer service since day one! Someone who works at sprint plz help me!
Sent from my EVO using xda premium
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
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