yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
No there is not. As long as you do it properly you'll be fine.

I need someone's help. I know that everyone is trying to find a way to fix the bootloop, but can someone post to me EXACTLY what they did to get to N and then what they tried to do to get back to MM that caused the device to bootloop?

I am currently trying to get mine to bootloop but I am unable to do so. It's actually kind of maddening!!!

---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------

In some rear cases like yours, it is possible for the EFS partition being corrupted to cause a booting issue. Definitely glad you had that handy. I am currently narrowing it down to 2 of the 3 things you touched on. Vendor, and or TWRP 3.0.2-1. However, not directly TWRP because of the fact that the 3.0.2-1 IS needed to flash N related software. What is troubling is the fact that a full factory reset using any MM factory image doesn't solve the partition issues that I think is occurring.

I've been privately testing with others and I have confirmed that the Bootloader and Radio are indeed being downgraded to whatever MM version is flashed. What appears to be damaged in the tests we did is the Vendor partition. Currently testing on my own device now that I am home and don't really need my phone. We will be reporting what we find.
[Nexus 6P Q&A, Help & Troubleshooting] Ulver:
I'm on bone stock nougat that I installed via the android beta program. So stock recovery locked bootloader. I figured I could just OEM unlock, unlock bootloader and flash MM factory image and be done. Correct me if I'm wrong.

Sent from my Huawei P9
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
All correct except for the part about OEM Unlock on N and unlocking the bootloader. Not because you can't, but because I don't know if you CAN. On N for me, the OEM Unlock is not available for me to modify. My bootloader is unlocked though.

I've been going back and forth from MTC20F to N and back to MTC20F without any issues. I have not been doing any TWRP restoring and have never bootlooped from just being on N and going back to MTC20F.
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
I was on AICP (6.0.1).

* Flashed TWRP 3.0.2-1

* Made a backup of AICP (uncompressed, all parts)

* Wipe cache/system/data

* Flashed tupac4u's stock Nougat ROM (both radio/bootloader and ROM zips)

* Booted and ran just fine for a couple days

* Wanted to go back to AICP.....

* Wipe cache/system/data

* Restored the backup of AICP (ALL parts, vendor included)

* I present to you, The Bootloop

Thats how I go to it.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Okay, your bootloop is probably because of vendor restore. Do you still have TWRP installed and have the backup of AICP?
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
His bootloop is because he backed up and restored with the -1 version of twrp, he can try everything like I did and it won't matter. Twrp need to get involved with this issue
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
And it would HAVE to use the -1 version because its required to flash Nougat ROMs.

ALTHOUGH, I guess I could have made the backup of AICP using -0, and saved it on my laptop. Then flashed -1, and used that to install Nougat. Now say, if I wanted to go back to Marshamllow, I would flash -0 again, and THEN restore the AICP backup (as it was made using -0).

Just a thought. Its too late for me to try that now, but maybe for future reference?
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Indeed I never went to n at all before this issue happened to me all I did was upgrade twrp did a backup and restore of latest pure Nexus.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
I'm exactly the same as you except I was on pure nexus rom.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
So in your case it was restoring with 3.0.2-1?

There are a few people that restored using 3.0.2-0 and caused bootloop because they restored the Vendor as well. I didn't noticed he typed 3.0.2-1.

I'm trying to replicate his issue to see if there's any way I can fix mine and report back.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
I never had an issue restoring everything when using -0 and I never upgraded to n.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
So yours is definitely 3.0.2-1 related. Do you still have the device?
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Nope it's at the huwei service center.
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
Android N can be I stalled on twrp 3.0.2-0, even the OTA. You just have to be decrypted to access twrp with Android N.

Moral of the story...avoid twrp 3.0.2-1 and flash on!

