I'm having the following issues with my OnePlus 3 (stock recovery, no root):
15 November: last known date without any issues
16-18 November: when I played games I noticed that screen won't rotate even when auto rotate was ON
19 November: I wanted to click some pictures when the camera app just stopped working
Tried rebooting and clearing cache, but didn't work
Thought a software update might fix these problems
20-27 November: when I answered calls the screen won't turn off. That's when I realized that all the sensors on the phone had stopped working (no lift up display, motion sensors,etc). Read online that I could get the official Oreo update just by changing my VPN to Germany/Canada. So I did the same and upgraded to Oreo
Still the issues were there and battery drain was significant. The phone would reboot on its own.
On contacting OnePlus support they asked me to do a hard reset which seemed to work only for 3-4 days
28-29 November: the sensors stopped working again & again and I did a hard reset every time
In the end the phone switched off and the white notification light was on continuously. Pressing or holding the power button didn't work. Contacted support
2 December: through a remote session the OnePlus support installed Oreo again and on rebooting I got DM-VERITY error. So the support asked me to visit a Service Centre
3 December: I visited the SC where they concluded it was a hardware issue (motherboard: 17000/-) so I asked them to just roll back to OOS 4.5.1. Worked fine for 10-11 days
14 December: started rebooting randomly. Noticed that the phone would hang and reboot when using the camera (in WhatsApp, CamScanner and stock camera), maybe I'm wrong.
So now there's minimal usage of a phone with such high capabilities knowing that I'll have to do a hard reset once a week.
How can it be a hardware issue if the phone works fine for 4-5 days after a hard reset before breaking down again? What does that white notification light mean? Any help would be greatly appreciated
"3 December: I visited the SC where they concluded it was a hardware issue (motherboard: 17000/-) so I asked them to just roll back to OOS 4.5.1. Worked fine for 10-11 days"
There is your answer, there is a problem with you motherboard, you need to get it replaced, we cant diagnose a hardware problem here!
How come it works normally for a week or more if there's a problem with the motherboard?
And a hard reset seems to return the phone to its normal state.
Shmt_18 said:
How come it works normally for a week or more if there's a problem with the motherboard?
And a hard reset seems to return the phone to its normal state.
Click to expand...
Click to collapse
That just means that it is faulty and will fail after some time. This most likely means there is a bad memory sector on the board. As suggested. Get it replaced or you will keep having these issues.
Okay. Thanks for clarifying.
May I know what may be the causes for the motherboard damage? How common is it that a motherboard malfunctions?
Because there was no physical damage at all. Thanks again!
Shmt_18 said:
Okay. Thanks for clarifying.
May I know what may be the causes for the motherboard damage? How common is it that a motherboard malfunctions?
Because there was no physical damage at all. Thanks again!
Click to expand...
Click to collapse
See that is the thing. China has no real quality control standards. So it could just have been a bad board. If you look around you will see that a range of random issues seem to pop up over a short time. Yet some are just fine. Like mine. It had a faulty USB port from day one to the point that I knew it was gonna fail. (expected) So I am replacing it.
Related
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
focusedonsound said:
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
Click to expand...
Click to collapse
Anyone have any ideas.
focusedonsound said:
Anyone have any ideas.
Click to expand...
Click to collapse
I think it's just an hardware problem.
Something happens when a part of code is executed and the hardware does not respond correctly.
Similar problems happen with desktop computers, a faulty memory module, for example may create a reboot due to the error, or making a driver to crash. These smartphones are little computers...
This is what i think IMHO. I'm a computer technician.
PS. Maybe when you scroll faster the cpu goes at an higher frequency an becomes instable, did you overclocked it in the past? Try to lock the frequency as lower as possible with a custom kernel and verify if the issue appears anyway.
Anyway I'll pay a lot of attention flashing a new kernel or recovery on an instable phone, if it reboots during flash you may brick your device!
I hope this helps.
Thanks for the reply,
This is kind of the theory that I had but I didn't want to make any assumptions. With my computer background I am very familiar and understand how to trouble shoot problems with a computer. However phones area whole new cup of tea.
The phone resided in an otterbox which could have led to overheating and ultimately the processor going bad. I am no so quick to flash a new kernal etc to restrict the frequency.
The thing that I find most odd though is that there have been no similar functionality reports.
-Nick
Here's the video of my problem guys.
https://www.youtube.com/watch?v=i2DOknf_SJY&feature=youtu.be
Screen and the capacitive buttons isn't responding to touch although the screen is active and working. This always happens every 10 minutes. Really need your help guys.
What do you think is the problem? Is this a faulty Zenfone 2? This is not rooted. Using Stock ROM with latest update. I'm currently doing a factory reset. Will update later. Thanks
I had a problem with my phone not waking up, had to get a replacement.. so far the new one is flawless.
Sent from my ASUS_Z00AD using Tapatalk
I got the same problem as you, seems to be something you downloaded. I did a factory reset through the settings and it got rid of the problem.
Ty.
lostbuddy1 said:
I got the same problem as you, seems to be something you downloaded. I did a factory reset through the settings and it got rid of the problem.
Click to expand...
Click to collapse
Hopefully. I tried factory resetting the phone. Screen is not being unresponsive so far.
If problem continues, recommend performing a hardware reset including wipe cache partition. For hardware reset/wipe cache partition instructions please see the following: http://www.asus.com/us/support/FAQ/1011956/
Sincerely
ASUS_USA
Asus_USA said:
If problem continues, recommend performing a hardware reset including wipe cache partition. For hardware reset/wipe cache partition instructions please see the following: http://www.asus.com/us/support/FAQ/1011956/
Sincerely
ASUS_USA
Click to expand...
Click to collapse
I got this solved. It seems there is an error on the sim 2 tray.. The screen being unresponsive only happens if there's a text from sim 2 or a call from sim 2. Its not always happening but its really annoying if it happens since you have to wait for minutes in order for the screen to work again or you have to turn phone off. Now I only use sim 1 tray and never experienced the problem anymore.
This looks like a software bug as many users are complaining about this in asus zentalk forums.
rainversion13 said:
I got this solved. It seems there is an error on the sim 2 tray.. The screen being unresponsive only happens if there's a text from sim 2 or a call from sim 2. Its not always happening but its really annoying if it happens since you have to wait for minutes in order for the screen to work again or you have to turn phone off. Now I only use sim 1 tray and never experienced the problem anymore.
This looks like a software bug as many users are complaining about this in asus zentalk forums.
Click to expand...
Click to collapse
that's strange
Touch freezing while receiving call from sim2
during I receive calls on SIM 2, the touch screen becomes non responsive for some time. It recovers after sometime. already 4 update gone still ASUS team unable to solve this problem,I also email 2 times regarding this issue no response from ASUS,this is fundamental feature of phone ,ASUS team give first priority to solve this issue ASAP
Build no-MR7-LRX21V.WW_ASUS_Z00A-2.19.40.22_201150627_5104_USER044030427_201501060109
Touch panel version-5446_0X81_0Xba
rainversion13 said:
Hopefully. I tried factory resetting the phone. Screen is not being unresponsive so far.
Click to expand...
Click to collapse
Hello. I'm currently having the same problem with my zenfone 2, but I don't understand... how do you 'factory reset' the phone?
And is there any other way to fix this problem other than resetting the phone?
Read #6 post, even factory resetting could not solve the unresponsive touch screen issue. If you want no screen issues, dont use the sim 2. Try setting your mind that zenphone only uses 1 sim. Haha. Only use sim 1. You'll have no problem on unresponsive screen everytime there's a call or message coming from sim 2. Asus has yet to release a software fix for this as many are encountering this problem
rainversion13 said:
Hopefully. I tried factory resetting the phone. Screen is not being unresponsive so far.
Click to expand...
Click to collapse
rainversion13 said:
Read #6 post, even factory resetting could not solve the unresponsive touch screen issue. If you want no screen issues, dont use the sim 2. Try setting your mind that zenphone only uses 1 sim. Haha. Only use sim 1. You'll have no problem on unresponsive screen everytime there's a call or message coming from sim 2. Asus has yet to release a software fix for this as many are encountering this problem
Click to expand...
Click to collapse
I hope Asus fixes this problem real soon.
So, so far there is really no way to fix this yet? Because anyway, I'm not even using sim 2. Now what do I do...
I am also facing screen freezing issue due to SIM2 in my Zenfone2. I did a factory reset and the problem still persists. Is it that the phone is not suitable for dual SIM. Either it unfreezes after a min or so I had to hard boot it since the restart option on touch screen is not working. Phone per say is never frozen except the screen.
Can anyone suggest a solution on this forum
Touch freez issue on incoming call on sim 2
Having the same touch freez issue since i changed my sim 2...
Temporarily i am using zenmotion "hands up" feature to pick calls....
Waiting for asus to resolve the issue...
Touch freez issue
accidentally my screen got cracked, so i replaced the display. Now no more touch freez...
I think its a hardware related issue....
cm
This only happens to me with CM (12 and 13), not using SIM2 is not an option for me, so I'm stuck with stock rom.
I had this problem with the Asus Zenfone 2 View Flip cover. I removed the cover and the problem didn't repeat. So suspect something with the View Flip Cover app which causes the screen to freeze.
I'm having Ghost touch issues and screen becoming unresponsive before the ghost touches start to occur. I'm pretty sure that this is a hardware issue.. I've been able to fix the problem by turning off the phone and tossing it into the freezer for a few hours.
I'm going to re-flash stock rom and RMA and hope they actually fix the issue since it's intermittent.
I returned the phone for RMA last Friday and got it it back today.
I gave a detailed description of the issue on the rma form and they replaced the screen and so far it looks good. (I can tell it was swapped since some cosmetic damage on the lcd plastic bezel is gone)
Guess I'll give it a few days of normal usage to be 100% certain,but so far I can notice some touch response is better than the old screen too.
On a custom recovery / unlocked bootloader note (unofficial method)
Fortunately flashing back to stock was good enough and they didn't just send the phone back as an excuse.
I'm actually super impressed with the Asus rma process, and reckon the bad digitizers are a widespread and known issue since they replaced the screen so quickly and without hassle.
I'll definitely keep Asus as my hardware provider when I upgrade to my next phone and tablet!
guys.. i need help
i was using my phone..then it hanged..I cant use it anymore..the screen is still active..displaying the screen where it hanged...but its unresponsive..I cant do a thing....the power button is not working either..I cant even turn off my phone..and because we cant remove the battery on zenfone 2...how can turn it off?
pls help fast.
I am also facing the same problem from last two weeks after upgrading the phone to latest firmware update. I tried factory reset, cleared cache bit nothing worked. In case the screen is not responsive then I have to switch of the screen by physical button at top to unnlock sometimes I do this 2 or 3 times to get the phone working again.
And I am only using one SIM
I've been having this problem since the other day. The day before that, the phone's just working perfectly fine, tho, when I woke up in the morning, the phone just suddenly got this screen glitch. It only seems to be having a glitch in dark backgrounds... But given some time, the glitch disappears, but then again, if I turn off the display and leave it some time, the problem reappears.
Please look at the vid.
I don't think it's a hardware problem since the splash image isn't affected and the glitch seems temporary, but changing ROMs doesn't help. I haven't tried the stock firmware tho. Gonna download the stock fw and try it and see if the problem still persist.
Hi,
It's a hardware issue.
It's not related to any ROM you're using.
I've same problem as you and I decided to return it to stock and sent it to the nearest Asus Service Center (in Makassar) via my local seller because there is no one here in my location.
Sent from my GT-I9500
its not hardware issue if that not happen when you use screen recorder.
give a try then...
@baonxxx
This isn't related to software. I had this screen glitch even on stock (applies to everything: Splashscreen, etc) and caused difficulties on normal usage.
By general you can trigger this screen glitch by let the phone heating for a period of time, like let the phone idle for hours, charging, or let the screen on around the time. *only on affected devices*
You may need to read OP once again.
Sent from my GT-I9500
krasCGQ said:
@baonxxx
This isn't related to software. I had this screen glitch even on stock (applies to everything: Splashscreen, etc) and caused difficulties on normal usage.
By general you can trigger this screen glitch by let the phone heating for a period of time, like let the phone idle for hours, charging, or let the screen on around the time. *only on affected devices*
You may need to read OP once again.
Sent from my GT-I9500
Click to expand...
Click to collapse
as u can see in the video , it doesn't really affect the splash screen, tho if flashing back to the original fw doesn't help, then I may need to get it to Asus Service Center for them to check.
xCalibur15 said:
as u can see in the video , it doesn't really affect the splash screen, tho if flashing back to the original fw doesn't help, then I may need to get it to Asus Service Center for them to check.
Click to expand...
Click to collapse
I know that, but when the screen glitch becomes worse, it would happen on everything.
Sent from my GT-I9500
krasCGQ said:
I know that, but when the screen glitch becomes worse, it would happen on everything.
Sent from my GT-I9500
Click to expand...
Click to collapse
hhmm, not really everything, only glitches on dark backgrounds... seems like the screen on my phone's having a problem on dark backgrounds.
it is definitely a HW issue. did your phone ever fell on the ground?
this usually happens when there is loose connection between the mainboard and the display.
if you haven't void the warranty, send it for repairs, otherwise open the phone and fix it yourself (just detach and properly reattach the display connector, and make sure it's grounded properly).
@pecholino
Only unlocking the bootloader with official method provided by Asus could void the warranty.
Sent from my GT-I9500
damn it's a HW issue and it's getting annoying... gonna send it back for repairs... damn I didn't even dropped the phone once, so much for ASUS.
It happens with me too. On stock firmware. But is very rare and temporary. Turning off the screen and then again waking up solves it.
Rud09 said:
It happens with me too. On stock firmware. But is very rare and temporary. Turning off the screen and then again waking up solves it.
Click to expand...
Click to collapse
it happens to me on stock as well. Same as yours turning off the screen and waking it up makes it normal. so it's not a firmware problem? or is it?
Pause08 said:
it happens to me on stock as well. Same as yours turning off the screen and waking it up makes it normal. so it's not a firmware problem? or is it?
Click to expand...
Click to collapse
I don't think this is a hardware problem as so many people are having this problem.
This problem happened to me the next morning after I updated to 2.20.40.168 I didn't drop me phone in between the time I updated and the time I first seen it happen. I've already sent my phone in and Asus replaced my motherboard. I got it back and problem was still happening.
The problem may go away for you if you set Developer Options, Disable HW Overlays but the setting does not seem to persist after a reboot.
quick settings
I noticed another remarkable phenomenon. When I open the quick settings, the defect is gone. But I only can operate in the quick settings, nothing else.
The screen freezes until I open the quick settings. -
I have reinstalled all software, even the boot partition. The defect already occurs in the splashscreen and fastbootscreen. -
I have opened the plug connection to the screen and connected again. -
So far everything in vain. -
ASUS claims, it is a defect on the motherboard. - I am afraid they are right.
It is a hardware issue. The problem is with the screen, precisely, the multiplexer on the screen. But since it is a part of the LCD itself, you will have to get the entire display module replaced.
Replacement displays are available on eBay/Amazon and you can get instruction guides on YouTube.
If your phone type z00AD Try downgrade your rom only to 2.12.40.11.. its solved my problem..
Sent from my ASUS_Z00AD using Tapatalk
Hi everyone,
I'm having serious problems with my Wi-Fi on my Samsung Galaxy Note 3 Neo (SM-N7505). Whenever I click the button to activate the Wi-Fi, the icon goes from grey to a dull green (darker than the bright green which signals that a function is turned on), as it does when it's trying to turn itself on. Problem is, instead of turning on, it just stays in that state for a few minutes before reverting to grey. This has gone on for a while, and I've already tried several possible solutions which I found after online searches. I don't think it's a hardware issue (see point 1 for the reason), and I really hope it isn't, because my warranty has been voided due to rooting, so I can't have my phone replaced or repaired unless I pay for it (which I can't at the moment). So, I'm basically ignoring the possibility of hardware failure and trying every possible software solution, hoping one of them will work, otherwise I'm just stuck with no Wi-Fi. These are the fixes I've tried:
1) Take out the battery while the phone is on, wait a few seconds, then put it back in and boot the phone up. This used to work when the problem first presented itself a few months ago (which is why I don't think it's a hardware issue), and I've been since using this method to fix it whenever it happened again. But a few days ago, this method stopped working for whatever reason, so I was back to square one.
2) I tried renaming the data/misc/wifi/wpa_supplicant.conf file, which seems to have worked for some people, but not for me.
3) I tried updating the version from Kitkat to the recent Lollipop, hoping that would fix it, but nope.
4) I tried deleting practically every single app one by one, hoping that one of them was interfering with the Wi-Fi somehow, but nope.
5) As a last resort, I tried a factory reset, but not even that worked.
This is basically the long and short of what I've tried to fix this... I might've skipped a few of the simpler fixes I tried (for example, I just remember I tried disabling "Smart Network Switch", which seemed to do it for some people), but the big stuff is all there.
I'd really like to get my Wi-Fi back, so if anyone could help me fix this thing I'd be really grateful!
Thanks in advance to anyone who will bother to reply.
same problem dude
Same problem...wifi and bluetooth not working...pls help us
Same Problem for me, Initally it works fine even after updating Official Lollipop update (OTA), but after few months now wifi & bluetooth are not working for me. And finally faced battery drain issue for past few days. Battery goes down upto 20% per hour even in idle condition. Then i rooted & installed Note Rom & even after i face the same problem. Is there any way to fix?
OK, my situation:
Bought a new t-mobile z2 force a few months ago from eBay. Everything was fine but camera had the blur faulty hardware. The replacement finally arrived yesterday so I immediately wiped everything and reflashed Los 16 again: like in the previous phone, everything is perfect, this time minus the camera faulty lens. But now I have a problem and I don't know if its software or hardware related.
Im using it for 24 hours now and I already had 3 random shutdowns. I just took it out from my pocket (1 time it was just lying in my bed) and the phone was off. Mind that these are shutdown, not reboots.
U guys think this software / Roms related? Or could it be (another one ) hardware problem?
Thinking it might be the battery, I'm trying to hit and tilt (not to much of course) the phone but it keeps on...maybe it's not the battery...or is it?...how can I know for sure? Any ideas?
Happen again today, logs attached (saved as soon as I restart it after shutdown):
https://drive.google.com/file/d/137W-gSgXixcyWJyLheNYORh_tDksDSn6/view?usp=drivesdk
Ever since I got the new 11/15/19 update, my z2 freezes completely. I have no idea what's going on.
My device is somewhat stable now since I reinstalled the rom. My device doesn't power down now like yours, but it reboots/restarts itself randomly every few hours.
After trial and error I figured out why my device would freeze and then bootloop. The newest update as of 11/15 struggles to work with magisk's busybox module. Once busybox was deleted, it would no longer freeze then bootloop.
I wonder if anyone else is having problems since the new updates.
Well in my case, I still have phone off when I took it out of my pocket, even after flashed stock tmo ROM...the only app in common was magisk in both flashings.... could it be? Il try to test it without magisk this time, but I'm afraid it's an hardware problem...