Database Develop

No OTAs on AT&T XT1058

Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.

Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.

nhizzat said:
Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.
Click to expand...
Click to collapse
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?

RafaySid said:
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Click to expand...
Click to collapse
It will not SIM lock your phone.
RafaySid said:
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?
Click to expand...
Click to collapse
Since your phone has already been Bootloader unlocked (because the ROM in your phone is not stock right now), it doesn't matter which ROM you choose. I'd say choosing a bloat-free ROM is great!

RafaySid said:
Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.
Click to expand...
Click to collapse
First you need to know if your bootloader is unlocked or locked.
Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.

KidJoe said:
First you need to know if your bootloader is unlocked or locked.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.
Click to expand...
Click to collapse
2nd line: 30.70 (sha-88483d6, 2013-07-02 15:32:03)
.
.
.
.
Device is UNLOCKED. Status Code: 1
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Farooq>cd/
C:\>cd android
C:\Android>fastboot getvar all
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: TA1760BS0H
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: EF8D10040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Fri Jul 12 11:37:14 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X_140
(bootloader) ro.build.tags: intcfg,test-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: e13522
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 23546373
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X_140/23546373:userdebug
(bootloader) ro.build.fingerprint[2]: /intcfg,test-keys
(bootloader) ro.build.version.full[0]: Blur_Version.13.0.23546373.ghost
(bootloader) ro.build.version.full[1]: _att.ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 66c71d4 ([email protected])
(bootloader) kernel.version[2]: (gcc version 4.6.x-google 201201
(bootloader) kernel.version[3]: 06 (prerelease) (GCC) ) #1 SMP P
(bootloader) kernel.version[4]: REEMPT Fri Jul 12 11:55:44 CDT 2
(bootloader) kernel.version[5]: 013
all:
finished. total time: 0.122s
C:\Android>

A few things..
With Bootloader of 30.70, that is the initial shipping bootloader. Based on the versions, it appears to also been the initial shipping ATT ROM. (i.e. the previous owner did not flash only PARTS of a ROM).
Unlocked Status 1 is good. You should be able to flash signed and unsigned roms. So if you want to switch to CM or such, you can. And you can flash 3rd party recovery and root too.
A few things that concern me from the fastboot output...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
I've only seen it say YES or NO for those. This is the first I've seen "Not Supported"
(bootloader) cid: 0xdead
I've not seen the CID listed as DEAD before. Its always been a hex value.
And I'm hoping you just removed your imei and meid, and not that they are actually missing from the output.
One last thing I missed in your other posts, that it says XT1058 on the back and MADE IN CHINA. The ATT XT1058's all said made in USA if I'm not mistaken. So chances are best that its NOT an ATT XT1058.
What carrier are you using this phone on? Do they sell the XT1058? If so, consider finding the latest XT1058 SBF for that carrier and flashing it.
RISKS of doing that: It might fail and brick your phone in the process. It might be successful but you end up having no IMEI/MEID in the process. You end up in a state where you have that SBF on there, but improper carrier settings so future OTA's fail and you have to flash them manually. Or Best case.... It works, and those variables go back to "normal" values.
Its your call if you want to take the chance.

Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?

