{
"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
Related
WARNING: When using custom kernels on the S7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
OKAY SO
This is Kali NetHunter 3.15.2 for the Galaxy S7.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The NetHunter installer zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local/nhsystem, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.2 (stable, 2016-11-04)
Please be careful to download the right version based on this table:
SM-G930F, SM-G930FD, SM-G930W8, SM-G930X: kernel-nethunter-herolte-*
SM-G930K, SM-G930L, SM-G930S: kernel-nethunter-heroltekor-*
S7 edge: You're in the wrong forum!
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
This means that if your data partition is encrypted, you will need to use the [Format Data] button in TWRP to remove encryption.
This will delete all your data, including internal storage.
You should back everything up first before installing Kali NetHunter.
Samsung Smart Switch Mobile can be useful for this, and allows you to back up your apps to a location on an external SDcard.
Unfortunately it doesn't back up most app data.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
It's become apparent that there may be issues with the stock ROM and this kernel, and that it might run best on a Note 7 port.
FULL INSTALLATION STEPS
Install Team Win Recovery Project to your recovery partition.
{
"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"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
For new installations: Download the nethunter-generic-arm64-kalifs zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
THE KERNEL
The NetHunter kernel for the Galaxy S7 is based on Samsung's OSRC N930SKSU2BPID Note 7 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.44 (with dirtycow vulnerability patched)
SELinux permissive
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted data partition support
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
USB HID Gadget keyboard & mouse support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption disabled (not supported by custom kernels at the moment)
Kernel module support, insert your own modules!
CIFS, NFS available through included kernel modules
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
Reboot after 60 seconds - Sometimes when you boot your device it could reboot after 60 seconds because of a Samsung secure service not responding. Unresolved, but rare, and only happens within 60 seconds of a boot.
DEVELOPMENT
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Galaxy S7 NetHunter kernel source: https://github.com/jcadduono/android_kernel_samsung_universal8890/tree/nethunter-6.0
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7, Kernel for the Samsung Galaxy S7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.15.2
Stable Release Date: 2016-11-04
Created 2016-10-06
Last Updated 2016-11-04
I cannot test this today, but i ****in love you !
saphirrot said:
I cannot test this today, but i ****in love you !
Click to expand...
Click to collapse
Yeah I just hope it's all working fine this time Last time I opened a thread for NetHunter on S7 it was a little embarrassing as I didn't own any recent Galaxy phones I had no idea they'd be such a challenge to get custom development going on.
I still haven't exactly tested this, but I do have the Note 7 now so I'm really hoping that everything done to make it work on the Note 7 makes it work on the S7 and S7 edge too... *crosses fingers*
We've got a few issues to fix before an actual release but they're all related to the apps.
1. The NetHunter Terminal app is quite buggy, so you might want to use JuiceSSH local terminal for now. (type su -c bootkali_login to enter Kali environment)
2. The NetHunter app's scripts are all hardcoded for armhf right now. I've actually completed arm64 support in the installer and we can build working arm64 rootfs and install it, just the NetHunter app can't see it yet so we're using armhf on arm64 instead for now.
Anyways, hope to hear some good news from ya! These remaining issues shouldn't take long for us to overcome...
For s7 edge do I have download the arm packages or arm64 packages?
Handeman707 said:
For s7 edge do I have download the arm packages or arm64 packages?
Click to expand...
Click to collapse
you're in the wrong forum, go to S7 edge forum
http://forum.xda-developers.com/s7-edge/development/kernel-kali-nethunter-galaxy-s7-edge-t3475413
this probably isn't something you want to play around with if you don't know if your phone is arm or arm64 :/
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
XanSama said:
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
Click to expand...
Click to collapse
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
jcadduono said:
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
Click to expand...
Click to collapse
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
XanSama said:
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
Click to expand...
Click to collapse
Used USB RO to install Windows 10 from boot the other day, but that was in UEFI mode
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
ahamed.rafi135 said:
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
Click to expand...
Click to collapse
Only tested on latest stock FXXU1BPI firmware
jcadduono said:
Only tested on latest stock FXXU1BPI firmware
Click to expand...
Click to collapse
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
ahamed.rafi135 said:
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
Click to expand...
Click to collapse
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040 bytes :/
jcadduono said:
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040 bytes :/
Click to expand...
Click to collapse
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
ahamed.rafi135 said:
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
Click to expand...
Click to collapse
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
i have attached the log
jcadduono said:
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
Click to expand...
Click to collapse
also which rom do you recommend?
ahamed.rafi135 said:
also which rom do you recommend?
Click to expand...
Click to collapse
the one that matches your boot image...
i will always recommend stock over anything else though
ok try a build from here instead:
http://build.nethunter.com/test-builds/
update: tested myself and it worked fine, posted new nightly build with changes
it will remove the firmware upgrade service from boot image, which is useless anyway as we can't take OTAs with custom kernels
Hi, I have flashed both of the lastest kernels (kernel-nethunter-herolte-marshmallow-3.15.2-20161024-2241) and (kernel-nethunter-herolte-marshmallow-3.15.2-20161023-0148) but they are still laggy and are having poor CPU performance in geekbench tests. Any fix?
Does it requires an external WiFi adapter to test my internet security or does the WiFi adapter of the S7 can do the job ?
Thank you
{
"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?
'
{
"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"
}
SailfishOS for ASUS Zenfone 5Z by VerdandiTeam
Warning: Flashing this may void your device’s warranty, lead
to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore
must be done entirely at your own risk. No one affiliated with this project is responsible for your
actions but yourself.
Click to expand...
Click to collapse
THIS IS NOT ANDROID NOR THERE IS ANY ANDROID APP SUPPORT. GO USE GNU OR SOMETHING
Not working:
Camera recording (in progress but i wanted to share the sfos with yall already)
Use advanced camera from openrepos if you want wide angle (jolla didn't get to add it to stock camera yet)
calls are untested altho should work
GPS is untested (probably works too)
INSTALL:
Strap in for a ride, if at any step you don't know what you are doing, you better give up and stay on android. If i'm doing something incorrectly then tell me but i've been fighting over 3 days just to get lineage and twrp working… but maybe i'm just stoopid
If you can install provided lineage 17.1 on slot a then you don't need these instructions and jump to flashing sfos:
I couldn't find any valid tutorial on getting stock android 10 but i've found stock fastbootable image somewhere (yes, don't trust it lol) so i will share it with you [link]
Also lineage removed 17.1 builds but the guy was making nightlies which are still available so i also uploaded the build i'm using for archive purposes [link]
Idea is that no matter where you are coming from or if you just bought device you should get to sfos this way. And if you are wondering still yes we will be removing ALL YOUR DATA so backup it.
Flash the provided stock via fastboot (there is script and even files for QDL but i haven't tested those). It's pretty straight forward you should figure it out, if not then there is some tutorial i think on this forum or on internet, if you can't handle it then give up really you can do more damage than good.
Verify that its booting, stock will be flashed to slot a. flash and boot twrp (android 10 version, link to image, link to installer) via "fastboot flash boot twrp-3.5.2_10-1-Z01RD.img" i'm not really using windows but you should be able to figure it out already. Flash lineage 17.1 from provided link, it will flash to slot b. afterwards flash twrp installer (the zip) so that you can boot twrp (just flashing twrp on boot on slot b doesn't work GO FIGURE). Reboot, verify that lineage is booting, reboot to bootloader, select recovery, hold power button (fastboot reboot recovery only works sometimes, again GO FIGURE). you should be back in twrp on slot b. Flash lineage again as well as twrp installer so that lineage will be installed on slot a as well as twrp will be bootable. reboot, verify that lineage boots and that you are in fact on slot a. Finally we have lineage on slot a.
Sailfish flashing instructions (come here if you have lineage 17.1 on slot a):
- download rootfs
- flash/boot twrp on slot a (or slot b, i'm not even sure at this point)
- wipe everything (you need to format data, not wipe, format. data NEEDS to be unencrypted, advanced -> format data -> yes, if you didn't realize yet we are wiping EVERYTHING so backup your data)
- Install rootfs (aka sailfish, it will flash kernel onto the same slot so you don't have to worry about switching slots, at least i hope so, if it doesn't boot, get the hybris-boot.img from the zip and fastboot flash boot it onto slot a)
- Boot
- Have fun
Changelog:
STABLE 1:
Initial public release
F.A.Q.
HOW TO REPORT BUG
After bug occurs type in the terminal following commands:
/usr/libexec/droid-hybris/system/bin/logcat
devel-su dmesg
devel-su journalctl
and give me logs from there (do not paste it in the post! Use pastebin.com)
devel-su will ask you for password, you can set it in developer tools.
Contributors
Mister_Magister
Source Code: https://github.com/VerdandiTeam
Thanks for the efforts you put in to bring Sailfish OS to our device. Good work! ??
please make stable SailFish OS
i would like to use this ROM as Primary ROM
rootfs is missing... where can i find it.
i had it before and i misplaced it.
can anyone share the file with me
Hybris17 is almost ready. I'll re-port 5z on top of lineage17/hybris17 in hope of getting modem fixed. If the modem will turn out to be fixed i will push it forward as current hybris16 based port has only stereo and modem broken.
HEY ITS NOT DEAD OKAY
Mister_Magister said:
Hybris17 is almost ready. I'll re-port 5z on top of lineage17/hybris17 in hope of getting modem fixed. If the modem will turn out to be fixed i will push it forward as current hybris16 based port has only stereo and modem broken.
HEY ITS NOT DEAD OKAY
Click to expand...
Click to collapse
Cool, ping me when ready to test
Mister_Magister said:
Hybris17 is almost ready. I'll re-port 5z on top of lineage17/hybris17 in hope of getting modem fixed. If the modem will turn out to be fixed i will push it forward as current hybris16 based port has only stereo and modem broken.
HEY ITS NOT DEAD OKAY
Click to expand...
Click to collapse
If this hybris17 is not a android rom like havoc or bliss.
Then I am in for using it
Vivek Garg 001 said:
If this hybris17 is not a android rom like havoc or bliss.
Then I am in for using it
Click to expand...
Click to collapse
Hybris is library that Sailfishos uses to communicate with android side of things so it's still sailfishos just using newer android base, lineage 17 in this case
Mister_Magister said:
Hybris is library that Sailfishos uses to communicate with android side of things so it's still sailfishos just using newer android base, lineage 17 in this case
Click to expand...
Click to collapse
How many basic things are not working currently????
I just need calls , camera and wifi to work properly and Android app support is there in this os ... So when it's ready just post it please
I'm requesting the developer to develop further more to best of sailfish for the device , I want to use sailfish as a daily driver
alwinbernat said:
I'm requesting the developer to develop further more to best of sailfish for the device , I want to use sailfish as a daily driver
Click to expand...
Click to collapse
You can't request **** you don't own me
Anyway, i finally started making port based on lineage17.1/hybris17.1 lets see if i get sim to work
Vivek Garg 001 said:
How many basic things are not working currently????
I just need calls , camera and wifi to work properly and Android app support is there in this os ... So when it's ready just post it please
Click to expand...
Click to collapse
There is no android support.
Currently what is blocking me is being unable to boot twrp at all so i cannot flash lineage 17.1 and therefore i cannot flash sfos. This device is such pita…
Good news, since i got 17.1 to work, i also got port working on 17 base and mobile data (and probably calls too) are working! So now hopefully i will have 100% working port as now i only have camera left to fix. After that i will release it again
Mister_Magister said:
Good news, since i got 17.1 to work, i also got port working on 17 base and mobile data (and probably calls too) are working! So now hopefully i will have 100% working port as now i only have camera left to fix. After that i will release it again
Click to expand...
Click to collapse
grt news sar
Mister_Magister said:
Good news, since i got 17.1 to work, i also got port working on 17 base and mobile data (and probably calls too) are working! So now hopefully i will have 100% working port as now i only have camera left to fix. After that i will release it again
Click to expand...
Click to collapse
I am waiting for the release
Camera even with wide angle is working fine, i'm just fixing recording. Fingerprint doesn't want to preserve fingerptints between reboots and actdead (charging off screen) is not working
Mister_Magister said:
Camera even with wide angle is working fine, i'm just fixing recording. Fingerprint doesn't want to preserve fingerptints between reboots and actdead (charging off screen) is not working
Click to expand...
Click to collapse
Will we be getting android app support???
Vivek Garg 001 said:
Will we be getting android app support???
Click to expand...
Click to collapse
Ofcourse not, ports don't have android support
So i released the build because i was impatient. Instructions may sound difficult but if you know what you are doing then its pretty straightforward
Step 1 get provided lineage 17.1 installed on slot A
Step 2 make sure /data is unencrypted, format it
Step 3 flash sfos on slot A
Step 4 voila
{
"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"
}
PixelExperience Plus for S10e/S10/S10+
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- GPS
- Cameras (All of them)
- HWcomposer (HWC)
- Signal indicator
- Double tap to wake
- Wireless PowerShare
- Face unlock
Known issues
VoLTE/VoWifi (due to Samsung's proprietary implementation)
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download for S10e
Download for S10
Download for S10+
To install Magisk on this rom, follow the link here for instructions
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 11.0.0_r32
Security patch level: March 2021
Build author/Device Maintainer: turbolukex5
Device Source code: https://github.com/ivanmeler/android_kernel_samsung_beyondlte/
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Is safetynet passed by default , or is Magisk needed to pass it ?
I've been waiting for a long time, thank you very much. It would be great if it was official too
Edit: offline charging is not working for me :/
ILOIVE said:
Is safetynet passed by default , or is Magisk needed to pass it ?
Click to expand...
Click to collapse
Passed by default
OMG OMG THANKS SO MUCH!!!!!!!
offline charging is not working for me too... in any AOSP based rom for S10e
kullanici32 said:
I've been waiting for a long time, thank you very much. It would be great if it was official too
Edit: offline charging is not working for me :/
Click to expand...
Click to collapse
Wondering if dirty flash is OK over 2021-01-09 version?
Edit: Yeah, works fine for now at least. Made a full backup before.
Don't forget this link for magisk patched boot .img
beyond - Google Drive
drive.google.com
Oh my goodness, I just have to comment on this... thanks for this update.
UsernameNotRecognized said:
Wondering if dirty flash is OK over 2021-01-09 version?
Edit: Yeah, works fine for now at least. Made a full backup before.
Don't forget this link for magisk patched boot .img
beyond - Google Drive
drive.google.com
Click to expand...
Click to collapse
Added link to Magisk instructions to OP, thanks for making me aware.
kullanici32 said:
I've been waiting for a long time, thank you very much. It would be great if it was official too
Edit: offline charging is not working for me :/
Click to expand...
Click to collapse
etx40jtfnrh61 said:
offline charging is not working for me too... in any AOSP based rom for S10e
Click to expand...
Click to collapse
It is indeed a known problem that Offline Charging isn't available, once the developer of the LineageOS ROM finds time to implement this, I will most certainly include it in this and other ROMs too.
Hey
thank you soo much! I've been using an OP7t but now I'm actually thinking of giving another chance to the Samsung.
Mind someone giving some help on root and magisk please? Last time I rooted was 5 years ago
Basically, I rooted on stock and I have had magisk working. Then I followed this: https://forum.xda-developers.com/t/...-0-x-twrp-for-galaxy-s10-e-5g-exynos.4180287/ to have twrp and installed this pixelexperience rom. How do I get magisk with hopefully the security working (with the proper config and patches). I found this file: https://drive.google.com/drive/folders/14LgOP_7B_N55FR2_v4pBce_lLU7aNu-M however it's unclear to me which one is for my version (s10+ SEE Europe edition). I get I have to use it as a base for magisk patching (right?) but I just don't get which one?
Thanks
My bad, got the idea...
hmm
how to get the fingerprint working properly? does it involve the CLI tool provided in magisk or it should work natively?
problem_child said:
Hey
thank you soo much! I've been using an OP7t but now I'm actually thinking of giving another chance to the Samsung.
Mind someone giving some help on root and magisk please? Last time I rooted was 5 years ago
Basically, I rooted on stock and I have had magisk working. Then I followed this: https://forum.xda-developers.com/t/...-0-x-twrp-for-galaxy-s10-e-5g-exynos.4180287/ to have twrp and installed this pixelexperience rom. How do I get magisk with hopefully the security working (with the proper config and patches). I found this file: https://drive.google.com/drive/folders/14LgOP_7B_N55FR2_v4pBce_lLU7aNu-M however it's unclear to me which one is for my version (s10+ SEE Europe edition). I get I have to use it as a base for magisk patching (right?) but I just don't get which one?
Thanks
My bad, got the idea...
Click to expand...
Click to collapse
If you have everything setup you just need to flash the proper .img to your boot partition.
That's it.
You need beyond2LTE.
Don't use magisk patching, I tried to update it through that and after my phone didn't boot. Fixed that with the .img in the link.
problem_child said:
hmm
how to get the fingerprint working properly? does it involve the CLI tool provided in magisk or it should work natively?
Click to expand...
Click to collapse
It works natively for me with the S10+.
UsernameNotRecognized said:
If you have everything setup you just need to flash the proper .img to your boot partition.
That's it.
You need beyond2LTE.
Don't use magisk patching, I tried to update it through that and after my phone didn't boot. Fixed that with the .img in the link.
It works natively for me with the S10+.
Click to expand...
Click to collapse
the trick is not to long press the fingerprint
Aslo, I've read through the telegram channel that actually one should setup using the CLI - but only if it's not working (telegram of Ivan Maler - lineagOS 18.1 dev).... There are a lot of helpful hints there btw.
ok, are there some culprits as to when is magisk working after reboot? seems I have lost root in along the way.
Can anyone else confirm whether the Bixby button works or not? And also, is there a setting somewhere (or a workaround) to force some apps and games to utilize the full screen including the notch area as in stock One UI? (I heard that there was a setting for this in Developer's Options, but haven't been able to find anything so far)
PS. Solid ROM BTW, updated from Pixel Experience Beta. Been using that one as my daily driver since January, and now updated to this one.
How do I get GPay to work? Do I need Magisk for it?
Edit: safety net doesn't pass by default for me for some reason
monkeymechanic said:
Can anyone else confirm whether the Bixby button works or not? And also, is there a setting somewhere (or a workaround) to force some apps and games to utilize the full screen including the notch area as in stock One UI? (I heard that there was a setting for this in Developer's Options, but haven't been able to find anything so far)
PS. Solid ROM BTW, updated from Pixel Experience Beta. Been using that one as my daily driver since January, and now updated to this one.
Click to expand...
Click to collapse
I think you mean the display cutout settings. I don't think they work to do that though. I think there is no way to force full screen unless you use Samsung ROMs. It's up to the app developers to do it themselves.
hey
does anyone have problems booting and rebooting the phone? Basicaly mine is stuck with a black screen. The only way I can get SOME signs of life is to boot it using the volume-downd + powerkey combination and then volume-up, bixby and power to get to twrp bootloader. From there I select reboot to system but nothing happens.
I thought that the reboot was somewhat klunky with magisk but I really didn't learn the trick yet. I appreciate any advice.
thanks
Google assistant is not working on the bixby button
Even configuring still not working
Hi all,
Is there an easy way to get off the BETA pixel experience onto this one, if I have magisk flashed?
Hello everyone,
To keep it short: Some of you may have noticed. Google uploaded a mainline 5.15 branch for the Pixel 6 Pro.
Here´s a build for those that dare trying or simply want to run a mainline kernel on their phone.
I don´t plan to update this much outside of the scope that googles does and what I already did. It´s more of a proof of concept and I think there are at least some that would be eager to try.
I was able to daily drive it two days without a single crash, due to disablng WiFi Calling and by not using my USB C buds, but rather bluetooth buds.
However now I´m back to 5.10 as it´s really just a piece of concept. Essentially mainline GKI kernel with downstream android driver changes. Some pieces that are in the 5.10 kernel that haven´t been brought to 5.15 yet, are missing.
Feel free to report bugs and I will add them to the list.
However if you have issues you have been warned
Features:
Main Features:
- Based on latest kernel sources from Google for 5.15
Bugs:
- powerhal broken due to several scheduler optimizations still missing , removed faulty hints when running powerhint mainline module
- vibration, fixed when running powerhint_mainline module
- USB-C devices crash the device upon connection usb c hub now works, connect mouse to usb c hub works too
- USB-C headphones do not output sound
- USB-C to 3.5mm adapter is not working
- having wifi calling/vowifi enabled makes a network driver crash the phone
- fast charging is not working correctly on my end
- probably many more I didn´t notice
DOWNLOAD:
Download is always located in this folder:
https://www.androidfilehost.com/?w=files&flid=329868
Changelog:
Android 12
Initial Release
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- a device rooted with magisk
- vbmeta flashed with disabling verification and verity flags (check process how to root the phone here)
How to flash the Kernel:
1. Download the images provided in the downloads section to your PC.
2. Download the powerhint magisk module for mainline found in downloads section and flash it via Magisk Manager like any other magisk module.
3. Flash ALL the provided images using fastboot/bootloader and fastbootd (different to the regular Kirisakura Kernel)
4. Don´t forget to patch the boot.img with Magisk Manager prior to flashing it.
3. Magisk-patched boot.img, dtbo.img and vendor_boot.img need to be flashed in fastboot, while vendor_dlkm needs to be flashed via fastbootd
First boot to bootloader, either via the option in Magisk Manager or via adb command:
Code:
adb reboot bootloader
Now in fastboot flash boot.img and dtbo.img
Commands:
Code:
fastboot flash dtbo dtbo.img
fastboot flash boot yourmagiskpatchedboot.img
fastboot flash vendor_boot vendor_boot.img
How to boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
google for all the work on this
Source Code: https://github.com/freak07/Kirisakura_Raviole
mine too
{
"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 belongs to me too.
and the last one
Did you notice any benefit performance/battery wise? I'll probably give it a try, thank you!
Tomatot- said:
Did you notice any benefit performance/battery wise? I'll probably give it a try, thank you!
Click to expand...
Click to collapse
probably both for the worse as several optimizations from google have not yet found their way to 5.15 from 5.10.
Does this mean it would be possible to run a linux operating system on the pixel 6 pro? For example, postmarketos, fedora or manjaro? Just like the pinephone?
deleted
This should work on P6 also correct?
ne0ns4l4m4nder said:
This should work on P6 also correct?
Click to expand...
Click to collapse
Just read the title... (also Raviole = Raven + Oriole)
Krullendhaar said:
Does this mean it would be possible to run a linux operating system on the pixel 6 pro? For example, postmarketos, fedora or manjaro? Just like the pinephone?
Click to expand...
Click to collapse
That would be possible anyway.
Freak07 said:
Essentially mainline GKI kernel with downstream android driver changes.
Click to expand...
Click to collapse
So its not really mainline, its google downstream, just not as big of a delta as usual. What I'd *really* love to see, is this hardware running on a real mainline straight from kernel.org.
So this is what rolling Android looks like lol
It seems to be amazing
bush911 said:
It seems to be amazing
Click to expand...
Click to collapse
have you flashed the kernel? if so, what's your experience like.
Alekos said:
have you flashed the kernel? if so, what's your experience like.
Click to expand...
Click to collapse
not yet, I prefer flash a zip kernel via EXKM, i am afraid of these commands
bencozzy said:
Best kernel period. Fixed all the stock bugs for me.
Only the known kernel bugs exist this is a step in the right direction.
Where can I send funds to buy you some adult beverages?
Click to expand...
Click to collapse
Click "Toggle signature" at the bottom of their post to show the donation link that's in their signature.
Worth looking at 5.17 or nah?
android-mainline-5.17
vassosman said:
Worth looking at 5.17 or nah?
android-mainline-5.17
Click to expand...
Click to collapse
If I find time, I might push out an updated build some time in the future.
but whether it´s based on 5.15, 5.17 or even 5.18 no clue.
I personally don´t think this is daily driver ready in any way, only a proof of concept and uninteresting for most.
Outta curiosity how did you figure out the boot.img config/offsets, or what are they I guess. Everytime I try to parse it through abootimg it crashes on me or complains about a missing page size.
I can boot this image just fine but I haven't been able to make my own yet