yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Original Android Development] WelcomeToTheSkye:
Can now officially confirm

Backup

Restore

Flashing

Updating

From an sdcard that is being used as internal

Works perfectly no issues yet!!!!
[X Style (Pure) Original Android Development] DJTeeJay:
TWRP 3.0.0 Announced : http://www.androidpolice.com/2016/0...th-new-theme-true-terminal-emulator-and-more/
[X Style (Pure) Original Android Development] Hashbang173:
yep, clark already built successfully, just wait for download page to be re-indexed
[X Style (Pure) Original Android Development] Hitti2:
Was gonna ask that. Because

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

still lists older versions.
[X Style (Pure) Original Android Development] Naddict:
https://jenkins.twrp.me/job/clark-prod/

experiment at your own peril...
[X Style (Pure) Original Android Development] DJTeeJay:
Thanks but ill wait on Hash to drop the ball
[X Style (Pure) Original Android Development] WelcomeToTheSkye:
I checked there too you can't download from there....
[X Style (Pure) Original Android Development] chevycam94:
Unfortunately, it seems the supposed current version 2.8.7.1 is VERY buggy, and Im having trouble flashing ANYTHING. Aroma wont load (freezes the UI completely), 90% of the time, it cant mount system, and of course, the build number of the DOWNLOAD says 2.8.7.1, but the version of TWRP installed from that download is actually 2.8.7.0.

Makes things VERY difficult to do anything with this phone. So unless 3.0.0.0 fixes all that, Im likely to give up on this one, and find a different phone.
[X Style (Pure) Original Android Development] lafester:
Yeah uh nobody else is having your issues. Who said this was aroma compatible anyway?

---------- Post added at 05:07 AM ---------- Previous post was at 04:55 AM ----------

Any difference between this and your test build?
[X Style (Pure) Original Android Development] caspersfi:
Morning guys. So I mistakenly received this version of TWRP a couple weeks ago.

It was still in testing and not ready for release yet. I've been using it and flashed multiple ROMS done backups and restores etc. In other words haven't had any issues. It's also Aroma compatible with Open Aroma Gapps. I haven't shared it with anyone cause at the time I received it wasn't ready for the public yet.

So can anyone tell me which version this is and is it the same version as this TWRP 3.0.0 that I'm seeing is released?

Thanks

Edit: and obviously I see the version number but I don't believe that's actually the correct version number...

Edit: looking at the Android Police article it looks like I'm running the 3.0.0 version. The version number is just incorrect. Obviously cause this was a test version of TWRP.
[X Style (Pure) Original Android Development] Hitti2:
Same here i have no hell idea which one to download. Where is 3 at. Can someone link to 3?

Sent from XT1575, TrupureXMM 2.4, FrankenClark 0.5.2.
[X Style (Pure) Original Android Development] tombepa:
I've been wondering this. I just set up mine as internal for the first time. If I change roms or update, do I have to reformat it each time or will it be usable automatically?
[X Style (Pure) Original Android Development] daniel.1983:
Go to the official site, where you can search for Clark. The version 3 is already available for our phone.

Edit: https://twrp.me/devices/motorolamotox2015pure.html
[X Style (Pure) Original Android Development] sir-harlekin:
I can not install XClark kernel with 3.0.0.0? Says splitting failed. 2.8.7.1 is working fine...
[X Style (Pure) Original Android Development] Hitti2:
Hm. I am using an encrypted mxpe xt1575, I went to flash franken kernel 0.4 I get

Dumping/splitting image failed. Aborting.

Updater process ended with error: 1
Error installing zip file '/externel_sd/misc/frankenclark-0.4.zip
[X Style (Pure) Original Android Development] lafester:
This was already discussed with the test build...

The last two franken kernels are compatible. No idea what xclark is. But it will need to be updated.

---------- Post added at 04:09 PM ---------- Previous post was at 04:06 PM ----------

I've flashed all the mm roms and combined storage is retained perfectly. Going back to lp obviously would not work.

---------- Post added at 04:29 PM ---------- Previous post was at 04:09 PM ----------

This was from the kernel thread...
[X Style (Pure) Original Android Development] ffejy462:
Flashed 0.5.2 frankenclark kernel with no problems using 3.0.0. No encryption.

