Database Develop

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.

[Q] Unusual Boot loader variables in Moto X

I recently bought a used Moto X AT&T Version from a retailer (it's AT&T, back printed with its logo). It's functioning normally. GSM Network is recognized. I was also able to take an OTA upgrade to 4.4.4 (it was previously 4.4.2). Everything is working up to the mark.
Well, I rebooted my phone in Fastboot Mode (just for curiosity) and was completely shocked when I read Device is Unlocked: Status Code 1 printed on the screen. But, I know this variant can't be unlocked and secondly, I have never read about Status Code: 1. My Developer Edition prints Status Code: 3 which is obviously unlocked. Amazed of what I read, I got worried! So I issued fastboot getvar all command to the phone.
The result variables got me more worried! I have added them below for reference:
(bootloader) version-bootloader: 30B7
(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: 0x6
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: LXXXXXXXXXX
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: XXF8F3030C000100000000000000
(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: Wed Jun 25 00:10:28 PDT 2014
(bootloader) ro.build.id: KXA21.12-L1.26
(bootloader) ro.build.tags: bldacfg,release-keys
(bootloader) ro.build.type: user
(bootloader) ro.build.user: dbbuild
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 26
(bootloader) ro.build.version.release: 4.4.4
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.4.4/K
(bootloader) ro.build.fingerprint[1]: XA21.12-L1.26/26:user/bldacfg,re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.212.44.26.ghost_att
(bootloader) ro.build.version.full[1]: .ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-gb444bf1-00
(bootloader) kernel.version[1]: 004-g6b785f7 ([email protected]
(bootloader) kernel.version[2]: id14) (gcc version 4.7 (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Wed Jun 25 00:21:2
(bootloader) kernel.version[4]: 1 PDT 2014
Click to expand...
Click to collapse
1. Why the IMEI is being reported as 00000000000..... If I go to System>About>Status, IMEI is being correctly reported. Dialing *#06# also displays the IMEI correctly.
2. Why CID is 0xdead? From my knowledge CID is always a hex value. And what this CID 0xdead implies?
3. Bootloader reports unlocking is not supported. My friend also has a Moto X AT&T. His reports 'no' and also correctly shows IMEI and CID. Why this?
4. Does this means my Moto X is unlocked and I can flash any custom recovery on it? As Device reports it's unlocked.
5. Stock Recovery doesn't seem to work as it always says 'No Command'. Is it safe to flash the stock recovery?
From all this, I have only come to the conclusion that the device was tampered. But how such happened?
Thanks to everyone, who replies!

mfbcool said:
Device is Unlocked: Status Code 1 printed on the screen.
Click to expand...
Click to collapse
That is the factory state.
In bootloader mode do you see AP Fastboot Flash Mode (S) or (NS)?
---------- Post added at 08:23 AM ---------- Previous post was at 08:21 AM ----------
mfbcool said:
From all this, I have only come to the conclusion that the device was tampered. But how such happened?
Thanks to everyone, who replies!
Click to expand...
Click to collapse
Maybe it was a factory device and someone cloned an IMEI onto it - that might be what happened here.
---------- Post added at 08:30 AM ---------- Previous post was at 08:23 AM ----------
mfbcool said:
4. Does this means my Moto X is unlocked and I can flash any custom recovery on it? As Device reports it's unlocked.
Click to expand...
Click to collapse
I think it does. Try flashing TWRP and you will see.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
mfbcool said:
5. Stock Recovery doesn't seem to work as it always says 'No Command'. Is it safe to flash the stock recovery?
Click to expand...
Click to collapse
It is always safe to flash stock, signed files as long as you have the right version for your device.

Thanks JulesJam for the reply!
AP Fastboot Flash Mode is NS (please see picture in the attachment)
I'll try flashing TWRP tonight. Hope everything goes well! If bootloader locked I won't be even able to pass the flashing step, right? (as pre flash signature validation will fail)
Flashed TWRP 2.8.6.0 successfully! Everything is working like a charm.
Flashed Carbon ROM 5.1.1. Working flawlessly!

Where do all those factory devices suddenly come from?

Exactly my question!
dagoban said:
Where do all those factory devices suddenly come from?
Click to expand...
Click to collapse
I think such phones are actually being secretly stolen from the factory or being leeched out secretly. How could it be possible that Motorola sells a bootloader factory unlocked smartphone?

FYI, there are several old threads covering phones in this state.
The oldest example:
http://forum.xda-developers.com/moto-x/moto-x-qa/otas-att-xt1058-t2963150

mfbcool said:
Thanks JulesJam for the reply!
AP Fastboot Flash Mode is NS (please see picture in the attachment)
I'll try flashing TWRP tonight. Hope everything goes well! If bootloader locked I won't be even able to pass the flashing step, right? (as pre flash signature validation will fail)
Flashed TWRP 2.8.6.0 successfully! Everything is working like a charm.
Flashed Carbon ROM 5.1.1. Working flawlessly!
Click to expand...
Click to collapse
Flash away dude!!! Just keep in mind that your device is very unsecure in that if you lose it, anyone with any knowledge about these things will be able to do anything they want with that device just like you are able to. They will be able to circumvent any security on the device b/c the fastboot is not secure.
---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------
mfbcool said:
I think such phones are actually being secretly stolen from the factory or being leeched out secretly. How could it be possible that Motorola sells a bootloader factory unlocked smartphone?
Click to expand...
Click to collapse
They definitely weren't supposed to be sold to retail customers.
These devices didn't have IMEIs and so someone had to put an IMEI on the device, which is shady depending on how the IMEI was obtained.

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

[HELP] Completely stock Moto G5S plus "Start up failed"

Hi guys,
Today I woke up with myMoto G5Splus (completely stock & never unlocked bootloader) in bootloader mode showing the error "Start up failed: Your device didn't start up successfully. ecc".
Fastboot can see it, ADB can't. No luck with LMVA or RSC Lite. No luck with any fastboot command.
Here you can see fastboot getvar all output.
Code:
C:\Program Files (x86)\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12(*)
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: *omitted by me*
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 39694B0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.099s
From here I can see CID = 0xDEAD, which doesn't sound really reassuring. Any hint? Is my phone gone for good?

Your phone is stuck in "AP Fastboot mode (secure)" right?
I have the same problem! Even my getvar shows cid as 0xDEAD, no IMEI!
I am trying to roam around the XDA forum to find an answer but not luck! (I even asked for assistance yesterday but no one replied!)

daisiesk said:
Your phone is stuck in "AP Fastboot mode (secure)" right?
I have the same problem! Even my getvar shows cid as 0xDEAD, no IMEI!
I am trying to roam around the XDA forum to find an answer but not luck! (I even asked for assistance yesterday but no one replied!)
Click to expand...
Click to collapse
Exactly, without any reason. I am sure that it was still alive at least until 3am (I can see last backup), today at 7am it was "AP Fastboot mode (secure)" and 0xDEAD.

Biz92k said:
Exactly, without any reason. I am sure that it was still alive at least until 3am (I can see last backup), today at 7am it was "AP Fastboot mode (secure)" and 0xDEAD.
Click to expand...
Click to collapse
is your phone a XT1804, too?
Even i tried LMSA (and of course, it did not work), so after that went to show my phone to the Motorola customer service (in the midst of a pandemic!). No luck. Instead of helping me with the phone they started accusing me that I took my to some unofficial service center! This is completely false!
Then tried RSD lite, fastboot, mfastboot but I can't get past fastboot oem fb_mode_set. It says remote failure.
Now, I think we are in same (if not, at least similar) situation here. Annnnd I think I have a bad news about our phone.
In this case, we can, 1) Replace the eMMC/ whole motherboard (or whatever it is.... I have no idea).
2) Buy a new. (But I love my MOTO :crying: )

daisiesk said:
is your phone a XT1804, too?
Even i tried LMSA (and of course, it did not work), so after that went to show my phone to the Motorola customer service (in the midst of a pandemic!). No luck. Instead of helping me with the phone they started accusing me that I took my to some unofficial service center! This is completely false!
Then tried RSD lite, fastboot, mfastboot but I can't get past fastboot oem fb_mode_set. It says remote failure.
Now, I think we are in same (if not, at least similar) situation here. Annnnd I think I have a bad news about our phone.
In this case, we can, 1) Replace the eMMC/ whole motherboard (or whatever it is.... I have no idea).
2) Buy a new. (But I love my MOTO :crying: )
Click to expand...
Click to collapse
Mine is actually a XT1805, but it seems that the issue is exactly the same. I am actually already looking forward to the moto G8 plus because I need a phone in my everyday life, and right now I gave back life to my old Moto G (2013).
Btw, there is a way to at least access the memory? Might be useful to get access to the data stored in my phone (not saved on the SD card).

Biz92k said:
Mine is actually a XT1805, but it seems that the issue is exactly the same. I am actually already looking forward to the moto G8 plus because I need a phone in my everyday life, and right now I gave back life to my old Moto G (2013).
Btw, there is a way to at least access the memory? Might be useful to get access to the data stored in my phone (not saved on the SD card).
Click to expand...
Click to collapse
No offence, you still want to go for Motorola?
And about the data, I don't think it is possible. I think the problem with our phone is that the phone's partitions are corrupted (and, apparently, cannot be formatted).

daisiesk said:
No offence, you still want to go for Motorola?
Click to expand...
Click to collapse
Actually I really like the active display, and in the price tag (around 200€) I didn't found anything that really caught my attention, so I might actually go for the G8 plus. What would be your recommendation? I actually didn't check deeply, I just surfed Amazon a bit.
daisiesk said:
And about the data, I don't think it is possible. I think the problem with our phone is that the phone's partitions are corrupted (and, apparently, cannot be formatted).
Click to expand...
Click to collapse
At this point I think is not even a software problem, but I'm getting the idea that something definitely fried on the inside. Which would probably cost more to repair than to get a new phone

Biz92k said:
Actually I really like the active display, and in the price tag (around 200€) I didn't found anything that really caught my attention, so I might actually go for the G8 plus. What would be your recommendation? I actually didn't check deeply, I just surfed Amazon a bit.
Click to expand...
Click to collapse
I agree with the display as well as its classy look! I always wanted to own a MOTO phone, like from the days of MOTO G4 play. But I went for Xiaomi redmi 1s (I have to use it until I fix or buy a new phone).
Even I stated looking for a new phone. My budget is similar as you and all I can see are Samsung phones of which I am not a fan, TBH! Well Nokia was good, but not in the competition anymore.
You know about Motorola, I heard that.. since it is now owned by Lenovo, the quality of the phones aren't as good as it was before (I think, now, i am starting to believe that). My personal opinion is that I don't want to think about Motorola anymore because this phone has given me a headache!
[At this point I think is not even a software problem, but I'm getting the idea that something definitely fried on the inside. Which would probably cost more to repair than to get a new phone
Click to expand...
Click to collapse
Oh yes, the repair cost! But, I think, once they mess up with the insides of the phone, we cannot guarantee that it'll survive for long. I am afraid that after the repair, it might die without giving me a chance to save my personal data!

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.