Database Users

Phone started rebooting randomly yesterday, now stuck at Google splash screen

I'm pretty adept when it comes to adb/fastboot/flashing etc but I'm running out of ideas here.
Yesterday my phone rebooted twice on its own --- didn't think much of it (but probably should have in hindsight). Happened a third time and now all I get is the white "Google" splash screen with constant reboots.
Holding volume down does get me to bootloader --- however cannot get into recovery (same issue with google screen). Tried plugging phone into multiple PCs in bootloader mode but I get device cannot be recognized (usb device malfunction). Tried manually updating the driver - nothing.
All I want is to retrieve the photos/videos of my kids --- hoping there is some last resort that someone can suggest before I give up on this thing.
Ideas anyone?

UPDATE: Got phone to recognize via fastboot ---- still can't get to recovery. Anyway to get files?

Same happened to me, something is horribly wrong with the build(s) that came out this month as more and more people are having this exact issue. I was able to barely get mine to boot initially with the latest stock image, just long enough to upload all my pictures via Google Photos before it would freeze and go right back to the constant rebooting.
Eventually even trying a stock image stopped working, I RMA'd my phone.
This seems to be a ticking time bomb and is going to be a huge issue very soon. It's really going to be rough for anyone beyond their warranty period unless Google/Huawei steps up after they realize what's going on. I'm not even sure what I'm going to do with my phone once I get it back for fear of causing the issue again.

My bootloader is locked so I feel like I'm SOL here.... hoping for a miracle

Just got off the phone with Huawei tech support.... apparently its a known issue with no resolution currently. This is some bs

That's not gonna help you ATM but you should really always backup important stuffs. My important stuffs are also kid photo and they are backed up in my cloud AND in Google photos.
From bootloader screen, can you give us your device specs? Like emmc, date, sku,.. ?

NYYFan325 said:
Just got off the phone with Huawei tech support.... apparently its a known issue with no resolution currently. This is some bs
Click to expand...
Click to collapse
Wow really? Are you saying they wont allow you to RMA it? Are you still covered by the warranty?

Seanmiz said:
Wow really? Are you saying they wont allow you to RMA it? Are you still covered by the warranty?
Click to expand...
Click to collapse
Trying to find out now....
Is there anyway to reflash stock images with only being able to access fastboot and a locked bootloader?

