yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] sixgunmojo:
Well I don't know what steps you've taken to resolve the problem but here's my 2 cents. Assuming you can get back into TWRP*:

1) Wipe > Advanced Wipe > wipe everything that is not internal storage

2) Restore nandroid. Unless you also included vendor image in your nandroid you will also have to flash the vendor image again (pretty sure, may be wrong, don't think it would hurt).

If this fails, try it again, Ive seen things fail the first time and work the second. If it fails the second time you may have to come to grips with the fact that you probably are going to be doing a clean flash, hopefully without having to wipe internal data. If THAT fails get back to us with the steps you have taken.

*If you can't get into TWRP someone more knowledgeable than I will have to chime in.
[Nexus 6P Android Development] joeyddr:
I have done everything, not caring about saving data this phone wont boot from a stock factory image using flashall.bat
[Nexus 6P Android Development] kyzn:
I don't even disable them anymore...
[Nexus 6P Android Development] dbroer91884:
This is precisely why I haven't gone back. I wonder though, and people who have the boot loop issue can come in, if I just downloaded the latest mm image from Google, flashed that through fastboot, then put twrp on and then flash PN would that help avoid the boot loop issue?
[Nexus 6P Android Development] sixgunmojo:
Deleted for being wrong. Really, really wrong.
[Nexus 6P Android Development] kantjer:
A clean flash will wipe all OMS layer files.

With RRO the layer files were stored in the vendor portion, that's not wiped when doing a clean install. With OMS everything is stored in the data portion, that's cleaned when doing a clean install.

Sent from my Nexus 6P
[Nexus 6P Android Development] Gizmoe:
I flashed the mtc20f image to roll back from N without issue. Everything was completely stock though. Once back on MM you could flash twrp and restore backup.
[Nexus 6P Android Development] joeyddr:
did all that also.
[Nexus 6P Android Development] hinxnz:
I tested out an N ROM, afterwards I reverted back to PN with no issues.

When I reverted back I booted into bootloader, flashed bootloader 3.54, rebooted bootloader, flashed radio 3.62, rebooted into twrp 3.0.2-1 and then restored my nandroid which included system, data and vendor, then rebooted into Android.

By the way N is great :) I hope Nate re-enables the night mode with PN's build, the system ui tuner navbar options are great too.
[Nexus 6P Android Development] Shaelz:
Why'd ya switch back?

​
[Nexus 6P Android Development] hinxnz:
To test again I guess because people posting here about how they can't return to PN and wanted to see for myself. I think it's probably just user error though why they can't. I may probably just wait till Nate releases PN build of N before jumping again.
[Nexus 6P Android Development] Juzman:
I have tried that, tried completely flashing stock MTC20F image.

The ONLY way I can get the phone to boot is with sideloading N OTA, then flashing MTC20F vendor. However that renders the phone an iPod, since I have no sim / camera.
[Nexus 6P Android Development] hinxnz:
You would need to flash the vendor image for N.

Isn't OTA for stock setup only..

And are you flashing bootloader 3.54 when returning to PN..

I don't want to get to engrossed in too much OT :angel:
[Nexus 6P Android Development] Juzman:
I was on PN > Flashed stock MTC20F > Flashed OTA to N. Booted.

Went to go back to PN with nandroid, flashed MTC20F boot/radio/vendor + nandroid.

Boot loop issue.

Now even trying to wipe and flash stock images > Boot loop.
[Nexus 6P Android Development] Mesmurized:
Did you flash nandroid ...then... boot/radio/vendor?
[Nexus 6P Android Development] sixgunmojo:
Other than trying to flash back to stock again and double checking every step on the way, I got nuthin. Not being the flashaholic I once was the only issue I had (on this phone, knock on wood) was fixed with a re-flash of the ROM.
[Nexus 6P Android Development] Juzman:
Nope. I am in the middle of retrying again.

Erased all partitions, manually flashed bootloader/radio/boot/cache/recovery/system/vendor

Flashed twrp-3.0.2-0 and repaired partitions

