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

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?

[ROM][UNOFFICIAL][woods] darklineage-14.1-20200913 [MOD 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"
}
Hi guys, I have been working on this rom from corona vacation due to some other works, I couldn't push the stable version of this rom. Today I'm releasing my modified rom of lineage as darklineage.
Key features
Full OMS support
Signature spoofing support
Pixel animated navbar (with on/off switch)
Pulse Notification LED Works (notification & Charging) [ Can be customize led notification light for apps]
Wifi hotspot client counts
Pixel accent colors
Rounded icons
LiveDisplay with Color Calibration
Ambient display (default - pulse notification) [ can be enabled to work with the proximity sensor (Reboot Required)]
Custom Headers (Added New Header images)
Quick unlock with Fingerprint After reboot
Change navbar height
USB Tethering tile
Separate ring and notification volume
Choose Ambient display brightness
Dynamic navbar color (changes color to the same of the status bar)
Quick Magisk Manager & Substratum dashboard launcher (Fixed magisk launcher error)
Two Column Dashboard
Memory bar on recent
immersive recent
enable/disable clear all button
SafetyNet
Install Hidden Core module from Xposed to pass SafetyNet.
Installation
If You are on custom rom with a working fingerprint than no pre-requirements just clean flash this rom. If not you are on a stock rom with the latest version (NMA.26.42-169) than downgrade your Rom with Spflash tool (Flash NMA26.42-113 / NMA26.42-75) rom and come to this rom otherwise the Fingerprint not work correctly.
- Backup first... always backup first
- Wipe system, data, cache, and Dalvik cache
- Install darklineage
Optional
- Install GAPPS / MicroG ( NanoDroid zip)
- Install root package of your choice (I recommend Magisk)
Enjoy!
Donations
I added a Donation Button in Settings → about. Please consider small support for me. Thanks in Advance. :good:
Screenshots
Check It in screenshot tile.
Download
darklineage-14.1-20200913-UNOFFICIAL-woods.zip
Motorola_Moto_E4_XT1762_MT6737M_WOODS_NMA26.42_75_04082017_7.0.zip
Support
join on Telegram Group : Moto_E4_Plus_Custom_Roms
XDA:DevDB Information
Dark Lineage, ROM for the Moto E4
Contributors
Zumairmhd, Dark_Eyes_, iykeDROID™ , @vishalk17 , @SamarV-121 , @RebelLion_ , @manjuyashu & Many others
Source Code: https://github.com/mhdzumair
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: <= NMA.26.42-113
Based On: lineageOS
Version Information
Status: Stable
Current Stable Version: 14.1-20200913
Stable Release Date: 2020-09-13
Created 2020-09-13
Last Updated 2020-09-13

Is VoLTE working sucessfully on this build?
also does it has edge lighting support?..
I'll try this after exams

Abish4i said:
Is VoLTE working sucessfully on this build?
also does it has edge lighting support?..
I'll try this after exams
Click to expand...
Click to collapse
I don't sure volte working or not. I added some of the volte wanted vendor blobs need to test by jio users.
Secondthing, you earlier also mention about this light. But in my device i have white led in the front of the phone (near to front camera). I mentioned in my post as notification led. So in this build That is work perfectly for battery charging, low batter and notifications.

really a great rom, very smooth, you gave this old smartphone a second life

VOLte status
hitman72 said:
really a great rom, very smooth, you gave this old smartphone a second life
Click to expand...
Click to collapse
Is Volte working on this rom
& Is it for xt62 or for moto e4 plus?

I have installed to xt1761 (standard "moto e"), sorry I don't know about volte. previously I had installed a rom from this forum with always a kernel present here, the phone was laggy like hell... about these kernels... guys don't use zram in your kernels! zram is the absolute evil for an android smartphone

hitman72 said:
I have installed to xt1761 (standard "moto e")
Click to expand...
Click to collapse
If you have this rom running can you please check for volte provisioning from ussd pls!
SINCE Only stock supports VOLTE and No other custom rom so I was thinking If this kernel has volte Functionality ... :fingers-crossed:

Abish4i said:
If you have this rom running can you please check for volte provisioning from ussd pls!
SINCE Only stock supports VOLTE and No other custom rom so I was thinking If this kernel has volte Functionality ... :fingers-crossed:
Click to expand...
Click to collapse
I found this after reading some guide, I hope it will be useful to you

