[Verizon Motorola Droid Turbo General] EjđiSixo:
Still no usable help from devs or anybody more experienced..

Update:

Phone is still bricked and probably will be until stock firmware is released. After that i'll consider selling the phone for good, luckly it's brand new, used for few days only.

Unlock data

I'm currently analyzing unlock data (get_unlock_data) . So unlock data looks something like this :

99**************#4C4D3556313230303737313
63031303332323239#BD008A672BA474
6C2CE02328A2A0C39F951A3E5#1F5328000
20000000000000000000000

Code is not mine and not of droid turbo, just fake code found on internet.

* are replacing real numbers.

I reffer to "line" till the # symbol.

So 1st "line" is imei number no question about it but scrambled.

2nd "line" didn't make any sense at all , but discovered later after running whole code through hex to ascii that it's just hex writen : serial number of device and product number (xt1254).

3rd "line" : This is probably what's responsible for creating bootloader unlock code. Possibly some deep stored number of something, not sure..

4th "line" i later figured to be my UID.

In my opinion , when you provide bootloader unlock data , it probably checks 1 2 4 to tell if the device is "unlockable" and then somehow converts 3rd line into unlocking code ( or unlock_token, not sure , I've only used HTC web for unlocking devices).

Without discovering algorythm / method used for converting I think the only way to unlock is brute force. To get little more idea about it, it would be really helpful if somebody who has unlocked their moto maxx / moto turbo through website could provide code for analyzing..

I somehow don't think that motorola has some "database" and believe that code is created "on the spot".

Just something to think about, maybe somebody has some idea.

I've tried manipulating all the data but motorola's website every time returned device is not unlockable so probably all 4 lines have to match and that's the info they have database about.

Brute force

I would never ever recommed this to somebody. On the other hand I am willing to try it on my device. Especially now since it's bricked and useless anyway.

Let's say some script is created , and we have few used unlocking codes from maxx/ turbo and know how it has to look like , which format. Script generates random codes in that format and tries them in sequence, without repeating them.

You connect the phone when you don't use it like overnight and during day if you may, and script is trying. Given the possibilities of numbers and latters it could take up to 3 months constantly connected to get the code. I think fastboot can try around 1 to 2 codes per second.. Still , that doesn't mean it WILL take that long, code can be found in 2 days, in 1 hour , in 2.5 months. It's a Casino gamble.

The only concern I actually have with brute force besides time is the fact that devices has AMOLED screen and AMOLED screens are prone to "screen burn in". That means if same screen is being displayed on display over and over, that frame will "burn in" the display and be in the background forever when for example you look at white screen. And 2-3 alltogether (again in theory) months of showing same screen (bootloader) over and over is more than enough to create a burn in I think..

Just something to think about..

EDIT:

Sorry, haven't seen your response. Yes, I'm interested in the actual unlock code . Don't worry, it's useless once when it's used..

Thanks a lot!