ive a xperia m2 d2303
I previously ran a bootloader unlock via sony this worked fine
I then had to relock the boot loader
this is were my current problem lies I did this on a computer I no longer own.
if I look in the service menu is shows I can unlock the bootloader but when I try I get an error.
I then try
fastboot -i 0x0fce oem unlock mykey
mykey is unlock key provided I get this error
FAILED (remote: Command did not succeed)
finished. total time: 0.100s
or
FAILED (remote: Device is already rooted)
finished. total time: -0.000s
does this mean its already unlocked or is there something im doing wrong any help appreciated
thanks
Open Service Menu, service info, configuration /
If Rooting Status says Yes
You are unlocked.
Xperia M2 D2303 on K.K. 4.4.4
So I've pretty much hit a wall. I have unlocked bootoader, and everytime I try to enter into factory resetting via volume + power button, it'll boot into "your device is booting now..." and it'll stay there. Same thing if I try to do it via the settings.
Whenever I try to install custom recovery or anything, I get this message.
C:\adb>fastboot flash recovery TWRP-CN.img
target reported max download size of 471859200 bytes
sending 'recovery' (29218 KB)...
OKAY [ 0.789s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.804s
I've tried all sorts of twrp files. My phone has locked me out of changing anything from adb commands it seems. How do I fix this?
My FRP is also locked, if that matters. I've tried to delete all accounts from my phone, as well as the "find my phone" option.
I'm on Anroid 7, EMUI 5.
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot devices
73QDU16B22001173 fastboot
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (remote: Command not allowed)
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format cache
FAILED (remote: Command not allowed)
OEM is greyed out in the developer settings, I can't activate it or decative.
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
TomboIa said:
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
Click to expand...
Click to collapse
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Zebieok said:
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Click to expand...
Click to collapse
Dont share your unlock key here, and are you sure that was your bootloader unlock keys.
Frp lock means your bootloader is locked.
FRP lock is a security action, for remove them you must boot a device and remove all google accounts.
Unfortunately this casw happened to me, when i want factory reset my phone, his dead and i cant boot it again just fastboot work but FRP LOCK activate and i cant flash any thing, give error command not allowed, in last i have to go to repair services, and they do this with hard box (maybe chimera or sigma.. Or other).
If you can boot your device you can do any thing, but if your device get bootloop go to services center.
When i've try to unlock bootloader via minimal adb and fastboot..i reboot my device to bootloader use the command ( adb reboot bootloader ) but i try to type this command (fastboot oem unlock ) why always unknown comand or device is lock ..same thing with i use (fastboot flashing unlock)..anybody..if u can solve this thing..please help me..
bootloader unlock failed in vivo y65
..
FAILED (remote: unclock fail.)
finished. total time: 0.015s . This always comes when i use fastboot bbk unlock_vivo. Help me solving this problem plz
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying:
I've been trying for awhile now to unlock the bootloader on my AGM M5. It is running on a simplified Android 8.1. I've enabled USB debugging and have enabled Bootloader Unlocking in settings. ADB works fine but I cannot get the bootloader to unlock when I run the following commands.
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\platform-tools>fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: -0.000s
I've tried running them from several different devices. Windows 7, Windows 10, and Raspberry Pi. But they all gave me very similar results.
If someone could give me some help it would be great. I'll mention right here that my ending goal is to install Postmarket OS. So if this is totally an unnecessary step please let me know. The reason for this step was I was trying to get a boot.img from the device and I wanted to install TWRP. But I was running up against every direction it tried and all my research was yielding very little as it seems that my M5 is not a very popular device.