Hello, i got a question if some one more has this problem, when i try to unlock the bootload from sonys site,
http://developer.sonymobile.com/unlockbootloader/
when i use fastboot devices i found my device.
Next step is the code for the unlockboot load
C:\sdk\platform-tools>fastboot -i 0x0fce oem unlock ***************
...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
C:\sdk\platform-tools>but why do i get FAILED commando not allowed some one know the answer please help me.
oem unlock
you must in developer setings allow "unlock oem"
GameboyZA said:
you must in developer setings allow "unlock oem"
Click to expand...
Click to collapse
And turn off my Xperia
Sent from my Xperia XA using XDA Labs
His bootloader could be carrier locked the even changing oem unlock it will still not unlock and will give error
Sent from my F8131 using Tapatalk
GameboyZA said:
you must in developer setings allow "unlock oem"
Click to expand...
Click to collapse
i think that will work the settings was off, so i will try again to day
i just tried this to day and now i got this error
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Related
So i followed the directions by first unlocking it and than rooting it... the nexus never gave me that gui screen i see in all the videos saying that the device is being unlocked yet i do have files in a folder "iReadyToFlash" but nothings worked so far... anyone have any ideas?
What directions are you following? What video are you referring to?
Are you getting any error message? If so, at what step? What have you done so far?
setox said:
So i followed the directions by first unlocking it and than rooting it... the nexus never gave me that gui screen i see in all the videos saying that the device is being unlocked yet i do have files in a folder "iReadyToFlash" but nothings worked so far... anyone have any ideas?
Click to expand...
Click to collapse
My device didn't confirm root either, but after the system booted I checked and it surely worked. Have you confirmed that you indeed do not have root?
I was following the directions from the Nexus Root Toolkit. I am not getting any error messages but i do follow the steps but its still not letting me unlock the boot loader so i can unlock it.
I am on LMY48M right now. i just really want to restore all my stuff from titanium back up from my galaxy s5.
I've seen in a few videos that people get a unlocked boot loader gui that comes up but that never occurred.
blyndfyre said:
My device didn't confirm root either, but after the system booted I checked and it surely worked. Have you confirmed that you indeed do not have root?
Click to expand...
Click to collapse
what method did you use to obtain root? and titanium backup is what i use to confirm root
setox said:
what method did you use to obtain root? and titanium backup is what i use to confirm root
Click to expand...
Click to collapse
CF-ROOT and I used ES File Explorer to confirm root access.
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
FAILED (remote failure)
finished. total time: 0.407s
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
nope didn't work
by the way i am on project fi
Did you hit the slider in dev options on the phone to allow unlock?
what slider?
setox said:
what slider?
Click to expand...
Click to collapse
You have to enable "OEM Unlocking" in Settings - Developer Options.
Screenshot
RMarkwald said:
You have to enable "OEM Unlocking" in Settings - Developer Options.
Screenshot
Click to expand...
Click to collapse
YES!!!! that did it....
Same occurrence. Root not stick.
setox said:
So i followed the directions by first unlocking it and than rooting it... the nexus never gave me that gui screen i see in all the videos saying that the device is being unlocked yet i do have files in a folder "iReadyToFlash" but nothings worked so far... anyone have any ideas?
Click to expand...
Click to collapse
Any resolution? Ray6279
I'm hoping someone can help:
I've been rooting/unlocking android phones for years. I've run Linux as my desktop OS for 15 years and I'm used to using fastboot.
I've had an Xperia Zr for a few years and when I saw them new on Ebay new for <$100 I bought another one.
So the first thing I try and do is unlock the bootloader, I have done this on several phones, including the ZR I use as my main phone.
I get the IMEI off the back of the phone and make sure it's the same as the one I get when I *#*#SERVICE#*#* and it is.
In Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes
I go to sony and get the unlock code for that IMEI (I've done this 4 times, it's always the same, I've double checked all the fields).
When I enter the command from fastboot to unlock the bootloader I get this:
[email protected]:/media/rolf/Data/Android$ sudo fastboot -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.598s]
finished. total time: 1.598s
So no error, it looks like it worked. When I reboot the phone it's like new again it wiped itself as it does after you unlock the bootloader.
But when I go back to Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes , but it should now say bootloader unlocked.
When I go back to fastboot and try and flash anything it behaves like it still locked.
[email protected]:/media/rolf/Data/Android$ sudo fastboot flash recovery cm-13.0-20160930-NIGHTLY-dogo-recovery.img
sending 'recovery' (11570 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
The phones both look identical, the new one looks genuine, the FCC ID and model number and Type are the same. The old phone was made in the 25th week of 2013 the new one is 30th week 2014.
Does anyone have any idea what is going on?
Thanks,
Rolf
Use flashtool to unlock bootloader.maybe this will work.I used flashtool to unlock my zr bootloader easily.
Flashtool is just a way for people who don't use the command line to issue commands.
Just to be sure I installed it under Linux and Windows and tried the bootloader unlock from there with the same results on both OSs.
01/004/2016 11:04:58 - INFO - Device connected in fastboot mode
01/007/2016 11:07:45 - INFO - Unlocking phone using key 3214A89EDE406752
01/007/2016 11:07:47 - INFO - ...
01/007/2016 11:07:47 - INFO - OKAY [ 1.385s]
01/007/2016 11:07:47 - INFO - finished. total time: 1.385s
01/007/2016 11:07:47 - INFO - Device will reboot into system now
01/007/2016 11:07:47 - INFO - Unlock code saved to C:\Users\rolf\.flashTool\registeredDevices\EP74168AM1\ulcode.txt
01/007/2016 11:07:47 - INFO - Device disconnected
Like when I use fastboot directly the device factory resets itself but remains a locked bootloader.
Has anyone ever seen a phone that says Bootloader unlock allowed: Yes but when you issue the command it fails silently?
Just to be sure, I have tried many different versions of flashtool. I have also tried using the wrong key to see what happens.
If I change the last digit of the unlock code then the command fails.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406751
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
If I give the correct unlock code the command succeeds, but the phone never unlocks.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.569s]
finished. total time: 1.569s
I've tried using 2 different computers now so I have ruled out the computer hardware or software.
It seems to be the phone, this one is made in Malaysia the other one does not say where it was made.
Does anyone have any ideas?
This won't happen if your zr isn't carrier locked.So check it otherwise i'm unable to help you.Here are some great members in zr community can help you with this wired problem.PM with daedroza or sigprof.without PM it's not hard to get help from great members.
Never seen something like this, so the following is mostly a guesswork…
What ROM do you currently have on this phone, and did you reflash it? In theory it's possible that some strange (carrier-specific) ROM version relocks the bootloader during boot; another possibility is that the unlocking process is broken with some bootloader versions. Because creating the TA backup before unlocking needs root, I used old ROMs when unlocking — maybe even something ancient like 10.3.1.A.2.67, which can be rooted with opensource rootkitZ, and definitely not something which requires the malware-infested King Root. So flashing a stock ROM with a different bootloader version may help (the bootloader version number in boot_delivery.xml inside FTF must be different from the installed verson, otherwise flashtool will skip the bootloader parts when flashing — e.g., 10.6.x and 10.7.x stock ROMs have the same VERSION="1264-2309 S1_Boot_Lagan_1.1_10").
Thank you for some excellent advice. I had already re-flashed 5.1.1 with no change, so I tried 5.0.1 and there was also no change.
I found the oldest KitKat Rom I could and flashed that, as before the bootloader unlock command appeared to have worked but this time it rebooted into a boot loop.
I dropped back into fastboot and was able to flash a new boot.img and installing cm13 was quick and easy. The bootloader now shows as unlocked in SERVICE.
What software did you use to flash an old rom?
Hi guys!
I'm having a problem.
I'm trying to unlock my bl but the toggle(as the title says) does not appear. So when I try to unlock via adb or flashtool I got this error:
27/021/2018 11:21:07 - INFO - finished. total time: 0.063s
27/021/2018 11:21:07 - WARN - Maybe the OEM is not enabled
and on adb I got the same thing.
Does anybody know how to solve this?
I just want to update to oreo
Thanks in anticipation
Many Z3c tablets don't have the ability to have their bootloader unlocked. I'm in Canada, and this tablet was sold through Rogers, and I have the same issue. There's no workaround, you're stuck with stock.
I had this on Z4 Tablet. Solved when I go to Developer's options and set ON the option which allows to unlock Boot Loader.
sammywtf said:
Hi guys!
I'm having a problem.
I'm trying to unlock my bl but the toggle(as the title says) does not appear. So when I try to unlock via adb or flashtool I got this error:
27/021/2018 11:21:07 - INFO - finished. total time: 0.063s
27/021/2018 11:21:07 - WARN - Maybe the OEM is not enabled
and on adb I got the same thing.
Does anybody know how to solve this?
I just want to update to oreo
Thanks in anticipation
Click to expand...
Click to collapse
I had the same problem I can't toggle the
When I go to Developer Options -> enable the OEM Unlock, I got the attached image (OEM Unlock blocked!)
And when I go to fastboot I got:
C:\ADB_FASTBOOT>fastboot oem unlock MYNUMBER
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
Finished. Total time: 0.012s
So I am in a dead end.
How to solve this?
Ps: factory reset did not resolve this...
That is interesting. Does it stay gray after a reboot?
This will definitely tell if you can even unlock it. https://motorola-global-portal.cust.../unlock-your-device-a?utm_source=ausdroid.net
Neffy27 said:
That is interesting. Does it stay gray after a reboot?
This will definitely tell if you can even unlock it. https://motorola-global-portal.cust.../unlock-your-device-a?utm_source=ausdroid.net
Click to expand...
Click to collapse
It stay gray after reboot.
I got "MYNUMBER" from this site. I received it in my email but no success in unlock.
After 72 hours (more or less) after buying the cellphone, it activated alone...
Now I can unlock the bootloader.
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
lm8lm8 said:
Hi guys
I just succeed to unlock with potatoNV my ale L21.
but, its looks like there is no twrp for the 2015 version?
Im having this last one and it looks like 99% of xda regarding ale_L21/p8Lite towards 2017 version.
Isnt it possible to know how to switch to twrp/lineage with 2015 hw version?
I tried lot of twrp files regarding "looks like" 2017 ver (none says 2015, so I guess it's 2017):
FAILED (remote: image verification error)
fastboot oem lock-state info
...
(bootloader) FB LockState: UNLOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.000s]
finished. total time: 0.000s
I thank you vm
Click to expand...
Click to collapse
I run into the same problem and managed to fix this. You have to run the potatoNV again, keeping the testpoint shorten during the reboot, and DO NOT check the "unlock FB" checkbox this time. This checkbox actually effectively locks the bootloader.