yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Original Android Development] anupritaisno1:
Most of my time went in the P bringup and fixing bugs on Oreo so I had no time to work on the September security patch

Please be patient, update is coming soon
[OnePlus 2 Original Android Development] anupritaisno1:
Since the last week or so, a lot of users are joining and we suspect that most of them are bots.

For now we are making the discord chat rules stricter. Any newcomer who fails to message an admin or send a message in the chat after joining will be banned

Do not message memeko or apex. They manage the servers and the infrastructure of glassrom and will ignore you if you message them

Discord might ask you to verify your phone number and email before you can post in the chat. You should message an admin to get this restriction lifted if you do not want to provide your phone number or email to discord

If you're coming from the r/oneplus, oxygen updater or other oneplus related discord servers (except the op2 family) this restriction does not apply to you as we already know that you're not a bot
[OnePlus 2 Original Android Development] anupritaisno1:
https://transfer.sh/XnurC/MonochromePublic.apk

This is our build of chromium

Remember that you cannot sign in to Google. This is not supported

Bugs: I added some code to make the browser skip the welcome screen but Google changed their compiler a little and so on the first start the browser shows a blank welcome screen for about 2-3 seconds before actually skipping it
[OnePlus 2 Original Android Development] anupritaisno1:
Glassrom's server has been hit by a very large ddos attack

Currently our provider is trying to handle all the load but it's still too early in the morning in UK, where our provider is based

Considering the situation I can't tell when the server will be up again but it will be up soon
[OnePlus 2 Original Android Development] anupritaisno1:
Update: I finally found the cause of the first issue

System server was preoptimised with speed-profile and the ROM expected the optimisation level to be everything. Selinux blocked system server from being optimised and this caused the freeze

Fixed in commit https://github.com/GlassROM-devices...mmit/48094922de3bc72d82d22915b20e33ba2d65dce6 upstream
[OnePlus 2 Original Android Development] samael07:
OK, but how to change it?
[OnePlus 2 Original Android Development] anupritaisno1:
Updated:

Fixed lots of bugs

October 5 security patch

Improved battery life

Added dm-verity for the vendor partition

Huge performance improvement for hardware-accelerated encryption users

More optimisation
[OnePlus 2 Original Android Development] Zaykov:
Any screen shots for this build ?
[OnePlus 2 Original Android Development] anupritaisno1:
We haven't had any reports of people shooting their screens after flashing this build but we'll keep you updated
[OnePlus 2 Original Android Development] anupritaisno1:
Glassrom's download server has been upgraded to only reply to clients with TLS 1.3 support. Please make sure you update your browser

For android: chrome 70 and above works

For windows: chrome 70 works, 71 is recommended

For linux: chrome adds an entry to your package manager. Consult your distribution's documentation on how to use your in-built package manager to update
[OnePlus 2 Original Android Development] tbaybucs:
You sir win the internet today !
[OnePlus 2 Original Android Development] samael07:
After installation, the system falls into the bootloop on the start screen.

Since this is not my first installation, I have reason to believe that it is ROM's fault.

Has anyone noticed a similar symptom?

I passed from the original Oxygen 3.6.1 and from the latest LineageOS.

---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------

Has this been repaired in the latest version? And if not, how do you change this setting yourself?
[OnePlus 2 Original Android Development] anupritaisno1:
The vendor partition is protected with dm-verity. You are the first to trip it though. What have you installed other than the ROM that actually wrote to the vendor partition?

You can flash the dm-verity disabler tool which is there on XDA and boot
[OnePlus 2 Original Android Development] samael07:
I competed with OxygenOS 3.6.1.

In sequence:

- I've downloaded recovery-vendor

- I made a factory reset and format

- restart to recovery

- I copied your ROM + opengapps in the micro version

- I installed both + restart

