Database Develop

Not able to install any Android 9.0 based ROM's

I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?

Did you tried another recovery? Try Batik Recovery!

Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.

Amir_espie said:
Hey there, how about u try to install Pitchblack twrp the latest one and install Pixel experience pie riva, it can be used for rolex also because the developer make the rom to unified for both rolex and riva. Then install the magisk after that. I've been using pixel experience pie for a month and it is so far so good.
Click to expand...
Click to collapse
Sure,will give it a go

An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys

Solved Magisk Error!
I've been using Pixys OS on my Redmi 4A and it works fine smoothly. I recommended to clean wipe before installing. Android Pie us amazing and I've installed stable version. Do backup before clean wipe.
For Magisk I recommended this: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html?m=1
It worked for me. Also go through this step before any custom ROM. Do let me know the status

Anirudh15 said:
An update
I installed Batik recovery.Magisk could be flashed but Im still getting the decryption unsuccessful message when I install Pixys
Click to expand...
Click to collapse
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.

You have two problems.
Anirudh15 said:
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
You need to flash the twrp separated vendor version by my friend Offain https://androidfilehost.com/?fid=962187416754475993
The other problem with the decryption:
You must enter in the twrp press wipe and format data. Type yes and then reboot into twrp again. After that flash the rom and gapps and you will not have the decryption problem again

Anirudh15 said:
I dont know if this is the right place to post this issue,sorry if this violates any rules
Recently I've shifted to custom roms on my device.I've always wanted to use one of those 9.0 ROM's.I tried 2 flavours-Pixys and Havoc.Both based off 9.
I tried flashing it with TWRP 3.2.1-0,as soon as I installed and rebooted it shows me Decryption failed and proceeded to factory reset my device.I had to repair my phone's file system to EXT4 to correct it and install an 8.1 based rom
Since I thought it might have to do something with TWRP, I tried RedWolf Recovery and tried installing Pixys and Havoc only to return to the same "Decryption Failed" issue.
Is there something different that I am doing?Can anyone help me in this regard.
Also,Im not able to install Magisk, recovery shows me Error-1 Couldnt mount vendor partition.What's the solution to this?
Click to expand...
Click to collapse
I had the same problem. Its because your phone is encrypted. The only solution I found is to boot the device into fastboot and using command: [fastboot format userdata] on PC. This will wipe all data off your phone so do backup. It removes encryption and now you can install any custom rom.

Decrypt ur phone first then flash, use twrp vendor

athish said:
to solve decryption unsuccesful message, format data (Wipe>Format Data) after installing the rom, make sure you backup your internal storage coz Format Data will also ERASE the internal storage. This how i got over the decryption unsuccessfull message. hope this helped.
Click to expand...
Click to collapse
Format Data was the only thing that worked for me. First backup everything on your mass storage.

[Official] Android 9 Community Beta for OnePlus 3/3T

