So. I would like to unlock the bootloader. All fine, I get the code, and when I type in
Code:
fastboot -i 0xfce oem unlock 0xcodehere
it says
Code:
FAILED: Command did not succeed.
However, when I do it the second time (enter the command right again) it says OKAY but the device will end up on a bootloop next start, and when I try to flash a kernel, it says not allowed.(fastboot) If I flash when unlocked without restarting device, the device will shut down at SONY logo. Is it possible that I got a temporary unlock? How could I unlock the device successfully?(permanently) I tried it with Flashtool, and the same results. I literally tried everything. I also cannot install the permanent OS-independent CWM because of the shutdown at the SONY logo. I didn't yet contact my service provider, but I don't think they would like the idea. I really want CyanogenMod on my device, and I'd also like to fix some problems if I can. Please try to help ASAP. Thanks!
Code:
C:\Users\Felix>fastboot devices
e46fc864 fastboot
C:\Users\Felix>fastboot getvar version
version: 0.5
finished. total time: 0.000s
C:\Users\Felix>fastboot -i 0xfce oem unlock 0xCODEHERE
...
FAILED (remote: Command did not succeed)
finished. total time: 0.162s
C:\Users\Felix>
I have the same problem. Did you resolve it?
Open Phone and dial *#*#7378423#*#* go to Service Info->Configuration if Rooting Status says Bootloader unlock allow: No you can't unlock it. If it says Yes go to Sony's official website for unlocking and follow the instructions.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4
Related
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 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.
Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.
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
Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed
NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something
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: