OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)

OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available) - OnePlus 7 Pro Guides, News, & Discussion

Hey everyone,
Here are the latest open beta builds based on Android 11 for the OnePlus 7 and OnePlus 7 Pro!
Please bear in mind that this is beta software and, as such, may be less stable than stable MP builds. If you are installing this build, we highly recommend you make a full system back-up before proceeding. We also recommend you read all the instructions and notes before proceeding.
OPEN BETA 1Changelog
System
Update to OxygenOS 11 version
Fresh new UI visual design brings you a more comfortable experience with various optimizations of details
Optimize the stability of some third-party applications and improve the experience
Camera
Updated the camera UI and optimized some of the function paths to offer more convenient operation
Newly added HEVC codec to reduce video storage size seamlessly, capture and shoot more without compromising on quality
Newly added access to a third-party app to share the picture by pressing and holding it in preview
Newly added the quick access to recording mode by pressing and holding the shutter button and by sliding the button, you can easily zoom in or zoom out
Newly added the playback display in Time-lapse mode to show the actual filming time
Ambient Display
Newly added Insight clock style, a joint creation with Parsons School of Design. It will change according to the phone usage data ( To set: Settings > Customization > Clock Style)
Newly added Canvas feature that can automatically draw a wireframe picture based on a lock screen photo on your phone（Path：Settings-Customization-Wallpaper-Canvas-Choose photo preview and it can be generated automatically）
Always-On-Display feature is under internal test and will be released in subsequent versions. In this build, you can use the "Ambient Display" by picking up your phone or tapping the screen, it can be turned on in the Settings.
Dark Mode
Added the shortcut key for Dark Mode, pull down the quick setting to enable.
Supporting automatically turn on feature & customize time range. path: Settings – Display – Dark Mode – Turn on automatically – Automatically enable from sunset to sunrise / Custom time range
Shelf
Newly shelf interface design, the interface is clearer
Added weather widget, animation effect smarter
Gallery
Supporting Story function, automatically form weekly videos with photos and video in storage
Optimize the loading speed of the gallery, and the image preview is faster
Known issues
Potential risks of increased power consumption and instability.
In some conditions, the Gallery app might be slower to load and some pictures may not be displayed in the Gallery.
The devices (earphones, speaker,s etc.) connected through Bluetooth may not be able to play sound occasionally.
Brightness adjustment may lag in some conditions.
Please note:
This Build is only for OnePlus 7/7Pro unlocked Non Carrier variants, and please make sure the battery level is above 30% and a minimum of 3GB of available storage space.
This OBT Build can be installed on the current Stable build. Later, if you rollback the build, you will return to the previous OxygenOS 11-based Open Beta build.
OPEN BETA 2Changelog
System
Optimized the sliding effect of the dynamic wallpaper
Improved power consumption in some scenarios
Optimized the adjusting intensity of automatic brightness to bring a more smooth using experience
Fixed the issue with the adapter not charging and using the headset at the same time
Fixed the issue in which the battery icon is not displayed on the status bar
Fixed the issue that 'Tips & Support' is not displayed in the Settings
Camera
Fixed the small probability flashback issue with the camera when unlocking in professional mode
Ambient Display
Newly supported Always-on ambient display feature (Only OP7 Pro) (Go to: Settings - Utilities - OnePlus Laboratory - Always-on ambient display)
OPEN BETA 3Changelog
System
Optimized the effect of unlocking animation
Fixed the issue of slow charging rate in some cases
Fixed the lagging issue when playing screen-recorded videos
Fixed the small probability failure issue with the Double Tap to Wake
Fixed the issue that Netflix could not play HD videos
Bluetooth
Fixed the silent issue when the Bluetooth transport protocol is changed to AptX
Network
Improved the stability of the Wi-Fi connection and reduce Internet outages
OPEN BETA 4Changelog
System
Fixed the issue that the battery icon in the status bar is abnormally displayed
Fixed known issues and improved system stability
Bluetooth
Fixed the issue where Bluetooth headsets are silent in aptX Adaptive mode
Note:
Enabling the AOD feature will lead to increased power consumption in the build. However, this will be optimized in the upcoming builds.
Please keep in mind that this is beta software. These builds are sometimes not as stable as our official OTAs generally are. By installing this update, you accept the potential risks. For those who were on previous versions of OnePlus 7 and OnePlus 7 Pro, we appreciate your active feedback and for reaching out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to getting your continued feedback via the Community app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you don't have the Community app installed on your device, feel free to download it HERE. You can check here for more information on the integrated Feedback tool.
Please note:
If you have already flashed an Open Beta (you are currently running the latest Open Beta), you will receive this new build as an OTA.
If you are not running open beta software and would like to, please refer to the flashing instructions and the full ROM on the downloads page here.
Once you migrate to the Beta path, you will continue to receive Open Beta OTAs. You will no longer receive the regular Official Stable OTAs.
Moving back to the Official OTA path from the Beta path will require a full install and clean flash (full wipe of all data and cache).
Make sure to let us know how you feel about the beta builds here in the thread too. We are watching.
Never Settle.
DownloadsOxygenOS 11 Beta 1Official LinkAndroid File Host MirrorOxygenOS 11 Beta 2Official LinkAndroid File Host MirrorOxygenOS 11 Beta 3Official Link (Missing)Android File Host MirrorOxygenOS 11 Beta 4Official LinkAndroid File Host Mirror
Android File Host CollectionsAndroid 10 FolderClick HereAndroid 11 FolderClick Here
Rooting Guides for Open Beta Versions of OxygenOS 11OxygenOS 11 Beta 1Download from Android File HostOxygenOS 11 Beta 2Download from Android File HostOxygenOS 11 Beta 3Download from Android File HostOxygenOS 11 Beta 4Download from Android File Host
Extracted image collectionsOxygenOS 11 Beta 2Download from Android File HostOxygenOS 11 Beta 3Download from Android File HostOxygenOS 11 Beta 4Download from Android File Host
Check your downloads after completion, for integrity, by confirming MD5 checksum, I would recommend the following for Windows : WinMD5 Free - Windows MD5 Utility Freeware for Windows 7/8/10
Both OnePlus's download site and Android File Host will show the MD5 which should be shown for your completed download, if your file doesn't match then it's not a good download.

Downloaded and Installed over magisk rooted OB19, flashed TWRP in EXKM, opened Magisk Manager and installed Magisk to Inactive Slot, rebooted and all is working well.
Edit: TWRP flashes when trying to boot to recovery and never opens. Gonna try a few things.
Edit 2: No functioning TWRP for OOS11 currently, flashed stock boot.img and now unrooted with stock recovery and boot. Gonna stay here and wait until TWRP is working for us.

Downloaded and installed on non-rooted GM1917 unlocked phone. Smooth update, no issues so far.

Jammmmm said:
Downloaded and Installed over magisk rooted OB19, flashed TWRP in EXKM, opened Magisk Manager and installed Magisk to Inactive Slot, rebooted and all is working well.
Edit: TWRP flashes when trying to boot to recovery and never opens. Gonna try a few things.
Click to expand...
Click to collapse
TWRP needs to be updated I think

Jammmmm said:
Downloaded and Installed over magisk rooted OB19, flashed TWRP in EXKM, opened Magisk Manager and installed Magisk to Inactive Slot, rebooted and all is working well.
Edit: TWRP flashes when trying to boot to recovery and never opens. Gonna try a few things.
Click to expand...
Click to collapse
Can you confirm TWRP and Magisk versions? I had tried TWRP with the Hydrogen Beta and it froze on fastboot, went back to stock release OOS cycle but looking to install this beta later after work.
I already have latest TWRP and 21.4 Magisk

Jammmmm said:
Downloaded and Installed over magisk rooted OB19, flashed TWRP in EXKM, opened Magisk Manager and installed Magisk to Inactive Slot, rebooted and all is working well.
Edit: TWRP flashes when trying to boot to recovery and never opens. Gonna try a few things.
Click to expand...
Click to collapse
twrp flashes when booting at all for me. if anyone comes up with a fix or workaround, please post.