For Unlocked Bootloader Devices - Flash at your own risk. Make sure to take a complete internal memory backup before flashing.
Following is a copy-paste from OP Forums
Hey everyone,
We know everyone is excited to finally try the delicious Pie update on the OnePlus 3 and OnePlus 3T. Thanks to the feedback from our beta testers, we are getting closer to launching Android Pie on the OnePlus 3 and 3T.
Now, we would like to invite you to download and try the Community Build available here and continue to help us shaping the stable update. Anyone can try this build, but please have in mind it won’t be available via OTA, you’ll have to download and install it yourself.
Community Beta for OnePlus 3
https://oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_075_all_1904171151_74affb85cc694452.zip
Community Beta for OnePlus 3T
https://oxygenos.oneplus.net/OnePlus3TOxygen_28_OTA_075_all_1904171149_20a0443ddf734944.zip
Those who download the Community Beta build will get OTA update when the stable build is released.
Changelog
System
Updated system to Android™ 9 Pie™
Brand new UI for Android Pie
Updated Android security patch to 2019.4
Do Not Disturb mode
New Do Not Disturb mode with adjustable settings
New Gaming mode 3.0
Added text notification mode
Added notification for 3rd party calls
Phone
Deep integration with Google Duo
Camera
Integrated Google Lens mode
Instructions for updating to the Community Build
For those on the latest stable version 181206
Preconditions: Boot Loader should be locked
Steps:​
Download the file from the link provided on the forum post
Move the downloaded file to internal storage root folder using the File Manager.
The device can then be updated via two methods.
First method: Local Update
Open Settings -> System update -> Click top right setting icon
Choose Local update
Click on the downloaded file and wait until the device reboots
Second Method: Recovery Update
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
​
For those who are on the latest Open Beta version 180712
Note: The entire data will be wiped since there will be a version transition from Open beta to the stable version. If you made a OnePlus Switch backup, be sure to make a copy of it before moving forward.
Steps:
Download the file form the link provided on the forum post
Move the downloaded file to internal storage
Device can be updated only via Recovery Update:
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
​
Thank you once again for all your patience and we can’t wait to get your feedback.
We are one step closer to releasing the Pie for OnePlus 3 / 3T, you can now download and try our community build right now.
Never Settle.
EDIT 1
Procedure that worked for me
So I've managed to install it and as expected, I had to format and delete everything on my internal memory. Here is the procedure I've followed and I'm 100% sure it'll work for others too.
Stuff I did before flashing:
1. Took a complete backup of internal memory.
2. Downloaded ROM + Recovery ( I use Holy Dragon custom twrp) + magisk 18.1 zip to an external OTG drive
My Configuration before flashing:
OOS 5.0.8, Unlocked BL, Magisk and root, Custom Kernel, Custom HolyDragon recovery
Procedure I followed:
1. Boot to recovery.
2. Wipe System, Dalvik, Cache
3. "Format Internal Memory". Please note, I formatted internal memory, not just wiped. This will remove encryption for once which will help the rom boot. It won't boot on encrypted partition with unlocked bootloader on first start up.
4. Flashed ROM zip.
5. Flashed twrp image.
6. Pressed power button for as long as possible until it rebooted again.
7. Pressed volume button before it could reboot so that i can select recovery. This step is important. If you won't do it, your recovery will be replaced with stock one.
8. Flash magisk zip. 18.1
9. Reboot system. It will take 10-15 minutes as it will reencrpt the storage.
10. Profit! Enjoy your new official oos pie on OP3/T.
Some things to note:
1. On first boot, it WILL NEED either mobile data or wifi. It downloaded some update and then installed and proceeded.
2. It will ask for your previous pattern. It didn't work for me so i simply login with my previous Gmail account on 5.0.8 and login successfully.
3. You will need to install magisk manager on first boot. It will show magisk not installed. Don't panic. Simply reboot your device once and it will appear in magisk on second reboot.
EDIT 2:
Community Beta 2 Released 5/6/2019
Hey everyone,
Here is the Community beta 2 for the OnePlus 3 and OnePlus 3T, the update primarily contains bug fixes:
Changelog
Bug fixes
Clock timer and stopwatch interface display is incomplete
Microphone doesn't work when earphones are plugged in
Crash issues with native message app
Community Beta 2 for OnePlus 3
https://oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_080_all_1905061403_459f9d6e543f4a16.zip
Community Beta 2 for onePlus 3T
https://oxygenos.oneplus.net/OnePlus3TOxygen_28_OTA_080_all_1905061406_f9d7f76f3a5d45da.zip

I am at the latest open beta, unlocked bootloader, rooted with twrp recovery. Does anyone know if I could flash this build through twrp?

brian13th said:
I am at the latest open beta, unlocked bootloader, rooted with twrp recovery. Does anyone know if I could flash this build through twrp?
Click to expand...
Click to collapse
I am currently at work. I will flash it once I am home. but make sure you take complete backup of your internal memory. It will mess up your internal data partition if you have unlocked bootloader. Don't take an unnecessary risk with your data.

Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:

FSadino said:
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
Click to expand...
Click to collapse
Flashed over closed pie beta (unlocked bootloader) with Red Wolf recovery. No problem, no data loss.

FSadino said:
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
Click to expand...
Click to collapse
kojakcr said:
Flashed over closed pie beta (unlocked bootloader) with Red Wolf recovery. No problem, no data loss.
Click to expand...
Click to collapse
That makes sense as you already had the closed pie build. Also, one question, are you both currently encrypted?

abhibnl said:
That makes sense as you already had the closed pie build. Also, one question, are you both currently encrypted?
Click to expand...
Click to collapse
I am

FSadino said:
I am
Click to expand...
Click to collapse
Seems like there is no other way than to format internal memory once. I'm on stock 5.0.8 rooted and UL BL

Where I found a download link from stock recovery.
On the OnePlus page I don't found it.
After flash stock recovery I must locked bootloader
Thanks
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app

Clean install, twrp 3.30-1, magisk, everything's fine
Thank you oneplus

On the 3T build I can't get it to install magisk for God's sake. The system partition is full and it seems it installs magisk fine, but when I boot up it says it isn't installed.... Tried different versions from 17.2 to 19

What's the procedure if I'm on twrp with custom rom?