mxpe 6.0
[X Style (Pure) Original Android Development] WelcomeToTheSkye:
[MENTION=4630246]Hashbang173[/MENTION] hehehe forum topic name derp [2/516]
[X Style (Pure) Original Android Development] Hashbang173:
fixed
[X Style (Pure) Original Android Development] 3's&7's:
Solid install from twrp app...Ty as always [MENTION=4630246]Hashbang173[/MENTION]
[X Style (Pure) Original Android Development] lafester:
Change log says you made this capable of flashing sparse chunk files? So how would one use twrp to say flash the factory image found in the firmware thread?
[X Style (Pure) Original Android Development] chevycam94:
Doesnt change the fact that I had the issues. But after I flashed 3.0.0-0, all the issues disappeared. Also, since how far back was TWRP NOT Aroma compatible? Ive had 2.8.7.1 on my 6P and G3, and both played just fine with Aroma. So yes, its Aroma compatible. You didnt know that?
[X Style (Pure) Original Android Development] lafester:
Not on this device...
[X Style (Pure) Original Android Development] Hitti2:
I think using these test builds borked my stuff.

I can't install that 0.4 kernel.

Dumping/splitting image failed. Aborting.

Updater process ended with error: 1
Error installing zip file '/externel_sd/misc/frankenclark-0.4.zip

I can't do an encrypted backup I get a 255 error.

Im pretty much left in the dark and am pissed about it.

See if i test any more...
[X Style (Pure) Original Android Development] lafester:
.4 isn't compatible
[X Style (Pure) Original Android Development] Hitti2:
That would explain it.

Ohhhhhhh. I vaguely recall frankenkernal had to be adjusted to work with latest twrp.

Facepalming myself.

Mark me in shame.
[X Style (Pure) Original Android Development] ffejy462:
During testing you assume responsibility for getting yourself out of a potential, and probable, jam.

Knowing how to use fastboot and adb (at the very least having both ready to use on pc).

Having backups of known stable state to revert back to, on and off (pc and otg drive) device.

Having the time and patience to do testing, troubleshooting, logging, and potential repairs.

With encryption I'd have an encrypted and regular backups (I suppose that totally defeats the purpose of encrypting data).

You can learn a lot testing and the community as a whole appreciates developers and the testers for putting out a stable product.

mxpe 6.0
[X Style (Pure) Original Android Development] Hitti2:
I don't think it works that way.

When encrypting through MM, mm encrypts the partition, the OS data resides in that data partition. Is this correct?

I've got backup of LP & MM unencrypted.

But if that partition is encrypted before the OS, restoring will not decrypt.

I tried decrypting "wiping" using fastboot.

I got an error stating something about raw.

Edit.

http://xdaforums.com/showthread.php?p=65186228
[X Style (Pure) Original Android Development] ffejy462:
Tbh, I don't know. I haven't used, or plan to use, encryption. I merely suggested having a backup of both states that you could restore in either case.

mxpe 6.0
[X Style (Pure) Original Android Development] patt2k:
For kernel images you have to un-zip it and flash "image" not .zip (select boot) for flashing
[X Style (Pure) Original Android Development] chevycam94:
And how exactly is Aroma being installed in TWRP "device-specific"? That would be the first time Ive ever heard of that.
[X Style (Pure) Original Android Development] lafester:
Well you have now.
[X Style (Pure) Original Android Development] skwitko:
I give this recovery a 5/7.
[X Style (Pure) Original Android Development] stanleyopar2000:
This is awesome! Love the UI overhaul. Question about the "adaptive storage decryption" does this mean I can switch ROMS back and fourth and not have to worry about losing access to my adaptive SD card because the "adaptive storage was set for the previous ROM? I heard adaptive storage was a nightmare into wanted to switch ROMS. If that is the thing of the past then I have no reason to not use adaptive storage. I have a massive Sony HCXD card that I would like to use for this
[X Style (Pure) Original Android Development] Hashbang173:
I think that might depend on the ROMs you are switching between
[X Style (Pure) Original Android Development] stanleyopar2000:
Hey thanks for replying! Can you please explain an example where " decryption of adaptive storage" would be used?
[X Style (Pure) Original Android Development] playenball:
[MENTION=4630246]Hashbang173[/MENTION]

I am on TWRP 3 and when I installed a new rom tonight it told me that my encrypted data partition was corrupt and that I needed to format to remove encryption to continue. When I try to Format Data from TWRP I get a Error 255. I copied the log and it is below.

http://pastebin.com/fGJvkVyX
[X Style (Pure) Original Android Development] Hashbang173:
What ROM was it?
[X Style (Pure) Original Android Development] playenball:
[ROM][6.0.1][Clark][Unofficial]Temasek's CM13.0

