Database Develop

[Q] Stock su binary present, uid not allowed to su

Hello,
On my Teclast P90HD running Kitkat 4.4.2, I found a /system/xbin/su binary while connected through adb. However, the su command in Terminal emulator gives :
uid 10107 not allowed to su
I guess it has to do with SELinux. After setenforce = 0 and reboot, getenforce returns 'Disabled', yet no change in Terminal Emulator.
Installing SuperSU apk from Play Store obviously fails, and I can't get it to boot in recovery to try flashing UPDATE-SuperSU-v2.46.zip.
Is there anything I can do to get that su file helpful ?
Thanks.

Hi, did you find any solution here ?
I'm in the same situation, what looks to be a solution is to recompile su.c removing the AID_ROOT / AID_SHELL related part.

Patching sepolicy failed

Dear friends
Good evening
i have honor 4x indian version che1-l04 model
when i try to use supersu.zip systemless version i get patching sepolicy--failure abort:crying:
i have attached sepolicy from unpacked boot.img
please help me patch this file
or
run following code in adb shell on your rooted phone and send me sepolicy_out file
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
thanks a lot:good:

I also had a problem similar to this, I was implementing SuperSu by hand becuse my boot.img is quirky. At one point I had to patch the sepolicy file, so I did it via an emulator.
Check here for up to do it (Note: I used a 64 bit android Nexus Lollipop system image as the emulator).
http://forum.xda-developers.com/showpost.php?p=68764185&postcount=9

edit: Wrong topic

You can easily get a patched sepolicy file by downloading a custom kernel that already includes SuperSU. Then you can extract the sepolicy file from that kernel to place it into your system.

tuiyaan said:
Dear friends
Good evening
i have honor 4x indian version che1-l04 model
when i try to use supersu.zip systemless version i get patching sepolicy--failure abort:crying:
i have attached sepolicy from unpacked boot.img
please help me patch this file
or
run following code in adb shell on your rooted phone and send me sepolicy_out file
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
thanks a lot:good:
Click to expand...
Click to collapse
hey, i'm facing the same problem for my lenovo yoga book...can't flash su cause it fails patching sepolicy.
did you solve the problem? if yes, how did you do that?
thanks for your help.

danjac said:
hey, i'm facing the same problem for my lenovo yoga book...can't flash su cause it fails patching sepolicy.
did you solve the problem? if yes, how did you do that?
thanks for your help.
Click to expand...
Click to collapse
i tried magisk and phh su method.
https://forum.xda-developers.com/honor-4x/help/honor-4x-che1-l04-mm-6-0-1-emui-4-root-t3475854\
chain fire su is not working (both systemless and systemmode)

tuiyaan said:
i tried magisk and phh su method.
https://forum.xda-developers.com/honor-4x/help/honor-4x-che1-l04-mm-6-0-1-emui-4-root-t3475854\
chain fire su is not working (both systemless and systemmode)
Click to expand...
Click to collapse
great man!!!! it worked for me as well!
thanks a lot. would buy you a beer instantly!

danjac said:
great man!!!! it worked for me as well!
thanks a lot. would buy you a beer instantly!
Click to expand...
Click to collapse
Good to hear
Thanks for the offer
Cheers

Camera2API enabled in build.prop, but can't use manual mode?

I'm trying to get the Google HDR+ caamera to get working on my Redmi 4A. I've tried this guide https://forum.xda-developers.com/redmi-4a/how-to/redmi-4a-how-to-install-google-camera-t3728439 and flash the .zip file in TWRP. I've opened my build.prop to see that persist.camera.HAL3.enabled is on and it is, but according to manual camera compatibility i don't have manual mode enabled
how do I fix this?
I'm running AEX 5.7 on my Redmi 4a
Many thanks!

Open your terminal (Enable it in Developer Option)
To check if you've enabled Camera2Api. Type this in Terminal:-
Code:
getprop | grep camera
If you don't have it enabled, do this
Type in:
Code:
su
Code:
setprop persist.camera.HAL3.enabled 1
Reboot your phone after doing it

Making Safetynet (CTS Profile) Pass on ROG II - CN Rom

Hey Guys,
Any ideas?
I tried extracting my P30 Pro Values and made a script. (In Service.d with 0777 Permission)
#!/system/bin/sh
resetprop ro.debuggable 0
resetprop ro.secure 1
resetprop ro.build.type user
resetprop ro.build.tags release-keys
resetprop ro.build.description VOG-L29-user 9 HUAWEIVOG-L29 153C185 release-keys
resetprop ro.build.fingerprint HUAWEI/VOG-L29/HWVOG:9/HUAWEIVOG-L29/153C185:user/release-keys
resetprop ro.bootimage.build.fingerprint HUAWEI/VOG-L29/HWVOG:9/HUAWEIVOG-L29/153C185:user/release-keys
resetprop ro.build.version.security_patch 2019-08-01
Click to expand...
Click to collapse
Still the CTS profile fails, Any ideas how to make it pass?

