Database Develop

xperia z (c6603) bootloader wont unlock!

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

Unable to unlock bootloader - WTF?

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?

OEM Unlock toggle missing

Hi guys!
I'm having a problem.
I'm trying to unlock my bl but the toggle(as the title says) does not appear. So when I try to unlock via adb or flashtool I got this error:
27/021/2018 11:21:07 - INFO - finished. total time: 0.063s
27/021/2018 11:21:07 - WARN - Maybe the OEM is not enabled
and on adb I got the same thing.
Does anybody know how to solve this?
I just want to update to oreo
Thanks in anticipation

Many Z3c tablets don't have the ability to have their bootloader unlocked. I'm in Canada, and this tablet was sold through Rogers, and I have the same issue. There's no workaround, you're stuck with stock.

I had this on Z4 Tablet. Solved when I go to Developer's options and set ON the option which allows to unlock Boot Loader.

sammywtf said:
Hi guys!
I'm having a problem.
I'm trying to unlock my bl but the toggle(as the title says) does not appear. So when I try to unlock via adb or flashtool I got this error:
27/021/2018 11:21:07 - INFO - finished. total time: 0.063s
27/021/2018 11:21:07 - WARN - Maybe the OEM is not enabled
and on adb I got the same thing.
Does anybody know how to solve this?
I just want to update to oreo
Thanks in anticipation
Click to expand...
Click to collapse
I had the same problem I can't toggle the

Xiaomi Mi 8 phone bricked when trying to re-lock it

I bricked my Xiaomi Mi 8 phone by performing steps to re-lock it. It only boots into MI-Recovery 3.0 or Fastboot mode but I cannot do anything with it. MI Unlock and MI PC Suite does not recognize the phone, Flashing it does not work and MI PC Suite does not detect the phone. .
Here is what happened:
1) Xiaomi Mi 8 came with MIUI 9.5 Global Stable ROM installed that was unlocked from the Factory.
2) I used OTA upgrade to upgrade to MIUI 9.6.1 Global Stable ROM right after turning on the phone for the first time. 3) A few days later the phone allowed me to upgrade to MIUI 10 on my device also via OTA upgrade and everything worked fine until this point.
I have not been able to install a few of my applications from Google Play store – Netflix being one of the examples. In Xiaomi forums I got the information that this is because the device has been unlocked. To change that I followed an article to re-lock the device in an Xiaomi forum “[Tutorial] How to Re-lock Bootloader of Any Xiaomi Devices without Flashing” .
Unfortunately this is where I got into trouble. Here are the exact steps I performed:
-> fastboot devices
2dbe209b fastboot
-> fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.021s]
finished. total time: 0.022s
-> fastboot oem lock
...
OKAY [ 0.050s]
finished. total time: 0.052s
After entering this command the phone rebooted into MI-Recovery 3.0 with 3 Menu Options:
1. Reboot
2. Wipe-Data
3. Connect with MIAssistant
There is an error message on the bottom of the screen saying "This MIUI version can't be installed on this device". Rebooting brings me to the exact same screen.
Here are the resolution actions that I have tried so far:
1. Connecting to MI Assistant is not working. The phone shows that the USB is connected but MI PC Suite 3.2.1.311 does not detect the device.
2. Trying to undo the locking and unlocking the phone again does not work either. Here is the commands I have tried
-> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.030s]
finished. total time: 0.042s
->fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.008s
3. Following the official Unlock procedure with MI Unlock Tool Version 3.3.827.31 does not work either because the program does not recognize my phone and stays at the “Not Connected to Phone” screen.
Any ideas how I get out of this? I would appreciate any help.
-----------------------------------------------------------------------
I fear after reading more posts from this forum I know what happened. It seems the merchant sold me a Chinese version of the MI 8 with Global ROM without telling me. Packaging of the phone was original sealed and everything brand new and not tampered with so I fell for it. Appreciate any suggestions how to resolve nevertheless otherwise I bought an expensive paperweight ...

You have brick the phone,you need authorized account to install a China rom and lock bootloader and unlock with your mi account. If you install China rom you need to unlock bootloader waiting 720 hours then unlock and install global rom only with unlock bootloader!

Last week I bricked my mi 8 due to ARB protection, maybe I can help you. In your case you should try to unlock the phone with the official mi unlock tool, if it doesn't work or you don't want to wait too much, things are gonna be a little harder.
You have to open the phone and put it in EDL mode: http://en.miui.com/forum.php?mod=viewthread&tid=3459005&extra=page=1&mobile=2
After that you have to check s-unlock and someone with "EDL authorized account" will help you to restore your rom.
Ok, it's not free, but it's the only thing saved my mi 8 without sending it back to China or waiting months for an EDL authorized account

Thanks
Thank you for the fast answer - I will try it.

mi 8 locked
lucaci.ed said:
Last week I bricked my mi 8 due to ARB protection, maybe I can help you. In your case you should try to unlock the phone with the official mi unlock tool, if it doesn't work or you don't want to wait too much, things are gonna be a little harder.
You have to open the phone and put it in EDL mode: http://en.miui.com/forum.php?mod=viewthread&tid=3459005&extra=page=1&mobile=2
After that you have to check s-unlock and someone with "EDL authorized account" will help you to restore your rom.
Ok, it's not free, but it's the only thing saved my mi 8 without sending it back to China or waiting months for an EDL authorized account
Click to expand...
Click to collapse
hi lucaci.ed can you explain to me how you fix your mi 8.,? thanks before

sherwinprambudi said:
hi lucaci.ed can you explain to me how you fix your mi 8.,? thanks before
Click to expand...
Click to collapse
https:// s-unlock. com /productsandservices/server#g15
You have to buy one of these services.. it depends by what you need, but I think the cheaper option would be fine. I suggest you to contact them on Facebook before you buy and explain your problem, so they can tell you what's the best option for you.
I specify I don't work for them, but they just saved my phone from sending back to China. It's not my responsibility if it doesn't work or if you lose your money

P8Lite / ALEL21/ 2015

Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm

lm8lm8 said:
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
Click to expand...
Click to collapse
I run into the same problem and managed to fix this. You have to run the potatoNV again, keeping the testpoint shorten during the reboot, and DO NOT check the "unlock FB" checkbox this time. This checkbox actually effectively locks the bootloader.