Seems like a nice deal. Identical normal price though.
Just wish I had more time with my good gear. "Deep listening" is kind of an hobby. Picking out flaws and stuff or simply enjoy a perfect song when I can't find anything that annoys me [e]1f609[/e]

I am also having this issue. It is definitely caused because TWRP thinks the ROM isn't compatible with our Device despite it being a OnePlus 7 Pro and currently running Open Beta 5 (rooted w/ Magisk).

Apparently, you used to be able to extract the ROM, go into /META-INF/com/google/android/updater-script and delete the 'assert' lines of the file in order to resolve this issue. However it appears the ROM no longer contains that file.

I'm unsure how to proceed, but suppose I will wait for the official Open Beta 6 forum post and hope this issue is resolved there.

Jelly BeanNov 20, 2019

I am also having this issue. It is definitely caused because TWRP thinks the ROM isn't compatible with our Device despite it being a OnePlus 7 Pro and currently running Open Beta 5 (rooted w/ Magisk).

Apparently, you used to be able to extract the ROM, go into /META-INF/com/google/android/updater-script and delete the 'assert' lines of the file in order to resolve this issue. However it appears the ROM no longer contains that file.

I'm unsure how to proceed, but suppose I will wait for the official Open Beta 6 forum post and hope this issue is resolved there.

Click to expand...

Talking to two more cases of it happening on Telegram. Users have tried formatting data without success. It's therefore NOT an encryption issue. All users have tried installing on v72 of TWRP so far. Perhaps reverting to v70 will resolve.

GingerbreadNov 20, 2019

I am also having this issue. It is definitely caused because TWRP thinks the ROM isn't compatible with our Device despite it being a OnePlus 7 Pro and currently running Open Beta 5 (rooted w/ Magisk).

Apparently, you used to be able to extract the ROM, go into /META-INF/com/google/android/updater-script and delete the 'assert' lines of the file in order to resolve this issue. However it appears the ROM no longer contains that file.

I'm unsure how to proceed, but suppose I will wait for the official Open Beta 6 forum post and hope this issue is resolved there.

Click to expand...

I try to install twrp 3.3.1-72 but it said "Failed to map file '/sdcard/AA/twrp-3.3.1-72-guacamole-unfied-installer-maurofrio.zip'

GingerbreadNov 20, 2019

Talking to two more cases of it happening on Telegram. Users have tried formatting data without success. It's therefore NOT an encryption issue. All users have tried installing on v72 of TWRP so far. Perhaps reverting to v70 will resolve.

CupcakeNov 20, 2019

Talking to two more cases of it happening on Telegram. Users have tried formatting data without success. It's therefore NOT an encryption issue. All users have tried installing on v72 of TWRP so far. Perhaps reverting to v70 will resolve.

Click to expand...

I'm currently running twrp 3.3.1-71 if that makes a difference. I posted on the Reddit thread as well, hoping someone has dealt with this before.

CupcakeNov 20, 2019

Talking to two more cases of it happening on Telegram. Users have tried formatting data without success. It's therefore NOT an encryption issue. All users have tried installing on v72 of TWRP so far. Perhaps reverting to v70 will resolve.

Jelly BeanNov 20, 2019

Ahh, I think you have to actually link the 'share link' for the telegram channel, which can be found by clicking the 3 dots in the upper right hand corner of the channel, selecting 'info', and then copying the 'share link' so I can join the channel and view the messages.