Kali NetHunter for OnePlus 8 series
{
"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"
}
DescriptionKali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.DisclaimerYour warranty is now void.
I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame me or XDA and its respected developers.Features
WiFi injection
Internal WiFi monitor mode
AirSpy / HackRF (RTL-SDR)
Bluetooth (RFCOMM)
USB Arsenal
External WiFi adapters from NetHunter's support list
HID attacks
RFID platform support
A11 version based on Neutrino's kernel with CAF 4.19 and linux-stable merged in
A12 version based on crDroid kernel with CAF 4.19 and linux-stable merged in
Disabled Android Paranoid Network mode to allow access to all networking features for PostgreSQL, apt, ping and other commands
Prerequisites
Clean A11 OxygenOS or custom ROM
Custom A12 ROM
Unlocked bootloader
TWRP
Magisk
Universal Mount System read write R/W
How to Install
Spoiler: OxygenOS
Copy twrp, magisk, System_RW_sript, NetHunter kernel & NetHunter zip to external USB-C drive
Flash TWRP
Reboot into recovery, format data & reboot back to recovery
Reboot to system, finish Android setup, launch Magisk app & apply post install requirements
Copy systemrw_1.32 folder to /data/local/tmp & make script systemrw.sh executable (chmod +x)
Reboot into TWRP, launch terminal & run command /data/local/tmp/systemrw_1.32/systemrw.sh size=100
Reboot to system & check the ability to write into system folder (e.g. create empty folder)
Install NetHunter zip through Magisk
Flash NetHunter kernel using kernel manager or twrp recovery
Reboot to system & run NetHunter app
Update NetHunter app from NetHunter Store
Spoiler: Custom ROM
Copy twrp, magisk, NetHunter kernel & NetHunter zip to external USB-C drive
Flash TWRP
Reboot into recovery, format data & reboot back to recovery
Install Magisk
Reboot to system, finish Android setup, launch Magisk app & apply post install requirements
Install NetHunter zip through Magisk
Flash NetHunter kernel using kernel manager or twrp recovery
Reboot to system & run NetHunter app
Update NetHunter app from NetHunter Store
Downloads
A11 NetHunter Magisk Installer
A11 NetHunter Kernel
A12 NetHunter Magisk Installer
A12 NetHunter Kernel
Known issues
Switching internal wlan0 to monitor mode and back to managed mode freezes device for about 15 seconds (A11 kernel only)
Run chown -R postgres:postgres /var/lib/postgresql/14/main in case of postgresql service start fail
CreditsThe Offensive Security Team and the NetHunter community
My huge thanks to:
kimocoder
0ctobot
Re4son
@lebigmac
@Invincible-Man
@Zackptg5
RfidResearchGroup
iceman1001
Thanks for your great work, support, help and development!
Without you there would be nothing here!
Contributors
[email protected]!0T
SourceOfficial Source Code:
Official NetHunter Project
Source code for OnePlus 8 series:
[email protected]!0T/NetHunter Project
[email protected]!0T/NetHunter Devices
Kernel Source:
A11 kernel
A12 kernel
Notes & UpdatesStatus: Testing
Current Kernels Versions:
4.19.205 for A11
4.19.226 for A12
Created 2021-08-26
Last Updated 2022-03-27
Navigation in terminal doesn't work. Just install fzf package to repair.
Will recompile installer soon.
Upload new installer with fzf package included.
New kernel release
Updated kernel to last commits from Neutrino
Current kernel version - 4.19.205
Fixed some compile warnings
flypatriot said:
New kernel release
Updated kernel to last commits from Neutrino
Current kernel version - 4.19.205
Fixed some compile warnings
Click to expand...
Click to collapse
Will this kernel supports external adapter for monitor mode???
firdoshakir said:
Will this kernel supports external adapter for monitor mode???
Click to expand...
Click to collapse
Yes! It supports external wifi adapters with monitor mode and injection and internal wifi adapter in monitor mode only.
But there is no TWRP applicable to OnePlus 8 android11, is it available?
ottoskyer said:
But there is no TWRP applicable to OnePlus 8 android11, is it available?
Click to expand...
Click to collapse
Unfortunately, I didn't test this build on non custom recovery devices.
But you can try Ex Kernel Manager or Franko Kernel Manager to install kernel.
SystemRW script need more steps to do. You can reed about it in SystemRW thread.
i cannot get the internal wifi in monitor mode this rom and kernel.
I tried it with wifite and then every number from 1 to 6
even tried it with just airmon-ng start wlan0
but i cannot get it into monitor mode.
Is there maybe al solution ?
With external wifi card it does work
i noticed the title says "Oneplus 8 Series" ... does this mean it works with the regular Oneplus 8 5G variant?
Develectron 666 said:
i cannot get the internal wifi in monitor mode this rom and kernel.
I tried it with wifite and then every number from 1 to 6
even tried it with just airmon-ng start wlan0
but i cannot get it into monitor mode.
Is there maybe al solution ?
With external wifi card it does work
Click to expand...
Click to collapse
Can you describe you problem with more details, please?
1. What's your device (model).
2. What's your ROM (OxygenOS or custom)
3. Did you try to turn off wifi before switching wlan0 to monitor mode?
4. Do you use commands from NetHunter App menu or you just launch wifite and choose wlan from wifite's menu?
You always need to switch off wifi and then run commands from NetHunter App.
AiM2LeaRn said:
i noticed the title says "Oneplus 8 Series" ... does this mean it works with the regular Oneplus 8 5G variant?
Click to expand...
Click to collapse
Yes. It should works. But don't forget to backup you current kernel in case of some unexpected situations.
Develectron 666 said:
i cannot get the internal wifi in monitor mode this rom and kernel.
I tried it with wifite and then every number from 1 to 6
even tried it with just airmon-ng start wlan0
but i cannot get it into monitor mode.
Is there maybe al solution ?
With external wifi card it does work
Click to expand...
Click to collapse
only monitor mode is working on internal wifi. if you want to inject packets you have to
use external wifi recommended adapter. this rom is working on both custom and oos with
twrp recovery. i have personally tested. working good. if its not working then you are doing
some sort of mistake in installing nethunter.
flypatriot said:
Kali NetHunter for OnePlus 8 seriesView attachment 5394073
DescriptionKali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.DisclaimerYour warranty is now void.
I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame me or XDA and its respected developers.Features
WiFi injection
Internal WiFi monitor mode
AirSpy / HackRF (RTL-SDR)
Bluetooth (RFCOMM)
USB Arsenal
External WiFi adapters from NetHunter's support list
HID attacks
RFID platform support
Based on Neutrino's kernel with CAF 4.19 and linux-stable merged in
Preinstalled Oh-My-Zsh with theme adapted to android terminal and useful navigation plugins
Preinstalled RRG / Iceman - Proxmark3 client for Generic Proxmark3 Easy platform
Disabled Android Paranoid Network mode to allow access to all networking features for PostgreSQL, apt, ping and other commands
Prerequisites
Clean OxygenOS 11 ROM or any custom ROM based on Android 11
Unlocked bootloader
TWRP
Magisk
Universal ForceEncrypt Disabler
Universal Mount System read write R/W
How to Install
Spoiler: OxygenOS
Copy twrp, magisk, Disable_Dm-Verity_ForceEncrypt, System_RW_sript, NetHunter kernel & NetHunter zip to external USB-C drive
Flash TWRP
Reboot to bootloader & flash empty vbmeta with command fastboot --disable-verity --disable-verification flash vbmeta <path to vbmeta.img>
Reboot into recovery, format data & reboot back to recovery
Install Magisk & “Disable_Dm-Verity_ForceEncrypt”
Reboot to system, finish Android setup, launch Magisk app & apply post install requirements
Copy systemrw_1.32 folder to /data/local/tmp & make script systemrw.sh executable (chmod +x)
Reboot into TWRP, launch terminal & run command /data/local/tmp/systemrw_1.32/systemrw.sh size=100
Reboot to system & check the ability to write into system folder (e.g. create empty folder)
Install NetHunter zip through Magisk
Reboot to recovery & install NetHunter kernel
Reboot to system & run NetHunter app
Update NetHunter app from NetHunter Store
Spoiler: Custom ROM
Copy twrp, magisk, Disable_Dm-Verity_ForceEncrypt, NetHunter kernel & NetHunter zip to external USB-C drive
Flash TWRP
Reboot into recovery, format data & reboot back to recovery
Install Magisk & “Disable_Dm-Verity_ForceEncrypt”
Reboot to system, finish Android setup, launch Magisk app & apply post install requirements
Install NetHunter zip through Magisk
Reboot to recovery & install NetHunter kernel
Reboot to system & run NetHunter app
Update NetHunter app from NetHunter Store
Downloads
NetHunter Magisk Installer
NetHunter Kernel
Empty vbmeta && instructions
Known issues
Switching internal wlan0 to monitor mode and back to managed mode freezes device for about 15 seconds
Before doing any updates run service postgresql start && msfdb init commands to exclude any issues with database initiation after updates
CreditsThe Offensive Security Team and the NetHunter community
My huge thanks to:
kimocoder
0ctobot
Re4son
@lebigmac
@Invincible-Man
@Zackptg5
RfidResearchGroup
iceman1001
Thanks for your great work, support, help and development!
Without you there would be nothing here!
Contributors
[email protected]!0T
SourceSource Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/flypatriot/neutrino_kernel_oneplus_sm8250.git
Notes & UpdatesStatus: Testing
Current Kernel Version: 4.19.205
Created 2021-08-26
Last Updated 2021-08-30
Click to expand...
Click to collapse
Thank You For Your Hard Works Just a Question Did the Realtk RTL8812AU external adapter supported Hope You Tell me
deigo775 said:
Thank You For Your Hard Works Just a Question Did the Realtk RTL8812AU external adapter supported Hope You Tell me
Click to expand...
Click to collapse
Yes. Kernel patched for RTL8812AU monitor and injection support.
New kernel release
Updated kernel to last commits from Neutrino
Current kernel version - 4.19.205
Updated nethunter_defconfig
Hello everybody,
First thanks for your work. I'm having a problem regarding internal WiFi monitor mode.
First my config : Oneplus 8T EU version (kebab kb2003). Airmon-ng reports QC6390for the chip. I'm actually using Lineage OS 18.1 but had the exact same problem on stock oxygen O.S. (fully updated).
The problem : I follow your installation procedure, everything works fine. I shut down WiFi by clicking on the WiFi icon. Then I use Nethunter custom commands to start monitor mode on Wlan0.
Then a terminal windows open showing the command running to set monitor mode. The phone will freeze for 15 to 30 seconds then the window closes. The internal WiFi is then in monitor mode, I can start airodump or wifite but the refresh is extra slow and no data at all is captured. I only see from time to time beacons increasing but extra slowly. It's just as if the capture was lagging and there is no captured data.
Any idea to solve this problem ? I read a lot and I saw on the net docs stating that monitor mode is not supported on QC6390.
Thanks for reading and have a good day.
stang1818 said:
Hello everybody,
First thanks for your work. I'm having a problem regarding internal WiFi monitor mode.
First my config : Oneplus 8T EU version (kebab kb2003). Airmon-ng reports QC6390for the chip. I'm actually using Lineage OS 18.1 but had the exact same problem on stock oxygen O.S. (fully updated).
The problem : I follow your installation procedure, everything works fine. I shut down WiFi by clicking on the WiFi icon. Then I use Nethunter custom commands to start monitor mode on Wlan0.
Then a terminal windows open showing the command running to set monitor mode. The phone will freeze for 15 to 30 seconds then the window closes. The internal WiFi is then in monitor mode, I can start airodump or wifite but the refresh is extra slow and no data at all is captured. I only see from time to time beacons increasing but extra slowly. It's just as if the capture was lagging and there is no captured data.
Any idea to solve this problem ? I read a lot and I saw on the net docs stating that monitor mode is not supported on QC6390.
Thanks for reading and have a good day.
Click to expand...
Click to collapse
Hello!
Thanks for your detailed question!
It's a bit strange, you know.
Can you try lspci -k command and check the output?
I've attached my result to this post.
Monitor mode is supported in QCA6390 chipsets by using QCACLD drivers. I switched on monitor mode feature in qca6390_defconfig (see attached picture).
I've also attached pictures with my wifite and airodump-ng commands results.
You need to know that with QCACLD drivers and NetHunter custom command wlan0 doesn't rename to wlan0mon and keeps staying in wlan0 device name. So airodump-ng command should always run with wlan0 device name.
You also should try dmesg | grep qca6390 after running start wlan0 in monitor mode custom command and see if there are any issues with firmware loading.
flypatriot said:
Hello!
Thanks for your detailed question!
It's a bit strange, you know.
Can you try lspci -k command and check the output?
I've attached my result to this post.
Monitor mode is supported in QCA6390 chipsets by using QCACLD drivers. I switched on monitor mode feature in qca6390_defconfig (see attached picture).
I've also attached pictures with my wifite and airodump-ng commands results.
You need to know that with QCACLD drivers and NetHunter custom command wlan0 doesn't rename to wlan0mon and keeps staying in wlan0 device name. So airodump-ng command should always run with wlan0 device name.
You also should try dmesg | grep qca6390 after running start wlan0 in monitor mode custom command and see if there are any issues with firmware loading.
Click to expand...
Click to collapse
Hello @flypatriot and thanks for your quick answer.
Silly me, how could I forget to run a dmesg . You were right it's crippled with error saying that it can't find / open the firmware Dir / files (copy attached) .
The problem is how can I correct this ? I swear I thoroughly followed the install procedure and even made sure that the whole filesystem was R/W so that files could be written anywhere by nethunter install through Magisk
Any idea what to do to correct the install and put the files back in place ???
Thanks a million for your help I started to go nuts .
E.g of error :
12.126845] ueventd: firmware: could not find firmware for qca6390/regdb.bin
[ 12.126853] ueventd: firmware: attempted /etc/firmware/qca6390/regdb.bin, open failed: No such file or directory
[ 12.126856] ueventd: firmware: attempted /odm/firmware/qca6390/regdb.bin, open failed: No such file or directory
[ 12.126859] ueventd: firmware: attempted /vendor/firmware/qca6390/regdb.bin, open failed: No such file or directory
[ 12.126861] ueventd: firmware: attempted /firmware/image/qca6390/regdb.bin, open failed: No such file or directory
[ 12.126866] ueventd: firmware: attempted /vendor/firmware_mnt/image/qca6390/regdb.bin, open failed: No such file or directory
Nobody knows the solution ??
stang1818 said:
Nobody knows the solution ??
Click to expand...
Click to collapse
Sorry for delay. i've just checked my dmesg log:
Spoiler: dmesg.log
[ 9998.706496] cnss_pci 0000:01:00.0: Falling back to syfs fallback for: qca6390/amss20.bin
[ 9998.717074] ueventd: firmware: loading 'qca6390/amss20.bin' for '/devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin'
[ 9998.724436] ueventd: loading /devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin took 7ms
[ 9999.337453] cnss: FW name added with prefix: qca6390/regdb.bin
[ 9999.337506] cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: qca6390/regdb.bin
[ 9999.344640] ueventd: firmware: loading 'qca6390/regdb.bin' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin'
[ 9999.344790] ueventd: firmware: could not find firmware for qca6390/regdb.bin
[ 9999.344799] ueventd: firmware: attempted /etc/firmware/qca6390/regdb.bin, open failed: No such file or directory
[ 9999.344804] ueventd: firmware: attempted /odm/firmware/qca6390/regdb.bin, open failed: No such file or directory
[ 9999.344808] ueventd: firmware: attempted /vendor/firmware/qca6390/regdb.bin, open failed: No such file or directory
[ 9999.344812] ueventd: firmware: attempted /firmware/image/qca6390/regdb.bin, open failed: No such file or directory
[ 9999.344821] ueventd: firmware: attempted /vendor/firmware_mnt/image/qca6390/regdb.bin, open failed: No such file or directory
[ 9999.344852] ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin took 0ms
[ 9999.345024] cnss: Failed to load BDF: qca6390/regdb.bin
[ 9999.345072] cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: 14wlan.b0c
[ 9999.349328] ueventd: firmware: loading '14wlan.b0c' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0c'
[ 9999.351247] ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0c took 1ms
[10143.865458] cnss_pci 0000:01:00.0: Falling back to syfs fallback for: qca6390/amss20.bin
[10143.875459] ueventd: firmware: loading 'qca6390/amss20.bin' for '/devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin'
[10143.878906] ueventd: loading /devices/platform/soc/1c00000.qcom,pcie/pci0000:00/0000:00:00.0/0000:01:00.0/firmware/qca6390!amss20.bin took 3ms
[10144.494126] cnss: FW name added with prefix: qca6390/regdb.bin
[10144.494184] cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: qca6390/regdb.bin
[10144.501617] ueventd: firmware: loading 'qca6390/regdb.bin' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin'
[10144.501853] ueventd: firmware: could not find firmware for qca6390/regdb.bin
[10144.501868] ueventd: firmware: attempted /etc/firmware/qca6390/regdb.bin, open failed: No such file or directory
[10144.501873] ueventd: firmware: attempted /odm/firmware/qca6390/regdb.bin, open failed: No such file or directory
[10144.501878] ueventd: firmware: attempted /vendor/firmware/qca6390/regdb.bin, open failed: No such file or directory
[10144.501882] ueventd: firmware: attempted /firmware/image/qca6390/regdb.bin, open failed: No such file or directory
[10144.501897] ueventd: firmware: attempted /vendor/firmware_mnt/image/qca6390/regdb.bin, open failed: No such file or directory
[10144.501948] ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/qca6390!regdb.bin took 0ms
[10144.502265] cnss: Failed to load BDF: qca6390/regdb.bin
[10144.502334] cnss2 b0000000.qcom,cnss-qca6390: Falling back to syfs fallback for: 14wlan.b0c
[10144.506635] ueventd: firmware: loading '14wlan.b0c' for '/devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0c'
[10144.506833] ueventd: loading /devices/platform/soc/b0000000.qcom,cnss-qca6390/firmware/14wlan.b0c took 0ms
I have the same errors with firmware regdb.bin for cnss mode. But as I can understand it doesn't affect monitor mode. I also don't have this file in my firmware folders.
But there is another error in your log that is very weird. It seems to be a reason of your problem. Pay attention to WCNSS_qcom_cfg.ini open error. This file should be placed in /vendor/etc/wifi/qca6390 and link to /vendor/firmware/wlan/qca_cld/qca6390.
You need to check if this file exists.
Related
Nethunter Kernel for Samsung Galaxy S7 Edge (SM-G935F/FD) Stock Oreo
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 only for hero2lte . If you have flat 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
Boeffla wakelock blocker v1.10
Wireguard
Enabled Netfilter Target TTL
rtl88xxau driver
rtl8188eus driver
Download:
Latest version G935F here.
Installation:
1. Flash latest TWRP twrp-3.3.0-1+ ( to see data partition with enabled disk quota)
1. TWRP Backup your ROM
2. Flash G935F_Nethunter_StockOreo_v*.img
3. Flash Universal DM-Verity, ForceEncrypt (You don't need to disable disk quota)
3. Flash latest Magisk 19.1+
4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs.
5. Install busybox
6. Install Magisk Nethunter module from repository
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/ OR system/bin/ and give permissions to it rwxr-xr-x
9. Reboot
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)
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 G930F_Nethunter_StockOreo_v*.img
2.1.Look at EXTRA.
3. Flash latest Magisk (Recommend 18.1+ version, 18.0 could make frezzes)
4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs.
5. Install busybox can be one from Magisk repository
6. Install Magisk Nethunter module from repository
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/ OR system/bin/ and give permissions to it rwxr-xr-x
9. Reboot
Loadable modules:
G935F_Nethunter_Modules_vX.X.zip extract only modules for your version of kernel.
In every kernel folder are modules and firmware. You need only modules which you want to use.
For example if you don't want use tuners and dvb-frontends. Don't load modules from /modules/drivers/media tuners and dvb-frontends
In firmware are compiled firmwares for some of modules to use they you need to copy they to system/etc/firmware.
basic commands:
insmod 88XXau.ko - load module
rmmod 88XXau.ko - unload module
lsmod - list loaded modules
Some modules depend on another modules. If you want load rt2800usb.ko, you need first load rt2800lib.ko.
Another way to load modules is Module Loader
Copy modules to storage and choose modules which you want to load (load they more than 1 times, this apk load modules from up to down it don't look at dependence from modules)
EXTRA:
1.If you want to have unencrypted data partition:
1.1. Format data partition(you lose your data).
1.2. After flashing kernel flash "remove encryption.zip".
1.3. Reboot to system (First start configuration wizard).
1.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"
}
XDA:DevDB Information
[KERNEL] [G935F] Nethunter for Stock Oreo ROM, ROM for the Samsung Galaxy S7 Edge
Contributors
Wirusx
Source Code: https://github.com/Svirusx/NetHunter-s7-kernel-StockOreo
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2019-02-05
Last Updated 2019-05-16
CHANGELOG
2020-12-06 - v1.5.1
Added loadable modules support
Update to Samsung source G930FXXS6ESI4
Enable Netfilter Target TTL
Added rtl88xxau driver
Added rtl8188eus driver
2019-05-16 - v1.4
Nethunter defconfig fixes
2019-04-20 - v1.3
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)
2019-02-25 - v1.2
Added missing drivers like SUNRPC, NFS v4 etc.
Added Boeffla wakelock blocker
Removed unnecessary drivers.
2019-02-05 - v1.1
Rollback encryption drivers.
2019-02-05 - v1.0
Initial release.
Reserved
First Question
The image file, howe install boot or recovery with twrp
GroBat said:
The image file, howe install boot or recovery with twrp
Click to expand...
Click to collapse
When you are in "Install Zip" and can choose zip in the bottom you can choose "Install Image". Than you need to choose Nethunter boot.img and choose in TWRP that is boot.img not recovery.img
Thanks I'm testing
:good:
Is this Kernel also for _alexandr ROM? It's pretty stock-like. Thank you.
After installing don't boot frezz directly on Superman Rom, work this with TGP Rom?
GroBat said:
After installing don't boot frezz directly on Superman Rom, work this with TGP Rom?
Click to expand...
Click to collapse
I use Stock Oreo ROM with this kernel.
This kernel is made from Stock kernel source and inserted in Stock boot.img.
You could try some possibilities:
First try:
If you have encrypted data partition than try flash this kernel and then Magisk 18.1.
If you have unencrypted data partition than flash it than remove encryption.zip and than Magisk 18.1 (remove encryption.zip)
If you want yet trying than:
If it doesn't work maybe it could work if you extract kernel from boot.img and insert in your boot.img kernel but it can be complicated and no warrianty it going to working...
If you have soo much time for testing than but if you didn't used it before backup is recommended:
You can also try too Dualboot patcher and flash Stock ROM and then this kernel i tested S7 kernel first at second ROM before flash it on main ROM.
I have Galaxy s7 Flat so Flat version is tested by me this one i can't test :/
This kernal work s9 port rom?
Randhir Kumar Yadav said:
This kernal work s9 port rom?
Click to expand...
Click to collapse
It's only for Srock Oreo but i'm busy with custom kernel which could working with s9 port rom.
I try install:
1. Install Firmware G935FXXS3ERLF(Odin)
2. Install TWRP
3. Install remove-encryption.zip
4. install no-verity-opt-encrypt.zip
5. Install Magisk-v18.1
6. Boot on android
7. Reboot on TWRP
8. Go to "Install" and select G935F_Nethunter_StockOreo_v1.1.img
9. select "boot"
10. Reboot
And that is all. Just hanging the Samsung logo and not boot
What have I done wrong? Or am I installing incorrectly kernel?
Thanks
Need to know that
johnua said:
I try install:
1. Install Firmware G935FXXS3ERLF(Odin)
2. Install TWRP
3. Install remove-encryption.zip
4. install no-verity-opt-encrypt.zip
5. Install Magisk-v18.1
6. Boot on android
7. Reboot on TWRP
8. Go to "Install" and select G935F_Nethunter_StockOreo_v1.1.img
9. select "boot"
10. Reboot
And that is all. Just hanging the Samsung logo and not boot
What have I done wrong? Or am I installing incorrectly kernel?
Thanks
Click to expand...
Click to collapse
after flashing TWRP
1.flash G935F_Nethunter_StockOreo_v1.1.img
2.Install remove-encryption.zip (You don't need to install no-verity-opt-encrypt.zip its is in remove-encryption.zip and it may make errors or override settings from remove-encryption.zip)
3.Now Reboot to system (Without magisk because magisk corrupts remove-encryption if is installed without reboot to system and in effect of that you get encrypted data partition.)
4. after first configuration wizard reboot to TWRP and install magisk 16.1
If this doesn't help you than you can try WirusMOD version (Oreo Nethunter kernel based on TGPKernel)
@Svirusx. I flash this kernel and
@Svirusx i flash this kernel on my Samsung galaxy s7 edge g935f.. The wifi, Hotspot and Bluetooth is not coming up...
harbdulahi said:
@Svirusx i flash this kernel on my Samsung galaxy s7 edge g935f.. The wifi, Hotspot and Bluetooth is not coming up...
Click to expand...
Click to collapse
Did you "4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs." ??
This looks like you haven't copied those libraries. Here is too in Magisk repository module which fix this problem.
Svirusx said:
Did you "4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs." ??
This looks like you haven't copied those libraries. Here is too in Magisk repository module which fix this problem.
Click to expand...
Click to collapse
Thank you very much it works like charm @Svirusx
No issue at all.... I want to ask pls is there any where I can get a good oreo stock Rom.. Because the one am using is draining my battery and fluctuating my cell network and have read about it that it the oreo version has cell standby issue and android system draining battery... Is there any one u recommend I should use... You reply will be very much appreciated. Thanks @Svirusx
harbdulahi said:
Thank you very much it works like charm @Svirusx
No issue at all.... I want to ask pls is there any where I can get a good oreo stock Rom.. Because the one am using is draining my battery and fluctuating my cell network and have read about it that it the oreo version has cell standby issue and android system draining battery... Is there any one u recommend I should use... You reply will be very much appreciated. Thanks @Svirusx
Click to expand...
Click to collapse
I use normal latest stock version downloaded by samfirm app from this forum.
If after flash new rom you get again this issue try factory reset.
harbdulahi said:
Thank you very much it works like charm @Svirusx
No issue at all.... I want to ask pls is there any where I can get a good oreo stock Rom.. Because the one am using is draining my battery and fluctuating my cell network and have read about it that it the oreo version has cell standby issue and android system draining battery... Is there any one u recommend I should use... You reply will be very much appreciated. Thanks @Svirusx
Click to expand...
Click to collapse
Hi I've uploaded my twrp backup of latest stock oreo rom with magisk, stock kernel and all functions working. No bugs. It's in S7E thread. Give it a try
gupt07ash said:
Hi I've uploaded my twrp backup of latest stock oreo rom with magisk, stock kernel and all functions working. No bugs. It's in S7E thread. Give it a try
Click to expand...
Click to collapse
Thanks man ??
---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------
gupt07ash said:
Hi I've uploaded my twrp backup of latest stock oreo rom with magisk, stock kernel and all functions working. No bugs. It's in S7E thread. Give it a try
Click to expand...
Click to collapse
@gupt07ash pls can you provide a direct link because am still new to xda thread and I don't want to download the wrong twrp backup....
---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------
harbdulahi said:
Thanks man
---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------
@gupt07ash pls can you provide a direct link because am still new to xda thread and I don't want to download the wrong twrp backup....
Click to expand...
Click to collapse
And also mind me am still a noob... Does the backup include the modem also? Pls I will be waiting for your reply and the download link... thanks
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS 16.0 for Samsung Note N7000
Beware, you are about to enter a dangerous zone!
ABOUT
This is an unofficial Pie build for the Galaxy Note (N7000) based on LineageOS 16.0.
Read the sections below carefully to understand the status of this ROM and how to prepare your device for installation.
CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.
INSTALLATION FROM STOCK
Follow these steps if you are coming from stock. You will need access to a PC.
1. Prepare Odin, Samsung USB Drivers, PhilZ CWM Odin Flashable, and your phone with a stable USB connection.
2. Install the Samsung USB Drivers and fire up Odin.
3. Select AP and choose the PhilZ CWM Odin Flashable package.
4. Proceed to flash. Once done, reboot your device into recovery.
5. You should be in CWM recovery now. Flash this zip to get TWRP IsoRec: 20210209-boot_n7000-twrp_i9100_3311.zip
6. Reboot recovery. You should now enter TWRP IsoRec recovery. Proceed to the installation steps below, except for step 2.
INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration:
- Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip - Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card (only in Android 7).This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired, or boot_magisk.img if you need Magisk support.
8. Prepare a coffee or tea and sit back on your couch. Click to reboot system, BUT DO NOT SWIPE TO INSTALL TWRP APP or you will end up in a bootloop!
9. Remember to install Magisk Manager if you need Magisk support.
DOWNLOAD
Google Drive
SOURCE
GitHub - leewp14/local_manifests at lineage-16.0
Contribute to leewp14/local_manifests development by creating an account on GitHub.
github.com
GitHub - hikuii/android_kernel_samsung_smdk4412: Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000)
Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000) - GitHub - hikuii/android_kernel_samsung_smdk4412: Samsung Galaxy S II (GT-I9100) / Samsung Galaxy Note N7000 (GT-N7000)
github.com
LineageOS 16.0
LATEST BUILD
lineage-16.0-20210211-UNOFFICIAL-n7000
kernel-e604934cd028ba34c8a52d6898658a2e6053ad8e (hikuii597)
magisk-v21.4
NOT WORKING/UNTESTED
- GPS/AGPS: untested, A-GPS not working
- DRM: untested
- IPv6: no connectivity
- Bluetooth: in-call audio not working
- WiFi: extremely reluctant to auto-connect
- Kernel: app requires restart to use storage after granting storage permission
- Kernel: random reboot freeze at offline charging
- Kernel: requires toggle MagiskHide on each reboot to enable MagiskHide
BUILD-SPECIFIC NOTES
- PowerHAL has been removed to provide flexibility in adjusting CPU governor.
INSTALLATION NOTES
- When prompted in TWRP, do not install TWRP Updater app as it will cause softbrick.
- To pass SafetyNet, you must use boot_magisk.img and toggle MagiskHide on every boot.
- Do not update Magisk! Always stick to the version that the build provides.
Changelog
20210211
- general: upstream updates, ASB 2021-02
- kernel: enable RPFILTER (fixes tethering)
- kernel: switch back to PegasusQ governor with hotplug enabled
- kernel: restore mali400 to stock configuration (166/266MHz)
OLD CHANGELOG
minors 20200809
- device: revert lineage-17.1 configuration changes
- device/kernel: enable zram at 384MB with dual stream compression
- kernel: revert lineage-17.1 binder changes
20200928
- general: upstream updates, ASB 2020-09
- frameworks/base: upstream updates
- kernel: revert lineage-17.1 changes, enabled swap (thanks to @goodwu for notifying)
20200809
- general: upstream updates, ASB 2020-08-05
- frameworks/base: ColorFade fix for exynos mali- device-related: merge lineage-17.1 changes from @rINanDO
20200614
- general: upstream updates, ASB 2020-06-05
- device: merge lineage-17.1 changes- device: remove PowerHAL- hardware: default video buffer size to 1080p- kernel: mali400 reconfiguration, use 133Mhz, 160MHz, 266MHz.- kernel: lock mali to 160MHz during 1080p playback- kernel: disable CPU hotplug- kernel: use interactive CPU governor- kernel: use 500MHz as base CPU frequency- kernel: reconfigure thermal throttling, refer commit- kernel: add TriangleAway support, refer commit- kernel: remove a whole big bunch of logging that your grandpa never check on it
20200417
- galaxys2-common: bring back PowerHAL
- kernel/galaxys2-common: added Lineage Trust USB Restrict support (untested)- kernel: cherry-picked Syncthing-Fork "NAT transversal" fix (credits to @TheNatureOne)- kernel: switch to autosuspend (full credits to @rINanDO and @ChronoMonochrome)
20200407
- n7000: update GPS configuration
- n7000: update build fingerprint- n7000/kernel: add TriangleAway support- galaxys2-common: reconfigure wifi configuration- galaxys2-common: user configurable SWAP- galaxys2-common: actually fix in-call audio control- galaxys2-common: kernel modules to system- galaxys2-common: add Magisk build support (credits to @rINanDO)- galaxys2-common/kernel: bring over LOS 17.1 commits (credits to @rINanDO)- kernel: implement charge current control (credits to @TALUAtXDA)- kernel: prevent LCD lock busfreq- kernel: reconfigure ASV/DVFS for BUS/GPU- kernel: remove inbuilt recovery- kernel: bring back PegasusQ, adapted from Perseus-S3 (credits to @AndreiLux)- kernel: raised safefreq to 1.4GHz- kernel: bluetooth stack update (credits to @TALUAtXDA)
20200205
- kernel: cherry-pick mali400-r3p2-rel4 (don't expect anything from this!)
- kernel: disable modules support, KSM, LZ4 ZRAM and many other unnecessary stuffs- kernel: added GCC optimization flags, build kernel with -Ofast- kernel: a whole lot bunch of changes which is too much to be listed here- kernel: default CPU governor to OnDemand- kernel: modify CPU frequency steps back to 6steps- kernel: modify GPU (mali400) to 2steps, 190MHz and 267MHz- kernel: increase lowest busfreq from 160MHz to 190MHz- kernel: increase display frequency from 57Hz to 59.94Hz- kernel: decrease video engine clock from 267MHz to 190MHz- kernel: decrease shared GPU memory from 512MB to 256MB, increase GPU low-level memory to 24MB- kernel: slightly-slightly tune throttling configs, first throttle to 1200MHz, second throttle to 1000MHz- kernel: bring back FB_BLANK- kernel: adjust CONFIG_HZ to 300- kernel: add/enable exFAT, NTFS support- galaxys2-common: remove PowerHAL- galaxys2-common: revert use low-end video codecs- galaxys2-common: update whole bunch of framework configs- galaxys2-common: disable wifi adapter debug- galaxys2-common: more platform specific gcc optimization flags- galaxys2-common: fix USB info configuration- galaxys2-common: build libsecril-client- galaxys2-common: decrease ZRAM to 128MB- galaxys2-common: enable AOD (Always-On Display)- galaxys2-common: actually make macloader works- galaxys2-common: modify healthd to blank screen first before power off or reboot attempt in offline charging mode- n7000: rework GPS configuration (don't expect anything from this!)- vendor/samsung: add prebuilt si4709 FM driver- general: upstream source updates, security patch 2020-02-05
20191009
- kernel: panel brightness optimization from i9300
- kernel: adjust unified memory allocation size- kernel: disable logging- kernel: disable pegasusq core lock- kernel: switch to ZEN I/O scheduler- kernel: fix tuning table for Q1 (credits to rINanDO)- kernel: misc source updates from rINanDO, ChronoMonochrome, ComicoTeam- galaxys2-common: remove SamsungDoze- galaxys2-common: use low-end video codecs (credits to ChronoMonochrome)- galaxys2-common: make sure burn-in protection is enabled- galaxys2-common: wifi hotspot channel 1-11 instead of 1,6,11 only- galaxys2-common: platform specific gcc optimization flags- galaxys2-common: lower haptic feedback intensity- galaxys2-common: dual-speaker output implementation (back speaker + earpice speaker)- galaxys2-common: fix RIL PIN unlock (credits to rINanDO)- galaxys2-common: misc source updates from rINanDO- n7000: increase minimum adjustable brightness threshold- n7000: fake vendor security patch level- n7000: conditionally reset max17041 fuel gauge on boot- hardware/samsung: added missing OUI mapping [SEMCO - 50:cc:f8] (credits to J..J)- general: upstream source updates, security patch 2019-09-05
20190522
- Removed LTE network option in Settings
- Fixed GPS and RIL functionality- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)- New cursor icon for stylus (thanks to ComicoTeam)- Added xt_hl support in kernel
20190505
- Initial build
- Exclude RIL and GPS blobs due to non-working RIL and GPS
Hello,
We will have Android Pie on N7000 !!!!
Great and thank you !!!
I will buy a new battery for my Note I think.
Oh my god!
Got my N7000 out of the closet and charging it right now! Gonna flash this right away!
Thank you, @lee.wp14
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
[email protected] said:
@lee.wp14, it works! It actually works great!
I am not having any connectivity problems with WiFi and bluetooth detection seems to be working fine.
I just have one question, when in TWRP, I can see two partitions, Emulated Storage and Non Emulated Storage.
But once in Android, I can only see Emulated Storage, the Non Emulated Storage seems to be completely missing. Any way I can fix that? Or better, merge both the partitions (not sure if that would though)?
Click to expand...
Click to collapse
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
lee.wp14 said:
Non-Emulated storage is not mounted in android, so it won't appear (this is a expected behaviour). I'm not sure if we can actually have 3 storage at once. With repit script we can't delete partitions thus with the sdcard=min parameter the sdcard will be resized to a minimum of ~7mb, and this partition is being removed from the fstab in kernel.
Click to expand...
Click to collapse
I see, thank you for this information.
I will try repartitioning in the next build.
Right now, the ROM is working great!
GREAT! I am eager to try it as soon the RIL works! (still using this ancient phone as a backup)
Release 20190522
CHANGELOG
20190522
- Removed unused LTE network option in Settings
- Fixed GPS and RIL functionality
- Fixed QS Flashlight 10 seconds wakelock issue (thanks to ChronoMonochrome and rINanDO)
- New cursor icon for stylus (thanks to ComicoTeam)
- Added xt_hl support in kernel
Notes:
- Be patient when the phone is booting up, if you have a sim lock, wait a while before entering the PIN because telephony stuffs might still be loading. You will get SIM unlock failed error if the telephony stuffs are not loaded finish yet. We are using a 2018/2019 Android on a 2011 phone, be patient
- GPS is tested OK personally by me prior to this release. If you can't get a fix or detect any satellites, make sure your GPS antenna connection is ok.
- Due to upstream changes, we are currently using Autosleep driver to let the phone enter a suspend state (doze). A shorter standby time should be expected.
- Builds are not SafetyNet OK and also not pre-rooted. If you want root, you may flash the addonsu package from LineageOS's website.
- Builds have signature spoofing enabled by default (thanks to rINanDO), you may take advantage of this to replace GAPPS with MicroG.
- This build is tested OK with GAPPS (pico ARM 9.0), please expect a longer boot time if GAPPS is installed.
- I'm not sure why, but earlier before this after I made some changes in the sources, the USB dialog won't show in Notifications panel anymore. To change USB operating mode, go to Settings > Connected Devices > USB
Quote:
1. Make sure you have at least a working TWRP 3.x IsoRec on your device. If no, proceed to bauner's LOS13.0 thread for installation steps.
2. Flash this recovery by rINanDO: TWRP-3.1.0-EMU-MIGRATION-M-20170318-noassert.zip (under directory n7000/misc/recovery)
Unquote
That means I need to flash TWRP twice from stock recovery?
John Moore said:
That means I need to flash TWRP twice from stock recovery?
Click to expand...
Click to collapse
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:
> If you are from stock ROM
1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
> If you are from Custom ROM
1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
lee.wp14 said:
Yes and No. Yes, you need to flash TWRP twice (one is normal TWRP and another is emulated storage compatible TWRP), but No, not from stock recovery. If you are from stock, you need to flash a custom kernel first which has the prebuilt CWM recovery. We cannot flash normal ZIPs under stock recovery, we will need a custom recovery like CWM and TWRP to flash ZIPs.
To make things clearer, here is a detailed list on instructions to prepare for it:
> If you are from stock ROM
1. Flash this kernel (with CWM prebuilt recovery) using Odin: PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5
2. Reboot device to recovery. Flash this IsoRec-compatible kernel from bauner: Nightowl-lineage13-20171029-n7000-kernel_only.zip
3. After that, flash this TWRP IsoRec recovery from bauner: recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot recovery. You should now have a working TWRP 3.x IsoRec Recovery. Proceed from Step 2 below in section "If you are from custom ROM".
> If you are from Custom ROM
1. Do you have a TWRP 3.x IsoRec Recovery? If no, then go back to Step 2 in above section "If you are from Stock ROM" to get a working TWRP 3.x IsoRec Recovery.
2. Reboot recovery. You may now proceed starting from Step 2 in the instructions written in OP.
Click to expand...
Click to collapse
Thanks very much, Lee.
I Can't boot to twrp 3.1.0 EMU Migtation
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp
Stuck and reboot again in logo
Please help me
Zin Bo said:
I can install and boot to TWRP 3.x IsoRec Recovery,
But after installing Twrp 3.1.0 EMU Migration
i can't boot up into that twrp
Stuck and reboot again in logo
Please help me
Click to expand...
Click to collapse
Can you reconfirm the situation and possibly list out your procedures?
lee.wp14 said:
Can you reconfirm the situation and possibly list out your procedures?
Click to expand...
Click to collapse
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery
Then flash twrp 3.1.0-isorec.zip and reboot into recovery
And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)
So i start doing step-2( that you tell for n7000 pie rom installation )
I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)
So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.
Can't go to Twrp
Thank for your reply.
Zin Bo said:
First, my n7000 is in Stock rom.
I flash Philz-cwm recovery.tar with odin and boot into recovery .
And then I flash Nightowl-lineage13-kernel.zip with philz-CWM. And reboot into recovery
Then flash twrp 3.1.0-isorec.zip and reboot into recovery
And Twrp3.1.0-isorec is working fine (but i can't boot to stock rom)
So i start doing step-2( that you tell for n7000 pie rom installation )
I flash Twrp 3.1.0 EMU-Migration--noassert.zip from Twrp3.1.0 isorec(installation complete, done!)
So, I reboot into recovery again.
But then,loop in samsaung logo - boot again and again.
Can't go to Twrp
Thank for your reply.
Click to expand...
Click to collapse
Can you flash back to stock to make sure everything is still OK and repeat the procedures again and stop before the step of flashing the twrp emu isorec.
Instead, extract the boot.img from the rom zip and copy to phone (you can do it using TWRP usb mtp) or sdcard, inside TWRP choose inage flash mode, and flash the boot.img to Boot partition.
Next restart to TWRP again. If you can go into twrp then you may try flashing the twrp emu isorec. See if it works this time.
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^
dclou said:
Dear Lee.wp
Thank you for the contribution to PIE ROM...
Could you please let us know, whether this ROM is OK to use Magisk or not?
Appreciate the reply from you in advance...^^
Click to expand...
Click to collapse
Galaxys2/n7000 won't support magisk as our kernel 3.0.101 does not support namespace, which is required for magisk to operate.
Is this ROM Treble based?
TeamWin Recovery Project
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
TWRP is FREE SOFTWARETwo versions: for RUI1 (Android 10) and for RUI2 (Android 11)
Features:
• Fastbootd is working;
• Decryption is working
• Using custom themes and fonts (special thanks to [email protected])
• Added custom patches in the Advanced settings (special thanks to [email protected]):
- SafetyNet fix patch
- Google Pay fix patch
- Patch for mount System and Vendor as r/w
• AVB2.0 (vbmeta) disabling special (thanks to [email protected] for his patch)
• Fix stock .ozip installation
• Patch to conversion of dynamic partitions to r/w (special thanks to @lebigmac for his script. Original thead)
• Patch to fix Magisk on RUI2
Download:
From Google Drive https://drive.google.com/drive/folders/1xerR8NmCNEoR1afh4dfbyrLz0ZOuWZPp?usp=sharing
Spoiler: Screenshots
Spoiler: Guides
Spoiler: Convert any ROM to r/w
How to convert ROM to R/W
The process below describes how to transfer the entire firmware to R/W (the ability to change/delete/add files in the system partitions: system, vendor and others ..).
All actions are carried out in TWRP itself i.e. on "live".
Your data is not affected.
Required for a successful conversion:
* free space on the internal memory of at least 25GB.
* charged battery (preferably at least 40%)
The process itself is not complicated:
1. Make
backup a Super partition (optional)
2. Go to the "Advanced" section and select "Convert ROM to RW".
3. In the next window, confirm with a swipe.
4. That's it, we are waiting ... about 5 minutes ...
5. After all the actions, the device will reboot itself into the system ...
6. Go to the explorer with root rights and delete the /data/local/tmp/makesysrw_[version] (/data/media/makesysrw_[version] for Android 11) folder, or do it in the TWRP explorer
To access the system partitions, respectively, you need root rights and a file manager with the ability to mount partitions in r/w.
The test was conducted on RealmeUI 1 A.45 and RealmeUI 2 C.15. But there is no difference, it is possible to convert any Android 10-11 ROM to r/w.
Changelog - current version (Android 11):
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
INSTALLATION
via TWRP-based recovery:
Download the TWRP IMG file to your device
Reboot to your custom TWRP-based recovery
Install the TWRP img file as image in recovery partition
Reboot into recovery after installation
Enjoy!
via fastboot:
Download the TWRP IMG file to your PC
Reboot your device to fastboot mode
Install the TWRP image with command:
Code:
fastboot flash recovery [image name].img
Reboot to recovery with the command:
Code:
fastboot reboot recovery
Enjoy
Notes:
• Installation of OTA packages not working
• ADB doesn't work in fastbootd mode only
CREDITS
• TeamWin - for TWRP
• brigudav - for his TWRP customization
• @lebigmac - for his makeSystemRW script
Version Information
Status: Stable
Current version: 3.5.2_10-1 (Android 10) / 3.5.2_1011-3 (Android 11)
Created 2021-03-18
Last Updated - 2021-09-03
CHANGELOGS
Spoiler: Android 11
Spoiler: 2021-09-03 (3.5.2_1011-3)
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
Spoiler: 2021-05-03 (3.5.2_1011-2)
• Fixed the installation of some ROMs
• Fixed fastboot (it was broken in the last build)
Spoiler: 2021-05-01 (3.5.2_1011-1)
• Disabled non-working patches in the Advanced section
• Enabled the install/remove Magisk feature in the Advanced section
• Added a boot repackaging patch with an oplus.fstab fix for Magisk (now after applying this patch, Magisk booted correctly on RUI 2)
• A small fix under the hood
Spoiler: 2021-04-29 (3.5.2_1011-0)
• Initial build
Spoiler: Android 10
Spoiler: 2021-04-23 (3.5.2_10-1)
• Universal patch disabling vbmeta by [email protected] (thanks to him for the patch)
• Now the internal storage after formatting /data is available without rebooting
• Minor changes in device tree (some libs are now taken from sources, small changes in the fstab, unnecessary system.props and flags are removed, edits in translation)
• Updated and fixed the script for converting firmware to R/W (now temporary files are deleted automatically when the conversion is successful)
• Added logcat copying
• Updated magisk to Canary 22104 (21) in which the SafetyNet check works correctly.
• Languages: Added Indonesian language [android_bootable_recovery]
• Change the missing logical partitions from LOGERR to LOGINFO [android_bootable_recovery]
Spoiler: 2021-04-05 (3.5.2_10-0)
• The list of Firmware-Update partitions for backup is finally changed (It is recommended to delete old "Firmware" backups and make new ones #2)
• Fix a regression error for digest checking [android_bootable_recovery]
Spoiler: 2021-03-30 (3.5.1_10-1)
• Added conversion of dynamic partitions to r/w (see Guides). Special thanks to @lebigmac for his script. Original script thead
• In the Mounting settings you can now mount System and Vendor r/o and r/w (if the partitions are in r/w). Taken fromTWRP by brigudav for Poco X3
• Returned the reboot menu from TWRP 3.3.x. Taken from TWRP by brigudav for Poco X3
• Changed the list of partitions for Modem backup. It is recommended to delete old backups and make new ones
• Changes in languages
• Other changes under the hood
Spoiler: 2021-03-18 (3.5.1_10-0)
• Initial version
Reserved
Can i use this recovery for Flash Android 11 custom roms?
Ayushmak said:
Can i use this recovery for Flash Android 11 custom roms?
Click to expand...
Click to collapse
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2
Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com
Yes you can install it... 'cause i would try.. on RR rom
Zgadnijcie said:
Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com
Click to expand...
Click to collapse
All Android 10 Custom ROMs based on RUI1. Yes, you can install TWRP
Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the official project thread
lebigmac said:
Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the
Click to expand...
Click to collapse
Hi, I took this patch from TWRP by brigudav. I didn't find any mention of the creators anywhere other than brigudav, just "Make System to RW for Poco X3". I am always for the preservation of copyright and always indicate the developers of the program. I apologize to you for not finding your original official project thread. I would like to use your script for my recovery, of course, with the condition of saving the author and specifying a link to the original post...
Ctarchik please feel free to use latest version of my script in your project. The more people have system r/w access the better for the open source community.
@brigudav rather than hacking my update-binary and replacing my program's title (!!!) with your own meaningless words and torturing my script's comments section by modifying and removing the original script name, original author name, original version, link to original project homepage, disclaimer, credits, manual and automatic installation instructions, usage examples, (and much more...) I would suggest to try to improve the underlying algorithm of the script itself. And NO that does NOT mean simply renaming my variables and my functions and changing their order as well as injecting your bogus useless function that does absolutely nothing (...)
Please don't be such a lazy ruthless hacker without any morals or respect! Thank you! You have been caught red handed as a cyber thief and now the only right thing to do is to admit your guilt, beg for pardon and STOP IT! Please stop stealing my work and releasing as your own okay? That's just very very wrong on so many levels!
I clearly stated in my disclaimer that by using my script you agree to not abuse my work for criminal illegal purposes. And what you're doing is a perfect example of copyright infringement as well as intellectual property theft which is illegal even in Russia. Don't forget that!
Can you mod this twrp so I can use external sdcard to backup?
Thank you!
Super Partition backup fails when using FAT32 stick (exFAT works) · Issue #143 · TeamWin/android_bootable_recovery
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com
Ctarchik said:
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2
Click to expand...
Click to collapse
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11
beaker2 said:
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11
Click to expand...
Click to collapse
Yes, it is. I just shortened RealmeUI to RUI
The problem I have been having is when I previously installed TWRP on my phone using ADB to install- patched_vbmeta-2 and then TWRP. I could reboot from ADB into recovery to TWRP, but then when I tried to reboot into system I was in a boot loop and phone would only go back to the stock recovery . Then I had to re flash the stock rom to get out of the boot loop and be able to boot into system again.
So can I do the same install from ADB as before but when I reboot , from ADB, into TWRP then I can install this TWRP then I can have the ability to boot into the stock ROM system . Then I could go to recovery and TWRP will still be there so that I could install a custom ROM ?
Thanks in advance, I'm a noob with this phone and its partitioning
Well, I tried the installation described above, installed TWRP from ADB then when booted and rebooted into TWRP and flashed this version of TWRP, seemed fine no errors BUT... the phone just returned to the stock recovery .
Then I tried exactly as described in this thread no error message and all seemed to go smoothly BUT... The phones internal memory was unreachable from any file manager or computer and the stock recovery returned not TWRP. Had to re-flash the phone several times, 1. stock recovery 2.from update 3.from flash tool, to finally get the internal phone memory visible again.
My phones build number is RMX2061_11_A49. Has anyone successfully installed TWRP on this build ?
How?
1. Prevent replacing TWRP:
Flash this file in Advanced Menu in the first time you go in TWRP.
2. Decrypt userdata: do them in order
- Flash this file:
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
- Wipe / Format Data / yes
- Reboot to TWRP again
- Advanced / Fix AVB
- Reboot to System
Done!
P.S.: You will lost all data after this.
No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery
beaker2 said:
No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery
Click to expand...
Click to collapse
Try flash magisk before reboot system
nttuan said:
Try flash magisk before reboot system
Click to expand...
Click to collapse
I gave up and installed Magisk 23 and rooted. I just decided to live with the stock rom (debloated) and the stock recovery
Please find here my notes on the full configuration of a Redmi 7a.
I feel that these informations are generally very scattered, someone like me who didn't follow these topics for a few years may have a hard time getting back into the loop. I hope this guide will help others to quickly get a grip.
Note that I use Linux, so the Unlock part might be interesting for that. Windows users can still follow this guide but may need the official tool for the bootloader unlock and different drivers and tools to interact with the phone.
My configuration is rather intended to use a maximum of open source and securitized applications but with a door slightly open to applications requiring the Google framework.
WARNING : ALWAYS BACKUP, THIS GUIDE IS NOT INTENDED FOR UPDATES, BUT FOR A FULL FORMATTING SETUP.
XIAOMI REDMI 7A (PINE SDM439) : from locked Stock MIUI to Custom LineageOs 18.1 with microG and Gcam
Unlock the Bootloader and install a Custom Recovery (for linux)- [Android + Linux] Unlock your Xiaomi Device Bootloader : https://github.com/tkapias/XiaoMiToolV2
- [Linux] Dowload the SDK Platform Tools (ADB, Fastboot ...) : https://developer.android.com/studio/releases/platform-tools
- [PC] Download you current Stock Recovery ROM (Careful with the region): https://mirom.ezbox.idv.tw/en/phone/
- [PC] Patch your boot.img after extracting it from the Stock ROM : https://github.com/YaAlex3/patcher-oss
- [PC] Extract vbmeta.img from the Stock ROM
- [PC] Download PBRP zip and img, the best Custom Recovery : https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_pine-pbrp/releases/
- [Android + Linux] Copy boot.img, recovery.img and vbmeta.img to your phone
- [Fastboot] Reboot in Fastboot and flash :
fastboot flash boot boot.imgfastboot flash recovery recovery.imgfastboot flash vbmeta vbmeta.imgfastboot boot recovery.img- [Custom recovery] Boot in recovery and Flash the zip of PBRP
Unofficial LineageOs 18(Performance, Open sources, noGapps)
- [Linux] Download the last zip release of the Unofficial LineageOs 18.1 (Android 11 64bit) : https://github.com/TTTT55/Lineage-OTA/releases
- [Custom recovery] Wipe: system, data, cache, vendor
- [Custom recovery] Format: data
- [Custom recovery] Flash ROM Zip
- Reboot
Root, Kernel, Drivers...- [Custom recovery + Android] Root by installing the latest Magisk :
- Try the custom recovery method first : https://topjohnwu.github.io/Magisk/install.html#custom-recovery- Download the Magisk APK : https://github.com/topjohnwu/Magisk/releases- Rename the .apk file extension to .zip- In Custom recovery, flash the zip- Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.- In Magisk check that yours is > v24.0 with [Zygisk], it replace the Riru module to install Gapps later.- [Custom recovery] Flash the latest Cherry Kernel in Recovery (then wipe Dalvik) : https://t.me/s/CherryKernel_SDM439
- [Magisk] Install Adreno Team Graphics Drivers with Magisk([M] 4.2+) : https://drive.google.com/drive/folders/1sizBYMR40G8cF8c0SatGLqpOrbML0tPb?usp=sharing
- [Custom recovery] Flash the Cache Cleaner addon from the Team Graphics Addon Directory.
- [Magisk] Install the magisk module "Color accuracy preset for Redmi 7A" : https://t.me/AkiraLostSushi/30
- [Magisk] Install the magisk module "MagiskHide Props Config" : https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases
[WARNING] [Magisk] The sepolicy.rule file of modules may be stored in the cache partition. DO NOT MANUALLY WIPE THE CACHE PARTITION from this point, or rebuild the rules after :
susource /data/adb/magisk/util_functions.shcopy_sepolicy_rulesreboot
F-Droid in root- Install the official F-droid apk : https://f-droid.org/F-Droid.apk
- In F-droid install the F-Droid Privileged Extension
- [Custom recovery] Flash the zip org.fdroid.fdroid.privileged.ota...zip in /data/data/org.fdroid.fdroid/ota/
Custom Webview(UpToDate, AdFilter, more privacy)
- [Android] Download the last Bromite SystemWebView : https://www.bromite.org/system_web_view
- [Custom recovery] Use the file manager to copy the Bromite SystemWebview apk to /system/product/app/webview and rename it as webview.apk
- [Custom recovery] make sure the permissions of webview.apk are 0644 (should be by default)
- reboot phone
- [Android] install the Bromite webview.apk file as you would for any other app
- Once the installation is complete it will be possible to update the SystemWebView without root.
- If your have installed the Root privilege app for F-Droid :
- Add the Bromite repository to F-droid :- Address: https://fdroid.bromite.org/fdroid/repo- Fingerprint of the signing key: E1EE5CD076D7B0DC84CB2B45FB78B86DF2EB39A3B6C56BA3DC292A5E0C3B9504- You can update from F-droid.
Install NL Sound & Viper4Android with Magisk(change all the audio framework ant effects engine)
- Install Package Manager and Termux from F-droid
- Disable or uninstall AudioFx in Package Manager
- [Magisk] Install the module “Audio Modification Library” : https://zackptg5.com/android.php#aml
- [Magisk] Install the module “NL Sound” : https://github.com/Briclyaz/NLSound_module_QCom (Zip it or from Telegram)
- [Magisk] Install the module "ViPER4Android FX" : https://zackptg5.com/android.php#viper
- Reboot
- Open Viper4Android, follow the prompt to install the driver, or install them from : https://zackptg5.com/android.php#viper
- Reboot
- In Termux, install root packages :
pkg install root-repo && pkg upgrade- In Termux :
susource /data/adb/magisk/util_functions.shcopy_sepolicy_rulesreboot- After the reboot open Viper4Android and switch on the Legacy option.
- Reboot
- Check the driver status in the second icon on the top in V4A
- Activate "Master limiter", "Gain control", "Speaker optimization"
- Disable battery optimization for the app in android
Install microG with Magisk(Minimal Google framework to use Gcam and some apps from Aurora store)
- [Magisk] Install modules "Zygisk - LSPosed" : https://github.com/LSPosed/LSPosed/releases
- [LSPosed] Install the module "FakeGapps"
- [LSPosed] In FakeGapps, check that the recommanded app for subsystem is checked
- [Android] Add a file /data/adb/no_droid_guard with any content (it disables the installation of Droid Guard)
- [Magisk] From Magisk Modules, install "microG Installer Revived" : https://github.com/nift4/microg_installer_revived/releases
- [LSPosed] From F-droid, install "Aurora Store"
Tweak the network settings for a better roaming and latency- [APK] Install KTweak : https://github.com/tytydraco/KTweak-Android-App/releases/tag/build-2dd09c9_1639707532
- [KTweak] Give it root acces, restart on boot and use its "throughput" profile.
- [DNS] Activate AdGuard DNS : Go to Settings → Network & internet ( or Wi-Fi & Internet), Select "Private DNS provider hostname" option and enter the following address: dns-unfiltered.adguard.com
- [Props] In Termux:
su
settings delete system tether_entitlement_check_state; settings delete global tether_dun_required
props
- "Select an option below." → "Add/edit custom props" 5 ↵
- Select "New custom prop" with n ↵
- net.tethering.noprovisioning ↵ → true ↵ → y ↵
- "Do you want to reboot now?" n ↵
- Select "New custom prop" with n ↵
- tether_entitlement_check_state ↵
- "Are you sure you want to proceed?" y ↵ → 0 ↵ → y ↵
- "Do you want to reboot now?" n ↵
- Select "New custom prop" with n ↵
- tether_dun_required ↵ → 0 ↵ → y ↵
- "Do you want to reboot now?" → y ↵
Custom Gcam(Keep the stock camera app for fast results, Gcam is for quality HDR+)
- You need to install microG first
- Prefer 7.2/7.3/7.4 versions.
- Prefer Nikita or urnyx05 releases :
- https://www.celsoazevedo.com/files/android/google-camera/dev-Nikita/- https://www.celsoazevedo.com/files/android/google-camera/dev-urnyx05/- My favorite : GCam_7.3.018_Urnyx05-v2.5 https://www.celsoazevedo.com/files/android/google-camera/f/changelog1500/
- I uploaded my configs XML : https://www.celsoazevedo.com/files/android/google-camera/f/configs-urnyx-02/
List of favorite additional apps
F-Droid- FFUpdater (Install and update Browsers)
- Firefox Nightly (My addons collection: 17173754/tkacomplete, see Mozilla blog)- DAVx5 (Sync CalDav and CardDav)
- Element (Matrix messaging)
- FairEmail (Email)
- Identiconizer! (Contacts pictures)
- KeepassDX (Passwords - sync with Syncthing)
- Lemuroid (Game emulation)
- Librera Reader (PDF, Books, Comics...)
- LibreSpeed (Open source speedtest)
- Markor (just for quicknotes, sync with Syncthing)
- Material Files (File explorer)
- MinCal Widget (Calendar widget)
- mpv-android (Player)
- NewPipe (Youtube player)
- OsmAnd+ (Maps)
- Package Manager
- QR & Barcode Scanner
- SimplyTranslate Mobile (Google translate with privacy)
- Syncthing (to sync files)
- Task.org (Task in CalDav)
- Telegram (Messaging)
- Termux (A better terminal)
- Wireguard (VPN client/server)
- XBrowserSync (Sync bookmarks)
Aurora Store- Device Info HW
- Spotify (Music)
Thanks, your concise guide helped me a lot, makes it really easy. Should be pinned somewhere at the top
Thank you Tupolef. I have found your instruction set very helpful and modified my 7A thanks to you.
Hi, thank you for this guide. I am a newbie at modding, and I don't have any idea how to have a Linux environment. Is there any chance I can send you my boot.img and ask you to patch it for me?
I can send you files I used but you need only python and the script from the link listed in the instructions. where to upload them?
Hi,
I hope this is helpful, I have updated the post regarding 3 points:
Magisk no longer offers the modules directly from the Magisk app, you have to download them yourself. So I put the links where they are needed.
Magisk since version 24.0 offers Zygisk, a feature that replaces the Riru module. LSPosed now offers a Zygisk version, no more need for Riru. I changed the links.
I added a section about network improvement, through DNS and Kernel settings with KTweak and Props. I really saw a difference.
There is still a problem, the fact that there is no update for the release that I had chosen at the beginning for the moment: https://github.com/TTTT55/Lineage-OTA
I may try to update to another release with the same bases to see but for the moment I stay on this version.
lyleflyle said:
Hi, thank you for this guide. I am a newbie at modding, and I don't have any idea how to have a Linux environment. Is there any chance I can send you my boot.img and ask you to patch it for me?
Click to expand...
Click to collapse
You can patch boot.img on Windows too.
Install python3 and 7-zip :
- https://www.python.org/ftp/python/3.10.4/python-3.10.4-amd64.exe
- https://www.7-zip.org/a/7z2107-x64.exe
Download a copy of Patcher-Oss :
- https://github.com/YaAlex3/patcher-oss/archive/refs/heads/main.zip
Extract main.zip in a folder and put your boot.img in the same folder, where main.py is.
Open a command prompt or powershell under windows and go to this folder with the "cd" command. Then run the script main.py with the command :
Code:
python3 main.py boot.img
Tupolef said:
You can patch boot.img on Windows too.
Install python3 and 7-zip :
- https://www.python.org/ftp/python/3.10.4/python-3.10.4-amd64.exe
- https://www.7-zip.org/a/7z2107-x64.exe
Download a copy of Patcher-Oss :
- https://github.com/YaAlex3/patcher-oss/archive/refs/heads/main.zip
Extract main.zip in a folder and put your boot.img in the same folder, where main.py is.
Open a command prompt or powershell under windows and go to this folder with the "cd" command. Then run the script main.py with the command :
Code:
python3 main.py boot.img
Click to expand...
Click to collapse
Got it. Thank you for the quick response.
BTW, what launcher do you use guys? I just last week tried Kvaesitso and I find it perfect. If you haven't yet - try it.
MariusSays63 said:
BTW, what launcher do you use guys? I just last week tried Kvaesitso and I find it perfect. If you haven't yet - try it.
Click to expand...
Click to collapse
Currently using pixel launcher. I’ll have to try Kvaesitso
Hi,
I have been using stock lineage OS for the past 2 days and it performs amazing. I have installed magisk and flashed the cherry kernel along with the adreno drivers. However, it seems like I have been experiencing lags and stutters in overall navigation since. Is this normal? Should I wait for a brief period before it performs optimal again?
FWIW: I haven't installed cherry kernel neither adreno drivers and I'm happy with stock lineage performance as it is.
MariusSays63 said:
FWIW: I haven't installed cherry kernel neither adreno drivers and I'm happy with stock lineage performance as it is.
Click to expand...
Click to collapse
I was quite curious on how it will perform with Cherry Kernel. I, too, was fully happy with stock lineage. Do you have any idea if the kernel will be back to stock if I re-flash the lineage ROM?
>>Do you have any idea if the kernel will be back to stock if I re-flash the lineage ROM?
I'm pretty sure you will reinstall the kernel and drivers in this case. Play with it
Personally, I've been on this configuration for 5 months and I have no lags.
I use this device to receive important notifications from many apps and as a backup hotspot. Sometimes some web browsing or audio stream with NewPipe or Spotify, but no games. I only have 2 widgets for calendar and tasks, and I always close the apps I don't use.
The only downside is that the Gcam apps are all very buggy or slow with this device, I ended up switching back to the LineageOs app. Apparently LineageOs 19 switches to Camera2, I will try to install it on the 18.1.
{
"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"
}
Tupolef said:
Personally, I've been on this configuration for 5 months and I have no lags.
I use this device to receive important notifications from many apps and as a backup hotspot. Sometimes some web browsing or audio stream with NewPipe or Spotify, but no games. I only have 2 widgets for calendar and tasks, and I always close the apps I don't use.
The only downside is that the Gcam apps are all very buggy or slow with this device, I ended up switching back to the LineageOs app. Apparently LineageOs 19 switches to Camera2, I will try to install it on the 18.1.
View attachment 5600453 View attachment 5600455
Click to expand...
Click to collapse
FWIW I tried few Gcams and stuck with MGC 8.1.101.345618084 but sluggish saving pictures but all functions seem to work. Also Kvaesitso works great with it as I have mentioned. This is my personal phone, I don't even have data just pay as you go as I have work phone but wanted something cheap but with good specs for its cost so I can tinker with and 7A was a great choice back then and still is.
First of all, thanks a lot for this guide!
One information + 2 questions:
1) Info: unlocking the bootloader is no longer possible on linux, even with recent patches to the XiaoMiToolV2. See the thread under that tool. I was able to do it on Windows however using the official Xiaomi tool.
2) Question 1: after I have flashed PBRP I cannot boot into it from fastboot. "fastboot boot ./recovery.img" sends the image and says "booting OKAY" but nothing happens, the phone remains in fastboot. I have to deconnect from the PC and go to PBRP manually by long pressing vol up + power. Has anyone come across this? I have tried several times, even going fully back to stock, installing PBRP anew etc., it is repeatable. Also, with my old Redmi 4A there is no such problem, I can boot into my custom recovery from fastboot. Does it have any repercussions?
3) Question 2: I'm trying to install crDroidAndroid-12.1-20220617-Mi439-v8.6.zip. I wipe and flash with PBRP, no errors. But it soft-bricks the device, only fastboot comes up afterward and I have to flash stock again... Does anyone here have experience with crDroidAndroid-12.1-20220617-Mi439-v8.6.zip? Thanks!
Just an update with respect to what I wrote here yesterday: today, following _almost_ this same process, I was able to start the phone with a custom ROM today. Only 2 differences:
-This time I formatted data in PBRP (not just wipe); not sure this matters however, since output always says "formatting data"?!
-This time I flashed crDroidAndroid-11.0-20220318-pine-v7.16.zip. I can really recommend this ROM by the way!
bunchofdutch said:
Just an update with respect to what I wrote here yesterday: today, following _almost_ this same process, I was able to start the phone with a custom ROM today. Only 2 differences:
-This time I formatted data in PBRP (not just wipe); not sure this matters however, since output always says "formatting data"?!
-This time I flashed crDroidAndroid-11.0-20220318-pine-v7.16.zip. I can really recommend this ROM by the way!
Click to expand...
Click to collapse
Thanks for the information about XiaoMiToolV2.
For that and the boot, I'll update in a little while, I plan to reinstall the device with the new LineageOs within the month.
I will update this post and answer you more extensively.
---
Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
Which GApps would you suggest?
I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.
Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.
I've set the state of the development to BETA due to quite good overall performance.
After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.
I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0
I'll take a look into it asap. Please be patient.
I can't find any reason for the crash; I'm sorry.
New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.
New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2
Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.
New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022
Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?
kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?
Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check
Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..
Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.