Database Develop

HTC One Looks Dead/Bricked - What to do next

*** SOLVED - Problem was my own stupidity ***
Got the HTC One a couple of days ago. Came back to Android after a few months on iPhone. Figured I'd jump right back into rooting and flashing custom ROMs.
Anyway, unlocked the phone, wanted to install Android Revolution 51, tried to upgrade firmware, and that's when things went sideways. Now, I can't do anything. Can Fastboot, but can't ADB. Have tried to load every driver in the book, but to no avail. CID is CWS_001 if that helps. Have been at this for a day and a half now. I need ideas.
thoughts?

Does it get detected on your window device manager when you plug it in?
sent from my mobile device

SaHiLzZ said:
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
Click to expand...
Click to collapse
Yes. It shows up under Android USB Devices and says "My HTC"

diceman725 said:
Yes. It shows up under Android USB Devices and says "My HTC"
Click to expand...
Click to collapse
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...

Iz3man said:
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Click to expand...
Click to collapse
Would be very grateful. I agree, it would seem logical that I could ADB my way out, but at the moment, ADB doesn't recognize the device.

It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2

Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I don't have a ROM loaded in the Virtual SD. And unless I'm mistaken, I can really only use ADB sideload at this point to load one up

Can you get into basic HTC recovery on the phone? I'm assuming you can if you can get fastboot working.
If so can't you just reflash a actual recovery from there, and then a rom from that? Apologies if this is completely irrelevant, I base all my android knowledge off my Desire.
Sent from my HTC Desire using Tapatalk 2

Adb reboot
sent from my mobile device

Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.

Iz3man said:
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Click to expand...
Click to collapse
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.

diceman725 said:
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
Click to expand...
Click to collapse
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!

Iz3man said:
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Click to expand...
Click to collapse
I can get into recovery, yes...

If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device

SaHiLzZ said:
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
Click to expand...
Click to collapse
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.

diceman725 said:
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
Click to expand...
Click to collapse
No luck on flashing the RUU file. It sends successfully, but fails on the write.

You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device

also nearly bricked
..

Please make a new thread.
sent from my mobile device

SaHiLzZ said:
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Active cmdline overflow!

Hi, my dad just got a HTC One and tried to install a ROM but failed terribly by wiping everything that he possibly could, don't ask me how, and then he had me fix it because he couldn't. I sideloaded Android Revolution HD but got error 7 (old recovery) so I updated the recovery and that's where the problems started, I got the error 'Active cmdline overflow!' which I couldn't find a solution to, I installed an older recovery and it worked fine so it turns out that I can't install any recoveries capable of KitKat ROMs without getting that problem that prevents me from booting or getting to recovery. I restored using an RUU which didn't fix much; I can't update the stock ROM without getting a boot loop and if I try to change the kernel so I can S-OFF I get 'Active cmdline overflow!' again!! Now I'm stuck in bootloader because I can't flash any kernels Can anyone help me please?
Getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3B2W900221
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance Sorry if I got anything wrong this is my first post in a very, very long time

Please provide specific versions of recovery that works and the version that results in active cmdline overflow.

cschmitt said:
Please provide specific versions of recovery that works and the version that results in active cmdline overflow.
Click to expand...
Click to collapse
CWM - 6.0.4.5+ causes the error I think
TWRP - 2.6.3.3+ causes the error
All others seem to be fine

Jak3Mac said:
CWM - 6.0.4.5+ causes the error I thing
TWRP - 2.6.3.3+ causes the error
All others seem to be fine
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2708134

cschmitt said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2708134
Click to expand...
Click to collapse
No, it's the LTE version of the phone so that recovery won't work

Jak3Mac said:
No, it's the LTE version of the phone so that recovery won't work
Click to expand...
Click to collapse
??? It's for m7_ul, which is your phone.

