Hi all,
Is it possible to check if the bootloader of a Galaxy Nexus is locked or unlocked when connecting with the PC and executing a batch-file? Is there any command for checking?
I know how to check the status directly on the phone, but I want to check it on the PC.
Thanks,
Lunch
try: fastboot getvar all
should list all bootloader variables.
here is an old list for HTC, hopefully the getvar commands work, http://forum.xda-developers.com/showthread.php?t=544409
probably will be: fastboot getvar version-bootloader, or: fastboot getvar security
That's I've been looking for, thanks!
fastboot ...
oem unlock
oem device-info
oem gpt-info
oem shutdown
oem dump-reg_
oem write-reg_
oem reboot-recovery
oem dbg-level_
oem recovery-flash
oem backup-asusdata
oem restore-asusdata
oem uartlog
oem update-cmdline_
oem force-hwid_
oem emmc-info
oem factory-reset
oem factory-reset-uii
oem check-ddr
oem dump-reboot-record
oem erase-ddrmagic
oem led-
oem dump-led-
oem fuse_blow
oem check-fuse
oem reset-dev_info
oem reset-boot_count
oem enable-adb
oem auth-hash
oem gen-random
oem blow-overclocking-ok
oem blow-overclocking-no
oem check-cpuoverclock
oem unTAR_
oem enable-charger-screen
oem disable-charger-screen
oem select-display-panel
tested & working
the "oem unlock" command... does that unlock the bootloader?? I can't remember exactly what i did to unlock the padfone bootloader but I'm fairly certain that I had to flash something in recovery..
if the "oem unlock" command is for the bootloader that would make things easier... but then again.. would "fashionably late" be a correct term?
i2andog said:
the "oem unlock" command... does that unlock the bootloader?? I can't remember exactly what i did to unlock the padfone bootloader but I'm fairly certain that I had to flash something in recovery..
if the "oem unlock" command is for the bootloader that would make things easier... but then again.. would "fashionably late" be a correct term?
Click to expand...
Click to collapse
Yes, this command should unlock the bootloader but it doesn't work and it is not necessary to root the device or to flash a custom recovery.
Don't mess with the bootloader. You brick your phone faster than you can blink.
Use Towelroot to root your phone and i remember you have to downgrade to JB ... ehm ... no ... KitKat before unlocking.
That is just ludicrous to me.. Sorry if I sound facetious but I would never ever (even if my life depended on it) do that crazy $h!t you actually took the time to write out. Maybe if I had down syndrome... but honestly that is the only way I can see myself doing something crazy like that.
Can anyone tell more about this?
Will the command work to unlock the BL?
my device is asus zenfone c z007, anyone know how to unlock this device, or related to unlock this device. I has been searching all the threads but I can't find one, please help me to unlockbootlader this device. I only find to unlock app for asus A400CG with the same specification.http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/Unlock_Tool_A400CG.zip from this threads https://forum.xda-developers.com/zenfone-4/cm-12-1-cyanogenmod-12-1-asus-zenfone-4-t3249637.
.
.
here the specification + compare = https://www.ubergizmo.com/products/lang/en_us/devices/zenfone-c,zenfone-4/
@ArthurBalaOs
Before wasting your time with this check for boot-loader can get unlocked
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
jwoegerbauer said:
@ArthurBalaOs
Before wasting your time with this check for boot-loader can get unlocked
Code:
adb devices
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
ok it's nothing happened, but I try this command to my other device which supporting oem unlock it's nothing happened to. why ? btw, thanks :good:
0
ArthurBalaOs said:
ok it's nothing happened, but I try this command to my other device which supporting oem unlock it's nothing happened to. why ? btw, thanks :good:
Click to expand...
Click to collapse
May be they forgot to populate that entry...
Because not ADB but Fastboot is needed to unlock a Android device's boot-loader you always can try
Code:
fastboot devices
fastboot oem unlock
fastboot reboot
fastboot unlock-info
If outpout of last command is TRUE, then boot-loader got unlocked.
jwoegerbauer said:
May be they forgot to populate that entry...
Because not ADB but Fastboot is needed to unlock a Android device's boot-loader you always can try
Code:
fastboot devices
fastboot oem unlock
fastboot reboot
fastboot unlock-info
If outpout of last command is TRUE, then boot-loader got unlocked.
Click to expand...
Click to collapse
[COLOR="RESULT : FAIL (unknown OEM command)"][/COLOR]
that"s the result, what's that mean?
Seppppx said:
I checked the Asus website and I found no official unlocking tool for the zenfone c. I don't think I missed anything because other model have that.
Click to expand...
Click to collapse
nahh. they release the source code and kernel source, without unlocking tool. I mean everytime I trying to force unlock or force installing twrp the result always error
ArthurBalaOs said:
[COLOR="RESULT : FAIL (unknown OEM command)"][/COLOR]
that"s the result, what's that mean?
Click to expand...
Click to collapse
As I can see the version of Fastboot you use doesn't support the subcommand "OEM unlock":
Each OEM/Carrier has its own version of the Fastboot driver.
Try this instead
Code:
fastboot flashing unlock
BTW:
Become familiar with Fastboot subcommands supported on your device. Simply run
Code:
fastboot
or
Code:
fastboot OEM
you can see on this thread.
https://forum.xda-developers.com/zenfone-4/how-to-unlock-bootloader-asus-zenfone-c4-t3577340/amp/
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
mayberandomparable said:
I'm currently trying to unlock the bootloader on my Tecno Spark 8C, model KG5K. A fairly new phone brand, so documents regarding this is really shallow.
So I opted for ways that are supported on a variety of Android phones instead. I've used every way possible that I can find. ADB, Magisk, TWRP,... but none has worked, because of one sole reason: the Fastboot. So, essentially what is happening to the Fastboot is that it's seems to be missing a LOT of typical features in a Fastboot, like flashing unlock and OEM unlock.
I tried turning on OEM unlock in settings and made sure USB debugging is enabled, disabled all of the security features and even checked if my phone is ALWAYS transferring files to my laptop, but nothing is phasing the Fastboot unknown command and unlock bootloader failed error messages.
The only imaginative option that I can think of now, is whether if I can update/replace the original Fastboot that came with my phone, but I can't explain it in technical terms, or even know if such a method existed.
I would appreciate all the help I can, thanks to all of you in advance.
Click to expand...
Click to collapse
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
TNSMANI said:
In fastboot mode, is your phone recognised with a random string of numbers or alpha-numeric characters? If not, you may lack the fastboot drivers which are distinct from adb drivers. Please install the Platform Tools from this link and try.
Click to expand...
Click to collapse
080293723C004560
Does this qualifies as having distinct drivers? I'm not too sure.
mayberandomparable said:
080293723C004560
Click to expand...
Click to collapse
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Code:
C:\>fastboot devices
C:\>fastboot getvar version
C:\>fastboot getvar all
TNSMANI said:
If that is the response to the 'Fastboot devices' command and the same is shown when you issue the 'adb devices' command (while in adb mode) then you have no driver issue. What about the Platform Tools that you use (you said that several commands were missing), did you try the one I linked?
Further, the bootloader unlock command varies between devices and what works for one model may not work for another. You have to search for the proper command for your device.
Click to expand...
Click to collapse
I tried the commands, but one stood out because of the output it given. Fastboot getvar all returned nothing for all. And I did try the official Android platform-tools, but it's still the same results, I'm afraid.
Beside that, getvar version given a 1.0 version. Checked the device ID on both modes, they're the same.
Also, I did extensively search for any sliver of documentation on the fastboot of this device, but I basically got nothing, since this device is still fairly new.
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Renate said:
Fastboot is a bit of a weird animal.
The desktop executable knows valid commands and will not even attempt something that it doesn't know.
Code:
C:\>fastboot fishheads
fastboot: usage: unknown command fishheads
C:\>fastboot oem fishheads
FAILED (remote: 'unknown command')
fastboot: error: Command failed
C:\>fastboot erase fishheads
Erasing 'fishheads' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
The first error is local, the second one is remote because the desktop knows "oem" is good and doesn't care after that.
The third fails on no partition called "fishheads", but it tried. Try that and these:
Code:
C:\>fastboot getvar product
C:\>fastboot getvar serial
C:\>fastboot getvar unlocked
C:\>fastboot getvar variant
C:\>fastboot getvar partition-size:boot
C:\>fastboot getvar partition-size:boot_a
C:\>fastboot getvar partition-size:boot_b
Click to expand...
Click to collapse
I might picking up what you're putting down here.
The first 3 getvar(s) returned empty, partition-size:boot returned a failure, but boot_a and boot_b returned the same 0x4000000
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Renate said:
Did you try fastboot erase fishheads
It could tell you that your device is locked.
Click to expand...
Click to collapse
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
TNSMANI said:
@mayberandomparable
Did you try 'fastboot flashing unlock' command or 'fastboot oem unlock' command? If all such commands fail, you may need a special unlock zip file which seems to be available for the 8 Pro model but not for yours (https://forum.xda-developers.com/t/twrp-for-tecno-spark-8-pro-kg8-root-other-guide.4477425/).
Click to expand...
Click to collapse
Got stuck.
(ignore me listening to PATD, forgot for a moment)
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
You made me watch that video of PATD. It's kind of violent, eh?
Renate said:
The "special unlock zip file" is just a script that requires that fastboot flashing unlock works.
Click to expand...
Click to collapse
Oh shoot, yeah it is.
Well, we're going in circles now.
mayberandomparable said:
Got the "Flashing Lock Flag is locked. Please unlock it first!", chief.
Click to expand...
Click to collapse
So, is this operation possible?
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Renate said:
It could be that the OEM unlocking in Android Settings is broken/ineffective.
It could be that the fastboot needs some oem command.
Like (hypothetically) fastboot oem secret-unlocking-command pwd12345
Now, if you had a copy of abl we could reverse engineer it.
Have you tried to see if you can reach fastbootd? That's the user space fastboot that's in some Android.
Check if there is a difference between adb reboot bootloader and adb reboot fastboot
Is this a Qualcomm thing? Have you tried EDL? adb reboot edl
Click to expand...
Click to collapse
Hardly a Qualcomm thing, since this is using UNISOC.
Also, yes, it does have a fastbootd mode. Found on a whim!
Edit: Just tried EDL, sent straight back to the regular reboot command.
So... Does this other fastboot react at all differently?
Renate said:
So... Does this other fastboot react at all differently?
Click to expand...
Click to collapse
Oh I got something! The flashing unlock didn't work, guessing the manufacturer changed it. But OEM works flawlessly!
The last time I tried to do anything on fastbootd, platform-tools didn't even recognized the device, but now it works!
mayberandomparable said:
... but now it works!
Click to expand...
Click to collapse
So, can you fastboot erase fishheads
Renate said:
So, can you fastboot erase fishheads
Click to expand...
Click to collapse
Oop- still got a locked error, unfortunately.
Hi, I tried unlock oem to root my devies but when run command fastboot.exe oem unlock-go i get "FAILED (remote: 'oem unlock is not allowed')". The WeChat post tell that only way to unlock in newest ZUI is downgrade. Anyone success downgrade from 13.5.870 and unlock the bootloader ?
abbytan3108 said:
Hi, I tried unlock oem to root my devies but when run command fastboot.exe oem unlock-go i get "FAILED (remote: 'oem unlock is not allowed')". The WeChat post tell that only way to unlock in newest ZUI is downgrade. Anyone success downgrade from 13.5.870 and unlock the bootloader
Click to expand...
Click to collapse
Hi there,
The response itself says that you have not allowed your oem to be unlocked. Turn on the Developer option, then enable oem unlocking and try again.