Database Develop

[Q] XT1058 SIM lock mystery

I am baffled by my XT1058. I got it from ebay (clearlya mistake), so I don't know its history. The phone works fine with TMobile SIM cards; this should imply that the phone has no SIM locks. However, h2o and AT&T SIM cards ask for a network unlock PIN!
I've tried going through TMobile to get a network unlock PIN, but they say that the phone didn't originate with them (obviously) so they can't provide a PIN. Motorola has told me that the phone should already be SIM unlocked, so no help there.
Anyone have any thoughts on this? Could it be some kind of software issue? (I've tried flashing the stock AT&T sbf; didn't resolve the issue.)

Go through a 3rd party online unlocking company like cell unlocker net. Only costs like $8.99 or something.
I did this for my XT1058 in Canada, purchased at Fido. I'm now using on Bell.

Thanks for the advice.. I'm not very confident that they'll be able to produce a working code, but I've submitted an order to one of the unlocking services.

I bought an unlock code for my rogers 1058 no problem. On telus since day one.

ChadFM said:
Thanks for the advice.. I'm not very confident that they'll be able to produce a working code, but I've submitted an order to one of the unlocking services.
Click to expand...
Click to collapse
If their code has several groups of 8 numbers, read the instructions carefully, e.g., you may be required to enter the 2nd group of 8 numbers and ignore the rest.

I tried an unlocking service "Motorola unlock code All Models/Networks", and they told me that they couldn't unlock it. (I was quickly refunded, thankfully.) Any other thoughts/suggestions..?

Is the bootloader unlocked and what firmware was installed when you received it?

@ChadFM are you sure its an XT1058? Does it have the ATT logo on its back?
Can you see any model number on its back (near the bottom edge, by the little hole)? Its often small and difficult to read.

KidJoe said:
@ChadFM are you sure its an XT1058? Does it have the ATT logo on its back?
Can you see any model number on its back (near the bottom edge, by the little hole)? Its often small and difficult to read.
Click to expand...
Click to collapse
The case says it's an XT1058, yeah - no AT&T branding, FCC ID IHDT56PA1, assembled in the USA.

There is no XT-1058 that should be locked to t-mobile, well there is no Moto X period that should be locked to t-mobile. I am wondering if it is really even a XT-1058 or if it has had the back cover swapped out. For sure it is an odd ball phone that someone messed with or was some sort of demo/sample phone early in its life.

Steve-x said:
There is no XT-1058 that should be locked to t-mobile, well there is no Moto X period that should be locked to t-mobile. I am wondering if it is really even a XT-1058 or if it has had the back cover swapped out. For sure it is an odd ball phone that someone messed with or was some sort of demo/sample phone early in its life.
Click to expand...
Click to collapse
It's crossed my mind that the back might have been swapped out. To make matters more complicated, the phone was running an XT1053 custom rom when I got it.. Interesting idea that it might have been some kind of demo/sample.

Hmm, Any chance it is maybe some CDMA(Verizon, Sprint, or a smaller regional carrier) variant of the phone that happens to allow t-mobile but not AT&T and the seller slapped some other rom on to it along with a new back cover.
You might want to try the following command at the fastboot screen "fastboot getvar all" which will give detailed information regarding the hardware in the phone. Post the output if you can, removing all of your unique information. I'd really like to know which radio it has installed - that should tell us the actual hardware model you have.

Steve-x said:
Hmm, Any chance it is maybe some CDMA(Verizon, Sprint, or a smaller regional carrier) variant of the phone that happens to allow t-mobile but not AT&T and the seller slapped some other rom on to it along with a new back cover.
You might want to try the following command at the fastboot screen "fastboot getvar all" which will give detailed information regarding the hardware in the phone. Post the output if you can, removing all of your unique information. I'd really like to know which radio it has installed - that should tell us the actual hardware model you have.
Click to expand...
Click to collapse
Now that would be very interesting, if this is actually a CDMA variant. I've combed through the getvar info before, when previously trying to figure out if the phone's actually an XT1058 - I didn't notice any interesting radio info, but I wasn't looking for it specifically. I'll post a dump of that info later this evening!

