My Moto G5S is having multiple issues.
I unlocked the bootloader but now I receive a "bad key" message and the mobile phone reboots into the fastboot mode.
I re-flashed stock, same version ( OPPS28.65-37-7-2 ), but I does not relock the device, nor helps with the boot.
I tryied relocking the phone with the following commands:
Code:
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash boot boot.img
mfastboot oem lock
mfastboot reboot
But when flashing boot.img and oem.img, fastboot give me errors (Image signed with bad key).
Code:
version: 0.5
version-bootloader: moto-msm8937-BC.12
product: montana
board: montana
secure: yes
hwrev: P3
radio: 3
storage-type: emmc
emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
cpu: MSM8937
serialno: ZF522398CB
cid: 0x0032
channelid: 0x19
uid: 2F1B8B4200000000000000000000
securestate: flashing_unlocked
iswarrantyvoid: yes
max-download-size: 535822336
reason: Reboot mode set to fastboot
imei: ------ MY IMEI IS HERE OK ------
meid:
date: 03-07-2018
sku: XT1792
carrier_sku:
battid: SB18C18457
iccid:
cust_md5:
max-sparse-size: 268435456
current-time:
ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
ro.build.fingerprint[1]: S28.65-37-7-2/d0526:user/release-k
ro.build.fingerprint[2]: eys
poweroffalarm: 0
ro.build.version.full[0]: Blur_Version.28.251.2.montana.ret
ro.build.version.full[1]: ail.en.US
ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
version-baseband[0]: M8937_37.13.03.70R MONTANA_BRAZILDSDS_
version-baseband[1]: CUST
kernel.version[0]: Linux version 3.18.71-perf-g00b8a04 (hud
kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
kernel.version[2]: ) #1 SMP PREEMPT Fri Feb 1 11:05:40 CST
kernel.version[3]: 2019
sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
rpm.git: git=bd76357-dirty
tz.git: git=a0e13a9
devcfg.git: git=a0e13a9
keymaster.git: git=a0e13a9
cmnlib.git: git=a0e13a9
cmnlib64.git: git=a0e13a9
prov.git: git=a0e13a9
aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
frp-state: no protection (0)
ro.carrier: retbr
current-slot:
slot-suffixes: _a
slot-count: 1
slot-successful:_a: INVALID
slot-successful:_b: INVALID
slot-bootable:_a: INVALID
slot-bootable:_b: INVALID
slot-retry-count:_a: unknown
slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.063s
What can I do?
Try the following
mfastboot boot boot.img
command when the boot device goes to the unselect options and select unlock oem, make the bootloader unlock again and flash Rom
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?
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
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
ERROR: This package requires from an Android 8.1 stock ROM build.
Such a bug prevents me from updating the lineage-18.1-20220116-microG-cedric.zip image to a newer version,
e.g. lineage-18.1-20220301-microG-cedric.zip
Code:
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 SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZYxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AADB0F5700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:17:47 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.01u 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 (0)
(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.061s
I installed the stock rom via fastboot from the image:
CEDRIC_OPPS28.85_13_6_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
using this commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I installed TWRP, wiped the / system partition, / data, / cache,
then I installed lineage-18.1-20220116-microG-cedric.zip + Magisk.
the system is working fine.
However, the update to lineage-18.1-20220301-microG-cedric.zip stops on a bug with the firmware version.
I download lineage images from here:
cedric
Cheers
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
TheFixItMan said:
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Click to expand...
Click to collapse
Thank you very much for that firmware link... I was ready to give up.
Oddly, the official Motorola Repair tool does not install a Lineage-friendly version of the stock firmware.
If it helps any other noob, I used this site to install the stock firmware:
Install Stock Firmware on Moto G5 via Fastboot Commands
In this comprehensive tutorial, we will show you how to install stock firmware on Motorola Moto G5 via Fastboot commands and unbrick it.
www.droidwin.com
Hi
I Installed via fastboot:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After this operation, my Cedric does not have a unique IMEI number.
As a result, the SIM card does not work at all, I can only make emergency calls.
fastboot getvar all 2>&1| grep -i imei
(bootloader) imei: 356476085352435
I tried to fix IMEI according to this thread:
Moto G5 Cedric - Repair Imei = 0
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
forum.xda-developers.com
I did several times (after installing stock ROM, after installing LineageOS, after installing LineageOS-microg):
fastboot erase modemst1; fastboot erase modemst2 ; fastboot erase cache
Erasing 'modemst1' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'modemst2' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.020s
However, to no avail, the phone has no IMEI number on any SIM card.
It seems the XT1676 European version is more resistant to IMEI repair attempts.
Cheers
My IMEI was also zeroed by the stock ROM.
I tried using the recommendations in the following link, but I was ultimately unable to recover the IMEI from within the stock rom. Flashing LOS worked.
Moto g5 plus IMEI 0 after flashing anything? Read on!
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required! Prerequisites: U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on...
forum.xda-developers.com
Same here. Unable to recover IMEI for XT1676. The suggested procedure just does not work in this phone version with latest stock ROM OPP28.85-19-4-2.