yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Original Android Development] trickster2369:
4.5 gb nandroid?!?! Holy crap! Just a suggestion, but have you tried wiping cache, dalvik cache before backing up? This should save a lot of space,and won't hurt the backup that's made.

It was all just an illusion
[X Style (Pure) Original Android Development] milski65:
I must be doing something wrong with backups. My original stock is over 7 gigs. Not new by any means. Just hadn't paid attention before.
[X Style (Pure) Original Android Development] Stryder5:
Did you enable compression?
[X Style (Pure) Original Android Development] milski65:
No to compression. I'll restore stock and do that.
[X Style (Pure) Original Android Development] vx2ko:
I have a question. Would it be possible for someone to build twrp with hardware overlays disabled and share it? I believe it is why my aroma installer zip will not load the GUI. Someone in the Moto G forum is having a similar issue and this was his workaround. I know nothing about compiling android or recoveries.
[X Style (Pure) Original Android Development] UniX1rm:
I have been using twrp, but I cannot boot into it. It seems like I have to do fastboot to get into twrp everytime. Even tried from the twrp app from the play store, but it takes me to the recovery "no command". Anyone had a trick to get into twrp? I rooted and have been using it.
[X Style (Pure) Original Android Development] milski65:
Maybe Quick boot from ps?
[X Style (Pure) Original Android Development] UniX1rm:
Figured it out. I had to go to reset preferences and and flashed again via fastboot and made it write to system.
[X Style (Pure) Original Android Development] milski65:
Sounded like something was fishy. Glad you figured it out.
[X Style (Pure) Original Android Development] jmileti:
Can you flash a backup from one MXP to another? If so. How?
[X Style (Pure) Original Android Development] milski65:
Should be able to. Just save backup to pc, then load to other phone and make sure you put it in twrp backup. I've done it with 3 previous phones twrp and cwm without issue.
[X Style (Pure) Original Android Development] jmileti:
That's what I thought. But why to PC then to phone. Its on external sdcard already. Made copies to internal. Nothing works
[X Style (Pure) Original Android Development] milski65:
This is the first time I've had issues with twrp and internal/ext and reading files. Honestly have no idea. Always used to be able to switch SD cards no problems. Sure someone has another solution. I just don't know how to do it. Regardless, transferring a backup from one phone to another, same phone, should be no issue for you. Maybe boot into twrp and change backup location from internal, which appears to be default, to external, make backup of whatever your on, then go back versus rebooting and see if restore shows nandroid from previous phone. I'm sure I made no sense with that.
[X Style (Pure) Original Android Development] jmileti:
In some crazy way I was thinking same thing. Maybe.
[X Style (Pure) Original Android Development] milski65:
Yikes. You understood that? Good. I'd try that first. Again, this is the first time in years I've been at somewhat of a loss.
[X Style (Pure) Original Android Development] jmileti:
No dice...oh well. Just gonna delete and rebuild my backups I guess.
[X Style (Pure) Original Android Development] milski65:
Damn it. Not the end of the world but there should have been a way to do it.
[X Style (Pure) Original Android Development] ursubpar:
Make sure every folder name matches. There should be a folder that starts with "TA" in twrp/backups. This is your device serial number that you can check in settings/about phone/status.

I ran into this same problem. TWRP/BACKUPS/"yourphoneserialnumber"
[X Style (Pure) Original Android Development] vx2ko:
Has anyone had any luck with Aroma installer with this recovery yet?
[X Style (Pure) Original Android Development] douglastabajara:
Hello folks, is there a way to install TWRP on Moto X Style/Pure running Android 6.0??
[X Style (Pure) Original Android Development] gulshanstrider:
I tried to flash this recovery on moto-x-style XT1572 Indian version on MM. After flashing I was not able to to boot in recovery. When I selected recovery in bootloader, the phone booted up and TWRP got replace by Stock Recovery.

