yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] :
Nothing extreme about clean flashing-i clean flash Everything, including nightlies when I've been testing CM13, just a habit I've got myself into.

I'm finding I have fewer (if any) issues clean flashing than dirty flashing, what everyone else does is course their choice, but clean flashing does give me a much more fluid and stable system!

With regard to open gapps, the developer of official CM13 for surnia made a plea around 2 months ago for testers NOT to use open gapps as something open changed broke certain aspects of CM13.

The plea was largely ignored though, until a flood of complains in the CM13 thread of the set up wizard force closing after installation/first boot, most people making assumptions that something was amiss with the ROM (as in most cases) but a reflash with a different gapps package solved everyone's problem!

The issue wasn't moto e 2015 specific, other devices running open gapps/CM13/CM13 based ROMs had the issue.

This was all resolved after open gapps reverted their recent changes back to original after pleas from developers.

I've been using open gapps at least 5 weeks with no issues what so ever, but I must update my gapps to the newest version, as I'm still using a late may release, this I assume was the cause of the issues I experienced.
[E 2015 Original Android Development] badduke18:
Clean flashed the rom, with both opengapps and Bankgapps but faced setupwizard forced close..

sorry can't provide the logcat now.:(
[E 2015 Original Android Development] :
Tried without gapps????
[E 2015 Original Android Development] Sands207:
the only way i got it working for me was to flash the rom first then after setup go back to recovery and flash everything else. im using opengapps
[E 2015 Original Android Development] :
I'm very surprised you got it working installing/flashing the way you did, but if that works for you, all well and good, but its not an authorized flashing method, because marshmallow uses ART, gapps must be flashed with the ROM........

For example, my installation method.....

In TWRP select wipe (advanced) select system, data, cache.

Select install (select ROM zip)

Select add more zips (select gapps package here)

Select swipe to confirm flash.

Wipe cache

Wipe dalvik

Swipe to confirm.

Reboot system.

That is the "Official " flashing procedure, anything else can hardly be considered illegal, but we must be careful not to set a precedent, incorrect gapps installation can be attributed to 75% set up wizard failure or force closing.
[E 2015 Original Android Development] Sands207:
lol i dont care whats authorized ? For me its the only way that i can flash this particular ROM to my phone i always do a full wipe because i jump from ROM to ROM quite often testing and have here on xda for quite some time. If i flash my gapps and I use opengapps which could be the issue and im going to try banksgapps on my next new install to see if that yeilds different results and i suspect it will.. It is working great now so i don't really care but my phone will bootloop if i flash my gapps with this rom, I go back and do gapps,kernel etc after, and then wipe art and cache and im good to go. if it works by adding an additional step im not losing sleep over it ?
[E 2015 Original Android Development] IronTechmonkey:
[MENTION=4422917]ivan39[/MENTION] and [MENTION=6085001]Sands207[/MENTION]

I think this is one of those cases where all of these things may be true at the same time depending on different circumstances, particularly differences in the post flash initial configuration. There is some information about the setup issue in these posts (and maybe others) by [MENTION=5227588]Deltadroid[/MENTION] in the Delta Gapps thread:

http://xdaforums.com/showpost.php?p=65564486&postcount=2130

http://xdaforums.com/showpost.php?p=65978104&postcount=2219

http://xdaforums.com/showpost.php?p=66625720&postcount=2330

http://xdaforums.com/showpost.php?p=66874851&postcount=2370

Also, Based on my experience with CM11, CM12.1 and CM13 here are some observations;

- The recommended SOP for flashing ROM and Gapps is now indeed to flash both at the same time then reboot however, this is not absolute and was not always required.

- In CM11 I did occasionally flash ROM, then reboot, then flash gapps with no problems. I did this enough that I did not even know that the recommendation was to flash both together until...

- In CM12.1 I had problems with rebooting between ROM and Gapps flash and so I started flashing them together and had no problems until...

- The recent issues with CM and Open Gapps initial setup colliding as described in the linked posts above.

- Considering that the issue in question may be related the initial setup wizards it is not surprising that different actions taken at first boot after ROM/Gapps flash may work in some cases and not others, the 2 of you being good cases in point.

