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".
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
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
stygianblizzard said:
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
Click to expand...
Click to collapse
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
gee2012 said:
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
Click to expand...
Click to collapse
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
stygianblizzard said:
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
TWRP cannot flash the stock images. Only flash able zips. The modified zips linked by @gee2012 should work
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
Just few mins got img downloaded. That was bloody awesome. I dont know how to thank you :laugh::laugh::laugh::good:
Superb
Its working again!!!!!
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
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 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