Database Info

Problem Flashing Factory Images

Wondering if many others of you have run across this, what causes it, and how to avoid it. Basically, I download the factory image from google's image page, flash-all using adb/fastboot. All looks good, every part of installation says OKAY, no fails. Then upon reboot it goes back to bootloader, but now with a yellow banner at the bottom - ERROR: LoadImageAndAuth Failed: Load Error. Sometimes the banner reads ERROR: Slot Unbootable: Load Error. (see attached pictures)
There's no way out of it, flashing images, bootloader or boot.img or whatever separately, flashing twrp, switching between a/b partitions, nothing changes it. Adb/fastboot is current. It's happened after regular flash-all, it's happened when "-w" is removed. It's happened with and without twrp installed. This last time I tried to avoid it by updating without flashing the image, removed twrp and tried to sideload the OTA in stock recovery, which also landed me in the same spot, in the bootloader with that yellow banner of death. Been hit by this using Dec., Feb., and March updates. I stayed on the Dec. update for a while because I've been afraid of it happening again... sure enough it did.
I've replaced a few pixel 2's because of this, every time Google willingly stands by their product and replaces it. One google worker told me this is a known issue they were working on, others said it isn't, and none have provided an explanation for why it happens or how to avoid it. I assume it's some kind of instability with the a/b partition system. I did the same process with my N5x a couple days ago (flashed image then added twrp, magisk, all that stuff) and as usual everything went swimmingly. Tried just flashing current image on p2 the next day and another one bit the dust. Another replacement is on its way now.
So I turn to you. Any of you run into this? What causes it? How can I flash updates without this happening again?

As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.

deepdvd said:
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
Click to expand...
Click to collapse
Tried boot.img but not working for me, still stuck in bootloader. But good to know, I didn't realize that was a possibility. Sucks having to be tethered like that though. I backed up double before messing with it, both nandroid and titanium, expecting I might run into this again.
The replacement process is relatively painless, only takes like 3 days to get a new one. Just be sure to do it while covered under warranty.

Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.

clcdev said:
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
Click to expand...
Click to collapse
Thanks man, seems like it since not many people are experiencing this. Can't think of what external issue it could be other than something with my computer, but im sure not having any troubles doing the same stuff and more on my nexus.

@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.

craigacgomez said:
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
Click to expand...
Click to collapse
Well I tried flashing the ota in recovery and that's what triggered it this last time. But I didn't try doing each partition, maybe that's where it went wrong

Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.

COMpulse said:
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
Click to expand...
Click to collapse
That's what gets me, can't simply fastboot the image to recover, that fail-safe isn't reliable for me.
Got the replacement and set it up so I can update normally. Just booted twrp but didn't install, so I could flash magisk. With no twrp and easily uninstall magisk I can just update via regular OTA when it shows up. Then temporarily boot twrp again to reinstall magisk. Just did that for the March update and worked fine.
A little inconvenient of a workaround but I'm updating without concern about this image flashing problem.

I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.

kkjb said:
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
Click to expand...
Click to collapse
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.

kkjb said:
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
Click to expand...
Click to collapse
Wow great to hear it worked! I tried the deuce script but couldn't get it to work either. I heard there was an issue with the bootloader in December and was supposed to have been fixed in January. But that bootloader error was one that I was also getting after the yellow banner started showing up, even on this last go around. Just before the initial bricking fastboot was reporting all successful on the flash.

More of my troubles
I have twrp 3.2.1-2, Magisk v16.1(1610) Jan 18 8.1.0. The device is working as before. So to recap...first post is what I HAD. My bootloader is stuck on 002.0059.00 this is the one from opd1.170816.025 which is 8.0.0 Nov 17. This some how flashed through Deuce's script and stuck. Now of course nothing will flash with Factory images because I have a botched up Boot.img. From looking back the trouble started with going to update to P. Removed Magisk through manager. It "patched" boot but some how on mine (with flashed twrp) recovery caused a flag I guess to set.
So some point I'm going to get Magisk to patch current Factory Boot.img 002.0067.00 which is in Feb, Mar 18 and P.
Need time to read though Magisk or wait for others to experience. I believe this is the warning message of TWRP and Pixel 2 A/B slots.

update to my troubles
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....

kkjb said:
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
Click to expand...
Click to collapse
That's pretty slick that you got it working again, especially with the bootloader error. I didn't think you could get the current OS working with an old bootloader at all. Hopefully at some point you will be able to update it all the way.

I soft bricked it..so don't do this.
See previous to catch up. Since I pulled the plug and had a Google Warranty phone in hand...21 hours later!
I decided to do all the things NOT TO DO.
Pulled factory Image file from last bootloader with 0059 bootloader.. Nov 17
Flashed tdbo.img, boot.img.
Didn't change same Flash failure device return message. Had to boot TWRP, flash twrp to get working again. Since phone needs to return for credit.
Nothing to lose, I have been on slot = A always. Moved to slot = B....
Now it is a brick.
First couple of power cycles, one line flash, vibrate. Then after 3-4 more cycles no more vibration. longer time to one line flash.
Warm to touch, overnight charge. Same.
So message is to keep backup of files used in first portion of Magisk and twrp installs. Must follow instructions if want to remove Magisk root.
Somehow my problem is a weird one off with the bootloader oddity.

My OP 7 PRO(GM21AA) is being completely stuck at Fastboot.

Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.

Maybe THIS can help you?

Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.

Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone

lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John

Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.

Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"

You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck

junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John

Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.

I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.

junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John

Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John

I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things

aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.

Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks

aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John

Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.

firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.

Fastboot Bootloop

I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.

Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.img​Learned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.

Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.img​Learned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....

mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq

OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help

Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.

Nexus 6P, TWRP, Stock image, NetHunter... what could possibly go wrong?

I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!

[email protected] said:
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
Click to expand...
Click to collapse
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk

I formatted, installed factory image, installed TWRP, flashed Magisk, confirmed root, flashed NetHunter ZIP, same result
Droidriven said:
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse

So if anyone else is facing the same issuing of wanting to install this old(ish) software onto this old(ish) hardware, and got stuck in the same place as me, here are the three steps that I had to take to succeed that were not in official documentation:
1)When flashing the factory Android image, make sure that you are using the newest version that is supported by NetHunter. At time of writing, this is not the same as the newest version of Android.
2)Remove the -w option from the installation script
3)Be sure to install a compatible kernel from builds.nethunter.com
Thanks again to @Droidriven for the tip on using Magisk