yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] ochen85:
Can confirm that when Micro SD Card is set as portable/adoptable storage, this version of TWRP can see the files on your sd. I flashed your kernel with the latest TWRPand it worked flawlessly. Thank you so much for the TWRP fix. Was having trouble linking apps to my external SD Card, so now that adoptable storage works, I don't have to.
[E 2015 Android Development] fivefour:
Very nice, the updated UI and terminal is great.
[E 2015 Android Development] yelupic:
XT1524 - Encryption works very well with CM 13 @ 2016-01-19. - However the r7 TWRP recovery isn't able to decrypt the data partition (mounting states "invalid argument").
[E 2015 Android Development] hydeah:
What is the difference between this one and this one: http://xdaforums.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726 ?

Are these just different recovery images of different versions or are they completely different TWRP's?

I have XT1526.
[E 2015 Android Development] bloodsaw:
This topic is an update to that project.

Great job [MENTION=6485916]squid2[/MENTION] on the updates, the new R7 image works great with marshmallow based roms with adoptable storage in use windows 10 reports on the MTP device 2 items, there is "Internal Storage" and an "SD Card - Adoptable Storage"

-Using the XT1527 model
[E 2015 Android Development] ZETROzky:
TWRP 3.0.0

TWRP 3.0.0 has been announced, new theme coming up. (It does look mostly like the current theme you put on r7)
[E 2015 Android Development] EB20XY:
So, is there any essential change from r7 to that one ? :confused:
[E 2015 Android Development] :
Read twrp log about changes, theme wise some newer devices got the ui on 2.8.7.0 such as s5 Neo :)
[E 2015 Android Development] EB20XY:
Well, I had read that. But what are the differences to the "commit-level" of [MENTION=436307]squid[/MENTION] r7 of our twrp ?
[E 2015 Android Development] :
I honestly can't answer that,
[E 2015 Android Development] PimpMy5Ton:
[MENTION=6485916]squid2[/MENTION] Will you be updating your twrp to 3.0.0??
[E 2015 Android Development] squid2:
The r7 build is much closer to 3.0.0.0 than the original release tagged 2.8.7.0. Commit wise, the r7 build is 85% of the way to what was tagged 3.0.0.0.

I will do another build at some point in the future. I've been been periodically putting out new builds and there's no reason for me to stop. I might change the version number to 4.3.14.15926 to satisfy the people here who like big version numbers.
[E 2015 Android Development] atomomega:
I know man, I've never understood people who just can't live without an update when everything is working fine with the current release.
[E 2015 Android Development] squid2:
TWRP 3.4.5-r1

I have a new TWRP build for you. For various reasons, I've started building from my own fork of TWRP rather than the one in the OmniROM tree. My fork has miscellaneous bug fixes, additional translations, removes the built in SuperSU (that's not Marshmallow compatible anyway), and doesn't include a hack for certain old HTC devices. This build should fix encryption support on Marshmallow ROMs.

On my various device threads and via PM, I've had around a dozen people tell me that TWRP 3.0.0 has been released and asking for when or if I'll be providing an update. As a joke to pacify certain users who seem to think I live in a cave and don't know the TWRP version number was upped to 3.0.0-0, I've changed the versioning scheme for my fork. My previous 2.8.7-r7 build was 85% of the way to 3.0.0. This new build is from my fork which is newer than 3.0.0. My new versioning scheme is 3.4.5-r# where the last digit is the only meaningful number. This brings several benefits. It allows you to easily tell the version you are running from within the recovery. It allows you to brag to your friends that your TWRP version number is bigger than theirs. It makes it clear to the informed that is is built from a TWRP fork and not the OmniROM TWRP. It also serves to rebuff complaints that the version number is smaller than what some other device has.
[E 2015 Android Development] spiked_mistborn:
Can you incorporate "plus" and "pro" into the version number somehow to make it even better? :p
[E 2015 Android Development] yelupic:
Thank you very, very much for your hard work. :good:

I totally agree and I understand your frustration.

You could start your versioning here to outsmart any "competitor" (just kidding) ... :D
[E 2015 Android Development] spiked_mistborn:
I had a reboot in 3.4.5.r1 while restoring a backup. The screen was off due to the timeout, I pressed power and then after I swiped to unlock it rebooted back to recovery. I had just deleted a backup, backed up my current ROM, and then tried to restore an older backup. The backup restored successfully after it rebooted. Here's the end of the log, but I don't know if it will be much help. It goes straight from a file copy to twrp booting. [MENTION=6485916]squid2[/MENTION] I can pm you the full 25MB log if you want, but it looks like it's mostly 24.99MB worth of filenames being copied.

