ADB Hack - Granting extra capabilities via the ADB tool

Endercraft

Moderator
That seems like a library issue to me. Check if all the files that come with the adb executable are present (should be lib(something)).
 

KDG

Member
That seems like a library issue to me. Check if all the files that come with the adb executable are present (should be lib(something)).
Yes, they are all there.

What's odd is adb claiming it's looking in a place for a file when adb (& all associated files) are right where it's supposed to be. Really, you can place the adb package anywhere & the terminal acknowledges it's there. But why it's referencing that other file I don't understand.
 

Dimlos

Well-known member
If you just want to do an adb hack, there are ways to do it without a PC.

 
  • Like
Reactions: KDG

KDG

Member
If you just want to do an adb hack, there are ways to do it without a PC.

My goal is wanting to initiate GPS if a Bluetooth connection is established in my car. I can setup the script easy, but "location" functions need adb hack & so if I can use that app, I'll just do that.

Update; I have it running now with Shizuku
 
Last edited:

Abrahamchi

New member
Hi. I need help. I do everything correctly but when I open again the MacroDroid App and configure a new Macro (Open Gmail - when - Device Turn On) but is not working

I don´t have errors when install ADB Hacks, My devices is detected but idk what can i do
 

dhj49er

Well-known member
Hi. I need help. I do everything correctly but when I open again the MacroDroid App and configure a new Macro (Open Gmail - when - Device Turn On) but is not working

I don´t have errors when install ADB Hacks, My devices is detected but idk what can i do
Is this your macro?
T screen on
A launch Gmail
 

Abrahamchi

New member
Is this your macro?
T screen on
A launch Gmail
I do again everything

- First, Download abd from https://developer.android.com/tools/releases/platform-tools?hl=es-419#downloads (And Copy - Paste on my C: Folder the files, next i add to path the url "C:\adb")

- I open CMD like admin and run the command "adb devices" with my devices connected

1740604576966.png

- Next, I run the coomands
1740604628740.png

- Next, I finish CMD and go to my device and configure the Macro again

1740604732906.png

- Next I reboot, TurnOff and TurnOn or just run the Macro, but is not working
Idk if i need do something else
 

Qarboz

Well-known member
I do again everything

- First, Download abd from https://developer.android.com/tools/releases/platform-tools?hl=es-419#downloads (And Copy - Paste on my C: Folder the files, next i add to path the url "C:\adb")

- I open CMD like admin and run the command "adb devices" with my devices connected

View attachment 13159

- Next, I run the coomands
View attachment 13160

- Next, I finish CMD and go to my device and configure the Macro again

View attachment 13161

- Next I reboot, TurnOff and TurnOn or just run the Macro, but is not working
Idk if i need do something else

First of all, when you need to run the ADB commands taken to the directory C:\ADB

In the macro, before launching Gmail add a wait of 30s...1m (to be tested) to give time for the device to load all background services
 

Endercraft

Moderator
On newer devices, immersive mode may not work.
Because of secure boot, the device boot trigger may not fire unless the device is unlocked quickly. The MacroDroid initialized trigger should work.
 

fred59

New member
À partir de MacroDroid V3.16.11 (avec quelques efforts), vous pouvez désormais invoquer les fonctionnalités suivantes sur un appareil non rooté :

Action d'économie de batterie
Action du mode de localisation
Action d'activation/désactivation NFC
Définir l'action de la langue
Déclencheur Logcat
+ d'autres comme indiqué dans l'application.

Pour ce faire, vous aurez besoin d'un PC sous Windows/Linux ou d'un Mac ainsi que de l'outil ADB de Google qui peut être téléchargé à partir des liens ci-dessous :

Windows - https://dl.google.com/android/repositor ... indows.zip
Linux - https://dl.google.com/android/repositor ... -linux.zip
Mac - https://dl.google.com/android/repositor ... darwin.zip

Pour obtenir des instructions sur la configuration de votre appareil pour se connecter via adb, veuillez consulter les informations suivantes :

https://developer.android.com/studio/co ... e/adb.html

Une fois que vous disposez d'une connexion ADB fonctionnelle, vous devez exécuter la commande suivante à partir de la ligne de commande/du terminal sur votre ordinateur :

adb shell pm grant com.arlosoft.macrodroid android.permission.WRITE_SECURE_SETTINGS

suivi de:

adb shell pm grant com.arlosoft.macrodroid android.permission.CHANGE_CONFIGURATION

Si vous utilisez le mode démo, vous aurez également besoin de l'autorisation suivante :

adb shell pm grant com.arlosoft.macrodroid android.permission.DUMP

Si vous utilisez le déclencheur d'appui long sur le bouton de volume, vous aurez besoin de l'autorisation suivante :

