You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To install a system certificate, first connect a supported device using ADB, and the "Android device connected via ADB" interception option will appear on the 'Intercept' page in your HTTP Toolkit application. Click that, and the certificate will be added as a system certificate on the device, the HTTP Toolkit Android app will be installed if not already present (this may take 10 seconds or so), and then interception will start up automatically.
i clicked that and it didnt work also checked root
C:\Users\usuario\Desktop\platform-tools>adb devices
List of devices attached
d38f77b70221 device
C:\Users\usuario\Desktop\platform-tools>adb shell
pomelo:/ $ su root whoami
pomelo:/ # adb shell
/system/bin/sh: adb: inaccessible or not found
127|pomelo:/ # su -c whoami
root
pomelo:/ #
also magisk was denying access so i had to change settings
once granted, it still didn't work, tutorial doesn't tell you to disconnect android over qr first,if you switch to adb devices while you are in android qr it will not work
How often does this bug happen?
Every time
The desktop OS you're using
Windows 10
Details of other apps/devices
Any phone will have this issue
Error screenshot
No response
Any other info?
No response
The text was updated successfully, but these errors were encountered:
Thanks for the feedback @elproricardo123. To be clear, the biggest problem you had with the tutorial is that it didn't tell you to disconnect the QR code first is that right?
That's surprising, because that should be required. I've just tested and it works correctly for me on my test device going from QR code to ADB without manually disconnecting.
The Magisk access permissions are definitely required though, so that might have been the issue, and the tutorial is a bit weirdly written to make you test both approaches right now (most of the time, if you have ADB you should just use ADB all the time and skip the QR code completely).
There are quite a few other larger changes to the website already in progress, so I'm not going to update this immediately, but I agree there's plenty of improvements to make there. I'll make sure that tutorial gets revamped to include some of these points once the current big update is done.
Has this been reported before?
Repro steps
To install a system certificate, first connect a supported device using ADB, and the "Android device connected via ADB" interception option will appear on the 'Intercept' page in your HTTP Toolkit application. Click that, and the certificate will be added as a system certificate on the device, the HTTP Toolkit Android app will be installed if not already present (this may take 10 seconds or so), and then interception will start up automatically.
i clicked that and it didnt work also checked root
C:\Users\usuario\Desktop\platform-tools>adb devices
List of devices attached
d38f77b70221 device
C:\Users\usuario\Desktop\platform-tools>adb shell
pomelo:/ $ su root whoami
pomelo:/ # adb shell
/system/bin/sh: adb: inaccessible or not found
127|pomelo:/ # su -c whoami
root
pomelo:/ #
also magisk was denying access so i had to change settings
once granted, it still didn't work, tutorial doesn't tell you to disconnect android over qr first,if you switch to adb devices while you are in android qr it will not work
How often does this bug happen?
Every time
The desktop OS you're using
Windows 10
Details of other apps/devices
Any phone will have this issue
Error screenshot
No response
Any other info?
No response
The text was updated successfully, but these errors were encountered: