yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] Ravx:
No I don't think memory leak causes that much lag. There is some other problem. I am pretty sure.

---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------

Thank you bro you saved is all.

---------- Post added at 07:21 AM ---------- Previous post was at 07:20 AM ----------

Love it bro you are a life saver.
[E 2015 Original Android Development] squid2:
CWM Recivery for Otus

I don't have a CyanogenMod ROM ready yet (it will take some time), but in the interim, for those who for whatever odd reason prefer CWM over TWRP, here is a CWM touch recovery for otus that I built with my CM12.1 tree. It seems to boot, though that's all the testing I've done.

Download Link: http://www.mediafire.com/download/r21bucvh93gz6lk/cwm-20150427-otus.img

Functionally untested, use at your own risk. 3G model only.

UPDATE: Don't use this recovery. The posted version has an incorrect fstab. I'll post a CWM that works in a few days after I test.
[E 2015 Original Android Development] squid2:
CM12.1: Coming Soon

[IMG="CyangoenMod 12.1 on Otus"]http://i.imgur.com/fwHbX4I.png[/IMG]
[E 2015 Original Android Development] Ravx:
Can't wait to flash it on my phone. Thank you bro...
[E 2015 Original Android Development] Ravx:
When are you going to upload it. Excited to try it out.
[E 2015 Original Android Development] ShyPixie:
Congrats, everything works now.
[E 2015 Original Android Development] SidedX:
Doesn't work for me. I flash recovery and it says OKAY for everything, but nothing happens. Cannot boot into TWRP no matter how many times I do this.

[IMG="recovery does nothing"]http://s9.postimg.org/mwrgn6oou/Untitled.jpg[/IMG]
[E 2015 Original Android Development] squid2:
Your screenshot shows that it flashes correctly. After flashing, you just need to select the recovery on the phone's bootloader menu (by pressing the volume down key), then press volume up to boot the recovery after you selected the recovery menu item.
[E 2015 Original Android Development] SidedX:
I pressed volume up, and it shows the Android on his back with the red exclamation point.

Didn't know volume up was select though, thanks. Still can't get TWRP on there though.

---------- Post added at 07:35 PM ---------- Previous post was at 06:43 PM ----------

After installing generic ADB drivers, it worked, sorry for the irrelevant posting, I should have tried that first.
[E 2015 Original Android Development] Pratham Nathyal:
Post deleted
[E 2015 Original Android Development] squid2:
New TWRP build

I've posted a new build of this recovery that fixes reporting of the time and date. Now your backups will have correct times and dates on them. I now consider this recovery stable, so the new build is just called twrp-otus-2.8.6.img with no test designator.
[E 2015 Original Android Development] SpiralX15:
http://xdaforums.com/devdb/project/dl/?id=11977

This recovery is not working when I try locking my Moto E 2nd Gen 3G.
[E 2015 Original Android Development] squid2:
When locking the bootloader, the recovery must match your CID. The linked stock recovery is for the Latin American XT1506 model. The signatures for other models (such as XT1505, XT1511, and the Indian XT1506) are different. You will need to get a stock recovery signed for your model.
[E 2015 Original Android Development] SpiralX15:
Do you know where I can find a XT1506 stock recovery?
[E 2015 Original Android Development] PseudoDev:
My phone didnt boot up in your latest image.

but it did boot on the twrp test5.img .
[E 2015 Original Android Development] SpiralX15:
That's the otus version.

Sent from my Moto E2 XT1506.
[E 2015 Original Android Development] squid2:
New TWRP 2.8.7.0 build

I've posted a new build of TWRP 2.8.7.0 for otus. Apart from the newer TWRP version (and associated TWRP improvements), I have not made any changes to the recovery since the last build. Downloads are up on the downloads tab.
[E 2015 Original Android Development] silentvisitor:
Recovery does not boot

Hello friends,

Need your help.

I unlocked my cousin's Moto E 2015 (OTUS) bootloader and went on to flash TWRP 2.8.7 from here. Recovery flashed successfully.

Then I tried booting into Recovery by Vol - and then Vol+ (to select). Phone switched off. Had to power it on.

Second attempt, it showed me Android logo with no command. I pressed Vol+ for 15 sec and then pressed Power button for few seconds (as read here in forum). Nothing. Phone booted normally.

Please advise !

I am planning to flash crDroid on his phone. Recommendations for ROMs are also most welcome :)

Thank you !
[E 2015 Original Android Development] Ravx:
If u are trying to get into bootloader or recovery. Press power button+volume down simultaneously for few second and let go. I don't know of crdroid is out. But Cm is a good option currently.
[E 2015 Original Android Development] silentvisitor:
I resolved my issue :)

Problem was recovery wasn't getting flashed though phone and fastboot showed it did.

