[ROM][8.1.0_r36][OFFICIAL] Cosmic-OS v3.2 - Pulsar [oneplus2]

[anupritaisno1]

Next build of cosmic-os will force encryption and support will be denied if tools like magisk or no-verity-opt-encrypt are used to bypass the forced encryption

 

[Chiraag17]

Someone please help... i cleaned flash this rom with opengapps. it booted successfully and i set up the phone properly. then i went back to twrp and it showed my data blank. i couldn't flash nor wipe anything. i had to clean everything(internal too) and change the partition to make it work. After this whenever i flash the rom with gaps it either goes to bootloop or google play services keep crashing. i tried pico, full, stock gapps. still the same result. It's happening with other roms too.
PS - twrp is latest version
- partition was changed to ext4

 

[hariharanM25]

Someone please help... i cleaned flash this rom with opengapps. it booted successfully and i set up the phone properly. then i went back to twrp and it showed my data blank. i couldn't flash nor wipe anything. i had to clean everything(internal too) and change the partition to make it work. After this whenever i flash the rom with gaps it either goes to bootloop or google play services keep crashing. i tried pico, full, stock gapps. still the same result. It's happening with other roms too.
PS - twrp is latest version
- partition was changed to ext4

Same happened for me when i flashed it, but i did format data. Before that i switched all my files to pc while i was in cosmic os itself. Then I'll flashed another rom with gapps. And transferred all my files from pc..no issues at all. Otherwise u can use anupristano's enhanced twrp.

 

[anupritaisno1]

Someone please help... i cleaned flash this rom with opengapps. it booted successfully and i set up the phone properly. then i went back to twrp and it showed my data blank. i couldn't flash nor wipe anything. i had to clean everything(internal too) and change the partition to make it work. After this whenever i flash the rom with gaps it either goes to bootloop or google play services keep crashing. i tried pico, full, stock gapps. still the same result. It's happening with other roms too.
PS - twrp is latest version
- partition was changed to ext4

Read the thread dude.

 

[anupritaisno1]

Guys you need to install my unofficial twrp build. Official won't work

Read the thread carefully. The attached twrp isn't the official twrp

 

[anupritaisno1]

Guys next build is going to force encryption and I'll say this

You don't read the thread or make your own assumptions? It's not my problem and I'll ignore further support requests where users obviously didn't bother to read the thread

 

[hariharanM25]

Guys you need to install my unofficial twrp build. Official won't work

Read the thread carefully. The attached twrp isn't the official twrp

Yeah, but i flashed the unofficial test build which a guy asked me to test on july 18th. So that time this thread was not started... And wmbrucker helped me out by letting me know about ur enhanced twrp..

 

[anupritaisno1]

Yeah, but i flashed the unofficial test build which a guy asked me to test on july 18th. So that time this thread was not started... And wmbrucker helped me out by letting me know about ur enhanced twrp..

Somebody from the beta testers group leaked the build. It was not ready for official release at that time yet people flashed it. Quite catastrophic

I've said this before but I'll say it again, this ROM and all my other Oreo ROMs use a new filesystem feature to prevent apps from abusing the device's storage. TWRP's kernel needs to be updated to support this new feature

 

[hariharanM25]

Somebody from the beta testers group leaked the build. It was not ready for official release at that time yet people flashed it. Quite catastrophic

I've said this before but I'll say it again, this ROM and all my other Oreo ROMs use a new filesystem feature to prevent apps from abusing the device's storage. TWRP's kernel needs to be updated to support this new feature

That guy said he is a unofficial maintainer, wanted to be offical one, so he asked to test as if he developed that rom like other developers. Anyway thank u.

 

[anupritaisno1]

That guy said he is a unofficial maintainer, wanted to be offical one, so he asked to test as if he developed that rom like other developers. Anyway thank u.

Just like they say don't take candy from strangers don't take ROMs from places other than XDA

 

[anupritaisno1]

I'm actually serious. If a stranger walks to you and offers you some candy you'd reject it but for some reason you see no problem giving full control of your device to a stranger

 

[hariharanM25]

I'm actually serious. If a stranger walks to you and offers you some candy you'd reject it but for some reason you see no problem giving full control of your device to a stranger

each and every rom developers are strangers to everyone when they are flashing custom roms for the first time. So if i need to get something good, then i must try.. If u think like this,then no new developer would get a tester to trust them and test their build..

 

