yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
it all works fine now but i see weird wifi errors in log like

```

04-09 00:52:10.374 852 852 E WifiHAL : nan_data_interface_delete: requestEvent Error:-5

04-09 00:52:10.375 1396 2328 E WifiAwareNativeApi: disable: null interface

04-09 00:52:10.378 852 852 E WifiHAL : error_handler_nan: Error code:-95 (Operation not supported on transport endpoint)

04-09 00:52:10.378 852 852 E WifiHAL : nan_get_capabilities: requestEvent Error:-3

```

need to investigate these and then op7pro bringup is complete
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] :
i didn't realize you could lock the bootloader on this phone with this rom. are there any instructions on how to do this? where do i find the avb key?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
ok i have now fixed all issues on the device side. everything seems stable

it's on telegram https://t.me/glassrom_release_mirror/51

i've also uploaded it below

fastboot flash avb_custom_key avb_pkmd.bin

fastboot flashing lock

if you haven't done any modifications glassrom will now boot with the same level of protection as stock

some people think locking the bootloader is scary. for that i have some advice: keep oem unlocking turned on while locking the bootloader. this way even if it doesn't boot you can unlock again

i run my own device on glassrom with the bootloader locked so it it safe
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
here's the build https://glassrom.org/guacamole-ota_update-eng.suzumi.20210409.182050.zip

some things to know:

the update might take a long time. some patience is needed

after flashing the update the phone may get stuck on the boot logo for upto 2 minutes. this is normal. it is migrating your data from android 10 to 11 and this takes some time

after booting you will see an internal error screen. sadly this is something oneplus messed up on their side so no solution is possible. this error however isn't going to affect your device usage, it's just an annoyance at worst. just dismiss the warning
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Btw you will notice that this update introduces 2 new permissions: sensors and internet. These are granted by default. You should revoke them if you wish to. There is a proof of concept already available for recording audio through the phone sensors without needing the microphone for instance. This is a problem with all phones, not just OnePlus

The internet permission in glassrom is far stronger than the lineage firewall. Unless the app can IPC and pass a message to another app that has internet access no other bypass is possible

The lineage firewall can be quite easily bypassed if a malicious app wishes to do so. If you want to be sure, use the internet permission instead of the lineage firewall
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] hellcat50:
Just flashed your latest release. I have some questions:

- Why didn't you disable swap (zram)? It is pretty much useless on our device since we have 6gb+ ram which is more than enough.

- Signature spoofing apparently is missing? (maybe i'm doing something wrong though idk)

Other than that I did notice some animation lags that didn't happen with los 17.1, but that didn't bother me too much
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
signature spoofing is an unnecessary security risk. there is some work towards making a more secure implementation but it is not ready yet

i have also audited microg itself and it isn't a really secure application. even official google play services does way better than microg when it comes to security

zram does have some advantages even if you have a lot of ram. your system is not going to pointlessly swap everything to zram. It will only do so when it is actually needed. it isn't going to affect much unlike what some other people claim
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] hellcat50:
well okay then thanks for your response. it's okay i don't really need microg anyway, just wanted to know why signature spoofing was removed :) and about zram i don't mind it but as you said people claim that it harms battery and storage that's why i mentioned it. it's all good though so far :)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
phone storage has really advanced in the past few years. you can continuously write to your storage, maybe even run servers off your phone and nothing is really going to happen to your storage. your phone would become obsolete before the storage died

the battery impact isn't really all that much
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] :
well this is odd, with the new update i no longer have a webview implementation. it appears to be installed but the file silze is listed as 0B. any suggestions on how to restore the webview? i have already tried flashing the update again and a factory reset in recovery
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] hellcat50:
i just checked this and i have the same issue
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
fixed in https://github.com/GlassROM/android_vendor_lineage/commit/de170d82cd2a3edfa27ddacdc87ec3719bf43cb3
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
okay i see what the problem is now. upstream seems to have changed the package name for vanadium

https://github.com/GlassROM/android_vendor_lineage/commit/ef60b230a62be2a99fc56ec147d4984ad5c64f5d will fix it. i can prepare fixed builds soon
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] :
much appreciated, in the mean time, is it possible to downgrade? or will i need to clean flash the previous build from oos?

EDIT: use msmdownload tool to restore to oos, since twrp isn't compatible with a11 yet
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
https://glassrom.org/guacamole-ota_update-2021.04.11.12.zip
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
it isn't possible to downgrade glassrom. glassrom has downgrade attack protection and this is enforced by both software and hardware even if the bootloader is unlocked

however, note that glassrom will not touch the downgrade protection until you install a new system update that has booted to the lockscreen. if the hardware has insider attack protection then some firmware won't be updated at all until the user also unlocks the phone. a rollback would have been possible had 11 never booted but in this case it booted and the rollback indexes were updated
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
this build is the release candidate for 11. it will be released to stable if no new bugs are found
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
I would appreciate it if somebody could run CTS on the release candidate

