yashsingh1/xdaforums huggingface dataset:
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
I'm gonna need more info as to exactly what you did because myself and just about everyone else on Telegram has had NO issues updating to any version, especially the latest version without any issues whatsoever.

Send me a PM and I'll send you a link to the Telegram group. There we have options to get you un-bricked and maybe we can get a better understanding of what happened
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] washoq:
Thanks for quick answer. I already managed to unbrick my device using Lenovo Assistant. I have also successfully installed latest TWRP and Magisk. I don't know what caused the brick, maybe some Magisk issue. I went through the procedure like before, nothing has changed. Nevertheless it's rather not important now. I have my phone up and running, simply lost some of my data, but nothing important. Oh, and I am on Telegram group, just coudn't ask on in because my phone was dead ;)
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
Ok, good to hear! Glad you're back up and running and all is good again [emoji106]

Whatever did happen, at least Smart Assistant was able to save you without too much trouble

Also, in case you didn't know, there is a desktop app for Telegram for Windows, Linux and I would assume also Mac too.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] monolithcog:
*update*

Seems to be working now
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] zfk110:
Hi, is this work with Ocean? I dont see any TWRP for my G7 power
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
It does not, no. This is ONLY for the G7 Plus (lake).

However, if you use Telegram, there is an unofficial (beta) version in the G7 Power (ocean) group.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] zfk110:
I saw someone mentioned Telegram but I couldn't find the actual link/forum I don't know if its possible for you to PM me their link?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
Of course, will do it now
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] DJBhardwaj:
Couldn't we just use the 'Install Recovery Ramdisk' option in 'Advanced' to permanently install TWRP? Instead of flashing the installer zip?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Druadach:
Yes you can...

Taken from the G7 thread. My G7 is stock rooted with magisk and Riru Edxposed with TWRP flashed to Ramdisk. Works flawlessly.

No reason why this shouldn't work for the Plus variant as long as the TWRP is compatible. I had issues if using anything but the beta TWRP image tweaked for river G7. So get version for lake and no problems.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
Yes, you're absolutely right, I have included the repack tools which adds the Install Recovery Ramdisk option. The added benefit to the twrp-installer is that it can be directly flashed in Magisk Manager as a module. So, you guys can update twrp without actually having to reboot to recovery to do it.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] jc56au:
Zip signature verificaion failed!

Error installing zip file 'twrp-installer-3.3.1-v5.1-lake-jlb.zip'

Unlocked bootloader,

fastboot boot twrp-3.3.1-0-lake.img

then try and install. Same result downloading from a couple of mirrors and the md5 matches

Any ideas?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] jc56au:
Should have noted build PPWS29.98-66-2
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] DeividXDA:
black screen of death

Hello friend, I have done the tutorial correctly, when I got into the recovery, I switched from slot a to slot b (not for anything special, I was just curious), when I reboot it, the screen was turned off, and it never came back to turn on, power + volume does not work, the pc does not recognize it, I already have all the drivers / drivers of android adb / sdk and those of motorola, my phone was totally dead just for having made a switch, do you know how I could fix it ??
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] bricking Frank:
Hi there,

maybe you could help me with the following problem:

what I did:

- temporarily booted TWRP.img out off bootloader

- installed TWRP.zip out off temporarily booted TWRP from external_sd

- restarted into recovery

what happens:

- TWRP is coming up

- Touchscreen not working

- when I try to temporarily boot out off bootloader again I fail with the following error message:

"Sending 'boot.img' (28464 KB) OKAY [ 0.663s]

Booting (bootloader) Failed to load/authenticate boot image: Not Found

FAILED (remote: '')

fastboot: error: Command failed"

goal:

- want to temporarily boot TWRP out off bootloader again

- get TWRP runnig with touch working

any advise?

Thx a lot!
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] lautaro1:
Cannot boot it

HI. I tried to boot from it but I get a "FAILED (status read failed (No such device))" and then it shows "bad key" and proceeds to boot as normal.