RafaySid said:
Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
Click to expand...
Click to collapse
Yes, definitely caused while screwing around and doing something that shouldn't have been done.
So the IMEI is definitely missing? I would think in that case you wont see the mobile/cellular network and only Wifi would work. But you said other than the OTA's the phone was working fine.
There were some threads about some getting into that situation (Missing IMEI). I know there were some XT1052 users trying to flash Non-XT1052 roms and running into this, but being unable to recovery. I think there was some users who ran into it for other reasons and were able to recover. Its time to start searching. Like -> http://forum.xda-developers.com/moto-x/moto-x-qa/cdn-rogers-1058-fr-4-4-2-update-to-4-4-t2842787
RafaySid said:
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?
Click to expand...
Click to collapse
As I've said, the "Not Supported" and "0xdead" values do worry me. I've not seen them before, so I can't tell you what impact they have on flashing. That is why I said bricking was a risk and that its your choice what to do.
At this point, if you have a working phone, keep with it and using it. Or you try and flash a Rogers XT1058 SBF, taking the chance of bricking it in the process. If you take this route, use Option 5 (and its pre-req's) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html Get roms from places in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
I would really suggest flashing the LATEST SBF, in this case 4.4.4.
As for the "battery drain" reported under 4.4.4, for me anyway it seems to vary depending on installed apps. I can still get more than a day with my XT1060 running 4.4.4 with all google and moto apps updated. Occasionally after a bunch of apps update, I see less battery life, but then it seems to settle down and go back to normal.
If you want to flash Rogers 4.4.4, per this thread -> http://forum.xda-developers.com/mot...rogers-canada-4-4-4-sbf-t2905525/post56055157 it appears to be XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip BUT I HAVE NOT CONFIRMED THIS SO PROCEED WITH CAUTION!!!
Good Luck!!

The cellular network is working fine. Can I at least root it? Which method should I choose?

RafaySid said:
The cellular network is working fine. Can I at least root it? Which method should I choose?
Click to expand...
Click to collapse
First, find a copy of the SBF for the rom on your phone before you do anything.
Since you have an unlocked bootloader, just follow -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
Because you have an older rom and bootloader, just use the versions linked in there. If you ever update the ROM on your phone, you would want to consider using newer versions of TWRP and SuperSU

In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.

In order to root, you need to read. Seriously, just read and you'll have your answer.

I'm being 'extra careful' because of those abnormal values.
Sent from my Moto X using Tapatalk

RafaySid said:
In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.
Click to expand...
Click to collapse
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.

KidJoe said:
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.
Click to expand...
Click to collapse
Yes thank you. I had already rooted using TWRP.

Can I install an offline update instead of flashing, to update 4.2.2?
Sent from my Moto X using Tapatalk

These 2 threads have everything you need to know,
Rooting,
http://forum.xda-developers.com/showthread.php?t=2826159
Flashing firmware, (returning to stock section)
http://forum.xda-developers.com/showthread.php?t=2603358
I'm not sure what you are meaning by "offline" update... But how to update manually is covered in above thread. ?

Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk

RafaySid said:
Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
there are two types of Update.
OTA update (they are incremental, only flash what changed since the last version, need to be stock recovery, and rest of phone as close to stock as possible. and you'll need a certain version on your phone)
Flashing a full SBF (as explained earlier when I mentioned about possibly flashing the Rogers XT1058 rom, and pointed you towards using Option 5 and its pre-req's at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . It has a couple commands repeated which makes it a little more successful. )
Either way, in your situation, is risky.

[Q] Best route to take from 4.2.2 to latest LP?

I've just purchased a used MotoMaker Moto X XT1058. It has been reset to factory stock. I'm assuming it was purchased as an AT&T carrier phone as the only carrier branded app's is myAT&T, Visual VoiceMail and the AT&T Address Book in the Settings Menu. The info that might be needed to answer my question is as follows:
Android version: 4.2.2
System ver: 139.7.17.ghost_ATT.en.US
Build #: 13.9.0Q2.X-116-X-17
bootloader: 30.70
Device is UNLOCKED. Status Code: 1 (I'm assuming either Sunshine or China Middleman.)
FYI, I do have experience in unlocking bootloaders, installing recoveries, ROM's, SBF's, etc., on my Gnex and a few other phones. This is my first contact with a Moto X. Also, I have done quite a bit of reading the past few days but have been unable to obtain the information I seek to ease my concern about the correct way to proceed with this phone.
I intend to activate with Cricket wireless so there should not be a problem with carrier unlocking being needed, I'm thinking. My ultimate goal is to be on stock LP with wifi tethering (i.e. Hotspot) functioning.
Finally, my question is this: What is the best route to take from where I'm at to stock LP with WiFi Hotspot? I realize that stock LP isn't available so what would be a good temporary ROM until LP is here? Maybe I should stay with 4.2.2 until then? I would appreciate the experience that you all have to offer that will prevent me from making a mistake that could be avoided.
Best regards,
RFeTech

Where did you purchase it from?
Boot the phone into Fastboot/Bootloader mode. hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
Btw, does it have any ATT branding on the case? Were you told what carrier it was supposed to be for? Does it say Made in China, or Made in USA in the very fine print on its back?

Removed. I guess post was not appreciated.

KidJoe, thanks for your offer to help.
Purchased via Swappa. Seller was not original owner. Seller was using StraightTalk. I'm using Cricket, as of today.
No AT&T branding anywhere except the App's that I listed in the OP.
Don't know the original carrier. There wasn't many carrier options for an XT1058 via MotoMaker, at that time.
Designed and assembled in the USA
Purple colored back and buttons with Motorola Logo. Black face.
(bootloader) version-bootloader: 3070
(bootloader) revision-hardware: 0x82B0
(bootloader) unlocked: yes
(bootloader) sku: XT1058
(bootloader) cid: 0x00
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17/17:user/bldac
(bootloader) ro.build.fingerprint[2]: fg,release-keys (just in case you need this also)
(bootloader) ro.build.version.full[0]: Blur_Version.139.7.17.ghost_att.
(bootloader) ro.build.version.full[1]: ATT.en.US
Please let me know if you need additional info.

rfetech said:
KidJoe, thanks for your offer to help.
Purchased via Swappa. Seller was not original owner. Seller was using StraightTalk. I'm using Cricket, as of today.
No AT&T branding anywhere except the App's that I listed in the OP.
Don't know the original carrier. There wasn't many carrier options for an XT1058 via MotoMaker, at that time.
Designed and assembled in the USA
Purple colored back and buttons with Motorola Logo. Black face.
(bootloader) version-bootloader: 3070
(bootloader) revision-hardware: 0x82B0
(bootloader) unlocked: yes
(bootloader) sku: XT1058
(bootloader) cid: 0x00
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17/17:user/bldac
(bootloader) ro.build.fingerprint[2]: fg,release-keys (just in case you need this also)
(bootloader) ro.build.version.full[0]: Blur_Version.139.7.17.ghost_att.
(bootloader) ro.build.version.full[1]: ATT.en.US
Please let me know if you need additional info.
Click to expand...
Click to collapse
Looking good so far... a few more things I need to know...
(bootloader) unlocked:
(bootloader) iswarrantyvoid:
(bootloader) imei: <- don't paste your IMEI value, just tell me it its correct, or if its all zeros.
(bootloader) iccid: <- don't paste your ICCID value, just tell me if its all zeros or not.
Something else.. For an ATT XT1058, the usual value for CID is 0x01 so I am surprised to see you report the CID is 0x00. And I'm surprised someone would go through the trouble to unlock the bootloader, but stay on the initial shipping rom.
As long as the above values check out ok... (unlocked and iswarrantyvoid should say YES), and there is nothing special needed for Cricket, then to return the phone to "stock" and the latest firmware, I would consider just flashing the ATT 4.4.4 SBF via mFastboot. Unfortunately you'll get all the ATT bloat with it. There is a link in my signature for where to get the SBF files, and follow method 2 in the return to stock thread -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 (just skip the VZW lines since you have ATT).
After that, since the bootloader is unlocked, Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading) and the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053 and Root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Since I have Verizon, I haven't kept up on the tethering methods for use on the other carrier varients of the Moto X... you could try Xposed and this mod -> http://forum.xda-developers.com/moto-x/themes-apps/xposed-moto-x-4-4-native-tether-apk-t2601859
Or you can try -> https://code.google.com/p/android-wifi-tether/
for my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
Not sure if those same settings work on other carriers though...

KidJoe said:
Looking good so far... a few more things I need to know...
(bootloader) unlocked:
(bootloader) iswarrantyvoid:
(bootloader) imei: <- don't paste your IMEI value, just tell me it its correct, or if its all zeros.
(bootloader) iccid: <- don't paste your ICCID value, just tell me if its all zeros or not.
Something else.. For an ATT XT1058, the usual value for CID is 0x01 so I am surprised to see you report the CID is 0x00. And I'm surprised someone would go through the trouble to unlock the bootloader, but stay on the initial shipping rom.
As long as the above values check out ok... (unlocked and iswarrantyvoid should say YES), and there is nothing special needed for Cricket, then to return the phone to "stock" and the latest firmware, I would consider just flashing the ATT 4.4.4 SBF via mFastboot. Unfortunately you'll get all the ATT bloat with it. There is a link in my signature for where to get the SBF files, and follow method 2 in the return to stock thread -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 (just skip the VZW lines since you have ATT).
After that, since the bootloader is unlocked, Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading) and the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053 and Root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Since I have Verizon, I haven't kept up on the tethering methods for use on the other carrier varients of the Moto X... you could try Xposed and this mod -> http://forum.xda-developers.com/moto-x/themes-apps/xposed-moto-x-4-4-native-tether-apk-t2601859
Or you can try -> https://code.google.com/p/android-wifi-tether/
for my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
If you have troubles, its also suggested to...
check box: wifi-driver reload 2
Not sure if those same settings work on other carriers though...
Click to expand...
Click to collapse
I'll just give you the complete getvar dump in case you should find something else odd.
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x82B0
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: (verified but removed for security reasons)
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) uid: AE1CCF030C000100000000000000
(bootloader) imei: (verified but removed for security reasons)
(bootloader) meid:
(bootloader) sku: XT1058
(bootloader) cid: 0x00
(bootloader) iccid: (this line was blank. no zeros or anything)
(bootloader) date: 06-03-2013
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Sat Jul 6 00:58:28 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 17
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17/17:user/bldac
(bootloader) ro.build.fingerprint[2]: fg,release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.139.7.17.ghost_att.
(bootloader) ro.build.version.full[1]: ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-gfd1a
(bootloader) kernel.version[1]: 699-00155-g0f20230 ([email protected]
(bootloader) kernel.version[2]: 3lnxdroid80) (gcc version 4.6.x-
(bootloader) kernel.version[3]: google 20120106 (prerelease) (GC
(bootloader) kernel.version[4]: C) ) #1 SMP PREEMPT Sat Jul 6 01
(bootloader) kernel.version[5]: :10:36 CDT 2013
Yeah... I was hoping to avoid the AT&T bloatware. Reckon I'll look inside the SBF to see what's there before flashing it. I've searched around for a 4.4.4 stock with bloatware removed but no luck. Ver 4.2.2 seems pretty snappy on my Moto X compared to my GNex. I hope 4.4.4 on the MoTo X will be as good or better?? Maybe someone will release a stock LP without bloatware, when possible.
Was also hoping to avoid Xposed since I have no need for anything except tethering. I used the WiFI tether app a few years ago on the original Droid X and liked it very much. I read that you were using it also. This is my first GSM phone and I'm liking what I've seen so far with the phone and with Cricket. I've been with Verizon (and Alltel before Vz bought them) for ~25 yrs. Guess that dates me. I still have the unlimited data plan but don't really use enough to justify it. Looking to save some dollars with Cricket without giving up much in data speeds. So far, so good!!

[/QUOTE]Yeah... I was hoping to avoid the AT&T bloatware. Reckon I'll look inside the SBF to see what's there before flashing it. I've searched around for a 4.4.4 stock with bloatware removed but no luck. Ver 4.2.2 seems pretty snappy on my Moto X compared to my GNex. I hope 4.4.4 on the MoTo X will be as good or better?? Maybe someone will release a stock LP without bloatware, when possible.
Was also hoping to avoid Xposed since I have no need for anything except tethering. I used the WiFI tether app a few years ago on the original Droid X and liked it very much. I read that you were using it also. This is my first GSM phone and I'm liking what I've seen so far with the phone and with Cricket. I've been with Verizon (and Alltel before Vz bought them) for ~25 yrs. Guess that dates me. I still have the unlimited data plan but don't really use enough to justify it. Looking to save some dollars with Cricket without giving up much in data speeds. So far, so good!![/QUOTE]
Have you looked at Eclipse 4.4.4? It is stock based so all moto features work. Wifi tether is built in. I think you would really like it. Just something to think about if you are looking for a stock debloated rom. This is far from stock, but all stock features work.

Yeah... I was hoping to avoid the AT&T bloatware. Reckon I'll look inside the SBF to see what's there before flashing it. I've searched around for a 4.4.4 stock with bloatware removed but no luck. Ver 4.2.2 seems pretty snappy on my Moto X compared to my GNex. I hope 4.4.4 on the MoTo X will be as good or better?? Maybe someone will release a stock LP without bloatware, when possible.
Was also hoping to avoid Xposed since I have no need for anything except tethering. I used the WiFI tether app a few years ago on the original Droid X and liked it very much. I read that you were using it also. This is my first GSM phone and I'm liking what I've seen so far with the phone and with Cricket. I've been with Verizon (and Alltel before Vz bought them) for ~25 yrs. Guess that dates me. I still have the unlimited data plan but don't really use enough to justify it. Looking to save some dollars with Cricket without giving up much in data speeds. So far, so good!![/QUOTE]
Have you looked at Eclipse 4.4.4? It is stock based so all moto features work. Wifi tether is built in. I think you would really like it. Just something to think about if you are looking for a stock debloated rom. This is far from stock, but all stock features work.[/QUOTE]
Yes, I have looked at it and put it on my short list if I do end up going with a custom ROM. I've run several custom ROMs over the years and just never utilized very many features and that's why I hope to stay as stock as possible. As you know, Eclipse is a CMDA ROM that has been modified to work with GSM phones. I'm not saying that is a problem, but it does lend itself to not being ideal for a GSM phone. Also, I could never confirm that the wifi tethering would work on the GSM version of the ROM. Maybe I'm wrong. Since I have to upgrade to stock 4.4.4 before installing Eclipse 4.4.4, then I might as well give stock 4.4.4 a try and maybe I can get tethering working on it before going to a custom ROM.
Either way, I do appreciate your input. All of this is helping me learn important things about the Moto X that I'm sure will come in handy in the future. Thanks!

rfetech said:
Yeah... I was hoping to avoid the AT&T bloatware. Reckon I'll look inside the SBF to see what's there before flashing it. I've searched around for a 4.4.4 stock with bloatware removed but no luck. Ver 4.2.2 seems pretty snappy on my Moto X compared to my GNex. I hope 4.4.4 on the MoTo X will be as good or better?? Maybe someone will release a stock LP without bloatware, when possible.
Was also hoping to avoid Xposed since I have no need for anything except tethering. I used the WiFI tether app a few years ago on the original Droid X and liked it very much. I read that you were using it also. This is my first GSM phone and I'm liking what I've seen so far with the phone and with Cricket. I've been with Verizon (and Alltel before Vz bought them) for ~25 yrs. Guess that dates me. I still have the unlimited data plan but don't really use enough to justify it. Looking to save some dollars with Cricket without giving up much in data speeds. So far, so good!!
Click to expand...
Click to collapse
Cool, if you decide to stick with stock 4.4.4 I know this app worked for me when I tried it on 4.4.4 stock for tether.
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152

Travisdroidx2 said:
Cool, if you decide to stick with stock 4.4.4 I know this app worked for me when I tried it on 4.4.4 stock for tether.
http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
Click to expand...
Click to collapse
Thanks. I read the complete thread a few days ago but didn't see that anyone had used it on an AT&T phone. Are you aware that it will work on AT&T? I have a couple more possible options that I have found during my Googling Expedition the past few days but I will certainly give this one a try whenever I update my ROM and root my phone. Thanks again!

rfetech said:
Thanks. I read the complete thread a few days ago but didn't see that anyone had used it on an AT&T phone. Are you aware that it will work on AT&T? I have a couple more possible options that I have found during my Googling Expedition the past few days but I will certainly give this one a try whenever I update my ROM and root my phone. Thanks again!
Click to expand...
Click to collapse
Sorry, I am not on AT&T. I am on Verizon and only run Eclipse for 99% of the time. And native tethering is always built in so I have never had any issues with tethering.

@KidJoe
I'm sure you're very busy but did you have a chance to look at the getvar dump that I posted, at your request. There were a couple items that might have been of concern to you so I was hoping to hear from you before I started flashing.
Thanks!

rfetech said:
@KidJoe
I'm sure you're very busy but did you have a chance to look at the getvar dump that I posted, at your request. There were a couple items that might have been of concern to you so I was hoping to hear from you before I started flashing.
Thanks!
Click to expand...
Click to collapse
There are a few that surprise me under normal situations.. For example, XT1058 with ATT Firmware and a CID of 0x00, saying Unlocked=Yes with WarrantyVoid=No...
ATT branded XT1058 Cid is not 00. And unlocking the bootloader usually sets WarrantyVoid value to Yes. Now, if Sunshine was used, that might explain (since I never looked at the getvar all output from someone who had used Sunshine to unlock).
Those values are better than those who had Unlocked and WarrantyVoid set to "unknown" or "unsupported" and CID of 0xDead that I've seen some other users report when they got a used, or from ebay seller, XT1058 that still had the initial shipping rom on.
You should be relatively ok to flash or do what you want.

KidJoe said:
There are a few that surprise me under normal situations.. For example, XT1058 with ATT Firmware and a CID of 0x00, saying Unlocked=Yes with WarrantyVoid=No...
ATT branded XT1058 Cid is not 00. And unlocking the bootloader usually sets WarrantyVoid value to Yes. Now, if Sunshine was used, that might explain (since I never looked at the getvar all output from someone who had used Sunshine to unlock).
Those values are better than those who had Unlocked and WarrantyVoid set to "unknown" or "unsupported" and CID of 0xDead that I've seen some other users report when they got a used, or from ebay seller, XT1058 that still had the initial shipping rom on.
You should be relatively ok to flash or do what you want.
Click to expand...
Click to collapse
Thank you again @KidJoe
From stock recovery, I reset to factory and then cleared cache. Using fastboot, I flashed the AT&T 4.4.4 ROM. I reset to factory and cleared cache again. I then drove around for an hour checking signal strength and quality to verify that 4.4.4 was as good or better than 4.2.2. I was impressed. I then flashed TWRP 2.8.5.0 and installed SuperSU 2.46. Next, I installed EntitlementBypass-v1.2 and that did the trick for the WiFi Hotspot issue. So... now I have just what I was hoping for except Lollipop. Maybe that will come soon.
I also read the thread where you helped @RafaySid with a similar problem. Since AT&T 4.4.4 has more bloatware that 4.2.2 did, do you think I could safely install the Rogers SBF? It appears that it worked OK for @RafaySid.
Many thanks to @KidJoe and @Travisdroidx2.

rfetech said:
I also read the thread where you helped @RafaySid with a similar problem. Since AT&T 4.4.4 has more bloatware that 4.2.2 did, do you think I could safely install the Rogers SBF? It appears that it worked OK for @RafaySid.
Many thanks to @KidJoe and @Travisdroidx2.
Click to expand...
Click to collapse
Because you are bootloader unlocked, and your CID is 00, you can flash it.. HOWEVER... keep in mind that different build levels of 4.4.4 might have different GPT.BIN or MOTOBOOT.IMG parts. These parts can't be downgraded, so when you flash, the SBF must have the same or newer GPT.BIN/MOTOBOOT.iMG compared to what is on your phone.

KidJoe said:
Because you are bootloader unlocked, and your CID is 00, you can flash it.. HOWEVER... keep in mind that different build levels of 4.4.4 might have different GPT.BIN or MOTOBOOT.IMG parts. These parts can't be downgraded, so when you flash, the SBF must have the same or newer GPT.BIN/MOTOBOOT.iMG compared to what is on your phone.
Click to expand...
Click to collapse
Thanks. I'm satisfied with where I'm at right now and suppose I'll stay until stock LP gets here, if ever...

rfetech said:
I'll just give you the complete getvar dump in case you should find something else odd.
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x82B0
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: (verified but removed for security reasons)
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) uid: AE1CCF030C000100000000000000
(bootloader) imei: (verified but removed for security reasons)
(bootloader) meid:
(bootloader) sku: XT1058
(bootloader) cid: 0x00
(bootloader) iccid: (this line was blank. no zeros or anything)
(bootloader) date: 06-03-2013
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Sat Jul 6 00:58:28 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 17
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-116-X-17/17:user/bldac
(bootloader) ro.build.fingerprint[2]: fg,release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.139.7.17.ghost_att.
(bootloader) ro.build.version.full[1]: ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-gfd1a
(bootloader) kernel.version[1]: 699-00155-g0f20230 ([email protected]
(bootloader) kernel.version[2]: 3lnxdroid80) (gcc version 4.6.x-
(bootloader) kernel.version[3]: google 20120106 (prerelease) (GC
(bootloader) kernel.version[4]: C) ) #1 SMP PREEMPT Sat Jul 6 01
(bootloader) kernel.version[5]: :10:36 CDT 2013
Yeah... I was hoping to avoid the AT&T bloatware. Reckon I'll look inside the SBF to see what's there before flashing it. I've searched around for a 4.4.4 stock with bloatware removed but no luck. Ver 4.2.2 seems pretty snappy on my Moto X compared to my GNex. I hope 4.4.4 on the MoTo X will be as good or better?? Maybe someone will release a stock LP without bloatware, when possible.
Was also hoping to avoid Xposed since I have no need for anything except tethering. I used the WiFI tether app a few years ago on the original Droid X and liked it very much. I read that you were using it also. This is my first GSM phone and I'm liking what I've seen so far with the phone and with Cricket. I've been with Verizon (and Alltel before Vz bought them) for ~25 yrs. Guess that dates me. I still have the unlimited data plan but don't really use enough to justify it. Looking to save some dollars with Cricket without giving up much in data speeds. So far, so good!!
Click to expand...
Click to collapse
Very curious, the getvar data you posted. It suggests your phone may be a Motorola engineering device that was never intended for sale. Congrats on the phone, you might have gotten a special one.
P.S. Out of curiosity, does the model number written on the back of the phone match? (ie. does it say XT1058 or some other model number?)

