Huawei Nexus 6P :: Volume Down Jammed - Can't Boot Past Bootloader
Jan 6, 2016
The Volume Down button is jammed (the phone fell and landed on its edge slightly crushing the frame where the volume down is). Curiously the Volume Up button still increased the volume.
After turning the phone off the problem came when turning on the phone as it now only boots into the bootloader as a result of the jammed Volume Down button. Once in bootloader mode, the volume up/down buttons do not change the reboot options - it appears the stuck Volume Down button is causing this.
The way to fix this is to take the phone apart (as per the Youtube clips) and physically straighten the frame. This is no easy task, so the question: is there a way around this so that the phone can boot?It's rooted and fastboot commands work. (I installed TWRP but can only boot to recovery with adb).
Then i installed Pure Nexus rom and it was working fine. Then i installed Elemental X kernal, didn't change anything from stock options other than double tap 2 wake, and it would stay forever in the boot animation. Not a boot loop, but the animation with the circles. So i figured, i had a TWRP backup from before i rooted and all that and restored from that, still same never ending boot animation
EDIT::: I unchecked selinux enforcing but i still get the same issue. I noticed when trying to restore from recovery it would reboot when trying to flash the system, and that it would not be able to flash the system while trying to install pure nexus rom.
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:adb>fastboot devices ertyugg(this edited for privacy) fastboot
commands: update <filename> reflash device from update.zip flashall flash boot + recovery + system flash <partition> [ <filename> ] write a file to a flash partition
[Code] ....
Message shown :
options: -w erase userdata and cache (and format if supported by partition type) -u do not first erase partition before formatting -s <specific device> specify device serial number
I have had my fantastic Nexus 5 for some time now, and up until the Android 6 update I have had no crash issues at all. It may be coincidence, but since the update a couple days ago my phone has crashed three times, and with the last crash it will not boot past the colored symbols. In fact it will cycle the symbols without end at times, but sometimes it will cycle them for 30 seconds or so and then crash back to the black screen then to "Google" followed by the colored symbol screen. Rinse and repeat.
I have tried full shut off and re-start by holding down the power button and that does nothing new. I read on these forums a suggestion for a Nexus 4 user back in July to try holding down the power button and tapping the up volume once to pull up some options, but that seems to do nothing. Perhaps I am doing it at the wrong time though.
I read that Marshmallow handles permissions differently, so I wonder if it has to do with my third-party launcher. Though it seems strange that I was able to (until today) use my phone just fine between crashes for several days after the update.
Ok, so I just got my awesome new 6P. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't.
I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: [URL] ..... (wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently ...
So I think I know the answer but wanted to validate. If I leave the bootloader locked on my device and download a factory image from Google, cannot I just put the zip on the sdcard storage and run it through recovery to update? I don't think that I need to unlock the bootloader do I? I am trying to keep everything stock for now, but updates are a big reason I wanted this phone. Also don't want to break Android Pay.
I haven't received mine yet, but probably one of the first things to do is unlock the bootloader. Does the fingerprint verification/ unlock still works with an unlocked bootloader.
I am already unlocked and rooted, but I would like to relock the bootloader assuming that I can unlock it for future updates without losing data. The Nexus 5 had a boot locker app in the App Store which allowed this, but I do not find an option for the 6 P.
After i unlocked my bootloader and rooted my phone, everytime i boot up my phone i have this msg and then the phone start, how do i get rid of this msg?
I noticed there were 2 newer images on the Google developers page and thought I would flash the latest and greatest (MDB08M) since it wasn't coming down OTA. I enabled Developer Options and set USB debugging and OEM unlock, rebooted to bootloader, did a fastboot oem unlock, rebooted then back to bootloader and ran the flash-all.bat from the new image, rebooted and all was well. I re-enabled USB debugging and went back to bootloader to re-lock the bootloader and am getting an error:
... FAILED (remote: unknown command) finished. total time: 0.016s
Results of fastboot getvar version-main are blank:
version-main: finished. total time: -0.000s
I rolled back to MDB08K but it made no difference. I then tried rolling back to MDA89D and letting it pull MDB08K OTA but that too made no difference.
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Cannot seem to flash factory image from Google. Trying to do it via adb but cannot push onto device. Says "cannot open no such file or directory". What can I try?
Last year I bought the nexus 6 and for the first time (I've had a lot of android phones) in my phone was also disabled force encryption after the bootloader unlock, twrp and root. So I decided to decrypt it because reading on the nexus 6 forum some devs suggested this to increase the phone performances.
I read that now twrp supports encryption and that Google increased the phone performance also with force encryption enabled.
I used Wugfresh nexus root toolkit and went through the unlocking and root process. It unlocked fine, went through the reboot process. Then when I selected root and recovery I got to TWRP, swiped to apply the zips, it rebooted and never got back into system. Now it just hangs on the google logo. I can get into bootloader and stock recovery still as I attempted to reflash stock through the toolkit.
Got my 128 gb 6p last Tuesday, unlocked, decrypted, flashed Pure Nexus, joy no problems. This morning I decided to try God kernel, flashed booted up but I found out the camera stopped working. So restore a backup, no boot, just stays on the Google boot animation. Full wipe, reflash Pure Nexus, still won't boot, stayed on the animation an hour. So I guess I try a factory image next.
I've read that some people like to install twrp, root, etc. and then re lock the bootloader. Is there any benefits to doing that? And is there a way to unlock/lock without wiping every time you unlock again?
I've been running Android M preview (3?) for a while on my Nexus 6.2 months ago my USB-connector of the phone broke and only because I also have a wireless charger I can continue to use my phone.Just now I tried a headphone and noticed that viper4android wasn't working, which it did a while ago.I still had the file viper_aio_fixes.zip in my download folder I used to get it going a long time ago. [URL]..
I booted into recovery, flashed that zip and did a reboot.Now it is stuck at the black screen with only the text "Google" and a padlock.I am able to boot into fastboot where I can go in the several modes including recovery mode (Team Win Recovery Project v2.8.5.0). I don't have any possibility to connect it to my computer using an USB. The device does still have warranty, but I can't miss my phone.
Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added [URL] ..
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself.
I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Again, I can NOT access the OS at all whatsoever.
I recently got my 6P and immediately proceeded to unlock the bootloader and flash TWRP to start loading custom roms. I decided to start use Pure Nexus with it's accompanying gapps package but when I go to reboot the device, I am stuck at the circles boot animation.
I decide to try CM13 nightlies and the same problem occurs. After searching online for some time, I realize I needed to flash a SuperSU file from recovery that flashes a custom boot.img. I flash Version 2.66 and restart the device. After 5+ minutes on the boot screen, I decided I am stuck still. What do I need to do, I am unable to boot the device.
I had been running cm 12 nightly for quite a while but wanted to try something new so I downloaded Dirty Unicorns rom and a Gapps pack. Drag and dropped both the zips into root directory, booted into cwm recovery mode, cleared everything, then installed the rom zip and then the gapps zip but it wont boot past the Google logo, I can only access recovery mode and I don't know what to do from here, is there anything I can do?
So I have verizon and I'm using a nexus 6p. My phone died and I charged it and booted it back up.Problem was is I forgot my password. So since I'm rooted i went into twrp and tried my password there. it worked there but not on regular boot up. So i went into wipe and wiped everything. now when i go to reboot my phone it is stuck on the google logo.
So I'm on my 2nd day of owning my 6P, and it rebooted without prompting at some point when it was in my pocket. After entering my PIN it just sits there on the animated Google logo, getting pretty hot but never making it past the boot screen.
I'm planning on trying a factory reset and seeing if it happens again since I was going to unlock the bootloader anyway, but I fear I've hit a hardware issue.