And bootlop. After about 10 minutes, restart, install Oxygen again, then LineageOS and repeat the whole operation. With the same effect.
[OnePlus 2 Original Android Development] anupritaisno1:
If it shows the bootanimation and then goes to TWRP or keeps looping then it is asking you to format data (not wipe) from wipe > format data

If it loops on the oneplus logo, you're somehow the first person who managed to trip dm-verity. You can flash something like https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389 to be able to boot again
[OnePlus 2 Original Android Development] jukyO:
I had the same regarding boot logo bootloop....advice was to tick "Mount system as read only" in TWRP before flashing. That solved the issue.
[OnePlus 2 Original Android Development] Vishal Gharat1:
[MENTION=5893666]Anuprit[/MENTION]aiso1 is there any way to add volte on Android 9.0 based roms
[OnePlus 2 Original Android Development] anupritaisno1:
It appears that IMS is not covered by project treble so a new IMS blob is required to support volte

Sorry, I can't do much unless some device with a very similar radio gets P
[OnePlus 2 Original Android Development] Vishal Gharat1:
So are you working on project treble for op2?
[OnePlus 2 Original Android Development] anupritaisno1:
I tried but the camera and sensors break when I try to enable treble

As for volte, i don't even use jio so I wouldn't really know about it
[OnePlus 2 Original Android Development] dmilz:
Stupid question..

Is this ROM transparent...(like transparent glass)?
[OnePlus 2 Original Android Development] anupritaisno1:
Not really but you might be able to use a substratum theme to achieve the desired result
[OnePlus 2 Original Android Development] dmilz:
Alright, thank you
[OnePlus 2 Original Android Development] anupritaisno1:
Glassrom is not affected by the hidepid vulnerability detailed by the magisk developer

Please do not flash random magisk modules to fix nonexistent issues. Even if you're on a glassrom build from 2016 you are not affected by this bug

A new update is on the way. It will be released tomorrow

------

Ref: https://medium.com/@topjohnwu/from-anime-game-to-android-system-security-vulnerability-9b955a182f20

------

OT: fate series sure does confuse me xD. Anyone playing that just has some persistence. https://youtu.be/wnVwcUhxt1k <---- fate fans will hate me for this

Since I am building the ROM I have way more control than magisk over how things get validated and I have better ways to bypass detection of such apps. I can even use actual dm-verity if an app needs that. Contact me on discord if you have an app that performs stronger checks. You can also build glassrom yourself. By default, glassrom enables additional security when compiled from source (like dm-verity) which I can't add in release builds for obvious reasons

------

What are those huge signed OTA update files and why do none of those boot?

They are snapshot builds generated for testing purposes. You are not supposed to flash them however if you do

You have to tick mount system read-only before you flash them

Flashing anything after the snapshot ROM, even flashing gapps or mounting system without even writing anything to it will cause a snapshot build to refuse to boot. Basically snapshot builds do not like being modified, will detect this at boot and give up

Snapshot builds are experimental. You may lose all of your data or a lot worse could happen to your device. No support will be offered if you flash these huge builds.
[OnePlus 2 Original Android Development] anupritaisno1:
Glassrom has moved to glassrom.pw, please update your links
[OnePlus 2 Original Android Development] anupritaisno1:
New build is coming soon
[OnePlus 2 Original Android Development] anupritaisno1:
Okay everyone, new build is out

Changes

Optimisations

December security patch

Added fast charging thanks to aviraxp and shreyanshlodha

Went back to newer mode of hardware-accelerated encryption

Tripndroid is now the default I/O scheduler

Added kcal back, invert screen is working

Disabled input boost because EAS doesn't need it

Miscellaneous security updates

Tuned kernel for sd810

Fixed the bootloop on bootlogo bug

There is no incremental OTA available due to huge changes
[OnePlus 2 Original Android Development] anupritaisno1:
If you're unable to reach the download server, make sure you have chrome 71 or the latest version of Firefox

Other browsers are currently not supported

The glassrom server can be reached to with DNSSEC DANE. Try it