peachypickle said:
twrp flashes when booting at all for me. if anyone comes up with a fix or workaround, please post.
Click to expand...
Click to collapse
I had to reflash the stock boot img.
Boot to fastboot mode (hold both volume and power), and install the stock boot.img from the full OTA. Here's a download link for you if needed: https://drive.google.com/file/d/16QVeHEGiJS_3aGIFM-CKq-3kiXW2GCeP/view?usp=sharing
Command will be "fastboot flash boot c:\users\whateveryourusernameis\downloads\boot.img" and then you can restart and it will boot.
From Telegram on some custom ROM threads, there's no working TWRP for OOS11 at this time.

djsubterrain said:
Can you confirm TWRP and Magisk versions? I had tried TWRP with the Hydrogen Beta and it froze on fastboot, went back to stock release OOS cycle but looking to install this beta later after work.
I already have latest TWRP and 21.4 Magisk
Click to expand...
Click to collapse
Had to go back to stock boot img, and now I'll just wait for a functioning TWRP for OOS11.

Jammmmm said:
I had to reflash the stock boot img.
Boot to fastboot mode (hold both volume and power), and install the stock boot.img from the full OTA. Here's a download link for you if needed: https://drive.google.com/file/d/16QVeHEGiJS_3aGIFM-CKq-3kiXW2GCeP/view?usp=sharing
Command will be "fastboot flash boot c:\users\whateveryourusernameis\downloads\boot.img" and then you can restart and it will boot.
From Telegram on some custom ROM threads, there's no working TWRP for OOS11 at this time.
Click to expand...
Click to collapse
Giving this a try. Thank you.

It worked, but now i have no root. How do i get back root?
EDIT: Grabbed the stock boot.img and went to magisk canary, patched it, sent it back to my computer. now im going to flash the magisk patched boot to device.

peachypickle said:
It worked, but now i have no root. How do i get back root?
Click to expand...
Click to collapse
If you were using Magisk, you'll have to patch the stock boot img in Magisk Manager and then fasboot install it. I think you could follow the steps from section 2B from this page: https://www.droidwin.com/patch-stock-boot-image-flash-magisk/

Can anyone test if any of the usual methods (like adb shell settings put global policy_control immersive.full=*) will hide the status bar / nav bar? If I can't hide the status bar here and mitigate the risk of burn in, I don't want to go to A11 yet

Anyone else getting a screen flash like the OS is attempting to enable one-handed mode or something? I've had it in Chrome and YouTube so far where a scaled down version of the app is popping up on the left side.

Jammmmm said:
Anyone else getting a screen flash like the OS is attempting to enable one-handed mode or something? I've had it in Chrome and YouTube so far where a scaled down version of the app is popping up on the left side.
Click to expand...
Click to collapse
Report it in the Feedback on OnePlus Forums (Should report all issues this way) : Feedback - OnePlus Community

Anybody know when we're getting AOD? I'm quite disappointed it still isn't there...
Also the insight inactivity display looks quite weird since it doesn't go all the way down.
Of course I understand that that is because of the fingerprint scanner, but having it be a little bigger would look good imo.

Jammmmm said:
If you were using Magisk, you'll have to patch the stock boot img in Magisk Manager and then fasboot install it. I think you could follow the steps from section 2B from this page: https://www.droidwin.com/patch-stock-boot-image-flash-magisk/
Click to expand...
Click to collapse
Did this, but now it gives me a 'unable to parse kernel log' error.

Seems like I have lost VoLTE after updating, and PDC is not working properly, followed the adb method for Android 11 but it says Connection Not Ready. So I'm not even sure if updating switched back the PDC profile or not.

I'm on OOS10 beta 19, rooted with twrp. Is there a specific process for upgrading to OOS11 beta 1 without losing root and data?

I am currently rooted, with twrp. I want to clean install this and keep the stock recovery for now since twrp isn't working anyway. How can I do this and also keep root?

Zocker1304 said:
Anybody know when we're getting AOD? I'm quite disappointed it still isn't there...
Also the insight inactivity display looks quite weird since it doesn't go all the way down.
Of course I understand that that is because of the fingerprint scanner, but having it be a little bigger would look good imo.
Click to expand...
Click to collapse
Supposedly next OB, depends on bugs and development though.

Related

[ROM][Sailfish][7.1.1] WETA 2.3 [NMF26Q][AudioPhile][22nd.Dec]

Welcome....
I just wanted to start by saying, we all know things are a little bit different with the setup of a pixel device. I think i have a handle of things though there is always a chance of death... i mean crash. Just please, always backup.
Also i am pointing scripts etc to partition slot system_a. Im still not exactly sure if you will come across problems when things update but i suppose we will see.
Now with regards to TWRP and Root. Please read up carefully on these two subjects as they are both pretty young at the moment. Flashing TWRP will be the first thing you need to do. After that, flashing a kernel as i am not including one at this point. Maybe later... If you have come from the same firmware then you wont need to flash a kernel, or vendor etc for that matter. Just boot into TWRP and flash the rom. If you wipe data, you will need to flash SuperSU SR4 after the rom, just to get the SuperSU app back into your app drawer. If you dont wipe data, then the SuperSU apk should still be there along with root binaries.
The zip is big, and will get smaller as time goes on. At this stage there is no real debloating, unpacking and repacking of the system.img hasnt been done yet, so the whole thing is in there at this stage. Also because this rom is based off of stock a stock google android prebuilt image, this means you dont need to flash Gapps. In fact dont, itll break things.
On a wiped data, first boot, i did notice Google TTS crashes though after the play store updates, this goes away. Also if other google apps are crashing because you're lazy and didn't wipe data. Then try uninstalling the apps updates in the play store and reinstalling.
EDIT - One more caveat, you are going to need an extra 1.7gb of free space just for the rom flash, this is on top of the actual size of the zip. I have had to have the system.img extract to a tmp folder before flashing, this gets wiped on boot, so you get that space back after reboot.
I think thats all....
--->

Odds and Ends, Tricks to getting broken things working again
This is a very general post, and can possibly be used on other phones and roms.
My SystemUI keeps crashing, even after a fresh stock install...
If SystemUI is modified, and this modification causes a crash, this can damage the runtime data for systemui. This means that even though you flash a bone stock systemui, it may still crash on boot. Wiping all data fixes this, though that is a pain in the butt. All you need to do is go to, and delete /data/system/users/0/runtime_permissions.xml. You can do this in TWRP file manager. Reboot, job done. This will reset your wallpaper but who cares.
V4A keeps asking to install drivers, or V4A stops processing...
This is a constant issue people have, except for me...... what does this mean? it means i, as a rom dev, am constantly and consistently wiping data and sdcard for testing purposes. This tells me one thing i think is obvious, but of course i may be wrong, bad data will kill V4A. But i will say that flashing a stock vendor.img AFTER the rom will break V4A and Dolby (flash vendor.img before rom). SuperSU is crucial. If in doubt, flash the supersu zip again after rom install. V4A and Dolby both need selinux to be set to permissive. This is achieved with SuperSU and its boot scripts. Also Spotify will stop processing sometimes if a track plays through to the next by itself. (Skipping tracks isnt affected). This bug can be remedied by turning off gapless playback.
--->