adb shell pm grant com.arlosoft.macrodroid android.permission.SET_VOLUME_KEY_LONG_PRESS_LISTENER

Si vous utilisez le déclencheur Logcat, vous aurez besoin de l'autorisation suivante :

adb shell pm grant com.arlosoft.macrodroid android.permission.READ_LOGS

Ces commandes donneront à MacroDroid l'autorisation d'écrire dans certains paramètres restreints de l'appareil qui ne peuvent normalement être effectués que par des applications système (ou à l'aide de hacks root).
C'est un peu de travail mais j'espère que ce sera une bonne solution pour les utilisateurs qui ne peuvent pas ou ne veulent pas rooter leur appareil.

Les fonctionnalités ci-dessus sont actuellement les seules fonctionnalités qui peuvent être utilisées par ce hack d'autorisation adb, mais j'espère qu'à l'avenir je pourrai étendre la capacité pour autoriser des fonctionnalités supplémentaires.

Erreur d'autorisation lors de l'octroi

Sur certains appareils, une erreur peut se produire lors de l'octroi de l'autorisation ADB qui ressemble à ceci :

Ni l'utilisateur 2000 ni le processus actuel n'ont android.permission.GRANT_RUNTIME_PERMISSIONS

Dans ce cas, vérifiez les options de développement de votre téléphone et recherchez un paramètre appelé « Désactiver la surveillance des autorisations » ou « Débogage USB (paramètres de sécurité) » ou quelque chose de similaire et activez/désactivez-le selon le cas.

Informations complémentaires pour le fichier d'aide

À partir de MacroDroid v5.8, un nouveau fichier d'aide est disponible pour exécuter certaines fonctionnalités limitées qui ne peuvent pas être effectuées directement dans l'application. Afin d'accorder à ADB l'accès à ce fichier d'aide, veuillez utiliser la commande suivante :

adb shell pm grant com.arlosoft.macrodroid.helper android.permission.WRITE_SECURE_SETTINGS
Bonjour,

macrodroid m'indiquait un message d'erreur et me demandait de remettre la permission d'accessibilité avec adb. En cherchant je suis arrivé sur cette page
j'ai suivi les points cités plus haut et, depuis, j'ai un problème avec le talkback qui est activé en permanence. Quand je le désactive, il se réactive tout seul instantanément et en boucle infinie.

Peux-tu m'aider si tu veux ?
---------------------
Good morning,

macrodroid gave me an error message and asked me to reset accessibility permission with adb. While searching I came to this page
I followed the points above and, since then, I have a problem with the talkback which is permanently activated. When I turn it off, it reacts immediately himself and endlessly.

I ran all the adb commands from the previous message

Can you help me please t?
 
Last edited:

fred59

New member
MacroDroid --> Paramètres --> Laisser les services d'accessibilité en marche. Décochez toutes les cases et vérifiez si cela se produit toujours.
That works
I stopped talkback, thank you very much

I had done the adb manipulation because for 5 days my macros have no longer been triggered. adb commands didn't change anything

Any idea of the problem?
The macros are validated (check mark). It worked perfectly for a long time and one day nothing works anymore

macro triggers are not in the system log
 
Last edited:

harig123

New member
DISCLAIMER TO ANYONE TRYING THIS: PLEASE MAKE SURE THE "UNIVERSAL SWITCH" AND "TALKBACK" BOXES UNDER "KEEP ACCESSIBILITY SERVICES RUNNING" IN MACRODROID ARE UNTICKED BEFORE AND THAT ALL IMPORTANT MACROS ARE BACKED UP.

Have had the most frustrating two hours trying to get out of being stuck in Talkback.

To anyone with the talkback issue: as @Endercraft said above, it's because the Talkback (and Universal Switch) boxes are ticxked under "Keep Accessibility Services Running". You get into a loop that is hard to break of Android denying permissions to use it and MacroDroid reaffirming them again (and you get it saying "Talback on" loudly every few seconds and you can't do anything - even a restart doesn't help". In the end, lost patience and paid way too much for a subscription to a dodgy app (Coolmuster) to delete Macrodroid from my PC. Then, restarted and, whilst Talkback was still on, it was actually usable (if you search up instructions on how to online - three fingers for swipe etc.) and could finally turn it off through accessibility settings.
 

harig123

New member
However, it does look like it fixed my issue of my macros stopping after a pop-up of "accessibility required".
 

Winny57

Active member
If you have Shizuku enabled, I modified an existing macro to grant all possible permissions to the selected application.

Once triggered, you must choose which application will receive all possible permissions. The application will work and provide you with a result based on the permissions granted.
 

Attachments

  • Grant_ADB_apps-mod (2).macro
    83 KB · Views: 4
Top