yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Original Android Development] ximfinity:
It's not working for me.

I'm trying the 2.8.7.1 on MM and twrp can only see 18gb of my 32gb internal, and the SD card is listed as 0mb and cant mount, any ideas?

However my twrp header still says v2.8.7.0 (I see that is a typo for now)

I also tried the SuperSu Beta 2.52 and it instantly restarts twrp before flashing.
[X Style (Pure) Original Android Development] DaMadOne:
I didn't download it from that website(don't read the language haha), I just took the file name and then googled it and I found it on a yandex drive. I'll look through my browser history when I get home and then send you an exact link.
[X Style (Pure) Original Android Development] Forrice:
Okay so I was successful with the 2.8.7.1 install of TWRP but I was an idiot on reboot when TWRP asked about SU install I said yes. I was then stuck in a boot freeze, (just perpetually stuck on the initail "M" logo. I could still power off and then get into recovery so from post #316 I was able to flash all necessary zips for SuperSU 2.52 BETA.

Perhaps the OP can be updated with some critical info relating to 2.8.7.1? I'm sure you're busy Hashbang so hopefully you'll have time soon.

And thanks so much for the quick update!!!
[X Style (Pure) Original Android Development] onetraakmind:
Decryption still isn't working for me on 2.8.7.1.
[X Style (Pure) Original Android Development] sbcrumb:
can anyone tell my why in the OS I can't access the TWRP folder on the internal storage? I get access denied. I can see and access it in TWRP. Just not through the OS using FX file manager.
[X Style (Pure) Original Android Development] gulshanstrider:
Thanks it will be a great help.

I tried to Google the filename but no luck finding the yandex drive link .

Thanks
[X Style (Pure) Original Android Development] DJTeeJay:
Where is the DL for TWRP 2.8.7.1? Its not coming up in the TWRP App, just 2.8.7.0....
[X Style (Pure) Original Android Development] Forrice:
https://dl.twrp.me/clark/
[X Style (Pure) Original Android Development] lAndroXl:
Guys i need some help please... I dont get the latest TWRP installed on my Moto X Style.

I allready tried installing it with flashify, via fastboot and TWRP Manager but i wont work.

Is there any thing i have missed?

Drivers are intalled correctly and working properly.
[X Style (Pure) Original Android Development] gulshanstrider:
Are you on Marshmallow?

If yes then what version are you flashing?

Please flash TWRP 2.8.7.1 img file if you are on marshmallow.
[X Style (Pure) Original Android Development] lAndroXl:
I was on Lollipop CM12.1, now im on Marshmallow but it still wont work. I dont know what im doing wrong :|
[X Style (Pure) Original Android Development] gulshanstrider:
What version are you flashing?

Please go here and download 2.8.7.1 version.

Remember this version is compatible with Marshmallow but still in testing . So do everything on your own risk
[X Style (Pure) Original Android Development] lAndroXl:
As i said in the first post, i tried to flash the lastest version, so i mean 2.8.7.1.
[X Style (Pure) Original Android Development] JohnMcW:
Why do you think it didn't flash,

the 2.8.7.1 version will still say 2.8.7.0, but if you check the date as described in previous posts,

you should see that it says 12/03
[X Style (Pure) Original Android Development] lAndroXl:
that could be the reason yea, but why doesnt it show 2.8.7.1?

I think im not the only one asking.
[X Style (Pure) Original Android Development] Stryder5:
Because whoever modified it didn't change the text of the version number.
[X Style (Pure) Original Android Development] Forrice:
2.8.7.1 was released 2 days ago within 12 hours of the marshmallow soak test stating. His main concern was getting it functional for the marshmallow bootloader and so likely the version number change got missed. But it is correct, 2.8.7.0 won't work at all with marshmallow bootloader so if you are on the marshmallow bootloader and you can get in to twrp then you've got the correct version.
[X Style (Pure) Original Android Development] praetorzero:
If I decide to go back to AICP or CM, do I have to downgrade to 2.8.7.0 or can I keep .1?
[X Style (Pure) Original Android Development] Forrice:
Unless you also downgrade the bootloader also the answer is no. Whether or not those roms can be installed with the marshmallow bootloader is something that I don't know about.
[X Style (Pure) Original Android Development] jmileti:
If you took ota then I think not. Custom roms are running lp bootloader to make downgrading easier. At least that's my understanding.
[X Style (Pure) Original Android Development] AnimusVoxx:
Yeah I just can't get this new recovery to flash. Ive used flashify and it just hasn't worked., can anyone explain why it's not working?
[X Style (Pure) Original Android Development] Stryder5:
If the version number didn't change, it's because the dev didn't change it. If you got an error, tell us what it was. Vague descriptors such as "not working" doesn't provide much information.
[X Style (Pure) Original Android Development] AnimusVoxx:
I download the recovery image file, I flashed it. It reboots into recovery, yet it still says it's the same version. So yes..its either not changing the build number or its not working at all.
[X Style (Pure) Original Android Development] playenball:
2.8.7.1 is a new version that works with the MM bootloader. The developer just forgot to update the version number before he built it.
[X Style (Pure) Original Android Development] Forrice:
if you downloaded 2.8.7.1 file and you flashed it and you can get into recovery then you were successful. It will still say 2.8.7.0 because the developer forgot to change the text in the code that shows the version number.

If you flashed a version that wasn't compatible with your bootloader then likely when you chose recovery from the bootloader it would just load a black screen and then eventually reboot. Which is exactly what would happen if you flashed 2.8.7.0 after having taken the official marshmallow ota.

But if you did take the ota and you can now get in to recovery then you're fine. Just don't install superuser with twrp, he doesn't have the correct version for marshmallow embedded yet.
[X Style (Pure) Original Android Development] k3mik4l:
Same here flashify says it flashed it but it doesn't work .. Wierd, I guess I'll fastboot it unless there is a zip to flash?
[X Style (Pure) Original Android Development] Forrice:
Yeah you need to flash the .img using fastboot.

You can find it at https://dl.twrp.me/clark/
[X Style (Pure) Original Android Development] Stryder5:
The version number doesn't change when you flash it. As long as you flashed the correct img file, it updated properly.
[X Style (Pure) Original Android Development] smohanv:
Flashed 2.8.7.1 but when booting to recovery after flashing this recovery, i am still seeing version reference as 2.8.7.0.

I have flashed it on Moto X 1572 (Style)
[X Style (Pure) Original Android Development] Forrice:
This is as expected currently.
[X Style (Pure) Original Android Development] jyabor91:
I formated my sd card to the internal to get more memory for apps. Since I did that, my recovery doesn't allow me to open folders to flash things. This normal or has this happened to anyone else?
[X Style (Pure) Original Android Development] Stryder5:
Currently a known issue with MM and TWRP.
[X Style (Pure) Original Android Development] jyabor91:
Thanks!!! Is there currently a known workaround for this to flash things ?
[X Style (Pure) Original Android Development] Forrice:
I dumped the zips in the trwp folder while booted in recovery and connected to my computer. So in Windows just drag and drop to the twrp folder and Mac Android file transfer should come up on os x.

That's how I flashed the correct super SU apk and binary.
[X Style (Pure) Original Android Development] EVR_PR:
Cannot boot into TWRP on MM

My apologies for posting this here as well as in Heisenberg's thread but since I used his tutorial and the file provided in this OP, I thought that one of the two would be the correct venue for my issue. I read this thread and someone had a similar issue but the adb/fastboot commands provided didn't help..

I decided to unlock the bootloader and flash TWRP 2.8.7.1 after sideloading the official Android 6.0 OTA for the XT1575.

I was able to flash TWRP successfully. After flashing, I used the volume buttons to choose Recovery in the Bootloader menu and hit the power button which allowed me to boot into TWRP.

However, because I was also planning on using the systemless root method, and Chainfire recommends to keep TWRP as "read only" before flashing his BETA_SuperSU_v2.62-3.zip, when I tried to boot back in to recovery mode to flash SuperSU, the phone boots into the stock recovery. I tried manually and using the adb/fastboot commmands mentioned on previous posts here and it does not boot into TWRP.

Using FX Explorer, I can see a TWRP folder in my internal storage that I do not have access to.

Any suggestions on what I should do from here? I would greatly appreciate your input. Thanks in advance.
[X Style (Pure) Original Android Development] ffejy462:
Flash twrp via fastboot per op instructions.

Boot into recovery.

Reboot to recovery from recovery per op instructions.

Carry on with supersu installation.

If you boot system before rebooting back into recovery, the os will flash stock recovery. Rebooting to recovery from recovery patches that.

From TWRP:

https://twrp.me/devices/motorolamotox2015pure.html

"Note many devices will replace your custom recovery automatically during first boot. To prevent this, useGoogle*to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."

mxpe 6.0
[X Style (Pure) Original Android Development] EVR_PR:
Thank you for your reply but unfortunately, even after rebooting to recovery from recovery, the stock recovery is wrting over TWRP because I originally chose "read-only mode" (as per Chainfire's recommendation for his later SuperSU beta). I can only see TWRP if I keep flashing it with the fastboot command.

How can I revert to read/write mode in TWRP? Also, if I do install TWRP in read/write mode (which it says that will modify the /system partition), how can I use the systemless root method if TWRP will modify the /system partition in read/write mode?

Any help on this would be greatly appreciated.
[X Style (Pure) Original Android Development] ffejy462:
Assuming that you're bootloader was successfully unlocked and you followed the flash recovery instructions precisely in that same op, I'm not sure.

Just to be thorough, you don't happen to be using a custom theme or splash screen with twrp? If so they periodically need to be updated as twrp updates or it's really easy to inadvertantly use a wrong theme.

mxpe 6.0
[X Style (Pure) Original Android Development] EVR_PR:
No custom theme or splash screen.

As I said, I successfully unlocked the bootloader and flashed TWRP. But, because Chainfire recommends to keep TWRP as "read-only" for his systemless root method, no matter how many times I reboot recovery from recovery, as soon as I boot into system, the stock recovery overwrites TWRP. And, to make it even more complicated, I can't seem to find a way to revert the "read-only" status of TWRP because that option is gone no matter how many times I reflash TWRP.
[X Style (Pure) Original Android Development] DroidJay123:
Looking for instructions for booting into Stock Recovery on this device. I can get into the main but must not have the correct sequence of buttons figured out to go farther. Looking to at least do a nandroid backup before attempting to Flash 6.0

Thanks all!
[X Style (Pure) Original Android Development] Forrice:
stock recovery on this device results in the Android with the exclamation mark. I'm guessing they intended this mode to use adb and/or fastboot commands only for recovery. There is no stock gui for recovery that I'm aware of.
[X Style (Pure) Original Android Development] jaben2:
making backup now to external sd card.

Thanks,
[X Style (Pure) Original Android Development] markwebb:
Isn't it great to have the external sd card to store these backups? :)
[X Style (Pure) Original Android Development] zombicidal maniac:
I flashed the version [MENTION=4630246]Hashbang173[/MENTION] said and it seems to be working. :good:
[X Style (Pure) Original Android Development] Hashbang173:
Yes, in addition you also have the option on storing/backing up stuff via USB OTG
[X Style (Pure) Original Android Development] patt2k:
Can you try gravitybox?
[X Style (Pure) Original Android Development] jmileti:
sorry for noob question. if i put recovery on root of internal memory what is fastboot command. tried a few different ways i know i am doing something silly. thanks.
[X Style (Pure) Original Android Development] zombicidal maniac:
It works! :highfive:
[X Style (Pure) Original Android Development] Bootup:
You don't put the recovery on the phone. For ease of use, just copy it to the directory with fastboot on your computer, name it something easy (say motox.img) and run a command window in that directory: fastboot flash recovery motox.img
[X Style (Pure) Original Android Development] juanacevedo:
TWRP works, root works, Xposed works (use 64bit version)
[X Style (Pure) Original Android Development] spotmark:
Well looky here. Hello, Xposed.
[X Style (Pure) Original Android Development] jrbxx7:
Awesome work. Thanks for the quick development on this. Can't wait for mine to get here.

http://kryon.smugmug.com/Purenexus/i-bRKJdsk/0/O/OPERATIONPNbanner5x1.png
[X Style (Pure) Original Android Development] patt2k:
Now someone please try Viper4android I heard you have to use selinux enforcer and set it to off. This is what I almost care the most :)
[X Style (Pure) Original Android Development] dragonfly1113:
Anyone able to bypass the wireless tethering check yet? Very exciting news that we have recovery and root.
[X Style (Pure) Original Android Development] jaben2:
I didn't need root to bypass. It is already good to go
[X Style (Pure) Original Android Development] :
Freaking awesome great work guys! I did not expect this to be here today... I am just mad I just now checked the forums lol. Downloading tools now!
[X Style (Pure) Original Android Development] jmileti:
Viper working. Install apk and selinux mode changer to permissive. I downloaded Apollo apk to test.
[X Style (Pure) Original Android Development] dragonfly1113:
So there's no prompt to pay the extra amount from your provider to allow tethering ? Like their usually is on Verizon phones?
[X Style (Pure) Original Android Development] jaben2:
I'm on Verizon with UDP and activates and works as it should without root
[X Style (Pure) Original Android Development] LeonTLR:
Awesome work, thank you so much
[X Style (Pure) Original Android Development] vnphantom:
This paved the way to so much more on our phones... Thanks so much for the dev team! Now...to get rid of that pesky Bootloader Unlocked warning screen...;)
[X Style (Pure) Original Android Development] joshw0000:
Could someone create a flashable MM bootloader image? After installing MM I flashed the 5.1.1 bootloader so I could continue to use 2.8.7.0 (before Hashbang released the new version). I've dug through the OTA and don't see a bootloader image to flash back to MM bootloader. Am I missing something? Does something need to be packaged or pulled from a stock phone? Or is the only solution to revert back to 5.1.1 and flash stock MM again?

