Develop Bugs

[O][8141/8142][.270] M-ROM: Xposed, Daydream compatible

Hello everyone.
The XZ Premium is the LAST of the Mohawk tribe. It's got the genuine feel of unleashed power.
But this amazing masterpiece really DOES lack great ROMs. And, as you guys are not too active in this field, our Chinese friends took their turn.
So as nobody else did organize it into a separate ROM thread, I present this ROM to you. This ROM is NOT my work.
also, I'm NOT responsible for any damage you might encounter.
You MAY request for some corrections, but, as I'm NOT the author of the ROM, I'm not authorized to modify the ROM, NOR i'm really willing to.
Don't expect any updates from ME!
All I've done is the translating of the installer from Chinese into English, replacing some of the software with the international version, tweaking and making this step-by-step tutorial for you. I've spent a few days testing it, to make sure you guys won't have much trouble.
I did it voluntarily, because this ROM is SO GREAT that I just feel necessary to share it with you guys!
All credits to machao44 @ bbs.gfan.com
Remember, this CUSTOM ROM is a modified STOCK ROM.
And the MAIN reason you might need this ROM is the Xposed.
Features:
JanJan's .270 kernel and patch
Aroma configurable installer
DEODEXED
Magisk OR SuperSu
Viper4Android (Optional)
Xposed WORKING (!!!) (XposedInstaller.apk NOT included)
Daydream WORKING (!!!) (Install the Daydream Enabler patch from Magisk repo)
XZ2 Themes
XZ2 UI
XZ2 Camera
XZ2 Loops
XZ2 "Ambient Screen"
Some other stuff from Google Pixel and XZ2
Some old widgets you've been missing (Photos, Top Contacts, Camera)
And some extra minor tweaks.
Changelog [Google Translated from Chinese]
Code:
Updated to 47.1.A.12.270
---------------------------------------
Updated to 47.1.A.12.235 (must be forced to brush 235, otherwise drm is invalid)
Add Android P system animation (Setting - Custom Function)
Add pixel navigation bar animation (set - custom function)
Add status bar clock adjustment (Setting - Custom Function)
Add ram display to multitasking interface
Update multitasking interface locking function Restart does not become unlocked
Update multitasking interface lock icon to display directly
---------------------------------------
Updated to 47.1.A.12.205
Brush machine optional SuperSU or Magisk
Other adjustments
---------------------------------------
Updated to 47.1.A.12.179
Update to graphics brush
(Supported in the TWRP download of the graphics brush machine)
Brush machine optional streamline
Add status bar speed
Add task lock
Add v4a sound
Fixed an error in Ultra STAMINA mode
Other adjustments
Update app
---------------------------------------
Replace the boot animation for the XZ2 original animation
Add dialing to enter the number to display the attribution
Update the attribution of the call log display (display operator)
Add attribution details in the contact details
Delete the third-party call vibration that comes with it
Add native call vibration function (within dialing settings)
Porting XZ2 environment display
Add environment display extensions (lift up bright screen, gesture sensing, pocket mode)
Other adjustments
Ps: There is a patch for the XP framework to use normally in the download.
---------------------------------------
Update the bottom package to 12.119
Fix Bluetooth sharing error
Join the theme of XZ2C
Join the network location of the Bank of China
---------------------------------------
Porting XZ2 icon ringtone media tone theme etc.
Porting XZ2 UI system interface
Porting the XZ2 main camera
Porting XZ2 Loops System Animation
Porting the XZ2 lock screen clock and animation
Porting the Xperia Touch desktop clock (same style as XZ2)
Open environment display
Update app
Note that users of XO1.2.2 and previous roms must clear the data in.
---------------------------------------
Updated to 47.1.A.12.75
Update app
---------------------------------------
Updated to 47.1.A.12.34
Call vibration
Call Recording
Extended desktop
Navigation bar height adjustment
---------------------------------------
Separate the Google service (you can directly brush the Google service pack after you have finished brushing the rom)
Replace magisk with supersu (magisk will cause some apps to be abnormal and new magisk will lose the drm patch)
No longer integrate twrp
Fix screen image
Fully merged with odex
---------------------------------------
1.1.1 update added xperia assistant and several errors caused by not extracting lib
Updated to 47.1.A.8.49
Crack system signature
Add Sony's desktop widget
Add dial T9 pinyin
Add call attribution
Add night mode (blue filter)
---------------------------------------
Fix bug
SELinux status changed to PERMISSIVE
---------------------------------------
Based on 8.0 47.1.A.5.51
Lightweight and streamlined
DRM patch
Disable RIC
TWRP3.1 (power button + volume under power off)
Magisk
Bank Profile + Google Service
PS: Because XZP's TWRP does not currently support graphics flashing (reported to TWRP authors), this ROM does not have a graphics flash.
Old rules, the first version does not add extra features
Lots of tweaks in this ROM have been taken from xda, so credits go to those people as well:
@sToRm//
@zxz0O0
@serajr
@the_brad
@tobias.waldvogel
@Myself5
@sudamod
@mokee
@niaboc79
Instructions and download links are in the 2nd and 3rd post.

