Database Info

[Q] Samsung Galaxy g4 4.4.2 .config needed

I am trying to fix an issue with our phones -> code.google.com/p/android/issues/detail?id=67406
I can successfully adb connect to the device but no where can I find a .config or a /proc/config.gz in order to get the running kernel parameters.
How can I get a hold of either the proper .config for a kernel recompile or an already compile image with the patch installed?
I see folks doing custom ROMs with the same galaxy, so I know it can be done.
galaxy s4 sgh-i337 4.4.2

[Q][Solved][XT897] cifs module for CM 11 (3.0.101 Kernel)?

Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx

Fr4nz84 said:
Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx
Click to expand...
Click to collapse
Why the quotes around "official"?
Cifs and nfs support is built-in, there's no need for additional loadable kernel modules (you can check https://github.com/CyanogenMod/andr.../arch/arm/configs/msm8960_mmi_defconfig#L3091 )
If mount fails for you, try busybox mount.
Btw., after CM11 M2, Motorola msm8960 2012 devices were unified under moto_msm8960 moniker in CM11.
Later, after the release of the official KitKat update for only a subset of the devices being part of the moto 2012 family, xt897 builds went under moto_msm8960_jbbl (jellybean bootloader) unified builds.
So the latest CM11 builds for xt897 can be found here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
For CM12, the builds were separated again, so CM12 builds for xt897 can be found again under http://download.cyanogenmod.org/?device=xt897

A other problem?
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.

I've always accessed CIFS shares thru an app like ES File Explorer. Works fine.

Fr4nz84 said:
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.
Click to expand...
Click to collapse
CM11 M2 is quite old, so I can't be 100% sure it worked there, but I'm convinced that it worked fine even on such old build.
I mount cifs shares quite regularly on my xt897, so I guess I would have noticed if it was not working anymore in any milestone build.
Regarding SuperSU and BusyBox Free - there's no need to install anything like that, CM has built-in su and also busybox.
I'm on CM12 and I don't plan to restore CM11 any time soon (and certainly not M2, if anything it would be moto_msm8960_jbbl M12 or a recent moto_msm8960_jbbl nightly), but something like this has always worked for me:
Code:
su
mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I've just tested it (indeed with my own server path and user credentials) and it works fine.
To use busybox for mount, just replace "mount -o..." with "busybox mount -o..."
The stock CM busybox resides in /system/xbin , btw.

@arrrghhh good tip! Compared to AndSMB I can at least look at pictures without downloading with hand.
@kabaldan
You are totally right with cat /proc/filesystems I can see the Kernel supports cifs.
I had to install SuperSu because there was no su in terminal available.
After playing around, I was able to mount with:
mount -o username=franz,password=XXX,rw,nodev,relatime,default_permissions,allow_other -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
But it’s only available to the terminal where I executed the command. Do I have multiple root users?
I don’t know something in my system feels wrong.
Could there some other security policy I am not aware of?

