Database Info

Pattern Lock: "locked out permanently"-fix

hi there
maybe someone had the problem being locked out (not temporarily!)
my complete solution now is:
Code:
adb -d shell
sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=0 where name='lock_pattern_autolock';
sqlite> update secure set value=2726148 where name='lockscreen.lockoutattemptdeadline';
sqlite> delete from secure where name='lockscreen.lockedoutpermanently';
sqlite> .exit
# exit
detailed step-by-step instruction on demand.
troubleshooting:
if you get an "sqlite3 not found" error (like me) you can use titanium backup's sqlite3 (only pro? can somebody confirm?) by replacing "sqlite3" by "/data/data/com.keramidas.TitaniumBackup/files/sqlite3" in the 2nd line of code.
disabled usb debugging:
boot into recovery (clockworkmod in my case) and plugin the phone
my solution is a bit different from haykuro's one here -> G1 General > Pattern Lock.. Defeated! as you can see below:
the key 'lock_pattern_autolock' has been moved from system to secure
added some more sql (maybe you aren't forced to execute them but i recommend it)
regards
auipga

[Q] 4.3 update (touchwiz) - no codes work anymore - how do I QPST now?

original firmware had a number of hidden codes that you put into dialer and it does stuff. None of them work anymore. Particularly the ones I care about are:
*#22745927 to enable hidden menu.
*#7284# to switch the UART and USB from PDA to MODEM (so that I could program PRL with QPST)
*#0*# hardware test
Are there alternatives?..

No.
Sent from my Last Ever Samsung Device.

0331 said:
No.
Sent from my Last Ever Samsung Device.
Click to expand...
Click to collapse
On the older firmwares there was an IOTHiddenMenu activity which you could invoke using
Code:
am start com.android.hiddenmenu/com.android.hiddenmenu.IOTHiddenMenu
command, but that doesn't work on 4.3
I know in AOSP there was a notion to turn into QPST mode by writing to kernel pseudo-files...
Engineers got to somehow be able to reprogram these phones, there's no way Samsung disabled this completely

I dug out some old scripts for AOSP, which seem to work. Device was accessible in QPST-programmable mode after them:
Code:
#/system/bin/sh
# sets DIAG mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo diag,acm,adb > /sys/class/android_usb/android0/functions
cat /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
setprop sys.usb.state sys.usb.config
and to go back to MTP:
Code:
#/system/bin/sh
# sets default USB mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo mtp,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
setprop sys.usb.state sys.usb.config

[Q] Why can't I disable captive portal detection with ADB?

I issued the following command in terminal to disable captive portal detection.
"settings put global captive_portal_detection_enabled 0"
But it comes with the following failure message
"The term 'settings' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ settings put global captive_portal_detection_enabled 0
+ ~~~~~~~~
+CategoryInfo : ObjectNotFound: (settings:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"
Note that my phone has USB debugging enabled. When I type "ADB devices" it shows my device as connected.

You need to bring up shell first. Like:
> adb shell
> settings put global captive_portal_detection_enabled 0

Open diag failed

I it possible to enter the diag mode of the Pocophone without rooting?
*#*#717717#*#* shows a toast notification: "open diag failed".

coolboy744 said:
I it possible to enter the diag mode of the Pocophone without rooting?
*#*#717717#*#* shows a toast notification: "open diag failed".
Click to expand...
Click to collapse
Are you talking about CIT mode (engineering mode in Android)? If so: https://c.mi.com/thread-2188758-1-0.html

coolboy744 said:
I it possible to enter the diag mode of the Pocophone without rooting?
*#*#717717#*#* shows a toast notification: "open diag failed".
Click to expand...
Click to collapse
No. As of MIUI 10, Qualcomm HS-USB Diag 901D was blocked through that method and won't work without root access for obvious security reasons. use the Terminal or adb method with the command:
Code:
setprop sys.usb.config diag,adb
To disable it, use command:
Code:
setprop sys.usb.config mtp,adb

Alin45 said:
Are you talking about CIT mode (engineering mode in Android)? If so: https://c.mi.com/thread-2188758-1-0.html
Click to expand...
Click to collapse
No i am talking about How to Qualcomm Diagnostic Mode (Diag Port)

Slim K said:
No. As of MIUI 10, Qualcomm HS-USB Diag 901D was blocked through that method and won't work without root access for obvious security reasons. use the Terminal or adb method with the command:
Code:
setprop sys.usb.config diag,adb
To disable it, use command:
Code:
setprop sys.usb.config mtp,adb
Click to expand...
Click to collapse
so there is no option without root. thanks for reply.

>adb shell
sweet:/ $ setprop sys.usb.config diag,adb
Failed to set property 'sys.usb.config' to 'diag,adb'.
See dmesg for error reason.

For poco you need to enter two commands:
adb shell
su
setprop persist.vendor.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb

Set MTP as default for USB on Android 7.1.2 / LineageOS 14.1 on SM-T280

Hey,
I'm running LineageOS 14.1 (Android 7.1.2) on an SM-T280. It's also rooted.
Whenever I reboot and connect USB, it only enables adb and charges. I want it to enable adb and mtp by default.
I know about the setting in the developer options, but this also is not persistent.
How do I enable MTP by default?

In Android's system file build.prop add MTP as default USB-mode
Code:
persist.sys.usb.config=mtp,adb

xXx yYy said:
In Android's system file build.prop add MTP as default USB-mode
Code:
persist.sys.usb.config=mtp,adb
Click to expand...
Click to collapse
Tried, does not work. When I reboot I get this:
Code:
gtexswifi:/ # cat /system/build.prop | grep usb
persist.sys.usb.config=mtp,adb
sys.usb.gser.count=8
sys.usb.config=mtp,adb
persist.sys.usb.config=mtp,adb
sys.usb.configfs=1
gtexswifi:/ # getprop | grep usb
[persist.sys.usb.config]: [adb]
[sys.usb.config]: [adb]
[sys.usb.configfs]: [0]
[sys.usb.ffs.ready]: [1]
[sys.usb.gser.count]: [8]
[sys.usb.state]: [adb]
gtexswifi:/ # ls /data/property/ | grep usb
persist.sys.usb.config
gtexswifi:/ # cat /data/property/persist.sys.usb.config
adb
Of course I also tried setprop persist.sys.usb.config "mtp,adb" which modifies /data/property/persist.sys.usb.config but this is reset on reboot.
I've found many websites that say it is simply not possible on Nougat :/
I also found https://forum.xda-developers.com/t/app-root-r-3-3-marshmallow-mtp-enabler.3263467/ but I don't want to install an app :/ I'm curious how it does it.
When I setprop sys.usb.config "mtp,adb" while the device is running, usb disconnects and reconnects, but there is still no MTP available.

Also tried
Bash:
echo 0 > /sys/class/android_usb/android0/enable
echo mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
The device disconnects and reconnects from USB but only with adb enabled and
Code:
gtexswifi:/ # cat /sys/class/android_usb/android0/functions
ffs
afterwards
Source: https://books.google.de/books?id=0cuQAwAAQBAJ&pg=PA64&lpg=PA64&dq="android_usb/android0/enable"+mtp

Okay, I wen't through the effort to recompile the kernel and patch the init ramdisks /default.prop with
Code:
persist.sys.usb.config=adb,mtp
sys.usb.config=adb,mtp
Didn't help...
Any other ideas?