Database Develop

Updated!!(10/20/2007) UPGRADE YOUR PHONE WITH WINDOWS VISTA!!! PROVEN METHOD!

Windows VISTA Config guide
NOTE: Vista Rom update Utility(attached at the end of post #4) is required when Flashing Roms on Windows Vista.
To Download This Guide as a PDF, click HERE
To Send This Guide as an E-Mail, Click HERE
To Print This Guide, Click HERE​
Written by MrVanx <<ALL CREDIT GOES TO THIS MAN. This is a direct Copy of the original document.
Wednesday, 18 April 2007
(Thanks to invictive for the screenshots and testing) << I LINKED TO HIS SCREENSHOTS
UPDATE: Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first.
​One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista x32
Drivers for Windows Vista x64
NOTE:: If you are using a x64 bit computer, you will need to boot up with driver signing enforcement turned off. To accomplish this, you will need to press F8 during boot up. If you do not do this, the 64 bit drivers will not install properly and this tutorial will not be of any use to you.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.
​
​ ​ Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon.​ ​
​ ​ In the connection settings menu untick "allow USB connections" then press OK.​ ​ Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.​ ​ ​
​ ​ Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.​ ​
​ ​

Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".​ ​ This will bring up the properties of the currently connected device (the hermes in bootloader).​ ​
​ ​ Go to the "Driver" tab and click "Update Driver".​ ​
​ ​ Click "Browse My Computer for Driver Software".​ ​
​ ​ Select "Let me pick from a list...."​ ​
​ ​ Click the "Have Disk" button.​

​ ​ Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.​ ​
​ ​ Vista x32 users select the file "wceusbsh.inf"​ Vista x64 users select the file "wceusbshx64.inf"​ ​ Then click Open.​ ​
​ ​ click next and the driver will be installed (wait a moment).​ ​ ​

​ ​ Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
Click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which Vista uses when the device is in bootloader mode. ​
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Windows Mobile Based Device.​

Thanks!
I saw this same article somewhere else and already did this
Thanks for posting this here though! Also, it helps to use the windows mobile device center 6.1 update. It works both on my desktop Vista Ultimate computer and my mom's home premium laptop
Also, a little sidenote, if you want windows mobile device center to display your own phone as the image instead of the standard PDA/PPC Phone/Smartphone image when you sync follow these steps:
Disable USB connections in Windows Mobile Device Center
Uninstall the drivers for your device from device manager
Save the image you want to use as an icon file called sync.ico
Save the icon to the windows folder on your ppc
Disconnect your PPC and enable USB connections again
Wait for the computer to reinstall the device driver and it will sync with the new icon
Sorry, I don't remember who first suggested this. I take NO credit for this whatsoever.

Woooooooooow !!!
dharvey4651
Awesome!
Must say,cudn't have been better than this,commendable job.

zabardast_1 said:
dharvey4651
Awesome!
Must say,cudn't have been better than this,commendable job.
Click to expand...
Click to collapse
Thanks. It took me a while to type up but as long as it benefits the community, it was worth it.

thanks you very much for the write up

great bro, i will add it to TNT notes

works nice, but the Vista update tool is out of date. Cant flash my Wizard with it.

Doesn't work with G4.

neonkoala said:
Doesn't work with G4.
Click to expand...
Click to collapse
Have you tried my tutorial on how to dual boot your computer so that it has Vista and XP on it? I started having problems with my phone not flashing properly after like 2 weeks. I installed a few Windows updates and then the drivers stopped working so I set up my computer to have Vista and XP on it so that I can use Vista on a daily basis and only use XP when I'm working on my phone.

neonkoala said:
Doesn't work with G4.
Click to expand...
Click to collapse
Anybody have found a Vista Update Utility for G4?

Thanks!
This got my G4 to finally stop giving me connection errors in the boot loader!
Now I can finally get my G4 unbricked
I used the shelltool successfully in Vista 32bit, but the world isn't liking me for flashing in 64bit so far... Either way, thanks!
Also, you might want to update the tutorial to tell 64bit users to boot up with driver signing enforcement turned off (Press F8 on boot up) else the 64bit drivers won't take.

frazell said:
Thanks!
This got my G4 to finally stop giving me connection errors in the boot loader!
Now I can finally get my G4 unbricked
I used the shelltool successfully in Vista 32bit, but the world isn't liking me for flashing in 64bit so far... Either way, thanks!
Also, you might want to update the tutorial to tell 64bit users to boot up with driver signing enforcement turned off (Press F8 on boot up) else the 64bit drivers won't take.
Click to expand...
Click to collapse
Thank you very much for that piece of input. I will definitely update the tutorial as per your advice to better assist 64bit users.
Thanks again, Dan.

The Vista RUU doesn't crash as I was used to, but it doesn't run either (with a prophet that is) it 's complaining about "beeing outdated".
Are there any solutions yet known for this inconvenience? Thanks in advance!

Vista RUU
Is there a newer version of the ROM update utility? The one posted above doesn't run, but, rather, just complains that it's out of date!
The driver method detailed above works great (with the caveat for x64 users that they have to disable the driver signing restriction), but unfortunately I'm still no further along because I can't seem to find an RUU that will work!
If anyone knows of one that really works on Vista, please pass it one. (I've searched through all these postings, but none seem to work!)
Thanks much for the detailed driver instructions!

Thanks for the Vista instructions, helps me out! but I ran into a problem degradeing to unlock my CID. Im not sure its me,software,and/or myphone but I got a invalid Vender ID error 294. I am using a wizard 8125 for this and using Vista. This is my first time, but im loaded on knowlaege unless i missed somthing. Thanks in advance.

Still no luck with Vista!
Has anyone found a complete method to flash on Vista? As posted above, the RUU included with this thread doesn't work. It gets most of the way through and then, just before starting to flash, gives a "This utility is out of date" error and exits.
Again, the driver instructions given in this thread are sound, but without a working RUU they only give you half of the solution for flashing on Vista.
I have successfully flashed using Shelltool, but it works sporadically at best.
Does anyone have a start to finish solution?

I followed the instructions given in this forum and they seemed to work perfectly for me.
here is my 2 cents though i had initially flashed my device using the origional t-mobile rom (SPL/IPL 3.08 radio 2.69) and it worked without any problems. It was only when i tried flashing with a cooked rom that it gave me problems.
Here are the RUU file from that rom and hopefully someone can figure out why it worked

Please Help!

Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:

TomCarter21 said:
Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
Click to expand...
Click to collapse
Do the "factory reset". Erasing all data of course...

To try factory reset from recovery menu
1. turn off the phone
2. press vol down + power
3. waiting vibrate 2 times and release button
4. choose wipe data/factory reset
after that re-root again
don't forget setting debugging mode
before root.
Sent from my LG-P880 using xda app-developers app

First step would be to disconnect any other Android device.
Second one, put the phone to Airplane mode, you can do with some patience even with the SystemBackup.apk installed. Switch USB mode to "charging only".
If that doesn't help, you can still do a reset.

Do you have the Android SDK installed and are you running the root.bat as an Administrator?

XperiaPlayer said:
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
Click to expand...
Click to collapse
Sorry @XperiaPlayer but, I don't have the Android SDK installed, and my root goes perfect...
You're sure that matters?
Regards

Shift + right click the folder where the root.bat is located and type adb devices (or adb.exe devices) and paste the output here.

[HELP] I'm lost in the adb world

So my htc one has been a piece of a useless aluminum for the past 4 months when I lost access to recovery.
I have a windows 8.1 computer and no USB 3.0
My htc one does not boot it stays stuck on the htc logo until battery drains. I used to have a recovery image that I was able to access but now every time I try to reboot to recovery it snaps out of it and it reboots again. I CAN go to the bootloader but my computer won't communicate with the device so I can flash a new recovery.
Please ask me if I was unclear about anything but most of all, I need your professional advise please.
I want my htc to come back to life

Ninlour said:
So my htc one has been a piece of a useless aluminum for the past 4 months when I lost access to recovery.
I have a windows 8.1 computer and no USB 3.0
My htc one does not boot it stays stuck on the htc logo until battery drains. I used to have a recovery image that I was able to access but now every time I try to reboot to recovery it snaps out of it and it reboots again. I CAN go to the bootloader but my computer won't communicate with the device so I can flash a new recovery.
Please ask me if I was unclear about anything but most of all, I need your professional advise please.
I want my htc to come back to life
Click to expand...
Click to collapse
I used the Driver Hack here .. i have no problems with adb/fastboot on windows 8.1
here's the file and instructions
http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
HTML Code:
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
you may also need these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe

Oh dear lord IT WORKED!! I can't thank you enough !!!

Ninlour said:
Oh dear lord IT WORKED!! I can't thank you enough !!!
Click to expand...
Click to collapse
Yes sir .. your welcome

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?

Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.

Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!

OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse

mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!

Unlook Bootloader Asus Zenfone Max M2 (Unofficial)

Disclaimer :​
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER MAX M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max M2
Windows / Linux
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to System > Developer options and enable USB debugging ( If you had already enabled USB debugging, "revoke USB debugging authorizations" and lets start new)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers
- Go to "unlock" folder
- Open an Elevated command promt there and type :
Code:
adb devices
( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK and again enter :
Code:
adb devices
(Device should be listed)
Code:
adb reboot bootloader
(Device will now enter fastboot )
Code:
fastboot devices
(Device should be listed )
Now execute unlock.cmd (windows) or unlock.sh (linux)
Device will show unlooked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked
You will receive OTA as usual
Credits
 @Sudeep Duhoon 
 @Shivam Kumar Jha
 @Rk585
 @#ArtFuL
Downloads:
Note- This tool is not developed by me. I had taken this from Asus Zenfone Maz M2 pro and tested with my phone. Its fully working. Go ahead and unlock your bootloader.

kumar87 said:
Disclaimer :
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER MAX M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max M2
Windows / Linux
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to System > Developer options and enable USB debugging ( If you had already enabled USB debugging, "revoke USB debugging authorizations" and lets start new)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers
- Go to "unlock" folder
- Open an Elevated command promt there and type :
Code:
adb devices
( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK and again enter :
Code:
adb devices
(Device should be listed)
Code:
adb reboot bootloader
(Device will now enter fastboot )
Code:
fastboot devices
(Device should be listed )
Now execute unlock.cmd (windows) or unlock.sh (linux)
Device will show unlooked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked
You will receive OTA as usual
Credits
@Sudeep Duhoon
@Shivam Kumar Jha
@Rk585
@#ArtFuL
Downloads:
Note- This tool is not developed by me. I had taken this from Asus Zenfone Maz M2 pro and tested with my phone. Its fully working. Go ahead and unlock your bootloader.
Click to expand...
Click to collapse
There is already unlock tool for max m2 on the Asus website. Why go through so much hassle?

somi007 said:
There is already unlock tool for max m2 on the Asus website. Why go through so much hassle?
Click to expand...
Click to collapse
First that official app is not installed and if you are able to install that stop working when you click on unlock button that means that app is of no use.

somi007 said:
There is already unlock tool for max m2 on the Asus website. Why go through so much hassle?
Click to expand...
Click to collapse
You would never be able to relock bootloader, receive ota or get warranty if you unlock by the tool provided by Asus

Camera 2 API working? After unlocked bootloader
#ArtFuL said:
You would never be able to relock bootloader, receive ota or get warranty if you unlock by the tool provided by Asus
Click to expand...
Click to collapse
After unlocking boatloader
Camera 2 API working or not because I really want to install Gcam night sight vala

nirmalp982 said:
After unlocking boatloader
Camera 2 API working or not because I really want to install Gcam night sight vala
Click to expand...
Click to collapse
Yes, infact you can enable ai stickers after rooting

waiting for video tutorial

Sudarshan11331 said:
waiting for video tutorial
Click to expand...
Click to collapse
You can watch the video tutorial of pro m2. OP blindly copy pasted the pro m2 post, so there isn't any difference in procedure

Has anyone tested this on max m2. Does this work ?

arshad522 said:
Has anyone tested this on max m2. Does this work ?
Click to expand...
Click to collapse
Yess ,it worked

arshad522 said:
Has anyone tested this on max m2. Does this work ?
Click to expand...
Click to collapse
Yes here YouTube video

Maybe Now there are chance that some Custom ROM appear for my device.

DEvilAnimeGuy said:
Maybe Now there are chance that some Custom ROM appear for my device.
Click to expand...
Click to collapse
you are working on it ?

Is it worked on official pie rom?

Locking the Bootloader
kumar87 said:
Disclaimer :​
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
If you point the finger at me for messing up your device, I will laugh at you. Hard. A lot
Warranty will be VOID
UNLOCK BOOTLOADER MAX M2 (Unofficial)
<Device will be formatted, so keep a backup >
Requirements :
Asus Zenfone Max M2
Windows / Linux
Instructions :
//unlocking
Phone:
- Go to Setting > System > About Phone and tap on the build number until developer option appears
- Go back to System > Developer options and enable USB debugging ( If you had already enabled USB debugging, "revoke USB debugging authorizations" and lets start new)
Windows:
- Download "unlocker" and extract the files
- Go to "adb + asus drivers" folder and install ADB and necessary drivers
- Go to "unlock" folder
- Open an Elevated command promt there and type :
Code:
adb devices
( Allow usb debugging box will appear, check "always allow debugging from this computer" and click OK and again enter :
Code:
adb devices
(Device should be listed)
Code:
adb reboot bootloader
(Device will now enter fastboot )
Code:
fastboot devices
(Device should be listed )
Now execute unlock.cmd (windows) or unlock.sh (linux)
Device will show unlooked bootloader warning, encrypt and reboot
Thats it, Bootloader is unlocked
You will receive OTA as usual
Credits
@Sudeep Duhoon
@Shivam Kumar Jha
@Rk585
@#ArtFuL
Downloads:
Note- This tool is not developed by me. I had taken this from Asus Zenfone Maz M2 pro and tested with my phone. Its fully working. Go ahead and unlock your bootloader.
Click to expand...
Click to collapse
Is it possible to lock the bootloader back if I want to redeem my warranty?

arshad522 said:
Has anyone tested this on max m2. Does this work ?
Click to expand...
Click to collapse
Yes I have tried in my max m2 and successfully unlocked my bootloader.

i am on android 10 beta update ... when i am trying to run the unlock file.. it is not running plzz help

hello admin
whenever i run the unlock.cmd command. my mobile screen shows a very tiny "any key to shutdown" notification. how can i solve it. please give your insights. thanks in advance

Any one know here how to lock it?

nitishdk said:
Any one know here how to lock it?
Click to expand...
Click to collapse
I have same problem bro i wouldn't able to relock my asus max m2.please help us who knows.