yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Original Android Development] BooBzi:
Yea I know about that I dont need to patch boot image anymore. But I dont know if after flashing TWRP, my device will boot up.. = / need to test it again.
[X Style (Pure) Original Android Development] Naddict:
Just FYI, 2.64 works fine for me with stock MM (moto x pure 1575) ad stock odexed rom...I say give it a rip!
[X Style (Pure) Original Android Development] ban.codrut:
Hmm you are tempting me a lot here. I just hope I won't end up factory resetting again, it's a pain in the a** after a while. Thanks for the feedback.

Have you flashed other stuff before su 2.64 ? Like Xposed, older version of su(which ver?, 2.5x?)..

Sorry for asking lots of questions but something broke my setup and I want to figure it out what it was

Inviato dal mio XT1572 utilizzando Tapatalk
[X Style (Pure) Original Android Development] BooBzi:
Hmm... I have problem, now I am using stock MM, but succesfully flashed latest twrp.

From fastboot menu choosing recovery it boots me up to "Andy lying in its back with an exclamation mark and the words: "No command."

So I tried your: "After the 3 seconds, release volume up and then the power button. That will boot you into stock recovery", but that didnt work for me. Device just turn on normally.

I got could boot to TWRP recovery from fastboot PC "fastboot boot recovery.img", butis there possible to boot to TWRP from moto fastboot menu? Thanks!
[X Style (Pure) Original Android Development] EVR_PR:
Well, this could be a couple of things. For one, it could be that you opted to keep TWRP read only which means that the stock recovery will overwrite it after every reboot, or you chose to let TWRP modify the /system partition but didn't reboot into recovery from recovery after the first flash to make sure it sticks. If it's the latter, you need to reflash TWRP. Using fastboot boot recovery will only mount it but not let it replace stock recovery. Hope this helps.
[X Style (Pure) Original Android Development] Naddict:
I have been flashing everything, been with Lollipop, then stock rooted, tried both systemless and "regular" su. I am very experienced with most methods and enjoy the challenge. I see so many posts in here about issues and problems with both SU and TWRP, of which I too have had but eventually overcome. The best advise I can offer to you and anyone else is to read, all of the posts, in all of the threads. Odds are the answers are there. And I, amongst the many other talented members here, are around to help when and if they can. :cool:

Oh, and yes, I have exposed, with several fully functioning modules, and layers too!
[X Style (Pure) Original Android Development] BooBzi:
Thanks for advice! I did flash TWRP again via fastboot. After that I reboot to recovery (TWRP), and from TWRP I did reboot to recovery again, it booted to TWRP.

After booting up system, and turning device off I successfully booted to TWRP from fastboot menu.

Thanks. It helped!
[X Style (Pure) Original Android Development] ban.codrut:
That was a heck of a motivational speech :) motivational enough to convince me to go back to flashing. [MENTION=4353001]Naddict[/MENTION] and [MENTION=1007992]everyone[/MENTION] I should recommend trying L Speed: http://xdaforums.com/showthread.php?t=3020138

Inviato dal mio XT1572 utilizzando Tapatalk
[X Style (Pure) Original Android Development] Naddict:
You mean this:confused: http://xdaforums.com/android/software-hacking/tweak-l-speed-v1-0-02-02-2015-t3020138.. :good::highfive:
[X Style (Pure) Original Android Development] ban.codrut:
Yup, right that one! I see you are already on it :)

Inviato dal mio XT1572 utilizzando Tapatalk
[X Style (Pure) Original Android Development] dlarge:
You should just touch volume up once. This will get you into stock recovery.
[X Style (Pure) Original Android Development] BooBzi:
Thanks, so hold power button and press volume up one, later release power button?
[X Style (Pure) Original Android Development] dlarge:
In my experience, if it's on his back, just push volume up once.
[X Style (Pure) Original Android Development] BooBzi:
interesting.... now cant test it.. I got that TWRP is showing. So thanx!
[X Style (Pure) Original Android Development] dlarge:
Are you on stock and unrooted? If so, I'm wondering if you're able to boot the phone.
[X Style (Pure) Original Android Development] BooBzi:
Yea, I am on stock MM, and TWRP working right now. Got root and xpsoed right now.
[X Style (Pure) Original Android Development] MyDarkThrone:
Yeah. Yesterday I revert to stock and install ota and after this phone freeze in boot.

Enviado desde mi XT1572 mediante Tapatalk
[X Style (Pure) Original Android Development] Dahenjo:
So, you can boot into MM system after flashing TWRP and rooting? If so, how did you overcome the problem we were having?

