I was trying to install kali nethunter on my android mobile (android 13) and when i ran the

./install-nethunter-termux

command, I got the following response :

[*] Downloading rootfs...

--2023-09-25 13:33:06--  https://kali.download/nethunter-images/current/rootfs/kalifs-arm64-full.tar.xz 
Resolving kali.download (kali.download)... 104.18.103.100, 104.18.102.100, 2606:4700:9640:38fb:330c:6:6812:6664
Connecting to kali.download (kali.download)|104.18.103.100|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-09-25 13:33:09 ERROR 404: Not Found.

I don't understand what this error means and so I seek help with this. Thank you in advance!

I am trying to run an Android app on a Debian laptop (Storytel). I installed Waydroid from their repository, but it fails to initialise:

root@x1v5:/etc/apt# waydroid init
[23:15:43] ERROR: Binder node "vndbinder" for waydroid not found
[23:15:43] See also: 
Run 'waydroid log' for details.

Waydroid log looks as follows:

root@x1v5:/etc/apt# waydroid log
(021820) [23:09:48] % modprobe binder_linux devices="anbox-vndbinder,anbox-hwbinder"
(021820) [23:09:48] ERROR: Binder node "vndbinder" for waydroid not found
(021820) [23:09:48] See also: 
(021820) [23:09:48] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 64, in main
    actions.init(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 110, in init
    setup_config(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 97, in setup_config
    helpers.drivers.setupBinderNodes(args)
  File "/usr/lib/waydroid/tools/helpers/drivers.py", line 141, in setupBinderNodes
    raise OSError('Binder node "vndbinder" for waydroid not found')
OSError: Binder node "vndbinder" for waydroid not found

(021826) [23:10:28] % modprobe binder_linux devices="anbox-vndbinder,anbox-hwbinder"
(021826) [23:10:28] ERROR: Binder node "vndbinder" for waydroid not found
(021826) [23:10:28] See also: 
(021826) [23:10:28] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 64, in main
    actions.init(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 110, in init
    setup_config(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 97, in setup_config
    helpers.drivers.setupBinderNodes(args)
  File "/usr/lib/waydroid/tools/helpers/drivers.py", line 141, in setupBinderNodes
    raise OSError('Binder node "vndbinder" for waydroid not found')
OSError: Binder node "vndbinder" for waydroid not found

(021831) [23:10:48] % modprobe binder_linux devices="anbox-vndbinder,anbox-hwbinder"
(021831) [23:10:48] ERROR: Binder node "vndbinder" for waydroid not found
(021831) [23:10:48] See also: 
(021831) [23:10:48] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 64, in main
    actions.init(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 110, in init
    setup_config(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 97, in setup_config
    helpers.drivers.setupBinderNodes(args)
  File "/usr/lib/waydroid/tools/helpers/drivers.py", line 141, in setupBinderNodes
    raise OSError('Binder node "vndbinder" for waydroid not found')
OSError: Binder node "vndbinder" for waydroid not found

(021932) [23:14:28] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(021932) [23:14:28] *** output passed to waydroid stdout, not to this log ***
(021968) [23:15:43] % modprobe binder_linux devices="anbox-vndbinder,anbox-hwbinder"
(021968) [23:15:43] ERROR: Binder node "vndbinder" for waydroid not found
(021968) [23:15:43] See also: 
(021968) [23:15:43] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 64, in main
    actions.init(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 110, in init
    setup_config(args)
  File "/usr/lib/waydroid/tools/actions/initializer.py", line 97, in setup_config
    helpers.drivers.setupBinderNodes(args)
  File "/usr/lib/waydroid/tools/helpers/drivers.py", line 141, in setupBinderNodes
    raise OSError('Binder node "vndbinder" for waydroid not found')
OSError: Binder node "vndbinder" for waydroid not found

(022124) [23:20:40] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(022124) [23:20:40] *** output passed to waydroid stdout, not to this log ***

How can I get it working?

Previously, I had the same error related to the file: arch/arm64/boot/dts/qcom/apq8016-sbc.dtb, but I solved it by deleting the line subdir-y += qcom from the arch/arm64/boot/dts/Makefile. Now a new same error appears and I have no idea how to fix it. Internet advice didn't help. Error: make: *** No rule to make target 'arch/arm64/boot/dts/kona-rumi.dtb', needed by '__build'. Stop. make: *** Waiting for unfinished jobs.... make: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts] Error 2 make[1] : *** [arch/arm64/Makefile:172: dtbs] Error 2 make[1] : *** Waiting for unfinished jobs.... Error with make V=1: make -f ../scripts/Makefile.build obj=arch/arm64/boot/dts/ti need-builtin= (cat /dev/null; ) > arch/arm64/boot/dts/ti/modules.order make -f ../scripts/Makefile.build obj=arch/arm64/boot/dts/vendor need-builtin= make -f ../scripts/Makefile.build obj=arch/arm64/boot/dts/vendor/qcom need-builtin= (cat /dev/null; ) > arch/arm64/boot/dts/vendor/qcom/modules.order make: *** No rule to make target 'arch/arm64/boot/dts/vendor/qcom/kona-rumi.dtb', needed by '__build'. Stop. make: *** Waiting for unfinished jobs.... make: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts/vendor/qcom] Error 2 make: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts/vendor] Error 2 make[1] : *** [arch/arm64/Makefile:172: dtbs] Error 2 make[1] : *** Waiting for unfinished jobs.... MyKernel: kernel My build code:

export ARCH=arm64
export SUBARCH=arm64
export HEADER_ARCH=arm64
export DTC_EXT=dtc
PATH="/home/hehe/Downloads/clang/bin:/home/hehe/Downloads/aarch64-linux-android-4.9/bin:/home/hehe/Downloads/arm-linux-androideabi-4.9/bin:${PATH}"
rm -rf out
make O=out clean && make mrproper
make O=out ARCH=arm64 kona_defconfig
make -j$(nproc --all) O=out ARCH=arm64 CC=clang CLANG_TRIPLE=aarch64-linux-gnu- CROSS_COMPILE=aarch64-linux-android- CROSS_COMPILE_ARM32=arm-linux-androideabi-

I want to customize boot process of Android in emulator. system.img runs normally in Android Studio Emulator. This file in https://dl.google.com/android/repository/sys-img/google_apis/x86_64-26_r16.zip I tried:
\> fdisk -lu 'system.img'
Start End Sectors Size Type
system.img1 2048 4095 2048 1M Linux filesystem
system.img2 4096 6311935 6307840 3G Linux filesystem
\> sudo mount -o loop,offset=$((4096\*512)) 'system.img'
Without luck.
Tried to get hexdump
\> sudo losetup /dev/loop21 --offset=$((4096\*512)) 'system.img' ;
\> sudo hexdump /dev/loop21 -n 12500 -C;
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00001000 67 44 6c 61 34 00 00 00 4e 31 cf 64 27 54 42 f4 |gDla4...N1.d'TB.|
00001010 0e 25 c7 72 a1 8d 1f cc d8 b1 29 12 32 e5 93 f6 |.%.r......).2...|
00001020 5e 52 2f c7 ac 07 df 03 00 00 01 00 02 00 00 00 |^R/.............|
00001030 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00001040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00002000 67 44 6c 61 34 00 00 00 4e 31 cf 64 27 54 42 f4 |gDla4...N1.d'TB.|
00002010 0e 25 c7 72 a1 8d 1f cc d8 b1 29 12 32 e5 93 f6 |.%.r......).2...|
00002020 5e 52 2f c7 ac 07 df 03 00 00 01 00 02 00 00 00 |^R/.............|
00002030 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00002040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00003000 30 50 4c 41 0a 00 00 00 80 00 00 00 20 43 72 43 |0PLA........ CrC|
00003010 60 37 de ab 1b ef 45 7c a2 c1 1e fb a6 64 16 ee |`7....E|.....d..|
00003020 85 bf 04 dc bc c8 cf 00 d1 91 e0 14 d0 01 00 00 |................|
00003030 33 3f d6 a7 ed 2d f2 64 6c ee 5c f3 1b d3 55 e5 |3?...-.dl.\...U.|
00003040 d3 27 c5 1e f0 7b c5 9f 4d 1f 82 a7 f2 5f 0e 6f |.'...{..M...._.o|
00003050 00 00 00 00 04 00 00 00 34 00 00 00 d0 00 00 00 |........4.......|
00003060 04 00 00 00 18 00 00 00 30 01 00 00 02 00 00 00 |........0.......|
00003070 30 00 00 00 90 01 00 00 01 00 00 00 40 00 00 00 |0...........@...|
00003080 73 79 73 74 65 6d 00 00 00 00 00 00 00 00 00 00 |system..........|
00003090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000030a0 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 |................|
000030b0 01 00 00 00 73 79 73 74 65 6d 5f 65 78 74 00 00 |....system_ext..|
000030c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000030d0 00 00 00 00 |....|
Tried mount with -offset=203000
Also tried:
\> simg2img system.img system.unsimg.img
Edit: i made mistake in link. Real link is https://dl.google.com/android/repository/sys-img/google_apis/x86_64-30_r16.zip .
The problem : Google starting from Android-29 or Android-Q begin use ext4 filesystem with parameter "shared_blocks" - it is some type of compression, wich combine similar filesystem blocks. Before all manipulations make copy of system.img. You can watch it with commands
\>cp system.img system2.img
\>sudo losetup /dev/loop22 --offset=$((6144\*512)) 'system2.img'
\>sudo tune2fs -l /dev/loop22 | egrep "(shared_blocks|Block count)"
We have got Block count
Somehow 2048*3 = 6144 - is block number that works.
To unshare blocks and make almost normal ext4 filesystem need run:
\>sudo e2fsck -f /dev/loop22
\>sudo resize2fs /dev/loop22 3G #expand FS to new size 3G
\>sudo e2fsck -E unshare_blocks /dev/loop22
\>sudo mount /dev/loop22 /mnt; #mount partition
I delete useless files size=200M
\>sudo resize2fs /dev/loop22 $((900000/4)) #shrink size to 900000 blocks with block size 4k
Manipulation with system.img
\>sudo losetup /dev/loop23 --offset=$((6144*512)) 'system.img'
Write shrinked image to system.img
sudo dd if=/dev/loop22 of=/dev/loop23 bs=1024 count=900000
So data from shifted system2.img written to shifted system.img
so now second partition in system.img can be mounted without shared_blocks and is writable.
All the above described manipulations not let me run Android sdk Emulator with command:
\>./avdmanager create avd -n test -k "system-images;android-30;google_apis;x86_64"
\>./emulator -avd test -no-cache -show-kernel
I have got error:
Filesystem on /dev/block/pci/pci0000:00/0000:00:06.0/by-name/metadata was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x46

I am trying to run adb, in order to backup my android device. I installed android tools via dnf (sudo dnf install android-tools), but adb is giving a symbol error, specifically: adb: symbol lookup error: adb: undefined symbol: libusb_get_ssplus_usb_device_capability_descriptor. I have tried to look online if others have experienced this as well, but was unable to find anything. From what I've been able to gather, this symbol should be present in all libusb version greater then 1.0.26, but mine is greater but still gives the error.

$ rpm -q libusb1

> libusb1-1.0.27-9.fc41.x86_64
> libusb1-1.0.27-9.fc41.i686
> libusb1-1.0.28-2.fc41.x86_64
> libusb1-1.0.28-2.fc41.i686

I also checked that adb indeed does link to my system libraries, which it does.

$ ldd $(which adb)

> ...
> libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x00007f07c835f000)
> ...

I'm not fully sure what to try next, or how to get adb to run succesfully. Any call to adb gives this lookup error (even simply calling it as adb --help). I am running: - Fedora 41 (KDE Plasma) - Kernel 6.14.11 - with an Intel i7 mobile cpu, in case that might matter.

for example when I run sdkmanager this error displays:

Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
	at com.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)
	at com.android.repository.api.SchemaModule.(SchemaModule.java:75)
	at com.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)
	at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
	at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
	at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	... 5 more

and If I want to run any flutter code on my android device this error occur:

Launching lib/main.dart on VOG L29 in debug mode...
Checking the license for package Android SDK Build-Tools 30.0.3 in /opt/android-sdk/licenses
Warning: License for package Android SDK Build-Tools 30.0.3 not accepted.
Checking the license for package Android SDK Platform 31 in /opt/android-sdk/licenses
Warning: License for package Android SDK Platform 31 not accepted.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Failed to install the following Android SDK packages as some licences have not been accepted.
     platforms;android-31 Android SDK Platform 31
     build-tools;30.0.3 Android SDK Build-Tools 30.0.3
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html 

  Using Android SDK: /opt/android-sdk

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org 

BUILD FAILED in 17s
Running Gradle task 'assembleDebug'...                             18.1s
Exception: Gradle task assembleDebug failed with exit code 1

I also tried fixing the errors by acpeting licences but that also wouldn't work.

I was looking at the /proc//maps file for an aarch64 process running on an Android (10). This section caught my interest:

72582d2000-72582f6000 --xp 00012000 07:20 93        /apex/com.android.runtime/lib64/bionic/libm.so

According to readelf, that corresponds, as expected, to the .text section. What does it mean for a memory section to be executable but not readable? I didn't think that was possible.

I have nethunter android tablet. I set up the local Kex server, when i start the KEX client I get this error: > **Plugin "null" could not be loaded, do you want to remove it from xfce4-panel configuration?** > > this plugin is in the current xfce4-panel configuration but could not > be loaded, probably due to an installation issue. I run those commands sudo apt install --reinstall xfce4-panel sudo apt install xfce4-goodies but the error still persists. Whereever I click on the screen opens the start menu

I am working on a kiosk project using an android tablet. If there is no input power to the kiosk for a long time, then the tablet will eventually shut down. In order to auto-reboot the tab when the power comes back, I modified the code in my tabs battery animation file (ipod) using: #!/system/bin/sh sleep 300 /system/bin/reboot However, during the sleep period (shown above), the tabs screen remains in the ON state (and hence takes longer retries for the tab to charge and bootup). I need to turn the screen OFF. What is the command I should use prior to the sleep command to turn my tabs screen OFF during the charging/bootup stage.

I am using linux arch. I installed android according to [ArchWiki](https://wiki.archlinux.org/index.php/Android) . I uninstalled every skd component and android studio using pacman -Rs. Also, I removed every hidden folder in the home directory that had something to do with android such .android, .gradle, AndroidStudio. But the environment variable ANDROID_HOME is still set and the following command ps aux | grep 'adb' returns adb -L tcp:5037 fork-server server --reply-fd 4 Where is the environment variable ANDROID_HOME set and what means adb -L tcp:5037 fork-server server --reply-fd 4? Is android not properly uninstalled? The command adb returns bash: adb: command not found EDIT: In a */proc/pid/environ*, there are still things like */opt/android-sdk/platform-tools:/opt/android-sdk/tools:/opt/android-sdk/tools/bin*

My phone (Google Pixel 6 and Android 15) is connected to both 4G and a Wifi network with no Internet. The wifi network gives me IP address 192.168.4.2 and I know there's a WIFI Access point on 192.168.4.1. The 4G network gives me IP address 10.96.106.X. When I am connected to both networks I go to Termux and I try:

ping 192.168.4.1

but ping is unsuccessful - all the packets time out. Then I disconnect the 4G and I try again:

ping 192.168.4.1

And then the ping is successful. It seems like Android is thinking **"The only way to perform the ping is go through the 4G network because your Wifi doesn't have internet"**, so it does the ping over the 4G network and hence it is unsuccessful. But that's wrong - I'm trying to ping an internal IP address on the wifi network so it should do the ping successfully. Any suggestions?

I've been using rsync for Android to backup my phone to a remote NTFS filesystem on a Linux system for a while. Recently, the HDD containing the NTFS filesystem has started to fail (or throw "I/O Errors") so I took the opportunity to copy all the files onto a new HDD and new NTFS filesystem. In this instance I used the "FastCopy v2.11" tool for Windows. My problem is that when I do an rsync "dry run" I can see that it wants to recopy files which already exist on the remote rsync folder. For example, when I run with "-iv" I get this kind of output: ls -l to check the modified time). Given that I recently copied the remote rsync files from an old NTFS filesystem, the remote file's ctime is different (using ls -lc). Does rsync look at the remote ctime, and if so is there any way I can use rsync, or ntfs-3g to get around this problem?

I have debian dual boot with windows and try to install prime os also, while install it i didn't install it's grub because i have debian grub, but after installation i can't found it in grub . result in `fdisk -l /dev/sda2 112687104 133169151 20482048 9.8G 83 Linux ` i try to install grub-customizer and add it by code set root='(hd0,2)' search --no-floppy --fs-uuid --set=root e5d445e4-f59f-5158-b9c7-465f7009bc23 linux android/kernel root=UUID=e5d445e4-f59f-5158-b9c7-465f7009bc23 quiet androidboot.hardware=generic_x86 SRC=/android acpi_sleep=s3_bios,s3_mode initrd android/initrd.img then it was added successfully but when i open it it's show android/kernel not found file located at partition `PrimeOS/android/kernel partition details

I've been trying to Google, but all of the issues refers connection from PC to remote VNC server. So. I have an issue with VNC communication from Android to Linux. I have installed a TightVNC Server on latest Ubuntu version which works fine if I connect to it from PC with RealVNC Viewer on port 5901. I downloaded a VNC Viewer by RealVNC for Android and if I try to connect to my remote host it says "Too many authentication failures" even on first try. I also tried a couple different VNC Viewers, but result is exactly same. What would be the reason and how I am able to fix it? Some people were speaking about that the client can be unsecure, but I'm not sure what difference there would be with PC and Android version of VNC. - From PC to remote: Works - From Android to remote: Doesn't work About half-year ago on my different server I had no similar issues. It was working fine, no matter what device I used to connect VNC if I knew IP, port and password.

I have debian stretch installed in arm64 android phone in chrooted environment. I have installed docker-ce following these steps from here . On starting docker :: systemctl start docker returns this error :: Running in chroot, ignoring request. Checking using service docker status shows [FAIL] Docker is not running ... failed! How can I run it inside chroot on my android phone ?

First of all, I have inside an android Operating System a chroot environment created using Linux Deploy. I am able to access it from Android using a terminal emulator and root permission. I would like to run a script inside it. However, when trying to run the script, or even normal shell commands, it doesn't executes and returns this error: "No such file or directory" So, I am wondering, is it there a way to execute, from the host within a chroot environment, commands/scripts? Has the problem to do with the proper setting of the environment PATH variable? I am able to execute ls command within the chroot environment but when printing with the -la argument it doesn't even show the . and .. directories. Could someone explain why is this happening and how could we overcome this issue? P.D.: I've posted this issue in unix/linux stack exchange because I thought it concerns more to it. However, if you recommend me to also post it in stackoverflow or any other, I am open to do so.

I have a Bluetooth headset (Soundcore Q30), and when it is connected to my computer, I can still connect to it via my Android smartphone and play sound on it. However, if I want to do the opposite and connect my computer to the headset when it is already connect to my phone (even if not playing sound), bluez fails with the error: SET_CONFIGURATION request rejected: Stream End Point in Use (19) The error makes sense, but I am suprised my computer cannot do what my phone can. Is there a way to bypass that? I am on Ubuntu 20.04 with Linux 5.15 and Bluez 5.53.

I've got a rooted Android phone and am trying to enable IPv4 forwarding via adb shell. If I do

host$ adb shell
phone$ su -c "echo 1 > /proc/sys/net/ipv4/ip_forward"

then it works just fine. However,

host$ adb shell su -c "echo 1 > /proc/sys/net/ipv4/ip_forward"

produces

/system/bin/sh: can't create /proc/sys/net/ipv4/ip_forward: Permission denied

even though adb shell cat /proc/sys/net/ipv4/ip_forward shows that the file already exists.