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.
Related
hello bro
i have moto xt926 4.4.2
3 month ago unlock boot lodaer but now i need relock boot lodaer for new update please
who know instr to help me
nokia alkng said:
hello bro
i have moto xt926 4.4.2
3 month ago unlock boot lodaer but now i need relock boot lodaer for new update please
who know instr to help me
Click to expand...
Click to collapse
1. Wrong Forum, bro (here is Razr i)
2. Use ADB relock (pretty the same as ADB unlock you have done...)
5m00v3 said:
1. Wrong Forum, bro (here is Razr i)
2. Use ADB relock (pretty the same as ADB unlock you have done...)
Click to expand...
Click to collapse
please can you gave me instr how to plz
5m00v3 said:
1. Wrong Forum, bro (here is Razr i)
2. Use ADB relock (pretty the same as ADB unlock you have done...)
Click to expand...
Click to collapse
C:\android>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\android>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\android>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.010s]
finished. total time: 0.011s
C:\android>
i call to motorola support but not slove
oky no problem can you tell me how to install twrp for xt926 4.4.2 i try one by one but cant install twrp
nokia alkng said:
(bootloader) FAIL: Please run fastboot oem lock begin first!
Click to expand...
Click to collapse
did you try: fastboot oem lock begin
And for xt926, go to the section of this forum for your phone, there u find twrp instr and files: http://forum.xda-developers.com/droid-razr-hd
5m00v3 said:
did you try: fastboot oem lock begin
And for xt926, go to the section of this forum for your phone, there u find twrp instr and files: http://forum.xda-developers.com/droid-razr-hd
Click to expand...
Click to collapse
hi bro
yas i tried more
C:\android>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\android>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\android>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.010s]
finished. total time: 0.011s
nokia alkng said:
hi bro
yas i tried more
Click to expand...
Click to collapse
have a look into this batch file: http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
This is relock for Razr i, so DONT use it directly on your phone!
Look into the relock.bat file for ADB commands to relock...
---------- Post added at 04:08 PM ---------- Previous post was at 03:50 PM ----------
maybe you only need:
fastboot oem lock begin
fastboot oem lock
fastboot reboot
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.
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Check your phone box, there is a sticker that should say "XT 1541 retXX" so you know wich region is right for your phone, then download the fw from the filefacory repo http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50 and flash it whit mfastbootV2
PS
Your phone have a dedicated section --> http://forum.xda-developers.com/2015-moto-g
edrpomidor said:
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Click to expand...
Click to collapse
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
benjausen said:
Use mfastboot v2, and try to flash a firmware FROM THE SAME REGION. Did you change motoboot.img? If so then skip 5.X gpt.bin and motoboot.img flashing.
Click to expand...
Click to collapse
No I didn't
deleted
benjausen said:
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
Click to expand...
Click to collapse
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
edrpomidor said:
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
Click to expand...
Click to collapse
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
benjausen said:
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
Click to expand...
Click to collapse
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
edrpomidor said:
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
Click to expand...
Click to collapse
Try flashing CM12.1 then.
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!
Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?
Did you remove your screenlock and Google account before flashing?
Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue
From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)