Related
Good Afternoon,
I want to install cyanogenmod 10.1 on my xperia arc S. tried to follow a tutorial, but when it came to the part of booting the device in recovery mode I found that my bootloader was locked. Apparently, on the Rooting Status it says: bootloader unlock allowed: NO. So, my question is, what should I do in order to unlock the bootloader and install the cyanogenmod. thank you vm for your time.
Bernardo.
BernardoCalhanas said:
Good Afternoon,
I want to install cyanogenmod 10.1 on my xperia arc S. tried to follow a tutorial, but when it came to the part of booting the device in recovery mode I found that my bootloader was locked. Apparently, on the Rooting Status it says: bootloader unlock allowed: NO. So, my question is, what should I do in order to unlock the bootloader and install the cyanogenmod. thank you vm for your time.
Bernardo.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1034087
izida said:
Try this http://forum.xda-developers.com/showthread.php?t=1034087
Click to expand...
Click to collapse
I'm having problems downloading the -32/64bit drivers
izida said:
Try this http://forum.xda-developers.com/showthread.php?t=1034087
Click to expand...
Click to collapse
http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
found this, but cannot get into fastboot
I'm pretty sure that if you are not allowed to unlock it, there is no way to unlock it.
Edit: Ok maybe i was wrong. Take a look at this Thread -> http://forum.xda-developers.com/showthread.php?t=2102783
Edit2: Found a guide...but looks like you have to pay to unlock it. http://forum.xda-developers.com/showthread.php?t=1896553
Keksdroid said:
I'm pretty sure that if you are not allowed to unlock it, there is no way to unlock it.
Edit: Ok maybe i was wrong. Take a look at this Thread -> http://forum.xda-developers.com/showthread.php?t=2102783
Edit2: Found a guide...but looks like you have to pay to unlock it. http://forum.xda-developers.com/showthread.php?t=1896553
Click to expand...
Click to collapse
then there is no free way of doing this?
Cant Unlock Bootloader
Dear Sir
i Have Done all Instructions But It shows failed pls find below details.. please hellp me as soon as possible
Dear syed h done all what you mentioned but it shows error.. please find bellow.. and please reply me as soon as possible...
Microsoft Windows XP [Version 5.1.2600]
C:\Documents and Settings\ssubramanian>cd desktop
C:\Documents and Settings\ssubramanian\Desktop>cd flash boot
C:\Documents and Settings\ssubramanian\Desktop\flash boot>cd fast boot
C:\Documents and Settings\ssubramanian\Desktop\flash boot\fast boot>cd fastboot
C:\Documents and Settings\ssubramanian\Desktop\flash boot\fast boot\fastboot>fas
tboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: -0.000s
C:\Documents and Settings\ssubramanian\Desktop\flash boot\fast boot\fastboot>fas
tboot.exe -i 0x0fce oem unlock 0xDDA4329E6C449072
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.016s
Check if you wrote the code correctly.
I too have a Sony Ericsson (pro) with bootloader unlock allowed: NO. I've scoured the Web and only come up with this site http://www.wotanserver.com/en/sony-ericsson/xperia-pro-mk16/unlock-tool/debranding-flash
Which claims that if I pay 7.99 euros I'll be able to unlock my bootloader. My question is what am I paying 7.99 for? What does this service give that can't be found out for free?
engmex said:
I too have a Sony Ericsson (pro) with bootloader unlock allowed: NO. I've scoured the Web and only come up with this site http://www.wotanserver.com/en/sony-ericsson/xperia-pro-mk16/unlock-tool/debranding-flash
Which claims that if I pay 7.99 euros I'll be able to unlock my bootloader. My question is what am I paying 7.99 for? What does this service give that I can't be found out for free?
Click to expand...
Click to collapse
It works only if your phone is manufactured before 12W11. Check it under the battery.
your phone it is simlock ? you ned unlocked the be able to unlock the bootloader
http://forum.xda-developers.com/show....php?t=2102783
I am having problems in unlocking my xperia arc s lt18i boot loader. I have tried every sungle method of unlocking bootloader. my phone shows Boot loader allowed: yes and it is not sim locked as well. I am using the correct IMEI code and I have got correct unlock code from sony and still I am getting error remote: oem unlock failed. Help!! Help!! Help!! Please!!!
shehrozlt18i said:
I am having problems in unlocking my xperia arc s lt18i boot loader. I have tried every sungle method of unlocking bootloader. my phone shows Boot loader allowed: yes and it is not sim locked as well. I am using the correct IMEI code and I have got correct unlock code from sony and still I am getting error remote: oem unlock failed. Help!! Help!! Help!! Please!!!
Click to expand...
Click to collapse
okay this problem have many other of my friends. in 99.9 % i requested a new code from sony website & it all worked :good:
also check in the cmd window if the divice is connected before trying to unlock!
bejunk said:
okay this problem have many other of my friends. in 99.9 % i requested a new code from sony website & it all worked :good:
also check in the cmd window if the divice is connected before trying to unlock!
Click to expand...
Click to collapse
Actually I have tried every single thing and everytime I ask for a new code I get the same code as before from sony and I have installed proper drivers as well because it states that my device is connected
shehrozlt18i said:
Actually I have tried every single thing and everytime I ask for a new code I get the same code as before from sony and I have installed proper drivers as well because it states that my device is connected
Click to expand...
Click to collapse
i dont be rude bro, but i had this situatzion atleast over 20 times here with friends or others from my country (then i done the job over teamviewer lol, what a pain in ass)
theres a simple calcultion which allways was right for me:
- service menu says: bootloader unlocked allowed: YES [x] (check:good
- installed all the drivers & stuff properly
(you say that cmd tells you device is connetced, so [x](check:good
if its then still not working, ITS 100%:
a human (your) fault.
- maybe request wrong code (99%)
- ???
i say that because i have friends which telled me same thing. they said "i read it thrice & requested code more than 5 times...... bla bla" - & those a were mostly smart people. (no n00bs)
guess what, after triyng help them for hours (!) over internet, i go to them next day & unlocked phone in 5 mins. lol
i dont know what they doing wrong. or why its not working. i only know if you do it carefully,patiently, read all & DO IT EXACTLY like stated it allways works. because its my way & it allways worked (even they say they done it same.)
but keep in mind that maybe your carrier locked it in some way. here in my country its not allowed for carriers. but idk how its in yr country
BernardoCalhanas said:
then there is no free way of doing this?
Click to expand...
Click to collapse
I know not
As of March 2015 is there any free way to unlock the bootloader if it is not allowed?
arpcpro said:
As of March 2015 is there any free way to unlock the bootloader if it is not allowed?
Click to expand...
Click to collapse
no. sorry
BernardoCalhanas said:
then there is no free way of doing this?
Click to expand...
Click to collapse
I really hope you found a way to unlock your bootloader. If not, go on this site, just provide your email, confirm email, type your emai number and they give you the code instantly: https://developer.sonymobile.com/unlockbootloader/
I did worked for my xperia arc. Good luck
---------- Post added at 09:45 ---------- Previous post was at 09:30 ----------
arpcpro said:
As of March 2015 is there any free way to unlock the bootloader if it is not allowed?
Click to expand...
Click to collapse
I really hope you found a way to unlock your bootloader. If not, go on this site, just provide your email, confirm email, type your emai number and they give you the code instantly: https://developer.sonymobile.com/unlockbootloader/
I did worked for my xperia arc. Good luck
Code:
X:\Program Files\ANDROID\SDK\platform-tools>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.013s
Any suggestions? My device is recognized by and trusting my PC. I also tried the Device Unlock app by T-Mobile USA which says it isn't compatible with my device.
Go to developer options first then enable oem unlocking. Should work now
Thanks sooooooo much. I feel dumb yet don't remember this step on other devices. Guess I never had to unlock a Marshmallow phone? Also not mentioned in this thread I was searching http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930.
Edit: Nor google.
echardcore said:
Thanks sooooooo much. I feel dumb yet don't remember this step on other devices. Guess I never had to unlock a Marshmallow phone? Also not mentioned in this thread I was searching http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930.
Edit: Nor google.
Click to expand...
Click to collapse
This is a new, surprisingly under-the-radar thing you have to do. It got me at first, too when I tried to unlock it before first boot.
Another question.
I accidentally tapped and disabled Developer Options. When I reenabled it, the OEM Unlocking option was disabled. Did just RELOCK it?
EDIT:
It seems like its still unlocked.
Sooo...I locked my bootloader a while ago and I can't seem to be able to unlock it again now.
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Or it says that the device is already rooted.
I'll be flashing the original stock image to see if it works.
doriandiaconu said:
Sooo...I locked my bootloader a while ago and I can't seem to be able to unlock it again now.
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Or it says that the device is already rooted.
I'll be flashing the original stock image to see if it works.
Click to expand...
Click to collapse
had the exact same problem with you.
just update your phone with PC Companion and after this you will be able to unlock it again:good:
broky said:
had the exact same problem with you.
just update your phone with PC Companion and after this you will be able to unlock it again:good:
Click to expand...
Click to collapse
I had to get back on stock. It seems the problem was the pre-rooted rom :good:
EDIT: Resolved: While the OS had said it was up-to-date when I originally checked. It was not. After a bit of time it alerted me that an update was available. After updating the OS the OEM Unlocking option was no longer disabled.
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Gregyski said:
(Since this isn't specifically about alternate firmware, I believe this is the correct forum and not the dev forum.)
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Click to expand...
Click to collapse
The command should be fastboot oem unlock
ilatimer1 said:
The command should be fastboot oem unlock
Click to expand...
Click to collapse
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Gregyski said:
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Click to expand...
Click to collapse
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
ilatimer1 said:
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
Click to expand...
Click to collapse
Thanks for your help ilatimer1, but I have resolved it now. I had edited the original post to indicate this but probably should have followed up at the end for your sake. I was just trying to avoid bumping it. At the time I asked the question, I mentioned that that option was disabled.
When I originally setup the phone I didn't enter WiFi data since I knew a factory reset would occur when I unlocked the bootloader. However, as a result of this, I didn't get alerted to the presence of an OS update. Ultimately, I setup WiFi and discovered the availability of an update. I proceeded to update and the OEM Unlocking feature then became enabled. Thanks again.
I unwapped and went stright to fastboot. didn't know update needed. thanks
Same issue unresolved
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
[email protected] said:
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
Click to expand...
Click to collapse
Where did you buy your Pixel?
Mr. Orange 645 said:
Where did you buy your Pixel?
Click to expand...
Click to collapse
verizon store
[email protected] said:
verizon store
Click to expand...
Click to collapse
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
so there is no solution if Ive already updated to 7.1.1?
any chance a solution will open up in the future?
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Mr. Orange 645 said:
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Click to expand...
Click to collapse
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
[email protected] said:
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
Click to expand...
Click to collapse
No. That's for Nexus devices not Pixels anyway.
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
Im on Verizon
integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Mr. Orange 645 said:
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Click to expand...
Click to collapse
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
integraGSR said:
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
Click to expand...
Click to collapse
LOL! Glad I could help!
Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
But pixels purchased at Google store with 7.1.1 are still unlockable correct?
Sent from my Pixel XL using Tapatalk
Hi guys need some help right now.
OnePlus 5T. Had it rooted and SuperSu installed. Ended up deciding not to have it rooted so used the Full Clean SuperSu unroot. This was successfuly, and after a few days Iwanted to lock the bootloader as well, so went into fastboot and used the fastboot oem lock.
After that, I ended up getting a loop of:
"Your device is corrupt. it can't be trusted and will not boot. Visit this link on another device"
From research, I can see that flashing would be the best option. However, trying to flash through fastboot results in an error:
"OKAY [ 0.442s]
writing 'boot'...
FAILED (remote: Flashing is not allowed in Lock State)"
Any suggestions please?
Are you able to fastboot unlock it again?
rickysidhu_ said:
Are you able to fastboot unlock it again?
Click to expand...
Click to collapse
no, it doesnt allow it through fastboot. I assume it is because when it locked the bootloader, it refreshed the OEM Unlock option from developer options.
Did you see this thread?
[GUIDE] Restore to complete stock and relock bootloader. Easiest step by step guide.
The order is very important. You must restore to complete stock before re-locking the bootloader. That includes recovery. When this is all over, google "what is bootloader?" to see what it does.
Also, questions do not belong in the How-To section. Another moderator will be along shortly to move it into the Help/Q&A section.
yousufx said:
Hi guys need some help right now.
OnePlus 5T. Had it rooted and SuperSu installed. Ended up deciding not to have it rooted so used the Full Clean SuperSu unroot. This was successfuly, and after a few days Iwanted to lock the bootloader as well, so went into fastboot and used the fastboot oem lock.
After that, I ended up getting a loop of:
"Your device is corrupt. it can't be trusted and will not boot. Visit this link on another device"
From research, I can see that flashing would be the best option. However, trying to flash through fastboot results in an error:
"OKAY [ 0.442s]
writing 'boot'...
FAILED (remote: Flashing is not allowed in Lock State)"
Any suggestions please?
Click to expand...
Click to collapse
Call oneplus and have them fix ya
yes, call oneplus.
I have had the same problem and they solved it via remote connection.
Or read here: https://forum.xda-developers.com/oneplus-5t/help/please-help-hardbricked-oneplus-5t-t3716057