help me!!!
I did a youtube tutorial on how to install rom stock on my moto g7 power and now the phone does not exit fastboot mode.
Before the tutorial the phone worked normally, but I went to give a relative then prefer to install the rom stock factory, but it did not work.
In the installation of rom it said:
'' SMM: Android image roll back: 1.7 in red. ''
Now after Setup says:
'' SMM: Android image roll back: 5.7 in red
failed to validity boot image in purple
ERROR: Failed to pass validaton, backup to fastboot ''.
Tried to use Lenovo Moto Smart Assistant and this error:
'' Failed to match the connected device.
Please plug it out, and try again. ''
My device locked bootloader
my getvar all info:
C: \ Users \ Luanm \ Desktop \ platform-tools> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV = 08 PV = 01 FV = 0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE = 8Gb M5 = 01 M6 = 06 M7 = 00 M8 = 5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZF5225C2PW
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 3B8FE9F300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 354128100724492
(bootloader) meid:
(bootloader) date: 01-24-2019
(bootloader) sku: XT1955-1
(bootloader) carrier_sku: XT1955-1
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Aug 5 22:26:10 UTC 2019"
(bootloader) ro.build.fingerprint [0]: motorola / ocean_t / ocean_t: 9 / PPOS29.
(bootloader) ro.build.fingerprint [1]: 114-134-2 / 0d27: user / release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full [0]: Blur_Version.29.281.2.ocean.retai
(bootloader) ro.build.version.full [1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version [0]: Linux version 4.9.112-perf + (hudsoncm @ il
(bootloader) kernel.version [1]: clbld34) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version [2]: erelease) (GCC)) # 1 SMP PREEMPT Sun Aug
(bootloader) kernel.version [3]: 4 11:49:12 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a, _b
(bootloader) slot count: 2
(bootloader) slot-successful: _a: No
(bootloader) slot-successful: _b: No
(bootloader) slot-bootable: _a: No
(bootloader) slot-bootable: _b: Yes
(bootloader) slot-retry-count: _a: 0
(bootloader) slot-retry-count: _b: 5
all: listed above
finished. total time: 0.083s
Help me please!!!!!!!!!
English is not my native language. :Boa:
You probably tried to downgrade or update with a wrong channel firmware with your oem locked. You can't do that. You'll need install the same firmware (can be a up version) and channel (retbr) that you're using before.
mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
MurkBRA said:
You probably tried to downgrade or update with a wrong channel firmware with your oem locked. You can't do that. You'll need install the same firmware (can be a up version) and channel (retbr) that you're using before.
mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
Click to expand...
Click to collapse
Thanks for the answer.
I tried to do what you told me but it did not work, I saw that when I button to install rom stock appears the error in '' boot.img '' and '' dtbo.img ''. I used rom Retail and RETBR but neither were.
I even modified flashfile to remove the installation of boot.img and dtbo.img but it didn't work out.
at the end of the reboot appears written:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the software repair Assistant.
AP Fastboot Flash Mode (Secure)
SSM: Android image roll back: 5,7
failed to validade boot image
ERROR: failed to pass validaton. backup to fastboot
If you had the newer version of August you have to wait for the new firmware to come out, PPO29.114-134-2. So far, not available for download.
MurkBRA said:
If you had the newer version of August you have to wait for the new firmware to come out, PPO29.114-134-2. So far, not available for download.
Click to expand...
Click to collapse
thank you, when you have released this newer version I will install and talk if it worked.
Good news, there's a new release today:
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
Download the RSD Lite and just flash the firmware.
MurkBRA said:
Good news, there's a new release today:
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
Download the RSD Lite and just flash the firmware.
Click to expand...
Click to collapse
Thank you very much, I did what I said about using rsd lite and the new rom and managed to resurrect my cell phone. :victory:
Hola amigos.. tengo el mismo problema con mi moto G7 Power XT1955-2 en el link que dejaron solo vi la Version XT1955-1 hay algun problema si intento instalar esa que esta publicada???
Related
today my Moto E won't start. recently my mobile flashed a bug which i ignored now it is stuck to Motorola logo only..
what should I do please help..Please send me the details of how to unlock my Moto E XT1022.
Then I tried to unlock it and was unable..I'm attaching those results hope it helps..
HELP!!!
H:\Android\sdk\platform-tools> fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 3A55640206907587#5A583142333358
(bootloader) 364E5600585431303232000000#8D5A
(bootloader) 110BB311F3B8D086226093D55305A8B
(bootloader) 52E26#97B9FE0412000000000000000
(bootloader) 0000000
OKAY [ 0.267s]
finished. total time: 0.267s
H:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 500E
(bootloader) product: condor
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x5
(bootloader) emmc: 4GB Hynix REV=06 PRV=05 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8210 CS
(bootloader) serialno: ZX1B34RQXN
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 97B9FE0412000000000000000000
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 299892736
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355462060095778
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 16:27:51 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/condor_retaildsds/condor_
(bootloader) ro.build.fingerprint[1]: umtsds:5.1/LPCS23.13-34.8-3/3:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.201.3.condor_reta
(bootloader) ro.build.version.full[1]: ildsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g70ad15f ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Feb 22 10:19:39 CST 2016
(bootloader) sdi.git: git=MBM-NG-V50.0E-0-g3ccd862
(bootloader) sbl1.git: git=MBM-NG-V50.0E-0-g20700d2
(bootloader) rpm.git: git=MBM-NG-V50.0E-0-gcebb121
(bootloader) tz.git: git=MBM-NG-V50.0E-0-g65c6b0f
(bootloader) aboot.git: git=MBM-NG-V50.0E-0-g4ed7eaf
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.126s
3A55640206907587#5A583142333358364E5600585431303232000000#8D5A110BB311F3B8D086226093D55305A8B52E26#97B9FE04120000000000000000000000
Copy only this much to get unlock key.
Thanks for the reply. I tried it but the website said that my mobile does not qualify for bootloader unlocking..
I posted lenovo forum,still no reply..
what should i do to reinstall a fresh os??
Ujwal Agrawal said:
3A55640206907587#5A583142333358364E5600585431303232000000#8D5A110BB311F3B8D086226093D55305A8B52E26#97B9FE04120000000000000000000000
Copy only this much to get unlock key.
Click to expand...
Click to collapse
Same problem for me
Same happened with me but fortunately i got the key and unlocked the bootloader but now when i am trying to flash stock kitkat rom with mfastboot its failed every time.
is there any way to install TWRP in this case ?? Please
Akil Imran said:
Same happened with me but fortunately i got the key and unlocked the bootloader but now when i am trying to flash stock kitkat rom with mfastboot its failed every time.
is there any way to install TWRP in this case ?? Please
Click to expand...
Click to collapse
If you have unlocked your bootloader then first flash the latest twrp v3.0.2.0 . After flashing twrp then go to recovery from your phone. Clean the rom which is installed and then flash the Rom.
Phone is not turning on
Ankit_29 said:
If you have unlocked your bootloader then first flash the latest twrp v3.0.2.0 . After flashing twrp then go to recovery from your phone. Clean the rom which is installed and then flash the Rom.
Click to expand...
Click to collapse
Thanks bro but my phone is not turning on it stuck on motorola unlock bootlaoder sign.. is any way to install twrp in this case if yes plz help
Akil Imran said:
Thanks bro but my phone is not turning on it stuck on motorola unlock bootlaoder sign.. is any way to install twrp in this case if yes plz help
Click to expand...
Click to collapse
It seems that you have soft bricked your phone.
Just flash twrp through mfastboot note that android debugging must be on.
For better step by step instructions check this video on YouTube
The video is too long but well explained.
Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 CST 2020
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
finished. total time: 0.180s
Thank you!
claudiusuflea said:
Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 CST 2020
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(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
all: listed above
finished. total time: 0.180s
Thank you!
Click to expand...
Click to collapse
You cannot downgrade firmware with a locked bootloader.
There is no Android 10 for Dean/RetEU
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
There will be no fix until there is Android 10 firmware for your device.
sd_shadow said:
You cannot downgrade firmware with a locked bootloader.
There is no Android 10 for Dean/RetEU
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
There will be no fix until there is Android 10 firmware for your device.
Click to expand...
Click to collapse
Also tried the beta for android 10 for deen-reteu, retail, retbr, and everything I found on the internet, didn't work, once android 10 stable for reteu would roll out is this phone fixable by the fastboot flashing method?
Also LMSA deleted my ro.build.version.full, it appears null on the getvar
claudiusuflea said:
Also tried the beta for android 10 for deen-reteu, retail, retbr, and everything I found on the internet, didn't work, once android 10 stable for reteu would roll out is this phone fixable by the fastboot flashing method?
Also LMSA deleted my ro.build.version.full, it appears null on the getvar
Click to expand...
Click to collapse
You may have flashed so many incompatible versions there is no fixing
Sent from my ocean using XDA Labs
sd_shadow said:
You may have flashed so many incompatible versions there is no fixing
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
I guess i have to wait or take it to a technician if the stable android 10 won't work, my wrong I didn't unlock the bootloader. Thank you very much!
sd_shadow said:
you cannot downgrade firmware with a locked bootloader.
There is no android 10 for dean/reteu
https://mirrors.lolinet.com/firmware/moto/deen/official/reteu/
there will be no fix until there is android 10 firmware for your device.
Click to expand...
Click to collapse
reteu got 10
there was 1 more ota after that for march update
n1kolaa said:
reteu got 10
there was 1 more ota after that for march update
Click to expand...
Click to collapse
Ok, do you have a copy of the firmware?
I haven't seen it.
Sent from my ali using XDA Labs
sd_shadow said:
Ok, do you have a copy of the firmware?
I haven't seen it.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Didnt saved it, can provide fw id.
edit:
n1kolaa said:
Didnt saved it, can provide fw id.
edit:
Click to expand...
Click to collapse
also new LSMA version, it did recognise my phone now, but still after rescue it would have the same error
also we have android 10 roms on lolinet
trying the reteu android 10 from lolinet as last try
claudiusuflea said:
also new LSMA version, it did recognise my phone now, but still after rescue it would have the same error
also we have android 10 roms on lolinet
trying the reteu android 10 from lolinet as last try
Click to expand...
Click to collapse
Dead. Nothing worked again. So the phone is doomed, I will try once I can to take it to a gsm. It's the emmc partition which causes this problem.
Always unlock bootloader or at least enable oem unlock in developer settings before messing with firmwares (specially when downgrading). You got a really expensive papper weight.
It all started when I wanted to root my phone so that I could move more apps to my sd card. I followed this tutorial: https://www.theworldsbestandworst.com/2020/06/root-motorola-moto-e5-play/ but the version of SuperSU they had me install bricked my phone (My phone would freeze on startup at the t-mobile logo).
So, having done so in the past, I knew I could flash the stock firmware and hopefully get my phone back to working condition. I tried using two different downloads of the stock firmware. One from here: https://sourceforge.net/projects/moto-e5-firmware/files/JAMES/XT1921-3/ and one from here: https://forum.xda-developers.com/t/...he-e5-play-xt1921-3-t-mobile-variant.3839675/ (it's the link first given by timjames474). For both downloads I used the batch file method of flashing described here:
because RSDLite wasn't detecting my device. However, both of the times I tried flashing the stock firmware my phone worked normally but was unable to detect my sim card.
Was I using the wrong download of stock firmware? Is my phone broken for good? Please help me.
tezcatlipoca7123 said:
It all started when I wanted to root my phone so that I could move more apps to my sd card. I followed this tutorial: https://www.theworldsbestandworst.com/2020/06/root-motorola-moto-e5-play/ but the version of SuperSU they had me install bricked my phone (My phone would freeze on startup at the t-mobile logo).
So, having done so in the past, I knew I could flash the stock firmware and hopefully get my phone back to working condition. I tried using two different downloads of the stock firmware. One from here: https://sourceforge.net/projects/moto-e5-firmware/files/JAMES/XT1921-3/ and one from here: https://forum.xda-developers.com/t/...he-e5-play-xt1921-3-t-mobile-variant.3839675/ (it's the link first given by timjames474). For both downloads I used the batch file method of flashing described here:
because RSDLite wasn't detecting my device. However, both of the times I tried flashing the stock firmware my phone worked normally but was unable to detect my sim card.
Was I using the wrong download of stock firmware? Is my phone broken for good? Please help me.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Here is what my terminal returns when I enter getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.45
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323SRCZP
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 09E5223100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146092420788
(bootloader) meid:
(bootloader) date: 03-18-2019
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB9.45-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4
(bootloader) cmnlib.git: git=5fefee4
(bootloader) cmnlib64.git: git=5fefee4
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.45-0-gff56367
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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.772s
tezcatlipoca7123 said:
Here is what my terminal returns when I enter getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.45
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323SRCZP
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 09E5223100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146092420788
(bootloader) meid:
(bootloader) date: 03-18-2019
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCP27
(bootloader) ro.build.fingerprint[1]: .91-51-4/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5480efb-0001
(bootloader) kernel.version[1]: 6-gd2768b6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Fri Jul
(bootloader) kernel.version[3]: 20 10:36:48 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB9.45-0-geb7a3e0
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=5fefee4-dirty
(bootloader) devcfg.git: git=5fefee4-dirty
(bootloader) keymaster.git: git=5fefee4
(bootloader) cmnlib.git: git=5fefee4
(bootloader) cmnlib64.git: git=5fefee4
(bootloader) prov.git: git=5fefee4-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.45-0-gff56367
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(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.772s
Click to expand...
Click to collapse
The firmware you are using should be correct.
getvar say baseband is missing
Code:
(bootloader) version-baseband: <not found>
and both system slots are INVALID
Not a good sign.
You didn't see any flashing errors?
RSD Lite doesn't work with Windows 10, do you have a Windows 7 machine?
Try posting the service.xml text in https://kfhost.net/flashfile
and compare with your batch file.
sd_shadow said:
The firmware you are using should be correct.
getvar say baseband is missing
Code:
(bootloader) version-baseband: <not found>
and both system slots are INVALID
Not a good sign.
You didn't see any flashing errors?
RSD Lite doesn't work with Windows 10, do you have a Windows 7 machine?
Try posting the service.xml text in https://kfhost.net/flashfile
and compare with your batch file.
Click to expand...
Click to collapse
The batch file I had was slightly different than the one produced by the website you had me use. I replaced the batch file's contents and flashed the firmware again. I got these errors (not sure if 'image signed with key bad key' is an error so I'm including it just incase):
(bootloader) is-logical:FSG: not found
Sending 'FSG' (1696 KB) OKAY [ 0.222s]
Writing 'FSG' (bootloader) Invalid partition name FSG
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalSP: not found
Sending 'DSP' (16384 KB) OKAY [ 0.689s]
Writing 'DSP' (bootloader) Invalid partition name DSP
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.526s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.553s]
Finished. Total time: 1.279s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.698s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.584s]
Finished. Total time: 1.316s
I got the same bad key errors when I flashed the firmware with my first batch file. After this flash the phone still works normally besides not being able to read the sim card.
tezcatlipoca7123 said:
The batch file I had was slightly different than the one produced by the website you had me use. I replaced the batch file's contents and flashed the firmware again. I got these errors (not sure if 'image signed with key bad key' is an error so I'm including it just incase):
(bootloader) is-logical:FSG: not found
Sending 'FSG' (1696 KB) OKAY [ 0.222s]
Writing 'FSG' (bootloader) Invalid partition name FSG
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logicalSP: not found
Sending 'DSP' (16384 KB) OKAY [ 0.689s]
Writing 'DSP' (bootloader) Invalid partition name DSP
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.526s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.553s]
Finished. Total time: 1.279s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.698s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.584s]
Finished. Total time: 1.316s
I got the same bad key errors when I flashed the firmware with my first batch file. After this flash the phone still works normally besides not being able to read the sim card.
Click to expand...
Click to collapse
Strange you shouldn't have a recovery.img
Can you attach the service.xml ?
sd_shadow said:
Strange you shouldn't have a recovery.img
Can you attach the service.xml ?
Click to expand...
Click to collapse
I did have twrp on my phone before the flash
Here's the servicefile.xml, the firmware doesn't have a service.xml:
tezcatlipoca7123 said:
I did have twrp on my phone before the flash
Click to expand...
Click to collapse
Devices with a/b system slots don't have a recovery partition it's part of the boot.img now
so now when you install Twrp or magisk the boot partition must be changed.
Here's the servicefile.xml, the firmware doesn't have a service.xml:
Click to expand...
Click to collapse
Yes, my bad
Try just
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Tried it, each command comes back "OKAY". My phone still can't read the sim card though.
tezcatlipoca7123 said:
Tried it, each command comes back "OKAY". My phone still can't read the sim card though.
Click to expand...
Click to collapse
Windows 10?
sd_shadow said:
Windows 10?
Click to expand...
Click to collapse
Yes, I have have an older machine but I don't know if it still works or what version it is.
tezcatlipoca7123 said:
Yes, I have have an older machine but I don't know if it still works or what version it is.
Click to expand...
Click to collapse
If it's XP or 7 you could try RSD Lite
With the current machine, have you updated adb files?
Tried different USB ports?
sd_shadow said:
If it's XP or 7 you could try RSD Lite
With the current machine, have you updated adb files?
Tried different USB ports?
Click to expand...
Click to collapse
The other pc is also windows 10 .
I'm using the most current platform-tools.
I'll try using other usb ports but my computer doesn't have trouble connecting to my phone so I'm not sure how that'd help (or if your talking about trying to get RSD Lite to work I've already tried other usb ports).
tezcatlipoca7123 said:
The other pc is also windows 10 .
Click to expand...
Click to collapse
The only time RSD Lite has worked for me with Windows 10 is if it originally shipped with 7 and was upgraded to 10.
Man any solutions? I reinstalled firmware, after unlocking bootloader then I flashed twrp and magisk using that twrp but my baseband version is unknown, IMEI unknown.
but my Wi-Fi is working fine, Can someone guide me through with it?
muneebwolf said:
Man any solutions? I reinstalled firmware, after unlocking bootloader then I flashed twrp and magisk using that twrp but my baseband version is unknown, IMEI unknown.
but my Wi-Fi is working fine, Can someone guide me through with it?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323JV88W
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: B94B05DB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146091881899
(bootloader) meid:
(bootloader) date: 12-17-2018
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 9:35:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-150-5-1-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.311.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gf60ba68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue May 7 15:58:26 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=7a51f9f-dirty
(bootloader) devcfg.git: git=7a51f9f-dirty
(bootloader) keymaster.git: git=7a51f9f
(bootloader) cmnlib.git: git=7a51f9f
(bootloader) cmnlib64.git: git=7a51f9f
(bootloader) prov.git: git=7a51f9f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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
muneebwolf said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8920-B9.4A
(bootloader) product: james
(bootloader) board: james
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8920
(bootloader) serialno: ZY323JV88W
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: B94B05DB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354146091881899
(bootloader) meid:
(bootloader) date: 12-17-2018
(bootloader) sku: XT1921-3
(bootloader) carrier_sku: XT1921-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 9:35:18 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/james_t/james:8.0.0/OCPS2
(bootloader) ro.build.fingerprint[1]: 7.91-150-5-1-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.311.4.james_t.t.e
(bootloader) ro.build.version.full[1]: n.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gf60ba68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Tue May 7 15:58:26 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB9.4A-0-g8ffb6ee
(bootloader) rpm.git: git=02a0726-dirty
(bootloader) tz.git: git=7a51f9f-dirty
(bootloader) devcfg.git: git=7a51f9f-dirty
(bootloader) keymaster.git: git=7a51f9f
(bootloader) cmnlib.git: git=7a51f9f
(bootloader) cmnlib64.git: git=7a51f9f
(bootloader) prov.git: git=7a51f9f-dirty
(bootloader) aboot.git: git=MBM-NG-VB9.4A-0-g4e376e8
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(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
Click to expand...
Click to collapse
Looks like you have this version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-5-1-3_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC.xml.zip
this is the newest version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-14-13_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but that shouldn't have anything do with your problem, unless you have been flashing a different version than 27.91-150-5-1-3
The invalid slots are worrisome, often with this problem, a blankflash is needed to fix it.
Are you using flashfile.xml to get the correct flash commands?
sd_shadow said:
Looks like you have this version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-5-1-3_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC.xml.zip
this is the newest version
XT1921-3_JAMES_TMO_8.0.0_OCPS27.91-150-14-13_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but that shouldn't have anything do with your problem, unless you have been flashing a different version than 27.91-150-5-1-3
The invalid slots are worrisome, often with this problem, a blankflash is needed to fix it.
Are you using flashfile.xml to get the correct flash commands?
Click to expand...
Click to collapse
Man I used downloaded this firmware from lolinet, used all the necessary commands but still its not working, and yes I used flashfile.xml
Hey gang. I unlocked a motorola g play 2021 rooted it and tried to flash twrp onto it whch didnt work. So I flashed the boot.img file and it restarted as a new phone would. The next morning. bear with me here. It states no OS present to boot. So I restart the phone to the bootloader and it states the bootloader is locked and now will only restart to the bootloader. When I try to flash the recovery or boot image it just stated bootloader permission denied then it fails. I have been flashing samsungs for years with no problems and when there is I can usually solve it easily. But ths damn motorola has me stumped.. Here is the getvar all info. Any help possible would be greatly appreciated. Guess Im still more of an amature then i thought. Please advise. Thanks
I tried going through the unlock bootloader sequence and this is what it tells me.
C:\Android\platform-tools>fastboot oem unlock CSSPP***#*#********
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
this got me back to Android recovery page. But when I try to do a factory reset it says no directory or file present
fastboot --c "console=ttyHSL0,115200,n8" boot recovery.img
The Lenovo rescue tool fails at 40% every time.
Unlock Code: CSSPP***************
get var all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) product: guamna
(bootloader) board: guamna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: GWLC
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ufs: N/A
(bootloader) ram: 3GB SKHYNIX LP4x DIE=12Gb M5-M8=06 05 00 0D
(bootloader) cpu: SM_KAMORTA 1.0
(bootloader) serialno: ZY22BQWX4M
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: F66B2378
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 798750720
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351647111426774
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-20-2021
(bootloader) sku: XT2093-3
(bootloader) carrier_sku: XT2093-3
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 3854
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: metropcs
(bootloader) ro.build.fingerprint[0]: motorola/guamna_t/guamna:10/QZAS30
(bootloader) ro.build.fingerprint[1]: .Q4-39-57-2-2-1-1-3-3/882ca7:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.73.08R GUAMNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Jun 9 07:26
(bootloader) kernel.version[3]: :55 CDT 2021
(bootloader) git:xbl: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:xbl_config: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:abl: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) git:rpm: MBM-3.0-guamna_t-6b0a297-210609
(bootloader) git:tz: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:hyp: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:devcfg: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:keymaster: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:storsec: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:uefisecapp: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) gitrov: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:qupfw: MBM-3.0-guamna_t-f07d142-210609
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(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: 1
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86657
(bootloader) primary-display: hlt_hx83102d_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.267s
Mikeo31 said:
Hey gang. I unlocked a motorola g play 2021 rooted it and tried to flash twrp onto it whch didnt work. So I flashed the boot.img file and it restarted as a new phone would. The next morning. bear with me here. It states no OS present to boot. So I restart the phone to the bootloader and it states the bootloader is locked and now will only restart to the bootloader. When I try to flash the recovery or boot image it just stated bootloader permission denied then it fails. I have been flashing samsungs for years with no problems and when there is I can usually solve it easily. But ths damn motorola has me stumped.. Here is the getvar all info. Any help possible would be greatly appreciated. Guess Im still more of an amature then i thought. Please advise. Thanks
I tried going through the unlock bootloader sequence and this is what it tells me.
C:\Android\platform-tools>fastboot oem unlock CSSPP***#*#********
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
this got me back to Android recovery page. But when I try to do a factory reset it says no directory or file present
fastboot --c "console=ttyHSL0,115200,n8" boot recovery.img
The Lenovo rescue tool fails at 40% every time.
Unlock Code: CSSPP***************
get var all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) product: guamna
(bootloader) board: guamna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: GWLC
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ufs: N/A
(bootloader) ram: 3GB SKHYNIX LP4x DIE=12Gb M5-M8=06 05 00 0D
(bootloader) cpu: SM_KAMORTA 1.0
(bootloader) serialno: ZY22BQWX4M
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: F66B2378
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 798750720
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351647111426774
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-20-2021
(bootloader) sku: XT2093-3
(bootloader) carrier_sku: XT2093-3
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 3854
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: metropcs
(bootloader) ro.build.fingerprint[0]: motorola/guamna_t/guamna:10/QZAS30
(bootloader) ro.build.fingerprint[1]: .Q4-39-57-2-2-1-1-3-3/882ca7:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.73.08R GUAMNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Jun 9 07:26
(bootloader) kernel.version[3]: :55 CDT 2021
(bootloader) git:xbl: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:xbl_config: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:abl: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) git:rpm: MBM-3.0-guamna_t-6b0a297-210609
(bootloader) git:tz: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:hyp: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:devcfg: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:keymaster: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:storsec: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:uefisecapp: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) gitrov: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:qupfw: MBM-3.0-guamna_t-f07d142-210609
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(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: 1
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86657
(bootloader) primary-display: hlt_hx83102d_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.267s
Click to expand...
Click to collapse
Try flashing manually
LMSA should have a copy of firmware in C:\ProgramData\LMSA\Download\RomFiles
Or you can download it from
https://mirrors.lolinet.com/firmware/moto/guamna/official/MetroPCS/
XT2093-3_GUAMNA_METROPCS_10_QZAS30.Q4-39-57-2-2-1-1-3-3_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip
Unzip
First try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
fastboot reboot
It might boot normally
if not try
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
reboot bootloader
then try LMSA again
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
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
Try flashing manually
LMSA should have a copy of firmware in C:\ProgramData\LMSA\Download\RomFiles
Or you can download it from
https://mirrors.lolinet.com/firmware/moto/guamna/official/MetroPCS/
XT2093-3_GUAMNA_METROPCS_10_QZAS30.Q4-39-57-2-2-1-1-3-3_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip
Unzip
First try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
fastboot reboot
It might boot normally
if not try
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
reboot bootloader
then try LMSA again
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
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks very much I'll give it a go and repost. @sd_shadow
Mikeo31 said:
thanks very much I'll give it a go and repost. @sd_shadow
Click to expand...
Click to collapse
No good. on the first method.
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 798763008 bytes
sending 'partition' (37 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.167s
No good on the 2nd method
Permission denied
FAILED(remote failure)
and the LMSA gets as far as 50% depending on which time I ran it and states
Flashboot Flash single partition
Flash failed please try again
Could it be something to do with the A/B Partition.? I flashed Magisk on one of them and it restarted. I went to bed and got up the next morning and here we are.
Hi I'm Steve I'm new here and I'm just learning how to root my phone and be a developer so if anybody could help me I really appreciate it
Is there a blank flash.zip yet for this phone? Usually I've seen mirrors.lolinet.com include blankflash files with each variant of moto phones. This one is an exception. Or can anyone make one perhaps?
I transferred the fastboot.exe out of the LMSA or RSA file, because I noticed it's something like 7.5mb, and seemed to gain extra fastboot functionality. This was when I encountered, maybe not exactly the same, but a similar issue with relocking the bootloader.
I used the command (after copying the Lincoln log of a fastboot executable to my working directory):
fastboot -b flash boot boot.img
And by some stroke of luck, it booted into the OS. I know that command looks weird, but I was so frustrated, I just started going down the list and trying everything I could. If you haven't tried switching boot slots, you may give that a whirl as well. I do hope this helps.
My setup is an old dual core Intel, with windows 10 version 20H1....one of the older windows 10 releases.
Mikeo31 said:
No good. on the first method.
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 798763008 bytes
sending 'partition' (37 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.167s
Click to expand...
Click to collapse
Did you fastboot oem fb_mode_set first?
Hello Everyone.
This is my first post so please if i did anything wrong or posted this in the wrong place please let me know.
I have a Moto G Pure that im trying to root. I have to unlock the bootloader first from what i gather. I downloaded the adb, fastboot and drivers for the phone installed everything and went on motos website and used there bootloader unlock string tool and it says "your device does not qualify for bootloader unlocking". Not sure why that's coming up? Does anyone know a work around by chance? Here is the Unlock Data, the sting I used and the getvar info.
C:\\Desktop\platform-tools>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3A85832508840061#5A593232444C4B
(bootloader) 474433006D6F746F2067200000#F797
(bootloader) DDD03416481B0F85B69548533550013
(bootloader) 97C6CAAC01B02F6D820BD2048F29F#0
(bootloader) DF077A6F1E7E5E80000000000000000
OKAY [ 0.050s]
Finished. Total time: 0.052
3A85832508840061#5A593232444C4B474433006D6F746F2067200000#F797DDD03416481B0F85B6954853355001397C6CAAC01B02F6D820BD2048F29F#0DF077A6F1E7E5E80000000000000000
C:\\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ellis_a-320aeee45-211101
(bootloader) product: ellis
(bootloader) board: ellis
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX68MB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG N NVM DIE=512Mb M5=01 M6=07 M7=00 M8=0E
(bootloader) cpu: MT6762G
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0001
(bootloader) channelid: 0x88
(bootloader) uid: 0DF077A6F1E7E5E8000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-18-2021
(bootloader) sku: XT2163-6
(bootloader) carrier_sku: XT2163-6
(bootloader) battid: SB18D15249
(bootloader) iccid: 89012803320393497037
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 15 12:24:29 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ellis_a/ellis:11/RRH31.Q3
(bootloader) ro.build.fingerprint[1]: -46-50-2/20fec:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-r0.mp1.tc2sp-V1.66
(bootloader) version-baseband: MT6762_TC2.PR2.SP.V8.2.P20.01.66.54R
(bootloader) kernel.version[0]: Linux version 4.19.127+ ([email protected]
(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390
(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android
(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project
(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7
(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH
(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79
(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Mon Nov 1 05:00:56 CDT
(bootloader) kernel.version[8]: 2021
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: attpre
(bootloader) current-slot: a
(bootloader) running-boot-lun: 1
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28D31556
(bootloader) is-userspace: no
(bootloader) is-logical:
(bootloader) snapshot-update-status: none
all: listed above
Finished. Total time: 0.078s
Any pointers would surly be appreciated. Been pulling my hair out. haha!
Thanks for reading!
-BB
@Biggitybaked
The model you have (XT2163-6) is the AT&T variant of the Moto G Pure. The carrier doesn't allow unlocking the bootloader.
With that said, you can give an unofficial MediaTek reverse engineering tool named MTKClient a try. Only proceed if you know what you're doing.
That's what I figured. Ill never buy as phone from a carrier again. Thank you for confirming. And ima look into that MTKClient and see if I can do it. Wish me luck. haha!
Have you tested the mtkclient, work ?
meegosgift said:
Have you tested the mtkclient, work ?
Click to expand...
Click to collapse
The main issue preventing mtk client from working seems to be this: I have no clue on how to make my XT2163-2 phone enter the MediaTek ... brom mode!
There's a program it may not technically be for your peticular phone, so not responsible for any damage or problems I'm just saying I think it's like mtk auth bypass tool, it can get you to brom mode,
But ... what are the prerequisites (along with that app from MediaTek) for making the phone enter brom mode? Without JTAG, serial interface or "test points". A way for mere mortals like me, to allow me to unlock the damn bootloader, which Motorola (aka Lenovo) was plotting with Verizons, to keep us, legitimate owners of their stupid phones, out of the bootloader...
how to boot to brom on this phone? anyone figured it out?
smihaila said:
The main issue preventing mtk client from working seems to be this: I have no clue on how to make my XT2163-2 phone enter the MediaTek ... brom mode!
Click to expand...
Click to collapse
When using mtk client, power off the phone and disconnect the usb. While off, hold both VOL - & VOL + then plug in the usb while the client is running. Mtk client will automatically recognize your device I've used the same method for all versions of mtk devices with 100% success. The partitions pull as bin files but i just use a converter to solve that issue
yah2000 said:
how to boot to brom on this phone? anyone figured it out?
Click to expand...
Click to collapse
While Mtk client is running:
1. Power off device & disconnect the usb
2. Plug in usb while holding VOL - & VOL +
Mtk Client will automatically recognize mtk device
Biggitybaked said:
Hello Everyone.
This is my first post so please if i did anything wrong or posted this in the wrong place please let me know.
I have a Moto G Pure that im trying to root. I have to unlock the bootloader first from what i gather. I downloaded the adb, fastboot and drivers for the phone installed everything and went on motos website and used there bootloader unlock string tool and it says "your device does not qualify for bootloader unlocking". Not sure why that's coming up? Does anyone know a work around by chance? Here is the Unlock Data, the sting I used and the getvar info.
C:\\Desktop\platform-tools>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3A85832508840061#5A593232444C4B
(bootloader) 474433006D6F746F2067200000#F797
(bootloader) DDD03416481B0F85B69548533550013
(bootloader) 97C6CAAC01B02F6D820BD2048F29F#0
(bootloader) DF077A6F1E7E5E80000000000000000
OKAY [ 0.050s]
Finished. Total time: 0.052
3A85832508840061#5A593232444C4B474433006D6F746F2067200000#F797DDD03416481B0F85B6954853355001397C6CAAC01B02F6D820BD2048F29F#0DF077A6F1E7E5E80000000000000000
C:\\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ellis_a-320aeee45-211101
(bootloader) product: ellis
(bootloader) board: ellis
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX68MB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG N NVM DIE=512Mb M5=01 M6=07 M7=00 M8=0E
(bootloader) cpu: MT6762G
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0001
(bootloader) channelid: 0x88
(bootloader) uid: 0DF077A6F1E7E5E8000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-18-2021
(bootloader) sku: XT2163-6
(bootloader) carrier_sku: XT2163-6
(bootloader) battid: SB18D15249
(bootloader) iccid: 89012803320393497037
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 15 12:24:29 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ellis_a/ellis:11/RRH31.Q3
(bootloader) ro.build.fingerprint[1]: -46-50-2/20fec:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-r0.mp1.tc2sp-V1.66
(bootloader) version-baseband: MT6762_TC2.PR2.SP.V8.2.P20.01.66.54R
(bootloader) kernel.version[0]: Linux version 4.19.127+ ([email protected]
(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390
(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android
(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project
(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7
(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH
(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79
(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Mon Nov 1 05:00:56 CDT
(bootloader) kernel.version[8]: 2021
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: attpre
(bootloader) current-slot: a
(bootloader) running-boot-lun: 1
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28D31556
(bootloader) is-userspace: no
(bootloader) is-logical:
(bootloader) snapshot-update-status: none
all: listed above
Finished. Total time: 0.078s
Any pointers would surly be appreciated. Been pulling my hair out. haha!
Thanks for reading!
-BB
Click to expand...
Click to collapse
Successfully rooted my Moto G Pure (RRHS31.Q3-46-110-13):
OEM unlock was grayed out, so I used Motorola RSA to download the stock ROM, then after locating the ROM files, used Magisk 25.2 to patch the boot.img. I flashed the stock ROM using the RESCUE option in RSA then setup my phone once the process was complete. I enabled Developer Options as well as, the now available, OEM unlock and went through the steps to flash the patched boot.img from earlier. I've attached the stock boot and am currently using LSPosed in place of EdXposed
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Moto G Pure - XT2163-4 root? is there a root out there? thx
alan2424m said:
Moto G Pure - XT2163-4 root? is there a root out there? thx
Click to expand...
Click to collapse
Yes. I'm currently using a Moto G Pure TMO (Ellis) updated to Android 12 (S3RH32.20-42-10-2-3) with Magisk 25.2. I'll include my boot.img below which is Android 12-4.19.191+ Magisk patched (25.2) with HuskyDG bootloop protection. I also used LSPosed 1.8.5 (6695) zygisk with [email protected] GS Ram Drive (20GB swap). I had to use Motorola's Rescue & Smart Assistant to re-flash my phone before I could toggle OEM unlock, then I used the generated key to unlock my bootloader.
KMerrimanJr said:
Yes. I'm currently using a Moto G Pure TMO (Ellis) updated to Android 12 (S3RH32.20-42-10-2-3) with Magisk 25.2. I'll include my boot.img below which is Android 12-4.19.191+ Magisk patched (25.2) with HuskyDG bootloop protection. I also used LSPosed 1.8.5 (6695) zygisk with [email protected] GS Ram Drive (20GB swap). I had to use Motorola's Rescue & Smart Assistant to re-flash my phone before I could toggle OEM unlock, then I used the generated key to unlock my bootloader.
Click to expand...
Click to collapse
thx man does it matter that mine is android version 11 XT2163-4?
i got it unlocked already
alan2424m said:
i got it unlocked already
Click to expand...
Click to collapse
No, mine started as Android 11 but Google recently release an Android 12 update for the XT2163-4. ELLIS_T_S3RH32.20_42_10_2_3_subsidy_TMO_UNI_RSU_QCOM_regulatory_DEFAULT_CFC.xml is the latest T-Mobile rom released by Google. Check out the site below to download the official ROM. All carriers are listed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
alan2424m said:
thx man does it matter that mine is android version 11 XT2163-4
Click to expand...
Click to collapse
Android 12 tightened up on security so you might want to stay on 11. I use App Manager and overlayFS to "uninstall" any apps I don't want but I can't directly delete from the system dir. On 11 I could
KMerrimanJr said:
No, mine started as Android 11 but Google recently release an Android 12 update for the XT2163-4. ELLIS_T_S3RH32.20_42_10_2_3_subsidy_TMO_UNI_RSU_QCOM_regulatory_DEFAULT_CFC.xml is the latest T-Mobile rom released by Google. Check out the site below to download the official ROM. All carriers are listed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
ok mine is boost mobile but that shouldnt change anything right?
here is mine ELLIS_T_RRHS31.Q3_46_110_13_subsidy_BOOST_DISH_SHORT_regulatory_DEFAULT_CFC.xml
yours is tmobile like i said hopefully that doesnt change anything