Any ideas so that we can get it working on marshmallow?
[X Style (Pure) Original Android Development] alex1301:
Yeah, there is an option. Flash the bootloader of Indian 5.1.1 stock Rom and then flash TWRP. It's working like a charm.
[X Style (Pure) Original Android Development] Stryder5:
What command did you use to flash recovery?
[X Style (Pure) Original Android Development] timde9:
Is there any word when encryption will be supported. Seeing as many users are about to be forced into fde when marshmallow is released it seems fairly important to get this working.
[X Style (Pure) Original Android Development] gulshanstrider:
Fastboot flash recovery /path/recovery

.

Recovery was flashed successfully but I was not able to boot on recovery.
[X Style (Pure) Original Android Development] Stryder5:
Make sure you reboot before trying to boot straight into recovery.
[X Style (Pure) Original Android Development] Hashbang173:
Nobody is willing to test it...

I have a build with some changes for encryption but I need someone to try it.
[X Style (Pure) Original Android Development] timde9:
Well shoot I'm your man, send me a link if there's not one posted already
[X Style (Pure) Original Android Development] gulshanstrider:
I don't get what are you suggesting :D
[X Style (Pure) Original Android Development] Stryder5:
1. Flash recovery via fastboot.

2. Power off phone

3. Reboot phone into recovery.

You should now be in TWRP. It should say something about how you'll need to write changes to make it permanent.
[X Style (Pure) Original Android Development] MobileThrowAwayAcc:
Unified SD Card storage?

Has anyone on marshmallow has issues with the unified storage with sd card with TWRP?
[X Style (Pure) Original Android Development] Stryder5:
Yep, TWRP doesn't seem capable of decrypting the unifed storage yet. Guess we'll have to wait for an update.
[X Style (Pure) Original Android Development] timde9:
Im helping to test a few builds to try and get the encryption working OP is making good progress on the encryption issue.
[X Style (Pure) Original Android Development] Stryder5:
I can test it too if you still need people. I'm assuming this will help with Marshmallow compatibility?
[X Style (Pure) Original Android Development] timde9:
I'm not sure if mm compatibility is a real thing it was working perfectly fine in mm for me until I encrypted my storage to help with trsting. I'm on moto x pure and I was using the default build right from the op without issue
[X Style (Pure) Original Android Development] CJ-Wylde:
I hope when TWRP does get updated for MM that they update the default Theme.
[X Style (Pure) Original Android Development] Shishir Singhal:
am still not able to get into recovery the device boots up normally when i press open recovery in bootloader please help
[X Style (Pure) Original Android Development] Hashbang173:
Try doing a

fastboot boot pathtorecovery.img
[X Style (Pure) Original Android Development] Stryder5:
Type out the exact steps you're doing.
[X Style (Pure) Original Android Development] CraiaSoftware:
Help would be greatly appreciated!!

Looking for help...

The Moto X Force works with twrp-2.8.7.0-clark.img for the Moto X 2015 Pure, with one exception. The screen is upside down (but the touches are correct).

I am not experienced in compiling TWRP. Would someone be willing to recompile "twrp-2.8.7.0-clark" files with the screen flipped? I think it is just changing the two flags for:

I have only booted into it from adb. I have not flashed it. If someone is willing to send me the recompiled flipped screen, I will give it a try. Thanks!
[X Style (Pure) Original Android Development] Shishir Singhal:
flashing recovery through fastboot then from bootloader opening recovery. it just boots up the device after a vibration
[X Style (Pure) Original Android Development] Stryder5:
Type out the exact commands you run, as well as the results, in the order you perform them. And whether you have unlocked bootloader.
[X Style (Pure) Original Android Development] imakshar:
I tried these steps as advised and still same issue .. TWRP does not hold recovery boot. Each time i try to boot to recovery from Power & Volume Down, it gets stuck at broken Android Icon.

fastboot flash boot twrp-2.8.7.0-clark.img

After trying this commend, it gets stuck in Boot screen.

fastboot boot twrp-2.8.7.0-clark.img

No luck of TWRP on M unless if i m doing something wrong.
[X Style (Pure) Original Android Development] :
Two problems:

