[Moto G8 Plus ROMs, Kernels, Recoveries, & Other De] rygle:
The Retapac link you provided is for a different phone model (Code Name "Evert"). The Moto G8+ has the code name "DOHA" and the Retapac (Retail Asia Pacific) link is https://mirrors.lolinet.com/firmware/moto/doha/official/RETAPAC/

If you are from a different region, you might need RETEU (Retail Europe), RETUS (US), RETBR (Brazil), RETIN (India) - see here for the list for this phone - https://mirrors.lolinet.com/firmware/moto/doha/official/

Also, you should *NEVER*, *NEVER* do "fastboot erase modemst1" or "fastboot erase modemst2" as this can delete your efs and/or persist partitions, which has been a massive problem on other Motorola Phones (G5, G5S) and can lead to not being able to get data, make calls, as these partitions have your unique EMEI number/code and other unique data that your phone needs. You cannot restore a persist partition or EFS data from another phone, they are unique. It can also cause problems with the camera making all images very green, well at least it did on my G5S.

---------- Post added at 02:27 AM ---------- Previous post was at 02:12 AM ----------

There seems to be a problem backing up the EFS using the 3.40 version of this recovery. I have not tried any earlier versions.

The backup fails. The log file shows it is looking for a partition that doesn't exist.

It is looking for the following, as indicated in the setup part of the log file.

/efsg | | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition
SubPartition_Of: /efs1
Primary_Block_Device: /dev/block/bootdevice/by-name/fsg
Display_Name: efsg
Storage_Name: efsg
Backup_Path: /efsg
Backup_Name: efsg
Backup_Display_Name: efsg
Storage_Path: /efsg
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

When it gets down to doing the actual backup, it reports the following.

And then it quits.

When in the file manager in TWRP, I am able to see that, at least on my phone, there is no "/dev/block/bootdevice/by-name/fsg" partition, but there is both a "/dev/block/bootdevice/by-name/fsg_a" and "/dev/block/bootdevice/by-name/fsg_b"

For now, I have backed up the following partitions manually in the hope that I have the right ones

/dev/block/mmcblk0p42 - seems to be EFS1

/dev/block/mmcblk0p43 - seems to be efs2

/dev/block/mmcblk0p35 - should be efsc

/dev/block/bootdevice/by-name/fsc - should be FSC

/dev/block/bootdevice/by-name/fsg_a - should be efsg_a

/dev/block/bootdevice/by-name/fsg_b - should be efsg_b

And I also DD'd the following for good measure
/dev/block/bootdevice/by-name/modem_a
/dev/block/bootdevice/by-name/modem_b
/dev/block/bootdevice/by-name/persist
/dev/block/bootdevice/by-name/prodpersist
/dev/block/bootdevice/by-name/uefiscapp_a
/dev/block/bootdevice/by-name/uefiscapp_b
/dev/block/bootdevice/by-name/uefivaristore

I booted the phone into TWRP, then ran and ADB shell on the PC.

adb devices (make sure there's a response)
adb shell (to start a remote command shell)
md /sdcard1/backup (make a folder to backup the partitions to)
then dd if=/dev/block/bootdevice/by-name/fsg_a of=/sdcard1/backup/fsg_a.img

And so on doing dd for each partition until I had a bunch of img files that I could copy across by mounting the sdcard storage on the PC.

Could you please look into this and make appropriate changes to TWRP?

Thanks!