There are two types of nmap.sh available to the public, one for general use and one for Samsung.
Recently, a few nmap.sh for Samsung have been downloaded, but we recommend you to use LADB because nmap is unstable on Samsung devices.
Hi Dimlos,
Ithought I would register to provide some info I got from testing on Samsung tab S8+ Android 13 :
- I have a port set at 46349, so the 45000 upper limit in nmap.sh for Samsung ( PORTS=`nmap -sT -p30000-45000 --open localhost | grep "open" | sed -r 's/([1-9][0-9]+)(\/tcp.+)/\1/'`) is wrong
- simply running
nmap -sT -p46000-47000 --open localhost
in Termux, is unreliable. I might have to run it like 4 times to get my current 46349 port show up. (I reduced the port range for testing)
nmap -sT -p46000-47000 localhost
without --open, on the other hand, seems reliable. But it takes like 4 times longer to run.
I don't understand what the "--open" option is really doing. Maybe not scanning all ports in the requested range?
Obviously this has nothing to do with what is specific to nmap.sh for Samsung (fakeroot for adb connect), and will be at least one cause of problems with that script.
Hope this helps, even it is is not a solution.