Hey guys so i was given a galaxy S7 edge and worked fine completely up until i updated it to 6.0.1 , the touch screen still works no problem but the bottom half of the display has turned white, the screen has not been hit or the phone has been on a soft surface ever since it was updated and would like to know if this is a software issue and if it can be fixed by flashing a younger version of android onto it. it was locked to telstra and silly me flashed a vodafone version on to it, i have tried to flash the right firmware back on to it but the problem still happens. heres a lame video of what is happening:
https://www.youtube.com/watch?v=ONPPRtLlM44&feature=youtu.be
LayALAD said:
Hey guys so i was given a galaxy S7 edge and worked fine completely up until i updated it to 6.0.1 , the touch screen still works no problem but the bottom half of the display has turned white, the screen has not been hit or the phone has been on a soft surface ever since it was updated and would like to know if this is a software issue and if it can be fixed by flashing a younger version of android onto it. it was locked to telstra and silly me flashed a vodafone version on to it, i have tried to flash the right firmware back on to it but the problem still happens. heres a lame video of what is happening:
&feature=youtu.be
Click to expand...
Click to collapse
Hi, have you tried to boot it into download mode and manually flash the firmware downloaded from SamMobile.com? It's a bit strange for your phone to do that after updating it looks like (as you said) something a know or a drop would do...
Yeah me too but i just can't shake what happened to it then if it was hit on the screen overnight, i was pretty drunk. i've tried flashing yes.
LayALAD said:
Yeah me too but i just can't shake what happened to it then if it was hit on the screen overnight, i was pretty drunk. i've tried flashing yes.
Click to expand...
Click to collapse
It's extremely likely to be a hardware problem from what I saw in the video and if flashing a new firmware didn't work.
Good luck. I'd say get the screen replaced :good:
Related
Hope I’m posting this in the right place. Ok here we go:
Bought a Nexus S (i9020T) a couple of weeks ago. It was shipped with 2.3.2. I got the 2.3.4 upgrade OTA and installed it. After the installation the screen has a red tint. And I’m not talking about the color variations between different Android versions, this is really bad! I can’t look at pictures and some text is unreadable. The screen is not broken since the bootloader looks normal, so my guess is that it is software related.
I have downgraded the phone back to 2.3.2 and everything is normal. I have tried to reinstall 2.3.4 as well as going from 2.3.2 to 2.3.3 and then 2.3.4, both by downloading the files from Google and manually install and by doing it OTA. I have unlocked the bootloader and tried to load a whole bunch of different ROMs and Kernels. Nothing works. The Voodoo Color Control is not even close to fixing it. The only version that works is stock 2.3.2. I have googled it and it doesn’t seem to be a common problem.
So I’m reaching out to you guys to see if anyone has heard about this behavior and know what to do?? I can live with 2.3.2 but the reason I bought the phone was to get instant updates. I’ll attach a picture of the home screen which should be black. I don’t have international warranty so turning it in to Samsung is not an option.
Any ideas??
wow. that mr is a defective unit imho. i think that you should try to get a replacement. i do not think that you need international warranty or something. just a receipt might do it. (it worked with htc for many nexus one's purchased on ebay for ex) . just give it a try.
sorry for the news. i hope u get it solved or i hope i am wrong.
keep us updated.
Hmm, yeah I was afraid of that.
Just thinking though, what could be defective? It works just fine on 2.3.2. If i run 2.3.4 (or 2.3.3) and start the phone, the Google-logo shows up in white for about 5 seconds, then it turns red and everything is red after that.
Eldrin said:
Hmm, yeah I was afraid of that.
Just thinking though, what could be defective? It works just fine on 2.3.2. If i run 2.3.4 (or 2.3.3) and start the phone, the Google-logo shows up in white for about 5 seconds, then it turns red and everything is red after that.
Click to expand...
Click to collapse
That's really strange. It seems that the update only is screwing things for you. Try sending supercurio a PM. He knows these stuff. He is the dev of the voodoo tweaks and application. He'll surely be able to answer you and give you an advise.
Sent from my Nexus S using Tapatalk
Eldrin, Have you finally found a way to fix it ?
Or are you stick in 2.3.2 ?
Red complexion on ICS
Did you find a solution to this problem?
When I turned on my Nexus S i9020 this morning all greyish colors where red. Directly after turning it on, the lock and the google writing where white as usual, but after about 2 second it got a red complexion. I tried to make a screenshot of my homescreen, but in the jpg the red complexion has vanished and it looks as usual.
I'm running ICS 4.0.3 stock and did the update back in december. Removing the battery for a minute didn't help.
Has anyone an idea?
EDIT: After about 5 restarts it was back to normal! Anyhow, I made a short clip of the startup sequence before www . youtube . com/watch?v=vy5NkFrQDuA
Hey guys,
I tried looking for this issue but I can't seem to find it, I doubt I'm not the only one (I hope I'm not the only one...)
I've been flashing roms for a while now, fiddling with different settings/kernels/etc. and then all of a sudden I'm having issues with my Softkeys. I'll be using the phone and then they just go blank. What also happens is that the Search key gets held down (by a ghost, it seems) and it opens up the voice search option. I've also seen my Back button flicker as if it's being pressed repeatedly.
Right now I'm on CodeName Android 1.4 but I've tried 1.6, CM9 and it seems to be the same issue. I'm assuming that since this is consistant accross all ROMs that it's a hardware issue (I could be wrong) but I'm wondering if this has happened before and if there's a way to fix it.
Thanks gents
Hi friend,
The same happened to me once. It was very weird. I panicked, and locked the phone. Then when I unlocked it everything was as before. It must be some kind of a glitch, coming from CM9 built roms (almost all roms that are around). Try doing a totally clean install with a popular rom and see how it goes.
Now I remember that the same happened once again, when I got a drop of water on my screen, as the touchscreen seems to detect water as a form of touching and then all sort of weird things happened. Hope its a rom issue, not a Touchscreen failure.
Thanks man,
I'm really hoping it's not a hardware issue either as I'm not sure what the process is in terms of sending my phone in for repairs.
I'll try a clean wipe and install tonight and see how it goes.
Thanks again
Update: Alright so I ended up calling Samsung because I had come to the conclusion that it was a hardware issue because every ROM I flashed I had the same damn issue.
I got the ok to send in my phone and all that, I went to return my phone to Stock and when I installed the OEM operating system everything was okay... I seriously doubt that every ROM I downloaded was bugged.
I'm thinking it's just a general glitch or is it possible that 1 ROM I downloaded was bugged and everyone after that inherited the same problem? I don't know...
Hi there, I hope you guys can help me out on this.
I just got my HOS a few days ago and it was all good.
Rooted it after 1 day, everything was fine.. at first.
Played a few games, installed themes and so on. After a few hours, my HOS began to vibrate out of nowhere and apps started here and there, menu opens on its own and all that stuff. It was out of control xD
I then saw that theres an update available. Flashed stock recovery and unrooted it. Afterwards, I installed 1.78. Still unrooted, downloading most of my Apps again, works flawless. Gaming(specially Temple Run xD) is smooth.
Yesterday, I decided to root it again. At first no problems at all.
Just now on the train, playing Temple Run again, my HOS started going crazy, vibrating all the time as if it is pressing buttons on its own and I see the phone doing all kinda stuff(opening new apps, browsing thru home screen etc xD).
Has anyone else expierenced something similar? I have no idea where its coming from and it really annoys the hell out of me.
Right now I'm on TrickDroid v3.1 (wiped system/data/dalvik/cache before flashing)
Kernel: 3.0.8-01136-g9d2ad32
Baseband: 0.16.31501S.17_2_10.23.31501S.10L
Build: 1.70.666.1 CL52668
That really is strange !!! Its as if root contains some sort of poltergeist
I would have imagined a factory reset would have cleared it up, But in your case it didnt....
Have you tried an alternative rooting method ?
Nope, I did not. Always used the All-In-One Toolkit, except for when I flashed Trickdroid, since it comes rooted.
Is it ok if I unroot the HOS with Rootkeeper(is this just temp. unroot?) and then root it again with Superboot?
Unbranded HOS bought in Germany, if that matters. Also, no other recovery works for me except Intermin, CWM just won't boot for me.
that is weird...
Unlocking the bootloader was successful right ?
I dont understand why your phone is rejecting software lol.. Oh and I didnt know root keeper can unroot ive never used it..
how i got root was by flashing paul obriens recovery and then the root package zip file.. I did this on day one and have never had any issues at all.. Ive tested every single ROM and every single recovery lol..
Make a nandroid in recovery and just test out different methods and try get this issue fixed. If you have any issues just restore the nandroid..
Check your phone for remote access apps, maybe you got hacked. Most of those require root to function. Also check your google account for which IPs logged in and check the password recovery options for weird emailadresses and phonenumbers...
Ars has a writeup on hardening your android device, not very technical but some good stuff there. http://arstechnica.com/security/201...-smartphone-against-stalkers-android-edition/
Forget whatever i wrote.
My HOS registers my thumb, even tho I'm not touching it at all. If I'm like 5mm away from the screen, it registers it as if I'd touched it. My gf also has a HOS and it acts only if I touch the screen.
I also noticed that the hotter my HOS gets, the distance increases at which it recognized my "touch".
The distant screen touch has happened on my uprooted tmo us HOS. I've also experienced some craziness out of the device. I've kept it stock, no unrooting/rooting going on.
I was thinking an exchange with HTC cause I also have excessive battery drain and wavy lines in the screen but now I also have an awesome cracked screen too :-\
Sent from my HTC VLE_U using XDA
i also dont need to touch my screen to select something
I just hover my finger over the app, real close to the screen and it selects it...
I guess we have special powers
i also dont need to touch my screen to select something
Click to expand...
Click to collapse
Same here.
lets keep this quiet, We dont want people to know we are superhuman...
I cant be arsed with the fan mail from the CIA,,, Nor do i have the time to fight crime and save the world....
Id rather just continue to flash a ROM.
About a week and a half ago I got water into my GS3 and it ruined the OLED panel. It was a relatively slow process, and I was able to use it up until most of the screen turned black (touch still functioning properly). I ordered a new Screen Assembly which included the frame, OLED panel, digitizer, and glass as ONE unit, pre-assembled.
Upon taking the broken phone apart and re-assembling it into the new frame/screen, the phone hangs for a long time on the "Samsung Galaxy SIII" with Cyanogenmod Cid character, but finally boots, however the touch screen is unresponsive.
All hardware buttons work, and the capacitive buttons work as well (back and menu), it is only the touchscreen that doesn't function, but it looks beautiful!
is this a digitizer issue (faulty hardware sent to me)? It seems as if the phone is trying to communicate with the digitizer or some other hardware, gets stuck in that loop because it can't detect it, times out, and then finishes booting.
I tried re-flashing CM to see if it was a kernel error or something of the likes, but the issue persists.
Any Ideas? Thank you so much in advance.
XdrummerXboy said:
About a week and a half ago I got water into my GS3 and it ruined the OLED panel. It was a relatively slow process, and I was able to use it up until most of the screen turned black (touch still functioning properly). I ordered a new Screen Assembly which included the frame, OLED panel, digitizer, and glass as ONE unit, pre-assembled.
Upon taking the broken phone apart and re-assembling it into the new frame/screen, the phone hangs for a long time on the "Samsung Galaxy SIII" with Cyanogenmod Cid character, but finally boots, however the touch screen is unresponsive.
All hardware buttons work, and the capacitive buttons work as well (back and menu), it is only the touchscreen that doesn't function, but it looks beautiful!
is this a digitizer issue (faulty hardware sent to me)? It seems as if the phone is trying to communicate with the digitizer or some other hardware, gets stuck in that loop because it can't detect it, times out, and then finishes booting.
I tried re-flashing CM to see if it was a kernel error or something of the likes, but the issue persists.
Any Ideas? Thank you so much in advance.
Click to expand...
Click to collapse
Only way to tell if it's a hardware issue is to go completely to stock. If you can't get it to work at that point then something is wrong. Could be a broken digitizer, or could be a problem with the connection to the board.
I would try to make sure your connection is solid and you didn't miss anything. But I'd say going back to stock is a necessity. Just make sure you Odin a 4.1.2 image, and if your screen still doesn't work then pull the battery so it can't update, then decide where to go from there.
BadUsername said:
Only way to tell if it's a hardware issue is to go completely to stock. If you can't get it to work at that point then something is wrong. Could be a broken digitizer, or could be a problem with the connection to the board.
I would try to make sure your connection is solid and you didn't miss anything. But I'd say going back to stock is a necessity. Just make sure you Odin a 4.1.2 image, and if your screen still doesn't work then pull the battery so it can't update, then decide where to go from there.
Click to expand...
Click to collapse
Thanks for the input, I appreciate it!
I have double- and triple-checked the connections. So what exactly would Odin-ing back to stock get me? The software/firmware worked flawlessly beforehand, so wouldn't that eliminate the possibility of software/firmware issues on my device?
XdrummerXboy said:
Thanks for the input, I appreciate it!
I have double- and triple-checked the connections. So what exactly would Odin-ing back to stock get me? The software/firmware worked flawlessly beforehand, so wouldn't that eliminate the possibility of software/firmware issues on my device?
Click to expand...
Click to collapse
Theoretically yes, but if you go back to stock you'll know for sure. If the digitizer isn't working anyway you have nothing to lose. If everything is completely stock then you know for sure it isn't software related and it has to be the digitizer.
Okay thank you, I appreciate your help!
Sent from my ASUS Transformer Pad TF700T using XDA Free mobile app
BadUsername said:
Theoretically yes, but if you go back to stock you'll know for sure. If the digitizer isn't working anyway you have nothing to lose. If everything is completely stock then you know for sure it isn't software related and it has to be the digitizer.
Click to expand...
Click to collapse
Sorry for reviving my dead thread and noob questions, but I'm still having issues.
My phone is perfect except for the screen doesn't recognize touches, although all buttons and capacitive buttons work well.
I am currently running CM11 using clockworkmod recovery, and I want to return to rooted stock, as you mentioned.
I am wondering if the firmware for the display is not present, since it is a new display (entire assembly, including frame).
How would I go about returning to stock rooted, and flashing as much stock firmware as possible to hopefully ensure that the display firmware is flashed?
As a side question, does the MF1 firmware AiO include things like display firmware? I flashed that with no result, so is flashing back to stock pointless?
I would like a 4.1 Stock ROM or whatever DOES NOT have Knox, so that I at least have the option to go back to CM if I wish if I sort out the issues.
Thank you all so much
XdrummerXboy said:
Sorry for reviving my dead thread and noob questions, but I'm still having issues.
My phone is perfect except for the screen doesn't recognize touches, although all buttons and capacitive buttons work well.
I am currently running CM11 using clockworkmod recovery, and I want to return to rooted stock, as you mentioned.
I am wondering if the firmware for the display is not present, since it is a new display (entire assembly, including frame).
How would I go about returning to stock rooted, and flashing as much stock firmware as possible to hopefully ensure that the display firmware is flashed?
As a side question, does the MF1 firmware AiO include things like display firmware? I flashed that with no result, so is flashing back to stock pointless?
I would like a 4.1 Stock ROM or whatever DOES NOT have Knox, so that I at least have the option to go back to CM if I wish if I sort out the issues.
Thank you all so much
Click to expand...
Click to collapse
I'm almost sure Knox wasn't added until 4.3 ML1
From my Wicked S3 on SOKP
ShapesBlue said:
I'm almost sure Knox wasn't added until 4.3 ML1
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Yeah, I think you're right
So anything Stock that will allow me to still have an unlocked bootloader when I'm done with it would be great!
4.0 - 4.2
XdrummerXboy said:
Yeah, I think you're right
So anything Stock that will allow me to still have an unlocked bootloader when I'm done with it would be great!
4.0 - 4.2
Click to expand...
Click to collapse
Correct. Custom roms will work just stay away from anything in the development forums that says BL LOCKED or any variation of that
From my Wicked S3 on SOKP
ShapesBlue said:
Correct. Custom roms will work just stay away from anything in the development forums that says BL LOCKED or any variation of that
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
But to solve my issue I need the stock firmware, which means stock (and rooted) ROM. Is there a forum for that in the development section or where could I get my hands on it?
Thanks!
XdrummerXboy said:
But to solve my issue I need the stock firmware, which means stock (and rooted) ROM. Is there a forum for that in the development section or where could I get my hands on it?
Thanks!
Click to expand...
Click to collapse
I'm assuming you mean 4.1.2?
Edit: I found it, I don't know if the links work though. http://forum.xda-developers.com/showthread.php?t=2178482
From my Wicked S3 on SOKP
ShapesBlue said:
I'm assuming you mean 4.1.2?
Edit: I found it, I don't know if the links work though. http://forum.xda-developers.com/showthread.php?t=2178482
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
That was the right thread, the links were dead but took me to the right website, where I found this under archived devices:
http://www.scottsroms.com/downloads.php?do=file&id=511
Stock rooted 4.3 WITHOUT Knox, meant for people who haven't locked their device.
EDIT:
Just flashed, and WAHOOO Touch screen works well!
Thank you all so very much!
Hi
I am Sure the Title of this Thread was Mentioned Quite a lot. but bare with me .
I have Tried the Search Option and Didn't find a Thread that addresses the Problem that I Have.
I have a Samsung S7 " SM-G930FD " that Keeps Freezing.
it Only Freezes when the Phone is Locked and Not Used.Never freezes while Being Used or when the Screen is On.Always Happens when the Screen is Off.
I tried to Disable the Always on Feature, Removed the SD Card, Changed the SIM card, Changed the Service Provider, Kept it Updated and even Clearing the Cash wouldn't Solve the Issue.it Just Freezes Regardless and without any noticeable Reason.Some times it is a week between Freezing and some times it freezes multiple Times a day.
only can be Recovered with a Hard restart.
I Tried to Use it on Safe mode , rest it to Factory, Soft Reset and Hard Reset.
wiped the date and Did any Suggestion that I could Find on the Internet. Sadly most of the topics only cover how to Restart your Frozen phone.and Never Found a Single Hint about what to do about this Issue.
the Device is Currently on Android 7.0 , baseband Version G930FXXu1DQIL .
I really Wish I can get any Help.
thanks a lot.
I have exactly same issues, sometimes the notification led blinking but smartphone is dead..right now Samsung checking my phone in service center so ill let you known
Ivanhoe8 said:
I have exactly same issues, sometimes the notification led blinking but smartphone is dead..right now Samsung checking my phone in service center so ill let you known
Click to expand...
Click to collapse
yeah! Please, DO Let us Know.
it is a Shame such a Good Phone Suffers from this issue.
weneeakhborz said:
yeah! Please, DO Let us Know.
it is a Shame such a Good Phone Suffers from this issue.
Click to expand...
Click to collapse
So i have my s7 back..they changed completly motherboard, the first one have been faulty..So i think you can only send it to repair
Ivanhoe8 said:
So i have my s7 back..they changed completly motherboard, the first one have been faulty..So i think you can only send it to repair
Click to expand...
Click to collapse
oh Dear GOD!!