yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] SylvieL:
I know, which is why I want to try with stock, but I have no clue how to get that back.
[E 2015 Original Android Development] DanHutchins:
Where the signature verification is toggled it flashes then twrp restarts but my concern is that it flashes in about a second didn't dare to boot phone so I restored back to stock. Is this able to be flashed on stock rom I'm on xt1526 with latest version of twrp

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

Also my phone has already upgraded to 5.1.1
[E 2015 Original Android Development] diafero:
Are you using HW encryption? I had the same issue ("no SIM card") once I encrypted my phone. I wiped everything since then ("format data" in TWRP) to get rid of the crypto, now it's all working again.

Of course, that's a fairly severe bug.
[E 2015 Original Android Development] DanHutchins:
Not sure what I am doing wrong but the latest cm-12.1-20150827 doesn't seem to be a complete rom do I need cm already to flas this or can it be flashed to a phone that doesn't have it. Seems to download to fast to be complete and it also flashes in the blink of an eye. Didn't try booting after because it just didn't seem right so I restored back to original out of box rom please if anyone could help it would be appreciated. Figured it out I think thanks.
[E 2015 Original Android Development] DanHutchins:
Just wondering if themes are working in latest build
[E 2015 Original Android Development] PriPhaze:
Themes have been working for awhile now... There are things that you should try yourself lol
[E 2015 Original Android Development] DanHutchins:
Finally able to flash latest build seems like data keeps dropping every now and then on xt1526 boost mobile
[E 2015 Original Android Development] yelupic:
Stock-ROM To Go ...

You may try this (I did it with both firmwares and had success):

First make all your backups (if needed).

Check Settings > Developer options > OEM unlocking and Android-Debugging (allowed permanently)

Download either this (for Lollipop 5.1, retail US) - Yes, it works on Moto E 4G (2nd gen.), retail DE, XT1524:

http://motofirmware.center/files/file/149-surnia_retus_51_lpi2329-15_cid9_subsidy-default_cfcxmlzip/

MD5: f8760b4ce69b4a1f04e6b3c7ca23ed49

or this (for Lollipop 5.0.2, retail EU):

http://www.filefactory.com/file/5vb..._LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip

MD5: 623419f42075a9b8b74c2d833bc4fa2d

Check the MD5 hash of the files after the downloads.

From *one* of these xml-zip-files extract ONLY the following files into your adb-/fastboot-directory (nothing else):

boot.img

recovery.img

system.img_sparsechunk.0

system.img_sparsechunk.1

system.img_sparsechunk.2

system.img_sparsechunk.3

system.img_sparsechunk.4

system.img_sparsechunk.5

Open a terminal on your PC.

Change into your adb-/fastboot-directory.

Switch off your phone, remove all cards (SIM, external sd card).

Boot into fastboot mode (bootloader) with [ Volume Down ] and [ Power ].

Connect your phone to your PC.

Enter the following commands in the terminal (one line after the other, each line followed by [ Enter ]):

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5