- For what it is worth by comparison; I skip and disable everything at initial post flash boot (especially the Google account configuration) and always did the initial setup with no data connection until...

- In CM13 (and perhaps for some time late in the CM12.1 run for my device) I noticed that the data connection was enabled by default at first boot.

Anyhow, just for what all that was worth, which should at least be ti minimize any surprise about how we may each see different results from different actions, particularly the state of data connection and whether or not the Google account was configured at initial setup or later.
[E 2015 Original Android Development] :
Yes agreed.

I'm still thinking open gapps has some sort of issue again, this force close at initial set up sounds suspect.......

But

As I said, if it works for him, that's great, really good, my only concern is I know several users jump between these ROMs as new releases are posted, and then someone will quite innocently say the ROM doesn't boot as the set up wizard force closes.........

After some investigations late last night I did indeed flash the new release with full wipes, no custom kernel or mods like xposed, and with the A gapps google minimal package and a wipe of dalvik and cache.......

No issues.

I then reflashed with Banks gapps, again with a clean flash and wipes after flashing, again, I had no issues.

I tried a third time with open gapps but a newer package than what I had previously used and got the set up force closing.

Now, I'm not saying open gapps has another problem, but it does indeed force close at initial set up using the recommended installation procedure.

Using the unofficial set up procedure as described by the OP results in a constant bootloop, and another reflash (but having to get to recovery by force reboot by holding power and vol down to get into bootloader to select recovery)

Somethong strange is happening at the moment and I'm sure it could be attributed to open gapps again, but until someone confirms this is indeed the case, I'm sticking to what works best for me, and I don't wish to seem argumentative or dismissive of these different installation methods, I read and acknowledge that at times doing something different is the only plausible way to make something work, so if the OP got it working buy doing something different, we should maybe just take time to consider what on earth is going on or has changed from previous releases.
[E 2015 Original Android Development] :
Just spent some 4 hours doing some pretty intensive testing just to share with you guys.

I'm still suspecting some kind of open gapps problem, after all, its happened before, so it can in all probability happen again.

1 Clean flash of newest resurrection remix ROM, no mods with 16/06 open gapps package flashed with RR.

Boots and gets to "Resurrection remix is configuring apps 1 to X...... Then it hangs on "Configuring phone contact storage" and doesn't do anything else.

I then had to force reboot by power/vol down to boot loader to get back to TWRP.

2. Clean flash of RR with no gapps.

No issues at boot.

Reboot to TWRP, flash gapps and reboot.

Set up force closing.

3 Clean flash of RR with squid kernel, Xposed and the Motorola G4 boot animation, boots with no issues.

Reboot to recovery to flash open gapps, and sticks on the boot animation endlessly.

Force reboot to boot loader to get back to TWRP.

4. Clean flash of latest CM13 nightly with squid kernel, Xposed and Said boot animation with said open gapps package flashed with ROM, all OK.

Edit

As a 1st gen moto e owner too, I'm following the 1st gen moto e thread here on XDA, my "condor" sole purpose is a work device, its running CM13 for that device by squid.

In the last 12 hours, people have begun to report the set up wizard force closing, by users flashing open gapps.

It seem this issue has started affecting that device too.

[emoji33]
[E 2015 Original Android Development] PimpMy5Ton:
The setup force closing is not an OpenGapps issue, you said you flashed RR and then it booted with no issues and then went back into TWRP and flashed Gapps, this is an incorrect procedure you have done, reason being is with Marshmallow when it comes to flashing custom roms you MUST flash Gapps right after you flash the rom cause of the way Marshmallow assigns permissions to apps on first boot, if you do not do this then that is why the issues are coming along, I've been using OpenGapps Micro for a while now and haven't had any issues, just wanted to shed some light on part of your problem, hope this was some helpful knowledge for you :)
[E 2015 Original Android Development] IronTechmonkey:
Read back a few pages and read [MENTION=4422917]ivan39[/MENTION]'s post more carefully. ;) The issue we've been discussing is actually a CM change which seemed to impact some Gapps more than others, as somewhat described here http://xdaforums.com/showpost.php?p=67382960&postcount=669 and in the Delta Gapps links therein, as well as other posts in this thread. Although Flashing ROM and Gapps at the same time is now SOP, for at least one person flashing them separately was apparently the only way to get it to work: http://xdaforums.com/moto-e-2015/orig-development/rom-resurrection-remix5-5-1-t3160059/post67380816 and http://xdaforums.com/showpost.php?p=67382133&postcount=668, which is why [MENTION=4422917]ivan39[/MENTION] was testing that method. As you can see in item 1 of his report there were issues even with flashing ROM and Gapps at the same time.

