Hello
I'm trying to Relock bootloader after it has been unlock with fastboot oem unlock command, and it seems an impossible mission.... I've downgraded to stock version thru EMMA FlashTool (Android 9).
The command I use is: fastboot oem lock and I get the following error:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Also tried thru sony mobile flasher by androxyde (Pressed BLU button):
Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null
Any suggestion anyone??
It's not possible to relock the bootloader of the XZ1C. It's a one-way operation. All of the threads giving information on how unlock mention this fact, as (I believe) does the Sony unlock pages.
Thus why you're getting an unknown command ... because there's no such action supported.
If I use stock ROM (Not custom) from Xperifirm, it can happend?
No ... it has nothing to do with the ROM that you're using, it's in the bootloader. Probably an e-fuse.
You can't re-lock it. Full stop. No caveats.
Ohhh
So no way to Relock the bootloader then?? I saw that many phone can....
Yes, some phones can. But definitely not all.
This is one of the ones that cannot.
I've installed kernel-G8441-47.2.A.11.228-hideunlock.zip and it works great!
One thing I can't pass - Google Wallet (Pay)
I didn't root my device, only unlocked the bootloader.
Any advice?
Related
hey
well i got my xperia z c6603 a few weeks ago and i unlocked the bootloader using the instructions on the sony website,well everything went ok.
but i had a issue when flashing something so had to flash back to a generic uk rom,well ever since i have been unable to unlock my bootloader again!
tried flashtool and i get FAILED (remote: incorrect format for unlock data. should be in the form of "0x) and it does start with 0x
before this i tried the fastboot using cmd or command prompt
when i type fastboot.exe -i 0x0fce getvar version i get 0.5
but when i try to put in the unlock code i get
FAILED (remote: command did not succeed)
finished. total time: 0.040s
if i put the code in again it does work but then the phone gets stuck in a bootloop!
i have tried different generic roms and have even tried going to a older rom and upgrading through sony companion but i keep getting the same thing!
i really dont know what to do,i hope someone can help me please.
is there any other way of doing this? what could have caused it? it worked fine untill i failed installing a rom.
i am from the uk,so i have tried different generic roms but it just does the same thing the phone is working perfectly fine and theres no changes
Forgive me if I'm wrong, I'm sure someone will correct me but AFAIK the bootloader doesn't relock by simply flashing a stock rom. It should still be unlocked and that's why you are undergoing issues attempting to unlock possibly? Have you tried reflashing the kernel ?
flashing stock rom doesn't relock the bootloader
I'm hoping someone can help:
I've been rooting/unlocking android phones for years. I've run Linux as my desktop OS for 15 years and I'm used to using fastboot.
I've had an Xperia Zr for a few years and when I saw them new on Ebay new for <$100 I bought another one.
So the first thing I try and do is unlock the bootloader, I have done this on several phones, including the ZR I use as my main phone.
I get the IMEI off the back of the phone and make sure it's the same as the one I get when I *#*#SERVICE#*#* and it is.
In Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes
I go to sony and get the unlock code for that IMEI (I've done this 4 times, it's always the same, I've double checked all the fields).
When I enter the command from fastboot to unlock the bootloader I get this:
[email protected]:/media/rolf/Data/Android$ sudo fastboot -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.598s]
finished. total time: 1.598s
So no error, it looks like it worked. When I reboot the phone it's like new again it wiped itself as it does after you unlock the bootloader.
But when I go back to Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes , but it should now say bootloader unlocked.
When I go back to fastboot and try and flash anything it behaves like it still locked.
[email protected]:/media/rolf/Data/Android$ sudo fastboot flash recovery cm-13.0-20160930-NIGHTLY-dogo-recovery.img
sending 'recovery' (11570 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
The phones both look identical, the new one looks genuine, the FCC ID and model number and Type are the same. The old phone was made in the 25th week of 2013 the new one is 30th week 2014.
Does anyone have any idea what is going on?
Thanks,
Rolf
Use flashtool to unlock bootloader.maybe this will work.I used flashtool to unlock my zr bootloader easily.
Flashtool is just a way for people who don't use the command line to issue commands.
Just to be sure I installed it under Linux and Windows and tried the bootloader unlock from there with the same results on both OSs.
01/004/2016 11:04:58 - INFO - Device connected in fastboot mode
01/007/2016 11:07:45 - INFO - Unlocking phone using key 3214A89EDE406752
01/007/2016 11:07:47 - INFO - ...
01/007/2016 11:07:47 - INFO - OKAY [ 1.385s]
01/007/2016 11:07:47 - INFO - finished. total time: 1.385s
01/007/2016 11:07:47 - INFO - Device will reboot into system now
01/007/2016 11:07:47 - INFO - Unlock code saved to C:\Users\rolf\.flashTool\registeredDevices\EP74168AM1\ulcode.txt
01/007/2016 11:07:47 - INFO - Device disconnected
Like when I use fastboot directly the device factory resets itself but remains a locked bootloader.
Has anyone ever seen a phone that says Bootloader unlock allowed: Yes but when you issue the command it fails silently?
Just to be sure, I have tried many different versions of flashtool. I have also tried using the wrong key to see what happens.
If I change the last digit of the unlock code then the command fails.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406751
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
If I give the correct unlock code the command succeeds, but the phone never unlocks.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.569s]
finished. total time: 1.569s
I've tried using 2 different computers now so I have ruled out the computer hardware or software.
It seems to be the phone, this one is made in Malaysia the other one does not say where it was made.
Does anyone have any ideas?
This won't happen if your zr isn't carrier locked.So check it otherwise i'm unable to help you.Here are some great members in zr community can help you with this wired problem.PM with daedroza or sigprof.without PM it's not hard to get help from great members.
Never seen something like this, so the following is mostly a guesswork…
What ROM do you currently have on this phone, and did you reflash it? In theory it's possible that some strange (carrier-specific) ROM version relocks the bootloader during boot; another possibility is that the unlocking process is broken with some bootloader versions. Because creating the TA backup before unlocking needs root, I used old ROMs when unlocking — maybe even something ancient like 10.3.1.A.2.67, which can be rooted with opensource rootkitZ, and definitely not something which requires the malware-infested King Root. So flashing a stock ROM with a different bootloader version may help (the bootloader version number in boot_delivery.xml inside FTF must be different from the installed verson, otherwise flashtool will skip the bootloader parts when flashing — e.g., 10.6.x and 10.7.x stock ROMs have the same VERSION="1264-2309 S1_Boot_Lagan_1.1_10").
Thank you for some excellent advice. I had already re-flashed 5.1.1 with no change, so I tried 5.0.1 and there was also no change.
I found the oldest KitKat Rom I could and flashed that, as before the bootloader unlock command appeared to have worked but this time it rebooted into a boot loop.
I dropped back into fastboot and was able to flash a new boot.img and installing cm13 was quick and easy. The bootloader now shows as unlocked in SERVICE.
What software did you use to flash an old rom?
MOTO All-In-one Tool
https://forum.xda-developers.com/moto-g-2014/general/motorola-moto-one-tool-v1-0-t3397159
Try the steps listed here: https://www.theandroidsoul.com/relock-bootloader-fastboot-android/
NOTE: You may lose all data. It also may be disabled once you have unlocked. You may not be able to get your warranty back.
Error
I have used your fastboot adb trick for relock my device but unfortunately it shows
Lock failed - Err:0x fffffffffe
Er.chetanssoni said:
I have used your fastboot adb trick for relock my device but unfortunately it shows
Lock failed - Err:0x fffffffffe
Click to expand...
Click to collapse
That is unfortunately about what I expected. When you unlock your bootloader, you void your warranty. That is why I wrote "It also may be disabled once you have unlocked. You may not be able to get your warranty back."
I'm ussing XT1771 and still can't relock the boot loader i tried a lot of things gamn xD
my phone is SoftBank 502SO X Performance using GENERIC GLOBAL 8.0.0 F8131 rom. i tried most of the fastboot commands i could find. everything just throws out "command not allowed" error except for reboot and getvar command. any help please? i also have OEM Unlocking turned on as well as USB Debugging and turned off MyXperia Find My Device. my bootloader is locked and the service code shows up with "no". i remember a few years back where i use this android 4.4.4 budget phone (also bootloader locked and will not be unlocked in any way) can do most of the fastboot commands (flash system/ boot/ recovery/ etc...)
if it cannot fixed in anyway, is there any rooting app specifically for android 6.0.1 - 8.0.0? i tried using kingoroot, kingroot. none of them can break through.
Any help would be appreciated.
yeah , i have that phone as well , we kinna get ****ed because unless there is a exploit there is no way to unlock bootloader . There is a exploit have potential it's cve 2019-2215 but i found no developer working on it there is a app based on it (qu1ckr00t) but it not work on all device and i have try to compile it but i don't have the skill to do that . And i have try contact sony to resolve it but they said no . So yeah hope in the near future there will be a way
Hi all,
I recently unlocked the bootloader of my old Sony Xperia XZ2, which I bought from my mobile carrier in Peru, following the steps in the Sony Developer World page. It worked as expected, the bootloader was unlocked. However, when I installed another ROM to have Android 10, I saw the annoying message others have reported (here and here), "Your device software can't be checked for corruption. Please lock the bootloader".
I have read that the DRM keys should be backed up before doing this process, which are related to the Sony features, I don't care about losing those at this point. Is there a way to relock the bootloader again?
I already tried fastboot oem lock and fastboot flashing lock with no avail, the message returned is FAILED (remote: unknown command).
Flashtool BLU option doesn't work either. When trying to run it, it shows the message "ERROR - Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null", which leads me to think it's trying to read a string from somewhere but it doesn't exist.
I've already flashed the original stock ROM from my carrier but all the commands I tried above return the same failure.
I've also found this tutorial that applies for the Xperia XZ1 Compact and says that unlocking the bootloader is not a reversible process. Is that true for the Xperia XZ2 as well?
Thank you very much for your help on this.
Best regards,
Jorge