<--- Installation Instructions --->
This is a dynamic post, or in other words, it may change from build to build, when it does, i will inform users with the new ROM link post.
First off, this post is a little late, i should have done this earlier but it is what it is and its here now. At this time this is directly related from updating from WETA 1.0.5a (may work on others) to WETA 2.0.
- Boot Slots -
If you are new to the Pixel and are about to start flashing, there is something you need to realize. The Pixel devices have two sets of partitions to boot from. This allows seamless updating on googles part. Google it.. Anyway, in the ROM aroma menu you will notice options to select which boot slot to flash to, A or B. You need to flash to the correct slot, which would be the slot you are already booting into. You need to check this by booting into bootloader and it will be listed there. It states your boot slot in TWRP also when you select reboot. Though i would trust Bootloader more at these early stages.
Both methods below will work also if you are coming from stock. You just need to get yourself TWRP'd and Rooted.
Method #1 - No Wipe (dirty)
This method isn't usually recommended when jumping bases, but worked ok this time around. These are the steps i took that were successful for me.
I started out being on NDE63V WETA 1.0.5, TWRP, Rooted
1. Boot into bootloader and check what boot slot is active, take note of it.
2. Boot into TWRP
- dont do any wiping whatsoever.... the weta install automatically wipes dalvik and cache.
3. Flash NMF26O vendor.img using TWRP
4. Flash WETA 2.0 selecting the correct boot slot from step one in aroma.
5. Reboot system, this can take 5-6min as it rebuilds Dalvik
--->
Method #2 - Clean install (Wiped data) or (img flash only - no wipe)
OK, so we are jumping from 7.1 to 7.1.1. There are going to obviously be some changes, thats why i was surprised that Method #1 actually works without issue.. Having said this, when using the method above (method #1) but wiping all your data instead.. This creates a problem with acore crashing constantly on boot. This led me to trying to understand the system apps a little better, and from what i can see, all the system apps are odexed but the odex files live on another partition that gets loaded up on first boot. With changes between the old and the new firmware and its apps there is a good chance the odex file from the old firmware doesnt play well with the updated apk. And the only way to get those odex files onto your device is to flash the firmware package. Regardless... if you want a clean install this time around, follow these steps
1. Backup everything, because you may lose everything, or you may not.
2. You are going to need the stock firmware package and a pc, (aosp download page)
3. You are going to need fastboot drivers, google how to install adb and fastboot. You should already have them if you own this or any nexus devices.
4. OK this is where you flash the whole firmware package. If you do it as is, you will wipe all data on your phone. This includes photos and music. So again backup if you care.
- NOTE, you can preserve all of your data by opening the flash-all.sh(linux) or flash-all.bat(windows) script in a note pad and deleting the (-w) in the line (fastboot -w update image-marlin-nmf26o.zip)
- the process goes like this, open a terminal, cd into the firmware folder, and run the flash-all script (sh flash-all.sh for linux) (double click the flash_all.bat file for windows)
- Now you have all the stock img's flashed to your device on the active boot slot
5. You can now start the rom install process, you are going to need to re flash TWRP and SuperSU.
6. Now all you have to do is Flash the WETA rom. Select the boot slot that you have active in bootloader. Check it first then flash to it.
7. Reboot system, boot may take 5-6min
--->

Mine

WETA 1.0x (verizon)
Added a version based off the Verizon firmware NDE63X, all associated files are on the download page. Be sure to read the labels of files before flashing
I also renamed the V version to make things a bit clearer.
Download Page
--->

Perfect. Thanks for the effort

Download complete, commence flashing. Thank you for getting a ROM out in a day it's got to be like a record.

I've also realized I made a typo in a script that installs the V4A 2.3.4.0. it's not a big deal but what essentially happens is you are left with both versions of v4a being installed. Only 2.3.4.0 is functional though. Just delete the system/priv-app/ViPER4Android manually until I update
? --->

FIRST ROM Awesome!!

Thanks buddy! Been using your audio and ui mods on my phone since you released them. Glad to see you've put out the first rom once flashing was available. I'll probably get it installed tonight.
Again, thanks for all your awesome work!

WETA 1.0.1
Fixed V4A 2.3.4.0 install again. Removes V4A 2.5.0.5 properly...
Download Page
--->

Respect to you sir.

Flashed with no issues. Had a few force-closes on startup, mainly with clock and calendar. I ended up deleting those with TiBu and re-downloading from the Play Store. Everything else is flawless. Thanks!

stompysan said:
Flashed with no issues. Had a few force-closes on startup, mainly with clock and calendar. I ended up deleting those with TiBu and re-downloading from the Play Store. Everything else is flawless. Thanks!
Click to expand...
Click to collapse
Yeah I had a weird clock crash that fixed itself after updating. I think that was after a flash without wiping data though

So I bought my pixel from Verizon and I have the NDE63P will the Verizon roms work ?

Do we flash everything from within TWRP?

I am not trying to be rude in any way and I'm thankful for any and all development that happens on the devices but are there any differences to installing this rom vs just installing your system mods you have posted?
Sent from my Pixel using Tapatalk

JohnnyMcG said:
So I bought my pixel from Verizon and I have the NDE63P will the Verizon roms work ?
Click to expand...
Click to collapse
I'd recommend updating to November before flashing, or at least flashing the vendor from the November image as NDE63P is October. You'll want NDE63X

JohnnyMcG said:
So I bought my pixel from Verizon and I have the NDE63P will the Verizon roms work ?
Click to expand...
Click to collapse
joetheshmo said:
I'd recommend updating to November before flashing, or at least flashing the vendor from the November image as NDE63P is October. You'll want NDE63X
Click to expand...
Click to collapse
First thing you need to do is Unlock you bootloader and keep it that way. Before its patched by Verizon.

