Develop Bugs

Bootloader unlock failed

Hi guys...so i updated my phone to 2.3.4 then rooted it with the zergrush method.Now i'm trying to unlock my bootloader so that i can flash cyanogen mod.I followed all instructions from the cyanogen site but i'm getting this error...
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.000s
Does anyone know what this error means.

Are you 100% sure you can unlock yours? If you're sim locked then no you can't.
---------- Post added at 11:41 PM ---------- Previous post was at 11:38 PM ----------
Try following this guide? I unlocked mine problem free thanks to this one. ^^ http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/

Droid117 said:
Are you 100% sure you can unlock yours? If you're sim locked then no you can't.
Click to expand...
Click to collapse
I'm not sim locked and i followed the instructions to the t from start to finish.I even got the unlock key twice to check if that was wrong but both keys were the same.

I did the unlock bootloader check and it confirmed i can unlock it.
All drivers installed and can connect in fastboot mode ie blue light.
Getvar command was good ie 0.3
But i still get that error.

You typing in the unlock key correctly? Not getting the O/0s confused?
---------- Post added at 11:59 PM ---------- Previous post was at 11:56 PM ----------
Hmmmm did you get the phone unlocked yourself?
---------- Post added 23rd December 2011 at 12:03 AM ---------- Previous post was 22nd December 2011 at 11:59 PM ----------
What OS are you using?

Droid117 said:
You typing in the unlock key correctly? Not getting the O/0s confused?
---------- Post added at 11:59 PM ---------- Previous post was at 11:56 PM ----------
Hmmmm did you get the phone unlocked yourself?
Click to expand...
Click to collapse
Yeah there's no 0's or O's.No but if it wasn't factory unlocked would that cause this problem.

In cases like that I think you may have to pay some dude to get it unlocked. Try giving these forums a search. There's a link to the guy who does them someplace on here.

Droid117 said:
In cases like that I think you may have to pay some dude to get it unlocked. Try giving these forums a search. There's a link to the guy who does them someplace on here.
Click to expand...
Click to collapse
I might have to look into that...thanks for the help.Nice name by the way .

One more ? if i flash cwm without unlocking my bootloader would i still be able to flash custom roms.

As long as the custom rom runs on the stock kernel I think so. I've yet to try the Darkforest one. I couldn't get it to work when I was on stock kernel with a locked bootloader. So I wouldn't hold your breath on that one. I can message the results if I manage to get it to flash via CWM. Thanks for the compliment Just putting back in what I take out.

I think that thread for the pay service bootloader unlock was removed for some reason but he has a website now
www.unlock-bootloader.com
Sent from my R800a using XDA App

[Q] Unlocked bootloader

Unlocked bootloader
hello, help me!!! ... i see the tutorial (unlocked bootloader) and i make all the instructions but when i put fastboot.exe -i 0x0fce oem unlock 0x and the key ,I get an error Failed : (remote command not allowed)... i have windows 8 ...can you help me?...sorry bad english.

daruto80 said:
Unlocked bootloader
hello, help me!!! ... i see the tutorial (unlocked bootloader) and i make all the instructions but when i put fastboot.exe -i 0x0fce oem unlock 0x and the key ,I get an error Failed : (remote command not allowed)... i have windows 8 ...can you help me?...sorry bad english.
Click to expand...
Click to collapse
Don't post in 2 sections.
Is your phone connected to your PC with the latest drivers in fastboot mode.
Make Sure YOU have MADE a TA Backup.
---------- Post added at 06:01 PM ---------- Previous post was at 05:34 PM ----------
MahaDEVELOPER said:
Don't post in 2 sections.
Is your phone connected to your PC with the latest drivers in fastboot mode.
Make Sure YOU have MADE a TA Backup.
Click to expand...
Click to collapse
Done More Research and Found this:
http://forum.xda-developers.com/showthread.php?t=2540670
(Look at the last link)
Press Thanks if i have helped.