==> tar_extract_regfile(t=0xb5314300, realname="//data/data/com.chrome.beta/cache/Cache/abe874ad6abc3f03_0")
==> extracting: //data/data/com.chrome.beta/cache/Cache/abe874ad6abc3f03_0 (file size 6623 bytes)
Starting TWRP 3.4.5-r1 on Thu Feb 11 13:04:28 2016 (pid 292)
I:Lun file '/sys/devices/platform/msm_hsusb/gadget/lun0/file'
I:TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
I:Starting the UI...
[E 2015 Android Development] ayush rao:
Hey does this support aroma installer
[E 2015 Android Development] DroidFreak32:
It kinda supports.. The thing is I use open gaps aroma and the Feb versions don't support this recovery completely.. Some gapps don't get installed.
[E 2015 Android Development] ZETROzky:
Might've been a bit too much

Thanks squid2 for all the help you've done us so far (You're the only person who makes a "good" recovery that gets updated almost every month.), but I want you to go back to the original naming scheme. I know that we can brag about it to others, but it's just childish. Also, this is the quote from twrp's official news page, "For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.". I want you to use that numbering system, if it is possible.

P.S. When can we expect official cm13 builds for Surnia and Osprey? I'm waiting!..
[E 2015 Android Development] bloodsaw:
http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

http://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip

SuperSU 2.67 does in fact work on the Surnia running crDroid 6.0.1, to get it working install your ROM+Gapps and custom kernel, boot into android, enable developers menu, enable root for apps and adb, open the play store and install SuperSU reboot into TWRP install the SuperSU v2.67 zip reboot into android and test SuperSU it should now work

These are the steps I performed to get SuperSU working on my Surnia Running (Squid TWRP 2.8.7.0-R7/crDroid 6.0.1/Squid Kernel) So I don't see why TWRP 3 shouldn't be able to install SuperSU unless it's using a different version then the new WIP v2.67
[E 2015 Android Development] ZETROzky:
Guess what.

https://dl.twrp.me/surnia/

eueueueuè...
[E 2015 Android Development] bloodsaw:
Why the huge size difference though? Squid's twrp 3.4.5-R1 is only 7.75MB that file is 15.7MB
[E 2015 Android Development] ayush rao:
Hey the official TWRP is out.....do u think aroma is supported on that
[E 2015 Android Development] Sher1234:
Please tell which twrp to be flashed

Squid2 TWRP 3.4.5

OR

