yashsingh1/xdaforums huggingface dataset:
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] always6s:
Same thing happened to me. First 4g went followed next flash by my 3g. I tried everything I knew. I ended up unzipping my nps file into the adb folder again. Replaced everything with the new stuff. Fastboot flash everything and that worked. V
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] ANDROID O:
Because ,Ur micro SD card is fat32 ,it has some file system limitations, it can't copy an file more then 3gb ,Ur stock is 4gb of system.img ,try to format Ur micro SD card to f2fs or NTFS ,then backup Ur entire and check it'll work .I did same thing it worked for me
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
Fyi - fat32 is a 2 gig limit
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Adi5:
Not 4gb limit?

I copied to my sd card 4gb video and works(fat 32)
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
It's been 2 forever
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] m.mishka:
F2FS loopback

Hi. Firstly, thanks for your work. I have this recovery, Pixel Experience rom, and Alize kernel installed to Moto G5S Plus, Sanders. The problem that I have is that Magisk modules don't flash, as if the F2FS Loopback Bug has not been resolved. Apart from that, everything is working wonderfully: battery life, responsiveness, no charge issues. I saw that the F2FS bug was resolved in v.9 here. Is there anything I did wrong? Saying that, my cache partition is ext4. Is it worth reformatting it to something different? Thanks for any help.

EDIT: I just checked which kernel I installed exactly, and the name of the zip file is AlizeEAS-8.x_vSeven-64bit-Sanders.zip. From looking at the sourceforge page, it seems that's not the latest version and one before the loopback bug was fixed.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
Not really worth it. Gains are little, you wouldn't notice any difference.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] internetpilot:
Backup stalls at 20% on stock data partition...

Alright, I've always rooted/ROM'd my Android phones since the days of Froyo, but this phone has been really weird for me, even though my prior phone was a Motorola Nexus 6. Here's what I'm trying to do and what's not working:

I unlocked the bootloader (which wiped the phone), I flashed the r15 version of this TWRP, and successfully backed up all partitions of the stock ROM. So I have really TWRP backup of everything stock (which is good because I've had to rely on that when messing around with the phone).

I then flashed several different Oreo 8.1 ROMs, which didn't work out entirely well for me because none of them seem to work well on my carrier, Sprint. The ROMs boot fine and I get on Sprint, but if I edit ANY of the Cellular Networks settings, I lose connection with Sprint and cannot get it back unless I reset the Network Settings. Anyway, that has nothing to do with TWRP, other than being the reason why I had to revert back to the stock ROM, which I successfully did using my TWRP backup. I then setup the phone (remember, unlocking the bootloader wiped it), flashed TWRP again, and flashed Magisk. I have root and everything runs fine.

Here's my problem: When I try to backup the stock ROM again (now that it's setup like I want it), it stalls at about 20% through the data partition. I'm backing up to my external micro SD, which is definitely formatted in exFat. The system image partition backs up fine, so I'm not thinking it's a file size limit. Is it an encryption issue? I'm not receiving any error messages. It seems weird that it would be an encryption issue when it makes it 20% through the backup of data partition, but again, this phone is really making this rather experienced Android user feel like a noob. Please don't tell me to wipe or format the data partition, as that defeats the purpose of what I'm trying to do here. I want to get a full, snapshot backup of everything as it's setup on this phone now, so I can then start messing around with the Oreo 8.1 ROMs again to try to them working, but have full, working restore to stock available if that doesn't work out again. If I wipe or format data, I'm going to have to reconfigure everything all over again and then I might was well use my original restore that I got immediately after unlocking the bootloader.

I don't think I'm trying to do anything weird here, and I've done this (taken a stock backup) on every phone I've ever owned. Why would it not work on this phone?

Thanks for any insight/help anyone can provide.

SOLVED: Upgraded to r16 and backups work fine now.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
Send me the recovery log via pm - advanced in twrp/copy log. I'm curious. Can't say I ever backed up stock (never wanted to go back to stock), but I am curious.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] internetpilot:
Trust me, I didn't unlock the bootloader only to go back to stock, but these Oreo 8.1 ROMs currently turn my phone into a wifi-only mini tablet. Haha.

