[OnePlus 5 Guides, News, & Discussion] guitardedhero:
I thought I might share my preparation of OnePlus 5's latest OxygenOS 5.1.2 firmware update as the official offering still seems to be less than a smooth, uneventful updating procedure for many for a variety of reasons.

Soon after experiencing the consistency of unwanted /data partition formats and other less frustrating annoyances with the initial series of Oreo beta/stable updates for this device, I decided to test the results using my typical preparation which dates back to the Nexus 6's more youthful days.

Some may be familiar with XDA member [MENTION=5284958]tupac4u[/MENTION] and his "Debloated/Deodexed" Nexus and Pixel roms.

This preparation has been a longtime favorite of mine and is one of the easiest installation preparations, using or not using [MENTION=5787964]SuperR.[/MENTION]'s wonderful kitchen utility. I chose to abandon this automated method due to the OnePlus 5's /firmware-update and /RADIO directories of images, binaries, etc. not being targeted during the kitchen preparation.

I am not a typical user, I admit, I incessantly tinker and clock hours of bootlooping animations, so this particular preparation of mine is certainly one that those like me will enjoy:

The /system directory is available in all its glory for micro-managing system content, fully deodexed for convenient .apk/.jar adjustments, conducive to further tailoring for unique, individual needs due to the convenience of what is generally referred to as set_metadata rom builds. Simply extract the rom archive, perform file management tasks of interest, compress the extracted contents back to .zip format, and flash in your chosen custom recovery.

Users who merely want to update their firmware with the grace and predictability found on previous devices such as Nexus and Pixel, nothing more than flashing the .zip is necessary.

The default scenario booted from a successful installation:

Fully deodexed .apk's and .jar's with a light debloat of Google .apk's available in the Play Store:

Chrome

Drive

Duo (which I am now suspecting I failed to remove, lol)

Gmail

Maps

Play Music

Videos

YouTube

possibly more, none

/vendor/etc/apps directory

Full OnePlus firmware contents such as baseband, images, binaries generally not found in OxygenOS based custom rom builds.

The latest BusyBox arm64-v8a binary installed in /system/xbin including all applets.

Secure boot.img free of dm-verity and forced encryption properties.

SELinux mode is Enforcing with no changes to sepolicy or sepolicy rules.

Removal of shell operations attempting stock recovery integrity.

Root Solutions:

No root solution is installed during the rom installation as the zip appears once downloaded.

At the time of this posting, Magisk 16.4 (1642) and SuperSU-2.82-SR5 installations are possible during the rom installation in the following manner:

Extract the rom .zip archive any time after the download completes

Navigate to the /root directory of the extracted location

This directory presents the following three directories:

/install/(empty)

/magisk/root.zip

/supersu/root.zip

The objective for accommodating root flexibility is purposed for simplicity and unambiguity.

Achieving a root solution without any additional installation activities in custom recovery is only possible if /root/install/root.zip exists in the archive before the rom installation begins.

Extract the rom .zip if this has not already been performed.

Simply copy the desired root.zip from within the appropriate directoy (magisk or supersu) and paste the .zip directly into the neighboring /root/install directory before compressing the entire rom contents.

Of course, one may install a root solution zip immediately or any time after the rom installation similar to most rom flashing routines of present. This is another "tinkerer-oriented" aspect of the rom build.

It must be stated that the SuperSU solution has NOT been tested by me. It is simply provided as a potential solution until confirmation is observed by me.

Installation:

Some scenarios may be successful without any partition wipes in recovery.

All scenarios failing to meet individual satisfaction (one or more FC events, for example) will typically be fully resolved performing a factory reset while in recovery.

Any expectations exceeding what can be acquired with the official firmware is likely unreasonable unless expectations are pertaining to the stock experience and its swiftness/stability.

If you're still with me, you may be scratching your head to make sense of this post being here and not the first post of a new thread. I assure you, I had no intention of accumulating this word count. I just wanted to offer something different for those interested, nothing more, but I want to be as thorough as I could be in order to prevent unpleasant surprises and unanswered requests for help/info.

https://www.androidfilehost.com/?fid=890278863836288722

MD5: 55652daaa809a222ebde1e4a0f2efcf5

Lastly, anything that results from working with this or any of my rom .zip's owes no credit, mention, or anything else to me. This firmware is the property of OnePlus. My only request is that some level of discipline and quality assurance is present when sharing content purposed for device manipulation, especially firmware installations. :good: