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
Related
Hi. I had bootloader unlocked while I had android 4.3 without any problem but PC Companion didn't let me install 4.4.2 with bootloader unlocked so I had to relock it. After that I installed KitKat without any problem and have tried to unlock bootloader again doing same steps as before but unsuccesfull. The message I get was something like "your device is already rooted" but is not. Also the bootloader is locked for sure. What can I do to sort this out?
wmichniewski said:
Hi. I had bootloader unlocked while I had android 4.3 without any problem but PC Companion didn't let me install 4.4.2 with bootloader unlocked so I had to relock it. After that I installed KitKat without any problem and have tried to unlock bootloader again doing same steps as before but unsuccesfull. The message I get was something like "your device is already rooted" but is not. Also the bootloader is locked for sure. What can I do to sort this out?
Click to expand...
Click to collapse
Dial *#*#7378423#*#*
goto service info then configuration and tell me what it says about the bootloader
bootloader unlock allowed: Yes
Follow instyructions from here
http://unlockbootloader.sonymobile.com/instructions
and post the output of the command window
I did it already. The message I get was 'your device is already rooted'
wmichniewski said:
I did it already. The message I get was 'your device is already rooted'
Click to expand...
Click to collapse
I know it may be painful, but please do try it again and copy and past the content of the command window here.
Please.
After I did it first time the message I get was:
FAILED (remote: Command did not succed)
finished. total time: 0.018s
so I tried to do it again and the message is different:
FAILES (remote: device is already rooted)
finished. total time: 0.004s
wmichniewski said:
After I did it first time the message I get was:
FAILED (remote: Command did not succed)
finished. total time: 0.018s
so I tried to do it again and the message is different:
FAILES (remote: device is already rooted)
finished. total time: 0.004s
Click to expand...
Click to collapse
Did you make a TA backup?
If so, restore it and try again.
If not, flash a stock FTF of your choice, reboot and tell me what it says in service info configuration again
when I can get ftf stock rom from and should I flash it with flashtool. After I do it my phone is gonna be on factory settings and I'm gonna lose all data ?
wmichniewski said:
when I can get ftf stock rom from and should I flash it with flashtool. After I do it my phone is gonna be on factory settings and I'm gonna lose all data ?
Click to expand...
Click to collapse
From the FTF thread in the general section
You lose all data when unlocking bootloader anyway, (You must know this if you read the instructions)
Did you make a TA backup?
Do not have TA backup.
wmichniewski said:
Do not have TA backup.
Click to expand...
Click to collapse
well its a very good job you have not unlocked the bootloader then
follow this guide http://forum.xda-developers.com/showthread.php?t=2449244 to backup your TA
Downgrade to a rootable FTF, root using any means you are familiar with (Doomlord easy root kit or Bin4rys root many android method, just google them)
then backup your TA
then tell me when you have done that
In the meantime ensure you have read the instructions and all the information about unlocking properly as you seem not to have done that yet (From you not knowing you will lose data)
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
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
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 There,
im new here and wish to say hello to you all.
i read a lot of threads but nothing is my specific problem.
I unlocked my bootloader and rooted my 5c under Android 6. Then, the nougat 7 update came in and now i got the following problem:
when entering fastboot to flash twrp-recovery, my honor says "PHONE Unlocked FRP Lock" and the oem-unlock-trigger under developer options is in OFF-position and greyed out with no possibility to enable it.
When i try flashing recovery i always get the message
target reported max download size of 471859200 bytes
sending 'recovery' (21942 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
i think, that this toggle has to be in ON-position to be able to flash. Bootloader is unlocked
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
Any suggestion or help for me? I need my root access but i'm not able to get it and don't know whats the exact problem. Already tried disabling all screen-locks and thins i read in other posts but nothing worked.
youre on twrp right? if you are thn you need flash stock recovery (extract from B100 firmware)
thelous said:
youre on twrp right? if you are thn you need flash stock recovery (extract from B100 firmware)
Click to expand...
Click to collapse
no, thats the problem. under android 6 i was on twrp and rooted, then updated to nougat. after update twrp was gone but bootloader stayed unlocked and oem-unlock in developers mode is greyed out in off-position.
Now i want to flash twrp-recovery againg, but command not allowed
Nobody here with an idea?
weini1980 said:
Nobody here with an idea?
Click to expand...
Click to collapse
install B100 firmware thru DLOAD folder...
thelous said:
install B100 firmware thru DLOAD folder...
Click to expand...
Click to collapse
where can i get it?
am i back then on android 6?
is it the only way to enable "oem unlock button"?
whats the exact problem? Why this happened to me after update to 7?
Thanx in advance
weini1980 said:
where can i get it?
am i back then on android 6?
is it the only way to enable "oem unlock button"?
whats the exact problem? Why this happened to me after update to 7?
Thanx in advance
Click to expand...
Click to collapse
you can find it from huawei's site, im not sure why it happend to you, just start from B100 firmware again that solves 90% of problems when modding stuff
Hey,
still the same problem. can't find software. any link?
clear credentials greyed out too. oem unlocking greyed out too. need this so badly. any idea?
I can solve this issue
weini1980 said:
Hey,
still the same problem. can't find software. any link?
clear credentials greyed out too. oem unlocking greyed out too. need this so badly. any idea?
Click to expand...
Click to collapse
here is the link search the required firmware
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
download only the zip which has status as full.
But , emui 5 has 3 zips even for full update
weini1980 said:
Hi There,
im new here and wish to say hello to you all.
i read a lot of threads but nothing is my specific problem.
I unlocked my bootloader and rooted my 5c under Android 6. Then, the nougat 7 update came in and now i got the following problem:
when entering fastboot to flash twrp-recovery, my honor says "PHONE Unlocked FRP Lock" and the oem-unlock-trigger under developer options is in OFF-position and greyed out with no possibility to enable it.
When i try flashing recovery i always get the message
target reported max download size of 471859200 bytes
sending 'recovery' (21942 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.587s
i think, that this toggle has to be in ON-position to be able to flash. Bootloader is unlocked
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
Any suggestion or help for me? I need my root access but i'm not able to get it and don't know whats the exact problem. Already tried disabling all screen-locks and thins i read in other posts but nothing worked.
Click to expand...
Click to collapse
Hey dude, first fastboot oem relock, and then unlock, it should help you 100%, i promise, just try.
SCUZZY1337 said:
Hey dude, first fastboot oem relock, and then unlock, it should help you 100%, i promise, just try.
Click to expand...
Click to collapse
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
weini1980 said:
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
Click to expand...
Click to collapse
first of all, you have to relock your BL, then unlock man.
weini1980 said:
No dude, doesn't work. Command not allowed. Bootloader is unlocked but because of this behaviour i'm not able to flash SuperSU ...
Click to expand...
Click to collapse
You have to find a way to turn the FRP off.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
You have to find a way to turn the FRP off.
Click to expand...
Click to collapse
It's easyyyyy, just relock the bootloader and then unlock it again!
gopinaidu77 said:
U cant unlock if frp locked
Click to expand...
Click to collapse
If FRP locked, you have to enable OEM Unlock function, then relock and unlock bootloader. It works, i mean it worked for me correctly.
SCUZZY1337 said:
If FRP locked, you have to enable OEM Unlock function, then relock and unlock bootloader. It works, i mean it worked for me correctly.
Click to expand...
Click to collapse
To be frank , i really dont know why i see frp unlocked or locked status .