Database Develop

[Concept] Root without unlocking

Hello,
I've been trying the dolphin emulator for android and to get it running with the opengles3.0 backend, we need to disable some kernel function. Otherwise, the device is rebooting.
this is the command we run with root right:
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_pagefault_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ib_check
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/long_ib_detect
My guest is there is some flaw in these kernel function and maybe we can get root by using those flaw? Simply using an app ahah
Is there any possibility of a possible exploiting of these crash?
Thank, I'm simply curious. (and I've already root)

How to Enable fast charge and disable Fsync

I am using nyakkernel which supports fast charge and Disabling Fsync and i tried typing commands in terminal but i always get nothing can anyone tell me what i should do exactly ?

You could use an application like nsTools or:
To enable Fast Charge:
Enter in terminal emulator:
su
echo 1 > /sys/kernel/fast_charge/force_fast_charge
To disable:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Dynamic Fsync:
Disable:
su
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
Re-enable:
su
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active

is this tested?

[Q] How can I disable the LED while charging?

Hello XDA-developers
How can I disable the LED while charging?
I have root access on my Huawei ascend P7.
Lightflow (lite) doesn't help, and Settings > Display > LED and disable it there doesn't help too.
Thanks for your help.

heyhou95 said:
Hello XDA-developers
How can I disable the LED while charging?
I have root access on my Huawei ascend P7.
Lightflow (lite) doesn't help, and Settings > Display > LED and disable it there doesn't help too.
Thanks for your help.
Click to expand...
Click to collapse
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !

surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
sudru ..
i replaced bootanimation.zip bxcos i want original animation.. but instead is just small android write in the middle .. why it doesnt work ?

surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
Hey surdu_petru, what options else are there? You say echo 0 with output at red and green....can i find the options somewhere?
My red and green/red files are on zero but i have light at charging.

surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
It works
Thank you very much and good luck with the CM port.

Dont work on Mate S

surdu_petru said:
Hello !
Here it is :
Code:
> adb shell
$ su
# echo 0 > sys/devices/platform/hkled/leds/green/brightness
# echo 0 > sys/devices/platform/hkled/leds/red/brightness
# exit
$ exit
Good luck !
Click to expand...
Click to collapse
I tried that now under Lollipop, but it doesn't survive a reboot. When only setting brightness to zero, the light returns after un- and replugging. So, I set the rights to -r--r--r--, now it works until reboot.
There is also a file called trigger, which I can't change at all, although the rights are -rw-r--r--. I could save, but when opening the next time, it is like it was originally.
Does anyone have an idea how to make those changes permanent? Might the reset be caused by the kernel?

[help]magsisk echo script on boot

I want to make an echo command with magisk on boot
echo 0 > /sys/class/leds/button-backlight/max_brightness
so that it is applied on boot automatically
how to do that ?
thanks in advance

Just put your script in
Code:
/magisc/.core/service.d
and set execution permissions.
Since you want to edit sys files, you will need root permission. An example script would be (brightness.sh) :
Code:
#!/system/bin/sh
su -c 'echo 0 > /sys/class/leds/button-backlight/max_brightness'
Note :
If you want to execute your script at another boot stage you should have a look at this

pec0ra said:
Just put your script in
Code:
/magisc/.core/service.d
and set execution permissions.
Since you want to edit sys files, you will need root permission. An example script would be (brightness.sh) :
Code:
#!/system/bin/sh
su -c 'echo 0 > /sys/class/leds/button-backlight/max_brightness'
Note :
If you want to execute your script at another boot stage you should have a look at this
Click to expand...
Click to collapse
Can you tell what the -c flag in your example script is for?

Yaseen_the_Gamer said:
Can you tell what the -c flag in your example script is for?
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/blob/master/docs/tools.md#su
It's to use su directly in the command, basically.
Although in this case it's technically unnecessary since all Magisk boot scripts are run with superuser access.

How to change the value of ro.config.tima Systemless-ly?

Hello!
I am trying to change the value of the 'ro.config.tima' property from 1 to 0 using a boot script and resetprop,
I made a file in /data/adb/post-fs-data.d called 'resetprop.sh' and I put this into it:
Code:
#!/system/bin/sh
resetprop ro.config.tima 0
Then, I gave it execution permissions and rebooted, only to see that the value was still 1...
So I tried again, but this time I added other properties to that file to make sure that the script was running:
Code:
#!/system/bin/sh
resetprop ro.config.tima 0
resetprop ro.boot.warranty_bit 1
resetprop ro.warranty_bit 1
When I rebooted, the other properties changed from 0 to 1; while, the 'ro.config.tima' property stayed at 1.
I then tried a third time, this time I did the exact same thing but put the file in /data/adb/service.d instead, I rebooted and got the same result, the other properties changed to 1 and 'ro.config.tima' stayed at 1.
So then, I tried the "MagiskHide Props Config" Module but when I install it, it causes my whole system to crash and then my device restarts/reboots (Over and over again until I remove the module with TWRP).
Edit: My device is an SM-T350 (Samsung Galaxy Tab A)
Is there any way I can get this property to change to 0 Systemless-ly? Any help would be appreciated.

First try running the command in a terminal emulator. If that changes the value you can try adding a delay to the script before it executes the resetprop command (use service.d).

Didgeridoohan said:
First try running the command in a terminal emulator. If that changes the value you can try adding a delay to the script before it executes the resetprop command (use service.d).
Click to expand...
Click to collapse
When I type it in a Terminal emulator it changes to 0,
So how long of a delay should I add?

JJcoder said:
When I type it in a Terminal emulator it changes to 0,
So how long of a delay should I add?
Click to expand...
Click to collapse
Start with sleep 60 and if that works you can try 30 and so on until you find a value that works and you're comfortable with.

Didgeridoohan said:
Start with sleep 60 and if that works you can try 30 and so on until you find a value that works and you're comfortable with.
Click to expand...
Click to collapse
Thanks, I will let you know if it works.

Didgeridoohan said:
Start with sleep 60 and if that works you can try 30 and so on until you find a value that works and you're comfortable with.
Click to expand...
Click to collapse
Unfortunately, it did not work. Is there anything else I can try? This is what I have in the 'resetprop.sh' file located in /data/adb/service.d:
Code:
#!/system/bin/sh
sleep 60
resetprop ro.config.tima 0

JJcoder said:
Unfortunately, it did not work. Is there anything else I can try? This is what I have in the 'resetprop.sh' file located in /data/adb/service.d:
Code:
#!/system/bin/sh
sleep 60
resetprop ro.config.tima 0
Click to expand...
Click to collapse
If 60 doesn't work, try a longer time...

Didgeridoohan said:
If 60 doesn't work, try a longer time...
Click to expand...
Click to collapse
I tried 100, 300, 500, even 1000 and none of them have worked...
How much longer do I have to go? Or am I going to have to do something else?

Try something like this:
Code:
LOC="/data/media/0/tima_test.txt"
echo "$(date +"%H:%M:%S")" > $LOC
resetprop -v ro.config.tima 0 >> $LOC
until [ "$(getprop ro.config.tima)" == 1 ]; do
sleep 1
done
echo "$(date +"%H:%M:%S")" >> $LOC
resetprop -v ro.config.tima 0 >> $LOC
getprop ro.config.time >> $LOC
That is pure untested air code, but in theory it should let us know if the prop value resets to 1 sometime after boot, and when it happens. If nothing else, it might give us some info on what happens when resetprop runs on that prop (but unless something is wrong it'll likely not show anything).
All the info should be in the tima_test.txt file on your internal storage. Wait a good while before you check it...