Although I've made fundamental protection in the Xposed module of Greenify (especially in 2.6 beta 10), some of you are still experiencing bootloop if experimental Xposed-based features are activated.
It's really hard to dig these issue without logcat since Android devices and ROMs are highly diverse (fragmented). But logcat in the bootloop case is understandable harder to capture than regular crash issues.
If you are one of the bootloop victims, and would like to help me on this issue. Please follow this instructions to capture a proper logcat for the bootloop issue:
1. Download and install ADB tool, either as standalone package or from the Android SDK.
2. Connect your device with a PC or laptop with USB cable.
3. Enable developer options on your device. (this must be done before the bootloop happens)
4. Test logcat capturing by typing this command in shell (or command prompt): "adb logcat -v time -d" (without quote marks), if you see plenty of log scrolling through the screen and finished, it's ready.
5. Trigger the bootloop, then after the device reboot, type this command in shell: "adb logcat -v time > logcat.txt", if you read "waiting for device" and the command continues running, that's OK.
6. Wait until the last command to finish and return to the shell, then you will get a "logcat.txt" file in the current path (usually the root path of your user home / folder). Send it to me via email (or pastebin.com).
If the command does not finish in a long time, just press "Ctrl + C" to end it, and send me the logcat.txt if it's not empty.
Thanks very much for your effort to help diagnosing this issue.
I had some severe boot loops on a CM12 device last night, I think it was just soft reboots not hard (no way to confirm it, sorry). It was running in root mode. I think a play store update cured that one. The SuperSU logs confirmed it was the item requesting access just before soft reboot.
I also had severe soft boot loops on my Moto X OTA 4.4.4, running in boost mode. Updating from play store (to 2.6.1), or disabling the xposed module auth for Greenify would not fix it. Only blocking SuperSU access fixed it. I just verified that granting SU back again to Greenify immediately causes soft boot loop.
Unfortunately, the effected device is a work unit with sensitive information, so I cannot post anything. I can try limited requests if you have any.
Waking a hibernated system app (Spotlight Player) caused a soft reboot, but it appears its working properly now going back into hib and back.
I have been experimenting with flashing, etc. and somehow the lockscreen were corrupted and the pattern I was using was not longer valid. I had the fingerprint already setup so I could enter using the rear sensor, but having a corrupted lockscreen is annoying. THis method requires TWRP custom recovery. It is compatible with locked bootloaders and doesn't modify the stock boot or system. It is also compatible with all the AAXON 7 models.
If you have the stock ROM and need TWRP and ADB interface:
A. Setup ADB interface in your PC and device drivers. and connect your terminal to the PC.
B. Setup axon7tool in your computer. Enter into EDL mode by running the command "adb reboot edl" in the command prompt. The terminal will seen to be off.
C. Disable the antivirus and then backup your recovery image using axon7tool running "axon7tool -r recovery". Save the created file in a safe place.
D. Flash tenfar's signed TWRP as a new recovery using axon7tool. It will reboot to system again.
E. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
1. In TWRP , and with the ADB interface properly installed run these the commands from your computer:
Code:
adb devices
adb shell mv /data/system/locksettings.db locksettings.db.old
adb reboot
Now the system will allow you to pass lockscreen without security. In that case you do not need to apply the rest of the steps. Should you continue experimenting issues with the lockscreen, then you should apply the full procedure. Just add the following 2 steps:
2. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
3. When TWRP had fully loaded, run in the command prompt the following commands:
Code:
adb devices
adb shell mv /data/system/gatekeeper.pattern.key gatekeeper.pattern.key.old
adb shell mv /data/system/locksettings.db locksettings.db.old
adb shell mv /data/system/gatekeeper.password.key gatekeeper.password.key.old
adb shell mv /data/system/locksettings.db-shm locksettings.db-shm.old
adb shell mv /data/system/locksettings.db-wal locksettings.db-wal.old
adb reboot
If you want to restore the stock recovery, you just need to rename the recovery-backup.bin file created in step C back to recovery.bin and run the command "axon7tool -w recovery". after that you can enable your antivirus software again. axon7tool can't connect with some antivirus software. I will be editing this OP with links to the procedures required for each step. All of them are in this forums.
Enjoy
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
DrakenFX said:
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
Click to expand...
Click to collapse
Sure! but this guide is intended for people with the stock, unrooted, blocked bootloader who want to remain with a pure stock experience. Usually people without experience rooting devices. This is why I will edit the guide to add all the details to every step.
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
twilighttony said:
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
Click to expand...
Click to collapse
Yes, the procedure deletes everything. If you have problems just do the same also with:
gatekeeper.password.key
locksettings.db-shm
locksettings.db-wal
I have updated the OP just to describe the full procedure.
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Masterjuggler said:
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Click to expand...
Click to collapse
The problem of this method is that it only works if the bootloader is unlocked and the phone has the No-verify patch installed.
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Masterjuggler said:
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Click to expand...
Click to collapse
No-Verify is an additional security system implementend in the kernel. When No-Verify is active, it checks for the signature of the system partition. If the system was modified, then the system won't boot. This is why after unlocking the bootloader you have to apply No-Verify Patch or any package with the integrated patch such as SuperSU. As you can see, it has nothing to do with the app signature or the lockscreen at all.
The method presented in the OP is valid for most Android phones, and the only prerequisite is to have TWRP installed. It is safe and a lot more recommended than patching the system partition. Patching system or kernel should always be your last resort. usually deleting locksettings.db is enough, and it is a general method that works for almost any locking method.
On B25 and have followed all instructions. Seems this method no longer works :/
- Simple and safe installer;
- Installs stock and offers to install Customization Package (optional);
- Can be used to flash other ROMs that use "flash_rom.sh";
- Can be used to fix bricked devices with unlocked bootloader.
DISCLAIMER: You are using the provided files by your own risk, although I have tested the installation I am not responsible for any damage or data lost if you decide to use them.
Click to expand...
Click to collapse
Compatible with macOS/Linux (tested on High Sierra and Ubuntu 16.04) or Windows. Requires unlocked bootloader!
The script will check for requirements, and will only continue if everything is fine. If you are on Windows, make sure the drivers are working correctly before starting: open Device Manager and put watch in fastboot mode then check if it is detected correctly, or you can use the provided "checkdrivers_win.cmd" to do this and check if watch's bootloader is unlocked. If you get any errors then probably drivers aren't installed properly, and you should fix this before starting.
PS: If you are on Windows, make sure fastboot driver is working properly using the directions above. If the driver seems to be installed correctly (no question mark on the device) then try disabling or uninstalling your antivirus temporary. Avast is known to cause problems with USB drivers.
Current version installs firmware 2.6.2.0 (WOS2 = Watch OS 2.0) on Pace, and can be used to fix a bricked watch, simply put it in fastboot mode manually *before* starting the script. Make sure you try to do this with a Pace watch or provide the correct ROM in the "rom" folder, otherwise it will brick your device.
PS: During the ROM installation, when watch is in Recovery Mode, it will display a triangle with an exclamation mark and the text "no command", it's expected! Simply follow the instructions provided by the script.
- How to run on Linux
Go to the folder with the uncompressed files in terminal and run "sudo bash amazeflash.command" (Linux requires root access to fastboot), then follow instructions.
- How to run on macOS
Go to the folder with the uncompressed files in Terminal and run "bash amazeflash.command", or simply double-click "amazeflash.command" then follow instructions. PS: Decompress the 7z file with Keka or TheUnarchiver to preserve file permissions.
- How to run on Windows
Go to the folder with the uncompressed files in command prompt and run "amazeflash_win.cmd" or simply double-click "amazeflash_win.cmd" (you may not see the file extension in some cases), then follow instructions.
Use the same procedure if you want to run the custom package installation script after you successfully flashed the ROM, it will prompt to install modded files or revert to stock versions. Be aware the reverting to stock version may not work if you want to apply OTA to update later, it's recommended that you flash stock version again and don't apply the Customization Package.
For more info, please refer to the included "readme.txt" file.
Some remarks:
- Customization Package includes WearSettings, NewWearSport and HuamiWatchFaces with improved support and voice prompts in English.
- If watch is *not* on firmware 2.x yet (it means *any* 1.x firmware) then probably you want to do a factory reset first and then use the installer (it works even if watch shows QR code).
- If watch already have firmware 2.x, then no need to factory reset first a priori...
- On stock ROM in English, the "About" section in Settings causes it to crash, it works in Chinese and if the Customization Package is installed.
- After a Factory Reset, language will revert to Chinese, you can set it back to English with these adb commands (you can use copy and paste, a Windows batch script is provided too):
Code:
adb wait-for-device
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US
adb reboot
You can buy me a coffee or cheesecake (please, no beers ), Paypal address for donations: lfomartins[at]aim.com
Or most common cryptocoins here: https://freewallet.org/id/87331be5
PS: there is no fee free option to transfer money to my country, you must use "pay for goods and services". But don't worry, you will only be charged for the amount you send. Thanks!
This was only possible because of the modded recovery image provided by @Neuer_User:
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
In the above post you can find details on how to put Pace or Stratos manually in fastboot mode. It's tricky and very hard to do, but it works.
*************************
Latest Version v1.2 - firmware 2.6.2.0
- Installer will NOT run anymore if root is detected (this can happen if watch has other custom ROMs) and only install via fastboot/recovery (safer).
- amazefls.log now won't be erased every time you run the installer script, but store all flash history for debugging.
Download link:
https://mega.nz/#!9OJ0mIqA!QgnX9f675VbZI9ECx__ScnHtgHTAdRa1fldWtZdVR9U
SHA1SUM: E941FD472C626872707C06065177DC728BA64FB6
*************************
Old versions
v1.1 - * Link removed, please use v1.2 *
SHA1SUM: 0CB3FB554A397B53C1E739586E98C2FF8C1FCE0C
- Updated to firmware 2.6.2.0
- Updated support for EN
Firmware Changelog (translated using Google Translator)
- Added World Cup event reminder function, need to upgrade to the latest mobile phone App, and set a reminder in the live World Cup page
- Added virtual rabbit mode to support running, indoor running, outdoor riding, cross-country running, open in Sports Settings > Motion Control
- Added Heart Rate Interval to Reserve Heart Rate Mode, App> My> My Info> Heart Rate Interval Settings
- Added data items such as sectioning speed and section speed to support running, trail running, walking, outdoor cycling and other sports
- Occurrence of abnormal heart rate output after optimising Bluetooth heartbeat disconnection
- Repair the lock screen second hand display of the third party dial
- Fixed several bugs
Thanks to @Saratoga79 for sharing the system dump! You rock, dude!
v1.01 - * Link removed, please use v1.2 *
SHA1SUM: 47D0777F599586A63D293E592B6770D7FE77982A
- Fixed AmazeCustom installer for both Win and Mac when run separately;
- Moved all scripts to main folder for easier access and simplified maintenance;
- Moved all Windows binaries to pgm folder to simplify future updates;
- Added Windows script to set language to EN (needed after a factory reset/unpair).
v1.0 - * Link removed, please use v1.2 *
SHA1SUM: 64205E4D683B388E8C087FCF49B20FE6FDEA8235
- Initial Release
Thanks to @ingraynieris and @chincheang for testing and @1immortal for support.
Manual Installation
Requirements
- Pace watch (A1602 or A1612);
- Unlocked booloader (unlockamazfit.com - read carefully the warning, doing this will void watch's warranty!);
- adb, fastboot and drivers installed correctly;
- 40% battery or more, read English and pay attention!
******************************************
DISCLAIMER: You are using the provided guide by your own risk, although I have tested the commands I am not responsible for any damage or data lost if you decide to use it.
******************************************
This is an installation guide, if you have never used adb or fastboot, then please don't try to do this. Commands should be typed in terminal/prompt/whatever you use to do adb commands.
In the end of this guide, you should have a watch with stock WOS2, so OTAs should work. Do not modify any system files if you want to apply future OTA updates, not even get root access, it may break stock updates.
Unpack the compressed 7zip file from the link at some place you have at least 1GB of free space and adb/fastboot access, then change to this directory to begin. Commands below are for Windows, macOS and Linux users should change the backslash ('\') to normal slash ('/'), hit ENTER/RETURN after each line (duh!).
If you are trying to fix a bricked devices, make sure it's in fastboot mode and that the computer detects the device, then start from step #3.
1. Connect the watch to computer using USB cable, then:
Code:
adb devices
2. If you see your device listed, type:
Code:
adb shell reboot bootloader
3. Check if device is recognized correctly (on Windows, open Device Manager and check if you see a device in fastboot mode or similar), then type:
Code:
fastboot getvar all
4. If you see "unlocked: yes", you can continue. Reboot into temporary root/Recovery:
Code:
fastboot boot Amazfit-mod-recovery.img
5. Watch should show a triangle with an exclamation mark, it's in Recovey mode and it's normal, do not panic! Then make sure you have root now:
Code:
adb root
6. Then push files to watch:
Code:
adb push rom\boot.img /data/media/0/
adb push rom\md5s.txt /data/media/0/
adb push rom\system.img /data/media/0/
adb push rom\flash_rom.sh /data/media/0/
If it fails, try:
Code:
adb push rom\boot.img /sdcard/
adb push rom\md5s.txt /sdcard/
adb push rom\system.img /sdcard/
adb push rom\flash_rom.sh /sdcard/
7. Take a deep breath and then (after the first command, you should see a "#" only, indicating root prompt):
Code:
adb shell
cd /data/media/0
sh flash_rom.sh
or use "cd /sdcard" if you have copied the files to this directory instead.
8. Wait until it says "Finished", then type:
Code:
reboot
9. To set English language after booting (stock CN WOS2 has some bugs, i.e. About in settings crash, some watchfaces show Chinese names when screen is locked, etc):
Code:
adb wait-for-device
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country US
adb reboot
Thanks for your rom, have seen it on fb to great work!
Verstuurd vanaf mijn ONEPLUS A5000 met Tapatalk
Thank you for your great work!
Is it possible to install custom GPS.conf files? Will it break OTA updates?
xaametz said:
Thank you for your great work!
Is it possible to install custom GPS.conf files? Will it break OTA updates?
Click to expand...
Click to collapse
You're welcome. I am glad you like it.
Yes, you can install a custom gps.conf the same way you do with any other ROM (root, remount, push, fix permissions, reboot), but my personal experience is that GPS is much better on 2.6.1.0, no need to change anything. I cannot guarantee it will not break OTA, may or may not work as it's not a file that is used in stock firmware, but any modification to /system can cause problems. Anyway, with AmazeROM you can always flash stock later if you need it for future updates.
lfom said:
You're welcome. I am glad you like it.
Yes, you can install a custom gps.conf the same way you do with any other ROM (root, remount, push, fix permissions, reboot), but my personal experience is that GPS is much better on 2.6.1.0, no need to change anything. I cannot guarantee it will not break OTA, may or may not work as it's not a file that is used in stock firmware, but any modification to /system can cause problems. Anyway, with AmazeROM you can always flash stock later if you need it for future updates.
Click to expand...
Click to collapse
Thank you. I'll try it without custom config.
Enviado desde mi STF-L09 mediante Tapatalk
Hi,
Minor problem with the script that installs the customised apk's: You seem to have forgotten to replace "adb" with "$adbcmd" and "fastboot" with "$fbcmd".
Thanks for all the effort you have put into the scripts!
R.
Eeg.
superbert1969 said:
Hi,
Minor problem with the script that installs the customised apk's: You seem to have forgotten to replace "adb" with "$adbcmd" and "fastboot" with "$fbcmd".
Thanks for all the effort you have put into the scripts!
R.
Eeg.
Click to expand...
Click to collapse
True, thanks for reporting. There is a problem in the Windows installer as well, it doesn't work if you run it without command line arguments, it will be fixed in the next release.
I just made some quick an dirty adaptations in order to get the custom script running. Unfortunately, I'm now stuck with an unwilling fastboot (maybe it's because I'm still on "El Capitan" --> I'm considering upgrading, but first have to make a recent backup).
Though-luck for now, I'm stuck with a watch that has some Chinese notifications (at least for the time being).
superbert1969 said:
I just made some quick an dirty adaptations in order to get the custom script running. Unfortunately, I'm now stuck with an unwilling fastboot (maybe it's because I'm still on "El Capitan" --> I'm considering upgrading, but first have to make a recent backup).
Though-luck for now, I'm stuck with a watch that has some Chinese notifications (at least for the time being).
Click to expand...
Click to collapse
I have updated the installers, please check them. I am sorry for the trouble.
Hi,
You don't have to excuse yourself at all...
I just tried the new version, and it works perfectly fine now (even on my Mac).
I really appreciate the effort you're putting into AmazeROM
@lfom: HELP!
Unfortunately this installer crashs my Pace.
In the past I have used PACEfied and PACEficator custom ROM and the installers works always perfect.
But this one fails in some steps but continues and ends with an "ok" and now I see only the "A" logo before the boot animation.
Attached the whole CMD output.
I hope the Pace is not bricked. ADB devices shows the Pace, but no other commands (e.g. "fastboot reboot bootloader") are working.
Got the same problem, it crashed my PACE too, was running PACEficator Project before, now it keep having luncher has stopped error.
Installer stopped on fastboot and unable to boot to recovery anymore
fastboot boot Amazfit-mod-recovery.img
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.012s
Edit: after search the forums, I unpair and re-pair my PACE and the watch is working now. however, I am not sure should I still install this ROM on my watch anymore.
@Diginix @thomsontam Did you check you have an unlocked bootloader? If yes, you should be able to put watch in fastboot mode and flash the ROM again. It seems that the installer detected root and went ahead with the installation, but the watch crashed and it did not finish. If it's locked and you have a valid serial number, you should be able to unlock it using the same code as before. If not, please contact me via Telegram: http://t.me/lfomartins
@lfom
I had an unlocked bootloader until PACEficator 2.6.0.12. I didn't checked it after update to PACEficator 2.6.1.0
Root was definitely existing and working.
I have my serial nr. and the unlock code.
But what commands should I try now?
This doesn't work:
adb shell reboot bootloader
- exec '/system/bin/sh' failed: No such file or directory (2) -
using port=5555
Click to expand...
Click to collapse
My backlight is always on and shows the Amazfit "A". I hope the battery is charging.
@Diginix You have broken file system. You should be able to put the watch in fastboot manually. It is very hard to achieve but it works. Then check if bootloader is unlocked and try to flash it again. If you have problems, contact me on Telegram.
I have no Telegram and need ready for use commands please.
Your checkdrivers_win.cmd doesn't provide any hope.
btw: adb+fastboot was proper installed and works in the past perfect with the installer of other custom roms.
Edit: I will try this steps.
Edit2: My Pace can't be turn off as in the youtube video is shown. It always shows the "A" and backlight is on.
As it seems fastboot isn't reachable. But I will try some different delays at pressing the button and plugin it on PC.
@Diginix checkdrivers_win.cmd is useless now with a bricked device. You can turn the watch off by pressing and holding the button. Keep the watch connected to the computer and then press button again to turn it on, then count up to 4 (more or less) after the screen goes on again and release the button. If you see the battery icon you have released the button too early, if you see the A logo then you released too late. You have to release at the exact time to show the screen with Fastboot and ForceErase, then press button briefly once to enter fastboot. Keep the watch connected to the computer all the time, it's easier this way.
Now I'm in fastboot!
But "fastboot devices" doesn't prompt any device.
What to do with your ROM files?
Hi!
I installed and I'm using adb and fastboot on Mac, it works perfectly adb, but with fastboot it does not detect the clock. But if I try on my OnePlus 6, I detect both adb and fastboot the Mac. How can I do? Thank you
Ok lets first explain the situation
I've been dabbling with Tasker (Paid for version)- getting some automation depending on certain situations (mainly stuff like 'If I'm @ {location} get volumes set high' or ' If Unread msg then vibrate my Amazefit bip watch' - Nothing too complicated using variables / javascript etc)
One situation I want to attempt though is 'If Gpay app is started - turn on NFC, but when I leave the app - turn NFC off'
Now I already know there are 2 'main' ways I can turn on/off NFC in Tasker.. either use 'AutoInput plugin' or use 'Secure Settings'
- I've tried with Autoinput plugin but the problem is that with the free option, you need to watch an Ad every day to use it but of course I can pay for it (its only a couple of quid)
However you can't Install it & pay for it directly from within the plugin - you need to install yet another App (AutoApps) first - & although this one is free - I just don't like adding more bloat to my phone than necessary. Adding both the plugin & this additional App adds (although only a 'minor' amount) up to 20Mb
The other method is give Tasker 'Secure settings' permission
- So I read the 'What to do to give 'Write Secure Settings Permission' to Tasker' (enable Developer mode > Usb Debugging > Install ADB on PC etc etc) & it looks simple enough,
But (a loooong time ago) I tried other 'hacks' & it ended up disastrously (probably I did something wrong with missing a step or something) & I just want to make sure that it IS as simple as it seems and also ask how safe is it
for example
* If I type in the command in ADB - could something go wrong & could it crash/brick the phone ?
* Is this permanent - ie if I turn off/on phone or if I get an OTA update & phone restarts - will it stay, or will I have to repeat the ADB command each time ?
* Will this 'break' official OTA updates (whether security &/or Android firmware) - I once did a firmware update with a step that used ADB (IIRC) & it broke something that prevented any updates from happening
- official OR manual firmware updates
Any help/advice would be appreciated
Cannon_Foddr said:
* If I type in the command in ADB - could something go wrong & could it crash/brick the phone ?
* Is this permanent - ie if I turn off/on phone or if I get an OTA update & phone restarts - will it stay, or will I have to repeat the ADB command each time ?
* Will this 'break' official OTA updates (whether security &/or Android firmware) - I once did a firmware update with a step that used ADB (IIRC) & it broke something that prevented any updates from happening
- official OR manual firmware updates
Click to expand...
Click to collapse
ADB is the door to your phone's Android. It's a tool not meant to be used by John Doe. Wrongly used you can brick your phone. Hence it's by default disabled.
1. Yes, using ADB you can render your phone absolutely useless. If you e.g. enter
Code:
adb shell rm -rf /
then phone gets totally wiped ( really all gets destroyed, it gets naked ) - you can throw it into electric waste.
2. ADB commands aren't persistent, but their results may be.
3. ADB itself breaks nothing: it's a driver installed on your computer that let you access Android's files and launch Android executables.
Thanks for the reply
I doubt I'll use THAT command.
I forgot to mention what tasker's command is
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
Not 100% sure about your last comment though.
ADB allows access to android files so changing android files could break things, which I'm worried about especially with OTA updates etc. (my last phone stopped getting OTA updates when I rooted it despite using official firmware)
However IF I understand the above command all this does is tell the android operating system ('android') to only give the tasker app (which 'Real' name is 'net.dinglisch.android.taskerm') the rights ('permission') to access the required settings ('WRITE_SECURE_SETTINGS') which the NFC on/off toggle is part of (settings >connected devices > connection preferences> nfc) & 'shouldn' t' affect any other files such as OTA (unless OTA is also part of secure setting?)
@Cannon_Foddr
As I can see you until now haven't understood what ADB is, how it works.
Same probably your understanding of what an OTA is.
Personally never would allow 3rd-party apps ( like Tasker ) to modify sensible system settings: Tasker isn't an open-source app, so you can't control what it does in the last run.
It's simply on you to decide whether Tasker is given that right, or not ...
Can't see why 'open-source' has to do with this
IMHO if Open-source - anyone can release similar apps with added extra hidden code that could spy's on you/steal info etc, but a 'closed sourced' app from a long running developer (tasker been around for 10yrs with over 1mil downloads) must mean people seem to trust him/them & if he was 'dodgy' surely he would've been caught out by now
Anyway the Bottom line seems to be
Safe route: pay for plugin & live with extra bloatware
Or
Risky route: give access to secure system resources, see what happens & keep fingers cross nothing does
Thanks for your replies.. I think I may have to sit down & have a long hard think which route I feel more comfortable with
I have been using Automate for about 4 months now. I granted it WRITE_SECURE_SETTINGS and I have not noticed any modifications in my system. Granted I may have not looked specifically for them but as far as braking the system or disruption of OTAs no issues so far
DennisHarrows said:
I have been using Automate for about 4 months now. I granted it WRITE_SECURE_SETTINGS and I have not noticed any modifications in my system. Granted I may have not looked specifically for them but as far as braking the system or disruption of OTAs no issues so far
Click to expand...
Click to collapse
I assume you had to do something like Taskers command then to grant the secure settings
( "adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS" )
Cannon_Foddr said:
I assume you had to do something like Taskers command then to grant the secure settings
( "adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS" )
Click to expand...
Click to collapse
Automate is straight forward, there is a toggle for "modify system settings" needed for some tasks to run and one you run the ADB command, it's done