1) When i try a "factory reset" from configuration menu, the phone turn off and then boot into TWRP...

I only can make a factory reset from "wipe/Swipe to factory reset" option inside TWRP.

2)Also, when I'm inside TWRP and choose reboot (system, power off, recovery or bootloader) the phone freeze, and it must be switched off from the power button...

Excuse my sintax.

I don't speak english.
[X Style (Pure) Original Android Development] Stryder5:
You're typing the wrong command to flash recovery.

It should be:

fastboot flash [B]recovery[/B] twrp-2.8.7.0-clark.img

---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------

1. I don't understand what you're trying to accomplish. If you want to do a factory reset, you can do so from TWRP.

2. Choosing reboot system usually causes the phone to freeze for a brief moment for me. It then proceeds to actually rebooting the phone. How long are you waiting before manually powering off the phone?
[X Style (Pure) Original Android Development] MyDarkThrone:
Same here. TWRP runs perfect, only take a bit of time and then reboot or turn off

Enviado desde mi XT1575 mediante Tapatalk
[X Style (Pure) Original Android Development] Stryder5:
Did you unlock bootloader yet?

If the "fastboot boot recovery.img" doesn't get you into recovery, then you're doing something wrong. Either your bootloader isn't unlocked, or your recovery.img file is bad, or your fastboot isn't setup properly. Does "fastboot devices" show anything?
[X Style (Pure) Original Android Development] :
Factory reset from TWRP works well.

I tried to make it from "Settings/Backup & reset/ Factory data reset"

Thanks

You're right.

I've been a little impatient.

Thanks
[X Style (Pure) Original Android Development] imakshar:
Thanks a lot for quick replies ... My device is unlocked. Actually when I put 5.1 L, same TWRP works well but with update to M, same file and same device TWRP does not work. I tried searching around and a lot of other folks are also reporting similar issue with M.
[X Style (Pure) Original Android Development] Hashbang173:
So when you try to fastboot boot TWRP, does adb work?
[X Style (Pure) Original Android Development] imakshar:
When i run "fastboot boot twrp-2.8.7.0-clark.img" this is what I see ... i believe it does run .. no errors..

$ fastboot devices

NXXXXXXX	fastboot (I removed the number here but i do see device)

$ fastboot flash recovery twrp-2.8.7.0-clark.img

target reported max download size of 536870912 bytes

sending 'recovery' (34102 KB)...

OKAY [ 0.766s]

writing 'recovery'...

OKAY [ 0.688s]

finished. total time: 1.454s

$ fastboot boot twrp-2.8.7.0-clark.img

downloading 'boot.img'...

OKAY [ 0.764s]

booting...

OKAY [ 0.423s]

finished. total time: 1.187s

Once device boots up, i do see booting in recovery text on top of the device as normally I will see before TWRP splash screen is displayed, but than device will not go to TWRP and boot normally.

I apologize if i m creating any inconvenience here .. just trying to understand if i m doing anything wrong or if i have to wait for new version of TWRP, which I don't mind..
[X Style (Pure) Original Android Development] rsmiff:
How does that even work without the "flash"?

fastboot flash boot pathtoboot.img
[X Style (Pure) Original Android Development] Stryder5:
It works without "flash" because you are telling the phone to "boot" directly from the img file you provided. So "fastboot boot recovery.img" is issuing a "boot" command, rather than telling it to flash to the "boot" sector.

[MENTION=1732184]imakshar[/MENTION] Try doing just the "fastboot boot recovery.img" without flashing and see what happens. Also, check the MD5sum to verify you have a good download. I'm on Marshmellow and TWRP boots up fine.
[X Style (Pure) Original Android Development] Hashbang173:
Are you on the Marshmallow bootloader?
[X Style (Pure) Original Android Development] Stryder5:
Don't think so. I just flashed the ROM and radio from this thread: http://xdaforums.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684

EDIT: I just realized from your post that people having trouble are probably on the MM bootloader. I'm still on the LP bootloader which is probably why TWRP works for me.
[X Style (Pure) Original Android Development] dorkythegreat:
As far as I've tried with an OTA file that was posted for XT1575 this evening, it seems TWRP(2.8.7.0) flash via fastboot isn't working.

