Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Rooted?
You mention in the title that the phone is rooted. To be able to discount hardware errors, have you tried flashing a factory image to set it back to stock? If the same problems continue, then I suggest that you return it to Google. I did this myself when the back of my N6 started to peel and the process was painless, since they send you the new phone before you return the old one, so you lose no airtime.
saraddictive said:
Hi all,
So iv had 2 nexus 6s so far (the first's screen cracked so I had it changed) and both have several issues, most notably,
- random infinite bootloops on restarts. Phone goes to 'android is starting' pages, and then restarts the whole bolt process again
- I have to restore phone to a backup, whereupon phone works for a bit, before
- infinite bootloops start again.
- also, Google camera refuses to work.
I have absolutely no idea why this is happening, same issue on 2 separate phones, more less. Can someone please help me shed some light on this? This very expensive piece of hardware is nothing but a table ornament at this rate.
Click to expand...
Click to collapse
Yes, as mentioned, flash a factory image to rule out any software issues. However, it is most likely hardware failure. Especially the camera fault. I've noticed this is becoming a rather common issue lately. So, you should probably RMA again.
Thanks guys. I was just concerned as I unlocked the bootloader and rooted the phone almost immediately after I got it. If I try to RMA it, they won't cry foul over a re-locked boot loader,will they?
Also,I have a feeling this might be an OTA that is acting up. It appears that loads of people have had issues after installing an ota (I did this before unlocking and rooting) so I'm going to try to flash a factory image. Thanks guys
Hello everyone,
as an update, I did exactly as dahawthorne and evolution_tech said, and re-flashed a factory image. However, i found it extremely strange that both my nexus 6s were experiencing the same issue so i did a little research.
Turns out, many users from 5.1 have been experiencing issues with changing their dpi in android 5.1 and above. Because I'm not all that familiar with build.prop and using adb shell (tried using it once, it wouldnt work properly so i just gave up), im not going to bother changing my dpi and it works all fine and good now.
To anyone else experiencing the same issue, check this page out: http://forum.xda-developers.com/nexus-6/general/dpi-conflicts-lmy47e-t3061261.
Cheers
Yep, well known issue.
Hello!
My first thread on this one of a kind forum! So here's my problem: sometimes, when I get a call, the phone lights up and shows the caller name and call receiving interface, but no matter how many times I swipe left or right, it hangs and eventually the call drops. But on the other side, the call keeps on ringing. Which means the person on the other side thinks I am a lazy bum who never picks up :| (ie. My mother :|) There are good days and the bad days, meaning, I experience only one or two call drops on some days and then there are days when every freaking call gets dropped.
Solutions I have tried:
1) I noticed the problem first when I updated my phone to lollipop (official update). So I figured maybe the update was at fault. When the problem got severe I decided to roll the version back to kitkat. So I unlocked the boot loader and flashed the firmware.
2) Unfortunately, the problem persisted even then. It's important to understand this problem only started after the update. First four months with original firmware were total bliss.
3) Since even the original firmware gave me a lot of hell I decided to bid adieu to the whole institution of moto firmware and flashed cyanogen 12. The problem is still sometimes evident. Not as much as the moto firmware. But it's still there.
What to do? Is my hardware at fault? I hope not. If not the hardware, then how to fix this software problem? And why is it happening in cyanogen if it's a moto firmware issue? What can I do? Please help! Thanks.
Hello all,
This is my first post on XDA. I've had my Moto X (1st gen, XT1053) since 2014, with relatively few issues. However, I've recently been experiencing some problems. The phone seems fine, but randomly, if I get some notification on the Active Display, and I swipe to check it, the phone seems to reboot- except it doesn't reboot, the screen goes black, and nothing happens until I manually press and hold the power button (at which point the device powers on normally, and I get a "Bug Report"). The device does not overheat before this happens, nor when I power it on again.
I have no idea what could be causing this. At first I thought it may be a battery issue because it first happened while I was charging the phone, but now it happens randomly, even when the phone is not charging. I have tried clearing the cache of different apps that I suspected could be causing this issue, and I even uninstalled some, but I still have the same issue.
I would greatly appreciate it if someone can help me fix this issue..
The device software is up to date, running Android 4.4.4 (Kernel version: 3.4.42-g65e64e4 ([email protected]), Build Number: KXA21.12-L1.29.1.)
I can attach the Bug Report, if it would help.
Thank you in advance!
Hello I recently bought a brand new in box Moto x4 Android one I think and when I got the phone it lasted two days before it went full black, wouldn't cut on, wouldn't light on the charger and acted pretty much dead.
The first time it happened after I unlocked the bootloader, wiped my phone and installed lineage on and TWRP on it from a cmd booted up TWRP.
I got a replacement phone and this one didn't last a night as I tried to do the same thing but I payed attention and noticed the screen darkening as I unlocked the bootloader as a sign of things to come but the same thing happened after I installed lineage and tried to reboot.
I sent the phone back again today and wanted to ask experts here if I might have done anything wrong as I followed instructions from the lineage website and bootloader unlock instructions from Motorola.
This also isn't my first time rooting or installing custom order as I have a 3 year old Moto g4 play rooted with lineage os that's been rough but has been good to me but it's showing it's age(Sim slot went out, speaker messed up, weak antenna).
Hello good afternoon greetings from Mexico, a pleasure to greet you from here, months ago I tried to install lineage in a new motog7 plus since the factory rom is extremely restrictive and slow; in addition to the major security flaws.
at first all fluent install twrp and activate developer permissions, likewise unlock the bootloader; When flashing the phone, there was no problem, even I installed the gapps, the problem started when restarting it simply no longer turned on, it only lit the phone's led in red, when performing some procedures I managed to start it but it does not pass the image.
I have left it charging for hours and only the lightning logo comes out (which implies that it is charging); and in very small letters it says "any key to shutdown".
when I manage to turn on it does not go beyond the android logo.
These are the specifications:
Motog7 Plus Model: XT1965-T
Black
Dual SIM
I have tried to connect it to the pc to flash it and return it to its original state but it does not detect it.
Neither does it enter the recovery mode, the keys simply do not seem to work to enter the modes that it has natively.
Currently I have another phone the same since in those months I bought two similar ones; which I have not touched at all so as not to ruin it.
Any help to revive it would be greatly appreciated, thank you very much colleagues.