NYYFan325 said:
Trying to find out now....
Is there anyway to reflash stock images with only being able to access fastboot and a locked bootloader?
Click to expand...
Click to collapse
I would grab the Nexus Root Toolkit (that's what I used for all of my resurrection attempts, makes it super easy)
http://www.wugfresh.com/nrt/
Use it to flash stock (and unlock the bootloader in the process) from Fastboot. Let it sit (and bootloop many times) afterwards as the popup suggests and see if you can get lucky with some access to your phone. Either way you can then relock your phone with the toolkit and you're ready to RMA.

The bootloader is not able to be unlocked since the setting was never checked within android itself. I let the phone sit trying to boot for a solid half hour or so just rebooting at the google logo. I think its just a brick at this point

NYYFan325 said:
The bootloader is not able to be unlocked since the setting was never checked within android itself. I let the phone sit trying to boot for a solid half hour or so just rebooting at the google logo. I think its just a brick at this point
Click to expand...
Click to collapse
I'm not sure what you mean, I could lock and unlock the bootloader at will, without anything but fastboot functionality.

Seanmiz said:
I'm not sure what you mean, I could lock and unlock the bootloader at will, without anything but fastboot functionality.
Click to expand...
Click to collapse
You probably had the box ticked in developer settings or had previously unlocked it.

I believe rootjunky posted a video on how to do it with bootloader being locked

Just got off the phone with tech support again.... phone is under warranty and they are going to send me a new one. Sucks about the pictures/videos but what can you do

Is it the recent updates that's the issue? I'm still on pure Nexus 7.0

Same happend to me and someone in another thread too.i think there is a big problem with the last build
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk

Wish I knew the cause.... as stated I was bone stock - locked bootloader and all (that's never going to happen again since I couldn't re-flash stock images because of this). Huawei was no help as to the cause other than to blame google.

NYYFan325 said:
Wish I knew the cause.... as stated I was bone stock - locked bootloader and all (that's never going to happen again since I couldn't re-flash stock images because of this). Huawei was no help as to the cause other than to blame google.
Click to expand...
Click to collapse
Well, to be fair, this issue seems to have just started popping up with a handful of us in the last week or two.
I'm sure they are in the process of trying to figure out what happened and why with the RMA units they have. Since we were all just fine prior to this month and suddenly had this happen on various 6P phones of different ages, I'm guessing some code that Google added lately can potentially corrupt the memory/storage in certain scenarios.

This is an escalating issue
ArN0V said:
Same happend to me and someone in another thread too.i think there is a big problem with the last build
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Click to expand...
Click to collapse
Have you requested RMA? The same happened to me too last monday night just browsing Chrome, but it isn't just the build people have in common but also the TWRP version 3.0.2-1, so everyone with their 6P still running, update your TWRP and change your ROM it sucks being a week without your phone besides losing all your files :crying:

GKti22 said:
Have you requested RMA? The same happened to me too last monday night, but it isn't just the build people have in common but also the TWRP version 3.0.2-1, so everyone with their 6P still running, update your TWRP and change your ROM it sucks being a week without your phone besides losing all your files :crying:
Click to expand...
Click to collapse
Yes i send it back to amazon.i'm waiting news from it

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!

Nexus 6P BOOTLOOP after using Facebook

1 hour ago, I was checking Facebook, and a moment later, my phone started to restart... After a few moments, I realized that my phone was in bootloop. I tried booting into recovery, but It started a bootloop again. Flashed TWRP, nothing happens, still bootloop. Flashed vendor, system, boot, cache, recovery, radio, bootloader from lastest factory image. I have very important data on my phone, so the last thing I want to do is to do a factory reset. But I still hope that I can somehow get the userdata partition from bootloader or somehow make it boot. Can you help me? The only thing I can open right now is bootloader.

I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted userdata partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.

frostydawn said:
I'm having an exactly the same problem with you.
The only difference is that I didn't use Facebook.
I dared to lose my every data so I formatted every partition of my phone and flashed stock image, but it didn't fix mine.
I failed at figuring out the solution yet, but there's still one hope.
When I contacted with huawei, they said there's an upcoming update, and it will fix bricked phones.
I don't know if it will work, but considering you had your bootloader unlocked and can access it, and you have some important datas that you don't wanna lose, I recommend you keep your phone until the update gets released, then manually flash it without wiping your user data.
Given our phone's symptom is exactly the same and you tried similar methods I've tried, this is the best way I think you can try.
Good luck. You're in the same boat with me.
Click to expand...
Click to collapse
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...

fftorettol said:
Yes, but we can wait for this update for months.. Also, when you flash a factory image, you lose you data (correct me if I'm wrong). So, it doesn't matter to me, if I try to format user data, or wait for the update. Hm...
Click to expand...
Click to collapse
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.

frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc has been released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Right! I've just got an idea to try older factory image versions for Nexus 6P... Mabye I get it working . I will let you now

I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.

stillwind said:
I'm on the same boat as both of you guys. I tried installing TWRP but it continues to bootloop.
I have some important data I didn't get a chance to backup. and would not want to send it back/factory reformat.
Here's my thread:
https://forum.xda-developers.com/nexus-6p/help/nexus-6p-bootloop-to-recover-files-t3551455
Please keep us updated.
Click to expand...
Click to collapse
frostydawn said:
Well, android 7.1.2 beta for nexus 5x, pixel, or etc was released a few days ago, and for nexus 6p, it'll be released soon.
This is just my imagination, but maybe they're taking some times fixing boot loop so the release for 6p is getting late.
Also, you can flash factory images without user data lose by manually flashing it using fastboot commands.
The released image will contain some .img files, then you can extract it and then only flash required files without formatting userdata partition.
Don't use flash-all.bat, and use fastboot commands to selectively install image files except for userdata.
Click to expand...
Click to collapse
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.

fftorettol said:
Guys, did you manage to fix it? I was doing some research, talking to some persons, and they said that it is probably a hardware problem. So, I went to the nearest Huawai servis, and they told me, that if the problem is really on hardware, it will cost me around 340€ (363 dollars) to replace motherboard... I can't afford that much... Its is almost a price of a new phone. I hope you came up with some better solutions.
Click to expand...
Click to collapse
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks for my phone to be bricked after I bought this phone.
I really want to get this phone back, but the hope is too faint.

frostydawn said:
For now, I failed.
New 7.1.1 minor build update didn't fix my phone.
And google said they can't assure there will be update that will fix my phone.
I'm waiting for 7.1.2 beta, and if that doesn't work, well.. I don't know.
Maybe I should await 7.1.2 official, or.. just give up everything.
My hope is getting faded, and yeah.. for now, I can do nothing but wait for update.
Actually, I don't think those updates will work.
I'm just giving it a last chance, since repair service at here also costs about 350$, and if I fail, I should keep using Nexus 5.
Ah... It didn't took 2 weeks after I bought this phone.
I really want to get this phone back, but the hope is too faint.
Click to expand...
Click to collapse
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?

fftorettol said:
Exactly... I was thinking... What if we lock the bootloader and send the phone to repair service with warranty papers... Do you think that can actually work out? Can they see that the phone was rooted, if we lock the bootloader with ADB Shell?
Click to expand...
Click to collapse
I live in South Korea and in my country, they provide repair by post service for devices in the warranty period.
For me, my warranty is expired, so I had to bring it to the service center myself.
I've locked the bootloader and brought it the center.
They didn't check if it was ever unlocked or rooted.
The engineer only tried rebooting my phone several times, and said he should replace the motherboard. And they said they couldn't fix it for free because the warranty is expired.
I don't know how Huawei in your country will handle it, but I think if you flash the stock image and lock your phone, maybe they won't see that was ever rooted.
But I also don't know if they will provide free repair.

No luck on my end. I tried everything... I've been flashing and repairing problems like these since the nexus one but I'm totally stumped. Lucky/Unlucky for me I've only had the device for 3 months so I have an RMA ready since it is under warranty.
Most importantly tho is that I want to recover the files on the device which will not happen if I take it to the repair center as they reflash all the devices before proceeding to fix it.
I tried getting TWRP but the device reboots back into the boot as soon as I select recovery.
Also tried flashing everything but user data using flashboot and the nexus 6 .img files but still in the same situation.
I just wished they would've at least added a microsd option so I could at least have some of my files back...
I don't think I will ever get a phone without microsd option again or root and unlock bootloader on every device I get. This was the first phone I decided not to mess around with since everyone kept telling me to enjoy the stock experience....
Worse experience to date with android.

Well I gave up trying to fix it by software, and found another solution.
My warranty is expired, so it wasn't cost-efficient to bring my phone to official service center.
Now I bought a display-broken phone at about 60 dollars.
Gonna bring it to an engineer and replace my phone's motherboard with its intact one.

frostydawn said:
Now I bought a display-broken phone at about 60 dollars.
Click to expand...
Click to collapse
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.

v12xke said:
That's a great price. Is it the H1512 (International) and where did you purchase? Haenguneul bileoyo.
Click to expand...
Click to collapse
It seems like you're Korean like me.
I bought it from Naver Cafe Google Reference Nexus Forum's market.
And yeah. It's H1512.

No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.

v12xke said:
No, i'm not Korean but I spent a couple of years working in Okpo and Ulsan on several projects. There is a guy from KL in another thread looking for an H1512 motherboard. I'll pass your info on to him. Thanks.
Click to expand...
Click to collapse
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.

frostydawn said:
Well, then tell him this too.
Naver Cafe 'Joonggonara'
This is one of the largest market for used stuffs.
Click to expand...
Click to collapse
Link Product

VN_Optimus said:
Link Product
Click to expand...
Click to collapse
It was a one-off purchase of a broken phone on a Korean market equivalent of Craigslist. You'll have to dig around and find one locally... and be lucky, too.

I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc

DocEsq said:
I just had reboots today for the first lasting about 20 minutes. I was able to get into Recovery and clear the cache and then shut down the phone. Upon restart it looped a few times and then fully booted (thankfully). I have placed the latest firmware in the phone in the hope that if this happens again I can flash the firmware and access the phone.
I hope this helps a bit.
I am rooted and running N2G47H.
Doc
Click to expand...
Click to collapse
Hopefully it will but realistically this could be the beginning of the end for your phone given the 6P history with the boot loop of death. Presumably your phone is out of warranty?

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.

laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...

Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse

laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...

I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse

laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.

dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.

v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.

5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....

Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.

v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)

just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.

laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...

5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)

laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...

Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!

fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks

Nexus 6P: Bootloop

Hey, Thanks for taking the time to help.
Device: Nexus 6P
Previously Working ROM: Pure Nexus
Recovery Type Was: TWRP
So, I was on Pure Nexus just fine and decided okay! It's been a few updates I'll just update to the newest version. Went ahead and did a Clean Flash, wiped everything in TWRP except the Internal Data, proceeded with a Flash for the new Vendor Image and then to the newest ROM. Restarted and an immediate boot loop.
Thought okay, whatever. I'll just use the my backup that I have! booted into TWRP did backup.. still boot loops. At this point I'm pretty upset cause I know I'm in a pretty terrible spot now, so I decide to do a Factory Image complete restore through Fastboot flash-all.bin.
CONTINUES to boot loop after that, also doesn't even install the stock recovery or something because after a stock flash it shows "No Command". Decided okay, I'll flash TWRP and attempt a factory reset in there, do so. Still boot loop.
So yeah, here I am.
Any advice?

The bootloop of death may have caught up with your phone. When did you get the phone, you may have to rma the device. There is a thread here that many have the same issue. Some have gotten rma out of warranty some didn't. You may want to try.

Hey, the "No Command" is actually stock recovery. You should see the Android on its back with it's chest plate open or something like that. A red exclamation mark in a triangle as well, IIRC.
When you're on that screen, hold power and press and release volume up and that'll take you into stock recovery. If that doesn't work, do it the other way around. Hold volume up and press power.
If you can get into stock recovery, you should be able to use ADB to pull your files, at least.
My 6P screen crapped out yesterday and I just had to pull data myself, let me know if you need any help.

