Database Develop

Can't unlock bootloader

I cant unlock my bootloader on xperia z
Bootloader unlock allowed: Yes
I used fastboot.exe -i 0x0fce getvar version to see if the device was attached properly
version: 0.5
finished. total time: -0.000s
also when I use fastboot.exe -i 0x0fce oem unlock 0x(my key from sony site)
It said FAILED (remote: Command did not succeed)

Try typing the command correctly. oem-unlock. Its a dash not a space

error: invalid vendor id '0x0FCE.oem'

Try to remove .exe from the command so it will be like "fastboot -I 0x0fce oem unlock 0xYOUR KEY" I was getting the same error before but it's worked after I did that.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!

it's not working!

dragac90 said:
I cant unlock my bootloader on xperia z
Bootloader unlock allowed: Yes
I used fastboot.exe -i 0x0fce getvar version to see if the device was attached properly
version: 0.5
finished. total time: -0.000s
also when I use fastboot.exe -i 0x0fce oem unlock 0x(my key from sony site)
It said FAILED (remote: Command did not succeed)
Click to expand...
Click to collapse
Unlock it via flashtool.

Reinstall your driver package and reboot pc

dragac90 said:
I cant unlock my bootloader on xperia z
Bootloader unlock allowed: Yes
I used fastboot.exe -i 0x0fce getvar version to see if the device was attached properly
version: 0.5
finished. total time: -0.000s
also when I use fastboot.exe -i 0x0fce oem unlock 0x(my key from sony site)
It said FAILED (remote: Command did not succeed)
Click to expand...
Click to collapse
In linux you must have root priviledge.
Because i try it in my user and it say
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
and i use same code with root priviledge and it work.
...
OKAY [ 0.180s]
finished. total time: 0.180s
And in windows, i don't try it but i think you must execute fastboot code or bat script in administrator priviledge
Edit: Also in my first try it's not unlocking. But all time second time unlocking it. But IDK why it's not opening in first try

[Q] Unable to use fastboot

After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.

I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s

antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.

g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!

antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too

g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!

antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?

g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry

1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.

Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .

Unable to unlock Z1 bootloader - LP 270

I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?

ravi_buz said:
I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
Click to expand...
Click to collapse
Try unlocking from Sony's site ( official method ) http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Good Luck :fingers-crossed:

Found the solution
Please check my post here http://forum.xda-developers.com/showpost.php?p=61450689&postcount=390

Can't unlock bootloader

I recently discovered that my phone had already lost its DRM keys (purchased the phone second hand). So I decided I wanted to unlock the bootloader to install the DRM fix to see if that improves my camera quality.
I have followed all of the guides I can find and have attempted to troubleshot it, however nothing seems to be working.
This is the error I am getting:
Code:
C:\Flashtool\x10flasher_lib>fastboot -i 0x0fce oem unlock 0xKEYHIDDEN
...
FAILED (remote: Command did not succeed)
finished. total time: 0.022s
C:\Flashtool\x10flasher_lib>fastboot -i 0x0fce oem unlock 0xKEYHIDDEN
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
C:\Flashtool\x10flasher_lib>
I have tried creating a folder in the flashtool folder with my device id and ulcode.txt with the unlock code in it, same result.
Any suggestions on what I could be doing wrong?

So I realized what I was doing wrong today.
When I was creating the folder in flashtool with my device id and unlock code, I was creating a file named ulcode.txt.txt instead of ulcode.txt. When creating a txt document, it is not necessary to add the file extension.
Silly mistake, however I thought I would post it just in case anyone else encountered this "issue".

Verizon Desire 626

Need help to unlock bootloader. Htcdev website says get_identifier_token. Issue command in fastboot and I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.107s]
finished. total time: 0.123s
There seems to be 2 fastboot modes. One when I reboot to bootloader and I get fastboot to detect device. Different message than in the download mode, it has a recovery like menu but the options are different. There is one for usb-debug mode which just reboots the phone. I get the killswitch message in download mode, in the white screen after reboot bootloader I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.037s
3days of playing in adb shell and there is no root shell. adb root dose nothing nor an error. adb shell, then su gives an error that it dosen't exists. Anything to point me in some direction would be awesome

Update
DvineGem said:
Need help to unlock bootloader. Htcdev website says get_identifier_token. Issue command in fastboot and I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.107s]
finished. total time: 0.123s
There seems to be 2 fastboot modes. One when I reboot to bootloader and I get fastboot to detect device. Different message than in the download mode, it has a recovery like menu but the options are different. There is one for usb-debug mode which just reboots the phone. I get the killswitch message in download mode, in the white screen after reboot bootloader I get C:\Users\Dvine\Desktop\ADB>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.037s
3days of playing in adb shell and there is no root shell. adb root dose nothing nor an error. adb shell, then su gives an error that it dosen't exists. Anything to point me in some direction would be awesome
Click to expand...
Click to collapse
So I have found that the root user UID is 1000. ADB shell id: uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(ad
b),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),300
6(net_bw_stats) context=u:r:shell:s0