Official TWRP 3.0.0 (https://dl.twrp.me/surnia/)

Currently on squid2 twrp 2.8.7-r7
[E 2015 Android Development] squid2:
SuperSU zips work fine as always. What I removed is the old SuperSU bundled with TWRP that doesn't support Marshmallow.
[E 2015 Android Development] dandrumheller:
The one with the higher version number - that way you will have a newer version number than all your friends! [emoji3] [emoji3] [emoji3]
[E 2015 Android Development] bloodsaw:
Why not replace the old version with the version that works with Marshmallow then?
[E 2015 Android Development] squid2:
Different ROMs require different SuperSU versions (eg. 2.67 doesn't work with the Motorola Marshmallow stock ROM). Also, I don't like the idea of bundling a proprietary independent third party package with it.
[E 2015 Android Development] bloodsaw:
Ahh okay sounds reasonable, any idea's why the official TWRP is 15.7MB compared to yours which is only 7.75MB?
[E 2015 Android Development] eonarma:
to instal this I just have to download it and install it through TWRP->Install?
[E 2015 Android Development] spiked_mistborn:
TWRP -> Install -> Install Image

or

fastboot flash recovery filename.img
[E 2015 Android Development] squid2:
TWRP 3.0.0-r2

The focus of this release is on encryption support. I've done an extensive overhaul of the crypto support code in TWRP to fix bugs and simplify logic. I've fixed an issue where using TWRP 3 on a device with hardware encryption running Lollipop would render the Lollipop ROM unable to read the data any more. I fixed an issue that prevented the use of patterns and passcodes with an odd number of points/characters. Furthermore, I fixed support for 4x4 grid and larger lock patterns on CM13. There are also a few translation updates in this release.

This build once again comes from my personal fork of TWRP, though I've just submitted my crypto rework for consideration in the official TWRP tree.
[E 2015 Android Development] ayush rao:
Or u could use flashify if ur already rooted
[E 2015 Android Development] yelupic:
@squid - You are just too fast for me. - Why? Because just in this moment I wanted to give you the following feedback - now deprecated stuff:

@squid

Results testing encryption/decryption of TWRP recovery (twrp-surnia-3.4.5-r1.img)

Flashed twrp-surnia-3.4.5-r1.img

___

Clean Install of cm-13.0-20160201-UNOFFICIAL-surnia.zip + (fresh) Device encryption + Lockscreen Swipe (no|default_password): OK

> rebooting into TWRP: Not OK (password wrong > decryption not possible)

___

Clean Install of cm-13.0-20160201-UNOFFICIAL-surnia.zip + (fresh) Device encryption + Lockscreen PIN: OK

> rebooting into TWRP: OK (decryption possible)

Lockscreen type PIN > Changing lockscreen PIN

> rebooting into TWRP: Not OK (PIN wrong > decryption not possible)

(after resetting to old PIN in Settings decryption in TWRP possible again)

___

Clean Install of cm-13.0-20160201-UNOFFICIAL-surnia.zip + (fresh) Device encryption + Lockscreen password: OK

> rebooting into TWRP: OK (decryption possible)

Lockscreen type password > Changing lockscreen password

> rebooting into TWRP: Not OK (password wrong > decryption not possible)

___

Clean Install of cm-13.0-20160201-UNOFFICIAL-surnia.zip + (fresh) Device encryption + Lockscreen 3x3 pattern: OK

> rebooting into TWRP: Not OK (pattern wrong > decryption not possible)

___

Also tested:

Clean install of cm-13.0-20160201-UNOFFICIAL-surnia.zip + (fresh) device encryption + lockscreen type PIN (8 digits)

wipe of all partitions except system (encryption left intact)

Restore of a CM 12.1 Backup (only the huge production data partition) which has lockscreen type pattern

Result:

PIN intact > TWRP decryption possible

Lockscreen pattern intact & functional

> rebooting into TWRP: OK (decryption possible)

Next step:

After a change of lockscreen pattern & a reboot into TWRP

> Not OK (password wrong > decryption not possible)

___

My tries with

vdc cryptfs enablecrypto <wipe|inplace> default|password|pin|pattern [passwd]

vdc cryptfs changepw default|password|pin|pattern [newpasswd]

were leading to nowhere-land:

vdc threw a linking error, missing dependencies ... (adb in TWRP) & a "wrong parameter" message (adb root shell, Android booted up).

Nevertheless, I'm very pleased of having at least some sort of device encryption at hand. - Thank you again.

Ok, testing your new r2 ...
[E 2015 Android Development] EB20XY:
Wow. Thanks a lot. :highfive:

Hope it will still run with a Cm12.1-surnia as perfect as before. :)
[E 2015 Android Development] eonarma:
Awsome, thanks
[E 2015 Android Development] PimpMy5Ton:
[MENTION=6485916]squid2[/MENTION] Awesome work as always man, working good here on my XT1526 Surnia running latest release of Official BlissRom v6.1, thanks again ?
[E 2015 Android Development] yelupic:
@squid2 - blackbox testing device decryption in twrp-surnia-3.0.0-r2.img (XT1524)

(Initial clean install of cm-13.0-20160201-UNOFFICIAL-surnia.zip + (fresh) Device encryption + Lockscreen type "Swipe")

All lockscreen types are fully functional and transparent to TWRP now

Also when changing the tokens within a particular lockscreen type

Same for switching among different lockscreen types

(Backups & restores working)

One (minor) exception:

If you have set up a pattern lockscreen, restoring a data-partition with a different lockscreen type (i. e. password), the decryption with the pattern under TWRP will work and also the password lock when booting into Android. - But after changing the lockscreen the first time it won't be registrated in TWRP properly. - Consequence is, you have to format data to get away.

So, you are golden again ... Thanks a lot :good:
[E 2015 Android Development] Titantech2015:
nvm got it installed using rashr
[E 2015 Android Development] P0PETIN:
Okay which one do I flash?
[E 2015 Android Development] DeafGeek:
3.0.0-r2
[E 2015 Android Development] dzidexx:
Restore moved data&apps not working when the sdcard is set to the additional internal memory.

Backup of user data&apps is called sdext2 and it is restored to data/sdext2 - it is the wrong place.

It should be mnt/expand/e66ko89.....same letters and numbers.

Sorry for my english.
[E 2015 Android Development] Realfam Vigilante:
Rashr & twrp manager??

I have a Moto E 2nd Gen 4G LTE XT1527 with an unlocked bootloader, I am rooted with TWRP that doesn't let me do JACK!!, I can't make a Nandroid backup and all kinds of stuff, would I possibly brick my device if I flash the new TWRP img or a new kernel img with Rashr or TWRP Manager?! I would greatly appreciate some advice, thank you!
[E 2015 Android Development] P0PETIN:
Try flashing TWRP through adb, the one in this thread
[E 2015 Android Development] bloodsaw:
use this http://xdaforums.com/moto-e-2015/development/tool-moto-e-toolkit-one-click-unlock-t3047150 to flash over the recovery
[E 2015 Android Development] KonomiKitten:
Would someone mind explaining the difference between twrp-surnia-3.0.0-r2 and twrp-surnia-3.4.5-r1. I noticed the 3.0.0-r2 release was released after the 3.4.5-r1 release, which is a bit odd. Is there a reason for having both?
[E 2015 Android Development] DroidFreak32:
If you want to do that you can go to twrp> wipe> advanced wipe> select a partition> click on the repair button at the bottom > there you'll find options to format the selected partition to f2fs or other file system . (Afaik Motorola phones have the data partition set to f2fs out of the box)

Hope this helped :)
[E 2015 Android Development] xpmule:
Well if it is ALREADY integrated into TWRP why not ?