(Note: This intentionally isn't the full sequence for flashing the original firmware. The bootloader, logo, modem files/partitions etc. are left untouched, which is more secure, especially for the update to US retail 5.1.)

Disconnect your phone from the USB cable and restart into the bootloader.

Go into (stock-)recovery mode and perform a wipe cache partition and a wipe data/factory reset.

Boot into the homescreen, skipping all the initial setup dialogs (= no language, date/time/zone, no W-LAN, no Google account, no other settings, not installing apps etc.). - Let the phone settle for 2 minutes. - If you get a notification to downgrade Motorola Sensor Services firmware (with the 5.0.2 reteu-release flashed), then do it.

Power down your phone a last time.

Insert a SIM card (which works in another phone), reboot the device and test it.

Note:

A warning about bootloader relocking | Moto E 2015 | XDA Forums

Good luck!
[E 2015 Original Android Development] DanHutchins:
Just needing to know what gapps to use tried the arm stock full 5.1 gapps and Google app and Google play do not work getting connection timed out and there was an error please try again
[E 2015 Original Android Development] SylvieL:
Wow, that actually was my problem! I had no clue enabling encryption could cause this! Thank you so much for the suggestion that fixed it, and thank to all others for all the help! I hope OP can add this to the list of known bugs.

---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------

Seems I don't need to flash stock after all, but thanks a million for taking the time to write that up!
[E 2015 Original Android Development] diafero:
There seems to be an issue with music playback, independent of the app I am using (tried the one shipped with CM, and vanilla music). Sometimes (in particular, after a clean boot) the device will be in a state where hitting "play" tarts playback as far as the app is concerned (the current position in the slider changes, etc.), but there's nothing to be heard. If I now plug my headphones on and out a few times (or maybe one time is enough), I can hear it playing in my headphones - and then, after plugging them out (and hitting "play" again), the song is also played by the phone's speakers. I would however expect the song to be played on speakers even the first time I hit "play".

Sorry I didn't catch an adb earlier today, will do the next time I see this.
[E 2015 Original Android Development] Noeljunior:
Hi people! I may need some help from you!

I bought a Moto E 2015 LTE in europe (portugal) carrier-free on april. In that time I search how to unlock bootloader and install this thread's rom (CM12.1). Everything was great and the phone had no problem until now.

I was trying to update the rom to the latest and, as I usually do, I updated the recovery to twrp 2.8.6.0. The problem now is that I can't boot any rom! I tried the [MENTION=5644259]yelupic[/MENTION] solution with RETUS version and twrp 28.[5; 6; 7]. With [MENTION=5644259]yelupic[/MENTION] solution I stay stuck on motorola boot splash (not bootanimation) and with CM12.1 the phone always boots to recovery. I never tried to re-lock the bootloader. Anyone knows what's this? Thanks!
[E 2015 Original Android Development] DroidFreak32:
Have you tried flashing the stock Motorola firmware for your phone via fastboot? If not give it a try. It might at least make your phone usable :P
[E 2015 Original Android Development] Noeljunior:
Yes, i tried with no lucky :(

I tried the yelupic's solution (US version and EU) and neither work. I didn't flash every partition as I don't know how to flash every single flash in those zips

EDIT: well... I'm not sure what i've done/installed. I just tried a lot of stocks roms and one did the job. I'm assuming that now I can install CM as before. Thank you :)

EDIT2: Maybe the thing was doing all these commands. I was not doing all...
[E 2015 Original Android Development] jpmaster:
Do you think the problem was caused by twrp 2.8.6.0?

If so, you could try squid2 twrp 2.8.7, specific for moto e lte.

I use it and works very well with no apparent problems
[E 2015 Original Android Development] jpmaster:
Build 43

[MENTION=3445372]scritch007[/MENTION] Is there a change log for build 43?
[E 2015 Original Android Development] rokban:
Installed it since around 12 hrs, pretty solid, no reboots and all, didn't face any other issues too..I hope we get official support soon :)
[E 2015 Original Android Development] EB20XY:
You run build 43 or 42 ?
[E 2015 Original Android Development] rokban:
43 ofcourse
[E 2015 Original Android Development] SylvieL:
If you have at least one app group, and want to set that app group to not vibrate in a system profile, settings will crash:

D/AndroidRuntime( 4622): Shutting down VM
E/AndroidRuntime( 4622): FATAL EXCEPTION: main
E/AndroidRuntime( 4622): Process: com.android.settings, PID: 4622
E/AndroidRuntime( 4622): java.lang.NullPointerException: Attempt to invoke virtual method 'void cyanogenmod.app.ProfileManager.updateProfile(cyanogenmod.app.Profile)' on a null object reference
E/AndroidRuntime( 4622): at com.android.settings.profiles.ProfileGroupConfig.onPreferenceChange(ProfileGroupConfig.java:145)
E/AndroidRuntime( 4622): at android.preference.Preference.callChangeListener(Preference.java:928)
E/AndroidRuntime( 4622): at android.preference.ListPreference.onDialogClosed(ListPreference.java:281)
E/AndroidRuntime( 4622): at android.preference.DialogPreference.onDismiss(DialogPreference.java:398)
E/AndroidRuntime( 4622): at android.app.Dialog$ListenersHandler.handleMessage(Dialog.java:1263)
E/AndroidRuntime( 4622): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4622): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 4622): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 4622): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 4622): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 4622): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 4622): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 952): Force finishing activity 1 com.android.settings/.SubSettings
[E 2015 Original Android Development] DanHutchins:
Can't seem to connect to network when set to 3g but if set to 1x works fine on build 43 and phone xt1526 build 42 was the same
[E 2015 Original Android Development] starkly_raving:
CDMA seems to be borked, the 43 build included the eri overlays from codyf86 and sadly it didn't do anything. I'm guessing it's telephony related. Personally I'm just going to go back to my G for the time being until the CDMA stuff gets sorted. I'll keep digging and looking thru commits and hopefully find the answer. The dev is working on it too. [emoji106]
[E 2015 Original Android Development] spiked_mistborn:
I believe the command fastboot oem fb_mode_clear is the one that corrects this issue if your phone keeps booting into recovery.
[E 2015 Original Android Development] DanHutchins:
Not sure what happened but after flashing build 43 I tried flashing squid kernel when I tried rebooting it said no OS are you sure so I just went and restored from my backup but now I can't flash cm anyone know how to fix this??
[E 2015 Original Android Development] starkly_raving:
You can try 2 things that I know have worked in the past, 1st one is back up your internal SD to PC and format it then restore your SD and reflash. 2nd flash the factory firmware and reroot.
[E 2015 Original Android Development] DanHutchins:
OK do I flash firmware with fastboot if so what's the code for that
[E 2015 Original Android Development] gibi67:
It's ok, everything I've tried works fine.

