yashsingh1/xdaforums huggingface dataset:
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
As far as I remember there is no blankflash especially for the Moto G5+, it has never been leaked.

But there is one for a very similar device, the Moto Z2play (albus).

This post explains it a bit;

I would try all other solutions before I'd use blankflash.

I personally never had to but as I read there are several things thst could go wrong.
[Moto G5 Plus Guides, News, & Discussion] DEJAVU54:
So try LMSA and hope for the best?
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
https://mirrors.lolinet.com/firmware/moto/potter/blankflash/

Yes, putting a Moto device in EDL Mode should be the last thing tried.
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
LMSA is easy to use, it takes just a few minutes to use, there are no settings to mess with, it pretty much plug and play.

and in my experience, it either works or it doesn't.

If it doesn't you just move on to try something else.
[Moto G5 Plus Guides, News, & Discussion] DEJAVU54:
So, what should I try first? LMSA?

EDIT: Just saw your message. In LMSA, the target version is slightly different from the current version. Would it cause a problem? Also, I'm on the pixel experience ROM so that would work on that ROM, no?
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
I have no idea if your LoLTE issue is related to your flashing issue.

The Blankflash is to fix your bootloader flashing issue.
[Moto G5 Plus Guides, News, & Discussion] DEJAVU54:
So, even LMSA won't solve my VoLTE issue?
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
Can you post a screen shot of LMSA screen with snip?
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
It likely will but it could be unrelated
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
LMSA will always choose the newest Software available.
[Moto G5 Plus Guides, News, & Discussion] DEJAVU54:
So I'm fine with these settings, right?
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
I don't know, it doesn't say RetIN in the file name,

but the bootloader is unlocked, so it shouldn't matter.

If it was my device I would try it.
[Moto G5 Plus Guides, News, & Discussion] DEJAVU54:
Potter is RETIN, no?
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
No

RetIN is just one of 20+ software channels for Moto G5 plus

see the list

https://mirrors.lolinet.com/firmware/moto/potter/official/
[Moto G5 Plus Guides, News, & Discussion] DEJAVU54:
Well, nevermind. Tried LMSA, still getting IMEI 0 and no cellular networks.

I guess it's done now.
[Moto G5 Plus Guides, News, & Discussion] Fedegblack:
How do I know which version from lolinet to install? I'm from Argentina.
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
Use the

Device Model #

,

Codename, and Software Channel

[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...

xdaforums.com
[Moto G5 Plus Guides, News, & Discussion] Fedegblack:
Thank you, I managed to get the correct file. One problem though, I followed every step without any trouble but didn't manage to fix what I was looking to fix, which is a bootloop. It was on a stock phone and removed the userdata line to keep the files.

Question now is, how to proceed, how to troubleshoot and if deleting userdata would be a sure fix since I don't want to lose it for nothing.

Thanks again for the help.
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
So you flashed the stock firmware to fix a bootloop? What caused that bootloop in the first case?

Are you rooted? If yes any modules installed ?
[Moto G5 Plus Guides, News, & Discussion] Fedegblack:
Yes, flashed stock on stock. No root, and I have no idea what caused the bootloop.
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
The bootloop (or is it more a problem like booting into Fastboot mode/ stop booting at all?) appeared out of the blue? Nothing you remember that you did before?

Maybe it would be better to delete/format data too.

You can also try LMSA (Lenovo Moto Smart Assistant, now called Rescue and Smart Assistant) to flash stock firmware, some users fixed their problem that way:

Rescue & Smart Assistant| Motorola Support US

Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Rescue & Smart Assistant

motorola-global-portal.custhelp.com
[Moto G5 Plus Guides, News, & Discussion] Fedegblack:
It's an inconsistent bootloop where it shows the moto logo for a minute and then starts blinking every now and then, and sometimes it displays "hello moto". But never reaches full boot. I asked what the person did before the loop but seems pretty ordinary usage. I'll try then with the addition of data loss.

Thanks.

Update: LMSA did the job.
[Moto G5 Plus Guides, News, & Discussion] WordsworthFhang:
Hi. I'm trying to root my G5+ but when I try and flash TWRP in line with the instructions above (Now input the command: "fastboot flash recovery [filename].img", where [filename] is the name of your TWRP image file. Tap Enter and it will take a few seconds to flash the new recovery.), I get the following:

C:\adb>fastboot flash recovery twrp.img

target reported max download size of 534773760 bytes

sending 'recovery' (17424 KB)...

OKAY [ 0.391s]

writing 'recovery'...

(bootloader) Image not signed or corrupt

OKAY [ 0.312s]

finished. total time: 0.703s

So the process fails.

I've tried the most recent two .img releases from TWRP (https://eu.dl.twrp.me/potter/), twrp-3.5.2_9-0-potter.img and twrp-3.5.1_9-0-potter.img, but both give the same result.

Any thoughts gratefully received :)
[Moto G5 Plus Guides, News, & Discussion] sd_shadow:
If you just want root, use the patched boot.img method.