squid2 said:
Very curious, the getvar data you posted. It suggests your phone may be a Motorola engineering device that was never intended for sale. Congrats on the phone, you might have gotten a special one.
P.S. Out of curiosity, does the model number written on the back of the phone match? (ie. does it say XT1058 or some other model number?)
Click to expand...
Click to collapse
It has a Moto Maker back cover but it does have XT1058, made in USA, on it.
The bootloader was unlocked, status code 1, with I received it and it was running 4.2.2. I purchased another Moto X 2013 this week and it also came with 4.2.2. I unlocked with Sunshine and it states, status code 3. The first phone doesn't present the unlocked bootloader warning screen regardless of me flashing a complete 4.4.4 SBF. The second phone does show the warning screen so I have to re-flash the logo.bin in order to not show it. To me, that's another odd thing about the first phone. Also, despite numerous phone calls and emails to AT&T and Motorola, I've been unable to get a carrier unlock code for the first phone. Although it took a long phone call, I was able to get a code for the second phone. Go figure!!
Thanks for your comment.

rfetech said:
It has a Moto Maker back cover but it does have XT1058, made in USA, on it.
The bootloader was unlocked, status code 1, with I received it and it was running 4.2.2. I purchased another Moto X 2013 this week and it also came with 4.2.2. I unlocked with Sunshine and it states, status code 3. The first phone doesn't present the unlocked bootloader warning screen regardless of me flashing a complete 4.4.4 SBF. The second phone does show the warning screen so I have to re-flash the logo.bin in order to not show it. To me, that's another odd thing about the first phone. Also, despite numerous phone calls and emails to AT&T and Motorola, I've been unable to get a carrier unlock code for the first phone. Although it took a long phone call, I was able to get a code for the second phone. Go figure!!
Thanks for your comment.
Click to expand...
Click to collapse
Yep, the first phone's behaviour sounds like an engineering phone. Status code 0 is locked, 1 is engineering, and 3 is unlocked. The Moto Maker back is weird though for an engineering phone. Maybe they forgot to blow the secure boot fuses when building it in the American factory. Very strange. I'd reckon that phone would be able to run unsigned TrustZone images and such. Even if you can't carrier unlock it, keep it. Also, NEVER EVER run "fastboot oem lock" on that phone, as you can never go back to engineering status after you lock it.
The second phone you bought sounds like a normal Moto X. Status code 3 is what you should get when you unlock a secure device.

