Related
Has anyone figured out how to get OpenVPN working on a Motorola Milestone?
I tried to using the OpenVPN Installer and OpenVPN Settings apps from the Android Market but was not able to get it working.
Made some progress but still not working...
I've managed to install the OpenVPN binary to /system/bin.
Got a Motorola Milestone Tun.ko driver from, http://code.google.com/p/sbdtools/downloads/list. It's been copied to /system/lib/modules. I've been able to enable it using the insmod command in adb shell. Verified it was running with the lsmod command.
I've moved my openvpn .ovpn config files to my SD, /sdcard/openvpn folder. Started the OpenVPN Settings app, configured the tun and path settings.
Then I started my connection and was able to obtain an IP address.
BUT... still not able to surf to Youtube or other China blocked sites.
The upload & download stats appear to be not moving, even when I try to surf to one of these websites (up: 0.02kBps - down: 0.02 kBps).
Will continue at it for some more, but if anyone is able to help, that would be much appreciated.
dysa said:
I've managed to install the OpenVPN binary to /system/bin.
Got a Motorola Milestone Tun.ko driver from, http://code.google.com/p/sbdtools/downloads/list. It's been copied to /system/lib/modules. I've been able to enable it using the insmod command in adb shell. Verified it was running with the lsmod command.
I've moved my openvpn .ovpn config files to my SD, /sdcard/openvpn folder. Started the OpenVPN Settings app, configured the tun and path settings.
Then I started my connection and was able to obtain an IP address.
BUT... still not able to surf to Youtube or other China blocked sites.
The upload & download stats appear to be not moving, even when I try to surf to one of these websites (up: 0.02kBps - down: 0.02 kBps).
Will continue at it for some more, but if anyone is able to help, that would be much appreciated.
Click to expand...
Click to collapse
Hi, same here.. I am based in China and have done the steps you mentioned... I can connect to OpenVPN but there is no traffic.. I subscribe to 12vpn and called the helpdesk, they told me it could be due to DNS poisoning.. but really doubt that.. I got it working like once the first time but never did again...
@ pointdexler & dysa
I've also installed open VPN to system/bin on the droid 2 running 2.2.19. My config and certs have been transfered to /mnt/sdcard/openvpn and I've also setup my config in the open VPN GUI (available on the droid market) to point to this directory for my config.
After launching the app and attempting to connect, I get an error message that the command was not successful (the error is a bit more verbose than that).
I did find another app on Droid market that got me a bit closer to connecting called openVPN settings. The error output on this app is much more verbose and aids troubleshooting better. I was able to workout all of the application problems, but my issue now is with the tun.ko module. It appears that the downloadable modules online are for 2.1 and prior as none seem to work with 2.2. I have the module copied to /system/lib/modules and the app (openvpn settings) has a feature that loads the module (either by modprobe or insmod, you can choose). My problem now is that the tun.ko module seems to be wrong as I keep getting the error "Fatal: cannot allocate tun/tap dev dynamically."
Have either of you come accross this same issue?
Hi, I have running OpenVPN without problems. I use OpenVPN Settings from market, tun.ko on /sdcard and openvpn binary in /system/xbin. Make symlink ln -s /system/xbin /system/xbin/bb. Both files are in this archive http://www.android-hilfe.de/attachm...openvpn-auf-dem-milestone-tun_und_openvpn.zip. Working openvpn.ovpn + CA files in /sdcard/openvpn. In OpenVPN Settings set up Load module using - insmod and Path to module /sdcard/tun.ko. And OpenVPN is working. If not, try run from konsole : insmod /sdcard/tun.ko
Motorola Light 2.1 ROM + JIT
On CyanogenMod 6 for Milestone you need only tun.ko. No openvpn binary, no create symlink. In OpenVPN Settings only set up insmod and path to tun.ko.
(and sorry for my english )
OpenVPN
No worries ZS-Man, your English is much better than some people who are born speaking the language.
I unfortunately already tried loading the kernel module by command line with root (#) access and it gives me this error message:
insmod: init_module '/data/tun2.ko' failed (Exec format error)
I've tried many different versions of the tun.ko file available online. None seem to work with 2.2.20 OS (2.6.32 kernel)
Android version (2.1 or 2.2) is not important, only tun.ko must be compiled from same sources as kernel. You must search module for milestone2, or compile it by yourself from milestone2 kernel sources. Another nice app is Tunneldroid , it has log viewer - good for debugging openvpn connection.
help help help vpn issue
iam from a country that google does not support the market within
i installed the vpn and all works great market apps every thing but 3days later
the market wont open looks like the ip address from us has been blocked(internet sharing device located in us) and i was unable to open market again any way that i can chage the ip or howoften the company changes the ip address (cause its the same every time i connect vpn) or is there a way to use the vpn settings with another server provider than the freeopenvpn.com
where i can download another zip file with configuration to another server
help me please i ll die
I have a Nexus 6 on Verizon running the stock 5.1.1 factory image from Google (LMY47Z).
After flashing the entire stock image using the flash-all.bat, I installed the latest TWRP, installed su and SuperSu, and busybox.
When I enable the built-in wireless hotspot, whether using encryption or not, clients will successfully connect, but never obtain and IP. However, even when I manually assign an IP on the client device, still it appears that no internet is passed to clients.
Any ideas?
*edit*
Looks like it actually does work when I manually set an IP (192.168.43.XXX), I guess I just didn't give it long enough.
THIS IS CURRENTLY NOT WORKING
A newer version is available here: https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
suhide is an experimental (and officially unsupported) mod for SuperSU that can selectively hide root (the su binary and package name) from other applications.
Pros
- Hides root on a per-app base, no need to globally disable root
- Doesn't need Xposed
- Even supports SuperSU's ancient app compatibility mode (BINDSYSTEMXBIN)
- Passes SafetyNet attestation by default on stock ROMs (last officially tested on 2016.10.07)
Cons
- Ultimately a losing game (see the next few posts)
- No GUI (at the moment) - Unofficial GUI by loserskater
Requirements
- SuperSU v2.78 SR1 or newer (link)
- SuperSU installed in systemless mode
- Android 6.0 or newer
- TWRP (3.0.2 or newer, with access to /data - link!) or FlashFire (link)
Xposed
Xposed is not currently officially supported, but if you want to use it directly, you must be using @topjohnwu 's systemless xposed v86.2 exactly (attached at the bottom). It seems to mostly work during my non-extensive testing, but there are still some performance issues (both boot-time and run-time). Proceed with caution, expect bootloop.
Alternatively, there are some reports that the latest Magisk version + the latest systemless xposed (for Magisk) also works. I have not personally tested this.
CyanogenMod
I've personally tested with CM13 on i9300 without issue, however, several users are reporting it doesn't work for them. Proceed with caution, expect bootloop. Also, aside from just flashing SuperSU, you need to make sure /system/bin/su and /system/xbin/su are removed, or CM's internal root will still be used.
Usage
Install/Upgrade
- Make sure you have the latest SuperSU version flashed in systemless mode
- Make sure you are using the latest TWRP or FlashFire version
- Remove any and all Xposed versions
- If you have been having issues, flash suhide-rm-vX.YY.zip first, and note that your blacklist has been lost.
- Flash the attached suhide-vX.YY.zip
- If you are upgrading from suhide v0.16 or older, reflash SuperSU ZIP, and note that your blacklist has been lost.
- Optionally, flash the Xposed version linked above, and pray
At first install SafetyNet is automatically blacklisted.
If you have just flashed a ROM, it is advised to let it fully boot at least once before installing suhide.
Uninstall
- Flash the attached suhide-rm-vX.YY.zip. The version may appear older, the uninstall script doesn't change very often.
Blacklisting an app
You need the UID (10000 to 99999, usually 10xxx) of the app, which can be tricky to find, or the process name. There may be a GUI for this at some point.
(Note that all commands below need to be executed from a root shell)
If you know the package name, ls -nld /data/data/packagename will show the UID - usually the 3rd column.
Similarly, for running apps, ps -n | grep packagename will also show the UID - usually the 1st column.
Note that the process name is often the same as the package name, but this is not always the case. UID is more reliable for identifying a specific app, and it is also faster than blocking based on process names.
When you know the UID or process name:
Add to blacklist: /su/suhide/add UID or /su/suhide/add processname
Remove from blacklist: /su/suhide/rm UID or /su/suhide/rm processname
List blacklist: /su/suhide/list
All running processes for that UID or process name need to be killed/restarted for su binary hiding. For SuperSU GUI hiding, the device needs to be restarted. I recommend just (soft-)rebooting your device after making any changes.
Please keep in mind that many apps store their rooted state, so you may need to clear their data (and then reboot).
Integration into SuperSU
This mod isn't stable, and probably will never be (see the next few posts). As SuperSU does aim to be stable, I don't think they're a good match. But who knows, it all depends on how things progress on the detection side.
Detections
This mod hides the su binary pretty well, and does a basic job of hiding the SuperSU GUI. The hiding is never perfect, and suhide itself is not undetectable either. This will never be a perfectly working solution.
Debugging bootloops
- Get your device in a booting state
- Make sure you have TWRP or a similar recovery
- Install LiveBoot (link)
- If you are not a LiveBoot Pro user, enable the Freeload option
- Enable the Save logs option
- Recreate the bootloop
- In TWRP, get /cache/liveboot.log , and ZIP+attach it to a post here.
Download
Attached below.
Any rm version should work to uninstall any suhide version.
There may be multiple versions of suhide attached, please look carefully which one you are downloading!
YOU ARE EXPLICITLY NOT ALLOWED TO REDISTRIBUTE THESE FILES
(pre-v0.51: 17410 downloads)
Hiding root: a losing game - rant du jour
Most apps that detect root fall into the payment, banking/investing, corporate security, or (anit cheating) gaming category.
While a lot of apps have their custom root detection routines, with the introduction of SafetyNet the situation for power users has become worse, as developers of those apps can now use a single API to check if the device is not obviously compromised.
SafetyNet is of course developed by Google, which means they can do some tricks that others may not be able to easily do, as they have better platform access and control. In its current incarnation, ultimately the detection routines still run as an unprivileged user and do not yet use information from expected-to-be-secure components such as the bootloader or TPM. In other words, even though they have slightly more access than a 3rd party app, they still have less access than a root app does.
Following from this is that as long as there is someone who is willing to put in the time and effort - and this can become very complex and time consuming very quickly - and SafetyNet keeps their detection routines in the same class, there will in theory always be a way to beat these detections.
While reading that may initially make some of you rejoice, this is in truth a bad thing. As an Android security engineer in Google's employ has stated, they need to "make sure that Android Pay is running on a device that has a well documented set of API’s and a well understood security model".
The problem is that with a rooted device, it is ultimately not possible to guarantee said security model with the current class of SafetyNet tamper detection routines. The cat and mouse game currently being played out - SafetyNet detecting root, someone bypassing it, SafetyNet detecting it again, repeat - only serves to emphasize this point. The more we push this, the more obvious this becomes to all players involved, and the quicker SafetyNet (and similar solutions) will grow beyond their current limitations.
Ultimately, information will be provided and verified by bootloaders/TrustZone/SecureBoot/TIMA/TEE/TPM etc. (Samsung is already doing this with their KNOX/TIMA solutions). Parts of the device we cannot easily reach or patch, and thus there will come a time when these detection bypasses may no longer viable. This will happen regardless of our efforts, as you can be sure malware authors are working on this as well. What we power-users do may well influence the time-frame, however. If a bypass attains critical mass, it will be patched quickly.
More security requires more locking down. Ultimately these security features are about money - unbelievably large amounts of money. This while our precious unlocked bootloaders and root solutions are more of a developer and enthusiast thing. While we're all generally fond of shaking our fists at the likes of Google, Samsung, HTC, etc, it should be noted that there are people in all these companies actively lobbying to keep unlocked/unlockable devices available for us to play with, with the only limitation being that some financial/corporate stuff may not work if we play too hard.
It would be much easier (and safer from their perspective) for all these parties to simply plug that hole and fully lock down the platform (beyond 3rd party apps using only the normal APIs). Bypassing root checks en masse is nothing less than poking the bear.
Nevertheless, users want to hide their roots (so do malware authors...) and at least this implementation of suhide is a simple one. I still think it's a bad idea to do it. Then again, I think it's a bad idea to do anything financial related on Android smartphone that isn't completely clean, but that's just me.
Note that I have intentionally left out any debate on whether SafetyNet/AndroidPay/etc need to be this perfectly secure (most people do their banking on virus ridden Windows installations after all), who should get to decide which risk is worth taking, or even if Google and cohorts would be able to design the systems more robustly so the main app processor would not need to be trusted at all. (the latter could be done for Android Pay, but wouldn't necessarily solve anything for Random Banking App). While those are very interesting discussion points, ultimately it is Google who decides how they want this system to work, regardless of our opinions on the matter - and they want to secure it.
--- reserved ---
Changelogs
2016.10.10 - v0.55 - RELEASE NOTES
- Some code cleanup
- Support for blocking based on process name
- Should fix some crashes (requires uninstall/reinstall to activate)
2016.10.07 - v0.54 - RELEASE NOTES
- Fix for latest SafetyNet update
2016.09.19 - v0.53 - RELEASE NOTES
- Haploid container (monoploid)
2016.09.18 - v0.52 - see v0.51 release notes below
- Fix root loss on some firmwares
2016.09.18 - v0.51 - RELEASE NOTES
- Complete redesign
- Zygote proxying (haploid)
- Binder hijacking (diploid)
- su.d instead of ramdisk modification
- Xposed supported (-ish)
2016.09.04 - v0.16 - RELEASE NOTES
- Fix some SELinux access errors
- Should now work on devices that ask for a password/pattern/pin immediately at boot - for real this time!
- Binderjacking improvements for Nougat
2016.08.31 - v0.12 - RELEASE NOTES
- Fix some issues with suhide-add/rm scripts
- Fix not working at all on 32-bit devices
- Should now work on devices that ask for a password/pattern/pin immediately at boot
- Rudimentary GUI hiding
- No longer limited to arm/arm64 devices: support for x86/x86_64/mips/mips64 devices added
2016.08.29 - v0.01
- Initial release
As always thank you Chainfire! I will try and edit this post.
Edit @Chainfire this seems to work for enabling Android Pay! I didn't get the chance to actually pay yet. But it did let me add my card and did not display the message about a failed authorization of Android check! Before I couldn't even get past that first screen.
Edit 2: @Chainfire It seems to of had an adverse effect on Snapchat. I cleared cache on the app, uninstalled and reinstalled and restarted. It kept Force closing after a photo no matter what. I used suhide-rm and it seems to have fixed the app from any issues. Thanks again and hopefully we'll get you some more reports. Either way your solution works!
Tested on stock rooted 7.0 Nexus 6p.
@Chainfire
What was your reason for doing this project?
Sent from my Nexus 6P using XDA-Developers mobile app
Ofthecats said:
What was your reason for doing this project?
Click to expand...
Click to collapse
For building it, curious if the method I came up with would work well. For releasing, if others are doing it, join them or be left behind.
I'm assuming with custom ROM android pay still won't work right?
HamsterHam said:
I'm assuming with custom ROM android pay still won't work right?
Click to expand...
Click to collapse
I'd just give it a try. It's spoofing the specific app, not the entire ROM that matters. It's fairly simple to try.
Installed on LG G4 w/ V20g-EUR-XX update and rerooted with TWRP 3.0.2-0 and SuperSU-v2.76-2016063161323. seems to be working fine, for the moment. Thank you for the update.
So far so good, I was able to add card to android pay. I would try using it during lunch and report back. Again, thanks for the continuous hard work.
djide said:
So far so good, I was able to add card to android pay. I would try using it during lunch and report back. Again, thanks for the continuous hard work.
Click to expand...
Click to collapse
What was the UID or process you found to blacklist it with?
Sent from my ONEPLUS A3000 using Tapatalk
how to install it? which file should I flash ? Both?
I can't see to add an app using terminal.
I'm typing in
/data/adb/suhide-add 10284
Says file not found. Can someone help, cheers.
Joshmccullough said:
What was the UID or process you found to blacklist it with?
Click to expand...
Click to collapse
Android Pay comes blacklisted out-of-the-box
HamsterHam said:
I can't see to add an app using terminal.
I'm typing in
/data/adb/suhide-add 10284
Says file not found. Can someone help, cheers.
Click to expand...
Click to collapse
Are you in Android or TWRP ?
ls -l /data/adb/
Chainfire said:
Android Pay comes blacklisted out-of-the-box
Click to expand...
Click to collapse
Derp. That's what I get for not reading the entire sentence under 'Install' in the OP......thanks!
PedroM.CostaAndrade said:
how to install it? which file should I flash ? Both?
Click to expand...
Click to collapse
Please don't quote a large post like that just to ask a single question.
Please read the first post, so you know what to do.
OnePlus 2 here, stock 6.0.1, systemless rooted with SuperSU Pro v2.76, flahed using Flashfire.
Passes SafetyNet check, does not pass my bank's root check, propably for the reasons the OP states above.
thdervenis said:
OnePlus 2 here, stock 6.0.1, systemless rooted with SuperSU Pro v2.76, flahed using Flashfire.
Passes SafetyNet check, does not pass my bank's root check, propably for the reasons the OP states above.
Click to expand...
Click to collapse
You need to blacklist the UID for your bank. Directions are in the OP.
Hi, im running Android 10 with OneUI 2.5 rooted by Magisk v.21 on my Samsung Galaxy NOTE 10 Lite,
Root is working correctly, i have root access for donated FDE.AI, X-Plore file manager and etc..
Im using few Magisk modules, like Viper4Android and they works well too.
But, any atempt to download or install Magisk module from its own online reposirory ends with "Error downloading file", and atempt to check SafetyNet status gives me "SafetyNet API error" afzer hiting Ok to download SafetyNet API...
I searched on google, and here on the forum for similar problems, but i found topics from 2017 year (outdated)
Can anyone hp me solve this prob please?
Both those issues (module download error and SafetyNet API error) suggest that there are Internet connection problems.
There's been a couple of similar reports, but those have usually been fixed by clearing data for, or reinstalling the Manager.
Also make sure that you don't have any firewall rules or similar that might be restricting internet access for the Manager.
Thx for respone. I tried to delete Managers cache and App data too, nothing changes. I also tried to reinstall App, but no change.
About internet connection, yesterday I had to downgrade Magisk from v.21 beta to v.20.4 stable for unexpected random reboots 5times a day.. I done that in Magisk Manager App, selecting "Direct install (recommended)". Magisk downloaded necessery files without any problem and flashed it.
And, i dont use any third party security apps (antivirus, firevall).
So, any idea? After downgrade magisk reboots solved, here reported issue no.
No idea. A logcat might show what's up:
https://www.didgeridoohan.com/magisk/MagiskHelp
Heres my logcat, filters: level error, keyword magisj
Heres my new logcat, printed at error level verbose, filtered by keyword magisk.
I see only one problem, file permission (write permission), but where magisk wont write? Im able seriously give 777 permissions to this folder ?
Or did anybody see anything else?..
For now, nothing changes in my phone configuration.. FW version the same as in 1. Post, magisk v 20.4, actual stable magisk manager.. I also tried canary magisk manager, but the canary version wont load module list and crashed down at all, including UI.
KubikMichal5 said:
Heres my new logcat, printed at error level verbose, filtered by keyword magisk.
I see only one problem, file permission (write permission), but where magisk wont write? Im able seriously give 777 permissions to this folder
Or did anybody see anything else?..
For now, nothing changes in my phone configuration.. FW version the same as in 1. Post, magisk v 20.4, actual stable magisk manager.. I also tried canary magisk manager, but the canary version wont load module list and crashed down at all, including UI.
Click to expand...
Click to collapse
I have not had any opportunity to look at your log (and the new one won't download since it seems like the XDA attachments server is acting up again, good thing there's a new one on the way).
But, that the Canary Manager will crash when you try to access the modules list is yet another sign that your issue is that the Manager cannot get an internet connection (that's a currently known bug).
Thx u for your time . So, its known bug, but is there some way to solve it and get magisk manager functional? Or its not a global issue and its not specific to each user
It's a known issue that the Manager will crash when you enter the modules download section without an internet connection. It's not a common issue that the Manager can't get a connection at all.
I still suspect that there's something on your device that is blocking internet access for the Manager somehow.
Have the same problem.Magisk Manager 8.0.2 on Android 9,Magisk is working fine,but i become no update info for modules and i cant download any module,but 3 days ago all was ok,weird.
I think, that is not any app blocking magisk internet connection. The last stable mahisk manager dont have any problem to load online module list, and download of magisk core is aleays possible, as install ing core too....
But, i dont have time right now for test it, it is possible to reboot to safe mode and there run magisk?
I still cant understand that some app blocking magisk internet connection...
Look at my screenshot of magisk manager latest stable version, the connection working, magisk showing modules wich got updated today......
Sorry, but i still hope, that magisk manager do not have internet connection error, in screen, he knows about the module updated version, but it still wont download..
Im ready for N770FXXU6CTJ2 update, im going to flash it right now... Im confused of magisk support,
Is that last one with the Stable or Canary Manager? There seems to be something weird going on, and there have been some similar reports.
I suggest that you switch over to Canary again (Magisk and Manager) and grab a verbose logcat when you have connection issues. Upload that to a new GitHub issue where you also make sure to give all possible details as to what works and don't work on the stable Manager contra what works and doesn't work on the Canary Manager.
That way, better eyes than mine might be able to take a look at it and see if there is indeed something going on.
Nevermind... See below.
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Ok... Nice to know I wasn't wrong. :good:
Sad to see that app being used...
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Awesome,hughe thanx,works for me.Cheers!!!
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Life saver! It solved my problem too. Huge thanks!
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Thanks!!!!
I'm having an issue also with passing safetynet on Razer Phone 2 (Cheryl 2). Rooted with Magisk 22.1 and TWRP arter Kernel. Had a rough time getting the "new" all-in-one Magisk installed properly. I'm using adfree for an adblocker. I've cleared the hosts file and rebooted MANY times, to no avail. Thinking I may need to uninstall Magisk and go back to 20.4 and install the old Magisk Mgr. app. Any help would be appreciated. If you need log files, let me know. I DO have root as Ti Backup, ROM Toolbox, adfree all have root access.
Hello everybody,
I'm am a new member in this forum and a totally newbie in this theme.
More exactly I don't really know what I'm doing (it's not really so bad, but nearby) and I apologize for my maybe strange explanations in forehand, my English is not the best.
It's my first OnePlus phone and the first time I use a rooted one and I had help with the installation, of course. I knows a little bit of linux, but of course I have a lot to learn and I really would like to learn, so I hope you will be a bit patient.
Now to my phone.
It's a OnePlus Nord CE with 128GB Rom and 8 GB RAM.
Installed is the lineage.os version 18.1 and Kali Nethunter Version 2022.2 kernel version 4.19.125-GNorth(if necessary date: 2022-05-18)
Busybox Version v1.30.1-osm0sis
Root Status 25.2 MAGISKSU
Hope this is everything you need to know.
Now to the problem.
I tried to update nethunter but it doesn't work. After using apt update, but it returned the message:
temporary failure resolving http.kali.org
reading package lists.... done
etc.
All packages are up to date
W: Failed to fetch http://http.kali.org/kali/........ temporary failure resolving http.kali.org
W: some index files failed to download. etc.
I tried different solutions, but nothing worked.
- Change the sources.list into https://http.kali.org/...
- set new DNS servers at the resolve.conf
- reinstall the terminal
- reinstall nethunter
- try systemctl start systemd-resolved.service (doesn't work: answer is "running in chroot ignoring start")
When I use ifconfig everything seems ok, I got an IP address from my router.
It's just inside the terminal. Everything else where I need an internet connection works at the phone.
Also for example nmap scan of the open ports is working. It answered first with a warning that there is no DNS, but it worked. After I use the --dns-servers attribute (forgot the right word for it) the message didn't come again.
Next strange thing: The ping
I'm not able to ping anything inside or outside the network.
I got this message:
ping: socket: permission denied (but of course I am root)
Sometimes it worked when I use sudo before ping, but only when I try to ping the router and then I get the same failure with the dns.
When I use nmap for a ping it looks like it is working.
I really hope somebody can help me.
Thanks a lot,
angelsamira
angelsamira said:
Hello everybody,
I'm am a new member in this forum and a totally newbie in this theme.
More exactly I don't really know what I'm doing (it's not really so bad, but nearby) and I apologize for my maybe strange explanations in forehand, my English is not the best.
It's my first OnePlus phone and the first time I use a rooted one and I had help with the installation, of course. I knows a little bit of linux, but of course I have a lot to learn and I really would like to learn, so I hope you will be a bit patient.
Now to my phone.
It's a OnePlus Nord CE with 128GB Rom and 8 GB RAM.
Installed is the lineage.os version 18.1 and Kali Nethunter Version 2022.2 kernel version 4.19.125-GNorth(if necessary date: 2022-05-18)
Busybox Version v1.30.1-osm0sis
Root Status 25.2 MAGISKSU
Hope this is everything you need to know.
Now to the problem.
I tried to update nethunter but it doesn't work. After using apt update, but it returned the message:
temporary failure resolving http.kali.org
reading package lists.... done
etc.
All packages are up to date
W: Failed to fetch http://http.kali.org/kali/........ temporary failure resolving http.kali.org
W: some index files failed to download. etc.
I tried different solutions, but nothing worked.
- Change the sources.list into https://http.kali.org/...
- set new DNS servers at the resolve.conf
- reinstall the terminal
- reinstall nethunter
- try systemctl start systemd-resolved.service (doesn't work: answer is "running in chroot ignoring start")
When I use ifconfig everything seems ok, I got an IP address from my router.
It's just inside the terminal. Everything else where I need an internet connection works at the phone.
Also for example nmap scan of the open ports is working. It answered first with a warning that there is no DNS, but it worked. After I use the --dns-servers attribute (forgot the right word for it) the message didn't come again.
Next strange thing: The ping
I'm not able to ping anything inside or outside the network.
I got this message:
ping: socket: permission denied (but of course I am root)
Sometimes it worked when I use sudo before ping, but only when I try to ping the router and then I get the same failure with the dns.
When I use nmap for a ping it looks like it is working.
I really hope somebody can help me.
Thanks a lot,
angelsamira
Click to expand...
Click to collapse
Nethunter is only released for OnePlus Nord, not OnePlus Nord CE. This is why you experience such issues
Sony make.believe said:
Nethunter is only released for OnePlus Nord, not OnePlus Nord CE. This is why you experience such issues
Click to expand...
Click to collapse
Hm, that's bad...
Is there any possibility to fix that?
angelsamira said:
Hm, that's bad...
Is there any possibility to fix that?
Click to expand...
Click to collapse
Kali NetHunter | Kali Linux Documentation
Kali on your Android phone
www.kali.org
Try to build it
I think you can also write a request to developers of nethunter or the maintainer of OnePlus Nord, maybe someone is already working on something?
Sony make.believe said:
Kali NetHunter | Kali Linux Documentation
Kali on your Android phone
www.kali.org
Try to build it
I think you can also write a request to developers of nethunter or the maintainer of OnePlus Nord, maybe someone is already working on something?
Click to expand...
Click to collapse
Well, building one is not an option. I'm million miles away from knowing and understanding enough, even to try it.
But a request to the developers is a goog idea.
Thank you
Hi
I have the same phone and I ran into the same problem but I managed to fix it
enter these(without "") in the terminal(Kali) and then it's fixed:
"echo 'APT::Sandbox::User "root";' > /etc/apt/apt.conf.d/01-android-nosandbox"
"groupadd -g 3003 aid_inet && usermod -G nogroup -g aid_inet _apt"
Happy (almost)Hunting...