Hi all,
I have debranded my EVA-L09 from Three UK, so that I can get faster OTA updates (and also to try to participate in future betas) - I'm now successfully on C432B166
However, I'd like to now re-lock my bootloader, but am struggling.
Whenever I boot to fastboot and run "fastboot oem relock ****************", I get the following response:
Code:
...
FAILED (remote: root type is risk)
finished. total time: 0.006s
If I try "fastboot oem lock ****************", I get the following:
Code:
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
I have tried with "Enable OEM unlock" both enabled and disabled in Developer Options.
Can anyone give me any pointers on how to re-lock the bootloader?
Many thanks!
Sorry to bump an old thread. I'm currently having the same problems @ConfusedTA . Unfortunately I think it's difficult to re-lock bootloader without being on the same firmware that you were on when you unlocked it.
If anybody knows a way of forcing the bootloader to lock it'd be much appreciated!
Related
I have a Holiday Version of Nexus One with S-OFF and I unlocked it but was not able to relock it. I installed latest SDK and restarted the phone in "fastboot” mode and ran the following command from the computer:
fastboot oem unlock
It unlocked fine after I accepted unlock declaimer.
I then installed Amon RA 2.1.1 and then rebooted the phone and then I ran command from computer:
adb reboot bootloader
After the phone came up in bootloader I ran the following command from the computer:
fastboot oem lock
I got this reply “... INFOLock failed!”
I will appreciate any ones help who was successfully able to relock the holiday version on Nexus One.
xplorer1x said:
I have a Holiday Version of Nexus One with S-OFF and I unlocked it but was not able to relock it. I installed latest SDK and restarted the phone in "fastboot” mode and ran the following command from the computer:
fastboot oem unlock
It unlocked fine after I accepted unlock declaimer.
I then installed Amon RA 2.1.1 and then rebooted the phone and then I ran command from computer:
adb reboot bootloader
After the phone came up in bootloader I ran the following command from the computer:
fastboot oem unlock
I got this reply “... INFOLock failed!”
I will appreciate any ones help who was successfully able to relock the holiday version on Nexus One.
Click to expand...
Click to collapse
You need to type: fastboot oem lock
But why do you want to re-lock it??
Thanks for reply.
Apologies for the typo in my original post which I will correct that too but I am using the correct command:
fastboot oem lock
And I get the following reply “... INFOLock failed!”
I just want to remove the unlock icon.
xplorer1x said:
Thanks for reply.
Apologies for the typo in my original post which I will correct also but I am using the correct command:
fastboot oem unlock
And I get the following reply “... INFOLock failed!”
I just want to remove the unlock icon.
Click to expand...
Click to collapse
lock, not unlock !!!!!
Thanks but not working see here is paste from the commands I used just now:
adb reboot bootloader
fastboot oem lock
... INFOLock failed!
OKAY [ 0.141s]
finished. total time: 0.141s
fastboot oem unlock
... INFODevice was already unlocked!
OKAY [ 0.078s]
finished. total time: 0.078s
fastboot oem lock
... INFOLock failed!
OKAY [ 0.141s]
finished. total time: 0.141s
xplorer1x said:
Thanks but not working see here is paste from the commands I used just now:
adb reboot bootloader
fastboot oem lock
... INFOLock failed!
OKAY [ 0.141s]
finished. total time: 0.141s
fastboot oem unlock
... INFODevice was already unlocked!
OKAY [ 0.078s]
finished. total time: 0.078s
fastboot oem lock
... INFOLock failed!
OKAY [ 0.141s]
finished. total time: 0.141s
Click to expand...
Click to collapse
That's really weird, I've always wanted to know how to do that but I don't have S-OFF. Maybe you need to be on stock to lock the bootloader?
Weird, mine locks back up fine with fastboot oem lock, but it's not a holiday one.
Dear all,
I want to update my C6903 to Anndroid Lollipop by flashing AOSP images after building them by following the instructions from Sony. But when I tried to flash them, below error occurred.
----------------------------
fastboot flash boot boot.img
sending 'boot' (8866 KB)...
OKAY [ 0.482s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.485s
----------------------------
I used flashtool(0.9.18.5) and EasyRootTool(v12.3) to flash the firmware(C6903_14.4.A.0.108_HK.ftf) and root the system, and used that flashtool to relock the bootloader.
When I tried to unlock the bootloader again, below errors occurred.
------------------------------
[email protected]:/home/zhiming/Soft/PhoneBak/FlashTool# fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXX
//first time the command run
FAILED (remote: Command did not succeed)
finished. total time: 0.019s
//second time the command run
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
------------------------------
The rooting status showed by "*#*#7378423#*#*" -> "Service Info" -> "Configuration" is below.
After bootloader relocked using flashtool:
-------------------
Rooting status:
Bootloader unlock allowed: Yes
-------------------
After unlocking bootloader again using flashtool:
-------------------
Rooting Status:
Unknown
-------------------
Could anybody help to resolve the problem? Thanks very much!
Thanks & Regards, Zhiming WU
Can anybody help me to solve this problem?
Thanks & Regards, Zhiming WU
ZhimingWU said:
Can anybody help me to solve this problem?
Thanks & Regards, Zhiming WU
Click to expand...
Click to collapse
Check drivers then flash stock firmware again then check your bootloader status in service menu if unlocking is allowed use fastboot commands...
Follow this site
http://forum.xda-developers.com/showthread.php?t=2440597
Then go to [ how to unlock ]*(official way) in first page follow each step carefully remember Read twice, Do once.
Hello, I have problems with my sony xperia Z5p (E6853), when I try to unlock bootloader it say: (remote: Command not allowed)
C:\Users\Sampo>fastboot devices
CB5A299119 fastboot
C:\Users\Sampo>fastboot -i 0x0fce oem unlock MY CODE
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
When I check my unlocking status it say (Bootloader unlock allowed: yes)
And I have installed new drivers to my computer, I use win10.
Please help me!
Go to Z5 forum
selailija said:
Hello, I have problems with my sony xperia Z5p (E6853), when I try to unlock bootloader it say: (remote: Command not allowed)
C:\Users\Sampo>fastboot devices
CB5A299119 fastboot
C:\Users\Sampo>fastboot -i 0x0fce oem unlock MY CODE
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
When I check my unlocking status it say (Bootloader unlock allowed: yes)
And I have installed new drivers to my computer, I use win10.
Please help me!
Click to expand...
Click to collapse
Go to Z5 forum, this is only for Z normal
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:
not possible to flash firmware in downloade mode?
mrt box
elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..
Dude, I have the same problem with a P20 Pro since january!
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?
Hello all,
I think I messed my Nexus 6 badly.
I stupidly re locked the bootloader, then did a factory wipe in TWRP.
So there is no more way the phone boot to configure 'Allow OEM Unlock' in Developer Options
So I'm stuck:
C:\SDK\android-sdk-windows\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
C:\SDK\android-sdk-windows\platform-tools>
Any Idea ???
Please help
Thanks
Pas
Can you still boot to TWRP?
Deleted
runekock said:
Can you still boot to TWRP?
Click to expand...
Click to collapse
Thanks for replying.
It's on Stock recovery now.
But in TWRP flashing always fails because the bootloader is locked.
now I need to unlock the bootloader but how if "fastboot oem unlock" does not work
it give the FAILED (remote failure)
When the phone reboot it's stuck with a white Google display and nothing happen.
If you're on the stock recovery, installing the final OTA update (N8I11F) should get your device up and running so you can then enable OEM Unlocking in Android.
Strephon Alkhalikoi said:
If you're on the stock recovery, installing the final OTA update (N8I11F) should get your device up and running so you can then enable OEM Unlocking in Android.
Click to expand...
Click to collapse
Yes, the OTA update did it.
Installed fine with the ADB sideload option in stock recovery .
It finally boot up to enable OEM Unlocking
Thanks a lot
Best
Pas