Develop Bugs

[EOL][KERNEL][G930F]Nethunter for S7 LineageOS 14.1

[End Of Life]Nethunter Kernel for Samsung Galaxy S7 (SM-G930F/FD) LineageOS 14.1 ​
Code:
I am not responsible for bricked devices.
If you going to flash it, you accepted it.
Of course your warranty is void after flashing LineageOS 14.1
This kernel is only for herolte . If you have Edge go here
FEATURES:
BadUSB
HID gadget keyboard/mouse (with possibility to temporarily disable)
DriveDroid
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
Ethernet
F2FS
Bluetooth HCI USB support
RTL-SDR DVB support
Nexmon firmware bcm4359 monitor mode + packet injection, packet capture(partially)
Nexmon firmware bcm4359 native monitor mode, no packet injection, buggy
Extra:
Boeffla wakelock blocker v1.10
Wireguard
Download:
Latest version G930F here.
Installation:
Here isn't AiO package yet...
1. TWRP Backup your ROM
2. Flash G930F_NethunterKernel_LineageOS14.1_*.img
3. Flash latest Magisk (Recommend 18.1+ version, 18.0 could make frezzes)
4. Install busybox can be one from Magisk repository
5. Install Magisk Nethunter module from repository
6. Install kalifs-armhf-*.tar.xz by Nethunter manager
7. Extract Nethunter_Binaries.7z and binaries to folders:
Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
hid-keyboard binary: system/xbin/ and give permissions to it rwxr-xr-x
8. Reboot
Now you have Nethunter on your LineageOS 14.1.
EXTRA:
1. If you want to try monitor mode with your bcm4359 FIRST MAKE BACKUP your firmware in /system/etc/wifi/bcmdhd_sta.bin_c0 than you can install Nexmon_Binaries.7z like Nethunter_Binaries.7z. Modded firmware have troubles to connect to wifi network so use it only when you want monitor mode.
2.In Utilities.7z are wifi testing tools binaries like aircrack-ng compiled from source of nexmon
Screens:
{
"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"
}
XDA:DevDB Information
[KERNEL] [G930F] Nethunter for LineageOS 14.1, Kernel for the Samsung Galaxy S7
Contributors
Wirusx
Source Code: https://github.com/Svirusx/NetHunter-s7-kernel-LineageOS14.1
Kernel Special Features:
Version Information
Status: Beta
Created 2019-01-11
Last Updated 2019-06-24

CHANGELOG
2019-06.24 - v1.5
added wireguard
added rtl8187 patch
added possibility to disable hid patch
added bluetooth carwhisperer fix
added boeffla wakeblocker
updated nethunter_defconfig
2019-02-25 - v1.4
Added missing drivers like SUNRPC, NFS v4 etc.
Removed unnecessary drivers.
2019-01-15 - v1.3
Added support G935F
2019-01-12 - v1.2
Added some Nethunter drivers:
System V IPC
Netfilter
TCP Cubic
Bridge
CD-ROM/DVD Filesystems
2019-01-11 - v1.1
Added:
F2FS partition support
Bluetooth HCI USB support
RTL-SDR DVB support
2019-01-10 - v1.0
Initial release
Added:
HID gadget keyboard/mouse support
DriveDroid support
USB WiFi, mac80211 (Monitor mode + packet injection)
partially working nexmon firmware

Reserved

THank you!

Can you recommend rom for this kernel? With link.

_Danil_ said:
Can you recommend rom for this kernel? With link.
Click to expand...
Click to collapse
I made this kernel from source of Official Nougat LineageOS 14.1 for Galaxy s7 so this ROM is the best.
Download from official website of LineageOS

How to use airmon-ng monitoring? I have error on s7edge
[email protected]:~# airmon-ng start wlan0
Found phy0 with no interfaces assigned, would you like to assign one to it? [y/n] y
ERROR adding monitor mode interface: command failed: Operation not supported (-95)
Found 1 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to run 'airmon-ng check kill'
PID Name
14654 wpa_supplicant
PHY Interface Driver Chipset
phy0 wlan0 ?????? non-mac80211 device? (report this!)
ERROR adding monitor mode interface: command failed: No such device (-19)
[email protected]:~#

AbayefD said:
How to use airmon-ng monitoring? I have error on s7edge
[email protected]:~# airmon-ng start wlan0
Found phy0 with no interfaces assigned, would you like to assign one to it? [y/n] y
ERROR adding monitor mode interface: command failed: Operation not supported (-95)
Found 1 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to run 'airmon-ng check kill'
PID Name
14654 wpa_supplicant
PHY Interface Driver Chipset
phy0 wlan0 ?????? non-mac80211 device? (report this!)
ERROR adding monitor mode interface: command failed: No such device (-19)
[email protected]:~#
Click to expand...
Click to collapse
airmon-ng is working only for usb wifi adapters.
For wlan0 you need first have wifi off.
example commands:
ifconfig wlan0 up
nexutil -m2
LD_PRELOAD=libnexmon.so airodump-ng wlan0
For every commands you need to use LD_PRELOAD
(all in android terminal not in chroot)
Nexmon version of monitor mode cut every caputed packet... but packet injection works.
I implemented wlan0 monitor mode for test it's buggy. If you want normal monitor mode than you need usb wifi dongle and you can start with airmon-ng in chroot.

Svirusx said:
airmon-ng is working only for usb wifi adapters.
For wlan0 you need first have wifi off.
example commands:
ifconfig wlan0 up
nexutil -m2
.
Click to expand...
Click to collapse
nexutil command not found.
How to install metapackages in chroot manager? I have this in terminal (screenshot)

AbayefD said:
nexutil command not found.
How to install metapackages in chroot manager? I have this in terminal (screenshot)
Click to expand...
Click to collapse
nexutil you need to copy to xbin in system.
First you need to apt-get update
metapackages: apt-get install kali-linux-all or another one.

Svirusx said:
nexutil you need to copy to xbin in system.
First you need to apt-get update
metapackages: apt-get install kali-linux-all or another one.
Click to expand...
Click to collapse
Where download nexutil?

Where download nexutil? And look screenshot pls

Where download nexutil