Also https://github.com/GlassROM/glassrom-verification is a repo that contains a sha2-512 hash + releasekey + gpg key of every maintainer to help you verify that the build you downloaded was indeed released by glassrom
[OnePlus 2 Original Android Development] Gulbuddin:
My friend can you please inform me about the workability of cast function? So far none of the roms that I've tried seem to support it.
[OnePlus 2 Original Android Development] anupritaisno1:
I'm sorry but my op2's WiFi hardware broke a long time ago so I can't tell for sure
[OnePlus 2 Original Android Development] samael07:
Tnx:)
[OnePlus 2 Original Android Development] Surya Chandra:
Hey, I am not getting that fake cache thing. You are telling that I won't be able to flash OTA incremental updates if I dont flash custom recovery which is made by you with "fakecache" in the name. Is that right?

Please tell me if this is the process to make sure everything works

1) make backup of everything.

2) flash your modified recovery

3) run that code given by you in terminal

4) erase everything

5) flash ROM and gapps

6) Reboot.

Is there anything else I should do

Note: I am currently running another custom ROM with latest twrp

And what if I ignore the fake cache thing and just flash the ROM just like any other ROMs? Should I flash entire ROM every time it gets updated or can I flash OTA incremental zip manually just like any other zip file?

And one last thing

Consider I have flashed the fake cache recovery and run the code and did everything according to the instructions. Do I need to perform any other alterations to switch to any other custom ROM?

Please help me. I am new to this thread and ROM
[OnePlus 2 Original Android Development] anupritaisno1:
Announcement for the next build

Touchboost interferes with EAS's assumptions and wastes battery so I disabled it

However it seems that doing so has caused random stuttering for a few users

I will be releasing a build with the fix for this issue this week

The other reason for the stutter seems to be that tripndroid only handles one task at a time. I have changed it's behaviour to handle 16 tasks at once to solve some of the stuttering

Kcal invert screen works but once enabled it cannot be disabled without a reboot. Please use the livedisplay invert mode instead which is a lot more stable

Livedisplay might interfere with kcal. Go to settings > display > livedisplay and make sure it's set to disable all adjustments. Also make sure that reduce power consumption is disabled too
[OnePlus 2 Original Android Development] anupritaisno1:
Glassrom is down for maintenance. Sadly it looks like it will take 1-2 days before the server will be up again
[OnePlus 2 Original Android Development] anupritaisno1:
Updates time

I'll be releasing a new build soon

This release only contains a few fixes:

Introduced avirax's fingerprintd thaw hack. This will allow the device to be unlocked by the fingerprint sensor faster just like it was on N

I mixed some code into tripndroid to improve performance. I made it prefer synchronous over asynchronous just like maple and mixed a few of boeffla's zen commits into it. The end result is that it's smooth and a lot more tolerable especially when the last build disabled input boost

I haven't had any reports of battery drain from testers yet

Sadly, no incremental OTAs again for this release but there will be one for sure for the next release

As for P, development is in progress
[OnePlus 2 Original Android Development] Shree@:
Add volte feature in your next Pie build that will be very greatful
[OnePlus 2 Original Android Development] anupritaisno1:
Apparently adding volte on P makes the entire radio break. Just spoke with the lineage maintainers about it

Sorry but I'd prefer a working cellular connection instead of 10,000 VoLTE hacks and unreliable radio
[OnePlus 2 Original Android Development] rituj_b:
Can't reach the download server yet.
[OnePlus 2 Original Android Development] anupritaisno1:
It seems that the OS I use on the server (Debian) released a bad initramfs-tools update and that broke boot so the server is unable to start

I will have to check after the holidays sadly
[OnePlus 2 Original Android Development] Gulbuddin:
Great news to end 2018!! Yay!!
[OnePlus 2 Original Android Development] anupritaisno1:
I mean, the fact that the both of us are here on almost new year's day already implies that we are have no plans at all for new years

