yashsingh1/xdaforums huggingface dataset:
[Moto X General] Durhill:
SLOVED!!! just do a factory reset and everything ok
[Moto X General] Durhill:
I have to thank you so much @ samwathegreat, you saved my life... my wife gift me this cell phone and I actualise it manually, so the files of the modem was erased like you has say before and my phone has no signal (damn) and I search a lot of threads about how to recover the signal without an answer.. until I met you man

now I has 3G signal (that's a really great advance) but I'll try to flash another modem which work on GSM LTE 4G

I'll let you know what result happen
[Moto X General] iBowToAndroid:
The unlock is not contained within the ROM so that won't do any good
[Moto X General] ecs87:
There's too many people trying to take an easy way out. Youd think if all it took was a custom ROM that the instructions would say...use custom ROM X. Instructions weren't made to be skipped nor ignored.
[Moto X General] jordanrules:
Thanks iBowToAndroid for your respons i did not know that. And ecs87 if there were a way to downgrade without the brick i would have done it so dont asume i want the easy way maybe others want it.
[Moto X General] 6E 65 76 69 6E:
Compatibility with lollipop

Now that lollipop update is around the corner (a week away :p ) I don't know whether I am a bit early to ask this but what about the compatibility with lollipop?
[Moto X General] ecs87:
You might just have to wait and see. For the Samsung guys on Sprint devices that were eligible for lollipop, their unlock hack was patched up. Only recently have they found a new loophole. Get ready to pull out your CDMA tools if Moto decides to play NV item # bingo.
[Moto X General] 6E 65 76 69 6E:
I don't care re-doing the process again but a bit doubtful about how Motorola will come up with the update. No company wants a bad reputation of their software being hackable right?!
[Moto X General] elmy2424:
broken wifi and bluetooth after unlocking the third one moto x :crying::crying: they wont turn on anymore,
[Moto X General] PieWai:
Has there been any update regarding the Lollipop update on phones unlocked using this method?
[Moto X General] ong14:
It works on Lollipop, just tried this method on my Sprint X with XT1053 retail US.
[Moto X General] PieWai:
So you performed the unlock on Kitkat before upgrading to Lollipop?

I'm catching up this thread to see whether same can be done to the XT1049 that has been upgraded to Lollipop already.
[Moto X General] 6E 65 76 69 6E:
Regardless of unlock status prior to lollipop, the OTA script will erase the modem and hence you WILL HAVE to perform the unlock process on lollipop and this process is compatible on Lollipop. :)
[Moto X General] PieWai:
Okay, I want to perform this procedure on the RW XT1049. The OP stated that in order to do this, one would have to unlock the bootloader and flash the Sprint ROM.

Does this mean I would now have to flash the XT1056 Lollipop Sprint ROM to perform this procedure (Since downgrades in general are not advised)?

The bootloader of the device in question has already been unlocked by someone for me.

Background: I am using the phone on a GSM/UMTS network and bought the phone from someone who had already unlocked it. This "unlock" reverted to being locked again with the Kitkat and now Lollipop update. The seller unlocked it again previously, but I would like to do it myself this time. The back of my phone says its an XT1049 and the internal settings > about screen is as the attachment shows. I am unable to tell whether this phone is an XT1056 or XT1049, but all I want to achieve is to unlock it and have it working on GSM/UMTS.

Is all in place for me to use this guide to unlock this phone?
[Moto X General] 6E 65 76 69 6E:
Lollipop ROM for Sprint has not been released yet.

What I did:

1. Flashed XT1053 4.4.4 to my XT1056 (Yes, it is not recommended; YOU HAVE BEEN WARNED!)

2. Updated to lollipop using the OTA for XT1053.

3. Booted up to find out that the network was locked (unrecognized sim).

4. Unlocked it again using the method. (FYI, I am not a US resident and I am not on the Sprint network. It is just that I have a Moto X XT1056 and I do all sorts of experiments! ;) )
[Moto X General] PieWai:
Wow.... so what to do next?

My current System version is: 222.21.15.ghost_row.Retail.en.US Sprint as the screenshot above.

Hope anybody can shine some more light here.
[Moto X General] ong14:
You have to do the SIM-unlock process again.
[Moto X General] PieWai:
So I just tried performing the steps but I get stuck at the point where I need to use the SPCUtility.apk to get my SPC code. Note that the device is an XT1049 with the XT1053 Lollipop rom on it. I got to this version by accepting the OTA from Kitkat (4.4.4).

How can I get the SPC code to proceed with the procedures listed in the OP? I've understood well that downgrading is NOT advised and would like to move ahead without doing that (is that possible?).