AbayefD said:
Where download nexutil? And look screenshot pls
Click to expand...
Click to collapse
nexutil is in packages which i added to first release of this kernel and wrote info over it in EXTRA. nexutil is in Nexmon_Binaries.7z and Nexmon_Binaries.7z is in first release on github uploaded.
I saw your screen and wrote what you need to do without apt-get update you can't install anything because of old version and you need to use command first
wget -q -O - https://archive.kali.org/archive-key.asc | apt-key add
than apt-get update.
For most error with chroot you can easy find fix in google problem with update and installing metapackages isn't only on s7.
Try make less spam

Ohohohoho

AbayefD said:
Ohohohoho
Click to expand...
Click to collapse
hmm maybe try uninstall chroot and install full kalifs
than use commands
wget -q -O - https://archive.kali.org/archive-key.asc | apt-key add
apt-get update
apt-get upgrade
Anyway check your interne memory, chroot take a lot of space.

Svirusx said:
hmm maybe try uninstall chroot and install full kalifs
than use commands
wget -q -O - https://archive.kali.org/archive-key.asc | apt-key add
apt-get update
apt-get upgrade
Anyway check your interne memory, chroot take a lot of space.
Click to expand...
Click to collapse
How much memory needed? And for nexutil I need to move only nexutil file to xbin folder? Or need move all files from Nexmon archive

is Nethunter chroot required to use nexutil?
I don't have Nethunter installed yet and trying to run any nexutil command, but getting error "__nex_driver_io: error "
Do I need to run nexutil with Nethunter chroot?

zedfour said:
is Nethunter chroot required to use nexutil?
I don't have Nethunter installed yet and trying to run any nexutil command, but getting error "__nex_driver_io: error "
Do I need to run nexutil with Nethunter chroot?
Click to expand...
Click to collapse
No, Nethunter chroot isn't required. Nexutil is experimental added to my Nethunter kernel.
It's work without Nethunter.
try
WiFi OFF
ifconfig wlan0 up
nexutil -m2
LD_PRELOAD=libnexmon.so airodump-ng wlan0

Svirusx said:
No, Nethunter chroot isn't required. Nexutil is experimental added to my Nethunter kernel.
It's work without Nethunter.
try
WiFi OFF
ifconfig wlan0 up
nexutil -m2
LD_PRELOAD=libnexmon.so airodump-ng wlan0
Click to expand...
Click to collapse
Ahh, I didn't have wifi toggled off in the android settings. After toggling it off, it worked.
I noticed that airodump isn't hopping channels by default -- it stays on ch12. I can manually choose the channel with --channel in the command tho. Is this normal for nexmon firmware on s7?

[ROM] [Android 11] [taimen] ArrowOS 11.0 | OFFICIAL

{
"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"
}
ArrowOS​
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ReallySnow/android_kernel_google_wahoo
Device Source: https://github.com/ReallySnow/android_device_google_taimen
Common Source: https://github.com/ReallySnow/android_device_google_wahoo
ROM OS Version: Android 11
ROM Kernel: Linux 4.4.x
ROM Firmware: built-in
Version Information
Status: Stable
Created 2021-03-26
Last Updated 2021-04-25

ReallySnow said:
ArrowOS​
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
Click here to Download
Note: No GAPPS version is built
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ReallySnow/android_kernel_google_wahoo
Device Source: https://github.com/ReallySnow/android_device_google_taimen
Common Source: https://github.com/ReallySnow/android_device_google_wahoo
ROM OS Version: Android 11
ROM Kernel: Linux 4.4.x
ROM Firmware: built-in
Version Information
Status: Stable
Created 2021-03-26
Last Updated 2021-03-26
Click to expand...
Click to collapse
Hi. What features are include? Thank you

irmas5 said:
Hi. What features are include? Thank you
Click to expand...
Click to collapse
You sometimes need to visit the links in the OP
What is ArrowOS? – ArrowOS Blog

Same issue for me as far too many ROMs on here lately, errors out when installing NikGapps (full) with config file
"Installation Failed! Looks like Storage space is full!"
Even though the script finds more than enough space to install it....weird
Oh well, back to Proton or Pixel Experience which dont have that issue....its just me i refuse to use a small G-Apps package than ive used forever on every other ROM...

Figured it out

73sydney said:
You sometimes need to visit the links in the OP
What is ArrowOS? – ArrowOS Blog
Click to expand...
Click to collapse
You sometimes need to visit the links in the OP of nikgapps, and edit configuration file:
# NikGapps configuration file
# What is nikgapps.config?
# nikgapps.config is a configuration file which allows you to configure your installation the way you like.
# You can choose the partition to install and You can also skip any Package that you don't want to be part of your installation
# Where can I find nikgapps.config?
# nikgapps.config is placed in /sdcard/NikGapps folder automatically after first install with all the packages enabled for installation
# If you want to configure the installation with your very first installation, extract nikgapps.config from the gapps zip and place it to /sdcard/NikGapps folder
# NikGapps packages recognizes nikgapps.config from other places as well, following is the precedence of the location
# 1. "/tmp/nikgapps.config"
# 2. "$ZIPDIR/nikgapps.config" where ZIPDIR is the directory NikGapps package is located
# 3. "/sdcard1/nikgapps.config"
# 4. "/sdcard1/NikGapps/nikgapps.config"
# 5. "/sdcard/nikgapps.config"
# 6. "/sdcard/NikGapps/nikgapps.config"
# How to configure nikgapps.config?
# Edit the file and set 0,1,2,-1 against the package that you want to configure, save the file, flash the gapps.
# NikGapps installer recognizes 4 config values
# -> 0 (Skip the package)
# -> 1 (install the package and delete corresponding aosp app)
# -> 2 (install the package and do not delete corresponding aosp app)
# -> -1 (uninstalls the package if mode=uninstall)
# For e.g. if you want to skip GoogleContacts during the installation, the config should read GoogleContacts=0.
# if you want to install GoogleContacts and remove Aosp Contacts, config should read GoogleContacts=1.
# if you want to install GoogleContacts and keep Aosp Contacts, config should read GoogleContacts=2.
# if you want to uninstall GoogleContacts, config should read GoogleContacts=-1 and mode=uninstall

