yashsingh1/xdaforums huggingface dataset:
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Dahenjo:
Here are mine but I had a different authentication problem after restoring backups which had fingerprint/pattern security, not what [MENTION=4562745]zeft64[/MENTION] had but I think the same as [MENTION=1686918]Gronkdalonka[/MENTION], and was last using twrp-3.1.1-0-GtrCraft-potter.img that these logs are from, but it happened on earlier TWRP versions too. I have two logs because there was a checkbox to "Include Kernel log" so I also got that one.

I found that if you installed a different type of ROM than the backup it will fail to recognize the correct pattern/PIN/etc, but if you backup then restore the same ROM without another type in between, then it is recognized. The very same backup both succeeded and failed depending on what it replaced. Backups without lock screen security all restore properly with no other issues.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Gronkdalonka:
Decrypting the backup again fails. But this was GtrCrafts version. The Version from this thread always got stuck during backup and i had to reset the phone.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Santhosh M:
The error is qseecomd process fails to start (exits) and i couldn't get enough time to debug.

Note that qseecomd needs to be hex edited to use /sbin/linker instead of /system/bin/linker
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] vache:
It's already hex edited ;)
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Santhosh M:
Knew yours would already have ( as does my initial release), but that's where there issue is and that's why let you know. Even a proper qseecomd binary doesn't start the service properly.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] sandy108:
Why isn't this moved to official status yet..? Any bugs I should know about?
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Jrhotrod:
One that has been especially impactful to me is the failure to read the external SD card. This means that you can't backup, move files, or associate at all with the external SD until the bug is fixed. This phone (at least the 64gb version I own) doesn't really need an SD card anyway, but is useful for backups and whatnot.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Karlinski:
There is a 3.1.1 build in here somewhere that works fine with the SD Card
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] twcobra:
Interesting. I just got the same phone and the external sd works fine. I have a high speed sammy 64g card. Its the evo select sdxc
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Jrhotrod:
Hmm... Interesting. I've used the root method posted by Johnny Cipeli, and it can't read my external SD. I'm using a SanDisk. Maybe the manufacturer matters.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] zeft64:
There's a build with this fixed already. The biggest issue is with all forms of encryption
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] twcobra:
I used drtechied tool.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Dahenjo:
Post #158 in this thread. There have been four unofficial TWRP versions so far - first two couldn't see SD (both named 'twrp-3.1.0-0-potter.img', one at 13,656 KB, other at 14,460 KB), third (twrp-3.1.0-0-n3-potter.img) can see SD but is v3.1.0-0, fourth (twrp-3.1.1-0-GtrCraft-potter.img) can see SD and is latest v3.1.1-0. Hopefully soon there will be one official version listed in OP to avoid confusion.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Karlinski:
Agree 100%

Thanks for digging through the thread to find that!
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] bornlivedie:
Use GtrCraft's build. It has fixed ext card.

My sdcard is also SanDisk.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Jrhotrod:
Link?
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Paulo Narley:
twrp-3.1.1-0-GtrCraft-potter

https://drive.google.com/file/d/0B7X6bQHmiX_BNHRGTzdaZGlid1U/view?usp=sharing
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Jrhotrod:
Nice, thanks. I will try it out later today
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] edward.masih:
My internal storage is not mounted in twrp...and i dont know how to mount. And i cant flash any recovery img via fastboot now. I'm on build 33. I dont know what to do.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] bornlivedie:
One post above my answer lol.

Lazy as f*ck.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Jrhotrod:
Lol. Although your emotionally tinged addendum was not necessary.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] rayzen6:
The one which is linked on op also has extsd supported FYI.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Vishweshwaraiah Kj:
my bootloader is showing Flashing_locked, unable flash any img files. Please help, i'm even unable to open recovery, it is giving Invalid boot image header, failed to load kernel.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] zeft64:
So try to unlock your bootloader
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] SoujiTouban:
Hello. I seem to have found myself into an unusual situation (still reading over this thread to see if anyone else has had the same problem.)

I purchased a new Moto G5 Plus from a brick-and-mortar store today, unlocked. It has no sim card in it. While trying to install LineageOS onto it, I found myself stuck in a TWRP boot loop. Every boot displays the "Your device has been unlocked and cannot be trusted." prompt, then boots into TWRP, even if i attempt to reboot into system or recovery. I can boot into bootloader(fastboot) and if i select Factory Mode here, it boots once into the custom firmware i flashed. the firmware seems to work normally until I reboot, when I have to go into fastboot and 'factory mode' again.

Notes:

When I am in fastboot, the bottom display still states Software status: Official.

When I first tried to $ fastboot flash recovery twrp~.zip it gave an "Image Corrupt or not signed" error. fastboot boot booted twrp and it has been working? since, but further attempts to flash recovery gives the corrupt image error.

