IMEI 0 - Moto Z2 Force Questions & Answers

HELLO EVERYONE! PLEASE HELP TO RESTORE IMEI MOTO Z2 FORCE (XT1789-04 TMOBILE)
SHORT STORY: I TRIED TO FLASH TO ANDROID 9 FROM VERIZON CARRIER, I UNLOCKED BOOTLOADER, BACKUP ALL DATA BY TWRP BUT I DID SOMETHING WRONG AND DELETED BACKED UP DATA BY MISTAKE.
USING MOTOROLA RESCUE I CAN RESTORE ORIGINAL FIRMWARE, BUT IMEI SHOWS 0, WIFI ALSO DOESN'T WORK.
COULD SOMEONE EXPLAIN HOW TO RESTORE EFS FOLDER , IS IT ANY SOLUTION AND EXPLANATION HOW TO DO IT.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(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: ZY224CBHHC
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3C0920D9
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3565**********
(bootloader) meid:
(bootloader) date: 07-30-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3785
(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.08u 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) gitmic: 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) gitrov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(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: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.229s

IMEI is not in Android/ROM, ist in PDS partition!
You hab a backup from all version with twrp?

R!ffRaff said:
IMEI is not in Android/ROM, ist in PDS partition!
You hab a backup from all version with twrp?
Click to expand...
Click to collapse
I did, but I formatted hard drive by mistake and lost it, now trying to restore imei and have no idei how to do it

khurshed04 said:
I did, but I formatted hard drive by mistake and lost it, now trying to restore imei and have no idei how to do it
Click to expand...
Click to collapse
You can try restore the backup with a recover

I had the same problem , flashing lineageos seems to fix it but you can never downgrade below android 10 again and keep baseband. You're stuck with using 10+ only unless you don't care about IMEI/baseband but yeah just flash the newest lineage and if that doesn't work flash the second to newest etc. Worked for me several times

In my case with Sprint xt1789-03 help this way:
Flash NASH_RETAIL_9.0_PPX29.159-24 with MotoFlashPro WHITHOUT modem section - UNCHECK this:
%fastboot% flash dsp adspso.bin
%fastboot% flash modem NON-HLOS.bin
%fastboot% flash fsg fsg.mbn
%fastboot% flash bluetooth BTFM.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
Then flash full latest sprit 8 android stock

PrivyetCyka said:
I had the same problem , flashing lineageos seems to fix it but you can never downgrade below android 10 again and keep baseband. You're stuck with using 10+ only unless you don't care about IMEI/baseband but yeah just flash the newest lineage and if that doesn't work flash the second to newest etc. Worked for me several times
Click to expand...
Click to collapse
That worked for my Device too. I had lost IMEI & baseband. First I flashed the latest TMO(04) image (you can use Lenovo/Motorola Rescue and Smart Assistant Software for Windows ) to get the baseband working and then flash LineageOS.

Related

My phone boots to recovery

I installed TWRP a long time ago, for xposed ad other things, in one instalation of a rom or a kernel my phone started to boot directly to TWRP and not to system, y tried to flash stock but the problem kept going, then i realized that if i boot to bootlader with volume- and power, then hit start the phone will boot normally, so every time i restart the phone i had to boot in bootloader and then hit start. recently i installed the official nougat rom via adb and TWRP, and i still have the problem, i am going to sell the phone now, so i need to give it as stock as possible, so i need to fix the boot issue and relock the bootloader.
I apologize for my english, i did my best to explain the situation.
Thanks
Juanes2070 said:
I installed TWRP a long time ago, for xposed ad other things, in one instalation of a rom or a kernel my phone started to boot directly to TWRP and not to system, y tried to flash stock but the problem kept going, then i realized that if i boot to bootlader with volume- and power, then hit start the phone will boot normally, so every time i restart the phone i had to boot in bootloader and then hit start. recently i installed the official nougat rom via adb and TWRP, and i still have the problem, i am going to sell the phone now, so i need to give it as stock as possible, so i need to fix the boot issue and relock the bootloader.
I apologize for my english, i did my best to explain the situation.
Thanks
Click to expand...
Click to collapse
Please connect your phone in bootloader and write command "fastboot getvar all" and share data so status can be checked for solution.
Actually you need to flash same Bootloader version again to resolve the issue
Data
zahidm said:
Please connect your phone in bootloader and write command "fastboot getvar all" and share data so status can be checked for solution.
Actually you need to flash same Bootloader version again to resolve the issue
Click to expand...
Click to collapse
Hi, i'm sorry i took so long to get the data, here it is, can you still help me out ? thanks for the reply
version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322KZMMJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 34153EE200000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355662082344936
(bootloader) meid:
(bootloader) date: 01-28-2018
(bootloader) sku: XT1791
(bootloader) carrier_sku:
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-2/e71c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.2.mon.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_37.13.03.64R MONTANA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g784476b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 12:38:10 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=9a0b157
(bootloader) devcfg.git: git=9a0b157
(bootloader) keymaster.git: git=7b4297f
(bootloader) cmnlib.git: git=7b4297f
(bootloader) cmnlib64.git: git=7b4297f
(bootloader) prov.git: git=7b4297f
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(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
Juanes2070 said:
Hi, i'm sorry i took so long to get the data, here it is, can you still help me out ? thanks for the reply
version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322KZMMJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 34153EE200000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355662082344936
(bootloader) meid:
(bootloader) date: 01-28-2018
(bootloader) sku: XT1791
(bootloader) carrier_sku:
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-2/e71c:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.2.mon.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_37.13.03.64R MONTANA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g784476b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue Oct 9 12:38:10 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=9a0b157
(bootloader) devcfg.git: git=9a0b157
(bootloader) keymaster.git: git=7b4297f
(bootloader) cmnlib.git: git=7b4297f
(bootloader) cmnlib64.git: git=7b4297f
(bootloader) prov.git: git=7b4297f
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(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
Click to expand...
Click to collapse
I sold Montana but let me check solution for you

Is it possible to root the T-Mobile XT1789-04?????

I've been trying to root and install Lineage 16.0 on my Z2 force TMO XT1789-04 for a few weeks now.
I was able to unlock the bootloader on Motorola's website no problem.
The phone has been updated to OCXS 27.1.7.
When I run getprop ro.bootloader, MBM-3.0-nash_tmo-1f35305-190705 is my result. This didn't verify if my bootloader was OCSX, so I ran the getvar all command in fastboot, and the output said I was running MBM-3.0-nash_tmo-1f35305-190705 in slot _b. I will post all the info at the end of the post.
Earlier I made the mistake of moving ahead to set the bootloader partition to slot _a. Luckilly I didn't brick my phone. I used the following commands with no luck .
fastboot set_active other
fastboot set_active a
fastboot –set-active=_aslot
fastboot –set-active=_a
What am I doing wrong? Should I give up? I'd rather sell my phone than brick it.
If someone could point me in the right direction I'd appreciate it!!!.
Thanks!
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(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 SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224B9BP4
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 14905111
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ****(deleted)
(bootloader) meid:
(bootloader) date: 07-26-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4379
(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) gitmic: 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) gitrov: MBM-3.0-nash_tmo-1bc18bf-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
Why do u have to do all of this to just install lineage 16?
I'm on T-Mobile too and I just simply:
1- fastboot flashed the pre-los zip
2- follow the normal procedure for flashing Los (although it took time to find the right twrp version actually working, many didn't flashed successfully) + magisk for root
3- mind my tmo Z2 force was already on Oreo...
Use twrp 3.3.0.0.img to flash with, I wouldn't worry about installing twrp since the updater uses Los recovery. If you must insstall twrp 3.3.1.0.zip is solid I believe. Not sure why 3..3.0.0.zip isn't there, but I have the zip if needed.
I tried to install TWRP 3.3.0-0 using fastboot flash boot (path to) twrp.img
I wasn't able to get TWRP installed. Am I using the wrong commands or twrp image?
Google_is_Watching said:
I tried to install TWRP 3.3.0-0 using fastboot flash boot (path to) twrp.img
I wasn't able to get TWRP installed. Am I using the wrong commands or twrp image?
Click to expand...
Click to collapse
You'll need to run fastboot boot twrp.img once it boots to TWRP you can use the install option within TWRP to install the twrp.zip file
rcmaehl said:
You'll need to run fastboot boot twrp.img once it boots to TWRP you can use the install option within TWRP to install the twrp.zip file
Click to expand...
Click to collapse
It worked!!! I feel dumb but grateful. Thank you!

XT 1789-04 Can't Get Passed Bootloader

Hey all,
Okay. I have (apparently) the 1789-04 version of the Z2 Force. However, the phone insists, for the most part, internally, that it is an AT&T phone, not the TMO variant, which would be the variant indicated by the model number. This has lately become an issue due to the fact that the other day I was in camera mode on the phone, and POOF it bricked all over me, and I've tried to flash all kinds of stock firmware onto the phone. ATT firmwares flash successfully across the board, but just end up doing a bootloader boot loop, sometimes asking me to factory data reset the phone. TMO stock firmware fails at the point where the boot image flashes with the error "Preflash validation error". I've tried all kinds of firwmares, the most recent, slightly older ones.
The device shows in the bootloader as OEM locked, but when I flash the TMO bootloader, it starts off with the bootloader unlocked warning. Total bonkers. When the ATT is flashed, it never boots, so no point. I only get as far as the Motorola screen. I cannot get the phone to go to blankflash, as the command fastboot oem blankflash (no quotes) produces an error that says something along the the lines of that not being authorized. I would LOVE for my phone to be forced into a spot where I could use blankflash and go from there. Anyway, here's the getvar, if you guys have any suggestions, that would be great.
C:\Users\zacha>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(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: ZY2249JTJC
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 3D66704C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080795291
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3695
(bootloader) iccid: 89014103270252934039
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(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]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) git:storsec: git:storsec
(bootloader) gitrov: gitrov
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.206s
zjcook23 said:
Hey all,
Okay. I have (apparently) the 1789-04 version of the Z2 Force. However, the phone insists, for the most part, internally, that it is an AT&T phone, not the TMO variant, which would be the variant indicated by the model number. This has lately become an issue due to the fact that the other day I was in camera mode on the phone, and POOF it bricked all over me, and I've tried to flash all kinds of stock firmware onto the phone. ATT firmwares flash successfully across the board, but just end up doing a bootloader boot loop, sometimes asking me to factory data reset the phone. TMO stock firmware fails at the point where the boot image flashes with the error "Preflash validation error". I've tried all kinds of firwmares, the most recent, slightly older ones.
The device shows in the bootloader as OEM locked, but when I flash the TMO bootloader, it starts off with the bootloader unlocked warning. Total bonkers. When the ATT is flashed, it never boots, so no point. I only get as far as the Motorola screen. I cannot get the phone to go to blankflash, as the command fastboot oem blankflash (no quotes) produces an error that says something along the the lines of that not being authorized. I would LOVE for my phone to be forced into a spot where I could use blankflash and go from there. Anyway, here's the getvar, if you guys have any suggestions, that would be great.
C:\Users\zacha>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(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: ZY2249JTJC
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 3D66704C
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080795291
(bootloader) meid:
(bootloader) date: 07-28-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3695
(bootloader) iccid: 89014103270252934039
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(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]: Tue May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180130
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) git:storsec: git:storsec
(bootloader) gitrov: gitrov
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: att
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.206s
Click to expand...
Click to collapse
Try Flash/rescue option in
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Another note is that both att and tmo models are xt 1789-04, so the if your phone is telling you it's an att then there is no way to unlock the bootloader.
Sent from my moto z4 using XDA Labs
sd_shadow said:
Try Flash/rescue option in
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
Tried this multiple times but my phone can't get past fastboot so I can't check the USB debugging or even have the phone detected by the LMSA. when i manually tell the program that it's an xt-1789-04, it will get as far as cmd: getvar:serialno before saying it can't match the product with the model number.

MOTO G8 PLAY bricked/dead

Hello,
i need help trying to revive this motog8 play, i can do everything with the old models, but at the first time i tried to root those A/B systems, i bricked it and i think its ded.
Tried revive with rds, but doesnt recognice the xml file and the usb port, LSMA doesnt have the model yet, and by the fastboot still the same.
The server looks pretty empty, if no one can help i think its going to the thrash, cuz the techs here in my city doesnt flash devices, just change screens haha :')
Start Up Failed:
AP Fastboot Flash Mode (Secure)
No Bootable A/B Solt
Please, help, since i buy this stupid device i tried to install magisk and it died haha
Matiasfh01 said:
Hello,
i need help trying to revive this motog8 play, i can do everything with the old models, but at the first time i tried to root those A/B systems, i bricked it and i think its ded.
Tried revive with rds, but doesnt recognice the xml file and the usb port, LSMA doesnt have the model yet, and by the fastboot still the same.
The server looks pretty empty, if no one can help i think its going to the thrash, cuz the techs here in my city doesnt flash devices, just change screens haha :')
Start Up Failed:
AP Fastboot Flash Mode (Secure)
No Bootable A/B Solt
Please, help, since i buy this stupid device i tried to install magisk and it died haha
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
and post it here (remove the IMEI line)
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
sd_shadow said:
Run
Code:
fastboot getvar all
and post it here (remove the IMEI line)
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
I want to follow this close. This is 2nd or 3rd thread I have seen this failed to boot problem. It makes me second guess my choice to purchase one of these devices.
I have wondered if this phone, being Mtk soc, opens possibly to use sp flash tool for flashing and repair. This would be my first Moto device, but definitely not first Mtk. I am familiar and comfortable with sp flash tool. .
mrmazak said:
I want to follow this close. This is 2nd or 3rd thread I have seen this failed to boot problem. It makes me second guess my choice to purchase one of these devices.
I have wondered if this phone, being Mtk soc, opens possibly to use sp flash tool for flashing and repair. This would be my first Moto device, but definitely not first Mtk. I am familiar and comfortable with sp flash tool. .
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-d6ab3f7-190816
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326QRN5Q
(bootloader) cid: 0x0032
(bootloader) channelid: 0x04
(bootloader) uid: 5F9D600C3FE92E5C000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-23-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 1 22: 6: 0 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32_amx/lima:9/PMDS29
(bootloader) ro.build.fingerprint[1]: .70-70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32_amx
(bootloader) ro.build.version.full[1]: .amx.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: amxcl
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C56212
all: listed above
Matiasfh01 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-d6ab3f7-190816
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY326QRN5Q
(bootloader) cid: 0x0032
(bootloader) channelid: 0x04
(bootloader) uid: 5F9D600C3FE92E5C000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-23-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 1 22: 6: 0 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32_amx/lima:9/PMDS29
(bootloader) ro.build.fingerprint[1]: .70-70-2/ac5451:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.251.2.lima_32_amx
(bootloader) ro.build.version.full[1]: .amx.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 55) (gcc version 4.9.x 20150123 (prerele
(bootloader) kernel.version[2]: ase) (GCC) ) #1 SMP PREEMPT Thu Dec 26 1
(bootloader) kernel.version[3]: 0:20:37 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: amxcl
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: no
(bootloader) slot-bootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28C56212
all: listed above
Click to expand...
Click to collapse
So, based on what has been told. And the information in your post here. You need to use the boot.img from this firmware.
mirrors.lolinet.com >firmware >moto >lima_32 >official >AMXCL >XT2015-2_LIMA_32_AMX_9.0_PMDS29.70-70-2_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmwar...ubsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
mrmazak said:
So, based on what has been told. And the information in your post here. You need to use the boot.img from this firmware.
mirrors.lolinet.com >firmware >moto >lima_32 >official >AMXCL >XT2015-2_LIMA_32_AMX_9.0_PMDS29.70-70-2_subsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmwar...ubsidy-CLACLSL_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Doesnt work, or should i just flash the boot.img ?
Matiasfh01 said:
Doesnt work, or should i just flash the boot.img ?
Click to expand...
Click to collapse
Carefully, I have no experience with Moto. All I can say is from other device experience.
Based on the guide you quoted as followed. You downloaded firmware. Extracted the boot.img, patched that boot.img. then flashed it to slot_a and slot_b.
Then you had boot loop.
Was the firmware you downloaded the correct one that matches getvar output.(from before , not now). The firmware I linked matches getvar output from now.
And back to the question, yes try to just flash the boot.img from linked firmware to both boot_a and boot_b. Just like from the root guide, but with the stock images.
Matiasfh01 said:
Doesnt work, or should i just flash the boot.img ?
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
You want to flash the same
Blur Software version
If not sure you could just
Flash the full firmware.
Edit
Sent from my ali using XDA Labs
sd_shadow said:
Code:
fastboot flash boot boot.img
You want to flash the same
Blur Software version
If not sure you could just
Flash the full firmware.
Edit
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
did both and didnt work, and no, the lsma doesnt support the device yet
(bootloader) is-logical:boot_a
(bootloader) : not found
Sending 'boot_a' (32768 KB) OKAY [ 0.720s]
Writing 'boot_a' OKAY [ 0.589s]
Finished. Total time: 1.362s
what does the not found mean?

Question Moto e 2020 XT2052-1 Startup Fail

Hello, I have this device with problems booting android 10. A red legend appears showing "
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fail-through from factory boot mode "
I have tried to flash it with various tools like RSD Lite, Odin(NOT shown), and Lenovo User Assistant, all efforts have failed the device always shows the same red legend or sometimes it goes completely black with the charging indicator led blinking. Recovery mode is not accessible.
Please help. Thanks in advance
Rainwod said:
Hello, I have this device with problems booting android 10. A red legend appears showing "
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fail-through from factory boot mode "
I have tried to flash it with various tools like RSD Lite, Odin(NOT shown), and Lenovo User Assistant, all efforts have failed the device always shows the same red legend or sometimes it goes completely black with the charging indicator led blinking. Recovery mode is not accessible.
Please help. Thanks in advance
Click to expand...
Click to collapse
What does getvar all say? Remove imei before posting
Code:
fastboot getvar all
thanks sd_shadow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(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: ZY22BLLKRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 96F6A8B300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from factory boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-18-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66368
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 9 8:41:56 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-135-7/c2ede:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.02R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[3]: un 9 05:43:55 CDT 2021
(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-ginna_retail-b0c61b8e633-210609
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(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: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 1.609s
i downloaded and try to flash this ROMs:
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
GINNA_RETAIL_QPGS30.82_135_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
the variable (bootloader) ro.build.fingerprint[1] does not change its value, it always shows S30.82-135-7/c2ede:user/release-ke even after flashing with RSD Lite.
Thanks a lot
Rainwod said:
thanks sd_shadow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-210609
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(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: ZY22BLLKRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 96F6A8B300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from factory boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 12-18-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66368
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Sep 9 8:41:56 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-135-7/c2ede:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.02R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Wed J
(bootloader) kernel.version[3]: un 9 05:43:55 CDT 2021
(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-ginna_retail-b0c61b8e633-210609
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(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: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 1.609s
i downloaded and try to flash this ROMs:
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
GINNA_RETAIL_QPGS30.82_135_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
the variable (bootloader) ro.build.fingerprint[1] does not change its value, it always shows S30.82-135-7/c2ede:user/release-ke even after flashing with RSD Lite.
Thanks a lot
Click to expand...
Click to collapse
Rsd lite may not work with Windows 10.
Use Windows 7 or xp with rsd lite.
Sometimes this works flash this.
Code:
fastboot flash partition gpt.bin
fastboot reboot bootloader
Then retry LMSA if you have Windows 10 or RSD Lite if you have Windows 7 or XP
sd_shadow said:
(...)
Then retry LMSA if you have Windows 10 or RSD Lite if you have Windows 7 or XP
Click to expand...
Click to collapse
I have tried both methods that you have indicated, in both cases ( RSD lite with Windows XP ) the process ends normally without failures but the result is the same, red Startup Fail legend. Thanks for the help, do you have any other ideas?
Rainwod said:
I have tried both methods that you have indicated, in both cases ( RSD lite with Windows XP ) the process ends normally without failures but the result is the same, red Startup Fail legend. Thanks for the help, do you have any other ideas?
Click to expand...
Click to collapse
It's possible the issue is related to the Persist Partition or other secure partition.
There is a good thread in the Moto G5 Plus forum.
I don't know if any of that discussion applies to the Moto E though.
Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements
I have created this thread in order to have one thread that details just the solution to fixing your persist, identifying whether or not you have an issue with your persist, and how you can restore your IMEI without hacks. This guide is written...
forum.xda-developers.com
Honestly looks like a cross flash to retus, followed by a bootloader lock. I don't think you can trust any fastboot variables if that's the case. You'd just have to flash boot.img for every model and variant of the E 2020 until you find the one that is allowed to boot.

Categories

Resources