yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] fgl27:
I made a 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

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, but on Quark that partition is complex and need some explanation on how to use the zip so I made the below hide tutorial...

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

mdm1m9kefs1

mdm1m9kefs2

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

mdm1m9kefs1.img

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

adb shell
su

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

root@:/ #

then... do the next 4 lines

dd if=/dev/block/mmcblk0p1 of=/sdcard/modem.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/mdm1m9kefs1.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/mdm1m9kefs2.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

mdm1m9kefs1.img

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

Share this on Quark related thread, and if need help let me know... :good:
[Moto Maxx Original Android Development] TheSt33v:
That would be awesome. Encryption is the last thing on my list that would make RR the ideal, 100% perfect rom.

Also, if it helps, when I encypt using the stock rom and stock recovery, TWRP can decrypt it just fine. As soon as CM or RR get flashed though, it can't.
[Moto Maxx Original Android Development] fgl27:
I update the modem flasher, as there is no point to flash a old radio status image, I update it to clean radio stat so it is clean after the flash of the new "radio.img"

And I have test the Clean_modem_status.zip to solve GPS problem and it works just fine... :good:
[Moto Maxx Original Android Development] fgl27:
I have finished update TWRP build on MM the changelog in relation to official one is

===================

May-14-2016

====================

* twrp-3.0.2-0-Mod-quark

* Build TWRP on android Marshmallow source

* Change TWRP name to twrp-3.0.2-0-Mod so the user knows that is using the mod one

* Update the Kernel to a Mod version of my BHB27 kernel to better fit TWRP needs

* Included NTFS support, Test whit 16GB PD and 1TB external HD works great but NTFS is slow on TWRP

* Included Extra language (Japanese, Chinese Simplified and Traditional)

* Add Modem partition Backup/restore option

* Add USB-OTG to the wipe options (this is not a format of USB is just a "wipe" erase of the files, if need to format USB use PC or android app)

* Enable by default DT2W and S2W on TWRP (just like on my kernel)

* Enable Thermal driver (prevent over heat on TWRP)

* Update TWRP vendor libs from MM soak 3

* General improves to TWRP for quark

* Included all lates changes of TWRP source

It can be Download on my mirror folder

Notes:

NTFS is more slow to use, so backup/restore from a NTFS driver can be slower.

This version seems a little slow to backup/restore compare to official one, this is not a final version and will be improve on future updates, as the kernel is from 5.1 after update it to a MM moto source, and TWRP/android MM updates must be improves.

As today is not possible to implemented decryption on TWRP I try, so user be aware that the warning before encrypt are true encryption can only be reverted by formatting the data partition.

I tested encrypt on custom Marshmallow ROM, it is not need any recovery the only thing that is need is that the encryption block of data be clean before encrypt, 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:

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

Any bug found let me know... :good:
[Moto Maxx Original Android Development] ChazzMatt:
Can this "Marshmallow" TWRP version be used with Lollipop ROMs? OR only Marshmallow?
[Moto Maxx Original Android Development] fgl27:
Indifferent.. TWRP is a android OS, TWRP version is indifferent to user system OS.

The relation of the OS is with the bootloader, newer bootloader that probably will came with the next stock from moto may prevent old TWRP (and old stock or custom ROM) from boot, but the reverse will not, old bootloader and newer TWRP must work (ROM will need more test).

So keep it update to keep it compatible with the bootloader... that is way next official only after the bootloader gets update to make shore of the compatibility...
[Moto Maxx Original Android Development] gangrenius:
Can this new Twrp mod be used with CF stock mod 5.1 for Verizon turbo
[Moto Maxx Original Android Development] fgl27:
the post above doesn't answer to you?
[Moto Maxx Original Android Development] fgl27:
I manage to improve read and writing it is now as good as official, update the link with

twrp-3.0.2-0-Mod_01-quark.img

+ I have forgotten to mention that this mod version have the default brightness to 25% at TWRP and during boot of TWRP the user can change that on the settings...

===================

May-16-2016

===================

* twrp-3.0.2-0-Mod_01-quark.img

* Improve backup/restore speed

:good:
[Moto Maxx Original Android Development] fgl27:
TWRP Mod update

===================

May-26-2016

===================

* twrp-3.0.2-0-Mod_02-quark.img

* Fix decryption of custom ROM's

* Enable Logcat/LogD

* + General improves

TWRP can't remove encryption can only access the encrypted Data partition and backup/restore it, to remove encryption fallow the post above...

Any bug found let me know.
[Moto Maxx Original Android Development] kitcostantino:
Thank you [MENTION=5747496]baybutcher27[/MENTION] for all you are doing for our Quarks.

