[ROM][10.0][CHEESEBURGER] Pixel Experience [AOSP][TEN/PLUS][2020/07/20][EOL]

[saratrajan]

Make sure you clean flashed before you report bugs

I tried an incremental upgrade. Why is a clean flash needed, please let me know.

I also tried clean flash on full build image, issue persisted!

 

[itsjoeoui]

I tried an incremental upgrade. Why is a clean flash needed, please let me know.

I also tried clean flash on full build image, issue persisted!

1. I have 0 issues here with 0710, which means something is probably wrong on your side
2. Clean flash means wiping everything. I don't think you understand what 'clean flash' means

 

[saratrajan]

1. I have 0 issues here with 0710, which means something is probably wrong on your side
2. Clean flash means wiping everything. I don't think you understand what 'clean flash' means

1. I am sure that you are 100% correct there. Not sure what was wrong, still trying to figure out as I want to be on latest security patch on PE.
2. I tried clean flash with TWRP on full-build-image. Not sure why there were issues of device freezes most times. Will revisit when I get some free time. Been doing this for years, so I understand the jargons and processes that come with it.

However, that did not explain why an incremental upgrade (which does not require clean flash, basically) had those problems. I am not trying to point any fingers here, appreciate your work with PE. It is a solid ROM altogether!

Cheers,
Sarat

 

[itsjoeoui]

1. I am sure that you are 100% correct there. Not sure what was wrong, still trying to figure out as I want to be on latest security patch on PE.
2. I tried clean flash with TWRP on full-build-image. Not sure why there were issues of device freezes most times. Will revisit when I get some free time. Been doing this for years, so I understand the jargons and processes that come with it.

However, that did not explain why an incremental upgrade (which does not require clean flash, basically) had those problems. I am not trying to point any fingers here, appreciate your work with PE. It is a solid ROM altogether!

Cheers,
Sarat

1. I updated myself with an incremental update, and I have no problem at all
2. Did you wipe everything before you flashed? If not, then that's not a 'clean flash'

Cheers

 

[itsjoeoui]

1. I am sure that you are 100% correct there. Not sure what was wrong, still trying to figure out as I want to be on latest security patch on PE.
2. I tried clean flash with TWRP on full-build-image. Not sure why there were issues of device freezes most times. Will revisit when I get some free time. Been doing this for years, so I understand the jargons and processes that come with it.

However, that did not explain why an incremental upgrade (which does not require clean flash, basically) had those problems. I am not trying to point any fingers here, appreciate your work with PE. It is a solid ROM altogether!

Cheers,
Sarat

And I apologize as my attitude was not very good

 

[profetaii]

Hi Guys,

yesterday I install Pixel Experience on my OP5 and as I almost getting without battery the phone shutdown.
I put it on charger and try to turn it on but something strange happen, the phone started until the android background image and then it seens that it was on sleep but when i push the power button only the hardware buttons gave feedback(their light come on)

any one had this?

 

[davidcd13]

what is the " plus edition" ?

 

[profetaii]

what is the " plus edition" ?

yes. its normal?

 

[Nimrodz91]

So I was flashing this new ROM (Plus Edition), coming from OOS 10, but I got stuck on bootloop. Here's what I did:

1. I removed fingerprint lock, backed up my apps, not my internal storage since my phone was decrypted.
2. I did a nandroid backup
3. Wiped cache, dalvik, data and system
4. Flashed ROM, Magisk and No Verity 4.0
5. Rebooted and got stuck for 3-5 min.

6. I proceeded to wipe everything again to reflash it, but then I realized that the phone got encrypted and now I can't see my nandroid and other backups.

So now I'm stuck. Any solution?

 

[sjamie]

So I was flashing this new ROM (Plus Edition), coming from OOS 10, but I got stuck on bootloop. Here's what I did:

1. I removed fingerprint lock, backed up my apps, not my internal storage since my phone was decrypted.
2. I did a nandroid backup
3. Wiped cache, dalvik, data and system
4. Flashed ROM, Magisk and No Verity 4.0
5. Rebooted and got stuck for 3-5 min.

6. I proceeded to wipe everything again to reflash it, but then I realized that the phone got encrypted and now I can't see my nandroid and other backups.

So now I'm stuck. Any solution?

For some reason, my phone also got encrypted when I went from OOS 10 to NitrogenOS even though I flashed the same NoVerity file I've used many times successfully. My "fix" was to format the Data partition and start over. Thankfully, I had already backed up everything to my PC before I began contemplating switching ROMs.

 

[Nimrodz91]

For some reason, my phone also got encrypted when I went from OOS 10 to NitrogenOS even though I flashed the same NoVerity file I've used many times successfully. My "fix" was to format the Data partition and start over. Thankfully, I had already backed up everything to my PC before I began contemplating switching ROMs.

Yeah, that was my "fix" too, except for the fact that I didn't back up my internal storage, but I had an older backup. So I had to use that.

 

[sjamie]

Yeah, that was my "fix" too, except for the fact that I didn't back up my internal storage, but I had an older backup. So I had to use that.

I wonder what causes this unwanted encryption...

 

[scoobyjenkins]

