Does anybody know of a way to gain access to a password encrypted android 9 device? It is an Alcatel 5033D, locked bootloader and stock recovery, and I have no access to the virtual keyboard from the lockscreen after force uninstalling Gboard; which apparently the device was relying on for the lockscreen, even though other virtual keyboards work just fine after unlock. I am aware that USB OTG might be usable to enter the passphrase, using a physical keyboard, but I do not have the requisite USB OTG hub for that job and would like to try every other alternative before buying one as a last ditch effort.
I have tried to boot into recovery and sideload stock open Gapps, which contains google's keyboard, but it will not pass the signature verification phase and thus aborts the install. I do have USB debugging enabled and I can see the device when executing 'adb devices' but it is not authorized so I cannot actually interact with the device directly using adb. I have tried killing the server and starting it again with root (on my host machine) and this changed the device status from 'insufficient permissions' to 'unauthorized' which did not help at all. I do see an option for 'Enable adb' in the stock recovery screen, but I when I run that it prints the following; "Enable adbE:Failed to mount /persist: No such file or directory. /persist not yet mounted!"
Anyone got any ideas? Thanks in advance for any support
Related
I am using a Nexus 5 running Android 5.0.1, with adb version 1.0.32, on OS X 10.10.1.
When I reboot the device, on the initial screen I see:
USB debugging connected
Touch to disable USB debugging​
I swipe up to unlock and then see the dialog:
Allow USB debugging?
The computer's RSA key fingerprint is: <....>
[] Always allow from this computer​
I check always allow and tap OK.
If I reboot the device, I see the exact same thing again. I assume I should not be asked again and again to trust the same computer after a simple reboot.
Can anyone point me to a detailed description of how this system works so I can determine what is going wrong?
I believe the key identifying the computer is stored in the device in the data directory. I assume that a key would be stored on the computer as well. What is this location?
Is there anything else I can check?
Has anyone seen this before? If so, what was done to resolve the problem?
I currently have 5.1.1 installed on my honor 5x and am able to use adb automatically without accepting an RSA prompt (have installed twrp, rooted, etc.) but when I dload a MM stock rom and use usb debugging it is unauthorized and I get no RSA prompt I've even gone as far as to delete /data/misc/adb from my device and adbkey.pub from my desktop but there is still no pop up authorization in MM
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
ShadySquirrel said:
Developer options -> Revoke authorisation (something like that), replug. If that doesn't help, change connection mode to file transfer and try again.
Click to expand...
Click to collapse
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Tsunetoma said:
I actually don't have a "revoke authorization" button below usb debugging, odd I know but I've tried all those options to no avail
Click to expand...
Click to collapse
Tried toggling the debugging switch? I had issues like these on one of my previous devices, but usually these were fixed with a simple port change or debug off/on switch, if revoke->replug didn't work.
Have you checked drivers, or if dmesg says something about the device, if you're on Linux? Sometimes even running multiple adb instances (like one from terminal and one from Android Studio, for example) can cause this behviour.
Enable rsa key authentication
I installed a Substratum overlay which screwed up my phone and now every time I boot into system the screen remains black. I'm on RROS 6.0.0 (Android 8.1) so I was only able to install a TWRP without decryption thus I can't access system/data in order to delete the overlays there. The only way to access it now would be over ADB while the phone is booted to system. The problem is, although I've enabled USB debugging I'd have to enable USB file transfer (default set to charge only) in order to be able to access my phone via USB. Right now I always get the output:
Code:
[email protected]:~$ sudo adb devices
List of devices attached
???????????? no permissions
Is there any way to enable USB file transfer or just generally access /system/data without any inputs while being in system? I know, I could just do a factory reset but I'd rather avoid that... Any help would be appreciated!
I have a jp5s tablet running android 4.2.2. It is a prison issued tablet. USB debugging is not enabled, and you can't enable devlopers options. Bluetooth works but app installation is blocked for security purposes. And the ability to allow unknown sources is disabled. Recovery mode only has reboot now. There is no fastboot so adb on windows will not connect. My only idea is maybe a picture or video file that runs a script to allow USB debugging, or installs an apk(a file manager). Also I'll pay for one that will set my devices year back to 2011 or so. Please any help or advice. Maybe a windows program that will force connect adb somehow.
Yeah you can go to settings but its very limited, pressing build number only brings up a list of installed apps.
Nothing google at all its a prison tablet that's the issue I want to install apps
inameasone said:
I have a jp5s tablet running android 4.2.2. It is a prison issued tablet. USB debugging is not enabled, and you can't enable devlopers options. Bluetooth works but app installation is blocked for security purposes. And the ability to allow unknown sources is disabled. Recovery mode only has reboot now. There is no fastboot so adb on windows will not connect. My only idea is maybe a picture or video file that runs a script to allow USB debugging, or installs an apk(a file manager). Also I'll pay for one that will set my devices year back to 2011 or so. Please any help or advice. Maybe a windows program that will force connect adb somehow.
Click to expand...
Click to collapse
Hi , can you post video on YT in order to see what is actually happening your device.
Yes I do, I need to install a 3rd party app
Well, I need to install some apps on an APOS A8, but as it is in Release mode, it only accepts apps signed by the manufacturer, any attempt to install unsigned apps results in the error: INSTALL_FAILED_VERIFICATION_FAILURE
It runs an Android system called "Android 5.1.1 Secure OS", in MockUp mode it allows the installation of .apks normally, but I don't know how to put it in this mode. This "Secure OS" doesn't have a Developer Options installed, so enabling USB debugging or other function from this screen is impossible, and several common settings on Android phones are missing like enable unknown sources and backup and restore, apparently a service called "Titan " is responsible for blocking the installation of applications not signed by the manufacturer (they are signed with a program called LandiSignTool, which I didn't find anything), although there is no way to enable USB debugging, it is recognized by a modified version of ADB called "dlforU3.exe", through it it is possible to install signed applications, restart the POS in fastboot and EDL mode (its CPU is an MSM8909) and access a shell, however the system partitions are in read-only mode, and install applications with pm command is useless, only signed ones are installed. even though it goes into fastboot, I couldn't unlock its bootloader and I don't know what to do in EDL mode.
Can anyone out there help me?