yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] MotoJunkie01:
Bad news for you on using the xt1526 Boost for GSM providers or other CDMA providers. It is carrier locked with embedded encryption and,. as far as I know, the carrier restrictions have never been exploited or otherwise bypassed. (Though I have heard of the Boost xt1526 being activated on Straight Talk (CDMA LTE)). Flashing a custom radio is only beneficial to things like improving cell signal, more efficient data roaming handover, etc. I ported an Android 6.0.1 baseband (from the Moto G3) to the xt1526 because, at that time, it took advantage of an exploit which has long been closed off (the Virgin Mobile Data Done Right free 4G/LTE exploit). Here's the thread. Let's move our discussion there to keep squid's thread on topic. Thanks

https://xdaforums.com/moto-e-2015/orig-development/modem-stock-android-6-0-1-baseband-t3659689/page8
[E 2015 Android Development] Sbubba:
hello there, my touchscreen is broken. can you help me to find a version that works with physichal button?

I read about CWM non touch but I don't find for surnia. Now I have TWRP of this thread, but I cannot use it .__.

thank you
[E 2015 Android Development] Sid32:
Plug in a mouse with a otg cable.
[E 2015 Android Development] Sbubba:
I had not thought about it, it's probably better than a recovery, I'm looking for one.

if you have other suggestions you say as well, thank you :)
[E 2015 Android Development] daktary:
directly flashable from trwp itself

copy img file on sd card

restart in recovery mode, choose button "install", choose button "image", select the img file and choose "recovery" as partition ("boot" is for temporary install)

restart in recovery mode and it's updated
[E 2015 Android Development] daktary:
a question about the last version 3.2.3

in the backup function you must select following partitions:

- system

- system image

- data

- cache

- boot

- recovery

System image and recovery were not in my previous version. What is the use of each option?
[E 2015 Android Development] mnd123:
You don't need system image for ordinary backups, and probably cache also.

System image has something to do with some other method of backup and may have some advantages over system. But I had some problems on another device, when trying to restore it, so I didn't use system image backups afterwards.

Recovery is your TWRP installation.
[E 2015 Android Development] daktary:
Ok thanks, so system+data+boot is enough to keep backups like in the previous versions
[E 2015 Android Development] Jocantonio:
Link Is down, please fix it.
[E 2015 Android Development] Kumar201801:
Download link is not working. Please fix it
[E 2015 Android Development] Kumar201801:
I am answering my own question. I think developer wants us to download the official TWRP. If anyone is here like me in or after 2022 and trying to find TWRP, Use this Official TWRP Link, if Squid's link is not working.

UPDATE: MY PHONE IS STUCK AT MOTOROLA BOOT LOGO, AFTER FLASHING WITH OFFICIAL TWRP
[E 2015 Android Development] ThePiGuy3141:
What TWRP version did you use and how did you install it?
[E 2015 Android Development] chris1892006:
Yes, I'd like the twrp for Surnia XT1527. Download link is down.
[E 2015 Android Development] thathtcguy:
While running r8 my phone has a worse battery life than it had on r7, updated rom and it works great again
[E 2015 Android Development] dreyeth:
Is that the only step? that must be done with the phone powered down into the stock recovery (volume down + power on?)

and the USB cable plugged in, then issue the command with fastboot in a terminal on a connected PC?

Any other steps to avoid bricking on XT1527 surnia and of course on a phone with a unlocked bootloader?

I'm actually having trouble finding a good guide to cover the Moto E 2nd (2015) 4G LTE (XT1527) when it comes to getting

a custom recovery system on it.

Its been awhile though, and never really been that deep into this stuff on phones yet.

I've had CyanogenMOD on a couple phones this one has been a little more complicated then anything else

I've done yet (had a lot of trouble getting the bootloader unlock code), and the recovery options are different

on this phone, its been a long time.

I'm just really looking for something to flash ROMs and get CyanogenMOD or another ROM on my phone,

I really don't feel that a device is mine unless I can replace the operating system on it. >_>
[E 2015 Android Development] PriPhaze:
Well thats pretty much it.

As long as you already unlocked the bootloader then the warning text should display every time you turn on the phone.

You can also use the command "Fastboot devices" first to see if it shows your phone S.Number and if it does then proceed to flash recovery and you are good to go to flash Roms to your heart's content.

(As long as you know which ones are for your device. just make sure to stay away from otus which is 3G, it will most likely say "surnia or LTE")
[E 2015 Android Development] DroidFreak32:
I cannot use the " mass storage" mode in this recovery. Driver problems. I've to use mtp only. Cybojenix's twrp didn't have this problem :/
[E 2015 Android Development] yelupic:
Me too.

