[OnePlus 8 Pro Questions & Answers] ApollosArmory:
lmao no prob - im at the point of pulling my hair out trying to get things in proper order here with this device too - can literally make it do anything but get NH running proper with all the proper configs and system to turn from r/o to r/w correctly since all the old sys r/w's are depreciated - also note too theres weird varients with these op8 models even with being unlocked 5g phones there is 2017s tmobile and 2019s VW (2015 OP global) iirc - the in2017s and 2019s though for some reason are also classified in as in68cb firmware devices (IN2017 tmobile is IN55CB firmware) and im guessing trying to break any of the carriers encryption and trying to port the phone over to anyone but their services is made 20x more difficult than a factory unlocked variant. I can get all other models of oneplus's right now flashed up with NH but if someone is running it on an IN2017 varient bless their soul for figuring out whats taken me a week.

side note - I MSM'd myself back to A10.5.7 on an IN2017 build and then used one of the FASTBOOT ROMS listed over here https://xdaforums.com/t/rom-stock-fastboot-op8-stock-fastboot-roms-for-oneplus-8.4084629/ and followed that - unlocked bootloader before and flashed over the 10.5.9 (10.5.9-EUROPE-OnePlus8Oxygen_15.E.18_OTA_018_all_2007160043_913306-FASTBOOT) and was able to successful convert myself to a IN2017 running OOS 10.5.9 and then use the local update feature inside to OTA update myself using stock OTA OP Firmware For OOS 11 up to 11.0.11.11.IN21AA (https://community.oneplus.com/thread/1548746) and im up and running with an internationally unlocked OOS variant - NO IN2017 tmobile remainders (even their data collection menu at begining of phone prompt and boot image is gone) but my phone still is recognized by my PC as an IN2017 and androids main menu... now the real fun for me starts, hopefully you wont have to rabbithole your self like how I am with this lol

EDIT 2: holy cow now idk if anyone wants to even hear this news but after a week+ here on this phone alone, I can 100% confirm that this above method works to get nh installed ^ however the biggest issue I had was the fact that even after going to international firmware the phone still wanted to recognize itself as a in2017 model and by default kept kicking on force encryption and verity (similar to the OP7) sooo after doing all that.

- OnePlus 8 (IN2017 Tmobile 5g 126gb - 8gb - oem unlocked with their code) -flashed to OOS 11.0.11.11IN21AA

- I decided to backup once while working and say **** it and download the NH Kernel first - THIS RIGHT HERE IS WHAT GOT THINGS MOVING IN THE RIGHT DIRECTION - I CAN 100% CONFIRM 99.9% OF THINGS ARE WORKING ON THIS EVEN WITH /DATA/ being a pos and not decrypting and mounting correctly.

- out of sheer curiosity I decided to go flash lebigmacs newer SystemRW 1.41 and got an error 73 at the end due to the inability to produce a super_patched.img (don't know if this was simply because it wasnt convertiable or if because I was on a Frankenstein OnePlus - that seemed to be the issue - but I sideloaded the good old trustworthy DMVERITY-FORCE Encrypt tool (https://xdaforums.com/t/deprecated-...ncrypt-disk-quota-disabler-11-2-2020.3817389/ - get an error ODM can't mount so I freak out reboot back to recovery using twrp.img (adb reboot bootloader - fastboot boot TWRP.img)

- format the /data/ section to remove internal encryption on it (not wipe)

- try booting to system after formatting and rebooting back into bootloader to start /data/ rebuild process - met with a spinning oneplus logo - great -

-went back restored the build to before the above ^ and ended up doing the exact same but skipping the systemRW that is reccomended and opted for the Disable Verity and Disable ForcedEncryption methods listed by the following:

if you install through recovery (either for the first time or as an update) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:

echo KEEPVERITY=true>>/cache/.magisk

echo KEEPFORCEENCRYPT=true>>/cache/.magisk

If you can't access /data (TWRP can't decrypt, etc) you can instead use either /data/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.

Some devices need to keep dm-verity enabled to work properly. One example is some Huawei devices that might otherwise experience weird behaviour or bootloops.

Disabling dm-verity and forced encryption​

If you on the other hand want to disable either dm-verity or forced encryption, you can go about it the same way as described above. If you're using the .magisk file method, just change KEEPVERITY and/or KEEPFORCEENCRYPT in the commands to false:

echo KEEPVERITY=false>>/data/.magisk

echo KEEPFORCEENCRYPT=false>>/data/.magisk

If you can't access /data (TWRP can't decrypt, etc) you can instead use either /cache/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.

If disabling verity through Magisk doesn't help, you can try the following command (provided that your device has a vbmeta.img):

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

- being fustrated a week into the phone my dumb*** pulls off both the magisk and vbmeta flashes instead of chosing just on (I mounted every single partition in twrp before doing this too)

