Related
So a friend called me today and said he is having problems with his Vibrant and wanted me to come take a look at it. He explained that he flashed a rom and now everytime he boots it up, it gets stuck in a force close loop hell. I got there and verified that's happening and said that I could just flash him back to stock. Well, come to find out he's also hardware locked! I tried to figure out a way to enter safe-mode (have used this on my Mytouch but it had actual buttons to make this work) but it was no-go since it's capacitive. On top of all this, he doesn't have debug mode enabled and I can't get to the settings due to the force close loop and no working launcher/home. I couldn't get any adb commands sent to the phone due to no debug mode, so that means I can't even adb reboot into recovery. I spent almost 2 hours on it before I had to give up. Does anyone have any suggestions that I may have overlooked or not thought of?
Greatly appreciated! XDA has some of the smartest damn people around!
Have you checked this out?
http://forum.xda-developers.com/showthread.php?t=804305
Duce HD2 said:
Have you checked this out?
http://forum.xda-developers.com/showthread.php?t=804305
Click to expand...
Click to collapse
Yes, in fact I had that very thread open on my netbook as I was working on his phone. There's one (of many) problem with this:
"turn on USB debugging in Settings-->Applications-->Development"
As I stated in my OP, he doesn't have debugging turned on already, and I'm unable to get to it in settings because at startup it's in a FC loop and I can't get to settings either by holding MENU or using the launcher.
Is there another way to get to phone settings besides those two methods? How about going into safe mode? I've done that before with my MT3G, but it has hard buttons that facilitate this with ease. With capacitive, not so much. Is it possible to enter safe mode on the SGS phones with capactivie screen?
I seriously doubt this has stumped the brains of XDA!
Email me lets see if I could help
[email protected]
What do you think caused the force close loops? Was your friend tinkering with his phone? Did he install a lagfix?Are you doubly sure he's hardware-locked?Did you try Download mode?
Lots of questions...I had this problem once. It was due to the fact that installed Ryanza's early lagfix and tried to remove it. My phone had a force close loop, BUT I had enough patience to wade through the loops and in the very short gaps at which they appeared, I managed to navigate the phone into settings (~an hour). The moral is: Try very hard to get into settings and don't lose your patience.
You can try booting into safemode, maybe that will help. Just turn it off and when it powers on the second you see the animation start press and hold the home button.
cthach11 said:
What do you think caused the force close loops? Was your friend tinkering with his phone? Did he install a lagfix?Are you doubly sure he's hardware-locked?Did you try Download mode?
Lots of questions...I had this problem once. It was due to the fact that installed Ryanza's early lagfix and tried to remove it. My phone had a force close loop, BUT I had enough patience to wade through the loops and in the very short gaps at which they appeared, I managed to navigate the phone into settings (~an hour). The moral is: Try very hard to get into settings and don't lose your patience.
Click to expand...
Click to collapse
From what I gathered, he tried installing the FrankenTwiz rom and something went wrong. He couldn't fully explain exactly WHAT went wrong, and so I'm coming into this whole thing without a lot of answers to help troubleshoot it. I know he's HW locked because that was the first thing I tried (recovery mode) and it's not able to get into it. When I fist got my Vibrant it was HW locked and the behavior is the same. I exchanged mine the next day for a non-HW locked. I tried every method to get into recovery/download mode but unable to. I remembered "safe mode" from my MyTouch 3G, but it needed the hard button (menu) pressed on bootup. Being capacitive screen, it doesn't respond the same way so I couldn't even use safe mode. He doesn't have USB debugging enabled and I can't get to settings to enable it due to the FC loop. I sat there pressing CLOSE a million times to find that "break" in the process to try and get to settings with no luck. Hope that answered everything.
icandy75 said:
You can try booting into safemode, maybe that will help. Just turn it off and when it powers on the second you see the animation start press and hold the home button.
Click to expand...
Click to collapse
That didn't work. I thought safe mode was MENU, not home? (btw- which animation? The tmo pink or the Galaxy S? Tried both an no result.)
Ok, figured out SAFE MODE!
Power up the phone and start pressing the capacitive buttons. As soon as they light up during boot up process, press and hold MENU & HOME all the way through until you see SAFE MODE appear in the bottom left of the screen. At that point you can release the buttons and you will now be in safe mode.
Now I just need to get in touch with my friend and meet up with him to try this. Hopefully it will break the FC loop from Hell and I can get into his settings to enable debugging mode.
**MODS - I didn't find how to get into safe mode anywhere in the Vibrant forums. Maybe it can be added to the Bible to help others? Thanks!**
That's new for me, mine goes holding the home key. Timing is of the essence though. I have to press and hold the second the S forms on boot.
icandy75 said:
That's new for me, mine goes holding the home key. Timing is of the essence though. I have to press and hold the second the S forms on boot.
Click to expand...
Click to collapse
I tried multiple times using your method and no dice. I get consistent results with my method (MENU + HOME), so not sure what to say...
Anyhow, it looks like he's screwed. Met up with him after work and even though I can get into safe mode, the TW Launcher is still going nuts, FC hell! Unable to get it to stop long enough to get to settings to enable debugging. He's going to put it on Ebay for parts. Dude had it for a week and is out $400. Feel so bad for him, but I guess it teaches him a lesson. If you don't know what you're getting into with flashing ROMs, better step back and either ask for help from someone with experience or just not attempt it at all. This was his first flash attempt and he crashed hard.
I was running the 2.99 PA rom on my Nexus 7 with m-kernel without any issues until 2 days ago, when my device rebooted and entered a bootloop, got stuck on the Google screen first, then I managed to get into the twrp recovery and erased cache and dalvik cache. Then it booted until the "X" screen and got struck there until I resetted the device by holding the power button for a while. Since then, the screen is totally dead, the only response I can get is the Windows usb device connected sound. I've tried each and every button combination and also pulled the battery but it did not help. The tablet shows up as an APX device in the device manager. I have searched the forums and I only found other people who have accindentally erased their bootloaders and then got stuck in APX, but this is not the case with my nexus as there wasn't any bootloader tinkering involved at all.
Do you have any suggestions on what I should do/try to do?
Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
bftb0 said:
Should take 18 seconds or so.
You can get to the bootloader (fastboot mode) FROM ANY STATE.
Read that again - from any state.
See "bootloader interrupt" in this thread:
[REF] Nexus 7 Button Combinations
cheers
Click to expand...
Click to collapse
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?
wasab said:
I've read that thread and tried the methods listed there but it didn't help. Maybe there's something else that went wrong while the device was bootlooping and corrupted the bootloader?
Click to expand...
Click to collapse
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).
bftb0 said:
Quite possibly. From my limited understanding of the Tegra3 boot process, it sounds freakishly complicated. And complicated is the same thing as "lots of opportunities for bug expressions".
Also, it sounds like you had a spontaneous failure that was not temporally coincident with a flashing operation. That smells like a hardware problem, but it's hard to be certain though as you were using a dev kernel and custom ROM.
If you plug it in to the PC and then hold down the power button for an extended period of time, do you see any activity in the Device Manager that suggests that Windows is seeing a hardware state change (even if it rolls right back into APX mode?)
I'm not aware of any rescue methods at this time via APX on the Nexus 7 at this time (apparently they do exist for other Tegra devices, but the N7 experimenters using those methods have come up empty-handed so far).
Click to expand...
Click to collapse
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?
wasab said:
Holding the power button for around 10 seconds causes it to disconnect and then reconnect 4-5 seconds later. Holding the power button with any(or both) of the volume buttons has the same effect.
Click to expand...
Click to collapse
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
wasab said:
I did read that apx recovery thread too before posting.. What do you recommend, should I try to get it repaired in warranty as the guys in that thread did, or is it a no-go because of the custom rom and kernel?
Click to expand...
Click to collapse
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7
bftb0 said:
Uh-Oh. When you do the power-button-hold-thing with a tab that behaves normally (and is plugged into the PC) you see exactly that timing: APX disappears right around 10 seconds, and then the bootloader screen pops up about 4-5 seconds later. Good news is that your tab knows you are pressing the power button - bad news is the bootloader doesn't appear at the moment it should.
I can't speak from experience, but my guess is there is a technician sitting someplace with a pile of returns, and his/her bosses are breathing down his/her neck to increase the number of units turned per day. They won't be doing a forensic examination; that isn't a cost-effective way to do business. More than likely they will be replacing the motherboard if their diagnostics show the smallest hint of trouble. But I don't know for sure.
Either that or you can take this as a gauntlet thrown down and become the person that cracks open APX for the N7
Click to expand...
Click to collapse
Thanks for your help! I think that I will try to solve this the easy way, but if I have no luck with that then I'm sure that I'll do some serious digging about the apx recovery.
I've run into a problem with my S4. I'm rooted, and running Hyperdrive 15.
My phone refuses to boot quite often. Sometimes it will boot up perfectly fine and run for a day - day and a half, or it'll lockup and then refuse to boot up again, OR it will just not boot at all. My power button seems to be unresponsive, and the only way that I can get some action out of the phone is by reseating the battery in the well.
What I think it is, could be 1 of a few things, or a combination of them - i'm not sure.
Scenario 1: While playing with the Hyperdrive tweaks, my phone was hung after running the Zipalign tool for over 20 minutes and I had to pull the battery.
Scenario 2: I'm deployed on a ship currently, and I have my phone in a high-salt enviornment and I'm afraid that there might be salt corrosion inside of the power switch or the USB connection - shorting it out. I took my phone apart tonight and cleaned both items with isopropyl alcohol ( the switch itself on the main board ) but that didn't seem to produce any new results.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
A description of what my phone does when I reseat the battery: My phone will vibrate, the Galaxy S4 logo will show for 1.5 to 2 seconds ( same for download mode ) and if I hold the appropriate button, ' Recovery Booting.... ' will display as well. At that point, my phone will shutoff and the power button will become unresponsive.
If anyone can give me a bit of guidance on how to proceed to repairing my phone, I'd be super grateful.
Scenario 3: I was recently rooting a Kindle Fire HD 7" for a friend out here, and I was dumb and didn't realize that I was pushing boot loader files that were designed for the Kindle Fire and not for my Galaxy S4. I have since tried to enter recovery, but with little avail. Download mode is also out.
This sounds like the most plausible reason.
You will need something like JTAG to really fix it.
Lennyz1988, thanks for the quick reply. Internet out here is slow at best, and sometimes unusable.
As far as your JTAG option, I believe that would work, except that I dont have access to that kind of hardware right now. Sending my phone out at this point entails a month of transit time on each side of the turnaround time required for someone to re-flash my phone, and I wholly believe that I can do this.
As an update to my phone, it will not charge the battery anymore. I'll use someone elses phone to charge my battery soon. If anyone can give me a direction to go as far as how to completely reflash my phone IF it turns on, i'd be grateful beyond belief. I dont want to believe that if I can get it to start up again, that it is a total brick and completely useless - if it turns on again, i need someway to push new boot loader files to it. Really hoping someone can help.
Thanks again in advance.
Hey everyone I really hope you can help me out here. Last night my completely stock Nexus 7 2012 locked up during normal use. It had KitKat 4.4.4 on it not rooted or unlocked. I THINK usb debug was enabled but don't honestly remember. After the lock up I forced it to power off. When it started up again, it was stuck with the 4 circles going round and round. After a long wait I went into recovery and tried to wipe the cache. This went on for almost 10 min but never completed. I forced it to power off again (and here is where I panic and things get fuzzy. I tried to get back into recovery and just restore it but I can not get it to do anything except boot to the dead android picture and a message that says NO COMMAND. I've tried to use the VOL UP and Power button sequence to get the menu and it won't come up. It stays on that screen for a few seconds and then it acts like its restarts but I never see the google logo just this dead android flashing on and off with the no command error. I've read several threads, tried the WUG toolkit as well as skipsoft toolkit but with the device stuck in this loop nothing can communicate with it. I removed the cover and unplugged the battery which gets the machine to shut down but when it powers back on even with key sequences I can't get anything but this dead android. I can use power and VOL up to get into APX mode but that is my only other option. Please give me some more suggestions!
Well things have gotten worse now I can no longer get past the black and white google screen. I'm guess this thing is just toast.
How old is it? If it's under a year, you can RMA it back to ASUS and they'll fix it for free. Since you haven't rooted it nor unlocked it (although I don't think that would be an issue anyway), they shouldn't have any issue with repairing it. Just be sure you didn't leave any signs that you opened it or else, that will void the warranty and they won't repair it for free.
Its exactly 2 years old today. It was a birthday present. funny how it chose today to die.
Okay just so I can have some closure here,
The tablet will not shut off when I hold power button it shuts off and comes right back on to the google logo.
I can NOT get into boot loader or recovery at all. No key sequences work what so ever. I've been into recover and boot loader before on this device so its not that don't know how.
The only time it gets detected by my PC when plugged in via usb is if its int APX mode which as far as I can read is useless to me.
So is there any other secret or is it just trash now?
Thank you.
My wife's was doing this when it failed an OTA. Hold the power button long enough the screen will go dark for a couple seconds.when it's dark, hold all three buttons down and wait.it will go into fastboot.use nexus root toolkit to flash stock+ unroot and select bootloop .
---------- Post added at 09:56 PM ---------- Previous post was at 09:55 PM ----------
Ps it did this because she accepted an OTA not knowing I had TWRP on there.
KANDL said:
Okay just so I can have some closure here,
The tablet will not shut off when I hold power button it shuts off and comes right back on to the google logo.
I can NOT get into boot loader or recovery at all. No key sequences work what so ever. I've been into recover and boot loader before on this device so its not that don't know how.
The only time it gets detected by my PC when plugged in via usb is if its int APX mode which as far as I can read is useless to me.
So is there any other secret or is it just trash now?
Thank you.
Click to expand...
Click to collapse
"The tablet will not shut off..." <<---- This suggests that you are seeing or observing something happening. But based on your previous posts I can not tell exactly what you are now observing - the black & white Google logo?
I would start first with trying to determine if the battery is capable of being charged. The last thing you want to be doing is fooling around with this stuff with a nearly dead battery.
If you put it on a 2A wall charger (*not* a PC USB port), does the tablet warm up a little after 20-30 minutes? If so, leave it on the charger for at least 2 hours. (Heck, even if it doesn't warm up, same advice - put it on the wall charger for at least 2 hours)
OK, next item for you to consider. In Android devices, there is usually a nonvolatile storage area (maybe in the "misc" partition?) called the BCB (Boot Communication Block). The bootloader will always look at that area first, and if there are no boot instructions in there, by default the bootloader will attempt to load & jump to the entry point of the contents of the LNX partition (Linux boot partition). This would cause a "normal" Android boot to occur by default when turning the power on. The other two common instructions in the BCB are for a reboot into the recovery, or instructions for the bootloader to stay resident but drop into it's fastboot mode.
Why am I telling you this? Because there are certain pathological situations that can develop into loops without apparent escapes. Imagine that the tablet was sitting in custom recovery mode, and the dummy behind the PC keyboard flashes some random garbage to the recovery partition, and then uses the touch interface to reboot into recovery. What happens is that "boot to recovery" instructions are placed in the BCB, and a soft-reset of the device occurs... which (when the hardware finishes resetting) loads up the bootloader.**
Now the bootloader sees the "boot to recovery" instruction in the BCB, and attempts to load the garbage in the recovery partition. Eventually - either due to a watchdog timer reset, or a illegal instruction trap, the device will soft-reset again... WITHOUT EVER CLEARING THE CONTENTS OF THE BCB.
In this example, the bootloader is intact and operational, but the looping behavior continues until the battery drains. You don't get an opportunity to communicate with it in fastboot mode because it is always trying to load the bad recovery. Either there is a way to break out of this death spiral... or their isn't.
Now, one more thing - I lied slightly right around the ** annotation.
On the Tegra3 SOC, there is a kind of micro-kernel inside the Tegra3 that is responsible for loading the bootloader. Simpler processors of old would simply load a memory page at a specific hardware memory address when they reset, but this is far more sophisticated: the little micro-kernel in the Tegra3 can evaluate the bootloader to see if it has the correct cryptographic signature and so forth.
If that micro-kernel doesn't like what it finds, the Tegra3 will put the USB port into APX mode. This is important because it is diagnostic: if your tablet always goes into APX mode, for instance after disconnecting/reconnecting the (charged) battery and then powering up the device, then you are probably out of luck; but if it doesn't go into APX mode, that suggests that the bootloader is actually healthy, but perhaps thrashing in one of those nasty boot-loop cycles.
OK, still with me?
Have you looked at this thread carefully?
http://forum.xda-developers.com/showthread.php?t=2133986
It suggests that possibly you can get the bootloader to ignore the contents of the BCB by a carefully-timed press of the Vol-Down button - which, if it works - should let you escape to fastboot mode. This is documented in the above thread as "bootloader interrupt".
So, questions for you:
1) Are you sure the battery is well charged? (Not easy to tell without a voltmeter or heating of the tablet during charging - the temperature of the tablet will drop after it finishes charging. One way to be sure of things is to disconnect the battery, reconnect it, and then put it on the wall charger. That way you can be sure that the tablet is not on, so any heat would be due to battery charging, not other components running. FWIW, a discharged battery will be about 3.5v, and charged about 4.15v.)
2) Does the tablet always go into APX mode when it starts up, even if you only press the power button?
3) Once the battery is charged, what are you seeing on the screen during start-up? After you have disconnected the battery and reconnected it, do you see anything on screen when you put the tablet on the charger?
bftb0, Thank you for attempting to help me out, I really appreciate it. I understand 99% of what you wrote, and that gives me a little bit of hope! Let me begin by answering your questions.
1. I am certain the battery WAS charged. as I had just pulled it off the charger when this happened. Also I'm certain the battery IS charging when I plug it in. It does get warm after a while. The battery did drain down now since my last post, but I have removed the cover and unplugged the battery to get it to power off. Now it is currently charging back up as I'm typing this. I can see the battery charge indicator on the screen while its laying here.
2 and 3. The tablet does NOT go into APX mode by its self. It only does that when I hold power and VOL+. It now currently powers on with a press of the power button goes to the black screen with with the white google logo and stops. After that I can no longer get it to power off without manually disconnecting the battery. I can get it to reboot and go right back to the same google logo. Prior to it doing that it would go to the android on its back and just say no command. That screen would flash on and off like it was contentiously rebooting. However after trying all day to get some sort of menu to come up and different key sequences it now only goes to the google logo and stops.
I have it currently charging and will let it charge to full capacity while waiting for you to reply. I tried and tried to get the boot interrupt to work from the thread you posted in your reply and it wither does not work or I'm simply not doing it right but I'm willing to try some more if it will save this thing and I don't have to go buy a new one.
Thank you again for your help!
Well, because you have a pure stock tablet and the problem occurred spontaneously and under innocuous operating conditions, the most likely explanation is some type of hardware failure affecting the eMMC NAND chip.
Even if that is the case ... AND you successfully are able to get to fastboot mode ... it still might not be repairable. It could be a modest failure (e.g. something affecting the cache partition only, which could knock offline both the normal boot as well as the recovery boot), or it could be an enormous fraction of NAND.
eMMC NAND is supposed to be able to degrade gracefully, so there is a small chance that erasure and formatting of partitions will release blocks that have failed. But it could also be that the failure is extremely severe and no recovery is possible even if the bootloader is still intact.
I imagine you've already tried it, but since it will be your only possible means of rescue I would try the bootloader interrupt trick (Vol-Down approximately when the b&w Google logo appears - hold it down for 3-4 seconds)
Since the tablet gets stuck in a hardware reset loop, you should probably unplug the battery after every failed attempt, start it up normally (power button only), and then press and hold Vol-Down as soon as you see the Google b&w logo. Perhaps with the use of a stopwatch, you could experiment with slightly different timings, possibly even try the button press a second or two before you expect the logo to appear. I am not aware of any other way to get to fastboot (without having a booted kernel as in the recovery or normal os); and it may also be that the only time that the Vol-Down button has any effect is under the "default" (empty) BBC contents. If that is the case you are probably SOL.
The objective is to try and get the tablet into fastboot mode by any means possible.
If it were happening to me, and I was able to get that to happen, the next thing I would do would be to erase the entire tablet (except the bootloader) using fastboot, and then follow that up with an installation of a stock recovery (and formatting of cache, system, and userdata in that order), and then follow that up with a "factory reset" using the stock recovery.
If you can get just the recovery and (bootloader) fastboot mode working again, there is an outside chance that the tablet could be put back into service.
A little bit of explanation is in order here for me to explain why I am suggesting this. Sometime after I got my tablet, I spent a bunch of time dumping *all* the device partitions (things like MISC, USP, PERS, etc in addition to the "normal" Android partitions) before/after certain fastboot operations. What I noticed - by accident - was that I was seeing data that belonged in a certain partition showing up in other partitions. And always in block-sized offsets.
I think that what I was observing was an artifact of the eMMC wear leveling / block remapping that is part of the device's FTL (Flash Transition Layer). Literally, blocks were being shuffled around - even across partition boundaries - when they were in an unused/erased state.
In addition, if you look at the Google instructions for flashing a factory image, you will note that sequence is
erase p1
erase p2
...
erase pN
(followed by)
format p1
flash p2
format p3
...
That is, **as much as possible is erased before anything is put back into service**
It is my presumption that this happens to give the wear leveling and bad block remapping process of the eMMC chip maximum flexibility (as most everything in the device is marked as not in service it should be easy to remap based on block write counts as individual partitions are put back in service via via flash and format operations). Can't prove that though.
It looks like you did your reading about APX mode - there is a risky and fairly complicated procedure available to rooters that allows them to capture some custom (unique per tablet) file blobs that allow re-installation of a bootloader from APX mode, but is a procedure that has to be performed ahead of time. (And because the file blobs are unique per tablet - encrypted & signed with a unique hardware identifier, you can't get someone else to generate them for you) So APX mode is of no value to you afaik. It's barely of value to rooters as well. (I will say that I haven't kept up over the last year, so there is always the chance that someone discovered something new wrt the Tegra3 and APX mode that I don't know about - but that's the way it was a year ago or so)
Well, good luck with your tablet - I suspect you are going to need a bit of good fortune.
Thanks you so much for your help. I will continue to try the boot interrupt and see if I can get it to go. Failing that I guess I'll be shopping for a new one. I really appreciate your time in trying to help me.
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
edlovereze said:
Hello,
So my Nexus 6P turned off randomly and then would not turn back on. It would come on and show Google and sometimes even let me enter my pin to start the phone. But it constantly would freeze during start up and just shut down. I got into the recovery and factory reset my phone and now it won't even turn on. I hold the power and it doesn't do anything. I've tried the boot loader and such but it won't turn on at all. Any ideas on what I could do? Thanks!
Click to expand...
Click to collapse
Sounds like you may have more than one problem, but many have been able to get a dead phone to start by holding the power button down for a very long time, sometimes 2 minutes or more. If it doesn't start, fully charge it and try the power button again. Assuming you are stock with a locked boot loader.... you didn't mention.
My phone is stock with a locked boot loader. I held the button for over 5 minutes and got nothing. I'm wondering if Google would be willing to help me out. Unless anyone has other ideas
It's hopeless. Don't waste your time trying to revive. Contact Huawei regardless of date of purchase.
If it won't power on it's either not charged, a bad power button, or something with pcm. Which is on Motherboard.
Most common scenario is a bad power button because it's most used breakable part. That won't allow the board to receive power or not enough power if it's shorted.
Dunno if you've poked around the interwebs some more regarding this, but I've been slammed with the N6P bootloop error (which appears might be part of your problem) and I found a stop-gap solution. If you feel like you've got nothing to lose, you can try what I've done: Make sure the phone has a little charge, hold it with a hot mitt from your kitchen, and blast the back of your N6P in the region between the camera lens and the fingerprint sensor with a hairdryer. Doing so will trip the big cluster off, which is the source of the bootloop problem. If you can get it to boot to the Google logo, applying the heat for the right amount of time (maybe not too long.. 2-4 minutes tops) may cause it to make it to the spinning color graphics and beyond.
I've been able to resurrect my phone doing this, but only to back it up and do very simple tasks. The moment I do something processor-intensive (Waze, YouTube, etc) it immediately crashes and bootloops again. The only solution beyond this is to unlock your bootloader, download EX Kernel manager and use it to completely disable the big cluster. Then your phone will likely be reliable, but extremely hobbled.
I bought from Best Buy about 16 months ago, so both Google and Huawei have been utterly useless, which is infuriating. Shenanigans like this are criminal. This is my 3rd Nexus phone and I'm considering abandoning Android altogether after this experience.