I guess what I mean is the Changelog from the Official LineageOS site. I see the odd fixes here & there and did not know if these changes would be merged with your ROM.
[ROM] [9] GlassROM
- Thread starter anupritaisno1
- Start date
- Status
That is just lineageOS trying to fix stuff that isn't broken, breaking it in the process and then trying to fix it back
That stuff will be added eventually. For now I really need to fix other stuff for oreo
Next build will still be nougat
It will add experimental support for software acceleration of 10-bit video
Great for those who want to watch really high quality videos but you must make sure your phone doesn't overheat to an insane temperature. Again this is purely software acceleration and our hardware is incapable of 10-bit
If you use v4a, Dolby, etc you will have to disable it to allow the CPU to process the 10-bit stream
It will add experimental support for software acceleration of 10-bit video
Great for those who want to watch really high quality videos but you must make sure your phone doesn't overheat to an insane temperature. Again this is purely software acceleration and our hardware is incapable of 10-bit
If you use v4a, Dolby, etc you will have to disable it to allow the CPU to process the 10-bit stream
Last edited:
New build is up
Changelog
Linux 3.10.108
Fixed krack vulnerability
Picked upstream commits from Google
Optimised the kernel some more
Lots of bugfixes
Also with this release you can now verify the integrity of your downloaded file: https://github.com/GlassROM-devices/android_device_oneplus_oneplus2/tree/verify
How do you verify the integrity? Well use the search button
Changelog
Linux 3.10.108
Fixed krack vulnerability
Picked upstream commits from Google
Optimised the kernel some more
Lots of bugfixes
Also with this release you can now verify the integrity of your downloaded file: https://github.com/GlassROM-devices/android_device_oneplus_oneplus2/tree/verify
How do you verify the integrity? Well use the search button
Only partially. Follow-up patches were released for the Linux kernel quite later
cpu is alwais on max freq althoug there is no load
---------- Post added at 17:57 ---------- Previous post was at 17:38 ----------
or, maybe ex kernel manager shows incorectly
---------- Post added at 17:57 ---------- Previous post was at 17:38 ----------
or, maybe ex kernel manager shows incorectly
Hey guys I need some help
Think you can handle PR, communications or do some contribution (any kind, doesn't have to be development)?
Then join the telegram chat here https://t.me/joinchat/DKbLAFJsx6x0Hu7Q8Ke3UA
I will personally kick people who join this group to spam. So if you have plans to do that better watch out
Currently glassrom is just a project run by one guy (while I do have the resources) and it is getting harder to manage everything (development, PR, communications, distributions, thread designing, etc) all by just one guy.
When you join please mention your XDA username or github username (optional)
Think you can handle PR, communications or do some contribution (any kind, doesn't have to be development)?
Then join the telegram chat here https://t.me/joinchat/DKbLAFJsx6x0Hu7Q8Ke3UA
I will personally kick people who join this group to spam. So if you have plans to do that better watch out
Currently glassrom is just a project run by one guy (while I do have the resources) and it is getting harder to manage everything (development, PR, communications, distributions, thread designing, etc) all by just one guy.
When you join please mention your XDA username or github username (optional)
HaruhiOS now boots on locked bootloaders 
This is NOT a vulnerability nor a bootloader bug. It requires the user to unlock his bootloader and for that the user has to enable OEM unlocking and unlock the bootloader himself. Do NOT just start criticising oneplus. If this were really a vulnerability then on the basis of severity I would classify this one as "very low severity" or not even significant
Warning warning warning! This stuff is not for noobs
This requires you to have knowledge of Linux and bash. Knowledge of Linux doesn't mean simply installing and using a distribution. You should be knowing what you're doing before you attempt this
I am not responsible for any damage to your device! You are entering the danger zone. It is your responsibility if you mess this up. Read this carefully and if you don't understand anything, don't even try
Read all of the instructions before attempting anything
If you do not understand why I copied the su.img to /cache/ then do not try this. You did not understand what I did and should stop
The current version already supports this
Steps: download SuperSU, chainfire's signer and oxygen recovery
Now go to twrp and flash SuperSU and then the signer
Use the file manager to copy /data/su.img to /cache
Mount your /system in the mounts tab and uncheck the read-only option if enabled, and then open a terminal and type exactly this
Flash the oxygenos recovery, boot back into the ROM and verify that everything works, then check k that the oxygen recovery actually boots
Now take a full nandroid backup and save this to your PC. This is important. The locking process will wipe all of your data, even data on internal storage!
Make sure you really signed the boot.img!
Make sure you really didn't disable OEM unlocking as it is the only way to get back if something goes wrong!
Make sure you did not install magisk! Otherwise flashing SuperSU will brick your ROM (magisk can only be installed after SuperSU, you cannot install SuperSU before magisk)
Do NOT attempt to edit my commands and try it with magisk instead of SuperSU!
Make sure you backed up your entire internal storage! There is no going back at this point
When you're done, send fastboot oem lock to the phone
Now boot and copy twrp to your sdcard
The twrp image needs to be in the root directory of your internal storage! Do NOT ignore this warning
Now rename that file to twrp.img
Now assuming that you did
Already typed
To get root
All you need to do is run this command
Now just wait a few seconds. This stuff takes a while
Now boot to twrp and restore your nandroid
This is NOT a vulnerability nor a bootloader bug. It requires the user to unlock his bootloader and for that the user has to enable OEM unlocking and unlock the bootloader himself. Do NOT just start criticising oneplus. If this were really a vulnerability then on the basis of severity I would classify this one as "very low severity" or not even significant
Warning warning warning! This stuff is not for noobs
This requires you to have knowledge of Linux and bash. Knowledge of Linux doesn't mean simply installing and using a distribution. You should be knowing what you're doing before you attempt this
I am not responsible for any damage to your device! You are entering the danger zone. It is your responsibility if you mess this up. Read this carefully and if you don't understand anything, don't even try
Read all of the instructions before attempting anything
If you do not understand why I copied the su.img to /cache/ then do not try this. You did not understand what I did and should stop
The current version already supports this
Steps: download SuperSU, chainfire's signer and oxygen recovery
Now go to twrp and flash SuperSU and then the signer
Use the file manager to copy /data/su.img to /cache
Mount your /system in the mounts tab and uncheck the read-only option if enabled, and then open a terminal and type exactly this
Code:
echo "cp /cache/su.img /data/ && chmod 777 /data/su.img" >> /system/etc/init.d/supersu.sh && chmod 777 /system/etc/init.d/supersu.shNow take a full nandroid backup and save this to your PC. This is important. The locking process will wipe all of your data, even data on internal storage!
Make sure you really signed the boot.img!
Make sure you really didn't disable OEM unlocking as it is the only way to get back if something goes wrong!
Make sure you did not install magisk! Otherwise flashing SuperSU will brick your ROM (magisk can only be installed after SuperSU, you cannot install SuperSU before magisk)
Do NOT attempt to edit my commands and try it with magisk instead of SuperSU!
Make sure you backed up your entire internal storage! There is no going back at this point
When you're done, send fastboot oem lock to the phone
Now boot and copy twrp to your sdcard
The twrp image needs to be in the root directory of your internal storage! Do NOT ignore this warning
Now rename that file to twrp.img
Now assuming that you did
Code:
cd /sdcard
Code:
suAll you need to do is run this command
Code:
dd if=twrp.img of=/dev/block/bootdevice/by-name/recoveryNow boot to twrp and restore your nandroid
Last edited:
CAF is going to release October security patch for our CPU in late November
Nice job CAF
Well at least they do something as opposed to Google just cherry-picking and hyping but this is just too darn slow
Nice job CAF
Well at least they do something as opposed to Google just cherry-picking and hyping but this is just too darn slow
Hi guys the most recent build has been recalled due to a bug
Description: CPU frequency scaling is totally broken. This can the device to either stick to a very high frequency causing battery drain or stick to a very low frequency causing lag and freezing issues
Severity: Very high
Fix: a fix has been made available immediately. Download this boot.img https://srv1.botstack.host:8001/boot.img and flash it. This should fix the issue
Note: if you are on a custom kernel you can safely ignore this warning
For newcomers: wait a bit. A new build should be available very soon
Reported by: @chxei @FPSUsername
Can't apply the fix right away? Grab any custom kernel and flash it or just wait for the updated ROM. Make sure your device doesn't overheat
Description: CPU frequency scaling is totally broken. This can the device to either stick to a very high frequency causing battery drain or stick to a very low frequency causing lag and freezing issues
Severity: Very high
Fix: a fix has been made available immediately. Download this boot.img https://srv1.botstack.host:8001/boot.img and flash it. This should fix the issue
Note: if you are on a custom kernel you can safely ignore this warning
For newcomers: wait a bit. A new build should be available very soon
Reported by: @chxei @FPSUsername
Can't apply the fix right away? Grab any custom kernel and flash it or just wait for the updated ROM. Make sure your device doesn't overheat
Last edited:
Oh what the sources were never uploaded fully as far as I was aware. Or atleast compiled
in any case shake it up and support more devices
looking to fork for a overnight android session, stable?
You can go ahead and do so
Also where were you absconded for a whole year if I may ask?
There have been no updates to the source, instead I leave format patches in my tree and apply them during the build
A simple git pull --rebase should get all the repos updated
Hey guys I had some disc corruption and the support team was busy fixing my server
It took me a while to recover my Android tree but now it's fixed
I'll release a new build as soon as possible
It took me a while to recover my Android tree but now it's fixed
I'll release a new build as soon as possible
New update is out
This is a maintenance release
New stuff: November security patch
Added some extra patches Google released
Fixed some nasty bugs
Removed a partition entry from fstab which we don't use
This is a maintenance release
New stuff: November security patch
Added some extra patches Google released
Fixed some nasty bugs
Removed a partition entry from fstab which we don't use
Known issues: currently locking the bootloader after flashing won't work (if you already locked it then ignore)
My server disc is currently facing some nasty corruption issues
Download one of these files https://github.com/GlassROM-devices/android_device_oneplus_oneplus2/tree/verify?files=1 if you'reoure paranoid and check the integrity before you flash
A second maintenance build will arrive tomorrow to fix the first issue
My server disc is currently facing some nasty corruption issues
Download one of these files https://github.com/GlassROM-devices/android_device_oneplus_oneplus2/tree/verify?files=1 if you'reoure paranoid and check the integrity before you flash
A second maintenance build will arrive tomorrow to fix the first issue
Small announcement
You can safely ignore this if not interested
So some people might not know how to use these files to verify integrity
The .md5sum file is the md5sum has. Place this file in the same directory as the ROM before flashing and twrp will verify the integrity for you. Note that md5sum is very weak so false negatives in verification are possible
Any .shaxxxsum where x can be 1, 256, 512, 224 are sha{1,256,512,224} sums of the files. Pick whichever is convenient for you to verify
The .cert.txt is the signature of the zip file. To verify this, it's the same as verifying an application signature
keytool -list-printcert-jarfile *zip should do the trick. This isn't for beginners
The .sig file is the gpg detached signature of the ROM zip. It is complicated for a beginner to set up gpg verification but once it is done all you gotta do is gpg --verify <name_of_sig_file_with_extension> The gpg public key is in the same folder. It is gpg.key
The ROM signature is divided into 4 keys. Only the release-key fingerprint is disclosed.
All signing keys are sha256withrsa, 2048-bit and public exponent 3
The gpg key is 4096-bit with RSA
Avoid md5sum digest and sha1sum digests. They are weak and you should only use them if you have a proper reason to do so
You can safely ignore this if not interested
So some people might not know how to use these files to verify integrity
The .md5sum file is the md5sum has. Place this file in the same directory as the ROM before flashing and twrp will verify the integrity for you. Note that md5sum is very weak so false negatives in verification are possible
Any .shaxxxsum where x can be 1, 256, 512, 224 are sha{1,256,512,224} sums of the files. Pick whichever is convenient for you to verify
The .cert.txt is the signature of the zip file. To verify this, it's the same as verifying an application signature
keytool -list-printcert-jarfile *zip should do the trick. This isn't for beginners
The .sig file is the gpg detached signature of the ROM zip. It is complicated for a beginner to set up gpg verification but once it is done all you gotta do is gpg --verify <name_of_sig_file_with_extension> The gpg public key is in the same folder. It is gpg.key
The ROM signature is divided into 4 keys. Only the release-key fingerprint is disclosed.
All signing keys are sha256withrsa, 2048-bit and public exponent 3
The gpg key is 4096-bit with RSA
Avoid md5sum digest and sha1sum digests. They are weak and you should only use them if you have a proper reason to do so
Last edited:
I have plans to add a separate verity key that actually doesn't enable verity but fools the bootloader in order for you to lock it. That will very soon make it 5 keys instead of 4
On the download server side
The download server now uses apparmor (selinux doesn't work fine on Debian), yama and Linux hardened on top of a mainline kernel (maintained by me here: https://github.com/anupritaisno1/linux-hardened)
TLS certificates have been bumped to 4096-bit RSA from 2048-bit RSA
HPKP now pins for 2 months and 28 days (this is only for internal development)
OCSP responses are now strictly stapled
We are now fully compliant with chrome's upcoming EXPECT-CT
The download server now uses apparmor (selinux doesn't work fine on Debian), yama and Linux hardened on top of a mainline kernel (maintained by me here: https://github.com/anupritaisno1/linux-hardened)
TLS certificates have been bumped to 4096-bit RSA from 2048-bit RSA
HPKP now pins for 2 months and 28 days (this is only for internal development)
OCSP responses are now strictly stapled
We are now fully compliant with chrome's upcoming EXPECT-CT
- 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