I experimented again a couple days ago, ran 5.1.1 system restore tool then normally took the MM OTA, and then flashed TWRP 2.8.7.1. One thing I didn't remember correctly from doing this before, was that I

CAN

reboot to system after flashing TWRP

IF

I didn't root yet, but as soon as I root (install Beta-SuperSU-2.5.2 in TWRP - just used the old method before systemless root because it always worked perfectly in 5.1.1) is when it can't boot to system (hangs at first splash screen & never does the big vibration after which the animated part should begin). So I gave up and restored my Trupure 2.2.1 backup and all is fine, just wish I could solve this problem. Thanks for any info.
[X Style (Pure) Original Android Development] BooBzi:
I had issues before, now I installed stock 6.0, without going to 5.1.1 and upgrading via OTA to 6.0.

I have explained all my steps in this thread:

http://xdaforums.com/showthread.php?t=3276792
[X Style (Pure) Original Android Development] cherrydha:
Thanks for great work.

When we can get encryption data partition mount working with TWRP, please?
[X Style (Pure) Original Android Development] Flapjack:
Hopefully someone can help me. I have been running the stock ROM since I originally got the phone, just after it came out. The only thing I've done is rooted the phone, unlocked the bootloader, installed TWRP, and blocked OTA updates.

Today, I decided to update to a debloated MM ROM. While the ROM was downloading, I went to flash the latest TWRP in preparation for installing the new ROM. After installing the latest TWRP, I can no longer get the phone to boot. I get the animated boot screen, they the plain Motorola log, then the screen goes black, while remaining backlit.

I can boot into recovery mode and the newest version of TWRP looks just fine, but if I try to reboot again, I get the same black screen.

I would like to reiterate, all I did was update TWRP. I never got the point where I copied the new ROM to the phone and flashed. I'm afraid to do anything else and potentially make it worse.

The worst part is, I deleted my last nandroid backup so I had room to do another, prior to flashing MM. That was right before I updated TWRP.

**EDIT**

I do have xposed installed, along with a few apps. I haven't updated any lately, though... and I rebooted the phone prior to updating TWRP, so there should not have been a lingering change needing a reboot.

**EDIT 2**

I realize I also wiped cache/dalvik after installing the new TWRP. I always wipe cache after flashing a zip. Could that have somehow done it?
[X Style (Pure) Original Android Development] spotmark:
Guys, I'm having trouble following the thread. I just bought my wife an MXP on Swappa. If it arrives with MM, can I just unlock and root it the normal way, or do I need to flash it back to LP first?
[X Style (Pure) Original Android Development] jason2678:
I unlocked and rooted on M. Make sure you get the 2.8.7.1 version that is patched for the M bootloader. There are a few steps you seem to have to do just right to get things to work right on M.

I used a systemless root. BETA-SuperSU-v2.62-20151210170034.zip worked for me.

Also, I only let TWRP mount system read only. This fairly short thread has some details on what worked for me and a few others to get rooted and get TWRP to stick on M.
[X Style (Pure) Original Android Development] spotmark:
Can the MXP be downgraded to LP? It sounds like it's better to go about the rooting process from there.
[X Style (Pure) Original Android Development] countryfolk07:
I rooted stock MM. It was no big deal. Fastboot flash TWRP 2.8.7.1 reboot into TWRP. reboot to system to be safe. Then reboot back to recovery. Flash superSU 2.52. It seems to work the best for traditional root. If you want systemless root, I can't help you much.
[X Style (Pure) Original Android Development] spotmark:
Thanks, not interested in systemless root, so I'll give it a shot when it arrives.
[X Style (Pure) Original Android Development] Hashbang173:
If you don't use the systemless supersu zip, you'll need to flash a modified boot.img with root capabilities due to Marshmallow.

The latest systemless supersu zip would patch your current boot.img automatically
[X Style (Pure) Original Android Development] Dahenjo:
Yes, just use the 5.1.1 restore to stock tool, I've used it several times on both LP & MM and it always worked perfectly. I wasn't able to get traditional root on stock MM using SuperSU 2.52, it always hung on the boot screen right after flashing it. It seems others have done it now, but I think you'd need to do what Hashbang173 says, although I didn't try that method. Definitely works with the restore tool, then install TWRP and just flash a rooted custom MM ROM.
[X Style (Pure) Original Android Development] countryfolk07:
I'm sorry, i forgot about the modified boot. I just flashed the new optimized kernel from vladmtk. You need to do that before flashing superSU. It's just been a while. Sorry.
[X Style (Pure) Original Android Development] rsmiff:
I tried flashing recovery and got this...

writing 'reovery'...

(bootloader) Permission denied

