[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!)

Search This thread

pizzaboy192

Senior Member
Sep 15, 2010
387
124
Plymouth, MN, USA
That's good news! Thanks for clarifying. [emoji106]
Ugh. I guess when I decide to dump MultiROM and TWRP 3.1.1 and join the Pie party I'll have to reformat my card.
Strange how v3.2 backups to FAT32 don't work on the Moto or Axon 7 but do on the G3 (glad too since I run old ROMs that don't support exFAT).


Moto G5s Plus XT1806, MultiROM, XDA Legacy
Fat32 has a maximum file size of 4096MB. The system partition on the G5S+ is that exact same size, and with file identifier information and other filesystem necessities it ends up going over that 4096MB max limit. There may be a way to split the file into multiple parts, but that's not something easily done. Enabling compression does not fix the issue either, so that isn't a way to bypass it. I would assume the G3 had a system partition smaller than 4GB (4096MB) and that allowed a full contiguous backup image to be pulled onto a FAT32 SD card without it going past the size limitations.

A possible solution would be to order a large SD card (128GB are under $30 now) and do a split partition, with ~6-8GB available as ext4 or exFAT to backup your system image, and use the rest as FAT32 and traditional storage.
 

astroboye

Senior Member
Aug 1, 2011
77
6
@marcdw
yep make a backup before of you r sd card, that's what i've done et then you put it back every files from the phone link to the pc after resinstall and it works, caus if you do it directly from the pc to sdcard it won't be redable from the phone :(
 
  • Like
Reactions: marcdw

marcdw

Senior Member
Sep 24, 2014
5,750
2,894
58
Baldwin Park
@pizzaboy192, yes, I'm familiar with the filesystem limitations which is why I asked astroboye if he was using FAT32. Backing up system hasn't been a problem but data. Data backup could easily be 6 to 10GB or more on my main/primary ROM. TWRP 3.2.x on the G3 breaks everything up into smaller chunks as has/had been the norm. Backups are good whether to sdcard or flash drive, all FAT32.
The failures on the Axon 7 and Moto happen when backing up data, not system. TWRP 3.2 on those systems tries to create one huge file instead of breaking them up. When I first unlocked and rooted my Axon, running TWRP 3.2, I couldn't backup the stock ROM. Downgraded to 3.1.1, backed up the ROM, then went back to 3.2. I use Dual Boot Patcher on that device anyway so it handles the backups now. The Moto uses MultiROM-TWRP 3.1.1 where backing up is not an issue.
Just wondered why 3.2 changed things.


ZTE Axon 7 A2017U, Project New World, Multiboot, XDA Legacy
 
Last edited:

pizzaboy192

Senior Member
Sep 15, 2010
387
124
Plymouth, MN, USA
@pizzaboy192, yes, I'm familiar with the filesystem limitations which is why I asked astroboye if he was using FAT32. Backing up system hasn't been a problem but data. Data backup could easily be 6 to 10GB or more on my main/primary ROM. TWRP 3.2.x on the G3 breaks everything up into smaller chunks as has/had been the norm. Backups are good whether to sdcard or flash drive, all FAT32.
The failures on the Axon 7 and Moto happen when backing up data, not system. TWRP 3.2 on those systems tries to create one huge file instead of breaking them up. When I first unlocked and rooted my Axon, running TWRP 3.2, I couldn't backup the stock ROM. Downgraded to 3.1.1, backed up the ROM, then went back to 3.2. I use Dual Boot Patcher on that device anyway so it handles the backups now. The Moto uses MultiROM-TWRP 3.1.1 where backing up is not an issue.
Just wondered why 3.2 changed things.


ZTE Axon 7 A2017U, Project New World, Multiboot, XDA Legacy

On my G5S+, with a FAT32 SD card and TWRP 3.2.1-R20 my backup fails on full system image (it passes on just backup of /system but I need a full backup since I run rooted stock) It also completely backs up 15GB of data to my FAT32 SD card as well without a single issue. If I tell it to do system image and data, it fails right at the end of /system as it is preparing /data for backup. If I run just /data it backs up fine to my SD card.
I might suggest rechecking your logs to verify it fails on /data instead of /system during a backup.
 
  • Like
Reactions: marcdw

TheGreenDash

New member
Oct 15, 2018
2
0
Compatibility

Sorry but, i have a moto g5s plus xt1800, when i in fastboot, on some line says "sanders", i flash another twrp, but no response from the screen, boot into twrp but when i press nothing happens, this twrp will work for me? O
 

ainstushar

Member
Sep 28, 2013
34
10
Question

Hi there, I have installed r20 on my Moto G5s plus, and then I've installed the excellent pixel experience ROM (https://forum.xda-developers.com/moto-g5s-plus/development/rom-pixel-experience-t3856824). I am now trying to install magisk 17.1 via zip file using this twrp, but I am running into an issue: I get an error message saying it can't mount /vendor. From googling, I've stumbled upon the fact that it can happen in twrp that is not-treble. Is there a way to fix it? Do I need to downgrade to twrp 16 for sanders?

Thanks!
 

jakson7474

