Database Develop

Motorola Unlocking Bootloader Tool Will Work for Atrix HD?

Researching length of code: http://pastebin.com/zHh76h60
After researching, I can conclude the code is going to be between 1-20 digits (assuming I am reading syntax correct)
Looks like we need the code for it for work, normally fastboot tells you the code for use and explains how to do it...but this is much better than success story than Razr, I believe the unlocking bootloader tool from Motorola WILL support this device! [UPDATE: NOPE! Motorola at this time is not supporting this device, but this method is the proper way anyway. ]
Code:
C:\Users\matt>fastboot devices
(My device ID) fastboot
C:\Users\matt>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.104s]
finished. total time: 0.107s
C:\Users\matt>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.104s]
finished. total time: 0.107s
This is not a special Atrix HD, it still says "Device is LOCKED. Status Code: 0" on the AP Fastoot Flash Mode (S) screen.
Code:
C:\Users\matt>fastboot oem get_identifier_token
...
(bootloader) Restricted oem command
FAILED (remote failure)
finished. total time: 0.100s
EDIT: (August 14th 2012)
Code:
C:\Users\matt>fastboot oem get_unlock_data
...
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
OKAY [ 0.351s]
finished. total time: 0.353s
Put this into your own device and find out your unlock data
Below is an excerpt from a strings.exe of the abootBackup partition:
Code:
Device already unlocked!
%s: START
%s: value = %s
fastboot oem unlock [ unlock code ]
OEM unlock failure!
Could not get unlock data!
Above you can see... we HAVE the unlock data now. We just have to figure out how to use it.
Status codes shown in AP Fastboot:
Code:
Device is LOCKED. Status Code: 0
Device is UNLOCKED. Status Code: 1
Device is LOCKED. Status Code: 2
Device is UNLOCKED. Status Code: 3
More strings.exe:
Code:
Error while unlocking device
mot_sst_validate_token: Token header incorrect
mot_sst_validate_token: Format version incorrect
mot_sst_validate_token: Length incorrect
mot_sst_validate_token: Binding information incorrect
mot_sst_validate_token: Unable to validate token integrity
mot_sst_validate_token: Token integrity invalid
unlock failed in sst oem unlock handler %02x
unlock data invalid!
Password incorrect
Password incorrect!
Cannot provide unlock data
Cannot provide unlock data!
general failure in sst oem unlock handler %02x
General system failure! %02x
Unlock completed! Wait to reboot
General Unlock failure!
unlock failed in sst oem unlock handler
Set MOT SST values
Done Setup my special MOT SST values
mot_sst_create_token: Unable to retrieve PUID
mot_sst_create_token: Unable to retrieve FUID
mot_sst_create_token: Getting PSV
mot_sst_create_token: Unable to retrieve PSV
mot_sst_create_token: Generate token code
mot_sst_create_token: token code generated!
mot_sst_create_token: Writing token
mot_sst_create_token: Unable to generate token code
create_token status: %d
mot_sst_create_token: Creating token
mot_sst_create_token: Getting flash uid
%s START
mot_sst_oem_lock_handler: invalid state
mot_sst_oem_lock_handler: load and validate failed
Re-lock failure
lock complete
%s failure to delete or create token
mot_sst_oem_lock_handler
From what it seems like... the device itself must create the same token that I believe a webkit will give us. [UPDATE: Proven right lol ]

I dont have the HD, so I'm just going on what I'm reading on my forum, the og Atrix, but alot of people there are having problems unlocking with replaced atrixes. Seems moto blocked the bootloader on them, so maybe its the same for the HD. I've been following the attempts at rooting the HD and the "promise" of moto releasing unlockable bootloaders, so hopefully progress is made soon. Good luck!

pre4speed said:
I dont have the HD, so I'm just going on what I'm reading on my forum, the og Atrix, but alot of people there are having problems unlocking with replaced atrixes. Seems moto blocked the bootloader on them, so maybe its the same for the HD. I've been following the attempts at rooting the HD and the "promise" of moto releasing unlockable bootloaders, so hopefully progress is made soon. Good luck!
Click to expand...
Click to collapse
As far back as I remember, any device from Motorola that shipped locked before disabled the command "fastboot oem unlock." This is the first time I have personally seen it possible on a release-keys "Retail" device like this.
With the Photon Q coming soon as well.. I would like to personally see this as a sign of us getting the unlock as well. Hopefully