It works now. It seems it was a update problem.
I wipe/clean the system with Open Recovery
removed all Files and Folders in /system (To remove old apps especially SuperSu)
And installed cm-11-20140104-SNAPSHOT-M2-xt897.zip again with Open Recovery
Now su is there on start and root is managed by the System. And I can mount cifs normally.
Whatever, now the shell seams not proper configured so I get this ^[[A^[[D^[[C for arrow keys, in su.
Also I can't get Link2Sd to work because mount give me constantly "invalid argument"( not more) even when I try it on console. Fells like it don’t want me to mount my second partition.

OK is a problem with the SD Card mount works normally. I tested it with another sd card.

How to build custom ROM for enchilada(One Plus 6)?

I am new to AOSP development and want to flash a custom ROM for One Plus 6. I have done the following things:
1. Sync compatible source code with Enchilada:
- Find the build version of One Plus 6: Run adb shell getprop | grep ‘ro.build.id’ This will print OPM1.171019.011.
- Find the similar version at:https://source.android.com/setup/start/build-numbers.html#source-code-tags-and-builds. I found
OPM1.171019.011 android-8.1.0_r1 Oreo Pixel 2 XL, Pixel 2, Pixel XL, Pixel, Pixel C, Nexus 6P, Nexus 5X 2017-12-05
- Initialize repo using repo init -u https://android.googlesource.com/platform/manifest -b android-8.1.0_r1
- Finally, sync the code using repo sync
2. Find the proprietary binaries for the device. I have searched on google and find the below results:
- https://github.com/wuxianlin/android_device_oneplus_enchilada/tree/android-8.1/recovery/root. Here I found the vendor folder but I am not sure that I should copy this vendor folder directly into the aosp source or I need to configure it before copying?
- https://github.com/OnePlusOSS/android. Here, I found that there may exist pull_library.sh in the mobile itself but I am not able to find this file. The One Plus 6 device that I have is rooted and its bootloader is already unlocked. When I have tried to find the file using adb shell ls -lR | find "pull_library.sh" then I got permission errors. Resolved permission errors with `su` but got no result for `ls -lR | find "pull_library.sh"`.
- I have also searched an article https://forums.oneplus.com/threads/...vice-tree-kernel-source-for-oneplus-6.833612/. It refers to a GitHub page for the device tree https://github.com/OnePlusOSS. But due to my insufficient knowledge, I am not able to find the right device tree for my One Plus 6.
- https://forum.xda-developers.com/oneplus-6/development/official-xenonhd-8-1-t3868368 also have device tree and kernel code.
I just need help to understand the process to add binaries in aosp code. If someone can help me to go in right directions then I will be very thankful.

Kali Nethunter

Hi all!
Does anyone have a guide on how to install kali nethunter on flat s7 exy?
I saw a guide somewhere but the download link was not good anymore.
I know I need to have already an android installed and with initial setup done then flash kali from twrp.
1.What version of android I need?
2.Where I can find the right kali nethunter image to flash?
3.Does anyone use kali nethunter on an s7 with an wifi external adapter?

Kali-Nethunter
vladvlad12 said:
Hi all!
Does anyone have a guide on how to install kali nethunter on flat s7 exy?
I saw a guide somewhere but the download link was not good anymore.
I know I need to have already an android installed and with initial setup done then flash kali from twrp.
1.What version of android I need?
2.Where I can find the right kali nethunter image to flash?
3.Does anyone use kali nethunter on an s7 with an wifi external adapter?
Click to expand...
Click to collapse
Hello,
I am new to Nethunter, with the help XDA I got it to work on my S7 Exynos with LightROM [Android 8 Oreo] (https://forum.xda-developers.com/galaxy-s7/development/teamexykings-lightrom-t3816609), and I figured out that kali-nethunter has their own kernel-building tutorials and scripts, so you can also build it (https://www.kali.org/docs/nethunter/building-nethunter/).
For LightROM Oreo the right NetHunter Kernel that worked for me was the WirusMOD (https://forum.xda-developers.com/galaxy-s7/development/kernel-wirusmod-t3943468), and it says it's also compatible with LineageOS 16 & 17, but that just doesn't work for me.
The Main page for Nethunter Kernel downloads is here: https://www.offensive-security.com/kali-linux-nethunter-download/
But there are also other older NetHunter Kernels here: https://build.nethunter.com/archive/2019.03-13-0514/
And I didn't try it with the wireless adapter...yet
Best of luck.

I flashed los 16 from zip, then magisk then I flashed nethunter.img but after boot there is no nethunter installed... Can you please let me know the steps u followed to make it work? Thanks!

Installed nethunter on los 16 but still can not make the wireless module to work

vladvlad12 said:
Installed nethunter on los 16 but still can not make the wireless module to work
Click to expand...
Click to collapse
I couldn't get some things to work correctly on Los16.0 nor on Los17.1 but on LightROM(8.0) the "lsmod" and the "insmod 88XXau.ko" commands work fine and it should work there on LightROM with WirusMOD, I'm still learning but that adapter is my next step
The problem I got to is that WirusMOD doesn't copy/flash some "binaries/files" for Los16/17 kernel for "lsmod" to work, perhaps because the system structure is different from android 8 and it's missing some files, I don't know, but for now I'm using LightROM with WirusMOD and it works just fine.

kenny.33 said:
I couldn't get some things to work correctly on Los16.0 nor on Los17.1 but on LightROM(8.0) the "lsmod" and the "insmod 88XXau.ko" commands work fine and it should work there on LightROM with WirusMOD, I'm still learning but that adapter is my next step
The problem I got to is that WirusMOD doesn't copy/flash some "binaries/files" for Los16/17 kernel for "lsmod" to work, perhaps because the system structure is different from android 8 and it's missing some files, I don't know, but for now I'm using LightROM with WirusMOD and it works just fine.
Click to expand...
Click to collapse
I will try to install LightROM to see if the kali nethunter works and then will check the wireless driver, I will be back with the conclusion.
Thanks!

Installed LightRom and Nethunter, cloned the 8188eu from git, used make command and when try to do make install I get that
[email protected]:~/rtl8188eu# make install
install -p -m 644 8188eu.ko /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless
install: cannot create regular file '/lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless': No such file or directory
Nvm, created /kernel/drivers/net/wireless but now getting
[email protected]:/lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2# make install
install -p -m 644 8188eu.ko /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless
cp rtl8188eufw.bin /lib/firmware/.
/sbin/depmod -a 3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2
depmod: WARNING: could not open modules.builtin at /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2: No such file or directory
mkdir -p /lib/firmware/rtlwifi
cp rtl8188eufw.bin /lib/firmware/rtlwifi/.
After loot of work still get
install -p -m 644 8188eu.ko /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless/
/sbin/depmod -a 3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2
depmod: WARNING: could not open modules.builtin at /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2: No such file or directory

vladvlad12 said:
Installed LightRom and Nethunter, cloned the 8188eu from git, used make command and when try to do make install I get that
[email protected]:~/rtl8188eu# make install
install -p -m 644 8188eu.ko /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless
install: cannot create regular file '/lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless': No such file or directory
Nvm, created /kernel/drivers/net/wireless but now getting
[email protected]:/lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2# make install
install -p -m 644 8188eu.ko /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless
cp rtl8188eufw.bin /lib/firmware/.
/sbin/depmod -a 3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2
depmod: WARNING: could not open modules.builtin at /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2: No such file or directory
mkdir -p /lib/firmware/rtlwifi
cp rtl8188eufw.bin /lib/firmware/rtlwifi/.
After loot of work still get
install -p -m 644 8188eu.ko /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2/kernel/drivers/net/wireless/
/sbin/depmod -a 3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2
depmod: WARNING: could not open modules.builtin at /lib/modules/3.18.140.8-Nethunter_WirusMOD-twOreo-CTD2-v2.2: No such file or directory
Click to expand...
Click to collapse
Hmm if you Downloaded & Flashed the LightROM & WirusMOD, (& copied the nethunter_binaries*.zip content), then 'lsmod' should work, all you need is the 8188eu.ko file.
(Latest Link: https://androidfilehost.com/?fid=8889791610682940998 - make sure you're using the right driver for your kernel)
Download the Modules and extract the '8188eu.ko' file to /sdcard/. (/emulated/storage/0/.)
Start Kali-chroot and type in terminal:# insmod /sdcard/8188eu.ko
Then to view the loaded modules type:# lsmod
And after you're done and want to remove it type:# rmmod 8188eu
With the loaded module you can try with plugging in the wireless device and type:# ip link set [adapter] up && airmon-ng check kill && airmon-ng start [adapter]
Change the [adapter] with your adapter name, find it by typing:# ip a
I also tried with Android's Root, and it also works the same.
You can alternatively find an apk "Module Loader" and just extract into /sdcard/. and open the apk and load all modules in there.
Wish you good luck
~Kenny.

change permission of subfolder on "Android/data/" (Android 12)

on "Android/data/" ("/storage/emulated/0/Android/data/") - (Android 12 stock rom unrooted on Xiaomi RedMi Note 11 Pro 5G 128GB/6GB) - i've a subfolder w/ permission "2700" (and other all subfolders w/ permission "2770" and same user/group)
how to change permission of specific subfolder from "2700" to "2770"?!?
from ADB (from various platform & various ADB version...from PC Windows 10 x86/Windows 10 x64/Ubuntu 20.04 AMD64, from ADB via USB OTG & via wi-fi on another phone [Samsung Galaxy A32] w/ Termux last version & ADB Shell - Debug Toolbox PRO last version, etc), w/ chmod shell commands - obtain only "permission denied"

Phone's Android must be rooted so that it can succeed.

one cannot change individual permissions on file level, permissions are set from the mount options /storage/emulated is mounted with.
but root won't help anything as the permissions you mean aren't file permissions. you need to update the app to work properly with Android 11+
https://kb.vmware.com/s/article/85573