I am trying to install an Xposed module in my Android 9 Moto e6.
Unlocked the bootloader.
Have gotten the recovery.img strategy for Magisk to work, but it disables itself after the first rooted boot...and that's not the full Magisk capability. Because this phone doesn't have a Ramdisk, you can't use the patched-boot-image strategy.
Have *not* installed the full Magisk into the phone, and that's what I need to do (because the rest of the EdXposed install steps require this).
Does anybody know how to do this?
dav0dav0 said:
I am trying to install an Xposed module in my Android 9 Moto e6.
Unlocked the bootloader.
Have gotten the recovery.img strategy for Magisk to work, but it disables itself after the first rooted boot...and that's not the full Magisk capability. Because this phone doesn't have a Ramdisk, you can't use the patched-boot-image strategy.
Have *not* installed the full Magisk into the phone, and that's what I need to do (because the rest of the EdXposed install steps require this).
Does anybody know how to do this?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
So thru a lot of dead-end experimentation, I was able to understand better what's going on.
Once I was in the recovery mode that rooted via Magisk, the whole framework was already installed. You get the functionality just for one boot cycle.
So using it's modules-installer methods, I was able to install Riru, EdXposed, EdXposed manager, and the Xposed module I wanted...all in just a few minutes. Yay. But the module evidently doesn't work completely, so the whole adventure was a waste.
Have posted to the that module's discussion thread, but my fear is that even if I can get it to work in root, once I reboot its effects on the system will be gone (because it won't be there anymore).
Rooting E6 (Surfna)
I had success rooting this device (Moto E6 Surfna) by following the "Boot Image Patching" method here: https://topjohnwu.github.io/Magisk/install.html mingkee had success with the same method on the G7...
forum.xda-developers.com
sd_shadow said:
Rooting E6 (Surfna)
I had success rooting this device (Moto E6 Surfna) by following the "Boot Image Patching" method here: https://topjohnwu.github.io/Magisk/install.html mingkee had success with the same method on the G7...
forum.xda-developers.com
Click to expand...
Click to collapse
Did the root "stick" -- survive multiple boots? Using the "boot image patching" method (according to the Magisk installer page) can't work if your phone/OS doesn't have a RAMdisk, which mine does not.
So I can boot via recovery path into root...but it's not actually running from the boot partition.
Is that what you have experienced? Does your phone or OS version have a RAM disk?
dav0dav0 said:
Did the root "stick" -- survive multiple boots? Using the "boot image patching" method (according to the Magisk installer page) can't work if your phone/OS doesn't have a RAMdisk, which mine does not.
So I can boot via recovery path into root...but it's not actually running from the boot partition.
Is that what you have experienced? Does your phone or OS version have a RAM disk?
Click to expand...
Click to collapse
Why don't you believe your device does not have Ramdisk?
Ramdisk has been part of the boot partition for a while since android switched to a/b system slots.
Getvar all will say if you have a/b system slots.
sd_shadow said:
Why don't you believe your device does not have Ramdisk?
Ramdisk has been part of the boot partition for a while since android switched to a/b system slots.
Getvar all will say if you have a/b system slots.
Click to expand...
Click to collapse
Magisk Manager interrogates the phone, and it says no RAMdisk. Is there a reason to believe it's not authoritative (I assume it does its own getvar calls)
dav0dav0 said:
Magisk Manager interrogates the phone, and it says no RAMdisk. Is there a reason to believe it's not authoritative (I assume it does its own getvar calls)
Click to expand...
Click to collapse
You need to download the stock firmware, and patch the boot.img with magisk manager app
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
You need to download the stock firmware, and patch the boot.img with magisk manager app
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
That's exactly what I did, following the instructions. Looking at that page, it says "if you have no RAMdisk, you have no choice but to patch the recovery.img". It's possible the instructions are wrong, but they're pretty explicit.
Here's the getvar results -- I don't see a line that refers to RAMdisk...
bootloader) version: 0.5
(bootloader) version-bootloader[0]: MBM-2.1-surfna_retail-eed5d2ae395-20
(bootloader) version-bootloader[1]: 1124
(bootloader) product: surfna
(bootloader) board: surfna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=1F
(bootloader) cpu: MSM8940
(bootloader) serialno: ZY326LXK2L
(bootloader) cid: 0x0032
(bootloader) channelid: 0x96
(bootloader) uid: A18DEFEB00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 352181100763277
(bootloader) meid:
(bootloader) date: 08-26-2019
(bootloader) sku: XT2005-5
(bootloader) carrier_sku: XT2005-5
(bootloader) battid:
(bootloader) iccid: 89148000005179057245
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Nov 28 18:13:29 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/surfna/surfna:9/PPBS29.73
(bootloader) ro.build.fingerprint[1]: -81-20/2dfba:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.231.24.surfna.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-08100-89xx.0
(bootloader) version-baseband: M8940_41.00.01.163R SURF_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld163) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Tue No
(bootloader) kernel.version[3]: v 24 16:47:03 CST 2020
(bootloader) sbl1.git: MBM-2.1-surfna_retail-461a42d348-201124
(bootloader) rpm.git: MBM-2.1-surfna_retail-d84d6494-dirty-201124
(bootloader) tz.git: MBM-2.1-surfna_retail-60bc5c40d3-201124
(bootloader) devcfg.git: MBM-2.1-surfna_retail-60bc5c40d3-201124
(bootloader) keymaster.git: MBM-2.1-surfna_retail-60bc5c40d3-201124
(bootloader) cmnlib.git: MBM-2.1-surfna_retail-60bc5c40d3-201124
(bootloader) cmnlib64.git: MBM-2.1-surfna_retail-60bc5c40d3-201124
(bootloader) prov.git: MBM-2.1-surfna_retail-60bc5c40d3-201124
(bootloader) aboot.git: MBM-2.1-surfna_retail-eed5d2ae395-201124
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: comcast
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no: SP69A6P4BM
all: listed above
dav0dav0 said:
That's exactly what I did, following the instructions. Looking at that page, it says "if you have no RAMdisk, you have no choice but to patch the recovery.img". It's possible the instructions are wrong, but they're pretty explicit.
Click to expand...
Click to collapse
My bad, yes you need to use the recovery.img
Download the stock firmware
Copy the recovery.img to phone
Use magisk to patch recovery.img
Copy patched recovery to pc
Flash patched recovery to phone
sd_shadow said:
My bad, yes you need to use the recovery.img
Download the stock firmware
Copy the recovery.img to phone
Use magisk to patch recovery.img
Copy patched recovery to pc
Flash patched recovery to phone
Click to expand...
Click to collapse
Yep, that's exactly what I did.
So maybe you can answer a question that's super basic:
Since we're patching the recovery.img, if we do something while rooted, will that change survive and apply to the a normal (non-rooted) boot? The change survives soft-boots, but when you go through a hard boot I suspect that all those changes will be lost.
One of the sneaky things that Android does is erase the mod'ed recovery.img on the next hard boot, replacing it with the factory version...so unless the edXposed module somehow patches the "real" runtime, the changes it makes won't survive.
dav0dav0 said:
Yep, that's exactly what I did.
So maybe you can answer a question that's super basic:
Since we're patching the recovery.img, if we do something while rooted, will that change survive and apply to the a normal (non-rooted) boot? The change survives soft-boots, but when you go through a hard boot I suspect that all those changes will be lost.
One of the sneaky things that Android does is erase the mod'ed recovery.img on the next hard boot, replacing it with the factory version...so unless the edXposed module somehow patches the "real" runtime, the changes it makes won't survive.
Click to expand...
Click to collapse
Did you see this post?
and this?
Says Ramdisk No, but still works, annoyingly · Issue #3239 · topjohnwu/Magisk
Hello I have installed 21.0/8.0.0 on LineageOS 17.1 on both Xiaomi Redmi Note 8 (ginkgo) and Xiaomi Redmi Note 8T (willow). They both report "Ramdisk No" but work perfectly fine, without any messin...
github.com
dav0dav0 said:
Magisk Manager interrogates the phone, and it says no RAMdisk. Is there a reason to believe it's not authoritative (I assume it does its own getvar calls)
Click to expand...
Click to collapse
C:\>fastboot oem partition
(bootloader) sbl1: offset=128KB, size=512KB
(bootloader) rpm: offset=640KB, size=256KB
(bootloader) tz: offset=1152KB, size=1792KB
(bootloader) devcfg: offset=3200KB, size=128KB
(bootloader) aboot: offset=3456KB, size=1536KB
(bootloader) cmnlib: offset=4992KB, size=1024KB
(bootloader) cmnlib64: offset=6016KB, size=1024KB
(bootloader) keymaster: offset=7040KB, size=1024KB
(bootloader) prov: offset=8064KB, size=192KB
(bootloader) sbl1bak: offset=8320KB, size=512KB
(bootloader) rpmbak: offset=8832KB, size=256KB
(bootloader) tzbak: offset=9344KB, size=1792KB
(bootloader) devcfgbak: offset=11392KB, size=128KB
(bootloader) abootbak: offset=11648KB, size=1536KB
(bootloader) cmnlibbak: offset=13184KB, size=1024KB
(bootloader) cmnlib64bak: offset=14208KB, size=1024KB
(bootloader) keymasterbak: offset=15232KB, size=1024KB
(bootloader) provbak: offset=16256KB, size=192KB
(bootloader) modem: offset=16512KB, size=102400KB
(bootloader) fsc: offset=118912KB, size=4KB
(bootloader) ssd: offset=118916KB, size=8KB
(bootloader) dsp: offset=118924KB, size=16384KB
(bootloader) DDR: offset=135424KB, size=32KB
(bootloader) utags: offset=135552KB, size=512KB
(bootloader) utagsBackup: offset=136064KB, size=512KB
(bootloader) modemst1: offset=136576KB, size=2048KB
(bootloader) modemst2: offset=138624KB, size=2048KB
(bootloader) fsg: offset=140672KB, size=12288KB
(bootloader) persist: offset=152960KB, size=32768KB <---- this is were i am pretty sure the final code needs to sit
(bootloader) frp: offset=185728KB, size=512KB
(bootloader) cid: offset=186240KB, size=128KB
(bootloader) logo: offset=186368KB, size=16384KB
(bootloader) carrier: offset=202752KB, size=16384KB
(bootloader) metadata: offset=219136KB, size=16384KB
(bootloader) kpan: offset=235520KB, size=8192KB
(bootloader) boot: offset=243712KB, size=32768KB
(bootloader) recovery: offset=292864KB, size=49152KB
(bootloader) dtbo: offset=342016KB, size=8192KB
(bootloader) vbmeta: offset=350208KB, size=64KB
(bootloader) misc: offset=350336KB, size=1024KB
(bootloader) mota: offset=351360KB, size=512KB
(bootloader) syscfg: offset=351872KB, size=512KB
(bootloader) logs: offset=352384KB, size=2048KB
(bootloader) apdp: offset=354432KB, size=256KB
(bootloader) msadp: offset=354688KB, size=256KB
(bootloader) dpo: offset=354944KB, size=8KB
(bootloader) devinfo: offset=354952KB, size=512KB
(bootloader) mmi_misc: offset=355584KB, size=128KB
(bootloader) persist2: offset=355712KB, size=8192KB
(bootloader) padA: offset=363904KB, size=12928KB
(bootloader) hw: offset=376832KB, size=8192KB
(bootloader) sp: offset=385024KB, size=8192KB
(bootloader) oem: offset=393216KB, size=655360KB
(bootloader) vendor: offset=1048576KB, size=311296KB
(bootloader) cache: offset=1359872KB, size=262144KB
(bootloader) system: offset=1622016KB, size=2768896KB
(bootloader) userdata: offset=4390912KB, size=10997743KB
OKAY [ 0.172s]
Finished. Total time: 0.172s
yea it doesn't look like it
Related
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.
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 everyone.
I purchased a new Motorola Moto G6 with the intention to try out using LineageOS instead of the stock rom.
Here's everything that used to appear in the About section of the Settings. Keep in mind I selected Portuguese so I'll be translating some labels:
Software channel: retin
Android version: 8.0.0
Android security patch level: 2018-04-01
Base band version: M450_03.08.10.51R ALI_INDIADSDS_CUST
Kernel version: 3.18.71-perf-ga4749e5
[email protected] #1
Fri Mar 30 11:53:22 CDT 2018
Version number: OPS27.82-45
This is my first time messing with phones like this. I am a Computer Engineer, though.
I started following the instructions here. I enabled developer options in the settings, enabled USB debugging and allowed OEM unlocking.
Then I unlocked the bootloader. I'm using ADB and Fastboot that came with Android Studio.
I ran fastboot oem get_unlock_data, got the code, inserted in on the Motorola website, got the email with the unlock key and unlocked it with fastboot oem unlock UNIQUE_KEY.
Then I installed TWRP 3.3.1-0. No problems there.
Then I had to search for the link to download LineageOS and GApps because it looked like the steps I was following were incomplete.
I downloaded LineageOS from here and GApps from here. For the latter, I chose ARM64, Android 10.0 and full. I transfered them to the internal storage using Android Studio Device File Explorer.
Then I followed the YouTube video from the first link. I had trouble wiping because of encryption, so it seems. I followed this to proceed. Using a pass or a pin didn't work. The next solution, Repair File System, was unavailable. I could only see Change File System. Then I formatted /data to EXT2 then back to EXT4 and it worked.
Then I tried to flash LineageOS. I got error 255. I looked here. Apparently, I should have used a 64 bit TWRP. I found one here and flashed it. Then I was able to flash both LineageOS and GApps. No error messages here.
Then I rebooted without installing the TWRP app. I got the following:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect you device to your computer to get
the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from normal boot mode
USB connected
I searched and didn't find much. I looked for the Software Repair Assistant but it seems it's only good to reinstall the stock ROM. I still want to install LineageOS, though.
I found some results about flashing boot.img and some other stuff, but I'm too afraid to hard brick my phone to follow any instructions that haven't been written specifically for my situation.
I still can access TWRP. I wiped and installed again to double check that there wasn't any error messages during flashing and then again to try installing the TWRP app, but the prompt for that didn't show up.
Please advise on what to do to complete installing LineageOS on my Moto G6.
Update 2020-12-15: It seems that the tutorial I followed has been updated. Now there are no steps missing. I'll try again using the files provided there.
Thanks in advance.
According to this, I can bump. So, bump 1/7.
GuiRitter said:
Then I had to search for the link to download LineageOS and GApps because it looked like the steps I was following were incomplete.
Click to expand...
Click to collapse
It seems the steps have now been fixed. I downloaded the GApps from there, as the LineageOS ROM was apparently the same as the one I already had. Tried to flash again. No change.
It was suggested elsewhere that I might have to disable dm-verity. I was asked to install no-verity-opt-encrypt-6.1.zip. I tried and it failed with the following message in the log: /tmp/updater[63]: .: config.sh: No such file or directory.
It was also suggested to patch boot.img. However, it was also said that LineageOS should come with a patched one, so I didn't look further due to lack of time.
I was asked to flash the stock ROM in order to run Magisk Manager and get a screenshot. I used the Lenovo Rescue and Smart Assistant in order to do that. Phone is working again, but I still want to install LineageOS. Here's the screenshots.
In the process, I learned about the fastboot getvar all command. Here's the output
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-sdm450-C3.09
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) serialno: ZF62236MJW
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 63B4457200000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) imei: [REDACTED]
(bootloader) meid:
(bootloader) date: 08-11-2018
(bootloader) sku: XT1925-13
(bootloader) carrier_sku: XT1925-13
(bootloader) battid: SB18C18509
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue May 9 7: 0:46 UTC 1972"
(bootloader) ro.build.fingerprint[0]: motorola/ali/ali:8.0.0/OPS27.82-45
(bootloader) ro.build.fingerprint[1]: /56:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.81.56.ali.retail.
(bootloader) ro.build.version.full[1]: en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_03.08.10.51R ALI_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-ga4749e5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 30 11:53:22 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC3.09-0-g4650d8f
(bootloader) rpm.git: git=MBM-NG-VC3.04-0-g02798db
(bootloader) tz.git: git=827710b-dirty
(bootloader) devcfg.git: git=827710b-dirty
(bootloader) keymaster.git: git=827710b
(bootloader) cmnlib.git: git=827710b
(bootloader) cmnlib64.git: git=827710b
(bootloader) prov.git: git=827710b-dirty
(bootloader) aboot.git: git=MBM-NG-VC3.09-0-g225f207
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.082s
Solved with help from here.
what was the problem/ solution finally? Did you try again with other stock ROM 8.1.0 / 9.0 or was it GApps issue?
aIecxs said:
what was the problem/ solution finally? Did you try again with other stock ROM 8.1.0 / 9.0 or was it GApps issue?
Click to expand...
Click to collapse
I can't say, because I did 2 things differently: 1) I used the GApps from the tutorial I was following, for which there was no download link previously; 2) I followed your step by step instead of those from the tutorial I was following.
so you did not flash Android 8.1.0 / 9.0 because it worked with Android 8.0 this time, and your device is not system-as-root therefore you did not do the workaround bind mounting /system_root/system from adb shell
strange because the steps are exactly the same. it should have worked like the first time because you did nothing wrong
aIecxs said:
so you did not flash Android 8.1.0 / 9.0 because it worked with Android 8.0 this time, and your device is not system-as-root therefore you did not do the workaround bind mounting /system_root/system from adb shell
strange because the steps are exactly the same. it should have worked like the first time because you did nothing wrong
Click to expand...
Click to collapse
Just to be clear: Android 8.0 was the stock ROM. The LineageOS 17.1 that I used is supposed to be Android 10.0 (I forgot to double check yesterday but I think it's correct).
EDIT: actually, the Lenovo tool installed an Android 9. The original was 8.
so you did flash Android 9.0 (stock ROM) - probably the reason why it worked this time... LineagesOS installer is targeting Android 8.1.0 (probably min requirement) - seems it doesn't install well on Android 8.0 or below because of incompatibility with firmware/radio
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
Tried to flash to EU rom from china rom by following this tutorial and using the minimal adb and fastboot method. Now phone stuck in restart loop and when attempt to enter recovery mode, says "boot failed, press power button to retry" and at the bottom says "no bootable A/B slot". I'm at my wit's end, please send help.
Yasai1204 said:
Tried to flash to EU rom from china rom by following this tutorial and using the minimal adb and fastboot method. Now phone stuck in restart loop and when attempt to enter recovery mode, says "boot failed, press power button to retry" and at the bottom says "no bootable A/B slot". I'm at my wit's end, please send help.
Click to expand...
Click to collapse
What does getvar all say? (remove imei before posting it).
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nio_retail-6b3ddf45a7d-210503
(bootloader) product: nio
(bootloader) board: nio
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: SUPER
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB KIOXIA THGJFAT0T44BAILB FV=1001 WB=0
(bootloader) ram: 8GB MICRON LP5 DIE=8Gb CH=4
(bootloader) cpu: SM8250 2.1
(bootloader) serialno: ZY22BZBRKZ
(bootloader) cid: 0x000B
(bootloader) channelid: 0xc1
(bootloader) uid: E2421054
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (2)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 03-16-2021
(bootloader) sku: XT2125-4
(bootloader) carrier_sku: XT2125-4
(bootloader) battid: SB18C74374
(bootloader) battery-voltage: 3858
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 1
(bootloader) ro.carrier: retcn
(bootloader) ro.build.fingerprint[0]: motorola/nio_retcn/nio:11/RRN31.Q1
(bootloader) ro.build.fingerprint[1]: -20-52-3/2d98f3:user/release-keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-09000-SMxx50.0
(bootloader) version-baseband[0]: M55_HI20_209.334.01.69R NIO_PVT_SUPERD
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[4]: pr 23 20:53:41 CDT 2021
(bootloader) git:xbl: MBM-3.0-nio_retail-7815c7fde-210503
(bootloader) git:xbl_config: MBM-3.0-nio_retail-7815c7fde-210503
(bootloader) git:abl: MBM-3.0-nio_retail-6b3ddf45a7d-210503
(bootloader) git:aop: MBM-3.0-nio_retail-dca7944-210503
(bootloader) git:tz: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:hyp: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:devcfg: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:cmnlib: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:cmnlib64: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:keymaster: MBM-3.0-nio_retail-7f7b8912-210503
(bootloader) git:storsec: MBM-3.0-nio_retail-7f7b8912-210503
(bootloader) git:uefisecapp: MBM-3.0-nio_retail-7f7b8912-210503
(bootloader) git: prov: MBM-3.0-nio_retail-2d48c86f-210503
(bootloader) git:qupfw: MBM-3.0-nio_retail-e953b4db-210503
(bootloader) git:spss: MBM-3.0-nio_retail-f23af1d-210503
(bootloader) frp-state: no protection (77)
(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: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93721
(bootloader) primary-display[0]: tianma_nt36672c_1080x2520_670_105hz_dsc
(bootloader) primary-display[1]: _vid
(bootloader) secondary-display:
all: listed above
finished. total time: 0.128s
Yasai1204 said:
Tried to flash to EU rom from china rom by following this tutorial and using the minimal adb and fastboot method. Now phone stuck in restart loop and when attempt to enter recovery mode, says "boot failed, press power button to retry" and at the bottom says "no bootable A/B slot". I'm at my wit's end, please send help.
Click to expand...
Click to collapse
You really need to unlock the bootloader before trying to change the software channel.
Recovery isn't going to help with this.
You will need fastboot/bootloader mode
Download the RetCN Firmware
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
XT2125-4_NIO_RETCN_11_RRN31.Q1-20-52-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the file
find the flash_file.xml
Open the .XML with a text program like notepad++
Copy the text in the .XML and paste that text to the
Online FlashFile Converter
Use those commands to flash the firmware with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You really need to unlock the bootloader before trying to change the software channel.
Recovery isn't going to help with this.
You will need fastboot/bootloader mode
Download the RetCN Firmware
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
XT2125-4_NIO_RETCN_11_RRN31.Q1-20-52-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the file
find the flash_file.xml
Open the .XML with a text program like notepad++
Copy the text in the .XML and paste that text to the
Online FlashFile Converter
Use those commands to flash the firmware with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you. Will try.
sd_shadow said:
Online FlashFile Converter
Click to expand...
Click to collapse
Hi sorry but in this thread when creating the flashall.bat file, where do I move it to before executing it? The bullet points says: "Move bat file to" before cutting off and the next bullet says "execute bat file by double-clicking on it"
Yasai1204 said:
Hi sorry but in this thread when creating the flashall.bat file, where do I move it to before executing it? The bullet points says: "Move bat file to" before cutting off and the next bullet says "execute bat file by double-clicking on it"
Click to expand...
Click to collapse
Move bat file to the platform-tools folder (adb/fastboot.exe)
Alright, thank you.
sd_shadow said:
Move bat file to the platform-tools folder (adb/fastboot.exe)
Click to expand...
Click to collapse
Thank you so much for your help! My phone has been restored successfully. I honestly thought that I'd bricked the phone and blown my 500 bucks, really should have researched a bit more before attempting this kinda thing. Again, truly thankful for your help!