[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...

xdaforums.com
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
As @sd_shadow posted above, if it's just for rooting use the patch boot.img method.

Else:

Have you booted into TWRP after flashing it to make it stick before booting into system?

Because the message you got doesn't say that the process failed. TWRP images are signed with their own key so "not signed" is a normal output.

That the image could be corrupted is most probably not true as you tried different ones and not all of them should be damaged when being downloaded.

Also the process ends with "okay".

But to make sure that there's nothing wrong in the download process use another browser for downloading the image and try again.

There were reports that some browsers have problems, namely Firefox.
[Moto G5 Plus Guides, News, & Discussion] CharlieGarg:
i have done all the steps as above but i got network error. It shows no service after the installation. I have did as above multiple times but nothing changed. Even after installing twrp, i formatted all the system and flash the rom again using "flashallO.bat". Previously i was on Arrow OS 10.0. Now when i flash the Arrow Os again, i got network back. Please help so that i can switch back to stock. Thank You.
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
Her area few points to take care of:

- Make sure that you choose the correct firmware for your location. (e.g. RETIN for India)

If you were rooted and in some cases coming from a custom ROM:

- Don´t delete the fastboot erase userdata command from the flashallO.bat so that it will be omitted because some parts of Magisk or other root apps may reside at that location.

- You have to

erase everything

to be on the safe side.

- So save your internal userdata like pictures, documents, music etc. to a PC or a SD card before you start the

process!

- Flashing stock will overwrite the recovery.img (TWRP) and the boot.img (Magisk) so you don´t have to unroot or reflash stock recovery

As a last resort you can try LMSA (Lenovo Motorola Smart Assistant):

https://xdaforums.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
[Moto G5 Plus Guides, News, & Discussion] CharlieGarg:
Whenever i flash stock image, imei no becomes '0' and flshing any custom rom 10.0 or higher restores the imei number. So can you please tell me what to do? Also using LMA when i am on bootloader screen it shows IMEI number but when phone booted up, it shows imei number 0
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
So you flashed the firmware by LMSA?

Have you erased your persist.img at some point?

Maybe a custom ROM has changed something in your persist partition.

What does the getvar all command return?
[Moto G5 Plus Guides, News, & Discussion] CharlieGarg:
(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8953-C0.92

(bootloader) product: potter

(bootloader) board: potter

(bootloader) secure: yes

(bootloader) hwrev: P3B

(bootloader) radio: 6

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F

(bootloader) cpu: MSM8953

(bootloader) serialno: ZxxxxxxxxV

(bootloader) cid: 0x0032

(bootloader) channelid: 0xc0

(bootloader) uid: 3D72BB2E00000000000000000000

(bootloader) securestate: flashing_unlocked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 534773760

(bootloader) reason: Volume down key pressed

(bootloader) imei: 3xxxxxxxxxxxxx8

(bootloader) meid:

(bootloader) date: 04-26-2017

(bootloader) sku: XT1686

(bootloader) carrier_sku:

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Fri May 1 20:22:42 UTC 1970"

(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:8.1.0/O

(bootloader) ro.build.fingerprint[1]: PS28.85-17-6-2/77e7:user/release-k

(bootloader) ro.build.fingerprint[2]: eys

(bootloader) poweroffalarm: 0

(bootloader) ro.build.version.full[0]: Blur_Version.28.261.2.potter.reta

(bootloader) ro.build.version.full[1]: il.en.US

(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0

(bootloader) version-baseband: M8953_46.55.07.90u POTTER_INDIADSDS_CUST

(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7b625a0 (hud

(bootloader) kernel.version[1]: soncm@ilclbld112) (gcc version 4.9.x 201

(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP

(bootloader) kernel.version[3]: T Mon Mar 4 14:31:59 CST 2019

(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b

(bootloader) rpm.git: git=92e5e21-dirty

(bootloader) tz.git: git=27e6e4b-dirty

(bootloader) devcfg.git: git=27e6e4b-dirty

(bootloader) keymaster.git: git=27e6e4b-dirty

(bootloader) cmnlib.git: git=27e6e4b-dirty

(bootloader) cmnlib64.git: git=27e6e4b-dirty

(bootloader) prov.git: git=27e6e4b-dirty

(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0

(bootloader) frp-state: no protection (77)

(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
[Moto G5 Plus Guides, News, & Discussion] Jrhotrod:
Just stumbled upon this thread. I've not been active on XDA, and I've since moved from my G5+ to the Pixel 4a, but really great to see the community for this phone still kicking. Great job @Wolfcity & thanks for the credit in the OP 😄
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
Hey @Jrhotrod , nice to hear you.

I'm on a Xiaomi Mi 9T device in the meantime but as the Moto G5+ is still in use by a lot of people (and is my testing device) I'm having a look into the forum from time to time. Even the good old Moto G2014 is still in development!

No need to say thanks for the credits, should be normal to name sources. My Moto was rooted by your really good tutorial so thank you too!👍
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
Hey. Maybe you can help me. I followed your guide to flash stock, did all that. I have stock installed, with the latest TWRP and Magisk. And every time I boot up, it tells me "Your device has been unlocked and can't be trusted," and then it boots into Recovery. I can only get to the system if I choose Reboot > Bootloader and then choose the Start option from the bootloader.

I have tried flashing several different things that are supposed to remove dm verity, or turn it off, or whatever, and none of them worked. Also, I tried installing a custom rom with its own kernel, and the problem did not go away, so I'm assuming the solution must lie somewhere other than boot.img.

What do I do? How do I get this thing working 100%, booting normally?

XT1687, RETUS
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
The "Your device has been unlocked and can't be trusted" screen is normal after unlocking bl , you have to flash a custom bootlogo (as "logo.bin" or as a zipped file, check the forum for custom bootlogos).

When the device boots into bootloader instead of system try this fastboot command:

fastboot oem fb_mode_clear
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
Didn't help. And it doesn't boot into bootloader. It boots into Recovery. Every time it reboots, it reboots into Recovery. I have to either hold the Vol- button, or from TWRP choose Reboot > Bootloader, in order to get to the bootloader, and then from there choose Start to get to the system.

By the way, so I show my work:

C:\Users\Me>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.004s

I did it twice in a row just to be sure.
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
Have you tried to reflash twrp, boot back into twrp and after that into system?
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
I mean, I've tried reflashing stock from scratch, flashing TWRP, etc. I'll flash it again right now and see if that changes anything.

C:\Users\Me>fastboot flash recovery C:\Users\Me\Downloads\twrp-3.6.0_9-0-potter.img
target reported max download size of 534773760 bytes
sending 'recovery' (17544 KB)...
OKAY [ 0.386s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.593s

Power off. Power on. Boots into TWRP instead of system. Reboot > System. Boots into TWRP again. So nothing improved.
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
Maybe try to:

- Flash Twrp

- Don't power off or boot to system.

- Instead boot into Twrp again.

Quote:

- Now flash into system

You said you've tried Disable_Dm-Verity_ForceEncrypt.zip in several versions, that would be my next guess otherwise.
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
Flash. Check. Boot into Recovery. Check. Now trying to reboot directly into system. TWRP loads again.

DM Verity. Man, I've got these things coming out of my ears. no-verity-opt-encrypt-5.1.zip. no-verity-opt-encrypt-6.1.zip. lazyflasher-no-verity-opt-encrypt.zip. Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip. I've tried them all. Haven't tried them during this past reflash and reroot, but I'll try one now. I'll try that last one, since it's closest to what you named. There, flashed that last one via TWRP. Said it flashed it. But I rebooted, and it's back in Recovery again. Heck, I'll try the others again. 5.1, lazyflasher, 6.1, in that order, rapid succession. All flashed. Reboot. Now I'm back in Recovery again.

Would it help if I sent a backup of any partitions to you, and how would I best do that? Furthermore, I tried installing Arrow v9.0. It installs fine and runs, but it boots automatically into Recovery. Why should that be? It has its own boot.img. I mean, if I flash a custom rom with its own boot image, and it still has the exact same problem, doesn't that mean that boot.img isn't the problem? I don't get it at all. I'm doing exactly what the guides tell me to do, and it isn't solving the problem. What could I possibly be doing wrong?
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
Don't forget that the boot.img is not the same as the bootloader. The boot img is the place where Magisk is flashed to. Is this whole process happening on an unrooted device too?

I remember some users having this problem some time ago but can't remember if there was a solution for it, sorry.

@sd_shadow , you owned a potter too, any idea? Booting into recovery instead of system?
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
Well, the bootloader is unlocked, and once I install Magisk that should take care of all the rooting, shouldn't it? That's how I'm rooting. Specifically, I'm flashing Magisk through TWRP.

I mean is there a cracked bootloader.img that anyone can send me to flash? I'll try it, if you've got it.

What I'm doing again:

1. Flash everything stock with stock rom and flashallO.bat, via bootloader with fastboot.

2. Flash TWRP via bootloader with fastboot.

3. Flash Magisk with TWRP.

4. Limited profit.

As for all those special thingamabobs, I think they're targeting boot.img rather than bootloader.img. Is something not right? How do I make it right? Again, can I just have a cracked version of bootloader.img to flash directly?

Further question: Is there any way I might have flashed the wrong region? Is that even possible?
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
You can create your own Magisk patched boot.img.

Download the Magisk apk from here:

Release Magisk v24.2 · topjohnwu/Magisk

Maintenance release fixing various issues. [MagiskSU] Fix buffer overflow [MagiskSU] Fix owner managed multiuser superuser settings [MagiskSU] Fix command logging when using su -c <cmd> [MagiskSU]...

github.com

(Btw, which version are you using right now?)

The unpatched boot.img can be found in the firmware you are going to flash (unzip it and paste the boot.img on your device).

Install the above Magisk apk and instead of direct install choose patch boot.img in the Magisk app. Keep an unpatched boot.img on your device too, you can flash it if something goes wrong.

Everything about Magisk install and more can be found in this great guide by @Didgeridoohan .

Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

Flashing Magisk by Twrp should always be the last ressort.

Before doing all that I would try to install the firmware without rooting it.

After that it's up to you to install Magisk the way it's explained above in the mentioned guide.

If you don't need Twrp for other stuff you can just boot into it. If you want it flashed on your device do it now.

Maybe try different (older) builds of Twrp if you haven't.
[Moto G5 Plus Guides, News, & Discussion] Didgeridoohan:
Thank you... With the slight caveat that it needs a serious update after the v24 release. I've just been too swamped IRL the past few months. Hopefully soon™.
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
Um, what if I did a bunch of stuff with flashing Magisk via TWRP, and THEN I modified a virgin boot image and flashed it directly? Because I tried that. It didn't solve the problem, but I tried it. Is there anything that would be different if I did it some other way?

And couldn't I just get modified images from someone who has everything working flawlessly? Couldn't that work?

I supposed I could install older versions of TWRP, if someone thinks that would make a difference. But why would a newer version of TWRP work worse than an older version?
[Moto G5 Plus Guides, News, & Discussion] Wolfcity:
What's your firmware version? I'm on 8.1.0_OPSS28.85-13-3 but I think you're on 8.1.0_OPS28.85-17-6-2, I have no patched boot.img for that build.

But as said above,and can be found here:

https://www.didgeridoohan.com/magisk/Magisk

You can patch your own boot.img unzipped from the firmware.

it's absolutely no problem patching your own one, just follow the instructions in the guide and Magisk app.

Again: Which version of Magisk are you using?

Why can older builds of Twrp be more functional?

Because your device is older too and may not work with newer versions (that weren't available when the MotoG5+ was released)

Twrp 3.3.0.0 is working well on my Potter:

twrp-3.3.0-0-potter.img

drive.google.com

So I recommend to install

- Your fitting Firmware, boot into system and make your settings.

- Install Magisk 23 (it's also working well on my device): https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apkinstead

Try the "patch boot.img" method instead of direct install or Twrp flashing.

If everything is fine you can try to install Twrp 3.3.0.0 if you really need it!

If you don't flash it, your device can't boot into it and your problem would be solved...

You can always temporary boot into Twrp instead of flashing it.

Instead of

fastboot flash recovery [filename].img

in this case

fastboot flash recovery twrp-3.3.0-0-potter.img

give the command

fastboot boot twrp-3.3.0-0-potter.img

.

Do one thing after the other.

- Flash firmware unrooted, check system.

- If everything works well patch original boot.img with Magisk and flash it to your device.

- If necessary flash (or boot) TWRP 3.3.0.0.
[Moto G5 Plus Guides, News, & Discussion] FailSafeNow:
Edit: I didn't mean that to be a blank reply. Let me fix it:

I did the patch thing. That's what I said. I did some other things first, but afterword, just like I said, I took the raw boot.img from the unzipped firmware, ran Magisk to patch it, and then flashed it via TWRP.

Now hold on for something. You said that if I didn't flash TWRP at all, my device would not boot into it and my problem would be solved. Unfortunately, that's not true. Because without TWRP, I boot into the stock recovery, with the useless message of "No command". As far as I have seen, the only way to get out of it when it's like that is to hold down the power button until all the bones in your thumb snap in half. With TWRP, at least I have the option to reboot.

But ok, let me flash stock again — 28.85-17-6-2 — and see what happens before I install anything. Let's see if it boots normally.

NO COMMAND!!!

I installed the stock rom, did nothing to it, and it booted automatically into Recovery with the useless "No command" message. This is the stock rom doing this! And now it's in a bootloop. It will keep rebooting into Recovery until I intevene.

And yes, absolutely, I flashed it using the bat file. (In the bat cave. With the assistance of Batman.)

Well, we've eliminated a lot of possibilities, haven't we? BUT:

If the stock rom does this, and another common rom (Arrow v9.0) also does it, then does that mean it will do this no matter what rom I install? And if those roms do this, then what the heck do I have to modify to get it to behave?

You say you're running 85-13-3. You trust it. It works for you. So maybe that should be the very next thing I try. But man, if that doesn't do it, then what am I supposed to do?

Edit: Didn't see your version. So screw it, I'll just try the last version of Nougat and see what happens.
[Nexus 6 Android Development] larrywilson:
load TWRP 1 it will ask you for the key 2 enter your language 3 delete 4 4 in the menu look for wipe 5 slide the option Swipe to factory reset 6 after this adwanced wipe load again and it will not ask for the key this took days and hours find out I like it and recommend my lucky solution