Database Info

[TUTORIAL]ByPass Pattern

Having protection and security on your Android device is one essential thing you should take into consideration, especially if there are people who tend to snoop around your device without your permission. The possibility of actually forgetting the pattern you’ve set to unlock your device is not that high, but it may happen. What’s worse, your friend may have messed around with your Android device and set a completely different unlock pattern, leaving you stumped when you try to unlock your device.
In situations like that, you could lose all hope and start bickering with the perpetrator (either your friend or yourself), not realizing that there is a way to go around that misfortune. Thanks to XDA Developers member m.sabra, an easy way to regain access to your locked device has been made for your perusal.
This guide will work on any Android device, rooted or not. It uses the Android Debug Bridge or ADB. If you are having a hard time recalling what ADB is or you don’t know what it is, check our article about how to install the Android SDK (Software Development Kit) and how to setup and use ADB (Android Debug Bridge).
In this guide, learn how to bypass the security pattern lock on your Android device.
Warning
The instructions in this guide reportedly work for both rooted and non-rooted devices. Root privileges, however, make this guide work in most cases. Several users have reported that the guide does not work in certain non-rooted devices.
The information in this guide is provided for instructional and educational purposes only. There is no guarantee that these instructions will work under your specific and unique circumstances.
Use these instructions at your own risk. We shall not hold any responsibility or liability for whatever happens to you or your device arising from your use of the info in this guide.
Read and understand the whole guide first before actually performing the instructions.
Requirements
Any Android device with USB Debugging enabled, preferably rooted; or, if not rooted, the device must be running a kernel that grants root access to the adb shell.
To enable USB Debugging on devices running Android 4.0 and up, go to Settings > Developer Options. Check the box beside the USB Debugging option.
For devices running on older versions of Android, go to Settings > Applications > Development. Check the box beside the USB Debugging option.
A computer with ADB installed
For help in setting up ADB on your computer, check our article about how to setup and use ADB (Android Debug Bridge)
Your device’s USB cable
Make sure your device’s battery is charged 75% or more to avoid interruptions during the process.
Backup all personal data on your phone to make sure you have a copy of your personal data (e.g., contacts, SMS, MMS, Internet settings, Wi-Fi passwords, and the like) in case the procedure in this guide erases such data.
For backup tips, check our guides on how to sync your data to the cloud and how to create local backups of your mobile data.
Instructions
Connect your device to your PC using the USB cable.
On your computer, open a terminal window (or command prompt on Windows-based machines).
Type in the following commands at the terminal or command prompt window. Press Enter after every line:
Code:
adb shell
The prompt should display a # rather than a $. Otherwise, enter su to switch to the root user.
Code:
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
exit
adb reboot
After your device has rebooted, enter the following commands at the terminal:
Code:
adb shell
The prompt should display a # rather than a $. Otherwise, enter su to switch to the root user.
Code:
rm /data/system/gesture.key
exit
adb reboot
Your device will reboot. After it reboots and asks for a security pattern, you can use any pattern and the device will still unlock.
Once you regain access to your device, make sure to change the system security settings to re-select another unlock pattern.
Congratulations! You have successfully bypassed the pattern unlock on your device. You don’t need to panic anymore because you now know that there is a way back into your phone after you’ve been locked out.
Click to expand...
Click to collapse
Credits
 @m.sabra

Another security bug highlighted and now shared with the world. Won't be using pattern unlock in future. ....
Sent from my GT-I9505 using Tapatalk 4 Beta

ardsar said:
Another security bug highlighted and now shared with the world. Won't be using pattern unlock in future. ....
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I use pattern lock and I am rooted. But I make sure the USB de-bugging mode under Developer options is never ticked (I only turn it on specifically when required and then switch it off). My phone is also encrypted using the stock settings options. These 2 things will render the above technique useless and make your phone a much secure object.

Still it can be cracked even if you are not rooted and USB Debugging is turned off, by Aroma File Manager

Build Bumber

Hey fellas I am and always been stock Rom I have rooted and changed a few things to my benefit then I noticed my build number was change. Can anyone tell me what effects this can have on my device. I been trying to use adb installer for mtk Droid tool but my device isn't recognized even though it is thru the adb server via adb devices.

Nothing changes enable dev options again and USB debugging also put phone in mtp mode

Galaxy S5 with broken screen, need help controlling it from PC

Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)

_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.

Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!

Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)

aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.

Bloatware Apps Removal via ADB

Hello Everyone,
I would like to learn how to remove bloatware Apps from my Android phone.
I have tried using "ADB commands" but for some reason my computer doesn't recognize/find my Android phone when I connect it to it.
Please help.
Thanks in advance

Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb

petiolarissean said:
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
Click to expand...
Click to collapse
Hello, and Thanks
I have done that exactly, but it still doesn't work.
And I can't figure out why is not working.
I have installed the Samsung driver, allowed the ADB function on my phone from "Developer Options" etc.

In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.

Only to have mentioned it:
So-called bloatware typically is housed in Android's locations /system and/or /system/priv--apps what only can get accessed by Android's root-user after successfully mounted as RW.

James_Watson said:
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Click to expand...
Click to collapse
Thanks for your help
I think I will buy a new USB cable and give it a try, hopefully it will work.
Have a nice day

Sorry late reply.I have like 5 different phone.Hard core modder.
This question help alot
Even though you csnt get adb working
Can you still move files from your phone to pc or computer.Or nothing ay all.Your answr will tell me your problem

Access personal data with broken screen and root/usb debugging enabled (but not authorized)

hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug

I found somewhere on xda that the problem could be solved by mounting/unmountind sdcard, but I have no ideea hoe to do that

damndaniel0 said:
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
Click to expand...
Click to collapse
There is a way to do it, but it costs money

@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com

xXx yYy said:
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
Click to expand...
Click to collapse
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)

iBowToAndroid said:
There is a way to do it, but it costs money
Click to expand...
Click to collapse
what would it be

damndaniel0 said:
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
Click to expand...
Click to collapse
Not in system but in custom recovery (which you do have).

Timmmmaaahh! said:
Not in system but in custom recovery (which you do have).
Click to expand...
Click to collapse
Honestly I did not try, but I don't remember the phone directory showing up in windows file explorer after connecting the phone in recovery mode, I'll try againg when I'm home and I'll let you know

anyway I checked and no, I cannot access phone files

In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>

xXx yYy said:
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
Click to expand...
Click to collapse
unfortunately the result of this operation is always "pull: building file list... 0 files pulled. 0 files skipped". I tried already to pull form /sdcard, /storage, /data. Am I getting the location wrong?