You have to manually flash 5.1.1 bootloader.img first in order to appropriately flash TWRP.
[X Style (Pure) Original Android Development] rsmiff:
Edited: Ignore my question. Someone has said TWRP is being worked on for the Marshmallow bootloader.
[X Style (Pure) Original Android Development] Hashbang173:
TWRP 2.8.7.1 is released with compatibility with M bootloader and a fix for the reboot hang
[X Style (Pure) Original Android Development] patt2k:
Man you are like a Moto god! if I am on 2.8.7.0 I just fastboot flash it and that's it?

cheers bro!

I flashed 2.8.7.1 via fastboot and it all was OK and then I rebooted into recovery to see if version changed but still same version shows.

I also flashed it in TWRP to flash TWRP.

Once MM boots (from the stock deodexed rooted) rom I will try to enter TWRP again.
[X Style (Pure) Original Android Development] Hashbang173:
yep
[X Style (Pure) Original Android Development] timeToy:
Installed the 2.8.7.1 version on an updated XT1575 with the MM bootloader and it is working fine, just the version number in TWRP still showing 2.8.7.0
[X Style (Pure) Original Android Development] jreyno10:
If I'm still on LP, can I flash the new TWRP via flashify? I'll be flashing the MM rom soon, just wanted to make sure flashing the img via flashify was ok.
[X Style (Pure) Original Android Development] patt2k:
What about supersu on MM I can just flash newest beta and it will work?
[X Style (Pure) Original Android Development] Hashbang173:
No, you need a patched boot.img for root as well as SuperSU
[X Style (Pure) Original Android Development] DaMadOne:
No. Must also flash a boot.img/kernel that has sepolicy patched for root. I patched the one for clark_retus MM and can be found HERE. flash it and then you can flash SuperSU 2.52 BETA. Failure to flash the modified boot with SuperSU will result in a boot loop/non booting phone.

Good work on fixing up TWRP hashbang! Has anyone happened to pull the MM bootloader.img? I already downgraded.
[X Style (Pure) Original Android Development] lafester:
No you still need a modified kernel (boot.img).

Ha... three ppl beat me to it.
[X Style (Pure) Original Android Development] patt2k:
Thank you :) I will let you know how it goes :D about to flash odexed rom.

[MENTION=2614896]DaMadOne[/MENTION] works great you are awesome!
[X Style (Pure) Original Android Development] lilcdroid:
Now that this is updated for MM does anyone have just the MM bootloader.img since I downloaded to 5.1.1 boot loader to get twrp and now would like to upgrade to full MM

Sent from the X-Treme
[X Style (Pure) Original Android Development] Hashbang173:
I think the OTA updated individual parts of the bootloader like tz, sbl1, etc.

So you might be able to flash all of those in TWRP with a modified zip, or you could wait until a full image comes out with the entire bootloader.

Waiting would be the safest thing to do, since there doesn't seem to be any apparent advantage so far to the M bootloader.
[X Style (Pure) Original Android Development] lilcdroid:
Thanks wasn't sure if a zip had been made yet. Just trying to satisfy my OCD. Kudoos for all you've done for the community. Much appreciated.

Sent from the X-Treme
[X Style (Pure) Original Android Development] alershka:
I have noticed the same thing. I've reflashed it multiple times (both from TWRP itself and using fastboot flash) so either it is not "taking" or it is mislabelled. I'm still on the 5.1.1 bootloader so I can't tell.
[X Style (Pure) Original Android Development] Hashbang173:
do a

cat /proc/version

in adb shell

if it says november 3rd, you are on the new TWRP
[X Style (Pure) Original Android Development] juancaperez2000:
im on MM rom update, but with LP bootloader in order to get root, is fine if I fastboot the new TWRP or do I need to do something else, thanks in advance.