Where can I download the 113 firmware? Which part of it is exactly needed for the working fingerprint?
Edit: Found the thread with the backup of 113. We will see...
Ok, fingerprint not working anymore, even with this 113 twrp backup. Original 113 firmware not available anymore, just the latest for the SP flash tool. Not important, my mother don't like the fingerprint scanner, so it doesn't matter. Original IMEIs back with Toolhero has worked perfectly, just the serial number is wrong and this is not fixable and maybe not important like the right imei numbers.
There is one bug, safety menu in settings is not opening and seems to crash. That's because fingerprint is not working here, for sure. Or, all fine so far for mother.
And I have changed the bootanimation for her
Edit: Now she got a new battery. Hope the phone is not going down anymore around 75%

I have installed it on my Moto e4 XT1762 (2017), and my camera and gallery are not working... When I try to acces one of this futures, the phone stops and reboot.
It's there something to do with it?
Thx

Notification Lights are working perfectly which is blinking lights that were disabled in stock rom and in all custom ROM .
This is the only ROM that has enabled blinking notification lights for each added apps the pulse and speed of blinking.
Notification lights are white only & not RGB colors.
Wifi Calling also enabled and is supported by my carrier.
Screenshots below August 2020 security patch.
If all restored userapp icons dissapear like as if it was formatted, just clear Dalvik and cache.

Why doesn't the screen lock work? Clicking on "security" in the settings closes automatically. With the error "settings stopped"

Hi everyone!!
Must say an awesome ROM. The dark theme was the selling point for me tbh and the fact that its based off LineageOS sealed the deal. Thus, an amazing ROM overall in terms of performance, stability and battery life (the 3 things that someone wants out of a ROM )
But one issue that I am consistently facing is whenever I go into Settings and tap on either "Security" or "Set up Fingerprint" the Settings app either freezes or crashes entirely.
I currently have LineagOS 14.1 Dark installed on my Moto E4 XT1762 "Woods" MediaTek variant
LineageOS version is 14.1-20200913-UNOFFICIAL-woods
kernel version 3.18
Build Number being lineage_woods-userdebug 7.1.2 NJH47F 0b5190fbeb test-keys
I also Magisk version 23.0 installed for root.
Troubleshooting steps that I have taken till yet:
Restarted the device numerous times
Wiped the Cache/Dalvik Cache from Recovery
Signed up using Google Email
Deleted Google's application cache and restarted
Signed up using a new user (that time it just froze on the boot animation until I manually restarted it)
None of the steps work and still whenever I tap on Security or Fingerprint, its like my devices just tells me to eff off and not play around with the security settings. If this is something that the developer intended or locked, I would love to know any way to unlock it
I have also googled the issue quite significantly. However, for my specific device, I was unable to find any good information thus I decided to post on my own. I have tried a couple of different fixes that worked on other devices with similar issues but the same ROM. However, none of them have worked so far.
Otherwise, I must say I have been using this ROM as my daily driver for like 2 weeks and have yet to come across any other issues. All my required apps work seamlessly and its like my 3 yrs old mobile got a new life. Just this one issue is bugging me, and would love if I get some guidance regarding how to resolve this!
Thank you once again !! Y'all are awesome!!

poptart_boi said:
Hi everyone!!
Must say an awesome ROM. The dark theme was the selling point for me tbh and the fact that its based off LineageOS sealed the deal. Thus, an amazing ROM overall in terms of performance, stability and battery life (the 3 things that someone wants out of a ROM )
But one issue that I am consistently facing is whenever I go into Settings and tap on either "Security" or "Set up Fingerprint" the Settings app either freezes or crashes entirely.
I currently have LineagOS 14.1 Dark installed on my Moto E4 XT1762 "Woods" MediaTek variant
LineageOS version is 14.1-20200913-UNOFFICIAL-woods
kernel version 3.18
Build Number being lineage_woods-userdebug 7.1.2 NJH47F 0b5190fbeb test-keys
I also Magisk version 23.0 installed for root.
Troubleshooting steps that I have taken till yet:
Restarted the device numerous times
Wiped the Cache/Dalvik Cache from Recovery
Signed up using Google Email
Deleted Google's application cache and restarted
Signed up using a new user (that time it just froze on the boot animation until I manually restarted it)
None of the steps work and still whenever I tap on Security or Fingerprint, its like my devices just tells me to eff off and not play around with the security settings. If this is something that the developer intended or locked, I would love to know any way to unlock it
I have also googled the issue quite significantly. However, for my specific device, I was unable to find any good information thus I decided to post on my own. I have tried a couple of different fixes that worked on other devices with similar issues but the same ROM. However, none of them have worked so far.
Otherwise, I must say I have been using this ROM as my daily driver for like 2 weeks and have yet to come across any other issues. All my required apps work seamlessly and its like my 3 yrs old mobile got a new life. Just this one issue is bugging me, and would love if I get some guidance regarding how to resolve this!
Thank you once again !! Y'all are awesome!!
Click to expand...
Click to collapse
Thank you for your kind review. in my installation guide i was strictly said before use this rom you need to flash NMA26.42-75 firmware using spflash tool to work the fingerprint. i'll provide the firmware rom link. you need to flash the rom and then come back here. if you need any guides or help please join in our telegram group.
Thanks.

