Downgrading from Nougat to Marshmallow - Nexus 6P Q&A, Help & Troubleshooting

I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk

Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !

hutzdani said:
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
Click to expand...
Click to collapse
Yeah, so many stories of expensive paperweights when trying the downgrade. I suspect they're having some major issues with the 6p factory image, since the 5x has been posted for nearly two weeks. I've got mine working pretty well, with really good battery and ARISE sound actually working system-wide. I suspect we may see the factory image when this month's security update is rolled out - at least I hope so, given we're already into September.

That's what I figured. Looks like I'm staying on N. Thanks!
Sent from my Nexus 6P using Tapatalk

@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back 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
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.

Great thanks! I'll give it a go
Sent from my Nexus 6P using Tapatalk

RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back 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
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Works fine, thanks!

RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back 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
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?

srt4mn said:
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
Click to expand...
Click to collapse
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.

RoyJ said:
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
Click to expand...
Click to collapse
Thanks! I'll give it a shot here after I figure out this bootloader usb data cable issue.
EDIT:
Got back to 6.0.1 after following your instructions, thanks again!!

Worked like a charm. Thanks @RoyJ!

No problem, glad it worked for everyone.

I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.

bmwkeith said:
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
Click to expand...
Click to collapse
So your in PN MM with new nougat modem and bootloader ?

dutchy716 said:
I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey so I actually bricked my first Nexus 6p doing this but I have been fine with my replacement. The Key is to update your twrp to 3.0.2-2 (make sure you do this). I then from Android 7 did a full backup in Twrp and then in the bootloader flashed the MTC20F factory image and it rebooted just fine. I guess in Twrp 3.0.2-1 there is an efs partition problem that is causing the bricks; my old bricked nexus 6p was on 3.0.2-1. So just please make sure you flash 3.0.2-2 twrp

ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
Yes, and everything is working fine.

ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.

rndll said:
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
Click to expand...
Click to collapse
Yes. Already try it and everything is working fine.

What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.

NedbuR said:
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
Click to expand...
Click to collapse
Did you sideload 7.0 or upgrade from the beta program?
Sent from my Nexus 6P using Tapatalk

Related

[Q] [Solved] Factory Rooted

