Is it still possible to backup and restore with TWRP in current state? Is this something that could have a potential fix somewhere down the line?
It'll backup all but data
Is it still possible to backup and restore with TWRP in current state? Is this something that could have a potential fix somewhere down the line?
I take it you're running stock OS?So every time Android get it's security patch, the A/B slot setup/system causes a crash? If there was a way, I'd due without the OTA update and do it manually to both slots maybe? This blows...
But will it restore it correctly? A backup without restore is useless.
But will it restore it correctly? A backup without restore is useless.
Last time I tried a twrp restore on this phone I ended up with unresolvable bootloops and an unusable phone for 3 days. Needed to re-install everything from scratch.
(My Moto G7 river is on stock android pie with permanently installed 3.3.1-2-river twrp, rooted with latest Magisk. Afraid since then to try another twrp restore and have to reinstall everything again).
In device manager if it's listed as Qualcomm you will need to Use a blankflash for lake if you have G7 PlusI think I bricked my g7 plus, is there any hope?
I unlocked the bootloader and used adb to load twrp, I tried to install it but kept getting an error, then I turned off the phone. Now it's unresponsive (won't turn on or do anything when plugged in). Am I screwed?
Factory reset will nether unroot, nor relockI have a rooted (Marian) Moto G7 running android 9.
If I 'factory reset' the phone will that relock the bootloader too?
Thank you for taking the time to answer. I really appreciate it.No...it'll just reinstall the factory ROM and 'unroot' the phone and show that annoying 'This phone can't be trusted. Re-locking requires a bit of ADB wizardry first. Not sure if the orig. signed stock kernal must too be installed as well but one would think everything would halk be bone stock to qualify for re-locking and the 'trust' status that goes with it. The a thread telling how to re-lock here somewhere...
EDIT:
Here u are are bro-man... https://forum.xda-developers.com/t/back-to-stock-relock-boot-loader-google-fi.3966959/
You can try the update option in LMSAThank you for taking the time to answer. I really appreciate it.
Maybe I'm going about this the wrong way. My wife has the same phone but unrooted. She just got a seamless OTA update from android 9 to 10 and I'm jealous. What I really want to do is move to android 10 too without having to reinstall all my apps and settings. Is that possible?
I am rooted by Magisk, have twrp nandroid backups and Titanium Backups (both on the second sdcard and on my laptop). I do have adb enabled and fastboot etc on my laptop.
What is the easiest way I could move to android 10 since I cannot receive ota updates? I am not knowledgeable in android/fastboot etc but I can follow clear instructions.
Is there a way?
Thank you.
Thank you sd shadow. I will read up on it. Thanks for the link.You can try the update option in LMSA
![]()
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...forum.xda-developers.com
You will need to pull the boot.img from LMSA update folder and patch it with Magisk, but you will not lose data.
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.