FAILED (remote failure)

After updating my SDK it flashed fine. Just FYI.
[X Style (Pure) Original Android Development] shojus:
So is the newest 2.8.7.1 still showing as 2.8.7.0 in TWRP? Cause I have flashed it a few times and it is sticking in MM but it does not show as the newest version... I'm sure it is but I just wanted to ask. Also, I flashed a stock & rooted TWRP MM backup and it still did not root MM? Was I supposed to let TWRP install SU for me like it asked for or?? I have everything up and running on MM but I had to do a few steps that are different from what others are doing so I was just curious. I read several pages of this thread so hopefully I'm not repeating what has been asked 2 trillion times already... :)

EDIT: I figured out that the TWRP I have is indeed the right one, just did not get updated with the version number.
[X Style (Pure) Original Android Development] timde9:
Has there been any progress on encryption recently?
[X Style (Pure) Original Android Development] Guti1977:
So I was a bad user and flashed the superSU 2.52 beta and got stock at the Motorola boot screen. What are my options? FYI I can still boot to TWRP as well as Fastboot.

I received my Moto X Pure today and I was able to update to 6.0 Marshmellow so I was in the process of flashing TWRP as well as rooting but now I am in trouble :( Thx

Edit: Forget it, got the return to stock batch file and it is working again now :D
[X Style (Pure) Original Android Development] adparty:
How did you determine you actually have the right twrp installed if it still shows 2.8.7.0?
[X Style (Pure) Original Android Development] shojus:
Well I read quite a few posts that actually mentioned that HashBang did not remember to update the version number before this version was released. So therefore it will show as the same , but if you are able to flash on MM than you def have the right version because the original had issues with MarshMallow. So hope that clears it up?
[X Style (Pure) Original Android Development] fdc77:
minor issue

[MENTION=4630246]Hashbang173[/MENTION]

special characters (<>=) can't be used with keyboard because keys disappear
[X Style (Pure) Original Android Development] Hashbang173:
I am aware of the issue. But the special characters keyboard works fine with the material TWRP custom theme.
[X Style (Pure) Original Android Development] Dahenjo:
A good way to tell is that in 2.8.7.0 there was a fairly long delay when rebooting, so if it's only a few seconds then you have 2.8.7.1.
[X Style (Pure) Original Android Development] Hitti2:
[MENTION=4630246]Hashbang173[/MENTION]

2.8.7.1 does it support decrypting an encrypted partition to backup?
[X Style (Pure) Original Android Development] Hashbang173:
I think I remember testing it and I think it worked
[X Style (Pure) Original Android Development] Hitti2:
Fantastic. I will give her a shot in 12-15 hours.
[X Style (Pure) Original Android Development] nmh5001:
Anyone use this to resize the system partition? I really don't like having 2 gigs of unusable space because Moto decided they needed a 4 gig system partition.
[X Style (Pure) Original Android Development] Hitti2:
Hashbang, could you take a min to read this?

http://xdaforums.com/moto-x-style/help/encryption-unlocked-rooted-t3299897/page2

im having a problem.
[X Style (Pure) Original Android Development] fbiryujin:
Can you provide a link for me to test it?
[X Style (Pure) Original Android Development] Hashbang173:
PM sent
[X Style (Pure) Original Android Development] Hitti2:
I've got concerns about if there is a chance of bricking the phone by installing an alpha test twrp.

How may I revert back to an older version?

Where are dl links for testing?

I just got this phone depending on the circumstance above I will help test.
[X Style (Pure) Original Android Development] playenball:
Hashbang173, I would be willing to test your test build for encryption.
[X Style (Pure) Original Android Development] fbiryujin:
Working with you via PMs, but I see someone in the thread had a similar concern to mine so I'll ask that question here: What are the risks that a failed decryption attempt will corrupt or damage the data on the data partition? Being encrypted we can't back it up after all.

Thanks and looking forward to getting this working :)
[X Style (Pure) Original Android Development] Hashbang173:
Anybody want to test adopted storage in TWRP? PM me if you want a test build
[X Style (Pure) Original Android Development] Hashbang173:
Well it looks like adopted storage is working fine in this test build, there have been reports that it works with encrypted devices as well.

So I will leave the test TWRP here:

https://www.androidfilehost.com/?fid=24391638059058134
[X Style (Pure) Original Android Development] Hitti2:
Installing this will overwrite previous version? Just making it clear my phone doesn't have two installed version. Note: I've never upgraded twrp before.
[X Style (Pure) Original Android Development] Hashbang173:
yes, it will overwrite the previous version
[X Style (Pure) Original Android Development] fbiryujin:
How long should it take to mount an encrypted phone if it's a 64GB model running stock ROM on 5.1.1? No external SD card installed.
[X Style (Pure) Original Android Development] Hitti2:
[MENTION=4630246]Hashbang173[/MENTION]