Initially, I was getting an 'unable to mount /data" error, but that seems to have fixed itself somewhere in the process. I can now see the contents of internal and external storage within TWRP's file manager.

ADB sideloading seems to work. I'm still stuck in this loop so i'm not even sure what is "working" anymore.

As of posting this, I am attempting to adb sideload an aokp image.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] N0tSoFast:
I've just made an account here to say I ran into the very same issue. Purchased a brand new moto, flashed TWRP + Lineage ROM and now I'm getting constant bootloops to recovery mode. Loading into factory mode from bootloader seems to do the trick but this workaround is a little inconvenient to say the least lol. Also, I cant get any sim card to work with this phone, it says "No service" no matter which one I try. The sim cards I'm using work perfectly with my old phone.

SoujiTouban, if you find a solution please don't forget to post here, I will do the same, thanks!

---------- Post added 10th June 2017 at 12:22 AM ---------- Previous post was 9th June 2017 at 11:29 PM ----------

Alright so just when I was about to get really desperate, I finally found a solution that worked for me. What I did was download the stock firmware image (POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), extract bootloader.img, flash it with fastboot, then flash TWRP again. I no longer get bootloops and my sim card is finally working now!

To hide the ugly "Your device is unlocked" warning I downloaded and flashed Moto logo.zip from here.

Let me know if that helped.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Dahenjo:
The "Image Corrupt or not signed" is normal, it's not corrupt but not being stock it isn't signed. No problem, it flashed correctly.

After flashing and then first entering TWRP and before doing anything else, you need to do a Wipe/Format Data (not factory reset or wipe data; it makes you type 'yes' to proceed) then reboot right away into TWRP. That decrypts /data and fixes the mounting problem. I don't know if not doing that and installing/sideloading custom ROMs/etc would cause the OS booting issues, but imagine that it could. If reinstalling TWRP properly (w/formatting data) then a custom ROM again doesn't fix it, you might have to revert to full stock (ie, fastboot flash the official firmware) and start over.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] SoujiTouban:
First, the ADP sideload of a different rom didn't work. Or, it maybe did, but after waiting for about 30 minutes with the pink aokp unicorn and gear animation looping on the screen endlessly, I figured it probably didn't work.

Second, I had tried wipes and formats at different stages of the process, all to no avail. It still would only boot into the OS through the "factory mode" setting of fastboot.

So, I finally did something similar to N0tSoFast. I retrieved this toolkit. I flashed the stock rom (following directions within the program only, it had a link to stock roms.) and ensured it worked as it did originally. Then I used this program to flash TWRP, super SU, etc.(the included options in the program,) then within TWRP I installed a LineageOS rom successfully. However, within an hour or so of using it, I encountered the screen color fry-up others on lineageOS and potter seemed to be encountering, so I installed AOKP. Upon realizing the rom did not include GApps, I flashed GApps mini from here. Misc. authentication problems continued, so I retrieved the GApps full pack from there, wiped and formatted, re-flashed AOKP and gapps, finally resulting in a working phone.

Anyway, one important note I want to leave is I did not get the copy of TWRP on this thread working. Best of luck to everyone and thank you for your responses.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] arhncmh:
Any idea when TWRP will achieve official status for this device?
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] GtrCraft:
Is it important? Nothing changes apart from the name
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] arhncmh:
I thought my question was reasonable, now I'm being challenged? Maybe I didn't realize what I was getting myself into.

Maybe because then it would be listed under devices on the developer's website?

I didn't try, but how about also being acknowledged by the TWRP App?

I did some limited research and couldn't find anything conclusive regarding official vs. unofficial. Is there an actual answer/reason?
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Jrhotrod:
Not sure, but chances are that the TWRP devs review recovery submissions and evaluate if they are worthy of official status.

And I agree, your question was reasonable. No difference besides official support, but still nice to know that the devs consider the build to be stable enough as to make it official. But no need to fight over it. I just answer questions no matter how stupid/irrelevant they are (oftentimes redirecting the person to a different form :silly: )
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] arhncmh:
I totally agree and understand. I wasn't looking for anything other than some clearer feedback, which is greatly appreciated coming from you.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] djroese33:
Well, I think for us non-Dev-level members, it helps us feel things are stable and it's now worth rooting. Certainly awesome the work people on this thread have contributed, but some of us may be a bit cautious about when to commit to rooting (I'd be less so if Motorola wasn't so verbose about the death of warranty upon merely Requesting unlock code!):)
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] GtrCraft:
Official makes it more stable and worth rooting...

Biggest bull**** I ever heard
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Santhosh M:
I understand your thought :p . For a completely new user official gives a trust and you can't really blame it. Let's not spoil the thread continuing this :) Just turn a blind eye :)
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] donjuro:
True, and I don't think there's any firmware or recovery that is 100% stable yet anyways, sooo...
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] smitharro:
Why should making it official make it more stable?? I don't see that!