EDIT: just flashed with flashify and works, even still showing old TWRP but the adb shell shows november 3rd.
[X Style (Pure) Original Android Development] DaMadOne:
The new TWRP works fine with the LP bootloader. Hashbang also fixed the hang on reboot which is nice.

I'm debating on going through the process of restoring to 5.1.1 and redoing the OTA in order to get the MM bootloader back. If someone could provide instructions on how to pull it I would definitely do it so i could provide it for those that already downgraded back to LP bootloader. It's not quite like pulling other img's since it's actually multiple parts.

EDIT* I'm back to having the MM bootloader if someone wants to tell me how to pull it I will.
[X Style (Pure) Original Android Development] lafester:
http://newandroidbook.com/tools/imgtool.html ?
[X Style (Pure) Original Android Development] DaMadOne:
That won't even extract the 5.1.1 bootloader.img so I'm going to say no. It looks like it can only create boot.img's as well.

Honestly with something this important(can and will brick a device if done wrong) it's probably best left to the someone who is positive they know what they are doing.

EDIT* Found the factory 6.0 restore image for RETASIA (XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip) over HERE and it shares the same A0.48 bootloader we now have with RETUS MM. Should be able to just grab the bootloader.bin out of it so that those that downgraded the bootloader for TWRP/root before Hashbang fixed twrp can just flash it. We know it works because A) it's the same version and B) everyone who used/tried the first MM OTA leak was using it anyways.
[X Style (Pure) Original Android Development] smarcisin:
I've flashed the newest TWRP every possible way... In TWRP itself, via fastboot, flashify, and still doesn't appear it's working. When I check cat /proc/version it doesn't say November 3rd
[X Style (Pure) Original Android Development] DaMadOne:
paste what you are getting from it.
[X Style (Pure) Original Android Development] smarcisin:
u0_a117@clark:/ $ cat /proc/version

Linux version 3.10.49-perf-ge36128e (hudsoncm@ilclbld84) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jul 30 13:34:41 CDT 2015

u0_a117@clark:/ $
[X Style (Pure) Original Android Development] DaMadOne:
are you still on 5.1.1? because that's what it looks like.

EDIT* ohh.. I see "u0_a117@clark:/ $" are you doing cat /proc/version booted into the ROM? you need to do it while booted into twrp.
[X Style (Pure) Original Android Development] ursubpar:
Is decryption supported now?
[X Style (Pure) Original Android Development] smarcisin:
Yeah i was using terminal emulator. Oops
[X Style (Pure) Original Android Development] DaMadOne:
:laugh:

Yea you need to be booted into twrp and either use the terminal command under advanced I think it is or use an adb shell from your PC to do the command.

---------- Post added at 10:34 PM ---------- Previous post was at 10:05 PM ----------

Nope, they are not exactly the same as you can see below in my md5sum comparison. Some are the same, others aren't. So even though we know it does technically work, it's probably best to just wait for a bootloader.bin for our device for those who downgraded it after the OTA. I doubt there is any real reason to NEED to be on the new bootloader...

~/Desktop/bootloader/ = CLARK_RETUS MM bootloader files from the xt1575 MM OTA

~/Desktop/bootloader/RETASIA/ = Files I extracted from the bootloader.img from the CLARK_RETASIA factory restore image (XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip)

~/Desktop/bootloader/RETASIA_OTA = Files from the RETASIA OTA.. as you can see they match the ones I pulled from the RETASIA factory image bootloader.bin so I did that correctly ;)

aea1ea6e5d81a657dfb437e8811029ad ~/Desktop/bootloader/rpm.mbn
93c7e76d20acca8160c5e69e4df85823 ~/Desktop/bootloader/RETASIA/rpm.mbn
93c7e76d20acca8160c5e69e4df85823 ~/Desktop/bootloader/RETASIA_OTA/rpm.mbn

c0e8ebe3205313a7a4cdc534c59dd632 ~/Desktop/bootloader/tz.mbn
9bc6614741f3fce7aded1ffdd7d760d1 ~/Desktop/bootloader/RETASIA/tz.mbn
9bc6614741f3fce7aded1ffdd7d760d1 ~/Desktop/bootloader/RETASIA_OTA/tz.mbn

