Database Users

Nexus 6P stuck on boot screen

Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben

Can you boot into the bootloader/fastboot mode?

benhawley2711 said:
Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben
Click to expand...
Click to collapse
i have the same issue, i have tried using toolkits and even using fastboot commands and the phone just keeps getting stuck on the google logo screen. at this point i think i might have to get a replacement. unless some can offer a solution

Same issue
I have exactly the same issue. I am on Angler 7.1.1 Beta/NPF10C. Since the OTA came out everything was fine, until yesterday while trying to send a picture on Hangouts the phone froze and rebooted, and rebooted and rebooted. The bootloader is locked and no USB debugging enabled. So far I tried:
- wipe data/factory reset through recovery - first try, the phone reset and let me set it up, but then froze after 5 minutes and kept rebooting; after that any factory reset just get's stuck at Google logo at boot
- tried to adb sideload rescue OTA - previous build NBD90X starts verification and fails at 50% with the error: can't flash older over newer (duh!); and the ota build npf10c can't be read. I tried on Mac and Windows. No matter what I do adb can't read zip file. Also tried updated sdk tools and everything, no luck.
Read on Google forums that there is a chance of hardware issue and the phone must be returned for exchange if still under warranty.
Update: I was able to sideload rescue OTA on Linux, but the phone is still in bootloop. Only showing Google logo and reboots. I'll wait till next DP2 comes out and I will try to sideload it and see if it fixes the issue.

redduc900 said:
Can you boot into the bootloader/fastboot mode?
Click to expand...
Click to collapse
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?

.
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country

benhawley2711 said:
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?
Click to expand...
Click to collapse
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
benhawley2711 said:
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country
Click to expand...
Click to collapse
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.

denys2000 said:
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.
Click to expand...
Click to collapse
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/

benhawley2711 said:
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/
Click to expand...
Click to collapse
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.

denys2000 said:
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.
Click to expand...
Click to collapse
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.

benhawley2711 said:
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.
Click to expand...
Click to collapse
Good luck with the warranty. Unfortunately, mine has ended and I am currently using my girlfriend's old iphone 5s with a tiny tiny tiny screen

I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work

KKPGAME said:
I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?
Click to expand...
Click to collapse
use these commands in bootloader.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

Unlocked Nexus 6P Stuck in a Bootloop - Proper Reset Necessary?

Since I got my Nexus 6P sometimes it could just hang and then restart, I thought this was nothing major so I did nothing about it. Today however, I got a couple of these restarts in one day and after the last one I can't boot. The unlocked bootloader message appears, then the Google logo and after that it keeps looping. I can get into bootloader, however when I try anything there (boot into recovery, BP tools or "factory") it just starts looping again. I have tried restoring nexus 6p system images with Google's "flash-all" bat file, and with Heisenberg's method on 2 different android versions and it goes through without problem, however I'm still stuck in a bootloop.
Any help would be appreciated.
Thanks.

Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.

RoyJ said:
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
Click to expand...
Click to collapse
I've been through 5 so far. I'll give them a call tomorrow morning and see how it goes. Hopefully the warranty still covers me. I've done some digging around, and what is happening to me is the exact same thing as what is happening to some people through the OTA nougat update, with the only solution being exactly what you said.
I just really hope I can actually get a replacement as I have done nothing wrong on my side, it seems to be purely Huawei's fault. Thanks anyway.

Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.

domdomrys said:
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
Click to expand...
Click to collapse
How did they saw if your phone was rooted? Did you told them?