Am i crazy or is SuperSU already embedded into TWRP ?

Anything that helps lessen confusion is good in my mind.

And i bet if you just asked the guys hey it's in there but i want your permission etc ..i bet they would say ya fine go ahead.

For the end users who walk into all this blind it can be a colossal pile of crap to have to learn.

Then having to figure out which SuperSu's support which Firmware versions and where to get them etc

is just yet one more headache.

And the version numbers ?

Uhh ohh LOL

ya i see what that guy was saying now..

the newest one has smaller number than the 2nd newest one.. more confusion.

All i know is if users are going to switch to Marshmallow we need crystal clear & concise info.

And that starts with installing the Stock firmware.

THEN applying things like custom recovery and maybe patched boot screens and custom kernels.

With out Root and the custom stuff we are already used to the new Android version is of little use.

It doesn't hurt to add a little more info to the first post either.

Let's be real here guys... humans don't have the time or desire to read through every comment on all these topics.

And it doesn't require much effort to put key pieces of info in the right spot.. to prevent a lot of unneeded questions / confusion.
[E 2015 Android Development] majster95:
Thanks Squid, i have encrypted phone and official 3.0.0.0 build didnt work (didnt ask for password). I installed your build and works like a charm ! Again thanks !

Wysłane z mojego XT1524 przy użyciu Tapatalka
[E 2015 Android Development] vishalgupta.vns:
will it work in my moto e2 surnia xt1521

with stock marshmellow 6.0
[E 2015 Android Development] bloodsaw:
This is such a redundant question and don't quote the first post it makes threads messy.

Is your device code named surnia? Then yes it will work. Maybe you should learn to research your device before posting or even looking at installing custom roms. http://www.gsmarena.com/motorola_moto_e_(2nd_gen)-6986.php

Not trying to be an ass or anything of the sort but these things should be thought of first. People don't understand how easy it is to permanently brick a device by just flashing the wrong file, I remember installing Android 1.5 and 2.2 on a Sony Xperia X1i boy was that a mess to get setup running a custom version of a Windows Mobile Kernel to boot into the Android subsystem with Android installed completely to your SD Card.
[E 2015 Android Development] faheyd:
Hey Ass, "People don't understand how easy it is to permanently brick a device by just flashing the wrong file, " that's exactly what he's trying to prevent. I know this is a dev site, but it's terrifically hard to find info sometimes. Be patient, and remember, you too were a padawan at some point.
[E 2015 Android Development] bloodsaw:
That's why I gave the link for the information right? Xda has a q&a for a reason to ask questions like this
[E 2015 Android Development] vishalgupta.vns:
will it work with marshmellow 6?

---------- Post added at 06:23 AM ---------- Previous post was at 06:16 AM ----------