mattlgroff said:
As far back as I remember, any device from Motorola that shipped locked before disabled the command "fastboot oem unlock." This is the first time I have personally seen it possible on a release-keys "Retail" device like this.
With the Photon Q coming soon as well.. I would like to personally see this as a sign of us getting the unlock as well. Hopefully
Click to expand...
Click to collapse
Im hoping too! I wont ever leave my og atrix, but still hoping with google acquiring moto mobility, that something sweet is coming! Im dedicated to moto.

Updated OP with some important new information.

Would be awesome to get something similar to revolutionary before the official "void your warranty" tool...
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com

XT1068 - Error unlock bootloader, not write new rom

My xt1068 has locked bootloader, and was in the rom 5.0.2 and upgraded to 6.0 alone and began to hang, was then rewrite rom 6.0 (TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7), and not turned over, I tried to rewrite the 5.0. 2 (although I knew that the chance to return was almost zero because the rom does not downgrade with locked bootloader). and not worked ...
I tried to unlock the bootloader and the following error:
(Bootloader) unlock invalid date!
FAILED (remote failure)
finished. Total time: 10.031s
the equipment is stopped, and not do anything already used several commands like "mfastboot oem fb_mode_clear" among others, however nothing happens.
I have a little experience with rom motorola, but nothing is solving.
It will be someone there who can help me ...

unlock boatload

Hello, i got a question if some one more has this problem, when i try to unlock the bootload from sonys site,
http://developer.sonymobile.com/unlockbootloader/
when i use fastboot devices i found my device.
Next step is the code for the unlockboot load
C:\sdk\platform-tools>fastboot -i 0x0fce oem unlock ***************
...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
C:\sdk\platform-tools>but why do i get FAILED commando not allowed some one know the answer please help me.

oem unlock
you must in developer setings allow "unlock oem"

GameboyZA said:
you must in developer setings allow "unlock oem"
Click to expand...
Click to collapse
And turn off my Xperia
Sent from my Xperia XA using XDA Labs

His bootloader could be carrier locked the even changing oem unlock it will still not unlock and will give error
Sent from my F8131 using Tapatalk

GameboyZA said:
you must in developer setings allow "unlock oem"
Click to expand...
Click to collapse
i think that will work the settings was off, so i will try again to day

i just tried this to day and now i got this error
FAILED (remote: Command did not succeed)
finished. total time: 0.042s

Unable to unlock bootloader - WTF?

I'm hoping someone can help:
I've been rooting/unlocking android phones for years. I've run Linux as my desktop OS for 15 years and I'm used to using fastboot.
I've had an Xperia Zr for a few years and when I saw them new on Ebay new for <$100 I bought another one.
So the first thing I try and do is unlock the bootloader, I have done this on several phones, including the ZR I use as my main phone.
I get the IMEI off the back of the phone and make sure it's the same as the one I get when I *#*#SERVICE#*#* and it is.
In Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes
I go to sony and get the unlock code for that IMEI (I've done this 4 times, it's always the same, I've double checked all the fields).
When I enter the command from fastboot to unlock the bootloader I get this:
[email protected]:/media/rolf/Data/Android$ sudo fastboot -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.598s]
finished. total time: 1.598s
So no error, it looks like it worked. When I reboot the phone it's like new again it wiped itself as it does after you unlock the bootloader.
But when I go back to Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes , but it should now say bootloader unlocked.
When I go back to fastboot and try and flash anything it behaves like it still locked.
[email protected]:/media/rolf/Data/Android$ sudo fastboot flash recovery cm-13.0-20160930-NIGHTLY-dogo-recovery.img
sending 'recovery' (11570 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
The phones both look identical, the new one looks genuine, the FCC ID and model number and Type are the same. The old phone was made in the 25th week of 2013 the new one is 30th week 2014.
Does anyone have any idea what is going on?
Thanks,
Rolf

Use flashtool to unlock bootloader.maybe this will work.I used flashtool to unlock my zr bootloader easily.

Flashtool is just a way for people who don't use the command line to issue commands.
Just to be sure I installed it under Linux and Windows and tried the bootloader unlock from there with the same results on both OSs.
01/004/2016 11:04:58 - INFO - Device connected in fastboot mode
01/007/2016 11:07:45 - INFO - Unlocking phone using key 3214A89EDE406752
01/007/2016 11:07:47 - INFO - ...
01/007/2016 11:07:47 - INFO - OKAY [ 1.385s]
01/007/2016 11:07:47 - INFO - finished. total time: 1.385s
01/007/2016 11:07:47 - INFO - Device will reboot into system now
01/007/2016 11:07:47 - INFO - Unlock code saved to C:\Users\rolf\.flashTool\registeredDevices\EP74168AM1\ulcode.txt
01/007/2016 11:07:47 - INFO - Device disconnected
Like when I use fastboot directly the device factory resets itself but remains a locked bootloader.
Has anyone ever seen a phone that says Bootloader unlock allowed: Yes but when you issue the command it fails silently?
Just to be sure, I have tried many different versions of flashtool. I have also tried using the wrong key to see what happens.
If I change the last digit of the unlock code then the command fails.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406751
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
If I give the correct unlock code the command succeeds, but the phone never unlocks.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.569s]
finished. total time: 1.569s
I've tried using 2 different computers now so I have ruled out the computer hardware or software.
It seems to be the phone, this one is made in Malaysia the other one does not say where it was made.
Does anyone have any ideas?