[ROM][UNOFFICIAL][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Wifi
Bluetooth
Audio
LED
USB
RIL
Encryption
Fingerprint
Camera
Hall sensor
DT2W
Selinux Enforcing
Broken
nothing
Source code:
device: https://github.com/lenovo-devs/android_device_lenovo_TBX704
device-common: https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
Important
If you are using this ROM first time, wipe data. Wipe data completely. I mean the option where you need to enter "yes". Use this option and then flash the rom.
This ROM only works with the TWRP I added.
If you want to use GAPPS, flash it directly after flashing ROM. Don't let the ROM boot. Otherwise your device will not get certification, so you will not have Google Access.
Instructions (thx @matshias, just changed few lines to get ROM flashing working)
Put your ROM (and GApps) onto your sdcard (sdcard must be exfat or fat32, NTFS not supported)
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Format data using this tutorial
Flash ROM
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Restart
Download
2019-08-12 (hotfix)
• hotfix: fix camera
• security patch level: 2019-08-01
ROM
TWRP (Use this for TB704L too; you guys don't need 4g in recovery )
You can also get the latest ROM updates from codeworkx here:
https://sourceforge.net/projects/lineageos-on-lenovo/files/16.0/TBX704/
Bulids are same, just update.
Older downloads
2019-07-14
• security patch level: 2019-07-05
ROM
TWRP
2019-06-22 (thx @codeworkx)
• bugfixes and performance improvements
• fix camera detection for ov8856 sensor
ROM
2019-06-09 (thx @codeworkx)
• bugfixes and performance improvements
• set_permissive.zip patch no more required
• TWRP 3.3.0 support
• security patch level: 2019-06-05
ROM
2019-05-14
• fixed sim issue for x704l caused in last update
• fixed a little issue on x704l (should improve battery life)
• added double tap to wake
• latest changes of LineageOS
ROM
2019-05-10
• fixed wifi after fresh installation
• changed scheduler to bfq
• added wireless display broadcast
• improved performance
• removed ril elements from X704F variant
• security patch level: 2019-05-05
ROM
SIM fix for X704L
2019-04-30
• fixed fingerprint bug caused by SELinux
• removed PS3/PS4 controller hid, as it doesn't work
• optimized performance
ROM
2019-04-28
• fixed notifcation led (light was only red for notifications)
• fixed ril values
• added support for PS3/PS4 controller
• SELinux is enforced after boot
ROM
2019-04-24
• fixed hall sensor
• fixed camera
• fixed long time to wake up screen
ROM
2019-04-22
• fixed fingerprint removement after reboot/user switch
• fixed partially camera (same like in 15.1)
• fixed reboot to recovery and bootloader for advanced reboot menu
• fixed long time to wake up screen
• fixed deep sleep
ROM
2019-04-21
• intital release
• TB-X704L is now integrated, no more additional zip required
• You can update from previous version
ROM
Optional downloads
Dolby Digital Plus (use the TWRP one)
GAPPS (use 9.0 arm64; I suggest using pico variant)
Mounting system rw
This is impossible on our tablet. The bootloader enforces verity check, which causes this issue.
The only possibility is to modify bootloader, what is dangerous and requires good knowledge.
there is a workaround using magisk with a mod. which mounts your system rw on mount:
https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259
Thanks
@highwaystar_ru (he gave me the important hint, also used his sources and his thread )
@LumenReaper (for his work with CM14.1, where I took big part of his device tree :fingers-crossed
@Flowah123 for the TB-X704L files :fingers-crossed:
Donations
Thanks to @rorzer, @Preyer11, @Tschumi, @MrMagic, @max_work, @vicenza & 5 x anonymous
Please don't support Lenovo and buy their tablets
Code:
[I]Updates vary depending on the model where our tablets receive Android and security updates after the introduction.
We announced Tab 4 10 Plus in February 2017 and since then it has received seven OTA updates.
However, this model has reached the end of its update cycle and will not receive any more updates in the future.
- Lenovo (2018-05-11)[/I]
Just seven updates and not even one major upgrade, please don't support them.
Reporting bugs
Please tell what mods you are using and what tablet variant (TB-X704F or L or ABCDEFGH..)
If your tablet doesnt start:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files and upload it here.
if your tablet starts and bug appears later:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files
start your tablet normal, let the bug appear, enter adb root
use adb logcat and adb shell dmesg, copy the content to a text file and upload here
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus, ROM for the Lenovo Thinkpad Tablet
Contributors
yener90, codeworkx
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Created 2019-04-21
Last Updated 2019-06-11

Yener, you're amazing. Thanks to you we are on the current Android version. Installation ran without problems. I was so free to attach some screenshots.
What I noticed so far:
- I can confirm the list of things that are working and things that are broken.
- Significantly newer kernel (3.18.138) than LineageOS 15.1 (3.18.115) and of course Nougat (3.18.31).
- Magisk 18.1 works fine (had problems with it under LOS 15.1)
- Waking up the device by pressing the power button or using the fingerprint sensor takes an unusually long time (3-4 seconds). I caught myself several times pressing the button again.
Will you offer a new TWRP 3.3.0?

LumenReaper said:
- Waking up the device by pressing the power button or using the fingerprint sensor takes an unusually long time (3-4 seconds). I caught myself several times pressing the button again.
Click to expand...
Click to collapse
Wiil be fixed tomorrow release. It has the same bugs like the little older brother:
Fixed reboot to recovery and bootloader from reboot menu
Fixed long time to wake up screen
Fixed Deep sleep
Also there is an issue with fingerprint. After restart it doesn't work anymore. This will be also fixed.
LumenReaper said:
- The release is an engineering build. @yener90 isn't it common to release userdebug?
Click to expand...
Click to collapse
Everything is normal, I don't know, why it is like that
LumenReaper said:
Will you offer a new TWRP 3.3.0?
Click to expand...
Click to collapse
I'm not planning to change something on TWRP currently.

yener90 said:
Wiil be fixed tomorrow release. It has the same bugs like the little older brother:
Fixed reboot to recovery and bootloader from reboot menu
Fixed long time to wake up screen
Fixed Deep sleep
Also there is an issue with fingerprint. After restart it doesn't work anymore. This will be also fixed.
Click to expand...
Click to collapse
Okay, thank you very much. I can also confirm the problem with the fingerprint scanner, it occurs not only after a reboot, but also when you switch between two users.
yener90 said:
Everything is normal, I don't know, why it is like that
Click to expand...
Click to collapse
Maybe I can help here: You will get an engineering build if you run lunch lineage_TBX704-eng. If you run lunch lineage_TBX704-userdebug instead, you will get a userdebug build.

LumenReaper said:
Okay, thank you very much. I can also confirm the problem with the fingerprint scanner, it occurs not only after a reboot, but also when you switch between two users.
Click to expand...
Click to collapse
Same bug, will be also fixed.
LumenReaper said:
Maybe I can help here: You will get an engineering build if you run lunch lineage_TBX704-eng. If you run lunch lineage_TBX704-userdebug instead, you will get a userdebug build.
Click to expand...
Click to collapse
I didn't change anything How do you come to this conclusion? in Device Info HW App its listed as userdebug build

yener90 said:
I didn't change anything How do you come to this conclusion? in Device Info HW App its listed as userdebug build
Click to expand...
Click to collapse
Forget it, my mistake. I should read more carefully.

Update
2019-04-22
• fixed fingerprint removement after reboot/user switch
• fixed partially camera (same like in 15.1)
• fixed reboot to recovery and bootloader for advanced reboot menu
• fixed long time to wake up screen
• fixed deep sleep
ROM

I'm impressed!

Nice update @yener90, thank you very much.
Now, here's a good one, dirty flashed the V9 over your V8 and then flashed Gapps and Magisk19.
All went well and I was impressed with how well the tablet ran and its stability, a few apps needed updating and then I used the tablet for about 2 hours or so, no problems whatsoever.
So I did a backup and rebooted, now the tablet powers off after approx 30secs. or so displaying the 'powering off' notification but instead of actually powering off it reboots to TWRP.
I have wiped Dalvik and cache but to no avail.
I used your TWRP to flash the ROM and use the original TWRP to create the backups/restorations to/from Ext SD . TB-X704V (L)
Any ideas please, as it was running very well prior to doing a backup ?
TIA.

thanks yener
flashed it 5min ago and looking for something not working but so far, it runs nice

Sparkrite said:
Nice update @yener90, thank you very much.
Now, here's a good one, dirty flashed the V9 over your V8 and then flashed Gapps and Magisk19.
All went well and I was impressed with how well the tablet ran and its stability, a few apps needed updating and then I used the tablet for about 2 hours or so, no problems whatsoever.
So I did a backup and rebooted, now the tablet powers off after approx 30secs. or so displaying the 'powering off' notification but instead of actually powering off it reboots to TWRP.
I have wiped Dalvik and cache but to no avail.
I used your TWRP to flash the ROM and use the original TWRP to create the backups/restorations to/from Ext SD . TB-X704V (L)
Any ideas please, as it was running very well prior to doing a backup ?
TIA.
Click to expand...
Click to collapse
I'm suprised that it even starts. I really don't know. Maybe encryption got broken or filesystem error.

yener90 said:
I'm suprised that it even starts. I really don't know. Maybe encryption got broken or filesystem error.
Click to expand...
Click to collapse
Why are you surprised, I understood you had incorporated the 'L' fix into the ROM ?
It's doing my head in, it was running well, had rebooted a few times, intentionally, and all was well.
Make a backup and then the problem appears and I don't have time to do much before it re-boots, unfortunately.

Sparkrite said:
Why are you surprised, I understood you had incorporated the 'L' fix into the ROM ?
Click to expand...
Click to collapse
For me it looks like TWRP made some rubbish, which lead to failure on partition.
Normally you would end up in a bootloop. The system wouldn't start.
Use my TWRP then use in TWRP internal file manager.
Go to the location sys/fs/pstore and upload the files here.

Preyer11 said:
thanks yener
flashed it 5min ago and looking for something not working but so far, it runs nice
Click to expand...
Click to collapse
Does SIM work for you? On this release I tried to get it work on wifi and lte variant of tablet.

yener90 said:
Does SIM work for you? On this release I tried to get it work on wifi and lte variant of tablet.
Click to expand...
Click to collapse
sadly not,
i see all the settings in software (grey out) and it keeps asking for a Sim Card but none of my 3 Sim Cards avaible is noticed
could somebody that also use the L confirm this ? not that i am sitting on a broken sim card slot

Preyer11 said:
sadly not,
i see all the settings in software (grey out) and it keeps asking for a Sim Card but none of my 3 Sim Cards avaible is noticed
could somebody that also use the L confirm this ? not that i am sitting on a broken sim card slot
Click to expand...
Click to collapse
Its not broken. There is something wrong.
I need to compare both kernels X704F & X704L and check that issue out.

Hey, just wanted to report i also dirty flashed and it worked without problems, i own the F model. Works great so far, awesome! However i have one little bug (i guess it is one): long pressing an app icon to move it does sometimes not work, nothing happens then. but i have this since the 15.1 version. does anyone also have this?
kind regards

I dirty flashed it over lineage 15, after wiping system and caches. I flashed the gapps after the rom and everything works perfectly so far. No bugs yet or problems with apps and files. Thanks Yener, I had lost all hope of ever seeing this device updated.

hi @Yerner90 installed ROM using the format data method (ie wiped everything), so far everything is working good so thanks again for ROM

@yener90 great job, works a treat and you've fixed the led colours and added screenshot back on. I'm keeping an eye on the battery as it's draining much quicker I think.

[OOS][Stable][OP6T Global][OP6T Tmobile] Oneplus 6T stable OOS guide thread

OOS stable for Oneplus 6T Global
This thread is an attempt to make things clean for OP6T users.
It will contain latest zip links for OOS stable.
It will contain a brief guide on how to root, install TWRP , how to update with or without those elements.
6T global edition is supported by thread readers and me, and T Mobile converted specific concerns will be handled by community under the supervision of @Scott, thanks to him for the help.
It will not contain basics like ADB and Fastboot connection with a computer. Experiment, read, there are many and many tutorials on the internet for that. Don’t forget there is a world outside XDA and that you can perform a search on any search engine to grab information.
It will not cover by decision the ‘patching boot.img’ method for gaining root. It’s not necessary to use it when we have a working TWRP and Fastboot. If you want to try it search on the internet about ‘extracting boot.img from payload.bin’ and then use Magisk Manager to patch it.
Please NO discussion about: Magisk itself, custom kernels, debloating (whatever method you want to use), custom ROMS… Only STOCK STABLE OOS.
If you just want to flash custom kernels, no need to have TWRP, Ex Kernel Manager and Franco Kernel Manager for example can take care of that (see Play Store to grab those apps), and backup your stock kernel.
ALWAYS USE LATEST VERSIONS of the different tools used. Don’t ask for help if you’re using 6 months old TWRP or Magisk. Update it first.
First a bit of what I have understood about our phone, and its main specificity, i.e A/B slots.
A/B slots, what else ?
This structure is meant to enable to have two different versions of the SAME ROM, one slot will contain the previous version of the ROM, the other slot will contain the updated one. If you are on slot A and running 10.3.0, the update process will lead to have 10.3.0 on slot A and 10.3.1 on slot B. On next boot the bootloader will automatically boot updated one (i.e slot B will be flagged as the active one). In case of issues during boot process the bootloader will switch the active slot back to the ‘old’ version(here slot A) that was booting fine.
This means that IT’S NOT a dual boot feature!! If you want to run a custom ROM it’s better to have the same custom ROM on both slots and not a mix of OOS and custom ROM. But that’s already OT so let’s stay focus, each custom ROM should provide clear instructions about that.
Having a slot phone means that there is no Recovery partition. So if you ‘fastboot flash boot twrp.img’ it will overwrite your boot partition and thus the ROM kernel and can lead to issues. The .img file is only meant to be temporarly booted. Recovery (stock or TWRP) is a part of the boot ramdisk.
Some simple facts about slots and flashing in TWRP:
Flashing a whole ROM (OOS for example) will automatically flash it to the currently inactive slot and switch it to be the active one (that works also with stock recovery, when performing a ‘local update’)
Flashing a ROM overwrites completely the boot partition (in recent Android versions, flashing process is using partition RAW images and not files like it was before): that means that TWRP and Magisk (if present) will be ERASED.
Flashing TWRP installer will flash it AUTOMATICALLY ON BOTH SLOTS (and will erase Magisk if present)
Magisk (and GAPPS but it only applies to custom ROMs), when flashed with TWRP is only flashed in ACTIVE slot. That’s why you must REBOOT to recovery BEFORE flashing Magisk to have it installed on the active updated slot. And that explains why you must flash it last.
That said, if you stay on OOS, YOU DON’T care about slots, just remember those basics to understand why you have to respect some steps, and let the recovery take care of slots. Messing manually with them results often in soft bricks
Downloads
OOS stable full signed zips: thanks to @Some_Random_Username, @Titokhan, @trollavin (their thread here)
If the above doesn’t work anymore just let me know I’ll find something else.
FYI you can still go to Oneplus website but they take time to update it to latest version… And there is no archives.
XDA:DevDB Information
OOS Stable thread support, ROM for the OnePlus 6T
Contributors
Striatum_bdr, Scott
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-02-05
Last Updated 2020-02-06

Rooting
CHANGELOGS
OOS 10.3.4:
System
Updated launcher version to 4.1.6
Updated Android Security Patch to 2020.05
Improved system stability and fixed general bugs
Phone
Fixed the issue with default country in assisted dialing when SIM2 is in roaming state
Newly added Work-Life Balance to help prioritize notifications and allocate time wisely (India only)
Newly added Epic Games in Game Space (India only)
OOS 10.3.3:
System
Fixed the issue with a black screen randomly appearing while playing games
Updated GMS package to 2020.02
Updated Android Security Patch to 2020.04
Improved system stability and fixed general bugs
Network updates
Integrated VoLTE & VoWifi support for Telenor – Denmark
Integrated VoWifi support for RJIO – India
Phone
Newly added OpSoprts features in the shelf
Added OnePlus Roaming feature: choose a plan without worrying about the SIM card while traveling
Cloud Sync updates [India only]
Updated the CloudService to Version 2.0
OOS 10.3.2:
Changelog 10.3.2
System
• Fixed the screen flickering issue while swiping up to unlock
• Improved system stability and fixed general bugs
• Updated Android security patch to 2020.02
OOS 10.3.1:
Changelog 10.3.1
System
Fixed the issue with a black screen appearing after unlocking the device using fingerprint
Fixed the issue with the animation logo while rebooting the device
Fixed the issue with device heating up while charging
Fixed the random disconnection issue with 5Ghz Hotspot
Improved system stability and fixed general bugs
Updated Android security patch to 2019.12
Camera
Optimized the image preview time in the Pro mode
Fixed the camera crash issue
Gallery
Fixed the issue with videos and images not displaying in Gallery
OOS 10.3.0:
Changelog 10.3.0
System
Updated system to Android 10
Brand new UI for Android 10
Fixed the automatic reboot issue
Added the notch area display option in the Settings (Settings - Display - Notch display - Hide the notch area)
Fixed the issue with lock screen appearing even after unlocking the device with the password
Fixed the issue with Navigation bar after upgrade
Fixed the Digital wellbeing option missing in the settings
Updated Android security patch to 2019.11
Fingerprint
Fingerprint unlock functionality improvement
Enhanced the fingerprint animation
Camera
Camera performance improvement
Wifi Connectivity
Fixed the issue of Wifi connection to 5Ghz networks
OOS 10.0.1:
Changelog 10.0.1
System
Updated system to Android 10
Brand new UI for Android 10
Updated Android security patch to 2019.10
Fixed the fingerprint identification issue
Fixed the animation lag for fingerprint unlock
Fixed the automatic reboot issue after upgrade
Camera
Improved the performance and fixed known issues
Wifi Connectivity
Fixed the 5Ghz WiFi connection
OOS 10.0.0:
Changelog 10.0.0
System
Upgraded to Android 10
Brand new UI design
Enhanced location permissions for privacy
New customization feature in Settings allowing you to choose icon shapes to be displayed in the Quick Settings
General bug fixes and improvements
Full Screen Gestures
Added inward swipes from the left or right edge of the screen to go back
Added a bottom navigation bar to allow switching left or right for recent apps
Game Space
New Game Space feature now joins all your favorite games in one place for easier access and better gaming experience
Contextual Display
Intelligent info based on specific times, locations and events for Ambient Display (Settings - Display - Ambient Display - Contextual Display)
Message
Now possible to block spam by keywords for Message (Messages - Spam - Settings - Blocking settings)

ROOTING (+/- TWRP)
Magisk zip is to be found here
TWRP latest .img and installer are to be found here
Don’t use all-in-one tools, you’re a grown up person you can to it by yourself. Yes you can.
If you're not rooted and run an OOS version older than 10.3.1, update your phone normally to latest OOS stable version then do as below
If you’re not rooted and running 10.3.1 or higher, those are the simplest steps to gain root.
Unlock your bootloader (will wipe everything…): “fastboot oem unlock” from a computer (see beginning of OP to know why I don’t detail this) with phone in fastboot mode
Grab latest Magisk zip on your phone and latest TWRP .img on your computer (AND TWRP installer .zip on your phone if you want to install TWRP permanently). Boot in fastboot mode your phone.
Then :
“fastboot boot twrp_latest.img” (adapt to the name and path of your twrp file)
within TWRP, flash TWRP installer .zip if you want to keep TWRP
flash Magisk zip (always AFTER flashing TWRP)
Reboot
(you can theoretically use the TWRP feature ‘install recovery ramdisk’ to avoid flashing twrp installer but never tested)
Note: please STOP using blue_spark TWRP!!! Support for OP6T has been stopped long time ago, only OP6 twrp is still actively supported by eng.stk (errors are mandatory if you flash it on 6t). I even see people that use a 3.2.x version of blue_spark...

UPDATING WITHOUT ROOT
If your bootloader is locked (meaning no root no TWRP, factory state), the update process is trivial, OOS (or Oxygen Updater if you use it) will grab a patch file (around 100MB max usually) and will apply it and will ask you to reboot. Everybody should be able to do this as it’s the normal way every phone on earth updates itself… If major changes are present sometimes you’ll have the whole ROM file. It doesn’t matter anyway it leads to the same destination.
If your bootloader is unlocked but without root, the only difference is that OOS (or Oxygen Updater) will download the WHOLE ROM (around 1.8GB) and will apply it then ask for rebooting
UPDATING WITH ROOT (+/- TWRP)
Whole ROM update is mandatory. You can wait for System Update to download it or grab manually the zip file or use Oxygen updater. You then go in Settings > System > System Update > clic on the upper right cogwheel then choose ‘Local Update’ and select the zip file (If you download the OTA .zip file manually you must place it in the root of user data, like /data/media/0/ i.e the user internal storage, or eventually in the .OTA folder if there's one. If you use Oxygen Updater or System automatic donwload it will be right placed).
The following update method is the preferred one (even if you have TWRP, recommended by some TWRP devs) due to frequent changes in partitions by OnePlus
apply the ROM update via Settings > System > System Update > Local Update
DON’T REBOOT
Open Magisk Manager
[If you have TWRP, go in Modules menu, clic on ‘+’ and choose latest TWRP installer zip file on your phone. Don’t use Retention A/B Script Magisk Module I had issues with it] [then stay in Magisk Manager and do the next step]
On main screen of the app clic on ‘install’ next to Magisk paragraph
On the pop up menu confirm ’Install’
On the next pop up menu clic on the last entry: install on inactive slot (after OTA update)
Then only reboot.
The order can be changed (the most important thing to preserve is Magisk, TWRP is easy to flash back):
Update without taking care of TWRP, just Magisk part ("install to other slot after OTA thing")
Once rebooted to updated system, flash TWRP as a module with Magisk Manager
Install Magisk again using Magisk Manager ("direct install" option)
There are infinite debates about uninstalling or not Magisk Modules before updating. Most of the times nothing to touch, sometimes there could be issues, instead of uninstalling perhaps just inactivate them by precaution before updating.
Note: If you are rooted and run an OOS version older than 10.3.1, the above method should work, but you can also update your ROM to latest stable without taking care of root/TWRP and then root again as described in post #2
If you want to try TWRP way:
Reboot to TWRP
Flash OOS update
Flash TWRP installer
Reboot to Recovery
Flash Magisk
Reboot System
IF YOU ARE INTO A SOFT BRICK
Don't forget the Vol+/Vol-/Power_button combo that can save you from a non responding phone...
If you can boot in fastboot mode, flash the stock ROM with fastboot. A little trick is to edit the flash-all-partitions**.bat and remove ‘-w’ (-w means that the partition will be wiped before flashing) from the script, it will prevent personal data wipe. Or flash manually all partitions one by one, without ‘-w’ flag evidently. Some partitions can’t be flashed with fastboot, for that once booted back to OOS, download and install by ‘local update’ method the same ROM version you’ve just restored with fastboot (see the linked thread to know why, emojis issues for example sometimes).
If you can’t go in fastboot mode, use Oneplus MSM tool. See there and there.

Thank you for the time and effort for this thread as I just came from a Sony XZ1 as I was a bit confused by the different posting on how to do what...

Thanks for a detailed post.
Can I update my rooted OP6T 9.0.17 (TWRP 3.3.1-2+ Magisk) directly to rooted 10.3.1 using the following guide :-
1. Reboot to Twrp 3.3.1-2.
2. Flash Twrp 3.3.1-31 installer.
3. Rebbot to recovery twrp 3.3.1-31.
4. Flash Magisk uninstaller
5. Flash 10.3.1 OS
6. Flash TWRP 3.3.1-31 installer
7. Reboot to recovery.
8. Flash Magisk.
9. Reboot to system.

Goormeetsingh said:
Thanks for a detailed post.
Can I update my rooted OP6T 9.0.17 (TWRP 3.3.1-2+ Magisk) directly to rooted 10.3.1 using the following guide :-
1. Reboot to Twrp 3.3.1-2.
2. Flash Twrp 3.3.1-31 installer.
3. Rebbot to recovery twrp 3.3.1-31.
4. Flash Magisk uninstaller
5. Flash 10.3.1 OS
6. Flash TWRP 3.3.1-31 installer
7. Reboot to recovery.
8. Flash Magisk.
9. Reboot to system.
Click to expand...
Click to collapse
That sounds correct

Thank you for taking the time to do this. I am now subscribed

Very nice. Subscribed. Thank you.

I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please

jazzgott said:
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
Click to expand...
Click to collapse
I think you should format data after unlock. I think it's kinda safety feature if some1 try to get into your storage by unlock bootloader. But wait by some1 to confirm

jazzgott said:
I've been trying to do this for the past 8 hours.
Here's what I do, please tell me where am I going wrong
- msm 9.13
- update to 9.17
- local upgrade to 10.3.1
- boot system to enable oem unlock, usb debug
- boot to fb, unlock bootloader
- boot system
- boot fb, boot twrp
- flash twrp, both slots
- reboot twrp
here I get different results:
- try to install magisk, all internal storage encrypted. sideload, but still no cigar. try to install on both slots by rebooting twrp to a and b and sideloading magisk, still no cigar
OR
- flash magisk, boot system, no magisk
OR
System boots, we have root, we have everything, but file manager shows emptyness. Can't modify any files on internal storage. Via phone and via PC.
Now tell me what am I doing wrong, please
Click to expand...
Click to collapse
I know you managed to sort things as you posted it in another thread. Anyway I don't understand why you had to do all those steps .... But anyway the goal is achieved

Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
THANK YOU VERY MUCH. Several of us out here!

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
Welcome back sir Scott!
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
Thank you for this thread.

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
hodgestl said:
THANK YOU VERY MUCH. Several of us out here!
Click to expand...
Click to collapse
I second this, thank you and also thanks to OP!!
Is there any way we could get a change log for the stable update?

hodgestl said:
THANK YOU VERY MUCH. Several of us out here!
Click to expand...
Click to collapse
r3dp0is0n2012 said:
Welcome back sir Scott!
---------- Post added at 03:27 AM ---------- Previous post was at 03:26 AM ----------
Thank you for this thread.
Click to expand...
Click to collapse
..Cory.. said:
I second this, thank you and also thanks to OP!!
Is there any way we could get a change log for the stable update?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Your all welcome!
I love this phone and like to help so lets see how this goes down :good:
...
---------- Post added at 10:48 PM ---------- Previous post was at 10:39 PM ----------
As far as the change log, that could be a challenge. I have never been able to find the full change log for the international version. The T-Mobile Version is here: https://www.t-mobile.com/support/devices/android/oneplus-6t/software-updates-oneplus-6t. Because this is something we can direct link to, I dont think it should be included in full text here on XDA. I think a link the in first or second post under "useful info" would be sufficient.
As far as the international version goes, I know every verison number by heart.. worst case scenario, I could just google each OTA version and grab the change log from the from the first Android news site that pops up. Unless someone else knows of where one might be at? We could also start at version 10.0.0 because I feel anything older than that is irrelevant.

For changelogs it could be done eventually by grabbing them on the net. There is clearly something between Oneplus and changelogs....
I'm ask for an extra reserved post to have more space and avoid too long posts.

Changelogs added in post #4

Scott said:
Just an FYI: I will be helping to support the T-Mobile version of the device in this thread.
Click to expand...
Click to collapse
Awesome. I've been running a converted TMobile phone and can't wait b for them to related A10 so I can have android pay back without root

Development [ROM][CUSTOM] <<>> Polar Star Pure Edition <<>>

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Polar Star Pure Edition This ROM is unified for Edge S Pro / Edge 20 Pro.
Custom ROM based on Global Stock firmware
Android 13 RETAIL_T1RA33.55-15-10-1
Android 12 RETAIL_S1RA32.41-20-16-11
Android 11 RETAIL_RRA31.Q3-19-86-6
This custom ROM uses stock kernel without modification.
>>> Preliminary requirements <<<
Only unlocked bootloader
>>> What's done <<<- Root permissions via Magisk v.26.1 (26100) Stable (Android 12 - Magisk v.25.2 (25200) Stable) ;
- Removed the restriction on writing to the system, which in Android 11 is in Read Only (r/o) mode by default, which eliminates the possibility of modifying it. In this firmware it is possible to mount the system in Read Write (r/w) mode. Encryption is preserved in this case.
- System passes SafetyNet test, device is certified;
- NFC and GPay with unlocked bootloader and Root worked!
- Cleaned and lightened the system;
- Built in additional system color accents (only Android 11);
- Updated Moto and some Google applications; Android Auto is integrated into the system;
- Removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher. In the Android 13 version of the firmware, this feature is implemented systematically.
- YouTube removed, because I use YouTube Vanced;
- Installed apps AdAway ad blocker, Audio Recorder, File Manager, Gallery;
- Ringtones, notifications, alarms sounds have been replaced;
- Mod Logo and Bootanimation;
- The button for calling Google Assistant is reassigned to the: Android 12 - camera shutter and use it to activate the lockscreen; Android 13 - camera launch;
- Beginning with the PStar_PE_A12-41-20-16-5-01 build, I slightly increased the volume of the ear speaker.
How can I turn down the speaker volume?
Use RootExplorer or similar app to delete the mixer_paths.xml file from /vendor/etc. Rename the mixer_paths.bak file to mixer_paths.xml. Restart the device.
Click to expand...
Click to collapse
- No Warez!
What was done in the latest update (Dec, 05, 2022) :
- Updated ROM base to stock firmware version S1RA32.41-20-16-9;
- New logo & bootanimation;
- Updated Magisk to v25.2;
- Updated applications to the latest versions at the time of ROM build;
- Updated Moto Display;
- Updated Moto Widget;
- Updated Moto Audio Recorder;
- Updated Asus File Manager;
- Completely removed Google Assistant and reassigned its button to the camera shutter;
- Removed Google location history and telemetry apps;
- Removed Turbo and Wellbeing apps;
- Slightly increased the volume of the hearing speaker.
>>> Installation Instructions <<<1. Extract the system partition images from the archive (see the Download tab) and copy them to any convenient location on your PC.
2. Reboot the device into bootloader mode and:
- If you are installing the ROM for the first time or if you want to install the firmware with all data from the previous firmware removed, then use the _flash_custom.bat executable file;
- If you want to install the ROM as an update to its previous build, then use the _update_custom.bat executable file. Then all your data and applications will be saved and the system will be updated.
3. Phone will reboot into fastbootd mode and flash installation will start automatically. When the installation is completed the phone will automatically boot into the system.
4. When the boot is complete perform the initial settings.
Spoiler: Magisk v.23001(21)
Don't update Magisk and Magisk Manager! Build Magisk (d7e7df3b) (23010) (may be and laters builts) breaks Magisk Hide and SafetyNet.
5. Do not update Magisk Manager, but install this version Magisk Manager 23001(21) in the attached files.
Then you will be asked to configure the working environment. We agree. The phone will automatically reboot after the setup is complete.
6. In the Magisk Manager Settings, disallow "Check Updates". In "Update Channel" select "Custom channel" and in the opened window indicate the link:
Code:
https://raw.githubusercontent.com/topjohnwu/magisk-files/fde0bddfc5683cc8524e323e95f6c8432fbd11da/canary.json
If you are still updating, you can rollback to a working version of Magisk using the following instructions.
-= Rollback Magisk to version 23001 (21) =-
a) Uninstall Magisk with Magisk Manager - click "Uninstall Magisk" button, select "Complete Uninstall".
b) The phone will automatically reboot at the end of the uninstall process.
c) During the rebooting process, press and hold the "volume down" button until the phone enters the fastboot mode. Connect the phone to PC with a USB cable.
d) Extract the boot_magisk.img image from the archive to the folder with the drivers adb:
Android 12 S1RA32.41-20-16_boot_magisk
Android 11 RRA31.Q3-19-86-6_boot_magisk
e) Install boot_magisk.img with the command:
Code:
fastboot flash boot boot_magisk.img
f) Boot into the system and follow steps 5-6 of the basic Instructions for installing the firmware.
>>> Notes <<<
With the update Stock base to RRAS31.Q3-19-86 the problems described below are corrected.There is a hang-up when entering the connection settings of the NFC and Bluetooth settings. Don't worry about this. You just need to wait a little while.
There is no hang-up when you enable/disable NFC and Bluetooth via the icon from the Notification bar. This happens due to uninstalling any system applications.
>>> Download <<<
Please, don't put the ROM, or links to it, on other sites without the author's permission!
Android 13 PStar_PE_A13-55-15-10-1-02
Android 12 PStar_PE_A12-41-20-16-11-02
Android 11 PStar_Pure_Edition-19-86-6-01

