Hello guys, I have a problem. My device shows 'Command FAILED' when I try to unlock the bootloader. I have done everything by the book, this is not my first Sony device, I backed up my DRM keys, but this problem arose. ADB recognises my computer, OEM unlocking was ON in Dev options, fastboot devices returns Device ID, everything is ok, without the actual unlock. (note: I was on the downgraded LP firmware when I tried to unlock for the first time )
First, I tried with Flashtool and it got this same error, so I looked around the forum and saw the 'put ulcode.txt with your unlock code in my_devices folder', which I did.
Then Flashtool did NOT ask me to go into fastboot, only flashmode, which was strange but it said it was successful so I continued.
When I rebooted and tried to flash the modified kernel, BAM, unsuccessful...
So I flashed the latest firmware from Xperifirm (.253) and just kept using my phone as normal. Today I decided to try again and again 'Command FAILED'. Flashtool continues to think my device in unlocked and has the option of relocking... Which does nothing. Basically, whatever I do in Flashtool has no effect, even my DRM keys are untouched after all this tampering, so at least i got that going for me which is nice :silly::silly:
I can add screenshots and photos if it will help...
In dev settings, enable oem unlock.
I had the same problem with v224.
I have upgraded to 253 and it works fine for unlocking BL.
Dany21000 said:
In dev settings, enable oem unlock.
I had the same problem with v224.
I have upgraded to 253 and it works fine for unlocking BL.
Click to expand...
Click to collapse
But if you read my post, I wrote that OEM Unlocking was ON, I confirmed my password and checked, it was on. Still, the problem persists...:crying:
Bump... I don't know if Flashtool messed it up, it can 'lock' and 'relock' it but the phone itself doesn't reflect any changes. Still fastboot command failed...
Is your bootloader unlock available?
Wich 253 rom have you flash?
Dany21000 said:
Is your bootloader unlock available?
Wich 253 rom have you flash?
Click to expand...
Click to collapse
Yup, it is avaivable and a ROM from Xperifirm for my country (Bulgaria), downgraded LP one didn't work as well.
I use a US version...
It was on 224 FR version and it doesn't work, like you.
After upgrading to 253 (in FR, i think), same problem.
So i have to flash a new 253 in US version and it work fine.
Dany21000 said:
I use a US version...
It was on 224 FR version and it doesn't work, like you.
After upgrading to 253 (in FR, i think), same problem.
So i have to flash a new 253 in US version and it work fine.
Click to expand...
Click to collapse
I don't think playing the 'reflash game' will do the trick... I might try that sometime eve though I'm very skeptical. Idk about US firmware - it doesn't support fingerprint sensors so I don't know what might happen if I do flash it.
Bump
Related
Hi I've tried searching about quite a bit but can't seem to find the correct solution.
I've had the bootloader unlocked once by following DoomLords instrucions but locked it as an upgrade popped up on my pc companion, now I can't seem to unlock it again.
I've followed the same process as before, even through the sony bootloader unlock site (this gave me the same unlock key as before) I've attached my error from the command prompt screen.
Anyone??
the screenshot is not readable.
maybe you forgot to remove the last number form the unlock key.
or flash a firmware first then try again
Sorry here's another screen.
I tried to re unlock the bootloader after an update via pc companion, it didn't work then.
I've now flashed ICS onto the phone with flash tool and unlocking the bootloader still doesn't work.
I've tried taking the last digit off the unlock code, with no luck!
Random post to keep the thread alive, hopefully someone will know whats up
Last try, anyone?
You're not using 0xFFFFFFF as the key are you?
No definitely not. That was the error the 2nd time round trying.....
I did sucessfully unlock my bootloader, installed CM10.1 (pollux_windy), tested it, relocked my bootloader, returned to stock (with the correct code).
Now, when I try to unlock my bootloader, I'm unable to do so via flashtool (0.9.11.0), and I guess the main reason for that is that wrongly inputted the wrong unlock code (since I got several devices). No matter what I try, I'm unable to do so with the right code, mainly because I think the flashtool apparently read the IMEI/IDID from the device and that flashtool selects the relock code that is wrong ...
Is there any way to override this so that I can input the correct code?
Many thanks.
UPDATE: solved. removed flashtool and application data, restored stock and tried again ... It failed the first time, but worked after that ...
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
C:\>fastboot flash boot boot.img
sending 'boot' (32584 KB)...
OKAY [ 1.633s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 2.150s
Click to expand...
Click to collapse
Thank you for the help
Diomorgan said:
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
Thank you for the help
Click to expand...
Click to collapse
First of all it's not polite to create new thread in android development part. Here should be only roms, fixes, patches recoveries. Not q&a threads.
As to your problem, are you sure that you've unlocked bootloader? In service menu you should see
"Rooting status:
Boot loader unlocked: Yes"
if you doesn't see it, it means you haven't unlocked it or unlocking is not allowed on your device.
Diomorgan said:
Hi,
I made a different thread to find a solution about this error I got when I try to flash the Androkernel boot.im and TWRP recovery on my UNLOCKED BOOTLOADER Z4 712 wifi european tablet.
I updated with the Sony PC Companion tool, I DID NOT turn ofn the MySony Security (that was THE problem that caused this error last time), and bootloader is still unlocked (checked with Sony Mobile Flasher).
The service mode say "root:unknow", in previous tablets/room it should say "bootloader locked or unlocked", but I'm not sure.
That's what I got when I tri to flash boot.img:
Thank you for the help
Click to expand...
Click to collapse
Hi,
I think the problem is here if you enable myXperia before or after unlocking the bootloader ( can be @AndroPlus can explain better the problem ?)
Verify that your USB drivers for fastboot and adb are correcctly installed (install the USB drivers provided with Flashtool)
I hope you can root your tablet again :good:
I'm very sorry if I opened the thread here, feel free to close or move it, but I found it related the modding and , actually, in installing the androplus kernel.
As I said I did not turn on the sony security nor befor nor after, root status is "unknown", Flas Tool say is't unlocked, I already flashed the androkernel before and the problem was the MySony security, but now I know I don't have to turn it on.
Drivers are Ok, I flashed the new rom with Flash tool and then with Sony Companion.
Anyhow, if I'm bothering with this thread pleas close it, al try again and again
I think it's okey moderators will move the thread over.
Did you unlock your tablet by flashtool or follow official Sony instructions?
Do you have myxperia app installed?
Have you got factory reset after unlocking?
killdozer56 said:
Hi,
I think the problem is here if you enable myXperia before or after unlocking the bootloader ( can be @AndroPlus can explain better the problem ?)
Verify that your USB drivers for fastboot and adb are correcctly installed (install the USB drivers provided with Flashtool)
I hope you can root your tablet again :good:
Click to expand...
Click to collapse
alex009988 said:
I think it's okey moderators will move the thread over.
Did you unlock your tablet by flashtool or follow official Sony instructions? Official sony on previous firmware and flashtool say i'ts unloked
Do you have myxperia app installed? yes, but it's not enabled! Actually it's not an app, but an option in "security" menu.
Have you got factory reset after unlocking?
Click to expand...
Click to collapse
yes, I reinstalled the new rom with flashtool then with Sony Companion and root status is "unknown".I can try reflashing it tomorrow.maybe someway I got stuck in a unknow situation between locked and unlocked X-(
farfetch has beaten the same topic here to death.
same style:
many threads (unrelated to his topic)
look it up - it is not easy because of this
you will not like what you read:
you have bricked your tablet with enabling myXperia after unlocking the BL
DHGE said:
farfetch has beaten the same topic here to death.
same style:
many threads (unrelated to his topic)
look it up - it is not easy because of this
you will not like what you read:
you have bricked your tablet with enabling myXperia after unlocking the BL
Click to expand...
Click to collapse
First of all, I don't really understand how he was able to update something via pc companion with unlocked bootloader?
No ota update, nor update via pc companion is available after unlocking.
DHGE will we have the same? I mean when android MM will be released, we flash it and will it be with myxperia? And if we launch it by accident we break our tablet, right? In this case, how to remove it, factory reset?
alex009988 said:
First of all, I don't really understand how he was able to update something via pc companion with unlocked bootloader?
No ota update, nor update via pc companion is available after unlocking.
DHGE will we have the same? I mean when android MM will be released, we flash it and will it be with myxperia? And if we launch it by accident we break our tablet, right? In this case, how to remove it, factory reset?
Click to expand...
Click to collapse
I read about a guy thoblem because after updating with Companion bootloader was relocked, he unlocked again and so.
Anyhow,I just NOT UPDATED, but RESTORE/REFRESH the firmware flashed with Flashbout a bad flash with Flashtool. Immediately after the flash with compsnion,even without turning on the phone, I try and I got the same FAILED (remote: Command not allowed)
:crying:
I even relocked and reunlocked bootloader with Flashtool (didn't even know it's possible to relocked...).Thi lost :-/
UPDATE: I found that myxperia was administrator even if I didn't turn it on, so I remove from administrators, but....same problem
Maybe it's better to try to unlock bootloader again following official Sony instructions, not flashtool? WITH flashtool unlocking, you haven't got a factory reset, that's the reason of all your problems IMHO.
After unlocking my xperia must disappear.
alex009988 said:
I mean when android MM will be released, we flash it and will it be with myxperia?
And if we launch it by accident we break our tablet, right?
In this case, how to remove it, factory reset?
Click to expand...
Click to collapse
SONY thinks MyXperia is a useful feature security wise and I agree. It is just not for me since it prevents my tampering with the device.
I am sure it will be in MM.
You have to launch it explicitly on setup! SONY warns in the bootloader instructions to activate it after unlocking.
Once activated after unlocking the tablet is bricked. End of discussion, beaten to death in the xperia fora....
If a factory reset could revive the devices this would be no security feature but rather an annoyance for thieves.
DHGE said:
SONY thinks MyXperia is a useful feature security wise and I agree. It is just not for me since it prevents my tampering with the device.
I am sure it will be in MM.
You have to launch it explicitly on setup! SONY warns in the bootloader instructions to activate it after unlocking.
Once activated after unlocking the tablet is bricked. End of discussion, beaten to death in the xperia fora....
If a factory reset could revive the devices this would be no security feature but rather an annoyance for thieves.
Click to expand...
Click to collapse
I completely agree with what @DHGE said this is a no sense if a thief can reset the tablet with a factory reset once MyXperia has been activated. MyXepria operates at a low level, also be able to deactivate it easily is not possible.
:crying:
Oh my God.I haven't known it. http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html poor people. Indeed, with unlocked bootloader and enabled myxperia, people get tea-tray instead of working device. And it's unrecoverable.
If nevertheless icon of my xperia will appear in a menu of new MM. Can I delete it with some kind of system-app-uninstaller ?
Edit 1. This damned app was in my system, so I used "Uninstall" app and remove my xperia, wiped dalvik and cash.
I strongly recommend it everybody to keep your device safe and don't worry incidental pressing.Better delete it!!!
I activated myxperia with unlockebootloader and I have no problem, can't be able to unactivate it, when I reflash the ro if activate it or not and I can remove administrator priviledge in security section.
If I clickif I want to turn it on and sony says that "if turned on"repair the firmware but will be "unusable" till you imput your google account saved for the my'm UNLOCKED I try turning on myxperia a few days ago to an disable it later (no ways, my xperia has only a blank page without settings), then I reflashed 2 times and both time it asked me if I to turn on the myxperia.I even try with flashtools to chek the bootloader, relock and reunlock and everything wly problem is flashing things via fastboot!
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
EDIT:::: GO TO COMMENT 6, Solution for me was just waiting a couple of days(using legit method)
PIC:
http://imgur.com/a/38RsO
555satan said:
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
PIC:
http://imgur.com/a/38RsO
Click to expand...
Click to collapse
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Amirphp said:
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Click to expand...
Click to collapse
so basiclly just wait 11 days and then try again?
555satan said:
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
PIC:
http://imgur.com/a/38RsO
Click to expand...
Click to collapse
I have the same problem, I have tried countless times, but it would still show the same error, even though in the past I have performed this method countless times with 100% success rate, but now, idk why this error shows up.. I have a feeling that reinstalling the windows and then following the procedure again might solve the issue, but I dont wanna go through all that deleting and reinstalling stuff.
No need ro reinstalling windows.
Just install adb drivers and confirm u are using same sim card number in slot 1...which is used for login into mi account in phone and pc.
Amirphp said:
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Click to expand...
Click to collapse
Amirphp said:
No need ro reinstalling windows.
Just install adb drivers and confirm u are using same sim card number in slot 1...which is used for login into mi account in phone and pc.
Click to expand...
Click to collapse
i have all adb drivers installed and working(downloaded the clockwork ones so they are legit working), tried putting in the sim in slot 1 same issue.
it seems like a lot of people are having issues with that bootlocker, it's a shame i was happy to buy this device and now i regret every moment
EDIT:
today it worked, basiclly the solution is to wait, shame they dont mention it themself, no need to insert the sim
Hi guys, so I seem to have scewed up my phone quite badly. I tried to deodex running the new nougat firmware (with drm-fix and ric-off) by flashing a zip in the nougat firmware thread. Somehow I ended up with not being able to fastboot anymore.
I found out that my bootloader seems to be locked again. Thus I am not able to approach the fastboot mode, but failed to do any flash, as it says [FAILED (remote: not allowed)].
I checked the service menu and found the [Bootloader unlock allowed:no] and [Remote Lock State: Locked] after reflashing the nougat firmware.
So I wanted to unlock the device, how ever I ended up with flashing back to Lollipop and the device boots and then power off after a few seconds of use.
Could this due to "remote lock state: not allowed"?
Try relocking via flashtool?
So. Tried to lock and relock via flashtool. Checked drivers which are working fine.
I was trying to relock and then unlock again using flashtool after updating to .305 Marshmallow firmware . However this does nothing to the bootloader states. The weird thing is that there are no errors showing up in flashtool when unlocking/relocking. I can't even unlock via OEM because when I tick OEM unlock in the developer options this doesn't do any change (Rooting status: Bootloader unlock allowed : No, Remote Lock State: Locked). My DRM keys are gone as well. However I do have a TA Backup but can't restore because after downgrading to lollipop the device shuts down after 30 seconds.
I'm really annoyed because I bought the device with an locked bootloader (without carrier costumizations) and unlocked it via OEM unlock then updated to . Is there any chance to unlock the device again? Restore TA? Any recommendations what I could have done wrong would be helpful.
iArvee said:
Try relocking via flashtool?
Click to expand...
Click to collapse
[solved ] Bootloader is now sucessfully relocked andBootloader states are back to [Bootloader unlock allowed: Yes] and [Remote Lock State: UnLocked].
I need to mention that I bought a phone without carrier lock with [Bootloader unlock allowed: Yes].
So, for anyone who is interested or might face the issue in the future, here's what I did.
You will need your backed up TA-Partition-Image to restore via iovyroot:
1. Downgrade to Lollipop (32.0.A.6.200 / R2B (STOREFRONT GENERIC)) using Flashtool .
->Therfore select/tick everything in the wipe section when selecting the Lollipop-tft
2. Unmount your SIM, reboot the device
3. Skip everything on the welcome/configuration screen as fast as you can to get beyond the Android configuration screen
(skip wif config, Google-Account setup, untick myXperia services! etc.)
The phone might power off only after a few seconds because of the downgrade. So be fast!!!
4. Once you end up on the home screen, unlock developer options, and activate ADB debugging, grant ADB access (check via cmd: fastboot devices)
again: be fast! --> Don't worry if the phone shuts down again. Just reboot if you were not fast enough.
5. Download iovy.root ( iovy.root. Place TA-backup.img in the iovyroot-folder.
Then I modified "tarestore. bat" to save some time regarding the shutdowns. I used notepad++:
...
set response=
set /p response=Type "y" if you want to restore this file:
if "%response%" == "y" (
echo Starting restore
echo.
adb push "root/iovyroot" "/data/local/tmp/iovyroot" > NUL 2> NUL
adb push "root/restore.sh" "/data/local/tmp/restore.sh" > NUL 2> NUL
...
5. Run CMD as admin. CD to Iovyroot folder.
Restore using tarestore.bat (tarestore.bat TA-2016-xxx.img) as soon as your device boots up to home screen and seems to be connected as ADB device.
( I checked this by running the windows device manager simultaniously)
Wait to end the process.
-->When the restore was sucessfull, the device shouldn't shutdown again.
6. Reboot. Your bootloader is now locked again (but able to unlock via OEM unlock). DRM keys/functionality is restored.
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
When I faced this problem I noticed it happened because I wiped TA options with Flashtool. Never do that if you don't want to lose TA partition and all other things connected to it. I could fix it only by flashing TA backup even though I hadn't the timing issue zegovernator had for flashing back TA.
I actually wonder why Flashtool allows to wipe these critical partitions/options
ric69 said:
Same case here z5c unlocked since +/- 1 year and I don't have any TAbackup too
I will try to downgrade to .200 But with bootloader unlock allowed : no ... I don't have much hope
edit : no chance, I tried .200 but without tabackup, I can't do nothing
Click to expand...
Click to collapse
I'm sorry for you. I would recommend updating back to MM since LP gives you immediate shut downs when recognising that your TA is lost/wiped. It's sometime a pain in the ass that stuff gets posted before testing. Nonetheless, you could still try to send in your device back to Sony Costumer Service if you are under warranty (after flashing .200, say that it is "broken" and keeps crashing). However, I would not trust on them sending you a new device.
jutphaas said:
I have the same problem (after i had nougat working incl drm fix and root, also the deodex, tried flashing lower ftf files too when i got this problem, noticed the rebooting, which it does not do at 305 kernel or higher..
I would have hope in your solution, if I could find my ta backups (i have from some other phones, this one, may have been on a crashed laptop, already searched through old hdds)
Could this be because of fastboot flash recovery twrp.img (cause that is something i never done before on the z5c.)
If anyone has a solution other than restoring the ta partition, i would like to know. Because i am very uncertain that i can find those files again...
Click to expand...
Click to collapse
I sorry to say that, but if you lost your TA-backup or didn't even back it up before unlocking the bootloader there is no hope at the moment. You simply can't fastboot because of the Remote State: Locked. It keeps you from accessing the bootloader.
I found my iovyroot TA-backup.img file, I did have a .200 storefront ftf and tried it on that one, which was very anoying as it wants to start a demo , i found an other .200 ftf online which I tried, and the iovyroot seems to work, at that time no reboot, in service menu, the drm keys now seem fine there, Bootloader unlock allowed : No, Remote Lock State: unLocked , fastboot boot or oem unlock still seemed not working well i think that is what it said, (flashtool unlock always seems to, i did try) now i flash a new ftf and try my luck there with the unlock status.
flashing ftf 5.11 flashtool says
03/005/2017 05:05:49 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2_119 / Bootloader status : ROOTED
And now in 5.11 it also says bootloader unlocked : Yes Lost my drm again
So I am back in flashing and rooting (with drmfix etc) Android 7 again Thanks for sharing this solution!!
So you confirm that TA backup is the only solution to solve the "unlock allowed" bad state, don't you?
This is good for other people because when I faced the problem I was really scared to have messed up my phone!!!
i want to confirm the solution here
i had the same problem and the only way back of it was to downgrade to Lollipop and restore the TA-Partition
i dont think there is a solution if you did not backup your TA and have an image of it.
Yes, the TA restore is the only known solution, and I am glad Zegovernator shared his solution here