[Q&A] How can I disable PIE? - Samsung Galaxy S II Plus

My device has ResurrectionRemix 5.7.0 with Android M 6.0.1. I was going to trim my cache, data and system with LagFix (premium) app, but it sends me this error "error: only position independent executables (PIE) are supported.".
Surfing in the net I understand that I have to disable PIE (position indipendent executables).
Can someone tell me how can I turn off PIE controls?

It's not PIE controls but a new security check in Android System and you can't disable it, only rom developers can.

Related

[ROM][6.0.1_r79] nAOSProm for Google Nexus 7 (2012)

nAOSProm-6.0 for Google Nexus 7 2012
The purpose of this rom is to provide a rom not so far of the AOSP with some cool features (nAOSP means "near AOSP").
It is fork of nAOSProm for Xperia S.
nAOSProm is stable, works very smoothly, works well with layers, xposed...
It has integrated Superuser app so superSU is not necessary, but it works well also if you flash it.
There are no FCs with Setup Wizard and Google Play services, when clean flashed together with gapps.
Change log
nAOSProm-6.0 b11
AOSP android-6.0.1_r79 - February security patch
Previous releases
nAOSProm-6.0 b10
AOSP android-6.0.1_r74 - November security patch
f2fs: added f2fs check to fstab
nAOSProm-6.0 b09
AOSP android-6.0.1_r70 - October security patch
Fixed sound on system start
nAOSProm-6.0 b08
AOSP android-6.0.1_r66 - September security patch
nAOSProm-6.0 b07
AOSP android-6.0.1_r61 - August security patch
Superuser replaced with new Superuser with AppOps
su: Support for multiuser and the new Superuser
Ui: Battery styles (see Settings/nAOSProm/More)
Ui: Optimizing application displays the application name
Ui: Correct handling of NavBar menu button in old apps
Settings: Display safe entries into nAOSP section (depends on current user, root access ...)
Boot: check f2fs not run anymore - faster boot in the case of f2fs data and cache
Geolocation: fixed location provider
PerformanceControl: changed to drawer view ui
nAOSProm-6.0 b06
AOSP android-6.0.1_r52 - July security patch
Themes: Full support of Layers 4.0
SystemUI: Added battery percentage text to status bar
You can configure it from Settings/nAOSProm/More.../Battery Percentage
nAOSProm-6.0 b05
AOSP android-6.0.1_r46 - June security patch
Added Immersive Mode Quick Settings tile (hide NavBar and/or Status bar)
You can add/remove tile from Settings/System UI Tuner/Quick Settings
nAOSProm-6.0 b04
AOSP android-6.0.1_r43 - May security patches
Added nAOSP "More" settings:
Memory settings
Signature spoofing
Others: Quick Settings Expand and Status Bar DT2S switches
Animations speed up
nAOSProm-6.0 b03
AOSP android-6.0.1_r24
Switched to daniel_hk kernel
Performance improvements
Added PerformanceControl app
Added Caffeine Quick Settings tile
nAOSProm-6.0 b02
AOSP android-6.0.1_r22
Added ViPER4Android
Added adb over wifi quick tile
nAOSProm-6.0 b01
AOSP android-6.0.1_r16
OTA: support with ROM Updater (see Settings/About phone/Updates)
OTA: Layers: OTA will preserve theme files when flashing a new ROM version (updating)
F2FS support
Superuser integration
Browser, Music and Gallery2: AOSP version replaced by CyanogenMod version
Power Key: Include Reboot menu (Normal, Soft, Recovery and Bootloader)
Quick Setting: Can be pull down directly with one finger on the 1/3 right of the Status bar
Recent Applications : Close all applications button on the right bottom
Double Tap to Sleep on the status bar
Settings: nAOSProm section that permit you to configure the ROM, to start Layers Manager, Superuser and SuperSU if available.
No FCs for Setup Wizard and Google Play Services on initial boot
Requirements
Rooted Nexus 7, TWRP 2.8.7.0 - 3.0+
Flashing
nAOSProm can be dirty flashed over other AOSP-6.0 based roms (not from CM based). I recommend clean flash if you come from other roms.
Flashing Procedure
Clean flash
Backup everything
Reboot into recovery
Convert data / cache to F2FS
Backup /sdcard - adb pull /sdcard/ sdcard/
Change data to F2FS - in twrp go to Wipe, advanced wipe, select Data,
Repair or Change File System, Change File System, F2FS
Change cache to F2FS - same as for data
restore sdcard data - adb push sdcard /sdcard/
Wipe everything except sdcard
Unmount /system
Flash nAOSProm
Flash gapps - I recommend open gapps
Reboot
Dirty flash
Reboot into recovery
Flash nAOSProm
Flash gapps - I recommend open gapps - nano
Wipe cash & dalvik
Reboot
Upgrading from previous nAOSP versions
This ROM has OTA update feature - it periodically (once a week by default) checks for new versions and offers to download and install them. You can check for new version manually in Settings/About phone/Updates.
Before doing update you should set post update settings - other zip files (gapps, xposed) that should be flashed after rom update. Once you set post update you can use it for future updates, or you can set updated zips before every update. You can also add custom open recovery script commands. If you want to automatically reboot after upgrade you can enter reboot command into Post Update / Aditional script.
When flashing nAOSProm layers are preserved, so you don't need to worry about that upgrading.
You can also manually upgrade nAOSProm in twrp by dirty flashing.
Download
b11 - 2017/03/12
Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b11.zip
md5: d4eacd73204b8349edf1a4f546056679
Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b11.zip
md5: f435fe788c51a0c2e1126ba63ec6bffa
Previous releases
b10 - 2016/11/14
Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b10.zip
md5: 36603efdc8c975dc11d904b86420ad1d
Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b10.zip
md5: 82f9cfcc9fc7a52fc60ebbaacabff71d
b09 - 2016/10/06
Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b09.zip
md5: d51e2acfea135e1570d71bb993809e8f
Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b09.zip
md5: 0233af777850b6f22dcf34b07d088404
b08 - 2016/09/08
Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b08.zip
md5: abd3e21b2bfaf9a841707c41578d7c73
sha1: a7d2d4dfb0fcc64ff11f3067ae981694203495e8
Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b08.zip
md5: 632811a641a3aafb610a9cc3219bd468
sha1: 827608fc8f2ad3331653cabcb0e235772c2a4f19
Thanks
@mickybart - for creating original nAOSP rom
@dmitrygr - for porting android 6 to Nexus 7 2012
@daniel_hk - for stable kernel with f2fs support and Performance Control app
AOSP/Google
Cyanogenmod Team
ViPER4Android Team
Android Community
Source
https://github.com/millosr/naosp_manifest/tree/nAOSP-6.0-grouper
First! This ROM is stable or in beta?
It is unofficial?
pickmod said:
First! This ROM is stable or in beta?
It is unofficial?
Click to expand...
Click to collapse
Rom is pretty stable. There are occasional cpu hogs in chrome, but that is happening also in other aosp 6 based roms on nexus 7 and even in stock lolipop.
I didn't experience any random reboot, there are no Google Play Services and Setup Wizard FCs.
Xposed is working fine on it. Layers are working.
This is first release for Nexus 7.
It's unofficial.
nAOSProm b02 released
I have released nAOSProm b02.
This is list of changes:
AOSP android-6.0.1_r22
Added ViPER4Android
Added adb over wifi quick tile
Download
Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b02.zip
Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b02.zip
Important
If you are upgrading from Settings/About/Updates, please make sure ROMUpdater application has Storage permissions. You can set storage permissions by:
Go to Settings/Apps
Press menu button [three dots] and Show System
Open ROMUpdater app settings
Enable Storage permissions
Press FORCE STOP button
Go to Settings/About/Update and update the rom
Hi,
on my device encrypting the tablet doesn't work. The dialog opens and after confirming the tablet reboots but doesn't start to encrpyt.
I tried with F2FS and also EXT4 as file system.
rainh said:
Hi,
on my device encrypting the tablet doesn't work. The dialog opens and after confirming the tablet reboots but doesn't start to encrpyt.
I tried with F2FS and also EXT4 as file system.
Click to expand...
Click to collapse
Can you give me adb logs?
I didn't test encryption, since this is an old tablet and not very fast, so I believe that encryption will add additional overhead.
EDIT: Misread the above 2 posts, my reply was not relevant to that issue.
@millosr Thanks for the new b03 release, has some cool added features.
Mike T
nAOSProm b03 released
Changes:
AOSP android-6.0.1_r24
Switched to daniel_hk kernel
Performance improvements
Added PerformanceControl app
Added Caffeine Quick Settings tile
New kernel with PerformanceControl has overclocking support and Double Tap To Wake feature (which can consume battery).
Performance improvements are done by tuning memory parameters in device/asus/grouper.
Additional tuning can be done through PerformanceControl.
Download:
Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b03.zip
Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b03.zip
Very Stable ROM!
I use the nAOSProm-6.0-tilapia-b03 and my single problem is that mobile internet doesn't work when it's in standby mode for a longer time. i can see the triangle on the top but it's empty so there is no internet. After restarting the Nexus 7 mobile internet works fine again. Is it possible to solve this bug?
EDIT: I forgot to say that when it's in standby mode for a longer time i always active flight mode before to save battery. after wake up the nexus 7 and deactivate flight mode there's the internet problem described above.
How to disable Double Tap to Sleep on the status bar?
nilsxvx said:
Very Stable ROM!
I use the nAOSProm-6.0-tilapia-b03 and my single problem is that mobile internet doesn't work when it's in standby mode for a longer time. i can see the triangle on the top but it's empty so there is no internet. After restarting the Nexus 7 mobile internet works fine again. Is it possible to solve this bug?
How to disable Double Tap to Sleep on the status bar?
Click to expand...
Click to collapse
I will check mobile internet problem.
There is no option to disable Double Tap to Sleep for now. I will maybe add it in the next build.
where can i get open gapps, please?
tilapia
I become everytime "Insufficient storage space available in System partition." when trying to install open gapps with TWRP
So, i found that i forgot to mount "system", thats why i got "insufficient space" message
I downloaded OpenGapps arm 6.0 mini, but now i get something like "this gapps version is incompatible with your Android Rom"
RL_ka said:
So, i found that i forgot to mount "system", thats why i got "insufficient space" message
I downloaded OpenGapps arm 6.0 mini, but now i get something like "this gapps version is incompatible with your Android Rom"
Click to expand...
Click to collapse
I'm using OpenGapps micro 6.0 arm, never had problems with it. Mini is too big for N7, since it has small system partition.
System doesn't need to be mounted, open gapps installation does the mounting.
nilsxvx said:
Very Stable ROM!
I use the nAOSProm-6.0-tilapia-b03 and my single problem is that mobile internet doesn't work when it's in standby mode for a longer time. i can see the triangle on the top but it's empty so there is no internet. After restarting the Nexus 7 mobile internet works fine again. Is it possible to solve this bug?
EDIT: I forgot to say that when it's in standby mode for a longer time i always active flight mode before to save battery. after wake up the nexus 7 and deactivate flight mode there's the internet problem described above.
Click to expand...
Click to collapse
I have tried this, and I'm getting gsm connection after turning off airplane mode. It just needs 30 seconds to reconnect.
Try to turn off mobile data, instead of going to airplane mode.
millosr said:
I'm using OpenGapps micro 6.0 arm, never had problems with it. Mini is too big for N7, since it has small system partition.
System doesn't need to be mounted, open gapps installation does the mounting.
Click to expand...
Click to collapse
It doesnt work "Insufficient storage space"
RL_ka said:
It doesnt work "Insufficient storage space"
Click to expand...
Click to collapse
Are you doing clean flash, with micro open gapps?
Are you flashing anything else except rom and gapps?
Are you using TWRP 3.0.2 ?
You can also try nano or pico open gapps.
Nexus 7 system partition has only 640 MB. After flashing rom and gapps (micro) I have only 22 MB free. So supersu, exposed and layers can use additional space so that you cant install micro open gapps.
millosr said:
Are you doing clean flash, with micro open gapps?
Are you flashing anything else except rom and gapps?
Are you using TWRP 3.0.2 ?
You can also try nano or pico open gapps.
Nexus 7 system partition has only 640 MB. After flashing rom and gapps (micro) I have only 22 MB free. So supersu, exposed and layers can use additional space so that you cant install micro open gapps.
Click to expand...
Click to collapse
I wiped everything, formatted cache and data to f2fs, system still ext4. Flashed rom and directly after that trying to flash gapps.
Already tried to flash rom and boot it, before flashing gapps. No Luck
Yes, twrp 3.0.2
RL_ka said:
I wiped everything, formatted cache and data to f2fs, system still ext4. Flashed rom and directly after that trying to flash gapps.
Already tried to flash rom and boot it, before flashing gapps. No Luck
Yes, twrp 3.0.2
Click to expand...
Click to collapse
Have you tried nano or pico open gapps?
Can you send me twrp log - advanced, copy log, then transfer it to pc and send?
Can you also check partitions with "df" from adb shell, or from twrp terminal, but you need to mount system first?
I just installed this on my forgotten tilapia, so thanks!
Quick question: I see that on the Cyanogen's discussion they propose some performance tricks (journaling off, auto trim everyday and something called ParrotMod): should we take those suggestion or ignore them?
Thanks, will report back in a few days!
dvdbos said:
I just installed this on my forgotten tilapia, so thanks!
Quick question: I see that on the Cyanogen's discussion they propose some performance tricks (journaling off, auto trim everyday and something called ParrotMod): should we take those suggestion or ignore them?
Thanks, will report back in a few days!
Click to expand...
Click to collapse
I'm not sure those things work with F2FS. You can try them if you want.
Can you paste links with the discussion?