Edit:

I didn't mean mass storage, but MTP mode enabled (device doesn't show up in File Explorer in Win 7 Professional 64-bit)

Has this got to do something with it?

https://github.com/Motorola-Cyanoge...mmit/206ab7931855eaa900124297536d6dd983fca6e2
[E 2015 Android Development] squid2:
Thanks for letting me know, I'll look into it when I get time.
[E 2015 Android Development] DroidFreak32:
Ohkay I had the same problem when I encrypted the phone! And being stupid, I removed the pattern protection after encrypting. This made my phone impossible to turn on. I was stuck in the encryption screen asking me to put the password! (I kept the password as a pattern! ! BUT was asking for a text password! !) I had no choice but to go to the recovery and factory reset. And what happened? It failed! Unable to mount /data. Manually mounting /data didn't work either! I thought I had hard bricked my phone. Then for the last time I tried factory resting but I by mistake pressed the button next to it (it was probably "format data" or something, I don't remember). To my luck /data did get formatted and I could flash the Rom and boot the phone up at last.
[E 2015 Android Development] fix-this!:
Can this be used for the 4g lte sprint/virgin mobile varient? Xt1526 is the model.
[E 2015 Android Development] yelupic:
Morning, in the download section the last release is dated 2015-07-13 (r2).

On the GitHub there is an entry dated 2015-08-25 regarding the correction of fixing/handling encryption.

Is this WIP and not ready yet or would a new build (r3) with the current state of the repo work properly with an encrypted device?

If working, would it work only on a stock encrypted device or also on devices running a custom ROM (i. e. CM 12.1)?

Thank you.
[E 2015 Android Development] tattooedgod:
[MENTION=6485916]squid2[/MENTION] I'm running out of space on internal memory due to trying a bunch of different apps can I wipe internal memory or would that mess things up

Edit: Figured out for myself 2gb of useless data was hogging valuable space.
[E 2015 Android Development] ts_firehawk:
Whenever I try to run an Aroma-based ZIP, the recovery freezes. Does this has something to do with the zip size? Or it is something in the recovery?
[E 2015 Android Development] ahjee:
I've had the same issue as well, I tried Open G Apps Aroma package and it froze every time
[E 2015 Android Development] Bazilli:
Same here.
[E 2015 Android Development] DroidFreak32:
Hey [MENTION=6485916]squid2[/MENTION] , I found a minor bug/issue in your recovery. Whenever I try to flash open gapps aroma version the recovery freezes. I've to force reboot all the time. Same thing with cybogenix's recovery. But flashing the recovery by superR http://androidforums.com/threads/twrp-2-8-7-0-for-moto-e-2015-lte.920652/

The aroma gapps flash just fine. The only problem with that recovery is the annoying long time it takes to wipe. I'd appreciate a lot if you can look into this and fix this. Thanks

PS: Putting that same yellowish tint wouldn't be bad either[emoji12]
[E 2015 Android Development] squid2:
Release 2.8.7-r3 with Encryption Support

I've posted a new build where I fixed encryption support and did some cleanup to reduce size. Pin and password based encryption seems to work perfectly. For swipe pattern based encryption, there might be a glitch where TWRP will appear to reject the correct pattern. The workaround is to first swipe the correct pattern, let TWRP reject it, then swipe an incorrect pattern. TWRP will successfully decrypt if a correct pattern that was rejected is followed by an incorrect pattern.
[E 2015 Android Development] yelupic:
I tested this new r3 release of yours on official nightly cm-12.1-20151021-NIGHTLY-surnia.zip.

Very, very well work.

Before encrypting the device, I had only activated swipe mode to unlock the device (no pin, no password, no pattern).

Then I encrypted the device over Settings > Security > Encrypt phone successfully.

After this, I installed fastboot flash recovery twrp-surnia-2.8.7-r3.img.

When rebooting into the homescreen, I was asked for the password to decrypt the device.

How come? - If you encrypt your device without any pin, password or pattern (like I did) you must use "default_password" (without the quotes) to be able to go on. - But this has got absolutely nothing to do with squid's recovery. - Just FYI.

