Database Users

[Q] How often does yout TPT shut itself down?

It seem that my TPT is shutting itself off more and more often.
Sometime just like that, sometimes when charging.
I can't figure it out.
It also seems to take longer and longer to get the "buzz" when restarting.
Any thoughts??
Thanks

My TPT is rock solid. Not one reboot yet.
As you are observing longer and longer times for powering up this could be start of a failing power button. It is a quiet common issue

I've already had my mother board replaced.
Took about 2 weeks, no charge.
Looking at some of the complaints, not too bad.
Here we have IBM doing Lenovo guarantee work.
I hope it is not the power switch again.
I think it is something else but do not know what.

No reboots at all here. A few forced closes but no reboots. Maybe the forthcoming ICS from Lenovo will work out most of the bugs.

Maybe try installing a log app. You can try inspecting the things that happens right before the shutdowns.

Mine started doing the same and I sent it in for repairs. New mainboard was inserted and it took 5 working days.
I suggest you do the same, agian..
I don't know the laws and regulations of your country. But here, in Denmark, if they can't fix it by 2. try, you can demand a refund.

Same issue here, but I don't think that it shuts down...I suggest that it's more like falling in a deep deep sleep. Everytime it happens, I have to force a restart (press the power button for 10-11sec.?) But sometimes it wakes up again, after holding the pwr button for 2-3 sec. Just tapping the botton doesn't help too often.
And everytime it happens, the WLAN is on. If i turn on the flightplane mode, it won't shutdown....pretty strange..

Send it in for repairs. It's a systemboard issue. Mine was replaced and the issue was gone.

Possible reboot issue solution- not a software solution - YMMV

So everyone has talked about the reboot issues. I'm going to throw out something that HAS worked for me. My tablet was full stock, fully upgraded to Asus software as of about 4 weeks ago. I experienced random reboots at odd times, off, on, in my backpack. I could turn the screen off and on or reboot by pressing on various locations on the screen. I decided to pop off the back to look inside and noticed that the power button plastic sat VERY close to the power switch (think its a button type SPST?). So i took a razor to the power button plastic and took off about 1mm of the protruding plastic. Since then (about 4 weeks), I have gone from a reboot every day or so to one reboot in 4 weeks. The power button is still easy to depress, but has another 1mm of throw. I'd really hate to get pictures, but if anyone thinks they need them, I will try to make or find some.

I had the reboot issue a couple of months ago, it happened about once or twice a day. I RMA'd it to Asus, they made an appointment with me to pick it up from my home address and about 1,5 week later I got my tablet back. The repair letter said that my tablet was unstable because of a faulty mainboard, which they replaced. I haven't had a single reboot since

Yes, I noticed it to, I managed when I put my tablet into the backpack - sometimes it reboots/shutdown - my solution, put the tablet with the power button up. But a picture what did you the power button will be fine.
Sent from my unlocked ASUS TF300T

Won't turn on

I got my phone yesterday, and it was working for about 18 hours. All of a sudden I picked it up at work and it is no longer turning on. I tried plugging it into the charger, holding volume up + power, holding volume down plus power, but nothing worked. Has anyone else had this issue? I called Google support and they are going to send a new phone, but this doesn't give me a lot of confidence in this phone.

someone on reddit posted something similar. ended up RMA'ing the device as well. not sure what's up with this scenario - loose battery maybe?

Google is sending a replacement unit. It really sucks because I cut my sim to be nano from the nexus 5, so I can't go back to my old phone at all.

shaklee3 said:
Google is sending a replacement unit. It really sucks because I cut my sim to be nano from the nexus 5, so I can't go back to my old phone at all.
Click to expand...
Click to collapse
Use a sim adapter

shaklee3 said:
Google is sending a replacement unit. It really sucks because I cut my sim to be nano from the nexus 5, so I can't go back to my old phone at all.
Click to expand...
Click to collapse
Google sends a replacement unit overnight. Should arrive the next day, so you won't have a phone for at least 1-2 days.

jaidev.s said:
Use a sim adaptor
Click to expand...
Click to collapse
Thanks. I ordered an adapter in the meantime just in case something happens on the next phone.

zephiK said:
Google sends a replacement unit overnight. Should arrive the next day, so you won't have a phone for at least 1-2 days.
Click to expand...
Click to collapse
I'm having this issue as well. Phone worked well since Oct 29, then all of a sudden it shut down and will do nothing. I've requested a new device and Google support is telling me the phone won't ship until the 12th, when the rest of the Google Play Store orders ship. I stole my daughters phone in the mean time, but I can't wait a full week to receive the replacement as one of us will do without till it arrives. I may request a refund and buy a phone locally. Sad-- I waited a month for this phone, ordered on launch day. I shouldn't wind up in the regular queue to get the phone replaced. Poor support if you ask me.

Same thing for my N6p, picked it up and it was off. It's a brick now.
I called and was told they would ship me another, I just saw that its going to be a few days until it gets shipped out.
I transferred my Straight talk to the new nano sim, now I cant go back to my N5.
No phone for a few days.
Dang

Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.

deanb1234 said:
Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.
Click to expand...
Click to collapse
I had the same problem, put the phone down on my desk and picked up a brick. Tried deanb's method out of boredom and desperation, basically, and it actually worked for me as well. I think I held my power button for about a minute and a half before it booted back up. Very weird.

same
Same thing just happened to me, thank you so much for the tip!
Lets hope it will not be a recurrent problem.

Hold Power button+volume down until it turns on....it might take a min. or more.....it happened to me

IF your guys phones turns on, I would still suggest RMA'ing it back to google. There's obviously something wrong with it, don't be lazy. You'll thank me later

My sons just did the same thing. He had 15% and put it in power save and cut the screen off and it would not come back on. Charged it for a while and then read this post. Held the power button down for around a minute and Bam. Working fine now, powering on and off as normal. Thanks alot for the info deanb1234. Still gonna get rma, bad thing he got it from Huawei not the google store and their cs is the worst i have ever seen.

Had the same thing happened. Thankfully it was within 14 days so I returned and got a new one immediately. (Got it from a carrier)

I am having the problem right now. The phone was fully charged and I used it for 10 minutes this morning. The screen went black after 1 minute as normal. I used the finger print reader about 15 minutes later and it would not turn on. It is essentially dead as a brick. I will try to hold the power button + Vol down for over a minute to see it it works. The phone was working flawlessly beforehand. I did not have any problems whatsoever.
My question. Will I have a problem getting Google to RMA the phone if I get it revived? Can they tell if it is currently working? I would like to RMA the phone regardless just in case it is faulty. I purchased the phone in late Oct 2015 and I did not buy the insurance.
Edit: I got it to work again after holding down the power and volume down. Anyone find a cause for this problem? I was systemless rooted for several weeks but everything else was stock.

Wanna ask all you folks who are just sending phones back willy nilly. Are you wiping the phone of your personal data such as Google account etc? All you really have to do is just hold the power button for a while and the phone will turn on. It's not really a defect (well technically perhaps), but why not turn the phone back on and factory reset it before sending it back? Some dude in a warehouse is probably gonna turn your phone back on and he now has access to your Gmail account and God knows what else (if you don't have a screen lock). What am I missing here.
Sent from my Nexus 7 using XDA Free mobile app

I was planning to use android device manager to wipe device if I could not get it to respond. Factory wipe reset along with flashing system image is best option if possible.
systemless root may be cause in my situation . I was using older 2.62 apk. I will give it another few weeks and try new root when Jan security update is released before RMA.