Anyway, I installed a faulty system update and the server doesn't boot so until I fix that I can't promise a build right now

I will update you once I fix the damage
[OnePlus 2 Original Android Development] Gulbuddin:
Happy new year
[OnePlus 2 Original Android Development] anupritaisno1:
The glassrom server is partially up

Currently it only has the closed beta build and flashing it is a very bad idea

I am working on recovering all of the data

A release build will be available as soon as closed beta testing is over
[OnePlus 2 Original Android Development] anupritaisno1:
Yes, I know that the only recovery image that can be used to uninstall glassrom is currently not on the server

I am working on it
[OnePlus 2 Original Android Development] AL2000EX:
Ok, just to confirm, if I'm running a really old build, I can just flash the regular recovery, then flash the full zip normally? No need to mess backup scripts, fake cache, etc etc?
[OnePlus 2 Original Android Development] anupritaisno1:
For now you have to setup the fakecache

If the instructions confuse you then you basically have to run these commands once:

dd if=/dev/zero of=/data/fakecache bs=1G count=1

mke2fs -F /data/fakecache

Do NOT run these commands again unless you wipe/format data

Make sure you have entered your decryption passphrase and that /data is mounted before you run these commands

Now reboot back to TWRP and run

mount /data/fakecache /cache

Now you can flash the ROM

Btw please read the previous posts. The glassrom server lost all data due to a faulty system update and the only build on the server is currently the closed beta snapshot. You should not be flashing that huge 1.2 GB file unless you know what you are doing

A release build will be made available very soon
[OnePlus 2 Original Android Development] anupritaisno1:
Oh and as long as you are on glassrom you can flash any new glassrom build without having to worry about compatibility. It will boot

The first boot takes up to an hour
[OnePlus 2 Original Android Development] anupritaisno1:
Okay guys I'm updating the files on the glassrom server now

Since I'll be moving files around please don't download anything until I update this post

Edit: okay we are done
[OnePlus 2 Original Android Development] anupritaisno1:
Updated:

Tripndroid now prefers synchronous over asynchronous

Fingerprint unlock is faster now

There are not many changes in this update. I just built it because the old one was lost

This update was built on arch linux. I usually use Debian sid but the newer compilers on arch might introduce some bugs. No bugs are currently known but please report if you find any
[OnePlus 2 Original Android Development] anupritaisno1:
Please remember to tick zip file signature verification before you flash

Sha512sum provides integrity

Signature verification provides authenticity
[OnePlus 2 Original Android Development] anupritaisno1:
The glassrom-verification repository has been updated with all the hashes

What's new in the firmware zip? I fixed a small typo

The backup and restore zips? I signed them with my key so that TWRP can do signature verification against them
[OnePlus 2 Original Android Development] anupritaisno1:
Guys op2 will no longer get security patches

Google has decided to officially kill sd810 and the 3.10 kernel. No further security patching is possible

Glassrom will still continue to get security patches merged into the ROM but I will set the security patch date to 5 December 2018 because that is the last security patch date the sd810 can advertise

So yes the security patch date on glassrom will always be 5 December 2018 from this point onwards and if op2 gets P it will still have this exact date

I will continue to merge security patches into the ROM

Why?

Because setting the security patch date higher would give the user a false sense of security. There are 7 vulnerabilities with the severity rating "critical" that need to be fixed to advertise a security patch level of 5 January 2019. Op2 is vulnerable to every single one of them however I was just able to fix one

Any ROMs advertising a security patch higher than this are obviously just passing the date set in the source. That isn't the real security patch date
[OnePlus 2 Original Android Development] anupritaisno1:
In other words you are no longer secure and glassrom can no longer make any guarantees about security

If you want security it might be time to invest in a new device
[OnePlus 2 Original Android Development] ΦDroid:
Any thoughts on the Librem 5?
[OnePlus 2 Original Android Development] anupritaisno1:
I can't personally recommend anything I've not tried myself