squid2 said:
Yep, the first phone's behaviour sounds like an engineering phone. Status code 0 is locked, 1 is engineering, and 3 is unlocked
...
I'd reckon that phone would be able to run unsigned TrustZone images and such. Even if you can't carrier unlock it, keep it....
Click to expand...
Click to collapse
Is this something the modding community would benefit from having? If the phone is uniquely capable of accepting unexpected flashes I'm envisioning some of our really smart people learning more by having that phone in their hands. Am I way off base?

AT&T XT1058 - Stuck on 4.2.2

Hello,
I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T.
Whenever I try and update click the CHECK FOR UPDATE, it says, " NO UPDATE FOUND " your device is up to date.
The phone is NOT ROOTED as there are no superuser type apps on the phone. Not sure about the bootloader though. Phone runs perfectly fine just this update thing is getting me worried.
Its currently on 4.2.2
Can anybody please tell me why I cant get the OTA or what should I do to update it to KITKAT?
Thank you in advance.

I tried the adb fastboot thing, but it says waiting for device and never shows anything. Does that have anything to do with the phone or the Operating System im using (WINDOWS 8.1)

Please see -> No OTAs on AT&T XT1058
Please do what is listed in Post #5 and post the results. also include what it says for (bootloader) iswarrantyvoid: and who is the carrier you are using it on?

