Develop Bugs

[CLOSE] Project Treble For F8132

Project Treble For F8132
Based on Sony Open Devices​if you mess up re-partitioning your device, you will end up with a HARD BRICK. Nobody can help you then.
NOTICE: This method is only available for F8132!!!​The required documents:
V1.2: MEGA With:SW_binaries_for_Xperia_Android_9.0.6.3_r1_v2_tone_beta.zip
V1.0:MEGAWith: SW_binaries_for_Xperia_Android_9.0.6.3_r1_v1_tone_beta.zip
First: Flash the twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < DIR of recovery.img >
Second: Boot to recovery, USB connected to the computer. adb tools run these commands:
Code:
adb shell
sgdisk /dev/block/mmcblk0 --delete 54
sgdisk /dev/block/mmcblk0 --new=54:2408448:105168896
sgdisk /dev/block/mmcblk0 --delete 55
sgdisk /dev/block/mmcblk0 --new=55:105168897:106815487
sgdisk /dev/block/mmcblk0 --new=56:106815488:122134527
sgdisk /dev/block/mmcblk0 --change-name=54:userdata
sgdisk /dev/block/mmcblk0 --change-name=55:vendor
sgdisk /dev/block/mmcblk0 --change-name=56:system
This is based on the partition table of F8132.
Third: Reboot into recovery,format the vendor and userdata partition in EXT4.
Then flash the treble-v1.0-auto.zip.
This progress will flash the boot and vendor partition.
If you encounter errors, you can unzip the treble-v1.0.zip, flash boot.img and vendor.img
Code:
fastboot flash boot < DIR of boot.img>
fastboot flash vendor < DIR of vendor.img>
Fourth: flash the SW_binaries provided by sony.
For V1.0 I rename it OEM_P.zip, in fact it's SW_binaries_for_Xperia_Android_9.0.6.3_r1_v1_tone_beta.zip
You can download it from Sony official website.
Code:
fastboot flash oem < DIR of OEM_P.img >
Fifth: Flash a GSI compatible System image and boot!
Update and known BUG:
V1.2:
Updates：
1.SIM cards Fix.
Bugs:
1. Fingerprint is broken.
V1.0:
1. The SIM cards don't work.
2. Fingerprint is broken.
Sources Code
XDA:DevDB Information
Treble, ROM for the Sony Xperia X Performance
Contributors
Sjll
Email
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-10-15
Last Updated 2018-10-15

Just to be clear, if you mess up re-partitioning your device, you will end up with a HARD BRICK. Nobody can help you then.
You've been warned.
Otherwise, nice work sjll!

local__hero said:
Just to be clear, if you mess up re-partitioning your device, you will end up with a HARD BRICK. Nobody can help you then.
You've been warned.
Otherwise, nice work sjll!
Click to expand...
Click to collapse
Thanks for your advice!

DM Verity and Force Encryption disabling on Nexus 5X for Kali Nethunter installation

Hi,
GOAL: I'm trying to flash Kali Nethunter on my Nexus 5X (bullhead)
MIDD: This boils down to try to disable dm-verity and force-encryption from my Nexus 5X (bullhead).
STEP: I have a rooted, TWRP'ed phone on (alledgedly) stock ROM, disabling both FAILs
Let's 1st state my safety nets
1. I went the safe route : Fastboot > Temporary TWRP through fastboot > Full backup
2. So I have carefully backed up every partition, literally boot.emmc.win, data.ext4.win, efs1.emmc.win, efs2.emmc.win, recovery.emmc.win, system.ext4.win000, system.ext4.win001, system_image.emmc.win, vendor.ext4.win, vendor_image.emmc.win
3. I can at any time restore my phone - it was a huge step, using fastboot + twrp + the backup above
4. Then I installed magisk, produced a dm-verity-enabled and encryption-enabled boot partition copy
5. Then flashed this boot, then had root, then added twrp app, and gained permanent TWRP
6. Now I'm fine with a safe backup at that point
That said (100% clear : I can try anything out of deleting fastboot - if that's even a thing )
Guys .. I have a real corner case :
1. I want to flash NetHunter .. brings error "Can't write to /system"
2. OK I (think I) know that one : mount -o remount,rw /system && touch /system/test # .. oh crap
3. It looks like dm-verity-plus-encrypt switches prevent me from tinkering with /system
And that's where it becomes furry
4. I adb push my boot.emmc.win as /sdcard/boot.emmc.win.img
5. I use magisk to "disable dm-verity" and "disable force-encrypt" [screenshot Screenshot_20210416-131341.png] .. and patch that boot image. The result is some magisk_patched_kSiHo.img [screenshot Screenshot_20210416-131422.png]
6. I rename this to /sdcard/TWRP/boot.emmc.NOVERITY.NOENCRYPTION.img and go to TWRP
7. In TWRP I use *this* image to flash boot, and *format* (not wipe) data and *format* cache
8. Cross fingers, pray, reboot .. FAIL : Google white logo doesn't move - no fancy colorful anim
9. I flash back my stuf, go to step 4 state again, and decide I may have made a typo
10. I triple check the original boot.emmc.win.img, put it again on sdcard, go through magisk again with the same options
11. I get a alledgedly bullet-proof BOOT image again [screenshot Screenshot_20210416-131841.png], copy it to /sdcard
12. I decide to do it hardcore-style [screenshot EXTRACT 2021-04-16 à 13.22.21.png] and issue a fastboot flash boot boot.emmc_nodmverity_noencryption.win && fastboot format userdata && fastboot format cache
Now I can't possibly have typed things wrong and I'm hoping to
* Have wiped all my data (format userdata)
* Have gotten RID OF dm-verity and encryption
* Be able to boot the partition without android needing to decrypt it
And the result is ... tadaa .. FAIL
RESULT: A white "Google" logo forever (1 night so > 6h) without Android booting. Time to restore.
So .. I don't have dm-verity and force-encryption disabled. The boot partition is (still, to date) dm-veritied and data encrypted and .. the Kali Nethunter zip fails to Install using TWRP because it fails to mountpoint /system || mount -o remount,rw,seclabel /system .. and in fact it mounts but then fails to write to any /system/some_file (and TWRP terminal show the impossibility to even touch /system/hello_world # readonly filesystem)
Any checklist/hint/manual/request_for_getprop_or_info is welcome !

For some reason /system had become non-writable and non-mountable (rw).
I don't have any data on the phone so I went down the strong route :
* Using https://dl.google.com/dl/android/aosp/bullhead-n4f26u-factory-e6420fc1.zip to extract the cache.img
* Using https://dl.google.com/dl/android/aosp/bullhead-opm7.181205.001-factory-5f189d84.zip for every other partition
I did the following, which works :
Code:
fastboot format userdata \
&& fastboot format cache \
&& fastboot flash bootloader bootloader-bullhead-bhz32c.img \
&& fastboot reboot-bootloader \
&& sleep 6 \
&& fastboot flash radio radio-bullhead-m8994f-2.6.42.5.03.img \
&& fastboot reboot-bootloader \
&& sleep 6 \
&& fastboot erase cache \
&& fastboot flash cache cache.img \
&& fastboot flash boot boot.img \
&& fastboot flash recovery recovery.img \
&& fastboot flash vendor vendor.img \
&& fastboot flash system system.img \
&& fastboot boot ~/Downloads/twrp-3.5.2_9-0-bullhead.img \
&& sleep 30 \
&& adb push ~/Downloads/Magisk-v22-0.zip /sdcard/Magisk-v22-0.zip
At that point I had a *stock* ROM with TWRP booted temporarily, Magisk on the sdcard and no encrypted data partition.
I flashed Magisk and rebooted the phone.
After configuring Android (first boot overwhelmingly long wizard) I found out I had root and a writable /system . I don't know why it had become read-only. Something between dm-verity, encryption, using the TWRP app instead of the img and (probably) a shadow /system that gets re-signed and archived in /data with verity_keys each time.
Problem #1 solved. Onto the next - Kali NetHunter now installs in TWRP .. but does not boot.

I found a reproducible way to install Kali NetHunter on a Nexus 5X (in March 2021, in case you bump on this thread in the 'future')
Do this at your own risk. While it works, it erases everything on your phone. Please learn how to backup and use fastboot and TWRP first
Scope :
Model Nexus 5X, codename bullhead
A spare phone, you will erase everything on it by following the instructions
Installation of Android 8.1.0 OREO, namely https://dl.google.com/dl/android/aosp/bullhead-opm7.181205.001-factory-5f189d84.zip
With the addition of cache.img from a 7.1 archive, namely https://dl.google.com/dl/android/aosp/bullhead-n4f26u-factory-e6420fc1.zip
Installation of SuperSU 2.82, namely SR5-SuperSU-v2.82-SR5-20171001224502.zip from https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip/
Installation of Kali NetHunter 2021.1, namely https://images.kali.org/nethunter/nethunter-2021.1-bullhead-oreo-kalifs-full.zip
All this using fastboot and TWRP 3.5.2, namely https://dl.twrp.me/bullhead/twrp-3.5.2_9-0-bullhead.img.html
You, a fluent Linux (preferably) user with some knowledge of fastboot and adb - including the proper google USD drivers installed if on windows. You've been warned
Enough warnings. After long and painful weeks of tests I finally succeeded in installing NetHunter on Nexus 5X, the crucial point being SuperSU works whereas M.a.g.i.s.k does not (redacted to prevent search to get here)
Step 1​Download the prerequisites, create an install directory on your pc
Unzip there bullhead-n4f26u-factory-e6420fc1.zip/cache.img
Unzip there bullhead-opm7.181205.001/image-bullhead-opm7.181205.001.zip/*.img
Using the key combo POWER + Volume Down, boot in fastboot mode.
Connect your phone to the PC/Mac/Linux
Step 2​Here goes the (non-bricking but) destroying commands
Code:
D=YOUR_INSTALL_DIR
cd $D
fastboot format userdata \
&& fastboot format cache \
&& fastboot flash bootloader $D/bootloader-bullhead-bhz32c.img \
&& fastboot reboot-bootloader \
&& sleep 6 \
&& fastboot flash radio $D/radio-bullhead-m8994f-2.6.42.5.03.img \
&& fastboot reboot-bootloader \
&& sleep 6 \
&& fastboot erase cache \
&& fastboot flash cache $D/cache-bullhead-n4f26u.img \
&& fastboot flash boot $D/boot.img \
&& fastboot flash recovery $D/recovery.img \
&& fastboot flash vendor $D/vendor.img \
&& fastboot flash system $D/system.img \
&& fastboot boot $D/twrp-3.5.2_9-0-bullhead.img \
&& sleep 30 \
&& adb push $D/SR5-SuperSU-v2.82-SR5-20171001224502.zip /sdcard/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Your phone should now be inside the TWRP gui (if necessary slide to answer "yes I want to modify the system partition")
Step 3​
From within TWRP, choose "Install"
Select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Wait for the end of the install
Also run Wipe Davik/Cache
Select reboot > system
Your phone should boot within less than 2 mins in normal Stock Android 8.1.0. Configure it slightly (especially the wifi) and on to the next step
Step 4​
Boot again in TWRP mode
Code:
fastboot boot $D/twrp-3.5.2_9-0-bullhead.img
Now transfer the Kali NetHunter image from the PC
Code:
adb push nethunter-2021.1-bullhead-oreo-kalifs-full.zip /sdcard/nethunter-2021.1-bullhead-oreo-kalifs-full.zip
At the end (~20mins) run Wipe Davik/Cache
Select and run reboot > system
Wait for the ~1min for 1st boot
Enjoy !

Question Fastboot and windows.bat does not work

hi,I am currently trying to install MIUI 12.6 -21.10.27 on my PocoF3.Fasboot ROM with a Windows batch file.
My steps:
1 Unzip the file
2 Start the device in Fastboot and connect to the PC
3 Start the Windows batch file
But nothing is happening. In the file folder are the platform tools for Windows, images and windows fastboot .bat. when I do a fastboot device with cmd, I can see my device.
Is it possibly the cable or missing Windows drivers?

Tried using the MiFlash tool?
Also check similar posts, fe https://forum.xda-developers.com/t/fastboot-rom-tgz-file-into-adb-sideload.4352239/

dirtytwo said:
hi,I am currently trying to install MIUI 12.6 -21.10.27 on my PocoF3.Fasboot ROM with a Windows batch file.
My steps:
1 Unzip the file
2 Start the device in Fastboot and connect to the PC
3 Start the Windows batch file
But nothing is happening. In the file folder are the platform tools for Windows, images and windows fastboot .bat. when I do a fastboot device with cmd, I can see my device.
Is it possibly the cable or missing Windows drivers?
Click to expand...
Click to collapse
try to install device drivers especially fastboot and Qualcomm usb driver

dirtytwo said:
hi,I am currently trying to install MIUI 12.6 -21.10.27 on my PocoF3.Fasboot ROM with a Windows batch file.
My steps:
1 Unzip the file
2 Start the device in Fastboot and connect to the PC
3 Start the Windows batch file
But nothing is happening. In the file folder are the platform tools for Windows, images and windows fastboot .bat. when I do a fastboot device with cmd, I can see my device.
Is it possibly the cable or missing Windows drivers?
Click to expand...
Click to collapse
you could also try:
- disable Windows driver signature check;
How to Enable or Disable Driver Signature Enforcement in Windows 10
How to Enable or Disable Driver Signature Enforcement and Test Mode in Windows 10
www.tenforums.com
- reinstall the drivers; (find the ones that work on the mi flash program);
- move the rom folder to c: \;
- try another usb port, the rear or the 2.0 are better;
- make sure you have enabled usb debug in developer settings and have authorized the pc;
- start the .bat file as administrator;

what I've found so far:
first .bat is from 22.4.21 rom wich works
@Echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth"
if %ERRORLEVEL% neq 0 echo Missmatching image and device & exit /B 1
second .bat is from 27.10.21 which doesn't work
@Echo off
cd %~dp0
set DEVICE=unknown
for /f "tokens=2" %%D in ('platform-tools-windows\fastboot %* getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set DEVICE=%%D
if "%DEVICE%" neq "alioth" echo This package is for "alioth" devices; this is a "%DEVICE%". & exit /B 1
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B 0
so what can i do.

dirtytwo said:
what I've found so far:
first .bat is from 22.4.21 rom wich works
@Echo off
cd %~dp0
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B
platform-tools-windows\fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *alioth"
if %ERRORLEVEL% neq 0 echo Missmatching image and device & exit /B 1
second .bat is from 27.10.21 which doesn't work
@Echo off
cd %~dp0
set DEVICE=unknown
for /f "tokens=2" %%D in ('platform-tools-windows\fastboot %* getvar product 2^>^&1 ^| findstr /l /b /c:"product:"') do set DEVICE=%%D
if "%DEVICE%" neq "alioth" echo This package is for "alioth" devices; this is a "%DEVICE%". & exit /B 1
set /p CHOICE=You are going to wipe your data and internal storage. It will delete all your files and photos stored on internal storage. Do you agree? (Y/N)
if /i "%CHOICE%" neq "y" exit /B 0
so what can i do.
Click to expand...
Click to collapse
I see that they have changed the encoding of the installation script, but honestly I don't know why it doesn't work for you, it's weird!
Did you do all the moves I handed you?
Can you try to install it from another pc? (So let's see if the problem is the pc or the rom)
You can also try to re-download it because maybe the package got corrupted.
Also you can try asking for information here:
MIUI 13 Stable Xiaomi.EU [Poco F3, Mi 11x, Redmi K40]
This thread is for discussion about xiaomi.eu stable releases. Weekly releases won't be shared here. MIUI 13 :- Xiaomi.EU 13.0.2.0 (Fastboot ROM) Xiaomi.EU 13.0.3.0 (Fastboot ROM) Xiaomi.EU 13.0.5.0 (Fastboot ROM) Xiaomi.EU 13.0.6.0 (Fastboot...
forum.xda-developers.com
(this is the discussion dedicated to the rom xiaomi.eu)
Or directly to the xiaomi.eu community on the official website, here:
MIUI 12.6 - 21.10.27/28
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
(you must register in order to post).

[Solved] Which partition to flash to install LineageOS (project treble) from TWRP on Blackview BV 4900 Pro?

TLDR: I am trying to install LineageOS from twrp but do not seem to be able to find the right partition to flash.
I have a Blackview BV 4900 Pro (aarch64 / MT6762v/Wd / arm64-v8a) on which I successfully installed twrp, flashed Magisk (24.3) and Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
I am trying to install lineage-19.1-20220510-UNOFFICIAL-arm64_bvS.img from Andy Yan's personnal build ( https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/ ), but I am stuck.
When I try to install the lineage image from twrp, it asks which partition to flash among
- System_image
- Vendor_image
- Product_image
- Boot
- dtbo
- Recovery
- Persist Image
- Vbmeta
- Vbmeta System
- Vbmeta Vendor
- lk
- logo
- nvram
- TEE
- frp
- Super (Product, Vendor, System)
If I Try System_image, I have an error message "E: Cannot flash images to file systems". I can successfully flash on Super, but then nothing boots (I just have a black screen with "Fastboot mode" at the bottom, and I am indeed in fastboot mode).
What am I missing?
In twrp's log, I also have the error message "Failed to mount '/system_root' (Permission denied)", but that's it.

At this time, I am guessing that re-packaging a super.img with the current Product and Vendor image, but the lineage image for system, may be my best way forward.
Relevant threads:
- https://forum.xda-developers.com/t/...devices-with-dynamic-super-partition.4256667/
- https://forum.xda-developers.com/t/...ake-partitions-rw-in-super-partition.4120963/
- https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/
- https://www.hovatek.com/forum/thread-37896-page-3.html
- https://github.com/ADeadTrousers/an...om_LXL/blob/master/docs/HOW-TO-FLASH-SUPER.md
- https://forum.xda-developers.com/t/...midigi-a7-pro-amd64-a-only-with-twrp.4175241/
- https://forum.xda-developers.com/t/umidigi-devices-flashing-a-rom-gsi.4182673/
The most relevant being probably https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/

So, yes, the correct way of proceeding was to a. repackage a super.img, and the b. flash it.
To repackage a super.img, the best is to follow the instructions at https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/
In my case, I had to:
- Get the original
Code:
super.img
- Install simg2img
- Run
Code:
simg2img super.img super.ext4.img
- Pull the soucres at https://github.com/Exynos-nibba/lpunpack-lpmake-mirror
- Run
Code:
lpbinary/binary/./lpunpack super.ext4.img
- Pull together three images: the original vendor.img, the original product.img, and lineage-19.1-20220510-UNOFFICIAL-arm64_bvS.img
- Find the size of the super partition using https://android.stackexchange.com/a/247134/188657
- Use this python script ( https://forum.xda-developers.com/t/...shing-our-modifications.4196625/post-85096929 ) and run
Code:
python3 lpmakesimple.py lpbinary/binary/lpmake ./super.new.img 4294967296 system=./lineage-19.1-20220510-UNOFFICIAL-arm64_bvS.img,vendor=./vendor.img,product=./product.img
which outputted
Code:
lpbinary/binary/lpmake \
--metadata-size 65536 --metadata-slots 1 --device super:4294967296 \
--group main:4294103040 --partition system:readonly:2035568640:main \
--image system=./lineage-18.1-20220511-UNOFFICIAL-arm64_avS.img \
--partition vendor:readonly:312594432:main --image vendor=./vendor.img \
--partition product:readonly:1945939968:main --image product=./product.img \
--sparse --output ./super.new.img
And then flash super.new.img using
Code:
fastboot flash super super.new.img
and that was it!

Trying to install NetHunter on Nexus 5X that has Lineage-15.1 on?

I have looked and looked and still can't find any help so I thought I'd ask! I've been using Kali for the best part of 2 years and decided to give Nethunter a go.
Got myself a Nexus 5X, installed
twrp-3.6.2_9-0-bullhead.img
lineage-15.1-20220321-UNOFFICIAL-bullhead (rebooted after install)
Magisk-v25.2 (rebooted and verify app)
Got it rooted OK with Magisk, checked with Root Checker Basic.
So far so good.
Now I boot back into TWRP and try flashing:
nethunter-2022.2b-bullhead-oreo-kalifs-full
Which gets me to boot and the flaming Kali logo, then after 30 mins I'm still looking at it!
I also tried wiping it all and flashing the first three again then tried a different flavor of Nethunter and tried to flash:
nethunter-generic-armhf-kalifs-full-rolling-2019.03-13-0514
kernel-nethunter-bullhead-nougat-2019.03-13-0514 (I realise this is nougat and lineage 15.1 is Android 8.1 Oreo but thought it was worth a shot)
For a 3rd attempt I wiped and installed factory official 8.1 Oreo, then TWRP, then Magisk (same version as above), then the Nethunter directly from Nethunter.
AND as a last ditch attempt I wiped and installed factory official 8.1 Oreo, then TWRP, then Magisk.... THEN I transferred to internal storage:
KaliNethunter-v8.2(22).zip
kalifs-full.tar.xz
Then with Magisk I installed KaliNethunter-v8.2(22).zip, rebooted and opened the Nethunter app and used Kali Chroot Manager, however 'apt-get updates', 'apt-get install firmware-atheros' and 'ifconfig wlan1' doesn't work and it's just keeps giving me the error it's outdated plus it doesn't feel as baked in as if I was flashing it via TWRP!?
Soooooooo can anyone point me in the right direction of how to get this done please?
A lot of XDA posts are outdated or contain broken links.
I will caveat and say that this is not my everyday phone and understand the roms are not patched to the latest security and that's OK for what I need it for.
Thank you, thank you, and thank you for anyone that can help get this working.

Maybe it's a little bit late for this but the instructions stated here work:
DM Verity and Force Encryption disabling on Nexus 5X for Kali Nethunter installation
Hi, GOAL: I'm trying to flash Kali Nethunter on my Nexus 5X (bullhead) MIDD: This boils down to try to disable dm-verity and force-encryption from my Nexus 5X (bullhead). STEP: I have a rooted, TWRP'ed phone on (alledgedly) stock ROM, disabling...
forum.xda-developers.com
I slightly modified the script to:
#!/usr/bin/sudo bash
./fastboot format userdata \
&& ./fastboot format cache \
&& ./fastboot flash bootloader bootloader-bullhead-bhz32c.img \
&& ./fastboot reboot-bootloader \
&& sleep 10 \
&& ./fastboot flash radio radio-bullhead-m8994f-2.6.42.5.03.img \
&& ./fastboot reboot-bootloader \
&& sleep 10 \
&& ./fastboot erase cache \
&& ./fastboot flash cache cache.img \
&& ./fastboot flash boot boot.img \
&& ./fastboot flash recovery recovery.img \
&& ./fastboot flash vendor vendor.img \
&& ./fastboot flash system system.img \
&& ./fastboot flash recovery twrp.img \
&& ./fastboot boot twrp.img \
&& echo ENABLE read and write on partitions and install magisk \
&& sleep 30 \
&& ./adb push Magisk-v25.2.zip /sdcard/TWRP/ \
&& echo Flash NH with TWRP, clear caches and reboot into system \
&& echo ./adb push nethunter-2022.3-bullhead-oreo-kalifs-full.zip /sdcard/TWRP/ \
&& echo now copy and unzip this manually into /system/etc/firmware via terminal \
&& echo ./adb push firmware.zip /sdcard/TWRP/
And the firmware.zip can be found here:
GitHub - rithvikvibhu/nh-magisk-wifi-firmware: This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter.
This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter. - GitHub - rithvikvibhu/nh-magisk-wifi-firmware: This Magisk module adds the required firmwar...
github.com
Just zip this
nh-magisk-wifi-firmware/system/etc/firmware at master · rithvikvibhu/nh-magisk-wifi-firmware
This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter. - nh-magisk-wifi-firmware/system/etc/firmware at master · rithvikvibhu/nh-magisk-wifi-firmware
github.com
and extract into /system/etc/firmware via terminal/unzip
If you need rw permissions issue mount -o rw,remount /system
Once NH is installed you can check what dongles may work with cat /proc/config.gz (that's the kernel config) on TWRP. I had the fortune to make one work (an old tplink dongle).
Hope it helps someone.