[Motorola Droid 3] xaser66:
Hello!

First of all, Thanks to all for this post, but specially to queberican351 and lazarusrevol for their info and help.

ok, my D3 is still SIM-LOCKED and SUBSIDY Locked too (however after leave the phone for about half hour without battery, it enable again the option for type unlock code...)

@queberican351

Your info makes a lot of sense to me (I am not a programmer but have some electronic knowledge background...), so your comment about that maybe some kind of "algorithm" that is wrote in the first VRZ activation makes some sense to me (since as far I know previously, and by other clues around the net) the unlock code is somewhat wrote in and associated to hardware by manufacturer (Moto...), so, I always wonder about how VRZ could rewrote and change this unlock code after activation, but, some kind of "virus algorithm" that may make a double check of the settings "just" after the unlock option field is filled with a code and passed the internal check by moto hardware, seems more possible to me that a rewrote of the unlock code set by moto at the factory.

ok, enough guessing... well, I did a process of testing in order to return my D3 to the STOCK version VRZ_XT862_5.5.1_84_D3G-20_TA-9_CFC_1FF_01, since this appears to be the original stock version with the D3s was released from the factory (and I suppose that may be the version without the "algorithm" that blocks unlock codes).

Well, I did a long and controlled process of testing and error and sadly found thta like my phone was upgraded to the OTA version that is the same of the version VRZ_XT862_5.5.1_84_D3G-55_1FF_01 (AND that I wonder if may in fact including the "algorithm", so if the phone was flashed by this file, even if not activated in VRZ network, may be very possible that would fail in unlock codes of internet sellers...).

Well, I bricked my phone since my tests to return to the version STOCK VRZ_XT862_5.5.1_84_D3G-20_TA-9_CFC_1FF_01 give me errors during the flashing process (I used the moto-fastboot software option since it works fine for me and RSD seems to be more prone to give fails and refuses to flash in some times).Well the log of errors was:

---------------------------------------------------

sending 'mbm' (256 KB)... OKAY [ 0.018s]

writing 'mbm'... OKAY [ 0.669s]

rebooting into bootloader... OKAY [ 0.293s]

sending 'mbmloader' (39 KB)... OKAY [ 0.003s]

writing 'mbmloader'... OKAY [ 0.306s]

sending 'mbm' (256 KB)... OKAY [ 0.299s]

writing 'mbm'... OKAY [ 0.490s]

rebooting into bootloader... OKAY [ 0.292s]

sending 'cdt.bin' (16 KB)... OKAY [ 0.001s]

writing 'cdt.bin'... INFOPreflash validation failure

FAILED (remote: )

erasing 'userdata'... OKAY [ 0.296s]

erasing 'cache'... OKAY [ 4.887s]

sending 'lbl' (16 KB)... OKAY [ 0.001s]

writing 'lbl'... INFOPreflash validation failure

FAILED (remote: )

sending 'logo.bin' (854 KB)... OKAY [ 0.316s]

writing 'logo.bin'... OKAY [ 1.274s]

sending 'ebr' (16 KB)... OKAY [ 0.271s]

writing 'ebr'... INFOPreflash validation failure

FAILED (remote: )

sending 'mbr' (16 KB)... OKAY [ 0.271s]

writing 'mbr'... INFOPreflash validation failure

FAILED (remote: )

sending 'devtree' (512 KB)... OKAY [ 0.295s]

writing 'devtree'... INFOPreflash validation failure

FAILED (remote: )

sending 'system' (262144 KB)... OKAY [ 16.425s]

writing 'system'... OKAY [ 15.131s]

sending 'system' (175872 KB)... OKAY [ 11.026s]

writing 'system'... OKAY [ 9.304s]

sending 'radio' (14368 KB)... OKAY [ 0.899s]

writing 'radio'... OKAY [ 2.718s]

sending 'boot' (8192 KB)... OKAY [ 0.605s]

writing 'boot'... INFOPreflash validation failure

FAILED (remote: )

sending 'recovery' (9216 KB)... OKAY [ 0.728s]

writing 'recovery'... INFOPreflash validation failure

FAILED (remote: )

sending 'cdrom' (12032 KB)... OKAY [ 0.869s]

writing 'cdrom'... INFOPreflash validation failure

FAILED (remote: )

sending 'preinstall' (262144 KB)... OKAY [ 16.473s]

writing 'preinstall'... INFOimage bigger than partition

FAILED (remote: )

rebooting...

--------------------------------------------------------------

Ok, after this fail, my phone bricked and maintain rebooting in the red M logo, so I found a solution by flashing the XT883 rom (I know that may be dangeroous, but what a heck I am fed with this lock on my D3 so, I take my risk since my locked d3 is not going to any place by now...), wel I use the SOLANA version SOLANA_SLNCT-57.1.40_Fastboot-service, and it flash without errors and then I reboot succesfully to the Chinese version of the phone BUT this version dont have option for type Unlock code so... the LOCK is maintained over this ROM so my D3 in this step was always locked and didnt get connection on network.

After this I simply did a last flash with the OTA version VRZ_XT862_5.5.1_84_D3G-55_1FF_01 and it was succesfull, so I was able to reboot my phone to the verizon version, and working but STILL locked...

Finnally ONLY for checking that everything was working I did again one last test using my D3 in OTA version with my orange Turbosim and it again was able to unlock temporaly my D3 and was able to make calls on my Network (but as I said in previous posts the turbosim is Not a really working solution because lost signal and refuses to reconnect again in Network when You move from the cell tower where was activated in first time and so is needed to put You provider sim in another Unlocked phone in order to "reset" sim on service provider, since this appear as some kind of "turbosims" proctection that Carriers are including in their networks in order to avoid use of turbosims...)

Sooo... after this long and bother tale... I would like to ask if somebody may know a way o may belive that could be made a hack in order to be able to re-flash downgrade the D3s rom to the original STOCK version VRZ_XT862_5.5.1_84_D3G-20_TA-9_CFC_1FF_01, since according the info provided by queberican351, if the phone may be reflashed to thsi STOCK version, may be possible tha unlock code of internet sellers may work in the troubled D3.

Thanks again for patience and attention... best regards and please if there some more help, it will be very gratefull.