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

[FSadino]

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 believe AdAway is resetting hosts file after reboot in all pie ROMs, not only on OOS

 

[jeffrey268]

Having no trouble with adaway here.

Adaway v4.2.4.
Set systemless host in magisk and host location /system/etc/host

 

[cyberboy_sj]

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.

Can you link me the Custom TWRP?

 

[ajo81]

Is there any custom kernel available for this ROM?

 

[TNSMANI]

Is there any custom kernel available for this ROM?

What? This comes today and you want a custom kernel already?

 

[FSadino]

Is there any custom kernel available for this ROM?

Maybe when OP release sources

 

[FSadino]

Can you link me the Custom TWRP?

This will work: https://androidfilehost.com/?fid=1395089523397907195

 

[abhibnl]

Can you link me the Custom TWRP?

Honestly, the latest TWRP will work fine too but I'll link to the recovery I am using.

https://www.androidfilehost.com/?fid=3700668719832239620

This is the latest available HolyDragon TWRP will special optimizations for our chipset. It has always worked fine for me and never had any issues with it. Still working great to this date.

 

[abhibnl]

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

One first flashing Magisk, you have to manually install MagiskManager apk, get it from xda thread. When you'll run the app, it'll say magisk not installed. Don't worry, just reboot the device once and when you'll open magisk app again, app will show magisk is working.
if it still doesn't work for you, don't panic. Just extract a file called "boot.img" from OOS pie zip, patch it using the option given in magisk manager app, flash the modified boot.img using twrp, and magisk will work fine after that. Let me know if you need any help.

 

[svandasek]

One first flashing Magisk, you have to manually install MagiskManager apk, get it from xda thread. When you'll run the app, it'll say magisk not installed. Don't worry, just reboot the device once and when you'll open magisk app again, app will show magisk is working.
if it still doesn't work for you, don't panic. Just extract a file called "boot.img" from OOS pie zip, patch it using the option given in magisk manager app, flash the modified boot.img using twrp, and magisk will work fine after that. Let me know if you need any help.

Thanks for your response...
I did both. Even patched it and flashed, but I can't believe my eyes, it still says magisk isn't installed. ****
This never happened to me before, flashed pretty much already.
I am hopeless.

 

[pcesar.cercal]

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.

I'm very happy with this update. But the kernel has not been updated for more than a year. Can we know why?

 

[abhibnl]

I'm very happy with this update. But the kernel has not been updated for more than a year. Can we know why?

How do you know kernel isn't updated for more than a year? If you are talking about kernel version (3.X.X), that's not an easy task to move to 4.X.X. OEMs don't usually that much resources into developing a whole new kernel version/base for an older device. However, the kernel is regularly updated and has all the latest security and device patches.

Thanks for your response...
I did both. Even patched it and flashed, but I can't believe my eyes, it still says magisk isn't installed. ****
This never happened to me before, flashed pretty much already.
I am hopeless.

Are you using 18.1 or Canary build? I am using 18.1 without any issues at all.

 

[abhibnl]

BTW, anyone else noticed the phone is "slower to wake" when sitting Idle for longer time if unlocked by FP?

 

[svandasek]

How do you know kernel isn't updated for more than a year? If you are talking about kernel version (3.X.X), that's not an easy task to move to 4.X.X. OEMs don't usually that much resources into developing a whole new kernel version/base for an older device. However, the kernel is regularly updated and has all the latest security and device patches.


Are you using 18.1 or Canary build? I am using 18.1 without any issues at all.

V18.1
I wouldn't care so much if i didn't have a need to test my app on it.:crying:

 

[svandasek]

@abhibnl when I try to adb push something through terminal, it says "failed to copy file to /system': remote couldn't create file: Read only file system'"

Why is it read only!?

 

[jeffrey268]

Android security patch level

I thouth the android security patch level is supposed to be 1 April 2019,
but i have 1 November 2018. anyone else having this issue?

 

[abhibnl]

@abhibnl when I try to adb push something through terminal, it says "failed to copy file to /system': remote couldn't create file: Read only file system'"

Why is it read only!?

I am not sure. I haven't tried adb in a while tbh with you. I can give it a shot after work today and share findings with you.
But I will get free after 7 PM EST today.

 

[abhibnl]

V18.1
I wouldn't care so much if i didn't have a need to test my app on it.:crying:

Can you flash v18.1 zip on top of it again via custom TWRP i use? I linked it in an earlier post of mine. Honestly, I can't think of a reason it wouldn't work after flashing it via twrp.

 

[FSadino]

@abhibnl when I try to adb push something through terminal, it says "failed to copy file to /system': remote couldn't create file: Read only file system'"

Why is it read only!?

Maybe you need to "mount system" on TWRP first

 

[svandasek]

I am not sure. I haven't tried adb in a while tbh with you. I can give it a shot after work today and share findings with you.
But I will get free after 7 PM EST today.

I can confirm that my system image is Read-only while running. In TWRP it is perfectly accessible and writable. Idk what more i can do, but i want to stay on OOS.
WEIRD S h i t !