Related
Hey guys,
I've done some searching on this issue, yet I can't find much besides battery problems, or people who have contacted T Mobile and got warranty replacements. I've had some issues with my G1. Over the past month or two, my G1 has been rebooting repetitively, and this week it's gotten BAD. I would open a SMS, and then BAM. Start dialer, and then BAM. Reboot. Hell, even in the middle of a reboot it would reboot. Cool huh?
Anyways I called T-mobile customer support and they said I'm out of warranty. Great. Well, it still turns on, and it still operates when it's happy, so maybe I can work with this for a little bit... I did some searching, and some people attributed it to a software glitch in the gyroscope... Most people called T-mobile and got a warranty replacement. I'm over the one-year
I'm not about to say this is because I had CyanogenMod on it, because I would wipe, and put it back to an older version and it would still reboot... even in the SPL, it would reboot. But regardless, I decided to follow this how-to to unroot my G1: http://forum.xda-developers.com/showthread.php?t=491350
After step 6 (6. Push Alt+S on your G1 to flash it with update.zip), it came up with an error about the splash... "Cant store hboot image."
Well anyways, before I could do anything about it, guess what happened?
Yeah, it rebooted.
It came up with the unboxing logo at first, I didn't know what to do. I had forgotten what this meant, so I heled the power button down ( I realize this may have been the misteak I made, however there was nothing visual indicating anything was being done).
It shut down, the screen went blank, the charge LED remained on....
I pressed power.... Nothing.
I unplugged the phone, took out the battery.... put the battery back in... Nothing. The screen stayed black. Now my phone will not power up, and there is no LED charging indicator.
Anyways, I'm lost. This is my second G1. I'm slightly pissed and I feel bad for the T-Mobile rep on the other end of the call I just had, but, really, I can't spend $1200 a year on a slow phone.
Do any of you guys have any suggestions?
Home+power does nothing.
Camera+power does nothing.
Putting in the cable lights up no LEDs...
It is literally a brick. An unresponsive brick.
Well, I ended up taking the mainboard out of my old phone and putting it in this G1.... Everything should be back to normal however I'm still looking for responses as to what might be happening.
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 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.
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
Anybody ever have this happen to your MZF? Happens once every few days, and usually goes away after a few shakes. A few times I hard-rebooted the phone, and the display was still messed up in Recovery mode; the top half of the screen was affected but not the bottom. I could actually see the rows of static being drawn on the screen in big chunks. I can't remember if it was happening before the 7.1.1 update, but I think it was. Thinking it might be a faulty connection?
My phone did that around that time. It went away, but it's back now. Not only is it back for me, but it won't actually reboot. I can hear the splash screen (as if it was rebooting) however, the screen doesn't change. Still stuck with those crazy lines.
I had this happen... probably about 3 separate times. Each time there would be moments (either after tapping it, squeezing it, rebooting it) that it would flash back to a normal screen, then after about an hour it seemed to stay "fixed" probably for a month or two. The 3rd time it happened in the morning and hadn't resolved by the time I left work and stayed that way as I took it into Verizon. The Verizon guy took care of ordering the factory replacement at 7:30pm and it arrived literally the next morning. The crazy thing was that after I left Verizon it resolved and stayed "fixed" until I wiped it and sent it back in to Verizon, so I was able to copy and duplicate everything to the replacement phone.
While the screen looked like that, all the functions remaining intact, i.e. I could guess where I should tap and the sounds occurred that should have. I even attached my projector mod and the projector would display everything correctly even as the phone display was not.
I have not had the issue reoccur on my replacement phone.
Sent from my XT1650 using Tapatalk
Sent from my XT1650 using Tapatalk
edneum2 said:
I had this happen... probably about 3 separate times. Each time there would be moments (either after tapping it, squeezing it, rebooting it) that it would flash back to a normal screen, then after about an hour it seemed to stay "fixed" probably for a month or two. The 3rd time it happened in the morning and hadn't resolved by the time I left work and stayed that way as I took it into Verizon. The Verizon guy took care of ordering the factory replacement at 7:30pm and it arrived literally the next morning. The crazy thing was that after I left Verizon it resolved and stayed "fixed" until I wiped it and sent it back in to Verizon, so I was able to copy and duplicate everything to the replacement phone.
While the screen looked like that, all the functions remaining intact, i.e. I could guess where I should tap and the sounds occurred that should have. I even attached my projector mod and the projector would display everything correctly even as the phone display was not.
I have not had the issue reoccur on my replacement phone.
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
Sounds like exactly the issues I had, functions intact even though the screen was janky. Luckily was still in warranty period from Moto so got a new one sent to me. (Moto customer service is the ABSOLUTE WORST by the way). New phone is working fine... so far.