Ed_Newgate said:
What's the procedure if I'm on twrp with custom rom?
Click to expand...
Click to collapse
The procedure is always the same, the results may be different.
Factory reset
Wipe data, system, cache, art
Flash zip
Reboot

So I've managed to install it and as expected, I had to format and delete everything on my internal memory. Here is the procedure I've followed and I'm 100% sure it'll work for others too.
Stuff I did before flashing:
1. Took a complete backup of internal memory.
2. Downloaded ROM + Recovery ( I use Holy Dragon custom twrp) + magisk 18.1 zip to an external OTG drive
My Configuration before flashing:
OOS 5.0.8, Unlocked BL, Magisk and root, Custom Kernel, Custom HolyDragon recovery
Procedure I followed:
1. Boot to recovery.
2. Wipe System, Dalvik, Cache
3. "Format Internal Memory". Please note, I formatted internal memory, not just wiped. This will remove encryption for once which will help the rom boot. It won't boot on encrypted partition with unlocked bootloader on first start up.
4. Flashed ROM zip.
5. Flashed twrp image.
6. Pressed power button for as long as possible until it rebooted again.
7. Pressed volume button before it could reboot so that i can select recovery. This step is important. If you won't do it, your recovery will be replaced with stock one.
8. Flash magisk zip. 18.1
9. Reboot system. It will take 10-15 minutes as it will reencrpt the storage.
10. Profit! Enjoy your new official oos pie on OP3/T.
Some things to note:
1. On first boot, it WILL NEED either mobile data or wifi. It downloaded some update and then installed and proceeded.
2. It will ask for your previous pattern. It didn't work for me so i simply login with my previous Gmail account on 5.0.8 and login successfully.
3. You will need to install magisk manager on first boot. It will show magisk not installed. Don't panic. Simply reboot your device once and it will appear in magisk on second reboot.
Let me know if you need additional help.

would u say worth changing to this from the one3os cb rom all seems to be the same there as this?

ireaper4592 said:
would u say worth changing to this from the one3os cb rom all seems to be the same there as this?
Click to expand...
Click to collapse
I can't say for sure. I have never tested CB. But this is the latest we have and it could have some under the hood fixes. I would recommend flashing this over CB

I need some help. I was on the latest Lineage OS version, got into recovery and formatted my data. Then I flashed the OOS Pie version. Got stuck on the OOS boot animation. Then I tried flashing the last OOS Beta and the last Official OOS but both are stuck on the same OOS boot animation. I also tried locking my bootloader and then starting again but didnt work out either...

HouseFuzzy said:
I need some help. I was on the latest Lineage OS version, got into recovery and formatted my data. Then I flashed the OOS Pie version. Got stuck on the OOS boot animation. Then I tried flashing the last OOS Beta and the last Official OOS but both are stuck on the same OOS boot animation. I also tried locking my bootloader and then starting again but didnt work out either...
Click to expand...
Click to collapse
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.

abhibnl said:
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
Click to expand...
Click to collapse
Alright gonna give it an other try then. Flashed the Pie OOS now via TWRP at around 11.20 german time. If its not getting over the boot animation by like 12.00 german time im gonna reply again.
---------- Post added at 12:16 PM ---------- Previous post was at 11:27 AM ----------
abhibnl said:
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
Click to expand...
Click to collapse
Alright been letting it go an hour now. Still in the boot animation.

svandasek said:
On the 3T build I can't get it to install magisk for God's sake. The system partition is full and it seems it installs magisk fine, but when I boot up it says it isn't installed.... Tried different versions from 17.2 to 19
Click to expand...
Click to collapse
Having similar issue, but on my side Magisk is installed, apps correctly receives the root privileges, but AdAway can't install the hosts file, it says system partition is full.

i have issue with the OnePlus 3T

Hello.
I flash OnePlus 3T stock pie 9.0.3 to (ROM) aroma pie 9.0.4 with twrp (3.2.3.1)
My mobile got brick after then i use msmdownload tool from 1.11Gb mega.nz l then i got back my phone on Marshalls mallow but when i trying to upgrade to stock 9.0.3 pie with the twrp 3.2.3.1 successful flashed the rom and reboot to system but i can boot to system 3,4 hours still loading on red circle when stock first boot logo please help me what i do i need to upgrade stock 9.0.3 pie at least instead of custom rom now im using Miui 10 in OnePlus 3T so please guide me how i can back to upgraded os because i don't want to use custom rom