yes
MahaDEVELOPER said:
Don't post in 2 sections.
Is your phone connected to your PC with the latest drivers in fastboot mode.
Make Sure YOU have MADE a TA Backup.
---------- Post added at 06:01 PM ---------- Previous post was at 05:34 PM ----------
Done More Research and Found this:
http://forum.xda-developers.com/showthread.php?t=2540670
(Look at the last link)
Press Thanks if i have helped.
Click to expand...
Click to collapse
yes, I have the last drivers and i connect my xperia in fastboot mode but I get this error.

daruto80 said:
yes, I have the last drivers and i connect my xperia in fastboot mode but I get this error.
Click to expand...
Click to collapse
Open the service menu and check if bootloader unlocking is allowed.
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.

where i check that option ?
Antrikos48 said:
Open the service menu and check if bootloader unlocking is allowed.
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Click to expand...
Click to collapse
where i check that option ?

service menu
For service menu, open dialer and type *#*#7378423#*#* then GOTO service Info, configuration
---------- Post added at 07:34 PM ---------- Previous post was at 07:16 PM ----------
If your phone doesn't allow boot loader unlock, Your phone is probably network locked. Try unlocking phone from carrier. If it still doesn't allow, try reflashing firmware with Sony pcc

theperson333 said:
For service menu, open dialer and type *#*#7378423#*#* then GOTO service Info, configuration
---------- Post added at 07:34 PM ---------- Previous post was at 07:16 PM ----------
If your phone doesn't allow boot loader unlock, Your phone is probably network locked. Try unlocking phone from carrier. If it still doesn't allow, try reflashing firmware with Sony pcc
Click to expand...
Click to collapse
the configuration say bootloader unlock allowed: no , but my phone network is perfect, not locked ...and i reflashing firmware many times. help! :crying:

Then you fall into the unlucky people who can't unlock it for now might change in time
Sent from my C1905 using xda app-developers app

Mi Max not able to root

Hello sir
I have been trying to unlock bootloader of my mi max(qualcomm indian version) for some time. I already got the permission to unlock bootloader.
But i am not able to unlock it because of drivers problem. my device is not getting detected in MI UNLOCK TOOL although it is being detected in MI FLASH TOOL. What should i do please help me .. i am using the latest tools and latest drivers in my pc. Also i tried installing new windows 10 in both my pc and laptop but the same problem persists.
Thanks in advance..

Were you able to unlock bootloader ??
If yes then flash recovery twrp
Then
Root either using magisk 14.3.zip or supersu 2.82.

same problem
I got unlock codes from MI, but still I'm unable to root my phone. This sucks !
Anyone ! Please Help.
---------- Post added at 06:55 AM ---------- Previous post was at 06:50 AM ----------
Preshak said:
Were you able to unlock bootloader ??
If yes then flash recovery twrp
Then
Root either using magisk 14.3.zip or supersu 2.82.
Click to expand...
Click to collapse
Sir, the process given to unlock bootloader on Mi.com or else supporting websites are not working at all.
How can we proceed further if this not happening ?

preshak said:
were you able to unlock bootloader ??
If yes then flash recovery twrp
then
root either using magisk 14.3.zip or supersu 2.82.
Click to expand...
Click to collapse
i am not able to unlock bootloader.. As i already said my device is not getting detected in mi unlock tool

pk14392 said:
i am not able to unlock bootloader.. As i already said my device is not getting detected in mi unlock tool
Click to expand...
Click to collapse
Show me screenshot
---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------
mailanoop89 said:
I got unlock codes from MI, but still I'm unable to root my phone. This sucks !
Anyone ! Please Help.
---------- Post added at 06:55 AM ---------- Previous post was at 06:50 AM ----------
Sir, the process given to unlock bootloader on Mi.com or else supporting websites are not working at all.
How can we proceed further if this not happening ?
Click to expand...
Click to collapse
Wait for 3-4 day after receiving code from xiaomi.
As there servers are updated after 3-4 days. Sometimes may take more than a week..
Unlocking is different and rooting is different. Do not attempt to root without unlocking bootloader.