First of all, you WILL need an Unlocked Bootloader. I hope you know what it means, otherwise you'll have to RTFM.
#. Long ago I've learned from some wise guy who recommended to always flash a full stock FW before installing a custom ROM based on it. You MIGHT or MIGHT NOT want to do it. But I've NOT tested this FW without flashing the full .270 image upfront via Flashtool, with FULL wipes. (Or, flash 16.20 if you want to go for the 1.8.0. Also, HERE is the discussion on it)
Or this .235:Newflasher+.235
0. Push the Aroma-ready TWRP via ADB.
1. Boot into the Recovery (hold power&vol-) and install the ROM. You DON'T HAVE to reboot afterwards, so you might want to add all the other ZIPs to the queue.
2. Install the Xposed-v90-SDK26-arm64-beta3.zip, which contains - no surpsise - Xposed SDK. You might want to install the SYSTEMLESS version of it, but you will need to find and download it yourself and install it at THIS step, instead of this particular zip.
3. Install the Xposed FIX. It has to be done separately for an unknown reason. I've decided NOT to play with it, trying to embed it into the ROM itself, and left it as a separate zip. MAYBE you don't need it if you're not going to use Xposed, but why use this ROM at all then??
4. Install the Kernel Patch. It's the standard Kernel Patch from JanJan.
5. Optionally, you MIGHT want to install the Sound Mod. I recommend you NOT doing so, because the volume on it is cranked up TOO much, and on my device it began producing crackling sound not even reaching the maximum volume.
6. HERE I INSTALL GAPPS. You might NOT need to do so, but if you want to use the phone with Daydream VR, and also if you might want to use Google Camera (sadly no HDR+, but I use it mainly for a cool Bokeh and 3d panoramas!), you'll need to install the SUPER arm64 8.0 package, which is almost 1gb big. Don't worry, we're going to debloat our device in step 7, deleting 80% of that crap...
p.s. To enable Daydream, install Daydream Enabler magisk module from repo
p.p.s. To enable Google Lens, install Google Lens Enabler magisk module from repo. It will also let you backup the photos with the Google Photos app in original quality as if it were the Google Pixel FOR FREE! It WON'T TAKE UP YOUR SPACE!!!
7. Debloater. Here is what it removes:
Code:
delete_recursive("/system/app/AdvancedLogging");
delete_recursive("/system/app/AnonymousData");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/com.sonymobile.infoapp");
delete_recursive("/system/app/com.amazon.mShop.android.shopping");
delete_recursive("/system/app/com.facebook.appmanager");
delete_recursive("/system/app/com.facebook.katana");
delete_recursive("/system/app/com.s.antivirus");
delete_recursive("/system/app/com.sonyericsson.xhs");
delete_recursive("/system/app/com.sonymobile.xperialounge.services");
delete_recursive("/system/app/com.spotify.music");
delete_recursive("/system/app/com.swiftkey.swiftkeyconfigurator");
delete_recursive("/system/app/com.touchtype.swiftkey");
delete_recursive("/system/app/DemoAppChecker");
delete_recursive("/system/app/DeskClock");
delete_recursive("/system/app/DMAgent");
delete_recursive("/system/app/Exchange-release");
delete_recursive("/system/app/ExternalKeyboardJP");
delete_recursive("/system/app/externalkeyboardsinternational-release");
delete_recursive("/system/app/FitnessPrebuilt");
delete_recursive("/system/app/fota-service");
delete_recursive("/system/app/Gmail2");
delete_recursive("/system/app/GoogleHindiIME");
delete_recursive("/system/app/GoogleHome");
delete_recursive("/system/app/GoogleJapaneseInput");
delete_recursive("/system/app/GooglePinyinIME");
delete_recursive("/system/app/GoogleZhuyinIME");
delete_recursive("/system/app/IddAgent");
delete_recursive("/system/app/KoreanIME");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/Lifelog-googlePlayLiveRelease-4.0.A.0.14-8388622");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/newssuite");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/playstationapp");
delete_recursive("/system/app/PlusOne");
delete_recursive("/system/app/PrebuiltBugle");
delete_recursive("/system/app/PrebuiltDeskClockGoogle");
delete_recursive("/system/app/PrebuiltExchange3Google");
delete_recursive("/system/app/PrebuiltGmail");
delete_recursive("/system/app/PrebuiltNewsWeather");
delete_recursive("/system/app/SemcEmail-release");
delete_recursive("/system/app/SemcWarrantyTime");
delete_recursive("/system/app/SomcMovieCreatorRmm-release");
delete_recursive("/system/app/Tycho");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/com.facebook.services");
delete_recursive("/system/priv-app/com.facebook.system");
delete_recursive("/system/priv-app/com.sonymobile.retaildemo");
delete_recursive("/system/priv-app/EnterpriseService");
delete_recursive("/system/priv-app/NexusLauncherPrebuilt");
delete_recursive("/system/priv-app/sonyentrance2-release");
delete_recursive("/system/priv-app/textinput-chn-xxhdpi-release");
delete_recursive("/system/priv-app/Turbo");
delete_recursive("/system/priv-app/UpdateCenter-release");
delete_recursive("/system/priv-app/usb-mtp-backup-transport");
delete_recursive("/system/priv-app/usb-mtp-factoryreset-wrapper");
delete_recursive("/system/priv-app/usb-mtp-fotaupdate-wrapper");
delete_recursive("/system/priv-app/usb-mtp-update-wrapper");
Voila.

