Database Develop

No OTAs on AT&T XT1058

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Removed. I guess post was not appreciated.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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!

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.