UNKNOWN
Preshak said:
Show me screenshot
---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------
Wait for 3-4 day after receiving code from xiaomi.
As there servers are updated after 3-4 days. Sometimes may take more than a week..
Unlocking is different and rooting is different. Do not attempt to root without unlocking bootloader.
Click to expand...
Click to collapse
Hi, the message I received with unlock code from MI say it (the code) only valid for 10 days.
---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------
mailanoop89 said:
Hi, the message I received with unlock code from MI say it (the code) only valid for 10 days.
Click to expand...
Click to collapse
Can I have the links for the requirements (tools and files) to root MI-max which is used by you or nay type of screen shots or correct procedure for it?

https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594/page33

Hi, after i flashed twrp and entering recovery i swiped allow modification and it asks for decrypt key and then my phone got in to bootloop... i actually couldn't flash supersu Bcoz in not able to see it without decrypt key... How do i fix this issue? Can u pls help?

The Only Thing Stopping Me From Rooting This Device...

So, I got this phone today, its a major upgrade... I got it to replace my oh so crappy a10e. Got really lucky, only 250 bucks and its like new.
Now, the only reason I haven't rooted it is I've realized there's 2 different fastboot's... Fastbootd and the bootloader
I looked into it, fastbootd can't unlock bootloader and all that. When I boot into bootloader where I should be able to flash it... No driver I've found for this device has let my computer see the phone in bootloader/fastboot mode.
Anyone know where the heck we can get the drivers for this? I've tried the "Add Legacy Drivers" and that didn't work either
Update on this: I got the pc to recognize it in Fastboot/bootloader, Fastbootd, recovery sideload and ADB. Some fastboot oem commands work, but none of the standard oem unlock methods work

Android 10 feature
Flash boot, recovery, dtbo, vbmeta, and super in fastbootd
All other operation on bootloader

if you ever get this device rooted please let us know. I'm waiting for a root on this device before I will purchase. You may have to unlock the bootloader or get a engineer bootloader before you can root this device. I'm not sure because I do not own one yet.
---------- Post added at 06:43 PM ---------- Previous post was at 06:29 PM ----------
Have you tried King root yet?

Unable to relock bootloader without receiving message that says "Your device is corru

Unable to relock bootloader without receiving message that says "Your device is corru
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.

I was able to relock my 7T using fastboot. If you can boot to fastboot? In linux the command was 'fastboot flashing lock'. Not sure in windows if it's the same. Worked for me. Now 'OEM unlocking' option is visible again under system / developer tools. Prior to re-locking it was grayed out, unavailable.

Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk

Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader

v.konvict said:
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
Click to expand...
Click to collapse
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.

TBHSilentAce07 said:
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
Click to expand...
Click to collapse
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux

xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
Click to expand...
Click to collapse
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
---------- Post added at 11:17 PM ---------- Previous post was at 11:13 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
Click to expand...
Click to collapse
Being that this is Debian 9, maybe my fastboot is an old version as well. ADB and fastboot both seem to work pretty good though. No stinkin' USB driver issues like with Windows 10.

SenyorMauricio said:
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
Click to expand...
Click to collapse
xe0r said:
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
Click to expand...
Click to collapse
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.

SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
Thanks. Confirmed this works. Needed to install an older version (went with 10.0.8 global), then skipped through most of the setup minus wifi, did a system update to 10.0.12, reboot to bootloader, fastboot oem lock, and no more corruption errors.

SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
So to be clear, can a T-Mobile converted to Global be bootloader re-locked the same way without getting the corrupt phone boot refusal screen? The wife's phone refuses to lock, but haven't tried the update from OnePlus method above?

YES.