All tests succeded very well: Booting into Android/recovery, decrypting in recovery (pattern, password, I didn't test pin protection), backing up and restoring.

Contrary to what @squid2 described for his phone, the pattern unlocking on my device is working immediately, but the password mode needs first the correct password (which will be rejected as wrong), and then - followed by a wrong password - will finally decrypt the device in recovery and you are good to go.

Thank you, squid2, for giving this to us to make this planet a little bit safer. :good:

(I pray each day treble to all known and unknown gods for your health and wealth ... :angel:)

Edit:

Even an OTA update via CM Updater from cm-12.1-20151021-NIGHTLY-surnia to 2015-10-22 with this (r3) recovery on an encrypted device had no flaws ... Yeehaaa!
[E 2015 Android Development] jasdeep singh:
deleted
[E 2015 Android Development] squid2:
SELinux Breakage

I just notices that a change I had made to the recovery's kernel in the last (r3) build resulted in an undesirable side effect. I had disabled SELinux in the recovery kernel, and that resulted in created files and directories having an unlabeled SELinux context. This broke installation of the WiFi driver in my "Squid Kernel". I'll be posting a new build soon to fix this issue.
[E 2015 Android Development] squid2:
Squid TWRP r4 for surnia

I've posted a new TWRP build to fix the SELinux issues in yesterday's build.
[E 2015 Android Development] yelupic:
I've tested the r4 recovery with

a clean install of cm-12.1-20151024-NIGHTLY-surnia => WiFi ok

followed by flashing kernel r10b => WiFi ok

(Re-)Booting into/from recovery, restoring, backing up => ok

_

Encryption problems (due to own dumbness using kernel r10b):

I had a message "your password is ok, but your data is corrupted" with an encrypted device right after flashing the r4 recovery (which worked before with r3) and had to factory reset the device and to restore an older twrp backup

[*]A new encryption of that restored backup resulted in an error "Encryption unsuccessful - Encryption was interrupted and can't complete... [RESET PHONE]"

[*]After following the advice to reset the phone (which kept its r10b kernel), I tried to encrypt the device again directly right after skipping all settings. - The encryption procedure led to the same error message.

[*]Then I wiped the whole device in TWRP r4 and flashed the nightly again via sideload, which finally did the trick (= not using the r10b kernel)

[*]After the successful encryption, I flashed the kernel r10b via adb sideload and had the old error from above

_

Then I started to think: After flashing the new kernel r10c I had no more self-inflicted headaches (sorry for the noise)

Thank you for your fast WiFi fix.

_
[E 2015 Android Development] MarquesYOLO:
How I install new build? Simply flashing from previous or I have to do something else? Thanks.

Sorry for my bad english.
[E 2015 Android Development] EB20XY:
so, the message in first post is wrong now ? :confused:

"Status: Stable

Current Stable Version: 2.8.7-r3

Stable Release Date: 2015-10-23"
[E 2015 Android Development] squid2:
Oh, I forgot to update that part. Will do so now.
[E 2015 Android Development] nandofer:
This recovery is the best ever. wipes so fast:o
[E 2015 Android Development] cmason37:
The latest build still freezes with Aroma. When I update opengapps, I have to flash the Android Fourms build, then flash this one back.
[E 2015 Android Development] squid2:
New TWRP Build with Aroma support

I've posted a new build (2.8.7-r5) that works around an issue that prevented the Aroma installer from starting. There is still a bug with Aroma where is hangs if you try to exit the installer before completing installation, but that's an Aroma or TWRP bug, and there's not much I can do about it. You can at least install Aroma packages if you go through the full wizard.

Aroma hangs when used with hardware overlays on a newer Qualcomm device, so I had to disable hardware overlays to make it work. Aroma's code is in need of patching to properly support newer chipsets.
[E 2015 Android Development] yelupic:
I don't know, if this is only occasional or if there is a pattern. - With r4 and activated screensaver (after 60 secs) it happened to me two times (randomly, not in a row), that a (encrypted) backup of system, data, boot proceeded until data and got stuck there. - I had to cancel the backup, reboot the recovery and repeat. - Without screensaver (or by touching/scrolling the on display log before the screensaver gets triggered), the backup runs through as intended. (Before installing a TWRP recovery I also delete ".twrps" in all locations.)
[E 2015 Android Development] xpmule:
Thanks again for the update(s) Squid :)

Also can i suggest when you update the version info on post #1

You mention updating instructions ?

I am assuming just go ahead and overwrite the old TWRP version.
[E 2015 Android Development] conductive:
I flashed the recovery, TWRP popped up and I was able to make a backup but now I can't enter TWRP and and can not upgrade SuperSU. What is up abd/or what do I need to do to get TWRP back?

Thanks

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

