Hello all,
I've got an Arc S that I've been trying to unlock the bootloader on using Sony's method, without success.
1. I have fastboot and adb installed on my machine (Linux Mint 14 32bit)
2. I've pulled the unlock code from Sony's website
3. I set my udev rules as laid out in this tutorial.
4. I have checked my bootloader to confirm that it can be unlocked (and currently is locked)
5. Fastboot is working (When I type in sudo fastboot devices, I get a hexadecimal string in response)
6. However, when I try to unlock, it always fails.
Initially, it gave me a "oem unlock failure code". After I rebooted thought, the code changed. Instead of something like this
Code:
oem unlock failed!
it gave me this
Code:
...
and did nothing. I let it sit for a few minutes and then forcibly shut down terminal, no damage done to the phone.
I'm quite confused at this point. From all my google searching I can't figure out why the booloader won't unlock. I'm pretty sure that I have the right unlock code.
A second and curious thing that may or may not be related is that the phone is rooted, but when I tried to transfer CWM via fastboot it threw an error, saying that the phone needed to be rooted first. However, it is rooted and apps such as Titanium Backup work just fine, verifying the root. Can anyone give me some direction on this?
I know there is a video on the how to unlock lt18i bootloader. It also has step by step process on fixing issues for unlocking bootloader. Lemme get.it for ya.
Sent from my LT18i using xda premium
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
I don't believe that it is simlocked. I don't believe the phone was purchased through a carrier. For clarification, this is a friend's phone so I would need to ask them as to where they purchased it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Someguyfromhell said:
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Click to expand...
Click to collapse
As taken from the Cyanogenmod Wiki page for Anzu devices:
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY was the bootloader unlock I received from Sony.
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
MarcSinger said:
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
Click to expand...
Click to collapse
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Guanfy said:
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Click to expand...
Click to collapse
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
MarcSinger said:
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
Click to expand...
Click to collapse
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Guanfy said:
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Click to expand...
Click to collapse
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Someguyfromhell said:
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Click to expand...
Click to collapse
Yup, that I have. I originally entered the 15 digit code and the website threw an error, so I deleted the last digit to get the unlock code that I tried.
same issue as LT26ii
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
nkiy said:
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
Click to expand...
Click to collapse
oem unlock failed
Problem solved!
Hey guys, I just unlocked my LT26ii after many times of "oem unlock failed". Here's my solution:
0. well first just remember your IMEI code, cause later it will changed.
1. Download a new firmware in ftf format.
2. Update firmware with Flashtool.
3. Turn on your phone and get you imei code. Now you should got a new one different from the previous one.
4. Use the NEW imei to unlock your phone.
Good Luck !
PS: dont guarantee that worked but if it does please let'me know.
Hi everyone. My device just came back from lg, and apparently I've got a brand new mother board. There is a problem though: my rpmb is gone (fastboot states "no rpmb" right next to the secure boot string), and I guess that is what makes my device fail to unlock its bootloader. Now, doing a little searching on the net, what I get is that really little people also encountered this problem, and ALL of them seem to have sent their device to lg from Italy (as have I). Have I got any chance to fix it? Or maybe just take it back to lg for a check? What could I possibly say to them?
Note that I know pretty well how to unlock bootloaders under normal circumstances, as I have already unlocked many nexus devices of mine in the past, so that is not the problem.
Hey there! I found a solution to get root access, here's my post on Reddit about it:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
Hope this helps!
hello, good morning, this is my first topic, I do not know if I'm posting in the correct location, if not, please correct me.
I bought a moto z2 play and a camera error resulted in a big problem, first asked to restart and so I did, the second time came the problem, it just does not stay more than 3 seconds on the welcome screen, I already tried hard reset , I already installed another stock, already tried to start in safe mode and nothing, unlocking oem and debugging usb are disabled, I contacted the motorola to ask the unlock code oem for the code obtained by fastboot and they told me that it would not be possible give me such a code, and now, is there anything I can do?
This doesn't seem to be a modding problem, looks more like hardware... so I'd strongly reccomend you NOT to void your warranty by unlocking bootloader. Send it to an official repair center and hope they either fix or replace the phone...
Purchased this phone in this condition. It is a US unlocked model SM-N975U1.
When the phone boots the screen immediately goes to locked screen stating "Phone locked: This phone can't be used without authorization (0001)". so I am unable to get into Dev. Options to look at anything.
From searching on here there are not a lot of solutions to get past this and the ones I have found involve flashing the Combo/Eng ROM which is not possible anymore without the Samsung token/permission. And on this phone I can't flash anything because of the KG Locked condition not allowing anything to be flashed. "All binaries are not allowed to be flashed due to KG Locked"
Does anybody know what can be done?
Ready to just swap out the main board and be done with it.
Thanks in advance.
Added pics but the site seems to be having problems showing them.
The only thing I can say to you, is this, problems as the one you are exposing here, always are somewhat unsolvable due to the device having a shady or dubious history, legally obtained devices, are always easy to fix by official channels, you will not get any help to unlock or crack the security of any device here in XDA
Hey,
My first time posting here. A little context first.
This is a phone that I bought faulty from eBay, that the seller stated had belonged to their mum and they were selling it on their behalf. How true that is I don't know, as i've encountered this error.
I thought it would be a simple fix of using Xperia Companion, however that returns a 'UEUpdateFailed' error, ue_2005
I have tried tools such as Flashtool, however they won't work without the bootloader unlocked, and due to not being able to turn the device on properly I can't get into developer options.
I have also given Sony Emma a shot, however that also states that my phone is locked and says about unlocking my bootloader.
Due to the age of the device I don't expect a reply, but it'd be great to get this device fixed if it's possible.
Many thanks in advance,
Jared