[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
This ROM contains dm-verity

This ROM will encrypt your device by default

This ROM will replace your current recovery if you do not disable verity

Please be careful before flashing

We are not responsible for anything that happens to your device, your data, people next to you, people on the opposite side of the earth or anyone, including you for the matter. You are choosing to do these modifications

Only builds with their sha2-512 (newer devices can use sha3-512) hashes uploaded to glassrom-verification are official, stable builds. If a hash is absent from the glassrom-verification page for a file then either the file is corrupt or the file you downloaded was not meant for you. You are requested not to visit the download server and download files that do not have entries in glassrom-verification. Such builds/files is used will not be supported

Glassrom for op3 and 3t

Download links:

Download from glassrom server (no logging) (ipv4 and ipv6):

https://glassrom.pw/op3_glassrom.zip

Download from CDN (see privacy and GDPR notice below) (ipv4 only):

https://cdn.glassrom.pw/op3_glassrom.zip

Build verification: https://github.com/GlassROM/glassrom-verification

Verifying builds: use the build verification link to verify your download. The hashing algorithm is sha2-512. The commit is signed with an x25519 private key. Glassrom is signed with a 2048-bit e3 RSA key with sha2-256 as the hashing algorithm. The glassrom server discloses DANE TLSA records and has certificate transparency, HPKP and CAA and only replies over TLS 1.3 with a secp384r1 private key. The domain supports DNSSEC

Donate to glassrom: https://donorbox.org/glassrom

Note that glassrom is a for-profit company. Donations are not tax exempt

Privacy policy:

Glassrom collects

absolutely zero

data

Lineageos might collect some data like analytics. Read their privacy policy at the link below

https://lineageos.org/legal/

We use bunnycdn. Read their privacy policy here: https://bunnycdn.com/privacy

https://bunnycdn.com/gdpr

Note that if you access the server with glassrom.pw you bypass bunnycdn and connect to the server directly. If you don't want to use the CDN use https://glassrom.pw which directly connects to the server

Features:

Kernel hardening: selinux compiled in release mode, unsafe configurations turned off, enabled yama with ptrace scope 3, kspp patches applied

A completely clean kernel with no "optimisation" or other nonsense

Tripndroid I/O scheduler is used as the default

Upstreamed kernel to 3.18.140

F2FS backported from the latest 5.2-rc1 release

P gestures and navbar are enabled by default

Substratum exposure support

Aggressive battery optimisation*

Maximum permissible password length is 64 characters instead of 16

Aggressive AOT compilation**

Includes both microg as well as Google apps packages. Full freedom of choice. Signature spoofing is supported. Installing proprietary webviews even when using microg is supported. Open source/self-built webviews need to be put into /system/app for proper functionality. Minimal gapps packages can be flashed as well as opengapps super

Light optimisation. Utmost care has been taken to ensure that optimisation doesn't break anything

Kernel compiled with totally stock GCC and ROM compiled with AOSP clang. No gimmicks

Full resize support for encryption

Support for booting off locked bootloaders

User build signed with release-keys. Release-keys ensure authenticity and security. User build removes a lot of debugging code and enforces stricter and more secure defaults

No dependency on firmware. Flash and run on any firmware

Did we mention that we collect absolutely zero data and have strong data protection policies for any data you willingly agree to submit through us through our support channels

*Agressive battery optimisation shuts down the CPU during doze. Alarm apps and all apps that implement GCM will continue to receive notifications. Implementation is tightly integrated into doze. Whitelisting an app from doze will also whitelist it from agressive battery optimisation. Aggressive battery optimisation never kills or moves apps out of RAM. It can achieve as low as 1% battery drain overnight (as per tests)

**This feature improves performance immediately on first boot. As a consequence the first boot takes 50 minutes however this optimisation seriously improves both performance as well as battery life

Instructions: flash the ROM

Flash anything else that you want

If you want to boot with dm-verity tick "mount system partition read-only" before flashing the ROM and don't flash anything after flashing the ROM

Do not wipe caches. Read this first https://forums.oneplus.com/threads/...-and-battery-calibration-myths-busted.993896/

Bromite webview users should install https://glassrom.pw/bromite.apk

Once bromite system webview is installed go to the "verifying installation" section of the wiki https://github.com/bromite/bromite/wiki/Installing-SystemWebView#verifying-installation

Installing updates:

Dirty flash the build. No need to wipe caches or any other nonsense

Remember to reflash all your mods (including gapps) since backuptool is not present

Update firmware as required. Note that glassrom doesn't enforce firmware requirements

Troubleshooting:

Stuck on oneplus logo: dm-verity failure. Make sure you ticked mount system partition read-only and didn't flash anything after the ROM or use a dm-verity disabler like https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389

Boots, get stuck on bootanimation then reboots to TWRP

This happens if glassrom fails to reserve space for the crypto footer. Space will be reserved even if you disable encryption. Format data partition (not wipe) using enhanced twrp if this is the case

Doesn't flash with enhanced TWRP:

Use official twrp to flash glassrom and then flash enhanced twrp. Enhanced twrp can only flash new glassrom releases and not the current glassrom release. When upgrading glassrom always update glassrom before updating enhanced twrp

Decryption unsuccessful error:

This can happen if you use F2FS and flash a custom kernel. Glassrom uses the latest F2FS and enables all new F2FS features very quickly. If your custom kernel does not support the same features as glassrom's kernel them you'll run into this error

Remember that data recovery is possible through TWRP

Boots for a long time

This is a feature. First boot can take 50 minutes. If you want to boot faster then don't wipe dalvik-cache in recovery

This has been fixed on newer builds and should no longer be a problem

Overnight battery drain:

Agressive battery optimisation while saves more battery than OOS allows apps to continue running instead of killing them. If you have battery drain it's because of some app and not the ROM's issue

Also I will NOT listen to these bug reports. You are supposed to leave your phone on a charger overnight while it is turned on. If you're not doing what the android system already expects then I can't help you.

TWRP flashing errors:

Error codes are useless. Read the message above the error

Sources: https://github.com/GlassROM

https://github.com/GlassROM-devices

https://github.com/anupritaisno1/proprietary_vendor_oneplus

https://github.com/LineageOS

https://bitbucket.org/anupritaisno1/aarch64-linux-gnu

Flashing instructions: just flash it in your recovery and flash whatever else you flash

For TWRP I recommend enhanced twrp but you can use any TWRP and the result will be the same

If you use enhanced twrp you must use 1 version older than the current release. Whole flashing you must remember to update the twrp after the ROM

Latest OOS firmware needs to be flashed

Unlike other ROMs there is no need at all to wipe cache or clean flash new builds. In fact it is advised not to do so while flashing an update

The following is not allowed when reporting bugs: xposed, custom kernels, anything other than gapps that is installed to the system and magisk

An exception is made for xposed - merely having the framework installed causes no issues. While asking for support only xposed modules need to be disabled. The framework itself can be kept installed

Magisk is strictly forbidden while submitting bug reports. Bug reports made with it installed will be rejected and I won't even read your log. If you have magisk uninstall it and clean flash the ROM before making bug reports

Locking your bootloader:

This is dangerous. Glassrom takes absolutely zero responsibility if you try this

Note: currently the lineageos recovery is not available so there is no way to update glassrom on a locked bootloader. Upgrading glassrom on a locked bootloader will be possible once lineage recovery has been finalised

Flash glassrom and preserve dm-verity

Boot and interrupt the boot process

Boot to recovery. Make sure it has been replaced with glassrom's recovery

Boot to fastboot and issue this command

fastboot oem lock

Caveats: currently there is no way to format the data partition correctly. This will be fixed once lineage recovery is up

Notes for custom kernel developers:

Note: only custom kernels built by the modding system are officially supported. The requirements for official support are way different than this

If you package a kernel and use a special configuration app glassrom lacks selinux policy to allow the app to read out values. Make sure you ship a proper selinux policy or make sure your configuration app always runs commands as root

Make sure your kernel has the sdfat driver and the configuration options (SDFAT=y SDFAT_USE_FOR_VFAT=y) are enabled or ship your own fstab

Optionally include the tripndroid I/O scheduler or use your own init script to set an I/O scheduler

F2FS MUST at least support inline_dentry and fsync_mode=nobarrier. Backports for 3.18 are available from Google and other parties

To support USB-OTG devices properly make sure (SDFAT_USE_FOR_EXFAT=y)