1.6.1 Google Disk.
1.8.0 - as is!!
Beetle84's contribution, translated 1.8.0 installer
The folder should contain:
aroma-ready twrp.img
1. ROM image. Google, Yandex
2. Xposed SDK
3. Xposed FIX
4. Kernel Patch (JanJan's)
5. Optional Sound Mod (DontBelieve)
7. Optional debloater patch
Enjoy!
Known issues:
#0. I'm not the author of the ROM. I'm only sharing with you what's working for me. I am not a professional developer either. Please remember it's a COMMUNITY, not a workshop.
#1. Substratum DOESN'T WORK.
#2. If you WON'T upgrade your phone fully to stock .270 via FLASHTOOL (!), or if you won't flash the included .235+newflasher beforehand, your G8141 WILL NOT RECEIVE ANY SIGNAL.
#3. SOME G8141 users still report having NO signal. Try flashing your device as G8142, and then flash the G8141 kernel manually before step 4. You can find the Shoey's G8141 kernel inside the zip file of ROM. Don't foget to patch.
#4. If you can't stand the one tab in Settings that's in Chinese, here's the translated settings.apk
1.8.0 settings.apk
#5. DON'T UPDATE XPOSED AND MAGISK.

Screenshots.
{
"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"
}

You are going to hate me, but I still have no signal. This is driving me crazy.

It is a very very fast and stable rom
Used the original 1.6.1 and it is fast

Mobfigurz said:
You are going to hate me, but I still have no signal. This is driving me crazy.
Click to expand...
Click to collapse
So, you redownloaded the ROM, and you chose the G8141 kernel while installing, and it didn't work?
Are you sure you're using the right files?
Did you flash 235 or 270 beforehand? Try flashing full .270 or 235 upfront and then install this rom on top of it.
Else, I don't know why @amakuramio has no problem with her G8141...

karrouma said:
It is a very very fast and stable rom
Used the original 1.6.1 and it is fast
Click to expand...
Click to collapse
I only translated the installer and embedded the G8141 kernel in it. Adding gBoard doesn't count, so, it's the same ROM you're talking about And yes it's fast!

Very fast!!
Thanks again for your time

saved-j said:
So, you redownloaded the ROM, and you chose the G8141 kernel while installing, and it didn't work?
Are you sure you're using the right files?
Did you flash 235 or 270 beforehand? Try flashing full .270 or 235 upfront and then install this rom on top of it.
Else, I don't know why @amakuramio has no problem with her G8141...
Click to expand...
Click to collapse
Yes, redownloaded your files and installed in this sequence, 1, 2, 3, 4, 7 and no change with the signal, still not able to pick up a network, even when I search for it and click it, tell me I cannot register on the network.
I did a clean flash of .270 yesterday and started on the files you shared, I will flash .270 from scratch now and run through the files you provided and report back.
I do appreciate all your help, this is just a glitch and hopefully I will have a fully functioning device soon.

Mobfigurz said:
Yes
Click to expand...
Click to collapse
Very strange.
By the way. Once you flash the stock FW... Run it and check if your phone receives the signal on the stock FW.
Then try dirty flashing (without wiping /data).
Also, after the full installation, if the signal still doesn't work, try pushing the JanJan's kernel via ADB and patching it, then wipe dalvik/cache and try for luck once more.
If there's no luck, maybe you really need to flash the .235 ~150mb that @amakuramio mentioned. I'll try to find it and then I'll upload it to the Google Disk. I'll let you know when it's there.

Mobfigurz said:
Yes
Click to expand...
Click to collapse
DONE.
Try here
Is your phone provider-locked, or locked to the network, or sim-card, or in any other possible way? Call the provider and tell them you "updated the software and the phone stopped receiving the signal, so you had to roll back to be able to make this call"... Maybe try another SIM card as well... Check everything to exclude every single stupid possibility!

saved-j said:
Very strange.
By the way. Once you flash the stock FW... Run it and check if your phone receives the signal on the stock FW.
Then try dirty flashing (without wiping /data).
Also, after the full installation, if the signal still doesn't work, try pushing the JanJan's kernel via ADB and patching it, then wipe dalvik/cache and try for luck once more.
If there's no luck, maybe you really need to flash the .235 ~150mb that @amakuramio mentioned. I'll try to find it and then I'll upload it to the Google Disk. I'll let you know when it's there.
Click to expand...
Click to collapse
Stock 270 have network signal. Images attached.
I think something is missing, there is nothing I have removed or added to your file collection to alter it, so something must not be doing what it should be doing for single SIM, G8141.
I am going to flash your files over this now and see what happens.
Update - Back to no signal, I think the Kernel is not set for G8141, only G8142.
Update - Flashing JanJan's Kernel obtained from his/her thread gives me the same issue, no signal. I am going to flash from the beginning, stock .270 and then JanJan's kernel and see what happens. But, if I do that and have a signal, would flashing Xposed and the Xposed fix in TWRP without M ROM give me a working Xposed?
UPDATE - The issue is not with JanJan's Kernel,it is with M ROM, as I installed Stock .270, installed JanJan's Kernel and additional files and booted fine, strong signal, Root and DRM, but obviously no Xposed.

Mobfigurz said:
M ROM
Click to expand...
Click to collapse
I'm sorry bro. I will think what could be causing this issue. I'll try to inspect the differences between 8141 and 8142, but don't expect it to be soon ?

Mobfigurz said:
Stock 270 have network signal. Images attached.
I think something is missing, there is nothing I have removed or added to your file collection to alter it, so something must not be doing what it should be doing for single SIM, G8141.
I am going to flash your files over this now and see what happens.
Update - Back to no signal, I think the Kernel is not set for G8141, only G8142.
Update - Flashing JanJan's Kernel obtained from his/her thread gives me the same issue, no signal. I am going to flash from the beginning, stock .270 and then JanJan's kernel and see what happens. But, if I do that and have a signal, would flashing Xposed and the Xposed fix in TWRP without M ROM give me a working Xposed?
UPDATE - The issue is not with JanJan's Kernel,it is with M ROM, as I installed Stock .270, installed JanJan's Kernel and additional files and booted fine, strong signal, Root and DRM, but obviously no Xposed.
Click to expand...
Click to collapse
I have g8141 and dont have a signal issue, try to download internet settings or manually enter APN.

Beetle84 said:
I have g8141 and dont have a signal issue, try to download internet settings or manually enter APN.
Click to expand...
Click to collapse
His phone doesn't receive ANY NETWORK. Like if there was no sim-card. With all respect, I don't think your advice is relevant.
But it's surely very important to know that you don't have the signal issue on your 8141.?

[email protected] updates the brand new ROM.

saved-j said:
His phone doesn't receive ANY NETWORK. Like if there was no sim-card. With all respect, I don't think your advice is relevant.
But it's surely very important to know that you don't have the signal issue on your 8141.?
Click to expand...
Click to collapse
After tinkering with the packages and flashing them in different sequences I managed to get going. In M ROM Aroma installer I ignored the G8141 option and let it flash the G8142 files and bingo, Network Signal and showing SIM 1, the software thinks it is a 8142 and I tinkered some more, got Xposed running, but then, I had a major issue, System UI crashed and would not re-appear after installing some Xposed modules.
I think, if I can find 12.75 I am just going back to that, I just need a stable, working phone for daily use and though others seem to work, mine does not. SO I thank you all for your help and assistance.
Who knows where I can get a '3 UK' 12.75 ftf or any 12.75 ftf as Xperifirm does not keep older roms?

Mobfigurz said:
After tinkering with the packages and flashing them in different sequences I managed to get going. In M ROM Aroma installer I ignored the G8141 option and let it flash the G8142 files and bingo, Network Signal and showing SIM 1, the software thinks it is a 8142 and I tinkered some more, got Xposed running, but then, I had a major issue, System UI crashed and would not re-appear after installing some Xposed modules.
I think, if I can find 12.75 I am just going back to that, I just need a stable, working phone for daily use and though others seem to work, mine does not. SO I thank you all for your help and assistance.
Who knows where I can get a '3 UK' 12.75 ftf or any 12.75 ftf as Xperifirm does not keep older roms?
Click to expand...
Click to collapse
I have the Australian .75 firmware I think and I have TurboROM p75d which I will upload to mega for you. My internet's pretty crap though

I have 12.75 both in US and CE1. And I also have pretty much all Turbos roms

MIUI-Pro ROM(V8) ported For msm8916 & snapdragon 410 devices like LYF Wind 3(LS-5502)

MIUI-Pro ROM(V8) ported For msm8916 & snapdragon 410 devices like LYF Wind 3(LS-5502)
Hey Guys!
Its Amit,
I recently decided to bring back the dead soul of my old phone with the help of custom ROM's.When I searched for my phone i.e LYF Wind 3(LS_5502) on google i came with no result except for the TWRP Recovery.
By the way, my phone's i.e--LYF Wind 3(LS-5502) android version is lollipop V5.1.1. It's running stock android provided by the LYF company till then no updates,no security patches and no-nothing.
Then I decided to port ROM for my phone with the help of millions of tutorials and guide & also with intense work.
I finally had made a stable custom Rom-----MIUI-Pro Miui 8 on top of lollipop-V5.1.1.
It has following features:----->
VOLTE Working{Added option to turn on and turn off volte}
All Miui 8 Features
Wi-Fi & Hotspot Working
Bluetooth
All sensors working
Gesture-Anywhere feature
Animation Control
small DPI
feature to disable buttons
Themes Working
All System app extra-customization
Added feature to import third party themes
Notification customization
Home-screen customisation
Mi Account{Working}
App Lock
Dual Apps
Weather Mate(M8) intead of normal weather app
Volume Boost
Rounded-Corners
Dolby Atmos Pre-installed
Pre-Rooted
Mix Explorer
Jeejen Home
Chinese Bloatwares Removed
One-Handed Mode
And many many many many many more
*But I faced some bugs like this which i was not able to solve.:--------->
Camera
I was not able to completely port camera.
When I start phone everytime(power ON), and open camera it work for a slight second(upto 4-5 seconds)but then after it says ''can't connect to camera''. And after it whenever i launch camera app it says the same.
Except Camera this ROM is smooth and very much stable than the stock one.
I'm using this for quiet a month and had felt no issues
It had better battery backup,batter RAM Management
If any dev is seeing this please help me solving th camera problem described above
And here is the link for the miui pro ROM :------->
https://drive.google.com/file/d/1mo7cfWtFoAymOrrHShRSCBZP-0f9XGVv/view?usp=drivesdk
Note That Gapps are already included.
Procedure for Installing ROM:-------->
1) Download the ROM
2) Boot to twrp and wipe data,system,cache
3)Install the ROM so simple.
4)Enjoy!
SOURCE :
As The oem has not release the kernel source which is againt gpl that android follows.
So I have ported ROM on top of prebuilt stock kernel.
Kernel
Have Fun!!!
And
Once
Again
THANKS!

