Database Develop

Gingerbread 2.33 CF-Root 3.7 Busybox messed up

Hi
i rooted my Phone (Gingerbread XWJVI) a few Days ago with CF-Root 3.7.
Everything went fine, thanks to the great work from Chainfire
Unfortunatly i tried to install a newer Busybox Version.
I tried Busybox Installer (JRummy) from Market, unfortunatly the Connection got lost during download/install.
After that i tried installing Busybox (Stericson) which gave me an Error :
Failure /system/xbin/ could not be remounted as RW!
Root Checker gives:
Code:
Congratulations ...
Superuser.apk - com. ... is installed.
The adb binary is set to default shell user access as a standard non-root user.
Standard su binary location : ls -l /system/bin/su:
Segmentation fault
Standard su binary location : ls -l /system/xbin/su:
Segmentation fault
Alternate su binary location :
Segmentation fault
and for Busybox verification:
Code:
Installed Busybox Version:
Busybox is not sharing its version information.
Busybox supports the folloeing applets:
Busybox is not sharing its supported applets.
So i messed things up.
Is there any way of getting Busybox 1.16androidminimal back which came with CF-Root 3.7 ?
Any help apreciated.

Try flashing CF-Root 3.7 again via odin
[put ur sgs into download mode {HOME+VOL DOWN+POWER}, load kernel in pda {DO NOT select REPARTITION} and flash] instructions are here
Or else you can flash a new rooted/custom rom via odin.
Copy/Back up all your personal data to ur pc/sd before flashing. because it will wipe!!!

Reflashed CF-Root and wiped.
No Result, Busybox stayed messed up.
The problem may be a differnet one.
If i just want to get a directory listing in terminal,
ls gives me a segmentation fault.
If i do a "toolbox ls" everything is fine.

[Q][DEV] system() call fail when executing native app with su permission

Hi all,
I have run into very disturbing problem when developing a native app with NDK. When my program calls system(), popen() or other function of that kind the return value of system() call is 32512 (which is 127: "command not found"). popen() does not return error code but crashes when trying to read() (returns -1). I have tested this on basic commands such as ls, ps, etc. Tried to provide a full path to the binaries as well without success.
The issue appears only when executing binary with su (I have tried interactive su, su -c and many other variations- I run it via adb shell). When calling system() without su permission then commands are executed correctly. When programmatically reading files in /system/bin (when my program is run with su) I see all files and everything is accessible.
I have verified that su is installed correctly, I can do all kind of root-only stuff without any problem. My program when executed with su permission is able to enter protected areas of Android.
I have tried to switch context without any luck. There is no interesting logcat output that could point to any permission I could allow with supolicy.
This happens on Samsung S3 i9300, S4 i9505, S5 G900F, Note3 N9005...
Happens both on SELinux enforcing and permisive.
Code:
[email protected]:/ $ su -v
2.45:SUPERSU
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Any help and clues are much appreciated.
Thanks,
Piotr.

Turns out that the reason is that fork() is prohibited when executable is not located under /system. When placed binary on /system/bin everything works fine.

Latest SuperSU stalls indefinitely on new systemless install, Moto X Pure Edition

I recently got a repaired Moto X Pure Edition running Marshmallow. I unlocked the bootloader and used fastboot to start TWRP, then set up the systemless install of SuperSU 2.79. The installation seemed successful. I watched it patch the boot image and upon reboot, the SuperSU app was available. It seems happy when I run it.
However, if I run the terminal emulator and type "su", it stalls indefinitely. Nothing happens. The SuperSU "allow/deny" dialog does not appear and nothing shows up in the SuperSU logs. The same happens when I run su via "adb shell" on my PC. TitaniumBackup also stalls when it starts with "Detecting SU and Busybox".
I originally installed SuperSU 2.79, then found the SR3 update and installed that as well. Both had the same problem. The su binary is not completely broken, as some commands work.
Some commands that work:
Code:
[email protected]:/ $ su -v
2.79:SUPERSU
Code:
[email protected]clark:/ $ su -V
279
Code:
[email protected]:/ $ su --help
SuperSU v2.79 (ndk:arm64-v8a) - Copyright (C) 2012-2017 - Chainfire & CCMT
...
Any idea why SuperSU isn't working?

Okay, here's another data point. I switched the default permission from "Prompt" to "Grant", and I can get root. The problem has something to do with showing the dialog.

I figured it out. In a previous cleanup attempt, I failed to restore the link named /system/bin/app_process that points to /system/bin/app_process64. This fixed it:
From the TWRP terminal:
Code:
mount /system
cd /system/bin
ln -s app_process64 app_process

su not permitted error

After installing the xpose framework(v82) on Android 5.0 not able to execute su command in terminal emulator app(kernel version is 3.10). But able to execute su command before installing xpose framework.
And in both cases from adb I am able to execute the su command without any problem.
Any suggestion will be of great help. Thanks in Advance.

Help w a twrp convert/ port and chmod

Edit* ok two things I have finally managed to get rooted on an Android TV amlogic device running Android 10 with magisk! But problem 1: it detects an old su binary that came pre-installed and hidden by chmod permissions in this user debug firmware I am running so you had root ADB shell. Now magisk wants me to remove the other su binary I chmodded to 777 in /system/xbin/su that came w debug build. How to chmod hide from execute or detection or remove that? And problem #2: have a twrpof a different device but with the same motherboard but it's a .zip with no recover.img fastboot boot recovery.img, to boot to twrp..how to compile the zip to a twrp img or finish porting my own?