Thank you.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
This sounds more like a fastboot/bootloader issue, not so much twrp. Unless your download is/was corrupted.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] texya:
:svetius::svetius:
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] KyrinMzia:
Hello i cannot temporarily boot twrp onto my moto g7 plus.

This is what i get from the command

PS C:\ADB\platform-tools> .\fastboot boot twrp-3.3.1-0-lake.img

Sending 'boot.img' (28468 KB) OKAY [ 0.609s]

Booting FAILED (remote: '')

fastboot: error: Command failed

PS C:\ADB\platform-tools>

I have my bootloader unlocked, usb drivers installed, data reset and i'm 99.9 percent certain that i have the correct twrp image. Please help!
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Kimpfimp:
$ fastboot boot twrp-3.3.1.0-lake.img

gets stuck in "downloading 'boot.img' . . . "

only way to break the loop is by restarting the bootloader or starting the device.

adb devices returns the device

fastboot devices returns the device

fastboot oem unlock returns that the device is already unlocked (just to double-check).

No earlier version of twrp is installed. No Magisk installed (since no twrp yet).

Build number: PPWS29.98-111-5

TWRP version: 3.3.1.0-lake (from the TWRP site), but have also tried other version here from the thread, all with the same results.

I am on Ubuntu 19.04 with both adb and fastboot installed, the device is recognized as it should.

Working with the USB-C v2 cable that came with the phone (plugged into an USB-C port in the motherboard of the PC).

I am not sure what I am doing wrong, any hints would be highly appreciated. I have been looking through various forums for about 2 hours without any results now.

EDIT: I purchased a different cable (USB-A to USB-C) and went through all the steps again on a Windows machine and it worked without any issues.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Vsx06:
No luck with booting :(

I'm on system:

[IMG="win ver"]https://i.ibb.co/PrJzRQx/win.jpg[/IMG]

Tried USB-C = USB-C and the most I managed to do is unlocking bootloader after ~15 tries

so I bought data transfer cable USB-A = USB-C in hope that it'll get better.

While phone is running android 'adb devices' is showing device.

I can use 'adb reboot bootloader' and after this step I get no devices connected.

I've used:

- Motorola Device Manager

- Motorola x64 drivers

- ADB Driver Installer (while android is running gives me positive)

- Minimal ADB and Fastboot, running CMD as admin

- Turned off verification of installed drivers (or however it's called)

[IMG="motog7+ shot"]https://i.ibb.co/mvBDVyD/IMG-20200105-165023.jpg[/IMG]

/Edit:

Forgot to mention that 'fastboot devices' works and returns: "ZY2268ZGK5 fastboot"

--------------------------------------------------------------------------------------------------------------------------------------------------------

Now I got to this point and it stays on "downloading" till I close adb manually...

And when I close it or disconnect cable I get this:

Before anyone asks, Yes cable is working on 2 phones (incl. this one) and two different PCs.

______________________________________________________________________________________________

/2nd Edit:

Managed to boot into temp recovery with USB-C cable by making bat file with commands in loop :)

'fastboot reboot bootloader'

'fastboot fastboot boot twrp-3.3.1-0-lake.img'

'fastboot reboot bootloader'

'fastboot fastboot boot twrp-3.3.1-0-lake.img'

After this tried to replicate succes and it worked every time by starting 'fastboot boot xxx.img' split second before bootloader reboot was fully finished.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Basti49:
Hi,

i'm having the exact same issue with my G7 Plus. i flashed TWRP via temporary TWRP and the permanent TWRP got stuck with no touchscreen support. Now i get the error mentioned above.

Unfortunately creating a batch loop like Vsx06 didn't work for me. I couldn't boot the TWRP image.

Is there a way to brick the bootloader, so it shows up as "Qualcomm HS-USB QDLoader 9008 (COM..)"? idk, like switching to slot b?

So i can blankflash it again? (i started with a bricked phone)

https://xdaforums.com/g7-plus/how-to/hard-brick-moto-g7-plus-downgrade-t3958608

thanks in advance

/Edit

I also found this thread interesting, having the same issue in another Moto Model, but since i'm not that deep into flashing, i couldn't find a way to adapt it for my G7 Plus

http://forum.gsmhosting.com/vbb/f783/moto-x4-xt1900-2-no-bootable-b-slot-failed-boot-linux-2696340/

/Edit 2

I found out, how to recover the phone. You have to flash a stock software command by command. Just like mentioned in the link above (for the Moto X4), i typed in every command of the flashfile.bat, which can be found in the stock software file:

https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

You'll have something like:

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot flash bluetooth BTFM.bin

fastboot flash dsp dspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash vendor vendor.img_sparsechunk.0

fastboot flash vendor vendor.img_sparsechunk.1

fastboot flash oem oem.img

fastboot flash oem_b oem_other.img

fastboot erase modemst1

fastboot erase modemst2

fastboot erase carrier

fastboot erase userdata

fastboot erase ddr

fastboot flash fsg fsg.mbn

fastboot flash bluetooth BTFM.bin

fastboot oem fb_mode_clear

fastboot reboot

After you've done this, the phone is back to stock and you can try flashing TWRP again.

This time it worked perfectly with no issues.

Cheers, Basti
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] moochermick:
Haven't installed twrp since 2015 on my lg G3 and quite a lot has changed but thanks to op everything went swimmingly and I now have twrp on my g7+ .
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] tuteec:
Unable to boot TWRP 3.3.1

