Database Users

Moto X Style (DS) XT1572 bootloader unlocking issue....

hi guys. i have moto x style dualsim XT1572 variant. attempting to unlock its bootloader to further install twrp and custom roms. upon performing the get_unlock_data step i m getting error. i have already enable oem unlocking and usb debugging in developer option. dont know whats wrong ..... one thing i noticed that "Device is Engineering" is mentioned in bootloader details. can i install/flash TWRP without bootloader unlocking ?

Try this https://forum.xda-developers.com/mo...l-windroid-universal-android-toolkit-t3206883

aakashverma0007 said:
Try this https://forum.xda-developers.com/mo...l-windroid-universal-android-toolkit-t3206883
Click to expand...
Click to collapse
not working. the tool booted into bootloader without any issue. upon clicking get unlock key the tool start working and then suddenly an error appears and it crashes.

mkhurram0023 said:
hi guys. i have moto x style dualsim XT1572 variant. attempting to unlock its bootloader to further install twrp and custom roms. upon performing the get_unlock_data step i m getting error. i have already enable oem unlocking and usb debugging in developer option. dont know whats wrong ..... one thing i noticed that "Device is Engineering" is mentioned in bootloader details. can i install/flash TWRP without bootloader unlocking ?
Click to expand...
Click to collapse
So you enter
Code:
fastboot oem get_unlock_data
And you are getting an error? Can you screenshot the error (clearly) or copy and paste the terminal session?
Going to be honest, unless you are doing something incorrectly, there is little we can do... Motorola does have an official forum area for bootloader unlock issues on their support site, although it is a tough to get a response sometimes but this whole mechanism is pretty well locked down to the point that unless it's user error there isn't much we can do.

i am getting below things when i enter "fastboot oem get_unlock_data"
c:\adb>fastboot oem get_unlock_data
. . .
(bootloader) Failed to get unlock data, please try again !
FAILED (remote failure)
finished. total time : 0.013s
c:\adb>
i m unable to post screenshots as i m new use on this forum.

mkhurram0023 said:
i am getting below things when i enter "fastboot oem get_unlock_data"
c:\adb>fastboot oem get_unlock_data
. . .
(bootloader) Failed to get unlock data, please try again !
FAILED (remote failure)
finished. total time : 0.013s
c:\adb>
i m unable to post screenshots as i m new use on this forum.
Click to expand...
Click to collapse
That's fine... Can you copy and paste output of
fastboot getvar all
And mask out your IMEI number (but verify its there), please.

C:\adb>fastboot devices
NX7C3A0096 fastboot
C:\adb>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.010s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=01 TYPE=57 PNM=BGND3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: NX7C3A0096
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: 5C2725001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 2 12:18:43 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retla_ds/clark_ds:6
(bootloader) ro.build.fingerprint[1]: .0/MPHS24.49-18-8/4:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.8.clark_retla
(bootloader) ro.build.version.full[1]: _ds.retla.en.01
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02p CLARK_LATAM
(bootloader) version-baseband[1]: _DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g2c916d9 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Fri Sep 23 04:52:36 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.235s
C:\adb>

mkhurram0023 said:
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1 <-- This is the "Bootloader State"
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
Click to expand...
Click to collapse
Here is your problem in bold above... You device has been reflashed by engineering (ie. Motorola repair/support) and not placed back into a production state, it is in Engineering mode. There is nothing you can do, you should contact Motorola support. We have seen this in the Moto G much more than the X, but it definitely happens sometimes. Most of the time customer service won't know what you are talking about and you will have to go to the Lenovo forums, post about it and wait for a Moto support engineer to respond.
The Bootloader State (mot_sst) should be 0, 2, or 3... never 1... 0 means LOCKED, 2 means RELOCKED (was unlocked, but relocked with 'oem lock' procedure), and 3 means UNLOCKED. A value of 1 means Engineering, and that should never be seen in a production device.
Also, that bootloader date and sku looks messed up (unless you masked that as well), I don't recall seeing other engineering state devices with that. There are some other weird parameters that make me think this device has had problems before too, but they are not as important as what I noted above.
There is nothing you can do, you need to either leave it as is... assuming it is operating normally, or contact Motorola/Lenovo to correct the issue.
EDIT: See this thread for more information: https://forums.lenovo.com/t5/MOTORO...g-and-Unlocked-bootloader-status/td-p/3420219

Moto G4 plus stuck in bootloader mode (Hard Brick)

Hi All.
I have unlock boot-loader and flash stock ROM after that i got an update (nougat 7.1) and I allowed.
after allowing my mobile stuck in bootloader and i am not able flash new images getting:
FAILED (remote failure)
finished. total time: 0.144s,
i tried all possible way.
for hard brick i followed https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but no success. please help me out.

If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.

echo92 said:
If you're able to boot into the bootloader, then you're not hard bricked (fortunately).
What output do you get if you have your device in fastboot mode, then type 'fastboot getvar all' into the ADB terminal, then press enter?
If you can, use a different USB port and/or USB data cable.
Also, which firmware were you on? There is no 7.1 update for stock firmware, only 7.0 for Nougat or 8.1 for Oreo.
Click to expand...
Click to collapse
Below is the output of fastboot getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(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: MSM8952
(bootloader) serialno: d72acc4e
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: EC1CEC0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(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) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.104s
and i flash nougat 7 then i got update, I allowed update and phone got stuck in bootloader.

What firmware are you trying to flash now? Looks like your main issue is that you do not have a GPT partition table on your device, so your device does not know what files to flash.
I would recommend downloading the Oreo firmware from here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip delete the old stock ROM files from your ADB folder and replace with the Oreo firmware files. Then try to flash the Oreo GPT file

Stuck on bootloader with NO OS and OEM_LOCKED -- (MOTOG4PLUS)
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!

viking_vikram said:
I am stuck on Bootloader with NO OS and OEM_LOCKED . The bootloader vers. it shows is
B1.06(*) (sha-0edfb0d, 2017-06-01 12:10:43)
When installing GPT.bin file it says FAILED TO INITIALISE PARTITION TABLE .
don't know what to do totally stuck .
Service Center was of no use .
PLS HELP ME OUT !!
SOS !!
Click to expand...
Click to collapse
What happened to your device before this?
Which GPT.bin are you trying to load up? Try the April 2018 GPT and bootloader https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI or the December 2018 GPT and bootloader: https://drive.google.com/open?id=1TlFPYf4y3MEARFUuHSNB5Ty0GD-SQua-
However, if your device continues to report GPT partition initialisation errors, it's possible your flash storage is damaged and may require a motherboard replacement.

Where can I get a motherboard replacement ?
will it finally solve my problem ?

viking_vikram said:
Where can I get a motherboard replacement ?
will it finally solve my problem ?
Click to expand...
Click to collapse
Probaly a service centre would be the best place to request a motherboard replacement. It may solve your issue, however, as your G4 Plus is out of warranty, a motherboard replacement is not cheap - I've seen quotes for 8000-1000 rupees. Thus, you may wish to look into buying a new device altogether.

Moto G7 (Soft brick?)

Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(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: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss

Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
and the fastboot details? its like, corrupted?

WoKoschekk said:
Try to flash the stock firmware. It must be signed and the same version as already installed.
Even if the bootloader is locked you can flash it.
Click to expand...
Click to collapse
Dont Work, Remove Error

Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?

WoKoschekk said:
Are you able to boot into TWRP via "fastboot boot twrp.img" ? Is there any fastboot command executable on your device?
Can you enter the stock recovery?
Click to expand...
Click to collapse
Nope, i cant go to the Stock Recovery, and the fastboot boot twrp.img dont work.

if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Or try RSDlite or any Motorola repair software...

WoKoschekk said:
if you can't run the following commands then maybe you will need a blankflash...
Just use the gpt.bin and bootloader.img files from your stock rom:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Gpt and bootloader don't installs, the remote error its back.

WoKoschekk said:
Or try RSDlite or any Motorola repair software...
Click to expand...
Click to collapse
i tried, the RSD, and not recognize the phone.

So, you can't do anything... I guess the only chance to fix your phone is a blank flash.
I'm sorry but I don't know how to do that.
It would be better for you to use the search function.
Good luck!!

GordinhoBr said:
Hi Guys, i have a moto g7 1962-4.
After flashed the lineage os rom, and installed wrong modules, i decided to install the Havoc Os, after that, my cellphone's restarted on the fastboot(secure) screen.
The oem_turns to lock, says oem_lock
and, i can't flash roms.
The error on start: failed to initialize partition table.
No Bootable A/B Slot, and failed to boot Linux, falling back to the fastboot.
here is my bootloader informations:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(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: MBM-2.1-river_retail-a5c9d71-190801
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
i can't flash nothing, Its giving me, ex:
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: 0.037s
Remote Failure.
Can someone help me? please angelllllllllllllss
Click to expand...
Click to collapse
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.

diegovmsouza said:
Got the same here brow. I've tried everything without success. I took the cell phone in the authorized service and they charged me incredible 840 reais to fix (the phone already costs 899 new in the store). In the G7 plus forum there is a topic talking about Blank Flash. I tried to do it but I need the singleimage.bin file for the G7 model, since there the file is for G7 plus and it doesn't fit. I didn't find this file anywhere on the internet so I tried to build mine. apparently needs to extract the booloader.img file and create from the extracted files the singleimage.bin file with a program called star. For now, assists cannot recover. I already put mue G7 in the drawer and bought an a50, because I believe that in a few months this blank flash file will appear on the internet and solve our case. anyway, good luck! and any news please let me know here! I will do the same.
Click to expand...
Click to collapse
send me you phone number.

Do you have access to Fastboot mode, right?

River blankflash is available on Tel$gram

HueyT said:
River blankflash is available on Tel$gram
Click to expand...
Click to collapse
On what now?

iamcubeman said:
On what now?
Click to expand...
Click to collapse
Telegram

Android does not start after flashing Lineage OS with Micro G

I have finally tried to install Lineage OS (Micro G Version) on the G7. When rebooting, I now get a message under the Lineage logo that says:
"Can't load Android system. You continue to get this message, a factory data reset and erase a device." Then I have the options to "Try again" or to do a "Factory data reset."
The bootloader is unlocked, and I followed the instructions on the Lineage OS website (cannot post the link) and made sure to sideload copy-partitions.zip. I verified all files I put on the phone by checking against their md5s etc.
Here is what I did on the terminal:
(In the code below I had to replace the prompt by "COMMAND LINE: " Otherwise, the system would not let me post the message.)
Code:
COMMAND LINE: ~/Downloads/Moto_G7$ adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
0xxxxxxxx1 device
COMMAND LINE: ~/Downloads/Moto_G7$ adb devices
List of devices attached
0xxxxxxxx1 device
COMMAND LINE: ~/Downloads/Moto_G7$ adb reboot bootloader
COMMAND LINE: ~/Downloads/Moto_G7$ fastboot devices
0xxxxxxxx1 fastboot
COMMAND LINE: ~/Downloads/Moto_G7$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-7dec2bb-190401
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 0xxxxxxxx1
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: Cxxxxxxxxxxxxxxxxxxxxxxxxxx0
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3xxxxxxxxxxxxx4
(bootloader) meid:
(bootloader) date: 04-11-2019
(bootloader) sku: XT1962-4
(bootloader) carrier_sku: XT1962-4
(bootloader) battid: Sxxxxxxxx8
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 4 13:45: 2 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/river/river:9/PPOS29.80-6
(bootloader) ro.build.fingerprint[1]: 1-2/b7f44:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.2.river.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-03800-89xx.0
(bootloader) version-baseband: M632_11.47.01.85R RIVER_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld30) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Mon Apr
(bootloader) kernel.version[3]: 1 21:43:55 CDT 2019
(bootloader) sbl1.git: MBM-2.1-river_retail-535b1da-190401
(bootloader) rpm.git: MBM-2.1-river_retail-adee4d9-190401
(bootloader) tz.git: MBM-2.1-river_retail-32db80b-dirty-190401
(bootloader) devcfg.git: MBM-2.1-river_retail-32db80b-dirty-190401
(bootloader) keymaster.git: MBM-2.1-river_retail-32db80b-dirty-190401
(bootloader) cmnlib.git: MBM-2.1-river_retail-32db80b-dirty-190401
(bootloader) cmnlib64.git: MBM-2.1-river_retail-32db80b-dirty-190401
(bootloader) prov.git: MBM-2.1-river_retail-32db80b-dirty-190401
(bootloader) aboot.git: MBM-2.1-river_retail-7dec2bb-190401
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.013s
COMMAND LINE: ~/Downloads/Moto_G7$ fastboot flash boot twrp-3.3.1-2-river.img
target reported max download size of 536870912 bytes
sending 'boot_a' (27096 KB)...
OKAY [ 0.821s]
writing 'boot_a'...
(bootloader) Image not signed or corrupt
OKAY [ 0.155s]
finished. total time: 0.976s
COMMAND LINE: ~/Downloads/Moto_G7$ fastboot boot twrp-3.3.1-2-river.img
downloading 'boot.img'...
OKAY [ 0.766s]
booting...
OKAY [ 0.782s]
finished. total time: 1.548s
COMMAND LINE: :~/Downloads/Moto_G7$ adb sideload copy-partitions.zip
Total xfer: 1.00x
COMMAND LINE: ~/Downloads/Moto_G7$ adb sideload lineage-16.0-20200220-microG-river.zip
Total xfer: 1.00x
COMMAND LINE: ~/Downloads/Moto_G7$ adb reboot
According to the Lineage OS website, I had to fastboot flash boot twrp-3.3.1-2-river.img, whereas most of the posts on the forum suggest to run the twrp image from the computer, i.e. to fastboot boot twrp-3.3.1-2-river.img. But I do not know if this has anything to do with my problem.
Of course, any help is greatly appreciated.
Best regards,
Bernbacher

PS: ADB still sees the device. It responds with its serial number and "unauthorized."

Sorry for not writing all this in the first post...
The phone responds to fastboot, too, and I can start twrp by typing
fastboot boot twrp-3.3.1-2-river.img

Hello friend it's perfectly normal if you're installing lineageOS,it is supposed to prompt for a factory reset then you'll Boot into the system, normally it takes 5minutes for the first boot,also check out my post ''how to flash Custom Roms on moto G7 river" in the Question and Answer Section.

This fixed it. Thanks a lot! I installed LinageOS on a different phone a couple of years ago, and I do not recall the prompt for the factory reset. I actually read your post before flashing, but I missed that point. Sorry...

Im in a chicken egg situation, please help!

So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
UPDATE: LMSA gives me two errors first "Failed to match the connected device.
Reconnect device, then try again."
second error: just stays in "wait for matching firmware, don't unplug your device"
(i put my stock folder in the LMSA download folder but just stays like i said
UPDATE 2: i forgot to mention it but when i get to the part of flashing that says "fastboot erase DDR" i got this error back:
>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.006s
UPDATE 3: trying to at least repair the wifi to pass the google wizard encountered the following problem doing some tutorial i read in another forum.
>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.220s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.223s
That means i dont have the system formated?
I dont know what to do anymore guys...

cowb0y said:
So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
Leave phone in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

Thanks
sd_shadow said:
Try LMSA's Flash Rescue option
Leave phone in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Gonna try, i will post the updates as soon as i can!

Update
sd_shadow said:
Try LMSA's Flash Rescue option
Leave phone in fastboot mode.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
"Failed to match the connected device.
Reconnect device, then try again."
The phone is connected and in fastboot mode.

UPDATE 4
cowb0y said:
So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
UPDATE: LMSA gives me two errors first "Failed to match the connected device.
Reconnect device, then try again."
second error: just stays in "wait for matching firmware, don't unplug your device"
(i put my stock folder in the LMSA download folder but just stays like i said
UPDATE 2: i forgot to mention it but when i get to the part of flashing that says "fastboot erase DDR" i got this error back:
>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.006s
UPDATE 3: trying to at least repair the wifi to pass the google wizard encountered the following problem doing some tutorial i read in another forum.
>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.220s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.223s
That means i dont have the system formated?
I dont know what to do anymore guys...
Click to expand...
Click to collapse
I attach a getvar all for you
>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY3232R25R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: B6D17C90
(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: IHAVEIMEIBUTICENSOREDIT
(bootloader) meid:
(bootloader) date: 12-05-2018
(bootloader) sku: XT1926-6
(bootloader) carrier_sku: XT1926-6
(bootloader) battid: SB18C208
(bootloader) battery-voltage: 4068
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-16/5555b:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.361.26.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf134223-0256
(bootloader) kernel.version[1]: 0-g4e158e0 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Thu Jan 2 01:06:09 CST
(bootloader) kernel.version[4]: 2020
(bootloader) git:abl: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) git:xbl: MBM-3.0-evert_retail-b872199-200102
(bootloader) gitmic: MBM-3.0-evert_retail-b872199-200102
(bootloader) git:rpm: MBM-3.0-evert_retail-718b013-200102
(bootloader) git:tz: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:hyp: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:devcfg: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:keymaster: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) gitrov: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:storsec: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
(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.203s

cowb0y said:
So i buy a new battery for my dead moto g6+, and encountered with the following problems.
Its a xt1926-6 Evert RETAR
1st: baseband not found, no wifi, and no signal, so i cant pass the google wizard setup
2st: Cant flash a stock firmware/rom cause i didnt have the usb depuration on, and no oem locked (cant turn on beacuse i cant access the phone, like i said in the 1st problem)
Recovery mode works.
Already tried: Flashing stock rom/firmware via ADB, flashing stock rom/firm via SD, bypassing google wizard (also i have the account, but no internet to login), reverse tethering to give the phone internet but didnt work too.
If anyone can give me help, i will aprecciate it, im so frustrated and been fighting with this phone for 4 days.
UPDATE: LMSA gives me two errors first "Failed to match the connected device.
Reconnect device, then try again."
second error: just stays in "wait for matching firmware, don't unplug your device"
(i put my stock folder in the LMSA download folder but just stays like i said
UPDATE 2: i forgot to mention it but when i get to the part of flashing that says "fastboot erase DDR" i got this error back:
>fastboot erase DDR
erasing 'DDR'...
(bootloader) Invalid partition name DDR
FAILED (remote failure)
finished. total time: 0.006s
UPDATE 3: trying to at least repair the wifi to pass the google wizard encountered the following problem doing some tutorial i read in another forum.
>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.220s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.223s
That means i dont have the system formated?
I dont know what to do anymore guys...
Click to expand...
Click to collapse
If your phone is currently flashed with the stock rom, the only way to fix bootloader lock would be to enter edl mode. That means hard bricking on purpose ?

reply
mrsiri said:
If your phone is currently flashed with the stock rom, the only way to fix bootloader lock would be to enter edl mode. That means hard bricking on purpose
Click to expand...
Click to collapse
can you explain to me how i can do that? also sorry for not replying on time,i have same internet issues.
Also i need all the help i can get, because my moto g4 is slowly dying, having ghost touchs, etc. i want to use the g6 +

actualization
So i found a nano sim to try on, and the phone didnt read it, its like i didnt put the sim.
Now im desperate, i tried to formate the phone via fastboot, got this message:
PS C:\Users\cowb0y\Desktop\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
OKAY [ 0.387s]
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.392s
i noticed that one partition is on raw format.
I dont know what to do anymore.

cowb0y said:
I attach a getvar all for you
>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY3232R25R
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1a
(bootloader) uid: B6D17C90
(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: IHAVEIMEIBUTICENSOREDIT
(bootloader) meid:
(bootloader) date: 12-05-2018
(bootloader) sku: XT1926-6
(bootloader) carrier_sku: XT1926-6
(bootloader) battid: SB18C208
(bootloader) battery-voltage: 4068
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-16/5555b:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.361.26.evert.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf134223-0256
(bootloader) kernel.version[1]: 0-g4e158e0 ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9.x 20150123 (prerelease) (GCC)
(bootloader) kernel.version[3]: ) #1 SMP PREEMPT Thu Jan 2 01:06:09 CST
(bootloader) kernel.version[4]: 2020
(bootloader) git:abl: MBM-3.0-evert_retail-8e93af8-200102
(bootloader) git:xbl: MBM-3.0-evert_retail-b872199-200102
(bootloader) gitmic: MBM-3.0-evert_retail-b872199-200102
(bootloader) git:rpm: MBM-3.0-evert_retail-718b013-200102
(bootloader) git:tz: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:hyp: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:devcfg: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:cmnlib64: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:keymaster: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) gitrov: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) git:storsec: MBM-3.0-evert_retail-763d5fe-200102
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retar
(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.203s
Click to expand...
Click to collapse
If you have access to a Window 7 or XP machine ?
you could try RSD Lite
Are you using this firmware?
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml

reply
sd_shadow said:
If you have access to a Window 7 or XP machine ?
you could try RSD Lite
Are you using this firmware?
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml
Click to expand...
Click to collapse
i think a got a netbook with w7 to try rsd lite, gonna try in a few hours and post the results.
No, im trying with the 116-11-16 versions https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-16_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml.zip (and the same but from 2019 date)
i will try with the version you handed me.

I give up
sd_shadow said:
If you have access to a Window 7 or XP machine ?
you could try RSD Lite
Are you using this firmware?
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAR/
XT1926-6_EVERT_RETAR_9.0_PPWS29.116-11-23_subsidy-DEFAULT_regulatory-XT1926-6-ARGENTINA_CFC.xml
Click to expand...
Click to collapse
Well i installed w7 to try rsd, but all i got is "failed to switch to fastboot" the phone is already in bootloader mode.
Also try to flash manually the version that you give me, but got error on at least 5/6 files, retry, and all good, but still the same problem.
I dont know what to do anymore, tomorrow i will take the device to a "technician" i dont have hope on this...