Have you tried a different PC btw?
[ROM] [9] GlassROM
- Thread starter anupritaisno1
- Start date
- Status
Yup, I did. (A desktop and a laptop) Same issue in Device Manager.
Though could just be my phone's port. But at the moment it is charging fine just no mass storage option.
Last edited:
Lineageos has added a "trust interface" feature
It's total nonsense. If you actually take any of the weird stuff it says seriously then you really don't know what security and trust is
Please don't get this false sense of security it's even worse than having no security at all
It's total nonsense. If you actually take any of the weird stuff it says seriously then you really don't know what security and trust is
Please don't get this false sense of security it's even worse than having no security at all
Guys I need someone to message me on discord for vendor partition preparation
I'm about to repurpose a partition to be used as vendor
If we are lucky we could flash GSIs
To clarify: we aren't exactly repartitioning the device but moving the contents of an existing partition to another already existing partition
I'm about to repurpose a partition to be used as vendor
If we are lucky we could flash GSIs
To clarify: we aren't exactly repartitioning the device but moving the contents of an existing partition to another already existing partition
As of now we have 3 options
Move /cache to reserve partition
Make /cache a temporary filesystem in ram
Move /bt-firmware to reserve partition
The bt-firmware approach is the best one if our bootloader permits it
Reasons: the bt-firmware partition is 1.1 GB in size but only holds 500 kb of data
This partition doesn't need to be modified often like /cache
Twrp won't break if the bt-firmware partition is relocated but will definitely break if we relocate the /cache partition
The bt-firmware partition's 500kb data can be moved to the reserve1 partition by flashing the image in fastboot and then modifying the fstab and selinux policies to label and mount this new location
No actual code changes will be required to relocate the bt-firmware partition
Move /cache to reserve partition
Make /cache a temporary filesystem in ram
Move /bt-firmware to reserve partition
The bt-firmware approach is the best one if our bootloader permits it
Reasons: the bt-firmware partition is 1.1 GB in size but only holds 500 kb of data
This partition doesn't need to be modified often like /cache
Twrp won't break if the bt-firmware partition is relocated but will definitely break if we relocate the /cache partition
The bt-firmware partition's 500kb data can be moved to the reserve1 partition by flashing the image in fastboot and then modifying the fstab and selinux policies to label and mount this new location
No actual code changes will be required to relocate the bt-firmware partition
https://www-xda--developers-com.cdn...trust-centralized-interface-security-privacy/
Contradiction: Google introduces treble so that proprietary blobs don't have to be updated by the silicon manufacturer
I see what you did there XDA, I see what you did there
Contradiction: Google introduces treble so that proprietary blobs don't have to be updated by the silicon manufacturer
I see what you did there XDA, I see what you did there
New release build coming
Hardware accelerated encryption
Full spectre v1 mitigation (CPU not vulnerable to v2 and v3)
Full meltdown mitigations
July 5 security patch merged in ROM and kernel
90% of HALs binderised
Several improvements to the RIL
Improved audio quality
Misc changes:
Glassrom will now verify your system after updating it. It will throw a failure and warn you if the system partition doesn't match an expected value. This will prevent accidental flashes if your download was corrupt
For low bandwidth users the compression rate of the OTA has been increased so that they can actually download the file. Compression doesn't affect the time required for flashing. (Btw compression of this level takes 11 hours on my server! Thanks to the way Google wrote the compression algorithm only 1-2 minutes are required for the flash. We're using brotli level 11 for compressing the system image and zip level 9 for compressing the overall OTA package)
Since oneplus2 doesn't currently support vboot 2.0 (implementation is possible and I'm working on it), the current verification mechanism for system is sha1 which isn't a very secure algorithm. It will prevent 99% of bad flashes but it's not perfect and we should move to vboot 2.0 with sha512 which has a very low error rate soon. I'm other words the system partition check isn't entirely foolproof
Glassrom will boot with software accelerated encryption and NOT convert to hardware accelerated encryption unless you format data. This is done intentionally to prevent data loss
That concludes the changelog. The release build should be out in the next 24 hours
Oh yeah and after this I'm going to look into twrp. Since I'm the twrp maintainer I gotta fix a lot of bugs
Hardware accelerated encryption
Full spectre v1 mitigation (CPU not vulnerable to v2 and v3)
Full meltdown mitigations
July 5 security patch merged in ROM and kernel
90% of HALs binderised
Several improvements to the RIL
Improved audio quality
Misc changes:
Glassrom will now verify your system after updating it. It will throw a failure and warn you if the system partition doesn't match an expected value. This will prevent accidental flashes if your download was corrupt
For low bandwidth users the compression rate of the OTA has been increased so that they can actually download the file. Compression doesn't affect the time required for flashing. (Btw compression of this level takes 11 hours on my server! Thanks to the way Google wrote the compression algorithm only 1-2 minutes are required for the flash. We're using brotli level 11 for compressing the system image and zip level 9 for compressing the overall OTA package)
Since oneplus2 doesn't currently support vboot 2.0 (implementation is possible and I'm working on it), the current verification mechanism for system is sha1 which isn't a very secure algorithm. It will prevent 99% of bad flashes but it's not perfect and we should move to vboot 2.0 with sha512 which has a very low error rate soon. I'm other words the system partition check isn't entirely foolproof
Glassrom will boot with software accelerated encryption and NOT convert to hardware accelerated encryption unless you format data. This is done intentionally to prevent data loss
That concludes the changelog. The release build should be out in the next 24 hours
Oh yeah and after this I'm going to look into twrp. Since I'm the twrp maintainer I gotta fix a lot of bugs
What happened to the incremental OTAs?
They can't be flashed with the current twrp. I'll need to fix twrp so that it can be possible
They can't be flashed with the current twrp. I'll need to fix twrp so that it can be possible
Also no I won't be using transfer.sh anymore. I'm hosting on my server and it has an actual dedicated 10 gigabit port with 1ms latency in most of Europe. Also since I'm hosting it expect the download server to be very secure
New build here https://glassrom.botstack.host/glassrom-release.zip
If I may please ask, but what is the best way to decrypt the phone so I can use TWRP again? I've tried using a set PIN & pattern, but keeps failing to decrypt.
Last edited:
Hello everybody. Just checking: could it be used as a daily driver? Regards
If you have to ask such questions then this ROM is not for you
Agreed. But being polite is not for you, either.
Btw guys I've reuploaded the twrp build to discord
An official upload will be made here shortly but if you need something right away well you know where to look
An official upload will be made here shortly but if you need something right away well you know where to look
The download server now supports clients using the new TLS 1.3 protocol
Currently only chrome canary is supported
To visit the download server using TLS 1.3, in chrome canary go to chrome://flags and in TLS 1.3 variant choose draft 28
Currently only chrome canary is supported
To visit the download server using TLS 1.3, in chrome canary go to chrome://flags and in TLS 1.3 variant choose draft 28
Btw guys since this ROM encrypts your device don't try to "test" the encryption system to see if the password at boot is placebo. It isn't and if you enter an incorrect password too many times there is code in AOSP to actually erase the data to protect it from brute forcing the password out
At the end of this is like to say: really internet? You couldn't come up with something a little less obvious
The limit is pretty high although, about 90-100 attempts before the erase happens. Haven't actually read the code to see how high it is
Yeah someone actually tried that
Also there's no backdoor. There is no way to recover a lost password and this is the only ROM to use hardware based encryption to truly secure the password
At the end of this is like to say: really internet? You couldn't come up with something a little less obvious
The limit is pretty high although, about 90-100 attempts before the erase happens. Haven't actually read the code to see how high it is
Yeah someone actually tried that
Also there's no backdoor. There is no way to recover a lost password and this is the only ROM to use hardware based encryption to truly secure the password
- Status
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone