yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] acetone802000:
Hello

Thank you for your very interesting ROM

I have small questions:

Is this rom frequently updated ?

Can i update this ROM with the LineageOS ROM ?

i installed it, of course, i forgot to install GAPPS, not possible to install it after boot without to change the recovery ?

In settings, i don"t found any update menu, is it a bug with my install ?
[OnePlus 3 & 3T Cross Device Development] :
Can I remove packages from /system/app and system/priv-app without having issues with dm-verity enabled?

As you know I am using a script using several packages but I am unsure if dm-verity can be enabled....

Edit: you already answered; https://xdaforums.com/showpost.php?p=79551813&postcount=132
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
1 no, only security patches

2 no, signatures will differ so even if it is lineage you can't switch between lineage and glassrom

3 if you forgot to install gapps and you want to then you should read the documentation that came with them

4 glassrom doesn't do OTAs. It expects the user to have a more active participation in updating the system rather than just skipping through the changelog and hitting the update button
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Magisk has a mode where it can change how /system looks even if verity is enforcing. Then again magisk is not officially supported on glassrom so you're on your own
[OnePlus 3 & 3T Cross Device Development] :
Not using Magisk at the moment, so only solution would be adb with pm disable or pm uninstall --user 0 then.

But decided to keep my LOS install till Android 10 is arrived.

Thanks for all you information and help!
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Here's a glassrom build that tests android Q's system-as-root enforcement

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

This build has been tested and it boots. However you really should only try this if you know what you're doing.

I do not know of any way to disable verity reliably on such a build. I spoke with Zach and it seems magisk has a solution
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Hi guys Google is no longer releasing tags for P

This means that I'll have to generate a CVEs fixed list for the next build to show that the security patches have been applied

This will probably be the case until we get Q

September 5 security patch is coming very soon
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Sorry guys I was busy so I couldn't release it

Anyway updated bromite system webview builds are now available. I recommend upgrading if you're using it
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Sorry guys since I'm not well I'll be taking a break from development for a while

I will be back on the 20th of October
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5842226]anupritaisno1[/MENTION], take your time, hope you will get feeling better soon! :good:
[OnePlus 3 & 3T Cross Device Development] Sytis:
May I request a feature or ask for your opinion on that? As you're interested in security as well, you probably heard about all that SIM jacker fuzz going on. There is a project to scan for such intrusions but needs a specific kernel driver which this ROM seems to lack. Therefore my feature request would be adding the DIAG_CHAR kernel driver which is a Qualcomm diagnostic driver. You can read more about that here https://opensource.srlabs.de/projects/snoopsnitch
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
The glassrom kernel now has loadable module support. All I have to do is compile a kernel module. If it compiles I'll send the module to you

I'm never going to include that driver however. That driver is dangerous and misuse could potentially require a motherboard replacement
[OnePlus 3 & 3T Cross Device Development] Sytis:
Thank you very much that information, that is also a very good way to solve that request without natively compiling it in. I know what I'm doing with it but you may be right that it doesn't hold true for everyone. Thanks for looking into that :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Why is it dangerous? I tried using SnoopSnitch on LOS a long time ago and it complained about a missing DIAG driver (whatever that means) which I assume is included in OEM stock ROMs according to the FAQ.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
The same driver is used to write IMEI, mac addresses, etc to a device

Op2 and op3 both have pretty broken twrp recoveries and terrible fragmentation when it comes to efs backup implementations. Everyone has a different way to backup EFS and neither is 100% right. Even my enhanced twrp doesn't restore efs correctly. Neither does official or any other recovery for the matter. Op2 was even worse as the efs backup backed up radio firmware instead of imei

The thing is: you lose imei writing it back using qcom diag is an extremely hard task. In most cases all the service centres can do for you is order a new motherboard
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Do not be concerned about CVE-2019-2215

Glassrom fixed the vulnerability a very long time ago in the 5th march security patch