Discuss security in #linux-hardened on discord
[OnePlus 2 Original Android Development] nelson pansare:
Hey ...thanks for all the work you did for oneplus two i really appreciate the hardwork you did... im not questioning your honesty but i googled about this whole snapdragon 810 not being supported by google anymore... and failed to find any material regarding this...can you please provide the source from where you got this news that 810 won't be supported for security patches anymore..? ThaNk you in advance
[OnePlus 2 Original Android Development] anupritaisno1:
Google does security patches for 3 years

2 years of major version upgrades and one year of security patches

The last update for angler was the 5th December 2018 patch so security stops there

Google also deleted all kernel sources for the 3.10 kernel branch

Regarding those "critical" vulnerabilities I sat and fixed those critical vulnerabilities that were in the ASB so I'll release a build with those changes in

However there is no official ASB for the sd810 anymore and the maximum I can do is fix the vulnerabilities in the ASB which is obviously not enough to advertise a higher patch level

From now on every release changelog will contain a CVEs fixed section instead of a security patch date. You can look up the CVE ID on https://cve.mitre.org
[OnePlus 2 Original Android Development] nelson pansare:
Thank you...that cleared lot of doubts... thank you again for your contribution... Cheers
[OnePlus 2 Original Android Development] anupritaisno1:
Updated:

Changes:

Dropped hacks for the memory corruption issue and actually fixed the issue

Kernel uses unaligned memory accesses again

Some fixes for tripndroid

vsync is enabled by default

More optimisation

Security:

Implemented:

Kernel:

CVE-2018-10876 A-116406122 EoP High ext4 filesystem

CVE-2018-10880 A-116406509 EoP High ext4 filesystem

CVE-2018-10882 A-116406626 EoP High ext4 filesystem

CVE-2018-13405 A-113452403 EoP High Filesystem

CVE-2018-18281 A-118836219 EoP High TLB

CVE-2018-10877 A-116406625 ID High ext4 filesystem

ROM:

CVE-2018-9582 A-112031362 EoP High 8.0, 8.1, 9

CVE-2018-9583 A-112860487 RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9584 A-114047681 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9585 A-117554809 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9586 A-116754444 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9587 A-113597344 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9588 A-111450156 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9589 A-111893132 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9590 A-115900043 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9591 A-116108738 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9592 A-116319076 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9593 A-116722267 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2018-9594 A-116791157 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

Not implemented:

Kernel:

none

ROM:

none

Not applicable:

Kernel:

CVE-2018-17182 A-117280327 EoP High Memory Manager

ROM:

none

CVE-2018-17182 -> bug in vmalloc driver but op2 doesn't use this driver so exploiting this vulnerability is not possible

Additional vulnerabilities have been fixed which were not connected to the ASB. Please refer to github for more details
[OnePlus 2 Original Android Development] ΦDroid:
I believe we are missing sha512 sums? Can you please generate those for us?

Thank you for the build!
[OnePlus 2 Original Android Development] anupritaisno1:
The glassrom server is just working as-is for now. I'm still restoring data because the recent systemd 240 bugs caused a lot of data loss so you might have to wait a bit for the sha512sum
[OnePlus 2 Original Android Development] anupritaisno1:
Thanks for this post

I realised that sometimes this kind of stuff can happen and sha512sums might not be available

To solve your issue I came up with this solution:

From now on glassrom installation zips will flash their own TWRP. This TWRP will be different from the one on my server and it will only accept glassrom's signing keys when zip file signature verification is enabled

In other words from now on you can just tick zip file signature verification and be sure that the ROM is not corrupt

This approach also allows one more thing: downgrade attack prevention. From now on glassrom will check the current build date before starting the flash and refuse to flash if the version of glassrom you're flashing is older than the version of TWRP that the previous glassrom build installed

I believe this should solve the issue

Anyway I'm really sorry about the hashes not being available for this release. The next release build will come in a few hours and sha512sums will be available on the server and github for that