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

XT1092 Bootloader unable to re-lock. Need to get replacement

Hi, i recently ordered my moto x 2014 32gb from flipkart(just in case this info help). The Model number is XT1092. I did bootloader unlock and flashed cyanogen mod. It is my mistake i didn't backup my factory images. Now i want to return the phone to flipkart. I restored my phone to factory settings using RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml image. I then did fastboot oem lock...but it gave me two errors
1. sst failure
2. need to do fastboot oem lock begin.
I did the lock begin command and flashed firmware but it resulted in failure stating PreFlash Verification failure. Please I need to return this phone, I dont want to use it anymore but i need to first lock the bootloader. What should i do.
Regards
Mohit Goyal

Does not matter, when you unlocked it was with a code through motorola's website. They know you unlocked it and the warranty is void. Relocking does not give you back your warranty. Plus after relock it is "relocked" not "locked" which is proof that it was unlocked before. There is no way to get it back to a true locked state.
Sent from my XT1095 using Tapatalk

mohitgoyal707 said:
Hi, i recently ordered my moto x 2014 32gb from flipkart(just in case this info help). The Model number is XT1092. I did bootloader unlock and flashed cyanogen mod. It is my mistake i didn't backup my factory images. Now i want to return the phone to flipkart. I restored my phone to factory settings using RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml image. I then did fastboot oem lock...but it gave me two errors
1. sst failure
2. need to do fastboot oem lock begin.
I did the lock begin command and flashed firmware but it resulted in failure stating PreFlash Verification failure. Please I need to return this phone, I dont want to use it anymore but i need to first lock the bootloader. What should i do.
Regards
Mohit Goyal
Click to expand...
Click to collapse
You didn't purchase this device just for playing, did you? Keep in mind that by unlocking bootloader, you voided any warranty as well as your right to return this device, because you modified the system. When handling online returns, the seller usually wants 'unused' device. You could try giving it back though, but keep in mind you ruined a device even if they accept your return.

XT1068 - Error unlock bootloader, not write new rom

My xt1068 has locked bootloader, and was in the rom 5.0.2 and upgraded to 6.0 alone and began to hang, was then rewrite rom 6.0 (TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7), and not turned over, I tried to rewrite the 5.0. 2 (although I knew that the chance to return was almost zero because the rom does not downgrade with locked bootloader). and not worked ...
I tried to unlock the bootloader and the following error:
(Bootloader) unlock invalid date!
FAILED (remote failure)
finished. Total time: 10.031s
the equipment is stopped, and not do anything already used several commands like "mfastboot oem fb_mode_clear" among others, however nothing happens.
I have a little experience with rom motorola, but nothing is solving.
It will be someone there who can help me ...

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?

I found a way to unlock amazon x4! (only tested on european model xt1900-7)

So a few days ago I picked up my X4 on Amazon to replace my dying old Samsung, (XT1900-7, 4/64) for 125€ which is a steal for the specs you get. After playing with it for a while I decided to unlock the Bootloader so I can root it. When I tried the fastboot oem get_unlock_data in fastboot mode It only says "Invalid Command" then I realised I have the Amazon Prime version (which had Alexa installed), which allegedly cannot be unlocked, and was stuck in Android 8. So after a lot of googling I tried Sideloading Pie in fastboot, which didn´t work. Applying update from SD Card also didn´t work (couldn´t mount /sdcard). So I followed this method here: https://forum.xda-developers.com/moto-x4/how-to/rom-upgrade-directly-to-pie-8-0-locked-t3876127 (thanks to TeamRainless). I downloaded the factory signed Image from the MEGA Link: https://mega.nz/#!QQ1mgKpS!ce2kysojSUv9pzA-V4YE4kv5jg0S7X5X1lNrIWn6su0. I put the zip file (DO NOT RENAME THE FILE!) in the root folder of my internal storage, then checked the update manually in the Settings, and voila! It applies the Pie update in the 30 Minutes and now I have the retail version of the ROM without Amazon apps on it.
I applied all patches until September 2019 (PPWS29.69-37-5). I rebooted into fastboot mode and ran the fastboot oem get_unlock_data as usual and now I get the 5 lines of code I could use to unlock the device. I logged into Motorola website and pasted the code, accepted all the T&Cs, got the unlock code in my Email and now my phone is unlockable. I ran this in fastboot fastboot oem unlock *code given in email* and the phone was unlocked. When I rebooted the phone all my data was deleted so if you want to do this back up your data first! I hope this gives hope to all of you who bought the Amazon version without knowing. Good luck trying and stay healthy guys!
https://postimg.cc/gallery/XXVR3H3

wow thnx for information

Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?

gatesps said:
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
Click to expand...
Click to collapse
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Or is there any other way how to install mentioned image?

maks_kyiv said:
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
Click to expand...
Click to collapse
Device Model #, Codename, and Software Channel.
maks_kyiv said:
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Click to expand...
Click to collapse
Only if the bootloader is already unlocked
maks_kyiv said:
Or is there any other way how to install mentioned image?
Click to expand...
Click to collapse

sd_shadow said:
Device Model #, Codename, and Software Channel.
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
sd_shadow said:
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
Bad, I will wait for any working bootloader unlocking method for Amazon phones.

maks_kyiv said:
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
Click to expand...
Click to collapse
Tried on another PC. Got all fastboot variables successfully.
So my phone is from US.

I also have an XT1900-1 already upgraded to Pie with a locked bootloader. I had a thought - would it be possible to trick the update service into thinking that this image is an upgrade? How does the update service know that the image is a newer version anyway?