Hi,

I can not boot my Moto G7 play (XT1952-1, with build nummer: PPYS29.105-134 or PPYS29.105-134-7) with the official twrp-3.3.1-0-lake image?

fastboot boot twrp-3.3.1-0-lake.img

downloading 'boot.img'...

OKAY [ 0.608s]

booting...

FAILED (status read failed (Too many links))

The phone then boot as normal.

Any suggestions?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] moochermick:
This is for Moto g7 plus not play.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] SpicyG:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.3.1-0-lake.img

downloading 'boot.img'...

OKAY [ 0.615s]

booting...

FAILED (remote failure)

finished. total time: 1.566s

I am getting these messages everytime I attempt to boot twrp. I searched on this site and Google and I couldn't find the answer on what is the issue. Has anyone else had this problem?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] SpicyG:
I wanted to add that my model number is: XT1962-1 US Retail according to the software channel. Also, I have unlocked the bootloader.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] 恩田珍:
Hi, it is nice to know that we have the very similar problem.

I have Motorola One Action and tried to install TRWP

The first time I thought I did successfully but then Android started booting error.

I couldn't find any answer other than sending the phone to Motorola, so I tried upgrading my Android from 9 to 10. It was successful.

But then I couldn't install TRWP getting the same error message.

I did research and found out TRWP is not quite compatible with Android 10.

This could be your case also?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] SpicyG:
You know what man it could be. The crazy thing is I have a Moto G6 and didn't have any issues rooting it. I'm glad to know I'm not the only one who had issues doing this. I was feeling a little lonely there for a bit haha.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jleeblanch:
I've upload updated versions for Stock Q and Q based custom roms with working decryption. These builds may also work on Pie roms too (but haven't tested).
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] maybeme2:
The twrp backups are taking up a significant percentage of my Moto G7 phone's available disk space. Are there suggestions on how to get around that?

I heard that nandroid backups to a usb flashdrive are not always dependable. Is that true?

I also have a separate sd on the phone. Again, I'm not sure how dependable these are because I've had occasional errors when going that route.

Other options?

Thank you.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] rhollan:
I've unlocked the bootloader on my 1T962-4 (Oops: it's an XT1952-4) Moto G7 Play, and tried to boot twrp.