Here's the getvar output; note that I've got an XT1053 rom running currently. (I get the same SIM behavior on the stock AT&T rom.)
Do the radio/hwrev codes here have any significance?
(bootloader) version-bootloader: 30B4
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(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: 0x6
(bootloader) secure: yes
(bootloader) mid: 026b
(bootloader) serialno: LXTU2K0005
(bootloader) qe: qe 1/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) uid: <snip>
(bootloader) imei: <snip>
(bootloader) meid:
(bootloader) sku: XT1053
(bootloader) cid: 0x00
(bootloader) iccid:
(bootloader) date: 06-15-2013
(bootloader) cust_md5:
(bootloader) reason: Reboot to bootloader
(bootloader) ro.build.date: Fri Jan 10 22:11:02 CST 2014
(bootloader) ro.build.id: KXA20.16-1.25
(bootloader) ro.build.tags: release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: hudsoncm
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 31
(bootloader) ro.build.version.release: 4.4.2
(bootloader) ro.mot.build.customerid: Retail
(bootloader) ro.product.name: ghost_retail
(bootloader) ro.build.fingerprint[0]: motorola/ghost_retail/ghost:4.4.
(bootloader) ro.build.fingerprint[1]: 2/KXA20.16-1.25/31:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.161.44.25.ghost_row
(bootloader) ro.build.version.full[1]: .Retail.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-g8ee710a (h
(bootloader) kernel.version[1]: [email protected]) (gcc version
(bootloader) kernel.version[2]: 4.7 (GCC) ) #1 SMP PREEMPT Fri J
(bootloader) kernel.version[3]: an 10 22:24:43 CST 2014

This line should indicate which version it is - (bootloader) radio: 0x6
I am not at home to verify but am 99% sure that an XT-1058 will report radio 0x1.
I am also pretty sure that the XT-1053 has radio 0x6 - hopefully someone can verify.

Steve-x said:
This line should indicate which version it is - (bootloader) radio: 0x6
I am not at home to verify but am 99% sure that an XT-1058 will report radio 0x1.
I am also pretty sure that the XT-1053 has radio 0x6 - hopefully someone can verify.
Click to expand...
Click to collapse
Another thread seems to support those values: http://forum.xda-developers.com/moto-x/general/moto-x-cyanognmod-11-nightlies-to-start-t2627812
If there is a definite correlation between that value and the model number (the value is HW based), then this situation is even more complicated.. Does a sim-locked XT1053 even exist?

ChadFM said:
Here's the getvar output; note that I've got an XT1053 rom running currently. (I get the same SIM behavior on the stock AT&T rom.)
Do the radio/hwrev codes here have any significance?
<SNIP>
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) uid: <snip>
(bootloader) imei: <snip>
(bootloader) meid:
(bootloader) sku: XT1053
<SNIP>
Click to expand...
Click to collapse
So it appears its an XT1053 and has its bootloader unlocked.
The iswarrantyvoid being yes, makes me question if its the "unlocked GSM (comes with T-Mobile SIM)" version, or does the GSM Dev Edition say that too?

Taking a step back, are these getvar all values hardware based, or could they have been modified by flashing different firmwares..?

ChadFM said:
Taking a step back, are these getvar all values hardware based, or could they have been modified by flashing different firmwares..?
Click to expand...
Click to collapse
it is my understanding that the uid, imei, meid, sku, cid, iccid, and a few others are hardware based. Those that start with ro.build, and kernel are based on the rom flashed on the device.
In the OP you mention you tried flashing the stock XT1058 SBF... what was the last SBF you flashed to this phone? If it was the ATT XT1058 sbf, and the phone still reports XT1053 for SKU, then at least that field is hardware based.
And to answer your earlier question, No I haven't seen an XT1053 that is SIM-Locked. Moto sells the XT1053 as the "GSM Unlocked (ships with T-Mobile SIM)" version, and the GSM Dev Edition, both are sim unlocked out of the box.

I did last flash an AT&T XT1058 SBF.. so you're right, that supports that at least some of the fields are HW-based.
Maybe there's some international carrier that locks the XT1053, and it just happens to work on TMobile?

