Unable to unlock bootloader

[zynexiz]

I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is what I get after I pull the cable);

*#*sudo fastboot oem unlock 0x9366CB600ED6A33C
[sudo] lösenord för zynex: 
< waiting for any device >
                                                   FAILED (Status read failed (No such device))
fastboot: error: Command failed

I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).

PS, yes I have OEM unlock checked, ADB debug etc etc...

-- Mike

 

[MartinX3]

I have an odd problem that I never experienced before, maybe some have? Using Linux (Arch with android-tools installed), I'm trying to unlock my XZ2C like I have done lots of time with "sudo fastboot oem unlock 0x". But, this time it just wont run. The cursor jumps about 30 characters (spaces I guess) and just sits there, nothing else happens. Have to pull the cable to the phone to "abort" fastboot. It looks like this (the FAILED part is when what I get after I pull the cable);

*#*sudo fastboot oem unlock 0x9366CB600ED6A33C

[sudo] lösenord för zynex: 

< waiting for any device >

                                                   FAILED (Status read failed (No such device))

fastboot: error: Command failed

I have tried change the cable, but still the same. Any ideas?? I read in the twrp thread about a bootloader bug, not sure if that have something to do with it. I'm on latest fw (52.0.A.10.6).



PS, yes I have OEM unlock checked, ADB debug etc etc...



-- Mike

Latest is 11.3
I would update first

Do you use at least platform tools v29.0.4?

Is the phone in the blue led fastboot mode?

 

[zynexiz]

Latest is 11.3
I would update first

Do you use at least platform tools v29.0.4?

Is the phone in the blue led fastboot mode?

Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?

Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.

Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?

 

[MartinX3]

Ah, seems that 11.3 hasn't been released here yet then, still says I'm up to date. Not sure if that's the issue here thou?

Yep, use android-tools v29.0.4-2, that's the latest release on Arch Linux.

Yes, it's blue. It finds the device when running fastboot devices, and continues after the "waiting for any device" part, but get stuck after that. Never had this issue before, so I'm not sure where to start. Maybe an issue with the bootloader itself?

The bootloader didn't change since months

Do you use the correct code or only "0x"?

And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)

 

[m4ikl1983]

Can't install TWRP on XZ2C

Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out

 

[zynexiz]

The bootloader didn't change since months

Do you use the correct code or only "0x"?

And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)

I used the code I got from Sony. Maybe should check so I entered the correct IMEI?

Yep, did get a bunch of stuff from it. Can post it if it would help?

 

[zynexiz]

Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out

Bit of topic here, but check so you have read permission for the file (if using Linux). Not sure what you mean by ADB directory, but I guess you mean the directory you have the binary in? You will need to provide the full path to the image file (if you are not in the same directory), fx ~/Download/yourimage.img.

 

[zynexiz]

The bootloader didn't change since months

Do you use the correct code or only "0x"?

And does "fastboot getvar all" gives you output?
(Bootloader version should be 118)

Not sure why, but I think I entered the wrong IMEI last time. Although, I get the same problem. Running the command, the cursor just jumps like 30-35 characters to the right and stays there, not additional text. Have to pull the cable to abort the command.

This is some of the output from getvar (omitted the partition part);

(bootloader) hw-revision:20001
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4015
(bootloader) version-baseband:1311-5320_52.0.A.10.6
(bootloader) version-bootloader:1310-7079_X_Boot_SDM845_LA2.0_P_118
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SDM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:BH901602BZ
(bootloader) serial:28b51f27
(bootloader) product:H8324
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi

 

[zynexiz]

Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though

One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?

 

[MartinX3]

Guys, trying to install TWRP recovery in Fastboot, posting that code: "fastboot flash boot twrp-3.2.3-0-xz2p.img" and it says that "twrp-3.2.3-0-xz2p.img not found", although i've put .img file in ADB directory. Can't figure it out

Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.

---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------

Ok, this was pretty odd. While typing the last comment here, I had run the unlock command and it was just sitting there in the backgrund for a couple of minutes, nothing happened. Pulled the cable, and then the bootloader was magically unlocked anyway. So problem fixed. Not sure why I didn't get any output from the command though