How I came to know ?

I flashed recovery amd then entered in it and was greeted by Android logo with command not found (simply means it couldn't find recovery). Then I pressed Power button for 3 seconds and just once pressed Vol Up button. Voilà.... I was in Recovery. But.....stock :p

I decided to flash again but this time I remembered something from my past experience with HTC Sensation.

After connecting device I first issued fastboot devices and......no device. This was the problem. I tried again. Nothing. Again tried and this time it showed up. Then I flashed Recovery which successfully flashed and cousin currently rocking RR 5.5.1 ;)

Thanks to everyone who shares their findings and experiences here :good:
[E 2015 Original Android Development] squid2:
New 2.8.7-r2 release

I've posted a new build that adds support for hardware encryption. Users who have turned on user data encryption on the stock ROM will now be able to enter their password into TWRP and access their encrypted data. Be aware that the encryption support in TWRP itself is still a bit immature and kludgy. You will see a keyboard asking for a password regardless of the type of lockscreen you have set up (PIN/Password/Swipe). For a numeric PIN, type in your PIN using the keyboard that appears. For a 3x3 swipe pattern, the 9 points in the grid correspond to the numbers 1-9.

I also cleaned up the kernel configuration, taking out unnecessary features to reduce kernel size. In addition, I switched to using better compression algorithms for the kernel and ramdisk to further reduce size. As a result of these optimizations, the new recovery is much smaller than the previous builds (6.7 MB instead of 9.1 MB).

I haven't yet added encryption support to CyanogenMod, but I'm working on it.

EDIT: I've noticed that the reboot into system function is broken right now. I've pulled this built till I fix it.

EDIT 2: Never mind, it works fine, my phone was just in a weird state. I've posted it back up.
[E 2015 Original Android Development] IronTechmonkey:
I had something similar happen. Rooting and unlocking bootloader went OK but recovery seemed to be a partial installation. I managed to accidentally get into the interface once but, having never seen it before, did not realize what it was.I tried so many things that I forgot which actually resolved this but these three thing helped:

1) Thorough windows PC driver cleanup. In the past I've seen driver combinations that worked for daily use fail for ADB stuff (and for utilities that allowed my past phone to connect to PC by mass storage mode). For people on Windows Vista/7 PCs (not sure about 8 or 10) you can clean old drivers like so (but BE WARNED - when viewing the device manager this way you CAN remove things you computer really needs but since you are here and flashing ROMS y'all can dig this):

- Run these 2 commands from an administrative command prompt. "set devmgr_show_nonpresent_devices=1" and "devmgmt.msc" The device manager will open.

- Use menus in Device Manager to Show hidden devices.

- Remove greyed out entries for anything pertinent to your phone's connection to the PC (ONLY ITEMS YOU RECOGNIZE WHICH RELATE TO PHONE).

2) Removal of Motorola Device manager and installation of v2.60 Moto drivers for this phone.

3) The use of TWRP 2.8.7 instead of 2.8.7R2

