Hi Fellow devs,
As you may know, I have been compiling Android 4.0-4.3-based ROMs for Galaxy Tab 10.1. Currently, I am trying to get kitkat 4.4 to work on our devices.
Although I can compile a ROM with only minor difficulties, it already fails when flashing a ROM. It errors with the following message: "set_metadata_recursive: some changes failed". I think this is related to the new way of setting permissions in KK4.4.
If I look in the recovery.log after flashing, I see this:
minzip: Extracted 1197 file(s)
ApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip
I have no idea whether the problem is that the recovery needs an update, or the updater binary is not yet finished, or that the updater script needs to be adjusted.
Anyone also working on this?
Hello, although I'm not a rom dev, I think I found the problem and a possible solution.
http://forum.xda-developers.com/showthread.php?p=47212560#post47212560
Here, I hope it's of some use to you. Keep up the good, quality work!
miztahbeezy said:
Hello, although I'm not a rom dev, I think I found the problem and a possible solution.
http://forum.xda-developers.com/showthread.php?p=47212560#post47212560
Here, I hope it's of some use to you. Keep up the good, quality work!
Click to expand...
Click to collapse
Thanks. I guess it is related to recovery then, with a need for an updated recovery. I guess that the lack of proper selinux support may also contribute to the problem....
OK, I tried to build both cwm & twrp based on latest kk source code. Recovery image is always over 5.5MB, which is way too large for our device, as our recovery partition is only 5MB. Even when trying to strip recovery & recompile kernel with maximum compression, I can't get to 5MB.
So then I tried a different route, I put the old permission code from an updater-script from jb4.3 in a kk4.4 ROM. Flashing such a ROM works, but it hangs on the bootanimation. Logcat won't connect, so I couldn't find the source of the problem.
Verstuurd van mijn Nexus 5
Go Kasper! ben trots op je! (proud of you!)
kasper_h said:
OK, I tried to build both cwm & twrp based on latest kk source code. Recovery image is always over 5.5MB, which is way too large for our device, as our recovery partition is only 5MB. Even when trying to strip recovery & recompile kernel with maximum compression, I can't get to 5MB.
So then I tried a different route, I put the old permission code from an updater-script from jb4.3 in a kk4.4 ROM. Flashing such a ROM works, but it hangs on the bootanimation. Logcat won't connect, so I couldn't find the source of the problem.
Verstuurd van mijn Nexus 5
Click to expand...
Click to collapse
kasper_h said:
Hi Fellow devs,
As you may know, I have been compiling Android 4.0-4.3-based ROMs for Galaxy Tab 10.1. Currently, I am trying to get kitkat 4.4 to work on our devices.
Although I can compile a ROM with only minor difficulties, it already fails when flashing a ROM. It errors with the following message: "set_metadata_recursive: some changes failed". I think this is related to the new way of setting permissions in KK4.4.
If I look in the recovery.log after flashing, I see this:
minzip: Extracted 1197 file(s)
ApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip
I have no idea whether the problem is that the recovery needs an update, or the updater binary is not yet finished, or that the updater script needs to be adjusted.
Anyone also working on this?
Click to expand...
Click to collapse
Just sent a message to pershoot on gtalk or whatever its supposed to be called, I'll let you know if he says he'll take a look at it
update: he's hasn't been working on the sgt 10.1 in a long time, but if he get's some free time, he might look at it.
good luck either way, you seem to have no trouble pumping out good stuff, I'm sure you'll get it figured out
I'm no developer, but I did some Google search about the error. Most people said that latest recovery is needed, but there's another guy with a different point of view: http://stackoverflow.com/questions/19860479/set-metadata-recursive-failing-on-android-install
Good luck getting KitKat to boot on our tabs!
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
I'm no developer, but I did some Google search about the error. Most people said that latest recovery is needed, but there's another guy with a different point of view: http://stackoverflow.com/questions/19860479/set-metadata-recursive-failing-on-android-install
Good luck getting KitKat to boot on our tabs!
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, any help is appreciated!
I actually got recovery to shrink enough to fit in the recovery partition. It just won't boot
The struggle continues
Well then let's just hope that pershoot finds some time to help us out.
Sent from my GT-P7500 using Tapatalk HD
kasper_h said:
Thanks, any help is appreciated!
I actually got recovery to shrink enough to fit in the recovery partition. It just won't boot
The struggle continues
Click to expand...
Click to collapse
Could you please share the recovery?
I found this thing ro.build.selinux=1 in the build.prop. Is there someway to change this to 0 and removing all the set_metadata_recursive lines from the updater-script? Doesn't work
Here's what I've tried so far: I followed my android 4.3 guide but it needs some extras. There's 1 header line from libnbaio/audiostreamoutsink that needs to be removed. The error message tells you exactly which one. I also had to comment out 2 lines in surfaceflinger to prevent a very annoying crash I got when I first did android 4.3. There are a few other random lines from audioflinger that have to be removed but the error messages are pretty specific on which ones those are. I also cheated the recovery's gr_text that it said was missing and added in a dummy function according to the header since I never planned to use the recovery and just put that in to get it to compile. I can't get past a metadata error in cwm recovery from pershoot. My TWRP refuses to install the zip at all.
AAccount said:
Could you please share the recovery?
I found this thing ro.build.selinux=1 in the build.prop. Is there someway to change this to 0 and removing all the set_metadata_recursive lines from the updater-script? Doesn't work
Here's what I've tried so far: I followed my android 4.3 guide but it needs some extras. There's 1 header line from libnbaio/audiostreamoutsink that needs to be removed. The error message tells you exactly which one. I also had to comment out 2 lines in surfaceflinger to prevent a very annoying crash I got when I first did android 4.3. There are a few other random lines from audioflinger that have to be removed but the error messages are pretty specific on which ones those are. I also cheated the recovery's gr_text that it said was missing and added in a dummy function according to the header since I never planned to use the recovery and just put that in to get it to compile. I can't get past a metadata error in cwm recovery from pershoot. My TWRP refuses to install the zip at all.
Click to expand...
Click to collapse
Hi AAccount, thanks for joining in! I also talked to matt604 through gtalk last night. Glad to see I am not alone
I am trying to compile OMNI in stead of CM. Advantage is that it does not require any changes to the source code to compile for p4wifi. Works fine for 4.3 as well.
Anyway. I think we have two options: give proper SELinux support, which means making a SE policy for our device. Or we have to completely get rid of it. Because I think the second is simpler, I chose that route. What I did:
-Add the ro.boot.selinux=disabled prop (maybe we should try ro.build.selinux=0 as well!)
-I removed all the SELinux patches from the kernel (so essentially go back to the 4.2 kernel). This kernel boot fine on 4.3
-Manually swap the set_metadata lines in the updater script by set_perm lines from a 4.3 script (I compared the two and besides the change from set_prop to set_metadata, the permissions set are the same).
This time the ROM booted. But when I saw the launcher for 0.1 sec, I got a "Launcher3 has unexpectedly stopped" error. And with the current security feature for adb, you can't get a logcat on a fresh ROM boot, as you need to approve the connection first, which is impossible due to the continuous FC.
I then also tried adding Apex Launcher (confirmed working on KK on my Nexus 5) - first added to system/app and then moved to /data/app. Both times didn't boot at all.
Removed Launcher3 with Apex in /system/app. Didn't boot.
But at least I saw kitkat running for 0.1sec on my tab, so I feel it should be possible!
My next step:
-Add the HAVE_SELINUX := false flags to BoardConfigCommon
-Add ro.build.selinux=0 to p4-common.mk
Samsung have updated their several devices which latest firmware of Android which are old but popular as new. Now the devices are on an end of its update life cycle on Jelly Bean. But the upcoming Google's Android 4.4 KitKat rise an hope for the older Galaxy phone as the KitKat is rumored to feature an improved Linux kernel supporting lower memory devices.
Here is the list of nominated Galaxy Devices for Android 4.4 KitKat
Galaxy Grand and Grand DUOS
Galaxy Ace II
Galaxy S III mini
Galaxy Beam
Galaxy Express
Galaxy S Advance
Galaxy S II and S II Plus
Galaxy Premier
Galaxy Note I
Galaxy Young and Young DUOS
Galaxy Fame
Galaxy X Cover 2
Galaxy Tabs
Click to expand...
Click to collapse
I think it's a little obious that our revoceries are not compatible anymore with android 4.4 since there changed alot in recoveries... So.. Older versions of CWM won’t work, nor will TWRP. I think we will need at least cwm 6.0.4.3 to be compatible with kitkat 4.4, our latest recovery is and older build (cwm 6.0.3.6) which is ment to be for android 4.2.2
Edit:
Looks like it's also because of selinux, and you need a newer version of TWRP or cwm as i said. Right now in the Omni 4.4 manifest it actually has the AOSP recovery so you'll wanna change that to Omni 's TWRP on a local manifest. Or at least you need a recovery with proper fstab because the new fstab format in Android 4.3+ is not used by TWRP yet. Beyond that it depends on your BoardConfig.mk whether the recovery is flash able, if you configured it ok then yes!
kasper_h said:
Hi AAccount, thanks for joining in! I also talked to matt604 through gtalk last night. Glad to see I am not alone
I am trying to compile OMNI in stead of CM. Advantage is that it does not require any changes to the source code to compile for p4wifi. Works fine for 4.3 as well.
Anyway. I think we have two options: give proper SELinux support, which means making a SE policy for our device. Or we have to completely get rid of it. Because I think the second is simpler, I chose that route. What I did:
-Add the ro.boot.selinux=disabled prop (maybe we should try ro.build.selinux=0 as well!)
-I removed all the SELinux patches from the kernel (so essentially go back to the 4.2 kernel). This kernel boot fine on 4.3
-Manually swap the set_metadata lines in the updater script by set_perm lines from a 4.3 script (I compared the two and besides the change from set_prop to set_metadata, the permissions set are the same).
This time the ROM booted. But when I saw the launcher for 0.1 sec, I got a "Launcher3 has unexpectedly stopped" error. And with the current security feature for adb, you can't get a logcat on a fresh ROM boot, as you need to approve the connection first, which is impossible due to the continuous FC.
I then also tried adding Apex Launcher (confirmed working on KK on my Nexus 5) - first added to system/app and then moved to /data/app. Both times didn't boot at all.
Removed Launcher3 with Apex in /system/app. Didn't boot.
But at least I saw kitkat running for 0.1sec on my tab, so I feel it should be possible!
My next step:
-Add the HAVE_SELINUX := false flags to BoardConfigCommon
-Add ro.build.selinux=0 to p4-common.mk
Click to expand...
Click to collapse
Perhaps this might be useful to you:
http://forum.xda-developers.com/showthread.php?t=2457427
Its a sort of work around to pre authorise the ADB connection to your computer using the ADB authentication keys from a working (i.e. 4.3 ROM) build.
It sounds like a very long work around though. Also don't want to sound insulting but did you remembered to put the appropriate mount and install lines for Apex while in /data/app into the updater script!
scaryshark said:
Perhaps this might be useful to you:
http://forum.xda-developers.com/showthread.php?t=2457427
Its a sort of work around to pre authorise the ADB connection to your computer using the ADB authentication keys from a working (i.e. 4.3 ROM) build.
It sounds like a very long work around though. Also don't want to sound insulting but did you remembered to put the appropriate mount and install lines for Apex while in /data/app into the updater script!
Click to expand...
Click to collapse
Thanks.
Don't worry, I am not easily insulted I even checked through a file manager whether apex ended up in the right spot. I didn't check permission though, so that may have been wrong, but I am almost sure I checked that one well...
Thanks kasper_h for your hard work. I thought HAVE_SELINUX boardconfig flag was only for android 4.2. I read that here http://selinuxproject.org/page/SEAndroid#Merge_Status. Another thing i t tried was changing the ro.selinux flag in 4.3.1 to see if it made any difference in the about device selinux status page. Setting that flag to disabled or 0 didn't effect that. Ill try omni rom next but i have limited time this weekend though. I agree a removal would be ideal. I disable it on my desktop and laptop right away after installing fedora.
Sent from my GT-P7510 using xda app-developers app
I now managed to get it to boot. But I get fatal errors in AUDIO_SERVICE, crashing the system. I had something similar when trying to compile AOSP in the past. Maybe CM11 is a better choice than OMNI...
I'll keep on trying.
But at least, getting rid of SELinux seems to be thé way to go.
So the xda app messed up my post big time. What I wanted to say was that by using a non selinux kernel, setting the selinux build.prop flag and changing the install script it boots? Yesterday I tried doing the build.prop edit on my cm11 rom and it didn't boot. Very interesting suggestion about the kernel though.
--------------------------------------------Added-----------------------------------------------------------------------
I tried the 3 things you did on my cm11 rom from yesterday:
-Add the ro.boot.selinux=disabled prop (maybe we should try ro.build.selinux=0 as well!)
-I removed all the SELinux patches from the kernel (so essentially go back to the 4.2 kernel). This kernel boot fine on 4.3
-Manually swap the set_metadata lines in the updater script by set_perm lines from a 4.3 script (I compared the two and besides the change from set_prop to set_metadata, the permissions set are the same).
and I can't get past the "samsung galaxy tab 10.1" screen. Note I did these things after the rom was compiled since build.prop can be edited from the update zip and I just flashed an older A1 kernel with no selinux.
kasper_h said:
I now managed to get it to boot. But I get fatal errors in AUDIO_SERVICE, crashing the system. I had something similar when trying to compile AOSP in the past. Maybe CM11 is a better choice than OMNI...
I'll keep on trying.
But at least, getting rid of SELinux seems to be thé way to go.
Click to expand...
Click to collapse
Finally downloaded the omnirom source. A possible cause of this is becasue omni rom has no ICS_AUDIO_BLOB flag in its source at all. You'll probably need to take a working android 4.3 source, do a "grep ICS_AUDIO_BLOB -r ." on the source and find every place in the working source this flag is defined and then transfer it over to omni rom. Yes it sounds like a pain in the butt.
AAccount said:
Finally downloaded the omnirom source. A possible cause of this is becasue omni rom has no ICS_AUDIO_BLOB flag in its source at all. You'll probably need to take a working android 4.3 source, do a "grep ICS_AUDIO_BLOB -r ." on the source and find every place in the working source this flag is defined and then transfer it over to omni rom. Yes it sounds like a pain in the butt.
Click to expand...
Click to collapse
Maybe it is easier to swap all OMNI project that contain ICS_AUDIO_BLOB in CM for the CM-code
With regard to the kernel, you can't flash a 4.2 kernel on 4.4, as there are ramdisk changes causing it to not boot. I can send you a kernel that will boot on 4.4 that you could try to flash on top of CM11....
I will try a kernel on CM11 and then compare the ramdisk to OMNI to see if that gives a hint why it won't boot...
kasper_h said:
Maybe it is easier to swap all OMNI project that contain ICS_AUDIO_BLOB in CM for the CM-code
With regard to the kernel, you can't flash a 4.2 kernel on 4.4, as there are ramdisk changes causing it to not boot. I can send you a kernel that will boot on 4.4 that you could try to flash on top of CM11....
I will try a kernel on CM11 and then compare the ramdisk to OMNI to see if that gives a hint why it won't boot...
Click to expand...
Click to collapse
What are those ramdisk changes? That would probably help for the rom not booting.
Hi,
I'm currently running Slimkat 6.7 on my i8190, and it's fantastic. The only problem is that the system log is filling up with the following line:
E/bt_upio (31479): upio_set : open(/proc/bluetooth/sleep/btwrite) for write failed: No such file or directory (2)
I've googled it, and there doesn't appear to be much info around as to a fix - does anyone have any idea whether this bug is known/fixed?
Many thanks, Jaime
Ok, at the moment, I'm not even sure whether this is a kernel or a rom problem. I'll try flashing a different kernel or two, and I'll report back in case anyone can pitch in with some helpful advice...
J
Ok, I've tried the kernel built in to Android Andi's latest (Slim-golden-4.4.4.build.7.2.1-UNOFFICIAL-20140812-2310.zip) and that has the bug. I've also tried flashing the 2 kernels bundled into GT-I8190-ANY-Kernel_v1.6.zip (that's version 3.0.31 and 3.0.44) and they too have the same problem. Any ideas anyone?
Greetings.
So ever since (Late April?) the LineageOS 18.1 official builds for the Pixel 4a5g (bramble) stopped and are now on 19.1, I was curious to endevour into the world of building. I wasn't ready to upgrade to Android 12 yet and so I wanted to see if I could build an equivlent up-to-date unoffical "nighly" build for my device. BIG MISTAKE, haha. I had to go through many trial and error build runs having to deal with everything from out of memory (ram), out of hard drive space (200gb+!!), out of java heap space, build failed (after 12-18 hours!). Oh yea, and I'm doing this all on an AMD A-10 6800k (circa 2013?) with 16GB of ram but on a virtual machine w/ around 12GB of RAM and utilizing all 4 cores writing inside a 500gb VDI HDD vm container file with a 30gb /swap partition on Debian 11. Good times.
So anyhow, since I'm having to wait for these builds to finish, I can now qualfiy for Social Security. To those people with super-duper 8/10/16/32+ core cpu's with 32-64GB ram able to build complete roms within 40min to an hour (or 2)--I hate you.
So after all the trial and errors and LEARNING. I have finally been able to complete a build! At first I was missing vender blobs but was able to pull them with TheMuppets repo.
I followed these guides (substituting 18.1 for 19.1):
https://wiki.lineageos.org/devices/bramble/build (following just this would fail the build after a few eons with various errors)
(these 2 youtube vids helped me with creating roomservice.xml and pulling vendor blobs vs extraction via rom/firmware.zip or device).
Some of the errors during the builds (not necessessarly both as just one of these errors would stop the whole process. The errors are combined here for reference as these were obtained on a trial and error basis (Try this. fail. Try this...get little further fail, try this build suceeded with warnings, etc etc)
Code:
java.lang.OutOfMemoryError: Java heap space
ERROR:payload_generation_config.cc(200)] Sum of sizes in google_dynamic_partitions_partition_list is 4879237120, which is greater than google_dynamic_partitions_size (4873781248)
FATAL:generate_delta_main.cc(619)] Check failed: payload_config.target.ValidateDynamicPartitionMetadata().
It took around 18 hours for it to attempt to build and end with those errors, which were resolved by a couple 'export' commands I entered before re-running the build(s):
Code:
export _JAVA_OPTIONS=-Xmx2096m
or
Code:
export _JAVA_OPTIONS="-Xmx4g"
or was it
Code:
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4096m"
(my mind is a little mush so I don't rememer which one(s))
and
Code:
export WITH_GMS=true
re-ran brunch bramble and it compiled and only took about 40 minutes this time. Probally because I had ccache enabled per the build instructions.
YAY it built. But I am concerned about a couple warnings I recieved during the build process:
Should I be worried about these warnings? Can anyone advise?
Code:
depmod: WARNING: could not open modules.order at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.builtin at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.order at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_ramdisk_intermediates/lib/modules/0.0: No such file or directory
depmod: WARNING: could not open modules.builtin at /home/user/android/lineage/out/target/product/bramble/obj/PACKAGING/depmod_vendor_ramdisk_intermediates/lib/modules/0.0: No such file or directory
This is my first ever attempt at building LineageOS from source, so I'm a little proud of myself for making it this far. But any help on those warnings, if I even need to worry about it, would be appreciated. I have NOT flashed this new unoffical build yet.
Thank you!
* Logs can be provided upon request. I think there are many to choose from it seems in the /out folder.
If anyone wants to try it (and have courage I lack) here it is:
Downloads for : Google Pixel 4a 5g | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
https://www.androidfilehost.com/?w=files&flid=335433
Not sure if you have to wipe first since going from official to unoffical. I don't have encryption and staying w/i 18.1 so hopefully not. Regardless back up your phone. Flash/Install at your own risk.
Dont install this. Caused a boot loop and clearing cache didnt resolve. So reverting to backup. Oh well.
*Might actually work on a clean a wipe and reinstall of gapps.
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...