fastboot boot Downloads/twrp-surnia-2.8.7-r5.imgdownloading 'boot.img'...

OKAY [ 0.309s]

booting...

OKAY [ 0.652s]

finished. total time: 0.961s
[E 2015 Android Development] pdiddyfan:
I installed this recovery along with the latest cyanogenmod nightly and I'm getting bootloops. It boot loops into recovery and just runs open recovery script. Once I get back to a working recovery, it can't mount anything. xt1526
[E 2015 Android Development] pdiddyfan:
Any version that is specific to variant xt1526?
[E 2015 Android Development] jacoghi:
Files created / modified by this recovery can't be seen / touched by the Os. Is that the intended behavior? Never seen twrp behaving this way.
[E 2015 Android Development] yelupic:
Boot into TWRP Recovery

Either

1. with computer (and adb root shell)

Connect to USB

Mount > Disable MTP (must show Enable MTP afterwards - to have adb working)

Open a command window on your computer and type the following commands:

___

adb shell

restorecon -FR /data/media/0

chown -R media_rw:media_rw /sdcard/TWRP

ls -la -R /sdcard/TWRP

exit

___

Reboot and test with a file explorer on your phone/computer.

or

2. standalone without USB/computer

Advanced > Terminal Command > /sdcard > Select

Then type the following commands and hit the Enter key one by one:

restorecon -FR /data/media/0

chown -R media_rw:media_rw /sdcard/TWRP

ls -la -R /sdcard/TWRP

Reboot and test with a file explorer on your phone/computer.
[E 2015 Android Development] xpmule:
@OP

twrp-surnia-2.8.7-r5.img

You forgot to update the first post with new version number ;)
[E 2015 Android Development] squid2:
Surnia TWRP 2.8.7-r6

I've posted a new TWRP build with various improvements. It's built from TWRP's Marshmallow branch and has assorted updates and fixes throughout the code base, along with a new user interface. The version number is still 2.8.7.0, and the way things have been going it looks like it may stay at 2.8.7.0 forever, but don't let the version number fool you. Substantial improvement has been underway and this release is visibly different from earlier builds.
[E 2015 Android Development] starkly_raving:
Still compatible with 5.1.X?
[E 2015 Android Development] squid2:
Yes, it should be independent of the ROM.
[E 2015 Android Development] EB20XY:
the new R6 is really interesting and great !

Thank you for the support. :highfive:
[E 2015 Android Development] :
Just flashed it. Looks good.
[E 2015 Android Development] Agusyc:
I don't have a PC in this house (My dad's) so I can't flash it D,':
[E 2015 Android Development] starkly_raving:
Can't you use flashify from market?

---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------

Here's a flashable I put together.

https://drive.google.com/file/d/0B46DbOH2IgChRmZHVG9feVVsZWs/view?usp=docslist_api
[E 2015 Android Development] DroidFreak32:
You can flash it using the older twrp too.. Just switch to " images" at the bottom right of the install section
[E 2015 Android Development] Agusyc:
Oh, I thought that if I flash it from TWRP, it will cause problems, because it's trying to replace the recovery that is in usage
[E 2015 Android Development] starkly_raving:
Nope you can flash via twrp then reboot to recovery within twrp for testing.[emoji106]
[E 2015 Android Development] :
You can flash boot while booted into a system ;) so this goes same way [emoji14]
[E 2015 Android Development] till22:
TWRP now looks actually quite good, nice work!

Sent from mobile, excuse brevity.
[E 2015 Android Development] Agusyc:
Ok, thanks. I've already flashed it. It works perfect.
[E 2015 Android Development] starkly_raving:
It's working well...about time they gave it a cosmetic overhaul...I think its had the same GUI since ICS lol... Good job [MENTION=6485916]squid2[/MENTION]
[E 2015 Android Development] Joseluize:
Pero qué bonito les quedó el nuevo tema de TWRP. Looks great the last update. Thank you.
[E 2015 Android Development] starkly_raving:
[MENTION=6485916]squid2[/MENTION] do you think twrp will be able to decrypt the adopted storage? While the adopted storage is brilliant... If you're rooted and can't access it via recovery... #sadpanda [emoji209]
[E 2015 Android Development] gameSTICKER:
I have a secondary ext4 partition on my SD Card (created using 'aparted') and I've moved a couple of apps to this partition (using 'link2sd'). However when create a TWRP backup, my secondary partition is not displayed, not backed up and hence not restored. I tried to dig into TWRP settings, but I don't see any option to backup secondary partition. Am I missing something?
[E 2015 Android Development] prbassplayer:
Why do that when android supports moving apps to extsdcard on itself?
[E 2015 Android Development] dandrumheller:
Link2sd does a much better job of saving space on internal than the built in Android apps to SD system.

