Database Develop

"Superuser Permissions" freezing (JF 1.51)

Hi all,
Whenever I go to use a program for the first time that requires root, my screen goes black and processes start freezing. Eventually, a box comes up saying that the "Activity SU Request" process has frozen.
Any idea what's causing it (could it be the amount of apps i've installed?) and/or how to remedy it?
EDIT: found this:
@Androidandy the easiest way to get it working seems to be:
turn on your phone by holding the home+end(power) key
press alt+x to enter the recovery console and then press enter when it asks you
next type:
mount data
rm /data/data/com.koushikdutta.superuser/databases/superuser.sqlite
if you have the problem where it says this file does not exist, type:
rm /data/data/koushikdutta.superuser/databases/superuser.sqlite
Click to expand...
Click to collapse
Sorry for asking without looking completely thoroughly first, a mod can close this thread if they like.

blakew said:
Hi all,
Whenever I go to use a program for the first time that requires root, my screen goes black and processes start freezing. Eventually, a box comes up saying that the "Activity SU Request" process has frozen.
Any idea what's causing it (could it be the amount of apps i've installed?) and/or how to remedy it?
EDIT: found this:
Sorry for asking without looking completely thoroughly first, a mod can close this thread if they like.
Click to expand...
Click to collapse
Or...... dear lord, why.... you could just go to Settings>Applications>Development and enable "USB debugging". It's a known problem with the current SuperUser.apk

Usb debugging simply isn't working with my stupid windows computer, and I'm too lazy to boot it into linux. I found out the hard way that the recovery console doesn't work on my phone, I must have forgotten to update the phone somehow. I was fiddling with all the key combinations, conveniently forgetting alt + w = wipe.
Managed to get an old backup working, and the SU popup is working again.

Shell command to halt/restart the Java VM?

A few times recently I've found that my phone will lock up, or go VERY slow, and I can't do anything with it. But if I plug it in and run ddms and Halt VM after about 10s it restarts Android and 20s later back to normal.
This is not a full reboot, don't need that. It's just restarting the Android VM.
My idea is that maybe I can have Tasker intercept incoming SMS with a command to run this program. I know in general this idea will work, but I wonder how long it might take for it to actually execute, or if the SMS will even be received in this state.

Try "hot reboot", now on the market. It kills the system server process.
http://forum.xda-developers.com/showthread.php?t=787611
Some background info (hope this answers all the questions above): the app kills the system server and reboots android without rebooting the linux kernel. It uses busybox to execute the command because not all devices come with the same set of linux/unix commands. So yeah, you need to have busybox installed otherwise you see only the beautiful animation. Furthermore, there are buggy busyboxes around so you may wish to install the newest from the market.
Click to expand...
Click to collapse
Not free anymore, but I have a backup of old version.

britoso said:
Try "hot reboot", now on the market. It kills the system server process.
http://forum.xda-developers.com/showthread.php?t=787611
Not free anymore, but I have a backup of old version.
Click to expand...
Click to collapse
Cool, thanks for that reference. Sounds like it's clearly possible from the command line. Probably as simple as killall java-something Just haven't looked or experimented yet.

Code:
adb shell
su
killall system_server
that worked for me. Took a few seconds before it hot rebooted.

BACK TO WEAR 1.5 FROM 2.0(COMPLETE GUIDE) and ELIMINATE THE PERSISTENT UPDATE NOTIFIC

Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!

Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1

Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423

For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!

Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423

After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?

Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?

Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates

szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?

Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible

Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.

hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch

Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!

riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?

LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.

pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?

LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.

mediafire link is dead (twrp) - please, reupload it!

Thanks so much for this, it worked perfectly! So great to have my watch back!

Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.

auto start

Hows do I automatically shut and start my phone at specific times

One option is via Tasker with Secure Settings plug-in, but your phone must be rooted.

Action > System > Reboot type: Shutdown
Change reboot type to Normal if you want the device to simply reboot.

Using an s7edge , says reboot option is unavailable

k****ij84 said:
Hows do I automatically shut and start my phone at specific times
Click to expand...
Click to collapse
k****ij84 said:
Using an s7edge , says reboot option is unavailable
Click to expand...
Click to collapse
You can also use the shell command "reboot" (without quotes). I don't remember properly, but I don't think you have to write "su" before. You can try and if it fails, then write "su" before.

#Henkate said:
You can also use the shell command "reboot" (without quotes). I don't remember properly, but I don't think you have to write "su" before. You can try and if it fails, then write "su" before.
Click to expand...
Click to collapse
You mean "su -c"
And he can simply tick the "Use root" box.

Sorry all this is going over my head , new to tasker , can you please put in a step by step

Any help?

Action > Code > Run Shell
Tick the "Use Root" box and enter this code:
reboot

Yes but my device is unrooted , don't want to root

k****ij84 said:
Yes but my device is unrooted , don't want to root
Click to expand...
Click to collapse
Try it without root.
It might work.

want to see for xperia z3.

snhfa said:
want to see for xperia z3.
Click to expand...
Click to collapse
Dude, just read the other posts of this thread.