C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Toshiba REV=06 PRV=00 TY
(bootloader) product: ghost
(bootloader) revision-hardware: 0x81B0
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: LXAA1H0042
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: 420E19000C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Reboot to bootloader
(bootloader) ro.build.date: Sat Jul 6 01:51:06
(bootloader) ro.build.id: 13.9.0Q2.X-116-X-17
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: userPAEH\♦☺è
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 8
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/g
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X-
(bootloader) ro.build.fingerprint[2]: g,release-
(bootloader) ro.build.version.full[0]: Blur_Vers
(bootloader) ro.build.version.full[1]: ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.
(bootloader) kernel.version[1]: 699-00155-g0f202
(bootloader) kernel.version[2]: 3lnxdroid79) (gc
(bootloader) kernel.version[3]: google 20120106
(bootloader) kernel.version[4]: C) ) #1 SMP PREE
(bootloader) kernel.version[5]: :04:24 CDT 2013

I am using wataniya on it. Phone and everything works pretty fine. I am just stuck on 4.2.2. Like the member in the thread you pointed out to.

OmMeE said:
I am using TELENOR on it. Phone and everything works pretty fine. I am just stuck on 4.2.2. Like the member in the thread you pointed out to.
Click to expand...
Click to collapse
And like the member in that other thread... you have...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
were the IMEI and SKU really reported as 0's, or did you do that in your post here to keep them hidden?
Btw, if you follow that other thread, I gave a lot of warnings of the phone being in an unknown state, I wasn't sure if it was safe or not to try and flash, do so at your own risk, etc... in the end, the user flashed the Rogers Canada XT1058 rom -> http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip using mFastboot, and did a factory reset. It didn't cure the values I'm pointing out which are not standard.. but it did get him to 4.4.4 and was working on his GSM carrier..
If you're up for it, and are willing to take the risk, maybe that will work for you too... and hopefully it doesn't brick your phone.

KidJoe said:
And like the member in that other thread... you have...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
were the IMEI and SKU really reported as 0's, or did you do that in your post here to keep them hidden?
Btw, if you follow that other thread, I gave a lot of warnings of the phone being in an unknown state, I wasn't sure if it was safe or not to try and flash, do so at your own risk, etc... in the end, the user flashed the Rogers Canada XT1058 rom -> http://www.filefactory.com/file/5z0...4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip using mFastboot, and did a factory reset. It didn't cure the values I'm pointing out which are not standard.. but it did get him to 4.4.4 and was working on his GSM carrier..
If you're up for it, and are willing to take the risk, maybe that will work for you too... and hopefully it doesn't brick your phone.
Click to expand...
Click to collapse
I didnt hide anything, just posted as it came on the CMD.
So if I flash to that rogers rom, will I be getting future updates or will I have to flash everytime?
Also, my apologies, but can you point me towards a step by step guide for using mfastboot, as im new to this and running windows 8.1.

OmMeE said:
I didnt hide anything, just posted as it came on the CMD.
So if I flash to that rogers rom, will I be getting future updates or will I have to flash everytime?
Also, my apologies, but can you point me towards a step by step guide for using mfastboot, as im new to this and running windows 8.1.
Click to expand...
Click to collapse
Ok, well, seeing those things things, let me reiterate that your phone is in an "unknown" or at least "unusual" state. Anything you do at this point is risky! So its up to you if you really want to do anything (like flashing) or leave it like it is (since its working).
There is a chance you will not get updates if you are using the XT1058 rom branded for another carrier. (i.e. if you have the ATT XT1058 rom on an XT1058 being used on a different carrier).
As for step by step... you have a few options..
http://mark.cdmaforums.com/MotoX-ReturnToStock.html See the requirements at the top of the page, and then option 5
Or...
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Oh, and I only suggested the Rogers Canada XT1058 rom because it worked for that other user in that other thread, and I THINK it might have less bloat than the ATT XT1058 rom.
And I do suggest you read that entire thread... there are a few good posts in there with info that might help you understand the situation... because this is a weird state.

KidJoe said:
Please see -> No OTAs on AT&T XT1058
Please do what is listed in Post #5 and post the results. also include what it says for (bootloader) iswarrantyvoid: and who is the carrier you are using it on?
Click to expand...
Click to collapse
KidJoe said:
Ok, well, seeing those things things, let me reiterate that your phone is in an "unknown" or at least "unusual" state. Anything you do at this point is risky! So its up to you if you really want to do anything (like flashing) or leave it like it is (since its working).
There is a chance you will not get updates if you are using the XT1058 rom branded for another carrier. (i.e. if you have the ATT XT1058 rom on an XT1058 being used on a different carrier).
As for step by step... you have a few options..
http://mark.cdmaforums.com/MotoX-ReturnToStock.html See the requirements at the top of the page, and then option 5
Or...
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Oh, and I only suggested the Rogers Canada XT1058 rom because it worked for that other user in that other thread, and I THINK it might have less bloat than the ATT XT1058 rom.
And I do suggest you read that entire thread... there are a few good posts in there with info that might help you understand the situation... because this is a weird state.
Click to expand...
Click to collapse
Thank you very much for the reply.. I followed your instructions and I am now on 4.4.4. The same happened exactly, home button not working, active display not working, quick settings could not be reached.. FACTORY RESETED it and its working fine now.

unknown x, need help idenifiying

just received a lot of defected 2013 x's and one is like i have never seen, it has no branding on bat cover and bootloader is unlocked with 4.2.2 os, it has a very weird home screen with a pic of file folder in right bottom home screen with colored blocks on it, when taped tinnier icons appear, has a test cam, fr on ,settings...., it has no google apps or services with some apps i cant remember ever seeing on a x.
baseband version
msm8960pro_bp_2323.010.71.00r
kernel version
3.4.42-xline-eng-g9c632ef-00003-g99060a2
[email protected] #1
system version
unknown
build number
factory_ghost-userdebug 4.2.2
13.9.0q2.x-118_ghost-gnpo-6 8 test-keys
imei is listed as (0),
in ap fastboot we got, mode (ns)
30.50
was hoping maybe i got some thing that can be useful to one of our respected developers if not what frimware should i try to install?

In the bootloader if you type:
fastboot getvar all
Click to expand...
Click to collapse
You might be able to get a bit more info.