I will like to give this a try..

Here is the link:----->
https://drive.google.com/file/d/1mo7cfWtFoAymOrrHShRSCBZP-0f9XGVv/view?usp=drivesdk
Feel free to feature on YouTube.
Thanks!

please solve the camera issue
please solve the camera issue

Thanks for this Rom
I have been searching for MIUIPRO 64 bit Rom to port since long time, thanks bro for providing this rom. I can try helping you for Camera fix.

Thread closed due to GPL non-compliance. PM me when you're ready to add the link for kernel source.
Thread re-opened.

Well cool.

this link dont work

[ROM] [OFFICIAL] [AOKP 9.0/Pie] [cheeseburger] AOKP Pie for OnePlus 5

{
"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"
}
[ROM][AOKP 9/PIE][cheeseburger] AOKP Pie for OnePlus 5
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Introduction
WE ARE LIVE!!
AOKP is a ROM developed by TeamKang, based on AOSP/LineageOS with magical unicorn bytes (awesome features) baked right in!
Features
Android 9 Pie
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
Custom animations
Customizable AOKP logo in status bar
So many other features, explore and find them on your own!
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
Click to expand...
Click to collapse
Known Issues
Pixel Launcher crashes constantly if you try to use it. This is an upstream issue, Lineage-16.0 has the same issue.
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Ensure you have the proper firmware installed (9.0.9)
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
Official AOKP download page:
AOKP cheeseburger files
Source:
AOKP Source
Kernel source
Click to expand...
Click to collapse
Changelog
Initial Official release.
Thanks To/Credits
TeamKang
tdm
LineageOS
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Pie Android Open Kang Project for OnePlus 5 [cheeseburger], ROM for the OnePlus 5
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, TWRP 3.2.3 or later by codeworkx (Other TWRP versions not tested!!), Firmware package from OOS 9.0.9
Based On: LineageOS, CyanogenMod, OmniRom, AOSP
Version Information
Status: Nightly
Created 2020-01-20
Last Updated 2020-01-24

Reserved

Reserved

Builds are LIVE!!
Hey guys, AOKP Pie is OFFICIAL! Download links are in the OP, and I am including them below.
http://xfer.aokp.co/?developer=AOKP&folder=cheeseburger

This ROM doesn't officially support signature spoofing/microg?

