Sorry if I have some grammar errors, English is not my main language
OK so Recently I bought this phone from a friend thinking it was an easy fix by just flashing a rom but I couldn't find a way to make it work.
I've tried many way on how to fix, via LMSA and from ADB but got no luck.
The rom I use is the one who LMSA gave me:
LIMA_32_AMX_PMD29.70-81_subsidy-DEFAULT_regulatory-XT2015_2L_CFC
This is what the command ¨fastboot getvar all¨ trows at me:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-210600d2e-200306
(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: ZY326VQQK5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x08
(bootloader) uid: F60944C9BFC7792F000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) meid:
(bootloader) date: 10-28-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 12 2:10:26 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32_amx/lima:9/PMD29.
(bootloader) ro.build.fingerprint[1]: 70-81/cb27e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.51.97.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: MT6771_V16.03.01.90R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 171) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Fri Mar 6 0
(bootloader) kernel.version[3]: 9:15:39 CST 2020
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: amxco
(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: SB28C70228
And this is the ADB command that i use before
Code:
fastboot flash gpt PGPT
fastboot flash preloader preloader.bin
fastboot flash lk_a lk.img
fastboot flash tee_a tee.img
fastboot flash md1img_a md1img.img
fastboot flash spmfw_a spmfw.img
fastboot flash scp_a scp.img
fastboot flash sspm_a sspm.img
fastboot flash cam_vpu1_a cam_vpu1.img
fastboot flash cam_vpu2_a cam_vpu2.img
fastboot flash cam_vpu3_a cam_vpu3.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtb_a dtb.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash -u system_a system.img_sparsechunk.1
fastboot flash -u system_a system.img_sparsechunk.2
fastboot flash -u system_a system.img_sparsechunk.3
fastboot flash -u system_a system.img_sparsechunk.4
fastboot flash -u system_a system.img_sparsechunk.5
fastboot flash -u system_a system.img_sparsechunk.6
fastboot flash -u system_a system.img_sparsechunk.7
fastboot flash -u system_a system.img_sparsechunk.8
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash -u system_b system_other.img_sparsechunk.1
fastboot flash vendor_a vendor.img
fastboot reboot
I already tried to flash the boot.img using boot_a and boot_b
I hope that someone could help me, I would be very grateful
DoctorStrange007 said:
Hi Juan
Very simple to solve. In the bootloader with the side buttons go to find recovery, in recovery the droid will appear, hold the Power button and with it pressed press up on the volume and hit factory reset . If that doesn't work what I think is impossible ,because your bootloader is blocked only using midiatek's flash tool
Click to expand...
Click to collapse
Thanks for the fast response, but my phone goes back to the fastboot menu after attempting to get in the recovery.
Is there any way I can get my hands on a scatter file, I didn't find one online or where I can contact someone who is willing to help?
same problem
JuanChoF23 said:
Thanks for the fast response, but my phone goes back to the fastboot menu after attempting to get in the recovery.
Is there any way I can get my hands on a scatter file, I didn't find one online or where I can contact someone who is willing to help?
Click to expand...
Click to collapse
im also stuck on fastboot, tried to flash firmware but didnt work
EDIT: can someone help me find the apropiate rom/firmware for my device:
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-dd9cedf-191003
(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: ZY326R9C9F
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 520DE472090CB2D5000000000000
(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: 11-04-2019
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 10 21: 4:55 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMD29.70-7
(bootloader) ro.build.fingerprint[1]: 0/a51aa:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.51.85.lima_32.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
(bootloader) version-baseband: MT6771_V16.03.01.88R
(bootloader) kernel.version[0]: Linux version 4.4.146+ ([email protected]
(bootloader) kernel.version[1]: 151) (gcc version 4.9.x 20150123 (prerel
(bootloader) kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Mon Nov 18
(bootloader) kernel.version[3]: 20:12:45 CST 2019
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(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
finished. total time: 0.188s
youtube.com/watch?v=svtPdIVoloE
Related
Hello,
I have a problem with may XT1789-06.
I have flash the baseband from XT1789-04 from this post: https://forum.xda-developers.com/showpost.php?p=76123350&postcount=2
So the Sim Card are found, but I have noch Mobile connection.
So I Think, it's Easy, you can flash NASH_RETAIL_8.0.0_OPX27.109-34_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml with
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
and all it's fine.
No, so i have no baseband, no Sim Cards and no Wlan. I Flash only the modem.img from 1789-04, baseband is working without mobile connection
My fastboot getvar all at the last state
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-641a15b-171206
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224GXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 82CA716E
(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: 35651808XXXX
(bootloader) meid:
(bootloader) date: 09-07-2017
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5986A
(bootloader) battery-voltage: 4380
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.10.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01M NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g6174029 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Dec 6 17:42:00 CST 2017
(bootloader) git:abl: MBM-3.0-nash_retail-641a15b-171206
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-171206
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-171206
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-171206
(bootloader) git:tz: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:cmnlib: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:storsec: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) git:prov: MBM-3.0-nash_retail-7d478e6-171206
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(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: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.280s
I have do all I can't find, I work since 2 day's on this problem, I coudn't find a solution. I don't know with detail what I have do, so many Tut have "play it".
I think this is the main Issus. Always was unknown Baseband if I flash, flash I the modem.img from -04, baseband found. What I havn't du blankflash, without a Tut this is to dagoures for me I think.
Can everyone send me a backup from a retail XT1789-06?
Or have anyone another solution?
So long...
This files I need, I think.
Code:
abl.img
bluetooth.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dto.img
fsg.img
hyp.img
keymaster.img
modem.img
pmic.img
prov.img
rpm.img
storsec.img
tz.img
xbl.img
did you get it to work any how?
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!
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?
Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.
Here's all the variables if that's helpful:
(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: 6
(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: ZL4223V3D5
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 3572CA9F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) meid:
(bootloader) date: 08-29-2018
(bootloader) sku: XT1922-2
(bootloader) carrier_sku: XT1922-2
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 5 11:34:57 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter_n/aljeter_n:9/PPP
(bootloader) ro.build.fingerprint[1]: S29.55-35-18-7/6a0d0:user/release-
(bootloader) ro.build.fingerprint[2]: 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_EMEA_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: eegb
(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.152s
Click to expand...
Click to collapse
xt123xt said:
Hi. I've unlocked my phone for flashing and tried to install different ROMs, but nothing works.
My device is XT1922-2 JETER and I thought I'm having issues because I tried to install aljeter (as I can't find any jeter for XT1922-2..)
I tried to install different ROMs from TWRP, and even if it didn't give me any errors my phone was keeping loading into bootloader. Tried to use "fastboot oem fb_mode_clear" command but it didn't help.
Help me please, as I have no ideas what to do next and how to fix it. I don't know how to leave bootloop and make phone to load system.
Click to expand...
Click to collapse
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Ruben8ap said:
The model XT1922-2 is ALJETER , try to install Stock by fastboot from this link you can get it
Click to expand...
Click to collapse
Thank you for your reply.
It gave me an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system aljeter.zip
target reported max download size of 535822336 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 411641469 is not a multiple of the block size 4096
sending sparse 'system' 1/3 (523260 KB)...
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 947459709 is not a multiple of the block size 4096
OKAY [ 17.139s]
writing 'system' 1/3...
(bootloader) Invalid sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.145s
Click to expand...
Click to collapse
Try these https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETEU/
I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.
xt123xt said:
I tried, didn't work.
In the variables it says JETER.
(bootloader) product: jeter
(bootloader) board: jeter
I suppose XT1922-2 JETER could be a version which is exclusive to the UK.
Click to expand...
Click to collapse
Download this file --> https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Then you open the CMD and put in fastboot devices and the phone code should appear, of course the phone should already be in fastboot mode for that moment.
If everything is in order you should copy these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Just select all then copy and paste them into the CMD and the stock installation process will start :fingers-crossed:
I suppose you've saved my phone. Thank you very much!
Hi, I carried out the instruction as given above by Ruben8ap, on my XT1922-2 Aljeter Moto G6 Play phone, and have recovered my phone, so I can boot into the OS, but I have lost access to Fastboot and TWRP, etc. So, I now have a phone that is stuck with this OS and no way of gaining root access or anything else. My bootloader says AP Fastboot Flash Mode (Secure). I cannot flash anything from the stock recovery on the SD card. Can anyone advise how I can get out of this state?
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX64MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322Q2DZQ
(bootloader) cid: 0x00FF
(bootloader) channelid: 0x00
(bootloader) uid: 2CF0D7BF00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 359574083302191
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1795
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jul 16 9:14:51 UTC 1972"
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-7-6/4cc5a:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.montana.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_37.13.03.72u MONTANA_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g26d4309 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Jun 26 06:06:58 CDT
(bootloader) kernel.version[3]: 2019
(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=9a0b157
(bootloader) cmnlib.git: git=9a0b157
(bootloader) cmnlib64.git: git=9a0b157
(bootloader) prov.git: git=9a0b157
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: unknown
(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.094s
deepa007 said:
(bootloader) reason: Reboot mode set to fastboot
Click to expand...
Click to collapse
this is it
did you use a script to flash stock or did you flash all parts step by step?
at the beginning there is a
fastboot oem fb_mode_set this means fastboot always reboots to bootloader/fastboot to make sure all is done before reboot to system
at the end, when all files are flashed and all /data /cache etc is erased there is a
fastboot oem fb_mode_clear to clear the lock
fastboot reboot
done
zitronenmelissa said:
this is it
did you use a script to flash stock or did you flash all parts step by step?
at the beginning there is a
fastboot oem fb_mode_set this means fastboot always reboots to bootloader/fastboot to make sure all is done before reboot to system
at the end, when all files are flashed and all /data /cache etc is erased there is a
fastboot oem fb_mode_clear to clear the lock
fastboot reboot
done
Click to expand...
Click to collapse
yeah then also i stuck stuck on fastboot
mode
Try booting the phone to bootloader from fastboot command through system. Then you can copy the rom to internal storage and then flash directly.
deepa007 said:
yeah then also i stuck stuck on fastboot
mode
Click to expand...
Click to collapse
how did you flash stock? with a script or step by step? which firmware did you choose?
here is a good HowTo: https://forum.xda-developers.com/t/...latam-ora-playpl-retail-retru-trueth.3845848/
you can boot twrp with fastboot: fastboot boot twrp-name.img
then you should backup efs / persist to sdcard first if you haven't done that already.
then format data in wipe menu (agree with YES) and reboot
rdbhadri said:
Try booting the phone to bootloader from fastboot command through system. Then you can copy the rom to internal storage and then flash directly.
Click to expand...
Click to collapse
Please tell me the steps how to do