zunairkh said:
Hello.
I flash OnePlus 3T stock pie 9.0.3 to (ROM) aroma pie 9.0.4 with twrp (3.2.3.1)
My mobile got brick after then i use msmdownload tool from 1.11Gb mega.nz l then i got back my phone on Marshalls mallow but when i trying to upgrade to stock 9.0.3 pie with the twrp 3.2.3.1 successful flashed the rom and reboot to system but i can boot to system 3,4 hours still loading on red circle when stock first boot logo please help me what i do i need to upgrade stock 9.0.3 pie at least instead of custom rom now im using Miui 10 in OnePlus 3T so please guide me how i can back to upgraded os because i don't want to use custom rom
Click to expand...
Click to collapse
At first use the latest TWRP 3.3.0.1
https://eu.dl.twrp.me/oneplus3/
Then try again...

Master_TC said:
At first use the latest TWRP 3.3.0.1
https://eu.dl.twrp.me/oneplus3/
Then try again...
Click to expand...
Click to collapse
You should have said "use the latest", in this case 3.3.1-0 instead

Master_TC said:
At first use the latest TWRP 3.3.0.1
https://eu.dl.twrp.me/oneplus3/
Then try again...
Click to expand...
Click to collapse
Can i use aroma 9.0.3 or OOS 9.0.3 with twrp3.3.0.1

Immortalis said:
You should have said "use the latest", in this case 3.3.1-0 instead
Click to expand...
Click to collapse
Can i use aroma 9.0.3 or OOS 9.0.3 with twrp3.3.0.1

zunairkh said:
Can i use aroma 9.0.3 or OOS 9.0.3 with twrp3.3.0.1
Click to expand...
Click to collapse
Yes you can.
The latest version is 3.3.1.0. Sorry i have mistyped.

i failed
i tried with letest twrp 3.3.1.0 recovery OOS.9.0.3 modem zip then i flash OOS9.0.3 FIRMWARE but still stuck on booting not enter in system

Master_TC said:
Yes you can.
The latest version is 3.3.1.0. Sorry i have mistyped.
Click to expand...
Click to collapse
i tried with letest twrp 3.3.1.0 recovery OOS.9.0.3 modem zip then i flash OOS9.0.3 FIRMWARE but still stuck on booting not enter in system

zunairkh said:
i tried with letest twrp 3.3.1.0 recovery OOS.9.0.3 modem zip then i flash OOS9.0.3 FIRMWARE but still stuck on booting not enter in system
Click to expand...
Click to collapse
OK you want to use the original OxygenOS 9.0.4?
Then go this way (all your data will be lost!):
1. in TWRP (3.3.1.0) delete all partitions (Dalvik, Cache, System, Data,...)
2. reboot into TWRP
3. format Data in Wipe - Format Data - type YES
4. reboot into TWRP
5. connect your phone with your computer and install full OxygenOS 9.0.4 zip (download from OP page)
6. reboot into TWRP and install magisk, if you want to keep TWRP. Else reboot into system
First boot takes 5-10 Minutes.

Thanks sir i will try and inform you if it work i will be thanks ful

Master_TC said:
OK you want to use the original OxygenOS 9.0.4?
Then go this way (all your data will be lost!):
1. in TWRP (3.3.1.0) delete all partitions (Dalvik, Cache, System, Data,...)
2. reboot into TWRP
3. format Data in Wipe - Format Data - type YES
4. reboot into TWRP
5. connect your phone with your computer and install full OxygenOS 9.0.4 zip (download from OP page)
6. reboot into TWRP and install magisk, if you want to keep TWRP. Else reboot into system
First boot takes 5-10 Minutes.
Click to expand...
Click to collapse
step 1 All partition include ( internal storage)?
Step 5 for transfer file oxygenos.zip? How to install though computer adb sideload or twrp flashing swipe

