Related
Hello,
I recently lost my IMEI and just got my replacement phone from Motorola. I'm looking to unlock and root again but I don't want to lose the IMEI again! Is there a way to back it up? I've seen how to do it on other phones but nothing for the Moto X 2nd Gen yet.
Thanks.
You don't "lose" your IMEI as such. It won't not show up, in case you flash a wrong radio. Unlocking the boot loader and rooting your phone alone won't make your IMEI disappear. So go ahead and unlock, root you'll be fine
Yeah, what did you do besides rooting to get to where you were? I suspect you flashed an inappropriate modem somehow? Can you confirm?
CaptainMocha said:
Hello,
I recently lost my IMEI and just got my replacement phone from Motorola. I'm looking to unlock and root again but I don't want to lose the IMEI again! Is there a way to back it up? I've seen how to do it on other phones but nothing for the Moto X 2nd Gen yet.
Thanks.
Click to expand...
Click to collapse
Back up your /pds partition, in the sticky in this forum you can find a guide
I'm about to buy a used Moto X XT1060 in a couple of days. I understand thats the Verizon variant of the phone.
I wanted to make sure that this phone will work fine on GSM and 3G networks in my country. My country uses 850/1800 for GSM, 2100 for 3G and 1800 (Band 3) for LTE. I know that LTE wont work cause this device doesnt have band 3 but Im quite happy with 3G.
Can you guys please confirm that 3G will work fine on this phone? Ive found some threads here on XDA from people who are having issues using 3G data on this phone.
http://en.wikipedia.org/wiki/Moto_X_(1st_generation)#Variants
XT1060
CDMA Bands: 850/1900
GSM Bands: Quad
UMTS Bands: 850/900/1900/2100
LTE Bands: 4/13
All variants support four 2G GSM bands 850/900/1800/1900.
The XT1050 is a regional device for smaller carriers but uses identical bands.
The Verizon XT1060 is CDMA/GSM variant that is SIM unlocked out of the box. To use the XT1060 on a GSM carrier, you need to force its radio to GSM and the Verizon firmware will always tell you its a "non-verizon sim" inserted in the phone.
It supports the following frequencies..
CDMA = 800/1900
GSM/GPRS/Edge (aka 2G/2.5G) = 850/900/1900/2100 MHz
UMTS/HSPA (aka 3G) = 850/900/1900/2100 Mhz
HSPA+ (aka 4G) = 850/900/1900/2100 Mhz
4G LTE = Band 4 and 13.
When using on GSM carriers, it will get the fastest connection based on what the phone supports vs what the carrier uses.
To be honest, If you want to use it on a GSM carrier, you're better off getting the XT1053, or other GSM unlocked X. And.. take a look at this thread... http://forum.xda-developers.com/moto-x/moto-x-qa/xt1053-xt1060-developer-edition-t3057585
Hey guys! Thanks for the help @fury683 and especially @KidJoe
Fortunately, I'm very well versed with the frequencies supported by the phone.
And my first choice would be to try and get a XT1052 - the international variant.
Unfortunately, in my city, the only variant available is the XT1060 and the too the retail version.
All I wanted to confirm was whether the Verizon Firmware will give me any problems like not detecting my sim or not connecting to 3G networks (local networks use 2100 for both HSPA & HSPA+ so theoretically it shouldn't have any problems).
Also, can I root it? There's a 90% chance that it'll be running 4.2.2 so I've heard there's the Sunshine unlocking method or something which can help me unlock the bootloader (unless the previous owner already did it; in which case it'll be a blessing!)
And is there anyway I can confirm if the phone is refurbished (whether it has been opened at any point in its life)?
usmanshahid said:
Hey guys! Thanks for the help @fury683 and especially @KidJoe
Fortunately, I'm very well versed with the frequencies supported by the phone.
And my first choice would be to try and get a XT1052 - the international variant.
Unfortunately, in my city, the only variant available is the XT1060 and the too the retail version.
All I wanted to confirm was whether the Verizon Firmware will give me any problems like not detecting my sim or not connecting to 3G networks (local networks use 2100 for both HSPA & HSPA+ so theoretically it shouldn't have any problems).
Also, can I root it? There's a 90% chance that it'll be running 4.2.2 so I've heard there's the Sunshine unlocking method or something which can help me unlock the bootloader (unless the previous owner already did it; in which case it'll be a blessing!)
And is there anyway I can confirm if the phone is refurbished (whether it has been opened at any point in its life)?
Click to expand...
Click to collapse
The XT1060 will work on GSM for carriers supporting/using the "standard 4" (850/900/1900/2100 MHz). You MIGHT have to manually enter your APN settings.
As for rooting, If the phone has 4.4.2 or lower, and has NEVER had 4.4.4 on it, you can use Sunshine to unlock the bootloader, then root. IF you receive the phone and it has 4.4.4 on it, you will not be able to unlock the bootloader. And there is no root method for 4.4.4 with a locked bootloader.
I found this beautiful AT&T Moto X today. And before I finalize the deal in a day or two, I want to run a few things by you guys;
1. The phone is running '165.44.1.ghost_att.ATT.en.US' - which is 4.4.2, right?
The bootloader is locked with a Status '0'. So I guess rooting is out of the question, right?
2. When I opened the phone in fastboot, it showed the following bootloader info;
30.B4 (sha-a542ee0)
What does that mean, exactly?
3. Under the 'Kernel Version', it showed some numbers and this;
[email protected]#1
a date stamp
^What does this mean?
I had the phone in my hand for about a good twenty minutes. It was in a very good condition. Had the AT&T logo and a tiny "assembled in USA" stamp on the back. It had a couple of AT&T apps as well.
So what do you guys think? Should I go for it? And are there any other things I should check before I cough up the cash?
And is there any way I can check NFC in the store?
Oh and did the new XT1058 come as a network locked device? Will I be able to run it on my local networks without any locking issues? (all frequency bands available on the phone are supported in my country!)
@KidJoe The phone was showing its IMEI in the "About Phone" tab in the settings menu.
So that should indicate its free from that dead IMEI issue that some of the other guys on XDA faced, right?
Also, I've heard the Rogers stock ROM is almost completely free of bloat. So can I flash a Rogers 4.4.2 SBF without unlocking the bootloader on the phone?
usmanshahid said:
I found this beautiful AT&T Moto X today. And before I finalize the deal in a day or two, I want to run a few things by you guys;
1. The phone is running '165.44.1.ghost_att.ATT.en.US' - which is 4.4.2, right?
The bootloader is locked with a Status '0'. So I guess rooting is out of the question, right?
Click to expand...
Click to collapse
That is correct. Its 4.4.2
usmanshahid said:
2. When I opened the phone in fastboot, it showed the following bootloader info;
30.B4 (sha-a542ee0)
What does that mean, exactly?
Click to expand...
Click to collapse
That is the bootloader version. Its consistent with 4.4.2... WHICH IS GOOD!!!
Use Sunshine to unlock the bootloader, then you can root no matter what rom is on your phone.
usmanshahid said:
3. Under the 'Kernel Version', it showed some numbers and this;
[email protected]#1
a date stamp
^What does this mean?
Click to expand...
Click to collapse
I'm not sure the Kernel Version for the ATT roms. Sorry.
usmanshahid said:
I had the phone in my hand for about a good twenty minutes. It was in a very good condition. Had the AT&T logo and a tiny "assembled in USA" stamp on the back. It had a couple of AT&T apps as well.
So what do you guys think? Should I go for it? And are there any other things I should check before I cough up the cash?
And is there any way I can check NFC in the store?
Oh and did the new XT1058 come as a network locked device? Will I be able to run it on my local networks without any locking issues? (all frequency bands available on the phone are supported in my country!)
@KidJoe The phone was showing its IMEI in the "About Phone" tab in the settings menu.
So that should indicate its free from that dead IMEI issue that some of the other guys on XDA faced, right?
Also, I've heard the Rogers stock ROM is almost completely free of bloat. So can I flash a Rogers 4.4.2 SBF without unlocking the bootloader on the phone?
Click to expand...
Click to collapse
If you do NOT take any updates, you can unlock the bootloader using Sunshine, and then you're free to upddate, and root as you wish.
To test NFC in "store", if you have a fitbit Flex, Force or Charge, install the fitbit app on the phone, tap your fitbit device. Does the app launch? If yes, NFC is working fine. I don't know of another way.
The XT1058 is SIM Locked (aka carrier locked), but you can purchase a SIM unlock code on line cheap, unless you can get ATT to provide it to you (you have to meet their conditions).
You can NOT flash anything but stock Moto XT1058 for ATT rom unless you unlock the bootloader.
KidJoe said:
That is correct. Its 4.4.2
That is the bootloader version. Its consistent with 4.4.2... WHICH IS GOOD!!!
Use Sunshine to unlock the bootloader, then you can root no matter what rom is on your phone.
I'm not sure the Kernel Version for the ATT roms. Sorry.
If you do NOT take any updates, you can unlock the bootloader using Sunshine, and then you're free to upddate, and root as you wish.
To test NFC in "store", if you have a fitbit Flex, Force or Charge, install the fitbit app on the phone, tap your fitbit device. Does the app launch? If yes, NFC is working fine. I don't know of another way.
The XT1058 is SIM Locked (aka carrier locked), but you can purchase a SIM unlock code on line cheap, unless you can get ATT to provide it to you (you have to meet their conditions).
You can NOT flash anything but stock Moto XT1058 for ATT rom unless you unlock the bootloader.
Click to expand...
Click to collapse
Thanks for all your help!
I got the phone today. It's on 4.4.2 and is already SIM unlocked. I plan to unlock the bootloader after a few days!
usmanshahid said:
Thanks for all your help!
I got the phone today. It's on 4.4.2 and is already SIM unlocked. I plan to unlock the bootloader after a few days!
Click to expand...
Click to collapse
Cool, just make sure you do NOT take any Over The Air Updates. Once you get 4.4.4 on there, you wont be able to bootloader unlock an ATT XT1058.
@KidJoe
Dude, I ran into a problem with Sunshine. They don't accept my credit card and I don't have a paypal account.
I'm working on getting a new card, but in the mean time I wanted to ask if I could use the Pie hack to temporarily root the phone to remove the AT&T bloatware.
Would that work?
usmanshahid said:
@KidJoe
Dude, I ran into a problem with Sunshine. They don't accept my credit card and I don't have a paypal account.
I'm working on getting a new card, but in the mean time I wanted to ask if I could use the Pie hack to temporarily root the phone to remove the AT&T bloatware.
Would that work?
Click to expand...
Click to collapse
Yes, but keep in mind that TowelPie is a temp root and doesn't disable write protection. So, Boot, root, remove the bloat, but if you reboot the phone (or power off/on), bloat returns and you need to re-root
@KidJoe
I unlocked my phone's (ATT XT1058) bootloader recently using Sunshine.
Unfortunately, after I updated it to 4.4.4, it somehow got network locked.
Can I remove the network lock by flashing the stock ROM of the international Moto X (XT1052)?
usmanshahid said:
@KidJoe
I unlocked my phone's (ATT XT1058) bootloader recently using Sunshine.
Unfortunately, after I updated it to 4.4.4, it somehow got network locked.
Can I remove the network lock by flashing the stock ROM of the international Moto X (XT1052)?
Click to expand...
Click to collapse
Flashing the rom from a different model will not sim unlock you.
KidJoe said:
Flashing the rom from a different model will not sim unlock you.
Click to expand...
Click to collapse
So how do I SIM unlock my phone? Besides getting the code from ATT.
Is there any way to do it for free?
Thank you for your help!
EDIT: In many of your threads you've warned people to not attempt to downgrade the ROM. Meaning I can't flash a Stock 4.4.2 SBF after I've updated the phone to 4.4.4.
But what if flash a custom ROM like cyanogenmod and then attempt to flash the stock 4.4.2 SBF. Will it still brick my phone?
usmanshahid said:
@KidJoe
Dude, I ran into a problem with Sunshine. They don't accept my credit card and I don't have a paypal account.
I'm working on getting a new card, but in the mean time I wanted to ask if I could use the Pie hack to temporarily root the phone to remove the AT&T bloatware.
Would that work?
Click to expand...
Click to collapse
You can use Western-Union to transfer your payment to the sunshine developers... Im also from Pakistan and Unlocked my bootloader through sunshine by using the western union payment method... You dont need to work hard for a new credit card..
usmanshahid said:
So how do I SIM unlock my phone? Besides getting the code from ATT.
Is there any way to do it for free?
I just spent around $35 on Sunshine (the $10 extra was for transferring the money from my country).
It may not sound like much, but it's a lot in my country.
Click to expand...
Click to collapse
I don't have anything I can suggest to SIM unlock the XT1058 for free. Some services online sell SIM unlock codes, that would be the only thing I can suggest.
usmanshahid said:
EDIT: In many of your threads you've warned people to not attempt to downgrade the ROM. Meaning I can't flash a Stock 4.4.2 SBF after I've updated the phone to 4.4.4.
But what if flash a custom ROM like cyanogenmod and then attempt to flash the stock 4.4.2 SBF. Will it still brick my phone?
Click to expand...
Click to collapse
CM11, CM12, or any ROM based on AOSP, only flash SYSTEM, and do not touch gpt.bin or the critical parts of motoboot.img. So if you go from Moto 4.4.4 -> CM, you still have parts of the Moto 4.4.4 on there... So later if you go CM -> Moto 4.4.2 SBF, you're still at risk of bricking.
And the next question you will likely ask is... "what if I skip those parts"... To that I say... Read items 11, 13, 14, 16, and 17 at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
KidJoe said:
I don't have anything I can suggest to SIM unlock the XT1058 for free. Some services online sell SIM unlock codes, that would be the only thing I can suggest.
CM11, CM12, or any ROM based on AOSP, only flash SYSTEM, and do not touch gpt.bin or the critical parts of motoboot.img. So if you go from Moto 4.4.4 -> CM, you still have parts of the Moto 4.4.4 on there... So later if you go CM -> Moto 4.4.2 SBF, you're still at risk of bricking.
And the next question you will likely ask is... "what if I skip those parts"... To that I say... Read items 11, 13, 14, 16, and 17 at -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Click to expand...
Click to collapse
Thank you for all your help and advice. I really appreciate it!
@KidJoe
Sir, I went through your blog on cdmaforums and I have a couple of questions.
1. Due to the GPT.BIN issue, will all the nandroid backups I made using TWRP on 4.4.4 become useless after I update to Lollipop in future?
2. If (after its released), I take the Lollipop OTA file, extract it and only flash the system and boot images will I still have the GPT.BIN issues?
Cause technically, I will have the gpt.bin file from 4.4.4 and all my nandroid backups should work just fine, no?
Found another thread where you warned us not to try this.
3. Supposedly while messing about with my phone, I brick it. Can I get it back to normal?
I found a method to do this on your blog, but I was wondering if it could be used to recover from the messed up gpt.bin files?
[I want to try the thing I mentioned in point 2 above so I need to know if I'll be able to recover my phone if something happens.]
4. What is NON-HLOS.BIN? I found this file in a 4.4.4 SBF that I extracted. Didn't flash it - I was moving from ATT 4.4.4 to EU 4.4.4 so I guess it wouldn't have made much of a difference.
5. I have a ATT phone which was carrier locked. Will erasing the modemst partitions re-activate the modem lock?
6. After I've downloaded an OTA via the system update option on my phone, is there anyway to extract that OTA from the /cache partition?
7. I had a stock ATT 4.4.4 ROM from which I switched to the stock EU 4.4.4 ROM (I didn't flash the entire EU SBF because TWRP was giving an error - MD5 sums didn't match - so I extracted the system and boot partitions and flashed those). So now, as I understand, if I get an official 5.1 OTA, all I have to do is flash the stock recovery and install the OTA after which I can re-flash TWRP again. That correct, or am I missing something?
Thank you!
usmanshahid said:
@KidJoe
Sir, I went through your blog on cdmaforums and I have a couple of questions.
1. Due to the GPT.BIN issue, will all the nandroid backups I made using TWRP on 4.4.4 become useless after I update to Lollipop in future?
2. If (after its released), I take the Lollipop OTA file, extract it and only flash the system and boot images will I still have the GPT.BIN issues?
Cause technically, I will have the gpt.bin file from 4.4.4 and all my nandroid backups should work just fine, no?
Found another thread where you warned us not to try this.
3. Supposedly while messing about with my phone, I brick it. Can I get it back to normal?
I found a method to do this on your blog, but I was wondering if it could be used to recover from the messed up gpt.bin files?
[I want to try the thing I mentioned in point 2 above so I need to know if I'll be able to recover my phone if something happens.]
4. What is NON-HLOS.BIN? I found this file in a 4.4.4 SBF that I extracted. Didn't flash it - I was moving from ATT 4.4.4 to EU 4.4.4 so I guess it wouldn't have made much of a difference.
5. I have a ATT phone which was carrier locked. Will erasing the modemst partitions re-activate the modem lock?
6. After I've downloaded an OTA via the system update option on my phone, is there anyway to extract that OTA from the /cache partition?
7. I had a stock ATT 4.4.4 ROM from which I switched to the stock EU 4.4.4 ROM (I didn't flash the entire EU SBF because TWRP was giving an error - MD5 sums didn't match - so I extracted the system and boot partitions and flashed those). So now, as I understand, if I get an official 5.1 OTA, all I have to do is flash the stock recovery and install the OTA after which I can re-flash TWRP again. That correct, or am I missing something?
Thank you!
Click to expand...
Click to collapse
Except for NON-HLOS.BIN, What you are asking is pretty much covered in -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
but I'll reply here anyway...
1. You could restore them, BUT once you have a newer ROM installed on the phone, due to the mismatch of GPT.bin and Motoboot.img parts of the phone, you'll likely encounter bugs and potentially some features not working (due to the mismatch between the GPT and Motoboot parts and the rest of your rom, and the mismatch of any other parts of the phone not included in the nandroid back up made with TWRP).
2. Although you scratched and said you found the thread... Again, see my answer to #1.
3. There are varying degrees of "bricking." If you still can access the phone via fastboot, in some cases recovery is as simple as re-flashing the SBF that matches the NEWEST version you had on your phone. Other cases its much harder than that, and still other cases you can't recover at all. We've seen it all.
4. it either IS or IS RELATED TO the MODEM of the phone.
5. I'm sorry, I do not know for sure.
6. After downloading, but before installing, the OTA update ZIP file is stored on the phone in /cacahe folder. You need to be rooted to access this folder. If you are rooted, you can copy this file to /SDcard to then copy it to your PC or elsewhere.
7. First off, TWRP doesn't work with flashing IMG files from inside an SBF so I'm not sure what you were trying there. But anyway... IF you used mfastboot to flash EU's System.IMG and BOOT.IMG to your phone, IF you get notified for an available update, it will be the update for the EU ROM. It will be interesting to see what happens. Due to the mix-matched parts on your phone (system/boot from EU, rest from ATT USA), the pre-flash validation might fail, and the OTA wont install. However, IF enough of your phone matches the EU rom, then the update will install and PATCH files/parts on the phone with the EU version, then you may be stuck on the EU version..
KidJoe said:
7. First off, TWRP doesn't work with flashing IMG files from inside an SBF so I'm not sure what you were trying there. But anyway... IF you used mfastboot to flash EU's System.IMG and BOOT.IMG to your phone, IF you get notified for an available update, it will be the update for the EU ROM. It will be interesting to see what happens. Due to the mix-matched parts on your phone (system/boot from EU, rest from ATT USA), the pre-flash validation might fail, and the OTA wont install. However, IF enough of your phone matches the EU rom, then the update will install and PATCH files/parts on the phone with the EU version, then you may be stuck on the EU version..
Click to expand...
Click to collapse
I'm sorry, I should have been more clear.
TWRP was giving errors so I opened the zip file on a computer and flashed the system.img and boot.img via the fast boot command.
I had flashed the recovery.img as well, but that got overwritten when I flashed TWRP again. Pretty much all that was left was gpt.bin file, non-hlos.bin, fsg.mbn and motoboot.img.
As I understand it, motoboot.img is the bootloader and gpt.bin is a partition table and both these files will be the same for all 4.4.4 ROMS.
And non-hlos.bin and fsg.mbn are modem files which should also be the almost same for both EU and ATT ROMS. Except maybe having a modem lock or something on the ATT version.
Before I take the OTA, I'll flash the recovery.img from the EU 4.4.4 SBF which I unzipped to prevent clashes.
Do you think the rest of the files would be enough to cause the pre flash validation check to fail?
Could you elaborate on what you mean by 'stuck on the EU version'?
And would you recommend that I take the OTA, provided I get one?
Thank you!
I have Moto X (2013), I want to know why my phone is still on 4.4.2 KitKat and not getting any newer updates? Others running 4.4.4 KitKat and about to get Android L, what's wrong with my phone? I have tried resetting my phone couple of times and tried Motorola Device Manager too but no luck. I don't know whether I have XT1049 or XT1058 because I got this phone from a friend, he just gave it away and I am not living in a country where I can get Motorola Support. I thought I had XT1049, I contacted Republic Wireless, they checked my IMEI number and told me that it's not their phone, I contacted Motorola's online support they told me by looking at the IMEI number it's XT1058 AT&T phone but when I connect my phone to my computer it says "XT1049 is connected to the computer" and in pictures "details" I can see that the picture is taken by XT1049, I am so confused. Kindly help, I want updates coming to my phone
Dee Singh said:
I have Moto X (2013), IMEI # 990002933335380, I want to know why my phone is still on 4.4.2 KitKat and not getting any newer updates? Others running 4.4.4 KitKat and about to get Android L, what's wrong with my phone? I have tried resetting my phone couple of times and tried Motorola Device Manager too but no luck. I don't know whether I have XT1049 or XT1058 because I got this phone from a friend, he just gave it away and I am not living in a country where I can get Motorola Support. I thought I had XT1049, I contacted Republic Wireless, they checked my IMEI number and told me that it's not their phone, I contacted Motorola's online support they told me by looking at the IMEI number it's XT1058 AT&T phone but when I connect my phone to my computer it says "XT1049 is connected to the computer" and in pictures "details" I can see that the picture is taken by XT1049, I am so confused. Kindly help, I want updates coming to my phone
Click to expand...
Click to collapse
Your device belongs with ACG Regional Carriers. It is currently at 4.4.2 only. You can see your model in the lower area of your back panel..
Check out moto site for your device. Your "System Version" in the screen shot is "161.44.38.ghost_row.ACGLTE.en.US". Check out...
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94927/p/30,6720,8696
lol u are lucky because we AT&T users updated to 4.4.4 and now stucked :::: cant root or unlock bootloader and sunshine is only working till 4.4.2 so be happy and unlock it root it and enjoy any custom rom
Thanks for the help
Now I know that I have "ACG Regional Services" phone, any idea about me getting updates in future or is there another easy option to get the 4.4.4 or 5.0.2 update?
Javajohn said:
lol u are lucky because we AT&T users updated to 4.4.4 and now stucked :::: cant root or unlock bootloader and sunshine is only working till 4.4.2 so be happy and unlock it root it and enjoy any custom rom
Click to expand...
Click to collapse
I really don't have any idea how to unlock and root or use any custom rom, I am afraid I will break my phone if I try, suggest anything else or tell me how to do it in an easiest way
Dee Singh said:
I really don't have any idea how to unlock and root or use any custom rom, I am afraid I will break my phone if I try, suggest anything else or tell me how to do it in an easiest way
Click to expand...
Click to collapse
here is the best thread for you to start
CLICK ME
Unlock your bootloader first theroot.ninja , rooting after that is easy, so is anything else you want to do with your phone.
Dee Singh said:
Now I know that I have "ACG Regional Services" phone, any idea about me getting updates in future or is there another easy option to get the 4.4.4 or 5.0.2 update?
Click to expand...
Click to collapse
OTA updates are really up to your carrier and/or Motorola. You will seen no updates, until THEY make them available.
When the bootloader is locked, you can only flash official roms (or parts like recovery) for your model/carrier, which are digitally signed by Motorola. Attempts to flash anything else, will fail.
Dee Singh said:
I really don't have any idea how to unlock and root or use any custom rom, I am afraid I will break my phone if I try, suggest anything else or tell me how to do it in an easiest way
Click to expand...
Click to collapse
As for unlocking the bootloader, and/or rooting.. see -> http://forum.xda-developers.com/mot...w-root-moto-x-confusion-t2826159/post54671918
Why would you want to unlocked the bootload? So you could flash either a totally custom rom, or a rom meant for another carrier/model 2013 X which might be newer. (like some ATT XT1058 users like to flash Rogers XT1058 rom to get rid of the ATT bloat).
I really know nothing about the "ACG Regional Carriers" variant of the Moto X. I'm not sure if it might be the same hardware as another variant, only with a different ROM flashed on it. So I don't know if its safe to flash another carrier's ROM on it. But with an unlocked bootloader, you can try 3rd party roms like CM11 or CM12.
Unlock the BL and flash custom ROMs
You may want to edit your post and remove your imei number. It can be hijacked and leave you with a non functioning device. (no calls or texts or data anyway.)
?
i've managed to recover the imei (dont know exactly how) and everything seems to be working now.
Regards.
------------------------------------------------
Hello everyone,
First of all, sorry for my English and thanks in advance.
I recently bought a Moto x XT1060 (Verizon), unlocked bootloader with Sunshine, installed TWRP and CM 12.1
Everything went fine for 2 days, LTE and calls without problems, but suddenly i wasn't able to make calls anymore (LTE still working) so i decided to flash a modem through fastboot and i did, but now the device does not recognize the SIM card at all and, in phone status, MEID and IMEI shows 0. (i think i screw up with the process or the file) so, how can i recover from this state? don't know mi IMEI....
Some useful (i think) information: Im in Argentina, using Movistar. i believe we use 850-1900 mhz
thanks again.
best regards
You've flashed the wrong modem firmware. Find the latest one that is specifically for the xt1060 and your Imei will get restored. If your device is from Verizon then only their modem will work on the device. I had the same problem after installing modem from another carrier.
Sent from my Moto X using Tapatalk
bushako said:
You've flashed the wrong modem firmware. Find the latest one that is specifically for the xt1060 and your Imei will get restored. If your device is from Verizon then only their modem will work on the device. I had the same problem after installing modem from another carrier.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Thanks for your replay Bushako.
I've tried to find it here and in Google but without luck, do u know where can i find it?
Thanks.
Regards
Please help!!!!!!
I bought xt1060 with unlocked bootloder on kitkat 4.4.2 after some time i thought why not install twrp and custom rom.
At the starting of modding i installed twrp (latest) then cm12.1.
After some time with cm12.1, i decided to install AICP (marshmallow), there the problem started, the problem was that when i receive an incomming call there was no sound on ear piece but after turning on the loud speaker, i can clearly hear the sound.
I searched the forums and found out that if i flash lollipop modem, i can get rid of this problem i mentioned earlier, so i downloaded verizon xt1060 modem from (http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843) and run:
Fastboot flash modem non-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg. Mbn
Fastboot reboot
Using adb while moto x (which is on AICP custom rom) was in fastboot mode.
Phone started boot loop on the initial starting screen.
I rebooted in recovery then wiped system, data, cache, dalvic cache then installed AICP ROM, but no luck still phone was boot looping on the initial screen, then i downloaded verizon xt1060 5.1.1 firmware from (https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1060 Verizon/). Flashed it and phone booted fine after booting was completed i found out that phone was not reciving carrier signals. I searched for solutions, but no luck.
phone IMEI, baseband version was there but every thing was unknown in (about phone > status > sim status)
I checked sim from CQAtest, it said:
Sim state:absent
Sim operator:
Sim operator name:
Sim country:
Sim serial number: null
Phone ICCID:was there
Sim ICCID:null
Phone ICCID compared with sim ICCID: error
I have also checked different sims of different carrier, but still no signals.
I also flashed other modems but still no luck.
Please share if there is any way i can fix this problem :crying:
i went to the unlocking guy and asked him to give me my SPC code, he was able to extract my SPC code using "sigma key", i came home, downgrade my phone to 4.4.4, applied sim crack method (http://forum.xda-developers.com/moto...t1056-t2825155) and then i finally got my precious sim working.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
uzairali98 said:
Please help!!!!!!
I bought xt1060 with unlocked bootloder on kitkat 4.4.2 after some time i thought why not install twrp and custom rom.
At the starting of modding i installed twrp (latest) then cm12.1.
After some time with cm12.1, i decided to install AICP (marshmallow), there the problem started, the problem was that when i receive an incomming call there was no sound on ear piece but after turning on the loud speaker, i can clearly hear the sound.
I searched the forums and found out that if i flash lollipop modem, i can get rid of this problem i mentioned earlier, so i downloaded verizon xt1060 modem from (http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843) and run:
Fastboot flash modem non-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg. Mbn
Fastboot reboot
Using adb while moto x (which is on AICP custom rom) was in fastboot mode.
Phone started boot loop on the initial starting screen.
I rebooted in recovery then wiped system, data, cache, dalvic cache then installed AICP ROM, but no luck still phone was boot looping on the initial screen, then i downloaded verizon xt1060 5.1.1 firmware from (https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1060 Verizon/). Flashed it and phone booted fine after booting was completed i found out that phone was not reciving carrier signals. I searched for solutions, but no luck.
phone IMEI, baseband version was there but every thing was unknown in (about phone > status > sim status)
I checked sim from CQAtest, it said:
Sim state:absent
Sim operator:
Sim operator name:
Sim country:
Sim serial number: null
Phone ICCID:was there
Sim ICCID:null
Phone ICCID compared with sim ICCID: error
I have also checked different sims of different carrier, but still no signals.
I also flashed other modems but still no luck.
Please share if there is any way i can fix this problem :crying:
Click to expand...
Click to collapse
Still in problem?
Yes im still facing the problem. One day i checked my imei on international database and found out that it was xt1056 (not xt1060), i went to firmware download and downloaded
XT1056_GHOST_SPRINT_5.1_LPA23.12-39.10_cid9_CFC.xml.zip
912.0 MiB
Flashed it.
But now its taking forever on activating screen (on every boot).
I think the problem took place because i flashed verizon modem on sprint moto x
Please help ??
uzairali98 said:
Yes im still facing the problem. One day i checked my imei on international database and found out that it was xt1056 (not xt1060), i went to firmware download and downloaded
XT1056_GHOST_SPRINT_5.1_LPA23.12-39.10_cid9_CFC.xml.zip
912.0 MiB
Flashed it.
But now its taking forever on activating screen (on every boot).
Click to expand...
Click to collapse
Try reinstalling AICP since that's what you were running before, and since you flashed the correct XML everything should be working correctly.
You can find the correct model number on the back (assuming it's the original back) it's really small towards the bottom
Btw where did you check your imei?
Sent from my Moto X using Tapatalk
Josephdbrewer25 said:
Try reinstalling AICP since that's what you were running before, and since you flashed the correct XML everything should be working correctly.
You can find the correct model number on the back (assuming it's the original back) it's really small towards the bottom
Btw where did you check your imei?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
sir i checked my imei on multiple websites like (http://www.imei.info),(https://imeidata.net)....
They both gave me same details, btw my orignal back cover was broken so i changed it with a new one. Is there any other way of finding IMEI on hardware like under the battery or something. I'm currently running AICP because as u know phone takes forever on activating screen on stock rom.
I contacted sprint through internet, i told them every thing so they asked for my sprint phone number (for activating purpose using manual programming method) i went to settings>about phone>status>sim status, there i found this number 0000000xxxx which was not a sprint number according to sprint. I think its not activating because there is no sprint activity in pakistan.
uzairali98 said:
sir i checked my imei on multiple websites like (http://www.imei.info),(https://imeidata.net)....
They both gave me same details, btw my orignal back cover was broken so i changed it with a new one. Is there any other way of finding IMEI on hardware like under the battery or something. I'm currently running AICP because as u know phone takes forever on activating screen on stock rom.
I contacted sprint through internet, i told them every thing so they asked for my sprint phone number (for activating purpose using manual programming method) i went to settings>about phone>status>sim status, there i found this number 0000000xxxx which was not a sprint number according to sprint. I think its not activating because there is no sprint activity in pakistan.
Click to expand...
Click to collapse
Do you have a sim card?
Sent from my Moto X using Tapatalk
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
uzairali98 said:
sir i checked my imei on multiple websites like (http://www.imei.info),(https://imeidata.net)....
They both gave me same details, btw my orignal back cover was broken so i changed it with a new one. Is there any other way of finding IMEI on hardware like under the battery or something. I'm currently running AICP because as u know phone takes forever on activating screen on stock rom.
I contacted sprint through internet, i told them every thing so they asked for my sprint phone number (for activating purpose using manual programming method) i went to settings>about phone>status>sim status, there i found this number 0000000xxxx which was not a sprint number according to sprint. I think its not activating because there is no sprint activity in pakistan.
Click to expand...
Click to collapse
You can find the imei on the sim tray if that hasn't been changed. Or thru Fastboot. Select barcodes. It's where I found mine.
Sent from my Moto X using Tapatalk
---------- Post added at 07:18 AM ---------- Previous post was at 07:06 AM ----------
You can also see the correct model number as well.
Sent from my Moto X using Tapatalk
Thanks for a quick reply.
Im checking then i'll let you know
Those websites are accurate but not precise, for mine one says xt1055 another says xt1060 but it's really xt1050.
Sent from my Moto X using Tapatalk
Its showing me 18 digit imei( which is invalid i think?) and
My serial nember
And my SKU That is xt1056.
How can i find compatible stock rom using serial number?
So how did you find real model number??
Using SKU( in barcodes) or something else
its xt1056 i have checked it. then why its not activating? :crying: :crying: :crying:
uzairali98 said:
Its showing me 18 digit imei( which is invalid i think?) and
My serial nember
And my SKU That is xt1056.
How can i find compatible stock rom using serial number?
Click to expand...
Click to collapse
The SKU is the model number. What's your bootloader?
Sent from my Moto X using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:27 PM ----------
And what did you flash from the Verizon xt1060 firmware?
Sent from my Moto X using Tapatalk
Same problem I'm facing .. I also erased modemst1/2 now no signal or not detecting Sim card .. I've flashed stock ROM also still no luck plxx help :crying:
I flashed the whole Verizon firmware not modem only
My SKU WAS XT1056
Is there any way I can downgrade from lollipop to KitKat on sprint version moto x ???
Because phone can be activated from KitKat illegally
(MY BOOTLOADER IS UNLOCKED)
I'm asking this because in my area there is shop which downgrades android version and unlock sprint phones for 500RS
Downgrading is not recommended. It can cause issues. And since you flashed the whole firmware from Verizon, you can only use the 5.1 firmware from Sprint.
Sent from my Moto X using Tapatalk
---------- Post added at 08:44 PM ---------- Previous post was at 08:42 PM ----------
A little tip: always do a nandroid backup. Maybe someone else on the forum can help. Sorry guys ?
Sent from my Moto X using Tapatalk
SOLVED
uzairali98 said:
Please help!!!!!!
I bought xt1060 with unlocked bootloder on kitkat 4.4.2 after some time i thought why not install twrp and custom rom.
At the starting of modding i installed twrp (latest) then cm12.1.
After some time with cm12.1, i decided to install AICP (marshmallow), there the problem started, the problem was that when i receive an incomming call there was no sound on ear piece but after turning on the loud speaker, i can clearly hear the sound.
I searched the forums and found out that if i flash lollipop modem, i can get rid of this problem i mentioned earlier, so i downloaded verizon xt1060 modem from (http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843) and run:
Fastboot flash modem non-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg. Mbn
Fastboot reboot
Using adb while moto x (which is on AICP custom rom) was in fastboot mode.
Phone started boot loop on the initial starting screen.
I rebooted in recovery then wiped system, data, cache, dalvic cache then installed AICP ROM, but no luck still phone was boot looping on the initial screen, then i downloaded verizon xt1060 5.1.1 firmware from (https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1060 Verizon/). Flashed it and phone booted fine after booting was completed i found out that phone was not reciving carrier signals. I searched for solutions, but no luck.
phone IMEI, baseband version was there but every thing was unknown in (about phone > status > sim status)
I checked sim from CQAtest, it said:
Sim state:absent
Sim operator:
Sim operator name:
Sim country:
Sim serial number: null
Phone ICCID:was there
Sim ICCID:null
Phone ICCID compared with sim ICCID: error
I have also checked different sims of different carrier, but still no signals.
I also flashed other modems but still no luck.
Please share if there is any way i can fix this problem :crying:
Click to expand...
Click to collapse
i went to the unlocking guy and asked him to give me my SPC code, he was able to extract my SPC code using "sigma key", i came home, downgrade my phone to 4.4.4, applied sim crack method (http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155) and then i finally got my precious sim working.
uzairali98 said:
i went to the unlocking guy and asked him to give me my SPC code, he was able to extract my SPC code using "sigma key", i came home, downgrade my phone to 4.4.4, applied sim crack method (http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155) and then i finally got my precious sim working.
Click to expand...
Click to collapse
Your phone will also work in 5.1 lollipop on both verizon and sprint both by just doing some things without downgrading whole firmware
Br
Shahzaib Jahangir