After i have done the fast oem unlcok it unlocks, but when im trying to do ADB reboot bootloader it sais, device not found
Because you are issuing a adb command while in fastboot.
There is a reason the command to unlock is fastboot oem unlock and not adb oem unlock bootloader
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
When i've try to unlock bootloader via minimal adb and fastboot..i reboot my device to bootloader use the command ( adb reboot bootloader ) but i try to type this command (fastboot oem unlock ) why always unknown comand or device is lock ..same thing with i use (fastboot flashing unlock)..anybody..if u can solve this thing..please help me..
bootloader unlock failed in vivo y65
..
FAILED (remote: unclock fail.)
finished. total time: 0.015s . This always comes when i use fastboot bbk unlock_vivo. Help me solving this problem plz
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
Code:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot oem lock begin
fastboot oem lock begin
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system.img_sparsechunk.0
fastboot flash system_b system.img_sparsechunk.1
fastboot flash system_b system.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot.exe erase carrier
fastboot.exe erase userdata
fastboot.exe erase ddr
fastboot oem fb_mode_clear
fastboot oem lock
pause
when i run
Code:
fastboot oem lock
the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
MadMan29729 said:
i have the official firmware downloaded using Lenovo Moto Smart Assistant: OCEAN_PPOS29.114_134_7_1_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
running a batch file with the following
when i run the final time it tells me "Still Requires Signed Boot.Img"
flashing the boot.image results in "(bootloader) Still require signed boot.img"
any ideas where i can get a working boot.img?
Click to expand...
Click to collapse
(coming from flashing stock)
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
vinoxflame said:
(coming from flashing stock)
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
Click to expand...
Click to collapse
that worked! Thanks!
that didn't lock mine
C:\ADB>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.993s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.763s]
finished. total time: 1.760s
C:\ADB>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.014s
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
MadMan29729 said:
your going to have to root it with magisk or the option will be greyed out and say "bootloader already unlocked".. once you have a booted rooted rom, goto developer options and check enable Allow OEM Unlock..
Click to expand...
Click to collapse
So have to to root it first, then lock the bootloader?
endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
Yeah that doesn't sound like a good idea.
Sent from my mata using XDA Labs
---------- Post added at 05:58 AM ---------- Previous post was at 05:56 AM ----------
Make sure you have the correct software channel
Sent from my mata using XDA Labs
yes cause that's what I had to do cause motorola won't let you relock it unless you flash the factory firmware along with the lock command but you can't lock it without checking allow oem unlock
endleesss said:
So have to to root it first, then lock the bootloader?
Click to expand...
Click to collapse
its the only way to get rid of the bootloader error that says you need to enable Allow OEM Unlock.. rooting with magisk just forces the allow oem unlock to be enabled.. so you can check it..
as far as locking.. once you run the lock commands you have to flash the factory images then run the lock command again.. therefore you won't be rooted in the end!
Question for anyone who may know ..
So if we're already rooted and we would like to lock our bootloader we have to flash our factory image and type in the bootloader lock command as well?
Anyone successfully locked there bootloader?
If we have an unlocked bootloader and we lock it can we return back to unlocked bootloader immediately afterwards? Has anyone done this? Do we use same method as we initially did to unlock our bootloader? I only say that because I do not have my original code for my bootloader unlock that I used. If we go about it same way will Motorola give us the code again or do we need to still have those #s that we originally used?
I'm on a mission now. Soon as I comment this I'll search my butt off for a while and see what all I can figure out. If I get any good solid information I shall return here and share it for sure. Good day to everyone.
---------- Post added at 07:21 PM ---------- Previous post was at 07:08 PM ----------
Credit to @smokinu from motp G7 River forum. I'm pasting the comment here below.
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Above is from post #34 here: https://forum.xda-developers.com/mo...are-29-114-t3913673/post79305396#post79305396 And I'm quite sure the same method will work for Power although I have not tested this. Pretty sure it will though.
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Sent from my moto g(7) power using Tapatalk
MrCamby said:
In order to relock my bootloader, I had to root my phone using the magisk method.
After I was rooted I was able to go into develope options and turn on allow oem unlocking.
Then, I was able to flash the signed bootloader from an oem firmware and relock the bootloader.
You must use the same bootloader version that is currently on your phone. You can not downgrade the bootloader.
And yes, you can unlock it at a later time.
Click to expand...
Click to collapse
Thanks for the info! I always just assume on any device that bootloader can't be downgraded. When I first get the device anyway.. thanks!
can you help me relock bootloader of motorola one p30 play? i am having same issue even after typing
fastboot oem lock begin
fastboot oem lock begin
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock
it still says "still require signed boot.img"
also i have a dual slot partition slot phone
Hello,
I'm trying to bootloader unlock this phone and have encountered the above error. I am using the OEM cable, and basic ADB commands work (adb reboot ______, etc.) The command fastboot oem device-info yields the same error message. I'm thinking I don't have the right USB drivers but the phone is so new I can't find anything for it.
Do you guys have any ideas?
Boyo Synth II said:
Hello,
I'm trying to bootloader unlock this phone and have encountered the above error. I am using the OEM cable, and basic ADB commands work (adb reboot ______, etc.) The command fastboot oem device-info yields the same error message. I'm thinking I don't have the right USB drivers but the phone is so new I can't find anything for it.
Do you guys have any ideas?
Click to expand...
Click to collapse
Getting the same error, OnePlus 10 Pro NE2213
dev options enabled, OEM unlock checked, debugging enabled
device is seen in 'fastboot devices':
c:\adb>fastboot devices
84250aa3 fastboot
c:\adb>fastboot oem unlock
...
FAILED (remote: Unable to open fastboot HAL)
finished. total time: 0.002s
same happens with me.....IQOO Neo 6...
C:\Users\*****\Desktop\A13\platform-tools>fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Under developer options set the OEM unlocking ON