Ok, I upgraded it.

Enter password to decrypt, so I entered my password.

Now on the twrp cmd window screen. I have

Mount: Trying Decryption
Updating partition details
...done
[COLOR="Red"]unable to mount storage[/COLOR]
Full SELinux support is present.

Its just sitting and trying to decrypt.

Moto X Pure XT1575.
[X Style (Pure) Original Android Development] fbiryujin:
[MENTION=4630246]Hashbang173[/MENTION]

I'm having the same issue. I let it go for half an hour and neither the UI or /tmp/recovery.log showed signs of progress
[X Style (Pure) Original Android Development] Hashbang173:
can you give me the recovery.log?

adb shell cat /tmp/recovery.log
[X Style (Pure) Original Android Development] fbiryujin:
PMing you mine
[X Style (Pure) Original Android Development] Hitti2:
Yes I can give you that. Should I hard shutdown?
[X Style (Pure) Original Android Development] fbiryujin:
I've done that a few times during this testing. It's safe to do
[X Style (Pure) Original Android Development] Hitti2:
I am having a problem.

C:\SDK\android-sdk-windows\platform-tools>adb shell cat /tmp/recovery.log
error: no devices found

C:\SDK\android-sdk-windows\platform-tools>adb devices
List of devices attached

C:\SDK\android-sdk-windows\platform-tools>

Devices are blank, MXPE is in fastboot flash mode (secure).

Am I suppose to be in a different mode?
[X Style (Pure) Original Android Development] fbiryujin:
In order to access that file, the recovery has to be running. Start the recovery, attempt decryption, wait a few minutes until you are sure it's stuck, then run the adb command while it's still trying to decrypt.

Hope this helps!
[X Style (Pure) Original Android Development] Hitti2:
[MENTION=4630246]Hashbang173[/MENTION]

Code has been sent by pm.
[X Style (Pure) Original Android Development] Hashbang173:
What Android version are you on?
[X Style (Pure) Original Android Development] Hitti2:
Marshmallow 6.0
[X Style (Pure) Original Android Development] fbiryujin:
Stock ROM & Kernel

Android: 5.1.1

Kernel: 3.10.49-perf-ge36128e

hudsoncm@ilcbld84 #1

Thu Jul 30 13:34:41 CDT 2015

System version: 23.21.18.clark_retus.retus.en.US retus

Build number: LPH23.116-18
[X Style (Pure) Original Android Development] Hashbang173:
ok, new build with more debugging enabled

this time after it hangs at decrypting, can you give me the output of:

adb shell cat /tmp/recovery.log

adb shell dmesg

adb logcat

https://www.androidfilehost.com/?fid=24391638059058273
[X Style (Pure) Original Android Development] fbiryujin:
PM with dropbox link to logs is inbound
[X Style (Pure) Original Android Development] Hashbang173:
ok, compatibility with encrypted devices has been fixed in this test build

thanks to [MENTION=7168306]Hitti2[/MENTION] for confirming it works

https://www.androidfilehost.com/?fid=24391638059058761
[X Style (Pure) Original Android Development] fbiryujin:
lt's working for me too. Thanks so much!
[X Style (Pure) Original Android Development] Hitti2:
Agreed. Confirmed working. Thank you, Hashbang173.
[X Style (Pure) Original Android Development] playenball:
Running smoothly for me too.
[X Style (Pure) Original Android Development] Hitti2:
I've encountered an error

backing up with compression enabled and encryption enabled for the backup while encrypted.

createTarFork() Process ended with error 255

Any of you guys get the same?
[X Style (Pure) Original Android Development] playenball:
Haven't had that error. I made a compressed encrypted backup, on the latest version posted, about 4 hours ago with no issues. If you can reproduce get a log for [MENTION=4630246]Hashbang173[/MENTION]
[X Style (Pure) Original Android Development] Hitti2:
Ok. Must be something with my phone then. I'll wait for hashbang to toss logs to him. I made complete backup without encrypting the backup. It went without a problem.
[X Style (Pure) Original Android Development] lafester:
Recovery is working great with combined storage. Successfully backed up, flashed aicp (which retained combined storage) and restored my backup.

---------- Post added at 02:49 AM ---------- Previous post was at 02:49 AM ----------

Love the new layout and button settings.
[X Style (Pure) Original Android Development] psxmail:
Hi,

I have a Moto XT1572 EU 32 Gb in MM not unlocked yet.

Yesterday I downloaded the stock firmware XT1572_CLARK_RETEU-UK-FR_6.0_MPH24.49-18.

Next Week I will unlock it, and I have 2 questions :

1) I want to make a raw backup before flashing twrp. So if I do "fastboot boot twrp-2.8.7.1-clark.img" could I make a backup in the internal sdcard with the "system image" option ?

2)I want to install xposed, I don't need Android Pay, so I couldn't use systemless root, I plan to use BETA-SuperSU-v2.62-20151210170034 for a normal root, ohter version seem to failled in booting ?

Do I miss something ?
[X Style (Pure) Original Android Development] WelcomeToTheSkye:
Good news! I am running the latest test build with adopted storage and twrp works like a dream! it recognized to sdcard and everything. Was able to flash stuff and back up stuff with no issues!
[X Style (Pure) Original Android Development] lafester:
New recovery will not flash kernel zips. Works fine with images though.
[X Style (Pure) Original Android Development] Hitti2:
yea. And i cannot encrypt my backups, i get a 255 error.

Hope hashbang comes back.
[X Style (Pure) Original Android Development] fbiryujin:
Are you trying to encrypt them with TWRP itself or just store them on an encrypted partition? I generally rely on the media's encrypted (OS X Filevault/Android encryption/etc...) to protect my files so I never tried an encrypted TWRP backup.

On another note, has anyone tried a non-TWRP encrypted backup and restore when the internal data partition is encrypted? (Android 5.1.1 in particular if possible)

Thanks
[X Style (Pure) Original Android Development] Hitti2:
I've got my sim card locked. I wonder how twrp gets the date and time because test twrp thinks it is the 29th of jan. It doesnt file date of backup correcty.

See all of the jan 29th backups?

---------- Post added at 08:26 PM ---------- Previous post was at 08:24 PM ----------

This is a cluster.
[X Style (Pure) Original Android Development] WelcomeToTheSkye:
I had one that said 1970 ????
[X Style (Pure) Original Android Development] Hitti2:
Ok I booted down leaving the phone off for bout 2 min. Booted into recovery n backed up. It filed the name correctly this time.

Might wanna try this?

---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------

Trying to encrypt the backup onto an unlocked and not adopted sd storage.

For marshmallow yes i backed up the encrypted android os and restored just fine.

I confirmed this with hashbang which leads to

http://xdaforums.com/moto-x-style/o...h-recovery-t3200520/post65045746#post65045746
[X Style (Pure) Original Android Development] fbiryujin:
Awesome!
[X Style (Pure) Original Android Development] Hitti2:
[MENTION=4630246]Hashbang173[/MENTION]

Is there a reason I am getting this?
[X Style (Pure) Original Android Development] c3drik 67:
Hello everybody,

I have a question i have installed twrp 2.8.7.1 on my phone for root in systemless. I have twrp in read only, but when i would restore my backup i can't because twrp is in read only. How can i change this for restore my backup. Thanks a ton
[X Style (Pure) Original Android Development] fbiryujin:
I never picked "read only" but TWRP usually asks me that question every single time I go into it. You could try reflashing it to see if it forgets your choice to go read only.
[X Style (Pure) Original Android Development] Hitti2:
Hey. Check this out.

http://xdaforums.com/moto-x-style/development/kernel-frankenclark-t3289939/post65096209#post65096209
[X Style (Pure) Original Android Development] Hitti2:
Yup. Flashing kernels works. I am on tpxmm 2.4 with f kernel 0.5.2.
[X Style (Pure) Original Android Development] psxmail:
No advices about this ?
[X Style (Pure) Original Android Development] Digital Cha0s:
As far as advice goes I don't claim it to be good or bad...This is just what I have done, would do, see no reason why it wouldn't work that way. From my understanding of the question/experiences..... I feel this is a pretty good disclaimer on my part :p

Question 1-- I personally see no reason why this wouldn't work but I would recommend saving the three main Partitions :Boot, System, EFS:

Question 2-- as far as xposed I have use SuperSU 2.67 systemless and all seems to work out fine

you can get the flashable file here then you can always extract the APK from this file and do the non systemless thing but its not recommended
[X Style (Pure) Original Android Development] psxmail:
Ok I will try for the backup ;)

I was thinking we can't use Xposed on a systemeless root ?
[X Style (Pure) Original Android Development] tombepa:
Sorry to bother, but is there a way to flash this without using a computer or existing twrp? Is there an app that works? I ask because existing twrp doesn't see my downloads and no access to my computer for another day or so. Thanks

Edit : never mind , I tried Rashr from play store and it worked!