Related
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
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 .
I'm trying to allow bootloader unlock but keep getting the error above. I've seen various posts on this in the past but am still stumped after doing the following :
- the phone is an xperia Z3 compact
- enabled Developer options
- enabled USB debugging
- allowed installation of apps from unknown sources
- set 'Install software' with USB Connectivity
- unlocked sim (network unlocked)
- received unlock code from Sony
- running software on Ubuntu linux
Commands I've run
=================
fastboot -i 0x0fce oem unlock 0xB9D9999DF99BDB9A
...
FAILED (remote: Command not allowed)
finished. total time: 0.003s
[email protected]:~# fastboot getvar version
version: 0.5
finished. total time: 0.002s
[email protected]:~# fastboot devices
YT9110A9BX fastboot
Anybody got any other ideas ? Thanks in advance.
I think the problem is that the setting of "Bootloader unlock allowed: No" can't be unset other than by Sony. I have contacted them but I'm not holding my breath.
I just got my OnePlus 10 Pro, and am trying to unlock the bootloader. I've enabled USB debugging, and enabled the option to allow the bootloader to be unlocked in the Developer Settings.
I ran `adb reboot bootloader`, then ran `fastboot devices` to confirm the phone was connected and visible.
When I try to run `fastboot oem unlock`, I get this response:
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Fastboot version if necessary:
Code:
C:\Windows\system32>fastboot --version
fastboot version 33.0.2-8557947
Installed as C:\Program Files\Android Platform Tools\fastboot.exe
Thanks!
Fastboot flashing unlock
Awesome, thank you very much!
I got my token, hit oem unlocking. Rebooted to fastbootd mode, then I use fastboot flash cust-unlock. Which returns,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock_code.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
If I try it without cust-unlock I get,
C:\Users\James>fastboot flash C:\Users\James\Desktop\10pro\unlock_code.bin
unknown partition 'C:\Users\James\Desktop\10pro\unlock_code.bin'
fastboot: error: cannot determine image filename for 'C:\Users\James\Desktop\10pro\unlock_code.bin'
If I fastboot reboot to bootloader and do the same command I get,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.002s]
Writing 'cust-unlock' (bootloader) Device is unlocked.
OKAY [ 0.004s]
Finished. Total time: 0.099s
But, that doesn't actually unlock my bootloader. Can someone please help?
Here's some more I have tried
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock C:\Users\James\Desktop\10pro\unlock_code.bin
fastboot: usage: unknown 'flashing' command unlock
C:\Users\James>fastboot unlock C:\Users\James\Desktop\10pro\unlock_code.bin
fastboot: usage: unknown command unlock
Edit:
Sequence of commands
Code:
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
centifanto said:
Edit:
Sequence of commands
Code:
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
Click to expand...
Click to collapse
I even renamed the file but here's what I got,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Then I moved the unlock.bin and same results.
I was able to hit oem unlock so it shouldn't be sim related, but thanks for helping
Grin59 said:
I even renamed the file but here's what I got,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Then I moved the unlock.bin and same results.
I was able to hit oem unlock so it shouldn't be sim related, but thanks for helping
Click to expand...
Click to collapse
Four things:
Name of file doesn't matter
SIM unlock and bootloader unlock are separate things
Move the unlock.bin to the same folder as your platform tools so you don't have to put the entire the path. Or put it in quotation marks
Is fastboot in your system PATH? If not, prefix fastboot to look like this
Code:
./fastboot.exe
Also, what does the following command return?
Code:
fastboot devices
centifanto said:
Also, what does the following command return?
Code:
fastboot devices
Click to expand...
Click to collapse
C:\>fastboot devices
*serial number* fastboot
Also not too sure what you mean, "Is fastboot in your system PATH? If not, prefix fastboot to look like this"
But it is installed to my system drive. Even tried downloading new platform tools and trying it in my root drive of C:\
No worries. If you got the "5497b039" returned it means fastboot is working for you and your device is in the correct bootloader mode.
Does your device display "locked" in red letters?
Are you sure that "OEM unlock" is still toggled in the developer settings?
centifanto said:
No worries. If you got the "5497b039" returned it means fastboot is working for you and your device is in the correct bootloader mode.
Does your device display "locked" in red letters?
Are you sure that "OEM unlock" is still toggled in the developer settings?
Click to expand...
Click to collapse
Okay so I got it, thank you for the help.
Did the commands you sent in the bootloader menu, guess I missed the second.
For anyone who can't unlock the bootloader I'll post simple instructions, on the NE2217
OEM unlock - on
adb reboot bootloader
fastboot devices
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
anyone can add anything else