It would appear that the solution to my problem was r16. I was running r15. I just flashed r16 and ran a backup and it worked without a hitch. Of course, that means the r15 log is no longer there to satisfy my (yours and anyone else's) curiosity, but at least r16 seems to have solved the issue.

Now I'm going to try the Oreo 8.1 ROMs again with different Gapps to see if that helps my situation on Sprint.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
It's working - fork the logs!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] internetpilot:
I'm now having this same issue after restoring my backed up stock ROM via TWRP r16, but the above commands did not work. It says no such directory.

Is there any other way to get out of this bootloop to Recovery hell?

Nevermind. I restored the stock recovery. Unfortunately, the phone then booted to it and promptly erased the entire data partition, so it apparently had a problem with the encryption from me restoring the data partition. So I flashed TWRP r16 again, restored the data partition, and it booted up fine, but it claimed my PIN was invalid. So I used the TWRP file manager to delete /data/system/locksettings.db, which defaults the lockscreen back to just a swipe. All seems to be okay now. It boots back to the stock ROM instead of TWRP.

...sigh...

I'm beginning to REALLY hate this phone. It might time to chuck it and move on to a Pixel 2. The headaches of this phone (just the time spent rooting/ROMing it) just aren't worth the $ savings.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
Oh well - give it to the looks top play with (they won't need anything more). Wish I knew what the issues are and could keep ya out more. For me, this was like any other device except for going through the unlock bs with moto.

If ya do go for pixel, and looking for custom os, check the forums. Last I knew folks were having trouble with the new partitioning scheme in that device (something about dual partitions I think it was).

Good luck man - all the best!!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
Not doubting you or anything but I have had the easiest transition with this device than any other device I have owned. Less than 5 minutes out of the box, I had this unlocked, rooted, twrp, and a custom rom on it. Never looked back... Never get a Samsung with it's ODIN and Knox crap, or an HTC with it's annoying S-Off. I thought about the Pixel 2, but the extra 700$ wasn't worth it. I have just about everything and more a Pixel 2 comes with for a 1/4 of the price. Best thing I ever did was jump off vzw, that company just blows...
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] internetpilot:
I've been rooting/ROMing phones since Froyo, and did deal with HTC, Samsung (multiple phones), and my phone before this one was a Nexus 6, which was also made by Motorola. This G5S Plus just keeps kicking me in the arse every which way I turn! The Nexus 6 was so easy to work with that I thought for sure I'd have an easy time with this phone, but I just feel like I'm constantly having to pull work-arounds out of my posterior. Still, despite my annoyance and rage posts (haha) about getting a Pixel 2, no matter how bad this phone is, there's just no way I'm going to pay US $1,000 phone. Any phone that costs $1,000 better root and ROM itself...and massage my feet...and mow the lawn.

I'll keep working at it and try to keep the rage posts down to a minimum. Your experiences with this phone gives me hope that there's a light at the end of this tunnel.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
I have an idea, but what worries me is Sprint. Some carriers have absolutely no sense of humor when it comes to byods.

You said you have a stock bu that works without issue - what's one more try. Pm me with current state of the device - recovery, root, encryption, os etc.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Helltech:
Any reason my SD card isn't showing up in this version of TWRP?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
Too much porn?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
Hahahahahhaha!!! This is great!xxx
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] s.k.rajput:
Format data u will be good to go then
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] sharique88:
After updating Cosmic os to 26th Feb build, I am unable to boot into device. At first boot, it restarts and reboots automatically to TWRP. I am using TWRP R16. Any solution?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
Sounds like a question for Cosmic thread not TWRP. Did you do a clean install? Dirty flash? Did you make a backup? Does that install? Usually when roms don't boot up, it is because of conflicting files or bad data. I suggest wiping and reflashing rom and gapps.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Adi5:
Cosmic is bad.Don't flash newest one
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] siheyo:
I do have same issue with pixel experience rom. Using r16 version.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
Wtf are you reserving?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Phazmos:
A brain - might get 1 someday, ya never know
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] revengineer:
I have trouble with permissions on my SD card; I cannot write to it. There is supposed to be an option to "Fix Permissions" in TWRP, but I cannot find it. I see Fix Contexts but this does not help. Advice appreciated. Thank you.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
Internal sdcard? Is your data encrypted? Is it formatted correctly?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] revengineer:
I use a 64 GB SD card and it's treated as internal memory. I do not know if the issue is with the SD card memory or the internal phone memory or both. On previous phones, I have used the "fix permissions" function in the recovery to resolve such issues, but I cannot find it in this version of TWRP. I have inserted the memory card into a PC and used diskpart to check if the read-only flag was set on the card - it was not.

Advice appreciated, but I am sensitive to not hijacking this thread. If suggestions are not TWRP related, I suggest using a PM. Thank you.

EDIT: Problem solved, the memory card went bad. Surprising because it was only 4 months old. FYI, it was a SanDisk microSDXC card. Still wondering though where the fix permission function went in TWRP.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] yohannos:
i'm stuck here with the same bootloop to twrp. i tried different roms (aex, pixelexperience, rr), but it all ends in twrp. i can manually boot to fastboot mode an select 'start' - then the rom boot without issues... any suggestions?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] internetpilot:
I encountered this numerous times myself when trying different ROMs, but especially when I just loaded (rather than flashed) TWRP the first time so I could get a full TWRP backup of all the stock partitions (including the stock Recovery). Then I re-read the OP and finally noticed this:
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] marcdw:
The above is where I messed up, too. Finally got it squared away but it took all night. :)

