Stock unrooted device in soft-brick bootloop running 7.1.1 - Nexus 6P Q&A, Help & Troubleshooting

Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(

I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.

bkgovols said:
I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.
Click to expand...
Click to collapse
When you say haven't gotten an answer yet.... you posted it somewhere? I bet an easy fix for google would be to release a newer full OTA... but unless they respond in a day, i'll be returning phone...

gunigugu said:
Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(
Click to expand...
Click to collapse
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.

tropical cactus said:
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.
Click to expand...
Click to collapse
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.

gunigugu said:
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.
Click to expand...
Click to collapse
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile

gunigugu said:
Hi,
...I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked....
Click to expand...
Click to collapse
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?

fapste said:
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile
Click to expand...
Click to collapse
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'

v12xke said:
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?
Click to expand...
Click to collapse
Yup never did it :'(
Didn't think I needed to unlock / root my devices anymore since I can get all the functionality out of stock android these days. Though now I feel like I'm being punished for not unlocking it :'(
I'm positive I did a factory reset from recovery. I do believe flashing a full google image would fix the issue, but im unable to from fastboot as device is locked and sideload images appear to be older :'(

Really sorry to hear this, and I know being without the phone even for a day or two is inconvenient at best. Could be critical for your work or school. Most every bootloop I have encountered, I've been able to fix by re-flashing the kernel. Either stock or custom... like EX Kernel. Have you ever played with WugFresh's NRT? You can temp flash TWRP and maybe temp flash or flash the kernel? This probably won't work with a locked bootloader If you could just start the OS, you could toggle the OEM unlock. At a minimum, TWRP will give you a file manager, MTP file transfer, wiping and other tools. If you have time, it may be worth a try. Other than that, successfully altering the signature of the OTA may work, but I've not seen any work on this, but have never had to look. I'd keep searching for ppl having the difficulty of going from DP2 to Public Release (older/newer) and see if there was another solution other than flashing the full image, which obviously you can't do right now. Good luck, and let us know if you make any progress.
Edit : Read here for possible help. This may work in conjunction with getting TWRP installed via NRT.

gunigugu said:
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'
Click to expand...
Click to collapse
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images

fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
Many ppl have had problems sideloading the OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".

fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
I believe it's because the latest OTA on https://developers.google.com/android/ota is 7.1.1 (NMF26F) and my phone is already running 7.1.1 build (NPF26F).

v12xke said:
Many ppl have had sideloading OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".
Click to expand...
Click to collapse
This guy gets it!!! Yeah, I've unlocked a lot of my older devices and am comfortable with 'messing' my devices, but I didn't with the 6p as the stock experience is great now. But now I feel like I'm being punished because my device is dead with no recourse for action. Unless google release a newer full OTA.

If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".

v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
This will work on a locked device? I'll give it a crack and report back.

v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
Yeah failed :'( (remote: unlock device to use this command)

[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 i encountered a problem like this too

boxguy1 said:
[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 i encountered a problem like this too
Click to expand...
Click to collapse
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.

Deleted
---------- Post added at 05:53 AM ---------- Previous post was at 05:34 AM ----------
gunigugu said:
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.
Click to expand...
Click to collapse
Sorry I thought it would have worked you should wait until the January security patch as all the other users said best of luck

Related

[Q] Software update using sideload and fastboot

Hi this is my first post and i hope its in the correct place and all
My nexus 7 (2013) is stuck in an android update circle where it constantly fails.
I tried to so the update to jss15q 4.3 using sideload where got so close but it said "signature verification failed" why could that be and can i stop it needing a verification?
I then tried to do it using fastboot and got so close again but got
:checking version-bootloader failed"
:device version-bootloader is "flo-03.05"
:Update requires "flo-03.14"
is there a way to correct either of them?
I am not rooted and i have downloaded the jss15q from developers google themselves (and i have debugging enabled)
Thanks for any help
Joe
Do you have the LTE version of the nexus or the WiFi version?
Guhrasoh said:
Do you have the LTE version of the nexus or the WiFi version?
Click to expand...
Click to collapse
I have the wifi only version.
joeyt90 said:
I have the wifi only version.
Click to expand...
Click to collapse
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Guhrasoh said:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Click to expand...
Click to collapse
What exactaly do i have to do on that page to be able to continue the methods i am trying to use? If i just unlock the bootloader willi be able to update the boot loader from version-bootloader "flo-03.05" to "flo-03.14" then download jss14q using fast boot or is it not that easy?
Thanks again
P.S I dont want to root yet and Is it possible to just update the bootloader without unlock bootloader or do you have to unlock before you can update?
Thanks
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
sfhub said:
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
Click to expand...
Click to collapse
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Thanks Joe
joeyt90 said:
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Click to expand...
Click to collapse
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
sfhub said:
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
Click to expand...
Click to collapse
PERFECT!!!
Thank you so much to everyone who helped me on here my device is now running 4.3 version jss15q and what a difference from jwr66n.
I used the Unlock bootloader and then use factory images and it worked a treat!!
Again i cannot thank you enough i called google and the people who suplied my nexus and they both said they didnt know!!
WAHOO!!!:good::good::good::laugh::laugh:

Your device is corrupt. It cant be trusted and may not work properly. FIXED!

*** NOTE: Please excuse my English.
*** WARNING: I'm not responsible if anything happens to your device, I'm just sharing my experience and what I did to fix my own phone. Proceed at your own RISK.
I bought my Nexus 6p 64gb and as soon as I took it out of the box, I went directly and followed the guide here. So i unlocked the bootloader, flashed TWRP as a custom recovery, flashed CM13 + OpenGapps.
I noticed that every time I boot my device I get this warning:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
and it does not seem to be a normal warning because when my OS boots up it shows me this
"Android system:
There’s an internal problem with your device. Contact your manufacturer for details"
Later on when I updated to the latest nightly image my camera crashes and doesn't function properly. I also already has an issue with Bluetooth and "Bluetooth share" crashing but that was unrelated. Anyways I was crippled in my day to day usage. Then I thought that I need to fix this asap because it might cause performance/security/hardware problems in the future.
So basically the fix is you should flash the latest bootloader image and radio image. Personally I wanted to start clean and make sure I have no corrupted files so here is what I did,
1. What i did is erase all boot, system, kernel & recovery files by typing the below command using fastboot just incase they were corrupted,
(Note: YOU DONT NEED TO DO THIS STEP, but i prefer starting clean incase i had some corrupted files. YOU WILL ALSO LOSE ENCRYPTION DOING THE FIRST STEP)
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Source: http://devs-lab.com/...i-nexus-6p.html
2. Then i flashed the latest factory images in this sequence using fastboot, which can be found here: https://developers.g...s/images#angler
(Note: 6.0.1 (MMB29M) was latest image at the time i did this. For people who are doing this for the first time, then you just need to download the image then extract the needed files from it)
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
Source: http://forum.xda-dev...operly-t3268407
3. From there i reflashed TWRP using fastboot, then flashed the latest beta SuperSU v2.62 at the time, and then CM13, then OpenGapps, then again reflashed SuperSU v2.62 just incase, lol. (Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When using TWRP before you've actually flashed SuperSU 2.50+, when you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.)
What got fixed ?
-FIXED, this won't show up anymore:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
-FIXED, this won't show up anymore:
Android system:
There’s an internal problem with your device. Contact your manufacturer for details.
-FIXED, Camera is working !
-NOT FIXED, "Bluetooth share" still crashes but I think its unrelated to this issue.
Hope this helps everyone as it helped me, thanks.
Sent from my Nexus 6P using Tapatalk
\*O / Thank you !!
Thanks, but better option? Don't reboot.
Sent from my Nexus 6P using Tapatalk
bob_mord_les said:
\*O / Thank you !!
Click to expand...
Click to collapse
Ur welcome [emoji1]
Sent from my Nexus 6P using Tapatalk
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Why are people trying to fix an non issue? To get rid of the message you need to relock the bootloader which is more of a risk if your rooted. Its a message that only appears for a few seconds when you reboot and you don't need to do anything to get past it.
There is no corruption and the phone is trusted by YOU as you unlocked it and nothing else cares. Where is the issue?
g_kos said:
Followed your guide, thanks, but the message "Your device is corrupt. It can’t betrusted and may not work properly." still appears during a CM boot.
The message "There’s an internal problem with your device. Contact your manufacturer for details" appears when I boot into recovery (TWRP)
The camera is working now.
Also, before I was able to flash CM-13 I had to do "WIPE >> Format Data" from TWRP, otherwise CM was exiting with error 7.
The following packages were used:
original 6.0.1 (MMB29P) factory image
BETA-SuperSU-v2.66-20160103015024.zip
cm-13.0-20160115-NIGHTLY-angler.zip
open_gapps-arm64-6.0-micro-20160115.zip
twrp-2.8.7.2-angler.img
I also noticed that when rebooting into factory image, the same warning message appears as well.
Any way to fix it or did I do something wrong?
Click to expand...
Click to collapse
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
XxMORPHEOUSxX said:
It's just telling you what you already know. You modified your system partition yourself so don't worry about it.
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Thanks. I read it in the original Heisenberg's unlock guide and was surprised when I read this post that it was possible to get rid of the warning message without locking the bootloader .
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
The message "There is an internal problem with your device..." seems to be related to the security patch version. This was my biggest issue, the message I get when booting the phone was annoying and I knew it was not a big deal, but having an internal problem warning was concerning, flashing the vendor image was the solution for me. But if you like to start clean then I have the steps written, but if you update then again you'll get the warning when booting up.
Sent from my Nexus 6P using Tapatalk
zooman31 said:
I'm new here in the forum's..I usually just read and carry on..the one think I'd like to say is..I don't understand why people got to say 'why you doing that for, ya don't need to' far as I know..this an educational site to learn..if he wants learn how to get rid of the warning..I don't see any problems in that whatsoever.
Click to expand...
Click to collapse
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during boot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
XxMORPHEOUSxX said:
I think what people are trying to say is the risk/reward for getting rid of the message is not worth it. Especially since its just a brief warning you only see during bouot. Just flashing twrp recovery will give the red message. SuperSU will help get rid of it which is why the OP was able to remedy it. It will not work for everyone though. Modifying the bootloader is the only sure fire way to snuff it out for good and you would be a fool to try and mess with your bootloader for something aesthetic. That's how most real bricks happen, is when a bootloader gets corrupted.
Click to expand...
Click to collapse
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
zooman31 said:
I assume that most people know the drill..you proceed to test at your own risk..the how to in the first post seemed to have worked after it was tested by the author.
Click to expand...
Click to collapse
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
XxMORPHEOUSxX said:
Basically just flash SuperSU last in whatever sequence, and as long as it boots,the red message will be gone. But change anything after and it will probably come back. I have nothing negative to say about this thread. I originally posted the nexus link just so people can rest assured that it is not an actual problem and a normal, albeit annoying, side effect of modifying the Nexus 6p. Happy Flashing
Click to expand...
Click to collapse
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
TechMillz93 said:
all i did was flash twrp and unlocked the bootloader and still got the red message. so all i have to do is flash supersu and root? to get rid of it?
Click to expand...
Click to collapse
Yes. The SuperSU beta 2.66 is what I use.
XxMORPHEOUSxX said:
Yes. The SuperSU beta 2.66 is what I use.
Click to expand...
Click to collapse
so i just reflashed the vendor and now im in bootloop ;(
TechMillz93 said:
so i just reflashed the vendor and now im in bootloop ;(
Click to expand...
Click to collapse
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
XxMORPHEOUSxX said:
Why did you flash vendor? Try clearing caches and then reboot. Let it sit for 10 min too while starting up.
Click to expand...
Click to collapse
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
TechMillz93 said:
im good now i just reflashed all the images im good.
but i have to feflash twrp now, what would u recommend
systemless or traditional ?
Click to expand...
Click to collapse
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
XxMORPHEOUSxX said:
Systemless unless you want to use xposed otherwise it doesn't matter. Systemless just makes it so you can use root apps like android pay. I use the 2.66 systemless. The instructions are a little all over the place on that thread. You no longer need a modified boot.IMG. the SuperSU zip patches whatever boot.IMG you have. So all you need to flash is the supersu2.66 for systemless or the traditional zip if going that route.
Click to expand...
Click to collapse
so i dont need gapps etc?
its all in there?

Latest Android N Update Bootlooped Me, Need ADB Sideload Help

Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
UserDemos said:
Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
Click to expand...
Click to collapse
Try this out.
1. Download TOOL ALL IN ONE
2. Download Drives
3. Check if device is recognize
4. Then UNLOCK to unlock bootloader
5. Verify if Bootloader is unlock
6. Flash a stock firmware.
If for some reason that application doesnt work do it manually
1. Install Minimal ADB and Fastboot
To get CMD working just click on the Minimal ADB and Fastboot application program
To flash a .img file place the files inside the Minimal ADB and Fastboot folder located in your program folder
2. Unlock Bootloader ( follow this guide)
3. Then follow the section [ How To Flash The Factory Images]
UserDemos said:
Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
Click to expand...
Click to collapse
Having the exact same problem this OTA has also bricked my phone.. It just shows boot animation forever. I've tried factory resetting, clearing cache and side-loading the OTA which succeeded but still didn't change anything. I didn't have OEM unlocking enabled so I can't even flash stock again I think I'm screwed
peaconut, I never selected the OEM unlock option whenever I had the N Preview. Just didn't expect to have it get totally messed up from an OTA.
Any additional thoughts based on my errors produced?
I had the bootloop issue as well. I fixed it by:
booting into recovery
wiping cache
wiping data
wiping cache
reboot
Booted into N just fine. Sucks I lost data, but was a quick fix.
Note: I never unlocked bootloader ever with phone. Was a bone stock 6 install with May security patch that was OTA updated that broke.
major97702 said:
I had the bootloop issue as well. I fixed it by:
booting into recovery
wiping cache
wiping data
wiping cache
reboot
Booted into N just fine. Sucks I lost data, but was a quick fix.
Note: I never unlocked bootloader ever with phone. Was a bone stock 6 install with May security patch that was OTA updated that broke.
Click to expand...
Click to collapse
Or, you can let it bootloop for about 15 mins, and it fixes itself...that's what mine did, scared the crap out of me at first, thank goodness I've learned patience....
You don't need it unlock. I was just explain the process to unbrick it in case you had a soft brick
---------- Post added at 10:05 PM ---------- Previous post was at 10:04 PM ----------
UserDemos said:
peaconut, I never selected the OEM unlock option whenever I had the N Preview. Just didn't expect to have it get totally messed up from an OTA.
Any additional thoughts based on my errors produced?
Click to expand...
Click to collapse
I'm in the same boat. Took the OTA and it bootlooped for at least an hour or 2. I did the adb sideload ota and still bootlooping. Tried factory reset and cache wipe and has been trying to boot for 10 mins without any luck. Hoping it just boots because I have no other ideas.
Imacellist said:
I'm in the same boat. Took the OTA and it bootlooped for at least an hour or 2. I did the adb sideload ota and still bootlooping. Tried factory reset and cache wipe and has been trying to boot for 10 mins without any luck. Hoping it just boots because I have no other ideas.
Click to expand...
Click to collapse
I'm in the exact same position as you! Let me know if anything changes
can anyone help me please? i did the ota update and i am stuck on the boot animation. i dont even have access to adb sideload since i didnt enable usb debugging and i also didnt enable oem unlocking
Ame123 said:
can anyone help me please? i did the ota update and i am stuck on the boot animation. i dont even have access to adb sideload since i didnt enable usb debugging and i also didnt enable oem unlocking
Click to expand...
Click to collapse
You didn't need to do that, and side load will still work. Just boot into recovery, and choose update from adb. You may just need to install drivers on your PC but it should work.
I was unable to resolve my issue, and got on chat with Google support. They are replacing it for me, so if you can't fix it try chatting with them.
Imacellist said:
You didn't need to do that, and side load will still work. Just boot into recovery, and choose update from adb. You may just need to install drivers on your PC but it should work.
I was unable to resolve my issue, and got on chat with Google support. They are replacing it for me, so if you can't fix it try chatting with them.
Click to expand...
Click to collapse
my nexus 6p is connecting via fast boot but its not connecting via adb can you help me? and where should i go to chat with google? can you give the link?
Imacellist said:
You didn't need to do that, and side load will still work. Just boot into recovery, and choose update from adb. You may just need to install drivers on your PC but it should work.
I was unable to resolve my issue, and got on chat with Google support. They are replacing it for me, so if you can't fix it try chatting with them.
Click to expand...
Click to collapse
Did you buy your phone through Google? I'm still having the issue however I bought my phone through Carphone Warehouse in the UK, gonna go down this weekend and see what they say
For Google chat just go to the play store on your PC and click help. As for adb, did you choose recovery, then update from adb? If so adb should be working fine. If not then it's a driver issue on your PC.
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
AlfexOmega said:
Did you buy your phone through Google? I'm still having the issue however I bought my phone through Carphone Warehouse in the UK, gonna go down this weekend and see what they say
Click to expand...
Click to collapse
Yes I bought it through Google. This has always provided the best customer service from my experience. Did you at least get Nexus protect? If so at least you can pay to replace it.
Mine got in a bootloop. I entered recovery mode and performed a reset/wipe and it worked.
Sent from my Nexus 6P using Tapatalk
mkouk said:
Mine got in a bootloop. I entered recovery mode and performed a reset/wipe and it worked.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
you are lucky mate i have wiped so many times but it still gets stuck on the boot animation forever. also adb isnt working the since i never connected it to the pc. now i dont have a phone :crying::crying::crying:
UserDemos said:
Hello all,
I got the latest update OTA and it appears to have bricked my phone. It looks like it is stuck on the boot screen and won't go further. I went into Recovery and tried to clear cache, but no dice. I also tried to factory reset and no dice either. Now, I'm stuck. I don't have an unlocked bootloader to flash factory images, nor did I ever enable OEM unlocking.
When sideloading the OTA from Google's site, the Android N OTAs don't work, so I tried Marshmallow. Those do work, however, I hit a roadblock and have no idea how to solve it. It starts installing the update when I get the following:
Warning: No file_contextsThis package is for "angler" devices; this is a " ".
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I fix this? Anyone?!
Click to expand...
Click to collapse
checkout my thread http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895
Ame123 said:
checkout my thread http://forum.xda-developers.com/nexus-6p/help/help-unbricking-nexus-6p-t3382895
Click to expand...
Click to collapse
You are a life-saver my friend! I'm going to post this thread in so many places for other people who are having the same issues as I did. You literally saved me a $500 headache. Amazing!
So here's an interesting change. So after reading the advice of others to flash the ota that you receive to revert from N, I was able to get M to boot normally. I unlocked the bootloader, and then tried updating back to the N beta. Didn't work. No problem, I'll just flash the factory image, still nope. Basically I can consistently get it to boot to M, but once I try to upgrade it to N, I get nothing. I've had it on N before, but moved off it due to stability. Any thoughts?
hey all, i was on developer preview 4 when this happened. however, I never flashed manually, always OTA. I cannot access recovery. any option besides "barcodes" results in a bootloop. I can fastboot and unlock, push an image, and relock, but it still bootloops. any thoughts?

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

Downgrade from 7.1.1 to anything lower with a locked bootloader?

In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
matistight said:
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
Click to expand...
Click to collapse
Hi... Did the bootloop came from nowhere or what were you doing when it happened?
What error do you get when you sideload the ota?
Tried formatting cache or factory reset?
Edit: You can't downgrade with a locked bootloader.
matistight said:
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
v12xke said:
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
Click to expand...
Click to collapse
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
matistight said:
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
Click to expand...
Click to collapse
If you erase or corrupt the bootloader then the phone is hard bricked (if it already isn't). I think you need an unlocked bootloader to do that anyways. Any flashing or erasing command in fastboot is going to need an unlocked bootloader. Even if you did somehow manage to delete the bootloader, without the phone being unlocked you can't flash a new one = hard brick.
If your phone is BL locked, you can't access Android, recovery doesn't help, you're mostly out of luck. Some people have said that using MSkips toolkit recovered their phones, but others had no such luck. There's a lot of people in the same boat as you. Others have tried calling Google about the issue despite their warranty status. Your phone is locked and a stock OTA took it out, from the sounds of it. Maybe they'll be willing to work with you. The worst they can do is say no, can't hurt to try. Good luck!
Why do you want to downgrade?
rchtk said:
Why do you want to downgrade?
Click to expand...
Click to collapse
Never really like 7.x and it has been the only OS that has bricked my phone without being rooted.
Unfortunately you can neither use an OTA to downgrade nor flash a factory image without BL unlocked.
And I'm not sure that would help either. Your device corrupted itself for a reason and that might be the flash failing (which the Nougat update exhibited, but Nougat isn't the root cause probably). You could rather wait for a higher OTA and hope.
Any recovery log to post?
How old is the phone? 1 year?

Categories

Resources