That all being said, CM/CM based ROMS and Gapps should be playing nicely now and not having this issue anymore, but this is not the only place it has been reported in the past few days... just for what that is worth.
[E 2015 Original Android Development] :
Thanks for pointing that out.

If you read the previous posts, you will see I DELIBERATELY flashed gapps the incorrect way to prove a point that flashing gapps after booting into android and back into recovery causes the errors I described, and should not be attempted for the reasons you quite rightly and correctly pointed out.

If you also read back a few posts, you will see that a user has only been able to install gapps by flashing in the way I tried, and I tried to copy his procedure and that did not work for me.

My test was to prove incorrect proceedures dont work and to point out that gapps must be flashed in the same time as flashing the rom, one should not reboot into android and then back to recovery to flash gapps, that causes an ART conflict.

But

If the user is adamant this is the only way he can install gapps to get back to work with RR then who am I to argue with him?

I'm not a developer or experienced tester.

I did as you have and point out that gapps should be flashed at the same time ad the ROM by using "add more zips" in twrp.

As for your comment that open gapps does not have a problem, if you read a few posts back you will see I have tested other gapps packages and the 16/06 release caused me and a few others some problems, in that the set up wizard forced closed, nothing to do with incorrect flashing.

I changed my preferred gapps package as I have used open gapps since may with no problems, to the A gapps google minimal package and tested and the problem went away, but open gapps does indeed work great with CM13, again if you read my test report, you will see that's what I found!

Im not telling anyone not to use open gapps, but there was an issue with them a few months back, I simply reacted to other peoples reports and shared what I found.

I appreciate you taking the time to correct me on what I did, but I hope after reading my reply you realise why I did that and suggest you read a few pages back in this forum..........
[E 2015 Original Android Development] PimpMy5Ton:
I stand corrected, my apologies, on another note I haven't been able to get RR 5.7.0 to flash correctly, even by itself, so I have no idea what the issue may be, I even tried downloading it right from my phone and it still wouldn't flash all the way through, strange... :/
[E 2015 Original Android Development] :
Firstly, no need to apologise to me, good on you for taking me to task for doing something unofficial or unauthorised [emoji5]

Secondly, Yes, another point Ive tried to test over the last few days.

This latest release does indeed take a very long time to flash and install....why I'm not sure.

Of all the custom ROMs for the Surnia I've tried and tested (Resurection Remix, CM13, AICP and the latest Slim Rom) Resurrection remix always seems that little more "finicky" or misbehaves more than the others-Not a criticism, just an observation [emoji14]

I love RR for its shear customisations, but this new release does have some sort of issue.

I can't explain what that is, but it takes twice as long to flash, and has a "hizzy" fit and goes totally bonkers with certain gapps packages.

Maybe we will find out what these issues are with further testing?

Once up and running, it is quite stable but does suddenly freeze up solid for 30-40 seconds at times for no reason (tested with mods like xposed and without mods)

I think we need a more experienced eye to look at this.

I can only give my opinion and share my experience, but knowing what my luck is like, 20 people will now scream at me saying nothing is wrong with it, again, I can only post here my findings, and I'm not wanting to be at all critical of [MENTION=4910973]Vatsal[/MENTION]s hard work.
[E 2015 Original Android Development] Ozero.blue:
Try slim gapps no issue with any ROM on any device I have tested so far.ROM is running as expected great!
[E 2015 Original Android Development] :
I've tried them and can report no issues so far, in fact, the only package that I had any problems with was open gapps, but to be fair, it wasn't the package I have been using since may, it was the latest package of 16/06.

Let me just say that after leaving my moto e running CM13 for the duration of yesterday, I've now reverted back to RR with a Google apps minimal package from here on XDA, and I'm using various mods such as xposed to give me an android N environment.

So far, so good, no issues to report.
[E 2015 Original Android Development] IronTechmonkey:
To this point, an old trick (at least since CM11/KK) is to use an older gapps package and allow Google services to update naturally when the device goes on line after flash (LOL, this is one of the few times some of us want to see those stealthy and unavoidable Google updates) and from your experience it sounds like that trick still works, at least in some cases.
[E 2015 Original Android Development] :
Good point.

But.

I've had a rather sudden and catastrophic error.

I had a sudden reboot while driving about 45 mins ago, I noticed the boot animation just before I arrived home, taking the moto e out of the car cradle, and put it back inside it's wallet flip case and removing the charge lead, I took it inside, and everything has gone.

Apps, photos ringtones, apks, the whole lot.

Everything.

On closer inspection my google account is still on the phone, but everything else has gone.

Upset? Definitely.

Ideas?

None.

I notice even xposed and the android n module are gone.

BTW, my SD card is a class 10 sandick 16gb set as portable storage.
[E 2015 Original Android Development] IronTechmonkey:
Wow that is weird. I just experienced an issue which resulted in the deletion of all contents on my internal SD today (partly my own fault). I'm actually on CM12,1 so it would be OT for me to go on about it here but on the remote chance that there is some common thread related to TWRP here is my post about it in the TWRP thread.http://xdaforums.com/showpost.php?p=67408852&postcount=94.

[EDIT] Also, for what this is worth to your circumstances: If you can see the contents of your external SD via card-reader on a computer the drive may have experienced corruption due to repeated read/writes in which case Sandisk's native protection (to prevent further data loss) may have created a dirty bit which prevents it from being written to. This would cause the drive to appear as empty and or un-mountable on the Android device and prevent it from being written to when connected directly to PC, although it would allow existing data to be copied from the drive to computer via USB (card-reader) connection. This happened to a Sandisk card I was using a while ago.
[E 2015 Original Android Development] krocksss:
Thanks for the great work on RR Rom [MENTION=4910973]Vatsal[/MENTION].

The latest update running great. It has been my daily driver for a while now.
[E 2015 Original Android Development] :
Yes, I have some kind of SD card corruption.

I usually use ES file explorer but last few days I've been getting read/write errors from that app and stopped using it, going back to the native file explorer.

I did delete some obsolete apk files when I was downloading those other ROMs and gapps packages for the gapps test I did over the weekend, and my SD card is unreadable via PC or other phones (luckily my wife and children all have android phones, but my middle son has a Microsoft lumia 550 with windows 10, but its unused and obsolete......I wonder why??? Hehehe he's now upgrade to an Xperia z3)

My SD card is unreadable in all the phones but partly readable in the windows phone, but only my ringtone/music folder is readable.......

I also reflashed back to the 6.0 stock ROM, re rooted and am now reconfiguring my apps from play store.

I'm still puzzled about this, at least I can day 100% that resurrection remix was not the culprit, I'm feeling a bit silly and embarrassed as I've probably deleted something I shouldn't and messed it all up

I'll give you a nod once I'm back on RR but as its late and I've had to work late tonight I'll leave stock ROM on for now and re flash RR tomorrow evening.
[E 2015 Original Android Development] PimpMy5Ton:
Did you say 6.0 stock rom?? As far as I know Surnia in the States didn't get 6.0 officially, so no 6.0 stock rom, unless you're in a country that did get it lol
[E 2015 Original Android Development] swivels:
Yeah 5.7 is working great
[E 2015 Original Android Development] :
I'm in England, we got 6.0 in March.
[E 2015 Original Android Development] PimpMy5Ton:
Do you have hangouts by chance?? [MENTION=4422917]ivan39[/MENTION]
[E 2015 Original Android Development] :
Yes, and google plus and all the other goodies :)
[E 2015 Original Android Development] PimpMy5Ton:
Can you send me a pm with your gmail address so I can add you on hangouts??

---------- Post added at 10:42 PM ---------- Previous post was at 10:29 PM ----------

@ivan39 I sent you a message on Hangouts, sorry for off topic
[E 2015 Original Android Development] IronTechmonkey:
That's about when Moto finally threw the L5.1 update at US retail Otus devices in lieu of M. Sorry for OT. For what it is worth there is actually a thread about the Moto E update track here: http://xdaforums.com/moto-e-2015/general/motorola-provide-update-to-marshmallow-t3211958
[E 2015 Original Android Development] Joel Oliveira:
Last link MM to otus pls ?
[E 2015 Original Android Development] Silent Visitor:
Page no:- 66

Post number :-657

Latest Marshmallow !!??

Moto E 2015 (3G)
[E 2015 Original Android Development] PimpMy5Ton:
Well I finally got RR 5.7.0 installed on my phone, seems it installs better from my internal storage than from my 128gb microsd card lol
[E 2015 Original Android Development] kaotd99:
Great ROM but there is overheat problem !!! even deepsleep my phone still very hot ...
[E 2015 Original Android Development] cango123:
Log or it didn't happen..
[E 2015 Original Android Development] p321:
I using ringplus service with this rom and some https website do not work (not loading and progress bar is stuck). WiFi is OK.

Any idea? My other phone LG Volt 2 on ring plus can load the same website.
[E 2015 Original Android Development] PimpMy5Ton:
Are you using the default kernel that's included in the rom or a custom one?? I'm using Chriszuma Surnia v4 kernel on RR with no issues at all ?
[E 2015 Original Android Development] kaotd99:
i use the default kernel...
[E 2015 Original Android Development] PimpMy5Ton:
Out of respect to the OP I won't make any recommendations, but you could always try a custom kernel to see if it makes a difference ?
[E 2015 Original Android Development] PimpMy5Ton:
[MENTION=4910973]Vatsal[/MENTION] Will RR 5.7.0 ever get uploaded to Basketbuild?? It would make it easier than sifting through this entire thread to find the DL link for the current version :)
[E 2015 Original Android Development] BillyMumphry:
Speaking of which....Any news on Surnia570?

Oh, And also I too have been attacked by this 'Ghost In the Machine!' people have been discussing --Sudden, spontaneous and totally unnecessary SD unmounts. Screen freeze. Bootloops. I've had three corrupt sd's in the past three weeks. This problem, whatever it is, has even begun to affect my Recovery. I've started drinking again. TWRP has been doing odd things also. I was in Recovery, connected to PC through ADB and was granted no access to any files on my sdcard. I went from 6 Gbs to 13 in a matter of i day and all i did was play Tiny Troopers 2 . I did a scan using ES File explr.'s built in clean tool and it returned 3 copies of resremix. All in different spots. One was just /sdcard /myfolder. Put there by me. The other was /storage/emulated/0. and the next was /external_sd/emulated/0 . Based on the word 'emulated' I think they might not have been actually real. Now while I cannot confirm the existence these extra files, I will tell you the amount of space they took up on my sdcard was defiantly real.

And ADB was no help at all!! I adb shell'd. I adb su'd. I seetenforce 0'd. I mv'd, I mkdir'd, I even rm -rF'd until it started resembling my sex life...PERMISSION DENIED !

I finally got lucky by picking my phone up and using TWRPs file manager tool, selecting the files to delete, and swiping.

I still Love this Rom. I've been using the 569 version since it came out pretty much all the time and just within the last few weeks did i make any adjustment in

variables, Open GApps.

.

Edit: Omission:

In Recovery I, for the first time had to force a reboot by holding the power button for 15-20 seconds. I had to act quick because I had no OS no system. With hardware combos I got back to TWRP through the bootloader. Then during an install of 3 consecutive .zips near 4 or 5 red error messages printed out along with an extra large font sized "FAIL". Then the top of my screen the status bar area the whole thing lit up bright orange like when your battery is low. Buttons failed to button. They must've been the Hardest Buttons To Button. This was all past few days. Today all I'm running is a freshly downloaded Basket build of ResReMix v569 from last month I think and a new few day old open mini gapps.

All these other things are affecting my ROM! My recovery has gone HAL, my gapp apps misbehave and Resy does his best to hold it all together.

I'll miss you 569!

Oh yeah, my original question : Is there a secret handshake I can learn to get 570 for Surnia?
[E 2015 Original Android Development] beast99:
https://www.androidfilehost.com/?fid=24591020540821914