Hi,
I got a Moto Z2 Force. It is a T-Mobile US ROM and I think also a TMO device. Not sure if it is a "test sample". I think I have somewhere seen something like "testkeys" or similar.
I bought this via internet - not in a Telekom Store.
So out of my experience from HTC devices - it could be anything.
I use this device in Europe, actually with a Telefonica SIM.
My device get´s a permanent update notification for a OTA which leads into an error: Cannot install OCXS27.1.4. I am actually on OCX27.1.3 BUILD
Note there is no "S" - whatever this means.
This device is not tached from my side. Though I don´t know what the seller has done before.
Baseband is: M8998TMO_20207.117.02.41.02R NUS
So I did not root the device.
There is no unlocked Bootloader, and I do not see the point
Patchlevel is sep. the first 2018
I would like to update to the latest official TMO ROM, shouldn´t be too big of an issue.
On Huawei Devices I updated the OTA manually, with no issues and fast. Or a complete official ROM over an older one.
HTC devices have been easy to update also, if you stay in its path, like official or testkeys, same with regions (regarding ROMs).
Is there a similar way for Motos? This is actually my first Motorola since my MPX 220 (IF anyone nows what I mean)
TMO is XT1789-04 which should be seen by the charging port. You can boot into bootloader and run the command fastboot getvar all to see the status of your phone. I suspect that it is in fact bootloader unlocked and has had a custom logo flashed to hide the bootloader unlocked warning, which also will keep an OTA from installing.
Post the output of the getvar command if you're not sure and I can help you sort it.
Hi,
sorry missed your reply because I did not get an notification. anyway:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-180905
(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: ZY224WX6BN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 1F21F01A
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356503081281xxx
(bootloader) meid:
(bootloader) date: 03-26-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4287
(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]: 27.109-51-11/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.4.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.02R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g15222f4 (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 Sep 5 05:41:24 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-180905
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180905
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180905
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180905
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(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: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.109s
I do not have any marking on my device, like the TMO XT ....
Does "PVT" has anything to say? Hardware Revision - I think.
Looks pretty clean, the easiest way would be to use lenovo moto smart assistant to upgrade.
Mtot Device manager says:
There is no noew software for my device.
Current version:
N/A
Not a good sign. The Software does´t read my device at all.
41rw4lk said:
Looks pretty clean, the easiest way would be to use lenovo moto smart assistant to upgrade.
Click to expand...
Click to collapse
So I actually misunderstood the Moto Software tool you ment. When I googled I found "Motorola Device Manager". You ment - obviously "Lenovo moto smart assistant", which, interestingly is a totally different software. Maybe this has something to do with regions. I don´t know.
To round up this thread:
I read twice, searched the Tool you ment (the US version, although I use an EU SIM), it installed nicely and connected correctly to my device. It found the latest update and updated directly to the lastet. From .4 to version .7. So the file had a size of 2GB.
Although the software (LMSA) says differently, it does NOT wipe my device.
Edit: Connection to my PC did NOT work via USB 3.0! Interestingly it worked via a keyboard extend USB Hub 2.0 though.
Related
Hello guys,
Looks like I've screwed up very badly. After an update to android 9 Pie i wanted to downgrade back to 8 following the guide on youtube (I can't post links yet)
I FORGOT to unlock the bootloader and ran the flash. And it went wrong. Now the phone freezes trying to connect to a Wi-Fi (i can't skip it) and I'm clueless what to do next. Maybe you can help me?
The data i have available on the bootloader:
BL: MBM-2.1-aljeter_retail-02dae09-190122
Baseband: <not found>
Product/Variant: jeter XT1922-3 32GB P4
Serial Number {i dont think it's necessary}
CPU: {i think irrelevant}
eMMC: {i think irrelevant}
DRAM: {i think irrelevant}
Console [NULL]: null
Tools Mode Config: DSABLED
Battery OK
oem_locked
Medawk said:
Hello guys,
Looks like I've screwed up very badly. After an update to android 9 Pie i wanted to downgrade back to 8 following the guide on youtube (I can't post links yet)
I FORGOT to unlock the bootloader and ran the flash. And it went wrong. Now the phone freezes trying to connect to a Wi-Fi (i can't skip it) and I'm clueless what to do next. Maybe you can help me?
The data i have available on the bootloader:
BL: MBM-2.1-aljeter_retail-02dae09-190122
Baseband: <not found>
Product/Variant: jeter XT1922-3 32GB P4
Serial Number {i dont think it's necessary}
CPU: {i think irrelevant}
eMMC: {i think irrelevant}
DRAM: {i think irrelevant}
Console [NULL]: null
Tools Mode Config: DSABLED
Battery OK
oem_locked
Click to expand...
Click to collapse
EDIT: I managed to get this info too:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) product: jeter
(bootloader) board: jeter
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(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: ZL62225459
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 8122A81100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351844090939113
(bootloader) meid:
(bootloader) date: 05-18-2018
(bootloader) sku: XT1922-3
(bootloader) carrier_sku: XT1922-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Mar 28 11:32:34 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/aljeter/aljeter:9/PPPS29.
(bootloader) ro.build.fingerprint[1]: 55-25-2/06dbf:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.2.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: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-gccbc3e0 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Mar 28 06:11:01 CDT 2019
(bootloader) sbl1.git: MBM-2.1-aljeter_retail-b867b3e-190122
(bootloader) rpm.git: MBM-2.1-aljeter_retail-099a494-dirty-190328
(bootloader) tz.git: MBM-2.1-aljeter_retail-f917b84-dirty-190328
(bootloader) devcfg.git: MBM-2.1-aljeter_retail-f917b84-dirty-190328
(bootloader) keymaster.git: MBM-2.1-aljeter_retail-f917b84-190328
(bootloader) cmnlib.git: MBM-2.1-aljeter_retail-f917b84-190328
(bootloader) cmnlib64.git: MBM-2.1-aljeter_retail-f917b84-190328
(bootloader) prov.git: MBM-2.1-aljeter_retail-f917b84-dirty-190328
(bootloader) aboot.git: MBM-2.1-aljeter_retail-02dae09-190122
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.074s
Did you already try to unlock the bootloader. You could then fastboot flash a stock rom from here https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/
It worked finally, I was confused which software is the right one. Thanks!
Medawk said:
Hello guys,
Looks like I've screwed up very badly. After an update to android 9 Pie i wanted to downgrade back to 8 following the guide on youtube (I can't post links yet)
I FORGOT to unlock the bootloader and ran the flash. And it went wrong. Now the phone freezes trying to connect to a Wi-Fi (i can't skip it) and I'm clueless what to do next. Maybe you can help me?
The data i have available on the bootloader:
BL: MBM-2.1-aljeter_retail-02dae09-190122
Baseband: <not found>
Product/Variant: jeter XT1922-3 32GB P4
Serial Number {i dont think it's necessary}
CPU: {i think irrelevant}
eMMC: {i think irrelevant}
DRAM: {i think irrelevant}
Console [NULL]: null
Tools Mode Config: DSABLED
Battery OK
oem_locked
Click to expand...
Click to collapse
My moto g6 play 1922-5 ta so too. Can you solve it?
Hello and thanks in advance to everyone for your suppport. Its been two weeks since my z2 force bricked, last month ive received official AMX OTA Android Pie Update, since the last update arrived my phone started to shutdown ocaionally when ive used the double shake to open camera and some times with no reason, i didnt worry because my phone on that was totally stock with locked bootloader and the OTA was the provided from my carrier.
Also Ive used BlankFlash with no errors > flash stock oreo no errors > stock pie no errors > no boot > black screen and same results with LineageOs.
Since that my phone was able to boot on Stock 1 time and LineageOs 1 time by luck. But ive restarted it and the issue still there and i cant boot again. So right now im unbootable (Only lineageOs for few seconds but it shutdown on Hello Setup Screen, as ive mentioned before here i can see the sim signal bars or wifi ok)I dont know but i think ive corrupted some A or B slot, ive already checked a lot of threads but none can fix it. Here I leave my getvar-all specs hoping for some help.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-477a1f5-190327
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(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 (4)
(bootloader) serialno: ZY224FXGKV
(bootloader) cid: 0x0032
(bootloader) channelid: 0x03
(bootloader) uid: DDE2C032
(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: :silly:
(bootloader) meid:
(bootloader) date: 08-31-2017
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3675
(bootloader) iccid:
(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-g8f2ad85 (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 Mar 27 15:45:03 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-477a1f5-190327
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-190327
(bootloader) gitmic: MBM-3.0-nash_retail-9869834-190327
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-190327
(bootloader) git:tz: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) git:devcfg: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) git:cmnlib: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) git:keymaster: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) git:storsec: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) gitrov: MBM-3.0-nash_retail-4b26fc4-190327
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxmx
(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: 7
(bootloader) slot-retry-count:_b: 6
Hi,
I have got the golden retcn version of the Moto Z2 Force. Unfortunately, it is still on Android version 8, and I would like to change this. Is this possible? If so, could you please point me in the right direction? I do not want Lineage OS, only the updated stock rom. And I do not care much about SafetyNet.
SKU: XT1789-05
Android 8.0.0
Software channel: retcn
Thanks,
Mark
mark_14 said:
Hi,
I have got the golden retcn version of the Moto Z2 Force. Unfortunately, it is still on Android version 8, and I would like to change this. Is this possible? If so, could you please point me in the right direction? I do not want Lineage OS, only the updated stock rom. And I do not care much about SafetyNet.
SKU: XT1789-05
Android 8.0.0
Software channel: retcn
Thanks,
Mark
Click to expand...
Click to collapse
The golden rule when it comes to pie is, don't flash any pie firmware that isn't for your variant. Once you upgrade to pie modems you can't go back to oreo, and if the modem isn't right you won't have a baseband and possibly no way to fix it. That being said, many of the retail variants have the same firmware so it might be possible for you to upgrade properly. Boot into bootloader and run getvar command, then post the results so we can see what you're on.
PHP:
adb reboot bootloader
fastboot getvar all
fastboot reboot
41rw4lk said:
Boot into bootloader and run getvar command, then post the results so we can see what you're on.
Click to expand...
Click to collapse
Thanks for your fast response. These are the results:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retcn-013cc51-180201
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: CHINA
(bootloader) storage-type: UFS
(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 (4)
(bootloader) serialno: <removed>
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: 5DE0141F
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: logging
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: <removed>
(bootloader) meid:
(bootloader) date: 03-29-2018
(bootloader) sku: XT1789-05
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3691
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-52-10/12:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.27.411.12.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.01R NCD
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g33eec99 (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]: Sun Nov 4 09:34:03 CST 2018
(bootloader) abl.git: MBM-3.0-nash_retcn-013cc51-180201
(bootloader) xbl.git: MBM-3.0-nash_retcn-4ee2102-180201
(bootloader) pmic.git: MBM-3.0-nash_retcn-4ee2102-180201
(bootloader) rpm.git: MBM-3.0-nash_retcn-d3e45a4-180201
(bootloader) tz.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) hyp.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) devcfg.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) cmnlib.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) cmnlib64.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) keymaster.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) storsec.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) prov.git: MBM-3.0-nash_retcn-f4e3658-dirty-180201
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retcn
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _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
I join the question. I have exactly the same results from 'fastboot getvar all ' command. Also i have compilation number OPXS27.109-34-21, which is different than NASH_RETCN firmware on lolinet
forgottennick said:
I join the question. I have exactly the same results from 'fastboot getvar all ' command. Also i have compilation number OPXS27.109-34-21, which is different than NASH_RETCN firmware on lolinet
Click to expand...
Click to collapse
This should be a newer firmware version for your device.
https://mirrors.lolinet.com/firmware/moto/nash_retcn/official/RETCN/
XT1789-05_NASH_RETCN_8.0.0_OCX27.138-29_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Sent from my payton_sprout using XDA Labs
Hi
I got my mobile with Android 9 installed on my sprint (XT1789-03). I installed lineageOS 17.1 and worked fine without any issues. But after a month it starts rebooting randomly. So I tried flashing the update but this cause it not to boot and it goes to lineage animation and then reboots. So I installed Sprint Retail Android 8.0: XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It installed without any issues. But now my baseband is not found (written in bootloader). My wifi and sim not working.
Please anyone help me solve this issue
@Uzephi
Hasan Khurshid said:
Hi
I got my mobile with Android 9 installed on my sprint (XT1789-03). I installed lineageOS 17.1 and worked fine without any issues. But after a month it starts rebooting randomly. So I tried flashing the update but this cause it not to boot and it goes to lineage animation and then reboots. So I installed Sprint Retail Android 8.0: XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It installed without any issues. But now my baseband is not found (written in bootloader). My wifi and sim not working.
Please anyone help me solve this issue
Click to expand...
Click to collapse
Same problem here, but XT1789-04
IMEI shows up fastboot getvar, but in fastboot it says "Baseband: <not found>". Wifi doesn't work and the network mac address is 0200000000. Firmware is stuck at 8.0.0. I can flash and run any ROM (Lineage, stock) but Wifi nver works and baseband always says not round.
I've tried a dozen different NON-HLOS.bin files and flashalls and nothing will give me baseband back.
This doesn't work:
https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
ryazbeck said:
Same problem here, but XT1789-04
IMEI shows up fastboot getvar, but in fastboot it says "Baseband: <not found>". Wifi doesn't work and the network mac address is 0200000000. Firmware is stuck at 8.0.0. I can flash and run any ROM (Lineage, stock) but Wifi nver works and baseband always says not round.
I've tried a dozen different NON-HLOS.bin files and flashalls and nothing will give me baseband back.
This doesn't work:
https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
Click to expand...
Click to collapse
I hope you haven't tried any nonhlos that was not made for your mobile. Have you tried flashing the last AT&T firmware? If not, You can download from here: https://mirrors.lolinet.com/firmware/moto/nash/official/ATT/
@ryazbeck How did you lost your baseband?
@ryazbeck How did you lost your baseband?
Hasan Khurshid said:
@ryazbeck How did you lost your baseband?
Click to expand...
Click to collapse
I followed the official guide and after it was complete my baseband was dead. It seems the Lineage team has given a big **** you to Moto Z2 Force users
https://wiki.lineageos.org/devices/nash/install
---------- Post added at 04:59 PM ---------- Previous post was at 04:41 PM ----------
Hasan Khurshid said:
@ryazbeck How did you lost your baseband?
Click to expand...
Click to collapse
Hasan Khurshid said:
I hope you haven't tried any nonhlos that was not made for your mobile. Have you tried flashing the last AT&T firmware? If not, You can download from here: https://mirrors.lolinet.com/firmware/moto/nash/official/ATT/
Click to expand...
Click to collapse
Hasan, I finally got it to work using this guide
https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
The only difference is that I booted into stock recovery and formatted everything before using the updated Flashalls on the 27.1.7 TMO rom. Both of those files are attached at the thread I linked.
ryazbeck said:
I followed the official guide and after it was complete my baseband was dead. It seems the Lineage team has given a big **** you to Moto Z2 Force users
https://wiki.lineageos.org/devices/nash/install
Click to expand...
Click to collapse
Yes it seems like some people are having issues with LOS. One person on reddit also had similar problems with LOS. It's good to hear that your phone is in working condition again but mine is sprint so I can't follow that guide. Is your baseband showing now?
Hasan Khurshid said:
Yes it seems like some people are having issues with LOS. One person on reddit also had similar problems with LOS. It's good to hear that your phone is in working condition again but mine is sprint so I can't follow that guide. Is your baseband showing now?
Click to expand...
Click to collapse
Yep, it shows up now.
Have you tried using that guide with this firmware?
https://firmware.center/.zdrive/z_gdrive_viewer.php?ID=1nH3cofg7EK5KUFbKsnGbZsbagNzQQBcE
here's another download of the same firmware https://androidfilehost.com/?fid=746010030569960275
ryazbeck said:
Yep, it shows up now.
Have you tried using that guide with this firmware?
https://firmware.center/.zdrive/z_gdrive_viewer.php?ID=1nH3cofg7EK5KUFbKsnGbZsbagNzQQBcE
here's another download of the same firmware https://androidfilehost.com/?fid=746010030569960275
Click to expand...
Click to collapse
I can't go back to nougat as I am already on Oreo. So nougat modem will not work.
Hasan Khurshid said:
Hi
I got my mobile with Android 9 installed on my sprint (XT1789-03). I installed lineageOS 17.1 and worked fine without any issues. But after a month it starts rebooting randomly. So I tried flashing the update but this cause it not to boot and it goes to lineage animation and then reboots. So I installed Sprint Retail Android 8.0: XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It installed without any issues. But now my baseband is not found (written in bootloader). My wifi and sim not working.
Please anyone help me solve this issue
Click to expand...
Click to collapse
You are in dead end...
The pie baseband is not compatible with Oreo...
Do bankflash to save the life or go ahead to trash it out
Sent from my LG-LS997 using Tapatalk
cgigate said:
You are in dead end...
The pie baseband is not compatible with Oreo...
Do bankflash to save the life or go ahead to trash it out
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
It never had a pie baseband or modem. And I never flashed it. But still I can't get it to work. Also for blankflash I cannot go into edl mode. Stock roms are all working fine but without sim and wifi.
Hasan Khurshid said:
It never had a pie baseband or modem. And I never flashed it. But still I can't get it to work. Also for blankflash I cannot go into edl mode. Stock roms are all working fine but without sim and wifi.
Click to expand...
Click to collapse
If you insist "Stock roms are all working fine", then you don't need to do anything.
You lost baseband, you don't have any wireless things: no wifi, no mobile signals...
It is even cannot be a phone.....but may have Bluetooth...
When you fastboot , then you have EDL mode...
Sent from my LG-LS997 using Tapatalk
cgigate said:
If you insist "Stock roms are all working fine", then you don't need to do anything.
You lost baseband, you don't have any wireless things: no wifi, no mobile signals...
It is even cannot be a phone.....but may have Bluetooth...
When you fastboot , then you have EDL mode...
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
Sorry I meant stock roms boot up fine whereas custom roms like LOS can't boot up on my phone. Any solution for no wifi & sim?
fastboot oem blankflash command shows command restricted.
bro i can help you! you need to start the phone and then you need to enable oem unlock at the developer options it will be grayed out you will need another phone to share internet via bluetooth and connect your moto z2 force as its the only thing you can enable bluetooth after that just open the playstore login to your account and oem unlock will be available enable it and put your phone into bootloader mode unlock the bootloader flash the stock rom and restart the phone once its done
note: restart the phone after stock rom is done but without locking the bootloader
after that go to reset options at system settings then reset the phone and start the phone again and you will do this until you get wifi and sim once everything is working again now you can relock the bootloader and reset the phone and everything will be ok again, send pm if you need assistance because my english is not so good
Manuelmartad said:
bro i can help you! you need to start the phone and then you need to enable oem unlock at the developer options it will be grayed out you will need another phone to share internet via bluetooth and connect your moto z2 force as its the only thing you can enable bluetooth after that just open the playstore login to your account and oem unlock will be available enable it and put your phone into bootloader mode unlock the bootloader flash the stock rom and restart the phone once its done
note: restart the phone after stock rom is done but without locking the bootloader
after that go to reset options at system settings then reset the phone and start the phone again and you will do this until you get wifi and sim once everything is working again now you can relock the bootloader and reset the phone and everything will be ok again, send pm if you need assistance because my english is not so good
Click to expand...
Click to collapse
I appreciate that you want to help me. But my bootloader is already unlocked and I can flash stock roms.
Hasan Khurshid said:
I appreciate that you want to help me. But my bootloader is already unlocked and I can flash stock roms.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_sprint-ab41784-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SPRINT
(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: ZY224D2CB4
(bootloader) cid: 0x0032
(bootloader) channelid: 0x86
(bootloader) uid: 77D1F1DC
(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: xxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 08-28-2017
(bootloader) sku: XT1789-03
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4144
(bootloader) iccid: 89011202000056485193
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-23/
(bootloader) ro.build.fingerprint[1]: 113ea:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.23.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(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]: Fri Jul 5 09:27:21 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_sprint-ab41784-190705
(bootloader) git:xbl: MBM-3.0-nash_sprint-9869834-190705
(bootloader) gitmic: MBM-3.0-nash_sprint-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_sprint-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:hyp: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:devcfg: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:cmnlib: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:keymaster: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:storsec: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) gitrov: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: sprint
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.200s
Hasan Khurshid said:
What does getvar all say?
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_sprint-ab41784-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SPRINT
(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: ZY224D2CB4
(bootloader) cid: 0x0032
(bootloader) channelid: 0x86
(bootloader) uid: 77D1F1DC
(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: xxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 08-28-2017
(bootloader) sku: XT1789-03
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4144
(bootloader) iccid: 89011202000056485193
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-23/
(bootloader) ro.build.fingerprint[1]: 113ea:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.23.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(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]: Fri Jul 5 09:27:21 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_sprint-ab41784-190705
(bootloader) git:xbl: MBM-3.0-nash_sprint-9869834-190705
(bootloader) gitmic: MBM-3.0-nash_sprint-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_sprint-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:hyp: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:devcfg: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:cmnlib: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:keymaster: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:storsec: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) gitrov: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: sprint
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.200s
Click to expand...
Click to collapse
Normally I refer to this site
https://mirrors.lolinet.com/firmware/moto/nash/official/Sprint/
This is the newest version on that site for Sprint is
XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Which is Android 8
You have PPX29.159-23/.... Which is Android 9
So you must have flashed a Retail version or the site hasn't been updated.
You could try Lmsa's flash rescue option
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
And see which firmware version it wants to flash.
If it can determine what firmware is needed you will be given a chance to download it and then asked if you want to flash.
If you aren't sure if it's right,
copy the full filename and post it here.
Sent from my payton_sprout using XDA Labs
Hasan Khurshid said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_sprint-ab41784-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SPRINT
(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: ZY224D2CB4
(bootloader) cid: 0x0032
(bootloader) channelid: 0x86
(bootloader) uid: 77D1F1DC
(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: xxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 08-28-2017
(bootloader) sku: XT1789-03
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4144
(bootloader) iccid: 89011202000056485193
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-23/
(bootloader) ro.build.fingerprint[1]: 113ea:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.23.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (hud
(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]: Fri Jul 5 09:27:21 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_sprint-ab41784-190705
(bootloader) git:xbl: MBM-3.0-nash_sprint-9869834-190705
(bootloader) gitmic: MBM-3.0-nash_sprint-9869834-190705
(bootloader) git:rpm: MBM-3.0-nash_sprint-b13e14f-190705
(bootloader) git:tz: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:hyp: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:devcfg: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:cmnlib: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:keymaster: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) git:storsec: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) gitrov: MBM-3.0-nash_sprint-9059a28-190705
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: sprint
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.200s
Click to expand...
Click to collapse
you flashed a wrong version there is no pie for sprint variant
Hi.
I've just bought an unlocked Austarlian model Moto G30. I'd like to install Magisk but I'm having trouble locating a stock rom. No roms are found either by searching, normal connection or fastboot connection by the Lenovo Rescue and Smart Assistance app. A dump from fastboot reads as follows (with serial numbers, IMEIs omitted):
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) product: caprip
(bootloader) board: caprip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: *****
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: 1AFA7FED
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *****
(bootloader) imei2: *****
(bootloader) meid:
(bootloader) date: 07-21-2021
(bootloader) sku: XT2129-2
(bootloader) carrier_sku: XT2129-2
(bootloader) battid: SB18C98449
(bootloader) battery-voltage: 3976
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retapac
(bootloader) ro.build.fingerprint[0]: motorola/caprip_retailn/caprip:11/
(bootloader) ro.build.fingerprint[1]: RRC31.Q1-3-34-1/7ff77b:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-01800-KAMORTA.0
(bootloader) version-baseband[0]: HAK10_18.534.02.65R CAPRIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue F
(bootloader) kernel.version[4]: eb 9 10:48:17 CST 2021
(bootloader) git:xbl: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:xbl_config: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:abl: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) git:rpm: MBM-3.0-caprip_retail-f43cd45-210209
(bootloader) git:tz: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:hyp: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:devcfg: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:keymaster: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:storsec: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:uefisecapp: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) gitrov: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:qupfw: MBM-3.0-caprip_retail-349f4d1-210209
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PBEP
(bootloader) primary-display: djn_nt36525c_652_vid_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.244s
So far I've only managed to find one site (under a couple different names/addresses) that has the (bootloader) ro.build.fingerprint[1] and (bootloader) ro.build.fingerprint[2] strings of:
RRC31.Q1-3-34-1/7ff77b:user/release-keys
It doesn't look like the file has been downloaded at all so I'm a little dubious. Can anyone possibly point me to a surer source, or another stock rom that has worked with an Australian moto g30 and Magisk?
Cheers.
cedwich said:
Hi.
I've just bought an unlocked Austarlian model Moto G30. I'd like to install Magisk but I'm having trouble locating a stock rom. No roms are found either by searching, normal connection or fastboot connection by the Lenovo Rescue and Smart Assistance app. A dump from fastboot reads as follows (with serial numbers, IMEIs omitted):
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) product: caprip
(bootloader) board: caprip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: *****
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: 1AFA7FED
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *****
(bootloader) imei2: *****
(bootloader) meid:
(bootloader) date: 07-21-2021
(bootloader) sku: XT2129-2
(bootloader) carrier_sku: XT2129-2
(bootloader) battid: SB18C98449
(bootloader) battery-voltage: 3976
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retapac
(bootloader) ro.build.fingerprint[0]: motorola/caprip_retailn/caprip:11/
(bootloader) ro.build.fingerprint[1]: RRC31.Q1-3-34-1/7ff77b:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-01800-KAMORTA.0
(bootloader) version-baseband[0]: HAK10_18.534.02.65R CAPRIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue F
(bootloader) kernel.version[4]: eb 9 10:48:17 CST 2021
(bootloader) git:xbl: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:xbl_config: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:abl: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) git:rpm: MBM-3.0-caprip_retail-f43cd45-210209
(bootloader) git:tz: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:hyp: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:devcfg: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:keymaster: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:storsec: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:uefisecapp: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) gitrov: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:qupfw: MBM-3.0-caprip_retail-349f4d1-210209
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PBEP
(bootloader) primary-display: djn_nt36525c_652_vid_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.244s
So far I've only managed to find one site (under a couple different names/addresses) that has the (bootloader) ro.build.fingerprint[1] and (bootloader) ro.build.fingerprint[2] strings of:
RRC31.Q1-3-34-1/7ff77b:user/release-keys
It doesn't look like the file has been downloaded at all so I'm a little dubious. Can anyone possibly point me to a surer source, or another stock rom that has worked with an Australian moto g30 and Magisk?
Cheers.
Click to expand...
Click to collapse
I think you know this but
You look for these lines
Code:
sku: XT2129-2
ro.carrier: retapac
product: caprip
ro.build.fingerprint:...RRC31.Q1-3-34-1/...
and
Code:
imei: *****
imei2: *****
Means you have Dual sim, there may be firmware that is for a single sim, you do not want to use that.
There a few sources for stock moto firmware.
I prefer LMSA, it is the official Moto flashing program for Windows
The 2 other sources I like are run by the same people
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
and
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Looks like you are running an older build and lolinet may have removed it already, you could use a newer version
you will need to flash the full firmware.
Moto Update Tracker has this
Codename: #capri
Carrier(s): Australia
Phone Model(s): XT2127-2-DS/PAMN0016AU
Version: RRBS31.Q1-3-34-1-2
Android: 11
Download: Here
Click to expand...
Click to collapse
CAPRI_RETAIL_RRBS31.Q1-3-34-1-2_subsidy-DEFAULT_regulatory-XT2127-2-APEM-SAR_CFC.xml.zip
again if you have a Windows PC I recommend LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
I think you know this but
You look for these lines
Code:
sku: XT2129-2
ro.carrier: retapac
product: caprip
ro.build.fingerprint:...RRC31.Q1-3-34-1/...
and
Code:
imei: *****
imei2: *****
Means you have Dual sim, there may be firmware that is for a single sim, you do not want to use that.
There a few sources for stock moto firmware.
I prefer LMSA, it is the official Moto flashing program for Windows
The 2 other sources I like are run by the same people
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
and
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Looks like you are running an older build and lolinet may have removed it already, you could use a newer version
you will need to flash the full firmware.
Moto Update Tracker has this
CAPRI_RETAIL_RRBS31.Q1-3-34-1-2_subsidy-DEFAULT_regulatory-XT2127-2-APEM-SAR_CFC.xml.zip
again if you have a Windows PC I recommend LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Awesome, many thanks for your help and suggestions, i'll definately take them on board. I tried the LMSA tool straight up and it couldn't find any compatable stock roms via either usb debug or fastboot. I also couldn't find anything searching by name. I did trying searching a few sites for stock roms but the phone doesn't show system updates as being available so i didn"t think to search on more recent versions. *blushes* Thanks again for your digging, you've hopefully helped save me a few more grey hairs!