yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Original Android Development] anupritaisno1:
Also guys new twrp is out and decryption works well on that one. Sorry because I forgot to announce earlier

Also on my server you will see a recovery-vendor.img. That is for the next build of glassrom which will add the vendor partition. You can flash it but since I haven't released instructions on how to use it it won't work at all
[OnePlus 2 Original Android Development] anupritaisno1:
If you join the discord group you must send at least one message so that we can confirm your account

You don't have to be an active member, a simple hi will work because we need to verify that bots aren't joining discord

User bots are against discord's TOS and we have to report them

Once you have the member tag in the discord server you don't need to be active at all but this confirmation step is required
[OnePlus 2 Original Android Development] anupritaisno1:
The next build of glassrom will bring full hardware accelerated encryption support

Those who flashed glassrom in July will be able to use hardware accelerated encryption after the upgrade

Those who were glassrom users before July will still use software accelerated encryption. To use hardware accelerated encryption you'd have to go to twrp, format and then reboot. You can't switch between hardware accelerated and software accelerated encryption. They're totally different

What to do?

Do you plan on using glassrom, are an old user and plan to switch ROMs?

Use the old software accelerated encryption you still have

Do you otherwise don't plan to switch from glassrom?

Format data to use hardware accelerated encryption

Are you a new user who doesn't plan to switch from glassrom?

Use the new hardware accelerated encryption

Are you a new user who's unsure?

Request a special build with software accelerated encryption then flash the release build. It will automatically fall back to the software accelerated implementation even if the ROM supports hardware accelerated encryption

As for twrp, it doesn't matter at all. I recommend using my twrp for extra stability regardless of what ROM you flash
[OnePlus 2 Original Android Development] anupritaisno1:
What's the huge difference?

Software encryption causes a little bit of lag and heat and doesn't have hardware support to delete the encryption keys during a brute force attack

Software accelerated encryption works on all ROMs and beats hardware accelerated encryption in terms of cross compatibility

Hardware accelerated encryption is indistinguishable from an unencrypted device, doesn't cause any lag or heat and erases the encryption keys if a brute force attack is detected

Hardware accelerated encryption only works on glassrom and cosmic-os
[OnePlus 2 Original Android Development] anupritaisno1:
New build coming soon

Major changes:

Added the /vendor partition

SIM card switcher now works

Full hardware accelerated encryption support + legacy encryption fallback

Device will now boot faster
[OnePlus 2 Original Android Development] anupritaisno1:
New update is out

For glassrom, instructions are simpler

Flash the recovery-vendor image

