Develop Bugs

Help me flash this phone

Help me find compatible firmware to flash on fastboot my Moto G5 EU version 2/16GB
I try flash random clean stock 8.1 fw. But i have errorcant start system or enter recovery.
I cant start phone
Info from my phone is
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 625716AC00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: XXXXXX
(bootloader) meid:
(bootloader) date: 06-13-2017
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:40 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_22.29.02.69.01R CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.702s
C:\Program Files\Minimal ADB and Fastboot>
Any help will be apperciate. I really need this phone back to work. I want only flash clean stock 8.1.0 rom.
When i buyed this phone. But now i have semi brick.
Anyone here can help me?

Problem solved. I found newest 8.1.0 stock rom. I flashed and phone back to life.
Last problem what i have is i cant unlock bootloader.

Morricorne said:
Problem solved. I found newest 8.1.0 stock rom. I flashed and phone back to life.
Last problem what i have is i cant unlock bootloader.
Click to expand...
Click to collapse
Follow the process for unlocking on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sure usb debugging and oem unlock (if available) is enabled
Make sure the unlock string is correct and you have removed all spaces so its on one long single line as per instructions

TheFixItMan said:
Follow the process for unlocking on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Make sure usb debugging and oem unlock (if available) is enabled
Make sure the unlock string is correct and you have removed all spaces so its on one long single line as per instructions
Click to expand...
Click to collapse
This device is supported. But i have message This device isnt allowed to unlock bootloader. On Motorola site.
I follow every step on This guide
Still the same.
XT1676 EU 2/16 GB version here.
Stock Android 8.1.0 OPP28.85-19-4-2
This suck, cause i want try 64 os but os on This device. But cant

Morricorne said:
This device is supported. But i have message This device isnt allowed to unlock bootloader. On Motorola site.
I follow every step on This guide
Still the same.
XT1676 EU 2/16 GB version here.
Stock Android 8.1.0 OPP28.85-19-4-2
This suck, cause i want try 64 os but os on This device. But cant
Click to expand...
Click to collapse
Either the device is an amazon device or locked to a carrier which doesn't allow bootloader unlocking until the device is carrier unlocked (officially) or it has been previously unlocked in which case you would need to know the unlock code to unlock it again
If it has been registered before with Motorola you need to sign in using that email or try and unlink that address from the device (motorola device id option under settings)

https://imgur.com/cDPKjin
https://imgur.com/hblRtIU
Still no luck

TheFixItMan said:
Either the device is an amazon device or locked to a carrier which doesn't allow bootloader unlocking until the device is carrier unlocked (officially) or it has been previously unlocked in which case you would need to know the unlock code to unlock it again
If it has been registered before with Motorola you need to sign in using that email or try and unlink that address from the device (motorola device id option under settings)
Click to expand...
Click to collapse
I Just give up for good. I try many times, and cant unlock bootloader. I spend almost 5 hour today to figure out how ressurect this phone from dead. Its working and Its enough. Adreno 505/506 is to weak to emulate Dolphin And Citra emulator.
Time to buy something with new snapdragon cpu.
I buyed this moto from second hand for 10 euro today. Little cracked screen. But works. Its enough for me. Anyway thanks for all help i really apperciate it.

Morricorne said:
I Just give up for good. I try many times, and cant unlock bootloader. I spend almost 5 hour today to figure out how ressurect this phone from dead. Its working and Its enough. Adreno 505/506 is to weak to emulate Dolphin And Citra emulator.
Time to buy something with new snapdragon cpu.
I buyed this moto from second hand for 10 euro today. Little cracked screen. But works. Its enough for me. Anyway thanks for all help i really apperciate it.
Click to expand...
Click to collapse
Can you copy and paste the bootloader output of fastboot oem get_unlock_data (unedited) and I'll try and unlock it - I can't be bothered to manually type it in
If it gives the same for me then it can't be unlocked

Last question about bootloader and this device.
Root is needed to unlock bootloader on moto G5?
Maybe this is a problem. I dont have root access.

Morricorne said:
Last question about bootloader and this device.
Root is needed to unlock bootloader on moto G5?
Maybe this is a problem. I dont have root access.
Click to expand...
Click to collapse
You need to have an unlocked bootloader
Flash twrp
Flash magisk in twrp

