Related
I have seen around the forum that many do not find where to unlock their Verizon Droid 3
I recommend this website is very cheap I paid 6.00 Dollars for unlocking code and it worked.
unlock4moto.com
good luck..
when did you purchase it?
I bought it yesterday
Ed27 said:
I bought it yesterday
Click to expand...
Click to collapse
How long did it take them to send you the code?
30 to 45 minutes
Ed27 said:
30 to 45 minutes
Click to expand...
Click to collapse
I have been waiting for the past 2 hours, still nothing... are you sure its not a fraud website?
---------- Post added at 02:35 AM ---------- Previous post was at 02:35 AM ----------
papa.khan123 said:
I have been waiting for the past 2 hours, still nothing... are you sure its not a fraud website?
Click to expand...
Click to collapse
Also the contact number is somewhere in Europe (Poland).
papa.khan123 said:
I have been waiting for the past 2 hours, still nothing... are you sure its not a fraud website?
---------- Post added at 02:35 AM ---------- Previous post was at 02:35 AM ----------
Also the contact number is somewhere in Europe (Poland).
Click to expand...
Click to collapse
its not a fraud website for me work fine, just wait until tomorrow morning and check your email
Got the Unlock code after 8 hours, Maybe it was the time in europe that was the problem.
Ordered another code just now and got the code in 10 mins.
Oh and yeah the codes work perfectly... Thanks for the link
Does unlocking with this method makes D3 compatible with World GSM networks?
europe is 6 hours ahead. well italy is, so poland is probably 8 hours ahead EST so plan accordingly. And thanks you alot to the OP who found the first site to work now
erfannf2 said:
Does unlocking with this method makes D3 compatible with World GSM networks?
Click to expand...
Click to collapse
At least I can confirm out of USA GSM. but don't know about TMO and other GSM providers in the US, but I think I saw a thread about unlocking them as well. so good luck!
papa.khan123 said:
I have been waiting for the past 2 hours, still nothing... are you sure its not a fraud website?
---------- Post added at 02:35 AM ---------- Previous post was at 02:35 AM ----------
Also the contact number is somewhere in Europe (Poland).
Click to expand...
Click to collapse
Hello. I used this service and everything is ok... my droid 3 was unlocked in just 1 hour.
Goodl uck
XT860 unlocking
yesterday i used:
"www.mobileincanada.com", $20 and 20 minutes and it's done!
--------------------------------------------------------
XT860 on GSM (out of Canada)
so does this mean i can report my phone lost/stolen, get a new one for $50 from asurion and unlock the old one?
noob question but will it work on any rom such as cm9?
Yep, should work on any ROM as its an unlock code, OS independent. unless someone can justify why not?
well... ok, with little hope, I just wated another $6 in try to unlock my Droid 3...
The code from unlock4moto.com was the same that I previously got from other sellers, so, It FAILS too in unlocking my Droid 3 that is in locked since september 2011 that was I bougth it.
So, in order to try to help other people around and some new member I feel that I shoould to clarify some may be important info that was collected in the past months about unsuccesfull unlocks attemps...
1) For use the online unlock codes sellers, seems that your phone WILL NEVER activated before in veri$on network coverage, since appears that at first vrz activation, the vrz network will change the internal unlock code that came with phone from moto factory and since then the only code that may unlock your D3 seems that will be the code that must be provided by vrz service if you are a full customer active by the vrz conditions.
2) If yoru phone is never activated under vrz network, you almost would be lucky in use online sellers codes.
3) If the phone was used in Vrz network, you mostly will be without luck in unlock your phone, at least that you may have a friend that may receive your phone and may activate it in Vrz account and network, so You could get the vrz code for your phone, that in addition seems that is generated by the MEID number and NOT by the IMEI number.
So, by now I STILL have my phone locked after bought the code ONE MORE TIME (by now I have 6 different code sellers and 2 Turbosim sellers, from which I have some luck in use the phone with some orange turbosim, BUT it fail in maintain the signal and connection when I move, like in a car from one loctaion to another and when connection fail none turbosim was able to allow to restore connection and in fact need to reset the sim on ANOTHER unlocked diferent phone to allow connection on D3 again... is a bother and mess to use...)
If somebody have new/improved info about this or the details about the above comments, I would be very gratefull for some help in order that i may get my D3 some day.
by now, again as paperweight on my desk... :-(
First you have to get in the secret menu dialing *#*#4636#*#* and check if your phone finds any GSM networks.
Phone Information- GSM Auto for prefered network , and then go to General Setting and look up for your countries
networks. If it works then you should be able to unlock the phone with a code obtained from ebay..
Worked for me in Greece
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.
Just wanted to leave a clear feedback about unlock4moto services, I bought the unlock code for the global carriers and received my code within 3 minutes. Yes just 3 Minutes!
Impressive, Affordable, and the best, it works!
Highly Recommended...
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
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
cropythy said:
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
flashallthetime said:
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
Click to expand...
Click to collapse
I tried manually entering it (3 times) i have tried copying it directly, and I have tried copying into notepad and making sure there are no spaces, but it still says my devices is not eligible for a bootloader unlock. Guess I'm calling motorola after work tomorrow.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
I just tried unlocking a Rogers Canada phone and it told me the phone isn't eligible. It certainly should be and I know I'm doing everything correctly as I unlocked a different one a few days ago.
So being you're seeing the same thing my conclusion is that the backend server which the website communicates with to manage the unlocking is broken at the moment.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
Try it again today, so far from my testing the unlock website is working again.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
As others have said, you need a code. The reason is you have to see like five warnings that the warranty will be voided before you get the code. They want to make sure people can't use the "I didn't know it would void the warranty" response if something goes wrong.
GSM Dev Can't go into CWM recovery
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
hondamarlboro said:
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
Click to expand...
Click to collapse
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Volume UP is the "select"
lensgrabber said:
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Click to expand...
Click to collapse
Thank you!!! This is my first moto device and I don't know this manner. Successfully recovery into CWM. Thank you again!
Welcome.
Sent from my XT1053 using Tapatalk
Is possible, Lock bootloader ?
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
I'm trying to figure out the same thing. I followed motorola's instructions on reflashing https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images but it does not re-lock. It tells me "No valid PIV block in SP for userdata"
edit - deleted userdata and it locked, but i still get the warning screen on boot
warranty
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
vespadaddy said:
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
Click to expand...
Click to collapse
Anyone knows anything about that?
Also, is the image altered in any way after a unlock? or is it exactly the same as a factory reset?
---
edit:
apparently it is all fine
Requesting an unlock code will no longer void the device’s warranty
We will start posting return-to-factory software images
Click to expand...
Click to collapse
-- http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html
Why really lock?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
Why would you unroot and/or unlock?
If it is a dev edition, it will not hurt the warranty.
The reason for this phone is for unlocking, rooting, flashing and roming.
Once you have saved a nandroid with a custom recovery (TWRP) you can't mess anything up. Go crazy and have fun
hello, I have been searching relentlessly for a real answer to this and have not found clear answers that I believe apply.
I wanted to install TWRP on my retail verizon Moto X running 4.4.2 but I get a message:
Code:
sending 'recovery' (9854 KB)
OKAY [ 0.860s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.260s
In my searches, i saw this message being related to a locked bootloader. The part that gets me is that I unlocked the boot loader when using JCase slapmymoto v1.0 root method. I saw that some 4.4.2 OTA was supposed re-lock the bootloader, but the last I checked, right after rooting, it was still coming back as unlocked and I have not done any updates since rooting.
Any answers on this would be appreciated to clear up my noobness.
Also, I can't remember or find again, the adb/fastboot command for checking the bootloader, if I had that to tell me whether my BL got re-locked I could just go on that.
Thanks in advance!
Slapmymoto does not unlock your bootloader. You can't unlock the bootloader on a retail verizon Moto X. You either have to have the Dev Edition or you can try that Chinese site.
Either way, the only way to do it is to use fastboot oem unlock (unlock code). If you never did that, then you didn't ever unlock.
That said, you can't install TWRP on your phone unless you use that Chinese site to unlock your bootloader. There is a thread on it.
Sent from my Dev Edition Moto X
chuck4100 said:
hello, I have been searching relentlessly for a real answer to this and have not found clear answers that I believe apply.
I wanted to install TWRP on my retail verizon Moto X running 4.4.2 but I get a message:
Code:
sending 'recovery' (9854 KB)
OKAY [ 0.860s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.260s
In my searches, i saw this message being related to a locked bootloader. The part that gets me is that I unlocked the boot loader when using JCase slapmymoto v1.0 root method. I saw that some 4.4.2 OTA was supposed re-lock the bootloader, but the last I checked, right after rooting, it was still coming back as unlocked and I have not done any updates since rooting.
Any answers on this would be appreciated to clear up my noobness.
Also, I can't remember or find again, the adb/fastboot command for checking the bootloader, if I had that to tell me whether my BL got re-locked I could just go on that.
Thanks in advance!
Click to expand...
Click to collapse
The above poster is correct jcase method is not to unlock your bootloader it is just to root your phone and then another method is to disable write protect.
in order to install TWRP you must unlock your bootloader and in order to do that you need to go here and see if your phone is able to have its bootloader unlocked or not. if you want to find out follow the link below.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
if your phone can not unlock its bootloader then the closeest thing to TWRp you can use is Safestrap that is if they have ported it over to 4.4.2 im not sure if they have yet or not but below is the link to it for you to check out.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
hope this helps and here is a link to my thread with guides on how to do most things on the moto X
http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Hmm, guess i misunderstood what i was doing. The write protect sounds right, guess I mistook that for a bootloader unlock workaround.
Thx for the replies.
I do not believe that I have Dev Edition. I bought my motoX earlier this year, directly from Motorola's website and specified that it was for T-Mobile's network.
All I did was to go online and requested a bootloader unlocking from MotoX.
The phone is now unlocked with TWRP and rooted.
So I am not sure that it cannot be done.
Pat
patspdaphone said:
I do not believe that I have Dev Edition. I bought my motoX earlier this year, directly from Motorola's website and specified that it was for T-Mobile's network.
All I did was to go online and requested a bootloader unlocking from MotoX.
The phone is now unlocked with TWRP and rooted.
So I am not sure that it cannot be done.
Pat
Click to expand...
Click to collapse
Anyone that bought the AT&T or Verizon retail variants cannot get unlock codes through Motorola due to the carrier not allowing unlocked bootloaders. However, codes can be obtained through a third party without Moto's or AT&T/Verizon knowledge.
Sent from my Moto X.
One more semi-related question since I don't want to make another thread just for this....
I thought I saw somewhere that the 4.4.2 OTA will re-lock the bootloader. Is this to mean that if I bought a code and unlocked the bootloader, it would re-lock if I continued with 4.4.2 or updated to 4.4.3?
No it won't if the bootloader loader is unlocked. If you have a locked bootloader and you are rooted with the write protection disabled. You will at least lose the write protection. I am locked and rooted on 4.4.2. I used supersu pro ota survival and kept root, but that's not guaranteed
Sent from my XT1058 using xda app-developers app
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?