If you choose to leave nougat, I would flash stock MM before flashing a custom ROM to be safe...I personally haven't tested this but from what I have read, this should work. (If any information I have given is incorrect, please correct me so no one bricks their phone)
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
That sounds like the answer. I cant vouch for it as Im past the point of no return (as far as I can tell). Maybe TWRP doesnt know how to handle the difference in M and N partitions?
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Well I'm giving up trying. Sideloading OTAs, full flashing factory images all don't work.

And one of the clues to fixing it seems to involve a full nandroid backup of a previous rom, I don't have that since I always backup only boot, system and data partitions. EFS and vendor backups seem to be important as well.

So I'm just going to wait for Nougat Factory Image to be out as my last resort and if that doesn't work, off to service center.
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
Out of curiosity, if you flash MTC20F, then flash TWRP-0, then flash Nougat, then restore MTC20F backup, will things be any different? Not sure if anyone tried that yet or not. Just a random thought that popped into my head.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
For people that are still stuck:

Try using twrp 3.2.1-1 to wipe everything, boot directly to bootloader, fastboot all the necessary files, flash 3.2.1-0, boot to recovery, repair your partitions, wipe data/cache, then boot.

Don't try to boot at any point in between.
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
I know ETA's are frowned upon, but two questions:

1. When about is the Nougat Factory suppose to drop? Days? Weeks? Months?

2. How long does a phone typically take to go to the Huawei Service Center and back?
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Is this working for you? Or just a trial? I can try this later when I'm back home.
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
I'll give this a try right now....report back...

REPORT: So, thats a no-go. Now, I get a bootup message that says "Your device is corrupt. It can't be trusted and may not work properly." Has a red triangle instead of a yellow one.

Its not unrecoverable. Not sure how many of you have gotten that red triangle before. But I have to send my Nexus back to Google tomorrow as they have a hold on my account for the price of the replacement. Unless I can tinker before I mail it out, Im out of the guinea pig phase.
[Nexus 6P Q&A, Help & Troubleshooting] SpiritBreak3r:
I was able to get my device back up on MTC20C firmware by going back to TWRP 3.0.2 and restoring my first ever EFS backup and then flashing google's firmware.

I am pretty sure this mess was created by latest TWRP.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Well the new version of Android is supposed to have that seamless update ability. That is supposed to create a sportster partition to store the update during installation. I feel that has something to do with the vendor partition getting screed up
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Okay I have been trying all freaking night and I cannot get this thing to brick. It's actually frustrating me to all freaking hell!!!!!

I've been combing through post after post and tried different roms and still nothing. I've even shut the dang thing off during fastboot flashing and twrp restoration and a simple execution of the flash-all script fixes it.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Try running selinux fix, and chmod 775 on system files from a different device. That's practically what happened when I was porting and bricked.

Realistically, it's probably **** hardware with no long term memory.
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
14 days is what they told me.

---------- Post added at 05:42 AM ---------- Previous post was at 05:40 AM ----------

Backup purenexus rom and vendor on -1 and restore it
[Nexus 6P Q&A, Help & Troubleshooting] Andromjb:
Trust me, you do not want to soft brick. It's not solvable ATM. TWRP needs to release a fix or the factory images need to be released.. or a combination of the two.
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
For Christ's sakes someone update the OP and mention Don't Attempt to Restore any kind of backup via TWRP -0 or -1 , atop telling people to attempt to restore EFS and / or Vendor backups created in TWRP !

TWRP has not been updated for the 6P since the OTA Dropped ! Until TWRP updates based on the yet to be released factory image don't do any restoring or anything, if you going to role back full wipe repair the partitions and manually flash via command line or a tool kit that supports the version you wish to flash !
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Everyone's success has been through different methods. If you find any sure fire fails, let me know. That's why post three is reserved.

P.s. Chill the heck out, yo.

Note to everyone. If you find information that you feel necessary to all users, tag me with a descriptive post, otherwise, rm -f yourself.

I am running too many of my own tests to moderate this thread without the aforementioned.
[Nexus 6P Q&A, Help & Troubleshooting] psychemisha:
https://mega.nz/#F!CFgSgKKB ok here it is full backup with efs restore through twrp 3020 full wipe needed and mtc20f bootloader after you boot up flash what u wont