Send from my Motorola Moto G5 Plus (XT1685) using Tapatalk
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] djroese33:
WOW dude, got enough attitude??

I said "Well, I think for us non-Dev-level members, it

helps us feel

things are stable and it's now worth rooting" Want to slam someone, at least have the honesty to quote them accurately. And really, "Biggest bull**** I ever heard"?? You should get out more.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] abeloman:
You want the official tag for start the complaints about it isn't stable at all? Then I'd prefer keep it unofficial forever

Enviado desde mi XT1681 mediante Tapatalk
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] smitharro:
Chill... He's right! Mind your own attitude towards our developers!
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] djroese33:
Are you talking to me? I never said a single bad thing about any developers.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] sinchan_nohara:
Well said man i just wanted to say the same thing you did not disrespect anyone and he slammed you for no good reason
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] djroese33:
Well, thanks. I was just taken aback.. I wasn't trying to start anything, I was just explaining why someone like me might wait for an 'official' TWRP. I thought it was a pretty benign post!

Well, I think for us non-Dev-level members, it helps us feel things are stable and it's now worth rooting. Certainly awesome the work people on this thread have contributed, but some of us may be a bit cautious about when to commit to rooting (I'd be less so if Motorola wasn't so verbose about the death of warranty upon merely Requesting unlock code!)​

And this seemed completely dishonest reading of my post:

Official makes it more stable and worth rooting...

Biggest bull**** I ever heard​

So seemed pretty harsh. I'm not a newbie (jailbroke my 3 iphones, and rooted my last 5 Androids), but I do it when I feel I have concise directions and there's a history of success in the forum. So, don't pretend to be a dev-level dude. I'd like to think non-developers (and their amateur opinions) are welcome here.. otherwise, who are people developing for? Other brainiacs?:o
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] GtrCraft:
Wow 5 rooted android phones, good job of you. Oh and btw, I made the most recent twrp image here, maintain multiple roms, contribute with all the issues that come and go on this device. And here you are saying we need official because its better...
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] djroese33:
Jeez, you're an oversensitive nutjob. I never said anyone "needed," I was just expressing why someone FAR LESS SKILLED AND INTELLIGENT than your almighty self might feel more comfortable when TWRP was 'official'. You're a bit dense dude.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] servalg:
Impossible backup twrp-3.1.0-0-n3-potter

First of all sorry for my bad english.:)

I just bought my Motorola G5+ and I try to make my first root. it is not easy! But luckily you are there to help me.

Here is my problem: I installed twrp-3.1.0-0-n3-potter and I want to make a backup before continuing. The backup begins well but stops at 98%.

Here is what is written when the backup stops:

Failed to mount '/data' (Invalid argument)

Backup Failed. Cleaning Backup Folder.

What does it mean? :confused: Someone help me please?

Thank
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] zeft64:
Well from what I gather it seems like when things are officially not only do you get support from the maintainers but you get support from the team the software originated from. Would be nice to have support from the twrp team
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] rayzen6:
I would love to see this "official" "unofficial" useless discussion to be end. There's nothing like the main dev of twrp himself will support if we have official. It'll just results in change of download location. Nothing more or less will be there even if we'll go official. So I think this useless discussion spamming the usefulness of this thread. :) would like to see thread on topic now. I don't think you guys want this thread to close again. :)
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Dahenjo:
Was the thread closed recently, if so why? Also, why isn't the latest TWRP 3.1.1-0 linked in the OP? It's been a few weeks and it seems to be working well.

"Can't we all just get along?" - Rodney King, RIP

With all due respect to our developers & maintainers, I've not seen this level of resistance to getting TWRP to official status in other forums here at XDA. My previous phone (still have) is a Moto X Pure and just checked it's TWRP thread - it took

3 days

from initial release for it to go official. Maybe in these two years since it's become more complex with systemless root, encryption, and such. So is something like that the reason why? I'm calmly asking what to me is a relevant technical question pertaining to one of our main XDA tools, and expect answers to please adhere to the same tone.

That said, I'm going to contact some other folks involved with TWRP and present our situation here for their opinions as to what our best approach should be. Does official status matter, if so why or why not, and are there reasons why it's harder to do than in the past, etc? Personally I'd like to see it go official if there's no major reason for it not to be, as well as having the latest version listed.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] vettejock99:
Can someone maybe help me with this? I posted in Q&A that I did an unlock, rebooted the system, then went back into bootloader and did a "mfastboot boot" of TWRP 3.1.1 to backup my stock system, boot, data, etc. like I always do with my Motos when I get them. I noticed the time was way off and I wanted to check the phone once more because I'd expected the time to be set when I booted to system. Anyway, instead of rebooting properly again it hung on the device unlocked trust warning screen. I noticed that I have the ID: "bad key" message (instead of ID: N/A) some have reported. So I wanted to start fully over. I actually relocked the bootloader, reflashed stock -35, unlocked the bootloader again (and I still have the bad key message), and booted to TWRP to try again.

