[ROM] DivestOS 15.1+18.1 for shamu - Nexus 6 Android Development

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Nexus 6 Notes:
- 15.1 builds are also available for those who need IMS/VoLTE
- in-place upgrade to 18.1 is not possible unlike previous DivestOS releases due to keystore change
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-shamu
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#shamu
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/LineageOS/android_device_moto_shamu
- Kernel: https://github.com/LineageOS/android_kernel_moto_shamu
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...8.1/CVE_Patchers/android_kernel_moto_shamu.sh, https://github.com/Divested-Mobile/...5.1/CVE_Patchers/android_kernel_moto_shamu.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----

Hi, this is really great! I'm on e OS now so I'm accustomed to (almost) no google. Although I want to ask:
1. if microG is possible to install and use? Say like in a work profile. I have a banking app which is dependent on google and I figure if bootloader is locked it won't detect root no more.
2. Updates are OTA?
3. Reverse process is possible? Going back to e OS in examlpe
Regards

Kjivar said:
Hi, this is really great! I'm on e OS now so I'm accustomed to (almost) no google. Although I want to ask:
1. if microG is possible to install and use? Say like in a work profile. I have a banking app which is dependent on google and I figure if bootloader is locked it won't detect root no more.
2. Updates are OTA?
3. Reverse process is possible? Going back to e OS in examlpe
Regards
Click to expand...
Click to collapse
1. microG is not supported by DivestOS. If you want to compile DivestOS yourself you just need to change one line to build in microG. However simply having a locked bootloader with microG is not enough to pass SafetyNet. At a minimum you'd likely need 'DroidGuard Helper'.
2. Yes, of course.
3. Most definitely. Just unlock and flash whatever.

Ok, thanks
It actually isn*t depending on SafetyNet, just detects root (unlocked bootloader I think) with Rootbeer. Using Magisk hide is only solution now. Dunno if Droid Guard helper has been updated yet. I'll check into it tho.
Going stock with locked bootloader is out of the question. Guess I'll just go ahead with this, and use a second device for that app.
Keep up the good work