Thanks for the replies, still stuck in a boot loop even after trying another Factory Image in case the one I got was just no good.
Still nothing, was able to get into the recovery even with the no command thing to Factory Reset/Wipe Cache and the problem still persists.
I'm at a loss at this point, I even tried to flash each file in order manually instead of with the flash-all command anddddddd nothing In the end, I'll probably try and RMA since I'm still within a year.
Anyone been through the RMA process want to give any tips on the process? Should I re-lock the boot loader before sending it in?

Don't even bother, you're screwed basically. Call Google or Huawei were you bought it from and ask for a out of warranty RMA. I got mine only last week after they had it for a week. Prepared to be given the run around if this is with Huawei. Google is currently out of 6P's so you might be given credit if you bought from them, that's a big BUT. Good luck and I hope you have a backup of your files off the phone.

bammyman said:
Don't even bother, you're screwed basically. Call Google or Huawei were you bought it from and ask for a out of warranty RMA. I got mine only last week after they had it for a week. Prepared to be given the run around if this is with Huawei. Google is currently out of 6P's so you might be given credit if you bought from them, that's a big BUT. Good luck and I hope you have a backup of your files off the phone.
Click to expand...
Click to collapse
Actually, I'm still within the 12 months. But I know that the whole Custom Rom thing kind of voids that. I did end up calling Huawei and ended up getting the in-warranty RMA started but... kind of scared cause I'm not sure if the whole flashing the thing with a non-offical ROM gets flagged some how.
Should I call back and specifically request an OOW RMA? Or just take my chances with the In-warranty RMA?

They do not care about custom roms. Just send it in with a factory reset. I sent mine in with Android O and they were fine with it

I'm sorry I don't know who to turn to for help. I have a Nexus 6p and it is stuck in bootloop. I'm phone illiterate so I don't even know how to go about fixing it. There are very important photos and voice notes on there of my father that I would like to preserve as they are the last things I have of him before he passed away. Willing to pay $ to get this fixed. Any ideas?

BB12345 said:
I'm sorry I don't know who to turn to for help. I have a Nexus 6p and it is stuck in bootloop. I'm phone illiterate so I don't even know how to go about fixing it. There are very important photos and voice notes on there of my father that I would like to preserve as they are the last things I have of him before he passed away. Willing to pay $ to get this fixed. Any ideas?
Click to expand...
Click to collapse
Are you able to get into recovery?