Moto G5s Plus XT1806, PixelExperience Oreo, MultiROM, Tapatalk 4.9.5
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] pranavpmanoj:
TWRP says my password is incorrect even after entering the right one. I'm unable to flash or browse files on TWRP. I'm running the latest Pixel Experience (Encrypted). Anybody else have this issue?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Adi5:
Format data
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] pranavpmanoj:
I'm unable to use the recovery whenever I encrypt my phone running Pixel Experience. I don't feel it's safe leaving it decrypted. All files can be accessed by just booting into TWRP. When I'm encrypted, TWRP keeps saying that the entered password is incorrect. Is there something I can do about this?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] reyasat:
after installing custom rom asking for password in twrp
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
Read install instructions in OP

Sent from my Moto G5S Plus using Thebear Blue XDA Labs
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] fuuuu.ind:
[ask] currently on 3.1.1

[1] if I install this version, will my data get wiped?

[2] will it take out my roof access?

[3] can't I use twrp 3.1.1 to flash pixel experience rom? I've heard that it's 64 bit thus it needs proper TWRP version.

Current status:

- g5s plus

- nougat 7.1.1 stock

- unlocked BL

- rooted with magisk
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Thebear j koss:
No. No. And no. Twrp only flashes to your recovery partition. Data will not be touched. It also doesn't affect root. If you need a 64 bit recovery for a 64 bit rom, then you will need to flash a 64 bit version of TWRP. If you are going to flash a new rom from what you are on now, you will need to do a full wipe, erasing all data, system, and caches. You will need to reflash Magisk after flashing rom if root is not included in the rom. Read and follow directions carefully in the OP of this thread and the thread of the rom you are flashing. You may also need to flash a gapps package after flashing rom.

Sent from my Moto G5S Plus using Thebear Blue XDA Labs
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] namehidden:
I am on stock rom XT1804 (android 7.1.1) with 01 June 2017 security patch, build no. NPS26.116-26. I have unlocked bootloader with twrp installed version 3.1.1-0. Can I upgrade to TWRP-3.2.1-r16 (64bit Supported!) by following instructions in the OP? Does this twrp support my phone?

I believe steps should be like:

Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot

Is above correct or did I miss something?

whether these "cancel the password prompt" and "Format Data/Userdata (on f2fs)" options available on new twrp?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Raje dhakal:
Just flash the recovery and reboot , no need of formatting user data.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] tith968:
Hello,

can somebody help me?

I flashed the r16 via fastboot. But when i try to install Magisk i get the message "Updater process ended with ERROR : 1"

Same when i try to install a Rom, i get ERROR Code 7.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] ANDROID O:
Probably ur zip might corrupted or something else ,

But not the problem of recovery
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] CheckYourScreen:
Updated!

Hi folks!

Updated twrp to r20 with following changelog:

You can now switch to custom roms without formatting userdata as encryption support is fixed now.

Quite alot of changes made up to this release so update to r20 ASAP!! Highly recommended update!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] pranavpmanoj:
Thank you!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] treyweez11:
Yay! Something new.....that works!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] fuuuu.ind:
[ask] recovery back to stock rom

hello. newbie here :)

what my system was:

stock 7.1.1

unlocked bootloader

rooted with magisk

i have backed this up

my current system:

pixel experience rom

rooted with magisk

what i intend to do:

get back to my previous stock rom android 7.1.1 without having IMEI problems as much people stated

will restoring from TWRP to my previously backed up system work? when i press restore, it says that i has these options to be restored:

- system

- boot

- oem

- efs

- logo
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Raje dhakal:
Yes these are enough
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] QkiZMR:
For work yes, but not for install OTA
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] pranavpmanoj:
Will I be able to encrypt my phone and still use TWRP with the new update?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] QkiZMR:
Yes

Sent from Moto G (5S) Plus via Tapatalk
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] omegaorgun:
It says it flashed but I still have no twrp, it is unlocked. All I have is an android icon, no twrp.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] chaostrodamis:
Boot into bootloader, fastboot/side load this recovery. Then inside TWRP reflash the recovery IMG again. Reboot into bootloader and select recovery from there. It should stick
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] JaggedPill:
Is it possible to completely lock the twrp so that it doesn't open without a password. In current version r20, recovery is still accessible if you press the cancel button. Only data is protected.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Raje dhakal:
No dude that's why we use twrp since it is used to rescue when something goes wrong or to install some zip file if u lock twrp then u r totally messed up if u forgot ur password.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] JaggedPill:
Totally agree with u but earlier we used to have locked down versions. There should be an option if we want to leave a loose end or not. Locking in my opinion is fully secure in case you lost your device.