This won't happen if your zr isn't carrier locked.So check it otherwise i'm unable to help you.Here are some great members in zr community can help you with this wired problem.PM with daedroza or sigprof.without PM it's not hard to get help from great members.

Never seen something like this, so the following is mostly a guesswork…
What ROM do you currently have on this phone, and did you reflash it? In theory it's possible that some strange (carrier-specific) ROM version relocks the bootloader during boot; another possibility is that the unlocking process is broken with some bootloader versions. Because creating the TA backup before unlocking needs root, I used old ROMs when unlocking — maybe even something ancient like 10.3.1.A.2.67, which can be rooted with opensource rootkitZ, and definitely not something which requires the malware-infested King Root. So flashing a stock ROM with a different bootloader version may help (the bootloader version number in boot_delivery.xml inside FTF must be different from the installed verson, otherwise flashtool will skip the bootloader parts when flashing — e.g., 10.6.x and 10.7.x stock ROMs have the same VERSION="1264-2309 S1_Boot_Lagan_1.1_10").

Thank you for some excellent advice. I had already re-flashed 5.1.1 with no change, so I tried 5.0.1 and there was also no change.
I found the oldest KitKat Rom I could and flashed that, as before the bootloader unlock command appeared to have worked but this time it rebooted into a boot loop.
I dropped back into fastboot and was able to flash a new boot.img and installing cm13 was quick and easy. The bootloader now shows as unlocked in SERVICE.

What software did you use to flash an old rom?

Huawei p20 pro CLT-L09 Brick

Hi. I have a Huawei p20 pro CLT-L09.
The mobile was not completely smooth, so I tried to force Android 10 to see if that solved the problem.
Now you have a "brick" in which it says:
"Your device has loaded a different operating system"
And now he just goes into the "erecovey" but does nothing. It doesn't update or anything. Fails. Does anyone know if there is any solution? Thank you
C:\adb>fastboot oem get-product-model
...
(bootloader) CLT-L09
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.008s
rom install now 9.1.0.187 (c432e8r1p11)

Try this method https://forum.xda-developers.com/hu...de-install-emui-9-1-p20-pro-c432-usb-t3951653

Thank you. It does not work for me since the latest version that is available for download is lower than the one that my phone has, so it does not allow me to install a previous version to the one that I have installed.

I have nearly the same problem.
I tried literally everything I can - without unlocking the bootloader, cause I can't get a code, also I don't want to pay for some doubtful source - without result.
I solved the problem: bought a broken phone, and got the mainboard into my perfect one.

its posible by a tool to wake it up by test point, forget flash by idt if u lose imei then u have a toy

kikson112 said:
its posible by a tool to wake it up by test point, forget flash by idt if u lose imei then u have a toy
Click to expand...
Click to collapse
And what tool?

Ex extoplus, and all what can partial flash to not lose imei