GKti22 said:
How did they saw if your phone was rooted? Did you told them?
Click to expand...
Click to collapse
The guy at Huawei didn't really know what the warranty covers. I mentioned trying to restore from Google's factory images (implying that I unlocked the bootloader) and he said that this might have voided the warranty (which I'm pretty sure it hasn't) as it is a software modification in a sense, but he's not entirely sure. They're going to send me a box to send the phone to them, and through that they'll be able to tell that no modifications have happened I hope (it's technically all stock and unrooted now, it just doesn't boot up). If they do try and charge me, I'll call the actual repairs team (as they're not available today) and explain the situation. No way am I paying for something like this as it hasn't happened through my own fault.

Under Europe regulations THEY have to formally prove the software modifications lead to the hardware fault (if that's a hardware fault) and that would be really bad publicity for Huawei. Not sure how UK applies that to its local right.

Root may very well void the warranty based on an old thread on XDA here that's buried in the general section somewhere, but an unlocked bootloader absolutely will not void the warranty.

Hi, can someone please upload the build.prop for nexus 6p 7.1 dev preview, I did some changes and now stuck in boot loop, also the backed up copy that I have has previous version names and all according to 7.0 , I am stuck in twrp and don't have computer then how is it possible to make changes directly from twrp terminal, I tried "vi build.prop" and was able to see build.prop but couldn't edit, Thanks

Here you go https://paste.debian.net/897221

For anyone wondering, I got the phone the other day and they fixed it under warranty. No extra costs or anything (I enclosed a letter giving proof as to why I believe it should still be under warranty, and it worked fine). The serial number and IMEI has changed, so it leads me to think that it was indeed a motherboard failure. Thanks for the help!

[WARNING] Flag for unlocked bootloader

This I just an alert for anyone who is thinking about unlocking their bootloader. I wish I was warned about this before doing mine which ended up being ok but could potentially cause issues for people. Once you decide to unlock the bootloader you will permanently have a thrown flag at boot up which states your bootloader is unlocked. If you decide to relock your bootloader you will have a flag thrown that says your device may be corrupt... This is important because of your try to return your device at the store the employees will know it has been tampered with... Just so you know.
tApPeD fROM mY nExUs 6

Really when I relock and make mine stock again it doesn't do that. If you don't mind me asking what variant do you have?

I'm betting they'll find a way to mask that flag once things really get cracking around here. The proverbial floodgates have been opened!

jameslapc2 said:
Really when I relock and make mine stock again it doesn't do that. If you don't mind me asking what variant do you have?
Click to expand...
Click to collapse
H918 T-MOBILE
tApPeD fROM mY nExUs 6

andrewjt19 said:
H918 T-MOBILE
tApPeD fROM mY nExUs 6
Click to expand...
Click to collapse
This is not true, I factory reset mine and relocked the bootloader for an exchange when my loudspeaker died, after that it booted just like new. On T-Mobile h918
Common sense isn't all that common

ZDeuce2 said:
This is not true, I factory reset mine and relocked the bootloader for an exchange when my loudspeaker died, after that it booted just like new. On T-Mobile h918
Common sense isn't all that common
Click to expand...
Click to collapse
Well maybe you can offer some insight on how to do that instead of just criticizing. Pardon me if I'm reading that wrong but that's what your reply sounds like. This is the guide I used to go back to stock. Afterwards I tried to flash the stock recovery which failed or so I believe and then relocked the bootloader in fastboot mode. I still had a flag... How did your do it, if you will please.

andrewjt19 said:
Well maybe you can offer some insight on how to do that instead of just criticizing. Pardon me if I'm reading that wrong but that's what your reply sounds like. This is the guide I used to go back to stock. Afterwards I tried to flash the stock recovery which failed or so I believe and then relocked the bootloader in fastboot mode. I still had a flag... How did your do it, if you will please.
Click to expand...
Click to collapse
It's not a criticism, I removed root, in adb I did oem bootloader lock. It reset data, which in turn turned off developer options, resetting the oem unlock switch. Rebooted, and no security warning. I didn't bother flashing stock firmware, just unrooted, and relocked the bootloader in adb, That is all
Common sense isn't all that common
---------- Post added at 11:42 PM ---------- Previous post was at 11:35 PM ----------
Sorry you took my post as being critical, that wasn't my intention, I was just simply stating that I was able to remove the secure boot message, although T-Mobile didn't even check, I told them I had so ready backed everything to my SD card and reset. They just pulled the battery, sim, and SD card, stuck them in my new one, made sure my Google account loaded, and I walked out the door.
Common sense isn't all that common

ZDeuce2 said:
It's not a criticism, I removed root, in adb I did oem bootloader lock. It reset data, which in turn turned off developer options, resetting the oem unlock switch. Rebooted, and no security warning. I didn't bother flashing stock firmware, just unrooted, and relocked the bootloader in adb, That is all
Common sense isn't all that common
---------- Post added at 11:42 PM ---------- Previous post was at 11:35 PM ----------
Sorry you took my post as being critical, that wasn't my intention, I was just simply stating that I was able to remove the secure boot message, although T-Mobile didn't even check, I told them I had so ready backed everything to my SD card and reset. They just pulled the battery, sim, and SD card, stuck them in my new one, made sure my Google account loaded, and I walked out the door.
Common sense isn't all that common
Click to expand...
Click to collapse
Good to know. Although I tried those steps it still didn't take away the flag. But I suppose I did something wrong... Thanks for your input.
tApPeD fROM mY nExUs 6

funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.

dimm0k said:
funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.
Click to expand...
Click to collapse
I traded in my v10 still rooted, no question asked... And returned my first v20 for a blown speaker, it was rooted when I took it in, I did restored to to unrooted and looked the bootloader for the return, mainly to see if it fixed the speaker. But in all the years I've had T-Mobile, that is the first time I've returned a phone stock... No one has ever said anything about it.
Common sense isn't all that common

Yeah with sprint currently and I've returned rooted HTC 10, rooted note 4, rooted htc m8, and no questions ever.
Beastmode on my LG V20

dimm0k said:
funny note, my LGV10 experienced the fruity bootloops this past Thursday and realizing any sort of repairs would take too long to be without a phone so I gambled $$ away and went for the LGV20. during the purchasing process they asked me if I wanted to trade in my LGV10, for which they'd give me $95 if the screen wasn't cracked and there was no water damage, as long as it powers on. Well, it powered on and it was on the bootloader unlocked message... the rep saw this message clearly, but called over the manager to verify. pretty sure right as the manager came over to take a look, he saw the message for less than a second or two before the device booted up... that's when LiveBoot kicked in with the fast scrolling kernel messages in various colors. the look on the dude's face was priceless! as it read WTF! despite that he was like yeah, it just has to turn on so process it.
Click to expand...
Click to collapse
Wow, thats funny. Im glad you had that luck. Idk that id be so lucky, but that made for good story.

I found a couple posts which were terse but sent me on the right path it seems. For others here is what I did:
1. Removed all of my accounts in the Settings.
2. Made sure USB debugging enabled.
3. Booted into download mode (hold volume down whilst inserting USB cable.
4. Fired up uppercut (being sure to disable A/V program first). Sees the device on a com port.
5. Loaded the 10p kdz, checked upgrade, and let her rip.
6. Device rebooted showing my apps and stuff. But no root any longer.
7. Factory reset the device.
8. Went through just enough of the setup to enable developer mode and USB debugging.
9. Note that OEM unlock is still on.
10. Did the following variation on what is shown in the first post of this thread <https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258>:
* adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
* adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
* fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
* fastboot getvar unlocked ----->THIS CONFIRMS THE BOOTLOADER HAS BEEN LOCKED
* fastboot oem lock---->THIS COMMAND WOULD LOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
* fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN RE-LOCKED
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
11. Device now boots without warnings and into stock Android welcome screen.
BTW - when doing anything like this with a device I always recommend that (a) use USB 2 port, not later, and (b) be sure to use a USB port that is on the computer's motherboard.

Stuck on twerp read only ...with lock

Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?

back to bootloader and
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...

pen101 said:
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
Click to expand...
Click to collapse
Hold power longer than 10 seconds (hard reboot) then volume down and it'll boot bootloader. From there flash a working boot image with working TWRP patched for the Rom you are on.
Sent from my PH-1 using Tapatalk
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
pen101 said:
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
Click to expand...
Click to collapse
https://www.youtube.com/channel/UCucUjVNJshybBA8JWftayVA check out my channel where I provide tutorials, reviews and files in links to complete pretty much any task for essential.
Sent from my PH-1 using Tapatalk

First and foremost,,,,
THANKS FOR THE REPLIES AND ADVISE.
Got up, drank a cup, dragged a brush across me head...booted up bootloader, hit on recovery mode and now back to square one with the latest pie flavor.
Sometimes you "over work" the problem.
As a mechanic I sometime got "stuck" and instead of getting frustrated, I simply walked away and came back to it, only to find (as with this) a simple solution.
I am expecting a tv box (PIE, 4 and 64)....should be a head scratcher.
Great forum, good peeps...MANY THANKS!

[HELP] Unlock bootloader.

Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.

Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..