I unlocked bootloader, flash twrp 64 bit. I now check lineageos 17 64 bit.
But battery life suck.
Time to find Best 64 bit rom.
Anyway thanks for help

XT-1922-5 Brickerd, showing N/A, going to TWRP even after flashing Stock and then off

Here's the story:
Got an used G6 Play from my cousin today, decided to do a Hard Reset, after the hard reset here it was the FRP, so i asked him the last Pattern lock and then i proceeded.
So i decided to: install twrp, root and then try Custom Roms
I unlocked the bootloader, everything ok, then i installed the decrypt script, also ok, installed Magisk through twrp, also ok.
Then i proceeded with trying custom roms: first the RessurectionRemix, i failed, because no matter which gapps i did, it said that system space was not enough
THen, i proceded to Lineage, than i downloaded the image and the gapps, after installed, it rebooted and the logo screen was "Blinking", like the logo appeared and then black screen, then again appeared and black scree. It keep like this forever, like a bootloop but i never got one blinking like this before, actually very strange.
Now, no matter what i do, it simply dont come back, i tried flashing stock rom 5 times already, and after the process, it goes like this:
It shows the Motorola logo, with some codes above (i guess the unlocked bootloader), then it shows N/a, then it goes to a brief TWRP logo and reboots. Then it starts all over again
I DON'T KNOW WHAT TO DO, THE PHONE IS DEAD, SOMEBODY HELP ME PLEASE

riquemonteiro said:
Here's the story:
Got an used G6 Play from my cousin today, decided to do a Hard Reset, after the hard reset here it was the FRP, so i asked him the last Pattern lock and then i proceeded.
So i decided to: install twrp, root and then try Custom Roms
I unlocked the bootloader, everything ok, then i installed the decrypt script, also ok, installed Magisk through twrp, also ok.
Then i proceeded with trying custom roms: first the RessurectionRemix, i failed, because no matter which gapps i did, it said that system space was not enough
THen, i proceded to Lineage, than i downloaded the image and the gapps, after installed, it rebooted and the logo screen was "Blinking", like the logo appeared and then black screen, then again appeared and black scree. It keep like this forever, like a bootloop but i never got one blinking like this before, actually very strange.
Now, no matter what i do, it simply dont come back, i tried flashing stock rom 5 times already, and after the process, it goes like this:
It shows the Motorola logo, with some codes above (i guess the unlocked bootloader), then it shows N/a, then it goes to a brief TWRP logo and reboots. Then it starts all over again
I DON'T KNOW WHAT TO DO, THE PHONE IS DEAD, SOMEBODY HELP ME PLEASE
Click to expand...
Click to collapse
Code:
fastboot getvar all
To make sure you have the correct codename and software channel for the firmware
Sent from my Moto E (4) using Tapatalk

me too
C:\_Android\Motorola\mg6>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-aljeter_retail-b1f322d35c1-2
(bootloader) version-bootloader[1]: 00404
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GX6BMB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: 0047220008
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 62A7DC6800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3555XXXXXXXX
(bootloader) meid:
(bootloader) date: 05-29-2018
(bootloader) sku: XT1922-5
(bootloader) carrier_sku: XT1922-5
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jun 24 0:45:34 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPPS29.
(bootloader) ro.build.fingerprint[1]: 55-35-18-7/6a0d0:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.311.7.aljeter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-03700-89xx.0
(bootloader) version-baseband: M8937_34.42.05.98R JETER_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g3e480e17e11
(bootloader) kernel.version[1]: f-04280-g407726838ebf ([email protected]
(bootloader) kernel.version[2]: 8) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Sat Apr 4 12:
(bootloader) kernel.version[4]: 24:37 CDT 2020
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-0d2031d6b9-200404
(bootloader) rpm.git: MBM-2.1-aljeter_retail-af31f6ae-200404
(bootloader) tz.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) prov.git: MBM-2.1-aljeter_retail-f9b266cd30-200404
(bootloader) aboot.git: MBM-2.1-aljeter_retail-b1f322d35c1-200404
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.184s

Help Needed - Flashing Stock NON-HLOS.bin erases Baseband.