One question though, when rebooting I get a lock pad icon and the text "You device software can't be checked for corruption. Please lock your bootloader". Never seen that on a Sony device before. Is his a new thing?

Nice to hear that it works now.

I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.

Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).

 

[zynexiz]

Please follow the TWRP instructions in the TWRP thread.
Your command is wrong.

---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------



Nice to hear that it works now.

I never saw a android device which doesn't mention on boot that it got unlocked.
So it isn't new for me.

Ahh btw
Since you unlocked on 9.0 your camera will still work in stock.
(In custom rom anyway but there the camera is under construction and get its next update this or next month, but only on android 10.0 with 4.14 kernel).

Tried the camera, and it works like a charm

Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.

Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.

Sending 'boot.img' (30904 KB)                      #FAILED (remote: 'unknown command')
fastboot: error: Command failed

The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.

 

[MartinX3]

Tried the camera, and it works like a charm

Oh, I never saw anything like it on my other Xperias, just the normal Sony logo The only device I seen it on is Samsungs.

Althougt, I still having problem now that I'm about to flash TWRP. Get the same problem as before, just
hangs there without anything happens.

Sending 'boot.img' (30904 KB)                      #FAILED (remote: 'unknown command')
fastboot: error: Command failed

The # is where the cursor is, and when i pull the cable I get FAILED. This is pretty odd.

Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?

 

[zynexiz]

Did you follow the twrp instructions carefully including the correct booting into the fastboot mode?

Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.

Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/

 

[MartinX3]

Yep, I read about the bug and booted into fastboot with adb. But still hangs the same way when I tried unlocking the bootloader itself. Also downloaded the platform tools from Google and tried the fastboot from there, but still same outcome.

Is there another way to flash TWRP, think I seen a app of some kind long ago. But I guess I need to have it rooted before I can use it. Think I have a moment 22 situation here :/

That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?

Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)

 

[zynexiz]

That's a very weird situation
Did you try it with another computer?
Or with linux instead of windows?

Or switched the slot to slot A with "fastboot --set-active=a" ?
That also requires to flash the newest 11.3 stock firmware again.
(With xperifirm and newflasher from XDA since OTA won't work any longer.)

Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system

Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.

 

[MartinX3]

Just tried with another one, running KDE Neon. Same problem. Always using Linux, don't even own a Windows system

Tried fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img, but that one got stuck to. Nothing happens. I will try flash 11.3 and see is that might solve the issue I have.

So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.

 

[zynexiz]

So weird.
You use google plattform tools v29.x and I assume a up to date linux distribution? (I tested it with at least kernel 4.15, running 5.0 now).
Since we both use the same bootloader, it must be something in your hardware or usb cable which disturbs the communication.

Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.

Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.

 

[MartinX3]

Yep, downloaded the latest one from Google to but got the same error. Using Arch, so it's very up to date Using kernel 5.3.7-arch1-2-ARCH. Have tried another USB cable to, I will see if I can dig out a third one and try.

Btw, seems that NCB firmware are still at 10.6, that' why I haven't gotten any update yet.

No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.

Maaaaybe the kernel is too new and contains a driver bug?

 

[zynexiz]

No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.

Maaaaybe the kernel is too new and contains a driver bug?

I downloaded Customized DE 11.3 and flashed it, but still have problem trying fastboot boot twrp.img.
This is very odd indeed. Don't think it's the kernel, the other computer has kernel 4.4.

Starting to think there's an problem with the phone itself, whatever that could be!?

 

[zynexiz]

No woories, the 11.3 is only relevant for the TWRP installation.
A "fastboot boot twrp.img" should still work.

Maaaaybe the kernel is too new and contains a driver bug?

It seems that I can't do anything regarding fastboot, except rebooting it. Nothing else work, tried fastboot --set-active=a, but nothing happens at all. Tried fastboot flash boot twrp.img, same thing. Fastboot executes, but then nothing. Have to pull the cable to abort the program.

Have never in all the years I played with Android phones run into this stuff. Fastboot has always worked.

*# sudo fastboot reboot bootloader
Rebooting into bootloader                          OKAY [  0.001s]
Finished. Total time: 0.051s
*# sudo fastboot --set-active=a
<no output after this>