Zumairmhd said:
Thank you for your kind review. in my installation guide i was strictly said before use this rom you need to flash NMA26.42-75 firmware using spflash tool to work the fingerprint. i'll provide the firmware rom link. you need to flash the rom and then come back here. if you need any guides or help please join in our telegram group.
Thanks.
Click to expand...
Click to collapse
Most welcomee!!
Plus, regarding the NMA ROM I must have missed that part. I am still a n00b when it comes to rooting/installing custom ROMs, thus pls excuse my silly mistake.
Please do share the link of the NMA ROM, plus if there is any guide to do the installation of the NMA ROM and then this ROM, please do share that as well. Although you have already mentioned that you flash the NMA ROM and then flash this one and the fingerprint should work fine, so not a strict requirement, but would be nice to have if possible
Plus, pls pls pls do share the telegram group link. Tbh after flashing the ROM I have gotten interested in learning about custom ROM development, plus, if I encounter any bugs I can get quicker responses from the OG devs like you, so would greatly appreciate the share !! ^_^
Thanks once again!! Awesome ROM!!

poptart_boi said:
Most welcomee!!
Plus, regarding the NMA ROM I must have missed that part. I am still a n00b when it comes to rooting/installing custom ROMs, thus pls excuse my silly mistake.
Please do share the link of the NMA ROM, plus if there is any guide to do the installation of the NMA ROM and then this ROM, please do share that as well. Although you have already mentioned that you flash the NMA ROM and then flash this one and the fingerprint should work fine, so not a strict requirement, but would be nice to have if possible
Plus, pls pls pls do share the telegram group link. Tbh after flashing the ROM I have gotten interested in learning about custom ROM development, plus, if I encounter any bugs I can get quicker responses from the OG devs like you, so would greatly appreciate the share !! ^_^
Thanks once again!! Awesome ROM!!
Click to expand...
Click to collapse
Here is the telegram link: Moto_E4_Plus_Custom_Roms

essa rom funciona a impressa digital no moto e4 XT1763

Very glad to see that there is development for the E 4 woods. Would like to install this ROM, but only have a hard-bricked E4 XT1762 Mediatek MT6737M. Made already a post on a (very old) thread
https://forum.xda-developers.com/t/e4-sprint-xt1766-unbrick-easy-with-sdcard-method-tested.3833408/
Is there anyone who could kindly try to build an unbrick.img for a XT1762? Don't have access to a working XT1762, so method of post 1 and 5 in the mentioned thread doesn't work for me. Or ist it possible to build an unbrick.img from stock rom? Thanks in advance

pancobe said:
Very glad to see that there is development for the E 4 woods. Would like to install this ROM, but only have a hard-bricked E4 XT1762 Mediatek MT6737M. Made already a post on a (very old) thread
https://forum.xda-developers.com/t/e4-sprint-xt1766-unbrick-easy-with-sdcard-method-tested.3833408/
Is there anyone who could kindly try to build an unbrick.img for a XT1762? Don't have access to a working XT1762, so method of post 1 and 5 in the mentioned thread doesn't work for me. Or ist it possible to build an unbrick.img from stock rom? Thanks in advance
Click to expand...
Click to collapse
you can try to unbrick it with sp flash tool. there plenty of videos around the internet about how to use sp flash tool

Hi,
I get to the first screen and then the phone reboots every time! Do we have a functional Lineage OS that I can use on the phone (android 7.1.2).
Thank you!
KR
Rok

Any idea how to add second SIM on/off switch for adb or rooted terminal?
I tied to use this method but couldn't find correct command.
Turning off second SIM via adb shell/Tasker - using activities/intents
I have a Xiaomi Mi6, which supports two SIMs. I need to figure out how I can switch the second SIM (SIM2) off outside business hours using Tasker. I've got as far as figuring out how to open the
stackoverflow.com

How To Guide A Complete Guide to Unlocking and Flashing for the A52s 5G.

Disclaimer​
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!​Now that we got that out of the way, we can continue.
Unlocking the Bootloader​UNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!​
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom Recovery​Credit to @BlackMesa123 for this guide.
Rooting your Phone​
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)​
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources​
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.

This is very helpful thanks

Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.

BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?

kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t

Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.

Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.

I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.

kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.

What about volte and hotspot on GSI pixel experience 13?

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?

7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.

Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.

Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.

7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.

Thx, all worked.

Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...

I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.

Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/