have you tried https://droidholic.com/fix-cts-profile-mismatch-errors/ ?

z3r0h said:
have you tried https://droidholic.com/fix-cts-profile-mismatch-errors/ ?
Click to expand...
Click to collapse
Didn't help much.

Having the same problem on it.
Try to install two magisk module and it doesn't help.
MagiskHide Props Config
SafetyPatch

attachsnow said:
Having the same problem on it.
Try to install two magisk module and it doesn't help.
MagiskHide Props Config
SafetyPatch
Click to expand...
Click to collapse
Not really sure where is the problem.
Need to probably emulate starting from device name itself.

JazonX said:
Not really sure where is the problem.
Need to probably emulate starting from device name itself.
Click to expand...
Click to collapse
After flashing WW rom on CN device, I try to search prop value.
Maybe we can try those info first?
Search CN:
[persist.asus.ship_location]: [CN]
[ro.boot.country_code]: [CN]
[ro.build.fingerprint]: [asus/CN_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys]
[ro.config.versatility]: [CN]
[ro.product.carrier]: [ASUS-ASUS_I001D-CN]
[ro.product.name]: [CN_I001D]
[ro.product.vendor.name]: [CN_I001D]
[ro.vendor.build.fingerprint]: [asus/CN_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys]
Search WW:
[ro.asus.build.version]: [asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys]
[ro.asus.product.name]: [WW_I001D]
[ro.bootimage.build.fingerprint]: [asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys]
[ro.build.asus.sku]: [WW]
[ro.build.csc.version]: [WW_ZS660KL-16.0622.1906.19-0]
[ro.build.description]: [WW_Phone-user 9 PKQ1.190414.001 16.0622.1906.19-0 release-keys]
[ro.build.display.id]: [PKQ1.190414.001.WW_Phone-16.0622.1906.19-0]
[ro.build.flavor]: [WW_Phone-user]
[ro.build.fota.version]: [WW_Phone-16.0622.1906.19-0]

Okay, I know how to workaround it.
But it is just workaround. Use adb shell to do this:
su
resetprop ro.build.fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys
stop;start
cts profile will pass until you restart. (Yes, restart will get fail again.)
By the way, we cannot use this method if your device is unroot.

Hi all,
If you are using CN device and flash WW rom with Magisk root, you can use this method for pass cts profile:
Create init.sh in /sbin/.core/img/.core/service.d as the following code:
#! /system/bin/sh
sleep 10
resetprop persist.asus.ship_location WW
resetprop ro.boot.country_code WW
resetprop ro.build.fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys
resetprop ro.config.versatility WW
resetprop ro.product.carrier ASUS-ASUS_I001D-WW
resetprop ro.product.name WW_I001D
resetprop ro.product.vendor.name WW_I001D
resetprop ro.vendor.build.fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys
stop;start
You can modify sleep time to any if you like. I set 0 for now but maybe it will let boot not fully complete.
And before try it, backup your data first.
Thanks.

attachsnow said:
Hi all,
If you are using CN device and flash WW rom with Magisk root, you can use this method for pass cts profile:
Create init.sh in /sbin/.core/img/.core/service.d as the following code:
#! /system/bin/sh
sleep 10
resetprop persist.asus.ship_location WW
resetprop ro.boot.country_code WW
resetprop ro.build.fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys
resetprop ro.config.versatility WW
resetprop ro.product.carrier ASUS-ASUS_I001D-WW
resetprop ro.product.name WW_I001D
resetprop ro.product.vendor.name WW_I001D
resetprop ro.vendor.build.fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys
stop;start
You can modify sleep time to any if you like. I set 0 for now but maybe it will let boot not fully complete.
And before try it, backup your data first.
Thanks.
Click to expand...
Click to collapse
Device wont boot. It's stuck in the Bootanimation splash screen.
Any ideas to recover other than Re-flash the whole thing again?

attachsnow said:
Okay, I know how to workaround it.
But it is just workaround. Use adb shell to do this:
su
resetprop ro.build.fingerprint asus/WW_I001D/ASUS_I001_1:9/PKQ1.190414.001/16.0622.1906.19-0:user/release-keys
stop;start
cts profile will pass until you restart. (Yes, restart will get fail again.)
By the way, we cannot use this method if your device is unroot.
Click to expand...
Click to collapse
almost bricked but never mind, fixed it\
I was getting "unable to connect to google services" before, but now it's "payload invalidation".....
safety passes in core mode but not normal magisk mode
edexposed is triggering it but forcing blacklist on gsm/gsf doesn't solve it.

Magisk command line

Is there any way I can do things like enable magiskhide or grant su access from the su command line?

If you type "su" you still need to grant root access in dialog pop-up.
For enabling denylist:
Code:
magisk --denylist enable
More here:
Magisk Tools
The Magic Mask for Android
topjohnwu.github.io