@Kjivar
Anyway, locking the bootloader is perhaps a bad idea while running a custom rom - if the phone becomes unbootable for some reason, you may not be able to fix it.
Edit: see reply below - locking is safe on this rom (but I still wouldn't try it on any other rom)

runekock said:
@Kjivar
Anyway, locking the bootloader is perhaps a bad idea while running a custom rom - if the phone becomes unbootable for some reason, you may not be able to fix it.
Click to expand...
Click to collapse
Bootloader locking on supported devices is one of the primary benefits of running DivestOS.
Older devices let you unlock no matter and newer ones will do so as long as OEM unlocking is checked.
Even if /system is corrupted the OEM unlock flag is stored in the checksummed persistent data block and you'd still be able to unlock to fix.
Especially on older devices bootloader locking can be bypassed using manufacturer tools.
My daily driver for the past five years has always had its bootloader locked.
And my stack of test devices all have their bootloader locked.
It is not my fault other ROMs aren't signed correctly to support such a basic feature.

This ROM looks shady

Rootmaster906 said:
This ROM looks shady
Click to expand...
Click to collapse
Please elaborate.

SkewedZeppelin said:
Please elaborate.
Click to expand...
Click to collapse
You can't do anything with this thing. You can't flash gaps and you can't flash magisk. What good is this ROM if you can't do any of that?

Rootmaster906 said:
You can't do anything with this thing. You can't flash gaps and you can't flash magisk. What good is this ROM if you can't do any of that?
Click to expand...
Click to collapse
Those are valid concerns for some users like yourself, but that simply makes you not the target audience.
It does not make it shady.

SkewedZeppelin said:
Those are valid concerns for some users like yourself, but that simply makes you not the target audience.
It does not make it shady.
Click to expand...
Click to collapse
My apologies. I wasn't trying to diss your rom. What happens when I flash this? Is this actually a good ROM or no?

Rootmaster906 said:
My apologies. I wasn't trying to diss your rom. What happens when I flash this? Is this actually a good ROM or no?
Click to expand...
Click to collapse
If you feel the features offered are in your interest, I welcome you to try it.
Just sure to backup first and ensure that backup is somewhere other then your phone.
As forceencrypt is set by default.
And TWRP will be replaced with DivestOS recovery on first boot.

SkewedZeppelin said:
If you feel the features offered are in your interest, I welcome you to try it.
Just sure to backup first and ensure that backup is somewhere other then your phone.
As forceencrypt is set by default.
And TWRP will be replaced with DivestOS recovery on first boot.
Click to expand...
Click to collapse
How do I decrypt? Same as formatting data? Also, can I flash twrp back in divest recovery?

Rootmaster906 said:
How do I decrypt? Same as formatting data? Also, can I flash twrp back in divest recovery?
Click to expand...
Click to collapse
You can format /data in TWRP.
You can flash TWRP back using fastboot.

SkewedZeppelin said:
You can format /data in TWRP.
You can flash TWRP back using fastboot.
Click to expand...
Click to collapse
This ROM is pretty dope! I guess only 8.1 is available. Why can't gapps and magisk be used? Thanks

Rootmaster906 said:
This ROM is pretty dope! I guess only 8.1 is available. Why can't gapps and magisk be used? Thanks
Click to expand...
Click to collapse
Hmm?
8.1 is only if you require VoLTE, otherwise 11.0 is reported stable and more secure.

SkewedZeppelin said:
Hmm?
8.1 is only if you require VoLTE, otherwise 11.0 is reported stable and more secure.
Click to expand...
Click to collapse
Page doesn't have a link for a11. Edit..had to refresh page. Sorry.

Rootmaster906 said:
Page doesn't have a link for a11
Click to expand...
Click to collapse
I assure you, it is there, use Find In Page/Ctrl-F:
https://divestos.org/mirror.php?base=LineageOS&f=shamu/divested-18.1-20210807-dos-shamu.zip

SkewedZeppelin said:
I assure you, it is there, use Find In Page/Ctrl-F:
https://divestos.org/mirror.php?base=LineageOS&f=shamu/divested-18.1-20210807-dos-shamu.zip
Click to expand...
Click to collapse
Found it. So....why isn't magisk and Gapps supported?

Rootmaster906 said:
Found it. So....why isn't magisk and Gapps supported?
Click to expand...
Click to collapse
I don't believe most users need root access, and it also reduces security and prevents easily using features such as verified boot.
GAPPS goes strongly against the privacy and freedom that DivestOS strives to offer, as it is proprietary code from Google.

Related

[DISCONTINUED][GSI][9][Reference] LineageOS 16.0 GSI (all archs) and how to build them

{
"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"
}
Background:
We've been offered LOS 16 GSIs in the past (here, and here), but they haven't been updated in quite a while, so as a LineageOS lover, I decided to step up and do it myself. Turns out it wasn't so easy - there were a number of hurdles that prevented it from building properly, booting or being feature-complete. But here I am, having figured out most if not all what's needed, and verified booting on an arm64 ab device I own, I'm ready to share my findings as well as some builds with you.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Do not report hardware-related bugs in this thread. I am selfish and only care about getting it running on my device with whatever features I need working. Plus I'm not PHH and can't solve any either.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete, see below
Disabled "vendor mismatch" warning on boot
Re-enabled lockscreen shortcuts
Default stretch-to-fullscreen (force apps to render in 18:9)
Extra tip:
If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!
Modifications needed (builders-only):
Now for the juicy part. On top of PHH's already fantastic build script, you'll need these:
device/phh/treble:
Revert Update lineage.mk for LineageOS 16.0 - add back LOS sepolicy, so that LOS-specific features like Profiles, LiveDisplay, Styles, Trust would work
Revert exfat fsck/mkfs selinux label - fix a conflict in doing so
build/make:
Revert Enable dyanmic image size for GSI - fix building
external/tinycompress:
Revert tinycompress: Use generated kernel headers - remove dependency on generated kernel headers
frameworks/base:
Revert Initial support for in-display fingerprint sensors - use PHH's implementation
vendor/lineage:
Apply build/soong/Android.bp: Disable generated_kernel_* - disable generating kernel headers, since GSIs don't have a kernel
Revert lineage: Enforce privapp-permissions whitelist, or change it to log
vendor/qcom/opensource/cryptfs_hw:
Revert cryptfs_hw: Use generated kernel headers - remove dependency on generated kernel headers
Apply [TEMP]: Header hack to compile for 8974 - fix a missing header
And that's it. Doesn't look like much, but most are pretty hacky solutions, and I don't expect them to be merged anywhere. As I said, I'm only interested in getting it running, I don't care what it takes.
Stuff on GitHub (builders-only):
I've also collected necessary scripts/patches and uploaded them: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you still need more clues.
Donate?
https://paypal.me/AndyCGYan
Thanks for reading - I hope this could be of use to fellow LineageOS lovers / home builders.
Is there any chance for A-only 64 build?
Lecterr said:
Is there any chance for A-only 64 build?
Click to expand...
Click to collapse
I hope will be for A-only too.. many people would welcome it . :silly:
Lecterr said:
Is there any chance for A-only 64 build?
Click to expand...
Click to collapse
Dejvid50 said:
I hope will be for A-only too.. many people would welcome it . :silly:
Click to expand...
Click to collapse
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
AndyYan said:
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
Click to expand...
Click to collapse
Thank you very much!!! Will test and give feedback....ist it build on latest Phhs V111?
Cool, which one is the a-only? ...it's not clearly writen
odysseus84 said:
Cool, which one is the a-only? ...it's not clearly writen
Click to expand...
Click to collapse
I thought it's the avN one. (Didn't boot on my phone.)
As of now I've received 1 report of A-only booting up alright. Although I don't take hardware-related bug reports, it's advised to post whether it boots on your device so as to let other users know.
Lecterr said:
Thank you very much!!! Will test and give feedback....ist it build on latest Phhs V111?
Click to expand...
Click to collapse
Not sure how I could determine that, but it's fresh synced.
odysseus84 said:
Cool, which one is the a-only? ...it's not clearly writen
Click to expand...
Click to collapse
avN, bvN - not clear enough?
Thanks again for A-only build...tested and works great on MiMax3 with stock PIE vendor!!!
Only thing not working is equalizer for audio, opens a empty screen but no FC or error message...but ringtone, music etc. working.
Just tested this on a Nokia 7 Plus (B2N) with the bvN images. Everything seems to work just fine, except for VoLTE/VoWiFi (which I don't care that much about anyways...).
Voice calls, Camera, MusicFX, Fingerprint, Bluetooth, LTE, all work as expected. Will come back after some usage with more info about battery life and such.
@AndyYan Awesome stuff, Andy! Thank you for this guide--will try to build it myself soon enough after I run your build for a few days to test.
By the way, do you think this will get OTA updates from LineageOS? The updater seems to work as expected, but haven't seen any new options there yet.
Thanks again!
MadalinC said:
By the way, do you think this will get OTA updates from LineageOS? The updater seems to work as expected, but haven't seen any new options there yet.
Click to expand...
Click to collapse
Nope, LOS team even stated explicitly they won't be making any official GSIs.
AndyYan said:
Nope, LOS team even stated explicitly they won't be making any official GSIs.
Click to expand...
Click to collapse
Oh, that is very unfortunate. It is running really smooth as a GSI
So that means that each security patch comes out, I will need to start from scratch and reflash the image? That would make it a bit a pain each month
Anyways, thanks for the quick reply!
On the Galaxy S9: I dirty flashed it over vanilla phh 111 to see if it boots. It did with the usual force close of course.
Then I wiped and reflashed. But stuck at the boot animation. The splash screen was there for a half century too... my guess is the ramdisk stoff from the kernel. there are some other Kernel version I will try those later.
MadalinC said:
So that means that each security patch comes out, I will need to start from scratch and reflash the image?
Click to expand...
Click to collapse
Just flash the image on top (along with whatever mods you're using), no wipe needed. It works like flashing ROMs on a regular A-only device.
AndyYan said:
Just flash the image on top (along with whatever mods you're using), no wipe needed. It works like flashing ROMs on a regular A-only device.
Click to expand...
Click to collapse
Any chance of arm-a LOS16 build?
AndyYan said:
Done, check OP. I can't spare an A-only device to test it though, try at your own risk.
EDIT: might have to wait for SF to mirror the file...
Click to expand...
Click to collapse
Now I'm busy, at night I will try to flash and will report. Thanks for your work
EDIT: Ok, so I was try to flash on Huawei P10 Lite with OpenGapps, and can't boot, no logo, just goes to recovery, that's all.. I was WIPE system, data, cache, dalvik cache
Lecterr said:
Thanks again for A-only build...tested and works great on MiMax3 with stock PIE vendor!!!
Only thing not working is equalizer for audio, opens a empty screen but no FC or error message...but ringtone, music etc. working.
Click to expand...
Click to collapse
do you mind sharing the instructions for flashing the gsi? im on the latest pie beta on my max3.
drxllxffxct said:
do you mind sharing the instructions for flashing the gsi? im on the latest pie beta on my max3.
Click to expand...
Click to collapse
Do u have TWRP recovery?
Finally there's a LOS 16 GSI! I have been looking to try to compile my own with phh build script.
Sorry which one should I use _avN or _bvN if I have an A Only Arm64 (Wayne).
I tried to flash the _avN and got stuck at the Mi logo.
Thank you very much to do the work.
Sent from my Mi MIX 2 using XDA Labs
Boots on Razer phone 1 but no wifi or data. Everything else seems to work. Thank you for the rom (no wifi or data razer phone problem).

crDroid v5.6 for harpia[9.0.0_r40][Stable][Enforcing & VoLTE]

<!---This is a forum post template for manitainers to use on XDA, or whatever forum you post your build(s) on. You can copy/paste what is here and edit as necessary for your purposes-->
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your Moto G4 Play, or coming from another ROM: <--THESE MAY NEED UPDATING FOR YOUR PARTICULAR DEVICE; BE THOROUGH IN INSTRUCTIONS-->
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data.
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
None ATM, tag me and include logs if you see any.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!(Magisk Modules are usually fine)
- have modified system files
- have dirty flashed
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE​
XDA:DevDB Information
crDroid for harpia, ROM for the Moto G4 Play
Contributors
reachomk
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 5.6
Created 2019-07-10
Last Updated 2019-07-17
This ROM is very slow and lagger. The vídeos are very slow. Sometimes flashlight doesn't works and UI system crash. I will return to AOSP extended.
Accelerometer and proximity sensor don't work.
Clean flash.
Enviado desde mi Moto G Play mediante Tapatalk
Flashlight, camera, proximity sensor are with a bug being necessary to restart the cell several times
Update!
Changelog: Fixes sensor issues.
https://drive.google.com/file/d/1O0hkyRA-FWWhpkCUkRN0wM3_17MJ7SoY/view?usp=sharing
I will try it tomorrow.
Sakul94 said:
This ROM is very slow and lagger. The vídeos are very slow. Sometimes flashlight doesn't works and UI system crash. I will return to AOSP extended.
Click to expand...
Click to collapse
Sakul94 said:
I will try it tomorrow.
Click to expand...
Click to collapse
Yes dear bro AOSP Extended is awesome
reachomk said:
Update!
Changelog: Fixes sensor issues.
https://drive.google.com/file/d/1O0hkyRA-FWWhpkCUkRN0wM3_17MJ7SoY/view?usp=sharing
Click to expand...
Click to collapse
Dear mate, you said that you were going to apply to AOSPExtended Official Mantainer in Mid June or July
What happen dear brother??? Because you didn't release the latest version (v6.6) of AOSPExt for your device
Thanks a have a great day
BouncingState said:
Yes dear bro AOSP Extended is awesome
Dear mate, you said that you were going to apply to AOSPExtended Official Mantainer in Mid June or July
What happen dear brother??? Because you didn't release the latest version (v6.6) of AOSPExt for your device
Thanks a have a great day
Click to expand...
Click to collapse
The AospExtended team did not respond to my official request or pm asking for official status. I have no idea why. Perhaps if members ask for it as well, they will be more likely to grant official status. Feel free to lobby them for me. Also, please discuss AEX related things on the AEX forum post I have created.
I plan to skip to AospExtended 6.7 as I have not had much time latly.
beraca said:
Accelerometer and proximity sensor don't work.
Clean flash.
Enviado desde mi Moto G Play mediante Tapatalk
Click to expand...
Click to collapse
Fixed it. Download the new build.
reachomk said:
The AospExtended team did not respond to my official request or pm asking for official status. I have no idea why. Perhaps if members ask for it as well, they will be more likely to grant official status. Feel free to lobby them for me. Also, please discuss AEX related things on the AEX forum post I have created.
I plan to skip to AospExtended 6.7 as I have not had much time latly.
Click to expand...
Click to collapse
Ok my dear friend, thanks a lot for your response
SELinux
Hello all,
how can I activate SELinux in crDroid?
Why is upload by Google drive?
check_for_droid said:
Hello all,
how can I activate SELinux in crDroid?
Why is upload by Google drive?
Click to expand...
Click to collapse
SELinux is currently enforcing. You can set it to permissive by typing in:
Code:
setenforce 0
into an android terminal or flashing a permissive patcher. I use Google Drive because I like it and I have unlimited storage space.
reachomk said:
SELinux is currently enforcing. You can set it to permissive by typing in:
Code:
setenforce 0
into an android terminal or flashing a permissive patcher. I use Google Drive because I like it and I have unlimited storage space.
Click to expand...
Click to collapse
Thanks for your prompt feedback. I have the problem with the full data encryption. The process is hang at 100%.
Otherwise, I like it very much. Very good job!!
Signature Spoofing and Root ADB
HI all,
Do this build have signature spoofing disabled? In CRdroid there used to be a switch to enable signature spoofing and afaik there is a patch on upstream that suggest the signature spoofing is enabled by default:
hXXps://github.com/crdroidandroid/android_packages_apps_crDroidSettings/commit/fe45b12172edf660533f57fc36c7d01e9f0bf0c4
I've tested and seems is disabled, so I'm not sure if there was a patch on this specific build to disable it. I would like to use MicroG on this ROM , and as Xposed is not yet available for pie...
BTW, is it not possible to access ADB as root on this room ?
# adb root
adbd cannot run as root in production builds​
nachognues said:
HI all,
Do this build have signature spoofing disabled? In CRdroid there used to be a switch to enable signature spoofing and afaik there is a patch on upstream that suggest the signature spoofing is enabled by default:
hXXps://github.com/crdroidandroid/android_packages_apps_crDroidSettings/commit/fe45b12172edf660533f57fc36c7d01e9f0bf0c4
I've tested and seems is disabled, so I'm not sure if there was a patch on this specific build to disable it. I would like to use MicroG on this ROM , and as Xposed is not yet available for pie...
BTW, is it not possible to access ADB as root on this room ?
# adb root
adbd cannot run as root in production builds​
Click to expand...
Click to collapse
Your commit link doesn't work, so I can't help you with that until you fix the link. As for adb root, it does not work in "userdebug" flavored builds. It is customary to build "userdebug." If you want root, try using Magisk.
You can read more about build flavors here:
https://source.android.com/setup/develop/new-device#build-variants
Works ok on a XT1607 (2GB of RAM), however is a little laggy. I ran antutu benchmark in this rom, here's a little video i made: https://www.youtube.com/watch?v=loiqq8OBpzY
HI all,
I see my last post was a bit missunderstood.
In CRdroid there used to be a switch to enable signature spoofing and afaik there is a patch on upstream that suggest the signature spoofing is enabled by default:
hXXps://github.com/crdroidandroid/android_packages_apps_crDroidSettings/commit/fe45b12172edf660533f57fc36c7d01e9f0bf0c4
(Please, notice XX on the url. I cant post URLs, so please replace hXXps with https)
Anyway, on this build the singature spoofing is disabled. I would like to use MicroG on this ROM, and signature spoofing is important as I would like to avoid installing Google Apps.
Apart of this, I'm used to use ADB as root on LineageOS and other rooms. In this rom looks is not enabled. I have of course rooted the phone with magisk and I have set on the options "SuperUser access: Apps and ADB".
I can use applications as root, but when I try to connect via ADB as superuser I get this error:
# adb root
adbd cannot run as root in production builds​[/QUOTE]
Is there something missing on this build ?
nachognues said:
HI all,
I see my last post was a bit missunderstood.
In CRdroid there used to be a switch to enable signature spoofing and afaik there is a patch on upstream that suggest the signature spoofing is enabled by default:
hXXps://github.com/crdroidandroid/android_packages_apps_crDroidSettings/commit/fe45b12172edf660533f57fc36c7d01e9f0bf0c4
(Please, notice XX on the url. I cant post URLs, so please replace hXXps with https)
Anyway, on this build the singature spoofing is disabled. I would like to use MicroG on this ROM, and signature spoofing is important as I would like to avoid installing Google Apps.
Apart of this, I'm used to use ADB as root on LineageOS and other rooms. In this rom looks is not enabled. I have of course rooted the phone with magisk and I have set on the options "SuperUser access: Apps and ADB".
I can use applications as root, but when I try to connect via ADB as superuser I get this error:
# adb root
adbd cannot run as root in production builds​
Is there something missing on this build ?
Click to expand...
Click to collapse
I have compiled the rom with the userdebug build flavor, wheras adb root only works in the eng flavor. If you want to use root, try magisk.
adbd cannot run as root in production builds​
Click to expand...
Click to collapse
Reboot to Recovery and you can use "adb root"
Hi, this rom is almost perfect. I'm coming from Aex both of those roms are the best rom.
But this rom app launch time is very poor than aex. Whatsapp and facebook takes very long to launch. Please fix it. Also please update Aex rom too. Thanx

[ROM] DivestOS 15.1+16.0 for hammerhead

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Nexus 5 Notes:
- 16.0 is quite buggy, 15.1 should be stable
- Bluetooth may or may not work on 16.0
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-hammerhead
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#hammerhead
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_lge_hammerhead
- Kernel: https://github.com/LineageOS/android_kernel_lge_hammerhead
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...CVE_Patchers/android_kernel_lge_hammerhead.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
I'm trying to use this but both camera and wifi hotspot do not seem to work. Can I help somehow?
Hammerhead: camera and hotspot do not work. · Issue #140 · Divested-Mobile/DivestOS-Build
Phone boots fine, tho. Bootloader relocking works as well. I haven't tried calling, incoming SMS do work. I'd like to use this phone again, but I can't without camera and hotspot. I did run a logca...
github.com
Hi
@SkewedZeppelin Just did a clean install. I can't remove apps the regular way (tap, hold, swipe to the uninstall field at the top). I have to go into apps section in the settings and there click uninstall.
fw190 said:
Hi
@SkewedZeppelin Just did a celan install. I can't remove apps the regular way (tap, hold, swipe to the uninstall field at the top). I have to go into apps section in the settings and there click uninstall.
Click to expand...
Click to collapse
This is an old bug in the launcher, it happens at random sometimes. Just force stop Trebuchet.
Hi guys.
I have device LG Nexus 5x bullhead and tried to install Divest on it.
(I installed custom ROMs several times, I am not new to this process)
All went smooth, but when I was setting up the phone, on the step to set the screen lock pin/pattern - it just crashed.
After this I had difficulties to boot it even into fastboot menu and when I did - I tried to flash the genuine (Google) ROM on it (I did it several times and it is working ROM), but during the flashing, in the terminal it showed a list of archives missing.
Now the phones goes to Google logo and then to black screen.
Well, I do not know if there is any workaround or not.
Please advice.
Thanks
balakarpo said:
Hi guys.
I have device LG Nexus 5x bullhead and tried to install Divest on it.
(I installed custom ROMs several times, I am not new to this process)
All went smooth, but when I was setting up the phone, on the step to set the screen lock pin/pattern - it just crashed.
After this I had difficulties to boot it even into fastboot menu and when I did - I tried to flash the genuine (Google) ROM on it (I did it several times and it is working ROM), but during the flashing, in the terminal it showed a list of archives missing.
Now the phones goes to Google logo and then to black screen.
Well, I do not know if there is any workaround or not.
Please advice.
Thanks
Click to expand...
Click to collapse
That sounds less like a DivestOS issue and more like user-error or the dreaded Nexus 5X bootloop issue: https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues#Nexus_5X
I test DivestOS on bullhead each monthly update before release (without issue).
SkewedZeppelin said:
That sounds less like a DivestOS issue and more like user-error or the dreaded Nexus 5X bootloop issue: https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues#Nexus_5X
I test DivestOS on bullhead each monthly update before release (without issue).
Click to expand...
Click to collapse
Thanks for replying so soon.
I installed two ROMs before (LineagOS 17.1 and 19.1 Unofficial version) on this device without problem. The unique problem was that I was unable to encrypt the phone on those and that was the main reason to try DivestOS.
I understand it can be the hardware problem (maybe mine), but is there any workaround? Thanks
Hello, first of all thank you for creating this awesome rom. Im using it for some extended period of time on my backup devices which is Nexus 5 and it works great, it feels so secure and also having latest security patch is awesome. Keep doing the great job! Rom is awesome, recommended for everyone!
I managed to install DivestOS 18.1 even on my Nexus 4, works as it should for now. (Been a nexus fan before so i got these 2 nexuses :-D) Is there a chance that you make it for my main phone which is Xiaomi Mi 10t pro, please? At least one build and thats it
scorpion994 said:
I managed to install DivestOS 18.1 even on my Nexus 4, works as it should for now. (Been a nexus fan before so i got these 2 nexuses :-D) Is there a chance that you make it for my main phone which is Xiaomi Mi 10t pro, please? At least one build and thats it
Click to expand...
Click to collapse
Any device I add I have to perpetually maintain.
apollon is already in the queue to be eventually added maybe someday: https://github.com/Divested-Mobile/DivestOS-Build/issues/68
Thank you so much for this
Hello, good day! I was trying to fix my nexus 5 Wi-Fi problem, so I was flashing a few ROMs to see if it get fixed. I tried this one then... No success. Now I'm trying to go back to a stock image, but I'm having trouble to get my phone recognized by the computer. Do I get this problem because the phone is encrypted? Can I decrypt my phone? Can't use trwp eider, because of the encryption.
arnoldwu said:
Hello, good day! I was trying to fix my nexus 5 Wi-Fi problem, so I was flashing a few ROMs to see if it get fixed. I tried this one then... No success. Now I'm trying to go back to a stock image, but I'm having trouble to get my phone recognized by the computer. Do I get this problem because the phone is encrypted? Can I decrypt my phone? Can't use trwp eider, because of the encryption.
Click to expand...
Click to collapse
TWRP should work fine?
DivestOS makes no changes that would lock you to DivestOS or prevent you from switching.
Maybe try a different cable, and a USB 2.0 port.
Also Wi-Fi works fine on my hammerhead, if it doesn't work on multiple systems maybe you have a hardware issue or corrupted persist partition.
SkewedZeppelin said:
This is an old bug in the launcher, it happens at random sometimes. Just force stop Trebuchet.
Click to expand...
Click to collapse
Big fan of your OS, i know you do not support SU or Magisk or microG, but could you atleast let us multiboot with your awesome OS? please kindly add the Kexec-Hardboot patch to your kernel so we could be able to boot into a googled OS, or Ubuntu Touch.
thanks in advanced and looking forward to this patch added.
Kexec-hardboot patch
[email protected] said:
please kindly add the Kexec-Hardboot patch to your kernel so we could be able to boot into a googled OS, or Ubuntu Touch.
Click to expand...
Click to collapse
No, kexec is explicitly disabled for security reasons: https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Common/Functions.sh#L1048
If you want such changes the way to get them is by compiling your own builds: https://divestos.org/pages/build
Ubuntu Touch for this device is also blatantly insecure missing years of basic security patches: https://github.com/ubports/android_kernel_lge_hammerhead/commits/ubp-5.1
SkewedZeppelin said:
No, kexec is explicitly disabled for security reasons: https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Common/Functions.sh#L1048
If you want such changes the way to get them is by compiling your own builds: https://divestos.org/pages/build
Ubuntu Touch for this device is also blatantly insecure missing years of basic security patches: https://github.com/ubports/android_kernel_lge_hammerhead/commits/ubp-5.1
Click to expand...
Click to collapse
please do elaborate on the security reasons, all kali nethunter kernels have Kexec-hardboot enabled, i run the latest version and would love to see the exploits for it. Please enlighten me.
[email protected] said:
please do elaborate on the security reasons, all kali nethunter kernels have Kexec-hardboot enabled, i run the latest version and would love to see the exploits for it. Please enlighten me.
Click to expand...
Click to collapse
There are no direct exploits for it, it is just attack surface reduction.
SkewedZeppelin said:
There are no direct exploits for it, it is just attack surface reduction.
Click to expand...
Click to collapse
maybe possibly supply an optional flashable zip for this minor reduction. giving the user the option to enable this to run nethunter kernel, currently i run it systemless, but i have to use an external wifi adapter, honestly is not very stealthy. I believe there are various benefits to having hardboot, that is just one. (having internal wifi support for nethunter)
P.S. maybe it could be added as a developer option in your OS?
[email protected] said:
maybe possibly supply an optional flashable zip for this minor reduction. giving the user the option to enable this to run nethunter kernel, currently i run it systemless, but i have to use an external wifi adapter, honestly is not very stealthy. I believe there are various benefits to having hardboot, that is just one. (having internal wifi support for nethunter)
Click to expand...
Click to collapse
no.
That would require compiling every kernel twice.
SkewedZeppelin said:
no.
That would require compiling every kernel twice.
Click to expand...
Click to collapse
to recompile your kernel do i simply remove "optionsNo+=("KEXEC" "KEXEC_FILE");" and add it to the "optionsYes+=(" section ?

[ROM] LineageOS 20.0 UNOFFICIAL - 1.2 [2023-05-06]

LineageOS 20.0 for Sony Xperia XZ1
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat).
DOWNLOAD
You can download the latest releases here:
poplar (G8341):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_dsds (G8342):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_canada (G8343):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar KDDI (SOV36)
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
RECOMMENDED GAPPS (others works too)
https://androidfilehost.com/?w=files&flid=322935
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Currently, LOS isn't feature complete yet, so some things, buttonn, advanced menù etc. may be still missing
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Source Code
poplar: https://github.com/whatawurst/android_device_sony_poplar
poplar_dsds: https://github.com/whatawurst/android_device_sony_poplar_dsds
poplar_canada: https://github.com/whatawurst/android_device_sony_poplar_canada
poplar_KDDI: https://github.com/whatawurst/android_device_sony_poplar_kddi
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-06
ALL CREDITS TO DERF ELOT AND THE OTHER DEVS BEHIND THE ROM, I'M ONLY POSTING IT.
---------------------------------------
Changelogs:
v1.2 (2023-05-10):
- Updated to T QPR2 release (LineageOS upstream)
- Updated to May 2023 Security updates (both ROM and kernel)
- Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
- Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
- Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
- Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
- Fully enabled IMS on Congstar Germany via overlay on lilac
- Possibly some battery/performance optimizations here and there
- Fixed Android Auto support
- Added new LineageOS "Charging control hal" for battery charging care (3)
- Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
v1.1 (2023-01-08):
Updated to T QPR1 release (LineageOS upstream)
New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)
Any other updates by LineageOS upstream
Kernel security updates (also thanks to Flamefire)
Dropped keyprovd service - it is useless on unlocked BL anyway
Show 4G instead of LTE icon - saves some space too
Enable IMS by default - this still only works if carrier is supported
Fix some selinux denials (also thanks to Flamefire)
Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
v1.0 (2022-10-02):
Initial release
Can’t wait to try it !!! Thanks tux
Can i flash this using old twrp version like 3.6.2 - 9?
The rom is great but every time the device reboots and finishes the boot animation it repeats one more time boot animation.
According to the picture, I can't scroll down as usual, can only use those 4 buttons @@ until rebooting (I had landscape rotation to watch youtube then rotate the screen again when the video ends and it's like that
).
rarely but the sound doesn't play even if i keep the volume high or switch to listening to music or watching youtube until the device is restarted
(sorry if I said wrong or wrong grammar, I'm not very good at English. )
raffyei8ht said:
Can i flash this using old twrp version like 3.6.2 - 9?
Click to expand...
Click to collapse
No idea, but for internal memory decription the new one is needed.
Tux111 said:
No idea, but for internal memory decription the new one is needed.
Click to expand...
Click to collapse
What is the use of internal decription if you don't mind me asking
raffyei8ht said:
What is the use of internal decription if you don't mind me asking
Click to expand...
Click to collapse
By default android protect (encrypt) your internal memory. TWRP lacked decryption for a long time, now its supported. This means, with new recovery, you can see and manage your internal memory via TWRP using your lockscreen password. Before, you simply can't.
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
This is a very good ROM. Good for daily use. Didn't encounter any problem. Can't wait for the Pixel Experience Android 13.
ecrissor said:
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Click to expand...
Click to collapse
FP perfectly working.
ecrissor said:
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
Click to expand...
Click to collapse
I guess you have some missing files or something like that. Try reflashing stock rom and persist.img, something wrong with your files.
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Nice room
great work
poplar_dsds said:
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Click to expand...
Click to collapse
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Tux111 said:
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Click to expand...
Click to collapse
Okay i see, thank you! I updated to your version of twrp and dirty flashed the rom from 19.x to this version, worked great, even with apps and so on!
Also thanks for the ROM!
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
xdatomsgmail said:
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
Click to expand...
Click to collapse
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Hi, so I've been absent from Custom Roms for the last couple years - since I got my XZ1 and the DRM key extraction was too much of a hassle for me as I didn't miss much from the stock rom.
Since I got some spare time over the years I was thinking to finally tackle that topic, but I have two questions:
1) The opening post says this
Tux111 said:
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Click to expand...
Click to collapse
is it even still relevant for me to back up my DRM keys / back up the TA partition if I don't want to go back to stock? what camera are you using then? is the quality comparable? is slow motion still possible?
2)
i know that in the past, safety net checks were just looking for bootloader / root, but they changed to checking if the ROM is signed with a proper signingkey, right? is this rom signed with a non-test-key?
I've got a couple of banking apps on my phone and it would obviously prevent it from being a daily driver if they were not supported anymore :/
Thanks in advance!
New LOS Update 1.1 is here! Enjoy!
xdatomsgmail said:
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Click to expand...
Click to collapse
By default the browser isn't Google Chrome afaik, so i don't see the problem. Also, tbh, this makes no sense considering Android=Google. Chromium is builded inside the ROM,is part of the ROM,so once you install Android, you are installing something from Google. So i don't get it.
If you don't install gapps, then you don't have Chrome as default browser. Otherwise, flash gapps and remove Chrome.