Some extra info: I am only interested in GSM/UMTS modes since the phone won't be used on a CDMA network.

Please advice.
[Moto X General] ong14:
Try to do this process without SPC code.

Do not downgrade if you are not sure what to do.

In my case, I got XT1056 with 4.4.4.

Then I downgraded to 4.4.2 to get the SPC code.

But I did not take OTA to 4.4.4, I manually flashed to 4.4.4.

When I heard of 5.1 OTA on XT1053, I convert to XT1053 4.4.4 and took OTA to 5.1, then did the SIM-unlock.
[Moto X General] md07:
i Think you have a big problem when you updated Lolippop without SPCcode. You should get it when use Kitkat, and alway remember your code, beacause The tool SPC code only works on Kitkat. So if you downgrade from Lolipop back Kitkat (to use tool SPC), your phone'll bricked.
[Moto X General] ong14:
Agree, but SPCUtility works on 4.4.2 or lower.
[Moto X General] PieWai:
Previous updates were not done by me. The update I did perform was from 4.4.4 to 5.1, on which the SPC code utility would still not work, since it requires 4.4.2 or before.

[MENTION=2509024]samwathegreat[/MENTION] mentioned somewhere in this thread that SPC is not needed for all procedures to unlock the phone. Does this apply to my case?
[Moto X General] ong14:
I've tried this once when I was on 4.4.4, and it worked without SPC code.
[Moto X General] md07:
Link?
[Moto X General] ong14:
I said I've tried to SIM-unlock without SPC code when I was on 4.4.4 Sprint.

And it worked for me.

But I wanted to know my SPC code then I semi-downgraded to 4.4.2 to get it.

Don't do this if you are not sure what you are doing, it may brick your phone.
[Moto X General] md07:
what, you mean, you use NV item reader tool without SPCcode ?
[Moto X General] ong14:
Yes.
[Moto X General] PieWai:
Okay guys and [MENTION=2509024]samwathegreat[/MENTION] What could go wrong if I proceed without having the SPC code.

That is trying to unlock the 5.1 version (XT1053 software on XT1049 hardware) using procedures from OP?
[Moto X General] afox27:
Sam has been gone from xda for 5 or so months. Also it may mess up your modems it may not. It may fail before it dose anything so I guess you have to take a risk here. Shouldn't brick your phone tho.
[Moto X General] PieWai:
I just went ahead without the SPC code and have unlocked the phone. It's only the writing of "nv-ruim-only.txt" that failed due to the absence of the SPC code.
[Moto X General] prince_arsalan:
Always getting this error on writing nv-unlock.txt .. kindly help..

Writing NV-items from a file:

Unsuccessfully written NV-items:

08378 (0x20BA) - Access denied

Done.
[Moto X General] ong14:
You need SPC code.
[Moto X General] Ephemera:
SPC code is only required for RUIM only. I always flash this without the SPC.
[Moto X General] 6E 65 76 69 6E:
I guess you accepted the maintenance update OTA; which *might* have set the NV-ITEM 08378 read only. Just guessing.
[Moto X General] prince_arsalan:
Spc Code Is Correctly entered Bro..

Log message: > SPC is correct. Phone unlocked

Writing NV-items from a file:
Unsuccessfully written NV-items:
08378 (0x20BA) - Access denied
Done.

Writing NV-items from a file:
Done.

Writing NV-items from a file:
Done.

Writing NV-items from a file:
Done.

Just getting error on writing "nv-unlock.txt"..

---------- Post added at 05:24 PM ---------- Previous post was at 05:19 PM ----------

Phone android version is 4.4.4 Build number KXA21.12-L1.28.2.. Phone is boot loader unlocked and Rooted.. So is there any way I can activate Gsm network in it..?? Just getting SIM card error on sims other then sprint..
[Moto X General] 6E 65 76 69 6E:
Try redownloading nv-unlock.txt you used?
[Moto X General] prince_arsalan:
can you kindly share your tested file..??
[Moto X General] 6E 65 76 69 6E:
Well, I'll make it clear. One of the moto x which accepted the recent OTA had exactly the same problem but upon downgrading to the version before, it worked fine.

I don't have access to the file now, but just redownload from OP.
[Moto X General] prince_arsalan:
I have already tried re downloading it from OP Post but no luck... :( And i don't exactly know which Version was running in it before but can you suggest which version shall i downgrade it too..?? and is there a risk of bricking device in downgrading process..??
[Moto X General] 6E 65 76 69 6E:
There is always a risk in downgrading but the maintenance OTA may not have updated the bootloader and partition (my wild guess; ;) ).

Conlcusion:

