Guys,
I recently bought a Moto E(XT1022). Being the curious tinkerer that I am, I started poking around the forums here for custom ROMs. Found quite a lot of them. One of the devs released an unofficial port of Carbon ROM for moto e. Cybojenix recently released an early build of of Slimkat ROM based on Android KitKat4.4.4. He also said that he will release an unofficial build of CM11 for moto e. But the problem with all of these ROMs is that they work only on single sim variants of moto e. I tried PMing dhacker29 the official dev of CM11 for Moto G unified Build about help to get these working on dual sim variants but to no avail. Same with JackpotClavin. So are there any other devs willing to take this up for us. Also I read on the Moto G forums about flashing XT1032 firmware on XT1033 to get only one working sim and to use single sim supported Roms. Is it anyway possible to do this with Moto E and is it practicak . The main problems being faced here are SystemUI crashes, not working radio etc.. There must be some work around.Hope we find it real soon.
yeah me too waiting for that but many users flashed the us moto e rom and result was none of the sims are working hope so we get some help
I asked cybojenix about it. He said that dual sim sources are pretty messed up. That's the reason devs are hesitant in supporting them.
Sent from my XT1022
subham99 said:
I asked cybojenix about it. He said that dual sim sources are pretty messed up. That's the reason devs are hesitant in supporting them.
Sent from my XT1022
Click to expand...
Click to collapse
BTW @cybojenix just released a cm11 fix for dual-sim versions. Single-sim works for me.
:good:
Check cm11 thread for more info.
Related
Hey guys,
I'm a developer for the Optimus Black p970 and the creator of Aeroi rom. I am getting this phone soon and plan on developing it, any news from sources from Motorola? Have they released them yet?
The LTE model is known as Styx LTE. It's sources are available on GitHub:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop-5.0.2-release-styxlte
The LTE model uses an MSM8916, so use the msm8916_defconfig.
The 3G model is similar to the Moto G and previous Moto E. It uses a MSM8212 SoC. Motorola hasn't released a kernel for the 3G variant, but the previous Moto E's kernel sources might work. They haven't released Lollipop sources specifically for the old E either, but this kernel *might* work when built for msm8610_defconfig:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/lollipop—5.0.2-release
I'm working on a kernel for the LTE model, but I don't have anything that I consider worth releasing yet.
Should we be seeing better dev support for the LTE model soon?
Any news / expected availability of official CM/PAC for the LTE model?
Official CM doesn't mean better support.
I'm the maintainer of the moto E 2014 with @percy_g2.
Once I have a fully working CM for moto E 2015 build I'll push for getting the device official. The only change will be that the builds will be done by CM servers and you'll have the updates form CM. Also pushing changes to the repo will have to go through the grit system.
This is the same for PAC. PAC device tree and kernel can be easily done based on cm one.
I really hope that CM and PAC become official. Thanks for helping out.
can some of you fantastic developers create an Android M ROM for the LG Optimus G E970 at some point? does anyone have an ETA? I would love to learn to build it myself, but I have limited access to a computer (The library is practically my only source). I noticed that there is no developer preview for the Nexus 4, so would that slow down the building process? Thank you a lot!
Update : @ChiKaLiO is working on a few variants for the Optimus G and might start soon for geeb . Someone else has released Marshmallow for other variants...is anyone else working on it?
optimisandroid said:
can some of you fantastic developers create an android M ROM for the LG Optimus G E970 at some point? does anyone have an ETA? I would love to learn to build it myself, but I have limited access to a computer (The library is practically my only source). I noticed that there is no developer preview for the Nexus 4, so would that slow down the building process? Thank you a lot!
Click to expand...
Click to collapse
We'll have to compile from source for a bug-free version for the e970. However, there is a Google employee that's working on a version of M for the Nexus 4, so we may just be able to port that version on to our phone. ETAs are a big no-no. I'd get pissed if people kept asking when I'm going to release something when I'm working tirelessly to squash bugs and have a working build. It'll come. Patience is key.
Now that there is a Nexus 4 Marshmallow ROM out, is there someone experienced working on E970 Marshmallow (not asking for an ETA) or someone who could give me some tips on doing it myself as my first ROM?
yeah, an CM M Rom would be nice!
topdawg7793 said:
We'll have to compile from source for a bug-free version for the e970. However, there is a Google employee that's working on a version of M for the Nexus 4, so we may just be able to port that version on to our phone. ETAs are a big no-no. I'd get pissed if people kept asking when I'm going to release something when I'm working tirelessly to squash bugs and have a working build. It'll come. Patience is key.
Click to expand...
Click to collapse
Oh yeah. So great
Gửi từ LG-E970 của tôi bằng cách sử dụng Tapatalk 2
apparently there's already an M rom out for the nexus 4 (aosp) as well as the international optimus g (e975/f180 i believe). thing is i don't want to go back to a broken rom without a lot of features (biggest pain for me is changing mac addresses since my workplace uses mac filtering for allowing wifi devices). hopefully it'll come around before the year's out, preferably with some of M's bugs removed as well but ya never know.
There are a couple different ones built for the intl optimus g, e975.
If someone builds a 6.0 kernel for e970, most of those roms should actually work with little other modification.
kernel
i have one, but it is very unstable
kamera isn`t working properly, and video broken
Hope devs do make an M build
I skipped L, not interested in it, and Ive been quite happy on my 4.4.4 SlimRom and do hope Slim, Bliss or CM make builds for our phone with help of devs such as optimus, its an awesome phone and really dont feel the need to change it still, nothing new has really wowed me on new phones exept maybe some cameras but dont take much of video or pics so hope the comunity does deliver an M version for our phone.
Waiting patiently
I also am interestef in an M ROM. I installed M on my Galaxy S4 and love it. But i am selling it now (need the cash) and am keeping my e970.
Marshmallow for E970
I have been running the geeb version of Marshmallow (Nitrogen by Mr Mex) again now for a week or so (March 1 version). The biggest problem is the SIM card is intermittently not recognized when not on a call (shows EMERGENCY CALL ONLY instead of carrier) and Layers does not appear to be as stable for themeing as CM's theme engine though I have found a couple of Layers that spare my retinas.
You can download at http://xyyx.ga/nitrogen-os/geeb/ and install using TWRP v2.8 though Philz last CWM derivative may work as well. I still have one foot in the Resurrection Remix v5.6.4 (Lollipop) camp as it runs nicely on my E970 without the SIM recognition issue and with Privacy Guard and Interruptions has basically the same featureset as Marshmallow just a slightly different implementation. In addition CM themeing appears more polished than Layers for Marshmallow (not necessarily Lollipop) at this time as some Layers cause system problems.
If you want to see how well it works for you I would skip installing any Layers or Xposed until you've run it for a day or so to cut down variables.
See
http://forum.xda-developers.com/optimus-g-att/development/dev-roms-development-t3279183
http://forum.xda-developers.com/optimus-g-intl/development/rom-nitrogen-os-27-10-2015-t3234308
thanks for the info, hope the SIM card problem can be fixed.
does camera and sd card works?
GEEB builds
No problem with camera or SD. There was a major camera problem for a while but that has been fixed in recent builds.
OMGMatrix said:
There are a couple different ones built for the intl optimus g, e975.
If someone builds a 6.0 kernel for e970, most of those roms should actually work with little other modification.
Click to expand...
Click to collapse
The e975 is a geehrc device and the e970 is a geeb device. The ROM won't install. It fails with the error stating that it requires a geehrc device.
GEEB builds
Are you trying one of these?
http://xyyx-dev.ru/nitrogen-os/geeb/
http://xyyx-dev.ru/nitrogen-os/testing/geeb/
KnowNadda said:
Are you trying one of these?
http://xyyx-dev.ru/nitrogen-os/geeb/
http://xyyx-dev.ru/nitrogen-os/testing/geeb/
Click to expand...
Click to collapse
Not until I know the SIM is stable.
blitz9826 said:
apparently there's already an M rom out for the nexus 4 (aosp) as well as the international optimus g (e975/f180 i believe). thing is i don't want to go back to a broken rom without a lot of features (biggest pain for me is changing mac addresses since my workplace uses mac filtering for allowing wifi devices). hopefully it'll come around before the year's out, preferably with some of M's bugs removed as well but ya never know.
Click to expand...
Click to collapse
Mac addresses are Hardware IDs. They are not going to change with a new OS.
http://xyyx-dev.ru/nitrogen-os/geeb/
downloaded 2016-3-29 zip
tried to install it but installation of zip stops with error
this zip is not for geebus !!!
I have att lg optimus g E970
You do not mention what recovery you used or wipes performed, et cetera.
It installed for me using TWRP 3.0 (for geeb). I dirty flashed (cache wipes only) over my March 1st Nitrogen install.
KnowNadda said:
You do not mention what recovery you used or wipes performed, et cetera.
It installed for me using TWRP 3.0 (for geeb). I dirty flashed (cache wipes only) over my March 1st Nitrogen install.
Click to expand...
Click to collapse
Thanks updated my recovery to TWRP 3.0.
now Nitrogen OS sucessfully installed
I'm wondering if the similarities between Surnia and Osprey will allow us to benefit from the work that Motorola is doing to bring Marshmallow to the Moto G 2015? It looks like a Marshmallow soak test was just started for the Moto G 2015 (Droid Life 11/4/2015), and it is rumored to have LTE band 12 support enabled, which would imply that VoLTE is also supported. I think it's very likely that in order for VoLTE to work it would need specific support for it in the baseband software. I have read that there are other SD410 phones that support VoLTE, so at this point it just seems like we have an issue where decent hardware is being held back by poor software from Motorola. Since it seems like Motorola has decided to abandon us, hopefully the XDA community will be able to step up and fill in some of these gaps in functionality. Here are a few questions that I have about the similarities between these two devices.
Are Surnia and Osprey similar enough that Surnia can run Osprey baseband software? Has anybody heard of any attempts to flash an Osprey baseband on Surnia? Would this be limited only because of code signing issues and not hardware limitations?
Surnia and Osprey use very similar kernels, so would this also make it easier to port anything related to VoLTE from the stock Osprey kernel back to Surnia?
When the stock Marshmallow update for Osprey is released would the similarities between the two phones make it more likely that somebody would be able to port it to Surnia?
Any thoughts on this?
I saw ROMs for Osprey that are based on Surnia's device tree, so why not? I don't think flashing a Osprey ROM on surnia will work, but what about flashing it with a Surnia kernel? I'll try it, can simply solve a bootloop!
Tried that, caused bootloop, but while downloading a backup ROM, I suddenly saw this:
It looks like Surnia and Osprey probably have different sized /system partitions. I tried flashing this http://forum.xda-developers.com/2015-moto-g/orig-development/caf-6-0-osprey-t3229378 and when it was verifying /system it gave an error message. I next flashed the squid2 kernel and it just bootlooped.
I just bought the moto z, I know it has an unlockable boot loader along with the source code is out from motorola BUT I failed to find any custom ROMS right now for this phone. Are there any out right now? Do they work with moto mods? Is the source code for the moto mods system out? If the answer is no and there are any developers working on porting something like cyanogenmod to the moto z, let me know as I can help contribute to the project.
I have the unlocked US version as well. (retus software channel)
I think everyone's just waiting for Nougat to drop at this point.
41LY45 said:
I have the unlocked US version as well. (retus software channel)
I think everyone's just waiting for Nougat to drop at this point.
Click to expand...
Click to collapse
So no one is going to develop until android 7.0? can custom roms even support moto mods?
eddi3x3x3 said:
So no one is going to develop until android 7.0? can custom roms even support moto mods?
Click to expand...
Click to collapse
That's what I assume most people would be doing. (Aside from trying to port over the Droid version of Nougat)
From the what I can recall, the mods stuff are released along with the source code. I saw a dev saying that Moto borrowed a number of stuff from Project Ara (RIP).
41LY45 said:
That's what I assume most people would be doing. (Aside from trying to port over the Droid version of Nougat)
From the what I can recall, the mods stuff are released along with the source code. I saw a dev saying that Moto borrowed a number of stuff from Project Ara (RIP).
Click to expand...
Click to collapse
I also noticed that some kernels have been released, Can I unlock the bootloader, install the custom kernels with stock roms and still use moto mods?
eddi3x3x3 said:
I also noticed that some kernels have been released, Can I unlock the bootloader, install the custom kernels with stock roms and still use moto mods?
Click to expand...
Click to collapse
As long as the include the Mods APKs. I don't see no reason why they won't work.
Heavily based on the WIP LineageOS port for the Moto E4 (Qualcomm) [perry] -- for more information about that, click here.
Known working:
Booting
Connecting to Sprint's 1xRTT network (2G data, voice, SMS)
Fingerprint sensor
WiFi
Broken:
Sound
Sprint 3G data and LTE (need to add in Sprint network blobs)
XDA:DevDB Information
LineageOS 14.1 for Moto E4 Plus (Qualcomm), ROM for the Moto E4 Plus
Contributors
ReimuHakurei, squid2, Alberto97
Source Code: https://github.com/ReimuHakurei/android_device_motorola_owens
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-10-31
Last Updated 2017-10-31
Uploaded another build that seems to get LTE on Sprint. All of the menus are still broken so you presumably need to be activated on stock before flashing.
Is there any way to make the fingerprint function to wake up / close screen to work with out requiring a pin/pattern/code to be active? That'd be an awesome feature
Installed on my XT1775 briefly and except for the sound this looks pretty good. I'm on AT&T and LTE worked fine, etc. I just can't live without sound as I need my phone for work teleconferences. I will *definitely* use this as soon as I can daily drive it!
I have tried (and failed) to get CDMA data properly working. Once someone gets CDMA/Sprint support working properly on one of the other devices in this family, it should be simple enough to port whatever the fix may be, but until that happens, this will likely remain as-is.
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
fix-this! said:
Since gsm seems to get LTE will this ROM still be worked on to get sound working? Even though I know CDMA users are out of luck for now. I have the standard e4 and want to buy a plus but I definitely need aosp ROMs.
Thanks for your work porting this. Actually shocked to not see more development considering how huge the battery is on the device.
Click to expand...
Click to collapse
I need to repair my shattered Moto X Pure so I have a working phone to use while developing before I can do much more work here (ie: on fixing audio). This was mainly a proof-of-concept to make sure I was, in fact, able to get the thing to boot, before I spent too much work fixing other things.
For CDMA, I think the root of it is the new architecture Sprint is using in preparation for CDMA+VoLTE; I tried porting over files from the Moto X Pure's LineageOS port, but it uses older tech for CDMA internally. The Moto G5S has the same ISIMv2 SIM card on Sprint so should be similar software-side, and the Moto G5S will almost certainly have a pretty active community judging from past Moto G series phones. Moto X4 should be similar as well.
I am likely to be pretty busy for the next month or so, though, so probably won't have time to do any work on this until then.
so does someone plan to pick back up development on this? really surprised there isnt more devs on the plus model. much better build, camera, cpu and that big ?.
What exactly did you have to do to get this to work. I'm considering trying to port a few roms from perry over to owens, but if it's too hard, or just practically impossible I'm not going to bother.
Which version seems to have LTE working? I currently have no LTE just call(no sound) and txt lol
So I am attempting to build my first rom for the Moto e4 plus Qualcomm. I'm just following the build instructions on lineageos's website. I'm stuck now because there is not a device tree in the lineageos git. I see that the OP has a device tree on git and I also see that there is now a Moto kernel on git. I am unsure what the next step is? I'm unsure how to make the device tree part of my local git and also how to mix the new kernel posted from Moto. Any help and I will post what I create. Thanks.
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
FlagersXDA said:
@ReimuHakurei would you please attempt to fix sound for this custom ROM now that the kernel sources have been released. I've been looking forward to replacing the stock room on my phone for a while
Click to expand...
Click to collapse
Yes please! I really want to use this rom but I use my phone for listening to music all the time. Will some please fix the sound?
Bump, can someone please fix this?
Thank you for releasing this!
+1 for no sound or mic on xt1775
I tried Bluetooth and wired audio devices and sound/mic is not functioning for them either.
I am able to connect to the Verizon network with a their Sim through net 10, but only 3g (EvDo-rev.A, by choosing global auto) and not LTE after trying various modes in the 4636 menu. With the same Verizon Sim through net 10 my Nexus 5x h791 does connect to LTE .
Besides the issues above, this appears to be working well!
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that. After I flashed twrp, instead of the Motorola bootloader unlocked screen, all I see is the white text "N/A" on a black background in the top left corner during bootup. Also, after I installed twrp I could no longer boot to the os until I installed this unofficial lineageos rom. I'm not sure if that is expected. Since I didn't make a backup of the system partition and boot before flashing twrp, I'm unable to restore the stock os. Lesson learned... immediately after making the mistake. I did make a backup of the boot and system partitions after flashing twrp before installing this unofficial lineageos rom(when I was already having the boot up issue), but when I restore them I have the same issue where the phone will not boot into the os. This is what I expected, at that point anyways.
Thanks again!
For Mediatek Variant
Sir,Any custom rom for Mediatek variant of this handset
fllannell said:
Also, if anyone can share complete stock partition images files (boot, recovery, and system partitions) for the xt1775, this would be appreciated, but I'm ok using my phone as is for now. I wish I had thought to make a complete backup by booting twrp through fastboot (fastboot boot recoverimagefilenamehere.img) and then making a backup first instead of flashing twrp before doing that.
Click to expand...
Click to collapse
I'm not sure if its the exact same variant, but @_maerk released stock images for the retail (snapdragon) e4 plus. Even if yours is carrier specific, as long as your bootloader is unlocked and you have the Qualcomm version you should still be good. I remember on my old Sprint Moto E from 2015 I could still flash the OS/Recovery/Boot images from the retail version, just not the modems or bootloader.
Update: I was able to restore to stock using the following link.
SCROLL TO POST # 10 for directions for Moto E4 Qualcomm (Owens) retail unlocked:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
Then I flashed Reiku's version of TWRP for the phone:
https://forum.xda-developers.com/moto-e4-plus/development/twrp-twrp-moto-e4-plus-qualcomm-t3697154
Then I installed this unofficial Lineage version:
[ROM][UNOFFICIAL][owens] LineageOS 14.1 for Moto E4 Plus (Qualcomm)
https://forum.xda-developers.com/mo...lineageos-14-1-moto-e4-plus-qualcomm-t3734197
Then I installed OpenGAPPs and AddonSu. The only hiccup I had through the process was that I got an ERROR Code: 64 when trying to install the ARM 64 version of openGapps in TWRP, so I used a non 64 version without issue.
Thanks to everyone for all of your efforts on these projects.