yashsingh1/xdaforums huggingface dataset:
[E 2015 Android Development] xpmule:
I am on the same path you mentioned ;)

I just flashed that exact version but it wouldn't boot.

I hope i understood correctly that the newer separate "systemless" binaries have a built-in bootloader patcher?

many sites offer info on it but they also link to those patched bootloader files and say you HAVE to install those.

They are telling people this all over the web... still.

Here is how i loop around so i am on-topic ;)

I am just reading a topic that says you need to be rooted for the TWRP to "stick"

It seems there is plenty of people having the same exact identical problem as me.

I have a backup with SuperSU and TWRP running great aside from a petty little time bug ;)

So i can and have been restoring that when i get tired of fighting with Marshmallow LOL

My persistence will find any info that is out there :)

Someone posted a suggestion i am trying out right now.. wish me luck.

About the TWRP not sticking Issue.

And i thought it was interesting how some guy said the OS can restore the ORIGINAL recovery

Which is what i am seeing instead of TWRP (after first boot)

And yes i have been going straight to TWRP a couple times in a row before even going to the OS.

Weird because i assumed before that TWRP overwrote the original recovery.. i guess not LOL

It must divert the loader and redirect it or the original recovery is ALSO embedded into the OS.

Because where else would it come from? LOL

Which meeeeeans i may have done something bad before !

I had for ages now been replacing the recovery.img when i flash the firmware with the TWRP one.

Just to be safe in the future i will do the proper orig one then do TWRP after..

And yes i tested that already re-flashing the original one a few times.

I already tested using adb to flash the original then the TWRP one right after

and variations etc

EDIT:

Ok weird, i tried again and it *seems* to be sticking now (current Squid TWRP + Marshmallow)

What i did was use ADB to flash the stock recovery then right after i flashed the TWRP

then i hit eject on Windows 7 and started TWRP and i selected Reset my settings in TWRP..

i selected restart into Recovery then i went and booted system and then back to recovery again

expecting to see "no command" but i did not :)

I retested this 3x in a row and it is working now hooray :)
[E 2015 Android Development] aksclusive:
Thanks man for the link
[E 2015 Android Development] bloodsaw:
lol I see you found the solution before I could wake up and post it :P yeah the issue with TWRP not sticking is it needs to overwrite the original stock recovery therefore you need to have the stock recovery installed before flashing TWRP over, then once TWRP has been initially flashed you boot into TWRP and tell it to overwrite the stock recovery and everything should work fine. Did you make sure to install SuperSU from the play store before flashing the v2.67 .zip file? I tried using the apk included within the .zip file and it caused nothing but bootloops so I installed it from the playstore attempted to install SU to /system/bin/su once it failed I in booted into recovery and flashed the 2.67 zip and it worked like a charm I just found that the phone really slows down after it is installed so I stopped using it

I was only using SuperSU for 2 reasons, 1)I like the popup notification it uses. 2)so I could use liveboot which for any geek/nerd looks really cool, screw a boot animation being able to look at your system booting up as if it were an old linux computer is great :D
[E 2015 Android Development] xpmule:
[MENTION=4038530]bloodsaw[/MENTION]

It's weird because i had obviously at different points had the original recovery on my phone.

The way some of this stuff works is a mystery to us really.

Like think about what i said earlier..

If TWRP overwrites the original then how is it the original can be restored after with out flashing it again?

This is a contradiction big time. LOL

In other words it can't really sort of.. If it DOES in fact really gets overwritten 100%

Then the original getting triggered would have to come from somewhere.. where?

See what i am saying guys?

I have seen people say they had weird behavior going on like they had an OTA update

and when they woke up TWRP was gone.. problem is the OTA doesn't flash the recovery.

also..

I have installed 6.0 over top of 5.1 or.. flashed 5.1 over 5.0 or restored from a backup

and what do i see? a Moto prompt telling me to uninstall sensor firmware.

So think about it.. how did that "persist" ? It's CRAZY !

And about SuperSU

First off i noticed no speed problem at all with Marshmallow.. it's running fast as hell.

And no offense but i think you did it wrong.. chainfire says DO NOT use the Play-Store version.

That maybe part of the reason you seen speed issues.

The play store version has no support for a systemless install.

The systemless install versions are a separate version entirely.