The nv-unlock.txt failed with read only error on the ROM post the maintenance update but then worked fine on the ROM prior to the maintenance update (ghost_sprint-user-4.4.4-kxa21.12-l1.28-28-release-keys-cid9).
[Moto X General] cedricdhaenens:
Complete downgrade?

I'm having the same issue... I'm really not looking forward to losing all of my data AGAIN, though! Is there no way I can do this without a wipe? Apart from that I wanted to let you all know that Lollipop OTA is coming really soon! :o

UPDATE:

Tried downgrading 4.4.4 to 4.4.2, but got errors while trying to flash 'partition gpt.bin' and 'motoboot.img':

This leaves me pretty much f**ked now... Would dowgrading to an even lower version be an option?

Plz help me out on this one! Thanks
[Moto X General] elmy2424:
had same problem, flashed this 4.4.4 stock firmwarehttp://xdaforums.com/showpost.php?p=55854354&postcount=11 then unlocked the phone without problem, what prevents the NV item to be changed is a short 5.4mb OTA that comes after this one.

hope it works to you:good:

LOL just took the 5.4mb OTA and phone blocked again, 0_0
[Moto X General] 6E 65 76 69 6E:
The OTA scripts may be:

erasing the modemst1 and modemst2

making the NV-ITEM read only preventing it to be patched

So it is pretty much clear; Sprint has patched the vulnerability.
[Moto X General] cedricdhaenens:
Thanks elmy2424! ;) I indeed remember a small update after the main one!

Will try it out tonight! ::o
[Moto X General] 6E 65 76 69 6E:
Yes, the 4.4.4 ROM prior to the maintenance OTA
[Moto X General] cedricdhaenens:
Yes okay, I think that would be the:

ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9

That system version is: 212.44.28.ghost_sprint.Sprint.en.US

Right?
[Moto X General] cedricdhaenens:
Solved it!

I can confirm that this indeed solved my problem.

Thanks to elmy2424 & 6E 65 76 69 6E! :o:D
[Moto X General] bobby2478:
I just re-installed Sprint factory image "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9", and after doing this successfully I received an OTA update notification, which I installed. Now when I check my System Version and Build numbers, I see the following:

Android Version: 4.4.4

Kernel Version: 3.4.42-g6b785f7

System Version: 212.144.2.ghost_sprint.Sprint.en.US

Build Number: KXA21.12-L1.28.2

Can anyone with the most up to date stock Sprint Moto X confirm for me that this looks correct? I was curious why my system version only shows 212.144.2, build number shows 21.12-L1.28.2, while Moto's website says 212.44.28. Just want to make sure everything is up to date and back to stock. THanks!
[Moto X General] nukeman239:
I have Sprint Moto X running 4.4.2. How do I go about unlocking it for GSM only outside the States? If I have the SPC code, can I take the maintenance OTA?
[Moto X General] 6E 65 76 69 6E:
The maintenance OTA will block writing the NV-ITEM
[Moto X General] nukeman239:
Thanks for the prompt reply. So, what do you suggest I do?
[Moto X General] 6E 65 76 69 6E:
Unlock it now and DON'T accept the OTA.
[Moto X General] nukeman239:
Oh! So no KitKat for me? Here, I was expecting to use it on Lollipop. Lol! Can things change in the future or I am stuck with 4.4.2 for ever?
[Moto X General] 6E 65 76 69 6E:
Read a couple of posts ahead of this one.

Nobody said you are stuck on 4.4.2.
[Moto X General] nukeman239:
Take the first 4.4.4 OTA & ignore the one that comes next. Correct? Also, if I unlock now & then take the OTA, will the unlock stick?
[Moto X General] 6E 65 76 69 6E:
I can't recommend the OTA since I do not understand which OTA you are referring to.