Inviato dal mio XT1524 utilizzando Tapatalk
[E 2015 Original Android Development] matteo 06:
on 1524(eu) cm12.1build43+squid kernel r7f works marvelously

Thanks to developers
[E 2015 Original Android Development] starkly_raving:
Just an update for those on CDMA (Boost XT1526 specifically)

The 43 build included the eri overlays from the Moto G. This didn't fix our issue with improper carrier being displayed. Here's what I've done personally to this point.

1. Flashed rom/gapps...no change for carrier and 3G issues were there.

2. Fastboot config the carrier by using "fastboot oem config carrier Sprint" (yes in the command its supposed to be Sprint.)

3. Manually edited the eri in framework by decompiling, editing and recompiling framework.

4. Added carrier specific lines to build.prop.

5. Added the eri.xml to data

6. Changed to LTE/CDMA auto prl.

So in a nutshell we've tried everything framework related. Soooo I am pretty sure it is a issue in telephony somewhere.

I forwarded an older commit I found in CM to the developer to see if it was still there as it addresses carrier issues. There's a chance it could have been reverted or pulled at some point.

Anyway should there be a developer or a CDMA savvy person out there that can point us in the right direction that'd be awesome. It would address the issue for us in all CM bases and probably even AOSP.
[E 2015 Original Android Development] sirhc:
Flashed this rom on my SPRINT XT1526 and my service is gone. My phone number in settings is zero'd out and the carrier label is set to boost
[E 2015 Original Android Development] starkly_raving:
Very strange considering Boost users can't get their carrier label set to Boost but that's a good indicator of whats going on. Can you pull a radio log?
[E 2015 Original Android Development] sirhc:
Ok what i did was i made a test call and it worked, data just wasn't appearing. The carrier label said Boost Mobile. So i flashed the Universal APN Fix in this thread and after i did and rebooted my phone, it showed Sprint for a split second, then the network did a reset and now it says "000000" and i still have no data. I'm gonna do a full wipe and reflash and pull the radio log for you

EDIT: WOW this is some weird sh*t. I just did a full wipe and reflashed and now Sprint shows up as the carrier label and all of my text messages are coming in like a storm. Now i can't pull the radio log, that sucks. Data still isnt working though

---------- Post added at 11:22 PM ---------- Previous post was at 10:59 PM ----------