[ROM] DivestOS 20.0 for beryllium

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
(normally I only make threads for devices known fully working, however making this thread to replace an unofficial and improper thread)
Poco F1 Notes:
- camera does not work on these builds due to a longstanding incompatibility with the kernel changes made
a workaround is to flash an official LineageOS boot.img, however that negates all of the kernel security patches and hardening
if anyone technical can help bisect the changes that would be much appreciated
help to compile and what to change can be provided as needed
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-beryllium
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#beryllium
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_xiaomi_beryllium, https://github.com/LineageOS/android_device_xiaomi_sdm845-common
- Kernel: https://github.com/LineageOS/android_kernel_xiaomi_sdm845
- Kernel CVE Patches Applied: https://gitlab.com/divested-mobile/.../CVE_Patchers/android_kernel_xiaomi_sdm845.sh, https://gitlab.com/divested-mobile/.../CVE_Patchers/android_kernel_xiaomi_sdm845.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
SkewedZeppelin said:
Poco F1 Notes:
- camera does not work on these builds due to a longstanding incompatibility with the kernel changes made
a workaround is to flash an official LineageOS boot.img, however that negates all of the kernel security patches and hardening
if anyone technical can help bisect the changes that would be much appreciated
help to compile and what to change can be provided as needed
Click to expand...
Click to collapse
Probably something with hardening broke it?
I tag @Pierre2324 and @REIGNZ3 which maintain their own kernels, if they have some spare free time beside their own projects, to take a look and help with info if possible.
Retrial said:
Probably something with hardening broke it?
Click to expand...
Click to collapse
perhaps, the camera isn't broken on any other device with the same changes and I spent many hours sanity check the changes that are applied to it
even overhauled a lot of the CVE patcher in hopes it'd fix it: https://divestos.org/index.php?page=news#2022-03.2
it is a weird outlier
SkewedZeppelin said:
perhaps, the camera isn't broken on any other device with the same changes and I spent many hours sanity check the changes that are applied to it
even overhauled a lot of the CVE patcher in hopes it'd fix it: https://divestos.org/index.php?page=news#2022-03.2
it is a weird outlier
Click to expand...
Click to collapse
camera: fix new version · LineageOS/[email protected]
Opensource base V11.0.0.1 , but not anyone update More people get V11.0.5.0 stable,and Dev version Change-Id: I6903fe7026c16e47c8cd7c9af1169404f50bca59
github.com
Ever tried reverting this?
REIGNZ3 said:
camera: fix new version · LineageOS/[email protected]
Opensource base V11.0.0.1 , but not anyone update More people get V11.0.5.0 stable,and Dev version Change-Id: I6903fe7026c16e47c8cd7c9af1169404f50bca59
github.com
Ever tried reverting this?
Click to expand...
Click to collapse
Thanks I'll pull it into next update and see if it goes, but given the LineageOS kernel is known working I'm confident it is something I broke.
SkewedZeppelin said:
Thanks I'll pull it into next update and see if it goes, but given the LineageOS kernel is known working I'm confident it is something I broke.
Click to expand...
Click to collapse
I know this is time consuming but If you have time, add your sauce to kernel one by one, give for testing each time and see what change result to break the camera
Retrial said:
I know this is time consuming but If you have time, add your sauce to kernel one by one, give for testing each time and see what change result to break the camera
Click to expand...
Click to collapse
@SkewedZeppelin or you can try something like "binary search": apply 50% of patches. In case of no luck, apply other part. For else, divide problematic part again (to apply 50% from this patches). And so on... Anyway, thanks for great ROM!
Hi) Today you have updates on the conventions but I don't see our beryllium (it is no longer supported?
Morillio said:
Hi) Today you have updates on the conventions but I don't see our beryllium (it is no longer supported?
Click to expand...
Click to collapse
The January update is currently uploading. I do not drop devices without announcement.
You can either wait a few hours for the upload to finish or download the last build from here: https://divestos.org/builds/old/old.txt
next day edit: they've been up for a while: https://divestos.org/index.php?page=news#2023-01
Thanks for the reply)) I'll wait!
Anyone currently using this custom rom?
ushilives said:
Anyone currently using this custom rom?
Click to expand...
Click to collapse
> Updater checks past 4 days: 93
Hello there! In your rom there is no support wifi 5.0 frequency? in the settings only 2.4( Tell me I don't see it or it is not there?
Morillio said:
Hello there! In your rom there is no support wifi 5.0 frequency? in the settings only 2.4( Tell me I don't see it or it is not there?
Click to expand...
Click to collapse
you don't see any 5GHz networks at all? or just some? they may have country code mismatched?
SkewedZeppelin said:
you don't see any 5GHz networks at all? or just some? they may have country code mismatched?
Click to expand...
Click to collapse
I'm Talking about hotspot band 5.0 gHz support
Morillio said:
I'm Talking about hotspot band 5.0 gHz support
Click to expand...
Click to collapse
Oh. The Wi-Fi hotspot will default to 5GHz. To use 2.4GHz check the "Extend compatibility" option.
SkewedZeppelin said:
Oh. The Wi-Fi hotspot will default to 5GHz. To use 2.4GHz check the "Extend compatibility" option.
Click to expand...
Click to collapse
I have in the hotspot no switch band 5.0 / 2.4

			
				
The option is right there in your first screenshot.
5GHz is the default.
The "Extend compatibility" toggle is used to switch from 5GHz to 2.4GHz.
SkewedZeppelin said:
The option is right there in your first screenshot.
5GHz is the default.
The "Extend compatibility" toggle is used to switch from 5GHz to 2.4GHz.
Click to expand...
Click to collapse
I'm sorry, but no. On the connected device shows that the network 2.4 band

Categories

Resources