• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[RECOVERY][TWRP 3.3.1][For all Quark][Moto Maxx/Turbo and Droid Turbo]

Search This thread

fgl27

Recognized Developer
Feb 27, 2014
3,657
9,486
Brazil...South of the south
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

How it looks :
twrp_new.png

* This must work on all devices model quark (XT1250 and XT1254) or quark_umts (XT1225) * custom ROM may display only quark
To know you device model just open the app Terminal Emulator for Android and see the quark after the @ like below.


twrp_terminal.jpg

Main download folder
Mirror download folder

The folder contains the Mod TWRP version base on the latest official with proper support to all android versions (The one from TWRP site doesn't have the proper support For Nougat, Oreo or newer OS's, I tryed to push the changes so the one from they site can be updated they did not answer me so I give it up), the mod other than having the proper support for all OS that prevent bug as the "Bootloop to TWRP after a Factory Reset" it has extra backup option (Radio/Modem, boot logo etc), NTFS support for USB-OTG devices, all possible TWRP languages, full encryption support (For Nougat and earlier, Oreo and up encryption is not suported) and etc improves...
All the extras featuring can be seen in the Changelog click here

Big thanks:
A big thank for those that donating to thanks for my work on TWRP.
@ChazzMatt for his donation, and his help on many other threads of Moto Maxx on XDA.
Renan R. R. for his donation
And all the other users that I contribute.

On the developer side, thanks to:
@Dees_Troy for his work on TWRP, for the tutorial and help to bring the official support...
@Skrilax_CZ for his hard work on building the first stable CM to this device
@Aadi for a tutorial.
@respider for his original work on TWRP for quark.

Developer donation link:
To donate via paypal click here
No other donation option is available.

XDA:DevDB Information
TWRP For all Quark(Moto Maxx/Turbo and Droid Turbo)

Contributors
fgl27
Source :
Android :
Device :
TWRP Version: 3.3.1
Kernel: Linux 3.10.x

Version Information
Status: Stable

Created 2015-08-16
Last Updated Check changelog (click here)

I use many tutorial to make this TWRP, here some to help those who want to do the same.
 
Last edited:

fgl27

Recognized Developer
Feb 27, 2014
3,657
9,486
Brazil...South of the south
Check Changelog click here

How to install it.

Using Fastboot:

Download mfastboot
The fastboot I share is need replace fastboot with mfastboot in the commands below...

Copy the file you download form OP to the folder of fastboot and use the command in the bootloader screen

Code:
fastboot flash recovery recovery_name.img

! replace recovery_name with the name of the file, example:

Code:
fastboot flash recovery twrp-3.0.2-0-quark.img

Via app Flashify (for root users)
If you have root, try Flashify is really simple.

Install the app, download the recovery to the phone internal memory, open the app, chose recovery image, chose from file, confirm and flash, after you will go straight to the new recovery.

Via TWRP:

Yes TWRP can flash images recovery and boot image.

- install
- images... (is in the bottom right of the screen)
- select the image and image type (boot or recovery)
- swipe
- reboot to test, to recovery if flash a recovery or to system if is a boot...
...............................................................................

keep system read only?
1%20(1).png

This will be asked in the first time you boot to recovery after flash the recovery, if you not accepts it TWRP may be replace by the previously recovery of your device, but read way...

Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

..............................................................................
Note about restore from Stock 5.x.x to 4.4.4 and vice versa:

The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.

I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.

TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.

That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.

To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>

For Kitkat android 4.4.4 choose EXT4
For lollipop android 5.x.x choose F2FS

Swipe to change
Now restore.

But be aware that the data partition is were internal memory is, so if you change the file system you will loose all the files in internal memory

The wipe of internal memory doesn't happening if you only wipe data partition without change file system.

This will not affect custom ROM, but i recommend to use f2fs.


.....................................................................................
Note about encrypt

Test done in Nougat in the link below
Last Nougat test

Test done in Lollipop below
TWRP supports backup a encrypted system, but i only test this on lollipop stock ROM.

This is a simple description how to encrypt backup and restore the encrypted system.

Stock ROM


You can only encrypt if you have stock recovery and no modification to yours ROM, that means no root or rooted app like xposed modules etc, so if you have uninstall everything and do a full un-root.

To encrypt go to setting>secure>encryption the process take a while...

If you already have stock encrypted ROM you can flash TWRP and make a backup of it.