Pokemetti2 said:
This ROM doesn't officially support signature spoofing/microg?
Click to expand...
Click to collapse
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.

Does this rom has a working googlepay support?
I have been on stock oxygen OS roms for too long and i am thinking about a change.
EDIT: it is working. Had to make sure that safetynet is passed and using hidemagisk on google products

shane87 said:
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.
Click to expand...
Click to collapse
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.

d1n0x said:
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.
Click to expand...
Click to collapse
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.

shane87 said:
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.
Click to expand...
Click to collapse
That's fine by me, just wanted to know whether I had to flash NanoDroid Patcher.

Update to OP
Hey guys, I just wanted to point out that I made a small update to the OP. I included a notice of the required firmware package from OOS that this ROM needs. Currently that is 9.0.9. We ran into an issue over on 5T, and it likely had to do with incorrect firmware on the phone. I forget that not everyone pours over gerrit as much as I do, so they don't see the required firmware commits.
I will update the OP, and post an announcement, any time that we update the firmware base required.

I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.

fosunite said:
I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.
Click to expand...
Click to collapse
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.

shane87 said:
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.
Click to expand...
Click to collapse
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.

fosunite said:
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.
Click to expand...
Click to collapse
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).

Added to the OnePlus 5 Index Thread here.

shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Sorry it will take a while, because i am unfamiliar with doing logcat. I will try connect my phone to pc via adb and try to log the events. It s quite tough doing while phone should boot.

newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?

shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Ok, Finally managed to pull a logcat. Hope this helps.
rikkker said:
newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?
Click to expand...
Click to collapse
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.

fosunite said:
Ok, Finally managed to pull a logcat. Hope this helps.
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.
Click to expand...
Click to collapse
Thanks for the logcat. I'll dig into it this weekend and see if it shows anything interesting. Quick question, have you tried lineage 16? If so, does it do the same thing as far as the sim1/sim2? Since we base off of Lineage, I want to make sure that the issue is linked to AOKP, and not something that we have inherited from lineage. I only have a single sim, so I can't test myself.
On the flashing sequence, I have personally never had any issues with flashing magisk right away, but ymmv. I do a wipe/factory reset, (after backing up via tibu and/or nandroid back up in twrp), manually wipe system, cache, and dalvik cache, flash ROM, flash magisk, flash gapps. Again, YMMV.
Also, you ONLY need the no verity flash if you have unencrypted your data partition. I left my data partition encrypted.
I have not flashed the 01/31 build yet, but I will check it out, probably tomorrow.

TUTORIAL - How to install Treble ROMs (AOSP / Lineage / Pixel Experience)

Hi everyone,
I decided to make a thread about this topic because I took too much time trying to check how to do this, as isn't really documented.
If you are at Official Android 8 - 9, so you must use A-type Treble images. If you are at Official Android 10, so you must pick AB-type Treble images. Always pick ARM64 images.
Some nice projects about Treble:
- AOSP 10: https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
- LineageOS 17: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
- Resurrection Remix (Android 8, 9, 10): https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
- Many others: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
How to install it on your Tab S4, order is important here:
- Basically, get TWRP and install it: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
- Format your data folder at TWRP
- Make backup at least from Boot and Vendor Image.
- Pick and install any of the Treble images mentioned before. At TWRP go to "Install", then tap "Install Image", and pick "System Image"
- Install DM-Verity disabler https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- Install Magisk https://magisk.me/zip/#Download_Magisk_Zip
It should work, if doesn't, try another build as might be some bug. Be sure to follow all previous steps as mentioned, or you may be stuck at bootloop.
Known issues:
- Mono audio, only bottom speaker works.
- Some projects may have a rotation issue.
- S-Pen is detected as a mouse instead of pointer, but not really a bug.
- Others: https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-Tab-S4-10.5
Hope this helps to anyone! Let me know if you get some problem, from my side I had built and installed LineageOS, it works flawless! Encryption or password lock doesn't work (for me)
Example of LineageOS:
{
"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"
}

WalterCool said:
Hi everyone,
I decided to make a thread about this topic because I took too much time trying to check how to do this, as isn't really documented.
If you are at Official Android 8 - 9, so you must use A-type Treble images. If you are at Official Android 10, so you must pick AB-type Treble images. Always pick ARM64 images.
Some nice projects about Treble:
- AOSP 10: https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
- LineageOS 17: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
- Resurrection Remix (Android 8, 9, 10): https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
- Many others: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
How to install it on your Tab S4, order is important here:
- Basically, get TWRP and install it: https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278
- Format your data folder at TWRP
- Make backup at least from Boot and Vendor Image.
- Pick and install any of the Treble images mentioned before. At TWRP go to "Install", then tap "Install Image", and pick "System Image"
- Install DM-Verity disabler https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- Install Magisk https://magisk.me/zip/#Download_Magisk_Zip
It should work, if doesn't, try another build as might be some bug. Be sure to follow all previous steps as mentioned, or you may be stuck at bootloop.
Known issues:
- Mono audio, only bottom speaker works.
- Some projects may have a rotation issue.
- S-Pen is detected as a mouse instead of pointer, but not really a bug.
- Others: https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-Tab-S4-10.5
Hope this helps to anyone! Let me know if you get some problem, from my side I had built and installed LineageOS, it works flawless!
Click to expand...
Click to collapse
Can you send some pics please
Thank you

enotar said:
Can you send some pics please
Thank you
Click to expand...
Click to collapse
Just took 2 screenshot at my tablet and added them to first post using LineageOS. One at main screen, Second one at Settings using S-Pen (appears as mouse)
Be aware those roms may have incompatibilities, for example I can't encrypt or set a lock screen. Will report that later.

Anyone tried the lastest havocOS gsi?

i have 3 tab 4 tablets all upgraded to the latest update and 2 flashed with the latest HavocOS GSI. one i cant seem to get to work. its a wifi 256GB model. i have tried everything the same way as the 65GB models but nothing. anyone got some help?