Now going to restore nandroid, then flash-all the stock image and see if it boots.
[Nexus 6P Android Development] joeyddr:
please let me know
[Nexus 6P Android Development] Juzman:
It was a no-go. :(
[Nexus 6P Android Development] joeyddr:
do you think our efs is hosed somehow?
[Nexus 6P Android Development] Citizen_Snips:
May I ask why you're restoring a nandroid and then flashing stock images via fastboot? I had issues at first swapping back and fourth, but I've gone between PN and N like 5 times now.

All I do is boot to TWRP. Use the updated TWRP, 3.0.2-1. Wipe > Factory Reset. For good measure I will also use Advanced Wipe > System, Data, Cache & Dalvik. Reboot to bootloader;

fastboot devices (to ensure it's connected properly)

fastboot flash bootloader bootloader-angler-angler-03.54.img

(reboot to bootloader)

fastboot flash radio radio-angler-angler-03.61.img

fastboot flash vendor vendor.img

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

Now boot up and you should be on stock 6.0.1. You can reboot to bootloader again and;

fastboot flash recovery twrp-3.0.2-1-angler.img

Reboot to recovery and flash PN, Gapps and if you want a custom kernel or any other mods you use. You'll already be on the correct vendor so don't try flashing any. Like I said I've used this method 5 times already without a single hiccup, not sure why it wouldn't work for you.
[Nexus 6P Android Development] Juzman:
People over in this thread (http://xdaforums.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709) said when they restored nandroid, got boot-loop again, but then reflashed the stock image again over the nandroid, and it booted.
[Nexus 6P Android Development] Citizen_Snips:
Try without doing that and just follow the steps I outlined above. Let me know how it goes. Make sure the hash on your file matches what's on the factory image page by Google. Also make sure you're using the Factory Images page and not the Factory OTA page. They look exactly the same and you'll have a bad time trying to flash an OTA over nothing.

Edit: For reference, here's the OTA page;

https://developers.google.com/android/nexus/ota

Here's the Factory Images page;

https://developers.google.com/android/nexus/images

See how similar they are? The only reason I can think of as to why you're boot looping after wiping everything and flashing factory images is you're accidentally using the OTA file.
[Nexus 6P Android Development] joeyddr:
I actually did both. The only thing I have not tried is relocking the device which I won't do till I send back to huewi
[Nexus 6P Android Development] Juzman:
1. Downloaded angler-mtc20f-factory-d62de11e.tgz from https://developers.google.com/android/nexus/images

2. Confirmed SHA256 - SHA256(angler-mtc20f-factory-d62de11e.tgz)= 7ece3483ded6d12a1a4c12b447932a5c8ac55131e177c3a42e5f015a0dfc8abe

3. I did the following:

Booted TWRP > Wipe > Factory Reset, wiped system, data, cache and dalvik

fastboot flash bootloader bootloader-angler-angler-03.54.img

fastboot reboot-bootloader

fastboot flash radio radio-angler-angler-03.61.img

fastboot reboot-bootloader

fastboot flash vendor vendor.img

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

Selected "Start" from fastboot

Goes from "You're device software can't be checked for corruption. Please Lock Bootloader" > Google logo > "You're device software can't be checked for corruption. Please Lock Bootloader" > Google logo > repeat.
[Nexus 6P Android Development] Shockz:
That's not true. Flashall will completely wipe the device and flash all of the IMG files in the zip.
[Nexus 6P Android Development] Citizen_Snips:
Okay, it looks like from previous steps you mentioned you already nuked the data on your phone. I know you confirmed the hash, but just to rule anything out delete the file and download it again if possible. Follow those steps again except at the end reboot to recovery. When you get to stock recovery and see the Android on his back with the red triangle & exclamation mark, while holding power, press and release volume up to boot to stock recovery menu. If your 6P is in a case, take it out since a lot of them will press both volume buttons and you'll be stuck thinking your recovery is bad. From stock recovery perform a cache wipe and then a factory reset. Volume keys to select, power to confirm. Then try to boot.

Edit: backup your nandroid, this will wipe all user data from internal storage. [MENTION=4049833]Juzman[/MENTION] tagged so you see it.
[Nexus 6P Android Development] Juzman:
Nothing seems to work to get it to boot. Has to be something with a bad /vendor.

I went into recovery and flashed a 7 ROM > not boot, soon as I flashed MTC20F vendor it booted, but got error and no signal etc
[Nexus 6P Android Development] sixgunmojo:
Yeah, my mistake. I missed the final fastboot -w image-angler-xx.zip line. :(

In my defense, however, I'm a linux guy so I look at .bat files in a half-assed kinda way. :rolleyes:
[Nexus 6P Android Development] mswal2846:
I got to this exact place. I decided to restore EFS since I didn't think it could hurt and it worked ... Sim back. Back on V6. 0 Stock.
[Nexus 6P Android Development] Juzman:
I tried, but when restoring the EFS in TWRP I get:

E:Unable to find file system (first period).

E:Unknown restore method for '/efs2'
[Nexus 6P Android Development] Citizen_Snips:
Did you flash 7.0 OTA file over PN? You should never flash an OTA over a custom ROM. If that's the case, I'm not sure how to help. It could have corrupted one of your partitions. I'm not sure how to fix that. You said repairing all of them in TWRP did nothing, so you'd need someone with more knowledge on that than me. :/

So I guess for anyone else who decides to try N and go back to PN:MM; Flash stock 6.0.1 factory images. Take the OTA via About Phone. Use N. Decide you want PN again. Reboot bootloader and flash TWRP 3.0.2-1. Factory reset slider & advanced wipe for system, data, cache & dalvik. Reboot bootloader. Fastboot BL & radio from 6.01 factory image. Reboot bootloader. Fastboot flash the rest of the img files EXCEPT userdata & cache(we took care of fresh data partition from TWRP in the last step). Boot. You're stock 6.0.1. Enable debugging and reboot to BL. Flash TWRP 3.0.2-1 and flash PN again.

Like I said I had no issues going back and forth between MM & N. Very odd. I also see Heisenberg updated his guide stating to not go back to MM after N for bricks. That's odd. I haven't had any issues so I have no clue. Sorry man, tried to help best I could. Hopefully you can get it sorted out
[Nexus 6P Android Development] Juzman:
Nope, I did a nandroid backup, then complete restore to MTC20F, then sideloaded the 7 OTA.
[Nexus 6P Android Development] joeyddr:
something with vendor/efs is shot man..... not sure but going to try a replacement from huwei or i will just have to eat 500 on a new phone... this sucks

as an fyi..the vendor partition for N is 2 megs bigger than the vendor partition for MM. i have gone as far as to restore a N image copy contents to the "sdcard" folder and and then flashed the 20F vendor image copy the contents off that to another folder and copied back but wont boot... if i flash the N vendor then go in with adb shell and rm -rf all the contents and try to copy the MM folders/files back to the partition i get a boot hang. but i have booted up with flashing the N vendor and copying/overwriting the /firmware /lib /lib64 folder over and if you copy the build.prop from N to MM vendor partition you even get rid of the warning you get on boot that the image is corrupt .. etc. but when you try to copy the bin folder over you are 2 megs shy of copying/overwriting. I'm pretty exhausted at this point in trying to give my android N pod LTE.
[Nexus 6P Android Development] kyzn:
Hey guys, what's the baseband and bootloader number on the N DP5? I remember somebody mentioning that the official N baseband doesn't work on MM but I have 3.72...My bootloader version says 3.58.

And I'm not experiencing issues with signal.

Never mind. Found it. Huh...I guess the debloated N ROM came with the N DP5 baseband and BL?
[Nexus 6P Android Development] RED ZMAN:
http://www.androidauthority.com/android-7-0-nougat-source-code-released-713056/

Source released?
[Nexus 6P Android Development] KrazyAttack:
Hype.
[Nexus 6P Android Development] StormCell:
Hi, if I'm running MM and PN/Ninja, how do I switch to Android N and PN/Ninja? Many thanks for an understandable answer. :)
[Nexus 6P Android Development] chikimonke:
There is no N version of PN yet, so for now you wait.
[Nexus 6P Android Development] StormCell:
Hmmm...ok. Thanks. So, how would I go from current set up to rooted stock N with Ninja, as that is made for N? Thanks.
[Nexus 6P Android Development] DJBhardwaj:
IMO, I would wait for the factory images to show up on Google's website. If not, you can either install stock MM or N DP5, and upgrade through OTA. And then, you can install TWRP, Root it, and finally flash Ninja Kernel.
[Nexus 6P Android Development] StormCell:
Ok, so I'm expecting the Images for 6P to be live tomorrow, Monday. After then I'm guessing Beans will create PN from that and release it in the next day or so, and I'll just have to do a clean Flash? Or is that too simplistic?
[Nexus 6P Android Development] nathanchance:
I will say with 100% certainty PureNexus 7.0 will not be released within the next few days. Angler and Shamu blobs have to be done and there are still some other issues to be worked on. You are always free to build yourself from source but it will probably be at minimum a week or so for a very bare PN to be out (my estimate and no promises).

However, yes, you would just need to grab the N bootloader and radio then clean flash.
[Nexus 6P Android Development] StormCell:
Hey Nate!

Thanks for the reply. No chance of me building anything. I will patiently wait for your awesomeness to be be availed. I am a contributor to your cause. Keep up the great work. Thanks.
[Nexus 6P Android Development] blueren:
These blobs are relating to proprietary drivers right? If I remember, all devs had a tough time figuring this part out when M was released.
[Nexus 6P Android Development] smoothjeff:
Thanks night mode worked! If anyone tries this app, you're supposed to reset the notification pulldown quick tiles to default, but what got the app to work for me was playing with both the "on" and "turn on automatically" toggles until it took effect the first time.
[Nexus 6P Android Development] scoot0073:
Jus keep n mind if u do go to N ATM you can not return to MM so once u move to N it's best u stay there ..jus a heads up..
[Nexus 6P Android Development] Toutatis_:
I switched between MM and N a few times without any issue and many other people did so as well..
[Nexus 6P Android Development] scoot0073:
U and a few others have but there's way more peeps that have not and are still out of a phone until a fix or method is available. Most of them only hope is waiting for the Factory Image to be posted and even then it's not a sure thing..

Even Heisenberg has updated his guide advising peeps if you go to N u can't return to MM ATM..

Obviously they can do what they want I jus want to make sure that they are aware of the known issue..

Luckily ive had nothing but a positive experience with N and I have no reason to try n return to MM.. I'm just gonna rock it until PN 7.0 is released..but again each their own.
[Nexus 6P Android Development] Toutatis_:
Yes, I know some people got into trouble when trying to roll back to Marshmallow. However, I had to point out that your statement was not entirely true (you basically said "there's no turning back, once you install Nougat, you cannot roll back to Marshmallow") since some users, including myself, sucessfully did so.
[Nexus 6P Android Development] scoot0073:
I'll jus be glad when this is all sorted out and hope that all the peeps that are out of a phone can gain it back.

It's gotta be a user error somewhere that's causing this but people have tried different methods to revert back and find themselves in this boot loop thing.

And some have tried other users known method to go back and still no luck on some..

I believe I could revert back also but I don't want to gamble $500 to try it.

Lol...

I jus hate seeing the people go through this
[Nexus 6P Android Development] forty9er49221:
To get back to MM from N, I did the following:

Instead of flashing the latest 6.0.1 (MTC20F) (as this one was giving me errors), I went to the previous stock image (6.0.1 (MTC19X)). It worked fine! I then flashed Pure Nexus.

https://dl.google.com/dl/android/aos...y-83a34810.tgz

Try that for those having the problem.
[Nexus 6P Android Development] SyCoREAPER:
When I had my LG G3 I was just like you guys, flashing away. No longer have the patience for it because of issues like above. I'm happy to wait until beans releases Pure Nexus N
[Nexus 6P Android Development] scoot0073:
Could u post this here in hopes that it will help others with your method

Thank

http://xdaforums.com/showthread.php?t=3445709
[Nexus 6P Android Development] hutzdani:
I can't see why so many people are having issues with going back to MM i have done it twice already.

Backup your INTSD because your GOING to loose your data !

Make a full wipe and Reflash the MM bootloader / Radio and Vendor image, then flash your ROM that matches the radio / vendor you flashed and let it make a full normal boot, then boot into adb and flash the rest SU yadda yadda

Worked everytime without any issues here
[Nexus 6P Android Development] :
Antivirus can be scanning the messages! If you have an anti-virus app or security type app installed, uninstall it or go to the app settings then disable it and see if that helps.

Google Services by default has an app installed called 'hangouts' that is known to cause messaging issues. Even if you don't use the app, it can still cause issues related to the messaging services such as duplicate messages. To solve this issue goto app manager and clear the cache / data from the "hangouts" app and restart the mobile by turning it off and back on again.

If you are using any third party text messaging app try using the default one instead…!

However this issue could be on your friends mobile and not yours, get them to go over the above solutions also.
[Nexus 6P Android Development] kurt_cocaine:
Please let me know what fixed things for you. Thanks.
[Nexus 6P Android Development] joeyddr:
I have the issue and never went to N, all i did was upgrade to the latest twrp made a backup and restored and boom I got the bootloop, flashing N with 20f vendor is the only way i could get the phone to boot in android pod mode....
[Nexus 6P Android Development] RED ZMAN:
Well, a clean flash seems to have given me Android Auto back, my dear sweet Android Auto. Clean, quick to connect, beautiful Android Auto.

Mmmm, developer mode...
[Nexus 6P Android Development] hutzdani:
Then something is up with TWRP or your backup, I guess your using this build (http://xdaforums.com/nexus-6p/orig-development/recovery-twrp-2-8-7-0-touch-recovery-t3234976)

As a rule if your going to jump version rather than incremental updates Always clean flash and always start with a fresh flash of the OS your going to with a factory image, this way you can negate any issues with whatever rom you might want to flash and any complications with backed up images with encryption and or modified /system partitions.

its far more simple to start from a factory image and get TWRP and ROOT setup and flash ROMS form that point, I think some people get complacent when they have been flashing for a few years but even several ROM builders say if your jumping build numbers 5.X -> 6.X e.c.t that you should always start a fresh.

With N being quite new and not all issues have reared their head and been fixed and submitted you have to be extra cautious, until the Source has been dug through no one can assume that its just flash from TWRP and go.

Good hear your getting somewhere tho ! hopefully you will get booted, however if your spending a lot of time just flash back to a clean slate of 6.0.1 and start again.
[Nexus 6P Android Development] joeyddr:
I was on 3.0.0-1 upgraded to the latest made a backup and restored it... never went to N. Formatting all partitions via flashboot and flashing the stock image does not fix the issue.
[Nexus 6P Android Development] gonzlobo:
lol
[Nexus 6P Android Development] Jammol:
It is user error. A lot of them were posting that they were restoring PN straight onto N.?

---------- Post added at 10:48 AM ---------- Previous post was at 10:39 AM ----------

What issue is occurring? Just curious.
[Nexus 6P Android Development] beanboy07:
Complete shot in the dark here and may not be ROM related but is anyone else on TMobile have connectivity issues? The last 2 newest radios is when this started for me and doesn't happen on an older radio version 3.51? When streaming any video , music with an app using data, the radio just shuts itself off, reboot brings back 4g but then does it again after 10-15 minutes some times longer sometimes sooner. A few months ago I read a post from a couple different users experiencing the same activity but never saw what if any the fix was. I suppose I could go back to the older radio but I was just curious if anyone here knew what's up with this.

Current radio is 3.72, newest bootloader, clean installs etc etc. Doesn't matter the setup of ROM or app used, the only thing that doesn't cause the issue is using an older radio. Got a full log of everything before and after if anyone is willing.
[Nexus 6P Android Development] hutzdani:
What build are you trying to flash back to ?

People have had issues with the 20F build regardless of being at N or MM, really if your having issues you should not be trying to recover with older data that may or may not be compatible with where your trying to get to.

Are you trying to keep TWRP on your stock image flash ? or settling with the stock recovery, have you attempted this with a tool like NRT that will give you an error log or anything ?

In an ideal world you should be flashing the earliest build you can so in your case : 6.0.0 (MDA89D) and build up from there, if your boot looping it could be that your not waiting long enough for it to finish its encryption or something you have flashed is not a complete do your MD5 hashes match up ?

Also as stupid as this might sound the build you where on for the backup you made does that image throw any errors when trying to flash with TWRP does it do anything different ? The thing is everyone does things differently and has this issue but no one seems to have a clue whats going on here or written expressly their steps and order exactly so people can double check I.E

Full wipe

Flashed :

Bootloader & radio

rebooted bootloader

flashed vendor

Reboot bootloader

flashed system

flashed data

and so on

then throwing in this modified bootloader this recovery this SU then not remembering if their image was encrypted or not yadda yadda

people are telling us they attempted to flash back backups trying to get absolutely everything back then there is this vauge part of trying whatever they think might help / work with no logical steps or errors to go by its very hard to help other than tell you what you already know.

its frustrating for the end user i know
[Nexus 6P Android Development] chrisexv6:
Im surprised it took this long for someone to post that reply, but I sure LOLed when I saw that post.
[Nexus 6P Android Development] Jrmiller:
Mine something similar. Radio kind of reboots and lte comes back with in 10-15 seconds