When I dirty flashed the latest version, using no Verity 4.0 (I'm decrypted), it rebooted back to recovery. I'd updated my TWRP to 3.4.0-0 since the last version. So I went back from TWRP 3.4.0-0 to TWRP 3.3.1-0 and tried again. It booted.
Then I updated TWRP to 3.4 again and tried dirty flash the same latest version of PE Plus edition, this time with "Universal DM-Verity and ForceEncrypt Disabler (2020-03-04)" and it also booted fine.
So I guess my issue was with No Verity 4.0 and the latest TWRP?
Here's where I got the no Verity zip that seems to work for me with TWRP 3.4:
https://androidfilehost.com/?fid=4349826312261740342
I always dirty flash the full ROM zip by the way, I'm sure the incremental update would be fine, I just prefer to flash the full zip every time, just in case.

 

[Nimrodz91]

I wonder what causes this unwanted encryption...

When I dirty flashed the latest version, using no Verity 4.0 (I'm decrypted), it rebooted back to recovery. I'd updated my TWRP to 3.4.0-0 since the last version. So I went back from TWRP 3.4.0-0 to TWRP 3.3.1-0 and tried again. It booted.
Then I updated TWRP to 3.4 again and tried dirty flash the same latest version of PE Plus edition, this time with "Universal DM-Verity and ForceEncrypt Disabler (2020-03-04)" and it also booted fine.
So I guess my issue was with No Verity 4.0 and the latest TWRP?
Here's where I got the no Verity zip that seems to work for me with TWRP 3.4:
https://androidfilehost.com/?fid=4349826312261740342
I always dirty flash the full ROM zip by the way, I'm sure the incremental update would be fine, I just prefer to flash the full zip every time, just in case.

Do you think I can still flash the No Verity 4.0 zip (or the universal one that you described) after I have already formatted storage, booted the ROM and have been using it for a day in order to decrypt the phone again? Or so I have to format data again and reflash the ROM?

Or how should I confirm that I'm already decrypted in this case?

 

[sjamie]

Do you think I can still flash the No Verity 4.0 zip (or the universal one that you described) after I have already formatted storage, booted the ROM and have been using it for a day in order to decrypt the phone again? Or so I have to format data again and reflash the ROM?

Or how should I confirm that I'm already decrypted in this case?

The only way I know to decrypt a phone is to format the data partition (which erases everything including internal storage), flash ROM and flash a NoVerity solution. As @scoobyjenkins mentioned I had also flashed the NoVerity4 zip when my phone still became encrypted. On my last attempt, I tried the "Universal DM-Verity and ForceEncrypt Disabler (2020-03-04)" and it worked perfectly. Now I'm back running encryption-free!

 

[scoobyjenkins]

Do you think I can still flash the No Verity 4.0 zip (or the universal one that you described) after I have already formatted storage, booted the ROM and have been using it for a day in order to decrypt the phone again? Or so I have to format data again and reflash the ROM?

Or how should I confirm that I'm already decrypted in this case?

You only have to format internal to decrypt, the no Verity zips are just to make roms that don't natively support decryption be able to boot. You can always check your encryption status in settings, security, and under encryption and credentials it will say if you are encrypted or not. So long as you managed to boot I wouldn't worry, was just sharing my experience in case it may be helpful to others

 

[Nimrodz91]

The only way I know to decrypt a phone is to format the data partition (which erases everything including internal storage), flash ROM and flash a NoVerity solution. As @scoobyjenkins mentioned I had also flashed the NoVerity4 zip when my phone still became encrypted. On my last attempt, I tried the "Universal DM-Verity and ForceEncrypt Disabler (2020-03-04)" and it worked perfectly. Now I'm back running encryption-free!

I see... I'll try the Universal Disabler next time then.

You only have to format internal to decrypt, the no Verity zips are just to make roms that don't natively support decryption be able to boot. You can always check your encryption status in settings, security, and under encryption and credentials it will say if you are encrypted or not. So long as you managed to boot I wouldn't worry, was just sharing my experience in case it may be helpful to others

Ah, I understand now. I checked the encryption status and it is "encrypted". However, something weird is going on when I reboot to TWRP recovery. It shows that I must unlock it using the lock screen pattern, but it fails to confirm it. So I just tap cancel and I can flash normally without the files being encrypted. So I'm not sure why the lock screen pattern fails or even appears if I can see the files decrypted normally without it.

 

[scoobyjenkins]

I see... I'll try the Universal Disabler next time then.



Ah, I understand now. I checked the encryption status and it is "encrypted". However, something weird is going on when I reboot to TWRP recovery. It shows that I must unlock it using the lock screen pattern, but it fails to confirm it. So I just tap cancel and I can flash normally without the files being encrypted. So I'm not sure why the lock screen pattern fails or even appears if I can see the files decrypted normally without it.

Sounds strange, but could be to do with encryption. I had similar issues in the past, hence being decrypted ever since. You only need to flash no Verity with this rom if you're decrypted. Maybe if you do decrypt, your twrp pattern issue may go away!

 

[Nimrodz91]

Sounds strange, but could be to do with encryption. I had similar issues in the past, hence being decrypted ever since. You only need to flash no Verity with this rom if you're decrypted. Maybe if you do decrypt, your twrp pattern issue may go away!

I guess I'll decrypt it again if I need to flash a ROM then. For now, this twrp pattern issue is not preventing me from flashing. So I guess it's alright?

 

[scoobyjenkins]

I guess I'll decrypt it again if I need to flash a ROM then. For now, this twrp pattern issue is not preventing me from flashing. So I guess it's alright?

I'd say it's a matter of preference, whether you're encrypted or not, it shouldn't make a difference to being able to flash anything. Being encrypted and running a custom ROM was a minor issue for me, so I chose to decrypt.