One version, listed at the end of a different thread hear boots but won't let me install LineageOS 16 or 17.1 I get installer error. If I try the official or unofficial TWRP version here, it fails to boot.

I'm at wit's end. I know I need "the most recent" to install LineageOS, but I can't seem to find a "most recent" one that boots.

Can someone help?

At this point I will try restoring to stock (yet again), and start from scratch.

Update: That left me with a boot loop displaying "bad key" at top left. But. I noticed something: I don't have a 1962-4. I have a XT1952-4. Odd.

Update2: O.K. I managed to get the right firmware for it, and restore it to stock (there was an XML file that described the steps, obviously for some kind of installer, and I just decoded the meaning and applied the steps by hand. Now, to try and boot a recent TWRP. I wonder if the XT1952-4 vs XT1962-4 was what was causing me grief. I will have to see if there is a different TWRP for it.

Update 3: Still No go. The only TWRP that I can boot is small (I'll try to find the link to it) and won't install LineageOS. I've never had this much trouble with a phone. I'm not sure what "encryption" 'refers to. Encrypted partitions? That might explain installation failing. Also, talk of "I've uploaded a new version" does not help me if I don't know where.

Update4: FINALLY! SUCCESS! I suspected I was doing something stupid, and I was: I was uncompressing the .xz images incorrectly. Got ASOP and Lineage on the phone just fine after that with a restore to stock, fastboot -w, fastboot flash -u system <image>, fastboot reboot.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] rhollan:
Where have ytou uploaded a new version?

It might be obvious to old hats, but this noob has no idea where you uploaded a new version. I've been at this for a day and a half and I STILL can't find a TWRP that will install LineageOS on my Moto G7 Play XT-1952-4.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] maybeme2:
I would like to know the same thing.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] RedTopSR20:
I also cannot boot TWRP. Nor Lineage recovery.

XT1965-2. Android 9, security patch December 1, 2019.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] maybeme2:
I've always been a great believer in TWRP and it's backup/restore is one of the main reasons I root my phones: to restore the system when things go bad. But restoring a TWRP nandroid has failed and soft-bricked my Moto G7 phone more than once and I don't understand what has happened to the trusty TWRP backup I used to know.

Here's my latest tragedy:

I had a working Moto G7 phone with stock Android 9 rooted with Magisk. Trying to flash a system update using adb and flashback I messed up. So I did a twrp restore from a backup made the previous day thinking that would save the day. After all, isn't that why we do TWRP backups?

Rebooting after that restore caused a boot loop

. So, after meny tries and repeated TWRP restores, I finally flashed a stock boot.img from my W10 laptop and ended with the same boot loop or just the Moto image staying static.

I need a working phone so I gave up and decided to just do a

factory restore

of the phone wiping all data. That failed too!

TWRP is now no longer available as recovery. When I boot to recovery I now get the dead android with red exclamation mark. Using Power and Volume up, I got from there to the phone options and selected

factory restore with wipe user data

. But, now reboot gives me a static Moto image and nothing further. <crying>

I repeated the factory restore with wipe user data 2 more times with same result. I cannot boot to a reset working phone.

How do I get a working phone again? Someone

please

help.

This is beyong my knowhow and I am without a phone which I need badly.

Why are TWRP backups no longer dependable? Is it the Moto G7 phone?
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] KtownJeff:
I have used the restore and I found that when you restore it switches slots so you have to manually switch the slots to get the restore to boot or reflash magisk or reflash twrp..(then after an hour and 30 flashes later) yeah backup restore is not the same with these devices with the ab slots...After ota updates you have to reflash gapps and magisk to make it work right .I have a backup of etc i keep stashed and I backup data only usually...I too use TB more now.....I think its time to compile Orange fox recovery
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] maybeme2:
I think you hit it right on the nail. Especially about the."... after an hour and 30 flashes later.....". You just skipped mentioning the panic and desperation in the ordinary non expert end user.