Thanks in advance for any help!
[X Style (Pure) Original Android Development] EVR_PR:
Power + Volume Down while phone is off gets you to the bootloader. Select recovery with the volume buttons and press the power button. On stock, you will see Andy lying in its back with an exclamation mark and the words: "No command.":

To get into stock recovery from there press the power button and leave it pressed while you press the volume up button for 3 seconds. After the 3 seconds, release volume up and then the power button. That will boot you into stock recovery.
[X Style (Pure) Original Android Development] Forrice:
Nice I learned something new.
[X Style (Pure) Original Android Development] DroidJay123:
Is there a way to install TWRP without being rooted?
[X Style (Pure) Original Android Development] Stryder5:
Yes, you don't need to root to install TWRP. However, you do need to unlock bootloader.
[X Style (Pure) Original Android Development] Dahenjo:
Can OP or anyone confirm installing TWRP on stock 6.0 without this problem?

From my post in this thread started by someone with the same issue (slightly edited):

I keep running into a problem after the MM OTA update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animated part should start. Booted/rebooted normally a few times after the MM update, but as soon as I flash recovery it stops being able to. Could reboot ok back into TWRP or the bootloader, just not system.

Tried several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but made no difference. Only by already having TWRP on 5.1.1 am I able to install a custom 6.0 ROM and have functional MM + custom recovery. Haven't seen a really clear statement yet that someone has set up TWRP on fully stock MM with no problem, although it seems implied in some posts. Just would like to make sure, then if there is an issue OP will know about it.
[X Style (Pure) Original Android Development] vx2ko:
It almost sounds like an issue with the boot.img or partitions. Did you restore to stock yet?
[X Style (Pure) Original Android Development] Dahenjo:
Oh yeah, fine again now back on your TruPureX ... this was a couple days ago just trying to take the OTA after running the restore to stock tool, which worked great until adding TWRP then had this issue and gave up. In your work have you flashed TWRP on fully stock 6.0 and been able to boot system ok?
[X Style (Pure) Original Android Development] Aftab_khatri:
i was on 5.1.1 and Flashed 2.8.7.1 but no Version changed later i flashed MM 6.0 TruepureX rom and recovery is working without any problem In MM.

