Hi.
I want ask.
Last few days my oneplus3 start randomly rebooting. More and more often. Last state was that mobile refuse to boot. I was on stock 4.1.6. I flashed 3.1.2 with Oneplus3 unbrick tool (method 2 from this site) and than OTA to 4.1.6 again. But problem still here, phone randomly restarts and sometimes wants some kind of code on black screen after restart. I dont know what code is it. I dont have any security code in settings now. When I turn phone off for few hours on another attempt usually boot normal and ask for SIM card pin.
And another problem. From flash with unbrick tool it seems that some sensors and compass are dead. Light sensor isn´t working and compass is still locked in same position. i try calibrate but without success.
you can see sensors diagnose from gps status app.
What should i try? Can it be a hardware problem? Before problem started i used compass often a always working well. Hardware reset isn´t helpful.
Thanks
Sorry for my terrible english
Nobody know? It seems that problem is with persist.img as was on oneplus 2
repaired by waranty repair.... new mainboard
Related
So many threads about proximity sensor problems, but none of them with the right answer...
I have this problem with my Sensor were everytime I reboot my phone or do a Factory reset using recovery,
EVERYTHING starts to work normal. It last for about 5 minutes when the screen no longer turns off when I get a call and get it close to my ears.
I dont know what it is i've tried different Roms and going back to ICS but the problem keeps showing after some time. There must be some Gnex users with the same problem and yet there isnt a solution... perhaps is a hardware problem? maybe not because each time yo reboot or factory reset... the problem goes away. Any help will be appreciated.
Hello. My problem is with the phone's vibrator. 2 or more weeks ago I got the same problem, when I dropped my phone from the bed tot the floor (aprox. 40 cm height), it stopped vibrating for feedback, messages and calls. At that time, I thing I either turned it off and removed battery or just do a reboot, but it started working again until 3 day ago. Since then it stopped working completely. I tried turning it off, reboot, removing the battery for 15 min., nothing worked. I have no vibration feedback (for example when I type a phone number or message), no message receiving vibration, no incoming calls vibration and not even when I turn on/reboot the device does my phone vibrate(it was a small vibration when you turned on the phone). Today I thought I should first try to change my ROM prior to trying to replace the faulty vibrator, but when I selected to reboot to recovery, my phone rebooted and vibrated at the beginning, so I thought the bug is gone. I went back in to the phone and I had: vibrate feedback (typing a phone number), message vibrate, didn't have time to test the call vibration because after I received 2 messages the vibration stopped once again. So now I'm baffled: is it because of the ROM, is it a glitch/bug from the motherboard or is the vibrator almost "dead"? If anyone had this issue and can help me fix the bug I would be really thankful. If I have to replace the vibrator, it wouldn't be a hard thing to do and I would do it if I know this will fix the problem forever.
My phone is S-OFF, rooted, with AcesMod007 ROM. Thank you.
I have installed CM10 | Jelly Bean 4.1.2 - v2.8 by vijendrahs and still no vibration, so it must be from the motherboard or the vibrator itself. I might try to replace it and see if this solves the problem.
No one has encountered this problem until now? No thoughts on this? I've searched for this bug and found some applications that should remove this bug, but they didn't work for me, so I am still open to any suggestion. I still have to wait up to 3 weeks until the vibrator arrives.
L.E.: I've just noticed another anomaly: my phone jumps from 82%-85% battery to full when I'm charging it. Might this have something to do with the vibrator? How can I fix this problem? Thanks.
Tried all kinds of applications that would force the vibrator, but with no success. I am still looking for a solution.
I have no guarantee so I have to fix it myself. I saw that other peoples with the same problem had sent the phone back to HTC for a replace. One of them actually stated that HTC had replaced first the motherboard (with no success) and then the vibrator module. I hope that replacing the vibrator would solve the problem.
I've solved the problem. I decided to open it up, thinking it is a hardware problem, and take a look at it. I've blended the two legs a bit more to make sure they get a perfect connection to the the motherboard and voila. It is working fully.
Hey Guys!
I have a big problem!
2 Weeks ago, the display of my G3 (not rooted, original LG Android) broke and i sent it to repairmyphone.de (I'm from Germany) for repair. Today my G3 came back and the display was fine. So i think they changed the display and repaired my phone.
Sounds good right? Well not exactly, because now there is a problem:
The touchscreen is working fine, but when i lock my phone (With the DoubleKnock or the Button) and turn the display on again, the touchscreen isn't working and i can't unlock the phone.
Only after i pull the battery out and start the phone again, the touchscreen is working fine. But when i lock the phone the same thing happens again. Even when i turn off the lockscreen and turn the display, the touchscreen is not working.
The strange thing is, the KnockOn is recognized so it turns the display on when i double tap it, but nothing is recognized after that.
I did a factory reset but the same problem happens again.
So i don't really know if it's a hardware or software problem is and if any one of you can help me with my problem.
I wrote the repairservice an e-mail but i think it will be read on monday.
So if nothing works i have to send it back again, but maybe you guys have a solution for me.
Thanks in advance!
Hi, I have a Sony xperia T3 D5106 4.4.4
My problem began when the proximity sensor wasn't working so I decided to fix it. I got an app call "something... exposed" (which let me to manage the software in charge of the sensor) but I was required to root it before doing it. So I did it using Kingroot. Finally, It turns out that everything was good and the sensor was working as it was supposed to be with the new display.
Some minutes after that, the phone was power ON, but I couldn't turn the screen ON so I had to restart it (it happened about 3 times) , until the WIfi stop working... and then the SIM card slot wasn't working at all.
I try to solve this issue by returning the display to it was before, and stop beeing superuser and unistalling those apps. but nothing happened... (and sometimes the music player was working for 10 second and the app closed suddenly.
Well, I send it to a technical and he flash it and the WIfi come back to work. Now I tried by instaling differents firmwares but it's still not working I dont know what to do ...
I've read that kingroot can change my configuration to a chinese one. So that could be a reason but.... does it have a solution? Another thing I read is that I have to change the baseband... but I dont know where could i get the files for a company in Peru (actually is wasn't unlock for all companies, it was from Movistar Peru).
Please I want to fix it. eventhough it has almost 2 years It's almost new and the software is so fast. I really want to recover it.
Are you sure that isn't physical damage?
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.