{
"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 4 Notes:
- resized /system is required
- will fail to boot on very first boot. force off once after 3 minutes.
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-mako
- 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#mako
- 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/voron00/android_device_lge_mako
- Kernel: https://github.com/voron00/android_kernel_lge_mako
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...-18.1/CVE_Patchers/android_kernel_lge_mako.sh
- Please give our fellow @voron00 a thanks for keeping the Nexus 4 alive!
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-----
Hello DivestOS,
1 - Do you need to reparation internal memory with Clamor's script before flashing this rom ?
2 - Is it set to permissive like in the latest voron00's LineageOS release or to enforcing by default ?
3 - Can you update it via OTA ?
4 - Does it drain battery when the phone is switched off ?
Thanks
kjsu0 said:
Hello DivestOS,
1 - Do you need to reparation internal memory with Clamor's script before flashing this rom ?
2 - Is it set to permissive like in the latest voron00's LineageOS release or to enforcing by default ?
3 - Can you update it via OTA ?
4 - Does it drain battery when the phone is switched off ?
Thanks
Click to expand...
Click to collapse
1. Yes for the 17.1 build, there is however a 16.0 and 15.1 build available that doesn't need repartitioning.
2. No, DivestOS is *always* enforcing. DivestOS will never ever release a build with permissive SELinux.
3. Yes, DivestOS offers OTA updates for every device since 2017/05/30.
4. When the phone is asleep, no. When the phone is powered off, no.
mako was my daily driver for all of 2019, it was a solid experience despite the age of the hardware.
it was a solid experience despite the age of the hardware
Click to expand...
Click to collapse
I agree, this phone is amazing, never age ...
I got it working on my phone.
I used Clamor's script and everything went almost smooth but have two more questions:
1 - Is it normal that signature can't be verified when installing via twrp ?
2 - On first boot-up rom got stuck on divestos splash screen and didn't want to load entire OS...
I rebooted the phone and on second try it started without any problem and greeted with configuration screen, is that ok ?
kjsu0 said:
I agree, this phone is amazing, never age ...
I got it working on my phone.
I used Clamor's script and everything went almost smooth but have two more questions:
1 - Is it normal that signature can't be verified when installing via twrp ?
2 - On first boot-up rom got stuck on divestos splash screen and didn't want to load entire OS...
I rebooted the phone and on second try it started without any problem and greeted with configuration screen, is that ok ?
Click to expand...
Click to collapse
1. It is not recommended to use TWRP with DivestOS, except for a select few devices. You are intended to use the DivestOS recovery.
2. That is expected, it is a known issue. It occurs due to the modem failing to start after the data partition is encrypted for the first time. The workaround is to wait 5 minutes on the very first boot, power it off, then reboot it. All should be OK after.
@voron00 Are you going to release LOS 17.1 (w/ March security patches) as well? Or 16.0 is a better option for mako in your opinion?
Click to expand...
Click to collapse
16.0 is better.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/rom-unofficial-lineageos-16-0-mako.3758779/post-84653653
It loooks like @varon00 will continue to support only 16, will it impact divestos 17 releases ?
I'm not sure about @voron00 's reasoning to not make 17.1 builds.
But DivestOS 17.1, based on their sources has been fully functional by my standards for nearly a year now.
17.1: Initial bringup · Divested-Mobile/[email protected]
- See items marked with '17REBASE'
github.com
I redid everything again, used fastboot to flash recommended recovery and sideloaded rom from there again. The only downside are apps for banking that require ggle. Do you have any recommendation on that, should I go with open gapps ?
@kjsu0 please kindly read through the divestos.org website. Most of the questions you are asking are all already documented there.
DRM, such as Widevine, is not supported on DivestOS.
Root, such as Magisk, is not supported on DivestOS.
Runtime modification frameworks, such as Xposed, are not supported on DivestOS.
Google Apps, such as Open GApps, are not supported on DivestOS.
Any extra flashable ZIP modifications are not supported on DivestOS.
DivestOS has a strong focus on security, privacy, and freedom. Most of those things are not compatible with our ideals.
This looks like a great project, SkewedZeppelin.
I love the increased privacy focus and built-in OTA support.
I have a question about the custom hosts file. I know DivestOS doesn't recommend using root, but what if we prefer other options like AdAway to manage the hosts file instead?
I'm definitely going to flash DivestOS on the mako. Probably will go with 17.1 instead of the 18 build for now.
Thanks again for starting and maintaining this project!
aospray said:
I have a question about the custom hosts file. I know DivestOS doesn't recommend using root, but what if we prefer other options like AdAway to manage the hosts file instead?
Click to expand...
Click to collapse
DivestOS includes a fairly extensive HOSTS file. Assuming you do not install (m)any proprietary apps and use Mull/Fenix/Bromite with uBlock Origin there should be no visible ads or telemetry phoning home.
As DivestOS does not support root, AdAway is incompatible.
If you want more domains blocked you can use DNS66, however it functions using a local VPN, so you won't be able to use any other VPN apps such as Orbot.
I flashed 17.1 a few hours ago. I did run into the splash screen first boot bug that kjsu0 encountered. I think this should be noted in the first post or on the DivestOS website so people don't get confused, but other than that it's working pretty good so far. Thanks for all your work, SkewedZeppelin!
I looked at the hosts file for DivestOS and I feel like there might be too many sources. I also prefer personalDNSfilter over DNS66 since it has CNAME uncloaking built-in. I guess I'll just use Adguard DNS for private DNS as an alternative.
Calling/data on the latest 18.1 build works thanks to a recent fix from @voron00!
18.1 should now be daily drivable.
@SkewedZeppelin - Could you add the following patch to your rom?
https://android-review.googlesource.com/c/platform/frameworks/base/+/147266/1/packages/SystemUI/src/com/android/systemui/statusbar/policy/DeadZone.java
I've recently experienced the dreaded navigaton bar deadzone issue as described here: https://forum.xda-developers.com/t/wip-fix-dead-navbar-workarounds-and-fixes.3243822/
Edit - Looks like the patch was added a long time ago to AOSP... I guess my mako is finally showing its age.
To anyone who's wondering - DivestOS is still being actively updated. Last update was July 30th.
Thanks to OP for supporting mako to this date. Never thought Android 11 will work this flawlessly in 2012 device.
Wondering if we can get A12 and Material YOU, but then again, it will have serious UI performance problems
Hello DivestOS:
First of all, thank you very much for still supporting Nexus 4 today. I read your post and I still don’t quite understand some points. I would like to ask:
1. What are the specific steps for "resized /system"?
2. After installing Divest OS, can I install other applications on it
at will? Such as: Facebook,Whatsapp.......
3. If it feels inappropriate, can I install another ROM freely?
Please forgive my ignorance, cos I just started to touch the flashing and knowing that Nexus 4 is still supported by community, so I want to try it
Thank you again!
2021redmi2fans said:
Hello DivestOS:
First of all, thank you very much for your team that is still supporting Nexus 4 today. I read your post and I still don’t quite understand some points. I would like to ask:
1. What are the specific steps for "resized /system"?
2. After installing Divest OS, can I install other applications on it
at will? Such as: Facebook,Whatsapp.......
3. If it feels inappropriate, can I install another ROM freely?
Please forgive my ignorance, cos I just started to touch the flashing and knowing that Nexus 4 is still supported by community today, so I want to try it
Thank you again!
Click to expand...
Click to collapse
1. you can use @voron00's repartition script https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view or @Clamor's script https://forum.xda-developers.com/t/repartition-nexus-4-repartition-mako-8gb-16gb-ua-twrp.3844383/
2. yes, you can install Aurora Store from F-Droid in order to install such proprietary apps
3. of course, just flash another recovery from fastboot and flash any ROM as you please
SkewedZeppelin said:
1. you can use @voron00's repartition script https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view or @Clamor's script https://forum.xda-developers.com/t/repartition-nexus-4-repartition-mako-8gb-16gb-ua-twrp.3844383/
2. yes, you can install Aurora Store from F-Droid in order to install such proprietary apps
3. of course, just flash another recovery from fastboot and flash any ROM as you please
Click to expand...
Click to collapse
Okay, got it, thank you, please keep working hard, and may God bless !
Very nice, cool to see Android 11 on the ole Nexus 4.
However the lack of microG signature spoofing is a deal-breaker for me.
Fif_ said:
Very nice, cool to see Android 11 on the ole Nexus 4.
However the lack of microG signature spoofing is a deal-breaker for me.
Click to expand...
Click to collapse
I have no short term plans of including microG.
Related
{
"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.
Samsung Galaxy S5 Notes:
- USB can be weird.
- SD Card detection/mounting can be finicky.
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-klte
- 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#klte
- 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_samsung_msm8974-common, https://github.com/LineageOS/android_device_samsung_klte-common, https://github.com/LineageOS/android_device_samsung_klte
- Kernel: https://github.com/LineageOS/android_kernel_samsung_msm8974
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...VE_Patchers/android_kernel_samsung_msm8974.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-----
Currently using it on my kltedv, all good so far but haven't tested everything yet. Thanks for the work.
Hi,
It's my daily driver for the past few days and I'm really surprised by its fluidity, lightness and speed.
I recommend GS5 owners to test this ROM because it's worth it.
Thanks to the team DIVEST
How's the battery life?
blckberrymv said:
How's the battery life?
Click to expand...
Click to collapse
I have not tried daily driving my klte, but in theory it should be better then stock and most ROMs.
Mainly due to the few included apps.
Very smooth Rom. Thank you to the developers
sinkoo1979 said:
Very smooth Rom. Thank you to the developers
Click to expand...
Click to collapse
Noticed a battery drain. Will update after running placebo kernel with smartpack kernel auditor to check if the battery drain still persists.
sinkoo1979 said:
Noticed a battery drain. Will update after running placebo kernel with smartpack kernel auditor to check if the battery drain still persists.
Click to expand...
Click to collapse
Using a different kernel will dramatically reduce security.
Are you using a VPN? I've found they cause non-stop battery drain.
Any other long-running background apps?
Any spam in logcat?
SkewedZeppelin said:
Using a different kernel will dramatically reduce security.
Are you using a VPN? I've found they cause non-stop battery drain.
Any other long-running background apps?
Any spam in logcat?
Click to expand...
Click to collapse
The battery drain issue was from the new battery I bought from Ebay. The battery was not original. No, I'm not running VPN. Thanks for the ROM
2mecky said:
Currently using it on my kltedv, all good so far but haven't tested everything yet. Thanks for the work.
Click to expand...
Click to collapse
Hi mate, are you still using DivestOS? If not, do you remember any bugs you may have encountered? Thanks
How Stable is this ROM for our klte devices
Is there a thread for jfltexx as well? Search didn't find it, but for other devices. Hmm.
x2k13 said:
Is there a thread for jfltexx as well? Search didn't find it, but for other devices. Hmm.
Click to expand...
Click to collapse
I didn't make one because I only support a single jflte variant.
New thread for you: https://forum.xda-developers.com/t/rom-divestos-18-1-for-jfltexx.4354457/
There are many other devices available on the https://divestos.org website if it isn't clear.
Only a handful have a thread.
SkewedZeppelin said:
I didn't make one because I only support a single jflte variant.
New thread for you: https://forum.xda-developers.com/t/rom-divestos-18-1-for-jfltexx.4354457/
There are many other devices available on the https://divestos.org website if it isn't clear.
Only a handful have a thread.
Click to expand...
Click to collapse
Yeah, okay, I understand. Nevertheless, a dedicated thread might come in handy if some device specific issues occur. So, thanks for opening this.
x2k13 said:
Yeah, okay, I understand. Nevertheless, a dedicated thread might come in handy if some device specific issues occur. So, thanks for opening this.
Click to expand...
Click to collapse
You can report issues via any of the following:
- https://github.com/Divested-Mobile/DivestOS-Build/issues
- https://gitlab.com/divested-mobile/divestos-build/-/issues
- xmpp:[email protected]?join
- mailto:[email protected]
- https://forum.f-droid.org/t/divesto...port-with-enhanced-privacy-and-security/10105
2mecky said:
Currently using it on my kltedv, all good so far but haven't tested everything yet. Thanks for the work.
Click to expand...
Click to collapse
How is it going on the kltedv variant 7 months on? I'm asking because I also have a kltedv which I'd like to test.
Is it getting A12/12.1?
Build for klteduos
Got this running on a klte a few days ago... It was my first time flashing anything onto any phone, no issues. Odin to flash the recommended lineage recovery and adb to sideload the latest klte build of divest 18.1.
Re some things mentioned in the OP:
-I havent had issues with USB yet, tho all I've used it for is charging my thick 7800mah battery which is running as good as it was on stock MM if not better ie. haven't had to charge it much
-haven't tried to mount an SD card yet but will be feeling pinched for space if its not reliable. sooner or later
-not encrypted by default, but only took a minute to enable and its way quicker than stock MM encryption ever was
-the only things that seem laggy so far is 1. the default camera app, and 2. sometimes need to tap twice on a toggle in various settings to get it to flip. I havent tweaked much of anything yet tho or tried many apps
This beautiful old beast (first phone i got, 8 yrs ago) is back in service as muh daily driver
...gotta say I'm impressed with divest and happy to say buh bye to google!
Hallo,
who can give me support (Descriptons, links, etc.), installing divestos via Heimdall. My plattform is ubuntu.
Thank you very much
{
"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.
Kindle Fire HDX Notes:
- This is one of the few devices supported by DivestOS that is not -user and doesn't support encryption.
- This is one of the few devices supported by DivestOS that requires the use of TWRP
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-thor, https://divestos.org/index.php?page=devices&base=LineageOS#device-apollo
- 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#hdx-common
- 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_amazon_hdx-common, https://github.com/LineageOS/android_device_amazon_thor, https://github.com/LineageOS/android_device_amazon_apollo
- Kernel: https://github.com/LineageOS/android_kernel_amazon_hdx-common
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/..._Patchers/android_kernel_amazon_hdx-common.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-----
Thanks for your work
Nobody interested?
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
Click to expand...
Click to collapse
This puts me off trying.
i would try it but my recovery partition is to small says fastboot... so i can't? or can i flash it with twrp even it isn't supported?
scops said:
i would try it but my recovery partition is to small says fastboot... so i can't? or can i flash it with twrp even it isn't supported?
Click to expand...
Click to collapse
thor is sadly one of the few devices supported by DivestOS that *does* require TWRP.
DivestOS now runs on my Thor. Since the installation is different to other DivestOS-Installations, it should be explaied here more:
- No need for the DivestOS-Recovery; just use TWRP bundled with 1-Click-Unlock tool
- Place ROM on internal flash und install via TWRP (like LineageOS; normal wipe before install)
- Downgrade from LOS 16 without problems possible; tested
scops said:
DivestOS now runs on my Thor. Since the installation is different to other DivestOS-Installations, it should be explaied here more:
- No need for the DivestOS-Recovery; just use TWRP bundled with 1-Click-Unlock tool
- Place ROM on internal flash und install via TWRP (like LineageOS; normal wipe before install)
- Downgrade from LOS 16 without problems possible; tested
Click to expand...
Click to collapse
How to install on Thor? Mine says Fastboot when I press power and down button when boot up.
kkcheong said:
How to install on Thor? Mine says Fastboot when I press power and down button when boot up.
Click to expand...
Click to collapse
Try power + Vol up
scops said:
Try power + Vol
Click to expand...
Click to collapse
scops said:
Try power + Vol up
Click to expand...
Click to collapse
I lol'ed at myself. Anyway, so I got TWRP 3.0.2-0. I am wondering if I install this ROM, will I able to play Netflix? I know it doesn't support Widevine. But I just wonder.
So if I flash this ROM using TWRP and I don't like it, can I just restore it to my backup ROM?
kkcheong said:
I lol'ed at myself. Anyway, so I got TWRP 3.0.2-0. I am wondering if I install this ROM, will I able to play Netflix? I know it doesn't support Widevine. But I just wonder.
Click to expand...
Click to collapse
Sorry, i can't help you with netflix on Thor...
kkcheong said:
So if I flash this ROM using TWRP and I don't like it, can I just restore it to my backup ROM?
Click to expand...
Click to collapse
I haven't tryed but you could just reflash LOS 16 (...) if you want.
kkcheong said:
I lol'ed at myself. Anyway, so I got TWRP 3.0.2-0. I am wondering if I install this ROM, will I able to play Netflix? I know it doesn't support Widevine. But I just wonder.
Click to expand...
Click to collapse
Netflix will not work.
kkcheong said:
So if I flash this ROM using TWRP and I don't like it, can I just restore it to my backup ROM?
Click to expand...
Click to collapse
Yes, you can simply flash to another ROM.
Trying this Custom Rom out and it is very good. However not sure if it has anything to do with the rom but i cannot get Spotify to work, it just wont log in my account. Just says "Something went wrong, please try again later".
ushilives said:
Trying this Custom Rom out and it is very good. However not sure if it has anything to do with the rom but i cannot get Spotify to work, it just wont log in my account. Just says "Something went wrong, please try again later".
Click to expand...
Click to collapse
Spotify likely uses Widevine for DRM, which is removed in DivestOS.
SkewedZeppelin said:
Spotify likely uses Widevine for DRM, which is removed in DivestOS.
Click to expand...
Click to collapse
ok thanks
SkewedZeppelin said:
Spotify likely uses Widevine for DRM, which is removed in DivestOS.
Click to expand...
Click to collapse
Do you think there will be any future updates for this OS for this device? And is there a way to add WideVine back to device, if i were to do it myself? Juggling wether to use this OS or Lineage OS. I think this OS is a bit faster, will see if it charges quicker too.
ushilives said:
Do you think there will be any future updates for this OS for this device? And is there a way to add WideVine back to device, if i were to do it myself? Juggling wether to use this OS or Lineage OS. I think this OS is a bit faster, will see if it charges quicker too.
Click to expand...
Click to collapse
I have provided builds for this device every month since end of 2016. I fully plan to support this device (and others) as long as I can reasonably support the 14.1 branch.
Since TWRP is required in this case, you should in theory be able to extract the files from another ROM and adb push them into place:
Code:
vendor/lib/drm/libdrmwvmplugin.so
vendor/lib/mediadrm/libwvdrmengine.so
vendor/lib/libwvdrm_L3.so
vendor/lib/libwvm.so
vendor/lib/libWVStreamControlAPI_L3.so
SkewedZeppelin said:
I have provided builds for this device every month since end of 2016. I fully plan to support this device (and others) as long as I can reasonably support the 14.1 branch.
Since TWRP is required in this case, you should in theory be able to extract the files from another ROM and adb push them into place:
Code:
vendor/lib/drm/libdrmwvmplugin.so
vendor/lib/mediadrm/libwvdrmengine.so
vendor/lib/libwvdrm_L3.so
vendor/lib/libwvm.so
vendor/lib/libWVStreamControlAPI_L3.so
Click to expand...
Click to collapse
Thanks dude. Didn't realise you have supported this device for so many years, very nice secure ROM.
Installed DivestOS again. Noticed it boots up alot faster than LineageOS 16, 28 secs compared to 57 secs for LineageOS 16. Also less memory usage. And noticed it got an update few days ago!
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. You can also view the Changelog for a full list of changes & features.
Instructions:
Install LineageOS on pdx203 | LineageOS Wiki
wiki.lineageos.org
Downloads:
https://download.lineageos.org/pdx203
Known Issues:You tell me
Device Trees:Device Tree: https://github.com/LineageOS/android_device_sony_pdx203
Common Tree: https://github.com/LineageOS/android_device_sony_sm8250-common
Kernel Source: https://github.com/LineageOS/android_kernel_sony_sm8250
Credits:Huge thanks to:
Luk1337 and Sjllls for their help on debugging and fixing issues and device trees as references
Changelog:
Code:
- 2022-10-13
- So many things, see commits for details :)
- 2022-08-08
- Added High Brightness Mode (HBM) in livedisplay
- Added High Touch Reporting Rate (120Hz) switch
- 2022-08-02
- Fixed color settings in the Settings application (Thanks to cramfs28)
- Note that toggling "Creator Mode" in extra settings application will change the color setting
- Fixed an issue related to call microphone on T-Mobile sim cards
- Fixed echo cancellation in loudspeaker mode when in call
- 2022-07-27
- EXPERIMENTAL BUILD: May contain some extra functionalities that does not appear in final build
- Added extra setting application
- Added H.S. mode from Sony stock
- Added creator display mode
- Change default network type to 5G
- 2022-07-21
- **IMPORTANT:** You will need to flash the recovery.img BEFORE you flash the ROM
- Some ROM props changed, need to update the recovery
- Added double tap to wake
- Enabled picture enhancement feature in livedisplay
- Fixed dual-SIM detection
- Enabled touchscreen in recovery
- Check other updates in commit logs
- 2022-07-18
- Kernel
- Imported kernel source code from sony 58.2.A.7.55
- Merge CAF Tag LA.UM.9.12.r1-14300-SMxx50.0
- Enabled wireguard driver (Need testing)
- Initial merging of linux-stable (to 4.19.158)
- Update files for 58.2.A.8.92
- Check other updates in commit logs
- 2022-06-29
- Fixed microphone too low problem in some applications
- Fixed an issue causing the usb selection menu to grey out
Nice work! Thank you!
Should I "fastboot set_active a" before"fastboot flash boot boot.img"?
19920129 said:
Nice work! Thank you!
Should I "fastboot set_active a" before"fastboot flash boot boot.img"?
Click to expand...
Click to collapse
You can set the slot if you want, but honestly I don't think it is necessary.
clfbbn said:
You can set the slot if you want, but honestly I don't think it is necessary.
Click to expand...
Click to collapse
Hi，I just see two 20220609 roms，which one can I flash，any bugs？
19920129 said:
Hi，I just see two 20220609 roms，which one can I flash，any bugs？
Click to expand...
Click to collapse
There is a file with a suffix "_new", try that one. Flash it using lineage recovery.
Bug: Call Volume Change - Does not work for now
I think I have fixed other bugs.
Well I have found a significant bug that's going to prevent daily use. In-call microphone doesn't work at all, even on speakerphone. Using the recorder app, I can pick up audio but it is very very quiet. Everything else seems to work well so far, though, besides the in-call audio fixed max volume.
I am on the XQ-AT51, and have flashed MindTheGapps provided by LineageOS
citysurrounded said:
Well I have found a significant bug that's going to prevent daily use. In-call microphone doesn't work at all, even on speakerphone. Using the recorder app, I can pick up audio but it is very very quiet. Everything else seems to work well so far, though, besides the in-call audio fixed max volume.
I am on the XQ-AT51, and have flashed MindTheGapps provided by LineageOS
Click to expand...
Click to collapse
Are you using the latest build? I think I have fixed issues regarding the call volume.
The microphone in the recorder app is quite, I can confirm it, though.
I used 20220922 rom，but I can't use usb for transfer，only can charge。。。。
19920129 said:
I used 20220922 rom，but I can't use usb for transfer，only can charge。。。。
Click to expand...
Click to collapse
This is a known issue. Will be fixed along with the microphone problem.
You can try adb push as a workaround for now
Just installed LOS 19.1 on my Xperia XZ1 Compact, and really miss the WireGuard kernel feature on my Xperia 1 II, where I can have multiple tunnels active at the same time. Do you have any plans to add the WireGuard kernel module in a future release?
Anyways, great release! I have not personally encountered any bugs/issues yet. I use microG Installer Revived (with whew-inc's FakeGApps fork and, LSPosed Framework), Universal SafetyNet Fix, and MagiskHide Props Config with the bundled Xperia 5 II build fingerprint to fully pass a SafetyNet Attestation Check.
nixigaj said:
Just installed LOS 19.1 on my Xperia XZ1 Compact, and really miss the WireGuard kernel feature on my Xperia 1 II, where I can have multiple tunnels active at the same time. Do you have any plans to add the WireGuard kernel module in a future release?
Anyways, great release! I have not personally encountered any bugs/issues yet. I use microG Installer Revived (with whew-inc's FakeGApps fork and, LSPosed Framework), Universal SafetyNet Fix, and MagiskHide Props Config with the bundled Xperia 5 II build fingerprint to fully pass a SafetyNet Attestation Check.
Click to expand...
Click to collapse
Thanks for the report. Since I haven't used wireguard before, can you detail the information that can show whether this module is present in kernel or not?
clfbbn said:
Thanks for the report. Since I haven't used wireguard before, can you detail the information that can show whether this module is present in kernel or not?
Click to expand...
Click to collapse
When you enter settings in the WireGuard app, it will ask for root access to enable more features via the kernel module. Also if you run ls /sys/module/ | grep wireguard in a root terminal it will return wireguard.
I am not very well versed with Android kernel development but it seems as though the latest android-4.19-stable merge into the sony_sm8250 kernel tree happened before Google merged WireGuard into the android-4.19-stable kernel tree, and the sony_sm8250 kernel tree does not seem to have been updated since; thus /drivers/net/wireguard/ is missing, and gki_defconfig does not contain CONFIG_WIREGUARD=y.
nixigaj said:
When you enter settings in the WireGuard app, it will ask for root access to enable more features via the kernel module. Also if you run ls /sys/module/ | grep wireguard in a root terminal it will return wireguard.
I am not very well versed with Android kernel development but it seems as though the latest android-4.19-stable merge into the sony_sm8250 kernel tree happened before Google merged WireGuard into the android-4.19-stable kernel tree, and the sony_sm8250 kernel tree does not seem to have been updated since; thus /drivers/net/wireguard/ is missing, and gki_defconfig does not contain CONFIG_WIREGUARD=y.
Click to expand...
Click to collapse
The driver is there, see https://github.com/hellobbn/android_kernel_sony_sm8250/tree/lineage-19.1_new/drivers/net/wireguard
I have enabled the wireguard in my latest build, and you can try that out.
That said, not all upstream changes have been backported.
clfbbn said:
The driver is there, see https://github.com/hellobbn/android_kernel_sony_sm8250/tree/lineage-19.1_new/drivers/net/wireguard
I have enabled the wireguard in my latest build, and you can try that out.
That said, not all upstream changes have been backported.
Click to expand...
Click to collapse
Ignorant me did not think about there being multiple branches.
With the latest build the WireGuard app asks for root and all the features of the kernel module backend seem to work.
Dear dev, I have flashed lineage-os-19.1-2022-0718, but dual sim not work
RealNoobKanger said:
Dear dev, I have flashed lineage-os-19.1-2022-0718, but dual sim not work
Click to expand...
Click to collapse
Thanks, I can confirm this problem. Will look into it.
EDIT: Could be expected behavior if you first boot the rom with single SIM and then insert the other card.
Temp Solution (After each boot):
1. Enable Root Debugging in Developer Options
2. Enter adb shell:
Code:
adb root
adb shell
3. Type the following command:
Code:
/odm/bin/sony_ext_uim_ctrl
EDIT2: The next release will fix this problem.
clfbbn said:
Thanks, I can confirm this problem. Will look into it.
EDIT: Could be expected behavior if you first boot the rom with single SIM and then insert the other card.
Temp Solution (After each boot):
1. Enable Root Debugging in Developer Options
2. Enter adb shell:
Code:
adb root
adb shell
3. Type the following command:
Code:
/odm/bin/sony_ext_uim_ctrl
Click to expand...
Click to collapse
thanks for your reply bro, should we set 1 to the /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type ?
I tested it on your latest lineage os 19.1 build, dual sim works well now. thank you !
RealNoobKanger said:
thanks for your reply bro, did you means write 1 to the /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type ?
I tested it on your latest build, dual sim works well now, should we add to the init to set " /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" when device use dual sim (aka. dsds)
Click to expand...
Click to collapse
I set the "/sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" to 1 on my device with your lineage os build, ril works well not only dual sim but single sim (ss). should we set this value to "1" defaultly ?
No matter what, thank you from the bottom of my heart for your good rom, device tree and kernel source !
RealNoobKanger said:
I set the "/sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" to 1 on my device with your lineage os build, ril works well not only dual sim but single sim (ss). should we set this value to "1" defaultly ?
No matter what, thank you from the bottom of my heart for your good rom, device tree and kernel source !
Click to expand...
Click to collapse
Maybe this is related to SD card / SIM card detection, so I am not sure whether SD card will work properly if we set this always to be 1.
The exec file "/odm/bin/sony_ext_uim_ctrl" should take care of this. I forgot to label this exec file so it does not get executed when system boots, which causes the second sim not being detected. I have corrected that mistake now. If you are interested: https://github.com/hellobbn/android...mmit/68b69ac284cf3e4abe5464a2a70f37701581060f
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/instantnoodlep
Downloads :
https://download.lineageos.org/instantnoodlep
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8250
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thank for the new release!
Just flashed it. No issues so far.
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
desosav said:
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
Click to expand...
Click to collapse
It's normal:
[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro. This message was removed on OOS 12 which was one great thing by OP...
forum.xda-developers.com
desosav said:
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
Click to expand...
Click to collapse
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
JustinChase said:
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
Click to expand...
Click to collapse
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
No issues with following the lineage os version upgrade procedure to keep from needing to format data? The upgrade procedure didn't have about needing oos13 firmware beforehand, so I wasn't sure if it'd make a difference.
-update-
No issues yet after following the upgrade procedure without flashing oos13 stock fw first.
I still have some weird issue where it makes me have to sign in to the T-Mobile network. I think it's because I had a Verizon sim in sim slot 2 at one point.. it'll probably require a network settings reset to fix..
Is the 48MP sensor on the camera still locked? Just wondering considering the changes with the camera app and API with LOS 20.
d3viou5 said:
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
Click to expand...
Click to collapse
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
miramax001 said:
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Click to expand...
Click to collapse
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
mattgyver said:
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
Click to expand...
Click to collapse
Thanks @mattgyver
The problem WAS the WORK profile (with SHELTER).
I had to remove my WORK PROFILE (from SETTINGS->ACCOUNT)
And then, sideload magisk.apk (renamed as magisk.zip) and now I'm rooted again.
ThX!
roaringcrown said:
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
Click to expand...
Click to collapse
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Kuronosu said:
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Click to expand...
Click to collapse
yes, just follow the official guide
Upgrade LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
Bash:
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
andro[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
Any idea why this is happening?
sToRm1nG said:
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
{code}
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
{code}
Any idea why this is happening?
Click to expand...
Click to collapse
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
LuK1337 said:
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
Click to expand...
Click to collapse
Yeah, you're right... I was building user isntead of userdebug.
Thank you so so much for this! ♥ It works like a charm and it's so so much better than OxygenOS 13 (I can minimize notifications omg!!!1!).
The only thing I personally am missing, is the classic LOS 18 style quick shortcuts in the pull-down notification menu. I always used 1 row with 6 circles, but since LOS 19 it changed to 2 rows with only 4 large shortcuts. But oh well, I guess you can't have everything!
Thank you for maintaining this device @LuK1337 !
@LuK1337
Thank you for your great work.
Not only for your work for this great Oneplus 8 Pro device, but also for other devices before!
You are really one of the most important and best device maintainers.
haxorinjector said:
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
Click to expand...
Click to collapse
TWRP is only available for A11 and lower. It does not work on A12 or A13.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
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
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
[*]Gapps Included
[*]Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
Flash MAY Firmware
reboot bootloader
fastboot -w update rom_name.zip
Update installation:
fastboot update rom_name.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_pantah
Download:
ROM: Download
Changelog:
Known issues:
you tell me
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Changelog:
==== 05 May, 2023 =====
=== Rom Source ===
- Initial crDroid 9.5 release
- Updated to May 2023 security patches (android-13.0.0_r43)
- Added pixel style lockscreen weather based OmniJaws
- opengl: fix resource leak when dlsym failed
- Switch latest clang to 17.0.1
- Updated themed icons
- Updated translations
- Allow pause/suspend app feature with parallel space
- Settings: Expose radio info (*#*#4636#*#*)
- Added QS Header Image option
- Wallpaperpicker: fix overlapping when scrolling
- WallpaperPicker2: Remove the use of smaller images for thumbnails
- Updated libvpx, bionic
- Updated translations
- Add a toggle to force LTE_CA
- Added back 2 button navigation
- Fixed/Reworked switch to unlink ringtone and notifications volume
- Fixed process can't start because of mPendingStart is true problem
- Fixed SystemUI restart due to network traffic meter
- NetworkTraffic: Simplify stats calc to prevent issues
- PixelPropsUtils: Spoof user build
- Settings: Show memory usage in app info
- SystemUI: Rework dismiss all view in QS
- SystemUI: Handle more exceptions for firewall
- Prevent crash with pin protected user and taskview
- Fix hang when dumping local window
- Updated Webview to 112.0.5615.136
- Updated bionic, lmkd, sqlite
- Updated translations
=== Device ===
May Security Patch
New Kernel: MadKali thanks @Duhjoker
Removed Scrolling Tweaks/Fix Lags
===== 27 April, 2023 =====
-Resync Rom Source
-Qs Header Images
-Fix Safetynet OOTB
-Fixed NGA
-Other Tweaks and Optimizations
another one just in case
I've been waiting for this release to try something other than stock. Thank you for your hard work and this variant! Much appreciated!
Coming from your last unofficial version, is it necessary to install google april factory version first or can I just update crdroid rom (clean or dirty flash?)
Thanks in avance.
Bestiole222 said:
Coming from your last unofficial version, is it necessary to install google april factory version first or can I just update crdroid rom (clean or dirty flash?)
Thanks in avance.
Click to expand...
Click to collapse
Yes you need to install April firmware
Do you plan to release a vanilla version without gapps?
gap30 said:
Do you plan to release a vanilla version without gapps?
Click to expand...
Click to collapse
No it's a pixel so that's why I include the gapps
omariscal1019 said:
Yes you need to install April firmware
Click to expand...
Click to collapse
Ok, there are two april firmware panther-tq2a.230405.003.e1-factory-ae8e7da5.zip and panther-t3b3.230413.003-factory-14b0dd69.zip the second appears after your rom it's ok for you or I must flash the first one. Which kernel is included with your rom ,Kirisakura _ Raviantah if yes which version?.
Bestiole222 said:
Ok, there are two april firmware panther-tq2a.230405.003.e1-factory-ae8e7da5.zip and panther-t3b3.230413.003-factory-14b0dd69.zip the second appears after your rom it's ok for you or I must flash the first one. Which kernel is included with your rom ,Kirisakura _ Raviantah if yes which version?.
Click to expand...
Click to collapse
The OP shows the kernel.
rspkt said:
The OP shows the kernel.
Click to expand...
Click to collapse
Thanks
Noticed something strange with this build. When I attempted to enable Zygisk on Magisk stable it would immediately fail to boot. I could only get it to work by using the latest canary. Flashed after clean-flashing April to both slots.
stompysan said:
Noticed something strange with this build. When I attempted to enable Zygisk on Magisk stable it would immediately fail to boot. I could only get it to work by using the latest canary. Flashed after clean-flashing April to both slots.
Click to expand...
Click to collapse
No issue here.
Tried replicating on 26.1 several times, works without issues for me.
I've used crDroid on my Mix 2 and I loved it. I'll be trying this for sure.
Question: I have a JP version of Pixel 7, that have Sony Felicia chip (for transport and payments). Will that still work with this Rom? I'm not talking about 'custom rom'/'root' checks, I'm talking about rom compatibility with the japanese version hardware. Thank you.,
new update
04/27
Finally installed the ROM and rooted with Magisk v26.1 by patching the init_boot file in the ROM .zip and flashing via fastboot. No issues with either the install or rooting. Restored the majority of my apps with Swift Backup and everything seems good to go so far.
First time using this ROM and I'm pretty impressed at the amount of customization and features it has. Reminds me a lot of the customization found in ROMs like Resurrection Remix which was a favorite ROM of mine on an earlier model Pixel phone. Only complaint is the amount of pre-installed apps that I could do without but just disabled/froze them via Titanium Backup's freeze feature. I do love that it comes pre-packaged with Kirisakura Raviantah kernel though since it's my favorite to-date and was planning on installing it anyway.
Thanks for the hard work @omariscal1019 and hope this becomes official eventually.
EDIT: One question... what is the best method for updating the ROM from the 4/19 to 4/27 build? Thanks in advance.
EDIT #2: Nevermind. Just booted into the bootloader and flash with 'fastboot update crdroid_panther_04_27.zip' without the -w flag to preserve my data and update went flawlessly as well. Thanks again.
rspkt said:
Finally installed the ROM and rooted with Magisk v26.1 by patching the init_boot file in the ROM .zip and flashing via fastboot. No issues with either the install or rooting. Restored the majority of my apps with Swift Backup and everything seems good to go so far.
First time using this ROM and I'm pretty impressed at the amount of customization and features it has. Reminds me a lot of the customization found in ROMs like Resurrection Remix which was
Click to expand...
Click to collapse
Oh, nice to know that the kernel already include
My holiday has begun, time to flash it
Just finished install rom and root with magisk
May I ask, when I reboot phone, it always show a notice of your phone is in unsafe state, and I need to manually press power button to continue. It only for me or it's normal when using rooted pixel?
hungragezone said:
Just finished install rom and root with magisk
May I ask, when I reboot phone, it always show a notice of your phone is in unsafe state, and I need to manually press power button to continue. It only for me or it's normal when using rooted pixel?
Click to expand...
Click to collapse
This screen appears when bootloader is unlocked, it's normal.
hungragezone said:
Just finished install rom and root with magisk
May I ask, when I reboot phone, it always show a notice of your phone is in unsafe state, and I need to manually press power button to continue. It only for me or it's normal when using rooted pixel?
Click to expand...
Click to collapse
You don't technically "need to manually press power button to continue" as it should after a few moments continue the boot process after a short delay regardless. If you want it to boot a few seconds faster, then you can hit the power button twice and essentially speed up this notification dismissal and resume the boot process. Once your phone is unlocked (rooting is not the reason why) you will always see this message during the boot process and it's 100% normal as @Bestiole222 already stated.