sir, i dont know too much about operating in this site so it will take some time to know rules and regulations of it ,i dont think that ur born with perfection in it cos nobody have thats why this site and devs team provides help to all, by the way i m not that noob u r giving me link of gsm arena ,i know my device better and i was just triying prevent the chances of accidental damage of device............ so i hope some day u will thnk me for my posting..........
[E 2015 Android Development] bloodsaw:
Then shouldn't you be reading up on those rules and regulations and how the site works before posting for help to flash things on your phone, I mean it's just common sense to do some research first before you go asking questions
[E 2015 Android Development] dorofeev:
Newbie here -- some help please :)

So, I've successfully unlocked bootloader (thanks, Motorola!) on my Surnia XT1526 8GB P3 (Boost Mobile) and now want to install TWRP recovery image on it. The phone barfs at me when I try to do so:

>fastboot devices

TA0980T0GH fastboot

>fastboot flash recovery twrp-surnia-3.4.5-r1.img

target reported max download size of 268435456 bytes

sending 'recovery' (7934 KB)...

FAILED (data transfer failure (Unknown error))

finished. total time: 7.032s

>fastboot flash recovery twrp-surnia-3.4.5-r1.img

sending 'recovery' (7934 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.014s

Is there some other step that I need to do before TWRP can be installed? I've read a bunch of tutorials on this, but I don't think my case is covered in any of them. Thanks in advance for any help. :o
[E 2015 Android Development] vishalgupta.vns:
either ur using a wrong recovery or wrong recovery location.....plz put it fastboot folder on desktop or programme files/mdbfastboot folder and rename it with recovery.img then run mdb fastboot.exe then open fastboot folder with recovery, and flash it with commands,follew this site

http://www.droidviews.com/root-moto-e-2015-condor-and-install-twrp-recovery/

hit thanks if helps....
[E 2015 Android Development] atomomega:
Why link to another site when pretty much everything is here on XDA in this very same thread?
[E 2015 Android Development] bloodsaw:
use this http://xdaforums.com/moto-e-2015/development/tool-moto-e-toolkit-one-click-unlock-t3047150
[E 2015 Android Development] dorofeev:
Solved by NOT using Windows 10 VM and using native Mac ADB/fastboot tools on OSX.

bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)

Thanks anyway.
[E 2015 Android Development] Buzbee2:
Anyone notice the file manager is messed up in Squid's recoveries? I went into the system folder and the only thing I saw was the "bin" folder.

Also, when you install a rom via adb sideload, on exit you get a message that there is no OS installed and asks if you want to continue. Not sure why this is coming up.
[E 2015 Android Development] PresidentMcCain:
I think all you have to do is go to the Mount menu and "mount" the /system partition and then everything should work
[E 2015 Android Development] bloodsaw:
actually this happens with the 5.1 stock rom.

I have the XT1527 RETCA model which is the Canadian Unlocked Retail Version, RETCA only comes with 5.0.2 and no OTA available to go any higher but I have downloaded and flashed the 5.1 RETUS stock rom to my phone and with TWRP 3+ This error occurs every time the phone is rebooted.

In order for me to boot the stock rom now I must use the bootloader to load android by loading the bootloader and pressing the power button when the "start" option is highlighted or else TWRP loads and detects no OS installed when trying to reboot.

I never had this issue before I installed 5.1 RETUS. i'll attempt to install the latest build of crDroid 6.0.1 again and see what happens

When I bought the phone on boxing day 2015 it came with 5.0.2 and as soon as I got home with it I checked for custom roms and other flashable things and started by flashing Squid2's TWRP project then I flashed the unofficial CM13 builds by openhacker, I then moved onto crDroid 6.0.1 which has major improvements over openhacker's builds of CM13 but with the latest build I was getting a constant bootloop, I also recently tried PACrom 6.0.1 but it just gives a constant bootloop after reaching the launcher as well so I had installed 5.1 RETUS maybe now that I have installed 5.1 and got my modems updated the latest custom builds will work without bootlooping.
[E 2015 Android Development] DroidFreak32:
I've been having some problems with gapps aroma.. It works, but not all the apps I select get installed.. For ex YouTube never gets installed but the other apps get installed. Not to be rude or anything, but SuperR's 2.8.7.0 twrp from AF is able to install all apps that I select in the aroma installer. May be it's just me.. But can anyone confirm this using gapps aroma??
[E 2015 Android Development] q2n:
Thanks, Squid, just bought and flashed a new device and everything works perfectly AFAICT.

Actually downloaded your latest kernel (from your kernel thread) but decided not to flash it after reading a post that it didn't matter.

So I'll be following this thread and updating when you post new releases. Many thanks for your excellent work. :good: