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
Related
so i got my nexus 7 back around january and right when i got it i unlocked and rooted it with the tool kit. I was flashing many ROM's and kernals too but im a college student and got busy around march and so i wasnt using it and it was just sitting in my drawer. At the time it was in my drawer i remember it was working and powering on. So last month it came to my mind that i wanted to use the nexus 7 since i have time now. I go and look for it and when i found it and tried to turn it on it just wouldnt turn on.
First i plugged it into the charger with the ORIGINAL cable and plug for the whole day but when i plugged it in the screen started flashing every 3 seconds with a plain white light. So i tried booting into recovery using the power and volume buttons and that didint work. So i searched around the web and found that pulling out the battery and re connecting it works for most people. So i tried that and nothing changed. Right now its sitting plugged into the charger...flashing a white light every 3 seconds. So what else can i try? Idk if i have warranty too so im worried right now. The original owner received it as a gift and he was like 45 years old and didin't have the receipt to return it. My brother knows this guy because hes a regular customer and he bought it off of him and gave it to me knowing i like android devices. So i don't have a receipt for a RMA so idk what to do. Another thing is that the bootloader was unlocked last time i used it.
Please dont ignore this post and give me an opinion on what to do. Recommend me trying to give it to a electronics place to have them look at it and quote me how much would it cost me to get i fixed?
Your battery has discharged too low and your tablet has entered a form of hibernation to prevent it from becoming permanently damaged. Plug it in and hold all three hardware buttons to boot to the bootloader. From there, select power off. You should then be able to charge and use your device normally. These instructions are among the potential steps to take posted in the sticky thread at the top of this forum. http://forum.xda-developers.com/showthread.php?t=2090826
TL;DR: Any way to fix/flash a Nexus 7 that reports it's in APX mode to Windows yet, that won't do anything else?
Backstory: I've had a 2012 Nexus 7 32gb since the day it came out (Oct 2012 or so?). Worked great for a year, loved it! Had AOKP on it, unlocked/rooted, used tons of apps, never a single problem. And then one day while I was using it to play music while charging it, out of the blue, it hard shut off while it was running, rebooted and shut off during boot and... never turned on again. Wouldn't indicate a charge, wouldn't turn on, couldn't get it to respond to any power or volume key presses, nothing.
I called Asus, and they agreed it needed to be repaired. I sent it to them, they sent me back the same unit, repaired, and said they swapped the mainboard out in the repair notes. Worked great, except the device was completely wiped, relocked, unrooted, and they removed my nice Stenheil screen protector.
I was without it long enough that I got used to not having it. Since it was completly back to stock, I decided instead that I would sell it when I found a good buyer (friend, etc), and buy the new 2013 Nexus 7 instead. I found a friend who wanted it a few days ago.
Today's Issue: I charged it over night last night so it was on a full charge this AM. I saw that I was still running 4.3 on it (hadn't really used it since I got it back in November), so I did the factory/official "OTA" update to 4.4.2 this AM. Went flawless, no issues, booted up fine. I updated all the apps on it, also worked fine.
I then decided to do a Factory Reset on it, (Thru Backup/Reset IN android, NOT Recovery). I went thru the confirmations/warnings, and then it said "Shutting Down..." and, it shut down. I let it sit for a few minutes, expecting it to boot back up (it never did). I tried to turn it on, nothing. I tried ALL combinations of power + volume, + charging cable in/out, etc. Everything possible, trust me, I scoured the web for new combinations and timing ,etc. No matter what, I never got ANYTHING on the display, no charging indicator, no recovery or bootloader, nothing. It's like the display is dead. The battery was fully charged this AM after being charged overnight so I know the battery wasn't even close to low. It's like it's completely dead no matter what I do.
I then tried to hook it up to my PC, which is setup for ADB etc, couldn't see it in ADB. In Device Manager though, it's showing as being in APX mode? So I tried holding power down for 10 seconds with it connected, and it DOES disconnect from windows, and a few seconds later, it shows up again, again in APX mode. Nothing ever appears on the display. Holding VOL down or all three buttons while plugging into PC never changes anything, no matter what, it ALWAYS shows in APX mode.
From what I'm reading online, this is a sign that the bootloader is missing or corrupt, and, that there isn't a fix for that unless you first backed up your crypto "blob" using Flatline (which I didn't even know about till today). I'm hoping that maybe what I've read is out of date? Is there perhaps a way to fix or flash this yet?
The whole thing makes little sense. All I did is update it, then reset it, all officially supported/normal things, on a bone stock tablet. It seems more like they didn't ACTUALLY fix it the first time it went back to them....
Help? AFAIK the tablet is now out of warranty. I just want to sell it and get the 2013 model! The tablet is in perfect shape, it's been used with a screen protector and case since day 1 - not a single scratch on the screen or case. :crying:
i'll take the silence to mean I'm screwed, right? :crying:
I don't know how, but it seems your bootloader is gone. (corrupted sector on the nand,maybe)
You can't do much without the proper blobs.
If I were you, would try to send it back to Asus. They are the only ones who can repair it.
Wow I can't believe it's been two months, but, I still have this tablet, still not working, Asus won't fix it for a reasonable price... anything changed on this in the last two months?
It seems like it should be possible to do something... maybe I'm just optimistic.
I want a 2013 Nexus 7 but it's hard to pull the trigger knowing my very lightly used gen1 model failed twice now.
There is no way to produce an universal blob and device specific blob creation is working so there is little to no reasons for further development.
You could fit a new motherboard 32gb ones are expensive but the 16gb are a lot cheaper
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
They're readily available on eBay - $35 for a used 16GB motherboard, and $50 for a 32GB board. That's how I fixed my APX bricked N7...
Whoever stumbles across my late entry, if the N7 won't boot after empty battery, no button combinations work and PC shows only APX mode - take off the back housing (it's pretty easy to do) and disconnect and reconnect the battery cable, this let me boot it up immediately...
(my N7 however was plugged over night to charge before I attempted this unplug but actually didn't show up the charging indicator and wasn't bootable, surprisingly it was charged already half when I finally could boot it up)
Sent from my OnePlus5T using XDA Labs
Apparently it is possible without having done the backup first, at least for some people.
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-blob-bin-t4083879
I was listening to an audiobook when my phone suddenly died. It would not start back up, so I removed the battery. When I replaced the battery, the samsung logo would pop up but after about a second it would go black again. It will not start again until I remove/replace the battery, at which point it does the one second shutdown again.
At one point I got the phone to boot (no idea what I did differently) and I noticed that it got very hot around the camera area before going black again. A second time I was able to get into recovery, where I did a factory reset. Booted back up and it seemed to be okay, but then heated up very quickly and shut down.
Now, even if the phone is totally cool, I cant get past that 1 second of samsung logo. I'm really at a loss here, and totally screwed without my phone because I am traveling non-stop for the next 2 weeks. Does anyone know how I might try to troubleshoot this? Thanks
Possibly flash a new ROM and start over. That's what I would do
This EXACT situation happened to me yesterday! I was streaming from Google music, it was on the charger and things were fine. A call came in and the phone started vibrating like crazy and wouldn't stop. The screen went black and it kept vibrating. Finally it went off. On boot it will get to my lock screen and then crash after about 30 seconds. If I take the battery out and try again it lasts another few seconds after boot. If I leave it for a LONG time with the battery out and restart it I can get like 2 mins on the next boot without it crashing. The top part by the camera is getting hot on my phone as well. Recovery mode and download mode start fine and the phone doesn't crash. I have some data on the internal that I want to save so I tried to use Odin to flash the most recent build L720VPUFNG2 as that would just install the OS and not touch the data. On the next reboot things seemed to be working fine and I got maybe 5 mins out of the phone before it crashed again. I still don't have enough time to get the data off so I think I'm just going to say screw it and wipe it completely. You guys know of a way I can backup this app data using Odin or recovery mode? My phone is currently unrooted. I'm new to all this tinkering stuff. Phone is out of warranty now anyway.
Threw on a custom recovery, backed up all my data, did a full wipe, now I am good as new.
It worked for awhile but now it is back to rebooting itself. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
i7vSa7vi7y said:
I have no idea maybe try just using your stock battery for a couple days. See how that goes then use your other battery for a couple days and see what happens.
Click to expand...
Click to collapse
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
killerz298 said:
I think it was one of the xposed modules causing the issue. I realized the rebooting seemed to happen whenever I pressed the power button. I had installed a power menu module so perhaps it was the cause. I restored from a nandroid and uninstalled that module and things seem to be working now. Hopefully that was the cause and this thing won't start acting up again after the return period.
Click to expand...
Click to collapse
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
i7vSa7vi7y said:
That makes a lot of sense. Have to be careful with those Xposed modules. Don't get too carried away installing so many at one time and playing with them and then rebooting. You'll have a hard time figuring out which one is causing it. I'm pretty sure you found your problem.
Click to expand...
Click to collapse
That is exactly what I did I installed like 6 at once and things were working well for a few hours then disaster stuck. I think I won't play with this phone anymore as I am upgrading anyway and want to sell it in working order.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=
Hi everybody,
What Happened:
My phone has suddenly become totally unresponsive. I have been using it most of the day, it was sitting at around 70% the time that it happened, but it is now a totally black screen. I had just taken it out of my pocket and it was suddenly like this.
The only idea I could come up with as to why this happened is that I charged it off of a JBL Charge 2 last night. I'm not sure if that may have messed with the battery, but I do find it odd that it's totally unresponsive while plugged in.
I was running android 7.1.1 DP2, with the ElementalX kernel 4.0 I believe. I was also rooted with SuperSU. What's really odd is that I hadn't done anything new recently besides install uTorrent and VLC media player. Otherwise, my routine has not changed one bit. Up to when the phone actually died, I hadn't even used either of these new apps the entire day.
What I've Tried:
I have tried plugging it in via AC, via USB, I've tried booting into recovery or fastboot, but there is zero response from the phone. No indicators on the screen, no LED blinks, no vibrations, nothing.
What I'll Try:
If anyone has any experience with this happening, I could use some advice. Otherwise I'm just going to wait it out, consider an RMA I guess. However, my device did have the bootloader unlocked and was rooted, so.... I hope it comes back by itself.
My advice is to keep it plugged in, or see if there is a response on the computer perhaps on fastboot, upon using the bootloader keys. I haven't had this, just a few suggestions. Good luck!
PS: A RMA will probably be needed, there are much more experienced people around here. Sure you may get replies later.
Good luck?problem all nexus 6p!!! Lg responds repay helps, hawuei what to do? problem arises with nogaut not be our fault, how to fix this? My phone now in service but to be fair this? warranty and having to wait ..
I decided to start a thread because I noticed there were multiples about this issue. So 3 days ago I was on Facebook when my phone randomly froze. I pushed the power button, and that's when it began bootlooping. I instantly tried booting into recovery with no success. I was hopeful, however, because I could still access the bootloader. I got on my computer and began researching the issue and steps I could take to fix it. I tried every method out there and was unsuccessful. I ended up buying a Pixel today off Craigslist and am loving it so far. So anyway since my Pixel came with the OEM charger, and I had been using a non-oem ever since I had my 6P, I decided to plug in the OEM and see what happens. Within the first hour my 6P began to get very hot, almost to the point where I couldn't even hold it in my hand. Keep in mind the phone was still consistently boot looping the whole time. So I decided to unplug it. Well I left it sitting and went about my business and when I came back to my bed I noticed it was doing the Google boot animation!!!! I started freaking out! After it booted up I finished the tutorial stuff and just let it sit on the home screen for a second. I noticed the battery was low so I figured I would plug the charger back up and let it charge. Well in the time it has taken me to write this post, it just started boot looping again... Lol. So I just unplugged the charger AGAIN, to see if it will boot up again. To me, it seems like there might be a hardware issue with my battery. Anyway, my 6P was rooted and running nitrogen OS (wasn't running the latest build but was 7.1.)
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
dontbeweakvato said:
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
Click to expand...
Click to collapse
As of now it is still boot looping and no it doesn't boot into recovery. Only symptoms I've noticed is the phone starts to get extremely hot when I plug in the OEM charger that came with my Pixel. I figured they were the same so that's why I decided to use it since it was OEM.
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
dontbeweakvato said:
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
Click to expand...
Click to collapse
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
e1ement08 said:
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
Click to expand...
Click to collapse
my first bootloop years ago i thought the same.
it wont fix itself. its not a software isssue because youd be able to at least boot into bootloader. it sucks to hear the truth but thats the truth.
its a hardware issue and you could take it to a repair shop because they will inspect and fix. small drops that dont harm the device can ultimately cause small breaks in the solder joints so who knows what is wrong without inspection