[ROM] [UB] Updated February 9, Jaguar Amami LP5.1.1 Hardened Official HyperTool 5.4

This is the Official Jaguar rom for Amami, which is based on AOSP with some flavors from Slim and Dirtyunicorn. The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5 built with UBERTC 6.0; hardened rom built with HYPERTOOL 5.4
2. All ciphers enabled in kernel instead of just a few
3. Hardened/Fortified Bionic and Libs
4. Fstack protection strong to resist buffer overflows
5. Many System apps and processes are made read-only, to reduce elevation of privilege
6. Selinux replaced with Tomoyo Security, Yam security
7. Disc encryption, keymaster to 256 bit AES instead of 128
8. Latest TWRP with working brightness and ability to decrypt Data
9. Random number generation mixed hardware/software, as recommended by Linus Torwalds
10. Options to randomize host on every boot
11. Option to have a separate password for lock screen and boot
12. Qualcomm's Time Services disabled due to leaking on early boot (set time to automatic to get it from your carrier). Forget it. The rom now includes Sony TimeKeep that sets the time locally
13. WIFI Background Scanning disabled to prevent leaking
14. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
15. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
16. GRsecurity features, such as Sidechannel implemented
17. Some Pax Security Features
18. Option to deny USB connection: denied always; denied when locked; and allowed always
19. Hardened webview with Google and other "interesting" IPs removed
20. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
21. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
22. Camera hardware button works to focus, take pictures and start video recording
23. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
24. Option to disable continuing writing of logcat
25. Option to disable device cameras: back; front, both or none
26. Always latest Google Security Patches
27. Always latest Code Aurora Security Patches
28. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
29. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10 that has Down Syndrome, but Linux/Google/Code Aurora one)
30. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
31. Many more security features ported from Linux and Copperhead OS
32. Dns Crypt: a feature allowing to choose among many Dns providers (all encrypted)
33. Seccomp: secure computing enabled in kernel
Other features include: Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Supersu included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings; FM Radio and Recording plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. TimeKeep is ported from MM/N. Now time is set locally without the Internet or GSM signal. You need to set it once only and then TimeKeep will keep it current on each reboot, even if Airplane mode.
5. GAPPS: in order to escape f/c, you need to flash GAPPS right after the rom without reboot. If you reboot, you will have problems.
6. If you came from Kitkat directly to a custom LP (without having stock LP at least once), you might experience problems with hardware: gps/wifi irregularites. This applies to any custom rom above Kitkat. To remedy this, flash unmodified Sony stock LP 5.1.1, boot the phone and let it settle. Then you can reboot into fastboot and flash TWRP recovery. Then you can flash Jaguar
Download: All updates and change logs are in Post #3 now
Instructions:
1. You must have flashed and booted stock LP 5.1.1 once to upgrade your hardware (see explanation above)
2 Have TWRP (fastboot my unofficial version), unlocked bootloader and root
3. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
4. Flash the rom
5. If you use xposed, flash the latest installer (As of October 2016 no longer works due to multiple implementations from Nougat)
6. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
7. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault. :laugh:
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Sources: https://github.com/AOSP-Argon/android_kernel_sony_msm8974
XDA:DevDB Information
Jaguar Amami LP 5.1.1 r37 Official, ROM for the Sony Xperia Z1 Compact
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP Slim DirtyUnicorn
Version Information
Status: Stable
Created 2016-06-11
Last Updated 2017-02-09
I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...
Some screenshots: http://forum.xda-developers.com/showpost.php?p=62560391&postcount=2
February 9. New release:
1. February Security patches
2. DNS_Crypt (in settings/security)
3. Seccomp (secure computing implemented in kernel)
4. Open Source Superuser integrated
5. Silent SMS notification enabled
6. 1440p profile in camcorder added
7. Sony TimeKeep: now time is set locally without the Internet or GSM signal (you need to set it right the first time only)
8. Updated TWRP that now works with TimeKeep
If you enable Dnscrypt and you use Afwall, allow internet for apps running as root...
If you prefer closed source Supersu, just flash the zip...
Download Rom: https://forum.xda-developers.com/devdb/project/dl/?id=23073
Download TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=23070
______________________________________________________
January 12: Updated release that includes a fully working NFC-HCE for Android Pay. It may be possible to bypass Safety Net by deleting Superuser or Supersu with su binary, as Lollipop doesn't have dm verity. Although, if the check includes bootloader status, you may be out of luck.
You may flash dirty on top of the previous Jaguar release.
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22567
_________________________________________________________________
January 6: New release with January security patches from Google and Code Aurora. Also, qcom time service is back.
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22449
You can flash on top of the previous release. Otherwise, read the OP (fresh install).
____________________________________________________________________________________
December 10. Rom updated to include:
1. December security patches
2. Signature spoofing (like in Omniroms)
3. USSD fixed (maybe)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22005
__________________________________________________________________________________
November 11. Rom updated to include November Security Patches. I have also removed Supersu, as there is a built-in root manager and quite a few people no longer trust the Chinese owned Supersu.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21448
________________________________________________________________________________
October 5. New release:
1. Kernel overclocked to 2803: experimental, I have used it for 10 days on Z1 without problems
2. October security patches from Google and Code Aurora
3. Over 80 commits from Google Master Gerrit which included changes to bionic, art, frameworks and system
4. Updated Afwall
5. Maybe more
This rom is now about 40% Nougat. One of the side effects: Xposed framework no longer works, but getting rid of it and instead using Privacy Guard is almost as good. Don't forget, Xposed is an exploit, which provides hooks for good and bad things.
Rom Download: http://forum.xda-developers.com/devdb/project/dl/?id=20791
Afwall/Kernel Adiutor Download: http://forum.xda-developers.com/devdb/project/dl/?id=20790
You can flash dirty if on a previous release
_________________________________________________________________________________
September 8. Rom updated to include:
1. September Google security patches
2. Latest Code Aurora patches https://www.codeaurora.org/projects/security-advisories
3. MPdecision is permanently disabled due to interfering with other hotplug and CPU frequencies. Default is MSMdecision, but you can pick several others in Kernel Adiutor
4. CPU overclock and underclock removed: no benefit whatsoever
5. More hardening ported from 3.18 kernel: https://android-review.googlesource.com/#/q/hardened,25 You won't find those on any rom custom or stock. This is from 3.18 kernel and it has nothing to do with Sony
6. About 70-80 commits from Android Master Branch. Folks. This is no longer a lollipop rom
7. PXN security feature implemented, which takes advantage of special instructions on ARMv7 to prevent unprivileged execution. See here: https://android-review.googlesource.com/#/c/265892/
8. Further integration of VOLTE
9. Kernel Adiutor: author has decided to go with Mobile Ads/Adview/Adbanner. So these were removed...
10. Camera: improvements to camera wrapper (missing entries), as well as some modifications in /frameworks/av/camera, so, you have a sharper picture. See photo attached, although, XDA reduces pictures... . This was taken with Open Camera.
Maybe more...
WARNING: you need to do one thing after flashing the rom: flash the latest stock baseband. BASEBAND ONLY. If you don't, you will only have LTE: no H+/H/2G. This is a one-time procedure and is due to Volte implementation. You have been warned. First flash the rom, then reboot, then flash the latest baseband. I don't want to hear cries: where is my 3G!
Download Rom: http://forum.xda-developers.com/devdb/project/dl/?id=20290
Download Afwall/Kernel Adiutor:http://forum.xda-developers.com/devdb/project/dl/?id=20288
You may flash dirty if on a previous release. Otherwise, clean flash...
So far so good but I noticed some bugs which come from CM trees - The scrolling is laggy (this fixed it http://review.cyanogenmod.org/#/c/109956/ ) screen is flickering with low brightness ( I made a fix but looks like I'm not able to complete it https://review.cyanogenmod.org/#/c/106545/ ) and WiFi Mac is wrong (starts with 00:00 and I think this commit fixed it https://review.cyanogenmod.org/#/c/117270/ ) Otherwise great ROM and thanks for the work!
optimumpro said:
This is Official Jaguar Rom LP 5.1.1 r37 which enjoyed over 4000 downloads at Xperia Z1 thread. Jaguar is the only LP rom that is being actively developed and maintained, which means latest sources including June security patches...
Important Disclaimer: I don't have Z1 compact, so, although unlikely, you may have non boot issues. So, back up your prior rom and don't complain, as for the purposes of Z1 compact, this is an experimental build...
As you all know, MM is still in bad alpha state, not to mention horrible camera and it will NOT get any better for many reasons such as: idiotic switching to AOSP (instead of CM) trees; and CM abandoning AOSP in favor of its own closed source OS. Pure AOSP has NEVER had a stable Z1 rom for any version of Android be it MM, LP, Kitkat or even Jeallybean. So, forget about MM. It is bad and isn't getting better.
Click to expand...
Click to collapse
Thanks for the rom, I look forward to trying it out. I must say, though, that we have seen at least a couple of AOSP/AOSP-based ROMs for our device that are developing nicely - fully functional and with good cameras. See DU by @SpiritCroc, and AOSP by @freexperia.
However, as far as CM goes, you're quite right. Several nice ROMs, but little camera progress.
Syssx said:
So far so good but I noticed some bugs which come from CM trees - The scrolling is laggy (this fixed it http://review.cyanogenmod.org/#/c/109956/ ) screen is flickering with low brightness ( I made a fix but looks like I'm not able to complete it https://review.cyanogenmod.org/#/c/106545/ ) and WiFi Mac is wrong (starts with 00:00 and I think this commit fixed it https://review.cyanogenmod.org/#/c/117270/ ) Otherwise great ROM and thanks for the work!
Click to expand...
Click to collapse
In Kernel Adiutor use Ondemandplus, multicore power saving disabled. Set timer_rate at 33000. Don't use mpdecision, instead use Msmpdecision hotplug with idle frequency set at 1497. Use intelithermal. You will also have cpu and gpu overclocked to 2457 and 600 respectively. Also voltage changing is in kernel. Screen flickering does not exist on Z1. I will look into it...
Edit: those old commits were in from the beginning...
12. Mandatory use of Afwall (no internet unless Afwall is activated)
Click to expand...
Click to collapse
Afwall+ has never worked right for me. It actually blocked some apps explicitly whitelisted, and some blacklisted apps would still go through it. I know OP is not to blame about this, but making it mandatory is a big "no" for me.
optimumpro said:
In Kernel Adiutor use Ondemandplus, multicore power saving disabled. Set timer_rate at 33000. Don't use mpdecision, instead use Msmpdecision hotplug with idle frequency set at 1497. Use intelithermal. You will also have cpu and gpu overclocked to 2457 and 600 respectively. Also voltage changing is in kernel. Screen flickering does not exist on Z1. I will look into it...
Edit: those old commits were in from the beginning...
Click to expand...
Click to collapse
Flickering occurs while Adaptive Brightness is on and when Brightness slider is on minimum value. Screen (and or backlight) just starts to flicker.
What gapps should I use fro this rom?
I tried opengapps but they make AOSP keyboard crash. (clean install)
Syssx said:
Flickering occurs while Adaptive Brightness is on and when Brightness slider is on minimum value. Screen (and or backlight) just starts to flicker.
Click to expand...
Click to collapse
Disable ambient display: it is broken on lp and wastes battery.
leonmorlando said:
Afwall+ has never worked right for me. It actually blocked some apps explicitly whitelisted, and some blacklisted apps would still go through it. I know OP is not to blame about this, but making it mandatory is a big "no" for me.
Click to expand...
Click to collapse
You need to use built in binaries for iptables and busybox (prefrences/binaries), as Google iptables are modified to allow certain traffic. Afwall is good in preventing all kinds of leaks, but it can't do anything until it runs and it does not run on boot. So, this rom has a script on early init that cuts the internet until the firewall starts. Without it all your internet traffic is routed through an ip like this one: 26.147.196.122.
Cant install Afwall+KernelAuditori.zip md5 failed
is it the reason why I cant use the internet via WLAN or Mobile Data? Because someone has written that a script block all internet traffic till AFWall is started?
com.android.phone FC when I try to set up some mobile settings by long holding the mobile strengh indikator
Edit: com.android.phone FC only in german language and not in english language
Thanks
AlexandreVegetaroux said:
Cant install Afwall+KernelAuditori.zip md5 failed
is it the reason why I cant use the internet via WLAN or Mobile Data? Because someone has written that a script block all internet traffic till AFWall is started?
com.android.phone FC when I try to set up some mobile settings by long holding the mobile strengh indikator
Edit: com.android.phone FC only in german language and not in english language
Thanks
Click to expand...
Click to collapse
You don't flash Kernel Adiutor and Afwall: unzip the file and install as normal apps, as it says in the OP.
With regard to phone FC, change the language to English, set whatever you need and then switch back to German...
Edit: this rom is not based on CM, which only recently implemented localizations/translations. My rom and development is a one person thing, so, it is not possible for me to do all localizations. However, as described above, you can set whatever you want in English and then switch back to your language: the settings will hold
optimumpro said:
Disable ambient display: it is broken on lp and wastes battery.
Click to expand...
Click to collapse
Man I dont think you got me right. The brightness values of CM sources are too low for Z1C (they are using stock ones and not sony ones) - this file is missing from sources with propper settings https://github.com/sonyxperiadev/de...rameworks/base/core/res/res/values/config.xml
//edit// so ive found that the values are here: https://github.com/CyanogenMod/andr...rameworks/base/core/res/res/values/config.xml and as you can see CM uses lowest value of "20" and SONY AOSP sources use "32" ( <item>32</item> <!-- 64 --> from their source)
no internet
no internet conection with this rom.what is wrong?
Syssx said:
Man I dont think you got me right. The brightness values of CM sources are too low for Z1C (they are using stock ones and not sony ones) - this file is missing from sources with propper settings https://github.com/sonyxperiadev/de...rameworks/base/core/res/res/values/config.xml
//edit// so ive found that the values are here: https://github.com/CyanogenMod/andr...rameworks/base/core/res/res/values/config.xml and as you can see CM uses lowest value of "20" and SONY AOSP sources use "32" ( <item>32</item> <!-- 64 --> from their source)
Click to expand...
Click to collapse
This rom has exactly the same value as in Sony that you linked: 10, 32, 64... . . Is there a reason CM abandoned that commit that had 13 instead of 10? But anyway, whatever the values are, don't set brightness to the extreme low and you won't have any flickering...
bubaliana said:
no internet conection with this rom.what is wrong?
Click to expand...
Click to collapse
You have to read the OP: Install afwall and kernel adiutor as normal apps (they are linked in the OP), set/activate Afwall and you will have the internet...
optimumpro said:
You need to use built in binaries for iptables and busybox (prefrences/binaries), as Google iptables are modified to allow certain traffic. Afwall is good in preventing all kinds of leaks, but it can't do anything until it runs and it does not run on boot. So, this rom has a script on early init that cuts the internet until the firewall starts. Without it all your internet traffic is routed through an ip like this one: 26.147.196.122.
Click to expand...
Click to collapse
you mean we need to follow these instructions http://forum.xda-developers.com/showpost.php?p=62560397&postcount=3?
BTW great rom,thanks for bringing it to Z1C section also:good:
broky said:
you mean we need to follow these instructions http://forum.xda-developers.com/showpost.php?p=62560397&postcount=3?
BTW great rom,thanks for bringing it to Z1C section also:good:
Click to expand...
Click to collapse
No. Since that I have integrated the changes in the rom. Right now all you need to do is to install and activate Afwall. It is simple: no afwall, no internet. Yes activated afwall - yes internet.
optimumpro said:
You have to read the OP: Install afwall and kernel adiutor as normal apps (they are linked in the OP), set/activate Afwall and you will have the internet...
Click to expand...
Click to collapse
Thank you for help.

[CLOSED][ROM][Unofficial][10.0][microG][signed]hardened LineageOS 17.1 Oneplus 3/3T

This thread is deprecated - please refer to its LineageOS 18.1 successor thread
This thread is dedicated to provide hardened Lineage-OS 17.1 builds with microG included for the OnePlus 3/3T with current security patches.
It is the successor of my Lineage 16.0 thread.
It may be worth to also look there, if you are looking for information.
Features of this ROM
Download here
Pre-installed microG and F-Droid like LineageOS for microG project (own fork)
Pre-installed AuroraStore
OTA Support
eSpeakTTS engine
Bromite as default browser
Additional security hardening features listed below
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Kernel kept up to date with ASB patches and Google kernel/common 'android-3.18' branch
Debloated from Oneplus blobs for Alipay, WeChatpay, Soter and IFAA
Hardened bionic lib and constified JNI method tables
Current release levels
Security string: 2021-10-05
AOSP tag: 10.0.0_r41
Bromite System Webview: M93
Source-code and build instructions
Kernel: https://github.com/lin17-microg/android_kernel_oneplus_msm8996/tree/lin-17.1-mse3
Build manifest: https://github.com/lin17-microg/local_manifests/tree/lin-17.1-microG
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty of information available.
Pre-Requisites
If you come from OxygenOS Stock ROM, make sure to update to the latest offered software version (if not, no issue).
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
An unlocked bootloader (see e.g. LineageOS install instructions)
OxygenOS 9.0.6 firmware, which is needed for LineageOS 17.1 - see next section
Download the most current .ZIP file of the ROM and place it to your phone's internal memory
OxygenOS 9.0.6 Firmware
If you come from my LineageOS 16.0 build - or any Android 9 or 10 based ROM, you most probably have already the proper firmware.
And yes, LineageOS 17.1 is Android 10, but the latest firmware for this device has been published by Oneplus for Android 9.
How to find out about your current firmware, if you use a Custom ROM:
Connect as root via adb to your phone and enter the command adb shell cat /system/vendor/firmware_mnt/verinfo | grep Time_Stamp
If the result is "Time_Stamp": "2019-11-04 21:25:29", you are on the latest firmware, if the date/time is earlier, you need to update the firmware. THIS THREAD has got more information for you.
If you come from an Oreo (Android 8.x) Custom ROM, READ THE OP OF THIS THREAD CAREFULLY !
I can't explain it better and I am not going to repeat or summarize this. It really is in your interest to carefully read it - you have been notified and warned. Please also pay attention to the last section named "Alipay, WeChatpay, Soter and IFAA" - I strongly recommend to use the debloated firmware.
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery twrp-x.x.x-x-oneplus3.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into the phone's Android system after having flashed TWRP! Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP must be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory". Swipe to confirm the deletion and get back into the main menu.
DO NOT flash Gapps!
This ROM comes with pre-installed microG. So don't attempt to flash Gapps.
Install ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard). Choose the .ZIP file of our ROM and swipe to flash.
If you update from a previous version of my ROM, including my LineageOS 16.0 build, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 17.1 - be patient, the first boot after flashing a new ROM takes quite long!
Dealing with signed builds
Please note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.
This happens at your own risk - make a backup with TWRP before!
Download and extract the file migration.sh from this archive
This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
boot into TWRP
push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
(In case you receive an error, try sh ./migration.sh official instead)
flash the ROM .zip
wipe Cache and Dalvik/ART Cache
reboot system
More background information and the "theory behind" can be found in the LineageOS wiki and AOSP reference.
Bug reports:
If you have a problem, please create a post with these informations:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Please note that I can't and won't support issues with builds using a different kernel or Xposed.
In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.
Credits
AOSP project
LineageOS project
microG project
Graphene OS project
csagan5 (Bromite)
WhyOrean (Aurora)
nvertigo67 (for the modded 9.x firmware and for collaboration)
Change log
2021-10-14 - FINAL
ASB Security string 2021-10-05
Bromite System Webview and Browser updated to 93.0.4577.83
Kernel upstreamed (note: tag equals last months tag)
2021-09-12
ASB Security string 2021-09-05
Kernel upstreamed to tag ASB-2021-09-05_3.18
microG microG 0.2.22.212658-2
2021-08-08
ASB Security string 2021-08-05
Kernel upstreamed to tag ASB-2021-08-05_3.18
Bromite System Webview and Browser updated to 92.0.4515.134
F-Droid updated to 1.13
Fix in WiFi randomization
2021-07-10
ASB Security string 2021-07-05
Kernel upstreamed to tag ASB-2021-07-05_3.18
Bromite System Webview and Browser updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
2021-06-13
ASB Security string 2021-06-05
Kernel upstreamed to tag ASB-2021-06-05_3.18
Kernel WLAN driver (qcacld-2.0) patched to include mitigations against "Frag" vuln.
Bromite System Webview and Browser updated to 91.0.4472.102
microG 0.2.19211515-9
2021-05-09
ASB Security string 2021-05-01
Kernel upstreamed to tag ASB-2021-05-05_3.18
Bromite System Webview and Browser updated to 90.0.4430.204
microG upstreamed (no version change)
Update: AuroraServices 1.1.1
2021-04-10
ASB Security string 2021-04-01
Kernel upstreamed to tag ASB-2021-04-05_3.18
Bromite System Webview and Browser updated to 90.0.4430.59
F-Droid updated to 1.12
Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
2021-03-08
Security string 2021-03-05
Kernel upstreamed to tag ASB-2021-03-05_3.18
Bromite System webview updated to 88.0.4324.207
Bromite Browser updated to 88.0.4324.207
F-Droid 1.11
microG 0.2.18.204714
2021-02-04
Security string 2021-02-05
Kernel upstreamed to tag ASB-2021-02-05_3.18
Bromite System webview updated to 88.0.4324.141
Bromite Browser updated to 88.0.4324.141
F-Droid 1.10-alpha-234
microG 0.2.17.204714-5
2021-01-15 - Initial build
Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser (87.0.4280.106)
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below:
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView (87.0.4280.131)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables and hardened bionic lib
Security Hardening Features - Details
1. Pre-installed microG and F-Droid
same as the LineageOS for microG project
2. Pre-installed AuroraStore
works w/o having to enable the "unknown sources feature"
3. Extra control of sensor access for additionally installed user apps
Special access under app permissions
4. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
5. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 17.1 (all settings can be changed at any time later):
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sensitive information is hidden on the lock screen
Camera app: Location tagging disabled by default
Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without
6. Optional blocking of Facebook- and Google-Tracking
Settings => Network & Internet (scroll down)
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but certain apps on an internal exception list will still be able to connect (AuroraStore, microG, or e.g. NewPipe, if installed)
7. Optional disable captive portal detection and to select Captive portal server URL provider
Settings => Network & Internet (scroll down)
When deactivated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used. Further, the captive portal URL provider can be set (default is GrapheneOS and not Google; Settings - Network & Internet)
8. No submission of IMSI or phone number to Google when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties ) to provide this data . . .
9. Default hosts file with many blocked ad/tracking sites
The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)
10. Privacy-enhanced Bromite SystemWebView
Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.
11. Bromite as shipped Browser
A chromium based browser with many privacy features.
12. Firewall UI
Settings => Privacy - Firewall
Lists all apps and allows to restrict Internet access per app in regards to WiFi, mobile network or VPN
This per-app feature is a standard feature in LineageOS, but the UI to show all apps is an Extra (taken from a topic in LineageOS's Gerrit - it may, or may not, become part of the official LineageOS one day)
13. Maximum password length increased to 64
Thanks a lot!! Will flash and report tomorrow!!
Hello!
Does this ROM allow to lock a bootloader?
Clean flashed this morning. So far so good!
zhenev said:
Hello!
Does this ROM allow to lock a bootloader?
Click to expand...
Click to collapse
I would like to refer you to the below post from the 16.0 predecessor thread:
[CLOSED] EOL [ROM][Unofficial][9.0.0][microG][signed]hardened LineageOS 16.0 for Oneplus 3/3T
Thread is discontinued: Please visit the my LineageOS 17.1 successor thread This thread is dedicated to provide hardened Lineage-OS 16.0 builds with microG included for the OnePlus 3/3T with current security patches. It is the successor of my...
forum.xda-developers.com
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
WM-Sef said:
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
Click to expand...
Click to collapse
What phone and firmware? Works like a charm for me on OP3 and OOS 9.0.6 firmware.
WM-Sef said:
Installed this ROM today, clean.
My observations so far:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
In TWRP it works fine, so it clearly is a ROM issue.
(Possible related?) Termux crashes with a OutOfBoundsError
Thanks for your effort keeping this ROM alive.
Click to expand...
Click to collapse
USB works fine on my own device. As suggested by @Anghirrim - what firmware are you on?
MSe1969 said:
USB works fine on my own device. As suggested by @Anghirrim - what firmware are you on?
Click to expand...
Click to collapse
How do I check for the firmware version? It's not under Settings -> Build Number, only the Android Version.
Solved the problem by switching the default USB action to 'MTP'. After that, it suddenly started working.
Still no clue about the Termux issue.
WM-Sef said:
How do I check for the firmware version? It's not under Settings -> Build Number, only the Android Version.
Click to expand...
Click to collapse
The OP of this OP3(T) firmware thread indicates to look at the file /system/vendor/firmware_mnt/verinfo/ver_info.txt
WM-Sef said:
Still no clue about the Termux issue.
Click to expand...
Click to collapse
Their docu indicates issues with Android 10.
WM-Sef said:
USB doesn't work. When I plug it in, it sounds and it charges, but it is not connected to my computer. The 'USB mode' options in settings are all greyed out. No obvious messages in logcat.
Click to expand...
Click to collapse
I had the same issue but just enabling USB-Debugging from the developer options fixed it. I was a bit surprised too and that shouldn't be normal I guess.
SenseSei said:
I had the same issue but just enabling USB-Debugging from the developer options fixed it. I was a bit surprised too and that shouldn't be normal I guess.
Click to expand...
Click to collapse
As indicated before, I do not experience such an issue with my own device, so I can't reproduce this issue.
This is actually fascinating, thank you!
How is the exact steps to install? I'm coming from another rom.. Please help.
1) Advanced Wipe >> flash fw >> flash rom
or
2) Flash fw >> Advanced wipe >> flash rom
Confused after see this thread and fw installation's thread linked above.
vkey.ptr said:
How is the exact steps to install? I'm coming from another rom.. Please help.
1) Advanced Wipe >> flash fw >> flash rom
or
2) Flash fw >> Advanced wipe >> flash rom
Confused after see this thread and fw installation's thread linked above.
Click to expand...
Click to collapse
The above order does not matter, as the firmware is flashed to different partitions than those to be wiped.
EDIT:
If you have already 9.0.6 firmware, there is no need to flash it again.
this is just what I need for my old OP3. Running a degoogled 6T as daily and still need occasional apps that do not work w/o google. flashing without hesitation and reporting back.
EDIT: a question. can I flash twrp right back after flashing the rom? I know im giving up over the air updates, but im fine with that.
I am on LineageOS 17.1 for microG, unlocked bootloader, rooted with Magisk, 9.0.6 official firmware, but I would love to try this ROM.
Few questions, please:
- can I install modded firmware, because this sounds good: "The modem firmware contains some alipay* and soter* files used for Alipay and WeChatpay. Since these are suspect to be a privacy hazard, I've modified NON-HALOS.bin to not contain any of these files any more"
- this ROM can be rooted with Magisk 20.4 or newer?
- do I have to do "clean install", and finally
- is wiping internal sd card (pics, videos etc.) obligatory?
Thanks in advance