---------- Post added at 07:03 AM ---------- Previous post was at 07:00 AM ----------

Plz tell who succeeded and hit thanks
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Ok so did anyone tried this method yet? Especially the part where you fastboot format all partitions first before flashing the images. I wonder if the vendor partition can be fixed by a fastboot format?

I can only try this method later when I get home.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
You can't use format for the vendor partition. If I remember right it's only system, data, and cache that respond to fastboot format.
[Nexus 6P Q&A, Help & Troubleshooting] musashiken:
Ah yeah that makes sense, since TWRP can only repair those partitions as well..
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Yea, the other partitions appear to be hidden.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Yeah you can only flash Vendor sadly.

---------- Post added at 02:40 AM ---------- Previous post was at 02:39 AM ----------

Tried that.....Cayde 6, "Didn't work!"

Edit: I take that back!!!!! Brick!!! Testing time.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
First user here happy to brick. Did you try turning it off then on again?
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Yep it's a bootloop. I have a safety backup prior to 3.0.2-1 that I'll try in the morning. I'm making a backup of the bonked setup right now, so that I can go back to it if the restore works.

Plus I figured if I can't get it back from the dead, there's always Project Fi Support! [emoji3]
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
It was a joke. Glad you can test from the inside now!
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
I just feel it will be good information to put out there, to stop others from having suffering a similar fate that's all, the less people with the problem the better.

Frankly were dead out of luck until we get a proper factory image to see if that helps with the situation, advising people to stay where they are on N and those tempted to restore backups with TWRP builds 3.0.2-0 or -1.

Surefire fails so far seem to be so far :

1. with MM or N installed - Flashing the MM Vendor image with any version of TWRP to get the device to boot and then full wiping from this point and then attempting to sideload or flash the captured OTA's/Flashable Zips.

2. Full wipe from TWRP -0 or -1 and restoring a MM back up you already have.

3. Full wipe and manually flashing any image files from MM builds or N Builds including appropriate vendor images

4. Flashing someone else's EFS back up from a later date.

Smells like there is a change that's been made with this build of 7 and how things are partitioned and allocated to memory areas i'd guess this may have something to do with the seamless update feature due on the next devices and some of those changes have made their way into the 6Ps build.

Until the factory image for the device lands its all guess work, considering there are errors generated in the TWRP log when flashing from MM to N we really need to tell people to just not attempt to role back, Also i'd advise people not to make backups with TWRP 3.0.2-1 and attempt to restore those in either version -0 or -1 because it HAS already caused people to get this soft brick under both MM and N images.

I very much doubt we will find a solution until such time as the factory images and source goes online so those who maintain TWRP and such can work out exactly whats changed.
[Nexus 6P Q&A, Help & Troubleshooting] barturblits:
Can't you just look in the OTA file to see what changes are made to the partition layout or other partitions which are not in the mm factory images?
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
I guess we could, however if it was that simple i'm sure we'd have heard about it by now which might point to its an issue caused by a change that got screwed up on googles end.

Least that would explain why we have no factory image yet as it usually lands not long after the OTA goes out.

Has anyone attempted to flash/sideload this 1.1GB OTA image - https://android.googleapis.com/pack.../47ceb0f81a49e6866428f9996f8212aba8c29fbe.zip
[Nexus 6P Q&A, Help & Troubleshooting] psychemisha:
I shared link to mega with working back up and efs u can try it and it works i restored my device with it
[Nexus 6P Q&A, Help & Troubleshooting] rbouza1:
That's what got us in the trouble to begin with
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
so what i suggested gave you the brick you wanted? lol