Wipe cache (why? Cache moved to another filesystem, the ROM's cache is now in /data/cache however a cache partition is required to be able to correctly flash the ROM so a small 3 mb partition is used as buffer space for flashing the ROM, wiping this cache doesn't affect the ROM's cache)

Reboot recovery

Flash the ROM like any other build and reboot

After first boot it might lag a little. That is normal, it will be okay in a few minutes
[OnePlus 2 Original Android Development] AtzeDeVries:
i think i'll try this tonight. There are two recovery files (recovery.img and recovery-vendor.img). I think i only have to flash the -vendor.img correct? So the recovery.img is just the default recovery image?

thx
[OnePlus 2 Original Android Development] anupritaisno1:
Incremental OTAs are coming out next build

Further instructions will be given later
[OnePlus 2 Original Android Development] anupritaisno1:
The OTA server is down due to a DNS server outage, it'll be back in a bit

DNS is needed for proper certificate verification so your browser will be unable to verify the website's https certificate even if I bring it up
[OnePlus 2 Original Android Development] anupritaisno1:
And we're back up
[OnePlus 2 Original Android Development] anupritaisno1:
Oh I forgot to mention this

Source means your current system

Target means the system you're upgrading to

So your target becomes the source for the next (incremental) OTA
[OnePlus 2 Original Android Development] anupritaisno1:
Redisigned thread, looks a lot better than what it was before
[OnePlus 2 Original Android Development] anupritaisno1:
In about 6 hours from now the glassrom download server will go down for maintenance

Maintenance will start on or before 12:00 IST and might last for 24 hours
[OnePlus 2 Original Android Development] anupritaisno1:
Maintenance started, server will be back soon
[OnePlus 2 Original Android Development] anupritaisno1:
We're back
[OnePlus 2 Original Android Development] anupritaisno1:
I'm recalling recovery-vendor

It is causing inconsistencies in the flashed ROM and causes more issues than it fixes

The fakecache method will be the only supported way to get glassrom on

I'm working on a better workaround so please bear with me
[OnePlus 2 Original Android Development] anupritaisno1:
If you're using recovery-vendor get rid of it and switch to recovery-fakecache and reflash your ROM right away!
[OnePlus 2 Original Android Development] anupritaisno1:
Discord is currently down in a few countries so you might not be able to join the discord chat right now
[OnePlus 2 Original Android Development] AL2000EX:
Just to confirm, flashing this rom for the first time requires a proper /data format and not just a generic wipe, right? And if so will formatting to f2fs in the meantime interfere with hardware encryption or anything looking forward?
[OnePlus 2 Original Android Development] anupritaisno1:
F2fs isn't supported at all because our kernel version 3.10 is EOL and upstream f2fs changes required for O can't be brought to our kernel without breaking a lot of stuff

If the ROM gets stuck at boot for more than 30 minutes you'll know that a wipe is required. If this was AOSP it would have formatted the partition and continued with boot but I removed that code so that data isn't lost. It rarely happens that you have to format data btw. Encryption is in place and no data loss occurs unless it was interrupted by the user
[OnePlus 2 Original Android Development] anupritaisno1:
August 5 security patch is coming today
[OnePlus 2 Original Android Development] anupritaisno1:
New update is out

Changes:

August 5 security patch

Brought back android M's AOT

Fixed virtual disk

Fixed fragmentstack

Performance improvements

Fixed the issue with recovery-vendor. It can now be used again

This build might take a long time to boot because I brought back full AOT. Just flash it and wait. Some users report that boot takes just 10 minutes while some report that it can take more than 40 minutes. It all depends on how many apps you have installed. This is only for the first boot. Subsequent boots will be unaffected
[OnePlus 2 Original Android Development] anupritaisno1:
I'll start generating the folders for incremental OTAs on the server now
[OnePlus 2 Original Android Development] anupritaisno1:
Also now that TLS 1.3 is out the glassrom server has been updated to support the RFC version. Unfortunately no browsers support the RFC version at the moment but you can test it out with your own openssl build
[OnePlus 2 Original Android Development] anupritaisno1:
Why bring M's AOT in? Doesn't it increase app install time and boot time?

It does but it fixes 2 things:

It firstly makes exploiting certain spectre-like (I said spectre-like, not spectre!) in JIT harder

It makes it harder for malware to compromise the system by injecting malicious code into dalvik. If you have gapps then droidguard and safetynet make it even harder

It makes the system faster. There's nothing to optimise so the JIT interpreter almost never runs. This helps a lot in performance and also saves battery

Why is JIT still active if AOT is making it useless?

AOT isn't making JIT useless. Android deletes dalvik for apps that are inactive. If you were to suddenly launch an app that has no dalvik associated with it then JIT is the only fallback otherwise you'd have to wait 5-6 minutes for the app to launch. Also some instructions in certain apps are so large that AOT can't optimise them. JIT can avoid a sudden performance loss in these cases. This usually happens for games but also can happen for certain Google applications and messaging apps
[OnePlus 2 Original Android Development] anupritaisno1:
Also getting rid of JIT fixes 3 common issues

The classic android system battery drain. That is because AOT didn't have any time to have kicked in and preoptimised data is unavailable so JIT is processing everything. This causes battery drain. To the user it's just huge battery drain and android system on the top of the battery charts for no reason. This usually happens after a system update or a clean flash and goes away within a week. This will no longer happen

Getting rid of JIT also fixes the battery drain even when connected to a charger issue

Also ever had your phone heat a lot when it was at 100%, plugged in, full and idle? AOT kicks in when the phone is idle so that the system can finally get rid of JIT after a system upgrade or clean flash. By forcing it at boot this stage is avoided and the phone doesn't heat up
[OnePlus 2 Original Android Development] anupritaisno1:
I updated the kernel today

Expect a follow-up update soon

Changelog:

Updated sdfat driver to 2.0.8 (LineageOS version)

More security patches

Minor bugfixes
[OnePlus 2 Original Android Development] anupritaisno1:
Announcement for users:

We have a guy who's trying to mod the glassrom kernel and make a custom kernel for glassrom. You can expect a few more modding options then

Announcement for developers:

We love such mods and would like to see your creativity. If you have some good ideas for mods you can share them on our discord. We'd like to see what you can do with our sources. So go ahead and innovate!

Let your imagination run wild
[OnePlus 2 Original Android Development] anupritaisno1:
Server's going down for maintenance today. When it will be back up the new update will be ready. Incremental will also be available

About 6 hours before it goes down
[OnePlus 2 Original Android Development] anupritaisno1:
Okay everyone we're back

Changelog is 2 posts above, new build are out and the backup.zip and restore.zip files are in the tools folder
[OnePlus 2 Original Android Development] anupritaisno1:
I'd like to hear your feedback about the 38 mb incremental OTA

Have fun flashing it, it will upgrade your system exactly to the version in the full zip

Read the instructions carefully

Also if you accidentally downloaded the release zip instead of the full zip just extract the release zip, open META-INF/com/google/android/updater-script and remove lines with these in them

mount(/system args)

backuptool backup and restore commands

Put all files back into a zip and flash it and then flash the incremental OTA

Also use the backup.zip and restore.zip files to backup your gapps and other mods before you update your system and then copy them back
[OnePlus 2 Original Android Development] erzherzog:
The installation always fails with error 7. I tried full and incremental image as well as vendor and fakecache recovery.
[OnePlus 2 Original Android Development] anupritaisno1:
Please read the first post carefully. The recovery is unable to mount the cache partition on its own so you must manually mount it everytime using

mount /data/fakecache /cache

You have to type this in the TWRP terminal or adb shell

Also read the instructions given in the first post if you haven't created the fakecache yet
[OnePlus 2 Original Android Development] anupritaisno1:
Another bugfixing update is planned in August

Probably will be released tomorrow
[OnePlus 2 Original Android Development] anupritaisno1:
Glassrom will soon be getting a second server

So the next time we need to do a maintenance the backup download server will kick in and there will be a download server up to answer your requests before the main one comes up

This means that downtime will be seriously reduced. You might have to clear DNS cache though when that happens

Here's how it'll work

Main and backup server both up -> both handle requests -> main goes down for an update -> load is shifted to backup -> main comes up -> backup goes down for an update -> both are back up

This means that there will always be at least one server to serve downloads
[OnePlus 2 Original Android Development] M03:
who's monitoring or maintaining the servers?

and where are they located (because it matters for GDPR)

I'm happy to help, :fingers-crossed:
[OnePlus 2 Original Android Development] anupritaisno1:
All of them are in Germany and Sweden

As for GDPR, since we don't collect any user data at all I don't really think most of its terms would even apply to us. You can see that in the first post it is said that zero user data is collected

As for your questions

I monitor and maintain all the servers. Most of the servers are updated weekly. Nobody else ever connects to the servers. Nobody monitors who's connecting to the server however our provider does look for potential abuse patterns (like DDoS, etc) however that is done on our provider's side and if any abuse is detected it is just passed on to the appropriate people who are in charge (eg the police) and we never get the data

The servers are set up to automatically update themselves using unnattended-upgrades. Nginx is source-built with minimal options and we use openssl from the master branch. We use either torvald's tree or linux-next as the server's kernel (updated weekly)

Also in nginx we have logging off everywhere so we really collect no information at all about who's connecting

https://securityheaders.com/?q=https://glassrom.botstack.host&followRedirects=on you can also check that we aren't setting any cookies either on the sly
[OnePlus 2 Original Android Development] anupritaisno1:
[MENTION=7892165]Sec Karma[/MENTION] join the discord for GDPR related stuff and questions about our privacy policy. Also no matter how many times you ask we do NOT collect data and we never will
[OnePlus 2 Original Android Development] anupritaisno1:
Updated

Major changes

Went back to CAF HALs

CAF RIL is back

Doubled the compression streams for zram

Fixed a bug where USB mass storage and usb debugging were not working
[OnePlus 2 Original Android Development] anupritaisno1:
With this release a firmware folder is added

It upgrades your firmware to OOS 3.6.1

Bear in mind that it flashes all partitions that can be flashed and updates them. That means if you use recovery-vendor, it will undo changes to the cache partition and you'll have to format cache again in the recovery to be able to flash the ROM. Neither recovery-fakecache nor the ROM are affected

Since it is no longer safe to use TWRP after the firmware flash (as the partition that holds the firmware needed for encryption gets unmounted) and also the only way to cleanly wipe the misc partition is to do a misc reboot, the script reboots automatically upon success. No, rebooting to TWRP after the script runs is not possible currently

The script also produces no output whatsoever

Remember to update your recovery to the latest version and verify the sha512sum or tick zip file signature before flashing the firmware. You don't want to accidentally flash a corrupted firmware zip
[OnePlus 2 Original Android Development] M03:
lmao first thanks for dedicating a little bit of your time writing all that. it is indeed crystal clear and no proofs needed i know you here but you don't know me :good: .

Second, my intention from what I asked is to help out "voluntarily" (if possible) maintaining the servers (security and monitoring wise). we can pm for more information about my domain field and expertise if you want ;) .