-King of Unsolicited Advice
[Moto Maxx Original Android Development] TheSt33v:
I just re-encrypted my phone running the latest RR and tried to access the encrypted partition using this TWRP. The password still fails, although it takes longer to do so than the previous version.
[Moto Maxx Original Android Development] fgl27:
the attached pic of my post is from the result of TWRP of the situation you described... RR encrypt test with password and pin, other security methods may not work as TWRP can understand swipe...

after the error click cancel ope TWRP
[Moto Maxx Original Android Development] fgl27:
the attached pic of my post is from the result of TWRP of the situation you described... RR encrypt test with password and pin and it just works, other security methods may not work as TWRP can't understand swipe... and I didn't test without security lock.

after the error click cancel to open TWRP connect the phone to PC and give a command on the adb folder, adb logcat and post to me the result like this... when adb logcat is running, go to mount and click on decrypt data it will prop the password again and the log will display the error...
[Moto Maxx Original Android Development] TheSt33v:
Here you go. I'm using a PIN. I'm also using the latest RR with your latest kernel, if that matters.
[Moto Maxx Original Android Development] TheSt33v:
I got it working. The problem was that when I previously did a factory reset (and formatted the data partition), I did it using the Droid Turbo stock recovery menu. I tried formatting /data with TWRP and re-encrypting, and everything now works perfectly. Thank you very much for working this out. I know a lot of other Droid Turbo owners that were waiting for this feature as well.
[Moto Maxx Original Android Development] gangrenius:
Hey bud so I can just encrypt/decrypt now with no issues on RR and the modded twrp
[Moto Maxx Original Android Development] TheSt33v:
Seems that way. At least, that was my experience.
[Moto Maxx Original Android Development] kitcostantino:
i don't know if anyone is interested, but these themes work with the latest version of bb27 twrp for our quarks. http://xdaforums.com/android/themes/theme-twrp-3-0-0-0-dark-stock-colors-t3310235http://
[Moto Maxx Original Android Development] Ducadim:
Just tried[emoji6] ... Awesome! But the link little bit wrong [emoji12] , http://xdaforums.com/showthread.php?p=65199244

[THEME][TWRP] TWRP 3.0.2 dark stock theme pack w different colors v2 [07.03.2016]

from XT910 or XT925 using Tapatalk
[Moto Maxx Original Android Development] pmou:
thanks so much for the mod! i fastbooted it on to my device and am now able to decrypt my xt1254 stock encrypted/cm rom'd partition and install supersu!
[Moto Maxx Original Android Development] pmou:
I'm not entirely sure if it's related, but about the same time as flashing this, my ambient display has stopped working. After reflashing the unmodded TWRP (as well as radio and bootloader), it will turn on for notifications but never turns on for accelerometer or proximity. It looks as though the IR sensors are never even turning on. Any advice? I have tried a new nightly version and reflashing everything.
[Moto Maxx Original Android Development] unhappybirthday:
Did you switch from the stock ROM (with MOTO display) to CM (with ambient display)? I believe they work differently.
[Moto Maxx Original Android Development] pmou:
Sorry let me explain a little better..

Came from stock ROM. used the Moto display. Installed cm 13 nightly. Had the new ambient display enabled under settings, working fine. I wanted to install SuperSU, so I used the modded twrp so that it could read my encrypted system. Installed SuperSU. Since then, I have been unable to use ambient display successfully. I tried reflashing the SU4tl-49 stock ROM that I found on the forum, it never booted I got a black screen after entering my pattern. Have now gone back to cm 13, still no luck. Have also tried reflashing the non modded twrp, nothing. Done factory wipes from twrp several times with no luck.
[Moto Maxx Original Android Development] pmou:
I've solved my problem, still not sure how it was originall caused. I found a hidden to me setting under gestures, which controls how the ambient display is awakened. both proximity and phone movement were turned on. by turning them both off, turning the ambient display off, and then turning them all back on in reverse order, it has fixed itself. just wanted to follow up/include for completeness.
[Moto Maxx Original Android Development] ChazzMatt:
It's not hidden. Been discussed thoroughly. You don't just turn on Ambient Display, you also have to define WHAT is shown and when, in Gestures.

It's not a TWRP issue, it's just settings in CM-based ROMs. This post below is one from CM12.1, but the concept is the same and I believe the settings are about the same. I'm reposting it to make sure you found all the settings.

http://xdaforums.com/showpost.php?p=66362669&postcount=2
[Moto Maxx Original Android Development] pmou:
Thanks for the thorough reply. I understand it wasn't hidden, I meant "hidden-to-me" as in my eyes missed it. I guess coming from moto display, it was a little confusing to have settings in two different locations. anyway, not to hijack the topic. only posted it here because I thought it could have been related. Great work on the mod, thanks baybutcher.
[Moto Maxx Original Android Development] ChazzMatt:
That's OK. It is slightly different from Moto Display, but in my opinion is better.