cschmitt said:
??? It's for m7_ul, which is your phone.
Click to expand...
Click to collapse
I'm sorry, I don't know what's wrong with me :laugh: I'll give it a try when I get up, it's 3:30 am so I'm ready to sleep but I'll need to find and flash the stock kernel first because the current kernel is causing the issue at the moment and this prevents me from getting to recovery

cschmitt said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2708134
Click to expand...
Click to collapse
I tried this, it doesn't work. Same issue: "Active cmdline overflow! (1025 Bytes)"

Jak3Mac said:
I tried this, it doesn't work. Same issue: "Active cmdline overflow! (1025 Bytes)"
Click to expand...
Click to collapse
Thanks for giving it a try. So as soon as you return to a pre-2.6.3.3 TWRP the error no longer appears in hboot screen?
We seen this error in various cases and trying to nail down the exact cause.
FYI, Some have had luck with downgrading to a pre-1.54.000 hboot.

cschmitt said:
Thanks for giving it a try. So as soon as you return to a pre-2.6.3.3 TWRP the error no longer appears in hboot screen?
We seen this error in various cases and trying to nail down the exact cause.
FYI, Some have had luck with downgrading to a pre-1.54.000 hboot.
Click to expand...
Click to collapse
Yes that's right, it's very odd. I'm going to try and flash the Viper ROM using 4.2.2 and see if I can S-OFF, then I'll write super CID and downgrade hboot.
***Update***
I flashed the venom ROM but when using Rum Runner I'm getting a lot of pours so I don't think it's going to work

Jak3Mac said:
Yes that's right, it's very odd. I'm going to try and flash the Viper ROM using 4.2.2 and see if I can S-OFF, then I'll write super CID and downgrade hboot.
Click to expand...
Click to collapse
Here's hboot 1.54.0000 Aug 19, 2013 from GPE 3.07.1700.1. There are several 1.54.0000 hboots with different production dates, but the Aug 19 version is the last one to not include the 'Active cmdline overflow' code, so it should work for you once you are s-off.
firmware_3.07.1700.1.zip

cschmitt said:
Here's hboot 1.54.0000 Aug 19, 2013 from GPE 3.07.1700.1. There are several 1.54.0000 hboots with different production dates, but the Aug 19 version is the last one to not include the 'Active cmdline overflow' code, so it should work for you once you are s-off.
firmware_3.07.1700.1.zip
Click to expand...
Click to collapse
Thanks for all your help, could you help me out with S-OFF? I'm getting infinite pours but there's not much I can do about it, I can't flash kernels or flash the current rom. Would stock recovery help?

Jak3Mac said:
Thanks for all your help, could you help me out with S-OFF? I'm getting infinite pours but there's not much I can do about it, I can't flash kernels or flash the current rom. Would stock recovery help?
Click to expand...
Click to collapse
You're trying to get a specific rom and kernel installed to s-off?
Assuming bootloader is unlocked, just pull the boot.img out of the kernel zip you want and 'fastboot flash boot boot.img'
For the rom, maybe find a nandroid backup of the \system partition for the rom you want and just restore it using the older twrp or cwm recovery. Might work.
Ask in the rom thread your trying to install, maybe someone will post a backup for you. Or search for the 'guru reset' thread, I think there are some nandroid backups there.

cschmitt said:
You're trying to get a specific rom and kernel installed to s-off?
Assuming bootloader is unlocked, just pull the boot.img out of the kernel zip you want and 'fastboot flash boot boot.img'
For the rom, maybe find a nandroid backup of the \system partition for the rom you want and just restore it using the older twrp or cwm recovery. Might work.
Ask in the rom thread your trying to install, maybe someone will post a backup for you. Or search for the 'guru reset' thread, I think there are some nandroid backups there.
Click to expand...
Click to collapse
Flashing any kernel triggers the active cmdline error
On the guru reset thread I found one from a phone with the CID vodap002 but mine's vodap001, it will still work though won't it? I'm downloading now, will update the post when I've restored it
***Edit***
I think the partitions are messed up :\ I can't mount cache in recovery which is one of the symptoms of this. Would re-flashing the firmware solve this issue? If I could find it, that is
***Edit 2***
CWM isn't picking up the nandroid I might have to give up on this one, I don't know what to do. I'll put a JB ROM on for now, that'll have to do

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.