d3bdd030a8e9c61d361c16e24eb24dd1 ~/Desktop/bootloader/sbl1.mbn
d3bdd030a8e9c61d361c16e24eb24dd1 ~/Desktop/bootloader/RETASIA/sbl1.mbn
d3bdd030a8e9c61d361c16e24eb24dd1 ~/Desktop/bootloader/RETASIA_OTA/sbl1.mbn

b598e83aa448a0285754689f0912925e ~/Desktop/bootloader/hyp.mbn
b038d1c51a7698972d706c3bd3e95861 ~/Desktop/bootloader/RETASIA/hyp.mbn
b038d1c51a7698972d706c3bd3e95861 ~/Desktop/bootloader/RETASIA_OTA/hyp.mbn

804813dad74917d8e6d9461c1a530f03 ~/Desktop/bootloader/emmc_appsboot.mbn
804813dad74917d8e6d9461c1a530f03 ~/Desktop/bootloader/RETASIA/emmc_appsboot.mbn
804813dad74917d8e6d9461c1a530f03 ~/Desktop/bootloader/RETASIA_OTA/emmc_appsboot.mbn

b2bc237960f171c2f7bdadd25f6eb43c ~/Desktop/bootloader/pmic.mbn
b2bc237960f171c2f7bdadd25f6eb43c ~/Desktop/bootloader/RETASIA/pmic.mbn
b2bc237960f171c2f7bdadd25f6eb43c ~/Desktop/bootloader/RETASIA_OTA/pmic.mbn

d280eb2eca0ff1f45685772c539c1703 ~/Desktop/bootloader/sdi.mbn
0d66bd82692c125b9611d7b445d18080 ~/Desktop/bootloader/RETASIA/sdi.mbn
0d66bd82692c125b9611d7b445d18080 ~/Desktop/bootloader/RETASIA_OTA/sdi.mbn
[X Style (Pure) Original Android Development] swieder711:
Was on TWRP 2.8.7.0 running stock rooted 5.1.1.

Installed TWRP 2.8.7.1 via ADB from my PC. Install went fine. Went from Bootloader directly to TWRP. Version showed 2.8.7.0

ran 'cat /proc/version' which reported

SMP PREEMPT Tue Nov 3 05:01:11 CST 2015 which looks good based on what I read here.

#thanks.

Now I have a MM compatible version of TWRP.

Waiting for TruePureX MM to update my ROM.

EDIT: Tried to Update SuperSU to 2.52. Beta via TWRP but it did not take. Any suggestions?
[X Style (Pure) Original Android Development] imakshar:
Thanks [MENTION=4630246]Hashbang173[/MENTION] for the new TWRP, now i have my X Pure with Android M + TWRP 2.8.7.1 and Xposed for M .. waiting for device to finish the initial Setup ..

-Flashed MM

-Flashed TWRP 2.8.7.1 via Fastboot

-Boot in Recovery with Power + Vol Down

-Install Boot_root_mm_clark_retus.zip using TWRP (Thanks to post #316)

-Go back in TRWP Home Screen without rebooting and install BETA-SuperSU-v2.52.zip

-Reboot in Recovery TWRP

-Install Xposed and Fonts

-Reboot System
[X Style (Pure) Original Android Development] Stryder5:
For those on the new MM compatible version, is TWRP now able to read the SD card if you used adoptable storage?
[X Style (Pure) Original Android Development] gulshanstrider:
[MENTION=2614896]DaMadOne[/MENTION] could you please provide me the link to download the factory image or Asia Retail Marshmallow 6.0 which you mentioned couple of posts earlier. I went to that page but everything is in Chinese/Japanese :D

And it is also asking me to upgrade membership or something.

Could you please provide me the download link.

It will be a great help.

Thanks
[X Style (Pure) Original Android Development] MobileThrowAwayAcc:
It appears to be working for me, I can view the storage at least, haven't tried saving a backup to it yet