⚡ [INFO] [ROM][12][M205x] Lineage OS 19.0 [9-January-2022] [INFO]⚡

ѕαмαя νιѕρυтє​
ALL CREDIT TO SAMARV-121
Original on samarv121.cf/lineageos-19.0-m20lte/​
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.​
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Features​
Enforcing SELinux
AES-256-XTS File Based Encryption (FBE)
Passes SafetyNet out-of-the-box
Signature spoofing support (for microG)
Google Sans as a default font
Monet theme engine customizer (Display settings)
Fast charging disabler (Battery settings)
High touch sensitivity Mode (Display settings)
Swipe fingerprint for notification (Settings->System->Gestures)
Ambient display gestures (Settings->Display->Lockscreen->Ambient Display)
Known issues​
IMS (VoLTE,ViLTE,VoWiFi)
Wide angle camera
Reporting Bugs​
Don’t report bugs if you have any custom kernel or module installed
Create new issue here or Report it here.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you’re doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Changelog​2022-01-09
January ASB (android-12.0.0_r26)
Implemented almost every LineageOS feature
Added seperate built-in gapps build
Replaced AOSP Camera app with GrapheneOS Camera
Passes SafetyNet out-of-the-box
Unshipped Pixel Launcher and GBoard from Vanilla build
Added option to disable Fast charging (Battery settings)
Added option to enable High touch sensitivity Mode (Display settings)
Added LiveDisplay (Display settings)
Added setting to manually customize monet theme engine (Display settings)
Unlimited Google Photos storage
2021-12-102021-11-20
Screenshots​Expand
Device info​
Kernel - 4.4.x
Chipset - Exynos7904
Telegram channel​
Click here
Support group​
Click here
Instructions​If you are coming from stock ROM or any custom ROM
Boot into custom recovery
Format data
Flash latest build
Flash gapps package (optional)
Reboot your device once the installation is done
If you are already on LineageOS-19.0
Boot into custom recovery
Flash latest build
Reboot your device once the installation is done
FAQs​I’m getting bootloop
Don’t flash any additional package if you are flashing
FORMAT data (not WIPE)
TWRP isn’t booting after flashing this rom
Yeah, It’s not supported. just reboot your device. Lineage Recovery will automatically get installed.
MTP not working
Disable USB debugging from developer options if you have it enabled.
Safetynet is failing after rooting the device
If you are on Magisk 23.0:
Enable MagiskHide from Magisk Manager app
If you are on newer version (Zygisk):
Enable “Zygisk” option from the Magisk Manager app
Reboot your device
Enable “Enforce DenyList” option
Go in “Configure DenyList”
Enable “Show system apps” option then search ‘Google Play Services’ and tap on it (but NOT on the tick box!) to expand activities
Enable “com.google.android.gms” and “com.google.android.gms.unstable”
Downloads​
LineageOS-19.0(Vanilla) - Download
LineageOS-19.0(Gapps) - Download
Lineage Recovery - Download
Hi. There's a new build almost everyday. Where can I find the change log?
Could IMS and Wide Angle Camera work on future builds or is it next to impossible?
Hi ..
I m looking for a custom Lineage os for my Samsung m20 .UI : core 2 . M20 - DS20F , can you help me with this .

