Motorola Atrix 4G :: Manufacture Unlock Vs Bootloader Unlock?
Nov 23, 2011
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?
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?
I have the 8 digit network unlock code for my Atrix2, but when new carrier sim card is inserted it doesn't say sim not provisioned, and doesn't provide text box to enter code.Instead it gives me phone and text service but not mms enternet
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'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 ...
I bought a Atrix 2 from Moto online shop without subsidy, it's locked to AT&T network. I'm planning a long trip abroad, and would like to unlock the phone to use other carriers SIM card. But where can I get the unlock code or how to unlock the phone?
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.
I bought an Atrix 4g running Gingerbread this last Saturday (8/20/11). Over a day, it probably would freeze up 10 times. It would only freeze up when the display is off. When I go to hit the power button, the display wouldn't come up. The only way to restart it would be to pull the battery.
I read on this forum and some others that some apps could cause problems so I removed all downloaded apps (factory reset) but the problem persisted. I switched for a new Atrix from ATT and the same thing would happen. At this point I can't believe I got two bad phones from AT&T, so I feel like it must be something I have setup. The guys at the AT&T store said it could have to do with my exchange email I have setup for my work email. I configured it to not sync automatically and only manually. The problem would still persist.
I purchased this MB886 from AT&T but never activated it with them. I went with Consumer Cellular since they do not have a contract requirement. My Sim card from Consumer Cellular worked with the phone but no other carrier Sim card will since it is locked. AT&T does not have the code to unlock this phone since I did not activate it with them. Motorola still has the code and they will not give it to me.
I recently updated my Motorola Atrix 2 to the new 4.0.4 OS. Previously, I had my phone set up so that I had to enter a pin # if my phone had been asleep for 30 minutes or more. Otherwise, if less than 30 minutes, turning the phone on (from sleep) went directly to the home screen (no swiping or unlock needed). Under the new OS, I cannot seem to keep this. Now, there is a 2-step unlock process (selecting key icon, and then unlock option -- lock icon -- in order to get to main screen). The only way to avoid this annoying 2-step process (that doesn't really add any security) is to turn off all locks, but I would prefer to have some security (i.e. through pin lock after 30 minutes asleep). Anyway to disable this annoying 2-step/swype feature when turning on phone without disabling all locks? If not, is there anyway to go back to my previous OS?
having issues with the fingerprint scanner after upgrading to 4.1.83? I was on 4.1.57, and did the upgrade to 4.1.83 yesterday.This has happened a 3 or 4 times now, where it will no longer register attempted fingerprint scans and I have to unlock with the swipe + numeric code fallback option. It just displays "Swipe finger sensor.", and no matter how many times I swipe my finger, it continues to display that message. I don't get a "Swipe was too fast" or "Finger did not verify...". It seems to just stop working.If I reboot the phone, it works again, until after a while it just randomly stops working again. I have a workaround, but I was curious if anyone else was seeing this behavior after a 4.1.83 upgrade. I found it strange, because the update doesn't mention anything about the fingerprint scanner, but of course that doesn't mean they didn't tweak something with that module.