[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.

Lost Imei and Wifi signal, Help with remote failure in adb (Soft Brick maybe?)

First sorry for my english, i'm from Brazil and my english level is medium
So by the way here is my sad history
I used the Resurection Remix 7 (pie) but yesterday i tryed to go back for the stock rom, first it worked perfectly, but the IMEI is lost and i can't activate wifi, mobile data or receive/make calls or messages
I can't boot twrp in XT1929-5 because i receive the "your device is corrupt. It can't be trusted and will not boot" message
in fastboot i receive "flashing_locked" message but in the system i can't activate the oem unlock again because the option still unclickable (but the important detail is, i also have bootloader unlocked, this erros is some type of bug or something like this)
when i try to flash another stock rom also every command send the message:
"(bootloader) Permission denied
FAILED (remote failure)"
Now my system is working but how i sayed before, without imei and connections (not even wifi)
I can't found any blankflash to try to recover it and lenovo moto assist doesn't recognize my device at all
All the way, this is my getvar all information:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: BRAZIL
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0048010058
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: DC9858EE
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354106092159158
(bootloader) meid:
(bootloader) date: 06-18-2018
(bootloader) sku: XT1929-5
(bootloader) carrier_sku: XT1929-5
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 4319
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-2/7699:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.3.beckham.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gcc5f412 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Mar 27 12:33:10 CDT 2019
(bootloader) git:abl: MBM-3.0-beckham_retail-8ca64c4-190327
(bootloader) git:xbl: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) gitmic: MBM-3.0-beckham_retail-d286d94-190327
(bootloader) git:rpm: MBM-3.0-beckham_retail-4696e9e-190327
(bootloader) git:tz: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:hyp: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:devcfg: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:cmnlib64: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:keymaster: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) gitrov: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) git:storsec: MBM-3.0-beckham_retail-edce8d3-dirty-190327
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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: 0
all: listed above
finished. total time: 0.181s
the roms that i tryed is:
BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and
BECKHAM_SPRINT_OCW28.70-47_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Upadate
Today i try to flash custom roms with adb sideload (stock recovery) to try to fix my problem
and my result is a giant failure, i got these messages bellow:
with stock roms i've got
"error 21 installation aborted
signature verification failed"
and with custom roms i've got
"error failed to verify whole-file signature
installation aborted
signature verification failed"
Someone please help me, i'm out of ideas and really don't know what to do

Have you tried flashing the stock Pie ROM?
In my case, I tried to flash Oreo after having Pie (it was this firmware: BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) to recover an Oreo backup I had made with TWRP, but for some reason I couldn't enter the recovery because it gave me bootloop. Try out this firmware: Firmware oficial 9.0.0 Pie

This just happened to me on a never-unlocked bootloader using the OFFICIAL Lenovo Smart Assistant app to update to the software that the app located and flashed. All seemed well until I noticed wifi wouldn't turn on; mobile didn't work; IMEI is blank--not "0", blank as is baseband. Ran getvar and IMEI shows so the files must still be on it. My phone is just over 2 months old so still warranted.

Me too.... I just sent the device to moto USA for repair...
ritchea said:
This just happened to me on a never-unlocked bootloader using the OFFICIAL Lenovo Smart Assistant app to update to the software that the app located and flashed. All seemed well until I noticed wifi wouldn't turn on; mobile didn't work; IMEI is blank--not "0", blank as is baseband. Ran getvar and IMEI shows so it the files must still be on it. My phone is just over 2 months old so still warranted.
Click to expand...
Click to collapse

arburodi said:
Me too.... I just sent the device to moto USA for repair...
Click to expand...
Click to collapse
Yes same here. I was using the official lenovo app to upgrade and now my phone is junk. What do I do? Do you have the motorola phone number handy?
I have a moto z3 play no unlocked nonsense or unlicensed ROMs. Just a phone. Now it won't connect to wifi, Lenovo smart assistant doesn't recognize it, and I'm screwed. It said it had an update (not pie) just a regular beckham update. I downloaded it and went through the procedure as normal. Now nothing.
J

If your phone is still in warranty, go online and request repair, and you will get a replacement phone. I sent back my defective phone and I just got replacement this afternoon.
Try below link to start: https://motorola-global-portal.custhelp.com/app/mcp/service/p/30,6720,9277/#/service
Jcanner said:
Yes same here. I was using the official lenovo app to upgrade and now my phone is junk. What do I do? Do you have the motorola phone number handy?
I have a moto z3 play no unlocked nonsense or unlicensed ROMs. Just a phone. Now it won't connect to wifi, Lenovo smart assistant doesn't recognize it, and I'm screwed. It said it had an update (not pie) just a regular beckham update. I downloaded it and went through the procedure as normal. Now nothing.
J
Click to expand...
Click to collapse