I am surprised doing that would work and not screw up your OS so bad it wouldn't boot.

All you have to do is look at the flash logs in TWRP.

The bootloader has to be patched for one thing and the PlayStore version or "Stable" build editions can NOT do that.

I figured out by accident via a random web page for the Moto-G the install an old version trick..

For some weird reason that 2.6.2 "systemless special edition" WILL patch your bootloader.. when the current one will NOT.

And when i say current one i mean the 2.67 special systemless edition.

I HIGHLY advise people NOT to mix systemless versions with non-systemless versions.

Unless chainfire tells you to do it.. avoid it ;)

EDIT:

A quick update on the time bug i was having..

I noticed when i booted a fresh stock Marshmallow it failed to detect my time zone properly.

Then when i set it to -8 the OS no also shows 1 hour off.. weird.

I wonder if both "keep" time on their own or what (don't know how it all works under the hood)
[E 2015 Android Development] bloodsaw:
[MENTION=7004228]xpmule[/MENTION] the reason I suggested installing SuperSU from the playstore is when I did install the .zip it gave me a bootloop that was constantly optimizing the SuperSU .APK that came from the v2.67 .zip and I know from my previous phone(HTC ONE V) that installing from the play store then flashing the systemless v2.67 .zip makes SuperSU work without a bootloop because the app would already be optimized from being installed.

The only thing we can really do about figuring out the time issues and how that code works is by waiting for [MENTION=6485916]squid2[/MENTION] to chime in as to what happens in the code to make it all work.

On another note I met a girl today that has the XT1527(Wind Mobile) as well and she got an OTA 2 days ago that gave her android 6.0 not 6.0.1 but just 6.0
[E 2015 Android Development] ayush rao:
V 2.67 Never worked for me........ I always use V 2.65
[E 2015 Android Development] xpmule:
No offense but ask chainfire.. he will say that was a bad idea i bet.

The PlayStore version has nothing to do with install the systemless version.

I am surprised you did not screw up your phone doing that.

Seriously go tell him what you did and see what he says.

If your telling people to do that too i think that is seriously bad advice

and may explain why you were mentioning massive slow downs so bad you abandoned Marshmallow.

Where as i have seen NONE what so ever.. every aspect of my Marshmallow install is working fast

AND i installed properly according to advice from chainfire.

I read almost every word he said on a many topics he made on this as well as many comments he posted

on the beta topic and comments he made on it arguing with the guy who claims chainfire stole his work.

It's getting a tad on the off-topic side that is for damn sure but i concerned about giving BAD advice.

Best i can tell the method you said is a bad idea..

The PlayStore version is not compatible with Marshmallow so your not suppose to be installing it.

The method i -DID- mention is a proper clean & safe way of doing it.. using the files you are suppose to use.

You said you had to do that because you got a boot loop well so did i doing the same thing.

WHY ?

I could see looking at the logs doing it that the systemless 2.67 version does a non-systemless install.

This triggers the new bootloader related security in Marshmallow then stops it from booting.

So it really is not possible at all that the playstore would help you get it working.

installing 2.62-2 works because it actually does what 2.67 is SUPPOSE to but fails for some reason.

So essentially what that install twice trick does is simply installs a PROPER clean systemless install

and installing 2.67 right after simply UPDATES it.

You can see what i said by looking at the logs then going and looking at chainfires beta topics on the matter.

If you go and ask him i bet anything he is going to say there is a bug in 2.67.

EDIT:

The Time bug plagues me and mocks me ROFL

I updated my custom bootlogo a couple times going to the bootloader and check the logo with TWRP.

And what do i see ?

The time is set wrong (with -7)

Now it is off an hour and i look then set it to -8 (as it's suppose to be) and the time is now correct.

SO WEIRD !

So i pretty much did NOTHING different but boot TWRP to see it fixed itself hahahha

Then i thought well hmm since the OS was having the same problem i was curious..

So i loaded Android up and checked and it's still off an hour LOL

SO i have TWRP as -8 and the OS as -7 (so the time matches my clocks & time online etc)

Hilarious LOL
[E 2015 Android Development] bloodsaw:
yeah like I said TWRP for some reason likes to fix the time by itself after a while

If you think what I had said to do with SuperSU was bad I'll take your word for it. I didn't move away from marshmallow I just stopped using SuperSU and stuck with the Cyanogenmod SU binary.

Like I said before I was only using SuperSU for 2 reasons, 1 I like the notification dialog it gives compared to the notification dialog that CM SU uses and 2 I like using liveboot that chainfire has developed. those were the only reasons I had used it, So moving back to CM SU from SuperSU wasn't a huge deal for me.
[E 2015 Android Development] xpmule:
I am not going to keep going on and about installing SuperSU here unless it's related to TWRP.

There is a topic i made specifically on that in my SIG.

But i was surprised to see just now after going to the bootloader that my time is off by an hour again..

so back to -7 i go :eek:
[E 2015 Android Development] BillyMumphry:
[MENTION=7004228]xpmule[/MENTION] Glad to see you can keep your sense of humor through "your" issue. [emoji57] I'm in the same time zone as you (Victoria) and I'm glad to report (sorry) no issues here.
[E 2015 Android Development] spiked_mistborn:
For hash programs that support drag and drop, this works well too.

Open regedit.exe

Make a new key under Computer\HKEY_CLASSES_ROOT\*\shell called Hash, or Checksum, or whatever you want to call it.

Make a second key under your new key called command

Under command, change the Data for the (Default) entry to "C:\Program Files (x86)\HashCalc\HashCalc.exe" "%1" including all quotes. (point it to your hashing program)

You can now right-click on any file (or multiple files) and get your hash! It's hard to make it easier than that.

Very easy and useful for preventing strange behavior when flashing things on phones.
[E 2015 Android Development] xpmule:
That is cool but i would not want it.

I use a pile of Tools to strip out Context Extensions.

Other wise the list gets sick super long.

Also the program i shared has support for a pile of hashing algo's.

And you can't get easier than double clicking an .exe and dropping a file onto it.

..besides your way ;)

Thanks for sharing though i never heard of that method.

EDIT:

More importantly than HOW ?

is just DO IT !

I see a lot of people don't even bother :(
[E 2015 Android Development] lettucegoatee:
Hi,

I've got really slow loading times with this recovery. Over ten minutes of the logo screen. I've been using the last three versions as they become available and had the same loading times. Backups wipes and installs are taking their time too, but they all work.

I've been using Temasek's ROM, and performance has been great. Just slow recovery operation, and makes me a bit nervous to use it.

Is it the slow formatting problem? Any ideas or troubleshooting directions?
[E 2015 Android Development] sakdroid:
I have Sprint Moto E on Ringplus... I want to Install this Recovery.

In Download tab, i see

twrp-surnia-3.4.5-r1.img old dated but higher version

twrp-surnia-3.0.2-r1.img latest but lower version..

Which one to use?

Before flashing recovery, i should Unlock Bootloader right?

TIA
[E 2015 Android Development] Sher1234:
Go for 3.0.2-r1.img it's the latest & you should unlock bootloader before flashing
[E 2015 Android Development] Thexmastermind:
no flashy flashy

i've successfully installed the 4 most recent releases, but anytime i try to flash a rom, no matter what rom it is, my phone just reboots back into recovery again. i'm on xt1526 boost mobile.
[E 2015 Android Development] xpmule:
What does it say in the TWRP console after you hit "install" for the ROM ?
[E 2015 Android Development] Thexmastermind:
it goes on as normal, saying SELinux is present, and then the usual few lines after. then it goes blank and the twrp boot screen pops up. i can press the menu key at the bottom right to see it as a terminal, and it just says error no: (how ever many times i've retried)
[E 2015 Android Development] xpmule:
I'm a bit confused by what you are saying.

It sounds like you are saying it is not finishing flashing.

Have you been asking the dev or users of that ROM what they think about your problem?

I am not sure what to suggest but i was curious of you were getting an error code.

Then you could Google it etc.

Good luck maybe someone else can help you, i have little knowledge about installing ROMS.

If i were you i would bug the custom ROM dev.
[E 2015 Android Development] Thexmastermind:
oddly enough, after i reformatted my sd card, it began atleast giving me an error message. i googled the error(error 7) and used an older version of the rom, from back before it gained official status.

Edit: in twrp, i was also asked to boot into bootloader and enter the following text into a terminal:

fastboot oem config fsg-id boost

everything is fine now, and all is well in cosmos.
[E 2015 Android Development] FeRoCiiOuS:
Thanks, works great!
[E 2015 Android Development] AndersCF:
Isn't this a bit obsolete now that there's an official TWRP out for Surnia, even latest version?
[E 2015 Android Development] ayush rao:
The official TWRP isn't great. Squids TWRP is also up to date and usually has no bugs as compared to the official one
[E 2015 Android Development] AndersCF:
Ah sorry. For some reason didn't see that it had been updated. So the latest version of official TWRP is not good? Is it unreliable somehow?
[E 2015 Android Development] ayush rao:
I've had some problems with it but ur experience may vary
[E 2015 Android Development] DroidFreak32:
Not to mention the looks lol.. Squids twrp looks so much more better :P
[E 2015 Android Development] AndersCF:
Yeah, indeed. Just flashed the latest squid, it looks and runs very nicely :)
[E 2015 Android Development] cloudblue:
This may have been answered, but I aint reading 26 pages: Has anyone used this one with TWRP Manager by JMZ?
[E 2015 Android Development] kumaranwade:
Has function of installing super su ??
[E 2015 Android Development] DroidFreak32:
if you are asking what I think you're asking, then the answer is no. You've to flash supersu zip manually to install it ?
[E 2015 Android Development] cdnron:
I had an issue with the official TWRP where it could not unmount the /system partition. I couldn't mount the /system partition as r/w either. So, I couldn't wipe, couldn't install GAPPS (after an official CM update), couldn't flash any zips basically. Maybe I'll give this a try.
[E 2015 Android Development] hydeah:
I got the TWRP working on stock rom, google play is acting up and crashes on search. Can I just flash gapps overwriting all google apps over what I have on the device? Which gapps can I flash on stock rom on XT1526 (US Cellular)? Note that I do not and will not be using device for cellular/mobile voice/data. It's wifi only.
[E 2015 Android Development] ippon:
having some trouble with recovery.

my phone is behaving as if it has no recovery I am able to flash TWRP with adb, and it's functional, ie, flashing ROM, etc, but if I try to reboot into recovery or access it via Power/Volume Down, there is no recovery, and i only get 'no command' message.
[E 2015 Android Development] xtermmin:
Are you actually flashing TWRP, or are you just hot-booting into it? Reboot into bootloader and try flashing it with the following command:

fastboot flash recovery twrp.img
[E 2015 Android Development] bloodsaw:
adb.exe doesn't flash the recovery partition fastboot does

actually you should be using mfastboot for this device https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?pref=2&pli=1

use the command mfastboot devices to make sure fastboot is communicating with your device properly then proceed with the mfastboot flash recovery "recovery.img" command to flash the recovery to the device.

it is impossible to overwrite the recovery without an unlocked bootloader.

If your bootloader is locked i.e. you don't get a "Warning Bootloader has been unlocked" screen every time the phone starts up then you can use this tool to unlock your bootloader http://xdaforums.com/moto-e-2015/development/tool-moto-e-toolkit-one-click-unlock-t3047150 it supports flashing the recovery but I could never get it to flash the recovery.
[E 2015 Android Development] xtermmin:
When it comes to flashing recovery, Motorola Fastboot (mfastboot) and plain-old fastboot accomplish the same exact thing.
[E 2015 Android Development] ippon:
mfastboot is what i have been using to flash 'recovery.img'.

my bootloader is unlocked. i don't get the 'warning' screen, because i have replaced image. but my fastboot screen shows that my bootloader is unlocked.

and something changed last night. now every time the phone reboots, it goes to fastboot screen. i can press 'start' to boot the phone from there, but the phone isn't going straight to the OS.
[E 2015 Android Development] bloodsaw:
Sounds like you used the batch file on this page http://xdaforums.com/moto-e-2015/general/guide-restore-moto-e-2015-stock-firmware-t3044936 to reinstall the stock rom if you did it probably has to do with this line "mfastboot oem config carrier vzw" if you run this command "mfastboot erase carrier" it will erase the changes the "mfastboot oem config carrier vzw" command made
[E 2015 Android Development] ippon:
i tried that to see if i can return to stock, but the batch file didn't run properly either. it aborts before doing anything.

what's the best way to get this thing back to stock? it's Rogers phone, XT1527.

ran into a strange problem of being unable to unlock the phone too. the unlock code i bought does not work.

man, haven't had this much problem with Android phone in a long time.
[E 2015 Android Development] bloodsaw:
I have the ChatR locked one and my imei unlock codes bought from chatr never worked with CM I wonder if I need to be on stock for it to work.

run this command

mfastboot erase carrier

it should fix your weird boot up issue, I know when I used the original .bat file it did work for restoring the phone back to a stock rom but after that any time I restarted the phone TWRP would boot up instead of the installed Android OS and I had to go from TWRP to the bootloader and press the power button on the start option in order to boot up the Android OS.

here is the 6.0 stock rom for rogers phones https://www.androidfilehost.com/?fid=24459283995312546

copy and paste this into notepad save it as MotoEreturnToStock.bat

mfastboot oem fb_mode_set

mfastboot flash partition gpt.bin

mfastboot flash bootloader bootloader.img

mfastboot flash logo logo.bin

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img_sparsechunk.0

mfastboot flash system system.img_sparsechunk.1

mfastboot flash system system.img_sparsechunk.2

mfastboot flash system system.img_sparsechunk.3

mfastboot flash system system.img_sparsechunk.4

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot erase carrier

mfastboot erase cache

mfastboot erase userdata

mfastboot erase customize

mfastboot oem fb_mode_clear

once you finish downloading the stock rogers 6.0 rom unzip the archive you downloaded to a folder and place mfastboot and the new batch file you made in the same folder that you get from extracting the archive run the batch file and you should be able to flash the new 6.0 update to your phone and return to stock at the same time.
[E 2015 Android Development] santabanta114:
Same problem. Did you find any solution?

Edit:- The official TWRP posed no such problem at least for the booting part. Will update after backup and flashing.

Edit:- Squid TWRP working. All good
[E 2015 Android Development] BillyMumphry:
Ssems to be some sort if MRP boot loop. Like a dog chasing its tail! Anyone know what causes that

---------- Post added at 03:16 PM ---------- Previous post was at 03:15 PM ----------
[E 2015 Android Development] alex5908:
Can I use TWRP for Moto 2E (LTE) if I still have the original firmware?
[E 2015 Android Development] ayush rao:
Yep but u need an unlocked bootloader
[E 2015 Android Development] Sher1234:
Yes But it Requires Unlocked bootloader
[E 2015 Android Development] BillyMumphry:
Hey All,

Having a thing with my /sdcard. It keeps getting corrupted needing reformatting, or it unmounts itself and the apps on it are no longer usable. I'm on the (Squid)TWRP 3.0.2.r1 recovery. Sometimes the notification just says 'SD card missing' other times it will say 'SD card corrupted' When I'm lucky all i have to do is physically pop the sd out and pop it back in then the phone recognizes it all on its own and im back in action. When I'm Unlucky, most times, I have to boot into TWRP, wipe things down and sideload my Rom and Gapp packages. then go through the setup steps to finally get to be able to format the sd card as either 'Portable' or 'Adopted' I go adopted and load everything possible onto it. (Confession: I even Force move apps to the /sdcard even when it says 'This app doesnt declare itself the ability to move to the sdcard...' whatever, I do it.)

I've also noticed my /sdcard dir isn't being populated by the usual folders anymore. For example the TWRP folder used to automatically get a BACKUPS sub folder and that folder had a sub called TA0936....my serialno no i just get the first TWRP but no backups get stored there. for some reason the are getting put in /external_sd/media/0/TWRP/...I've come across a solution that worked for a guy that i will try soon as this backup is done.

In the mean time anyone have any ideas what causes this sd corruption? Personally I think its Satan.

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

Device: Moto E 2015 XT1527-Surnia

Bootloader: 0x8020 (Unlocked)

Recovery: (Squid)TWRP 3.0.2

ROM: Resurrection Remix v5.6.9
[E 2015 Android Development] cmason37:
This has nothing to do with the recovery. Your SD Card IS corrupted. As someone who's gone through many cards, I know the signs by now. It isn't very long now before your card will be completely unusable.
[E 2015 Android Development] ayush rao:
Yep I too have gone through a great share of SD Cards though I have never faced this issue on any of them. On the other hand my friends SD Card kept giving similar issues and then one day it just died and refused to be detected by any device.......

Also I don't think this is a TWRP issue