aw and i'm already a discord member :highfive:

P.S: according to ssllabs your server's "let's encrypt certificate" seem to fail when doing a handshake when requested on some mobile phones. I can help fix that issue if you're interested.

Have a good day!

Karma
[OnePlus 2 Original Android Development] anupritaisno1:
Yeah the handshake failure is intentional. The test at ssllabs seems to just take a list of supported ciphers and tries using those to handshake. The main issue with this is that any old android device having an updated version of chrome or any other browser can reach the website but the ssllabs test doesn't test this at all
[OnePlus 2 Original Android Development] Scarface05:
Hi,

Can someone please help me with flashing this ROM?

I'm currently running PixelExperience and have flashed the recovery-vendor.img. I was reading that we should be moving towards recovery-incremental? Any simplified steps? :/ I just really want to give this ROM a try.

Thank you.
[OnePlus 2 Original Android Development] anupritaisno1:
You mean the fakecache recovery? That's only if you can't download 600 mb OTAs and would like a 50 mb OTA instead. It's for usage when downloading a huge file is almost impossible. Since it's a hack the method of flashing is going to be complicated
[OnePlus 2 Original Android Development] samael07:
I think the question is a lot "simpler" - how to upload / install rom "to the test"?

This romu can not be used FOR TRYING. After encrypting the partition, going back to "ordinary" roms is, to put it mildly, difficult;)

