Nexus 6P stuck at unlocking after N update - Nexus 6P Q&A, Help & Troubleshooting

Hi there,
So I updated my 6P to android N Yesterday (build 3) and all went well untill I had to boot the device. Like normally it asked for my pin to unlock it, but when I enter it. It tries to boot and crashes every time while doing so. Does anyone know how I can fix this? The 6P is locked, but can I maybe go into recovery (which says there is no command when I do) and install Android N? Thanks!

sebastiendeb said:
Hi there,
So I updated my 6P to android N Yesterday (build 3) and all went well untill I had to boot the device. Like normally it asked for my pin to unlock it, but when I enter it. It tries to boot and crashes every time while doing so. Does anyone know how I can fix this? The 6P is locked, but can I maybe go into recovery (which says there is no command when I do) and install Android N? Thanks!
Click to expand...
Click to collapse
Probably do a factory reset then boot up. You may have to ADB sideload the DP3 file from within recovery. Instructions are also here as well.

Related

Nexus Bootloop (tried flashing and wiping)

Hi,
I have a rooted nexus 6p, all was well until it decided to reboot and boot-loop when I opened my music app. I get as far as the white Google logo then the phone restarts and I'm back to the normal warning then Google logo then reboot.
I have managed to get into the recovery screen (with the android laying down) but when i choose recovery mode the phone just starts boot-looping again.
I am wondering if I have somehow managed to hard brick it?
I have tried to flash the latest OS onto my phone but it said no signature.
I did managed to wipe the device also.
Thanks for any help.
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
istperson said:
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
Click to expand...
Click to collapse
When my phone started playing up I was still on MM 6.0.1, I tried to flash N after the boot-looping started.
Thanks

7.1.2 bootloop problem

Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Vince.L said:
Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Click to expand...
Click to collapse
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Geeks Empire said:
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Click to expand...
Click to collapse
Why are you spamming this forum? Please leave your personal advertisements out of your posts.
can't you sideload the ota file of a 7.1.1 rom? you should be able to access bootloader screen.
if it's not the bootloop of death that's been happening around here (included me) you can download an ota file from google factory image page and sideload it
jhs39 said:
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
Click to expand...
Click to collapse
Maybe i could donate to the websiteand we can get a thread up and runnig becuaseit took my over an hourto find a fix i havnt even tried yetin regards to the 71.1.1 bootloos onthe Goggle screen as well as the spash scrren, ihave sence lost the spalh screen now its juts black and white google
Some people have reported that the Skipsoft Toolkit got them out of a bootloop. I haven't tried it myself but I think you are giving up too easily. I've gotten lost of phones into boot loops but I don't panic because there is usually a way out. That isn't always the case with the 6P since there is the boot loop of death issue, but I still wouldn't give up just yet.

Nexus Player stuck on " Can't Load Android System. Your Data may be corrupt"