If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Now the ROM is the same for both modifications.

ROM update S_Pro_Pure_Edition. Added ROM 20_Pro_Pure_Edition.

Updated the ROM for both devices.
What's done:
- replaced the CommandCenter_2 widget with a slightly larger one;
- updated Moto and some Google applications;
- remapped the Google Assistant button to the camera shutter button;
- removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher.

Thanks for the ROM.
I was wondering if widevine was L3 or L1 on this.

Updated the ROM to the base RRA31.Q3-19-50.
Since 11.10.21 the firmware is unified for both versions of the phone.

Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.

rendmazues said:
Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.
Click to expand...
Click to collapse
Nvm my request, I just have additional question. Does this rom supports OTA? When I searched online, they said that OTA will be downloaded thru playstore so I think it is possible to be supported if that is the case.

do you happen to have any links where I can download your custom rom aside from mega.nz.
Click to expand...
Click to collapse
No. I don't have any free space on my other file stores.

rendmazues said:
Does this rom supports OTA?
Click to expand...
Click to collapse
No. This ROM only supports its own updates, which will be released as Stock firmware updates become available.

Hello
Can you add "Task lock" function in recent apps screen?
I want to keep apps I often use in task list, even if I push "all clear".

Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.

ilia3367 said:
Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.
Click to expand...
Click to collapse
Thanks for the tut on how to downgrade, I accidentally updated mine. I'll do the downgrading later.

