Fastboot oem unlock invalid command

broken image
broken image

So I said to myself, well maybe the Linux fastboot is busted, or doesn't do large blocks or something, so I downloaded the Windows Android SDK and tried to install it in a virtual machine. So I figured the factory cable must be the problem (even though I could see the device) and I ordered a high quality one from Monoprice. Both the X4 and Z2 behave exactly this way no matter which cable or how I wave my arms.

(bootloader) 'get_unlock_datas' is not a supported oem command

broken image

 

PreviousNext
Cookie Use
We use cookies to improve browsing experience, security, and data collection. By accepting, you agree to the use of cookies for advertising and analytics. You can change your cookie settings at any time. Learn More
Accept all
Settings
Decline All
Cookie Settings
Necessary Cookies
These cookies enable core functionality such as security, network management, and accessibility. These cookies can’t be switched off.
Analytics Cookies
These cookies help us better understand how visitors interact with our website and help us discover errors.
Preferences Cookies
These cookies allow the website to remember choices you've made to provide enhanced functionality and personalization.
Save