Also some people do not understand the display needs to be LOCKED for the Quark-customized Ambient Display to work. They use smart unlock exceptions, whether wearables or on-person, and then mistakenly complained about "butt dialing" because the touch screen was active. It was their own fault and had NOTHING to do with Ambient Display. They had unlocked their own displays! Ambient Display only works with a locked display, so Ambient Display was out of the equation.

I have a pattern passcode on mine because my work email requires either pin or pattern.
[Moto Maxx Original Android Development] quantum tao:
it wasn't a mistake, it was a bug that was acknowledged and squashed by [MENTION=2228410]Skrilax_CZ[/MENTION] . i still like moto display better, i have used both extensively. I have gotten used to ambient display and it doesn't irk me as bad anymore. except for the bug where if ambient display is active and the screen is off, notification sounds are cut off or dont play at all.
[Moto Maxx Original Android Development] Crateman:
Bypass the TWRP "Keep system read only"

Hi everyone!

My Moto Maxx has a broken digitizer and now I'm unable to use any touch inputs. I'm in the middle of hacking my way into bootting and using my phone by only using ADB commands, but in order to continue I need to bypass the TWRP "Keep system read only" so I can mount /data and do all the changes I need. Is there any way I can enable "Allow Modifications" without using a touchscreen? I know is a very rare problem, but any help will be greatly appreciated.

Thanks!
[Moto Maxx Original Android Development] fgl27:
Unzip file attached, place on sdcad/TWRP then boot/reboot to recovery... that must by pass it, but I never used TWRP via command don't really know what to do next...
[Moto Maxx Original Android Development] Crateman:
EDIT: Nevermind! After a second reboot it worked! Thanks!! :D
[Moto Maxx Original Android Development] iHusky:
Someone can tell me why TWRP 3.0.2 don`t work (stop on start screen) while I set my microSD card like internal memory?
[Moto Maxx Original Android Development] ChazzMatt:
You are in the wrong forum. None of the Quarks have microSD cards.

This is TWRP for Motorola Quark phones, not for any other phone.

[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
[Moto Maxx Original Android Development] iHusky:
Ok sorry you can delete this posts
[Moto Maxx Original Android Development] fgl27:
Are you shore you are on the right device thread?

This devices doesn't have SD card slot.
[Moto Maxx Original Android Development] iHusky:
No, I had LG G3s but I searched in google about don`t working TWRP and I found this topic
[Moto Maxx Original Android Development] quantum tao:
darn, i got excited that maybe someone found a hidden slot on quark. :silly:
[Moto Maxx Original Android Development] fgl27:
TWRP Mod update

Download

Note:

Is not possible today to build this version in the official Server (Gerrit changes of TWRP source need to be merged by TWRP team) when the server can build this version I push the changes to a new official TWRP to be made.

===================

Ago-08-2016

===================

* All the previously TWRP Mod + the below

* Kernel Update to the latest version of BHB27-Kernel v201-0 this kernel have the best featuring to feat TWRP need

* This kernel uses the latest Motorola kernel source

* Tune the kernel start script to better fit TWRP

* Included the latest TWRP updates to this date

One update to comment is:

ADB: Add adb backup for TWRP. (Had no time to test but must work)

Functionality for client side to backup

tar and image streams over adbd to the client under backup.ab.

Using adb backup on the client side you can backup the partitions

TWRP knows about.

On the client side you can do the following:

adb backup -f <filename> --twrp <options> where options are

--compress: compress data

system: backup system

cache: backup cache

data: backup data

boot: backup boot

etc for each partition.

You can string multiple options,

i.e. adb backup -f <filename> --twrp --compress cache system data

adb backup in TWRP will take any option corresponding

to TWRP fstab partitions, e.g. efs boot as well.

If you do not specify the filename with the -f option,

adb will backup your data to a filename backup.ab on the client.

You can then rename the file and encrypt it with desktop tools.

If you don't want to use command line arguments:

adb backup --twrp

will bring up the gui and allow you to choose partitions

from the backup page.

To restore the backup use the following convention:

adb restore <filename>

Structures are used to store metadata in binary inside

of the file itself. If the metadata structure is modified,

update the adb version so that it will invalidate older

backups and not cause issues on restore. When restoring,

we currently do not support picking specific partitions.

It's all or nothing.