Anyway, whenever I boot into TWRP it doesn't seem to want to mount internal OR external storage so I can do a backup. I've tried formatting data and wiping caches and rebooting into TWRP, I've tried clicking Mount for SD card, but every time I get 0 space showing available. I'm afraid it's associated with this "bad key" think as I see others saying they can't flash TWRP or another recovery and other issues. I haven't tried to actually FLASH TWRP because I wanted to take a stock backup like I always do, but I expect it would fail regardless as this should work as is. Can anyone help? I'm stuck.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Dahenjo:
Everyone has the "bad key" designation after unlocking, meaning it's 'normal' on the G5+ and nothing to worry about, and also that it's not behind your other problems. You can get rid of it at boot-time by fastboot flashing another logo, see this thread.

Something is messed up there, though. I 'd try re-flashing TWRP with again formatting (not wiping) data as soon as you get in, then immediately reboot right into TWRP and see if your partitions are recognized. Sounds like you're using the 3.1.1-0 version posted in this thread which works fine for me so it also should for you.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] vettejock99:
Thanks a ton for your response. I've got to admit I'm not convinced the "bad key" thing is normal. Common, maybe, but not normal. In fact while awaiting responses I did experiment and some through flashing stock and booting different versions of TWRP and wiping partitions I remain bootloader unlocked but I get ID: N/A again. I was also able to get it to recognize internal and external storage, so I was able to backup (with an old version of TWRP) and then flash the version you linked. I was able to boot, too, which was great.

Unfortunately, I've gotten to where it's booting to recovery only again, and I've gotten messages about /cache not existing. Next step is to try to flash a ROM to get /cache, and the ability to boot, back.

UPDATE: Flashed the lazy-flasher-no-verity file, boot test 7 boot.img, and wlan custom files and I am now able to boot. I can reboot to recovery, and so I flashed the latest magisk 13 and elemental x 1.01 (since I'm on -33) and I boot and have root. When the new TWRP drops I think I'll try restore stock to go to -67 and then try some of the stock-based roms.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Santhosh M:
Note :

There should be no spam about official thing anymore. I will clean them up as it comes by.

I will release a new version of TWRP that should have encryption working fine most likely
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] alevity:
Let me know when it's safe and clear bro. Still sounds like allot of noise considering I'm pretty happy with this phone and don't want to brick it so soon
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Karlinski:
I've never had a root issue outside of very early builds....

There's nothing that this BL can do to brick your phone....

If you can get it to turn on, it's never broken, and this can't change that. It's perfectly safe to install
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Dahenjo:
That post of mine you quoted was from three months ago (March 30th) at the very beginning of rooting efforts for G5+ and at that time the situation was as described. By now there's been a lot more development with many rooting successfully with both SuperSU and Magisk, so I'd say it's "safe and clear" now and to go ahead and try it if you haven't already.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] servalg:
Can anyone help please? I'm stuck.:confused:
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] washoq:
Did you wipe data after flashing TWRP?
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] servalg:
Thank you for taking time to answer me.

For the moment, i only activate via the bootloader and the recovery mode TWRP. I wanted to make a backup first of all.

I haven't wipe data (Not voluntarily) and flashed TWRP. I do the backup on a micro sd.

The backup runs well but at 98% the backup stops!!:confused:

And here is what is written :

Failed to mount '/data' (Invalid argument)

Backup Failed. Cleaning Backup Folder.

What does it mean?
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] washoq:
It is required to wipe data. It is marked as important note in the OP.

Probably this is cause of your issue. You need to wipe data after flashing TWRP to get it to work.
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] servalg:
If I understand correctly you advise to erase the data (all the data of the cell phone!! ??) and to flash before making a backup !?

I don't see the interest to make a backup if there is nothing to save !!

Is that what you advise? Erase data and flash before backup?:eek:
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] Santhosh M:
3.1.1-0 release (22/06/2017)

Hi all,

Have released new updated version of TWRP

Changelog :

Updated to latest twrp code (3.1.1-0)

Fixed encrypt/decrypt issue (Now you don't have to wipe /data at the first boot of twrp). TWRP will successfully decrypt your /data the first time you boot into twrp.

Download link is available in the OP.

Regards

Santhosh
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] GtrCraft:
I cannot download, getting network error
[Moto G5 Plus ROMs, Kernels, Recoveries, & Other De] vache:
How did you fix decryption issue ?