I tried installing AICP and TruepureX after and they both then as well. They both said that it was corrupt after attempting to install Temasek also.

I ended up flashing factory recovery to format it and then flashed TWRP back.
[X Style (Pure) Original Android Development] Tech_Savvy:
Is it possible to get f2fs implemented again
[X Style (Pure) Original Android Development] Hashbang173:
I'll look into it when time allows, probably an easy fix.
[X Style (Pure) Original Android Development] Hashbang173:
Try this build:

https://www.androidfilehost.com/?fid=24411628330025682
[X Style (Pure) Original Android Development] Tech_Savvy:
Thanks confirmed that f2fs works:)!!
[X Style (Pure) Original Android Development] playenball:
Tried repeating steps I did before after I re-encrypted my device and it worked without issue.
[X Style (Pure) Original Android Development] mrvanx:
TWRP 3.0.0-1

[MENTION=4630246]Hashbang173[/MENTION]

Hi, I am downloading the .img file to flash from within TWRP (currently on 2.8.7.1).

Should I grab the latest file (3.0.0-1) or the one in the changelog in the OP (3.0.0-0)?
[X Style (Pure) Original Android Development] Hashbang173:
Grab the latest one 3.0.0-1 as it has some f2fs fixes. But, it will show up as 3.0.0-0 when you boot into it since jenkins didn't seem to change the version properly.
[X Style (Pure) Original Android Development] milski65:
Question for anyone. I'm still on 5.1.1 and 2.8.7.0 twrp. Any need to update to latest? Not sure if it plays nice with anything other than mm.
[X Style (Pure) Original Android Development] minty1978:
I couldn't install 3.0.0.1 using the twrp manager as it thinks I already have it installed, when I'm using 3.0.0.0.

Guess this is due to the version number issue.
[X Style (Pure) Original Android Development] CJ-Wylde:
Thank you for the updated theme!!!!!
[X Style (Pure) Original Android Development] Razr1804:
i cant theme twrp can any1 show me how to use them. i followed the instruction on twrp xda page but no result.
[X Style (Pure) Original Android Development] AnimusVoxx:
is anyone tell me if they are havin gthe same issue as me, im doing a nandroid backup to my external sd card and whenever i go to back up it tells me im in like 1970s or something and im not sure whats causing it, any help would be greatly appreciated
[X Style (Pure) Original Android Development] Hitti2:
Shut down the phone for 2 minutes. Boot into recovery. Time and date should be correct.

Sent from XT1575, TPXMM 2.4, Frankenclark 0.6
[X Style (Pure) Original Android Development] Degod:
Hi, I just flash TWRP 3.0.0-1 but the banner still says 3.0.0-0... Is it normal?
[X Style (Pure) Original Android Development] Hashbang173:
yes, jenkins didn't change the version for some reason
[X Style (Pure) Original Android Development] nightwing713:
I flashed 3.0.0.1 but it just hangs on the logo when I boot into recovery
[X Style (Pure) Original Android Development] Mejilan:
No issues here. Perhaps try flashing it again via fastboot?
[X Style (Pure) Original Android Development] nightwing713:
Ah it's working now. Just needed to be patient :)
[X Style (Pure) Original Android Development] Tanker Bob:
Just flashed 3.0.0-1 and it seems to work fine. Thanks for the great update!
[X Style (Pure) Original Android Development] gpz1100:
Any feedback on this? Anyone have success with this?
[X Style (Pure) Original Android Development] nmh5001:
I just used Titanium and shoved a bunch of apps to System. Big time memory savings. The annoying thing is you need to constantly push updates to System or you'll have duplicate app files in System and Data.
[X Style (Pure) Original Android Development] gpz1100:
Does titaniumbackup move the .lib files to the appropriate place under /system? Not all apk's have .libs, but those that do won't work if these files are missing.

------------------------------------------------------------------

@Hashbang173, consider the following scenario; sd card used in mixed mode. (sm partition disk:179_64 mixed {some number} )

Portion of it is used as internal storage, remaining space is used as external (fat32/exfat).

Question:

When creating a twrp image, will all data be backed up, from userdata + internal storage ?