I suspected it had something to do with twrp restoring to the wrong slot but did not know enough to resolve it. Actually that seems like a major bug in today's twrp's restore. There should be some way to warn the user, many of whom like me are not experts, about this!

Could you explain further, —in newbie steps— how to *avoid* this hapening again during future twrp restores?

How does one determine which slot is the active one?

How to then tell twrp to restore to that correct slot?

My twrp backup was done two days earlier. The twrp restore was done using the same twrp on the same phone without touching anything to do with the slots. Is it unreasonable to expect the restore would restore to the same slot?

Please explain in detail the exact steps for a successful twrp restore. It would help so many besides me.

What is Orange fox recovery?

Thank you again.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] KtownJeff:
The second paragraph from the OP explains the whole backup restore process......For me When i come from stock moto 10 and I first boot to recovery then install the installer...then I format data and install the AB slot copy zip..The first Rom I install will automatically boot off slot b because this slots are in theory for seamless OTA updates so the device thinks that first flash is update...k well slot is set to b after you flash/reboot..I have gotten in a habit of manually checking my active slot as well as flashing twrp installer with every rom flash...some of these roms flash boot images that have stock recovery like lineagos 17.1...if u get stock on the wrong slot and TWRP is froze reboot to bootloader and type fastboot getvar all it will give you all the info and tell you which slot is active.... if you need to change active slot the command is fastboot --set-active=a or fastboot --set-active= b ..... still confused right?? totally i spend half my day remembering which special zip goes with which GSI because out of the four major devs they all have their unique tweak.....I have found that if I flash a g7 plus specific custom rom it brings all my security and vendor up to date.....then i flash an phhtrebel gsi img and i got a very nice rom with all the moto g7 plus extras like the radio and the moto gestures....you wont break these phones unless u do something totallly crazy and the way the bootloader is locked down on these devices you can always bring it back to life if you have the firmware and can read so dont be too nervous...trust me Ive been up and down all around trying to get the ins and outs down. with this phone and I promise its gonna keep up.. hopefully later this year motorola will bump us on the Android 11 update G8 is 100% G7 50% chance....that would be nice because they will probably switch to the new fastbootd.......

Re read the OP (original post) of this thread and check this thread out too...

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] maybeme2:
Deleted
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] maybeme2:
As I described above a restore of a nandroid backup made with twrp 3.3.1 ended in a boot loop of my Moto G7 phone that I could not get out of. I am now fine after flashing stock android pie, rerouting, and reinstalling everything. After reflashing the stock rom, twrp, and Magisk I also flashed copypartition.zip.

Obviously I did something wrong when I did my restore 4 days ago. So, to avoid repeating this painful experience in the future are there special steps or precautions I should take to ensure my next twrp restore goes smoothly? Do I need to check the A B partition status? Do something else?

Was my backup possibly corrupted somehow?

Any suggestions are very welcome.

Thank you.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] KtownJeff:
new official 3.40 update!!

[MENTION=4481495]Jleeblanch[/MENTION] update OP please new update for recovery image and installer

https://dl.twrp.me/lake/
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] skullkid383:
Anyway someone can make official twrp for g7 play [MENTION=4481495]Jleeblanch[/MENTION] the one we have doesn't allow stock to boot and doesn't decrypt
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] Jonny_Bandana:
Has anyone experienced the issue where touch is disabled in TWRP?

After wiping everything and installing TWRP using the .zip, I boot into TWRP and the touch is not working.
[Moto G7 Plus ROMs, Kernels, Recoveries, & Other De] KtownJeff:
Yes that was in issue with the 3.40 build..... moto changed something in the firmware a couple builds back.... The official maintainer for the TWRP recovery updated but for some reason I dont think this thread got updated.... The new patched version is unofficial so it dosent show on the actual TWRP website..... Here is the link to the developers webportal.... There is some custom rom links as well.

https://dl.jleeblanch.com/TWRP/lake/