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

Top cmds that you need to know

There are servel cmds which we can use
But I post only top 10 cmds to help that ones who need
###############
If I make a mistake so please reply with your suggestions
And if you want a cmd in the list .submit your reply with cmd and features ( full detail as you know.).
########cmds###########
For a lot of us, the fact that we can plug our Android phone or tablet into our computer and interact with it is a big plus. Besides the times when we've broken something and need to fix it, there are plenty of reasons why an advanced Android user would want to talk to his or her device. To do that, you need to have a few tools and know a few commands. That's what we're going to talk about today. Granted, this won't be the end-all be-all discussion of adb commands, but there are 10 basic commands everyone should know if they plan to get down and dirty with the command line.
The tools are easy. If you're a Mac or Linux user, you'll want to install the SDK as explained at the Android developers site. It's not hard, and you don't have the whole driver mess that Windows users do. Follow the directions and get things set up while I talk to the Windows using folks for a minute.
If you're using Windows, things are easier and harder at the same time. The tools themselves are the easy part. Download this file. Open the zip file and you'll see a folder named android-tools. Drag that folder somewhere easy to get to. Next, visit the manufacturers page for your device and install the adb and fastboot drivers for Windows. You'll need this so that your computer can talk to your Android device. If you hit a snag, visit the forums and somebody is bound to be able to help you through it.
Now that we're all on the same page, enable USB debugging on your device (see your devices manual if you need help finding it, and remember it was hidden in Android 4.2), and plug it in to your computer. Now skip past the break and let's begin!
1. The adb devices command
The adb devices command is the most important one of the bunch, as it's what is used to make sure your computer and Android device are communicating. That's why we're covering it first.
If you're a pro at the operating system on your computer, you'll want to add the directory with the Android tools to your path. If you're not, no worries. Just start up your terminal or command console and point it at the folder with the tools in it. This will be the file you downloaded earlier if you use Windows, or the platform-tools folder in the fully installed Android SDK. Windows users have another easy shortcut here, and can simply Shift + right click on the folder itself to open a console in the right spot. Mac and Linux users need to navigate there once the terminal is open, or install an extension for your file manager to do the same right click magic that's in Windows by default.
Once you're sure that you are in the right folder, type "adb devices" (without the quotes) at the command prompt. If you get a serial number, you're good to go! If you don't, make sure you're in the right folder and that you have the device driver installed correctly if you're using Windows. And be sure you have USB debugging turned on!
Now that we have everything set up, let's look at a few more commands.
2. The adb push command
If you want to move a file onto your Android device programmatically, you want to use the adb push command. You'll need to know a few parameters, namely the full path of the file you're pushing, and the full path to where you want to put it. Let's practice by placing a short video (in my case it's a poorly done cover of the Rick James tune Superfreak) into the Movies folder on your device storage.
I copied the superfreak.mp4 file into the android-tools folder so I didn't need to type out a long path to my desktop. I suggest you do the same. I jumped back to the command line and typed "adb push superfreak.mp4 /sdcard/Movies/" and the file copied itself to my Nexus 4, right in the Movies folder. If I hadn't dropped the file into my tools folder, I would have had to specify the full path to it -- something like C:\Users\Jerry\Desktop\superfreak.mp4. Either way works, but it's always easier to just drop the file into your tools folder and save the typing.
3. The adb pull command
If adb push sends files to your Android device, it stands to reason the adb pull command gets them out. That's exactly what it does, and it works the same way as the adb push command did. You need to know both the path of the file you want to pull off, as well as the path you want it placed into. You can leave the destination path blank and it will drop the file into your tools folder to make things easy.
In this example, I did it the hard way so you can see what it looks like. The path of the file on the device is "/sdcard/Movies/superfreak.mp4" and I put it on my Windows 8 desktop at "C:\Users\Jerry\Desktop". Again, the easy way it to just let it drop into your tools folder by not giving a destination, which would have been "adb pull /sdcard/Movies/superfreak.mp4". Remember your forwards slash for the Android side, and you'll have no problems here.
5. The adb reboot-bootloader and adb reboot recovery commands
Not only can you reboot your device, you can specify that it reboots to the bootloader. This is awfully handy, as sometimes those button combos are touchy, and if you have a lot of devices you can never remember them all. Some devices (the LG Optimus Black comes to mind) don't even a way to boot to the bootloader without this command. And once again, being able to use this command in a script is priceless. Doing it is easy, just type "adb reboot-bootloader" and hit the enter key.
Most devices can also boot to the recovery directly with the "adb reboot recovery" (note there is no hyphen in this one) and some can't. It won't hurt anything to try, and if yours can't nothing will happen.
6. The fastboot devices command
When you're working in the bootloader, adb no longer works. You're not yet booted into Android, and the debugging tools aren't active to communicate with. We use the fastboot command in it's place.
Fastboot is probably the most powerful tool available, and many devices don't have it enabled. If you're does, you need to be sure things are communicating. That's where the fastboot devices command comes into play. At the prompt, just type in "fastboot devices" and you should see a serial number, just like the adb devices command we looked at earlier.
If things aren't working and you are using Windows, you likely have a driver issue. Hit those forums for the answer.
7. The fastboot oem unlock command
The holy grail of Android commands, fastboot oem unlock does one thing, and one thing only -- unlocks your Nexus device (or an HTC device using their official tool). If you're using a phone from a different manufacturer, you have a different method of unlocking things -- maybe with ODIN or .sbf files -- and this won't apply to you. We're including it because even if you don't need it, it's an important part of Android's openness. Google doesn't care what we do with phones or tablets that we've bought, and include this easy way to crack them open. That's something you usually don't see from any tech company, and a big part of the reason why many of us choose Android.
Using it is easy enough. Once you've used fastboot devices to make sure everything is communicating, just type "fastboot oem unlock" at the prompt and hit enter. Look at your device, read carefully, and choose wisely.
Protip: Using "fastboot oem unlock" will erase everything on your device
8. The adb shell command
The adb shell command confuses a lot of folks. There are two ways to use it, one where you send a command to the device to run in its own command line shell, and one where you actually enter the device's command shell from your terminal. In the image above, I'm inside the device shell, listing the flies and folders on the device. Getting there is easy enough, just type "adb shell" and enter. Once inside, you can escalate yourself to root if you need to. I'll warn you, unless you're familiar with an ash or bash shell, you need to be careful here -- especially if you're root. Things can turn south quickly if you're not careful. If you're not familiar, ash and bash are command shells that a lot of folks use on their Linux or Mac computers. It's nothing like DOS.
The other method of using the adb shell command is in conjunction with one of those Ash commands your Android device can run. You'll often use it for more advanced tasks like changing permissions of files or folders, or running a script. Using it is easy -- "adb shell <command>". An example would be changing permissions on a file like so: "adb shell chmod 666 /data/somefile". As mentioned, be very careful running direct commands using these methods.
9. The adb install command
While adb push can copy files to our Android devices, adb install can actually install .apk files. Using it is similar to use the push command, because we need to provide the path to the file we're installing. That means it's always easier to just drop the app you're installing into your tools folder. Once you've got that path, you tell your device to sideload it like this: "adb install TheAppName.apk".
If you're updating an app, you use the -r switch: "adb install -r TheAppName.apk". There is also a -s switch which tries to install on the SD card if your ROM supports it, and the -l switch will forward lock the app (install it to /data/app-private). there are also some very advanced encryption switches, but those are best left for another article.
And finally, you can uninstall apps by their package name with "adb uninstall TheAppName.apk". Uninstall has a switch, too. The -k switch will uninstall the app but leave all the app data and cache in place.
10. The adb logcat command
The adb logcat command is one of the most useful commands for some folks, but just prints a bunch of gibberish unless you understand what you're seeing. It returns the events written to the various logs in the running Android system, providing invaluable information for app developers and system debuggers. Most of us will only run this one when asked by one of those developers, but it's very important that we know how to use it correctly.
To see the log output on your computer screen, just type "adb logcat" and hit enter. Things can scroll by pretty fast, and chances are you won't find what you're looking for. There are two ways to handle this one -- filters, or text output.
You also have to specify the cmds properly.
Hope it help you .
Like my work hit thanks button.
$$$$$$$$$$$$$$$$$$$$$$$$
Any suggestions most welcome.
$$$$$$$$$$$$$$$$$$$$$$$$$

