I was attempting to flash a stock recovery today, but after flashing I had no service. I went and looked at my IMEI number and, sure enough, it was corrupted. I was stupid and didnt take a backup beforehand.
So right now I'm looking at two options. One, find a way to restore my IMEI. I do have the number, thanks to Motorola Customer Service, but I have no way to change the phone's number to it. And from what I've read, it's illegal to change it anyway.
My second option is to get it replaced/repaired through Motorola. It is a Pure Edition, bootloader unlocked and rooted. Customer service has told me that the Pure Edition remains under warranty when unlocked, but not when rooted. Is there any hope for me to get them to replace it? I cant get texts or calls right now so I'm in a pretty bad position and need this fixed.
Any help/advice is much appreciated.
Thanks
How you flashed stock recovery? What exact command was used? What does it mean "IMEI number corrupted" Is it 0?
It is illegal to change the IMEI on the phone, but not to upload the correct original IMEI to the phone. So if you do have the IMEI then you can flash it back. There are tools to help you do that. I am not going to link them, because most people don't use them for legit purposes, but search Google and you will find what you are looking for. Sounds like if you are able to flash it back you would be up and running in no time.
I would say it is not absolutely necessary to flash his IMEI again. I have the case on Moto X 2013 when my IMEI was 0. It was due to wrong radio image flashed (i.e. I flashed NON-HLOS.bin and fsg.mbn from European Moto X to non-European Moto X). And I have restored IMEI just flashing right radio image. So no illegal operations were made in that case.
Probably he made a mistake flashing stock recovery and flashed it to radio instead of recovery. In this case he need just reflash radio and IMEI will be restored.
Does anyone have the right radio to flash for the pure edition? I need it also
please help me
accedently i have deleted system and internal storage in moto x (xt1052) indian version , so i have restored brazilian version now every thing okay but my phone imiei number is zero,now it not working network, someone please help me to fix my problem
You need to flash the modem from the indian firmware, not the one from the brazil firmware.
Sent from my XT1095 using Tapatalk
Hi freinds. I am also facing the same situation.
Hi... I am also facing the same situation. I flashed my moto g2 with cyanogenmod 13 and after that i dont see my IMEI informations and no sim detected.
Please provide me a fix.
Lishin Dev said:
Hi... I am also facing the same situation. I flashed my moto g2 with cyanogenmod 13 and after that i dont see my IMEI informations and no sim detected.
Please provide me a fix.
Click to expand...
Click to collapse
You should ppst in the moto g forums, this is the moto x forums.
Sent from my XT1095 using Tapatalk
My moto x shows xt1056 on back but i flashed xt1056 stock and my imei became 0. What do i have to flash to get it back??
It was some 1052 rom when i bought it at first..
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!
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
mikeboballen said:
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
Click to expand...
Click to collapse
That was the guide I was following, which led to this somehow.
I'm thinking about re-locking and un-rooting now so I'll have a shot at the warranty claim.
Good luck man hope it all works out for you
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
JulesJam said:
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
ccarrionc said:
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
Click to expand...
Click to collapse
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
JulesJam said:
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
Click to expand...
Click to collapse
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
ccarrionc said:
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
Click to expand...
Click to collapse
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
JulesJam said:
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
Click to expand...
Click to collapse
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
ccarrionc said:
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Click to expand...
Click to collapse
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
---------- Post added at 03:49 AM ---------- Previous post was at 03:46 AM ----------
ccarrionc said:
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Click to expand...
Click to collapse
They will know b/c you got an unlock code to unlock it.
ccarrionc said:
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
Click to expand...
Click to collapse
I would check the warranty status online. Even if the warranty is void, they may be able to repair the phone for a reasonable price if you don't hard brick it.
JulesJam said:
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
Click to expand...
Click to collapse
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
ccarrionc said:
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
Click to expand...
Click to collapse
No, they have you in the database as having requested an unlock code.
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Steve-x said:
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
Click to expand...
Click to collapse
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
JulesJam said:
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
Click to expand...
Click to collapse
I am 100% sure the files used were not the correct ones.
juliospinoza said:
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Click to expand...
Click to collapse
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
ccarrionc said:
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
Click to expand...
Click to collapse
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Steve-x said:
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Click to expand...
Click to collapse
Found a firmware from my original provider, everything is back to normal (except now I have the different status code in the fastboot screen).
For future reference, I just installed the previous firmware through fastboot (with mfastboot, of course). IMEI was recognized again and baseband too.