droidbot1337 said:
i have 3 tab 4 tablets all upgraded to the latest update and 2 flashed with the latest HavocOS GSI. one i cant seem to get to work. its a wifi 256GB model. i have tried everything the same way as the 65GB models but nothing. anyone got some help?
Click to expand...
Click to collapse
Hmm haven't tried HavokOS, what is the error you are visualizing? And where?
Can you boot TWRP normally?

droidbot1337 said:
Anyone tried the lastest havocOS gsi?
Click to expand...
Click to collapse
Works Great but, is it possible to realize at least mono in landscape.
Known issues:
- Mono audio, only bottom speaker works.
Greetings

3rink said:
Works Great but, is it possible to realize at least mono in landscape.
Known issues:
- Mono audio, only bottom speaker works.
Greetings
Click to expand...
Click to collapse
Is it possible to Activate all Speakers?

3rink said:
Works Great but, is it possible to realize at least mono in landscape.
Known issues:
- Mono audio, only bottom speaker works.
Greetings
Click to expand...
Click to collapse
I take lots of handwritten notes. My tab S4 is mainly a notebook. Does the s pen work properly?

g0at1 said:
I take lots of handwritten notes. My tab S4 is mainly a notebook. Does the s pen work properly?
Click to expand...
Click to collapse
I don't have a spen. I think it is displayed as a mouse.

g0at1 said:
I take lots of handwritten notes. My tab S4 is mainly a notebook. Does the s pen work properly?
Click to expand...
Click to collapse
It works like a mouse, as someone said, if there is some app supporting drawing with a mouse, it will work.
s-pen works quite good, but mouse icon is annoying for me.

Those running a treble rom, does your whole screen fill when in landscape mode or does it cut off the side by 96 pixels?

Does the S-Pen support pressure sensitivity when used via one of these ROMs?

don't install gsi roms, i tried several times and i advice you not to do it. they're too much unstable, but what's more important is that it will boot only once, if you reboot by mistake it won't boot again and will go bootloop. that's very sad that no rom has been developed for this device, indeed it has got very good specs. so, in short, tab s4 is not suitable for modding. sell it and buy the previous model, it has got more support and roms.

inducer said:
Does the S-Pen support pressure sensitivity when used via one of these ROMs?
Click to expand...
Click to collapse
no gsi rom supports s-pen features like the stock one, cause no software has been developed for them, so pressure sensivity won't be recognized. only stock rom fully supports it.

Out of curiosity: was anyone successfull in installing LineageOS 20? I tried it with several different versions already, but somehow I always end up in a boot loop...thats not much fun!
So I am open for any hints/tips/tricks which help to make it work!!

Or was anyone succeeding in installing LineageOS 19? Looking for anyone who is interested in making the tablet work with GSIs

For the case that others might have the same questions. I managed to get LineageOS 17.1 and LineageOS 20 up an running. How did I do it?
Install TWRP WIFI version from official TWRP website (also works on LTE version)
Format data -> type "yes" and cofirm
Wipe Cache, Dalvik, System
Flash LineageOS 17.1 arm64_bvS from AndyYan Sourceforge repository (if you start from Android 10, which you should because you should obviously install the latest available Samsung stock firmware)
Flash DM-Verity disabler (I installed 11.02.2020 version) to disable DM-Verity and also encryption
Voilà! It should run! If you want to run LineageOS 20 proceed with
Reboot to TWRP
Flash LineageOS 20 arm64_b versions (I installed bvN)
Flash DM-Verity disabler again (not sure if it has to be flashed again, I do it)
Voilà!
This is basically the only way it worked. I tried many others such as:
Different versions of treble roms
Flash LineageOS 20 straight away not flashing 17.1 before
Trying to keep encryption enabled with DM-Verity disabler
Trying to flash a patched boot.img instead of DM-Verity disabler to keep encryption enabled
but nothing worked.
I suspect encryption is not working since the tablet uses FDE instead of FBE...but I do not have enough knowledge to address such an issue.
Important: screen lock by gesture, pin, or password does not work!!
EDIT: after some days of usage it appears to be unstable. Maybe try not to skip any major LineageOS update, so first install 17.1, then 18.1 and so on until you arrive at the desired one. I did not test this approach.
I tried to figure out any way to enable encryption, but did not succeed. The ways I tried:
Install LineageOS, then flash no-verity-opt-encrypt.zip: results in known ERROR 1 when installing no-verity-opt-encrypt.zip. Just google the error for clarification.
Flash an old TWRP (3.3) in order to not run into ERROR 1 to install no-verity-opt-encrypt.zip. Installed, but did not find fstab.qcom file, so worthless.
Install DM-Verity disabler renamed to Disable_Dm-Verity_enfec_11.02.2020.zip not to disable encryption. Can boot but tablet is not encrypted and also pin lock does not work.
Flash a patched boot.img, install LineageOS 17.1, mount vendor partition in TWRP and edit vendor/etc/fstab.qcom manually via adb pull and adb push.
Changed forceencrypt=footer to fileencryption=ice did not work
Changed forceencrypt=footer to encryptable=footer which boots up. Also, one can set a pin lock, but then when entering it again after setting it, it will not be recognized anymore. Moreover, when trying to encrypt the tablet it just crashes and reboots.
Finally, I think there does not exist a way to flash LineageOS AND enable encryption on this device. I suspect the cause is that the Tab S4 uses FDE, and not FBE. I am sure there exists some way to make it work. I am not skilled enough for that though. One last point, obviously I searched for the setting in Developer Options to convert encryption from FDE to FBE, but sadly this setting does not exist (not in stock, nor in LineageOS).
Conclusion: I reverted back to stock since I have to have encryption enabled. If this is not a requirement for you then try the above mentioned steps. Also, try not skipping a major LineageOS update, maybe this fixes the instability issues! Also: REPORT your experiences in this thread!

m0byn said:
For the case that others might have the same questions. I managed to get LineageOS 17.1 and LineageOS 20 up an running. How did I do it?
Install TWRP WIFI version from official TWRP website (also works on LTE version)
Format data -> type "yes" and cofirm
Wipe Cache, Dalvik, System
Flash LineageOS 17.1 arm64_bvS from AndyYan Sourceforge repository (if you start from Android 10, which you should because you should obviously install the latest available Samsung stock firmware)
Flash DM-Verity disabler (I installed 11.02.2020 version) to disable DM-Verity and also encryption
Voilà! It should run! If you want to run LineageOS 20 proceed with
Reboot to TWRP
Flash LineageOS 20 arm64_b versions (I installed bvN)
Flash DM-Verity disabler again (not sure if it has to be flashed again, I do it)
Voilà!
This is basically the only way it worked. I tried many others such as:
Different versions of treble roms
Flash LineageOS 20 straight away not flashing 17.1 before
Trying to keep encryption enabled with DM-Verity disabler
Trying to flash a patched boot.img instead of DM-Verity disabler to keep encryption enabled
but nothing worked.
I suspect encryption is not working since the tablet uses FDE instead of FBE...but I do not have enough knowledge to address such an issue.
Important: screen lock by gesture, pin, or password does not work!!
Click to expand...
Click to collapse
Hello bro , thank you so much for your info and your time
I have two questions
When you tested LineageOS 20 :
1- Stereo Speakers (4 Speakers) working fine ?
2- When your tablet restart did your tablet boot loop or lost it ?
Because i heard that when your device restart you may loses it
Sorry about my English
Do you recommend to install LineageOS 20 ? Because i want to give my tablet fresh looking oneUI 2.1 so old
And i tried many versions of treble roms but no thing successfully with me

Amr.Bendari said:
Hello bro , thank you so much for your info and your time
I have two questions
When you tested LineageOS 20 :
1- Stereo Speakers (4 Speakers) working fine ?
2- When your tablet restart did your tablet boot loop or lost it ?
Because i heard that when your device restart you may loses it
Sorry about my English
Do you recommend to install LineageOS 20 ? Because i want to give my tablet fresh looking oneUI 2.1 so old
And i tried many versions of treble roms but no thing successfully with me
Click to expand...
Click to collapse
1) Only bottom speakers work (as far as I can tell this is pretty much always the case)
2) Depending on what I tried it either bootlooped or was stuck at the bootanimation logo of LineageOS. I documented some cases here.
I did not loose it (not exactly sure what you mean). If you're asking whether it broke, then no...still works fine.
If you do not care about encryption nor screen lock, then I recommend to install it! Actually, LineageOS runs very smoothly.

[ROM] [Unofficial] RevengeOS 4.0 [11.0] [V30]

RevengeOS for LG V30
RevengeOS is an aftermarket firmware based on AOSP. We are dedicated to a beautiful, fast, stable and minimal customized ROM, honesty and communication with our users, and openness with our code, Hope you will enjoy.​
Known Bugs:
Guide on AOSP ROMs, troubleshooting & recommendations
XDA doesn't allow Telegram and a few other site links so I'm taking down the thread as I don't want to post an incomplete guide. You may find the full guide here: https://bit.ly/3rGKKtQ , this will be the only place I maintain bugs and guides.
forum.xda-developers.com
Changelog:
- March Security Patch
- fixed USB issues(Android Auto, lsusb not detecting an id)
Download:
RevengeOS-4.0-R-UNOFFICIAL-joan-20210308-2309.zip
drive.google.com
Thanks to
@SGCMarkus for his device trees
Telegram Group:
LG V30
You can view and join @LGEV30 right away.
t.me
XDA:DevDB Information
[ROM] [Unofficial] RevengeOS 4.0 [11.0] [V30], ROM for the LG V30
Contributors
supremmotu, SGCMarkus
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Pie Blobs from Stock
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 3.2
Stable Release Date: 2020-08-22
Created 2020-08-22
Last Updated 2020-08-22

Does volte or vowifi work?

markdcouto said:
Does volte or vowifi work?
Click to expand...
Click to collapse
Of course not. No V30 LOS-based ROM has VoLTE and never will. That has to be present in the V30 parent LOS tree, and that Dev says it's basically impossible. So, it will never be a feature in a ROM based on V30 LOS. It's only possible in V30 stock-based custom ROMs like A.I.X.
Here's the V30 Custom ROMs FAQ -- which is linked in the WTF Instructions to read before you actually bootloader unlocked your phone. See #5.

RevengeOS 4.0 [11.0]
RevengeOS-4.0-R-UNOFFICIAL-joan-20210308-2309.zip
drive.google.com
Changelog:
- March Security Patch
- fixed USB issues(Android Auto, lsusb not detecting an id)
Download:
RevengeOS-4.0-R-UNOFFICIAL-joan-20210308-2309.zip
drive.google.com
Thanks to
@SGCMarkus for his device trees
Telegram Group:
LG V30
You can view and join @LGEV30 right away.
t.me

can you use microg with this rom?

I really like the build and speed of this. WiFi worked right out the gate which is what prompted me to ditch trying to get Android 10 working. The ROM doesnt include any of the google apps so I used NikGapps to get the store and things working.
The issue is that any games or apps request that i use the google play services which is already installed and running. Not sure how to overcome this. Anyone else have this problem and perhaps a solution?
Edit: Nevermind. I used the unofficial open gapps and it worked fine. I included it in the zip queue from TWRP when i flashed the rom. I did the following:
Manually wipe (format) your System partition
Flash your ROM
Flash Open GApps package
Wipe the Dalvik & cache
Reboot

Is it good for a daily?

@supremmotu
supremmotu
Any way you could upload the ROM to another file hosting service such as mega? When I try to download from the link it says there have been too many downloads in the past 24-hours.
Can't wait to test out Android 11 on this excellent device.
Edit: I was able to get through and download it

Can this rom work on korean Version?
V300L30p bootloader unlocker and twrp running.

packyman said:
Can this rom work on korean Version?
V300L30p bootloader unlocker and twrp running.
Click to expand...
Click to collapse
yes