I'm not familiar with twrp being able to back up external ext4 partitions. I think the assumption is that since its on external storage you can back it up yourself. Are you routinely wiping your external ext4 partition?
[E 2015 Android Development] prbassplayer:
Is it really that much better and worth the hassle? O_o
[E 2015 Android Development] gameSTICKER:
Moving app to SD using native android method moves only parts of the apps to SD, while other parts of the app stay on internal memory. Link2SD moves every bit of the app to SD. Moto E has very limited internal memory, hence something like Link2SD becomes important.

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

I need to backup sd-ext coz if I fresh-install another ROM, all the apps on sd-ext becomes invalid, and if you want to move any more apps from the new ROM, you need to clean up the old data on sd-ext.
[E 2015 Android Development] prbassplayer:
Hmm honestly don't see the need with my usage, but to be fair I don't have a single game on my phone. Seems like way to much trouble specially if you jump across roms alot. Anyway doubt twrp would support backing it up anyways. Unless you get one of the head honchos to implement it, or squid moves away stock twrp.
[E 2015 Android Development] gameSTICKER:
Have a look at the screenshot, native A2SD method only moves APK and LIB, while DEX, DATA and CACHE still stays on internal. About 1 years ago (while I was still using a Xperia, before moving to WP) I was able to backup ext partition using CWM. Anyways, I'll try to stick to A2SD until someone can suggest a solution. Thanks guys!
[E 2015 Android Development] dandrumheller:
That makes sense. I was using link2sd mostly on my aria, so did fresh installs every time I switched roms. But that was only a few apps, and very infrequent changes.

I'm on MM on my moto e, so no link2sd for me. Adopted storage isn't ideal, so I'm running my SD as portable and living with the limited internal storage. My minimal daily driver app load is eating 4gb of the available 5. Tolerable but not ideal. Big change from my normal daily driver, a 128gb S6.
[E 2015 Android Development] gameSTICKER:
I just checked and the apps moved to SD card using native Android move-to-sd (A2SD) are also not backed up. I have a simple test case:

1. Install app XYZ
2. Move app XYZ to SD card using native A2SD or 3rd party Link2SD method (any one)
3. Take a full backup from recovery, reboot
4. Uninstall app XYZ
5. Do a full restore from recovery, reboot
6. Check if app XYZ is present or not

Some research shows that 2nd partition (sd-ext) backups were at least available in (very?) old versions of TWRP (refer attachment)

With all due respect to [MENTION=6485916]squid2[/MENTION], I understand that this might be the acceptable default behaviour in the recent versions of TWRP. My point is that in the current state (without sd-ext backups), recovery backups becomes far less useful. Only internal memory apps are backed up, apps moved to SD card using native A2SD or 3rd party Link2SD methods are NOT backed up.

Given how small Moto E internal memory is, it's very common to keep lots of apps on external memory. If somehow we can enable external memory apps backup, this will be very useful for many Moto E users.
[E 2015 Android Development] squid2:
That would be useful. It's something that would need to be implemented in TWRP, and I expect someone to do it this year. I've just been building TWRP as is for various devices and not adding or removing any features myself.
[E 2015 Android Development] gameSTICKER:
I had a look at cybojenix's TWRP fstab and there is an entry for sd-ext, which is not there in squid2's TWRP fstab.

I went into squid2's TWRP terminal and I was able to mount my sd-ext partition, but it did not appear in backup screen. Hopefully it might be an easy process to enable sd-ext backup?
[E 2015 Android Development] magdeoz:
check this: https://gerrit.omnirom.org/#/c/15921/

although it is still a work in progress might try
[E 2015 Android Development] gameSTICKER:
EUREKA!!!!!

SD-Ext backup is supported in SuperR's 2.8.7.0 TWRP, but it's June 2015 build. [MENTION=6485916]squid2[/MENTION] is there any way you can include this feature in your recovery? Please :fingers-crossed::fingers-crossed::fingers-crossed:
[E 2015 Android Development] squid2:
Surnia TWRP 2.8.7-r7

I've posted a new TWRP build with bug fixes and new features. The most notable changes include:

Fixed support for ExFAT SD cards

Built in terminal accessible from the TWRP GUI

Experimental, untested, and probably incomplete support for Marshmallow adopted storage