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

[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

MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com

Bump

Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10

Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10

When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2

LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.

Pixel 2 stuck on G loading screen

My Pixel 2 took a dive on a few days ago and I've been trying to get it operational ever since. The things i've tried are
1. Waiting it out
2. Force restart
3. Force restart more than 7 times in a row to get it to revert back to another version
4. ADB sideload the proper system image to get it to begin working
But none of these has worked. Right now all I'm really concerned about is trying to salvage my data and create a backup file for all my apps and data but when I try to do the backup through the adb using 'adb backup -apk -shared -all -system -f Direction:\filename.ab' it gives me an error that says "adb: unable to connect for backup: closed" And there's no other way around it.
Side note, I've only been able to get my phone to show up on the adb devices list when i say to do a recovery through adb, otherwise it simply doesn't show up there and only shows up under fastboot devices.
I would love some help here, anything you all can do to point me in the right direction would be fantastic.

@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.

jwoegerbauer said:
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
Click to expand...
Click to collapse
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?

Otonirez said:
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Click to expand...
Click to collapse
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%

jwoegerbauer said:
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
Click to expand...
Click to collapse
I really wish I would have seen this a few minutes ago because I did a factory reset on my phone like right before i saw this. I doubt there's anything I can do at this point to reclaim my stuff

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