biggolfer said:
I am having the problem right now. The phone was fully charged and I used it for 10 minutes this morning. The screen went black after 1 minute as normal. I used the finger print reader about 15 minutes later and it would not turn on. It is essentially dead as a brick. I will try to hold the power button + Vol down for over a minute to see it it works. The phone was working flawlessly beforehand. I did not have any problems whatsoever.
My question. Will I have a problem getting Google to RMA the phone if I get it revived? Can they tell if it is currently working? I would like to RMA the phone regardless just in case it is faulty. I purchased the phone in late Oct 2015 and I did not buy the insurance.
Edit: I got it to work again after holding down the power and volume down. Anyone find a cause for this problem? I was systemless rooted for several weeks but everything else was stock.
Click to expand...
Click to collapse
Do you send your phone to google anyways? or just cancel the replacement?

GMScreech said:
Do you send your phone to google anyways? or just cancel the replacement?
Click to expand...
Click to collapse
No, I did not return the phone and no issues have occurred since. I suspect it was a problem due to rooting the phone. I was using a beta version of SuperSU.

Never seen this before!

I had an alarm app give me an alarm last night but I was busy in another app and dismissed the alarm in a way that the sound was still going. The only thing I thought to do was to do a reboot of the phone. I gave it a few minutes and when I pulled it from my pocket I noticed that it had not rebooted. So I held the power button for a few seconds and waited for that vibrate then the "Custom" screen.
Nothing.
Held the power button for about 30 seconds.
Nothing.
Good battery, at least 75% before this happened. No sweat. I have a spare battery that I know is 100%. When I put that one in, the phone immediately did a vibrate and gave me the "Custom" screen. Then dead. Power button did nothing.
Pulled the battery and upon insertion, I got that vibrate again. But this time I held Volume+ and I get that tiny blue bootloader message at the top of the screen for a half a second. Then dead. Tried it again and this time did Volume-, this time I got download mode for half a second. Then dead.
Tried all this with power plugged in and get even less. Nothing.
Connected it to a PC (OEM cord straight into the motherboard) and got nothing. No charging LED, no sound from the PC upon plugging. Nothing new showed up in Device Manager.
Did I just do the "Low Effort Brick" method just by rebooting? I have had this thing for a few years, running CWM then TWRP. Several ROMs in the past, xposed, done it all and never once even had a boot loop. Now I have a brick because I rebooted a phone that had been VERY stable for weeks (on Dan's GPE ROM)?
I am not so concerned about the device, I actually ordered a LG G4 already. What I REALLY want is the autobackup of Tasker that is in the internal storage. I know I have a TiBu of everything on the microSD and a TWRP is on there too. But both are a few days old and I have made many changes to Tasker in the past few days. Tasker updates a backup every time you leave the app, so I know I have a very recent file in there. But how do I get it?

It's not bricked. The power button on some S4's are janky. Mine did the same thing for a while. You can try smacking the power button on the corner of a desk or something but otherwise either just keep pulling the battery and trying, try opening it and cleaning the switch, or try replacing the switch.

It's hardware issue with power button. I've got the same issue with my S4. The only solution is to replace the button.

Good advice. Found a few YouTube videos that are pretty close the issue that I have. I shall do some work on this this weekend. Thanks for taking the time to respond!

Hell yeah. Effin HELL YEA. Found a few YouTube walk through videos and got down to the switch. Using my ever-awesome Simpson 260, I was able to determine that the power switch was bad. I exercised it a few dozen times and then it went open. Roughed everything back together (without screws) and got a boot.
Immediately made a TiBu of everything. I will also make a TWRP as soon as that is done. Now I have to source a power switch. I should have no problem replacing the switch. I have a fantastic solder station at work and a 20X magnifier. This shall be my crutch until the LG G4 arrives.
Thanks again for the advice. Proof again that this is a real community.
Side note: I went to AT&T to get my old Vivid back into action to replace my S4. When I mentioned that the device was rooted, they replied with some statement that my "jailbreaking" the device is what caused the failure. I asked if she knew what rooting was, and she said "yeah...jailbreaking". I asked her if she knew what an "unlocked bootloader" was and she just glazed over, mouth open. When I told her that the device has been rooted for years with no problem, she insisted that the problem happened when I "jailbroke" it.

Nexus 6p - bricked?????

Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.

Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.

If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.

Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.

Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838