Lately sprint released a maintenance OTA which is less than 10MB in size and that's the troublesome OTA update that I mentioned in the earlier posts. I can't mention the build number etc because I'm currently on CM.
[Moto X General] nukeman239:
The OTA's build number is 212.44.28.en.US. It is 148MB in size.
[Moto X General] 6E 65 76 69 6E:
Think that's safe to update.
[Moto X General] nukeman239:
I hope someone is able to tweak the unlock process when Lollipop arrives.
[Moto X General] iBowToAndroid:
There's nothing that can be "tweaked". That's the NV items that need to be modified in order for the phone to be unlocked. If the items are deemed read-only by the software, then there's no way around that besides downgrading
[Moto X General] nukeman239:
So basically no Lollipop for unlockers?
[Moto X General] 6E 65 76 69 6E:
Probably yes!
[Moto X General] iBowToAndroid:
Well assuming they leave the NV items as read-only in Lollipop, the unlock would have to be accomplished by unlocking the bootloader, downgrading firmware (which could be dangerous, going back that far), performing the unlock, and then flashing custom recovery and ROM if Lollipop is desired
[Moto X General] nukeman239:
Alright. Thanks for the detailed response. One last thing. Any news on the Lollipop update for the Sprint variant? There is nothing XDA. I even Googled it but nothing concrete. Your thoughts?
[Moto X General] iBowToAndroid:
No idea. Ask Sprint and Moto
[Moto X General] Anonyhead:
Ok, this is my situation, I recently bought a used XT1056 with confirmed clean ESN. It came with system version 212.44.28 (Kitkat 4.4.4) and was SIM unlocked (I don't know the procedure used to SIM unlock). SIM registered to my GSM/UMTS network without a hitch. Voice, data, WIFI, sensors etc all worked. Of course that wasn't good enough for me. I "researched" the various techniques and I was able to: unlock the bootlader, install latest custom recovery (TWRP), install latest SuperSU and finally install latest CyanogenMod Nightly. Yet again, SIM registered to my network, voice, data, WIFI, sensors etc all worked... except for the worst battery drain I have ever seen on a phone. The battery drain is a known issue but not one I was willing to battle so again to Google to find the best way to get back to stock (or so I thought). My conclusion was to use RSDLite to flash ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml. The flash was smooth and error free. On reboot I had assumed that the bootloader would have been locked but it wasn't, after lots of googling I still can't decide if that is normal and would appreciate some confirmation. The next minor issue was the Sprint Activation nagscreen that has since presented itself after every reboot and requires action to close. If the nagscreen was my only issue I would have remained a lurker here but part A of the the real problem was that I got a SIM Error notification and my SIM was unable to register on the network. The search to sort that issue led me here. Being on 4.4.4 the MSL Utility doesn't work so I used the modified version of the original post to successfully flash the attached nv-unlock.txt, nv-unlock2.txt and unlock-domestic.txt (of course, I tried flashing the nv-ruim-only.txt but no luck). On reboot I made the required settings changes and my sim registered quickly. Now, my understanding was that after every reboot I would have to reset the network settings, but that has not been the case, after every reboot I close the activation nagscreen and my network is up and running. Part B of the problem is that I assumed I wouldn't be faced with an OTA update that might possible render this SIM Unlock solution useless but no. As the phone settled down after the first reboot into the newly flashed stock ROM I had a screen pop open with this heading "New system software available! New version: 212.144.2.en.US". That popup has gotten more insistent too, showing up at least every half hour, and filling the entire screen. After all that "context" my questions are: 1. Not that I mind but why don't I have to reset my network after each boot? and more importantly 2. If I take this update will it disable this SIM Unlock procedure? Many, many thanks to the original poster and all contributors for getting me back on my network.
[Moto X General] iBowToAndroid:
If you accept that update, you won't be SIM unlocked anymore.

PS. Reflashing stock does not relock one's bootloader. You can only do that yourself via terminal command
[Moto X General] Anonyhead:
Well I guess no LP for me, when will I learn to leave well enough alone. Thanks anyway.
[Moto X General] nukeman239:
I unlocked my phone on 4.4.2, then flashed the Retail XT1053 Lollipop 5.1 ROM from the Dev section. The unlock sticks & the best part is LTE is available. I'm using it Internationally though.
[Moto X General] stanucc:
Wow, this is a good news
[Moto X General] gpz1100:
Does your speakerphone work - are you able to toggle while in a call? Which exact rom did you use?
[Moto X General] nukeman239:
Sorry, I don't have the phone with me at the moment to test the speakerphone but it does work as far as I can recall. About the ROM, it is one below.

http://xdaforums.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
[Moto X General] gpz1100:
^^Better check. Had to revert back to 4.4.4 because this function didn't work in that rom. If call is initiated with speaker on, then only speaker will work. Same for earpiece. You can't toggle between the two during the call.
[Moto X General] crabbyone:
Quick question: If I unlock the boot loader and install the latest CyanogenMod, do I need to use the GSM unlock method listed here or will it work with AT&T? I have an XT1056 my wife was using on AT&T with no issues, but she switched to an iPhone and I was thinking of selling it or using it to play with. I have an AT&T version on 5.1 have the same issues with it everyone seems to be having (handset to speaker, noise and battery life).
[Moto X General] iBowToAndroid:
Unless CM has implemented an option to do this unlock (unlikely), then you'll need to unlock it before you flash the ROM
[Moto X General] trissypissy:
where did you find a sprint 4.4.2 image that will render this workable

(the phone i'm working with has already OTA'd to 4.4.4)
[Moto X General] nukeman239:
I too can confirm that the speaker does not work on the ROM. Looks like the end of the road for the unlocking scene on this device.
[Moto X General] lurker316:
First off I would like to thank the OP for bringing to light such an exploit or method of Sim Unlocking. Thanks!

I would like to share my experience with this phone. I bought this phone in the UAE. It came all sealed and packed. The model was XT1056. It was the sprint variant. It comes with Jellybean 4.2.2 I believe. I put in a Local GSM sim in it and it was working just fine. Except for the LTE part. Initially I had to manually go into Network Mode and change it from CDMA to GSM/UMTS.

Then I started updating the phone and with each update I tested the Local SIM cards and they seemed to be working just fine. So I updated using OTA and went to kitkat 4.4.4. And SIM cards worked just fine. Then came a small security update which was about 5.4Mb after the Kitkat Update. This Update stopped the Sim card recognition. I kept getting sim card errors.

So I used RDSLITE and re-flashed the 4.4.4 Sprint Kitkat update which was before the Security update. Phone booted up fine but still sim card errors persisted. I may add that I had forgotten to get the SPC while I was on Jellybean. So I didn't have that. I used the NV Writer and Only wrote the nv-unlock.txt file. If you don't downgrade from the Security Update, the NV-Unlock.txt file cannot be written as I think it's write protected. So after the downgrade and after writing just the nv-unlock.txt file, GSM Sim cards started working again. I can't say anything about CDMA because I don't have such a service in UAE.

But that's what I did. That 5.4Mb security update Sim Locks the phone.

Dunno if OTA lollipop after that can fix this? After that 5.4Mb Security update, there were no more OTA updates available.
[Moto X General] 6E 65 76 69 6E:
The vulnerability is already patched by Sprint (the latest maintenance update) so Lollipop (once released) will also won't let you unlock network.

As I had mentioned earlier, the NV-ITEM will be read only and hence this method will fail on Lollipop too.

The only workarounds if you want lollipop:

1. Flash stock lollipop for XT1053 and unlock network using this method

or

2. Flash CM12.1
[Moto X General] tomhtg90:
Happen to me, too when update to 4.4.4 version 212.144.2.en.US. But i got replacement and got the same version sprint XT1056 but in 212.44.28 version. So, sim card working just fine. And from now on, i will never update again.

Sorry for OOT. are all custom rom on development thread can be flash on my device (sprint XT1056) with working sim unlock? or just CM12.1? thx
[Moto X General] 6E 65 76 69 6E:
ROMs based on CM should work fine..
[Moto X General] lurker316:
As long as CM is available with Lollipop support for this phone I don't really care much for OTA Lollipop Stock from Sprint. As it is I am not happy with them calling an Unlocked Sim a "vulnerability" and shutting it down. For some time I even gave them the benefit of doubt that perhaps this maintenance update was broken and they will quickly release a new one to "Fix" the problem they just created.
[Moto X General] 6E 65 76 69 6E:
No company wants their software to be hacked! So I strongly believe that they made the NV-ITEM read-only preventing any modifications to it. I do not see a reason why they should change their mind when they release lollipop! So that's it!
[Moto X General] lurker316:
It's not the hacking part that bothers me. These phones are sold by Sprint as Unlocked phones. They should be able to accommodate all sorts of SIMs. And they were infact working on Stock Roms from Jellybean to Kitkat until that extra "vulnerability" update. Which so happens to be the Last OTA update from Sprint for this phone thus far. This Last update causes that Sim Card Read Error with ALL sims except Sprint's own. It's like they did an about turn on "Sim Unlocked" advertising for this phone. Nobody would necessarily resort to hacking this phone if Stock Rom continued supporting the Unlocked Sim policy.
[Moto X General] iBowToAndroid:
When have they ever been sold or advertised as unlocked?

Extremely incorrect...
[Moto X General] 6E 65 76 69 6E:
I can't stop laughing! Whats the point of this thread if Sprint allowed unlocking? :p
[Moto X General] iBowToAndroid:
Exactly.

Moto X sold directly from Moto at full price or from Play Store, etc? Yes, unlocked.

Sprint version? Very different story.

Only phones that Sprint has ever sold unlocked are Nexus'
[Moto X General] hmajid_039:
Need Your Attension

Hello lurker316...!

Can you please confirm that which system version you are running now?

are you facing any updating profile issues when you boot up phone?

Thanks
[Moto X General] tomhtg90:
WTA

Is SPC number always the same even after upgrade? or it change if we update the rom. Thx