I think I permanently soft bricked my phone.
Possible reasons
I tried to to flash cm-12-20150115-NIGHTLY-falcon from recovery-clockwork-touch-6.0.4.7-falcon . I couldn't figure out how to go to recovery mode from fastboot, so I went there with command prompt via "fastboot boot openrecovery-twrp-2.7.1.0-xt1032.img" . From there, I went to flash CM 12 nightly, but I made one fatal error, I never backed up my stock rom The device restarted, but it took me to "Fastboot reason: Fall-through from normal boot mode". I tried to go to recovery and normal powerup, but I got the message "boot up failed".
Attempted fixes
I scoured the interned to find a possible solution, I tried to re-install a new recovery from fastboot, but I always got the message "Mismatched partition size". I tried to boot from a recovery like I did before with "fastboot boot openrecovery-twrp-2.7.1.0-xt1032.img", but I had no avail, as this message showed up:
downloading 'boot.img'...
OKAY [ 0.275s]
booting...
FAILED (remote failure)
finished. total time: 0.476s
I even followed this thread, http://forum.xda-developers.com/showthread.php?t=2542219 (for restoring the stock firmware), and did everything down to the very letter, and it still didn't work. I kept getting messages like "bab check failed for boot" or "bab check failed for recovery"
I am at my wits end. I don't know if there is anything else to do. If anyone can find a solution to my problem, I'll be forever grateful.
Here is some useful info:
I rememeber updating my phone from ICS to KITKAT (4.4.4) months before i tried to root/flash it.
I bought my phone in the US
"get var all" returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA95000LZM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 85054F0115000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 16 21:19:52 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_retus/peregrine
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.56/56:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_r
(bootloader) ro.build.version.full[1]: etus.retus.en.US
(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.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gc20375a-00001-g804
(bootloader) kernel.version[1]: 2017 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Wed Aug 6 01:2
(bootloader) kernel.version[3]: 3:55 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: retus
all: listed above
croissanwish said:
I think I permanently soft bricked my phone.
Possible reasons
Click to expand...
Click to collapse
Why are you flashing falcon(xt1032) stuff to your peregrine(xt1045)?
They are not interchangeable.
meekrawb said:
Why are you flashing falcon(xt1032) stuff to your peregrine(xt1045)?
They are not interchangeable.
Click to expand...
Click to collapse
Oh I didn't know that. I'm kind of new to this. Which recovery should I flash?
@croissanwish Hi you have a MOTO G 4G (XT1042 in your case). You need to use this custom recovery https://www.androidfilehost.com/?fid=95864024717072097 TWRP 2.8.3.0 (Credits to Somcom3X). Then and only then flash the custom firmware you want from the http://forum.xda-developers.com/moto-g/4g-development area
If you still have issues after that then PM me.
hacktrix2006 said:
@croissanwish Hi you have a MOTO G 4G (XT1042 in your case). You need to use this custom recovery https://www.androidfilehost.com/?fid=95864024717072097 TWRP 2.8.3.0 (Credits to Somcom3X). Then and only then flash the custom firmware you want from the http://forum.xda-developers.com/moto-g/4g-development area
If you still have issues after that then PM me.
Click to expand...
Click to collapse
Thanks, I got it to work now, it turns out I was using the wrong recovery.
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
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