Jcanner said:
Yes same here. I was using the official lenovo app to upgrade and now my phone is junk. What do I do? Do you have the motorola phone number handy?
I have a moto z3 play no unlocked nonsense or unlicensed ROMs. Just a phone. Now it won't connect to wifi, Lenovo smart assistant doesn't recognize it, and I'm screwed. It said it had an update (not pie) just a regular beckham update. I downloaded it and went through the procedure as normal. Now nothing.
J
Click to expand...
Click to collapse
To clarify the phone does turn on and everything but it doesn't have an IMEI and the wifi won't work. None of the recovery options work with motorola smart assistant. I did a factory reset and it is the same. Nothing. I ordered a g7 power a minute ago. I want to forget about this z3 phone but if I can get it to work someday maybe one of my kids can use it.
This is motorola/lenovo in a nutshell. It's like getting a tool from harbor freight. It will work. . .for a while. but it is cheap enough so you don't care, really.
J

I guess there was something wrong with the firmware. It looks like they withdrew the firmware from the tool because i don't see it any more...
You can get the replacement phone if you have warranty. Otherwise, you may just unlock the bootloader and install PIE.
Jcanner said:
To clarify the phone does turn on and everything but it doesn't have an IMEI and the wifi won't work. None of the recovery options work with motorola smart assistant. I did a factory reset and it is the same. Nothing. I ordered a g7 power a minute ago. I want to forget about this z3 phone but if I can get it to work someday maybe one of my kids can use it.
This is motorola/lenovo in a nutshell. It's like getting a tool from harbor freight. It will work. . .for a while. but it is cheap enough so you don't care, really.
J
Click to expand...
Click to collapse

arburodi said:
If your phone is still in warranty, go online and request repair, and you will get a replacement phone. I sent back my defective phone and I just got replacement this afternoon.
Try below link to start: https://motorola-global-portal.custhelp.com/app/mcp/service/p/30,6720,9277/#/service
Click to expand...
Click to collapse
Thank you so much for this! I just printed out the labels and Fedex stuff and I'll ship it out in the morning. I was a good phone I hope I get one back that is useful. Maybe one that even has Pie. One can wish.
J

Jcanner said:
Thank you so much for this! I just printed out the labels and Fedex stuff and I'll ship it out in the morning. I was a good phone I hope I get one back that is useful. Maybe one that even has Pie. One can wish.
J
Click to expand...
Click to collapse
I posted my experience here. I don't expect the phone to even have the Feb update--the one that messed things up? I just hope I get a phone in perfect condition because I sent them one in that shape. I'll follow up when it comes.
Good luck with your repair.
I got the replacement phone today and it does appear to be perfect. It's on Jan. update as I suspected. Maybe when PIE rolls out to my phone, I'll update--if I still have it by then.

arburodi said:
I guess there was something wrong with the firmware. It looks like they withdrew the firmware from the tool because i don't see it any more....
Click to expand...
Click to collapse
OPWS28.70-31-12 which should have been March? I believe that's the one that wiped my radio. My notes (which could be wrong) say OPWS28.70-60-3 was Feb update. OPWS28.70-31-12 is still showing on my Smart Assistant app. I didn't attempt to do anything with it. I'll sit on OPWS28.70-31-8 until Pie--and then wait a few weeks to be sure.

Hmmm, Ok, I did use the smart assistant to flash OPWS28.70-31-12 and lost baseband.
After I received the replacement phone, I reecived an OTA notification, and i was able to upgrade to the same OPWS28.70-31-12 via OTA without errors.
However, the new patch still says February 1, 2019...
ritchea said:
OPWS28.70-31-12 which should have been March? I believe that's the one that wiped my radio. My notes (which could be wrong) say OPWS28.70-60-3 was Feb update. OPWS28.70-31-12 is still showing on my Smart Assistant app. I didn't attempt to do anything with it. I'll sit on OPWS28.70-31-8 until Pie--and then wait a few weeks to be sure.
Click to expand...
Click to collapse

I think I remember that it may have said Feb again. I've never received an ota update on my phone. Glad it's working for you .

