EDIT:
1 - I don't really care about rooting the phone. I'd simply like to have Lineage OS on it.
2 - I don't really care about having a installed version of TWRP, I can do the fastboot boot only if that would work to install lineage on there.
So I unlock the bootloader fine.
Now following this :
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I am able to
fastboot boot twrp.img
Then I do the install of the .zip from the TWRP site.
Wipe davlik and reboot
System starts fine. I reboot in bootloader mode (power + volumn down) then go to recovery
it has that
N/A in the top corner, flash black and buzz, flash black again then the androdi starts normally.
I read somewhere the this is a bootloop - and I should install Magisk from TWRP, which I did probably incorrectly at one point.
Booting back into fastboot boot twrp.img
I wipe advanced (system davlik data system)
Then Advanced Fix Recovery Bootloop
Then this seems to be not good:
Unpacking Boot...
Backing up Boot...
Patching kernel...
(in red)
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
So did I screw up my kernel while trying to install magisk ? What would be the next step?
Would it make sense to flash the original firmware from here:
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
The question I would have is which one should I choose in there:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The retail one? Mine is factory unlocked, not connected to any network,
MPN: Moto G7 Play, XT1952-1
Network: Unlocked
The phone still work fine (I think, didn't do more than booting and checking the internet).
damaru said:
EDIT:
1 - I don't really care about rooting the phone. I'd simply like to have Lineage OS on it.
2 - I don't really care about having a installed version of TWRP, I can do the fastboot boot only if that would work to install lineage on there.
So I unlock the bootloader fine.
Now following this :
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I am able to
fastboot boot twrp.img
Then I do the install of the .zip from the TWRP site.
Wipe davlik and reboot
System starts fine. I reboot in bootloader mode (power + volumn down) then go to recovery
it has that
N/A in the top corner, flash black and buzz, flash black again then the androdi starts normally.
I read somewhere the this is a bootloop - and I should install Magisk from TWRP, which I did probably incorrectly at one point.
Booting back into fastboot boot twrp.img
I wipe advanced (system davlik data system)
Then Advanced Fix Recovery Bootloop
Then this seems to be not good:
Unpacking Boot...
Backing up Boot...
Patching kernel...
(in red)
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
So did I screw up my kernel while trying to install magisk ?
Click to expand...
Click to collapse
If you tried to install magisk, it may be interfering with TWRP.
damaru said:
What would be the next step?
Would it make sense to flash the original firmware from here:
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
The question I would have is which one should I choose in there:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
The retail one? Mine is factory unlocked, not connected to any network,
MPN: Moto G7 Play, XT1952-1
Network: Unlocked
The phone still work fine (I think, didn't do more than booting and checking the internet).
Click to expand...
Click to collapse
A few different options
to find the correct Firmware you need to know
Software Channel, Codename, Software Version, and Model #
all of these can be found in the getvar all (remove imei before posting getvar all)
Code:
fastboot getvar all
or you can use LMSA's rescue option, LMSA will find the newest firmware for your device,
So if it's the same Software version as what is on the device, can just flash the boot.img from the firmware folder.
Code:
fastboot flash boot boot.img
or use
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:
fastboot flash boot.img
Click to expand...
Click to collapse
That would be fastboot flash boot boot.img right?
I've downloaded the appropriate firmware using fastboot getvar all to get the right model. The phone boots properly (it wasn't after I used the wrong firmware). But then I get to the same error when I fastboot boot twrn.img and try the advance Fix Recovery Bootloop.
When I did flash the whole firmware, the Bad Code was back, then I flashed TWRP and then the N/A was there and when I tried to boot to recovery the same loop happened.
From my lack of understanding, did I updated the Kernel when I reflashed the firmware? And does magisk modify my Kernel. How would I put back the original kernel?
Thanks for the support it's greatly appreciated! I've been on this for too many hours now!
As you mentioned that I should remove my emei before posting this I though that posting it might help
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:56:26 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(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+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.010s
damaru said:
That would be fastboot flash boot boot.img right?
Click to expand...
Click to collapse
correct
damaru said:
As you mentioned that I should remove my emei before posting this I though that posting it might help
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:56:26 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(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+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.010s
Click to expand...
Click to collapse
Well, a few things don't look right.
Code:
(bootloader) reason: Reboot mode set to fastboot
Likely cause from not using fb_clear after flashing
Code:
fastboot oem fb_mode_clear
Baseband is missing
Code:
(bootloader) version-baseband: <not found>
Did you use firmware from RetCA?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Yes this is the one I used. I might have done more fastboot stuff than what was in the xml file (these are from the post itself and not from the firmware file):
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
which in the retca xml only had :
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
should I reflash the whole thing, omitting the erase at the end?
damaru said:
Yes this is the one I used. I might have done more fastboot stuff than what was in the xml file (these are from the post itself and not from the firmware file):
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
which in the retca xml only had :
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
should I reflash the whole thing, omitting the erase at the end?
Click to expand...
Click to collapse
No, if you used fastboot oem fb_mode_clear
then something else is going on
So the rescue and smart assistant is not working on that particular model (or so Lenovo say) should I try anyway?
I get a Start Up Failed now. So I can't boot in the normal phone anymore. Not sure what I did wrong. So to get back to a normal phone flashing the whole firmware wouldn't help?
I'm at a place where I'd like to bring back the phone to exactly how it was stock so that I can go trough the TWRP process which seems to be straight enough...
EDIT 1 trying with the rescue software I get
Device missed [ro.build.version.full]
Please contact after sale service to re-write
EDIT 2
Reflashed the whole thing and the phone is work now.
Trying to re-install TWRP from:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Using the TWRP page information, I tried to install it and then when I try to reboot it goes trough the boot loop. Phone boots fine, back the N/A in the top corner of the boot screen. Get back in fastboot boot twrp, the wipe davlik, try to fix the bootloop, get the same freaking error :
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
Phone boots fine though.
Try to fix Magisk (by installing the APK ):
Installation
The Magic Mask for Android
topjohnwu.github.io
Trying to Fix Magisk, using the apk, with the Boot.img that I used to reflash the whole phone didn't seems to work. I was able to create a custom boot img, and then the phone boot it doesn't say BAD CODE but a series of 40 numbers appears on the top screen. When I go back to the Magisk APK it shows that it's not installed, or more appropriate Installed: N/A ...
Trying to install lineage from the zip from the lineage site.
By booting in fastboot boot twrp, I wipe davlik, system, data, the install from zip I get:
Error installing zip file '/external_sd/lineage-18.1-2021-6-6-nightly-channel-signed.zip
Updating partition details...
...done
So, no idea where to go from there. Maybe I'm doing all that stuff in the wrong order. Should I try to reflash the boot, then not trying to install TWRP and trying to install Lineage like that? Is that possible?
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:37:43 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel/channel:9/PPYS29.
(bootloader) ro.build.fingerprint[1]: 105-220-3/74206:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.8.channel.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_37.155.01.146R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.011s
damaru said:
So the rescue and smart assistant is not working on that particular model (or so Lenovo say) should I try anyway?
I get a Start Up Failed now. So I can't boot in the normal phone anymore. Not sure what I did wrong. So to get back to a normal phone flashing the whole firmware wouldn't help?
I'm at a place where I'd like to bring back the phone to exactly how it was stock so that I can go trough the TWRP process which seems to be straight enough...
EDIT 1 trying with the rescue software I get
Device missed [ro.build.version.full]
Please contact after sale service to re-write
EDIT 2
Reflashed the whole thing and the phone is work now.
Trying to re-install TWRP from:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Using the TWRP page information, I tried to install it and then when I try to reboot it goes trough the boot loop. Phone boots fine, back the N/A in the top corner of the boot screen. Get back in fastboot boot twrp, the wipe davlik, try to fix the bootloop, get the same freaking error :
cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel (lots of numbers) process eneded with
ERROR: 1
Error patching kernel
Phone boots fine though.
Try to fix Magisk (by installing the APK ):
Installation
The Magic Mask for Android
topjohnwu.github.io
Trying to Fix Magisk, using the apk, with the Boot.img that I used to reflash the whole phone didn't seems to work. I was able to create a custom boot img, and then the phone boot it doesn't say BAD CODE but a series of 40 numbers appears on the top screen. When I go back to the Magisk APK it shows that it's not installed, or more appropriate Installed: N/A ...
Trying to install lineage from the zip from the lineage site.
By booting in fastboot boot twrp, I wipe davlik, system, data, the install from zip I get:
Error installing zip file '/external_sd/lineage-18.1-2021-6-6-nightly-channel-signed.zip
Updating partition details...
...done
So, no idea where to go from there. Maybe I'm doing all that stuff in the wrong order. Should I try to reflash the boot, then not trying to install TWRP and trying to install Lineage like that? Is that possible?
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-channel_retail-dd305e78aca-2
(bootloader) version-bootloader[1]: 00403
(bootloader) product: channel
(bootloader) board: channel
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326M5QF9
(bootloader) cid: 0x0032
(bootloader) channelid: 0x80
(bootloader) uid: 420A00D000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) date: 08-20-2019
(bootloader) sku: XT1952-4
(bootloader) carrier_sku: XT1952-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Apr 4 1:37:43 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/channel/channel:9/PPYS29.
(bootloader) ro.build.fingerprint[1]: 105-220-3/74206:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.8.channel.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_37.155.01.146R CHANNEL_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld151) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Fri Ap
(bootloader) kernel.version[3]: r 3 20:41:50 CDT 2020
(bootloader) sbl1.git: MBM-2.1-channel_retail-6c78ff914e-200403
(bootloader) rpm.git: MBM-2.1-channel_retail-22daab39-200403
(bootloader) tz.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) devcfg.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) keymaster.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-2
(bootloader) keymaster.git[1]: 00403
(bootloader) cmnlib.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) cmnlib64.git[0]: MBM-2.1-channel_retail-cf17343a58-dirty-20
(bootloader) cmnlib64.git[1]: 0403
(bootloader) prov.git: MBM-2.1-channel_retail-cf17343a58-dirty-200403
(bootloader) aboot.git: MBM-2.1-channel_retail-dd305e78aca-200403
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retca
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.011s
Click to expand...
Click to collapse
I don't think you need to Install TWRP to install Lineage
Just boot twrp and install the Rom
Edit: Looks like you tried that already
Make sure you are using the preinstall zip before installing the rom
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org
Related
Every time the phone get started the recovery is loaded. In recovery i had to boot into bootloader and then i have to select the normal "powerup ". et voila the rom loads normaly and everythink is working fine.
I got the moto g with bootloop from a friend. Then I tried to lift 5.1.x. I tried different Rom versions (including cm12.1) , and also diffrent recovery.
With stock recovery the droid lies back, but now menu. Now with TWRP-2.8.7.0.-falcon_STOCK_NOTHEME.img recovery is stable and everythink works.
Bootloader I tested 41.18 and 41.19, but both identical result.
On satellite receiver I would tap to broken environments in bootloader, but the mobile device I am blank.
Is naturally mega cumbersome without WAF!!!!
Where can I look what is going wrong, someone has a tip how to fix this boot Problem?
next try: can somebody post the result in fastboot from:
Code:
fastboot getvar all
or
Code:
mfastboot getvar all
my phone:
Code:
C:\MOTO\>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA92904GMH
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 17DF480XXX000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Mar 12 15:24:29 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:5.
(bootloader) ro.build.fingerprint[1]: 1/LMY47M.M001/6:user/release-keys
(bootloader) ro.build.version.full:
(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-ga838857 ([email protected]
(bootloader) kernel.version[1]: pe) (gcc version 4.8 (GCC) ) #1 SMP PREE
(bootloader) kernel.version[2]: MPT Tue Mar 17 11:09:24 PDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.059s
maybe there is something wrong?
problem is solved:
1) TWRP- Backup from the running system
2) restore stock 5.02 (click)
3) then the droid lies back and nothing goes on
4) boot to bootloader run factory default
5) then the stock image boots
6) reboot tobootloader
7) install TWRP 2.8.7.0
8) TWRP - Restore
9) finish
i'm sure that 3),4),5) is not necessary.
So here's what all I did with my XT1033. (Asia_Retail)
Flashed an AOSP Slim 6 ROM. - Worked fine for over a month.
Wanted to return to STOCK.
Followed steps:
- Used XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
- Extracted and flashed using the fastboot commands.
- Every partition flashes with NO ERROR.
But rebooting the phone leads me to the AOSP Slim bootanimation.
Also system boots somewhat frozen, i.e no touch response.
**Even the stock recovery doesn't work, it still loads up TWRP (Also frozen, stuck at TWRP bootsplash)
Though I have flashed several times using mfastboot-v2.
So end result.
Fastboot seems to working fine but has no effect.
*** I can only boot in the fastboot mode.
Any help or information which would guide me in the right direction would be appreciated.:fingers-crossed:
Thanks for help guys.
Fastboot getvar all info
dracovoldy said:
So here's what all I did with my XT1033. (Asia_Retail)
Flashed an AOSP Slim 6 ROM. - Worked fine for over a month.
Wanted to return to STOCK.
Followed steps:
- Used XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml.zip
- Extracted and flashed using the fastboot commands.
- Every partition flashes with NO ERROR.
But rebooting the phone leads me to the AOSP Slim bootanimation.
Also system boots somewhat frozen, i.e no touch response.
**Even the stock recovery doesn't work, it still loads up TWRP (Also frozen, stuck at TWRP bootsplash)
Though I have flashed several times using mfastboot-v2.
So end result.
Fastboot seems to working fine but has no effect.
*** I can only boot in the fastboot mode.
Any help or information which would guide me in the right direction would be appreciated.:fingers-crossed:
Thanks for help guys.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA91601GLT
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 61BBC1020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jun 23 1:17:28 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_asia_ds/falcon_umt
(bootloader) ro.build.fingerprint[1]: sds:5.1/LPB23.13-56/55:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: sds.AsiaRetail.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: MSM8626BP_1032.3116.98.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 10:37:16 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.084s
BUMP!
ADB seems to work fine too. I can pull/push files from my SD Card
Good morning everybody,
I consider myself skilled at installing custom OS in 30+ family and friends phones.
Now last year i had non working Moto G XT1032, the sim card reader broke and it took me a few months to buy the part and change it. Once I changed it i tried booting the phone up and was shocked it didn´t boot. It was running Android 6.0.1 . I tried doing a clean OS install in the phone with no success at all ( It gets stuck at the patching system file unconditionally). The recovery in my phone is Philz Touch 6.58.7 ClockworkMod V6.05.1 . I then moved on to trying a diffrent recovery (TWRP 3.1.0.0) but I didn't succed in this. The phone and the fastboot script say it was success full but as I boot back to recovery it opens the CWM V.605.1.
I have tried many other recoveries, stock 4.4.4, Stock 5.1, many other custom os, formating and fixing partitions and nothing.
The thing is that NOTHING i do to the phones seems to change at all.
I hope somebody can help me please.
Ps. The fastboot code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA89007JT7
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: 3468F3010F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jul 24 12:54:49 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxmx/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/58:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.MX
(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-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld35) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 17:35:52 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: amxmx
I then moved on to trying a diffrent recovery (TWRP 3.1.0.0) but I didn't succed in this. The phone and the fastboot script say it was success full but as I boot back to recovery it opens the CWM V.605.1.
Click to expand...
Click to collapse
have u ever try to boot recovery from dekstop/without flashing recovery?
looks like this
fastboot boot twrp.img
i'm 100% it will boot to recovery (except when emmc died you can't do anything about it)if storage readable/writeable copy recovery and rom install it. if didn't work try sideload the rom.
adb sideload xxx.zip
The following steps have led me to a semi bricked device:
1) installed TWRP via the official guide: https://twrp.me/motorola/motorolamotog7power.html
2) flash rom zip Havoc after following wipe instructions: https://forum.xda-developers.com/g7-power/development/rom-havoc-os-v3-4-t4080387
I am stuck in fastboot. What should I do?
Device is TMobile... I am guessing this is the stock package I want. https://mirrors.lolinet.com/firmware/moto/ocean/official/TMO/
Should I follow this guide? https://techorfy.com/stock-rom-firmware-moto-g7-power/
Thank you!
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_t-f71f50d-191127
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326FXDV7
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 7B20403700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: removed*
(bootloader) meid:
(bootloader) date: 07-18-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Nov 27 11:13:12 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ocean_t/ocean:9/PCOS29.11
(bootloader) ro.build.fingerprint[1]: 4-134-8/41baf:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.441.12.ocean_t.t.
(bootloader) ro.build.version.full[1]: 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+ ([email protected]
(bootloader) kernel.version[1]: clbld153) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Wed No
(bootloader) kernel.version[3]: v 27 04:00:33 CST 2019
(bootloader) sbl1.git: MBM-2.1-ocean_t-b508f3a-191127
(bootloader) rpm.git: MBM-2.1-ocean_t-22daab3-191127
(bootloader) tz.git: MBM-2.1-ocean_t-d9613e6-dirty-191127
(bootloader) devcfg.git: MBM-2.1-ocean_t-d9613e6-dirty-191127
(bootloader) keymaster.git: MBM-2.1-ocean_t-d9613e6-dirty-191127
(bootloader) cmnlib.git: MBM-2.1-ocean_t-d9613e6-dirty-191127
(bootloader) cmnlib64.git: MBM-2.1-ocean_t-d9613e6-dirty-191127
(bootloader) prov.git: MBM-2.1-ocean_t-d9613e6-dirty-191127
(bootloader) aboot.git: MBM-2.1-ocean_t-f71f50d-191127
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 3
(bootloader) slot-retry-count:_b: 0
Re flash stock firmware
@rea1|1
I'll tell you what I do when I've been in the exact same situation as you're in now. Now just know that when I fastboot my RETUS factory image I always format data partition just before installing an aosp rom and while I'm on slot_a after I format data I always install the copy-partitions-AB.zip so that I don't brick, again. That being said if you've installed the copy partitions AB zip while on slot_a and it installed without errors in your recovery screen then I've had luck manually booting into bootloader mode then plug in my USB to laptop and open terminal and switch to the other slot and reboot system and if that doesn't boot I've had some successes manually getting bootloader mode back up then in terminal wiping data with fastboot erase userdata and sometimes I hit my arrow going up key on my laptop keyboard and repeat it again just because I'm crazy then reboot system. I've booted a few times when I was in purgatory like you explain in your post here. Haha. Other times I've came out of fastboot loop by getting to bootloader mode then booting orange fox recovery and hit reboot and whatever slot I'm currently on I press the other opposite letter A or B then format data partition and wipe data in recovery and reboot system. That's all through just trying various methods of pulling up outa purgatory. ? Just know that if you attempted what I say here and you have not installed the copy-partitions-ab.zip successfully while on slot_a there's a chance you may hard brick your device so careful. All else fails and it's still not booted up flash factory image for your device. That's how I do mine and I have about flashed my device to death for real. I'm staying put now because i believe my Power just might bite it soon because of how it's been acting and the signs I've been noticing.. Totally getting the 4gb ram unlocked model if this one dies. Fingers crossed. I'm proof that the copy partitions AB zip works ? ! I probably have about 300-400 rom flashes in since I hard bricked 3-4 months ago I believe it was last time. That copy zip when installed with no errors saves the day for sure!
Ps: When I mentioned switching to opposite slot and formatting data and wiping data in orange fox recovery then rebooting system when I booted successfully that way I was installing a GSI system.img Bliss 12.6 actually BADDD ASSS rom btw!! And I had installed system image to slot a and slot b previously. Hell one time I couldn't get Havoc 3.4 to boot regardless of what I did and I had a zip for superior os rom on my thumb drive so I said wth and swiped to install the rom then changed my mind so while my phone was in the process of installing Superior I manually booted to bootloader wiped data, system and cache flashed Havoc , rebooted bootloader formatted data, and wiped data in recovery after installing NikGapps and it wouldn't boot so I went back in bootloader and wiped data using fastboot erase userdata and it booted up. ? The way I see it I'll try anything as long as i know I'm safe and that copy zip makes that happen.
Edit added below May 2
**Also I have found it's better to just do the: fastboot boot recovery.img when I need it. But if you want to install TWRP definitely use Electimon's unofficial build. You can boot the twrp.img then flash the installer zip while in recovery but many roms come with custom recovery installed already. And just because it's official doesn't necessarily mean it's better than something that's unofficial. The official TWRP has issues or it did where it would freeze and touch screen would become non operational and Electimon's unofficial TWRP very seldom ever does that, if at all. If and when it does happen to get around it just keep manually booting bootloader then try again until it stops and you can select buttons on the recovery screen.
Hi,
I don't understand what the issue is with this this phone. It continually just bootloops. It gives the error plese see pick:
I tired:
1. Lenovo's rescue tool-it successfully flashed; still bootloops.
2. Verizon's firmware tool-it successfully flashed; still bootloops.
3. Downloaded the firmware manually and manually flashed every file; still bootloops.
The phone turns on every time, I can boot to fastboot and recovery. Bootloader says oem_locked. I don't know what else to do. I thought this would be an easy fix.
lolwatpear said:
Hi,
I don't understand what the issue is with this this phone. It continually just bootloops. It gives the error plese see pick:
I tired:
1. Lenovo's rescue tool-it successfully flashed; still bootloops.
2. Verizon's firmware tool-it successfully flashed; still bootloops.
3. Downloaded the firmware manually and manually flashed every file; still bootloops.
The phone turns on every time, I can boot to fastboot and recovery. Bootloader says oem_locked. I don't know what else to do. I thought this would be an easy fix.
Click to expand...
Click to collapse
Can you post
fastboot getvar all
Please remove your imei
SyberHexen said:
Can you post
fastboot getvar all
Please remove your imei
Click to expand...
Click to collapse
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-berlna_global-ebfa575b6e-220324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0609 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_KODIAK 1.0
(bootloader) serialno: ZD2223NZCV
(bootloader) cid: 0x0033
(bootloader) channelid: 0x83
(bootloader) uid: 65414223
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxx
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-08-2022
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid:
(bootloader) battery-voltage: 4218
(bootloader) iccid: 89148000007374885701
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: vzw
(bootloader) ro.build.fingerprint[0]: motorola/berlna_globalv/berlna:11/
(bootloader) ro.build.fingerprint[1]: RRM31.Q3-23-39-1-1/83c2c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.42R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g6571075f035f
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Sep 15 0
(bootloader) kernel.version[9]: 9:20:11 CDT 2021
(bootloader) git:abl: MBM-3.0-berlna_global-ebfa575b6e-220324
(bootloader) frp-state: no protection (0)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
all: listed above
finished. total time: 0.115s
Thanks
SyberHexen said:
Can you post
fastboot getvar all
Please remove your imei
Click to expand...
Click to collapse
anything you gathered from that information?
lolwatpear said:
anything you gathered from that information?
Click to expand...
Click to collapse
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
SyberHexen said:
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
Now it gives me "no valid operating system could be found". think this is an EMMC issue? Here's the updated getvar all:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-berlna_global-c0108f80f8d-23
(bootloader) version-bootloader[1]: 0324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0609 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_KODIAK 1.0
(bootloader) serialno: ZD2223NZCV
(bootloader) cid: 0x0033
(bootloader) channelid: 0x83
(bootloader) uid: 65414223
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-08-2022
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid:
(bootloader) battery-voltage: 4191
(bootloader) iccid: 89148000007374885701
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: vzw
(bootloader) ro.build.fingerprint[0]: motorola/berlna_globalv/berlna:11/
(bootloader) ro.build.fingerprint[1]: RRM31.Q3-23-39-1-1/83c2c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.42R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g6571075f035f
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Sep 15 0
(bootloader) kernel.version[9]: 9:20:11 CDT 2021
(bootloader) git:xbl: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:xbl_config: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:abl: MBM-3.0-berlna_global-c0108f80f8d-230324
(bootloader) git:aop: MBM-3.0-berlna_global-8cce5a89-230324
(bootloader) git:tz: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:hyp: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:devcfg: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:keymaster: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:storsec: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:uefisecapp: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:prov: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:qupfw: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:cpucp: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:shrm: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(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: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
finished. total time: 0.135s
lolwatpear said:
Now it gives me "no valid operating system could be found". think this is an EMMC issue? Here's the updated getvar all:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-berlna_global-c0108f80f8d-23
(bootloader) version-bootloader[1]: 0324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB MICRON MT256GASAO8U21 FV=0609 WB=2048
(bootloader) ram: 6GB MICRON LP4x DIE=24Gb M5-M8=FF 05 00 14
(bootloader) cpu: SM_KODIAK 1.0
(bootloader) serialno: ZD2223NZCV
(bootloader) cid: 0x0033
(bootloader) channelid: 0x83
(bootloader) uid: 65414223
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-08-2022
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid:
(bootloader) battery-voltage: 4191
(bootloader) iccid: 89148000007374885701
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: vzw
(bootloader) ro.build.fingerprint[0]: motorola/berlna_globalv/berlna:11/
(bootloader) ro.build.fingerprint[1]: RRM31.Q3-23-39-1-1/83c2c:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.42R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g6571075f035f
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Wed Sep 15 0
(bootloader) kernel.version[9]: 9:20:11 CDT 2021
(bootloader) git:xbl: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:xbl_config: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) git:abl: MBM-3.0-berlna_global-c0108f80f8d-230324
(bootloader) git:aop: MBM-3.0-berlna_global-8cce5a89-230324
(bootloader) git:tz: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:hyp: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:devcfg: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:keymaster: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:storsec: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:uefisecapp: MBM-3.0-berlna_global-74c51cc4-230324
(bootloader) git:prov: MBM-3.0-berlna_global-e85a79169-230324
(bootloader) git:qupfw: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:cpucp: MBM-3.0-berlna_global-a2abf7e-230324
(bootloader) git:shrm: MBM-3.0-berlna_global-56ea1542f-230324
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(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: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
finished. total time: 0.135s
Click to expand...
Click to collapse
Hmm let's try flashing manually in bootloader using fastboot
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot set_active b
fastboot set_active a
fastboot reboot bootloader
Please note and forward any commands that fail
SyberHexen said:
Hmm let's try flashing manually in bootloader using fastboot
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot set_active b
fastboot set_active a
fastboot reboot bootloader
Please note and forward any commands that fail
Click to expand...
Click to collapse
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.260s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Due to locked bootloader I guess?
--------------------------------------------------------
fastboot set_active b
fastboot set_active a
These commands just aren't recognized in terminal.
--------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
lolwatpear said:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.260s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Due to locked bootloader I guess?
--------------------------------------------------------
fastboot set_active b
fastboot set_active a
These commands just aren't recognized in terminal.
--------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
Click to expand...
Click to collapse
Bad news pretty sure this has been unlocked and relocked by some paid tools or exploited in general.
If you're willing to spend 60 usd send me a pm or contact me on telegram for better responses @SyberHexen
SyberHexen said:
Bad news pretty sure this has been unlocked and relocked by some paid tools or exploited in general.
If you're willing to spend 60 usd send me a pm or contact me on telegram for better responses @SyberHexen
Click to expand...
Click to collapse
I really appreciate the help. Just going to return it. It's not worth the effort for what I planned to use it for. Thank you.
Have you
lolwatpear said:
I really appreciate the help. Just going to return it. It's not worth the effort for what I planned to use it for. Thank you.
Click to expand...
Click to collapse
have you fixed your issue i have same model with same problem
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader[0]: MBM-3.0-berlna_global-c0108f80f8d-23
(bootloader) version-bootloader[1]: 0324
(bootloader) product: berlna
(bootloader) board: berlna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: VZW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 256GB SKhynix H9HQ21AECMADAR FV=A002 WB=2048
(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5-M8=06 06 00 10
(bootloader) cpu: SM_KODIAK 1.0
(bootloader) serialno: ZY22DF6JQZ
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: B959D531
(bootloader) token: inactive
(bootloader) securestate: oem_locked
(bootloader) factory-modes: allowed
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-25-2021
(bootloader) sku: XT2141-1
(bootloader) carrier_sku: XT2141-1
(bootloader) battid: SB18D10749
(bootloader) battery-voltage: 3763
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: unknown
(bootloader) ro.build.fingerprint[0]: motorola/berlna_global/berlna:11/R
(bootloader) ro.build.fingerprint[1]: RMS31.Q3-23-39-2-2-6/8aadbb:user/r
(bootloader) ro.build.fingerprint[2]: elease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.14.r1-16900-LAHAINA.0
(bootloader) version-baseband[0]: M7325_HI43_45.1293.01.44R BERLNA_PVT_V
(bootloader) version-baseband[1]: ZW_CUST
(bootloader) kernel.version[0]: Linux version 5.4.86-moto-g3865606212fe
(bootloader) kernel.version[1]: ([email protected]) (Android (6877366
(bootloader) kernel.version[2]: based on r383902b1) clang version 11.0.
(bootloader) kernel.version[3]: 2 (https://android.googlesource.com/tool
(bootloader) kernel.version[4]: chain/llvm-project b397f81060ce6d701042b
(bootloader) kernel.version[5]: 782172ed13bee898b79), LLD 11.0.2 (https:
(bootloader) kernel.version[6]: //android.googlesource.com/toolchain/llv
(bootloader) kernel.version[7]: m-project b397f81060ce6d701042b782172ed1
(bootloader) kernel.version[8]: 3bee898b79)) #1 SMP PREEMPT Fri Jan 7 21
(bootloader) kernel.version[9]: :44:52 EST 2022
(bootloader) git:abl: MBM-3.0-berlna_global-c0108f80f8d-230324
(bootloader) frp-state: protected (77)
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D09212
(bootloader) primary-display: tianma_nt36672e_1080x2460_vid
(bootloader) secondary-display: none
(bootloader) fdr-allowed: yes
all: listed above
Finished. Total time: 0.187s
SyberHexen said:
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
SyberHexen said:
Bootloader seems out of date compared to the factory firmware available for vzw.
I don't think the firmware is flashing correctly.
Please try using Moto Flash pro:
[Utility] MotoFlashPro
- = MotoFlashPro = - Utility to flash for Motorola devices on Qualcomm processors. Instruction Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive...
forum.xda-developers.com
With this vzw firmware:
BERLNA_GLOBAL_S1RMS32.68-43-16-9_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_cid51_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
Thank you so much for the firmware. I looked so long for it but never could get the one with the 9 at the end. Thank you!