Also i tried to repair the vendor image through adb and made no diff, mounted it in twrp then adb shell type in mount get the device block thats mounted for vendor and then do an e2fsck on that.
[Nexus 6P Q&A, Help & Troubleshooting] vestaviajag:
I agree with about 98% of all this, however keep in mind, I'm in constant bootloop because I was on newest TWRP and tried to flash a backup from the previous version of TWRP. Never had 7 (N) on my device.
[Nexus 6P Q&A, Help & Troubleshooting] barturblits:
Thanks! Downloaded the zip and I see now. Lots of partitions are being updated which are not present in the MM factory image. If you want to revert to mm you should downgrade those partitions as well. No complete original dd mm image up yet?
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
I've been saying that TWRP is likely the issue along with Nougat is likely setting up the partitions for seamless updates for about a week now. Though I updated fine through the beta program, I tried restoring a backup of Nougat through TWRP and then got the bootloop, the only thing that made my phone boot again is flashing factory images, then TWRP, then pure Nexus, the I restored original firmware backup from TWRP THEN I restored my EFS AND IT BOOTED PERFECTLY. So I guess it depends on what got wonky on what will work. I can't say NOT to restore EFS if nothing else works for someone since it worked for me.
[Nexus 6P Q&A, Help & Troubleshooting] Gytole:
You can fastboot erase though. I doubt it fixes anything but someone just brought me a phone with what sounded like this problem and no matter what I did with twrp, formatting/erasing manually then flashing manually, I'm talking TYPING all the commands got it to boot. It's worth a shot.

The reason I say do it manually is because when I run a flashall.bat via the Nexus image download it errors out on like 3 partitions but you won't notice it unless you're reading it. BUT when I flash the exact same images manually I don't get such errors, and no longer had a brick also.

Idk I could be cray.
[Nexus 6P Q&A, Help & Troubleshooting] downslayer:
I have been bricked for days now because I tried to restore a MM backup with vendor in TWRP, there is no way backwards to MM or forwards to N that I have been able to get to work aside from flashing a MM vendor over a N ROM which kills SIM support. Looks like it's time to sit back and wait for the official N image to drop with the right vendor.
[Nexus 6P Q&A, Help & Troubleshooting] hutzdani:
Sounds like a two fold issue now :

1. TWRP 3.0.2-1 *might* be causing issues with backups and restoring no matter what build your on MM or N

2. Changes to how files are flashed to storage and their partitions are quite different between MM and N, so until we have a factory image we can't really reverse engineer it and problem solve very well yet.

Safe bet is to either stay MM / stay N / wait soft bricked until factory images arrive
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
There was a guy reporting in another thread he has a 5x with the same issue and the factory image did NOT fix his brick.
[Nexus 6P Q&A, Help & Troubleshooting] barturblits:
Dont think a N factory image will help you downgrade to MM. But it probably will fix the upgrade to N. Only way to downgrade to MM is to downgrade all the upgraded partitions which are not all present in the MM factory image. Should extract those from a clean MM device.
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Okay so I have come to some conclusions and it's not good....

As you saw I was able to successfully brick my 6P....Lol...yeah...for the love of TECH!!!

I was able to fix it....but only with the backup I made of stock (no root) on TWRP 3.0.2-0, and one other way that I kind of think was a fluke or I just got lucky?! I am unable to fix the bootloop by flashing image files, NO MATTER which way I do it. I have done so many different variations of flashing that I'm pretty sure there is no combination I haven't done. I did run into the success of booting DP5 but only when using an MM Vendor. This is where that other way I fixed it by fluke came in. My dang OTG cable is now shot and I am unable to do anymore testing until my new one shows up.

So what I did for the DP5 booting with MM Vendor way, was two separate instances of methods. The first method was to get DP5 running, and then simply reboot to Bootloader and run the Flash-all script from MTC20F. The first time I did this it worked. The problem is, I was so excited that I stupidly didn't try to replicate it a second or third time again right after. I stupidly went to try a different method which was to get DP5 running again, reboot to TWRP 3.0.2-0 and full wipe and flash [MENTION=5284958]tupac4u[/MENTION] 's stock ROM that was based on MTC20F as well as his flashable bootloader and radio zip. That worked! So I wen't back to the original method but that is when my OTG took a huge dump on me! So I am unable to continue testing until I get my new one I ordered.