killsforpie said:
In the bootloader if you type:
You might be able to get a bit more info.
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 3050
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Elpida S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: TA17607A81
(bootloader) qe:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: 6D3830040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Mon Jul 1 16:34:20 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X-118-GHOST_GNPO-6
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 8
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid:
(bootloader) ro.product.name: factory_ghost
(bootloader) ro.build.fingerprint[0]: motorola/factory_ghost/ghost:4.2
(bootloader) ro.build.fingerprint[1]: .2/13.9.0Q2.X-118-GHOST_GNPO-6/8
(bootloader) ro.build.fingerprint[2]: :userdebug/release-keys
(bootloader) ro.build.version.full:
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 9c632ef-00003-g99060a2 (hudsoncm
(bootloader) kernel.version[2]: @il93lnxdroid50) (gcc version 4.
(bootloader) kernel.version[3]: 6.x-google 20120106 (prerelease)
(bootloader) kernel.version[4]: (GCC) ) #1 SMP PREEMPT Mon Jul
(bootloader) kernel.version[5]: 1 16:57:14 CDT 2013
all:
finished. total time: 0.149s
this device seams to be some test or prototype device, maybe valuable to the right dev, it has no cam app but does have a test cam app also missing a lot of stock apps, app called( rf on) which seams to be some testing app, my pc recognized it as factory_ghost and not model number ,

Where did you get it man.

adity said:
Where did you get it man.
Click to expand...
Click to collapse
it was in a large lot of phones i got at an auction, i have no history, it has to be some sort of test device or prototype? did i mention in first post that bootloader is unlocked? what do you think?

also missing some settings compared to 444
touchless control
motorola connect
motorola privacy
motorola device id
about phone has no (system update)

hugh a said:
just received a lot of defected 2013 x's and one is like i have never seen, it has no branding on bat cover and bootloader is unlocked with 4.2.2 os,
Click to expand...
Click to collapse
In bootloader mode, go to barcodes - it should tell you the model number.
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
hugh a said:
did i mention in first post that bootloader is unlocked? what do you think?
Click to expand...
Click to collapse
Is the unlocked bootloader status code 3 or status code 1?
---------- Post added at 08:43 AM ---------- Previous post was at 08:22 AM ----------
hugh a said:
ro.product.name: factory_ghost
Click to expand...
Click to collapse
My XT1060 retail Verizon model and XT1060 Dev Ed both say:
ro.product.name: ghost_verizon
So what you have likely is a factory model. It should be unlocked status code 1, which is how they are manufactured and then they are locked in the factory and become status code 0.
Can you take a pic of the screen in bootloader mode?

Have you tried a factory reset to see if you get the standard settings + launcher back?

JulesJam said:
In bootloader mode, go to barcodes - it should tell you the model number.
---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------
Is the unlocked bootloader status code 3 or status code 1?
---------- Post added at 08:43 AM ---------- Previous post was at 08:22 AM ----------
My XT1060 retail Verizon model and XT1060 Dev Ed both say:
ro.product.name: ghost_verizon
So what you have likely is a factory model. It should be unlocked status code 1, which is how they are manufactured and then they are locked in the factory and become status code 0.
Can you take a pic of the screen in bootloader mode?
Click to expand...
Click to collapse
status code 1

dagoban said:
Have you tried a factory reset to see if you get the standard settings + launcher back?
Click to expand...
Click to collapse
yes, no change

hugh a said:
status code 1
Click to expand...
Click to collapse
That's definitely a factory device. Status code 1 unlocked is how they are in the factory before they get locked and shipped out as status code 0 locked.
Also, I believe that AP Fastboot Flash Mode (NS) the NS means not secure unlike on the production models where it is S for secure. I am not sure what this means exactly but I think I read it means you could get fastboot to flash a custom bootloader. Not sure.
Then the bootloader has an additional option - Switch console. Not sure what that means.
I would think a dev would be interested in the device - jcase or beaups in particular since they were the ones to have rooted and unlocked Moto X's in the past.
Obviously the device can never operate as a phone b/c of the lack of an IMEI number - you could clone one but that is illegal.

JulesJam said:
That's definitely a factory device. Status code 1 unlocked is how they are in the factory before they get locked and shipped out as status code 0 locked.
Also, I believe that AP Fastboot Flash Mode (NS) the NS means not secure unlike on the production models where it is S for secure. I am not sure what this means exactly but I think I read it means you could get fastboot to flash a custom bootloader. Not sure.
Then the bootloader has an additional option - Switch console. Not sure what that means.
I would think a dev would be interested in the device - jcase or beaups in particular since they were the ones to have rooted and unlocked Moto X's in the past.
Obviously the device can never operate as a phone b/c of the lack of an IMEI number - you could clone one but that is illegal.
Click to expand...
Click to collapse
im very interested in donating the board to the right dev could you please put the word out, this was the main purpose of me starting this thread, you are right the more i thought about it what good would it be to install os with out imei and i for sure dont even want to go there!
so jcase or beaups if you are interested pm me.

hugh a said:
im very interested in donating the board to the right dev could you please put the word out, this was the main purpose of me starting this thread, you are right the more i thought about it what good would it be to install os with out imei and i for sure dont even want to go there!
so jcase or beaups if you are interested pm me.
Click to expand...
Click to collapse
You have to put an @ in front of their names like this to get them notified
@jcase @beaups - @hugh a has a factory moto x 2013 that he would like to donate to a dev if you would like it as a test device. It is status code 1 unlocked with fastboot flash mode (NS) as shown in the pics this thread. Please PM him if you are interested.
The bootloader is version 30.50, which I have never seen before. I think the earliest bootloader released for sale was the 30.70. And this factory device has an additional option in the bootloader menu - Switch Console. It doesn't have an IMEI. He bought it in an auction of a batch of moto x's.

JulesJam said:
You have to put an @ in front of their names like this to get them notified
@jcase @beaups - @hugh a has a factory moto x 2013 that he would like to donate to a dev if you would like it as a test device. It is status code 1 unlocked with fastboot flash mode (NS) as shown in the pics this thread. Please PM him if you are interested.
The bootloader is version 30.50, which I have never seen before. I think the earliest bootloader released for sale was the 30.70. And this factory device has an additional option in the bootloader menu - Switch Console. It doesn't have an IMEI. He bought it in an auction of a batch of moto x's.
Click to expand...
Click to collapse
JulesJam :good:

Question Do NOT Convert from CN ROM to Global ROM (CN ROM Officially Supports Google Play Services)

For those who are planning to buy from Motorola China (CN ROM), do NOT convert to Global ROM! Do NOT buy from an online retailer where the phone has been converted to global ROM.
This is a warning to everyone if you don't want any headache in software support.
Reasons why you should NOT convert to Global ROM:
1. You can NEVER re-lock your bootloader - your phone will get BRICKED if you try to re-lock your bootloader.
2. You can NEVER update your software over-the-air. Do you want to own a phone with an update-less software? Yes, this is NOT possible as there will be an error message everytime you try to update your phone's software.
3. There will be a WARNING MESSAGE ("Your bootloader is unlocked.. etc") every time you restart your phone. Do you want this nasty message to ruin your phone's software?
4. Google Pay will detect your phone as tampered won't meet security requirements.
5. Streaming platforms and banking apps may not work once your phone is rooted.
Why do you NEED to update to Global ROM when in fact, CN ROM OFFICIALLY SUPPORTS Google Play Services.
1. Just go to Settings > System > Google Play Services
2. Toggle to ON and you can now install Play Store and use it to download your favorite Google Apps.
NO issues whatsoever. As simple as that.