If found any problem let me know
[Moto Maxx Original Android Development] gangrenius:
BHB27 I recently switched from alway using your mod kernel to the kernel that comes with RR for quark. I don't need your kernel for this Twrp to work do I?
[Moto Maxx Original Android Development] fgl27:
No TWRP has building kernel.
[Moto Maxx Original Android Development] z4ck1n:
slow ntfs fixed?
[Moto Maxx Original Android Development] fgl27:
That is not a bug is just how the featuring is. I only test for "work or not" it works.
[Moto Maxx Original Android Development] fenix3nk0r3:
What is better F2FS or EXT4 for flashing ResurrectionRemix-M-v5.7.3-20160810-quark.zip
[Moto Maxx Original Android Development] z4ck1n:
I wanted to do nandroid block level backup on my externally powered 1TB NTFS drive. Problem is its not getting detected, mount USB OTG option doesn't get ticked.
[Moto Maxx Original Android Development] fgl27:
System can only be flashed in ext4 partition.

not getting detected, or no power to start it?

My 1TB driver works just fine, and it doesn't need any external power the device can start it.

Check the driver on the OS if works there the problem may be some thing else, if didn't work there is no support for that driver.
[Moto Maxx Original Android Development] Claps1775:
When I download your trwp mod 3. It downloads and says its a disc image and I am not able to flash using adb fastboot. Do I need to change something to make it work. Also, says the same thing when I download the OG twrp.
[Moto Maxx Original Android Development] ChazzMatt:
what commands are you typing?
[Moto Maxx Original Android Development] Claps1775:
In the adb fastboot screen. I out flash fastboot recovery and I drag the file over to adb fastboot screen then hit enter.
[Moto Maxx Original Android Development] ChazzMatt:
I've never heard of that method. Not saying it won't work, but it hasn't so far for you.

Here's what does work: type the entire command and have the TWRP image file in the ADB folder so it can be found. Be sure you enable seeing file extensions on your PC so you know the exact name of the file.

See the root thread by [MENTION=5901115]TheSt33v[/MENTION] in the Droid Turbo/general forum. Follow the those instructions, especially in SECTION 2 (flashing TWRP) of the OP. A lot in that thread is Droid Turbo XT1254 specific. Those with XT1225 and XT1250 would not follow all the instructions in that thread.

[GUIDE] How to unlock your Droid Turbo XT1254 bootloader, install TWRP and gain root access

http://xdaforums.com/showthread.php?t=3292684

also see these posts in that thread for common mistakes flashing TWRP:

http://xdaforums.com/showpost.php?p=68211093&postcount=302

http://xdaforums.com/showpost.php?p=68212100&postcount=306

http://xdaforums.com/showpost.php?p=68222204&postcount=309

http://xdaforums.com/showpost.php?p=68224106&postcount=311

_______

For XT125 and XT1250 users THIS BELOW is what you need:

Updated Root & TWRP installation Guide for Moto XT1225 and XT1250

http://xdaforums.com/showpost.php?p=67955296&postcount=261
[Moto Maxx Original Android Development] Claps1775:
I will check it out later this weekend. Wife and I left on a vacation today.
[Moto Maxx Original Android Development] Claps1775:
I went through and read the post and followed. I am getting this when I am following it to a T.

Microsoft Windows [Version 10.0.10586]

(c) 2015 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices

XXXXXXXXX fastboot

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img

(bootloader) has-slot:recovery: not found

error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img

(bootloader) has-slot:recovery: not found

error: cannot load 'TWRP.img'

C:\Program Files (x86)\Minimal ADB and Fastboot>

Not sure what I am doing wrong. I have already done SunShine on Friday and its is unlocked. On my phone. It does say AP Fastboot Flash Mode (secure). I am lost here.
[Moto Maxx Original Android Development] fgl27:
have you try the fastboot I share?

Download Fastboot

And maybe run cmd as admin, I never need but may be the case of your problem.

*The fastboot I share is need replace fastboot with mfastboot in the commands lines...

I update #2 post with that file
[Moto Maxx Original Android Development] Claps1775:
I have tried yours and says the same. Yours was the first I tried. When I open Minimal ADB and Fastboot it asked for permission and I grant it. Do I need to rename yours to TWRP.img then? I will try using mfastboot and see.

---------- Post added at 09:01 AM ---------- Previous post was at 08:52 AM ----------

I downloaded your mfastboot. I renamed your twrp file to TWRP.img to make it easier to make less errors. I am getting this now.

C:\Users\Claps1775\Desktop\mfastboot>mfastboot devices

XXXXXXXXXX fastboot

C:\Users\Claps1775\Desktop\mfastboot>mfastboot flash recovery TWRP.img

target max-sparse-size: 256MB

error: cannot load 'TWRP.img': No error

C:\Users\Claps1775\Desktop\mfastboot>