I had the same issue after using Lenovo Moto Smart Assistant to update to OPWS28.70-31-12 tonight. After a lot of digging and frustration (I'm a relative noob), I found the following app, which allowed me to tether my computer's internet to my phone via USB.
https://github.com/Genymobile/gnirehtet
I downloaded the Windows Rust version, unzipped it and ran it. It failed, but I noted it required adb.exe, so I added the containing folder to my PATH (set path=%path%;C:\[folder-containing-adb.exe]). It ran without a hitch after that.
Since the phone now had access to the internet, the previously greyed out "Allow OEM Unlocking" in Developer Tools was available. I enabled it, successfully unlocked my bootloader, and am now working on reflashing a working ROM... will update with success, failure, or SOS.
I'm happy to go into further detail, should anyone need it, but thought I'd let people know it's not hopeless, and the app above was the key.
(Of course, if you'd rather take advantage of your warranty rather than voiding it, I completely understand. )
EDIT: The manual re-flash of the available stock ROMs failed to restore the Baseband, so the radios remain inactive and LMSA still won't recognize the phone for Rescue. Thoughts?

belltomb said:
(Of course, if you'd rather take advantage of your warranty rather than voiding it, I completely understand. )
Click to expand...
Click to collapse
Thanks. I was able to connect to internet via ethernet. I had successful adb already. None of that meant much without a zip to sideload. As you said, if you'd rather not void your warranty.
I'm glad more people are responding to this issue. A lot of users may have avoided this issue by not even being aware of the tool. Tool users with botched flashes probably did as you or I did--voided warranty/returned for replacement. My phone was too new to risk voiding warranty.
Did you return to stock? If so, what was your rom source?

ritchea said:
Thanks. I was able to connect to internet via ethernet.
Click to expand...
Click to collapse
Nice. USB-C ethernet dongle? I didn't have one and all the stores were closed. Or is there another way?
ritchea said:
Did you return to stock? If so, what was your rom source?
Click to expand...
Click to collapse
I certainly tried. This was my source: https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/
Their source seems to be zips of the files LMSA downloads, but they don't seem to be in a proper format to sideload. Nonetheless, I tried flashing the previous ROM I'd been on (28.70-31-8), the original Oreo ROM (28.70-31), and ResurrectionRemix. None of them restored the Baseband.

Hey guys, long time lurker, but first time poster. I also had the issue when I unlocked the bootloader on my XT1929-4 Unlocked Z3 Play and flashed the sprint variant rom. The Beckham-RETUS software does not have the sprint wi-fi calling option. After flashing the sprint variant rom, it also did not allow me to use the wi-fi calling app. So since I didn't want their bloatware on my phone, I wiped the device and re-flashed the Beckham_RETUS OPWS28.70-31-8 file. After flashing, the baseband was not found. So far the only baseband/modem file that has worked for me is M636_19.34.01.81R found in the sprint variant rom (XT1929-3_BECKHAM_SPRINT_8.1.0_OCWS28.70-61-4) also now with the official Beckham RETUS rom (BECKHAM_OPW28.70_60_3) Since I had already unlocked my bootloader my warranty was void, but my phone is working well on BECKHAM_OPW28.70_60_3 with FEB 2019 security update . Hope to see the official RETUS channel PIE update soon. Hope this helps

belltomb said:
Nice. USB-C ethernet dongle? I didn't have one and all the stores were closed. Or is there another way?.
Click to expand...
Click to collapse
I did have a USB micro dongle from years ago plus a C adapter.
Their source seems to be zips of the files LMSA downloads, but they don't seem to be in a proper format to sideload. Nonetheless, I tried flashing the previous ROM I'd been on (28.70-31-8), the original Oreo ROM (28.70-31), and ResurrectionRemix. None of them restored the Baseband.
Click to expand...
Click to collapse
I had two source files on PC from two updates. Yes, zip files but not packaged for sideloading
When I extracted the payload.bin from the second (bad one--28.70-31-12), it definitely shows a modem but no "radio" image. The more I look into how MOTO does things, the more I'm looking forward to selling the phone. It's a good phone in many ways, but I'll stick with the Pixel 3a. At least I can work within Google's parameters.

psxexpert said:
I wiped the device and re-flashed the Beckham_RETUS OPWS28.70-31-8 file.
Click to expand...
Click to collapse
How did you flash? a package? fb flash individual images? I'm just trying to understand how to work with these files as the files in the LMSA app downloads are at least 60% different from these downloads.
According to this site, stock roms can be flashed on LOCKED bootloader through fastboot. If I knew that, I'd forgotten it, but I don't think I knew that was possible. Has anyone done this. OTOH, I've read MANY tech articles on the web that had incorrect info. I just don't know enough about MOTO to know.
After flashing, the baseband was not found. So far the only baseband/modem file that has worked for me is M636_19.34.01.81R found in the sprint variant rom (XT1929-3_BECKHAM_SPRINT_8.1.0_OCWS28.70-61-4) also now with the official Beckham RETUS rom (BECKHAM_OPW28.70_60_3) Since I had already unlocked my bootloader my warranty was void, but my phone is working well on BECKHAM_OPW28.70_60_3 with FEB 2019 security update . Hope to see the official RETUS channel PIE update soon. Hope this helps
Click to expand...
Click to collapse

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.