Long story short. My TP has CM9 installed and will not turn on at all. I've searched and tried every possible thing to try and get it to boot but I get nothing at all. I'm basically out of options and thinking of sending it to HP for repair. Has anyone sent theirs to HP while Android was still on it? And if so, what did they do or say about it? My wife had dropped it once but it worked fine for awhile and has no sign of physical damage. I was thinking of opening it myself to see if anything came loose or something. Is there a way HP can tell it has been opened in case I still need to send it in after I open it up?
I don't have personal experience, but I would imagine unless the thing is completely broken where they can't get it booted and can't read the filesystem, they'll be able to tell. Technically, you already voided the warranty. I imagine opening it up will make matters worse as far as they're concerned. I believe I've read of people getting their TP fixed even with CM installed, but usually for screen issues that are obvious hardware faults.
I too have had the issue where my TP seemed completely dead, but finally after many combinations of button holding, rebooting, and recharging, it came back.
I will say, in my limited experience with HP's support, they are stellar especially considering the TP is a dead product. I want to recommend just being honest with them, and maybe they'll cover you this one time.
I sent mine in with CM7 installed and they replaced it without any problems whatsoever. My Touchpad had the battery with a question mark issue and they seem to have replaced the logic board along with the battery, but got me my original case back (same serial number, but different MAC address).
Yep I would just send it in as is and not try to do anything further. I highly doubt that they will be able to tell CM9 is installed since I don't think they even try to fix them via software without completely redoing the filesystem.
Have had my Note for almost 2 yrs now, rooted many times. Had the motherboard replaced and currently on extended warranty.
Problem is I have been experiencing sleep of death (phone randomly turns off). There is no frequency to this SOD. Sometimes it happens everyday sometimes in a few days. I thought maybe its a fault stock ROM so I rooted and flashed a custom but the problem is that the problem still exists.
So my question is do you think that the new hardware is causing the problem? If yes can i get it replaced since I am on extended warranty? Ofcourse after unrooting and going back to stock.
But I fear that they will just send it back incase they dont see it happen
xMorpheus said:
Have had my Note for almost 2 yrs now, rooted many times. Had the motherboard replaced and currently on extended warranty.
Problem is I have been experiencing sleep of death (phone randomly turns off). There is no frequency to this SOD. Sometimes it happens everyday sometimes in a few days. I thought maybe its a fault stock ROM so I rooted and flashed a custom but the problem is that the problem still exists.
So my question is do you think that the new hardware is causing the problem? If yes can i get it replaced since I am on extended warranty? Ofcourse after unrooting and going back to stock.
But I fear that they will just send it back incase they dont see it happen
Click to expand...
Click to collapse
Hello.
I used to share the same SOD problem. even though at that time my device was still brand new with 4.0.4 ICS. When I went to CS to complain, all they did were a factory reset. After just 1 day, the problem came back. My wife who bought the same phone also experienced the same problem. we're at loss that time and I even considered selling it. But one day, my device heats up so much that it spoiled the speaker, and I furiously went back to the CS and really gave them a piece of my mind. They replaced the broken parts and also gave me a new battery. ever since then, no more problems.
In case of my wife's, the SOD persists untill I decided to flash her a custom rom Ultimate JB and combined with speedmod's and the problem disappears.
What I was trying to say is, it's possible from the hardware AND Battery (as in my case) Or also from ROM/Kernel Related problem (As in my wife's case) Hers still have SOD's but after a few battery cycle, it srated to lessen n lessen n it hasn't happened in the last 6 months. (Ours also almost 2 years)
Guys, I have a problem with my HTC One M7. Phone is an AT&T phone however it's off contract (on AIO/Cricket) and has been S-OFF'ed, flashed to 4.4.4 with TWRP, etc.
I was commuting home from work on my motorcycle yesterday and got caught in rain/hail. Long story short, I was drenched by the time I got home and my phone got wet.
It's been in a bag of rice since I got home at 6:30PM.
From about 6:30-7:30PM the phones screen was black, but I heard the severe weather warning going off a few times. Then, from 7:30PM till about 1AM, it was in a reboot loop. I tried getting into recovery, etc. with no luck (as soon as I VOL DOWN to go to Recovery from Fastboot, it reboots) At that point, I went to bed so I don't know what it did all night.
Needless to say, this is my last HTC device unless they started making phones with removable batteries again. Regardless of what happens with this phone, I'm going to buy an LG G3 from T-Mobile today off contract.
I don't care what happens with this phone, but my issue or help request is: how do I get it to stay on so I can get my data off? That's the ONLY thing I am concerned with at this point.
IlyaKol said:
I was commuting home from work on my motorcycle yesterday and got caught in rain/hail. Long story short, I was drenched by the time I got home and my phone got wet.
Click to expand...
Click to collapse
Ok let me understand... because the phone got wet and now it refuse to boot, you are saying:
Needless to say, this is my last HTC device unless they started making phones with removable batteries again
Click to expand...
Click to collapse
the phone hardware was damaged with water, not related to the non-removable battery...
I don't care what happens with this phone, but my issue or help request is: how do I get it to stay on so I can get my data off? That's the ONLY thing I am concerned with at this point.
Click to expand...
Click to collapse
Water damaged the phone, if it can't boot its probably an hardware problem and unless you replace the defective component, there is no way to make it boot and backup your data. You should consider making backups of your data on your pc each weeks/months (depending on your needs) with you future phone so if something happen, you'll be able to recover almost everything. Unfortunately you did not and you lost everything, sorry.
I know its frustrating but
the phone got wet by the user fault
data was lost because the user omitted to make backups
So I dont think HTC is to blame here...
keep you phone in some sort of desiccant or even in a bag of rice like you did and hopefully it will be able to boot someday.
My point about the battery was that the phone is a sealed unit and thus I can't get to ANY of the internals without doing some serious taking-apart-this-POS work (which I'm probably going to do now that I have my new phone). If the phone had a removable battery, I'd be able to dry the internals a bit more manually with a cotton q-tip, etc.
The other reason why I mention that I'll never get another phone without a removable battery is because there is NO WAY to stop the phone from rebooting other than letting it die. You know how long it took for the phone to die (I keep it on charge all day)? I literally had to put it in the other room under a pillow to f'in shut that thing up. It went on and on for HOURS.
And thanks for stating the obvious...lol.
Btw, this new LG G3 is SUHWEET.
Had my Nexus 6 for 4 months now - originally had it on stock for a couple of months, it would constantly power off, usually when battery was less than 20% or when trying to access the stock camera or random apps.
So to try and resolve the issue I rooted the device and have now tried practically every ROM available and still have the same problem
Currently running SaberMod 5.1 with Vindicator kernel and the problem still happens.
Tried PA, CM12, PAC, Vanir, Chroma, Euphoria, LiquidSmooth, Terminus....you name it I've tried it.
Will probably be returning it to supplier but before I do would like to know if anyone has had similar issues - is this because of a bad batch of Nexus 6 phones? I guess it's hardware/battery related - but wondered if any software fixes were available?
I have started to face the same problem, mine shuts off usually below 10% but it's only a month old, so disappointed with nexus 6,not only was it effing expensive, it's not the premium device that Google boasted about with so many bugs, which include the speaker crackles and random shutdowns
Totally agree, why pay for a premium device to be plagued with problems?
I was going to try and find if there was a fix but might just return the device.
Really disappointed I expected a lot better for such a high end device.
FWIW, I've had the 6 since November 26th and don't have any issues. I'm sorry you've had issues but that doesn't mean the whole lot is bad. RMA and get a new one. There are issues with every device after it's launched, go to any forum and you'll see what I mean. You can't label the whole line defective just because of a few isolated problems.
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
thx1971 said:
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
Click to expand...
Click to collapse
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Diocat said:
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Click to expand...
Click to collapse
Thanks for getting back to me with this - I guessed there was an issue but didn't want to return the phone unless I was totally sure, so thank you again for clarifying this.
I am not happy to be returning it but looks like this is my only option.
I have the very same problem with my N6 bought in December 2014. Have tried factory reset multiple times without luck. I just gave it for service. The guy there said they would try reflashing the firmware and if that doesn't work I'll be given a replacement. I'm from India btw.
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
drkboze said:
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
Click to expand...
Click to collapse
Almost exactly what happened to mine: http://forum.xda-developers.com/nexus-6/help/refused-repair-moto-uk-device-rooted-t3077271/page2
TL;DR:
Dear xxx,
Thank you for contacting Motorola.
I have now heard back regarding your Nexus 6 unit. After carrying out the initial repair the engineers at our repair centre then discovered a more serious fault with the battery on the phone as it started to swell during their testing.
Click to expand...
Click to collapse
So if your phone is randomly shutting down when their is plenty of battery, and/or does the optimising 0/xxx apps at start up - get ready to RMA because you don't want a swelling battery and a possible explosion/fire...
I've submitted the device to their service centre and awaiting replacement.
Sent from my iPhone using Tapatalk
My device has been returned and will be replaced, no questions asked, as it is a recognised faulty phone.
So to re-iterate, all I was wanting to clarify was if there was a bad batch of Nexus 6 phones and whether or not mine could be one of them - and it looks like that seems to be the case.
I wasn't in any way saying the whole line of phones are bad but it's good to clarify that there is a bad batch out there and the suppliers are willing to replace them
Same exact symptoms
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
rocket808 said:
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
Click to expand...
Click to collapse
Yes on all points there. The random turn off when doing anything, app optimisation (very long) wifi passwords gone (very annoying) and restart again while optimising. And the resultant swelling battery..
It seems very few of us have experienced this, thankfully, but very worrying, I certainly wouldn't get another moto device after this.
Sounds like the very common battery calibration problem, which can be reset by following a set of instructions in the bootloader. Look around for them.
Bumping this as I think I've found the root cause of this problem. Are you guys using Google Fit? The replacement that I got was working fine till two days ago when I initialized/started using Google Fit. Device turned off twice. Then I disabled the app and the shutdown hasn't happened till now. If you guys are using Google Fit, try disabling the app and monitor it for a couple of days.
Well I managed to get a replacement phone from GiffGaff and guess what - same issue again!
Battery overheats, crashes on Camera App, resets WiFi, random app crashes
Have tried several ROMS including Android M to see if there is an improvement but unfortunately not - will try disabling Google Fit now and see if that helps but so far I'm really disappointed.
This device is supposed to be top of the range flagship Google model but for me it is a resounding fail.
I have got the same problem , but i cracked the top of my screen when i had the phone after a month , when i called Motorola they said they could take to repair but would cost £120 to fix screen as they cant send back with screen damage. Really frustrating as i know the screen isn't the fault. Anyone got any ideas ?
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
goinovr said:
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
Click to expand...
Click to collapse
Boot into fastboot, find bootloader logs and hold power for ~10seconds (till it resets by itself), best done on full battery, may help, if not you can try to calibrate the battery (requires root tho). If all this fails only thing left is to change the battery. Takes about 20mins and costs like 20-25usd (easy to do by yourself
Hi everyone. A bit over a month ago, I started getting horrible cell reception on my Nexus 6. I'm pretty sure that was around the time I dropped it on a concrete subway platform. I now miss calls when I'm in houses where my phone always worked. Changing the Verizon SIM card and using safe boot didn't fix the problem. Somehow, factory resetting it seemed to work for a bit, but I started noticing the problem again about a week later or so.
Is there some way for me to diagnose what happened here, and can I repair the hardware if that's what this is?
Does it get worse as the phone gets warm/hot? Try turning the phone off and let it cool down and see how it runs when it is restarted. If it gets better then I'd think a weak to begin with solder joint might have gotten worse.
Larzzzz82 said:
Does it get worse as the phone gets warm/hot? Try turning the phone off and let it cool down and see how it runs when it is restarted. If it gets better then I'd think a weak to begin with solder joint might have gotten worse.
Click to expand...
Click to collapse
Well, I would say that it gets hot as the phone begins to lose reception, but maybe it's the other way around. Also, I forgot to mention that turning on airplane mode and then turning it back off helps. It helps some of the time, anyway.
Thanks.
You can try the dialer code *#*#72786#*#* That will reset all the cellular config data and trigger a fresh activation after it reboots. Seems to be a software issue if you are able to improve it with an airplane mode cycle, if it was hardware I would think anything you do in android would be able to improve it.