irmas5 said:
You sometimes need to visit the links in the OP of nikgapps, and edit configuration file:
# NikGapps configuration file
# What is nikgapps.config?
# nikgapps.config is a configuration file which allows you to configure your installation the way you like.
# You can choose the partition to install and You can also skip any Package that you don't want to be part of your installation
# Where can I find nikgapps.config?
# nikgapps.config is placed in /sdcard/NikGapps folder automatically after first install with all the packages enabled for installation
# If you want to configure the installation with your very first installation, extract nikgapps.config from the gapps zip and place it to /sdcard/NikGapps folder
# NikGapps packages recognizes nikgapps.config from other places as well, following is the precedence of the location
# 1. "/tmp/nikgapps.config"
# 2. "$ZIPDIR/nikgapps.config" where ZIPDIR is the directory NikGapps package is located
# 3. "/sdcard1/nikgapps.config"
# 4. "/sdcard1/NikGapps/nikgapps.config"
# 5. "/sdcard/nikgapps.config"
# 6. "/sdcard/NikGapps/nikgapps.config"
# How to configure nikgapps.config?
# Edit the file and set 0,1,2,-1 against the package that you want to configure, save the file, flash the gapps.
# NikGapps installer recognizes 4 config values
# -> 0 (Skip the package)
# -> 1 (install the package and delete corresponding aosp app)
# -> 2 (install the package and do not delete corresponding aosp app)
# -> -1 (uninstalls the package if mode=uninstall)
# For e.g. if you want to skip GoogleContacts during the installation, the config should read GoogleContacts=0.
# if you want to install GoogleContacts and remove Aosp Contacts, config should read GoogleContacts=1.
# if you want to install GoogleContacts and keep Aosp Contacts, config should read GoogleContacts=2.
# if you want to uninstall GoogleContacts, config should read GoogleContacts=-1 and mode=uninstall
Click to expand...
Click to collapse
Not sure why youre quoting me?

73sydney said:
Not sure why youre quoting me?
Click to expand...
Click to collapse
73sydney​Senior Member​
Mar 26, 2021 at 4:44 PM
Add bookmark
#4
Same issue for me as far too many ROMs on here lately, errors out when installing NikGapps (full) with config file
"Installation Failed! Looks like Storage space is full!"
Even though the script finds more than enough space to install it....weird
Oh well, back to Proton or Pixel Experience which dont have that issue....its just me i refuse to use a small G-Apps package than ive used forever on every other ROM...
Last edited: Mar 26, 2021
My Current Device: Google Pixel 2 XL
My Current ROM: PixelExperience 11 Plus Edition
Wearables: Samsung Galaxy Active 2 (Working BP/ECG and Samsung Pay) and Samsung Galaxy Buds+
How to edit your gps.conf file for best GPS - My Magisk method for Google Pay SQLite Fix (Tested On P/Q/R) - Migrate, the Free ROM Backup App - Apps/Modules/Tweaks I Use On Q/R - Easy payload.bin dumper tool for Windows x64 (No Python install needed)

irmas5 said:
73sydney​Senior Member​
Mar 26, 2021 at 4:44 PM
Add bookmark
#4
Same issue for me as far too many ROMs on here lately, errors out when installing NikGapps (full) with config file
"Installation Failed! Looks like Storage space is full!"
Even though the script finds more than enough space to install it....weird
Oh well, back to Proton or Pixel Experience which dont have that issue....its just me i refuse to use a small G-Apps package than ive used forever on every other ROM...
Last edited: Mar 26, 2021
My Current Device: Google Pixel 2 XL
My Current ROM: PixelExperience 11 Plus Edition
Wearables: Samsung Galaxy Active 2 (Working BP/ECG and Samsung Pay) and Samsung Galaxy Buds+
How to edit your gps.conf file for best GPS - My Magisk method for Google Pay SQLite Fix (Tested On P/Q/R) - Migrate, the Free ROM Backup App - Apps/Modules/Tweaks I Use On Q/R - Easy payload.bin dumper tool for Windows x64 (No Python install needed)
Click to expand...
Click to collapse
Still failing to see why youre quoting me...sorry

非常流畅,比其他的aosp系统优化的要好！

我是十七 said:
非常流畅,比其他的aosp系统优化的要好！
Click to expand...
Click to collapse
did you manage to run Alipay mini programs?

Aether060 said:
您设法运行支付宝迷你程序了吗？
Aether060 said:
您设法运行支付宝迷你程序了吗？
Click to expand...
Click to collapse
Yes, it works perfectly and has a face lock
Click to expand...
Click to collapse

"Smart charging" result in settings search leads to nowhere.
"What to do" section is empty.
Just a couple of bugs I noticed. Else, the ROM is very nice. Kudos to the dev.

Sid2499 said:
"Smart charging" result in settings search leads to nowhere.
"What to do" section is empty.
Just a couple of bugs I noticed. Else, the ROM is very nice. Kudos to the dev.
Click to expand...
Click to collapse
I know, I will add it in the next version

Anyone else getting a crash when going to enable Wi-Fi Calling? This is on the gapps build
Edit: Logcat - https://drive.google.com/file/d/1-CIf8gXQbiFtyVFlH0voZa7UiaKjnBvH/view?usp=sharing

@ReallySnow
The 2016 pixel xml needs to be removed from /system/etc/sysconfig to allow working of unlimited Google Photos upload in our Taimen. Hoping its taken care of in the next build to help the novice users.
Phone feels very lite in ArrowOS, tried it first time and feels nice overall.

palimatix said:
@ReallySnow
The 2016 pixel xml needs to be removed from /system/etc/sysconfig to allow working of unlimited Google Photos upload in our Taimen. Hoping its taken care of in the next build to help the novice users.
Phone feels very lite in ArrowOS, tried it first time and feels nice overall.
Click to expand...
Click to collapse
Has been deleted, the next version will take effect.

13 June OTA update available now.

The latest version, found QQ flash back problem, hope to solve the next! thank you

Today's new weekly OTA update is live.
Walleye folks.. officially available for you

[ROM] DivestOS 20.0 for walleye