Hello all, I just had a quick questions for those of you who have unlocked / rooted your Nexus 10 and installed the factory image:
1. Did you all use the toolkit in the Android Dev Forum for Nexus 10 to achieve the root?
2. Once you flashed a custom recovery was installing the factory image as simple as downloading the zip from google (https://developers.google.com/android/nexus/images#mantaray) and then flashing it via recovery and rebooting AFTER you unlock the bootloader etc?
I was under the impression that once you Unlock / Root, you have no OS on your device, is this correct? Or can I root and Android 4.2.1 will still be there, albeit completely wiped of my user data from before.
Thanks for the help, don't wanna get started on this until I know what I'm doing! Don't want a $400 makeshift frisbee disk
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Fromako said:
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Click to expand...
Click to collapse
Thanks! I think I will go through with using the toolkit tonight and see if I can get it to boot into the factory image. Glad that it sticks around (hopefully) if not I can just flash 4.2 from google via TWRP...thats what I needed to know
So really all I need to root is this:
1. fastboot oem unlock
2. fastboot flash recovery [recovery.img]
3. Boot into recovery
4. Flash SuperSU.zip? --- Where can I download SuperSU.zip ?
5. Wipe Cache / Factory Reset via TWRP wipe data
6. Reboot
7. Profit?
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
TheEmpyre said:
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
Click to expand...
Click to collapse
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Fromako said:
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Click to expand...
Click to collapse
I just finished successfully rooting...got hung up after I unlocked the bootloader and flashing TWRP but all I had to do was Format the Data and wipe cache after to successfully boot into the OS. After that I was able to load SuperSU to my SDcard and then flashed it, reboot, did root-checker and I'm all good! Thought I was screwed there for a sec cuz I didn't pre-load SuperSU or the factory image in-case it hit the fan and I wasn't able to mount my SDcard storage via TWRP...Figured it all out though thanks for the help! Glad I was able to do it without the tool-kit!

I think my system portion is corrupt... Any chance of saving it?

I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good

Nexus 6p with Android 7.0 in bootloop cannot access recovery

Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?
fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.
I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?
Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..
I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.
Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..
So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.

Please help, possible bricked phone???

Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.
RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ
Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.

[How-To] Restore OOS from Oreo 8.1 | Restore factory encryption | Re-lock bootloader

You need to do this if you've flashed an Oreo 8.1 ROM and find that you can't get back to OOS because...
The ROM can't read /data so it hangs on the boot animation or reboots to recovery, even on a clean flash.
TWRP won't recognize your PIN/password or "default_password".
You've tried re-formatting /data from TWRP several times and it doesn't solve your problem.
Here is how to get back to 100% stock and/or restore factory encryption, which is different than Oreo 8.1 encryption:
1. Back up /sdcard to your PC as it will be erased with all of your files, pictures, music, etc.
2. Flash the stock recovery from bootloader.
Code:
fastboot flash recovery [I]stock_recovery.img[/I]
Latest OOS official stock recovery
Latest OOS beta stock recovery
3. Restore system setting in recovery.
This step is necessary to restore factory formatting and encryption of /data.
If a password/PIN is set, click “I forgot my password.”
Boot into stock recovery. Once there, go to Wipe data and cache > Reset system setting and Erase everything(Music, pics, etc.).
Note: If you don't do the "Erase everything..." option, factory encryption will not be reset.
4. Boot TWRP from bootloader.
You could flash TWRP and reboot to recovery, but TWRP will get overwritten with the stock recovery when OOS boots anyway. It's faster just to boot TWRP from a command prompt. Use the command:
Code:
fastboot boot [I]twrp-recovery.img[/I]
I recommend using using:
[RECOVERY][dumpling] TWRP 3.2.1-0 for Oreo (8.0 and 8.1) by codeworkx
5. While in TWRP, move “OOS...ROM.zip” to the SD card.
In Windows File Explorer, copy OOS...ROM.zip to the device.
Alternately, you may use the following ADB command from a command prompt
Code:
adb push [I]OOS...ROM.zip[/I] /sdcard/
Since OOS is a very large file (1.6GB), this will take 5-10 minutes.
Latest OOS signed flashable zip
Latest OOS beta (Oreo) flashable zip
6. Flash OOS...ROM.zip from TWRP.
7. Reboot system.
Your device will be formatted, encrypted and loaded with the stock recovery and ROM as it came from the factory. You may need to find the OOS...ROM.zip you pushed to /sdcard and delete it from emulated storage (/storage/emulated) if you don't see it at /sdcard after booting the ROM.
8. Optional: To re-lock your your bootloader, follow these additional steps:
This can only be done from a factory-supplied OOS ROM (including Oreo) with no modifications or the phone will not boot!
Enable USB debugging under Developer options.
Reboot to bootloader.
Unlock the bootloader with the following command:
Code:
fastboot oem lock
Return to Developer options and turn off "OEM unlocking"
Thank you for the write up .. nicely done :good:
Sent from my OnePlus5T using XDA Labs
It gave me an error 1 in TWRP. I had to do the following:
1) Make sure the bootloader remains unlocked
2) Back your apps up in TitaniumBackup
3) Back your /sdcard partition up on your computer so you don't lose anything
4) Reflash stock recovery in the bootloader
5) Boot into stock recovery and hit "forgot password" when it asks for your lock code
6) Boot back into bootloader and reflash TWRP
7) Place stock OOS zip onto the /sdcard partition
8) While you're in TWRP, flash stock recovery through its image flasher then reboot into recovery
9) Flash stock OOS, reboot, and then mod however you want
Click to expand...
Click to collapse
blackknightavalon said:
It gave me an error 1 in TWRP. I had to do the following:
Click to expand...
Click to collapse
Will in 9th last step restoring from nandroid OB-1 work ?
It should I guess
Sent from my ONEPLUS A5010 using Tapatalk
Bump!
I made a big update to the OP today with more explanation, more detail and download links.
Thanks buddy, that tutorial worked perfectly!
The other way is to flash rollback image to Nougat in stock recovery.
https://goo.gl/YRyrt6
there are no other ways to revert back to stock OOS without affecting internal sd /sdcard ?
thanks for the guide above.
Ok I'm a bit Rusty. Flash from bootloader? Meaning adb? Then adb TWRP then boot to TWRP then flash stock room(s)?
Ippolito1971 said:
Ok I'm a bit Rusty. Flash from bootloader? Meaning adb? Then adb TWRP then boot to TWRP then flash stock room(s)?
Click to expand...
Click to collapse
Please do not quote the whole OP just to get someone's attention. A mention (@the Doctor) would suffice.
To answer your question, flash the stock recovery with the fastboot command:
Code:
fastboot flash recovery [I]stock_recovery.img[/I]
The only ADB command involved is "push" to get the ROM onto the sdcard in step 5.
Thx @the Doctor. My apologies.
Thanks for the writeup, I'll probably try soon and report back.
Thanks for this, may need it. Plan to flash DU 8.1 tomorrow. So you can't just restore an ob1 or ob2 nandroid from a custom ROM?
tcat007 said:
Thanks for this, may need it. Plan to flash DU 8.1 tomorrow. So you can't just restore an ob1 or ob2 nandroid from a custom ROM?
Click to expand...
Click to collapse
You can, but TWRP will not recognize your PIN or password while in OOS, so you'll have to set lockscreen security to none or swipe. Or you could do the procedure in the OP, then restore only data from your nandroid. You'll have to re-flash Magisk or any other mods after that.
I don't use a pin for backups or restores. Since I seem to have to format internal storage to get a custom ROM to boot, was just wondering if restore of oos nandroid works once on DU.
Sent from my OnePlus5T using XDA Labs
hello thanks for the guide just did this when i boot i cant connect to any wifi network thanks
How can I get my wifi back after reverting to 4.7.6? Ive tried EFS backup and everything possible but the only way to get wifi back is to flash an Oreo zip.
forty9er said:
hello thanks for the guide just did this when i boot i cant connect to any wifi network thanks
Click to expand...
Click to collapse
Did you restore to 4.7.6 or Oreo Beta 1/2?
Dazed No More said:
How can I get my wifi back after reverting to 4.7.6? Ive tried EFS backup and everything possible but the only way to get wifi back is to flash an Oreo zip.
Click to expand...
Click to collapse
Have you flashed OOS Oreo Beta? My theory is that the firmware won't downgrade back to OOS 4.7.6, but I'm not sure. I've only restored back to OOS OB1/2, and wifi has worked perfectly every time.
the Doctor said:
Did you restore to 4.7.6 or Oreo Beta 1/2?
Have you flashed OOS Oreo Beta? My theory is that the firmware won't downgrade back to OOS 4.7.6, but I'm not sure. I've only restored back to OOS OB1/2, and wifi has worked perfectly every time.
Click to expand...
Click to collapse
Flashing Oreo beta is the only way to get it back as myself and others have found in the thread that was started on the subject. I hadn't seen that initially when I posted in here.
I was hopeful that following your method to a T would get me my wifi back on 4.7.6 but it wasn't meant to be. Absolutely nothing I have tried in the last 24 hours has worked to get it working on 4.7.6 including multiple clean and dirty flashes of the full 4.7.6 zip, twrp, stock recovery, restoring multiple backups, restoring EFS, factory reset, wipes, etc.
You might want to add that to the OP that if you revert to 4.7.6 that wifi will not work.
Dazed No More said:
You might want to add that to the OP that if you revert to 4.7.6 that wifi will not work.
Click to expand...
Click to collapse
Thank you, and done. :good:

Categories

Resources