See proof: https://github.com/GlassROM-devices...ad17097#diff-95cd049d92604511c7bc79529d79d0c0

If you at least have the march 5 security patch you're safe

Further reading: https://arstechnica.com/information...ty-that-gives-full-control-of-android-phones/
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
New release

Support for loadable kernel modules

Enabled a few kernel modules: all TCP congestion algorithms and target TTL. Modules are in /system/vendor/lib/modules

Updated security patch to 5th September 2019

And that's it

Or, is it?

Since Google is no longer officially releasing security updates for P here's a neat cve list

Implemented:

============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2115 A-129768470 EoP High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2123 A-34175893 EoP High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2124 A-127320867 ID High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2174 A-132927376 EoP High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2175 A-135551349 EoP High 9

CVE-2019-2176 A-134420911 RCE Critical 8.0, 8.1, 9

CVE-2019-2177 A-132456322 RCE High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2178 A-124462242 EoP High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2179 A-126200054 ID High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2180 A-110899492 ID High 8.0, 8.1, 9

Previously Implemented:

============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2103 A-120610669 ID High 9

Not Implemented:

================

None

Not Applicable (platform source):

===============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2108 A-130025324 RCE Critical 10

CVE-2019-9254 A-130164289 EoP High 10

Kernel:

Fixed:

CVE-2019-2181

Not applicable:

CVE-2018-20669 (fixed regardless)

Qualcomm components:

The last caf tag merged in the kernel fixed all of them

No cve links. I haven't yet recovered and I'm in no interest of breaking my head over linking each

No cve lists will be given once Q is out. This is just because google isn't officially fixing 9 vulnerabilities

https://source.android.com/security/bulletin/2019-09-01.html

https://github.com/GlassROM/glassrom-verification/commit/94652305c4c2ef8930de2f90635369a57b47a503

Bromite webview was updated. All users should download and install the update manually from the glassrom server
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Seems safetynet broke

Well I've pushed an update to the zip

Users who don't use gapps don't need to download the zip

The zip itself is 100% the same so it won't fix safetynet CTS

I just rebuilt it because I needed a target files package for some analysis. I'll fix the CTS issue later using this file. Probably tomorrow

Don't even bother redownloading for now
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Updated:

Changes:

Many loadable kernel modules. Check /system/vendor/lib/modules. Have fun experimenting with modules

SYN_COOKIES enabled (linux-hardened)

STRICT_DEVMEM enabled (Linux hardened & kspp)

MODULE_STRICT_RONX enabled (kspp)

IPv6 privacy extensions are enabled by default

Restored support for running fstrim on encrypted partitions

Implemented:

============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2114 A-123700348 EoP High 8.0, 8.1, 9

CVE-2019-2173 A-123013720 EoP High 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2184 A-134578122 RCE Critical 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2185 A-136173699 RCE Critical 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2186 A-136175447 RCE Critical 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2187 A-124940143 ID High 7.1.1, 7.1.2, 8.0, 8.1, 9, 10

Previously Implemented:

============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2110 A-69703445 ID High 9

Not Implemented:

================

None

Not Applicable (platform source):

===============

None

Kernel components:

CVE-2018-19824: https://github.com/GlassROM-devices...9187984#diff-d03738d1f07e9f072864b8bee1dc14d9

Merged Google's ASB tag:

Reference: https://android.googlesource.com/kernel/common/+/refs/tags/ASB-2019-10-05_3.18

Merged in: https://github.com/GlassROM-devices...mmit/daf926b18ee9730a855d459c65545ac4bef7c098

Qualcomm components:

CVE-2019-2268: https://github.com/GlassROM-devices...f4466b8#diff-5c1b53790ce8ed717d22e058bc8305ef

CVE-2018-11902: https://github.com/GlassROM-devices...08e1645#diff-9488409cc65bfaddea9ccc1d02256acc

October 6 2019:

Kernel components:

CVE-2019-2215: https://github.com/GlassROM-devices...ad17097#diff-95cd049d92604511c7bc79529d79d0c0

Alternative mitigations already in place: CONFIG_DEBUG_LIST breaks the primitive and crashes the kernel on very old glassrom builds. CONFIG_ARM64_UAO makes exploitation harder. Glassrom has both enabled since the very first release. In other words you'd have to be on an ancient glassrom build to be vulnerable to CVE-2019-2215

Note: kspp = kernel self-protection project
[OnePlus 3 & 3T Cross Device Development] Sytis:
Did you maybe change your permissions on the webroot? Your download site and all file links give off a 403 error.

Edit: Seems to be fixed.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Yes I accidentally did that. It has been fixed
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Hey guys I missed some security patches that exist in the source but weren't mentioned in the ASB

An update to resolve those will come soon

Also I bought an op7pro so I won't be active on op3 anymore. No need to worry as the op3t maintainer is still active
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Test build https://glassrom.pw/signed-ota_update2.zip

Changes: fixed massive battery drain issues faced by a few users

Fixed poor signal issues

Added some security patches I missed

Merged Google's common kernel up to commit 706ea6f5ad467fc028f71a70b34e84144120ca92

Reference: https://android.googlesource.com/kernel/common/+/706ea6f5ad467fc028f71a70b34e84144120ca92

Merged in: https://github.com/GlassROM-devices...mmit/706ea6f5ad467fc028f71a70b34e84144120ca92

And that's it

I deeply apologize to anyone affected by these bugs
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
a recent nginx upgrade went wrong and took the webserver down

it is currently being investigated
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
I planned to release a new build today but I've decided against it

The next release will be android Q

Also a short notice about op3:

Android Q will probably be the last glassrom release I'll be doing after which the glassrom ELTS team will take over. This will probably happen by december 2020. The ELTS team is made up of volunteers and is only concerned with releasing security patches. They may release new versions but it's not guaranteed (op2 did get Android P even after I left it)

For those who are unaware: glassrom was pretty much available since the very first day the op3 was launched. That's almost 3 years of support and honestly it's getting too hard

Anyway the timeline will look something like this:

Q4 2019: beta testing for Q

Q1 or Q2 2020: Android Q is released for op3

Q4 2020 or Q1 2021: I leave op3 and ELTS team takes over

(No guarantees) Q1 2026: ELTS team abandons op3
[OnePlus 3 & 3T Cross Device Development] ajash:
???? Nice Any Fix Date / Month? 2019?
[OnePlus 3 & 3T Cross Device Development] Sytis:
My mirror (and whole network) also died a little time ago because of a hardware defect in the gateway. Will probably be back up sooner than later. Was a reminder to have some hardware backups of the routing just in case. Looking forward to Q sometime in 2020 :)
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
these are some real blockers:

black theme doesn't work

developer options menu crashes

other than that i found nothing serious on lineage 17.0
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
fix? if you believe something is broken please describe it as clearly as possible so i can look into it
[OnePlus 3 & 3T Cross Device Development] Luiscasanova78:
last update is good for daily driver?
[OnePlus 3 & 3T Cross Device Development] ΦDroid:
Yes
[OnePlus 3 & 3T Cross Device Development] ajash:
I mean any confirmed date...
[OnePlus 3 & 3T Cross Device Development] Sytis:
No one can predict how long it takes to fix nasty stuff like weird crashes of the developer menu. Another prime rule of XDA and voluntary software development in general is to not ask for an ETA. He provided a timeframe already, and in case you need it earlier, you can always grab the source and build it yourself.

I might need to factory reset my phone because the GPU seems to hang quite often and dm-verity is borked. But I don't think its to blame on the ROM.
[OnePlus 3 & 3T Cross Device Development] SuperPsycho4347:
I tried to flash this rom but got error 7 : failed to update system. Tried with with twrp 3.3.1.0, enhanced one, and 3.2.3.0. Wiped data, cache but still error 7. Preserved dm verity too.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I'd recommend posting the recovery log so the dev can review it
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
The crash was fixed and if you're interested