---------- Post added at 09:17 AM ---------- Previous post was at 09:13 AM ----------

Unlocked bootloaders always give us an option to reflash recovery and ROMs so I would like to have my device fool proof to unauthorized access. More so when you have financial apps and password vaults installed on your device.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] anonyo:
Hello,

I just got this device today (Indian variant XT1804) and decided to do all system updates before proceeding to rooting. Updated to the latest system update NPSS26.116-61-8 with security patch level of 1 April 2018. Successfully unlocked the bootloader. Decided to first "boot" into twrp and backup all partitions to USB OTG device before "flashing" the twrp. But unfortunately, fastboot boot twrp-sanders-r20.img doesn't work, phone stuck on boot logo, I waited almost 5 mins. Since device is still stock untouched, it is encrypted.

I have to keep the power button pressed for a long time so that the phone then just boots back normally. Tried it multiple times with same results.

The fact that it is not "booting" into TWRP makes me doubt whether "flashing" TWRP will work, and I don't want to brick this device.

Can anyone help me and tell why I am unable to "boot" into TWRP.

Thanks
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] treyweez11:
Does fastboot give error when flashing recovery?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] anonyo:
No, fastboot doesn't give any error, it says, downloading boot and then Okay.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] treyweez11:
Try again. Use updated drivers. Use admin privileges. All I can think of. Re download twrps latest
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] anonyo:
Already tried multiple times, using command prompt as Admin. My adb and fastboot are latest ones downloaded from here https://developer.android.com/studio/releases/platform-tools. Moto drivers are latest too. My bootloader unlocking went without a hitch, so don't think it's a driver issue.

Just a month back I successfully unlocked, flashed TWRP and rooted my Moto X4. The Moto G5s Plus is my niece's device.

Thanks anyway.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] treyweez11:
Lol I've always backed away from messing with my girls ( wife, niece, sister, or mom's) phone for this exact reason. Sorry brotha. Hope someone chimes in.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] marcdw:
[MENTION=5717301]anonyo[/MENTION], I sort of remember having the same issue after fastboot installing that TWRP (older build though). I think using an older (official?) 3.1.x worked. Then updated TWRP from within TWRP.

Only been a few months and I'm forgetting already. Probably missing a step. LOL.

Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, Tapatalk 4.9.3
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] anonyo:
I have tried with r20, r16, r15, and with [MENTION=7792500]GeneticEnginer[/MENTION]'s TWRP as well. BTW, if any of you may have misread, I am not trying to "flash" TWRP, I want to "boot" into TWRP first without flashing.

My guess is it has something to do with my latest updated system version of NPSS26.116-61-8, and the updated kernel that comes with it. I haven't seen anyone mention this version here, all the different version numbers I have seen here are lower versions.

Thanks anyway.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] treyweez11:
[MENTION=5717301]anonyo[/MENTION]. You're worried about the message. That's nothing brotha. You can flash a new boot logo to cover that. When I find it. Ill add it to this thread.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] anonyo:
No, unlocked bootloader screen has nothing to do with it, I have already unlocked the bootloader and have that msg. Also, I have MotoBootLogoMaker and can make my own custom bootlogo whenever I need. I want to first backup my stock untouched boot, system, and other partitions that the TWRP offers to back up (data partition not needed). Once I flash TWRP, then I have to swipe to modify system (because I need root and TWRP to basically make changes to some system files) and then I have to flash Magisk or SuperSU, and they modify boot partition. That's why I want to boot into TWRP first, not flash.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] treyweez11:
Theres no option to boot direct into recovery on this phone like others. You have to go to bootloaded than select recovery. Confused me at first too. You can from rom but not from power off state.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] anonyo:
The OP says the following:

Other Methods(Fastboot) :

Make sure you have unlocked bootloader

Reboot to bootloader

Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)

I want temporary boot.
[Xiaomi Mi 5s Guides, News, & Discussion] patoberli:
Hi all

I just received a new OTA update on official Global ROM. New version is V8.5.4.0.MAGMIED.

Release notes only state one entry.

other

Fixed bugs

OTA is 128 MB.
[Xiaomi Mi 5s Guides, News, & Discussion] patoberli:
I've got the update now since around 1 hour and everthing is still working. I believe, but maybe that's because of the reboot, that the finger print sensor is a bit faster now. The update fixes various security issues, but based on the date in the About Phone, the WPA2 issue isn't yet fixed.