So , its Updated But Just OP forgot to change Version, Flash it With 6.0 Good to go no problems with me smooth :)
[X Style (Pure) Original Android Development] DroidJay123:
So after taking the 6.0 OTA update, this sequence of keys won't get me into the Stock recovery. It gets as far as Andy lying on his back with the words "No command" but the sequence of keys at that point don't bring up the recovery menu (Power + Vol Up for 3 secs, then release Vol then power). Is there a different sequence of keys since the 6.0 update? There has to always be a way to get into Recovery.

Thanks!!
[X Style (Pure) Original Android Development] EVR_PR:
That's the only way I know of. It is a bit tricky, though.

Once you count to three immediately release volume up followed immediately by power, otherwise you will reboot in system mode. So, remember:

Press power first, immediately hold volume up and count to 3, let volume up go followed immediately by the power button.
[X Style (Pure) Original Android Development] sm3691:
hello

i have a problem

i already installed 2.8.7.0

now when i flash new one the version dont change

i try erase recovery then flash 2.8.7.1 but nothing changed
[X Style (Pure) Original Android Development] thorpj:
If you have installed TWRP 2.7.1, and you have then got into TWRP successfully, then you are using TWRP 2.7.1 the dev forgot to change the version number that shows in the title.
[X Style (Pure) Original Android Development] thebobmannh:
It's amazing to me that