- flashed the kernel I found buried in the NH Build Page for A11 (as even after format I was running 11.0.11.11 OOSIN21AA international on a IN2017 model with full android security patches) - THANK YOU FOR THIS AS IM SURE THIS SAVES A TON OF PEOPLE THE SAME HEADACHE THAT I WAS DEALING WITH AS THE KERNEL WAS THE MAIN ISSUE ON NH FUNCTIONALITY (not OOS or A11 underlying) link here: see post 192 on here: https://xdaforums.com/t/rom-unofficial-nethunter-oneplus-8t-android-11-12-26-08-21.4324555/page-10 with the download link: https://sourceforge.net/projects/op8-a11-nethunter-kernel-old/ (this was a reupload kernel with approval by flypatri0t on it working.)

- looked like a success on the sideload of DisableDMVERITY etc so i booted to system after flashing the kernel through adb sideload

- after I flashed the kernel and going back to system I went and reinstalled magisk through a sideload and then went back in and repatched by magisk image in the install section (dont know if I needed to)

- phone boots up, everything looks normal, setup is good kernel is registering, phones still a in2017 but I notice now when I went over my OOS 11.0.11.11 IN21AA is still there on my firmware

-ignored it and went over adb and pushed over to /sdcard/ the "GENERIC ARM64 NETHUNTER IMAGE"

- after I flashed the new nethunter kernel image with TWRP and then transfered the magisk image over to I went and used the reccomended install and patched my magisk file direct since my phone was reading encrypted at this point somehow (even though it was installed already dont know if necessary - but encryption being kicked on here pissed me off so I said **** it and went out all)

- ignored all warnings as I was already on a in2017 with flashed global duel sims, unlocked oem bootloader, questionable kernel as it was depriciated off the main NH A11 OP8 page and made my way back to magisk

- Loaded the Generic-x64 Build from the nethunter lite in MAGISK from /sdcard/

- instead of a direct reboot however so I didnt trigger verity or anything I backed out of the magisk installer and went over to my nh store (ignored the "set nh up first preliminary then update from store" since I know I can install from the store but was already using the generic which is pretty up to date.

-update nethunter app direct from store (be patient as you can double install if you try and click through prompts quick and it ****s up the chroot and how it works) I'd post a log but they're buried and to be parsed with devs at a later time

- after full update from nh store rebooted the phone back into system

- opened nh did full install on chroot along w setup and got all my rolling updates in finally

- external monitoring and more

- sigh of relief here cus I finally got it running - injection working along w hid attacks - then realize when I go to change my boot image. The ****ing phone encrypted itself again so while I have a 95% functional kali experience the /data/ being readonly and no working SystemRW that I can find to decrypt and mount it proper without having the IN2017 varient kick off some shadow in the /system and lock up /system and /data back into encrypted states (no passwords or even screen swap on phone too) - as of now I can use my device albeit one sim, on some OOS that I never should've gotten since im supposedly tmobile locked even with an unlock token since they removed the local OTA update from OOS they use.

- Lessons to be learned: IF YOU WANT NETHUNTER INSTALLED PROPER ON A ** CARRIER ** VARIANT - visible, VW, Tmobile (in55cb/in68ce firmwares) itd be cheaper and probably more effective for you to head down to your local hardware store and stick a garden hose into the tailpipe of your car and then reattempt to do this process inside of a garage as it will be a less painful experience than trying to bust out of these carrier devices as for the 8T and 8Pro on global and EU varients I got them both working flawlessly with written guides if you need.

excuse all the typos - im exhausted after dealing with shell scripts all day lmao

*ALSO IF ANYONE CAN EXPLAIN THIS LAST PART TO ME I WOULD BE AMAZED AS I CANT FIND A LOGICAL ANSWER TO WHY THIS WORKS IF IT DOES :

- after doing all that and getting chroot up running fully updated packages etc etc then I got a notification from my system update which I though I disabled saying it had an update for me but it was for a 2015 variant which is a global oneplus 8 international under the C varient firmware, despite me being on a IN2017 - so its rolling my updates like im still on a regular OP not from tmobile - question is will I brick the phone if update to that since I OTA updated my way into 11.0.11.11 initially by flashing over to a FASTBOOT ROM - the whole thing sketches me out and im kinda scared I lose my nh build but I know IN2015 firmware is 2000000000x easier to work with than in2017.

edit 3: if anyone reading this was curious, yes, doing what I said above (OOS 11.0.11.11 on IN2017 TMO OP8 --> IN2015_C_32xxxxx) will 1000000% brick you and worse because of the modem issues had a nice oled paperweight for a few hours tonight :) Since im feeling like a bit of a masochist tonight I'm gonna re-msm myself and go back to stock and try to somehow beat the encryption fully like I can on every other model of OP8 (except verizon and stupid Visible - hydrogenOS was even easier to break and keep disabled than this POS - TO FB MARKETPLACE IT GOES AFTER TONIGHT! lmao)