My device is converted and bl is locked. That's how it came to me, i have no idea It's not even unlocked right now )
Updates are coming and installing, no problem.
BL locked & no warning message.
Even if this was not the case, i would like to convert the device again, because there is no language in CN rom, as far as i know, only CN and EN languages.
My country Turkey & my language Turkish
Your question is a little pointless. Not everyone has to know Chinese or English. For this reason, it may need this procedure, for example I

cascade128 said:
My device is converted and bl is locked. That's how it came to me, i have no idea It's not even unlocked right now )
Updates are coming and installing, no problem.
BL locked & no warning message.
Even if this was not the case, i would like to convert the device again, because there is no language in CN rom, as far as i know, only CN and EN languages.
My country Turkey & my language Turkish
Your question is a little pointless. Not everyone has to know Chinese or English. For this reason, it may need this procedure, for example I
Click to expand...
Click to collapse
Read below
Pls don't spread false information that bl can be RE-LOCKED because Motorola modders know it will brick your phone
[CLOSED] Convert your Moto x30 Pro (CN) to Edge 30 Ultra (EU)
FIRST OFF: If you have not bought the phone yet and plan on getting it: DON'T. The camera is broken and Motorola refuses to communicate with their customers. Is a fix coming? I someone working on it? Who knows. The phone is also still on Android...
forum.xda-developers.com

ijuanp03 said:
Read below
Pls don't spread false information that bl can be RE-LOCKED because Motorola modders know it will brick your phone
[CLOSED] Convert your Moto x30 Pro (CN) to Edge 30 Ultra (EU)
FIRST OFF: If you have not bought the phone yet and plan on getting it: DON'T. The camera is broken and Motorola refuses to communicate with their customers. Is a fix coming? I someone working on it? Who knows. The phone is also still on Android...
forum.xda-developers.com
Click to expand...
Click to collapse
Dude, i don't give information to "lock it". I wrote "It was sold to me like this, i received it like this" look there, read it well, don't be idle

ijuanp03 said:
Read below
Pls don't spread false information that bl can be RE-LOCKED because Motorola modders know it will brick your phone
[CLOSED] Convert your Moto x30 Pro (CN) to Edge 30 Ultra (EU)
FIRST OFF: If you have not bought the phone yet and plan on getting it: DON'T. The camera is broken and Motorola refuses to communicate with their customers. Is a fix coming? I someone working on it? Who knows. The phone is also still on Android...
forum.xda-developers.com
Click to expand...
Click to collapse
I dont know if it can really brick your phone when you convert in a clean way and your device is recognized as the original.
But I put the warning there as a lot of people have bricked their devices before by not paying proper attention.
In theory it SHOULD be possible to relock, once you are on the original firmware but I strongly advise against it.
No idea how @cascade128 received a locked converted device though, seems to be possible.
I dont know why you are so radical against unlocking, of course it brings drawbacks but that was always the case since Samsung implemented efuses.
Also: Android Auto and Hey Google do not work on CN and there is a very limited language selection.
@cascade128: could you boot into fastboot / bootloader, create a "fastboot getvar all" dump and send it to me via PM?
I'd really like to take a look at this. Also: Does the Lenovo Rescue assistant recognize your device as xt2241-2?

Killuminati91 said:
I dont know if it can really brick your phone when you convert in a clean way and your device is recognized as the original.
But I put the warning there as a lot of people have bricked their devices before by not paying proper attention.
In theory it SHOULD be possible to relock, once you are on the original firmware but I strongly advise against it.
No idea how @cascade128 received a locked converted device though, seems to be possible.
I dont know why you are so radical against unlocking, of course it brings drawbacks but that was always the case since Samsung implemented efuses.
Also: Android Auto and Hey Google do not work on CN and there is a very limited language selection.
@cascade128: could you boot into fastboot / bootloader, create a "fastboot getvar all" dump and send it to me via PM?
I'd really like to take a look at this. Also: Does the Lenovo Rescue assistant recognize your device as xt2241-2?
Click to expand...
Click to collapse
I sent

Well the fact to have a converted device with a locked bootloader it is good for modding!
I guess @cascade128 bought from a vendor that has maybe contacts in Motorola (or is someone from Motorola itself) that has access to stuff that we don't.
It is interesting though...cause I'm holding on on unlocking the bootloader (and then rooting) for warranty purposes and I don't how long I can wait
Cause now my "Unlock OEM" option isn't greyed out anymore

I bought the device second hand and it was like this. I also get this error when i try to unlock BL.
Error:
(bootloader) Failed to get unlock data.
OKAY [ 0.026s]
Finished. Total time: 0.028s
Mobile phones imported in our country(Turkey) must be registered with a passport, paying tax (government tax $150). Conditions: Having entered/exited a country with this passport in the last 1 year and the sim card(s) to be used in the device belong to the passport holder. This device has to be used by this passport holder for 3 years. For this reason, the imei numbers of this device have also been changed. 2 imei numbers belong to an old Motorola brand device. Main question; how did he enable bootloader lock after doing these? I think what he's using is the software box. Otherwise, this operation is not possible! The guy who made it gave this information, paid $60.
My device:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-eqs-3d687e600d1-220914
(bootloader) product: eqs
(bootloader) board: eqs
(bootloader) secure: yes
(bootloader) lcs-state: SECURE_PROD_MODE
(bootloader) hwrev: PVT1C
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB SAMSUNG KLUEG4RHGB-B0E1 FV=0201 WB=2048
(bootloader) ram: 12GB SAMSUNG LP5 DIE=12Gb CH=4
(bootloader) cpu: SM_PALIMA 1.0
(bootloader) serialno: ***************
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 41E4067C001D90E1
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) chipid: 0000043B41E4067C
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: ********************
(bootloader) imei2: ******************
(bootloader) meid:
(bootloader) date: 08-21-2022
(bootloader) sku: XT2241-1
(bootloader) carrier_sku: XT2241-1
(bootloader) battid: SB18D62340
(bootloader) battery-voltage: 3975
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: reteu
(bootloader) ro.build.fingerprint[0]: motorola/eqs_ge/eqs:12/S3SQ32.16-5
(bootloader) ro.build.fingerprint[1]: 3-9/d68d4-cb5c2:user/release-keys
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.VENDOR.1.0.R1
(bootloader) ro.build.version.qcom[1]: .11.00.00.816.142
(bootloader) version-baseband[0]: M8475_DE10_240.2652.01.143.19R EQS_PVT
(bootloader) version-baseband[1]: 1C_ROWDSDS_CUST
(bootloader) kernel.version[0]: Linux version 5.10.101-android12-9-00001
(bootloader) kernel.version[1]: -g1b6eff567cae-ab8943976 ([email protected]
(bootloader) kernel.version[2]: ld-host) (Android (7284624, based on r41
(bootloader) kernel.version[3]: 6183b) clang version 12.0.5 (https://and
(bootloader) kernel.version[4]: roid.googlesource.com/toolchain/llvm-pro
(bootloader) kernel.version[5]: ject c935d99d7cf2016289302412d708641d52d
(bootloader) kernel.version[6]: 2f7ee), LLD 12.0.5 (/buildbot/src/androi
(bootloader) kernel.version[7]: d/llvm-toolchain/out/llvm-project/lld c9
(bootloader) kernel.version[8]: 35d99d7cf2016289302412d708641d52d2f7ee))
(bootloader) kernel.version[9]: #1 SMP PREEMPT Sat Aug 13 08:16:31 UTC
(bootloader) kernel.version[10]: 2022
(bootloader) git:xbl_config: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:xbl_ramdump: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:uefi: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:abl: MBM-3.0-eqs-3d687e600d1-220914
(bootloader) git:aop: MBM-3.0-eqs-abd531e6-dirty-220914
(bootloader) git:aop_config: MBM-3.0-eqs-abd531e6-dirty-220914
(bootloader) git:tz: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:hyp: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:devcfg: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:keymaster: MBM-3.0-eqs-1a8597eb-220914
(bootloader) git:storsec: MBM-3.0-eqs-1a8597eb-220914
(bootloader) git:uefisecapp: MBM-3.0-eqs-1a8597eb-220914
(bootloader) gitrov: MBM-3.0-eqs-896c99b46-dirty-220914
(bootloader) git:qupfw: MBM-3.0-eqs-f3989a2-220914
(bootloader) git:cpucp: MBM-3.0-eqs-f3989a2-220914
(bootloader) git:shrm: MBM-3.0-eqs-01b1dd0a1-dirty-220914
(bootloader) git:spss: MBM-3.0-eqs-f3989a2-220914
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 7
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D53290
(bootloader) snapshot-update-status: none
(bootloader) primary-display[0]: csot_nt37701A_667_curve_1080x2400_dsc_c
(bootloader) primary-display[1]: md_c4
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
Finished. Total time: 0.126s

Killuminati91 said:
I dont know if it can really brick your phone when you convert in a clean way and your device is recognized as the original.
But I put the warning there as a lot of people have bricked their devices before by not paying proper attention.
In theory it SHOULD be possible to relock, once you are on the original firmware but I strongly advise against it.
No idea how @cascade128 received a locked converted device though, seems to be possible.
I dont know why you are so radical against unlocking, of course it brings drawbacks but that was always the case since Samsung implemented efuses.
Also: Android Auto and Hey Google do not work on CN and there is a very limited language selection.
@cascade128: could you boot into fastboot / bootloader, create a "fastboot getvar all" dump and send it to me via PM?
I'd really like to take a look at this. Also: Does the Lenovo Rescue assistant recognize your device as xt2241-2?
Click to expand...
Click to collapse
Exactly. Did the person really received a converted and "locked" device?
Moto modders know too well this WILL brick your phone. It's a given fact already

SedyBenoitPeace said:
Well the fact to have a converted device with a locked bootloader it is good for modding!
I guess @cascade128 bought from a vendor that has maybe contacts in Motorola (or is someone from Motorola itself) that has access to stuff that we don't.
It is interesting though...cause I'm holding on on unlocking the bootloader (and then rooting) for warranty purposes and I don't how long I can wait
Cause now my "Unlock OEM" option isn't greyed out anymore
Click to expand...
Click to collapse
I can say the same without any proof whatsoever. Unless...

English Community-Lenovo Community

cascade128 said:
English Community-Lenovo Community
Click to expand...
Click to collapse
Your version is "reteu" which is NOT "retcn" (CN ROM) so your phone is Edge 30 Ultra from the beginning

Nope. Its possible to switch carrier info via fastboot command.
@cascade128: What happens when you try to get an unlock code from the official site with the ORIGINAL imei?

cascade128 said:
English Community-Lenovo Community
Click to expand...
Click to collapse
So now you have to tell us where you bought the phone in order for us to unlock and then relock the bootloader! hahahah
I don't know how much I can resist without unlocking, but I have to say that now without root you can do plenty of things comparing with the past.

ijuanp03 said:
Your version is "reteu" which is NOT "retcn" (CN ROM) so your phone is Edge 30 Ultra from the beginning
Click to expand...
Click to collapse

Killuminati91 said:
Nope. Its possible to switch carrier info via fastboot command.
@cascade128: What happens when you try to get an unlock code from the official site with the ORIGINAL imei?
Click to expand...
Click to collapse
You can't tell him, because that kid doesn't really know, but he has a lot of ideas/claims. He doesn't know anything. I guess that's enough for the last photo i sent to be silent
The original imei numbers of the device need to be rewritten. The person who will do it is in Istanbul, but i am not in Istanbul. I am in a far place. I will go at the first opportunity and write the original imei numbers and unlock the device there. Of course that will cost me another $60.
@SedyBenoitPeace I bought it second hand from one of the users, it was used for 1 week. He had these processes done by a software repairman in Istanbul, for 60$. No need to be surprised, our place is full of inventors

cascade128 said:
You can't tell him, because that kid doesn't really know, but he has a lot of ideas/claims. He doesn't know anything. I guess that's enough for the last photo i sent to be silent
The original imei numbers of the device need to be rewritten. The person who will do it is in Istanbul, but i am not in Istanbul. I am in a far place. I will go at the first opportunity and write the original imei numbers and unlock the device there. Of course that will cost me another $60.
@SedyBenoitPeace I bought it second hand from one of the users, it was used for 1 week. He had these processes done by a software repairman in Istanbul, for 60$. No need to be surprised, our place is full of inventors
Click to expand...
Click to collapse
Well thank you for the insight...for sure this Istanbul's guy is someone from Motorola or at least has some Motorola tools

SedyBenoitPeace said:
Well thank you for the insight...for sure this Istanbul's guy is someone from Motorola or at least has some Motorola tools
Click to expand...
Click to collapse
There are service boxes we call "Box", this friend is Turkish. It's not from Motorola, it's a software developer. I don't know exactly, but he's famous in his business. As i said, there are many such people here. There are some Syrians, even Iranians. They can solve insurmountable problems with the service equipment (different manufacturers) we call this "box", these works are quite famous in our country.
For example very famous this Box: https://sigmakey.com/
That these devices can "force flash" the event. In other words, they can flash firmware without the need for any unlock code or processing.
For example very famous again(update list / writing edge 30 ultra:
ChimeraTool supported models
9,925 supported models of Samsung, Blackberry, Nokia, Sony, HTC, LG, Huawei, Lenovo, Xiaomi, MTK, Vivo, Qualcomm, Generic Android, Oppo, Motorola, Utility, ASUS devices. Find your model!
chimeratool.com

ijuanp03 said:
For those who are planning to buy from Motorola China (CN ROM), do NOT convert to Global ROM! Do NOT buy from an online retailer where the phone has been converted to global ROM.
This is a warning to everyone if you don't want any headache in software support.
Reasons why you should NOT convert to Global ROM:
1. You can NEVER re-lock your bootloader - your phone will get BRICKED if you try to re-lock your bootloader.
2. You can NEVER update your software over-the-air. Do you want to own a phone with an update-less software? Yes, this is NOT possible as there will be an error message everytime you try to update your phone's software.
3. There will be a WARNING MESSAGE ("Your bootloader is unlocked.. etc") every time you restart your phone. Do you want this nasty message to ruin your phone's software?
Why do you NEED to update to Global ROM when in fact, CN ROM OFFICIALLY SUPPORTS Google Play Services.
Just go to Settings > System > Google Play Services
Toggle to ON and you can now install Play Store and use it to download your favorite Google Apps.
NO issues whatsoever. As simple as that.
Click to expand...
Click to collapse
Does this work with all Google services? Such as Google pay, assistant and so on? Debating buying the phone on aliexpress as there's a sale.

Either way, dont buy it until they fix the camera.