You'll have to use a method that mimics human interaction. Give auto tools a try. See this reddit post for pointers.

[GUIDE][Difficulty: Intermediate] Disable Pattern/Pin/Password Lock using Shell

Since Marshmallow, I haven't been able to disable Pattern/PIN/Password (P3) using Secure Setting. I'm sure many others might be facing the same issue. So here's a guide on how to disable P3 using Shell commands.
Step 1. Set a P3 and remember it.​Step 2. Create a new Task named Disable Lock. Add Run Shell and under it type the following command​
Code:
mv /data/system/gatekeeper.pattern.key /data/system/gatekeeper.pattern.key.disabled;
mv /data/system/gatekeeper.password.key /data/system/gatekeeper.password.key.disabled;
mv /data/system/locksettings.db-wal /data/system/locksettings.db-wal.disabled;
mv /data/system/locksettings.db-shm /data/system/locksettings.db-shm.disabled;
mv /data/system/locksettings.db /data/system/locksettings.db.disabled;
reboot
Tick Use Root​Step 3. Create a new Task named Lock. Add Run Shell and under it type the following command​
Code:
mv /data/system/gatekeeper.pattern.key.disabled /data/system/gatekeeper.pattern.key;
mv /data/system/gatekeeper.password.key.disabled /data/system/gatekeeper.password.key;
mv /data/system/locksettings.db-wal.disabled /data/system/locksettings.db-wal;
mv /data/system/locksettings.db-shm.disabled /data/system/locksettings.db-shm;
mv /data/system/locksettings.db.disabled /data/system/locksettings.db;
reboot
Tick Use Root​Step 4. Now if you want to disable P3 just run Disable Lock Task and when your privacy is under danger, run Lock Task.​
Explanation: In Step 2 you rename files which store P3 data into ".disabled" which makes the files unreadable and thus your P3 is disabled. And in Step 3 we effectively nullify Step 2 restoring our old P3
PS: Run Disable Lock Task only if you have locked your phone using P3
PPS: Run Lock Task only if you have run Disable Lock Task
PPPS: I have personally used Pattern, PIN, and Password, so let me know in the comment section if you are able to successfully disable Fingerprint and Iris Scanner using above technique.

this is a very interesting approach.If I understand it correctly, you will have to reboot each time, right? is there anyway to bypass that, resulting a simple with on/off like the way secure setting works? maybe a kind of system force refresh?

alienyd said:
this is a very interesting approach.If I understand it correctly, you will have to reboot each time, right? is there anyway to bypass that, resulting a simple with on/off like the way secure setting works? maybe a kind of system force refresh?
Click to expand...
Click to collapse
Yeah, you have to reboot everytime you want to disable/enable lock. And I honestly don't know if there's any simple ON/OFF like in Secure Setting, I just discovered this method on an random forum. And I thought of posting the ideology here, since I'm sure many are not able to use Secure Setting to disable lock the same since Marshmallow.

I accidentally deleted those files , how to restore them ?

Midhun3! said:
I accidentally deleted those files , how to restore them ?
Click to expand...
Click to collapse
Are you using a custom ROM?

Yes

Midhun3! said:
Yes
Click to expand...
Click to collapse
Ok, try flashing your custom ROM. If that doesn't work, extract your custom ROM and copy pasting those deleted files to your phone.

this would have been great if not for the reboot. It just takes to long to reboot today's phones.
Sent from my LG-H815 using Tapatalk

I confirm the procedure works on rooted N LG VPad.
I will test on O LG G3 and report back.
I confirm that it works on android Oreo.
Now I would like to know where exactly did you find these commands. You said it was on anther forum. Please provide more info, maybe it proves to be a source of more interesting profiles and tasks.
Sent from my crDroid "O" powered LG-D855 using Tapatalk

I just checked one need not reboot, even a soft reboot does the job. Remove the "reboot" from the above commands. Create new shell task with "killall zygote" . Soft reboot is faster

My setup is
Honor 9 Lite
LineageOS 15.1
My intention is to
Set Fingerprint+PIN
Then, remove PIN and let Fingerprint remain.
Following KiranGadge911's instructions, I enter the following
Code:
adb shell
su
mv /data/system/locksettings.db /data/system/locksettings.db.disabled
reboot
The other files don't exist
/data/system/gatekeeper.password.key
/data/system/gatekeeper.pattern.key
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
I entered my fingerprint, after that it stayed stuck on "Android is starting..." message, indefinitely.
I've tried this twice, and had to Factory Reset twice. :silly:
If you have the same setup, let me know how you remove pin/password, in order to have fingerprint only.

@KiranGadge911 can this only be done if you have root? I have been looking for this exact approach, except not reboot but shutdown. However, I dont have root and I dont know if rooting my phone (OnePlus 6) violates any warranty.
Reason why I need this is that the phone (maybe others too) has a function that starts the phone based on schedule. I think it's great to be able to shut down the phone and let it start automatically at a given point.
However, if I haven't disabled any pin/password, I won't be reachable by phone.
This is where your solution comes in handy (although I think it would need to disable the SIM pin as well).