Senior Member
Oct 13, 2014
147
37
Salvador
Hi there, I have installed r20 on my Moto G5s plus, and then I've installed the excellent pixel experience ROM (https://forum.xda-developers.com/moto-g5s-plus/development/rom-pixel-experience-t3856824). I am now trying to install magisk 17.1 via zip file using this twrp, but I am running into an issue: I get an error message saying it can't mount /vendor. From googling, I've stumbled upon the fact that it can happen in twrp that is not-treble. Is there a way to fix it? Do I need to downgrade to twrp 16 for sanders?

Thanks!

Use this twrp is the treble version

https://drive.google.com/file/d/1CIDGLaJMZaKC6S7UGOen1UUEvv9V_M62/view?usp=drivesdk
 
  • Like
Reactions: ainstushar

neo_da_leo

Member
Jan 24, 2013
33
8

Attachments

  • error.png
    error.png
    12.6 KB · Views: 121

chaostrodamis

Senior Member
Mar 14, 2010
507
117
Google Pixel 4 XL
Google Pixel 5
  • Like
Reactions: neo_da_leo

neo_da_leo

Member
Jan 24, 2013
33
8
That twrp is good. Flash twrp in fastboot then enter command "fastboot reboot recovery". When inside twrp flash twrp again as an image from twrp itself. That will give you a permanent twrp.

Sent from my Moto G5S Plus using XDA Labs

Thanks, It worked
It was showing "Swipe to allow modifications for /system", then I swiped but Internal Storage is showing 0MB. I can't do anything.

Is it necessary to install magisk.?
 

pranavpmanoj

Senior Member
Thanks, It worked
It was showing "Swipe to allow modifications for /system", then I swiped but Internal Storage is showing 0MB. I can't do anything.

Is it necessary to install magisk.?
You'll have to format data to access it. Take a backup of everything and open TWRP>Wipe>Format Data> Type YES.
After completing the above step, go back and reboot to recovery. You should be able to view your internal storage now.

Magisk is necessary only if you need root.
 
  • Like
Reactions: neo_da_leo

tinyjackal0pe

New member
Dec 28, 2016
2
2
My stupid ass didn't read the directions, so TWRP runs OpenRecoveryScript, fails, and gets stuck in a bootloop. TWRP tells me that it fails to mount /data due to an invalid argument. Please, someone explain it like I'm five.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 49
    Unofficial TWRP for Moto G5S Plus (Sanders)​

    Additional Features over Official TWRP:
    • Supports flashing of both 32bit and 64bit ROMs and Kernels.
    • OREO Images/ROMs support.
    • Decryption and Encryption support.
    • No SuperSU by default.
    • No TWRP app.
    • No HTC Dumlock cruft.
    • Updated pigz compressor (slightly faster and more tolerant of corruption).
    • NTFS support(Both Read and Write).
    • Covers more partitions for nandroid backup (OEM, FSG and FSC).
    • Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
    • Faster I/O performance.
    • Fixed Gapps/aroma freeze issues.

    IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!

    • At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
    • Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
    • If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data


    Flashing Instructions:

    Using Existing TWRP:
    Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery


    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)

    Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
    Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot

    Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want. :)


    Download Links: https://www.androidfilehost.com/?w=files&flid=216298

    TWRP Themes: Check 3rd post

    Known Issues: None || Report if you find any.

    XDA:DevDB Information
    [RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus

    Contributors
    CheckYourScreen
    Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders


    Version Information
    Status: Stable
    Current Stable Version: r20
    Stable Release Date: 2018-04-04

    Created 2017-10-26
    Last Updated 2018-04-04
    15
    Updated to 3.2.1-r15..!

    Hey fellas!
    Updated to TWRP 3.2.1-r15 with following changes:
    • Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it)
    • Fixed Encryption Support! (No need to format data to decrypt and mount)
    • Updated to 3.2.1 upstream changes with full oreo support.
    • Remove android reboot during password check on multiple wrong inputs

    Added 64bit support so you can flash the upcoming 64bit version of custom roms and kernels.
    No need to format data, twrp will be able to mount encrypted partitions now. :highfive:
    Loading time of twrp might be increased due to necessary features like QSEE loading in TZ(For encryption support) and higher compression modes, so bear the waiting time of extra couple of seconds.
    Happy Flashing! :)
    12
    || Changelog ||

    r20:
    • Fixed Encryption support on custom roms.
    • Updated kernel
    • Updated build fingerprint for latest bootloader support.
    • Reverted pigz changes.
    • Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
    • Various bug fixes and improvements.
    r16:
    • Fixed compatibility with New Bootloader (C2.07-December patch)
    • Merged october patches in kernel.
    • Various twrp upstream patches and fixes.
    • Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
    r15:
    • Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
    • Fixed Encryption Support! (No need to format data to decrypt and mount).
    • Updated to 3.2.1 upstream changes with full oreo support.
    • Remove android reboot during password check on multiple wrong inputs.

    r9:
    • Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
    • Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
    • Fixed size of various partitions.
    • Switched to LZMA compression to decrease size.

    r7: Initial Public Release
    12
    Updated!

    Hi folks!
    Updated twrp to r20 with following changelog:
    • Fixed Encryption support on custom roms.
    • Updated kernel
    • Updated build fingerprint for latest bootloader support.
    • Reverted pigz changes.
    • Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
    • Various bug fixes and improvements.
    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!
    8
    Updated!

    Hi folks!
    Updated TWRP to r16 with following changes:
    • Fixed compatibility with New Bootloader (C2.07-December patch)
    • Merged october patches in kernel.
    • Various twrp upstream patches and fixes.
    • Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)