[ROM][Huawei][12] LeaOS - AOSP 12.1 for Huawei device (EMUI 9)

Official AOSP for Huawei (ane) - LeaOS-PHH (android 12.1 version)
LeaOS is a project which based on AOSP with phhusson's Treble GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, Media App, Default Sound, MediaScanner fixes etc..)
Changelog :
LeaOS-PHH Jul 2022 version
Jul 2022 SPL
Build with last android aosp source (12.1.0_r11) and v415 phh
Fix MediaScanner crash and no default sound (ringtone, alarms..)
Fix all selinux denied
Add dynamic root
Add option in TrebleApp to collect adb log and create txt file in sdcard
Include specific properties for ANE-LX1
Installation
Download file : “LeaOS-A12-20220724-iceows-google-ane.7z" or "LeaOS-A12-20220724-iceows-ane.7z" and extract img file
Flash system image : fastboot flash system <drag system.img here>
Reboot and setup phone with android first start assistant *
* Do not set pin code with google apps version
Source Code:
https://github.com/Iceows
ROM OS Version: Android 12.1
ROM Kernel: Linux 4.9.x
ROM Firmware Required: EMUI 9
Based On: PHH AOSP v415
Credits:
PHH
And all the others who tested my patches and helped me improve this ROM
Support Group
reserved
Is Bluetooth pairing bug fixed for our device in this version?
luka_bubi said:
Is Bluetooth pairing bug fixed for our device in this version?
Click to expand...
Click to collapse
This probably won't help under [A12] GSI, but have you tried bluetooth manager apk? (google play or f-droid)
-Alf- said:
This probably won't help under [A12] GSI, but have you tried bluetooth manager apk? (google play or f-droid)
Click to expand...
Click to collapse
You can solve the problem with this app
Bluetooth Force Pin Pair (Conn - Apps on Google Play
Solve some Bluetooth pairing connect problems such as: Get the error wrong pin..
play.google.com
luka_bubi said:
Is Bluetooth pairing bug fixed for our device in this version?
Click to expand...
Click to collapse
Pairing bug is only with code pin bluetooth device. You can use an app to fix it, see my Alf response
Root don't work for me, i don't know why.. Safetynet don't work too.. Any solutions ?
Dual SIM don't work on custom roms?
I too could not get root to work (in order to remove root) and as consequence pass Safetynet also. I have tried with LeaOS - AOSP and LeaOS - Lineage ROM. As recommended in this comment I went with Pixel experience, but did not like it so I returned to @AndyYan LineageOS ROM.
AndyYan pass safetynet ? And for root you want a root rom or a non root rom ?
Pixel pass safetynet and Netflix stock playstore work fine with my patch for drm.wide (preavs)
As long as there is a clean ROM with no extra stuff that I have to remove then I do not need root. In most ROMs I need to became root to remove root and be able to pass SafetyNet.
As far as AndyYans ROMs go they do not pass Safetynet completely, just enough to fool my banking apps to work normally. That is good enough for me for my normal daily use of this phone.
luka_bubi said:
As long as there is a clean ROM with no extra stuff that I have to remove then I do not need root. In most ROMs I need to became root to remove root and be able to pass SafetyNet.
As far as AndyYans ROMs go they do not pass Safetynet completely, just enough to fool my banking apps to work normally. That is good enough for me for my normal daily use of this phone.
Click to expand...
Click to collapse
Ok so just securize ROM. I have already made a twrp patch to do this job, but not publish for the moment
Hello, I would like to ask if this gsi can be used for hi6250 models?Because the gsi of Android12L that I brushed several phh before can't boot ...
altairfr-huawei - Browse /LeaOS-A13 at SourceForge.net
sourceforge.net
is this for p20lite?
how do i know wich Rom meant for lx1?
lucsol said:
altairfr-huawei - Browse /LeaOS-A13 at SourceForge.net
sourceforge.net
is this for p20lite?
how do i know wich Rom meant for lx1?
Click to expand...
Click to collapse
For the moment this version not boot on ane-lx1. Boot only with mi 10 phone

Categories

Resources