---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------

However - the rom itself is great!:):):)
[OnePlus 2 Original Android Development] anupritaisno1:
It's planned in a future release

For now if the ROM encrypts the device it will use dm-req-crypt but for compatibility reasons the old dm-crypt APIs are still supported

You could technically encrypt the device on another ROM to force the old crypto to be used when you flash this. Then you can switch between ROMs with ease
[OnePlus 2 Original Android Development] anupritaisno1:
[MENTION=1158368]samael07[/MENTION] do note that using the legacy encryption means that you'd be missing out on one feature, it's not a really important feature but

Google has added support in P (and also Oreo with the newer security patches) to flash ROMs without ever decrypting data. The updater app accesses the disk raw and tells the kernel to selectively decrypt blocks of data containing the system update. Then the misc partition is updated with a map to each of these decrypted blocks and the recovery reads these and flashes OTAs without ever decrypting data

This however is only possible with hardware accelerated encryption and since the feature is very new implementation is only planned and doesn't exist right now. The updater app can detect which dm-crypt API is used for encryption and will fallback to the old way of having TWRP decrypt data to flash the ROM

Currently the updater app is defunct

If you're on my new TWRP builds then this feature is already supported, it just has to be added to the ROM
[OnePlus 2 Original Android Development] samael07:
I have 3 problems:

- for some time OP2 has been suspending / blocking. The screen is black, does not react to any keys - I can wake up with the connection to the power supply only (since then we have been carrying a cable and Powerbank, but ... this is not a solution).

- the day before yesterday, "the clock froze." In the morning ... he was announcing 19:47 but on the previous day ...

- battery, battery, battery ....... Poor. It has never been good, but now it is very bad. And I replaced the batteries, maybe four months ago....
[OnePlus 2 Original Android Development] vignesh95:
Hey!

Since there are 64 gb space in our op2 can't we use some of it from internal storage and convert it as vendor partition ?
[OnePlus 2 Original Android Development] anupritaisno1:
There's always a risk of breaking something terribly doing that with no way to go back

Also what will people with the 16 GB version do?

Remember that I can't do anything that can actually do irreversible changes to a device
[OnePlus 2 Original Android Development] vignesh95:
May be you can check this out.

https://xdaforums.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734

For 16gb users it's up to their choice.

If op2 got treble mostly none of us would like to reverse.
[OnePlus 2 Original Android Development] anupritaisno1:
Treble isn't adding a vendor partition. We could have the vendor in /system/vendor and still get treble working

Treble is when all HALs run in their own process and communicate to each other using a common interface. Currently our camera and sensors HAL are unable to run in their own processes so unless you have a way to make them go through the binder simply adding a vendor won't work

The /vendor partition was added for isolation of the directory from /system. The main reason to do so is to make it harder for malware to modify the vendor partition (planned feature). Also since the vendor partition is never truly updated (only the metadata is), it's better to write a 12 kB metadata update than to have vendor in /system and have an extra 80 mb to download because the blocks of data containing files on /system/vendor have to be moved. Simply put, splitting them allows system updates without ever really modifying the vendor partition. This is how those crazy small incremental OTAs can be made and still the results are the same as flashing a full OTA

Even if we somehow satisfy treble, P expects treble devices to implement system-as-root layout so we won't pass P GSI tests anyway
[OnePlus 2 Original Android Development] anupritaisno1:
I'll look into the first 2 issues

Temp fix for your third issue is to go in kernel adiutor and enable core control, then go to the CPU tab and toggle the 5th CPU core to on. It doesn't matter if it comes up or not just toggle it to avoid a small bug
[OnePlus 2 Original Android Development] samael07:
Hot to call kernel auditor?

What application? Most need rooted rom :(
[OnePlus 2 Original Android Development] samael07:
Hey,

I'd like to return to the stock ROM...

I read somewhere, that it is a remedy for the - described by me - OP2's "properties";)

Unfortunately, I do not know how ...

Could you describe in detail what and how to do to:

- decrypt partitions

- upload stock recovery

Thanks.
[OnePlus 2 Original Android Development] anupritaisno1:
Flash this recovery https://glassrom.botstack.host/recovery.img

In mount section tick mount system read-only

Flash oxygenos

Wipe cache and format data (wipe>format data) to remove encryption. Backup everything as internal storage will be lost too

Reboot

(Optional) instead of rebooting you can adb sideload this zip https://glassrom.botstack.host/firmware/oos-3.6.1-firmware-signed.zip and then you can use fastboot oem lock after booting into the ROM once
[OnePlus 2 Original Android Development] samael07:
Thanks. It works! :) Now we'll see how OP2 works ...
[OnePlus 2 Original Android Development] anupritaisno1:
Urgent

A bug has been identified in the wireguard kernel module. I haven't found a fix yet and it's probably due to our ancient kernel

Anyway, wireguard isn't properly tunneling ipv6 on the op2 and it seems our old kernel is to blame. If you use wireguard, either disable ipv6 or use the userspace backend. The kernelspace backend can't handle ipv6 correctly

If you don't have ipv6 you don't have to worry
[OnePlus 2 Original Android Development] anupritaisno1:
The signed-MonochromePublic.apk on the server was supposed to be a browser app that even provides a webview for non-gapps users. However since it's my first app I messed up the signing procedure. I thought I could just sign an apk the way I sign the ROM. Well that doesn't work and the app won't install. Don't waste your time downloading it for now