I had my backup on my desktop so I was able to fix my device by restoring with 3.0.2-0. I honestly don't know if this is going to work for anyone because so many people were able to fix theirs' but others couldn't using the same method they did.
[Nexus 6P Q&A, Help & Troubleshooting] Andromjb:
Pretty vague on how you got DP5 "running". Did you mean ran the MTC20F flash-all script via bootloader after a manual flash of DP5? Need to be more descriptive please.

I've flashed some 7.0 ROM's which actually boot to the Android animation then bootloop from there. Something is going on with the vendor partition.

I've tried just about everything, nothing works.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
And all of this still has me pointing the finger (you choose which finger) at TWRP. I firmly believe it's the biggest culprit at this point. Once it's updated, I think all will reveal itself.
[Nexus 6P Q&A, Help & Troubleshooting] Andromjb:
TWRP isn't entirely at fault. It's both the new file system Nougat uses (most likely for seamless updates feature) and TWRP not using the new partitions correctly. Once the factory images come out, I believe it will be resolved eventually. In the meantime, we have a lot of people with useless phones.

Luckily, I have my OnePlus 3 has a backup. One thing is for sure, I won't be trusting TWRP restores for quite some time now.
[Nexus 6P Q&A, Help & Troubleshooting] Tomv5314:
Has anyone had luck with Huawei? My phone just landed in Texas at the service center. When I talked to them the rep said if your phone has been modified in any way "(They have ways of finding out)"they will call you and tell you then send phone back unfixed. I factory reset from the stock recovery and relocked my phone but I am nervous. Has anyone gotten their phone fixed or replaced from Huawei?
[Nexus 6P Q&A, Help & Troubleshooting] defcondev:
I wonder how many 6p's will be headed to Huawei in the coming week or two, mine included. haha
[Nexus 6P Q&A, Help & Troubleshooting] Andromjb:
If the device is soft bricked and not hard bricked and you sent it back with a factory image and a locked bootloader there is "techincally" no way they can refuse warranty service. You haven't broken any warranty guidelines at that point.

If they are really that shady of a company and refuse to service their own product.. Then I would definitely contact Google immediately and inform them about it as they will handle it properly. Just make sure you keep records of all information.
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
Just curious. Has anyone started on MM, upgraded to N, run it, and downgraded back to (any) MM ROM, and still retained FULL functionality? (camera, network, etc....) All while using ONLY TWRP 3.0.2-0 (NOT -1)
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
The fact that it's stock and locked with the qfuse enabled they really have no way of telling. Mine has been in they center almost 3 days now and no call yet.
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
I sent mine back to Huawei on Friday. They received on Monday. UPS tried to deliver it today but unfortunately I was not here. Will get it tomorrow. Pretty fast turn around....will keep y'all posted
[Nexus 6P Q&A, Help & Troubleshooting] joeyddr:
Was it the same issue as everyone here?
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Added to the top of 2nd post. Attempted myself. I am no longer bootlooping, but stuck at the google logo! positive growth!
[Nexus 6P Q&A, Help & Troubleshooting] bogomil4e:
Thanks! If we can be of any other assistance please do tell!

More info will be provided soon as well as a patched version for the affected devices!

Please also clarify that the ADB commands can be executed while phone is booted in TWRP and connected to the PC! :D
[Nexus 6P Q&A, Help & Troubleshooting] godzulu:
Yep, tried everything to get it to boot. My posts with my issue s are from last the stay until Thursday. Then I sent it in.
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
My 6P was bricked in the process of porting MIUI 8 to our device. I just ran the two lines and re-applied the stock mtc20f images...

My old device LIVES!
[Nexus 6P Q&A, Help & Troubleshooting] Andromjb:
So basically, if you don't have an EFS backup or your backup of EFS was done on the 3.0.2-1 TWRP... you're boned? Awesome.