So far so good (US998) - Wifi works, cell service works, GPS seems to work, tethering works. I'm running Magisk v22 fine, I installed Magisk App Debug and flashed Magisk-22.zip (just rename the apk to .zip) and MicroG works fine without the need to mess around with signature spoofing.
Edit: I could only get tethering to work from wifi, not mobile data (for internet access)
My only gripe is the always on display setting (always show time and info) glitches out so you can't really use it. If you try to turn the phone on the screen goes black and stays that way. I tried using a 3rd party app Always On Edge, but it uses too much battery to use aside from charging. FM Radio also doesn't work, but that isn't a deal breaker for the newest Android for me.

aventurer said:
My only gripe is the always on display setting (always show time and info) glitches out so you can't really use it. If you try to turn the phone on the screen goes black and stays that way. I tried using a 3rd party app Always On Edge, but it uses too much battery to use aside from charging. FM Radio also doesn't work, but that isn't a deal breaker for the newest Android for me.
Click to expand...
Click to collapse
Try the Always On AMOLED app from the store. I've been using that for the last year as an alternative to the broken AOD on Android 10. I haven't noticed any significant battery drain, perhaps because, as the name suggests, it's designed for AMOLED displays.

@Osprey00
Ty so much. This app seems a lot better. I had an issue at first where the permissions wouldn't go through, I just killed the app and cache and reloaded then it worked.
It also seemed to drain the battery a ton at first, but then I rebooted my phone and stopped messing with the settings so it seems fine now.
I also was wrong about tethering working, I could only get tethering to work via Wifi, not mobile data for internet, which defeats the purpose, maybe someone has some ideas viewing this?

aventurer said:
My only gripe is the always on display setting (always show time and info) glitches out so you can't really use it. If you try to turn the phone on the screen goes black and stays that way.
Click to expand...
Click to collapse
Even though you worked around it by using the app that I recommended and may even prefer to continue using it, I just saw this AOD fix on Telegram, credit to ɐoɔɐɾ:
This should fix the black screen bug when waking the device from sleep with aod on
This is tested and confirmed to work on DotOS and LineageOS A11, it is not for A10 and may not work on other A11 roms
Flash this after first boot, may not fix ddtw
Credit to @marvinhrivera for finding this fix
Click to expand...
Click to collapse

Hi, I have just flashed this ROM and it is great so far. Everything works fine exept finger print sensor. I am able to unlock the device etc. but sensor is not accessible in some apps (internet banking, Lastpass). Have you experienced this issue, too? It is a bit annoying, especially for these apps wher biometrics is essential. Thank you.

nekicz said:
Hi, I have just flashed this ROM and it is great so far. Everything works fine exept finger print sensor. I am able to unlock the device etc. but sensor is not accessible in some apps (internet banking, Lastpass). Have you experienced this issue, too? It is a bit annoying, especially for these apps wher biometrics is essential. Thank you.
Click to expand...
Click to collapse
yeah that's a known issue, should be fixed in the next build

sinkoo1979 said:
can you use microg with this rom?
Click to expand...
Click to collapse
Yes. Use the microg settings to grant the spoof permission (tap the unchecked "system spoofs signature" box to trigger the requst) and run
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Thanks for the build, it seems solid. Some minor features (e.g. edge lighting, voicemail notifications) that didn't work on HavocOS for me work out of the box here. There are only two issues so far:
- The styles and wallpapers system app doesn't work: it won't open whether accessed from the launcher or in the settings menu. I can change wall papers and icons using the shortcuts from long pressing on the home screen, but not theme/colors (it crashes if I pick that tab)
- I cannot get file transfer over USB to work; the phone doesn't show up in Windows explorer. It's not my box or cable; the same setup works just fine for USB debugging or file transfer in TWRP. I had the same issue on HavocOS, but there swapping off file transfer and back would trigger detection, but not on this ROM
This ROM has less customization than some (you can't swap the navbar layout, for example) but this looks nice. I'll try this out as a daily driver for a week or two and see.

EsotericScreenName said:
Yes. Use the microg settings to grant the spoof permission (tap the unchecked "system spoofs signature" box to trigger the requst) and run
Code:
pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
Thanks for the build, it seems solid. Some minor features (e.g. edge lighting, voicemail notifications) that didn't work on HavocOS for me work out of the box here. There are only two issues so far:
- The styles and wallpapers system app doesn't work: it won't open whether accessed from the launcher or in the settings menu. I can change wall papers and icons using the shortcuts from long pressing on the home screen, but not theme/colors (it crashes if I pick that tab)
- I cannot get file transfer over USB to work; the phone doesn't show up in Windows explorer. It's not my box or cable; the same setup works just fine for USB debugging or file transfer in TWRP. I had the same issue on HavocOS, but there swapping off file transfer and back would trigger detection, but not on this ROM
This ROM has less customization than some (you can't swap the navbar layout, for example) but this looks nice. I'll try this out as a daily driver for a week or two and see.
Click to expand...
Click to collapse
I fixed the USB issue by doing a reinstall and not using the stock kdz first (flashing directly to a fresh format). According to the dev, the styles app requires GApps, so it won't work if you use microG

I'm also having success with this ROM. I tried a couple of other (A 10 based) ROMs, but couldn't get the wifi to work despite loading old modems etc. Revenge appears to be fully functional (with the exception of spotty fingerprint access as noted above). For me the hotspot also worked straightaway.

Nice rom, simple whit FMradio application.
Installed on a freshly unlocked and rooted H930 with pico Gapps (open_gapps-arm64-11.0-pico-20210130-TEST.zip). But I'm stupid, I saw the instructions afterwards, and I didn't install a recent pie stock rom after the root, I've install directly this rom.
The wifi and USB transfer does not work. The wifi can be fixed with the fix for Android 10 : see here : https://forum.xda-developers.com/t/q-wifi-fix-for-north-american-variants.4012635/post-83473401.
Can I flash a stock rom now? which one?