I just ran my second seemingly successful backup with this (although I've not yet tested a restore). Assuming restore works OK will be trying to install CM12 Condor and Gapps with it. I've also run a successful Dalvik & Cache wipe.

One question - Have people been able to install CM12 and Gapps through this recovery? I'm accustomed to doing that with PT on my previous phone but have heard in some cases it's better to push from PC instead.

BTW Thanks a bunch for this thread. Mwahh!

<EDIT - Recovery OK in simple test. Wahoooo, and thanks again.>
[E 2015 Original Android Development] IronTechmonkey:
Although TWRP otus 2.8.7 is working for backup and restore on stock Moto E XT1511, there is a lot of confusion about and absent details when describing items that might be flashed with it, and the XT1511 is behind others in dev. Stock not yet leasked and nothing for it in CM.

With clarity of model #s in mind, here is a list of the 9 (yes nine) different models of Moto E: http://xdaforums.com/moto-e/orig-development/moto-e-model-list-t3195889/post62711847#post62711847.
[E 2015 Original Android Development] magdeoz:
hey man, you are doing too much spam in all forums, part I think the thread is in the wrong section
[E 2015 Original Android Development] IronTechmonkey:
[MENTION=6485916]squid2[/MENTION] - Since you've been so accommodating to my questions in the ROM thread...

Before flashing that ROM I'm updating from twrp-otus-2.8.7.img to twrp-otus-2.8.7-r2.img and confirming by testing that it will properly backup and restore from stock before proceeding to CM. I notice that the "secure" partition does not appear as an option in twrp-otus-2.8.7-r2.img where it did in twrp-otus-2.8.7.img. I'm curious about the significance of that and whether or not I've done any unseen damage by including that partition in previous backup/restores?

---------- Post added at 06:04 PM ---------- Previous post was at 05:45 PM ----------

Already addressed and moved by mods. Also, I'm not spamming. I'm providing information that should already be present in any firmware offering or supporting thread. With a chart, people who maintain the threads and people who don't want to brick devices because someone carelessly said "just use the 2015" version (or something like that) might be able to find and flash the appropriate items. I have not linked to that thread anywhere that the model #s and types are clearly described. I have linked to it at threads where I was given incorrect information about matching model #s and firmware. Even your own sig could use those details ;)
[E 2015 Original Android Development] squid2:
The android-secure "partition" was just a folder on your SD card. I had removed it from the fstab. You haven't damaged anything.
[E 2015 Original Android Development] IronTechmonkey:
Thanks, I've been including it in backups but it sounds like I no longer need to. I'm at another bump in the road now where I've flashed twrp-otus-2.8.7-r2.img, then created a backup in that version of TWRP, but when trying to restore backups created by either version of TWRP I get error "e: cannot restore system - - mounted read only".

Flashed back to twrp-otus-2.8.7.img and can now successfully restore a previous backup backup created that version of TWRP. I guess I can just try flashing CM12.1 and Gapps with twrp-otus-2.8.7.img but I'm curious about what causes system partition to be perceived as being mounted as read only.

In any event thanks for the resources and the advice.

[EDIT 9/8/15 12:30pm EST] Derp. It's glaringly obvious (now that I realize) the problem installing had to do with the TWRP setting to keep system read only. With TWRP 2.8.7.0r2 I've successfully flashed your 9/5 build and CM gapps. Now getting down and dirty with testing smaller ROM details. Among 100 or more test points, 2 particular things I'm looking at are how well the FM radio works in CM and if this ROM managed to avoid a recent CM issue where there was long delay to wake screen during incoming or ongoing call.

As to "android secure": when I test restored a backup that included android-secure and was created with TWRP 2.8.7 in TWRP 2.8.7r2 I got an error about there being no location with that name but the restored backup ran OK and everything else seemed to flash OK.

Glad to be back on CM - I really missed those little keyboard cursor left/right arrow. Thanks for this ROM!
[E 2015 Original Android Development] IronTechmonkey:
Is there any way to tell, from within TWRP or from raw files on the device, whether 2.8.7 or 2.8.7r2 is installed? The last_log file reports 2.8.7, but both 2.8.7 and 2.8.7r2 report v2.8.7 when booted from fastboot. I confirmed that I had the fastboot into twrp procedure correct by also testing 2.8.6 which did report as 2.8.6. Whatever is installed has been working fine for CM12.1 and CM13. I'm just curious.
[E 2015 Original Android Development] squid2:
There's no obvious way unfortunately, apart from encryption working or not. You may be able to tell by checking for encryption related files I changed in the recovery between versions, but apart from that both would be considered to be version 2.8.7.0. The r1 and r2 designators are just my own build revisions. It shouldn't hurt to just flash the latest one on top of whichever is currently installed.
[E 2015 Original Android Development] IronTechmonkey:
Since that previous encryption test worked I must have been using r2 but just to be sure I re-installed it. Thanks.
[E 2015 Original Android Development] RavikumarG:
Hi dude,

Don't know whati did with my moto e 3g 2015, when I'm installing custom ROM, saying "failed to mount /data".

Please help me to fix the problem.
[E 2015 Original Android Development] IronTechmonkey:
[MENTION=6485916]squid2[/MENTION]. Apologies if this was answered somewhere, but I've searched many Otus, TWRP & other threads to no avail. I may be working on a new XT1511 which I'd like to keep within warranty for at least a short while (to clear the way for a dialog I'm having with Motorola about OS updates). Is it possible to flash CM12.1 (and maybe SuperSU) via "fastboot boot twrp-otus-2.8.7-r2.img" to avoid unlocking bootloader or does that level of flashing require an operable TWRP on the device? Also, could a nandroid backup of unrooted stock be made by that method? If not I'll just unlock and flash as before. Tx.

[EDIT] I've found material describing how to use ADB with TWRP 2.8.x to perform tasks from the PC via ADB but that clearly requires TWRP on the device so the best I may be able to do is keep stock un-rooted, and unlock bootloader then install TWRP for backups and flashing. Does that sound about right to you?
[E 2015 Original Android Development] squid2:
Unfortunately, you do need to unlock the bootloader to even be able to boot TWRP. You can boot or install TWRP without rooting your device though. You can back up your unrooted system using TWRP as well after unlocking the bootloader. What I usually do is leave new devices I buy unrooted and bootloader locked for the first couple weeks in case a hardware defect pops up, and then go ahead and unlock it after the delay once I feel reasonably confident that the hardware isn't defective.
[E 2015 Original Android Development] IronTechmonkey:
That is sort of where I ended up: Unlocked BL, captured backups of stock without and with root before proceding. Although it is best practice and good advice, I did skip the sustained hardware test of stock. I usually do that as well, and would have this time for a more expensive or less urgently needed device. Thanks for the coaching and confirmation. It's a testament to the stability of CM12.1 on this device that clean flashing it is all yawns:).
[E 2015 Original Android Development] squid2:
Otus TWRP 2.8.7-r3

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 Original Android Development] squid2:
Otus TWRP 2.8.7-r4

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
[E 2015 Original Android Development] santoshx99:
[MENTION=6485916]squid2[/MENTION] TWRP 2.8.7-r4 supports exFat in Recovery. What If i format my Sandisk Ultra 32gb SDHC card (Fat32) to (exFat) partition, Could I able to use it on CM13 ROM or not? If yes, than Should I format it on windows 7/8/10 legacy format option or any other tool?

I heard that exFat is better than Fat32 and can handle large data files at good speed. Pls. tell me.
[E 2015 Original Android Development] santoshx99:
[MENTION=6485916]squid2[/MENTION] Teamwin has updated their recovery source to 3.0.0 pls. can u update the recovery to 3.0.0 for otus.
[E 2015 Original Android Development] Casper1982:
+1 :good:
[E 2015 Original Android Development] PriPhaze:
It was announced yesterday and you guys are already asking for the update? Jeez is not like squid is un aware that they updated TWRP . You dont need to come to askf or something he will probably work on eventually as is an important update
[E 2015 Original Android Development] magdeoz:
for those who can not wait a bit

I did a version of TWRP 3.0.0 using the device tree squid.

If not up to date, but should work.

LINK: TWRP_3.0.0-otus
[E 2015 Original Android Development] santoshx99:
I installed this recovery on my device. The material design is amazing. Everything is working fine.
[E 2015 Original 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 it 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 Original 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. I fixed encryption support for otus on CM13. 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 Original Android Development] rajit:
broda any luck on multirom ?
[E 2015 Original Android Development] IronTechmonkey:
[MENTION=6485916]squid2[/MENTION]: In the Adaway thread a user claimed that their version of TWRP 3.0 (most likely not your version) is not properly clearing cache and dalvik. I've had no problems with your version through a few CM13 tests and restorations to CM12.1 and multiple cache clearing, but have a question based on that user's report. Is there a way to determine if TWRP is properly clearing cache and dalvik other than seeing the the system rebuild the app cache upon first boot after clearing it? Thanks.
[E 2015 Original Android Development] IronTechmonkey:
In regards to twrp-otus-3.4.5-r1.img from 2/10/16 and twrp-otus-3.0.0-r2.img from 2/13/16. Is the lower version # of the 2/13/16 release just a return to the standard versioning but still newer than the one from 2/10/16? I missed the "cave" joke at the time (although it was funny) and was mistakenly using twrp-otus-3.4.5-r1 and just wanted to make sure that twrp-otus-3.0.0-r2.img is the newest and the one I should be using.
[E 2015 Original Android Development] squid2:
Yes, 3.0.0-r2 is the newest.
[E 2015 Original Android Development] IronTechmonkey:
Thanks. I'm chasing an issue where after installing 3.4.5-r1 a couple of my TWRP backups on the external SD (created before I installed 3.4.5-r1) stopped appearing when the directory is viewed through USB connection while still being visible in device file managers and in booted TWRP. I had to delete them on device and copy them back through a USB connection to get them to appear through USB connection. I have not been able to reproduce the issue and it has not occurred again.
[E 2015 Original Android Development] ÀnkanKoley:
I have a question. If I format my sd card as internal storage in Marshmallow, will it be still able to take nandroid backup/Flash Rom In TWRP?
[E 2015 Original Android Development] squid2:
Squid TWRP 3.0.1-r1

I've posted a new build from my TWRP fork. It's functionally equivalent to the upstream 3.0.1-0 release, though my fork has a few additional changes and cleanups. For this release, I have created a new dark green theme for my fork. I hope you like it. The download for this build is a bit bigger than earlier versions because of extra assets added for my theme.
[E 2015 Original Android Development] squid2:
Squid TWRP 3.0.2-r1

The issue that prompted this release is a regression in 3.0.1 that broke password entry. I found the bug, fixed it, and my fix has also been merged upstream. However, I took this opportunity to improve various other things. I added in power management (frequency scaling and hotplug) to reduce the battery consumption of recovery. I did some cleanup and optimization to reduce the size of the recovery. I tweaked the theme a bit. I also updated various translations from the upstream gerrit.

On otus, I also updated the kernel to the latest version used by CM13.