To remove the encryption you need to flash back the stock recovery and do a factory reset in Settings>Backup & Reset>Factory Reset

Factory Reset will deleted all the files of the device! so make a copy of important data...

Wiping all the partition in TWRP will not remove the encryption.

After the device finish the factory reset all the data of you phone will be deleted and the encryption will be gone.

Now you can flash back TWRP again and have fun...

If you need to restore that encrypted backup you can but after it finish restoring you will see that it is un-encrypted.

Custom ROM

I tested encrypt on custom Marshmallow AOSP base ROM (all the CM's), it is not need any recovery the only thing that is need to encrypt is that the encryption block of data be clean before encrypt.

Cleaning the encryption block of data
TWRP can't clean that so if the user encrypt the device the only way of clean that is by erasing the data via fastboot:

Code:
mfastboot erase userdata

The down side of it is that the partition will be erased lost every file of data and internal memory + when the system boot the data partition will be formatted as EXT4 that have a small performance lost over F2FS, to have it back to F2FS is need to give the command then start the OS, after the device finish boot and optimized it will format the partition and is need to go back to recovery and format the data as F2FS, going on wipe > advanced > select data > "repair change..." >change file sys> F2FS... then boot to the device and use it...


Note about official TWRP, USB driver via USB-OTG work, but your driver need to be formatted as FAT32(small drivers) or exFAT (big drivers), on the Mod version I have update the NTFS support and it now works
...........................................................
Collection of "Special_flash_zip" to go with the Mod TWRP
As some things are not directly attainable through TWRP menus, but they can be achieved via extra zips...

Clean_modem_status.zip
Logo_Flasher.zip
Modem_Flasher.zip

Clean_modem_status.zip

as the name implies this will erase the modem status partition, and erase any bad modem status, this can help in situations were the users is with some radio problem, one most famous on Quark is when user can get a GPS lock...

I test the GPS after flashing this and it works... (I did not had a GPS problem, but will test after I get one...)

Logo_Flasher.zip

This is a zip that can flash logo.bin via TWRP, is need of the user to have the logo.bin then place it inside of the root of the zip, then flash it over TWR.

Modem_Flasher.zip,
This is a zip made to flash the Radio.img + Clean modem status, thus achieving the update of Radio and clean any bad old radio status.

This zip is empty need the user to add the files on the future I will make a zip with the radio image inside... the below explain how to put the files inside.

As on Quark the radio.img is complex image that can't be flash via TWRP it is need to have a special zip, this zip contains the content of radio image after the user have flash it via fastboot, then for that I made this tutorial in how to use the zip, see the below hide...
Tutorial how to make this zip to work...

This zip must be used with a full backup of stock Modem image that can be achieve via app using apk called partition backup or via ADB

1# APP process... config the app Click on the tool, then in backup formats section, mark only Raw partition image
The partitions name to backup are

modem
mdm1m9kefs3

the file must be in sd/Partitionsbackups, the file names need to be just like describe below
before you put they on the zip so rename the files according the below...

modem.img
mdm1m9kefs3.img

make no modifications to the files, and place it on the root of this zip

The just flash the zip via TWRP

#############

2# ADB process, you must have SuperSu from Chainfire installed before making this, CM root will not work.

use the commands "adb devices" to check if the device is connected it will show the device serial number if it is...
then do the next two lines

Code:
adb shell
su

* after command "su" press enter 3 or more times... until the cmd displays

[email protected]:/ #
then... do the next 4 lines

Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
dd if=/dev/block/mmcblk0p32 of=/sdcard/mdm1m9kefs3.img

the files will be on the internal memory, the file names need to be just like describe below before you put they on the zip

modem.img
mdm1m9kefs3.img

make no modifications to the files or to the file name, and place it on the root of this zip

The just flash the zip via TWRP


The recommendation is to make a modem backup of yours device after you get a GPS lock, and store it to use whenever you need because you have a radio related problem, or make one to share on XDA with other users, be aware to share Radio zip and describe from with device model and ROM you pull it from, because flashing other device Radio may cause problem...


............................................................
This TWRP is theme-able, go to the tread to change the looks:

[THEME][TWRP] TWRP Materialised - Dark / Light / Play
 
Last edited:

fgl27

Recognized Developer
Feb 27, 2014
3,657
9,486
Brazil...South of the south
Update my source.

I can now compile TWRP from CM, Mokee and Omni source's.

Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.

My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.

Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.

+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
 
Last edited:

icondeg

Senior Member
Dec 19, 2009
175
60
México
Update my source.

I can now compile TWRP from CM, Mokee and Omni source's.

Omni source is the best one because is the TWRP source, but it doesn't have quark device tree, so i need to create/port everything and that take time, i'm finishing the testing of the new TWRP no new feature just a more slim image but more complete.

My CM tree is incompatible with TWRP source, Dees_Troy was not able to use my previously tree to build the Official one he tried.

Now after the test i will send the new source and he will be able to produce a new TWRP from TWRP server and if that work make this Official.

+ Now that exist a quark device tree working on omnirom may some one make a AOSP ROM using it (i don't have time right now but i will try in the future after the Official TWRP).
Omni is the most close AOSP source to google AOSP so a rom from they is really clean and very update. I believe that CM kernel tree should work, if any one try let me know...
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it

A kernel that we can use is the second dream of this forum

Jejejeje

Regards

Enviado desde mi Moto MAXX mediante Tapatalk
 

ChazzMatt

Recognized Contributor
Nov 30, 2010
18,469
14,333
Atlanta, Georgia
What about a kernel??
@w4tchout is trying to make a kernel but it seems so hard to do it

A kernel that we can use is the second dream of this forum

@w4tchout
@Skrilax_CZ

Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...

I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.
 

##W4TCH0UT##

Senior Member
Oct 7, 2013
1,629
2,115
22
\\___TheMiddleOfNowhere___//
@w4tchout
@Skrilax_CZ

Has Motorola ever released the mandatory kernel source code for 5.1 for the XT1254? Been two months since 5.1 was released for the Droid Turbo. It's a Quark, just like the XT1225...

I know @Skrilax_CZj is using the kernel sources from stock 5.0.2 for CM12.1 (Lollipop 5.1). But would be nice to be able to use something from Motorola updated 5.1, if possible.

I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.
 

fgl27

Recognized Developer
Feb 27, 2014
3,657
9,486
Brazil...South of the south
I don't know the actual problem as to why my kernel doesn't boot, it could be the dt img or the kernel itself. I'll try to figure it out though.

I don't know much about Kernel yet so i cant see what is going wrong in yours...

But i find a workaround, to compile the recovery.img without compile the boot.img i generated a boot.img but use pre build dt + kernel.

That way i can compile recovery in under 13 min and without a kernel folder in the source, before it take over 30, and when i'm resolving bug and error, how much fast i can produce a image better.

The workaround i copy from victara and put in the omni folder of my device source, is need the mkbootimg.mk + dtb (dt image renamed) + kernel.
Then check BoardConfig.mk kernel lines, the dt and kernel i use from a previously build of my on, after you have one no need to compile the kernel every time...

Don't know if this will help but this way you may grub a previously working dt + new kernel or vice versa, and combine to see what works.

My CM source folder is working but not update do to that yet but i believe will work in others source other then omni.

if something work or not let me know.
 
  • Like
Reactions: ChazzMatt

Top Liked Posts

  • There are no posts matching your filters.
  • 50
    Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    How it looks :
    twrp_new.png

    * This must work on all devices model quark (XT1250 and XT1254) or quark_umts (XT1225) * custom ROM may display only quark
    To know you device model just open the app Terminal Emulator for Android and see the quark after the @ like below.


    twrp_terminal.jpg

    Main download folder
    Mirror download folder

    The folder contains the Mod TWRP version base on the latest official with proper support to all android versions (The one from TWRP site doesn't have the proper support For Nougat, Oreo or newer OS's, I tryed to push the changes so the one from they site can be updated they did not answer me so I give it up), the mod other than having the proper support for all OS that prevent bug as the "Bootloop to TWRP after a Factory Reset" it has extra backup option (Radio/Modem, boot logo etc), NTFS support for USB-OTG devices, all possible TWRP languages, full encryption support (For Nougat and earlier, Oreo and up encryption is not suported) and etc improves...
    All the extras featuring can be seen in the Changelog click here

    Big thanks:
    A big thank for those that donating to thanks for my work on TWRP.
    @ChazzMatt for his donation, and his help on many other threads of Moto Maxx on XDA.
    Renan R. R. for his donation
    And all the other users that I contribute.

    On the developer side, thanks to:
    @Dees_Troy for his work on TWRP, for the tutorial and help to bring the official support...
    @Skrilax_CZ for his hard work on building the first stable CM to this device
    @Aadi for a tutorial.
    @respider for his original work on TWRP for quark.

    Developer donation link:
    To donate via paypal click here
    No other donation option is available.

    XDA:DevDB Information
    TWRP For all Quark(Moto Maxx/Turbo and Droid Turbo)

    Contributors
    fgl27
    Source :
    Android :
    Device :
    TWRP Version: 3.3.1
    Kernel: Linux 3.10.x

    Version Information
    Status: Stable

    Created 2015-08-16
    Last Updated Check changelog (click here)

    I use many tutorial to make this TWRP, here some to help those who want to do the same.
    20
    Check Changelog click here

    How to install it.

    Using Fastboot:

    Download mfastboot
    The fastboot I share is need replace fastboot with mfastboot in the commands below...

    Copy the file you download form OP to the folder of fastboot and use the command in the bootloader screen

    Code:
    fastboot flash recovery recovery_name.img

    ! replace recovery_name with the name of the file, example:

    Code:
    fastboot flash recovery twrp-3.0.2-0-quark.img

    Via app Flashify (for root users)
    If you have root, try Flashify is really simple.

    Install the app, download the recovery to the phone internal memory, open the app, chose recovery image, chose from file, confirm and flash, after you will go straight to the new recovery.

    Via TWRP:

    Yes TWRP can flash images recovery and boot image.

    - install
    - images... (is in the bottom right of the screen)
    - select the image and image type (boot or recovery)
    - swipe
    - reboot to test, to recovery if flash a recovery or to system if is a boot...
    ...............................................................................

    keep system read only?
    1%20(1).png

    This will be asked in the first time you boot to recovery after flash the recovery, if you not accepts it TWRP may be replace by the previously recovery of your device, but read way...

    Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

    ..............................................................................
    Note about restore from Stock 5.x.x to 4.4.4 and vice versa:

    The format of data partition is different, in 4.4.4 is ext4 and 5.x.x is f2fs.

    I have restore more then 100 times in my test, in some i end-up in a "bad/bug ROM" and it happens when flash 4.4.4 over 5.0.2 or vice versa, in the most bad one the device lost response of the touch screen even in the recovery, the bug was simply resolved by restoring to stock via fastboot using files from a stock XML rom. In others bug's android boot after boot i try to unlock to use and it reset, and stay in that loop, boot try to unlock reset, i try to wipe everything but system and did not work, in all those case partition format of data was wrong.

    TWRP will backup the partition exactly how it is, If the backup is EXT4 and the Data partition of the device is f2fs TWRP will restore the data and will not change the format.

    That may cause a problem, so when restoring to a different OS version advanced wipe the partition and change the format.

    To do that click Wipe>advanced Wipe> select Data> click on Repair or change File System>change File System>

    For Kitkat android 4.4.4 choose EXT4
    For lollipop android 5.x.x choose F2FS

    Swipe to change
    Now restore.

    But be aware that the data partition is were internal memory is, so if you change the file system you will loose all the files in internal memory

    The wipe of internal memory doesn't happening if you only wipe data partition without change file system.

    This will not affect custom ROM, but i recommend to use f2fs.


    .....................................................................................
    Note about encrypt

    Test done in Nougat in the link below
    Last Nougat test

    Test done in Lollipop below
    TWRP supports backup a encrypted system, but i only test this on lollipop stock ROM.

    This is a simple description how to encrypt backup and restore the encrypted system.

    Stock ROM


    You can only encrypt if you have stock recovery and no modification to yours ROM, that means no root or rooted app like xposed modules etc, so if you have uninstall everything and do a full un-root.

    To encrypt go to setting>secure>encryption the process take a while...

    If you already have stock encrypted ROM you can flash TWRP and make a backup of it.

    To remove the encryption you need to flash back the stock recovery and do a factory reset in Settings>Backup & Reset>Factory Reset

    Factory Reset will deleted all the files of the device! so make a copy of important data...

    Wiping all the partition in TWRP will not remove the encryption.

    After the device finish the factory reset all the data of you phone will be deleted and the encryption will be gone.

    Now you can flash back TWRP again and have fun...

    If you need to restore that encrypted backup you can but after it finish restoring you will see that it is un-encrypted.

    Custom ROM

    I tested encrypt on custom Marshmallow AOSP base ROM (all the CM's), it is not need any recovery the only thing that is need to encrypt is that the encryption block of data be clean before encrypt.

    Cleaning the encryption block of data
    TWRP can't clean that so if the user encrypt the device the only way of clean that is by erasing the data via fastboot:

    Code:
    mfastboot erase userdata

    The down side of it is that the partition will be erased lost every file of data and internal memory + when the system boot the data partition will be formatted as EXT4 that have a small performance lost over F2FS, to have it back to F2FS is need to give the command then start the OS, after the device finish boot and optimized it will format the partition and is need to go back to recovery and format the data as F2FS, going on wipe > advanced > select data > "repair change..." >change file sys> F2FS... then boot to the device and use it...


    Note about official TWRP, USB driver via USB-OTG work, but your driver need to be formatted as FAT32(small drivers) or exFAT (big drivers), on the Mod version I have update the NTFS support and it now works
    ...........................................................
    Collection of "Special_flash_zip" to go with the Mod TWRP
    As some things are not directly attainable through TWRP menus, but they can be achieved via extra zips...

    Clean_modem_status.zip
    Logo_Flasher.zip
    Modem_Flasher.zip

    Clean_modem_status.zip

    as the name implies this will erase the modem status partition, and erase any bad modem status, this can help in situations were the users is with some radio problem, one most famous on Quark is when user can get a GPS lock...

    I test the GPS after flashing this and it works... (I did not had a GPS problem, but will test after I get one...)

    Logo_Flasher.zip

    This is a zip that can flash logo.bin via TWRP, is need of the user to have the logo.bin then place it inside of the root of the zip, then flash it over TWR.

    Modem_Flasher.zip,
    This is a zip made to flash the Radio.img + Clean modem status, thus achieving the update of Radio and clean any bad old radio status.

    This zip is empty need the user to add the files on the future I will make a zip with the radio image inside... the below explain how to put the files inside.

    As on Quark the radio.img is complex image that can't be flash via TWRP it is need to have a special zip, this zip contains the content of radio image after the user have flash it via fastboot, then for that I made this tutorial in how to use the zip, see the below hide...
    Tutorial how to make this zip to work...

    This zip must be used with a full backup of stock Modem image that can be achieve via app using apk called partition backup or via ADB

    1# APP process... config the app Click on the tool, then in backup formats section, mark only Raw partition image
    The partitions name to backup are

    modem
    mdm1m9kefs3

    the file must be in sd/Partitionsbackups, the file names need to be just like describe below
    before you put they on the zip so rename the files according the below...

    modem.img
    mdm1m9kefs3.img

    make no modifications to the files, and place it on the root of this zip

    The just flash the zip via TWRP

    #############

    2# ADB process, you must have SuperSu from Chainfire installed before making this, CM root will not work.

    use the commands "adb devices" to check if the device is connected it will show the device serial number if it is...
    then do the next two lines

    Code:
    adb shell
    su

    * after command "su" press enter 3 or more times... until the cmd displays

    [email protected]:/ #
    then... do the next 4 lines

    Code:
    dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
    dd if=/dev/block/mmcblk0p32 of=/sdcard/mdm1m9kefs3.img

    the files will be on the internal memory, the file names need to be just like describe below before you put they on the zip

    modem.img
    mdm1m9kefs3.img

    make no modifications to the files or to the file name, and place it on the root of this zip

    The just flash the zip via TWRP


    The recommendation is to make a modem backup of yours device after you get a GPS lock, and store it to use whenever you need because you have a radio related problem, or make one to share on XDA with other users, be aware to share Radio zip and describe from with device model and ROM you pull it from, because flashing other device Radio may cause problem...


    ............................................................
    This TWRP is theme-able, go to the tread to change the looks:

    [THEME][TWRP] TWRP Materialised - Dark / Light / Play
    13
    TWRP update
    twrp-3.1.1-mod_1-quark.img

    Changelog
    Download

    Any problem found report and use a old version, after some long time latest V seems stable for my taste...
    12
    TWRP update
    twrp-3.1.0-0_MOD_1-quark.img

    Changelog
    Download

    Any problem found report and use a old version.
    12
    TWRP update
    twrp-3.2.3-mod_1-quark.img

    Changelog
    Download

    Any problem found report and use V 3.1.1-mod_02 from the "Old versions" folder

    Backup of encrypted ROM untested, must be work as was for Nougat and older OS, for Oreo encrypted is untested by me, if anyone test let me know.