Some months ago, I rooted my Samsung Galaxy and installed SuperSU.
Stupidly, I'd had believed that the only thing that happens when you enter the pattern wrong too many times is that you have to wait a bit until you can try again, so when an acquantaince's little kid played around with it, I didn't mind, only to figure out I was locked out afterwards.
Usually, I have data and wifi turned off on my phone to preserve battery life, which was the case here as well, so I cannot unlock the phone with my google account because the phone has no internet access.
I tried the "call from different phone and try to get into settings" tricks, but no dice.
So I hope for one of these solutions (in order of preference):
Somehow be able to activate wifi or data so I can unlock the phone conventionally
Somehow be able to disable or deactivate the pattern lock at least long enough to activate wlan or data
Any other way that lets me keep my data
Any other way that makes my phone useable again
"su" in the adb shell makes me wait, then does nothing (probably SuperSU trying to ask for permission on the phone but invisible due to pattern lock).
-- Edit --
I am aware of this:
Solutions 1-3 require the phone to have internet, which it doesn't
adb -d shell
works, butsqlite3 data/data/com.android.providers.settings/databases/settings.db
producessqlite3: permission denied
andmount /data
producesUsage: mount [-r] [-w] [-o options] [-t type] device directory
.adb -d pull
doesn't work either:failed to copy 'data/data/com.android.providers.settings/databases/settings.db' to './settings.db': Permission denied
The link to the zip file solution is dead
Apparently the security hole trick with calling the phone to try getting into the menu does not work for my phone
The next phone solution doesn't work either
the GSMHosting Solution is discontinued and taken down
Yeah..., I don't think I'm able to get my hands on a forensics program...
su --help
in the adb shell hasSuperSU v2.45 (aosp:armeabi)
in the header andsu --version
says2.45:SUPERSU
) – joelproko Dec 07 '15 at 07:12adb -d root
to circumvent su not giving permissions to access sqlite3 or pull, but that saysadbd cannot run as root in production builds
. All solutions I've found for that error message seem to require your phone not to be locked. – joelproko Dec 07 '15 at 07:20