First the core lineage developers are already aware

Second the crash only occurs on user builds

Technical details: the exact function that crashes is here https://github.com/LineageOS/androi...565f#diff-72c68df738b3258f530259527180c07fR62 and the exact crash is

11-22 08:48:40.842 3666 3666 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.adbroot.IADBRootService.getEnabled()' on a null object reference

Well I currently have 2 ways of fixing this

First is to just change the function to always return false

The second is

if (service != null) {
// function code
} else { return false; }
}

The second is more preferable but only makes any difference whatsoever on op3. Newer devices keep their sepolicy in vendor so this code really doesn't help them at all and flashing a debuggable boot image on anything other than op3 isn't going to give you root

And this approach still has a problem. The adbroot toggle is not removed from developer options. After this hack you can open developer options but enabling adbroot will cause a crash

Lineageos is nowhere near ready. Only 5 devices are currently being used for bringup and it just so happens that these 5 have good support from the manufacturer. Other than these 5 devices something is definitely broken on everything else
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Maybe your download is corrupt

Try one of these:

Check the hashes against glassrom-verification

Enable signature verification in enhanced twrp before flashing the ROM
[OnePlus 3 & 3T Cross Device Development] SuperPsycho4347:
Thanks, I'll try later and update you.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Glassrom board just passed a new rule with a 3-2 majority in the board

As per the rule glassrom will attempt to remove digital restrictions management blobs on all devices where doing so doesn't break any feature other than the DRM itself

Widevine, clearkey and a few others may be removed from the op3. I really don't care about the Netflix users. DRM is unethical and should not have been included in the first place

Since 70% of the core glassrom board members are in agreement this will never be reversed

Glassrom will test if it is feasible to remove DRM and if yes the rule will be enforced

https://www.defectivebydesign.org/
[OnePlus 3 & 3T Cross Device Development] Sytis:
Watching Netflix on a phone is questionable in the first place anyway. I'm not that deep into the DRM story, but I know its relevant for proprietary video streams. Is it also needed for music streaming services or do those use a different measurement?
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
people protested against music drm and now most music is drm free

the vote was at 3-2 last i was here. now it is sitting at 7-0

also in response to cloudflare's privacy invasive vpn glassrom will begin blocking all incoming cloudflare warp connections as of now on all servers owned by glassrom. if a cloudflare server attempts to connect to glassrom the server will not send any response at all to it
[OnePlus 3 & 3T Cross Device Development] knpk13:
What's wrong with cloudfare's warp? I tried it out but didn't really understand what it does or how it works (the information on the internet about it wasn't very helpful) so I uninstalled it. I am using their DNS (for DNS over https and tls) though, which did make enough sense to me after reading about it.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
You have to understand that cloudflare warp allows cloudflare to perform an mitm on any website that is on their network. Since cloudflare always sits between you and the server you're connecting to they can see all the traffic and even decrypt it. And this is not a "they could if they wanted to" case. It's more like their services require them to decrypt and reencrypt again. Cloudflare then becomes a single point of failure where a compromise might reveal everything, every password, every single piece of sensitive data as it's all going through cloudflare
[OnePlus 3 & 3T Cross Device Development] JahGruva:
When are we expecting android 10 with glassrom
[OnePlus 3 & 3T Cross Device Development] knpk13:
https://xdaforums.com/oneplus-3/one...evelopment/glassrom-8-1-t3876869/post80964921
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Well it's going to take some time

Glassrom P was only made for 2 devices out of which one was discontinued

Including op3 about 5 devices are going to be running glassrom Q this time

Also glassrom isnt known for fast major version releases. O was released in October of the next year, P took until june-july of the next year

Q will definitely follow a similar pattern

