Hi! I want to unlock bootloader on my Moto E7 plus and i have a problem. I install official sdk tool from android website and add path to system variables etc. I open CMD in platform tools and connect my phone to pc, activate USB debugging and OEM unlock in developer tools options, in the next step i type commands in cmd console - adb reboot bootloader (works), checked again it was my device still connected - adb devices (still visible), but now i'm stuck af because if i type "fastboot oem get_unlock_data" console responds to me (remote: unknown command).
Did i lost this battle forever, guys?
Related
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Vibestarter said:
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Click to expand...
Click to collapse
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
fastboot oem unlock Failed
The-Immortal said:
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
Click to expand...
Click to collapse
Hello, I tried your command suggestions to unlock the bootloader and they failed. The command 'fastboot oem-info' does not return anything and 'fastboot oem unlock' returns RESULT: FAIL (unkown OEM command) on the tablet and in the cmd window. Thanks for the suggested attempt nonetheless.
Still having this problem
fastboot oem unlock fails on the TF103C and it says RESULT:FAIL(unknown OEM command). It would be great if Asus could release a tf103c_unlock.apk utility like they have for other Asus tablets (for instance the TF701T has tf701_unlock.apk which works).
Asus, please help!
No bootloader interface is found !
Hi experts.
ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.
Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.
According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.
How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?
Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.
hey please help i am unable to unlock boot loader of my coolpad note 5 which has snapdragon 617 soc, no unlock code type help or instruction on official forum and no help there because all command returns as unknown command ,
i tried many command except these two command all return unknown command ,
fastboot devices works shows device no
fast getvar all works showing something
i checked all driver installed properly and pc showing it on device manager as fastboot device even fastboot recognized it as a fastboot devices, also i allow oem unlocking on developer setting and enabled usb debugging
after this all command like
fastboot oem unlock
fastboot oem unlock-go
fastboot boot
fastboot reboot
fastboot flashing unlock
fastboot oem device-info
fastboot flash
all and more i found i net returns unknown command remote
i tried with vendor id but no result
i checked fastboot getvar all returns its kernal as lk
so do little kernel has problem , i have its firmware package but not found aboot.c
please help its unrooted
attached error command screenshot in zip
I am facing same issues
Sent from my Andromax A16C3H using Tapatalk
I am trying to unlock the bootloader for my device (it's a cheap Chinese phone) and then root using Magisk. The first problem is that OEM Unlock option is not available in developer options, so I got no choice other than try unlocking using fastboot. Now the second problem is that fastboot doesn't show anything at all. Normally there is a Fastboot written at the top left corner of the device but in my case there is no output but the blank screen, and I do verify that my device is in fastboot mode because when I do fastboot devices, it show's the output:
Code:
C:\Users\Mujtaba>adb devices
List of devices attached
Y3123A0310Q0100020953 device
C:\Users\Mujtaba>adb reboot bootloader
C:\Users\Mujtaba>fastboot devices
Y3123A0310Q01000209 fastboot
Since fastboot was responding (partially), I tried to unlock the bootloader using different commands but each time I get read/write failed error.
Code:
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.011s
C:\Users\Mujtaba>fastboot oem unlock
...
FAILED (status read failed (Too many links))
finished. total time: 80.886s
Alas, I got the same results with fastboot oem unlock-go and fastboot flashing unlock as fastboot is not accepting (at least I think) any command except fastboot devices.
I read the official guide and there I found that:
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the unlock_ability to 1).
Click to expand...
Click to collapse
My device supports unlocking bootloader because I've checked the build.prop file using adb shell getprop and it includes the properties stated below:
The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device suppports flashing unlock, set ro.oem_unlock_supported to 1. If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0. If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or 0 if unlocked.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
Click to expand...
Click to collapse
Code:
C:\Users\Mujtaba>adb shell getprop
[ro.oem_unlock_supported]: [1]
[ro.boot.verifiedbootstate]: [green]
[ro.boot.flash.locked]: [1]
[sys.oem_unlock_allowed]: [0]
.
.
Someone on reddit did this to find the OEM unlock state, mine of course returned 0 as you can see above.
Code:
adb shell getprop sys.oem_unlock_allowed
Device Specs:
CPU: ARM Cortex-A-7 @ 1.20 Ghz
GPU: Mali-400 MP
Board: sp7731cea (Unisoc aka Spreadtrum)
Build: Q Infinity C_MP_26_01
Treble: NA
Seamless update (A/B): NA
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
jwoegerbauer said:
Your phone is based on Spreadtrum chipset. Means such a device has its own mechanism to unlock the bootloader.
Click to expand...
Click to collapse
Yes I know that and I already found a method but again it uses oem get_identifier_token to get Identifier token and when I do that fastboot returns nothing.
There are other methods as well, like getting a PAC file for your device then extracting boot.img from it, patching it with magisk manager and then flashing that single partition (in this case BOOT partition) using SPD Research Tool but it gives me error as well.
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
jwoegerbauer said:
Install the matching Android USB Driver if not done yet. Having installed common ADB / Fastboot drivers isn't enough.
Additional advice: Replace Help in this thread's title by QMobile QInfinity C
Click to expand...
Click to collapse
I have installed SPD drivers and Google USB drivers however the problem is not with drivers because I can use the following commands without an issue:
Code:
fastboot devices
fastboot reboot
fastboot reboot bootloader
The problem occurs when using:
Code:
fastboot oem unlock
fastboot flashing unlock
Google's USB driver is only suitable to Google devices like the Pixel / Nexus.
As already said: Install the Android USB Driver matching your phone!
Take note that OEM's Fastboot implementation isn't always same as AOSP 's Fastboot.
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
BTW: I no longer participate this thread.
jwoegerbauer said:
IMO before trying to unlock a device's bootloader it's always a good idea to check by means of ADB whether unlocking the bootloader is natively supported on device:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
I've already included this property in the post. It returned 1
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.