I'm writing to ask for your favor - Please provide us, some enterprising Defy (MB525) owners, a way to unlock the bootloader.Rationale:1. You are providing means to unlock the bootloader on many newer devices already, and it shouldn't cost you much to provide us a mean to unlock the Defy as well.2. The warranty of many of our Defy devices is expiring, so even if we brick our device, we couldn't file a warranty claim anyway.3. The Defy is the 2nd most popular devices running CyanogenMod according to http://stats.cyanogenmod.com/, so we have a huge following.4. If you allow us to unlock the bootloader, we will consider it as a gesture of goodwill and will be more willing to recommend our families and friends to buy Motorola devices in future.
5. Many other manufacturers have started to unlock their bootloaders and by comparison, Motorola is doing very poorly and has a bad image in our mind.6. Many of us bought the Defy without any carrier subsidy.7. Come on! Give us a Christmas gift, okay
I was searching for topics related to this topic, describing the diference beetwen manufacture unlock vs bootloader unlock. I bought an unlocked Atrix in AT&T, so I could use it at any company or overseas. Is this mean the bootloader is also unlocked? Or these are diferent things?
Totally stock Defy, upgraded to 2.2 and on its 2nd ear speaker.While in the browser the phone froze compleatly, so after waiting a while I pulled the battery, and on restarting it went straight to a bootloader screen.Then when i connect to the PC it, just changes the last line to Transfer Mode OK.I have tried the Start button and Volume rocker switch, but this seems to do nothing. Please tell my "Life proof" phone isn't dead before my 2 year contract is up!? I have tried googling, but all the help I can find, seems to be for people who are rooting their Devices, I would just like to state that is not what I was, or am trying to do.
The world knows updates in a Motorola phone is very slow! This leaves power users with no other option but to go for custom ROMs. Even there locked bootloader is always a very big problem! Moto promised long back to unlock bootloaders. Defy and Defy+ are now quite old phones and will receive no update either! So now is there any hope that the bootloaders will be unlocked? This deters most devs and power users from getting Moto phones inspite of an excellent build quality. Hope we get a reply and this thread don't die without any use!
If Moto does not unlock the bootloader shortly for my Atrix I will be selling the phone and moving to a Samsung Galaxy S II as soon as it's available. Moto, provide a date as to when you will provide an unlocked bootloader. I know this is a hot topic, but if you can not keep up with Development then allow me as the owner of the phone to do as I wish. Take samsungs lead and send your phones to CyanogenMod
THE STRING "fastboot oem get_unlock_data" DOES NOT RETURN ANY DEVICE ID. WHY?The bootloader on Motorola devices released before August 2012 is not unlockable. This fastboot command will not return a device ID or unlock data for these Motorola devices. At this point, only the devices on our Supported Devices list are eligible for the unlockable bootloader program.HOW DO I TELL IF MY DEVICE HAS AN UNLOCKABLE/RE-LOCKABLE BOOTLOADER?This depends on a few factors. First is whether the device ships with a bootloader that is capable of being unlocked or re-locked. Second is whether the wireless carrier that sells the device allows the bootloader to be unlocked, as each of our operator partners has their own policy. As new devices are released, please check the bootloader introduction page. You will be able to check whether your device shipped with an unlockable bootloader. We will be adding devices to this list regularly.As of August 2012, the only Motorola devices which can be unlocked are:
Now above what I have bolded are my areas of concern. In particular, the second quote:First is whether the device ships with a bootloader that is capable of being unlocked or re-locked.The Motorola Atrix HD has indeed shipped with a bootloader that is capable of being unlocked or re-locked. It supports the exact same commands as the Motorola Photon Q 4G LTE does, the commands of:
This device fits that exact definition. Running a strings.exe runthrough of the bootloader from the Atrix HD shows that it indeed supports these commands, and anyone with this device and the android-sdk can run these commands themselves. The part where the unlocking process is stuck is the Motorola "Unlock My Device" webkit, where the results of "fastboot oem get_unlock_data" were pasted into the box to get the emailed UNIQUE_KEY to put into "fastboot oem unlock [ unlock code ] " as the same process is the Photon Q 4G LTE. The site comes up with this error:As you can see, we can assume the second half of the "few factors" as the faq pointed out:Second is whether the wireless carrier that sells the device allows the bootloader to be unlocked, as each of our operator partners has their own policy.Assuming this, it is then AT&T's decision that the Motorola Atrix HD has a locked bootloader, but the device DOES support unlocking and re-locking, contrary to the first quote in this post from their faq about devices before August 2012 NOT supporting these functions.The bootloader on Motorola devices released before August 2012 is not unlockable.So my question is, will this information be able to get corrected, or is Motorola planning to make an announcement that the Motorola Atrix HD will not be unlocked because of AT&T, but that the hardware and software actually support unlocking and re-locking?
today i got crazy because of my Moto. I have Motorola Defy CEE edition - without BLUR account.Today i borrowed Defy to my friend who tried to unlock the phone.After few unsuccessful attempts i got following message:"Too many unlock attempts!" and i'm able to unlock it only with signing in with a Blur account. As Blur is not supportedf in my region (slovakia, central europe) i had never created the account. How can i unlock the phone? Is there any possibility?I'm really furious about this situation, how can motorola create such crapy unlocking procedure? Unlock the phone with blur in region where blur is not supported....
I would like to know is there a way how to unlock boot loader for Defy? I'm creating an app that needs this function to work properly with Defy. I know that this voids warranty but every other mobility company has published a safe way how to unlock bootloader (like Sony or HTC). I really need this for Defy and it would be very unfair to users who don't have Atrix or Droid RAZR.
the phone was fine and then I heard a noise and notived there was a black square with insatll now or later. I installed now and it showed a bar where the progress was.I did not touch the phone and I heard another noise and went to look at the phone.It was black and when i tried to give the pin, it said Sim card locked emergency calls only. The pin is correct.I turned it off and took the battery out and in again then turned it on, but it is still the same.The battery is at 60% so it is not that.Why would this be please? Did I install a virus? It looked just like the normal official updates.
I telephone T-Mobile today and requested the Carrier Subsidy Unlock Code for our Motorola Defy. They said that they would have it to me in 24 hours! Has anybody ever actually had that quick of a turnaround time on a T-Mobile Carrier Subsidy Unlock Code request?
I'll just get right to it. When I enter the service menu, it tells me that: unlock bootloader allowed: no. I cannot unlock my bootloader. Now, nobody seems to know of any solutions to this problem. I know it is the carriers that are at fault, but I just want to know if it is *possible* to unlock my bootloader. If not, I will have to return this device for one that is more developer friendly.
i'm trying to unlock the boot loader of my xperia z3, i'm following the instructions on sony's site but i'm stuck: i connect the phone to the pc in fastboot mode (blue light on), then i open the command prompt window in the platform-tools folder of android sdk, but when i type fastboot devices nothing happens. If i try to enter my unlock code i get "waiting for device" forever.
For some time I'm trying to make the process of unlockbootloader lamentablemnte this does not work, I'm doing in windows xp with PC Companion installed and operating adb follow all the steps but when Fastboot recognize that the phone is stuck and does not recognize this, I thought at first it was the virtual machine and how he was making the USB connection but probe in a native windows machine and not turned. Would like the possibility that perform differently
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
Ok, so I just got my awesome new 6P. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't.
I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: [URL] ..... (wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently ...
So like many people I'd like to customize my phone with a different image to the stock. I've done this before with HTC phones, and earlier this year updated to the Xperia Z2, with the intention of flashing it when a stable build came out from Cyanogen.
Finally gotten round to doing this and after a confusing twenty minutes trying to get it into fastboot I learn that on its service page its rooting status, bootloader unlock is not allowed.
I am already unlocked and rooted, but I would like to relock the bootloader assuming that I can unlock it for future updates without losing data. The Nexus 5 had a boot locker app in the App Store which allowed this, but I do not find an option for the 6 P.
My nexus 5 just turned off and is stuck on the boot animation. I am able to access the bootloader and have already tried to wipe cache and performed factory data reset but the phone is still stuck on the boot animation. I have tried to unlock the bootloader with 1-click-nexus-5-bootloader-unlock as well as CF-Auto-Root-hammerhead-hammerhead-nexus5 tools but after I accept to unlock the bootloader, the phone reboots and gets stuck on the boot animation. The bootloader status remains locked.
Last year I bought the nexus 6 and for the first time (I've had a lot of android phones) in my phone was also disabled force encryption after the bootloader unlock, twrp and root. So I decided to decrypt it because reading on the nexus 6 forum some devs suggested this to increase the phone performances.
I read that now twrp supports encryption and that Google increased the phone performance also with force encryption enabled.