AndroidmaxES USB Debug Enabler //Password usb debugging Andromax Es C46B2G import public class Main { public static void mainString[] args { //Ganti MEID dan IMEI warna merah di bawah sesuai di HP //MEID wajib 14 character. Jika MEID ada 15 character, cukup pakai 14 character pertama saja //Password USB debug terdiri dari 10 character hexadecimal String meid = "A1000012BC3456"; //tanda petik jangan dihapus String imei = "123456789012345"; //tanda petik jangan dihapus String pass = getPasswordmeid, imei; USB Debug agan adalah " + pass; } private static String getPasswordString s, String s1 { long l = 16.longValue; long l1 = 16.longValue; String s2 = new StringBuilder.appendl.append"".toString; String s3 = new StringBuilder.appendl1.append"".toString; String s4 = "C46B2G" ; // dari String s5 = "08apr2015" ; // getResources.getString0x7f090b35, sPreUATDate CRC32 crc32 = new CRC32; CRC32 crc32_1 = new CRC32; long l2 = << 8 ^ CRC32 crc32_2 = new CRC32; l2 ^= CRC32 crc32_3 = new CRC32; l2 ^= return } public static String stringReverseString s { return new StringBuffers.reverse.toString; } }

Based on OP's clarification done in the comments below Izzy's answer, I propose the following solution if one's device is locked out and ADB is not enabled under Settings. Note that this method is tested on Stock Android and Stock CM Android , both devices having custom Recovery ADB always enabled as default . If your Stock Recovery allows ADB shell access then you may also consider this solution. Instructions You should try your pattern-cracking software or whatsoever the genre it has from inside the Stock Recovery to see whether it works with the former's environment ADB shell available there or not. Since I would never try step 1., I would do the following For Jellybean Boot into Recovery and mount Data partition. Open a shell on PC and type adb pull /data/property/ ~/ Repace ~/ with home directory of your OS. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb. Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows mine is Linux so no issue here. In that case, I would suggest not using adb pull but doing adb shell echo 'mtp,adb' > /data/property/ You may verify that the echo command overwrote the file by using adb pull /data/property/ ~/ and seeing the file's content in some text editor. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled. For Lollipop JB users can also follow this method if the previous one didn't work for them. Boot into Recovery and mount Data partition. Repeat step 2 and 3 used in JB method. We need to tweak some parameters in Type adb pull /data/data/ ~/ Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX. In the global table, change the value for adb_enabled to 1 development_settings_enabled to 1 Check that verifier_verify_adb_installs is set to 1 in the global table. Check that as default, in the secure table adb_notify is 1 adb_port is -1 These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you. Save the changes in and copy it back into Android by typing adb shell rm /data/data/ exit adb push ~/ /data/data/ That delete rm command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind. Unmount Data and reboot into Android OS. ADB probably would be enabled. This is how it actually worked out when tested on my devices. Source Not really a source but got a hint from a comment under this answer.

. 157 134 142 157 125 367 224 74

password usb debugging andromax a