Hello i have the Lg h340n and i am trying to unlock the bootloader but it fails i did install sdk tools and adb/fastboot and the commands work fine but this happens
When the phone is on i can find it with:
-adb devices
LGH340n1620e7f3
-adb reboot bootloader
Reboots me in to some wierd place with only commands on the top left :/
-fastboot devices
1620e7f3 Fastboot
-fastboot oem unlock
...
Failed <Remote:Unknown command>
finished. total time: 0.004s
and it sits there on bootloader doing nothing
PS C:\adb> fastboot oem unlock
FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
PS C:\adb> fastboot devices
PS C:\adb> fastboot devices
PS C:\adb> fastboot devices
de3d7f09 fastboot
PS C:\adb> fastboot oem unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS C:\adb>
tried every fastboot command but szme error
The correct command is "fastboot flashing unlock" !
https://c.realme.com/in/post-details/1244566811094024192
zabbaluga said:
The correct command is "fastboot flashing unlock" !
https://c.realme.com/in/post-details/1244566811094024192
Click to expand...
Click to collapse
Same error with that command i tried every command noluck
Did you first apply the deep testing apk?
zabbaluga said:
Did you first apply the deep testing apk?
Click to expand...
Click to collapse
Yeah idid i solved the problem , to use fastboot command with realme devices you should use an usb 2.0 port not a 3.0 or usb ones coz my laptops had only usb 3.2 i used another one and i succeeded now im on pixel experience, thanks for your time dude
Hello all,
I currently have a Blu Studio Mega 2019 android device with me. It is running android 9. I have spent the last 3 days trying my hardest and expending all resources to root the device. I have been unsuccessful every time and the main reason is that When I run the below command it always fails. I have tried "fastboot oem unlock" or "fastboot oem device-info" and it always returns command not valid.
fastboot flash recovery twrp.img
Sending 'recovery' (16356 KB) OKAY [ 0.527s]
Writing 'recovery' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
Yes I do have usb debugging on, OEM unlock on, I have the android drivers for the "fastboot gadget installed". My device shows up when I type "fastboot devices" and will reboot with "fastboot reboot". I have not been able to find a solution to my 'Flashing Lock Flag is locked. Please unlock it first!' problem. I hope someone else has found the solution.
I need the boot.img for the EU-Version. Can someone please help me? Thx in forward.
Here are both magisk patched and stock boot.img files
Using latest magisk 25.1 stable
Stock
Magisk Patched
Thank you. I've now read rooting is not possible because Mediatek. Is it true please? Will not break it.
I'm rooted on my Nord2T. Whoever said that does not know what they are talking about.
The original Nord 2 was also mediatek and has a few custom ROMs and everything
I'm not able to boot correct in bootloader. There is written at the display extreme small "Fastboot Mode". If I set command "fastboot oem unlock" there is no reaction and nothing written. Changing with up/down is nothing doing.
Pushing Vol- and Powerbutton ends in recovery. There it is only possible to choose language and then wipe, reboot and power off.
My firmware is: CPH2399_11_A.09
Wrong code not
Code:
fastboot oem unlock
The correct command is
Code:
fastboot flashing unlock
Sorry, can not unlock the bootloader
Both commands failed
PS C:\adb2> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb2> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\adb2>
Try using a different ADB and fastboot. I use official platform tools from here
Also what comes up when you type
Code:
fastboot devices
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
I had the same problem while opening Bootloader...Tried everything - Windows 10
I did the same on Windows 7 and immidiately bootloader open.
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
Did you enable developer options and select Enable OEM unlock first?
garylawwd said:
I'm rooted on my Nord2T. Whoever said that does not know what they are talking about.
The original Nord 2 was also mediatek and has a few custom ROMs and everything
Click to expand...
Click to collapse
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
cioce said:
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
Click to expand...
Click to collapse
It will if you flash kdragon safetynet fix in magisk
cioce said:
Did you pass the safetynet check?
My new Nord 2T is arrived today, I will see how many days it will resist unrooted
Click to expand...
Click to collapse
Don't rush and don't do it like me. Here boot images are for 09. So upgrade first.
Safety net passes with magisk module
Root easily hidden with lsposed and shamiko module.
Riski3Run said:
Did you enable developer options and select Enable OEM unlock first?
Click to expand...
Click to collapse
Yes
mystery007 said:
Have downloaded and used the tools from official platform (your link)
PS C:\adb3> fastboot devices
UKGYBYZTL7699T8T fastboot
PS C:\adb3> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
PS C:\adb3> fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
I'm in "Fastbootd Mode".
The command was "adb reboot fastboot". The command "adb reboot bootloader" does not work at mine N2t
Click to expand...
Click to collapse
u should not be in fastbootd mode in adb type adb reboot bootloader
then type
fastboot flashing unlock
this should unlock your bootloader
so i am trying to unlock bootloader in my device tecno spark 8c i enter the fastboot mode and tried the command fastboot oem unlock it say message ok but nothing happenes if i try to flash the vbmeta it says the bootloader locked and need to be unlocked how to unlock it?
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
no it didnt get unlock it only say message ok
i tried this command fastboot getvar unlocked
which give me message unlocked:no and i am running linux so i am using its commandline working with it and as i say it didnt get unlocked what is the problem i cant figure it out
jwoegerbauer said:
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
Click to expand...
Click to collapse
[[email protected]]-[~]
>>> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
[[email protected]]-[~]
>>> adb reboot bootloader
error: insufficient permissions for device
See [http://developer.android.com/tools/device.html] for more information
[[email protected]]-[~]
>>> adb reboot bootloader
[[email protected]]-[~]
>>> fastboot oem unlock
< waiting for any device >
FAILED (remote: 'Unlock bootloader fail.')
fastboot: error: Command failed
[[email protected]]-[~]
>>> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.018s]
< waiting for any device >
Finished. Total time: 17.010s
[[email protected]]-[~]
>>> fastboot oem unlock
OKAY [ 0.001s]
Finished. Total time: 0.001s
[[email protected]]-[~]
>>> fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.001s
[[email protected]]-[~]
>>>
here is the commands and the output as u see and i already enabled oem in the developer options
Reboot Android to make changes permanent
jwoegerbauer said:
Reboot Android to make changes permanent
Click to expand...
Click to collapse
u mean reboot after i did the command?
i did it nothing change
try this method
https://forum.xda-developers.com/t/is-my-life-really-worth-it.4217751/post-84295797
fastboot flashing unlock