Develop Bugs

[MOD][APR 11][DEV] MultiROM v33

{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z1. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.​
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Omni TWRP - https://github.com/lj50036/platform_manifest_twrp_omni (branch twrp-6.0)​
Donations
[MENTION=3418703"Tasssadar[/MENTION] would be glad if you could spare a few bucks. You can use either paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris. And if you want to donate me for porting the updated version of MultiROM, PM me .
Thanks to all donors, it is much appreciated ​
XDA:DevDB Information
MultiROM Xperia Z1, Tool/Utility for the Sony Xperia Z1
Contributors
aquaboy11
Version Information
Status: Testing
Created 2016-04-11
Last Updated 2016-04-12

Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk

drakonizer said:
Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk
Click to expand...
Click to collapse
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.

aquaboy11 said:
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.
Click to expand...
Click to collapse
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?

drakonizer said:
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?
Click to expand...
Click to collapse
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.

aquaboy11 said:
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.
Click to expand...
Click to collapse
So you mean the recovery? I've got that working too, seems like we're both stuck at the same point...unfortunately we don't have the sources of the old multirom v30x.

Is it only me? I cannot find download links for your version

Hitman73 said:
Is it only me? I cannot find download links for your version
Click to expand...
Click to collapse
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs

drakonizer said:
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs
Click to expand...
Click to collapse
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.

aquaboy11 said:
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.
Click to expand...
Click to collapse
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.

drakonizer said:
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.
Click to expand...
Click to collapse
MultiROM v30 boots fine.
I used Sony's device tree
mr_init_devices.c
Everything from BoardConfig.mk after line 41.
I could give porting kexec to MM a shot when I have some spare time.

Hi. I experienced a problem entering the recovery. My device stuck at the Sony symbol displayed an the orange LED when I try to enter. Before I updated my recovery I used the one from v30 thread without any problems. Any idea where the problem is?
Thanks in advance!

LB multirom
Hello, I have a small question ...
If I install MultiROM v33 on my Xperia Z (LB) "locked bootloader",
can i install secondary ROMs for unlocked bootloader ???
thank you

Is this still being worked on?

KaliLinux NetHunter v1.0 [Kali v2.0/Backtrack 5][athene]

{
"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"
}
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, [URL="https://github.com/offensive-security/kali-nethunter/wiki/NetHunter-Mana-Wireless"]Evil AP MANA attacks[/URL], and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
FIRST THINGS FIRST, SERIOUSLY:
Your warranty was void as soon as you unlocked your bootloader.
Although Kali Nethunter should be safe to use, I am not responsible for whatever happens to your device, router, or whatever networking infrastructure because of YOU misusing the available facilities of Kali.
Remember that while Kali can be absolutely safe, if you handle root access improperly, no one will help you.
Make sure you read all of the info here and have some basic knowledge about networking, kernels and Linux/Unix.
Even if you're able to find a vulnerability on a different host (often called victim) , don't misuse the advantage you have.
Report the issue to the device's owner and the OEM. Do not complain if the attacks aren't working. Security has been ramping up ever since the wikileaks incident and the Edward Snowden thing.
FEATURES:
Kali NetHunter Application
Home Screen - General information panel, network interfaces and HID device status.
Kali Chroot Manager - For managing chroot metapackage installations.
Check App Update - For checking Kali NetHunter Android App updates.
Kali Services - Start / stop various chrooted services. Enable or disable them at boot time.
Custom Commands - Add your own custom commands and functions to the launcher.
MAC Changer - Change your Wi-Fi MAC address (only on certain devices)
VNC Manager - Set up an instant VNC session with your Kali chroot.
HID Attacks - Various HID attacks, Teensy style.
DuckHunter HID - Rubber Ducky style HID attacks
BadUSB MITM Attack - Nuff said.
MANA Wireless Toolkit - Setup a malicious Access Point at the click of a button.
MITM Framework - Inject binary backdoors into downloaded executables on the fly.
NMap Scan - Quick Nmap scanner interface.
Metasploit Payload Generator - Generating Metasploit payloads on the fly.
Searchsploit - Easy searching for exploits in the Exploit-DB.
3rd Party Android Applications (WIP)
NetHunter Terminal Application
DriveDroid
USB Keyboard
Shodan
Router Keygen
cSploit
Remember that there might be many other exploits and attack features available online, the ones mentioned above are officially documented by Kali. Secondly, not much support will be possible regarding the attacking since not everyone will have the same opportunities.
DOWNLOADS
Sourceforge might show this file as Malware for obvious reasons, but open the filename and choose the directlink. I will contact their support team for this soon, meanwhile you can also check the Android File Host mirror.
1. For N Custom ROMs :
Sourceforge folder
Android Filehost
2. For stock N:
3. For MM Custom ROMs:
4. For Stock MM:
INSTALLATION
IMPORTANT NOTE: Kali NetHunter is NOT an Android ROM, but it is an overlay ( you have to flash it above android).
The builds currently provided are to be used on Nougat based custom ROMs ONLY. (which use the LineageOS kernel)
Installing it on a ROM which uses the LineageOS 14.1 kernel. (examples include all of our N custom ROMs like Lineage, AEX, AICP, AOKP, DU ) :
1. Make sure you are running the latest available build of the ROM you have installed.
2. Reboot to TWRP.
3. Make sure you backup Boot, System and Data partitions, just incase you want to remove Kali, you can restore it.
3. Wipe Cache and ART Cache (Formerly known as Dalvik Cache). Do NOT wipe your data partition.
4. Install the zip file.
5. Reboot to System.
POST INSTALLATION:
1. Open the NetHunter App and start the Kali Chroot Manager.
2. You might want to download the real packages which might be around 400-500 MB in size.
3. Set up Hacker Keyboard.
4. Configure Kali Services, such as SSH.
5. Set up custom commands.
6. Initialize the Exploit Database.
BUGS:
Please read the help thread before you point out issues here. It has been created specifically to help new users to adapt to custom roms easier. Before you post your issue, please check if it has already been reported and if a fix has already been mentioned.
SCREENSHOTS:
https://vimeo.com/132329259
https://youtu.be/yV6AzqgdBo4
IMPORTANT LINKS:
1. My build of TWRP
2. KaliLinux NetHunter Github Wiki
3. KaliLinux NetHunter Website
4. Source for athene: https://github.com/tywinlannister7/nethunter-devices
XDA:DevDB Information
KaliNethunter for athene, ROM for the Moto G4 Plus
Contributors
tywinlannister7 @keerten
Source Code: https://github.com/offensive-security/kali-nethunter
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest stock Nougat firmware
Version Information
Status: Stable
Created 2017-07-20
Last Updated 2017-07-20

Reserved

Reserved

Will it work on AOSP CAF?

aravindmj said:
Will it work on AOSP CAF?
Click to expand...
Click to collapse
It uses the LineageOS kernel, so YES. :good:

First off thank you for this second how do we add HID devices to kali

khaoticking said:
First off thank you for this second how do we add HID devices to kali
Click to expand...
Click to collapse
You're welcome.
The NetHunter HID Atacks turn any device and its OTG USB cable into a pre-programmed keyboard, able to type any given commands. HID here refers to the Human Interface Devices like your keyboard mouse touchpad etc. The mounting process should be similar like you do on any android device. If you're not sure that kali isn't detecting the device, you might want to try running this command in the terminal:
Code:
lsusb

tywinlannister7 said:
You're welcome.
The NetHunter HID Atacks turn any device and its OTG USB cable into a pre-programmed keyboard, able to type any given commands. HID here refers to the Human Interface Devices like your keyboard mouse touchpad etc. The mounting process should be similar like you do on any android device. If you're not sure that kali isn't detecting the device, you might want to try running this command in the terminal:
Click to expand...
Click to collapse
Kali doesn't detect any HID devices when trying to run the hello world duck script it won't type anything

Can you give me the link to the kernel sources...

khaoticking said:
First off thank you for this second how do we add HID devices to kali
Click to expand...
Click to collapse
The Android HID patch as mentioned by pelya has not been applied to the kernel sources. That's why there is no HID Interfaces...
If anybody knows how to custom compile a kernel then one can look at @pelya guide how to patch it..
Link to kernel source of tywinlannister https://github.com/tywinlannister7/elementalx_kernel_motorola_msm8952
Link to patched kernel sources Jleeblanch but it is not compiling he is the official maintainer of Resurrection remix for Athene "the Kali branch"
https://github.com/Jleeblanch/android_kernel_motorola_msm8952
If anybody looks into the matter we can get fully functional Kali nethunter...
Thanks in advance..:good:

Does it work on Moto g4 plus and how to remove the Kali overlay latter. Thanks

Sobhan Bhuyan said:
Does it work on Moto g4 plus and how to remove the Kali overlay latter. Thanks
Click to expand...
Click to collapse
This is in the G4 Plus forum. That usually means it works on the G4 Plus.

zeomal said:
This is in the G4 Plus forum. That usually means it works on the G4 Plus.
Click to expand...
Click to collapse
I flashed it and got an error in twrp ( named error one or something) and then there were no overlays to be seen inside. Later I knew that caller ID is not visible while calling or being called. Restored then. Pls advice. Should I flash again.

Managed to get the error message from twrp. Pls advice

Sobhan Bhuyan said:
Managed to get the error message from twrp. Pls advice
Click to expand...
Click to collapse
As it says in the TWRP error, did you boot and set up your device, then reboot to flash the Kali overlay? From the opening post, this appears to flash over existing custom ROMs.
What ROM are you attempting to flash Kali over?

Sobhan Bhuyan said:
Managed to get the error message from twrp. Pls advice
Click to expand...
Click to collapse
First of all a ROM must be installed and on top of that only nethunter should be flashed(so only it is called overlay ROM ,something has to be underneath it...:good: )

echo92 said:
As it says in the TWRP error, did you boot and set up your device, then reboot to flash the Kali overlay? From the opening post, this appears to flash over existing custom ROMs.
What ROM are you attempting to flash Kali over?
Click to expand...
Click to collapse
I m currently on ressurection remix ROM ,device XT1643
So you mean that after wiping cache I must set up device as new first then reboot and flash the overlay. Ok I will try and let you know

Sorry to bother, but what about ElementalEx kernel? Is it compatible, untested, or uncompatible?
Also, does it need a fresh ROM flash, or could it be used over an already flashed, rooted and used ROM with EX ?

Will it work for Viper OS 7.1 nougat?

What is the difference between this version and version 3.0?
'

[EOL][KERNEL] [G93xx][2019-05-25] WirusMOD [Nethunter for Oreo]

End of Life WirusMOD Nethunter Kernel for Oreo ROMs
Samsung Galaxy S7 / Edge ​
Code:
I am not responsible for bricked devices.
If you going to flash it, you accepted it.
Of course your warranty is void.
This thread is for herolte. If you have S7 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
Most features of TGPKernel
Supported ROMs:
S7 Stock O ROMs - G930F / G930FD / G930W8 / G935F / G935FD / G935W8
S7 Hybrid O ROMs (G930F/G935F) - The Galaxy Project (TGP), Ambasadii S7, SilverRom, etc
S9 Port ROMs
N8 Oreo Port ROMs
Download:
Latest version Herolte here.
Installation:
1. Flash latest TWRP twrp-3.3.0-1+ ( to see data partition with enabled disk quota)
1. TWRP Backup your ROM
3. Flash Nethunter WirusMOD
4. Magisk and busybox is needed you can choose in aroma or install it later.
5. Install Magisk Nethunter module from Magisk Manager -> Downloads (Or another version of Nethunter)
If you get crashes in Magisk Nethunter app than install from here.
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
Now you have Nethunter on your herolte/hero2lte.
EXTRA:
1.In Utilities.7z are wifi testing tools binaries like aircrack-ng compiled from source of nexmon (Not needed for Nethunter only for test tools direct from android without Nethunter)
If you want use binaries you need to copy it to /system/bin or /system/xbin and give permissions to it rwxr-xr-x
2. DriveDroid without bugs made by disabling HID Patch:
To disable HID Patch: use this command in terminal: "echo Y > /sys/module/g_android/parameters/hid_disable"
Changing mode isn't instant after changing module status. Use DriveDroid (mount iso -> dismount) to active hid_disable.
To enable HID Patch: "echo N > /sys/module/g_android/parameters/hid_disable" and use DriveDroid like with disabling HID Patch.
HIDPatchSwitch this is simple script which can switch between HID enabled and disabled and show changed status.
Old Installation steps:
1. TWRP Backup your ROM
2. Flash Nethunter.WirusMOD.G93xx.vx.x.XXXXXXXX.zip
2.1.Look at EXTRA.
3. Busybox is needed you can choose in aroma or install another version.
6. Install Magisk Nethunter module from Magisk Manager -> Downloads (Or another version of Nethunter)
If you get crashes in Magisk Nethunter app than install this version.
7. Install kalifs-armhf-*.tar.xz by Nethunter manager
8. 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
9. Download Modules for your version of smartphone and copy it anywhere in your phone.
By using modules you can add features to kernel for which i hadn't memory in kernel and aren't most important like rarely used wifi card modules or file systems modules. Load only those which you need.
You can use modules by those commands insmod, rmmod, lsmod or use Module Loader this app is outdated but works fine.
Now you have Nethunter on your herolte/hero2lte.
EXTRA:
If you want to have unencrypted data partition:
1. Format data partition(you lose your data).
2 Flash Kernel with option NO ROOT
2. After flashing kernel flash "remove encryption.zip".
3. Reboot to system (First start configuration wizard).
4. Reboot to twrp and flash Magisk.
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"
}
Credits:
djb77 for his TGPkernel source
Nethunter creators for the best portable penetration testing tool.
XDA:DevDB Information
[KERNEL][G93xx][2019-05-25] WirusMOD [Nethunter for Oreo], Kernel for the Samsung Galaxy S7
Contributors
Svirusx
Source Code: https://github.com/Svirusx/Nethunter-s7-kernel-WirusMOD-Oreo
Kernel Special Features: Powered by TGPKernel
Version Information
Status: Testing
Created 2019-02-09
Last Updated 2019-06-22

CHANGELOG
2019.09.27- v1.4
Upstream to tgpkernel source Version 6.15.2[EOL]
2019.06.22- v1.3
Update source to TGPKernel Version 6.15.0
2019.05.25 - v1.2
Updated TGPkernel source to v6.14.0 (release from 2019-05-23)
Rebased source, removed loadable modules
Ramdisk compressed with xz to get more free space for drivers.
Little fixes in defconfig
2019-04-20 - v1.1
Added monitor mode patches to some wifi usb drivers.
Added possibility to disable HIDPatch (this fixes DriveDroid)
Added HIDPatchSwitch: Simple sh script to switch status of HIDPatch (Info in comments in script)
Updated TGP source to Version 6.12.8
2019-02-09 - v1.0
Initial release.

Reserved

What's different between 2 of your kali net hunter or wiresmod nethunter

I'm not sure if this is related but could this help me with the 5 GHz Wi-Fi disconnects on my phone every 10 minutes from the AP?
No other device has this issue for me, only this phone and I tried changing channels already, they all drop exactly at 10 minutes and I've given the phone permanent local IP, no lease time.
On the other hand 2.4 GHz is rock solid.

shabbir143 said:
What's different between 2 of your kali net hunter or wiresmod nethunter
Click to expand...
Click to collapse
This WirusMOD Nethunter is based on TGPKernel so it have features of TGPKernel too. Normal Nethunter is based on Stock Kernel.
GlossGhost said:
I'm not sure if this is related but could this help me with the 5 GHz Wi-Fi disconnects on my phone every 10 minutes from the AP?
No other device has this issue for me, only this phone and I tried changing channels already, they all drop exactly at 10 minutes and I've given the phone permanent local IP, no lease time.
On the other hand 2.4 GHz is rock solid.
Click to expand...
Click to collapse
No, this kernel can't help you for disconnects.

I'm going to buy a usb wifi dongle with an AR9271. By connecting it, I can use it in monitoring mode and send deauthentication packets. I understand correctly?

_Danil_ said:
I'm going to buy a usb wifi dongle with an AR9271. By connecting it, I can use it in monitoring mode and send deauthentication packets. I understand correctly?
Click to expand...
Click to collapse
Yes. You can do all what you can do in normal Kali Linux. Only you need to have htc_9271.fw in /system/etc/firmware/ in your android. ( It is included in Nethunter_Binaries.7z)

Hi! First of all, thanks a lot for your amazing job!
I'm trying to get my usb adapter tp-link tl-wn821n and I couldnt... I've installed the drivers from the tplink website, some drivers from this link and others sources with no success... any idea how to make it work?
Thanks!

maty25 said:
Hi! First of all, thanks a lot for your amazing job!
I'm trying to get my usb adapter tp-link tl-wn821n and I couldnt... I've installed the drivers from the tplink website, some drivers from this link and others sources with no success... any idea how to make it work?
Thanks!
Click to expand...
Click to collapse
I don't know which version of tp-link tl-wn821n you have. I heard that v1 - v3 are on atheros chipset. Next versions are on RTL8192.... and i don't know about compatibility v4+ versions with kali linux.
Looking at source code of which you used. I think you have v4+ so first you need to insmod modules RTL8192 than you need copy firmware.
In NetHunter_Binaries.7z are firmwares for RTL8192... in \system\etc\firmware\rtlwifi\ extract all of they direct in \system\etc\firmware
I think that android might not load drivers which are in extra folders in \system\etc\firmware\
All those things you need to do in Android not in Kali chroot.
If you have problems with inserting modules than try my kernel for Oreo Stock it have no modules, all are included in kernel. With this kernel you need only copy firmware.
My TGP based kernel is too big to have all modules included.

Svirusx said:
I don't know which version of tp-link tl-wn821n you have. I heard that v1 - v3 are on atheros chipset. Next versions are on RTL8192.... and i don't know about compatibility v4+ versions with kali linux.
Looking at source code of which you used. I think you have v4+ so first you need to insmod modules RTL8192 than you need copy firmware.
In NetHunter_Binaries.7z are firmwares for RTL8192... in \system\etc\firmware\rtlwifi\ extract all of they direct in \system\etc\firmware
I think that android might not load drivers which are in extra folders in \system\etc\firmware\
All those things you need to do in Android not in Kali chroot.
If you have problems with inserting modules than try my kernel for Oreo Stock it have no modules, all are included in kernel. With this kernel you need only copy firmware.
My TGP based kernel is too big to have all modules included.
Click to expand...
Click to collapse
Thanks for the info! I've tried to copy the files from the "rtlwifi" folder to the firmware folder but when I reboot the phone they get deleted :/ I supossed I'll try with an stock version... thanks!

maty25 said:
Thanks for the info! I've tried to copy the files from the "rtlwifi" folder to the firmware folder but when I reboot the phone they get deleted :/ I supossed I'll try with an stock version... thanks!
Click to expand...
Click to collapse
In my old phone i used this path /vendor/firmware maybe it can working for you.
I had too this problem but with copying to system/xbin. Solved by copying those files to system/bin

I just want to ask, can't hold my self.
Will it work on latest rr with android 9.x ?

SomniusX said:
I just want to ask, can't hold my self.
Will it work on latest rr with android 9.x ?
Click to expand...
Click to collapse
No, it's only for Oreo

Svirusx said:
No, it's only for Oreo
Click to expand...
Click to collapse
Yeah, figures.. just had one hope

Can you update to the latest version of TGP?
Also, what modules are included in the kernel?

_Danil_ said:
Can you update to the latest version of TGP?
Also, what modules are included in the kernel?
Click to expand...
Click to collapse
All what is in FEATURES is included, if you want look at all included in kernel modules you need to look at defconfig in kernel source.
When i get free time i try update it.

Sometimes the smartphone reboot itself. In a random time, with various actions. Sometimes in a couple of hours there can be 4 restarts.
Firmware: latest THE GALAXY PROJECT
But nethunter works fine, monitoring, injections and even interception of PMKID ?

_Danil_ said:
Sometimes the smartphone reboot itself. In a random time, with various actions. Sometimes in a couple of hours there can be 4 restarts.
Firmware: latest THE GALAXY PROJECT
But nethunter works fine, monitoring, injections and even interception of PMKID
Click to expand...
Click to collapse
Maybe try LineageOS 14.1 version this one is more stable than STOCK one. I switched to LineageOS 15.1. Later i going to publicate my new port of Nethunter kernel for LineageOS 15.1 and now i'm testing LineageOS 16.0 build which is not yet stable.

@Svirusx It may be to early to ask this, but do you have any plans to port either this or just bethunter to stock pie? https://www.google.com/amp/s/forum....t/blackdiamondfesmooth-fastv1-0-t3915483/amp/

[KERNEL] EvilKernel to work properly with Nethunter and Andrax

{
"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"
}
I am not responsible for using my kernel with bad intentions, the kernel only serves to test my network and devices.
Click to expand...
Click to collapse
Status: Beta
Developer: mozahist228
Kernel for Linux version: 4.9.226
Spoiler: Features
Generic IEEE 802.11 Networking Stack (mac80211)
HCI USB driver
HCI VHCI (Virtual HCI device) driver
USB RTL8150 based ethernet device support
Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
Multi-purpose USB Networking Framework
CDC NCM support
OTG support
USB Wireless Device Management support
USB 2.0 OTG FSM implementation
USB Modem (CDC ACM) support
Atheros Wireless Cards
Linux Community AR9170 802.11n USB support
Ralink driver support
Spoiler: Note
Put it through TWRP. If necessary, then flash magisk because with the installation of the kernel, it will be erased.
Only for Lineage OS-based firmwares
Spoiler: Bags
Working with the Bluetooth interface is not available
Spoiler: Screenshots
Spoiler: Download
GoogleDisk
Source code: GitHub

Just created an account to say thanks! This worked for me. I've been trying for the last week to get Nethunter to recognize my Wi-Fi USB adapters, and I think this package is what did it.
If anybody is curious, these are the steps I took
fastboot into TWRP, format everything/factory reset
in TWRP, adb sideload the new Lineage 18.1 ROM from this thread
still in TWRP, adb sideload the custom kernel OP posted
mozahist228 said:
Spoiler: Download GoogleDisk
Click to expand...
Click to collapse
Boot up Lineage OS, run through initial setup
Reboot back into recovery, use TWRP to sideload OpenGApps (optional) if you're going to do this, you *have* to get OpenGApps from this page, as their support for Android 11 is still in beta
use TWRP to sideload Magisk
use TWRP to sideload the Generic ARM64 Nethunter image from this page (or direct download by clicking me)
Boot back into Lineage, run the Nethunter app and ensure chroot is working properly (mine wasn't I had to do a bit of futzing around with it, but this was my own fault)
Finally, open the Magisk Manager app, go to the modules tab, search for and install "Wireless Firmware for Nethunter". Do *not* install the "KaliNethunter" module, as this continually caused problems for me.
I don't know if this is the best order to do it in, I'm very new with Android stuff, but just thought I'd share what worked for me. Thanks again OP!

Finally some Nethunter kernel for this device, Would love to see the feature : Monitor Mode on the SoC (SD625)

rubrex said:
Finally some Nethunter kernel for this device, Would love to see the feature : Monitor Mode on the SoC (SD625)
Click to expand...
Click to collapse
At the moment this is impossible, any patches do not work, and my knowledge is not enough to expand the driver's functionality

So, there is just usb adapters support with no monitor mode, or mode is available for external adapters? Anyway thanks for any movements to the right way!

mr.onegin said:
So, there is just usb adapters support with no monitor mode, or mode is available for external adapters? Anyway thanks for any movements to the right way!
Click to expand...
Click to collapse
I think this is all you wanted to see)

Are you planning to add HID support?

Firerust said:
Are you planning to add HID support?
Click to expand...
Click to collapse
It is already present

mozahist228 said:
It is already present
Click to expand...
Click to collapse
It doesn't work for me, using pelya's app to test HID feature

Firerust said:
View attachment 5219973
It doesn't work for me, using pelya's app to test HID feature
Click to expand...
Click to collapse
I don’t think it was adapted for new kernel versions.

mozahist228 said:
I don’t think it was adapted for new kernel versions.
Click to expand...
Click to collapse
Even last version of Rucky which was updated on 2020 doesn't work, it says kernel does not support HID, does this feature work for you?

Firerust said:
Even last version of Rucky which was updated on 2020 doesn't work, it says kernel does not support HID, does this feature work for you?
Click to expand...
Click to collapse
If you do not know the basic things then you should not go into this field

mozahist228 said:
If you do not know the basic things then you should not go into this field
Click to expand...
Click to collapse
Yeah you're right, just looking at your source I realized you have no idea of what I'm referring to, since f_hid.c hasn't been modified. Thanks anyway.

Firerust said:
Even last version of Rucky which was updated on 2020 doesn't work, it says kernel does not support HID, does this feature work for you?
Click to expand...
Click to collapse
I got Rucky to work, however I eventually had to reflash my device because it wouldn't boot up. Even before that, it would routinely take 5+ minutes to boot with this kernel installed. Not sure if this kernel is to blame or something Nethunter related.

Firerust said:
Yeah you're right, just looking at your source I realized you have no idea of what I'm referring to, since f_hid.c hasn't been modified. Thanks anyway.
Click to expand...
Click to collapse
He shouldn't have been changed

lmfao, so you literally got sleepy, kanged the defconfig + the commits you advertise as features. At least put proper authorship lmfao + no mention of lacia anywhere. NIce job sir

And FYI the sleepy source you used as a base is old af, newer one is in https://github.com/Couchpotato-sauce/kernel_xiaomi_sleepy

forsalebypwner said:
Just created an account to say thanks! This worked for me. I've been trying for the last week to get Nethunter to recognize my Wi-Fi USB adapters, and I think this package is what did it.
If anybody is curious, these are the steps I took
fastboot into TWRP, format everything/factory reset
in TWRP, adb sideload the new Lineage 18.1 ROM from this thread
still in TWRP, adb sideload the custom kernel OP posted
Boot up Lineage OS, run through initial setup
Reboot back into recovery, use TWRP to sideload OpenGApps (optional) if you're going to do this, you *have* to get OpenGApps from this page, as their support for Android 11 is still in beta
use TWRP to sideload Magisk
use TWRP to sideload the Generic ARM64 Nethunter image from this page (or direct download by clicking me)
Boot back into Lineage, run the Nethunter app and ensure chroot is working properly (mine wasn't I had to do a bit of futzing around with it, but this was my own fault)
Finally, open the Magisk Manager app, go to the modules tab, search for and install "Wireless Firmware for Nethunter". Do *not* install the "KaliNethunter" module, as this continually caused problems for me.
I don't know if this is the best order to do it in, I'm very new with Android stuff, but just thought I'd share what worked for me. Thanks again OP!
Click to expand...
Click to collapse
when i choose kali in the terminal, it just crashes, any idea on how to fix that?

Don't stop this project please, you are the one who delivered this "special" kernel!

Hello! I installed everything right. I tried a lot of variations. But when i boot into the system it shows the kali icon for a sec and then nothing visible its just a black screen. it reacts to the side buttons. This problem is only happen when i install nethunter on it, the kernel the lineageOS and the magisk is working properly.
Please help! I working on this for a very long time and i cant fix it.
Thanks in advance

[ROM] LineageOS 19.1 UNOFFICIAL - 1.3 [vendor & FBE] [2022-04-20]

LineageOS 19.1 for Sony Xperia XZ Premium
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
Real vendor partition
FBE instead of FDE encryption
DOWNLOAD
You can download the latest releases and TWRP here:
https://androidfilehost.com/?w=files&flid=333825
Check the ChangeLog below for firmware requirements!
INSTALLATION
This build uses a real vendor partition in place for the (now) useless oem partition. You will therefore need the modified TWRP with vendor/FBE support linked above.
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, No1Alien, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12.1 / 12L
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2022-04-20

SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.

REQUIRED FIRMWARE: 47.2.A.10.107 (47.2.A.11.239 should also work as there isn't any real changes)
CHANGELOG
2022-04-20 | 1.3| 47.2.A.10.107
Initial release

Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？

ssdsw said:
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
Click to expand...
Click to collapse
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.

derf elot said:
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
Click to expand...
Click to collapse
is there any clues/guide on how to edit the fstab?
so we can use f2fs on data & cache

is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?

m00ns0rr0w said:
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
Click to expand...
Click to collapse
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.

derf elot said:
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
Click to expand...
Click to collapse
hi,
thx for your answer. i was just curious, as the arrowos build is based on your work and has signature spoofing enabled. But if, as you write, that's a lot of work then ... no problem. the arrowos version is stable
And, without signature spoofing, the part with "howto best migrate from rom A to rom B" is obsolete Self-building doesn't seem to be an option, as the hardware requirements seem a bit ... ambitious

Thanks for the great ROM.
I did a few tests today and I couldn't find anything broken.
The only issue I have found so far is when I take a picture or video with Open Camera and try to open it for preview inside the app. It does not work.

Thanks for your working on the ROM.
I found that LOS installed on my G8142 seems to have screen always on when charging, both on 18.1 and 19.1 (which is this one). How to turn it off?

Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily

stipi69 said:
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
Click to expand...
Click to collapse
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.

derf elot said:
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
Click to expand...
Click to collapse
I agree, but i have faulty vol+ key so i was having a hard part sadlly.
Can i ask you something i see this problem 1+ years on all Lineage roms and i am not a developer:
SETTINGS / DISPLAY / LIVE DISPLAY / COLOR PROFILE / VIVID
If i choose this profile i get like 8 bit colors after a while of use, but realy like this profile... i adjusted it manualy now its good looking and stable but wondering if it is XZ P specific or all lineage

short message: my SIM card isn't working with this ROM.
long message: today i installed this ROM. I first flashed stock ROM, booted into it once, and then flashed this ROM. But, as with the ArrowOS ROM, my SIM card isn't working.
More Details: after fresh install of this ROM and during boot i enter the SIM PIN (so that works), but after boot it says: "service not available" (Dienst nicht verfügbar). I'm unable to get it working.
Provider: congstar (telekom daughter). The SIM worked with stock ROM, and it works in an older Samsung S5. Just for curiosity i flashed stock ROM again and
Yeah, i know, no warranty, but... someone had such a problem before?
thx

geee... getting crazy here... after the next (test) flash of this ROM the SIM suddenly works, as well as phone calls, SMS, ...
what's the difference to the first flash? after latest stock ROM flash i left the SIM inside, and the stock ROM (or the telekom software) did some settings, rebooted, and then i started the last flash. Is there something magic that is happening here?
if i had more hair all of it would be bright gray...

OK, after almost a week... no SIM card problems anymore. ROM is running stable.
Just some apps that somehow rely on Google Play Services (or microg maybe) don't run: apps that warn regarding severe weather conditions or catastrophes, like 'DWD Warnwetter', 'NINA KatWarn' etc.. Push notifications...

ROM is stable, and i finally managed the signature spoofing + microg stuff. Thx to @Yokurt815 and his little list in the XZ1C thread - going step by step, writing it all down, finally succeeded.
Am i right that the magisk/lygisk stuff has to be done again after flashing an possibly upcoming ROM update?

Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.

shoey63 said:
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
View attachment 5643169
Click to expand...
Click to collapse
Edited: NVM, seems like it won't work neither.
You need to set Ok Google/Hey Google at first boot; otherwise, it won't work.