Please be aware that the entire CTS needs several days to complete and requires a lot of ram on the computer running the test suite. It also requires a special setup which we aren't able to acquire ourselves during the pandemic but pretty sure a few other people already have it. Pm me for details
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] :
i think there may be a bug with the unifiednlp settings app in the release candidate. it's unable to recognize the location/address lookup backends i have installed (mozilla, deja vu, nominatim). i've tried restarting, reinstalling the backends, force stopping unifiednlp and clearing unifiednlp storage
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
It's probably lacking the QUERY_INSTALL_PACKAGES permission introduced in 11. It's not really a release blocker so I'll fix it with a monthly security update
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Package visibility in Android 11 | Android Developers

developer.android.com

I'll need to look into it later. There are other more important things to fix rn
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Right now I'm unsure how I want to fix the issue with unifiednlp. Unifiednlp is already a problematic app. Firstly this is a privileged system app that's accepting untrusted input from user installable sources. That should already be considered a security vulnerability of sorts. To make matters worse it forces the user to fetch these plugins from untrusted and unverifiable sources like fdroid. We don't want to make users rely on fdroid as it isn't secure. Do you see how much the impact of installing an untrusted plugin and having it feed data to a system app can be?

We have similar issues with microg. The code required for signature spoofing is already in place but the way it works is that it would check the permission of the installed microg app and only spoof the signature iff it matches. Again, fdroid doesn't have good security practices and we absolutely do not want to pin their signature. We also do not want users to think they are somehow more secure with microg -- even official GMS has better security than this. The only solution would be that someone at glassrom would need to spend a significant amount of time maintaining these apps
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Also remember that microg can be way more dangerous on custom ROMs other than glassrom. First of all almost every custom rom destroys the android security model completely. The second which is even scarier is that google likes to open up selinux exemptions for their own apps. Since microg is pretending to be a google app it also acquires all of these exemptions. These exemptions themselves are scary like a W^X protection bypass. Now this isn't much of a problem with official GMS as they have decent security practices but when it comes to microg and all the other security issues it has of its own (remember microg also has unifiednlp built in) combined with sourcing these apps from untrusted places like fdroid it can really become dangerous. I am talking arbitrary code execution from the context of an app with privileges higher than even privileged system apps
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Glassrom removes these exemptions and makes the sandbox very strong for the base system apps so it isn't affected unlike other ROMs or even AOSP

I really recommend doing some reading on what is actually going on in the security community right now

Open source also doesn't automatically mean secure. Open source by definition is just a software development model -- it doesn't make software secure or as a whonix security researcher likes to say it:

"Open source is a development model, not magic pixie dust that eradicates vulnerabilities"

- madaidan

Real world examples:

Windows is more secure/private than linux

Android is more secure/private than linux phones

If you still think otherwise then if open source actually made software secure then it should have worked by now. Why are security issues rising everyday with open source software. Logically, the number of issues should be going down, wouldn't it?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Glassrom also did extensive research over windows security in comparison to Linux

These were our results:

We were able to successfully and proactively mitigate several vulnerabilities made public for windows during the research period without even needing the relevant security patch installed that fixed them -- all this with just the tools microsoft provided alone (so no third party software at all). We even had proactive mitigations ready that would have completely halted the exchange activesync attack that happened a month ago (oh, and fyi we had windows defender disabled, it was useless)

Linux just kept getting pwned every single time. Every time there was a vulnerability our machines were vulnerable and we either had to wait for a patch or build it ourselves

I really advise anyone getting serious into security to read this http://www.ranum.com/security/computer_security/editorials/dumb/index.html

Open Source Does Not Equal Secure - Schneier on Security

www.schneier.com
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] hellcat50:
thank you for all the information, appreciate it! will read into this topic later though.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
There are no plans to make the auditor app work right now with the current signing keys

I plan to release builds signed with different keys for auditor support
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
a security vulnerability was found in the release candidate which is why there is no release announcement. glassrom will request a cve soon. information about the vulnerability cannot be made public at this time

the vulnerability is still pending severity assessment

all users on the release candidate are asked to just be patient. the release candidate still has better security than the past releases and we don't recommend users to downgrade or switch due to this announcement

edit: turns out we don't need to request a cve for prerelease software. the releases will fix the bug or remove the bad feature
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Update: the security issue has been fixed now. The actual release will be uploaded soon. Further, actions will be taken to prevent similar vulnerabilities from happening again in the future
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
I will be removing seedvault from the release. It does not back up apps correctly and if it does work it bypasses android security policy to restore applications. For an enterprise device with MDM set up it is technically possible to use seedvault to bypass the policy and install apps. They have known about this bug for almost a year now and show no interest in fixing it
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
btw this is the second advance notice that a future glassrom update will remove all support for non system accessibility services

non system accessibility services often are used by password managers and the like. however the capability itself is dangerous. often this functionality is used by malware/stalkerware to monitor phone data

low vision users need not worry as we plan to ship talkback into the system

the draw over other apps permission will also be restricted to system apps only
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] hellcat50:
appreciate you thinking about stuff like this, keep it up!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
I've been busy working on grapheneos for quite a while now and wasn't able to maintain glassrom much

