Related
I'm using AOSP 2.1, and I rooted as per the instructions in the topic (I got SetCPU and QuickBoot working just fine). I get this error message when ever I start it up:
Busybox works but the "su" command does not elevate to root: "whoami" reports "whoami: unknown uid 10051" instead of uid 0. I think your "Superuser Whitelist" system app does not work. Please check with your ROM provider.
Click to expand...
Click to collapse
Checking in Better Terminal Emulator, I also get the uid of 10051 when I use whoami. The dev suggested that it was a "Superuser Whitelist" problem, but I have no idea what this is. Could anyone help me out?
TheBiles said:
I'm using AOSP 2.1, and I rooted as per the instructions in the topic (I got SetCPU and QuickBoot working just fine). I get this error message when ever I start it up:
Checking in Better Terminal Emulator, I also get the uid of 10051 when I use whoami. The dev suggested that it was a "Superuser Whitelist" problem, but I have no idea what this is. Could anyone help me out?
Click to expand...
Click to collapse
The Superuser Whitelist is superuser.apk, they're saying it's a problem with that app.
No, though i have heard of it.
Just for safety's sake search this forum on whitelist ( has a bad affect on the cdma hero) , before going to market. Also check superuser.apk, it could be your answer. TB is probably using the uid as a semaphore so as to be responsive to SU permissions programs. Busybox does not have a setuid, so you can't #setuid 0.
http://forums.macosxhints.com/archive/index.php/t-3359.html
Edit: I see someone ( with a similar name ) has already asked the developer.
http://androidforums.com/android-applications/42636-titanium-backup-problems-droid.html
Ask the "superuser.apk" developer.
This might help
Are you using Darchstar's ROM? There is a known issue with it not rooting, and setting up the superuser whitelist. Take a look at these instructions and it might fix your issue:
http://forum.xda-developers.com/showpost.php?p=5741316&postcount=1705
willy900wonka said:
No, though i have heard of it.
Just for safety's sake search this forum on whitelist ( has a bad affect on the cdma hero) , before going to market. Also check superuser.apk, it could be your answer. TB is probably using the uid as a semaphore so as to be responsive to SU permissions programs. Busybox does not have a setuid, so you can't #setuid 0.
http://forums.macosxhints.com/archive/index.php/t-3359.html
Edit: I see someone ( with a similar name ) has already asked the developer.
http://androidforums.com/android-applications/42636-titanium-backup-problems-droid.html
Ask the "superuser.apk" developer.
Click to expand...
Click to collapse
Yeah, that was me. He doesn't know the ins and outs of rooting.
josue85 said:
Are you using Darchstar's ROM? There is a known issue with it not rooting, and setting up the superuser whitelist. Take a look at these instructions and it might fix your issue:
http://forum.xda-developers.com/showpost.php?p=5741316&postcount=1705
Click to expand...
Click to collapse
I am. I will try that out and see if it works.
Ok, when trying to fix the superuser whitelist as described, I get the error:
Code:
Unable to chmod su: No such file or directory
after the command
Code:
chmod 06755 su
I rooted following the instructions in the "How to root topic." Any ideas?
TheBiles said:
Ok, when trying to fix the superuser whitelist as described, I get the error:
Code:
Unable to chmod su: No such file or directory
after the command
Code:
chmod 06755 su
I rooted following the instructions in the "How to root topic." Any ideas?
Click to expand...
Click to collapse
did you get my pm?
darchstar said:
did you get my pm?
Click to expand...
Click to collapse
Yeah, performing a nandroid backup now. I have to root it again, right?
Oh, and should I wipe first?
EDIT: Everything works like a charm!
It also finally asks if I want to allow root access from apps.
ON a stock rom you would apply this update, by Mercado79, it gives you the whitelist and sets your uid to 0 upon activation.
The update is described here:
http://forum.xda-developers.com/showthread.php?t=593952&highlight=mercado79
download update zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=252801&d=1259860872
I tested the process and it sets the uid to 0.
Okay I must the most unlucky man on earth:
I rooted my HTC stock ROM, installed Titanium & Busybox, but I get the same su error...
I tried to install the update from mercado79, but after reboot it freezes on htc logo during first boot...
I don't know what else I could possibly do to finally be able to backup all my data and apps :-(
Okay so here's the story guys, I am simply baffled at the fact I am holding a ZTE Majesty Pro Android MM 6.0 handset.
I look through my /system/bin for cmd interface type programs & to my surprise I see a lot of friendly & functional tools I would even see a few on a device with BusyBox installed, so here is where my confusion starts,
I can call the 'am' command from terminal,
I can call the 'pm' one from ADB with permissions over any user app (not sure about system apps my guess is probably since I got AppOps running with ADB & the pm command)
I can chroot and the 'toolbox' command spits out a majority of BusyBox, + the 'cat' command is in there, along with the weirdest command thusfar
the 'ss' command (Im assuming safestrap?) it asked me for 64-bit ELF files.
I'd be happy to provide any other specs for my device if needed, would appreciate anyone willing to help me use p0six to root this internally encrypted pile of crap.
LilAnt530 said:
Okay so here's the story guys, I am simply baffled at the fact I am holding a ZTE Majesty Pro Android MM 6.0 handset.
I look through my /system/bin for cmd interface type programs & to my surprise I see a lot of friendly & functional tools I would even see a few on a device with BusyBox installed, so here is where my confusion starts,
I can call the 'am' command from terminal,
I can call the 'pm' one from ADB with permissions over any user app (not sure about system apps my guess is probably since I got AppOps running with ADB & the pm command)
I can chroot and the 'toolbox' command spits out a majority of BusyBox, + the 'cat' command is in there, along with the weirdest command thusfar
the 'ss' command (Im assuming safestrap?) it asked me for 64-bit ELF files.
I'd be happy to provide any other specs for my device if needed, would appreciate anyone willing to help me use p0six to root this internally encrypted pile of crap.
Click to expand...
Click to collapse
I would love to. However i have the majesty pro on 7.1.1. What is p0six
ATACELITE said:
I would love to. However i have the majesty pro on 7.1.1. What is p0six
Click to expand...
Click to collapse
https://en.m.wikipedia.org/wiki/POSIX
Did you purchase your majesty pro with 7.1.1 on it already?
Did you purchase your majesty pro with 7.1.1 on it already?[/QUOTE said:
Yes siree
Click to expand...
Click to collapse
ATACELITE said:
Did you purchase your majesty pro with 7.1.1 on it already?[/QUOTE said:
Yes siree
Click to expand...
Click to collapse
Awh man, i wonder if there's an update
Click to expand...
Click to collapse
Can anyone confirm that this 9.0 pie update breaks all call recording app from the play store. Thanks for your feedback.
Updated to Android 9 today and boldbeast no longer works, it will record my voice but not that of the call )-: I am considering root now to get the feature back as i did find it useful.
Update: found this on the play store https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_GB
Its all working fine now as it enables the oneplus6 built in recorder.
Thanks
But that also means that it wouldn't work without root like myself. Right?
Guess I gotta stick with my 8.1 until someone figures this one out. This one feature is like super important to me atm.
Thanks again for your kind reply.
Hi,
No root required, my phone is standard no unlocked bootloader and no root.
You just need to install the software, then enable developer options on your phone, enable usb debbugging and send the following command to your phone. adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
Then you will have the option in the software (joneplustool) to enable call recording and also restore calling recorder at boot.
Then on the phone dialler , go into settings and enable call record.
xtruss said:
restore calling recorder at boot.
Click to expand...
Click to collapse
That's a bummer...
But hey, thanks a lot for your kind reply. And as for myself, I've been using Cherinbo, pretty decent I would say.
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
vibo2013 said:
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
Click to expand...
Click to collapse
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
You seem as though you just want to promote a product to me, and one that doesn't work.
Darkest shades said:
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
Click to expand...
Click to collapse
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
xtruss said:
You seem as though you just want to promote a product to me, and one that doesn't work.
Click to expand...
Click to collapse
Lol, not my intention. But the one thing that I like about this one is that all saved, recorded files doesn't appear into my music player, where as for others, they always does. Thanks for confirming that it doesn't work.
vibo2013 said:
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
Click to expand...
Click to collapse
It's ok, you help a lot already.
Thanks for your help guys.
I am very happy with the built in call recorder. What is the benefit of having a third party app to record calls?
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Void
---------- Post added at 02:57 AM ---------- Previous post was at 02:49 AM ----------
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
dgunn said:
Void
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1"
It enables the default, native Call Recorder found on op6 and op5 and I really like it. It recorded all my today's calls ranging from 625KB to 2.29MB all good quality(aac files)
eliaspizarro said:
Requeriments:
root
terminal with su permisions
Manual steps
Method 1 (works until reboot):
Create a file ex. incall.sh:
Code:
#!system/bin/sh
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
execute from terminal: $ sh incall.sh
Method 2 (works until reboot):
with adb: > adb shell "settings put global op_voice_recording_supported_by_mcc 1"
My steps (permanent):
Install termux (add su permisions)
in termux: $ termux-setup-storage
Install termux boot
create folder un termux home path (default) named: .termux
in termux: $ ln -s /storage/emulated/0/<your boot script folder> ~/.termux/boot
create script in /storage/emulated/0/<your boot script folder>
Code:
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
exit
reboot
Click to expand...
Click to collapse
..
This is what I'm getting
sh: $: not found
Just by telling us to install this and add home path here..... We need instructions
---------- Post added at 06:26 PM ---------- Previous post was at 06:04 PM ----------
and again
sh: adb: not found
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
You can also use Tasker to enable native call recording (provided you've granted WRITE_SECURE_SETTINGS permission to Tasker).
It seems the system deactivates jOnePlus from activating call recorder after 8 hours. Anyway to make it a permanent activation?
Even after removing jOnePlus from the battery optimize list, the call recorder still gets deactivated after a couple of hours.
obislu said:
mzsquared said:
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
I took the official OTA Pie upgrade and enabled the recorder with adb command after that. I'm not planning to root my phone, at least not yet. I'm enjoying the Pie Rom as is. It's all good, actually great with the night mode, there is no bloat. I disabled few apps, mainly from google and that's that. I remember times when rooting was an important necessity, I've had a Motorola Defy XT, long time ago, with 1GB RAM and no space for any extra apps, rooting was mainly used for getting the bloat out and moving apps to SD card by way of creating ext4 partition.
My OP6 has 256GB storage space, 8GB RAM and I just don't feel like constantly reloading the system, chasing newest twrps and Magisk versions, softbricking etc,etc.. and having my phone 'off line' for hours while I'm fixing it.
Click to expand...
Click to collapse
I was told to run the following command to stop auto updates:
adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
Click to expand...
Click to collapse
If I want to turn them back on, does anyone know how would I do that?
Also, I presume that Oreo is the latest version for the L29 (I'm on US version). No Pie. IS that correct?
ewingr said:
I was told to run the following command to stop auto updates:
If I want to turn them back on, does anyone know how would I do that?
Also, I presume that Oreo is the latest version for the L29 (I'm on US version). No Pie. IS that correct?
Click to expand...
Click to collapse
Would doing a factory reset accomplish what I want?
That command uninstalled the system updates apk, but didn't permanently remove it.
Use: adb shell cmd package install-existing <name of package>
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Thanks. I really appreciate the help.
I ran the command like this:
adb shell cmd package install-existing com.huawei.android.hwouccls
Click to expand...
Click to collapse
I get the following reply:
Unknown command: install-existing
Click to expand...
Click to collapse
I do see my device when I enter "adb devices".
Try without a hyphen.
robogo1982 said:
Try without a hyphen.
Click to expand...
Click to collapse
That was it, but of course, still another catch. JFYI...I did enter the command this way:
adb shell cmd package install existing com.huawei.android.hwouccls
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Then I got this message:
Error: must specify a APK size
Click to expand...
Click to collapse
I thought that interesting. Anyway, I tried a search for com.huawei.android.hwouccls on my phone from what was listed as \ and found nothing. So I have no idea what to list as the size. And then there will be the syntax to do so.
I hate having to be so needy. Since I stopped rooting and using custom ROMS, my skills have seriously rusted.
I should add that I searched for com.huawei.android.hwouccls with App Inspector as mentioned in your link, and don't find it. My phone is not rooted...maybe that has something to do with that.
I'm using rmx3171_c06 stock rom.
i want to use viper4android which requires selinux permissive.
but when i flashed a module which makes phone permissive it automatically backs to enforcing ,help!!
May be the reason is that the module will not work because phone's kernel is compiled with always enforcing config, e.g., stock Samsung kernels.
is any other option?? like customise the kernel
san.v90 said:
I'm using rmx3171_c06 stock rom.
i want to use viper4android which requires selinux permissive.
but when i flashed a module which makes phone permissive it automatically backs to enforcing ,help!!
Click to expand...
Click to collapse
It's an old app but have you tried the Selinux Switch app? I was the tester for that app when it was made. It worked well at the time, the app hasn't been updated in a while so I'm not sure how well it still works.
i just use "setenforce 0" to make it Permissive.
This is a temporary solution, doesn't survive a reboot.
xXx yYy said:
This is a temporary solution, doesn't survive a reboot.
Click to expand...
Click to collapse
Yeah i know. Forgot to mention it.
Canny1913 said:
Yeah i know. Forgot to mention it.
Click to expand...
Click to collapse
xXx yYy said:
This is a temporary solution, doesn't survive a reboot.
Click to expand...
Click to collapse
Selinux Switch app has a setting to persist through reboot. All that is required is root and a kernel that supports permissive mode.
Or, a script can be created to automatically run the setenforce 0 command during reboot.
You must not tell me what I already know.
xXx yYy said:
You must not tell me what I already know.
Click to expand...
Click to collapse
That wasn't directed at anyone specific, hence, the multi-quote, no need to quote the OP as well as they would get notification for all comments. Additional information for anyone reading the thread since it wasn't stated by anyone else in previous comments to the thread.
san.v90 said:
is any other option?? like customise the kernel
Click to expand...
Click to collapse
Change the SELINUX value to SELINUX=permissive and/or SELINUX=disabled in the file /etc/selinux/config - requires phone is rooted and partition /etc is mounted as RW.
xXx yYy said:
Change the SELINUX value to SELINUX=permissive and/or SELINUX=disabled in the file /etc/selinux/config - requires phone is rooted and partition /etc is mounted as RW.
Click to expand...
Click to collapse
Sorry sir, but there is no file like /etc/selinux/config
-plz suggest another trick
Droidriven said:
It's an old app but have you tried the Selinux Switch app? I was the tester for that app when it was made. It worked well at the time, the app hasn't been updated in a while so I'm not sure how well it still works.
Click to expand...
Click to collapse
Yes i have tried but still nothing happening
i think it's impossible in this device
san.v90 said:
Sorry sir, but there is no file like /etc/selinux/config
-plz suggest another trick
Click to expand...
Click to collapse
Was my fault: path to SELinux policy file should be /system/etc/selinux/config
xXx yYy said:
Was my fault: path to SELinux policy file should be /system/etc/selinux/config
Click to expand...
Click to collapse
still can't find any config file
Its not in system its in boot
I am having the same problem, I tried all possibilities
I am using the Umidigi A13 Pro Max 5G on Android 12.
I think it is to do with Android 12 security that is preventing
Selinux from going permissive.
None of the old methods work with it now.
Yes there is no config file in the selinux directory.
I don't really know what to do, Viper will only
work with permissive mode.
Any ideas guys !!!!
ScarletWizard said:
Did u try thr repackaged version?
Click to expand...
Click to collapse
Thank you very much for getting back
Yes I did and also installed the
Audio Modification Library
Still no joy
I am very familiar with this as I used to
have issues with the Umidigi F2 and I
managed to sort that out
I think that the issue here is with
Android 12 security
None of the existing solutions
works with it
I even tried terminal commands
like getenforce and setenforce
and sestatus to temporarily
change selinux mode to permissive
Unfortunately some Mods like
viber4android will only work
when selinux is in permissive mode
that's a job for viber4android maintainer, but you can try yourself. just needs patience.
https://forum.xda-developers.com/t/4534599
I think that it's not a good idea to run in permissive mode.
You've got a jillion apps on your device that are just waiting to do stuff if you turn enforce off.
In any case...
When I want to make permanent permissive I just mod the kernel.
In my experience, the kernel starts out permissive then turns on enforce at some point.
Easey-peasy, just dump the kallsyms, get the address of sel_write_enforce.
In A64 just replace the two first instructions:
Code:
d2800000 mov x0, #0x0
d65f03c0 ret