Ok i figured something out. Changing the "Preferred Network" causes the "000000" Carrier Label issue and it affects data. When switching to "LTE Preferred" or "Global", my carrier label says Sprint, but i get no data what so ever. Switching to "3G" or "1X" changes my carrier label to "000000" but i get data. I'm able to make calls and text on whichever network i select regardless. This seems to be an issue revolving around Carrier Labels and Preferred Networks and an APN with LTE. My phone number magically showed up in settings too.
[E 2015 Original Android Development] DanHutchins:
On build 44 with squid kernel and everything is working great able to connect with 3g and not needing to change to 1x I'm on xt1526 so great job devs I think you guys finally did it. FYI CyanogenMod 11 for moto g doesn't show the carrier name either just says roaming indicator off and that's the official version
[E 2015 Original Android Development] starkly_raving:
The official CM 12.1 for the G does in fact show the proper carrier.
[E 2015 Original Android Development] sirhc:
Even though boost is under the sprint network there are still differences in how it gets connected to data. Since everything is provisioned for boost, it's not going to connect to a sprint network. PRL's can be service dependent also as well as the APN. Boost mobile uses a different server to obtain data. I took a look at the Boost APN Fix and majority of the XML is sprint related except for the last few lines where a custom Boost APN is made. I tried changing APN settings via app but its a no go as it seems due to the editing with the apn_conf.xml, it keeps using the boost settings in there. Ill try manually changing it and see if that fixes the issues with Sprint
[E 2015 Original Android Development] starkly_raving:
Yes Boost is an MVNO of Sprint. I've manually edited the apn conf, the eri within the framework, ran fastboot oem config scripts at boot and nothing is working to properly provision the device. Its definitely smali/java related within telephony/telephony manger.
[E 2015 Original Android Development] sirhc:
Man that sucks, thought i finally had a solid rom for my phone. Maybe a sprint version can be compiled?
[E 2015 Original Android Development] DanHutchins:
So this morning I couldn't connect to network without switching to 1x strange how it worked all day then stopped...
[E 2015 Original Android Development] Avranil Basu:
Heats Up on Xt1521

Sometimes while using net or listening to music it heats up rapidly and reaches 40 degree celsius on the latest cm 43 build any reasons for that ??? Thanx :)
[E 2015 Original Android Development] ssingh1:
The ROM is one of the best..... I hardly encountered any bugs... Just 2 things

1. Could you somehow incorporate moto display?

2. Will it be upgraded to Android Marshmallow?
[E 2015 Original Android Development] sirhc:
I've pulled the apn-conf and eri.xml from the sprint stock rom and replaced it with the ones for this rom and still no dice. It's definitely a telephony issue. Let me also add that when using 3G as my preferred network my messages come in about 30 minutes late or they don't come in at all. Wonder if some things in telephony can be replaced from stock rom. But the weird thing is, i'm running the boost mobile 5.1 rom and my sprint service is working fine, LTE and all is working flawlessly. How is it that it works on a Boost Mobile STOCK rom but not a Boost Mobile CUSTOM rom? There must be some more changes that need to be applied in CM. I say someone could compare some stock stuff with CM stuff and fill in the holes.

---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------

What's the model and carrier of your device?

---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------

The latest build is 44 (Which was released yesterday), not 43. Try updating and see if that fixes the issues
[E 2015 Original Android Development] starkly_raving:
I'm decompiling stock and CM telephony stuff now to see what the differences are. Somewhere something is different whether an XML or some smali code. Its just a matter of finding it.
[E 2015 Original Android Development] sirhc:
Moto display would be hard to include considering it's not open source unless it's possible to side-load which i doubt. When Marshmallow is OFFICIALLY released, the Cyanogen team will update their rom and sources so people can build it. It's more so up to the maintainer of this rom to take on that task unless someone else is willing to do so. Even then, i don't see a Marshmallow CM coming to this phone until early January.
[E 2015 Original Android Development] starkly_raving:
M won't be pushed to AOSP till Novemberish or until the new Nexus is released along with the factory images. Don't expect Dev Teams to update bases till after the holidays at the earliest.(Based on previous experience)
[E 2015 Original Android Development] sirhc:
Yes i can pretty much guarantee that's the issue. I'll try to decompile later on when i get home to see if i can find somethings also. I've had telephony issues in the past when building Hybrid roms for multiple carriers, so i know it can be a pain in the a** sometimes. Hope you find something though, don't give up on us CDMA (Sprint) users just yet lol :good:
[E 2015 Original Android Development] starkly_raving:
Going to check bools and sublds first hopefully we can have a truly unified build or get singular support for cdma.
[E 2015 Original Android Development] sirhc:
Yea that's why i assumed January at the very least, i remember it took that long last year when i was dealing with the G3
[E 2015 Original Android Development] DanHutchins:
I'm on the xt1526 and build 44+squid kernel so far that is the only problem oh its also boost version
[E 2015 Original Android Development] sirhc:
The CDMA version is still being worked on. People are aware of the issue and hopefully it gets fixed in the next 24-48 hours
[E 2015 Original Android Development] DanHutchins:
Thanks a lot looking good so far tho can't wait till it is fixed!!! Devs are doing a great job.
[E 2015 Original Android Development] starkly_raving:
[MENTION=3445372]scritch007[/MENTION]is doing a great job. We just have to keep digging and brainstorming, pulling logs etc to get CDMA.
[E 2015 Original Android Development] sirhc:
Is there a difference between the stock GSM and CDMA radios? If so, which radio was used in this rom?
[E 2015 Original Android Development] starkly_raving:
There is no modem included in the ROM. CM and most other bases cater to GSM.