As mentioned in the title I have an issue regarding the stock firmware. I have a Moto G7 Play (It's actually called Moto G7 Optimo) straight talk just renamed it. Anyways I cannot flash the Stock NON-HLOS.bin from the latest firmware (or any firmware of an earlier version). It erases my baseband and then no sim detected. Yet when I pull the modem Files from the Verizon variant and use them, my baseband returns and everything is good. The reason I'm wishing to return to the stock baseband is so I can properly receive updates. Like when Android 10 or a newer security version arrives. If anyone knows a fix please let me know and thank you.

hydroman202 said:
As mentioned in the title I have an issue regarding the stock firmware. I have a Moto G7 Play (It's actually called Moto G7 Optimo) straight talk just renamed it. Anyways I cannot flash the Stock NON-HLOS.bin from the latest firmware (or any firmware of an earlier version). It erases my baseband and then no sim detected. Yet when I pull the modem Files from the Verizon variant and use them, my baseband returns and everything is good. The reason I'm wishing to return to the stock baseband is so I can properly receive updates. Like when Android 10 or a newer security version arrives. If anyone knows a fix please let me know and thank you.
Click to expand...
Click to collapse
Run fastboot getvar all, send me the output, and I should be able to tell you. Be sure to black out your IMEI/MEID. You don't want people to have that info and I definitely don't need it. Alternatively, you can check your sim card for a carrier marker, like Sprint, At&t, etc and if it has one, that should be the modem you're after. The bootloader would probably give you the most accurate info though.
Being that's it's straight talk though, you might have to play musical chairs with modems before you get it right. They use like 4 different carriers for LTE.

Spaceminer said:
Run fastboot getvar all, send me the output, and I should be able to tell you. Be sure to black out your IMEI/MEID. You don't want people to have that info and I definitely don't need it. Alternatively, you can check your sim card for a carrier marker, like Sprint, At&t, etc and if it has one, that should be the modem you're after. The bootloader would probably give you the most accurate info though.
Being that's it's straight talk though, you might have to play musical chairs with modems before you get it right. They use like 4 different carriers for LTE.
Click to expand...
Click to collapse
This is my output:
C:\Users\MyComputer\Desktop\Modem Files
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-channel_trac-3747217-191127
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY323XB7MB
(bootloader) cid: 0x000F
(bootloader) channelid: 0x8c
(bootloader) uid: 9859ECFB00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: lol
(bootloader) meid: lol
(bootloader) date: 04-26-2019
(bootloader) sku: XT1952DL
(bootloader) carrier_sku: XT1952DL
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 11 18:17:35 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel_trac/channel:9/PP
(bootloader) ro.build.fingerprint[1]: YS29.105-134-7/fbb95:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.301.9.channel_tra
(bootloader) ro.build.version.full[1]: c.tracfone.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_32.127.01.130.01R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld71) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Wed Nov
(bootloader) kernel.version[3]: 27 05:21:02 CST 2019
(bootloader) sbl1.git: MBM-2.1-channel_trac-b508f3a-191127
(bootloader) rpm.git: MBM-2.1-channel_trac-22daab3-191127
(bootloader) tz.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) devcfg.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) keymaster.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) cmnlib.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) cmnlib64.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) prov.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) aboot.git: MBM-2.1-channel_trac-3747217-191127
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: tracfone
(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: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.308s

hydroman202 said:
This is my output:
C:\Users\MyComputer\Desktop\Modem Files
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-channel_trac-3747217-191127
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY323XB7MB
(bootloader) cid: 0x000F
(bootloader) channelid: 0x8c
(bootloader) uid: 9859ECFB00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: lol
(bootloader) meid: lol
(bootloader) date: 04-26-2019
(bootloader) sku: XT1952DL
(bootloader) carrier_sku: XT1952DL
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 11 18:17:35 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel_trac/channel:9/PP
(bootloader) ro.build.fingerprint[1]: YS29.105-134-7/fbb95:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.301.9.channel_tra
(bootloader) ro.build.version.full[1]: c.tracfone.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_32.127.01.130.01R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld71) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #1 SMP PREEMPT Wed Nov
(bootloader) kernel.version[3]: 27 05:21:02 CST 2019
(bootloader) sbl1.git: MBM-2.1-channel_trac-b508f3a-191127
(bootloader) rpm.git: MBM-2.1-channel_trac-22daab3-191127
(bootloader) tz.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) devcfg.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) keymaster.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) cmnlib.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) cmnlib64.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) prov.git: MBM-2.1-channel_trac-d9613e6-dirty-191127
(bootloader) aboot.git: MBM-2.1-channel_trac-3747217-191127
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: tracfone
(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: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.308s
Click to expand...
Click to collapse
Looks like
Model: XT1952DL
Codename: channel
Software channel: trac
Build version: 29.105.134.7
https://mirrors.lolinet.com/firmware/moto/channel/official/TRAC/
Sent from my mata using XDA Labs

This should be your most recent firmware. Direct download: Channel_Trac And this should be your firmware folder.
Make sure you run the commands fastboot erase modemst1 and fastboot erase modemst2 after flashing the modem.

hydroman202 said:
As mentioned in the title I have an issue regarding the stock firmware. I have a Moto G7 Play (It's actually called Moto G7 Optimo) straight talk just renamed it. Anyways I cannot flash the Stock NON-HLOS.bin from the latest firmware (or any firmware of an earlier version). It erases my baseband and then no sim detected. Yet when I pull the modem Files from the Verizon variant and use them, my baseband returns and everything is good. The reason I'm wishing to return to the stock baseband is so I can properly receive updates. Like when Android 10 or a newer security version arrives. If anyone knows a fix please let me know and thank you.
Click to expand...
Click to collapse
I had this issue with a T-Mobile revvlry, flashing the stock NON-HLOS.bin didn't help. I only get signal with the Verizon modem

Spaceminer said:
This should be your most recent firmware. Direct download: Channel_Trac And this should be your firmware folder.
Make sure you run the commands fastboot erase modemst1 and fastboot erase modemst2 after flashing the modem.
Click to expand...
Click to collapse
Ok I figured out why I have no baseband when I flash NON-HLOS.bin. It's because I flashed the Verizon one and it's newer than my stock firmware. Is there anyway to downgrade the modem?

hydroman202 said:
Ok I figured out why I have no baseband when I flash NON-HLOS.bin. It's because I flashed the Verizon one and it's newer than my stock firmware. Is there anyway to downgrade the modem?
Click to expand...
Click to collapse
Modems can't down grade. I did the same thing once with the Pie test release. If flashing the correct modem and wiping modemst1/st2 didn't work, you're stuck like that until a newer firmware gets released. Did you maybe flash an older firmware from Trac? Because they have a 2-7-2020 release and the latest from Verizon is just one day before that. So the most recent Trac modem should be as updated as Verizon's.
Also did you try flashing the full firmware or just the modem?

Spaceminer said:
Modems can't down grade. I did the same thing once with the Pie test release. If flashing the correct modem and wiping modemst1/st2 didn't work, you're stuck like that until a newer firmware gets released. Did you maybe flash an older firmware from Trac? Because they have a 2-7-2020 release and the latest from Verizon is just one day before that. So the most recent Trac modem should be as updated as Verizon's.
Also did you try flashing the full firmware or just the modem?
Click to expand...
Click to collapse
I tried to flash the full firmware. And there's a 2-7-2020 release for Trac? The reason I'm asking is because the latest I saw was 1-7-2020 on lolinet.

hydroman202 said:
I tried to flash the full firmware. And there's a 2-7-2020 release for Trac? The reason I'm asking is because the latest I saw was 1-7-2020 on lolinet.
Click to expand...
Click to collapse
My mistake, you're correct. It's 1-7-2020 and 1-6-2020. That really sucks. I think you're stuck until newer firmware pops up, or another OTA. You might be able to fix it by going one firmware release back, and then OTA updating into the latest release. You'd need WiFi though. It's worth a shot.

Spaceminer said:
My mistake, you're correct. It's 1-7-2020 and 1-6-2020. That really sucks. I think you're stuck until newer firmware pops up, or another OTA. You might be able to fix it by going one firmware release back, and then OTA updating into the latest release. You'd need WiFi though. It's worth a shot.
Click to expand...
Click to collapse
I'll give it a try. I appreciate the idea. I'll report back on here as to whether or not it succeeds. I'm hoping so. If not then I'll wait for the next firmware like you said.

It did not succeed. When i tried to downgrade to a previous firmware it boot looped the device. its back to where it was before with the same modem issue.

hydroman202 said:
It did not succeed. When i tried to downgrade to a previous firmware it boot looped the device. its back to where it was before with the same modem issue.
Click to expand...
Click to collapse
Did you flash both slots with the older firmware? If not that could be the reason it bootlooped.

Spaceminer said:
Did you flash both slots with the older firmware? If not that could be the reason it bootlooped.
Click to expand...
Click to collapse
I did not. Would rsd lite automate that? Or would I have to do it manually?

hydroman202 said:
I did not. Would rsd lite automate that? Or would I have to do it manually?
Click to expand...
Click to collapse
I'm pretty sure you'd have to do it manually. I never use RSD but I imagine it'd go strictly by the flash file, which would only flash to slot A, and send those smaller dummy files in the firmare to slot B.

I Need Some Custom Rom Installation Advice

I have four phones I am going to flash custom ROM onto. One Moto X 1st Gen 2013 (Codename: Victara), One Lg K7 2016 (Codename: M1), and Two Moto G 1st Gen 2013 (Codename: Falcon).
At the moment I have decided to work on one phone at a time and am tackling a Moto G first. I ran into some problems unlocking the bootloader and I think it may be related to data carriers. When I posted my device unlock data on the Motorola website it said it wasn't supported.
This is what it looked like before I removed the spaces:
(bootloader) A000002CECBEAD00#54413936353053
(bootloader) 4F363300585431303331000000#8805
(bootloader) 5A8D2DEECF6976804B5B4FF4EA1EEAB
(bootloader) DEB29#1F336F050F000000000000000
(bootloader) 0000000
And After:
A000002CECBEAD00#544139363530534F363300585431303331000000#88055A8D2DEECF6976804B5B4FF4EA1EEABDEB29#1F336F050F0000000000000000000000
https://forums.lenovo.com/t5/MOTO-G...ader-Unlock-Help-Please-post-here/m-p/3024663 This post worries me the most because I ran this line of code: fastboot getvar all, and it came back with this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8626 CS
(bootloader) serialno: TA9650SO63
(bootloader) cid: 0x0006
(bootloader) channelid: 0x00
(bootloader) uid: 1F336F050F000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 13:37:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_repw/falcon_cdma:5
(bootloader) ro.build.fingerprint[1]: .1/LPB23.13-51-R.14/5:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.26.14.falcon_cdm
(bootloader) ro.build.version.full[1]: a.RepublicWireless.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.98.00R REPUB_CDMA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gb965ded ([email protected]
(bootloader) kernel.version[1]: ilclbld35) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Sep 16 08:30:15 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: sprint
all: listed above
I think this phone used to be Sprint and switched to Republic Wireless because I dug around and there are only Republic Wireless apps on the phone but deeper there are Sprint pieces and fastboot getvar all did come back with these:
(bootloader) ro.build.version.full[1]: a.RepublicWireless.en.US
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.98.00R REPUB_CDMA_
(bootloader) ro.carrier: sprint
To make it worse on that other post it says certain CID are not allowed and mine came back as 0x0006 which isn't supported. They state plainly on that post as well several of the carriers they do not support not including Sprint but they did show Republic Wireless. What should I do?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/

ccoons said:
I have four phones I am going to flash custom ROM onto. One Moto X 1st Gen 2013 (Codename: Victara), One Lg K7 2016 (Codename: M1), and Two Moto G 1st Gen 2013 (Codename: Falcon).
At the moment I have decided to work on one phone at a time and am tackling a Moto G first. I ran into some problems unlocking the bootloader and I think it may be related to data carriers. When I posted my device unlock data on the Motorola website it said it wasn't supported.
This is what it looked like before I removed the spaces:
(bootloader) A000002CECBEAD00#54413936353053
(bootloader) 4F363300585431303331000000#8805
(bootloader) 5A8D2DEECF6976804B5B4FF4EA1EEAB
(bootloader) DEB29#1F336F050F000000000000000
(bootloader) 0000000
And After:
A000002CECBEAD00#544139363530534F363300585431303331000000#88055A8D2DEECF6976804B5B4FF4EA1EEABDEB29#1F336F050F0000000000000000000000
https://forums.lenovo.com/t5/MOTO-G...ader-Unlock-Help-Please-post-here/m-p/3024663 This post worries me the most because I ran this line of code: fastboot getvar all, and it came back with this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8626 CS
(bootloader) serialno: TA9650SO63
(bootloader) cid: 0x0006
(bootloader) channelid: 0x00
(bootloader) uid: 1F336F050F000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Sep 16 13:37:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_repw/falcon_cdma:5
(bootloader) ro.build.fingerprint[1]: .1/LPB23.13-51-R.14/5:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.26.14.falcon_cdm
(bootloader) ro.build.version.full[1]: a.RepublicWireless.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.98.00R REPUB_CDMA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-gb965ded ([email protected]
(bootloader) kernel.version[1]: ilclbld35) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Sep 16 08:30:15 CDT 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: sprint
all: listed above
I think this phone used to be Sprint and switched to Republic Wireless because I dug around and there are only Republic Wireless apps on the phone but deeper there are Sprint pieces and fastboot getvar all did come back with these:
(bootloader) ro.build.version.full[1]: a.RepublicWireless.en.US
(bootloader) version-baseband[0]: MSM8626BP_1032.3116.98.00R REPUB_CDMA_
(bootloader) ro.carrier: sprint
To make it worse on that other post it says certain CID are not allowed and mine came back as 0x0006 which isn't supported. They state plainly on that post as well several of the carriers they do not support not including Sprint but they did show Republic Wireless. What should I do?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Click to expand...
Click to collapse
Yes, that cid is a non starter, move on to next device.

(The forums said I am not allowed to make links in my messages, yet, so the links aren't clickable.)
I worked on the LG K7 and it followed these guides:
getdroidtips.com/unlock-bootloader-mediatek-device/
getdroidtips.com/root-and-install-twrp-recovery-on-lg-k7/
getdroidtips.com/download-latest-magisk-zip-magisk-manager-root-phone/
getdroidtips.com/pixel-experience-lg-k7/
It worked great right up to the end. It unlocked, installed TWRP, installed Magisk, and rooted. Right at the end when I gave it the Pixel Experience ROM that the guide said, it downloaded fine with no errors, but when I restarted the phone it just buzzed and flashed the LG logo. I think I broke it. :crying:
This is the file they told me to download for the device. mega.nz/folder/lfRSQIRa#rsKZEtcUdsTaSL46oCT6rQ
All the other files I downloaded for the device had the name of the device on it, but not that one. I didn't feel right about it and I probably shouldn't have done it. Is there anything I can do to put the backup back onto the device?

ccoons said:
(The forums said I am not allowed to make links in my messages, yet, so the links aren't clickable.)
I worked on the LG K7 and it followed these guides:
getdroidtips.com/unlock-bootloader-mediatek-device/
getdroidtips.com/root-and-install-twrp-recovery-on-lg-k7/
getdroidtips.com/download-latest-magisk-zip-magisk-manager-root-phone/
getdroidtips.com/pixel-experience-lg-k7/
It worked great right up to the end. It unlocked, installed TWRP, installed Magisk, and rooted. Right at the end when I gave it the Pixel Experience ROM that the guide said, it downloaded fine with no errors, but when I restarted the phone it just buzzed and flashed the LG logo. I think I broke it. :crying:
This is the file they told me to download for the device. mega.nz/folder/lfRSQIRa#rsKZEtcUdsTaSL46oCT6rQ
All the other files I downloaded for the device had the name of the device on it, but not that one. I didn't feel right about it and I probably shouldn't have done it. Is there anything I can do to put the backup back onto the device?
Click to expand...
Click to collapse
I would look in https://forum.xda-developers.com/lg-k7
Sent from my payton using XDA Labs

I followed some of those guides you sent me to and managed to recover the device and am very relieved. This time I am going to be much more careful and take my time. :victory:

The LG K7 doesn't appear to have any supported custom rom, so the stuff I downloaded is confusing. I guess I will sell the device instead.

Fastboot working improperly on xt1789-04 engineering

Since I saw that the Moto Z2 force was able to be rooted, and I had just killed my Z force, I figured I'd go ahead and order a new one on ebay.
First thing I tried was to get the bootloader unlock data.
The issue with this however was that the command wasn't running properly. It gave me unknown command. So I retyped it and tried it again and it told me I was running an engineering sample.
The problem here is that I had to, and have to, run a command multiple times for it to execute properly. Looking in the bootloader logs shows that the command is executed, but part of the last command is appended at the end to make the next command as long as the previous command. if the previous command was smaller than the next command, it's truncated.
Has anybody else experienced this? Is there a workaround, or is it due to my engineering sample phone?

Linuxfan724 said:
Since I saw that the Moto Z2 force was able to be rooted, and I had just killed my Z force, I figured I'd go ahead and order a new one on ebay.
First thing I tried was to get the bootloader unlock data.
The issue with this however was that the command wasn't running properly. It gave me unknown command. So I retyped it and tried it again and it told me I was running an engineering sample.
The problem here is that I had to, and have to, run a command multiple times for it to execute properly. Looking in the bootloader logs shows that the command is executed, but part of the last command is appended at the end to make the next command as long as the previous command. if the previous command was smaller than the next command, it's truncated.
Has anybody else experienced this? Is there a workaround, or is it due to my engineering sample phone?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
getvar all returns
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: no
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ***********
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 240B9928
(bootloader) securestate: engineering
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) date: 09-23-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 4113
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-14-7/12:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.351.12.nash_tmo_c
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.08R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g5b6c26aa-0177
(bootloader) kernel.version[1]: 2-g1e9c9a2 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Fri Jul 5 12:49:00 CDT 2
(bootloader) kernel.version[4]: 019
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:pmic: MBM-3.0-nash_tmo-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:hyp: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:devcfg: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:keymaster: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:storsec: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) git:prov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(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: 7
(bootloader) slot-retry-count:_b: 0
With IMEI and the serial blurred of course

I seem to have fixed the problem.
For anybody else searching for this thread, the solution was to use a different computer. Even after reinstalling fastboot and the drivers for my device, it continued to occur. However, after switching to my laptop everything works properly.

Linuxfan724 said:
I seem to have fixed the problem.
For anybody else searching for this thread, the solution was to use a different computer. Even after reinstalling fastboot and the drivers for my device, it continued to occur. However, after switching to my laptop everything works properly.
Click to expand...
Click to collapse
You have an engineering model, the bootloader is already unlocked, to my understanding.
Code:
(bootloader) securestate: engineering
This is a device designed for testing not normal use.
You need to be very careful, your device does not have consumer firmware.
The standard Moto firmware likely will not work correctly.
The Engineering firmware likely is not available.
This device might be rootable but if something goes wrong you have very few options to fix it.
I would try booting Twrp https://dl.twrp.me/nash/
Code:
fastboot boot twrp-3.3.1-0-nash.img
and see if you can do a full system backup
You may have to disable the pin/password... if twrp decryption doesn't work.
if booting does not work you can try flashing twrp but there may not be any going back to stock boot.img after that.
I don't have specific knowledge of Nash, this based on several conversions with owners of other moto engineering devices.

sd_shadow said:
You have an engineering model, the bootloader is already unlocked, to my understanding.
Code:
(bootloader) securestate: engineering
This is a device designed for testing not normal use.
You need to be very careful, your device does not have consumer firmware.
The standard Moto firmware likely will not work correctly.
The Engineering firmware likely is not available.
This device might be rootable but if something goes wrong you have very few options to fix it.
I would try booting Twrp https://dl.twrp.me/nash/
Code:
fastboot boot twrp-3.3.1-0-nash.img
and see if you can do a full system backup
You may have to disable the pin/password... if twrp decryption doesn't work.
if booting does not work you can try flashing twrp but there may not be any going back to stock boot.img after that.
I don't have specific knowledge of Nash, this based on several conversions with owners of other moto engineering devices.
Click to expand...
Click to collapse
It did actually come with retail firmware, but fastboot is in engineering and the bootloader cannot be relocked. Certainly a new experience for me. I got lineage running on it with magisk to hide from GPay. Works like a charm now!