a) people do these things iwhtout bothering to read a thing beforehand

b) all the work a dev puts into getting something working is all but forgotten if they forget to change a version string.
[X Style (Pure) Original Android Development] patt2k:
It will display 2.8.7.0.. Either way even if you flashed newer one.
[X Style (Pure) Original Android Development] ban.codrut:
I have an issue with TWRP (2.8.7.1 at the moment) and the backups. I can access the TWRP folder from the recovery itself but from android OS it says it can't access "/sdcard/TWRP". Even connecting it to PC doesn't allow me to get in and copy my backups, unless I connect meanwhile I'm in recovery and mount.

This issue was present in v2.8.7.0 as well. Anyone knows what's going on ? Why the contents of that folder isn't visible to Android ? Some permissions issues maybe .. even so, that folder is created by TWRP itself and it shouldn't behave like this

MotoX XT1752EU TruPureXv2.1
[X Style (Pure) Original Android Development] EVR_PR:
Have you tried a different file explorer? Are you rooted? If you are and used the systemless root method, ES File Explorer does not recognize root and won't give you access to the folder.

Try a different file explorer.
[X Style (Pure) Original Android Development] ban.codrut:
Es file explore doesn't recognise root? What are you saying? It did for me, I can access any of the folders from root / and it does respond to su when I try to mount system R/W.. I will try another file explore tomorrow just to cur that out too

MotoX XT1752EU TruPureXv2.1
[X Style (Pure) Original Android Development] EVR_PR:
I didn't read that you were on TruPureX. I had the same problem as you after I installed systemless root v2.6.2 and changing to FX File Explorer and logging is as Root allowed me to log into the TWRP folder.
[X Style (Pure) Original Android Development] lafester:
Any update on this? Would be nice to have a working recovery.

-edit- I see that some progress has been made. OP needs to be updated that this does not work with combined storage.
[X Style (Pure) Original Android Development] BooBzi:
Hello. I want to know is it recovery bug or not.

After upgrading to stock Marshmallow on XT1572 "Style", I unlocked bootloader, and installed latest TWRP on my device (2.8.7.1), but after restarting, my device is stuck on motorola logo and cant finish to boot up. Is there solution to use TWRP with latest stock Marshmallow update?

P.S. There isnt any EUROPEAN roms for this device, so I used restore to stock and installed marshmallow official way!
[X Style (Pure) Original Android Development] ban.codrut:
Have you clicked YES when twrp asked you to install superSU ? Or on the 'modify /system' warning at the beginning, right after the splash screen ..?

Inviato dal mio XT1572 utilizzando Tapatalk
[X Style (Pure) Original Android Development] BooBzi:
Yea, I agreed that TWRP can modifie my partitions. But I didnt install SuperSu!
[X Style (Pure) Original Android Development] ban.codrut:
I can't tell you for sure as I too am trying to figure it out MM stock with root TWPR and Xposed. I have motives to think that system modifications done by twrp are harmful as TWRP itself doesn't support marshmallow yet Clark's marshmallow bootloader. The custom ROMs based on Mm ota (TruPureX) keeps the old bootloader to solve this problem.

SuperSU works with no problem in systemless mode as for version 2.62.3 if you want to try. Version 2.64 breaks everything apart.

I have twrp and I have selected not to modify my system and I can confirm it works. Sometimes it goes away and you have to flash it back but it works.

To repair the done damage you have to flash all the system.IMG back and also do a cache wipe.

Inviato dal mio XT1572 utilizzando Tapatalk
[X Style (Pure) Original Android Development] BooBzi:
Will try to get stock EU MM again and flash TWRP, but now will change settings to not modify my partitions. So flasking SuperSu from TWRP will work?
[X Style (Pure) Original Android Development] ban.codrut:
Yes. I can only confirm version 2.62-3 , the other one 2.64 failed for me as there is some experimental automation going on. PS this is systemless root but you don't need to patch boot.IMG anymore as it does it for you in this version (and some versions before).

See post #3 here: http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Inviato dal mio XT1572 utilizzando Tapatalk