What about when restoring. Will it dump everything to the internal userdata partition or will respective files go back to their original locations?
[X Style (Pure) Original Android Development] nmh5001:
It must, because things seem to be working just fine. I did notice all the app data seemed to die, like app settings or game saves, but I just did a Titanium restore and it all came back. Obviously not the cleanest way to utilize that 2 gigs of empty space. Seriously, what was Moto/Leveno thinking? It's not like it's running TouchWiz.
[X Style (Pure) Original Android Development] gpz1100:
^^Futureproofing? Maybe android 7 will take up 3.5GB.
[X Style (Pure) Original Android Development] kamykowsky:
Hi, I'm new user of Moto X Pure and have a problem with using TWRP Recovery(lastest version). I'm on stock 6.0 with unlocked bootloader. After installing TWRP it boots normaly to recovery as it should do, but when I do reboot to system and then again want to go into recovery from fastboot menu I can't get in. I just have a black screnn with little android with exclamation mark and that's all. Is there any way to fix it? Also I know that this isn't the right topic to ask for that but it's easier to make questions in one thread. Do I have install something else if I want to install SuperSU 2.65 through recovery?
[X Style (Pure) Original Android Development] gpz1100:
^^I'm pretty sure this has been mentioned somewhere in this thread. After you flash twrp, unplug and power the unit off.

Reboot with the power+vol down, select recovery. Should work.

OR, it might have to do with your response to the mount system as r/w in the initial loading of twrp.

I don't remember what I did to make it stick as the stock rom was going away anyways. Of course, full system sbf was on hand in case something got messed up.
[X Style (Pure) Original Android Development] kamykowsky:
After first boot to TWRP I chose option to "Keep read only", should I change it? If yes, how can I do that? I tried your method but after reboot to system still I have to flash twrp again because of this little android with exclamation mark. What is full system sbf? Can I send you private message with some questions?
[X Style (Pure) Original Android Development] gpz1100:
Good question. See if there's a twrp folder on the internal storage or sd card. Delete both if present. Reflash twrp and see if it prompts you for this question again.

The android with the exclamation point is the splash screen for the stock recovery. It's some combination of power key and one of the vol keys to gain access to it (hold down power for a few sec then tap one of the vol keys. Might be the other way around. I can never remember).

SBF's are full system images (the entire firmware). There's threads on here that have links to it. One should always have this one hand _BEFORE_ they start flashing. In case you get to a point where the phone no longer boots or bootloops you have a way of returning to stock. HTC calls it a RUU, Samsungs use the odin tool with .tar files, etc.

_WARNING_ make sure the sbf/firmware image you download matches the current system of your phone, esp the bootloader. Downgrading is typically not permitted and may cause issues such as no signal/broken wifi, or even bricking of the phone. Varies with device and even versions of android.

--------------------------------------------------------------------------------------------

@Hashbang or anyone that knows

Does this current twrp 3.0.0.1 support adoptable storage on the moto x pure?

If it does, what can one do with it from within twrp? Can recoverable twrp images be generated if OTG storage is used?
[X Style (Pure) Original Android Development] kamykowsky:
Wow, looks like it's working now, thanks a lot.
[X Style (Pure) Original Android Development] CCivale:
I've scrolled through just about this entire thread and tried searching for this issue, but for some reason my 128gb micro SD doesn't get recognized by TWRP. It always says 0 gb. I've seen a few people with the same issue, but I've never seen an answer on why this might be.

Any help would be greatly appreciated. I'm currently using 3.0.0.0
[X Style (Pure) Original Android Development] Hashbang173:
What file system do you have your sdcard formatted as?
[X Style (Pure) Original Android Development] gpz1100:
Looks like I'm able to answer my own question (more or less). So it appears when the sd is configured entirely as adopted storage, twrp 3.0.0.1 recognizes it as adopted storage. Twrp images backup successfully to the adopted storage (and restore as well).

Apparently, this is not without caveats. Some apps still insist on storing data to the internal storage (google play music). There's a supposed workaround by installing GPM as a user app and then changing it's storage location (settings|apps|Google play music|storage) to reference the adopted storage. This didn't work for me. The setting to change storage locations was not there.

For non cloud users, the other caveat is one still has no access to the adopted storage outside of android system. MTP access is available through twrp which allows interaction with the files. If corruption or other loss occurs, tools that can recover from fat32/exfat would NOT work. Also, mtp transfers are slower.

There's a few tools such sambadroid (requires SELinux permissive) which works with either mode. This allows wireless access to the sd card and file manipulation.

At the end of the day, I'm going with portable storage. Plenty of room, even on a 16GB model with the number of apps I usually install. Also, many user apps can be relocated to the wasted /system partition to save some room in userdata.