{
"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.
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-walleye
- 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#walleye
- 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_google_muskie, https://github.com/LineageOS/android_device_google_wahoo
- Kernel: https://github.com/LineageOS/android_kernel_google_wahoo
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...1/CVE_Patchers/android_kernel_google_wahoo.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 DivestOS and support of the Pixel2 walleye.
I had some confusion installing it before I succeeded.
Here are the generic instructions from the DivestOS website: https://divestos.org/index.php?page=bootloader
I copy pasted the instructions below and left only the instructions specific to walleye plus a few steps I took.
Here are the steps from those instructions which I used (I removed unnecessary steps for walleye)
Enable 'Allow OEM unlocking' under 'Developer options' in Settings if available
Reboot to the bootloader via key combination or $ adb reboot bootloader
$ fastboot flashing unlock
$ fastboot update divested-version-date-dos-device-fastboot.zip
Be ready to hold down volume down button so reboot (after flashing from previous step) will be to bootloader again
$ fastboot -w to wipe data (not sure if necessary, but I did it)
$ fastboot set_active a (if current Boot-slot is b or vice versa)
I then repeated step 4 and after flashing was finished, I let the phone boot into Android system
re-enable developer-options and then $ adb reboot bootloader
Then set the custom operating system key:
$ fastboot erase avb_custom_key
$ fastboot flash avb_custom_key avb_pkmd-device.bin
After this, I relocked the bootloader $ fastboot flashing lock , then rebooted into Android system.
The official DivestOS instructions recommend to leave the OEM unlocking setting to ON to reduce the risk of a permanent brick after a bad update in the future.
After a couple of weeks, I'll see what happens after an OTA update arrives so I can be confident that both slots A and B are functioning correctly.
Any feedback is welcome on whether some of my steps are a bad idea or unnecessary. This is not a guide, just my feedback on what I did to get DivestOS working with the bootloader relocked on my walleye phone.

zpunout said:
Thanks for DivestOS and support of the Pixel2 walleye.
I had some confusion installing it before I succeeded.
Here are the generic instructions from the DivestOS website: https://divestos.org/index.php?page=bootloader
I copy pasted the instructions below and left only the instructions specific to walleye plus a few steps I took.
Here are the steps from those instructions which I used (I removed unnecessary steps for walleye)
Enable 'Allow OEM unlocking' under 'Developer options' in Settings if available
Reboot to the bootloader via key combination or $ adb reboot bootloader
$ fastboot flashing unlock
$ fastboot update divested-version-date-dos-device-fastboot.zip
Be ready to hold down volume down button so reboot (after flashing from previous step) will be to bootloader again
$ fastboot -w to wipe data (not sure if necessary, but I did it)
$ fastboot set_active a (if current Boot-slot is b or vice versa)
I then repeated step 4 and after flashing was finished, I let the phone boot into Android system
re-enable developer-options and then $ adb reboot bootloader
Then set the custom operating system key:
$ fastboot erase avb_custom_key
$ fastboot flash avb_custom_key avb_pkmd-device.bin
After this, I relocked the bootloader $ fastboot flashing lock , then rebooted into Android system.
The official DivestOS instructions recommend to leave the OEM unlocking setting to ON to reduce the risk of a permanent brick after a bad update in the future.
After a couple of weeks, I'll see what happens after an OTA update arrives so I can be confident that both slots A and B are functioning correctly.
Any feedback is welcome on whether some of my steps are a bad idea or unnecessary. This is not a guide, just my feedback on what I did to get DivestOS working with the bootloader relocked on my walleye phone.
Click to expand...
Click to collapse
Please follow the steps as on the site.
Developer options has NO effect on whether on not fastboot or adb is enabled in the recovery.
Do not manually swap the slots, instead use the slot sync script after the `fastboot update command` as laid out in the steps.
Do flash the OTA again, as fastboot zip does not contain firmware!
Do not immediately lock, you are supposed to verify boot first so you don't end with locked brick.
I've personally tested taimen working.

SkewedZeppelin said:
Please follow the steps as on the site.
Developer options has NO effect on whether on not fastboot or adb is enabled in the recovery.
Do not manually swap the slots, instead use the slot sync script after the `fastboot update command` as laid out in the steps.
Do flash the OTA again, as fastboot zip does not contain firmware!
Do not immediately lock, you are supposed to verify boot first so you don't end with locked brick.
I've personally tested taimen working.
Click to expand...
Click to collapse
Thanks for the quick reply. I have a taimen I want to install DivestOS onto as well. I recall that on the walleye device, I couldn't get adb sideload to work in recovery, so couldn't run the slot sync script.
I'll try the steps outlined in the official guide again with the taimen device.

zpunout said:
Thanks for the quick reply. I have a taimen I want to install DivestOS onto as well. I recall that on the walleye device, I couldn't get adb sideload to work in recovery, so couldn't run the slot sync script.
I'll try the steps outlined in the official guide again with the taimen device.
Click to expand...
Click to collapse
If adb shows no devices try running with sudo.
Also Pixel 1/2 has broken USB, so make sure to use a USB 2.0 port or hub.

SkewedZeppelin said:
If adb shows no devices try running with sudo.
Also Pixel 1/2 has broken USB, so make sure to use a USB 2.0 port or hub.
Click to expand...
Click to collapse
Thanks for the tip about using a hub. It solved my headaches in recovery with the sideload command. Now the official instructions work perfectly after flashing back to stock and then DivestOS.

An experimental 12.1 based build is up with near full feature parity.
I've tested it working quite well on my taimen, should be fine on walleye.

SkewedZeppelin said:
I've tested it working quite well on my taimen, should be fine on walleye.
Click to expand...
Click to collapse
The Google Pixel 2 (walleye) with divested-19.1-20220411-dos-walley Experimental has been successfully tested on April 15, 2022, and here documented. Meanwhile, I'm running build divested-19.1-20220613 with relocked bootloader.

any new update for walleye?

galibalmasanick said:
any new update for walleye?
Click to expand...
Click to collapse
Regarding?
All devices get updates once, sometimes twice, per month.
The August ASB isn't even public yet, and I won't start a build until after.
See the news page: https://divestos.org/index.php?page=news

SkewedZeppelin said:
Regarding?
All devices get updates once, sometimes twice, per month.
The August ASB isn't even public yet, and I won't start a build until after.
See the news page: https://divestos.org/index.php?page=news
Click to expand...
Click to collapse
Ok,Thank You

Hi.
I have a Pixel2 with Grapheneos already installed.
Should I re-flash the stock rom before installing Divestos?
Thankyou.

altromass said:
I have a Pixel2 with Grapheneos already installed.
Should I re-flash the stock rom before installing Divestos?
Click to expand...
Click to collapse
Nah, you can just flash over to DivestOS.

Hi.
How is it supposed to be used the copy-partitions-walleye-release.zip file?
Is it someting to do with copying the OS to both slots?
I used the command fastboot set_active a to install divestos on the other slot as well.
Would it be ok?
Thank you!

altromass said:
Hi.
How is it supposed to be used the copy-partitions-walleye-release.zip file?
Is it someting to do with copying the OS to both slots?
I used the command fastboot set_active a to install divestos on the other slot as well.
Would it be ok?
Thank you!
Click to expand...
Click to collapse
No you don't either of those steps.
Firmware is included on taimen/walleye.
Bootloader - DivestOS Mobile
divestos.org
You only need steps 1, 2, 3, 4, 5, 6, 7, 9, 11, 12, 13, 14, 15

I'd like to use this ROM but there's one tiny feature I need root for: the app Battery Charge Limit which modifies a single, specific system file. Is there any way around it?
It sounds like a neat ROM for a spare device used solely for crypto operations, but unfortunately not for banking apps based on SafetyNet (because SafetyNet won't work without Google services).

There is no way around that.
There is no proper solution for an integrated battery charge limit.
And root is not supported: https://divestos.org/index.php?page=faq#rootSupport

[ROM] DivestOS 20.0 for taimen

{
"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.
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-taimen
- 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#taimen
- 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_google_taimen, https://github.com/LineageOS/android_device_google_taimen
- Kernel: https://github.com/LineageOS/android_kernel_google_wahoo
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...1/CVE_Patchers/android_kernel_google_wahoo.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-----
[/CODE

If the gapps is not swiped in and the camera is open, it fails to open the camera. May the camera be in use by another program? What's the problem with ID?

我是十七 said:
If the gapps is not swiped in and the camera is open, it fails to open the camera. May the camera be in use by another program? What's the problem with ID?
Click to expand...
Click to collapse
Google Camera (GCam) is not supported.
Are you getting an error with the included OpenCamera?

SkewedZeppelin said:
不支持 Google 相机 (GCam)。
您是否收到包含 OpenCamera 的错误？
Click to expand...
Click to collapse
yes

SkewedZeppelin said:
Google Camera (GCam) is not supported.
Are you getting an error with the included OpenCamera?
Click to expand...
Click to collapse
Since it doesn't support opencamera, why should the system bring its own opencamera

我是十七 said:
Since it doesn't support opencamera, why should the system bring its own opencamera
Click to expand...
Click to collapse
Camera should work.
Have you tested any other apps?
That is a bug if it doesn't work.

SkewedZeppelin said:
Camera should work.
Have you tested any other apps?
That is a bug if it doesn't work.
Click to expand...
Click to collapse
When I open opencamera, it indicates that I can't open it. The camera may be being used by other programs, but I don't have other applications using the camera function!

我是十七 said:
When I open opencamera, it indicates that I can't open it. The camera may be being used by other programs, but I don't have other applications using the camera function!
Click to expand...
Click to collapse
OK, thank you for clarifying. I will look into it.

The tinfoil hat ROM....
I love the post install tip about putting your phone in a faraday bag...not sure how thats going to work well for a phone
Paranoid nonsense

73sydney said:
The tinfoil hat ROM....
I love the post install tip about putting your phone in a faraday bag...not sure how thats going to work well for a phone
Paranoid nonsense
Click to expand...
Click to collapse
This is absolutely not a tinfoil hat or ricing ROM.
This project intends to provide long term support to devices with some privacy and security benefits on top.
If you read that whole sentence with context the key word is "are in high-risk areas".
It is well known that during large events that law enforcement agencies will use interception devices.
Stingray use in United States law enforcement - Wikipedia
en.wikipedia.org

SkewedZeppelin said:
This is absolutely not a tinfoil hat or ricing ROM.
This project intends to provide long term support to devices with some privacy and security benefits on top.
If you read that whole sentence with context the key word is "are in high-risk areas".
It is well known that during large events that law enforcement agencies will use interception devices.
Stingray use in United States law enforcement - Wikipedia
en.wikipedia.org
Click to expand...
Click to collapse
Sorry but i thing his trying just foolout if u catch my minde in any conversation his posting

The camera hasn't been repaired yet?

我是十七 said:
The camera hasn't been repaired yet?
Click to expand...
Click to collapse
Has not, I do not have a Pixel 2 for testing.
Can you provide the output from the following:
adb logcat -b all -d | grep -i -e audit -e dlopen

○opencamera

我是十七 said:
○opencamera
Click to expand...
Click to collapse
I have determined the issue! A new build will be up within a few hours.
Edit: it is now up.

SkewedZeppelin said:
I have determined the issue! A new build will be up within a few hours.
Click to expand...
Click to collapse
thank

The developer option does not show the memory occupied by other applications. Can the next version be repaired? thank

我是十七 said:
The developer option does not show the memory occupied by other applications. Can the next version be repaired? thank
Click to expand...
Click to collapse
That is a side-effect of the hardening. And I'm not actually sure what part causes it.
Does the camera work now?

SkewedZeppelin said:
That is a side-effect of the hardening. And I'm not actually sure what part causes it.
Does the camera work now?
Click to expand...
Click to collapse
Well, the memory occupation function is not displayed. Anyway, it does not affect the use! The camera function is normal, thank you

I found that when ROM is in use, the mobile data network will disappear inexplicably. You need to manually switch the APN option, and then it will be normal. Can you repair it?

[ROM][11][UNOFFICIAL] AICP 16.1 UNNOFICIAL FOR MOTO ONE (DEEN)

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning, we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://sourceforge.net/projects/moto-one-deen/files/AICP-11/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal (and others) GApps packages could have issues, so try using MindTheGapps if you have any issues with other GApps packages
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases, these apps include proprietary libs/code and cannot be included in the device trees on GitHub or we risk having the ROM banned from GitHub. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from GitHub, and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is how users can/should install updates most of the time, this can be done with the built-in updater service or with a custom recovery.
Q. How do I 'dirty flash' builds?
A 1. For "A only" devices: Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
A 2. For "A/B" devices": Wipe the ART/Dalvik cache. Flash the ROM, reboot to the recovery, flash GApps, your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP is recommended, the lineage recovery is a great alternative however, it will not decrypt the internal storage so you will have to flash the rom with adb sideload or usb OTG or with an external sdcard).
3. Wipe the System (DO NOT WIPE THE SYSTEM ON A/B DEVICES!), Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file (reboot to recovery before flashing anything else if you have an "A/B" device).
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device.
7. You can then reboot to recovery and flash the root solution of your choice if you want to, and then boot back to the system.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on A/B Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/jro1979oliver/kernel_motorola_deenDevice tree source:
GitHub - jro1979oliver/device_motorola_deen
Contribute to jro1979oliver/device_motorola_deen development by creating an account on GitHub.
github.com
Vendor source:
GitHub - jro1979oliver/aicp_vendor_motorola
Contribute to jro1979oliver/aicp_vendor_motorola development by creating an account on GitHub.
github.com
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on GitHub
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
Information:
ROM OS Version: 11.x
Kernel: 3.18.140
ROM Last stock Rom required:
Status: STABLE
Release Date: 05-31-2022
You want to see a "normal" night at the "DEV office", click here!!​

Q&A:
1: It's stable?
Yes, it's currently running with selinux enforcing and no major bugs
2: Can I use encryption?
Yes, it's not enforced by default because twrp still can't decrypt, but if you prefer you can do it via settings
3: From where I can find a twrp for first install?
From here. NOTICE: Aicp also ships it's own recovery and it is functional. Besides extreme stable, deen kernel still has a bug where when you are on slot a, recovery can't switch to slot b by it's own, so you need to use fastboot --set-active=b with latest adb tools from google (Download).
From b to a, you can just reboot system. At first install, I recommend a format data to fix selinux contexts that twrp may bork and avoid storage issues

AICP 16.1 (android 11)
Moto One deen
Changelog:
June security patch
Signed build;
Enabled verity checks; added the hability to lock bootloader (do it at your own risk -
fastboot flashing lock and fastboot flashing unlock (this kill your data as stock does));
Added Dolby (settings/sound/dolby atmos);
Working usb internet tethering,
Selinux enforcing;
Reworked paddings;
Enabled proccess reclaim;
Gesture navigation as default;
Enabled LiveDisplay (again)
Bugs:
*
Currently, recovery can't change slot from a to b;
You tell me
May be few more changes idk
https://sourceforge.net/projects/moto-one-deen/files/AICP-11/aicp_deen-16.1_signed.zip/download

I've been away from the xda community for a while and got a Motorola One XT-1941-3 (retail from Brazil).
Is this AICP the most stable custom rom available?
Thanks!

jeferson1979 said:
AICP 16.1 (android 11)
Moto One deen
Changelog:
June security patch
Signed build;
Enabled verity checks; added the hability to lock bootloader (do it at your own risk -
fastboot flashing lock and fastboot flashing unlock (this kill your data as stock does));
Added Dolby (settings/sound/dolby atmos);
Working usb internet tethering,
Selinux enforcing;
Reworked paddings;
Enabled proccess reclaim;
Gesture navigation as default;
Enabled LiveDisplay (again)
Bugs:
*
Currently, recovery can't change slot from a to b;
You tell me
May be few more changes idk
https://sourceforge.net/projects/moto-one-deen/files/AICP-11/aicp_deen-16.1_signed.zip/download
Click to expand...
Click to collapse
Bro have Deen too?

zahidm said:
Bro have Deen too?
Click to expand...
Click to collapse
Yeah, more one moto

jeferson1979 said:
Q&A:
1: It's stable?
Yes, it's currently running with selinux enforcing and no major bugs
...
Click to expand...
Click to collapse
This is a very nice rom and gives more life to my moto one.
However, I'm trying to build it locally and having some issues with the manifest.
Do you mind sharing your manifest for the rom?
Thank you.

I'm trying to rebuild your rom locally with your repositories. Maybe I don't use the correct manifest, and I'm getting selinux policy violation.
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=11
AICP_VERSION=aicp_deen_r-16.1-UNOFFICIAL-20220728
TARGET_PRODUCT=aicp_deen
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.15.39-1-pve-x86_64-Ubuntu-20.04.4-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
KERNEL_TOOLCHAIN=gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
HOST_BUILD_TYPE=release
BUILD_ID=RQ3A.211001.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/motorola/deen device/motorola/deen hardware/qcom-caf/msm8996 vendor/qcom/opensource/data-ipa-cfg-mgr vendor/qcom/opensource/dataservices packages/apps/Bluetooth
============================================
wildcard(out/target/product/deen/clean_steps.mk) was changed, regenerating...
$(shell date +%H%M%S) was changed, regenerating...
[100% 26280/26280] writing build rules ...
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
[ 60% 26285/43481] build out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
FAILED: out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(out/host/linux-x86/bin/sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /system/ must be associated with the "system_file_type" attribute: clean_scratch_files_exec
12:07:01 ninja failed with: exit status 1
#### failed to build some targets (01:56 (mm:ss)) ####
My local manifest is as follows:
Code:
<manifest>
<remote name="kernel" fetch="https://github.com" revision="r11.1" />
<remote name="device" fetch="https://github.com" revision="r11.1" />
<remote name="vendor" fetch="https://github.com" revision="r11.1" />
<remote name="github_fetch" fetch="https://github.com/" revision="lineage-18.1" />
<project name="jro1979oliver/kernel_motorola_deen.git" path="kernel/motorola/deen" remote="kernel" />
<project name="jro1979oliver/device_motorola_deen.git" path="device/motorola/deen" remote="device" />
<project name="jro1979oliver/aicp_vendor_motorola.git" path="vendor/motorola" remote="vendor" />
<project path="external/bson" name="LineageOS/android_external_bson" remote="github_fetch" revision="lineage-18.1" />
<project path="hardware/motorola" name="LineageOS/android_hardware_motorola" remote="github_fetch" revision="lineage-18.1" />
<project path="system/qcom" name="LineageOS/android_system_qcom" remote="github_fetch" revision="lineage-18.1" />
</manifest>
Could you point me in the right direction? Is the manifest good or am I missing something?
Your help will be much appreciated.
Thanks.

xdadevc said:
I'm trying to rebuild your rom locally with your repositories. Maybe I don't use the correct manifest, and I'm getting selinux policy violation.
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=11
AICP_VERSION=aicp_deen_r-16.1-UNOFFICIAL-20220728
TARGET_PRODUCT=aicp_deen
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.15.39-1-pve-x86_64-Ubuntu-20.04.4-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
KERNEL_TOOLCHAIN=gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin
HOST_BUILD_TYPE=release
BUILD_ID=RQ3A.211001.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/motorola/deen device/motorola/deen hardware/qcom-caf/msm8996 vendor/qcom/opensource/data-ipa-cfg-mgr vendor/qcom/opensource/dataservices packages/apps/Bluetooth
============================================
wildcard(out/target/product/deen/clean_steps.mk) was changed, regenerating...
$(shell date +%H%M%S) was changed, regenerating...
[100% 26280/26280] writing build rules ...
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/hw/audio.primary.msm8953.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libsensorndkbridge.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib/libtinycompress.so'
build/make/core/Makefile:49: warning: overriding commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
build/make/core/base_rules.mk:513: warning: ignoring old commands for target `out/target/product/deen/vendor/lib64/libsensorndkbridge.so'
[ 60% 26285/43481] build out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
FAILED: out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests
/bin/bash -c "(out/host/linux-x86/bin/sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy ) && (touch out/target/product/deen/obj/FAKE/sepolicy_tests_intermediates/sepolicy_tests )"
The following types on /system/ must be associated with the "system_file_type" attribute: clean_scratch_files_exec
12:07:01 ninja failed with: exit status 1
#### failed to build some targets (01:56 (mm:ss)) ####
My local manifest is as follows:
Code:
<manifest>
<remote name="kernel" fetch="https://github.com" revision="r11.1" />
<remote name="device" fetch="https://github.com" revision="r11.1" />
<remote name="vendor" fetch="https://github.com" revision="r11.1" />
<remote name="github_fetch" fetch="https://github.com/" revision="lineage-18.1" />
<project name="jro1979oliver/kernel_motorola_deen.git" path="kernel/motorola/deen" remote="kernel" />
<project name="jro1979oliver/device_motorola_deen.git" path="device/motorola/deen" remote="device" />
<project name="jro1979oliver/aicp_vendor_motorola.git" path="vendor/motorola" remote="vendor" />
<project path="external/bson" name="LineageOS/android_external_bson" remote="github_fetch" revision="lineage-18.1" />
<project path="hardware/motorola" name="LineageOS/android_hardware_motorola" remote="github_fetch" revision="lineage-18.1" />
<project path="system/qcom" name="LineageOS/android_system_qcom" remote="github_fetch" revision="lineage-18.1" />
</manifest>
Could you point me in the right direction? Is the manifest good or am I missing something?
Your help will be much appreciated.
Thanks.
Click to expand...
Click to collapse
Just revert this commit. Also, use this repo for hardware/motorola

I made some progress (thanks). There seems to be another selinux issue:
Code:
[ 4% 400/9625] build out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
FAILED: out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
/bin/bash -c "(out/host/linux-x86/bin/treble_sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -b out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/built_plat_sepolicy -m out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/26.0_mapping.combined.cil -o out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/built_26.0_plat_sepolicy -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy -u out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/base_plat_pub_policy.cil ) && (touch out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0 )"
SELinux: The following domains violate the Treble ban against use of the binder_in_vendor_violators attribute: mm-qcamerad
14:04:29 ninja failed with: exit status 1
Looking at the sepolicy/vendor/mm-qcamerad.te file I see:
Code:
# TODO(b/36599434): Remove this once mm-qcamerad stops using Binder services
typeattribute mm-qcamerad binder_in_vendor_violators;
allow mm-qcamerad binder_device:chr_file { read write };
What would be the proper fix here? (sorry if I bother you, I understand I'm way out of my league).

xdadevc said:
I made some progress (thanks). There seems to be another selinux issue:
Code:
[ 4% 400/9625] build out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
FAILED: out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0
/bin/bash -c "(out/host/linux-x86/bin/treble_sepolicy_tests -l out/host/linux-x86/lib64/libsepolwrap.so -f out/target/product/deen/system/etc/selinux/plat_file_contexts -f out/target/product/deen/vendor/etc/selinux/vendor_file_contexts -f out/target/product/deen/system/system_ext/etc/selinux/system_ext_file_contexts -f out/target/product/deen/system/product/etc/selinux/product_file_contexts -b out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/built_plat_sepolicy -m out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/26.0_mapping.combined.cil -o out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/built_26.0_plat_sepolicy -p out/target/product/deen/obj/ETC/sepolicy_intermediates/sepolicy -u out/target/product/deen/obj/ETC/built_plat_sepolicy_intermediates/base_plat_pub_policy.cil ) && (touch out/target/product/deen/obj/FAKE/treble_sepolicy_tests_26.0_intermediates/treble_sepolicy_tests_26.0 )"
SELinux: The following domains violate the Treble ban against use of the binder_in_vendor_violators attribute: mm-qcamerad
14:04:29 ninja failed with: exit status 1
Looking at the sepolicy/vendor/mm-qcamerad.te file I see:
Code:
# TODO(b/36599434): Remove this once mm-qcamerad stops using Binder services
typeattribute mm-qcamerad binder_in_vendor_violators;
allow mm-qcamerad binder_device:chr_file { read write };
What would be the proper fix here? (sorry if I bother you, I understand I'm way out of my league).
Click to expand...
Click to collapse
Remove typeattribute mm-qcamerad binder_in_vendor_violators;

jeferson1979 said:
Remove typeattribute mm-qcamerad binder_in_vendor_violators;
Click to expand...
Click to collapse
This fixed the compile problem. Thank you so much. I've been struggling with compiling an updated aicp for deen for two whole days.
I had a few other issues with a modified api, hence my delay, but I was able to compile, and flash the moto one. It seems to work. No boot loops
I ended up with a few gapps installed in the system (youtube, photos, maps) but there was no google services. This is weird. Why did those apps get included in the first place and how do I remove them?

xdadevc said:
This fixed the compile problem. Thank you so much. I've been struggling with compiling an updated aicp for deen for two whole days.
I had a few other issues with a modified api, hence my delay, but I was able to compile, and flash the moto one. It seems to work. No boot loops
I ended up with a few gapps installed in the system (youtube, photos, maps) but there was no google services. This is weird. Why did those apps get included in the first place and how do I remove them?
Click to expand...
Click to collapse
You may want to use my TWRP with oem wipe option built in, this gapps are coming from stock installation

jeferson1979 said:
You may want to use my TWRP with oem wipe option built in, this gapps are coming from stock installation
Click to expand...
Click to collapse
Formatting the oem partition made them disappear. Most/all things seem to work, including all the hardware. I'm going trough your github commit history. You did quite a bit of work there over the last few months. Impressive. Thank you again !

I see on aicp page that there is latest version 17.1. I think this is android 12 aicp_deen_s-17.1-WEEKLY-20220713.zip
https://sourceforge.net/projects/moto-one-deen/files/latest/download
Someone have tested this version on our moto?

Ok,
jeferson1979 said:
You may want to use my TWRP with oem wipe option built in, this gapps are coming from stock installation
Click to expand...
Click to collapse
I was trying to sign my build and I made something stupid and hard-bricked my xt1941-3 deen.
I have fastboot. fastboot devices shows something but there is no partition table. No A/B slots and no imei/baseband or any other thing. The serial number changed as well. It's still seend as a "deen" product with variant 000000000000000
In linux the phone is recognized as
Bus 001 Device 055: ID 22b8:2e80 Motorola PCS Fastboot deen S
Blankflash will not work in either linux or windows. It waits for the device (I quess the qualcomm flashing device) which is not there.
Is there a way out?
PS: What I did was I flashed the A slot with my boot/system/vendor.img. Then erased the B slot partitions, then booted into TWRP, activated the B slot and flashed the signed ota update, thinking that it would go to the A slot. In the middle of the flash, my phone rebooted and I got a faled boot, no gpt.bin etc.

xdadevc said:
Is there a way out?
Click to expand...
Click to collapse
So, I managed to get my bootloader back. The issue with a partial bootloader was that it was not accepting the blankflash command. No QCOM serial inteface etc.
I found out that "fastboot oem blankflash" will put the bootloader into blankflash mode, and pull up the serial interface. However there's a timing issue. blankflash must start almost immediately after going into this mode. To same me the hassle I made a small script:
Code:
#!/bin/bash
fastboot oem blankflash
for i in `seq 1 1000` ; do
./qboot blank-flash --debug=4 $*
done
Now this is sub-optimal, but worked first time for me. Just power on the phone, wait for the bootloader to come up, then start the script. It will require a ctrl-c after the phone reboots into fastboot again, this time with a proper partition table, imei, gpt etc all working.
Back to business. I'm trying to sign AICP with my own keys, then enable AVB verifier and relock the bootloader. Perhaps blankflash can be used to actually flash my own boot in place of the motorola one?
For now I'm trying to understand how to exactly sign the image with my keys. Then how to enable AVB.
PS: The "blankflash" command from fastboot oem disappeared as soon as I had a working gpt. I guess it's a failsafe. Trying to put it again into blankflash mode resulted in an error. YMMV

Hi, it's been a long weekend here. I'm up and running now. ROM compiles and works nicely. I have one residual issue when updating from a build generated by me. The recovery accepts it (keys verify) but fails at the last stage (3/3) after updating some of the partitions. After this the moto will not boot any more and requires a full image file upload. Not sure why this is and if it's only on my own phone.
But overall, things look nice. Great job @jeferson1979 and for the help in setting this up.

There's an issue with TWRP 3.6.9. I tried to use it to make a nandroid backup of a running AICP (test keys) and I skipped the data partition. The backup seemed properly done (no errors).
However, rebooting the phone never gets past the initial bootloader screen. This is only after making a backup, no restore.
I tried restoring the boot image, then system and it failed with an error. Second thing I tried was flashing my current build of AICP (different keys that original). Booting works, but decoding the data (which is encrypted) resulted in an error. The message says "password is correct, but the data is corrupt and cannot be decoded". This is weird because it says the same even with a totally bogus password.
So, seems that booting in TWRP will damage the data partition. Is this due to the different selinux context? Any other suggestion for making a nandroid backup? Recompile TWRP for Moto Deen ?
I'm be willing to help/compile/work on this. Let me know where to dig
I'm trying to get my moto up to standard of being a daily driver and reliable enough to be safe with the data in it.
I think there's a lot of life left in it.
Let me know. Thank you.

xdadevc said:
There's an issue with TWRP 3.6.9. I tried to use it to make a nandroid backup of a running AICP (test keys) and I skipped the data partition. The backup seemed properly done (no errors).
However, rebooting the phone never gets past the initial bootloader screen. This is only after making a backup, no restore.
I tried restoring the boot image, then system and it failed with an error. Second thing I tried was flashing my current build of AICP (different keys that original). Booting works, but decoding the data (which is encrypted) resulted in an error. The message says "password is correct, but the data is corrupt and cannot be decoded". This is weird because it says the same even with a totally bogus password.
So, seems that booting in TWRP will damage the data partition. Is this due to the different selinux context? Any other suggestion for making a nandroid backup? Recompile TWRP for Moto Deen ?
I'm be willing to help/compile/work on this. Let me know where to dig
I'm trying to get my moto up to standard of being a daily driver and reliable enough to be safe with the data in it.
I think there's a lot of life left in it.
Let me know. Thank you.
Click to expand...
Click to collapse
It's a know issue of TWRP last years, also, encryption doesn't work either. And you're right, TWRP makes selinux contexts goes nuts