Nexus Player stuck on " Can't Load Android System. Your Data may be corrupt"
Hi, my Nexus Player is stuck on " Can't Load Android System. Your Data may be corrupt. If you continue to get this message you may need to perform a factory data reset......."
When I do the factory reset it brings me back to this screen. My son told me it happened after an update.
I can't get it to do anything else.
Is there a solution?
I’m experiencing this same issue now. Stock Oreo, unrooted. Anybody have any ideas?
Same happening here. Unrooted, Stock Oreo. Happened after an update.
Have attempted to get USB connected in recovery to ADB push the factory image with no luck.
Device not showing up on windows or mac.
ratmandu said:
Same happening here. Unrooted, Stock Oreo. Happened after an update.
Have attempted to get USB connected in recovery to ADB push the factory image with no luck.
Device not showing up on windows or mac.
Click to expand...
Click to collapse
So Google is hard-bricking our devices with no replacements in sight? This is crazy. This isn't the only thread about this.
taino211 said:
So Google is hard-bricking our devices with no replacements in sight? This is crazy. This isn't the only thread about this.
Click to expand...
Click to collapse
I wouldn't quite go so far as to imply that they are doing it on purpose. It is most likely lack of testing of updates going out, since it is an old, and now unsupported device.
This happens to my nexus player too, after update push from google.. Apparently google pretty much bricking all nexus player by pushing bad firmware update. I can see class action lawsuit coming if google doesn't fix this soon
Successful restoration of factory image into nexus player
Andy Jawa said:
This happens to my nexus player too, after update push from google.. Apparently google pretty much bricking all nexus player by pushing bad firmware update. I can see class action lawsuit coming if google doesn't fix this soon
Click to expand...
Click to collapse
Update, I did follow the direction posted on another forum and was successful on restoring my nexus player. Here's the procedure that I found working for me. I had to flash it couple of times since the latest image doesn't seem to fix it. Also the usb driver tool doesn't seem to work properly on my windows 7 laptop, but works in windows 10, but it may just be my Win7 laptop that has too much security restriction.
Here's the procedure.. good luck. Sorry, since I'm newbie, xda won't let me post actual link, I have to remove the http, but it is a good link, you just have to paste it into browser
1. Download Google USB driver from : developer.android.com/studio/run/oem-usb
2. Download and unzip ADB and Fastboot tools: developer.android.com/studio/releases/platform-tools
3. Download and unzip Nexus Player Factory Image: developers.google.com/android/images#fugu
I tried the lastest one : 8.0.0 (OPR2.170623.027, Nov 2017) , but it crashed again. I then loaded the 8.0.0 (OPR6.170623.021, Sep 2017), and it seems to work so far. I disabled the auto-update on the play store just to be safe, but not sure if this would prevent the OTA.
4. Open command prompt window and go to the unzipped folder for the fugu image
5. Add path to the ADB/fastboot tool into system PATH, example:
PATH=%PATH%;D:\Dnload\platform-tools_r28.0.0-windows
6. Get into bootloader of Nexus player using this procedure:
- unplug power of NP
- Press the button on the bottom of NP, keep it pressed and plug-in power
- keep it pressed for about 8 sec, and release, it would go into fastboot mode, showing you the current setting and boot option with default of "normal boot"
- press button one time to stop it from doing normal boot
7. Plug microUSB cable between NP and your PC, and install driver (unzipped in step 1) if asked.
8. Back on your command prompt, type "fastboot devices", it should show the nexus device, if nothing is listed, there's still driver issue that need to be fixed.
9. Now we can follow the instruction to flash the factory image from developers.google.com/android/images. I will summarize the step below that work for my nexus player (pre 2015 device)
- unlock bootloader by issuing command: "fastboot oem unlock". You should see the status updated on the screen to unlocked.
- Execute the "flash-all" script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
You should see the activity on screen, like downloading state. While the script is running, it would also reboot the nexus player into bootloader, and waiting for the NP to come back up into bootloader. Once it comes back up, the script would resume. In case the player doesn't go back into bootloader, do step 6 to manually get into bootloader
- After the script completes, for security you should lock the bootloader again, by going back into bootloader (see step 6) and issuing command: "fastboot oem lock"
Mine started doing this also, it sits at the GOOGLE screen for a while, flashes/reboots once in a while and then eventually goes to the NO COMMAND screen.
I flashed it back to 7.0.0 NRD90R and it booted up fine, setup things and it worked fine even after the OTA to 8.0, but something else updates soon after that and fails again.
I just flashed the 8.0.0 OPR2.170623.027 before I left for work so we'll see what state it's in when I get home.
My second one is fine so far.
Mines dead too, stock, no root.
I will try flashing older version and see.
Wow, WTF is happening to the Nexus Player?
My Nexus Player have been unused for the last few months (I think I just upgraded it Oreo to test it when it went out), what can I do to save it from the sudden death?
Can I power it up without WiFi and block updates or something?
Just saw this on the google forum.
Can't load Android System (https://productforums.google.com/for...us/Ski0fFZ0pZM)
Quote:
GEL1966 via Nexus Help Forum
I was encouraged by a reddit user to open this: https://issuetracker.google.com/114276277 He suggested I get as many people I could to "star" the issue. Hopefully it yields something other than an "escalation". Will post any news.
My Nexus Player has been at Android 8.0.0 for a while.
I hope I didn't jinx it by posting here
If it quits working, I still have a Roku and a fireTV.
Sent from my SM-G930T using Tapatalk

Nexus 10 stuck in boot animation even after wipe/sideload

I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
jsm11482 said:
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
Click to expand...
Click to collapse
Mine does it aswell, but after like 20 min it boots up. I flash mine with the "Nexus Rool Toolkit" with the option "Flash Stock + Unroot", in your case i wull put the radio button on "Softbrick/Bootloop". Then follow the steps on the screen and then when it reboots the programm will tell you that you need to wait like 20 min. And then it should be up and running again

Android 10 update hanged in locked phone. Recovery pattern locked.

Hello, everyone.
Hope you are having a good day with your OnePlus 5 phones. I recently tried the OTA update for Android 10 on my OnePlus 5. But the update hanged, and I had to force restart. Now, the phone doesn't go beyond the logo. I tried to start in recovery but it asks for pattern and doesn't recognize the existing one.
Is it possible to resolve this? I have lot of data on the phone. It seems that factory reset will delete data, but is it possible to recover the same?
Please guide me out of this issue.
Thanks.

Categories

Resources