zunairkh said:
step 1 All partition include ( internal storage)?
Step 5 for transfer file oxygenos.zip? How to install though computer adb sideload or twrp flashing swipe
Click to expand...
Click to collapse
1. without internal storage (you can wipe it too, if you don't have any important data)
5. yes to transfer file or you use a sdcard. install OS in TWRP

I wiped all thing
And wiped format data and instll oxygen os 9.0.4 with magisk
Thanks ? you solve my issue
If i want to imstall aroma rom so can i do same process
?

zunairkh said:
I wiped all thing
And wiped format data and instll oxygen os 9.0.4 with magisk
Thanks you solve my issue
If i want to imstall aroma rom so can i do same process
?
Click to expand...
Click to collapse
Yes, so you can install all roms clean and without problems.
Don't forget to save your data!

Master_TC said:
Yes, so you can install all roms clean and without problems.
Don't forget to save your data!
Click to expand...
Click to collapse
Is there any method i can download miui cloud message,call history backup without install miui rom

[James] Moto E5 Play won't boot into Custom ROM(s)

Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.

have you taken any recent OTA updates?

mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.

tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.

mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.

I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere

I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.

tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1

Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit

mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?

Open Beta 14 is Out Now

Open Beta 14 is out
Changelog
System
• Fix the problem that some software voice input cannot be recognized
• Fix the problem of the disappearance of contacts in the address book on some devices
• More clock style options now available in ambient display (Settings -- Customization --Clock style)
• Improved system stability and fixed general issues
• Updated Android security patch to 2020.05
Phone
• Now you can view call recording in call history (move to the call history, click the three-dot menu on the upper right to access the call recording)

we need the full rom zip

i6rb said:
we need the full rom zip
Click to expand...
Click to collapse
http://otafsg1.h2os.com/patch/amazo...35_OTA_035_all_2005122203_dfb6c8f59826ca0.zip

just intalled from the stable, works fine, no data lost

I can't get Magisk to work, anyone else? Tried both the normal release and canary.

What are the correct steps to flash from one beta to another, when you are rooted, and would like to keep root?? Thanks.

Went to download and it says beta 13

Tr4il said:
I can't get Magisk to work, anyone else? Tried both the normal release and canary.
Click to expand...
Click to collapse
Works for me. I downloaded the zip from oxegyn updater, flashed it in TWRP, wiped dalvik, flashed TWRP (not sure if necessary), wiped dalvik, flashed magisk, changed partition to B, restarted to recovery again, flashed magisk again and rebooted. All as fine. Dirty install too.

mexiken said:
What are the correct steps to flash from one beta to another, when you are rooted, and would like to keep root?? Thanks.
Click to expand...
Click to collapse
carnivalrejectq said:
Works for me. I downloaded the zip from oxegyn updater, flashed it in TWRP, wiped dalvik, flashed TWRP (not sure if necessary), wiped dalvik, flashed magisk, changed partition to B, restarted to recovery again, flashed magisk again and rebooted. All as fine. Dirty install too.
Click to expand...
Click to collapse
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot

lbcoach3347 said:
Went to download and it says beta 13
Click to expand...
Click to collapse
The file name contains a "13" but it is not beta 13.
Sent from my OnePlus7Pro using XDA Labs

lollyjay said:
The file name contains a "13" but it is not beta 13.
Click to expand...
Click to collapse
Will this wipe everything it just update to 14 from 13

Greatness83 said:
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
Click to expand...
Click to collapse
I actually make both slots identical.
Local install of OS
Install Magisk after OTA
Reboot
Local install of the OS (might fail the first time, do it again)
Flash TWRP in Magisk
Direct install of Magisk
OTA install of Magisk.
Reboot
Now both slots are bootable with the same OS and rooted.

Greatness83 said:
Your doing too many steps...
Install from update(don't reboot)
Install TWRP from magisk manager(install from storage)(don't reboot)
Install magisk( install to inactive slot after OTA)
Reboot
Click to expand...
Click to collapse
that screwed me up once, now i flash twrp from magisk, then reboot to recovery and flash magisk

lbcoach3347 said:
Will this wipe everything it just update to 14 from 13
Click to expand...
Click to collapse
Just update.
Sent from my OnePlus7Pro using XDA Labs

Did OnePlus pull the update? No longer shows up for me

Pubg automatically closing without any notification on oxygen os beta Latest and even previous beta.. Any fix ??
Please help

It looks like the "clock style" is the first step toward the incoming AOD

Greatness83 said:
Did OnePlus pull the update? No longer shows up for me
Click to expand...
Click to collapse
Yes. I don't know the reason why but hope it's nothing too bad cause I already installed it.
https://www.xda-developers.com/onep...-ambient-display-clocks-may-2020-patches/?r=2

tnmsrkr said:
Pubg automatically closing without any notification on oxygen os beta Latest and even previous beta.. Any fix ??
Please help
Click to expand...
Click to collapse
Happening with me too here.
Found a fix ?

[Pulled back] OnePlus 7 and OnePlus 7T series OxygenOS Open Beta 14
Shortly after this article was published,
OnePlus has pulled back all the builds.(OxygenOS Open Beta 14)
The reason for this is unknown,
but a reasonable guess could be that there may be a showstopper bug present on them.
original link:
https://www.xda-developers.com/oneplus-7-oneplus-7t-series-oxygenos-open-beta-14-4-ambient-display-clocks-may-2020-patches/?r=2