I'll try to get new builds out ASAP

As you might have noticed, this project needs a lot more help/people working on it than there are currently. Let me know if you're willing to help with development
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Glassrom doesn't have a manifest. You get the sources directly from lineage and then run the shell script in glassrom-landing (copy it to the root of the source you synced) to get the sources

We are really short on development resources right now and could use some help
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
You may notice that the glassrom repos are archived. This doesn't mean we're dead, we just can't use lineage as a base anymore and are working towards an alternative option
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
The OnePlus 7 pro is no longer receiving updates https://security.oneplus.com/mend.html

The glassrom team currently doesn't have resources to provide security patches for an out of support device

Thread will be closed

We are currently looking at the new OSOM phones as a viable device to run glassrom on but you shouldn't base your buying decisions on what we say. Wait and see if we announce support
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Oswald Boelcke:
Thread has been closed on request of OP @anupritaisno1

Regards

Oswald Boelcke
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mlock420:
I like the OP lol... Gives me that no bull-ish feel.... Anyway I'm working on getting my 6t setup so I can try this one out on my 7 pro... But I'm confused will the future of ROMs not use twrp anymore? I've seen los recovery it reminds me of stock oos recovery.... Are we able to do things like flashing ROMs with los recovery or am I lost... Not to talk about recovery all day just curious as to why...
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Actually the aosp way to flash a ROM onto an A/B device is something like this:

Flash the ROMs boot.img

(Developers only) set the root of trust in bootloader and reset antirollback counter

Use the power + volume down (not sure) or whatever combo is there to reboot to the recovery

Use the newly flashed recovery to sideload the rest of the ROM

Or something a little more simpler like:

Flash the fastboot image. I can generate these if needed
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Guys please find the telegram group link in the OP and join if you're willing to test

I really need a few testers
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Here's a lineage 17.0 testing build

https://glassrom.pw/signed-ota_update9.zip

Remember that for now you must dirty flash over lineage 16.0

If you forget to dirty flash and setup wizard crashes due to the clean flash remove the sim cards, reboot and complete the setup wizard before inserting them again

Currently the stock music app, lineage themes and adb root in developer options crash

Popup camera is currently broken

Secure element HAL keeps crashing

Other than that it's pretty stable but potential upgraders should be warned that this should not be your daily driver

Get the kernel source here: https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
New build https://glassrom.pw/signed-ota_update11.zip

All bugs present in the last release have been fixed. I'm not aware of any new bugs at the moment

Glassrom P users, this can be considered release quality and might be suitable as a daily driver so dirty flashing is safe

Users of the last Q build can also dirty flash. There are no issues on dirty flashing

For users upgrading from P:

Any system modifications you might have installed were not tested obviously

After flashing the ROM you must reboot to bootloader, boot your custom recovery and reflash them. It is also your responsibility to make sure your modifications actually work on Q

Installing twrp to the ramdisk may brick your phone. Do not do this on glassrom. This is not a bug and will not be fixed
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
New build:

Changes:

Ported Linux hardened patch

Most of kspp recommendations are now satisfied

Automatic stack initialization prevents use of uninitialized memory vulnerabilities. On op7pro the implementation even covers the kernel

January security patch

TCP fastopen now works as both client and server

Ipv6 privacy extensions are enabled by default

F2FS rapid gc has been removed

Cleaned up the kernel a bit, removed some oneplus changes

Download: https://glassrom.pw/signed-ota_update12.zip
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] androidacy:
Any particular reason why you refuse to let TWRP flashed work or fix it? Really inconveniences me to have to boot it Everytime, to me the point of having TWRP is so you can flash it and not get stuck with a pretty much worthless stock recovery
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Twrp needs permissive selinux. I disable selinux development features which also gets rid of permissive selinux

Twrp not having an selinux policy fails to boot on the glassrom kernel
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] androidacy:
I mean to even get full functionality of TWRP you'd have to allow so much it might as well be permissive.

Nonetheless intentionally breaking a tool many rely on is probably not the best way to reach users; I do however respect that this is your ROM to develop as you wish.

---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------

But worth noting a custom kernel would resolve this, albeit with no support being provided from you
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
It's worth noting that you can ship SuperSU's supolicy and libsupolicy inside twrp to make the selinux policy permissive

I'm surprised this hasn't been implemented yet by anyone

I don't recall saying anything about custom kernels. Support won't be refused unless there is proof the kernel actually caused the issue

There is only one thing I won't support and it's mentioned in the OP
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] androidacy:
Probably because SuperSU is kinda dead.

Unless you can accomplish similar with magiskpolicy.....
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Read the OP. I won't even read logs if I see magisk in them

Custom kernels are fine in most cases
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
This post describes changes that occured at glassrom

To avoid spamming the forum please see that announcement here https://xdaforums.com/showpost.php?p=81647035&postcount=323
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] :
That's sounds good. The first ROM that I come to know that fails to boot with Gcraps :laugh:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] anupritaisno1:
Actually it won't out of the box but you can disable verity and it will boot

That said glassrom hasn't been tested for use with gapps so proceed at own risk