[anupritaisno1]

each and every rom developers are strangers to everyone when they are flashing custom roms for the first time. So if i need to get something good, then i must try.. If u think like this,then no new developer would get a tester to trust them and test their build..

I think of XDA as a place to share one's code and the build is just to test stuff out before the user builds it himself. I have to be honest here but you really have to build it yourself if you want to trust your current system and sign it with your own keys. In this way you truly know what's going into the ROM and that's the only way you can trust something you make

 

[anupritaisno1]

Instructions for flashing the next build

First flash the vendor TWRP otherwise you'll get "error 7" while flashing the ROM
https://glassrom.botstack.host/recovery-vendor.img

Now after the TWRP is flashed it will tell you that it can't mount cache. DO NOT ignore this. Go to advance wipe, tick cache and wipe it. Then go to reboot and hit recovery. Now the error should be gone if not send me a message here, on telegram, on the glassrom tech support at discord or XDA

After that since we added a vendor partition you have to go and format system so that old backuptool scripts won't run in TWRP's wipe section

Flash the ROM zip.

Since the ROM will force encryption starting from this build, it's a good idea to take a nandroid and backup your entire internal storage to PC

On boot you'll see an encryption screen. Don't interrupt it. If you see the screen your device will boot normally in a few minutes. The encryption process also does not get stuck, sometimes encryption can take a while

If it's been more than 30 minutes and you still don't see the encryption screen

Go to twrp > wipe > format data > type yes > confirm wipe > reboot immediately

You can restore your nandroid later if you wiped. Remember to not restore the cache partition however

Starting from this build the ROM will update the twrp every time it is flashed so you no longer need to download my twrp from another server

 

[ahmedianist]

I have installed the rom. now I can't make calls even though It shows the carrier names. and in settings it shows SIM empty in sim cards option.

 

[anupritaisno1]

I have installed the rom. now I can't make calls even though It shows the carrier names. and in settings it shows SIM empty in sim cards option.

It's a bug with the ROM and oneplus 2 isn't the only device facing this. It seems several dual SIM devices are facing this issue on cosmic

 

[Chaprnks]

I'm curious, why does this ROM require a special TWRP? First time I've seen that in a ROM, just wondering why that is.


Also, is this special TWRP compatible with the rest of the ROM's, or do I have to go back to the official TWRP to flash any other ROM?

 

[anupritaisno1]

I'm curious, why does this ROM require a special TWRP? First time I've seen that in a ROM, just wondering why that is.


Also, is this special TWRP compatible with the rest of the ROM's, or do I have to go back to the official TWRP to flash any other ROM?

This ROM uses disk quotas to better understand disk usage by individual applications

You won't see anything different from other ROMs but disk management improves a lot due to this

2 things you can see however: when you go to app settings and check storage usage the amount used by the app will be returned almost instantaneously and when you delete or add files to your storage the usage statistics in settings will also update immediately

Official twrp obviously doesn't support this and needs to be updated to be able to mount data again after flashing the ROM

The other reason is the upcoming vendor partition addition

Future versions of this ROM will force encryption at first boot. Since we're using hardware accelerated encryption which isn't supported on other ROMs to avoid a significant slowdown on encrypted devices TWRP needs to be updated to mount data encrypted with hardware accelerated encryption

 

[danishajaz]

Is it necessary to force encryption? What if I don't want to encrypt my device?

 

[anupritaisno1]

Is it necessary to force encryption? What if I don't want to encrypt my device?

Legacy blobs
Legacy blobs
Legacy blobs

The services that are started by the legacy blobs we are using don't start at the right time at boot. This leads to several HALs not functioning correctly after boot. The one with the most issues is the camera HAL. I'm sure you've seen it yourself that the camera is unavailable after device boot on some other ROMs if you've flashed them and somehow a reboot fixes it

Encryption restarts several of these services, we need these restarts to get certain HALs to start correctly. I've never seen anyone with encryption report issues with the camera HAL or any other HAL because these are made to restart several times during encryption and are available after boot the way they are supposed to be

Also as per Google's CTS, Amy device that can support encryption at a speed higher than 50 Mbps should encrypt before the user sees the welcome screen. In our case the encryption performance is 150 Mbps+ (speed of the chip)