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.
Related
Hey everybody,
i wanted to update my rooted N4 with twrp from 5.1.0 tp 5.1.1. So i thought i just flash bootloader.img, radio.img, boot, system, recovery and cache.img from 5.1.1 factory image on top of my existing 5.1.0 setup. After that i reflashed twrp and rerooted with CF-auto-root. I gues that's where it went wrong. After that i got stuck in a bootloop. So i decided to restore my nandroid backup. Doesn't work. Can't mount cache and ends the data restore with error 255. That sucks. So i decided to flash the 5.1.0 factory image. So i flashed it with flash-all.bat in fastboot. Now it should be good to go, but i'm still stuck in a boot loop. The 4 colored dots are flying around for hours. Whats am i supposed to do?
Haalp!!
Thanks a lot
I had thamt proble so i finally booted into the bootloader using the press Volume Down and power button the did a recovery and let it reboot and everything worked fine after that....
Nexus GPF Lollipop Troubleshooting Guide & Tips
Scenario #1: For Folks that have received the OTA prompt, but the device seems to be “hung” in a bootloop state:
Please be ready to wait 30 minutes for the L installation to finish updating. Please do not interrupt the OTA mid-process.
If that doesn’t help, please see recommendations within Scenario #3
Scenario #2: For Folks that have received the OTA prompt, downloaded it and had it say “Failed”:
Is your bootloader unlocked? Are you rooted? There is some information that’s floating around that says an unlocked bootloader is causing issues. I, nor Google for that matter, can confirm the issue being related to that, I'm just here to try and help those having OTA issues. If you do have an unlocked bootloader, please try locking it, and accepting the OTA that way.
If you’re looking for ways to relock: a google search would yield similar results to this or there are toolkits that can help with relocking (Wugfresh for Example), however *tinker at your own risk, we are not suggesting this as the preferred method, just giving you options*
Scenario #3: “I still have not received the L OTA update! When will I be able to download it for my Nexus xxx”
Please be patient as the Android 5.0.1 Lollipop OTA update is still rolling out to all Nexus owners (for example, the factory images for the Nexus 4 & 6 just popped up). Depending on where you are located in the world, you should be receiving the notification soon.
For those trying to remember how to check for the update: Settings > About phone > System updates. We’re all guilty of checking at least several times a day, don’t fret, it will show up .
Wanna know how the rollouts work while you’re waiting? There's a good article on Android Central that explains how and why the OTA works. Owners of Nexus devices should periodically check the system updates as Google handles rollouts across devices differently.
I hope that helps
Let us know how you do
Blacksmith5 said:
I had thamt proble so i finally booted into the bootloader using the press Volume Down and power button the did a recovery and let it reboot and everything worked fine after that....
Click to expand...
Click to collapse
Thanks for ya help. But what exaclty do you mean by "did a recovery" in bootloader?
Thanks
Okay, never mind. I just interrupted the bootloop as i did a hundred times before. Now it restarted within seconds. Computers are weird people.
Wipe the cache in Recovery.
This fixed my boot loop on a dirty flash to 5.1.1.
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Probably something went wrong in the update process and conflicted with something else.
Anyway: hard reset.
The "no command" screen is just a security screen and it's normal, you need to bypass it to enter to the recovery with a button combination (that now I don't remember, but I never remembered it even though I used to enter in recovery after pressing random buttons combinations lol).
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
cybrdude said:
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
Click to expand...
Click to collapse
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
cybrdude said:
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Click to expand...
Click to collapse
Press power + volume up to get recovery menu.
Was having a similar issue. I'm all stock, unlocked bootloader. Signed for N preview and instantly got the OTA download. It installed and pretty much within a few minutes the bootloops started. couldn't even power down without it rebooting on its own. I got it to power down without turning itself back on through recovery/power down. I let it sit and cool down. Upon reboot.....was doing well, and started to boot loop again. I REALLY did not want to factory reset.
Heisenberg said:
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
Click to expand...
Click to collapse
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
So for me, a factory reset and setting up a brand new phone (no backups of any kind....even from Google) have seem to do the trick. Unfortunate that I lose my wifi password backups. Asking some people for their wifi passwords again is a PIA. Especially the ones who don't know them, and it's a 27 key password from their cable company. Anyone know how to pull just the wifi backups from google?
My thought is one app or setting was causing my problem so I'm slowing adding everything one at a time. PIA really. I don't miss the Froyo days that's for sure.
cybrdude said:
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
Click to expand...
Click to collapse
What happened to your old account?
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
My Nexus 6p just rebooted randomly, and it's stuck in a bootloop. I am on 6.0.1 (ignore the thread name, it's a typo), I did not upgrade to 7. I am rooted and bootloader unlocked. I can access recovery (TWRP). Can anyone help?
I just attempted to update to the latest build of 6.0.1 (since I had been putting it off) via fastboot, and that still didn't fix it. Still bootloops. Hoping to avoid a factory reset if possible.
Factory reset didn't help... Tried to format the data, didn't work.
Sadly it sounds like your 6P bit the dust. You can see if any of the posted possible solutions in this thread help, but...
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Yeah, I don't know... I thought if I could boot to recovery, it would be easy to fix. But no matter how many times I wipe, factory reset, format, use adb to reinstall, it keeps bootlooping.
Yeah sounds like the boot loop of death. If you formatted data and fastbooted the factory image and still no go, that's pretty much that.
Great. I'm just over a month outside the warranty period and they want me to pay $160+ to get a replacement. And the replacement will have just a 90 day warranty, and if this issue occurs again, which is likely, I'll have to pay $160 again. Never getting Huawei again.
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