I will also be releasing android 9 with the January security patch very soon
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Yesterday I managed to get op7pro 100% stable and I have a build ready that could be considered release quality

Not many bugs left for op3 either, just a few audio HAL bugs and selinux from what I'm aware

I know I haven't pushed any of my op3 related work on github yet. Will do so soon
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Okay so this is really experimental. Almost everything seems to work at first glance but I wouldn't recommend this as a daily driver at all. At least not for now

This is Android Q

New features:

Automatic stack initialization prevents many use of uninitialized memory bugs that occur in C/C++. Stack is now initialized with a 0xAAAAAAA... pattern just like bsd. This feature does not cover the kernel on the oneplus 3

Yeah that's it for now. Nothing else that's new

Caveats:

No signature spoofing support yet

Loadable kernel modules do not load at all due to build system breakages

F2FS is currently broken. Users who use f2fs should avoid this test build

For development purposes the compression ratio of the flashable zip had to be reduced leading to a huge zip file

Disabling dm-verity is not easy

To clarify:

This is a test build. It is experimental. Things will go wrong

All device sources are pushed on github

Download it here: https://glassrom.pw/signed-ota_update13.zip

Dirty flash from P is working fine but make sure you flash updated versions of any system modifications
[OnePlus 3 & 3T Cross Device Development] Har0sud3:
I'm so sorry for noob question. Can I enable encryption with Magisk installed?

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
The answer is yes

Do note that the first post says magisk won't be supported
[OnePlus 3 & 3T Cross Device Development] :
You found any code that directing something into a web address? Don't make the drama become worse if your sources is what the scammer said lol

It's a good laugh though reading the victim messages :laugh:

Thanks for the breaking news :good:
[OnePlus 3 & 3T Cross Device Development] Har0sud3:
I see.

Thank you for answering!

I'm try this ROM!
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Alright let me know if you face any problem
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Technical stuff ahead, you can ignore this post if you want to

So yes I tried to port the grapheneos patch and ended up reverting it

The only thing I ported was hardened malloc

All other features break huge parts of the system and breaking the system to make it secure is not security at least for me

I also introduced a few artificial security vulnerabilities in the system (like calling methods on null references). This is expected to crash but most of my tests did not crash the system at all with the grapheneos patch merged in. I don't know what exactly is going on and it's definitely hitting undefined behavior there

With the patch reverted my tests successfully crashed the system as expected

Tl;dr I tried porting it all but only ended up keeping some relevant parts after writing a lot of my own test cases and well, testing stuff

I also encountered a few hilarious bugs so I kept screenshots. If people are interested I can upload those here. We can have a roast [MENTION=5842226]anupritaisno1[/MENTION] montage, no issues there :)
[OnePlus 3 & 3T Cross Device Development] vny10:
Rom asking for password on boot
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Encryption probably doesn't work fine yet. I'm looking into it
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Yes I am working on getting the new kernel to work but it's not on a priority and is going slowly

Removing the DRM HAL has been proven to be a success on both op7pro and oneplus3. If all goes well expect a DRM-free ROM as promised earlier

Op3's external dependency on out of tree GCC 8 makes compilation tricky unless you break the sandbox. I'm working on getting the kernel to compile with clang and binutils from kdrag0n's llvm releases but it just doesn't boot. I have no idea as to why yet
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Glassrom is currently down. I am looking into it
[OnePlus 3 & 3T Cross Device Development] anupritaisno1:
Oneplus 3 is not at all stable on Q. We might be looking at the unlikely case oneplus 3 never gets anything newer than P

The glassrom server is dead and due to the current crisis there is nothing that can be done to get the download server back

Also I can't tell for sure how long this will last. I'm requesting the moderators to close this thread as there is no ROM to download, at least for now

Glassrom will be back for op3 in the future
[OnePlus 3 & 3T Cross Device Development] Timmmmaaahh!:
[Thread Closed] as requested by OP. Thank you for your participation and have a great day!