Unlocked Bootloader (D625 Tegra)? - LG G2 Mini

I've run "fastboot oem unlock" on my device (D625), and get this:
Code:
...
(bootloader) Bootloader is already unlocked.
OKAY [ 0.005s]
finished. total time: 0.006s
also when I run "fastboot getvar unlocked" I get this:
Code:
unlocked: yes
finished. total time: 0.000s
Is this normal? My phone really have unlocked bootloader?
If so, anyone can port CWM for him, if I give my boot.img?
EDIT: Bootloader seems to be locked, or at least the LG Secure_Boot remains active: http://forum.xda-developers.com/g2-mini/general/unlocking-bootloader-tegra-version-t2933295/page11

If says, yes. The problem is the lg secure boot, which we are looking into, stay tuned in the thread in general to know when/if a solution comes up.
Enviado de meu LG-D625 usando Tapatalk

Related

MM PLK-L01 313 | Unlocked Bootloader: Almost all fastboot commands fail

Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
MarioGirotti said:
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
Click to expand...
Click to collapse
Nothing wrong with you, these commands are just not supported by Huawei bootloader (fastboot)
Damn... I wanted to boot into a custom recovery without flashing it. On Nexus 4 this was possible.
MarioGirotti said:
Damn... I wanted to boot into a custom recovery without flashing it. On Nexus 4 this was possible.
Click to expand...
Click to collapse
Yup, sucks big time, especially when trying to develop something
MarioGirotti said:
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
Click to expand...
Click to collapse
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
^ maybe the green text saying "unlocked" is a hint
fosseperme said:
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
Click to expand...
Click to collapse
I will check this evening when I am back from work also this command
fosseperme said:
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
Click to expand...
Click to collapse
Great:
C:\Users\daniel>fastboot oem get-lockstate
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
But the bootloader screen itself tells: PHONE Unlocked
MarioGirotti said:
Great:
C:\Users\daniel>fastboot oem get-lockstate
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
But the bootloader screen itself tells: PHONE Unlocked
Click to expand...
Click to collapse
by the way, on this phone it's...
Code:
fastboot oem get-bootinfo
EDIT: IGNORE ME! You already said that in the OP

OnePlus X unlock bootloader problems

Hello,
I'm trying to unlock my bootloader on my OPX but every time I type:
Code:
fastboot oem unlock
I get this response:
Code:
...
OKAY [ 0.000s]
finished. total time: 0.000s
and the bootloader doesn't unlock. I'm using Ubuntu 16.10
Thanks

Bootloader unlock problem

I have problem when i try unlock bootloader of my ANE-AL00
CMD-Fastboot say: deactivate find my Phone. But isnt prossible.
https://youtu.be/a5CjIqQCbuw
Hi
Hi?
(bootloader) Necessary to disable Phone finder!
FAILED (remote: Command not allowed)
finished. total time: 0.020s

MTK8163 Fastboot flashing working not full

Hi,
Tried to flash my Acer Iconia B3-A30. Before I start with flashing i tried some commands. The "fastboot reboot" doesn't work for me.
Every Time i try
Code:
platform-tools>fastboot reboot
Rebooting FAILED (remote: 'not support on security')
fastboot: error: Command failed
bootloader is unlocked:
Code:
platform-tools>fastboot getvar unlocked
unlocked: yes
Finished. Total time: 0.003s
but i found the secure state in the getvar info's:
Code:
platform-tools>fastboot getvar secure
secure: no
Finished. Total time: 0.004s
is it ritght?
I hope u can help me. Because my tablet stuck on boot image. Recovery doesent boot anymore.. etc.
Same problem here. Did you figure it out?

Xiaomi MI A3 stuck on bootloader

Hi
I'm stuck in my Xiaomi MI A3 bootloader, can't boot to recovery and system.
After flashing my stock firmware.
Here is my oem device info
PS C:\platform-tools> ./fastboot oem device-info (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
Finished. Total time: 0.006s
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
bgsebiosjr said:
Hi
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
Click to expand...
Click to collapse
Change current-slot to 'a' and reboot.
PS C:\platform-tools> ./fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0
OKAY [ 0.002s]
Finished. Total time: 0.005s
PS C:\platform-tools> ./fastboot flashing unlock FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
How can i use EDL?
Sapper Morton said:
Since your bootloader is locked, and there's no proper system.img in slot B, you must change it to slot A; however it's not possible in locked state, first check if it's possible to unlock, by running:
Code:
fastboot flashing get_unlock_ability
If the output is 0, you cannot unlock, and EDL is a must, otherwise, the output will be 1, therefore, unlock is possible, then proceed with the following steps:
Code:
fastboot flashing unlock
Code:
fastboot set_active a
Code:
fastboot flashing lock
As explained above, it's not possible to change slot without unlocking the bootloader.
Click to expand...
Click to collapse
msatyanarayana said:
Change current-slot to 'a' and reboot.
Click to expand...
Click to collapse
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
bgsebiosjr said:
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
Click to expand...
Click to collapse
EDL mode and authorized Mi account. You should contact your nearest Xiaomi service center or use some online service (you might need to open your phone yourself in such case).

Categories

Resources