I am trying to unlock a USB debugging disabled device from ADB.
The device is recognized by ADB only when it is connected through USB in recovery mode (when the device is turned on, it is not recognized as USB debugging is off). ./adb devices
is returning the device serial and identifying that it is in sideload mode.
Any further command like ./adb shell
is returning "error:closed".
What can I do in this sideload mode? Any way to enable USB debugging while the device is recognized to be in sideload status?
I have tried some commands to unlock a different USB debugging enabled device I have at home and the commands work on that device.
So for now my first roadblock is enabling USB debugging in this locked device or something to that effect. Please give me some advice in this regard.
Any other advice on unlocking the device without losing data would be very helpful too.
Thank you.
More details: I am trying to unlock an Android phone that has stopped taking the correct password after a auto-restart. I know the PIN, I have not changed it in a long while. The phone stopped accepting the PIN after the sudden auto-restart so I am just clueless what may work. Hard reset is not an option for this device without backing up the data so willing to try anything that may help.
adb
. Sideload mode is used in recovery to flash ROM zips. If you want to useadb
commands you need a custom recovery like TWRP (which requires an unlocked bootloader). Both (unlocked bootloader andadb
sideload mode in recovery) has nothing to do with ADB in ROM (enabled through Developer Options). So please clarify what you exactly want to achieve (the actual problem other than enabling ADB). – Irfan Latif Mar 04 '20 at 12:49