Probably a topic for another thread, next question; Optimal cluster size to format the sdcard to...
[X Style (Pure) Original Android Development] CCivale:
Fat32 - although, now that you ask that, previously I had been using it in a Note 3, and it's partitioned for MultiSystem. Could that be causing the problem?

The majority is Fat32, but I think a small part is NTFS.
[X Style (Pure) Original Android Development] SR3TLAW:
Just to clear up a hitbtod my confusion. What is the latest stable (everything works) version I sbkkd be running?
[X Style (Pure) Original Android Development] Mejilan:
I've had no issues with 3.0.0-1 I downloaded from here:

https://dl.twrp.me/clark/

Been using it for a while now and it's just fine.

I briefly had 3.0.0 as well, but updated to 3.0.0-1 once I realized there was a new build uploaded.

I'm running stock MM 6.0 and have my SD card set as portable, though.
[X Style (Pure) Original Android Development] DroidForLife33:
I was just wondering I have twrp 3.0 installed and systemless root. I keep on getting notification for this security update. And I know to install it I need to have stock recovery and be unrooted. Unrooting is not the problem that's an easy fix. I was wondering if anyone can help me with the steps on how to install stock recovery again. Thanks
[X Style (Pure) Original Android Development] Hitti2:
Was wondering if it normal for twrp folder to be not accessible on internal drive.

I get access denied. I thought back a month ago when I started this I was able to make copy's from twrp internal drive to sdcard.

I can no longer access twrp folder under internal drive.

Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7
[X Style (Pure) Original Android Development] SpasilliumNexus:
Do you still need to re-install stock recovery? If so, can you pull the OTA from /data/data/com.motorola.ccc.ota/app_download/ and post it? I can help you get stock recovery back.
[X Style (Pure) Original Android Development] psxmail:
You just need to check fully unroot in SuperSU and after the reboot you will have the stock recovery back again. Then you will be able to put the ota. It is what I did last week.
[X Style (Pure) Original Android Development] DroidForLife33:
I only see these four folders. I don't see app_download. Folder?
[X Style (Pure) Original Android Development] Razr1804:
How to add theme for this version as I cant get it to theme
[X Style (Pure) Original Android Development] SpasilliumNexus:
You get the stock kernel back. Not recovery.

It could be in app_reservedSpace or cache or the /cache folder itself. BTW, you have a Pure right (XT1575), and not a Style?
[X Style (Pure) Original Android Development] nikeman513:
Why can't I get this to flash? I put it on fastboot directory where I unlocked and even changed the name to Motox. So I did fastboot flash recovery Motox.img it just says it can't flash or find partition.. Its all in adb...
[X Style (Pure) Original Android Development] juanacevedo:
[MENTION=3928294]nikeman513[/MENTION] You're in bootloader mode right? And you got the path right? Make sure the path is with this kind of slash \ and not this one /
[X Style (Pure) Original Android Development] nikeman513:
It's in C:/ adb/
[X Style (Pure) Original Android Development] silverxbv2:
Try opening the command prompt from the adb folder. Shift-right click and open command prompt here. Then type fastboot flash recovery nameofrecovery.img
[X Style (Pure) Original Android Development] spotmark:
No, what he means is, are you booting your phone into fastboot, before executing the commands?
[X Style (Pure) Original Android Development] nikeman513:
Yes I'm I'm bootloader mode BTW, I right click on windows 10 and it doesn't give me the option to do that. Are you on Windows 10? So, are you saying do it before or after?
[X Style (Pure) Original Android Development] jaben2:
I usually just type fastboot flash recovery, then drag the img to the command prompt. Works for me
[X Style (Pure) Original Android Development] hbar98:
This is great! Thanks so much!

On a different track: I had installed and set up Android Pay before I flashed TWRP and rooted the phone, and, so far, Android Pay is working for me. Anyone else notice this??
[X Style (Pure) Original Android Development] Locklear308:
Thank god
[X Style (Pure) Original Android Development] npjohnson:
Congrats Man!!!
[X Style (Pure) Original Android Development] spotmark:
Put your phone into fastboot, plug it into your computer, open a command prompt, in the folder where you have fastboot and recovery, and execute the commands.
[X Style (Pure) Original Android Development] Locklear308:
Sent in a donation as a thank you :D
[X Style (Pure) Original Android Development] nikeman513:
Got it, thanks! Should I make SD card Ext. 4.? I can't seem to write to my new SD card half the time, it says "busy" and its a new Samsung Pro... Shows 30GB free... It's not writing to SD card like I want it it to. I thought Android would format it automatically?