---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------

Can someone on the Boost Mobile variant running the 43 build add this line to their building.prop?

ro.ril.force_eri_from_xml=true
[E 2015 Original Android Development] sirhc:
Ahhh yes, forgot. Have you tried adding "telephony.lteOnCdmaDevice=1" to the build.prop? I doubt that would make a difference but that's usually included in build.prop's on AOSP roms, sometimes even stock

---------- Post added at 08:04 PM ---------- Previous post was at 07:34 PM ----------

Tried your build.prop edit on 44 SPRINT and it gets rid of the 000000 carrier label and says BOOST MOBILE, so that part seems to be fixed. As for LTE, it still doesn't work and i have to set my preferred network to 3G which still causes my SMS to come in super late or not at all. I'm not sure if the LTE and SMS is fixed on boost mobile serviced users but i can confirm the 000000 is gone :good:
[E 2015 Original Android Development] starkly_raving:
Well I tried it on Boost and still have 00000 lol...but it seems like we're getting closer.
[E 2015 Original Android Development] sirhc:
Lol jeez this is so weird, but yes we are. I'm taking a look at some telephony stuff now
[E 2015 Original Android Development] sirhc:
I wonder if this issue can be corrected in QPST. I know it's not the best fix for everyone, i just wanted to try as a temporary solution until the fix gets baked in. Essentially i could use QPST to reprogram my device to the Sprint Network in a more sufficient way. The only other option from that may be updating the source to add the necessary carrier settings for sprint. I would do it but i can't read smali nor do i have a building enivronment set up to compile.

EDIT: Just edited the APN's again using APN Changer. I deleted all the blank Sprint APN's and Change the Boost ones to the Sprint EHRPD and LTE ones. I made sure the bearer was set to LTE for both and i selected the LTE APN. As soon as i selected it, my service went out and stayed out for about 2 minutes which it has never done before. It finally came back but the network label was set back to 000000 and no LTE showed up. I feel like i'm on to something. I'm gonna apply these changes to the apn_conf.xml and see what that does
[E 2015 Original Android Development] Dunci10:
So I bought this phone after getting rid of my HTC Desire 510 (worst phone I ever owned) rooted it and put this ROM on it. At first I had major problems with performance, stock ROM was smooth, but this was choppy, and lots of reboots/lock ups. Updated to the version before this one and wiped out all clean again, seemed better but still a little slow. Noticed that system services alone was using about 80% of memory. I then updated to the newest one this morning, and put on Squid Kernel along with it. Amazing. Nice and smooth, and system is barely using any memory. Everything works perfect. I do notice that everyone is talking about issues with data issues? Im having absolutely no issue. I'm on Boost Mobile, LTE works, and 3G works with no problems. When it's on 3G it says 00000 like everyone else is having, but I don't find that an issue, even on LTE it says Sprint. On my old phone 3G would come up as roaming. I was just curious on what is up with Data that everyone's talking about. Thanks for such a great ROM!
[E 2015 Original Android Development] sirhc:
Lol its so weird because I came from a HTC Desire 510 the other day. You're right, that phone is HORRIBLE, I still have it on my dresser lol. But since your LTE is working do you mind giving a Logcat? Or giving a radio log? My LTE isn't working because I'm on Sprint, even though boost and Sprint are under the same network, some configuration is still different and when I use 3G it causes my SMS to come in late or sometimes won't come in at all, but there are others who's having issues with LTE on boost as well, so I'm not sure how you got so lucky lol