Related
Hey guys, I've got a problem and am hoping the minds at XDA can help.
My brother and I both have a Nexus One and both have unlocked bootloaders. I've never had a problem installing custom roms or restoring back to the shipping rom, or suffered any problems whatsoever.
However his phone, suffers random reboots all the time. I unlocked his bootloader and from the very first Rom we had problems. I double-checked my methods and even tested it again on my phone with no problem whatsoever. So, he got back into town today and I restored his phone to the shipping rom (userdata, boot, system, radio, etc.) It still randomly reboots. I thought it might have been a bad battery and swapped it out with a different one, and I was able to mess around longer with the phone, but it still rebooted on its own accord.
I told him he could call HTC, but more than likely he would have to pay 180 dollars to replace the motherboard on the phone. He says he'll just deal with the random reboots instead of the possibility of paying the money.
Does anyone have any suggestions as to what the problem could be, because after reflashing the shipping rom I'm out of ideas. Another odd thing I noticed with his phone from the get-go was the haptic feedback and vibrations in general, they were barely noticeable, almost non-existent as compared to my and my friend's nexus one.
my n1 having rebooting loop problem when i use it continuosly for 5-6mins or performing some task.in airplane mode i can use it for 30-40mins but then restarts and keeps restarting until i give it 3-4min rest before starting it again.probably this happen after 2.3.3 ota updat.
Wipe data (factory reset) and try again.
If it doesn't work - use "unroot/restore" guide in Wiki, PASSIMG with FRG33 image, test it.
If still reboots - use the warranty, something's wrong with your HW.
You can also look at the logcat to see, what is the problem that causes the reboot. Looks like something's overheating.
i am Having the same problem, i have unlocked bootloader and installed the latest cyanogen rom hoping the rebooting problem would be fixed but no luck ,,the rebooting or the overheating what ever causing it persist.
i don't know what else to try??!!!
i really like the phone and don't feel like buying a new one yet. nothing on the market right now convinced me to ditch my n1.
i am just sad that the hardware life span of of the n1 is 1 year only.
yah thats is overheating causing it.because when it becomes hot it goes into restarting loop until i cool it down.still dont know exact problem though.
Jack_R1 said:
Wipe data (factory reset) and try again.
If it doesn't work - use "unroot/restore" guide in Wiki, PASSIMG with FRG33 image, test it.
If still reboots - use the warranty, something's wrong with your HW.
You can also look at the logcat to see, what is the problem that causes the reboot. Looks like something's overheating.
Click to expand...
Click to collapse
Isnt the warranty void after you've unlocked the bootloader?
kled54 said:
i am Having the same problem, i have unlocked bootloader and installed the latest cyanogen rom hoping the rebooting problem would be fixed but no luck ,,the rebooting or the overheating what ever causing it persist.
i don't know what else to try??!!!
i really like the phone and don't feel like buying a new one yet. nothing on the market right now convinced me to ditch my n1.
i am just sad that the hardware life span of of the n1 is 1 year only.
Click to expand...
Click to collapse
I had that problem when my CPU speed was over 1000. Maybe this'll help?
illuminarias said:
Isnt the warranty void after you've unlocked the bootloader?
I had that problem when my CPU speed was over 1000. Maybe this'll help?
Click to expand...
Click to collapse
I don't think it's the cpu because since 2 days ago the phone started rebooting while charging without me working on it. so now i have to turn it off before plugging the charger, or it will hang on the x for hours.
i guess it's time for me to look for a new phone..too bad, i really like the n1.
yes nothing wrong withcpu its hardware problem.i also cant recharge it while on.
i keep it in fridge then it work fine.after little heat up it goes into loop again.
I've also had the rebooting loop when I had a bad battery fwiw. Changing the battery to a new one solved the problem.
I was having the same problem when it's charging (and I use the N1 a bit) and when I use the 3G data (surfing the web, installing apps from the market, etc.)!
And it's the 3rd time that I've sent my N1 to the Tech Repair!!!
Never repaired the first 2! I hope this time will be ok... I'm waiting for my Nexus 1 to come again with me...
This seems like a big N1 defect.
I called HTC today. Out of warranty repair in the USA is 55$ to 283$ plus shipping.
Could have bought a Nexus S for the 500$ I'm spending on repairs + devices.
*************
Update 5/5/2011
HTC fixed mine even though I unlocked the bootloader. No charge. Free overnight in both directions.
this is making me so much angry.although my n1 is in canada warranty but i am now in pakistan so dont what to do?even we dont know about the exact problem.is it board or something small problem?
I have a general question about sleep death, is this always a hardware issue? I have recently flashed stock Gingerbread KH3 and have noticed it occuring now whereas it never happened when I was on Froyo Firefly or Gingerbread KF1. I have also switched out the battery but the issue persists. Any ideas or suggestions before I warranty it?
-it seems to occur when left idle for 3+ hours.
-it does not occur when it is plugged in to the charger.
My IMEI was not one affected by sleep death according to the AT&T press release.
Maybe it was a bad flash, try reflasing?
God luck
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I have also read on another post that this may occur when running any roms based on stock Captivate, thus I asked if this was only a hardware issue, thanks for any responses.
iphaded said:
I have a general question about sleep death, is this always a hardware issue? I have recently flashed stock Gingerbread KH3 and have noticed it occuring now whereas it never happened when I was on Froyo Firefly or Gingerbread KF1. I have also switched out the battery but the issue persists. Any ideas or suggestions before I warranty it?
-it seems to occur when left idle for 3+ hours.
-it does not occur when it is plugged in to the charger.
My IMEI was not one affected by sleep death according to the AT&T press release.
Click to expand...
Click to collapse
The random shutdown issue has been quite well documented as a hardware issue. The most common understanding is that it was caused by a problem with faulty internal memory. If that is so, it is possible to explain the various reports that the shutdown issue occurs only on certain roms, or first appears when switching to a new rom. Because different roms access memory in a different way, the new rom may have accessed an address space in memory that had not been being used by the previous rom.
That is not to say that your phone has the well documented random shutdown issue. But I was never convinced that the IMEI information in that unofficial press release thread was really useful. A better general guide was when the phone was manufactured. I think the phones manufactured after a specific date were quality controlled to not have the random shutdown issue. I don't know the date, but it was probably somewhere in November or December of last year. You could maybe find more specific info on the date by searching.
Hopefully, your phone's issue is something different, and possibly caused by software. The only way to know is to try to solve the problem with software solutions through trial and error over an extended period of time. If unable to correct the problem, then it is probably hardware related.
My first phone developed the random shutdown issue somewhere around three months after I got it. I tried solving the problem through trial and error for almost three months after that before I had it replaced by AT&T under warranty. The replacement phone I have now has been golden.
Hope this helps.
Thank you for your thorough response. I will do as you suggested and try different roms. I did purchase my phone from Ebay but did also get a Squaretrade Warranty so I hope that they honor it if it is in fact a hardware issue.
I reflashed Gingerbread KH3 and the phone would still randomly shut down.
Upon reverting back to Stock Eclair, and leaving the phone on standby overnight for the last 2 days, it has not shut down on its own.
Out of the blue yesterday, my AT&T Moto X stopped vibrating. I noticed it first with the soft keys (home, back etc) but it affects everything from vibrating on ringing, to enabling silent mode, to unlocking with active display, to games.
I've tried rebooting and toggling vibration in settings. I've downloaded vibration tester apps from the Play Store. I only have the same ~70 or so apps that most of us use (dropbox, weather channel etc) and I don't run any obscure apps (less than 1000's of downloads), and I hadn't downloaded anything new for hours before the problem started.
I feel I've tried all the basic stuff, except factory reset, I don't think there's anything too obvious I'm overlooking.
So that leaves me facing either a hardware or software problem. I doubt its a problem with the physical vibration motor. Factory defects are so ridiculously rare that it should never be your first course of action. However, if it's a problem with the hardware I could try my local ATT Service Center. If it's a software problem, which seems much more likely, I could try a factory reset on the device. However it seemed a wise idea to post this question to the pros before I go down that road.
Appreciate any help you guys can offer.
AT&T Moto X
4.4
Not rooted
I would try a factory reset if you done everything else. My wife's Galaxy S3 did the same thing after the update to 4.3. A factory reset fixed it.
my gf's at&t motox running 4.2 lost vibration too. after many many reboots it would randomly work, or work very weakly (so it wasn't a problem with the physical motor, maybe it was an electrical connection to the motor?).
it was covered under warranty. they gave her a code, she re-did motomaker, and returned her original broken phone in the box the new one came in.
I hate the vibration in this thing. I would love mine to stop lol
Sent from my XT1058 using Tapatalk
I just performed a standard factory reset on the device and the problem persists... No vibrations, anywhere.
Is there anything else I can try? or am i headed to a service center?
Deenybird said:
I just performed a standard factory reset on the device and the problem persists... No vibrations, anywhere.
Is there anything else I can try? or am i headed to a service center?
Click to expand...
Click to collapse
You can sbf back to 4.2.2. I had a connectivity problem and a factory reset didn't fix it. But going back to 4.2.2 and taking the OTA did.
All the files are in the Dev section. If the links are broken I have copies of everything I can share. Except the 4.2.2 file for att I have Verizon.
Sent from my XT1060 using Tapatalk
If that doesn't work then your only other option is a warranty claim. Or live with it I guess.
The final verdict:
With nothing else working (factory reset, safe mode etc) I took the device to the ATT service center. They replaced the device, attributing the problem to defective hardware. Still find it hard to believe it was actually the hardware, but I don't see any other conclusions to draw.
Thanks for everyone's help.
Deenybird said:
The final verdict:
With nothing else working (factory reset, safe mode etc) I took the device to the ATT service center. They replaced the device, attributing the problem to defective hardware. Still find it hard to believe it was actually the hardware, but I don't see any other conclusions to draw.
Thanks for everyone's help.
Click to expand...
Click to collapse
At least it worked out and you have a working phone again.
I am with this problem right now and i can´t fix it.
After i flashed CM13 without Gapps my Moto X 2nd (xt1097 brazil) all vibration stopped working.
I tried going back to stock rom 5.1, 6.0 and even NX 10.1 but with NX i can hear something vibrating the phone, so i eliminated the possibilite of a hardware malfunction.
I don´t know what to do...
please help
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.