[APP]MTK ADB, how to use ADB on your device

If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
https://play.google.com/store/apps/details?id=fme.adb
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com

No need for multiple threads on same topic,
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
I'll close this one.
Darth
Forum Moderator

[APP]MTK ADB, Use ADB directly on your device

If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com

LordFME said:
If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
https://play.google.com/store/apps/details?id=fme.adb
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com
Click to expand...
Click to collapse
This is useful. Thanks :good:

Glad you like it

No need for multiple threads on same topic,
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
I'll close this one.
Darth
Forum Moderator

Using Android device to run adb and fastboot commands

To make this a short as possible I successfully unlocked my Motorola G7 power using an Android device rather than a PC I need help rooting my G7 power with magisk using my designated Android device rather than a PC

ADB⚡OTG - Android Debug Bridge - Apps on Google Play
⚡ Run ADB commands without a computer [No Need ROOT] ⚡
play.google.com

Thank you I appreciate your reply but I use another application for this purpose bugjaeger premium

@Sativa33
Either in magisk manager from device or you can also get the magisk module from Osm0sis' Odds and Ends- (multiple devices scripts) XDA thread. If you go there https://forum.xda-developers.com/t/...-and-ends-multiple-devices-platforms.2239421/
Scroll down halfway oe maybe 2/3 of fge way and click his "adb and fastboot " magisk module and install via magisk manager. Then use termux terminal and type "su" (enter) for root and place files you wish to install in ter
Termux's directory which it will show you after you tape sy and push enter on the screen in terminal just after you grant it root. Then you use an otg cable and connect two Android devices together throw files in Termux's directory and send fastboot and adb commands whenever. I've used this method on two phones so unlock my bootloader ad well. The only prerequisite being you need another (2nd) Android device that is bporloader unlocked and rooted so you can send commands to other device and an OTG cable which are $3-5 USD online. Sure does come in handy when you need it through. Like years ago when my laptop was stollen!! Life saver FR!!!

After reading it that sounds like a reasonable option. But wouldn't it be easier just to download the bugjaeger premium app on a second Android device. And that's basically all you need and a double ended USB c cord. No need for all this other programs or downloades . It's basically running fast boot commands it's purest form one Android device talking to the other using the same language no need to download packets drivers nothing because you're already in the Android shell talking to another Android