AT&T XT1058 - Stuck on 4.2.2 - Moto X Q&A

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.

Related

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

No OTAs on AT&T XT1058

Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.
Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.
nhizzat said:
Flashing a ROM will not lock your bootloader.
You can only flash same firmware versions or newer, never downgrade.
Yes you can flash the stock Rogers firmware. You can find it in the going back to stock guide.
Click to expand...
Click to collapse
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?
RafaySid said:
Thanks. Sorry for bothering but I meant SIM locking. Will flashing a ROM SIM lock my phone again or is the answer still the same?
Click to expand...
Click to collapse
It will not SIM lock your phone.
RafaySid said:
Secondly, how would I know which is the stock ROM for me? It says XT1058 and 'Assembled in China' on the back, so maybe it's from some Latin American country. Should I still go for the Rogers ROM because it's bloat-free?
Click to expand...
Click to collapse
Since your phone has already been Bootloader unlocked (because the ROM in your phone is not stock right now), it doesn't matter which ROM you choose. I'd say choosing a bloat-free ROM is great!
RafaySid said:
Hi, I just bought a used Moto X (2013). There is no carrier branding on the back and it's written Xt1058 but the ROM installed is of AT&T. When I installed WhatsApp, it said that my phone has a 'custom ROM' and that some features won't work, but otherwise the phone is working just fine. Due to this ROM I'm not getting OTAs as well and I'm stuck on 4.2.2 Jellybean.
My question is that can I flash any other ROM on the phone so that I start receiving OTAs and while making sure that my phone remains unlocked? I don't want to end up locking my phone again. Can flashing a new ROM lock my phone again? Can I revert to stock ROM somehow (maybe the set isn't originally of AT&T)? Or can I flash Rogers ROM which also of XT1058?
In need of help. Thanks.
Click to expand...
Click to collapse
First you need to know if your bootloader is unlocked or locked.
Boot the phone into Fastboot/Bootloader mode. What does it say for the status? And what is the version from the 2nd line.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.
KidJoe said:
First you need to know if your bootloader is unlocked or locked.
Next, while the phone is in bootloader mode, hook it to the PC and do a fastboot getvar all and post what it says for the following...
(bootloader) version-bootloader:
(bootloader) revision-hardware:
(bootloader) unlocked:
(bootloader) sku:
(bootloader) cid:
(bootloader) ro.build.id:
(bootloader) ro.build.fingerprint[0]:
(bootloader) ro.build.fingerprint[1]:
(bootloader) ro.build.version.full[0]:
(bootloader) ro.build.version.full[1]:
(or copy/paste the entire output into a post and I'll pick it out).
If the bootloader is locked, you'll only be able to flash Stock ROMs signed by Moto, and made for the same "(bootloader) cid:" as your phone.
Flashing a ROM will not lock a bootloader that has been unlocked. The only time I've seen flashing a ROM re-sim lock is the Sprint XT1056 where a hack is used to sim unlock it.
Btw, ATT phones usually have the ATT carrier branding on the case, even if it was from Moto Maker.
Click to expand...
Click to collapse
2nd line: 30.70 (sha-88483d6, 2013-07-02 15:32:03)
.
.
.
.
Device is UNLOCKED. Status Code: 1
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Farooq>cd/
C:\>cd android
C:\Android>fastboot getvar all
(bootloader) version-bootloader: 3070
(bootloader) version: 0.5
(bootloader) cpu: MSM8960 Pro CS
(bootloader) ram: 2048MB Hynix S4 SDRAM DIE=4Gb
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) product: ghost
(bootloader) revision-hardware: 0x8300
(bootloader) radio: 0x1
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) serialno: TA1760BS0H
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 805306368
(bootloader) uid: EF8D10040C000100000000000000
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) sku: 000000000000000
(bootloader) cid: 0xdead
(bootloader) iccid:
(bootloader) date: 01-01-1970
(bootloader) cust_md5:
(bootloader) reason: Key pressed
(bootloader) ro.build.date: Fri Jul 12 11:37:14 CDT 2013
(bootloader) ro.build.id: 13.9.0Q2.X_140
(bootloader) ro.build.tags: intcfg,test-keys
(bootloader) ro.build.type: userdebug
(bootloader) ro.build.user: e13522
(bootloader) ro.build.version.codename: REL
(bootloader) ro.build.version.incremental: 23546373
(bootloader) ro.build.version.release: 4.2.2
(bootloader) ro.mot.build.customerid: att
(bootloader) ro.product.name: ghost_att
(bootloader) ro.build.fingerprint[0]: motorola/ghost_att/ghost:4.2.2/1
(bootloader) ro.build.fingerprint[1]: 3.9.0Q2.X_140/23546373:userdebug
(bootloader) ro.build.fingerprint[2]: /intcfg,test-keys
(bootloader) ro.build.version.full[0]: Blur_Version.13.0.23546373.ghost
(bootloader) ro.build.version.full[1]: _att.ATT.en.US
(bootloader) kernel.version[0]: Linux version 3.4.42-xline-eng-g
(bootloader) kernel.version[1]: 66c71d4 ([email protected])
(bootloader) kernel.version[2]: (gcc version 4.6.x-google 201201
(bootloader) kernel.version[3]: 06 (prerelease) (GCC) ) #1 SMP P
(bootloader) kernel.version[4]: REEMPT Fri Jul 12 11:55:44 CDT 2
(bootloader) kernel.version[5]: 013
all:
finished. total time: 0.122s
C:\Android>
A few things..
With Bootloader of 30.70, that is the initial shipping bootloader. Based on the versions, it appears to also been the initial shipping ATT ROM. (i.e. the previous owner did not flash only PARTS of a ROM).
Unlocked Status 1 is good. You should be able to flash signed and unsigned roms. So if you want to switch to CM or such, you can. And you can flash 3rd party recovery and root too.
A few things that concern me from the fastboot output...
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
I've only seen it say YES or NO for those. This is the first I've seen "Not Supported"
(bootloader) cid: 0xdead
I've not seen the CID listed as DEAD before. Its always been a hex value.
And I'm hoping you just removed your imei and meid, and not that they are actually missing from the output.
One last thing I missed in your other posts, that it says XT1058 on the back and MADE IN CHINA. The ATT XT1058's all said made in USA if I'm not mistaken. So chances are best that its NOT an ATT XT1058.
What carrier are you using this phone on? Do they sell the XT1058? If so, consider finding the latest XT1058 SBF for that carrier and flashing it.
RISKS of doing that: It might fail and brick your phone in the process. It might be successful but you end up having no IMEI/MEID in the process. You end up in a state where you have that SBF on there, but improper carrier settings so future OTA's fail and you have to flash them manually. Or Best case.... It works, and those variables go back to "normal" values.
Its your call if you want to take the chance.
Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?
RafaySid said:
Thanks for the kind reply, I really appreciate it.
I asked Motorola's support person on live chat and he said that the previous owner most probably damaged the phone while flashing as it is not showing any IMEI number. I think the previous guy most probably flashed an AT&T ROM on it and this phone is likely to be from Latin America (XT1058). I'm interested in flashing Roger's ROM as it is bloat-free. I won't flash KitKat on it since it has battery draining issues and will wait for Lollipop.
Click to expand...
Click to collapse
Yes, definitely caused while screwing around and doing something that shouldn't have been done.
So the IMEI is definitely missing? I would think in that case you wont see the mobile/cellular network and only Wifi would work. But you said other than the OTA's the phone was working fine.
There were some threads about some getting into that situation (Missing IMEI). I know there were some XT1052 users trying to flash Non-XT1052 roms and running into this, but being unable to recovery. I think there was some users who ran into it for other reasons and were able to recover. Its time to start searching. Like -> http://forum.xda-developers.com/moto-x/moto-x-qa/cdn-rogers-1058-fr-4-4-2-update-to-4-4-t2842787
RafaySid said:
But are the..
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) cid: 0xdead
..things to be worried about? Will I most probably end up bricking it?
Click to expand...
Click to collapse
As I've said, the "Not Supported" and "0xdead" values do worry me. I've not seen them before, so I can't tell you what impact they have on flashing. That is why I said bricking was a risk and that its your choice what to do.
At this point, if you have a working phone, keep with it and using it. Or you try and flash a Rogers XT1058 SBF, taking the chance of bricking it in the process. If you take this route, use Option 5 (and its pre-req's) at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html Get roms from places in this thread -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
I would really suggest flashing the LATEST SBF, in this case 4.4.4.
As for the "battery drain" reported under 4.4.4, for me anyway it seems to vary depending on installed apps. I can still get more than a day with my XT1060 running 4.4.4 with all google and moto apps updated. Occasionally after a bunch of apps update, I see less battery life, but then it seems to settle down and go back to normal.
If you want to flash Rogers 4.4.4, per this thread -> http://forum.xda-developers.com/mot...rogers-canada-4-4-4-sbf-t2905525/post56055157 it appears to be XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip BUT I HAVE NOT CONFIRMED THIS SO PROCEED WITH CAUTION!!!
Good Luck!!
The cellular network is working fine. Can I at least root it? Which method should I choose?
RafaySid said:
The cellular network is working fine. Can I at least root it? Which method should I choose?
Click to expand...
Click to collapse
First, find a copy of the SBF for the rom on your phone before you do anything.
Since you have an unlocked bootloader, just follow -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738
Because you have an older rom and bootloader, just use the versions linked in there. If you ever update the ROM on your phone, you would want to consider using newer versions of TWRP and SuperSU
In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.
In order to root, you need to read. Seriously, just read and you'll have your answer.
I'm being 'extra careful' because of those abnormal values.
Sent from my Moto X using Tapatalk
RafaySid said:
In order to root, do I need a custom recovery? I'm at 4.2.2 Jellybean atm.
Click to expand...
Click to collapse
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.
KidJoe said:
There are two ways to root one is for LOCKED bootloaders, the other is if your bootloader is UNLOCKED.
Unlocked bootloader is done by flashing a custom recovery like TWRP, rebooting to bootloader (so the recovery sticks), entering the recovery, and TWRP will usually ask you if you want to root so you answer yes. (sometimes manually installing SuperSU from TWRP is needed). This both roots and disables write protection.
For a LOCKED bootloader you are exploiting vulnerabilities in the roms. You need to be on a certain rom for it to work, there are extra hacks needed to disable write protection. Its a complicated process that sometimes requires flashing different roms. (I don't remember back to the original shipping 4.2.2 for locked bootloader process, I think it might be PwnMyMoto??).
Because of those values on your phone, any flashing or hacking could be risky. Doing the unlocked method (thread link I pasted earlier) of flashing twrp, is the easiest way to root.
Unless you are willing to take a chance, and risk bricking your phone, I'm not sure how to really advise you because everything at this point is unknown territory.
Click to expand...
Click to collapse
Yes thank you. I had already rooted using TWRP.
Can I install an offline update instead of flashing, to update 4.2.2?
Sent from my Moto X using Tapatalk
These 2 threads have everything you need to know,
Rooting,
http://forum.xda-developers.com/showthread.php?t=2826159
Flashing firmware, (returning to stock section)
http://forum.xda-developers.com/showthread.php?t=2603358
I'm not sure what you are meaning by "offline" update... But how to update manually is covered in above thread. ?
Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk
RafaySid said:
Yeah I meant manually updating. Thanks.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
there are two types of Update.
OTA update (they are incremental, only flash what changed since the last version, need to be stock recovery, and rest of phone as close to stock as possible. and you'll need a certain version on your phone)
Flashing a full SBF (as explained earlier when I mentioned about possibly flashing the Rogers XT1058 rom, and pointed you towards using Option 5 and its pre-req's at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . It has a couple commands repeated which makes it a little more successful. )
Either way, in your situation, is risky.

[Q] 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

G7 Plus XT-1965-3 help please.

Guys,
I have the G7 plus XT19645-3 UK device, never been rooted or messed around with.
I had some issues with bluetooth not working with one particular car, so my neighbour 'upgraded' it to Android 10.
I was not happy with Android 10, so he then tried to revert t back to Android 9, which failed.
Currently, the phone boots, shows the Motorola logo, then the message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
I then have to restart it by holding the power button, I can get into fastboot using the volume down and power button, and it is recognised by fastboot devices.
Before I make the situation worse, can anyone show me how to get it back to ANY version of Android so I can use the phone please.
I have tried reading through the various posts on here, but quite frankly I am confused as which to follow.
Any help most gratefully received.
I see 2 options:
First option is to try download and use the Rescue and smart assistant (formerly the lenovo moto smart assistant) to recover the device. It easy to use with an user friendly interface
Second option is since you can boot into fastboot, than you just need to download a rom for the device and flash it. You can download the stock rom from lolinet (Here's the android 9 for reteu devices: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) and then flash it manually via cmd or use the blankflash script thats laying somewhere here in the xda treads for the phone
Hi Teo S, thank you for coming back to my request, I have tried smart assistant, it failed with an error something like 'key information could not be read from your device'.
I then tried using the flashfile.bat script, using the rome you linked to above, and the Android 10 rom from Olinet.
The Android 9 failed, with two errors related to' system_b system_b.img_sparsechunk.0' and 'system_b system_b.img_sparsechunk.1'.
The Android 10 rom flashed successfully as far as I can tell looking at the messages in the cmd window all commands finish with 'OKAY'.
However, when I reboot the device, I still get the Motorola logo, which flashes on and off a few times, then get the same message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
So although it looked like it had flashed correctly, something is still not right, can you suggest anything else?
A further bit of info, I left the phone for about 10 minutes with the message 'Verity mode is set to eio' and the Motorola logo, when I came back to it, that screen had gone, and was replaced with a black screen with yellow and red text, essentially it said 'Boot Failed', followed by red text about how to contact customer service and if it is a Verizon device (which is is not), but below that was more yellow text which said 'No Bootable A/B slot', 'failed to boot Linux, falling back to fastboot'
staffstony said:
was not happy with Android 10, so he then tried to revert t back to Android 9, which failed.
Currently, the phone boots, shows the Motorola logo, then the message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
Click to expand...
Click to collapse
staffstony said:
Hi Teo S, thank you for coming back to my request, I have tried smart assistant, it failed with an error something like 'key information could not be read from your device'.
I then tried using the flashfile.bat script, using the rome you linked to above, and the Android 10 rom from Olinet.
The Android 9 failed, with two errors related to' system_b system_b.img_sparsechunk.0' and 'system_b system_b.img_sparsechunk.1'.
The Android 10 rom flashed successfully as far as I can tell looking at the messages in the cmd window all commands finish with 'OKAY'.
However, when I reboot the device, I still get the Motorola logo, which flashes on and off a few times, then get the same message 'Your device is corrupt, it cannot be trusted and may not work properly', then, it displays 'Verity mode is set to eio'.
So although it looked like it had flashed correctly, something is still not right, can you suggest anything else?
Click to expand...
Click to collapse
So it sounds like you unlocked the bootloader before doing all of this? Please confirm. Not sure if you could still request unlock code if you don't have it yet.
Also, did you reset the device?
Could you dump all fastboot variables, and post them here ( fastboot getvar all ).
Notice that XDA upgrade scripts for flashing are often missing a step or two, due to them being for older versions. Extract "flashfile.xml" from you current ROM, and check line by line that everything is flashed and erased properly. It must be line for line exact!
I think your phone is totally recoverable, just need to follow the correct steps.
To be honest, my neighbour 'updgraded' my device from Android 9 to 10 so I am not sure if he unlocked the bootloader or not.
I have the unlock code though from Motorola in case it is required.
Here is the output from getvar all, i've replaced the device serial and IMEI with '*'.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9-200214
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: WEJP
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: **********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: B429986C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 07-11-2019
(bootloader) sku: XT1965-3
(bootloader) carrier_sku: XT1965-3
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 3773
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_reteu_n/lake_n:10/QP
(bootloader) ro.build.fingerprint[1]: WS30.61-21-9/664a:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 10 06:08:41 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9-200214
(bootloader) git:xbl: MBM-3.0-lake_retail-923e768-200214
(bootloader) gitmic: MBM-3.0-lake_retail-923e768-200214
(bootloader) git:rpm: MBM-3.0-lake_retail-50d7845-dirty-200214
(bootloader) git:tz: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:hyp: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:devcfg: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:cmnlib: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:keymaster: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) gitrov: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) git:storsec: MBM-3.0-lake_retail-79dd9bc-dirty-200214
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
I am unsure exactly which rom I should be looking at the flashfile.xml, Android 9 or 10?
The device is a UK G7 Plus, purchased from a UK national company.
Really apreciate any help you can give, i'm kinda stuck without my phone!!
staffstony said:
...
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
...
(bootloader) sku: XT1965-3
(bootloader) carrier_sku: XT1965-3
...
(bootloader) ro.build.fingerprint[1]: WS30.61-21-9/664a:user/release-key
...
(bootloader) ro.carrier: retgb
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
I am unsure exactly which rom I should be looking at the flashfile.xml, Android 9 or 10?
The device is a UK G7 Plus, purchased from a UK national company.
Really apreciate any help you can give, i'm kinda stuck without my phone!!
Click to expand...
Click to collapse
OK, things seem fairly clear now. It's still locked (iswarrantyvoid: no).
You may want to try first to switch the bootloader slot to a (fastboot --set-active=a). And reboot to fastboot, do getvar all again. Compare which version it is in slot A now, is it still 9 or 10 already. Your version B has some older 10, compared to Lolinet. Also, try Moto recovery software from both slots, just in case. Sounds like you already tried from B, now switch to A and try again. Your locked phone should be detected somehow. That software is exactly for issues like yours!
If neither A/B work, I am not sure if you can flash the full 9 or 10 to the locked device.
Your fastboot says GB channel, XT1965-3, so either of these 2 ROMs could work for you, 9 or 10:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Either zip will have flashfile.xml, so you can try 9 first, then 10. For each version follow its respective flashfile.xml for the exact files. It won't let you flash things that cannot be downgraded, so don't worry about trying it.
Anyway, if you are unable to flash with the locked BL, unlock it, flash 9 or 10, then boot to verity, and relock it if you care.
Update: read up here
https://www.reddit.com/r/AndroidQuestions/comments/in2zga
I say use the official procedures first, do not unlock yet.
In another place, if you google for 'Verity mode is set to eio', it says this:
I didn’t succeed. I returned the customer without repair. I believe it is a memory or processor failure.
Update2: It seems you actually cannot go back to 9, and must stick to 10 to avoid the EIO issue. It checks for roll back, and 9 after 10 is a rollback, which means - it thinks it's been tampered with. So do reload 10 back:
Verifying Boot | Android Open Source Project
source.android.com
bibikalka, thank you for the reply, lots of info for me to digest there.​I have just tried to switch to slot a, for some reason that didn't work, this is what I got.
D:\fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.003s
So I guess I have fallen at the first hurdle..
Ok, I have made some progress, I downloaded the RetailGB rom for Android 10 that you linked to, then unzipped it and looked at the flashfile.xml.
I then compared the contents to the flashfile.bat I had downloaded.
They were almost exactly the same except the flashfile.bat was missing this line from flashfile.xml
<step MD5="b3a54937c84fb5f3e7f71fc019c11c78" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
So I modified the flashfile.bat to include the line
mfastboot flash system system.img_sparsechunk.5
And tried again, and it worked perfectly, after rebooting, the phone booted up normally with the Motorola logo and then went through the setting up menus.
I popped my sim back in and it registered on the network
Before I go ahead and re-install all my apps / data, is there any point in rooting it, and if so how do I do that, i'd like to get it in a state where should anything happen again, I can be in a better position to recover it.
Thank you for the help and assistance in getting me back up and running.
staffstony said:
They were almost exactly the same except the flashfile.bat was missing this line from flashfile.xml
<step MD5="b3a54937c84fb5f3e7f71fc019c11c78" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
So I modified the flashfile.bat to include the line
mfastboot flash system system.img_sparsechunk.5
And tried again, and it worked perfectly, after rebooting, the phone booted up normally with the Motorola logo and then went through the setting up menus.
I popped my sim back in and it registered on the network
Before I go ahead and re-install all my apps / data, is there any point in rooting it, and if so how do I do that, i'd like to get it in a state where should anything happen again, I can be in a better position to recover it.
Click to expand...
Click to collapse
OK, so it looks like you were missing a chunk of the /system - no wonder it did not work before ...
Unlock can be useful, or may be a nuisance. Decide for yourself. Is it out of warranty now? If so, you won't lose anything by unlocking. Before unlocking, you'd install all the OS updates that are being offered. It will be more difficult to do it later. With unlock/root you get :
TWRP
Magisk
Titanium Backup
Other ROMs if you fancy those
But some apps seem to refuse to run if they detect a rooted device
Tethering (if you want to bypass the carrier restrictions)
Other little things
If you don't care about any of this, stay locked.
@bibikalka, I think I would like to root the device, mainly so I can use Titanium to back it all up.​That said, having read this thread ​
[RECOVERY] Official TWRP 3.3.1 for Moto G7 Plus [lake]
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
​I am not sure, the info in there is a bit confusing, how simple is it to do?
I have downloaded the relevant TWRP .zip and .img, downloaded the magisk .apk file for the G7 Plus, the device dows not yet have any apps installed, so wiping it is no problem either, there is no data on it that I am not prepred to lose.
The phone is out of warranty anyway, I have the bootloader unlock code from Motorola, so I guess I have everything required, just need a hand hold to actually do the unlock.

Categories

Resources