Amazon Fire Bootloader unlock code??

So when i entered the fastboot getvar all command in adb
Heres what i got
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-sizeKB: 100000
(bootloader) partition-typeKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0xaXXXXXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.180s
Im wondering if the unlock code can be used to unlock it or its just the binary data on true or false.

@sd_shadow Your thoughts on this?

This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi

Ugh wish i had another kindle fire

sd_shadow said:
This maybe useful or maybe not.
Link for the kindle hdx 8.9
[DEV] Bootloader unlock procedure and software by @dpeddi
Click to expand...
Click to collapse
Apparently I just tried this with the one Getvar gave me it didnt work. gave me an unlock code error

I bought this fire for my son. The hdx unlock worked until 3.2.4 firmware and is based on a bug on image verification. Probably we can't unlock any more the bootloader..both on newer HDx and on this cheap fire.

@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?

rjmxtech said:
@sd_shadow So what's the status on the bootloader unlock? Anything us common users can do to help?
Would making a petition online to Amazon help our cause? Or maybe get @geohot involved if possible?
Click to expand...
Click to collapse
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...

ldeveraux said:
Dude can you layoff for a bit? You're saying the same things in every thread. The bootloader isn't unlocked, most likely won't be. Amazon won't break for a petition, and geohot works for google. Be patient, the constant hounding doesn't make it work faster...
Click to expand...
Click to collapse
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.

rjmxtech said:
Um, this is one of the only threads I have posted this in. Calm yourself. I am just trying to see what I can do. Trying to do things is better than sitting and doing nothing and waiting for others to do them for you.
Click to expand...
Click to collapse
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens

ldeveraux said:
look, I get it, you really want the bl unlocked. You posted in 3 threads about it, one had to be cleaned. But unless you know anything about the process, there's nothing to help with. I'm not discouraging, it's just the way it is. Let those in the know alone, leave them to their work. Trust me, you won't miss anything if it happens
Click to expand...
Click to collapse
That one I posted in the wrong place I changed to "nvm" when I realized I posted in the wrong place but I get what you're saying.

well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.

jwalb89 said:
well i bricked my fire today trying to install cm12:crying: seems the recovery img was corrupted some how so ill need the bl to be unlocked to flash a custom one. i have reached the limits of my knowledge, as limited as it may be. rooting for those of you that know what you are doing. thank you for the effort, even if it doesnt result in a fix.
Click to expand...
Click to collapse
What are the symptoms of your brick? Can you get to fastboot?

Drax TD said:
What are the symptoms of your brick? Can you get to fastboot?
Click to expand...
Click to collapse
I do have access to fastboot, but not to recovery as stated so no adb commands for me... on normal boot it goes to the cm12 boot logo, and continues attempting to boot.

Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk

Franzferdinan51 said:
Shouldn't he be able to recover if he gets boot image and fastboot?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk

sd_shadow said:
fastboot mode doesn't work with 5.1.1 bootloader
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk

Franzferdinan51 said:
Are you sure because I'm pretty sure I used fastboot to restore my tablet when it bricked though I could be wrong may have been adb side load
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.

jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Ahh well good luck can't wait too see what you come up with would love to have a real recovery instead of flash fire
Sent from my KFFOWI using Tapatalk

jwalb89 said:
fastboot will not work to flash any thing as the bootloader is locked. my hope right now it to create a valid update.zip from the stock firmware, and use fastboot update. some one is making a full stock backup for me right now. maybe between that and the original firmware .bin i can make it happen. not exactly sure how to do it, as ive never had to do it before. i will give it a shot though.
Click to expand...
Click to collapse
Any luck getting a update.zip that can restore stock using fastboot?
Thanks

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