ilia3367 said:
If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Click to expand...
Click to collapse
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.

hello I just did the steps to be root, I succeeded. install root explore and link2sd to be able to remove apps they give me per, isos, but when I want to uninstall I can't.
root explore does not let me change to r / w and uninstallation fails and link2sd removes but reboot and this is the app.

tarshar01 said:
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.
Click to expand...
Click to collapse
Now the ROM is the same for both modifications.

Naza1879 said:
root explore does not let me change to r / w and uninstallation fails
Click to expand...
Click to collapse
Are you getting Root on the Stock firmware or on this Custom ROM?
Did Root Explorer ask Magisk for permission the first time it started up?

hello, everyone! I want to know this ROM's back main camera whether support longer than 1/4s exposure by Gcam?
Now I'm using Chinese Rom. It has a serious touch screen issue, and doesn't support longer than 1/4s exposure by Gcam.

Sir, Can you make a video on how to install this on moto edge 20 pro, On YouTube and share link

Updated the ROM to the base RRA31.Q3-19-50-1 - - - PStar_Pure_Edition-19-50-1-02

[CLOSED][STABLE] [ANDROID 12] Pixel Experience ROM for Galaxy A70

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.0
Warning:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
BUGS:- bluetooth ear/headphones do not work workaround- ( go into phh treble settings misc features and enable force-disable a2dp offload)
If bluetooth crashes your system disable media recommendations under Sound & Vibration > Media > Show media recommendations
mtp not working
sim 1 incoming and outgoing does not work (you can revieve calls and call but you wonth hear anything nor will your mic go trying to fix) (workaround is to put your sim into slot 2)
offline charging don't work, it would keep looping the charging screen (May happen, may not happen, if it happens to you, just press vol down and power everytime you want to charge your phone to reboot it to system. Charge only in SYSTEM and RECOVERY, as prolonged charging screen loop can cause burn-in.
Instructions on how to install (read carefully):
1. Make sure you already have your bootloader unlocked, TWRP flashed.
2. Unpack the "xz" or "zip" archive and put the .img file onto the sd card or internal (if you dont have a sd card do step 3 then transfer the img file to your phone)
3. In TWRP head to factory reset format type yes and hit enter
4. Flash the img file (as system obviously)
4.1 Install the custom kernel that I recommend, most stable and not going to mess up your device (optional)
5. install magisk (the one linked below only, others WILL NOT WORK) (optional)
6. Reboot and enjoy!
Magisk:
https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip
ROM:
Mod Edit: DL link removed.
Recommended Custom Kernel:
Stable kernel
Kernel source: https://github.com/TheLinuxAdmin/Eng_kernel_a70q
Enable fast charging: Fast charging magisk module and choose 4500mah 27w
FOR THOSE WHO HAVE FLASHING ISSUES / ROM BOOTLOOP / BOOTS INTO FASTBOOT:
TigerBootFix 1.1.1
Apparently there is an issue with devices not being able to flash ANY GSIs and if you do it would boot you into fastboot mode. If you have this kind of issue, try this:
https://forum.xda-developers.com/attachments/vendor_a11-zip.5518175/ - use Android 11 Vendor. Flash the zip via twrp.
IF IT STILL DOESN'T WORK!
install oneui via odin, boot into oneui change date to 3 months from now
check for updates and then go to developer mode and tap on OEM Unlock
boot into download mode
flash twrp and vbmeta (or a custom recovery that works with android 12, like twrp 3.6)
boot into twrp
do format data
flash multidisabler
flash rom
flash kernel as boot
do factory reset
reboot
if it boots you into fastboot shutdown flash twrp only via Odin and try another factory reset and reboot (In twrp)
For maximum performance (Battery life will not be affected):
TigerTweaks 3.0: FDE AI but BETTER!
Ktweaks is no longer used, just FDE AI and GMS Doze.
Step 1
- Uninstall ANY OTHER KERNEL MANAGER app including smartpack/Ktweaks to avoid conflict, since this app uses AI and machine learning to dynamically boost performance when needed
- Install FDE AI Magisk Module to make it a system app, thus it will work better and removes all kernel locks from OEMs (I'm looking at you, Samsung) https://github.com/feravolt/FDE.AI-docs/releases/download/12.4.1m/FDE.AI-as-system-app.MAGISK.zip
- Update FDE AI to the latest version by downloading the latest APK here, since the fde ai magisk module will only install fde ai 12.4.1, not the latest version: https://github.com/feravolt/FDE.AI-docs/releases
- Move to the bottom of the screen and select AI Chat, then type /advancedai (no space, no uppercase letters). This will going to make the AI more effective, without you having to do anything.
- Go to the settings tab and use the AUTO settings for FDE AI.
Why not performance? Why not powersave?
Well, by setting the FDE to stick to max performance or power savings at all times, youre missing out the one key advantage that FDE has. Which, the AI can shift between performance and power savings (or even in between depending on the load) in real time. If your phone is on idle, FDE would go into Automatic/Power Saving mode, and if you're playing your favourite game or is doing a heavy task, FDE would go into Automatic/Performance mode. So, you will get performance ONLY when you need it. If your phone is on idle, it would switch fde to powersave, thus saving a ton of battery life!
- Tap on boost heavy games, force doze, and disable throttling.
NOTE: Only disable throttling on NON OC KERNELS! Disabling throttling in OC KERNELS can lead to overheating!
- Good features to keep in mind:
1. /gamelistadd package name
You can add your own heavy game here! For example, if you play war robots, go look at the package name for War Robots, and then enter the package name (for war robots it's com.pixonic.wwr) because your game might not be listed on the heavy games list! Though this is not strictly necessary as FDE AI can detect if you're under heavy GPU/CPU load while playing games, so FDE can adjust to Automatic/Performance which will boost your game, even if it's not included in the heavy games list.
2. /downscale
You can downscale your resolution without having to adjust fiddly DPI settings! The AI would work on everything for you to scale it adaptively, so no risk of soft bricking!
For example:
Downscale 540 for 540p (qHD)
Downscale 720 for 720p (HD)
Downscale 1080 for 1080p (FHD)
Downscale 1440 for 1440p (QHD)
Downscale 2160 for 2160p (4K)
Step 2
- Install GMS doze magisk module. Helps to reduce power consumption of google play services which will increase performance and extend battery life.
Credits:
Phhusson Pixel experience team
Ponces Development
Zainullahk1234 Thread, Optimization, and bug fixes

double tap to wake fixed in new build!
also notification bar is now white and so is power menu in light mode this is subject to change

reserved

this is just a mirror of the a71 thread for bugs report here https://forum.xda-developers.com/t/...ience-for-a71-all-models-fod-working.4377973/

Zainullahk1234 said:
this is just a mirror of the a71 thread for bugs report here https://forum.xda-developers.com/t/...ience-for-a71-all-models-fod-working.4377973/
Click to expand...
Click to collapse
yes, but since it is a gsi I am going to share it to ppls who need the ROM for their devices that dont get android 12, GSIs are designed to work with any device and I tested it works on a70 too.

TigerLake said:
yes, but since it is a gsi I am going to share it to ppls who need the ROM for their devices that dont get android 12, GSIs are designed to work with any device and I tested it works on a70 too.
Click to expand...
Click to collapse
how did you make it to work, because on my a70 model keeps bootlooping after installing the rom

i'll try

i get pushed into the download mode

Der_Googler said:
i get pushed into the download mode
Click to expand...
Click to collapse
Bogdan2376 said:
how did you make it to work, because on my a70 model keeps bootlooping after installing the rom
Click to expand...
Click to collapse
do format data
flash rom
flash kernel (optional)
flash magisk (optional)
do format data again
reboot

is still the same issue -_-

Wanted to say a few things:
1. This is GSI nay?
2. It will only boot with Android 11 vendor for now
3. Try to find the vndklite variant, it allow for read-write system which is very useful later on

JakunTech1010 said:
Wanted to say a few things:
1. This is GSI nay?
2. It will only boot with Android 11 vendor for now
3. Try to find the vndklite variant, it allow for read-write system which is very useful later on
Click to expand...
Click to collapse
1 yes
2 it boots on a10 and it is better if you have a10
3 no that uses a lot of storage and i dont support it it can also have more bugs so im not supporting it

is this only for android 12? i installed this to my a70 android 11 and doesn't work. i follow the process of installing it and i got bootloop sometimes it put me in download mode.. and when i exit i found that there is no os installed in the warning of TWRP.. thanks for this. i hope this work to my device in the future

Eu Sunt Dracul said:
is this only for android 12? i installed this to my a70 android 11 and doesn't work. i follow the process of installing it and i got bootloop sometimes it put me in download mode.. and when i exit i found that there is no os installed in the warning of TWRP.. thanks for this. i hope this work to my device in the future
Click to expand...
Click to collapse
it should work with android 11 but that is unkown
try this:
flash system
flash kernel
flash magisk
do format data
do factory reset
reboot

Zainullahk1234 said:
it should work with android 11 but that is unkown
try this:
flash system
flash kernel
flash magisk
do format data
do factory reset
reboot
Click to expand...
Click to collapse
do you mean by flashing the system is i need to flash the .zip?

Eu Sunt Dracul said:
do you mean by flashing the system is i need to flash the .zip?
Click to expand...
Click to collapse
no the img

Zainullahk1234 said:
no the img
Click to expand...
Click to collapse
after i flash the .img, i flash the kernel and it gives me error "failed to mount 'system_root' (Invalid argument).

Eu Sunt Dracul said:
after i flash the .img, i flash the kernel and it gives me error "failed to mount 'system_root' (Invalid argument).
Click to expand...
Click to collapse
reflash stock rom change date to 2 months from now flash twrp and try agin

Zainullahk1234 said:
reflash stock rom change date to 2 months from now flash twrp and try agin
Click to expand...
Click to collapse
do you mean stock rom is the original rom of a70? or can i flash my downloaded lineageOS 18.1?

Zainullahk1234 said:
reflash stock rom change date to 2 months from now flash twrp and try agin
Click to expand...
Click to collapse
alright i got the stock rom, is the flashing tool i will use is odin. right?

Database Develop

welcome