Database Develop

Guardian Rom [Secure] [Privacy] [Preview]

Guardian Rom by x942​Thanks to:​
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?​
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?​
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:​
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
​
Click to expand...
Click to collapse
How to use:​
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:​Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.​

Reserved.

you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid

baz77 said:
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
Click to expand...
Click to collapse
I may use SeAndroid. Right now I am focusing on the encryption side of things instead of the exploit mitigation side. That will come later.

Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴

azrash said:
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
Click to expand...
Click to collapse
Awesome! Thanks! It's is based off the latest repo. I simple pulled and than modified the sources. I am currently getting some hosting for our own repo and Tor Hidden service for downloading. Stay tuned much more to come.

TimeAndroid said:
Look'in good, might try.
Click to expand...
Click to collapse
The next build will have an AOSP 4.2.2 base with Mobiflage built in. Also Lock screen PIN and Pre-Boot PINs are now separated. So you can use a simple 4 digit pin on the lock screen and a 32 character pin at boot.
Also for more security you have to passwords one for the "outer volume" which you use as you daily usage and one as "hidden volume" which is your hidden os. You use the second for anything sensitive. That way if an attacker tries to force you to give up your password you just give up the outer volume (decoy) password. There is no way to prove the hidden volume exists.
Encryption also uses AES-256-XTS now instead of AES-128-CBC. Better key length and protection against watermarking attacks.
EDIT: If anyone wants early access please PM. The build is not ready for prime time as there is no GUI for encryption but can be used as a daily driver.

SecUpwN said:
No, I'm sure you're right. But since he explicitly stated that he won't build an ('unofficial') AOKP version, I'm looking for a way to get in the favor of the securiry modifications without gaving to switch to another ROM. It's just that AOKP has so many cool simplifications compared to CyanogenMod, I'd like to avoid a switch backwards. Maybe he could create an unsupported AOKP version every month? Possible?
Click to expand...
Click to collapse
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta

DontPushButtons said:
I'm guessing the modifications he has been making go a little further beyond a flashable zip. Otherwise he would've done that instead of making a whole rom around privacy.
Could be wrong..
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. I custom kernel is needed at the very least. Not to mention removal of Google Apps and tweaked UI for encryption (mobiflage). All of these are OS level tweaks and cannot be made into a ZIP.
droidkevlar said:
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. AOKP will NOT be supported. EVER. If anyone wants a different base download the source code from my github and compile it yourself. Build documentation is on there. Furthermore AOKP and CM10.1 are both great roms, however there are too many variables. Both have a ton of unneeded binaries and settings. We cannot guarantee security are these builds. We choose CM10.1 because it's fully open source and has fewer complications then AOKP. On NEXUS devices we are using AOSP modified with our security tweaks. On non-nexus we use CM10.1 for now for simplicity.
I am hoping with the recent Google Edition devices it will be easier to port/compile AOSP onto those devices.
TL;DR:
WE WILL NEVER OFFICIALLY SUPPORT AOKP.
Thanks for understanding.This message is only meant to stop these requests, not to be rude so please don't take it that way.

Cleaning
This thread is in the DEVELOPMENT section. And is for the "Guardian Rom [Secure] [Privacy] [Preview]".​
If you need to report an issue or bug then READ THIS POST ABOUT BUG REPORTS
Keep ALL posts aimed at the ROM development.
This thread is NOT A Q&A thread.
So don't ask why the WiFi won't work, post a LOGCAT of the actual event or it did not happen.
I have cleaned this thread.
If you repeatedly make junk posts, then INFRACTIONS will follow.
~JAB

Hey @x942, where is our Android 4.3 version of this funky ROM?

SecUpwN said:
Hey @x942, where is our Android 4.3 version of this funky ROM?
Click to expand...
Click to collapse
We are working toward this. The issue we are having is that while 4.3 is latest 5.0 may be just around the corner. We don't want invest a ton of effort just to have re-port everything to 5.0 if it's released 2-3 months from now. That's not to say 4.3 won't happen. It's just we are focusing on adding more security. For now stable is 4.2.2.:good:

Am I missing where to find the flashable zip?
Sent from my Nexus 4 using xda app-developers app

Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?

koz said:
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
Click to expand...
Click to collapse
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.

Request
Hi,
Please add the new moto g xt1032 to your list of planned devices - it would be a great way to get more people secured as it is a very popular handset
Thanks for all your hard work!

x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
Has this ever been developed for the Galaxy S3? I haven't been able to find a download anywhere...

@X942 gaurdian rom sounds very interesting to me. would also like the att slll i747 to be added on list for consideration for dev.
am not a dev myself.
thank you for your work/time/energy. :thumbup:
err on the side of kindness

good
Sent from my Nexus 4 using XDA Premium 4 mobile app

x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
I cant find a download for the Note 3 ROM. The only thing I read about it is an update on http://shadowdcatconsulting.com/blog/ saying that support will come soon.

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [moto_msm8960]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​

Reserved

Also Reserved

Locksreen > see through option unchecked but I can still see the wallpaper through lockscreen ?
p.s no missed call auto responder seems to be working ?

orangzeb said:
Locksreen > see through option unchecked but I can still see the wallpaper through lockscreen ?
p.s no missed call auto responder seems to be working ?
Click to expand...
Click to collapse
Did you dirty flash?
I noticed the same issue with lockscreen, option was unchecked but it was enabled. I went into the settings for it, enabled/disable and it works as expected... try that.
As for missed call auto responder, I'm not sure what that is...

This ROM is great, I'm on 01/31 nightly and is working great. Thanks!

Gimmie a break, gimmie break, break me off a piece of that kitkat bar!
Good to see it's own thread. The jb one was getting confusing.
I'm currently on 2/3 nightly with aaarghhh's 1/31 cm11 kernel. So far so good.
KK launcher seems to use more battery than the other one included. Is the "ok google" listening enabled the reason? Im guessing having pocket mode on activates the sensor too..
Sent from my MB886 using Tapatalk

Which version of Arrrghhh's should I use? CM11 or AOSP?

mmapcpro said:
Which version of Arrrghhh's should I use? CM11 or AOSP?
Click to expand...
Click to collapse
I assume you mean my kernel, and CM...
Confusing, I spose I should remove the AOSP kernel It's only for pure vanilla AOSP. Most custom ROM's will use the CM kernel.

arrrghhh said:
I assume you mean my kernel, and CM...
Confusing, I spose I should remove the AOSP kernel It's only for pure vanilla AOSP. Most custom ROM's will use the CM kernel.
Click to expand...
Click to collapse
Nah, but something in Carbon's OP could mention "Use the custom CM-11 kernels, not the AOSP ones". Then we'll be able to laugh at people for not reading.
/Nooooooooooo. They're all gonna laugh at you
//But Mom....
/Nooooooooooo
///Anyone else have that CD back in the early 90's?
/Tell your friend Veronica, it's time for Hanukkah
/Drink some Gin and Tonica, and smoke some marijunikkah

skeevydude said:
Nah, but something in Carbon's OP could mention "Use the custom CM-11 kernels, not the AOSP ones". Then we'll be able to laugh at people for not reading.
/Nooooooooooo. They're all gonna laugh at you
//But Mom....
/Nooooooooooo
///Anyone else have that CD back in the early 90's?
/Tell your friend Veronica, it's time for Hanukkah
/Drink some Gin and Tonica, and smoke some marijunikkah
Click to expand...
Click to collapse
Hey goat! One of my favorite albums! He certainly doesn't make it like he used to.
Btw... Carbon rocks! I've used both nightlys with Arrrghhh's kernel and am very impressed.
Sent from my MB886 using Tapatalk

Nice ROM!
It blanked my voicemail which I was able to get from ATT and type in so voicemail works.
However I notice in about/status that for my phone number it says "unknown".
I think my phone has to be re-provisioned but on phone to ATT and so far they don't know anything about it.(EDIT: I hung up and will ignore it - see following posts)
EDIT phone IS able to receive calls to my number. Is this going to happen every time I flash carbon?(EDIT yes. no prob.)

I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.

KrisM22 said:
Nice ROM!
It blanked my voicemail which I was able to get from ATT and type in so voicemail works.
However I notice in about/status that for my phone number it says "unknown".
I think my phone has to be re-provisioned but on phone to ATT and so far they don't know anything about it.
EDIT phone IS able to receive calls to my number. Is this going to happen every time I flash carbon?
Click to expand...
Click to collapse
Probably every time you flash a rom that's CM10.2 or 4.3+.

mmapcpro said:
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
Click to expand...
Click to collapse
There is no device tunables for this device.
Developer Options is just like CM buddy.... click build # several times (7?).

mmapcpro said:
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
Click to expand...
Click to collapse
click "build number" 4 times
EDIT - sorry - DUPE - blush

mmapcpro said:
I can't find "Developer Options" for debugging, in the settings menu. And the Device Tunables is blank.
Click to expand...
Click to collapse
Go to About Phone and tap Build Number 7 times. That enables Developer Options.
I don't think we have any Device Tunables. Checking the sources and/or Arrrghhh can confirm that.
EDIT:
Well, damn, three posts in under a minute. Doesn't get much better than that.

skeevydude said:
Probably every time you flash a rom that's CM10.2 or 4.3+.
Click to expand...
Click to collapse
so do they have to re-provision it?

skeevydude said:
Well, damn, three posts in under a minute. Doesn't get much better than that.
Click to expand...
Click to collapse
lol. Seems this forum is now more active

KrisM22 said:
so do they have to re-provision it?
Click to expand...
Click to collapse
I dunno, that hasn't worked in a while and I'm not sure if anybody is even working on that. Everything works as it should -- those fields are more visual/for reference than anything.
---------- Post added at 12:28 PM ---------- Previous post was at 12:28 PM ----------
arrrghhh said:
lol. Seems this forum is now more active
Click to expand...
Click to collapse
Because this is the best rom as of late.

Carbon Rom Nightlies for M8 look to be live!

I'm sure that someone from the Carbon team will make an official post sometime soon but I periodically check their database and noticed that they now have nightlies for the M8! Woohoo! Was one of my favorites on my MoPho 4G LTE and M7 so looking forward to installing this in just a few minutes.
Here's the link: https://carbonrom.org/downloads/?device=m8&type=nightly
P.S. Hope this is not out of line for me to post before someone from their team does I just wanted to share my happiness! =)

Greetings,
I moved your thread to General and removed the link until it can be confirmed working on the Sprint M8.
Thanks BD619

BD619 said:
Greetings,
I moved your thread to General and removed the link until it can be confirmed working on the Sprint M8.
Thanks BD619
Click to expand...
Click to collapse
Fair enough, good sir. I do not know what exactly you require to show as proof but here are some screenshots I just took after installing^^
Don't judge me on my quick theming, was just trying to show the customizations work =P
After first reboot I did get a Gapps FC but I believe that may be due to the outdated binary I was warned of when installing the Gapps package I used(LiquidGapps from the Liquid Rom download page). Also, this ROM appears to be afflicted with the same forgetfulness as the other AOSP ROMs when it comes to WiFi passwords but so far those are the only things I've come across and one of them was likely my fault.

slimbrady said:
Fair enough, good sir. I do not know what exactly you require to show as proof but here are some screenshots I just took after installing^^
Don't judge me on my quick theming, was just trying to show the customizations work =P
After first reboot I did get a Gapps FC but I believe that may be due to the outdated binary I was warned of when installing the Gapps package I used(LiquidGapps from the Liquid Rom download page). Also, this ROM appears to be afflicted with the same forgetfulness as the other AOSP ROMs when it comes to WiFi passwords but so far those are the only things I've come across and one of them was likely my fault.
Click to expand...
Click to collapse
Thanks for confirming, my concern was it was built for GSM devices, and it would soft brick a Sprint device.
I don't see any harm in posting the link again.

BD619 said:
Thanks for confirming, my concern was it was built for GSM devices, and it would soft brick a Sprint device.
I don't see any harm in posting the link again.
Click to expand...
Click to collapse
No problem. I remembered I think Aarrgghh saying that CArbon wouldn't have a m8 build until Cyanogen unified their m8 devices so I knew once I saw it up there it was going to work for CDMA as well as GSM but I should definitely have posted AFTER installing and trying it if I'm going to promote a link, haha. Thanks for keeping me from possibly doing someone else a disservice.^^
Here is the link again if anyone wants to try it out:
http://carbonrom.org/downloads/?device=m8&type=nightly
The 5/20 build is still running stable for me since I installed last night. Haven't tried the 5/22 one yet but I'm about to. ^^
Happy Flashing!

Added the link to post 1 also

Any other bugs besides Wi-Fi passwords?

Yeah, I've came across another...camera app(native or 3rd party) seems to cause a reboot when opened. Possibly one or two more but i don't know if it would be better to wait for an official carbon thread/dev before i start complaining, haha.
Sent from my One M8 using XDA Premium 4 mobile app

[ROM][4.4.4][UNOFFICIAL] SlimKat Condor [Single Sim Only]

SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat, ROM for the Moto E
Contributors
cybojenix
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2014-06-27
Last Updated 2014-06-27

Latest Build
V1.0, SlimKat 4.4.4 Build 6
Mobile data Doesn't work Confirmed
Auto Brightness doesn't work confirmed SlimRoms bug. It's only being polled every 10 seconds.
As far as I know, everything else is fine
I will upload the device folders at a later point closer to when SlimKat goes official for condor.
The kernel is pretty much stock, with minor edits to make camcorder work, and modules load.

Information and Requests
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
XT1022 Is not supported as neither sim will work.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
I repeat.
Dual Sim is coming soon. Please stop asking
Thank you for being patient with me, but it will all soon pay off
from now on, If a question is asked that is answered already in the first page, or the last ten posts, or one that is easy to find with the search bar, please link this post to them.

Yay!! Thanks for your hard work! Will try this tomorrow
Just one question: Dual sim is supported?

Gogeta said:
Yay!! Thanks for your hard work! Will try this tomorrow
Just one question: Dual sim is supported?
Click to expand...
Click to collapse
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.

Thanks for the work
Thanks for the work... can you send me patches for this..

xperiafan13 said:
Thanks for the work... can you send me patches for this..
Click to expand...
Click to collapse
No but I'll say the approach you should take to fix it.
To build, there is an error that shows from qcom/media. To fix that you had to patch a kernel header. Use git to find the commit the definition is made, and that will fix camera.
To fix bt, check the bt loading script in etc. You will notice there are two blobs missing. Running these blobs will show there is another blob missing.
What other bugs do you have?

cybojenix said:
no but i'll say the approach you should take to fix it.
To build, there is an error that shows from qcom/media. To fix that you had to patch a kernel header. Use git to find the commit the definition is made, and that will fix camera.
To fix bt, check the bt loading script in etc. You will notice there are two blobs missing. Running these blobs will show there is another blob missing.
What other bugs do you have?
Click to expand...
Click to collapse
ok thanks... Im check this... Thanks in advance
you rockss!!!

Mobile data
cybojenix said:
Mobile data untested but probably works (can't test as no sim in)
Auto Brightness doesn't work confirmed SlimRoms bug. It's only being polled every 10 seconds.
As far as I know, everything else is fine
I will upload the device folders at a later point closer to when SlimKat goes official for condor.
The kernel is pretty much stock, with minor edits to make camcorder work, and modules load.
Click to expand...
Click to collapse
Mobile data doesn't work, good work on everything else.
Kind Regards.

First of all congrats man
Here are some of the doubts
Since I have a Indian version moto e (dual sim) as per the given information it won't support so my doubt is if I install this ROM will at least one sim work I don't care about other sim and hate dual sim and do I need to replace any files from stock ROM?
Thanks in advance

cybojenix said:
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
Thank you for being patient with me, but it will all soon pay off
Click to expand...
Click to collapse
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

im always ready to help!!
Hetalk said:
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cybojenix said:
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
Thank you for being patient with me, but it will all soon pay off
Click to expand...
Click to collapse
i do have Teamviewer, Windows 8.1 (ADB), Moto E XT1022 (Stock, Rooted, TWRP)

Hetalk said:
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same as above here ^
Contact anyone of us who are online.

not even single sim working in Moto E XT1022
cybojenix said:
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.[/Q]
woah woaaah woaahhh.... its awwwesommmeeee... loved it but sad thing not even single sim working
atleast make single sim to work!!!
anyway awesome work :good::good::good:
Click to expand...
Click to collapse

iblaziner786 said:
cybojenix said:
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.[/Q]
woah woaaah woaahhh.... its awwwesommmeeee... loved it but sad thing not even single sim working
atleast make single sim to work!!!
anyway awesome work :good::good::good:
Click to expand...
Click to collapse
Slim builds are always awesome.
I use them a lot on my gnexus.
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Ok thankyou to all the people who replied regarding dual sim. You truly are the best community I've been in so far.
Once I've got cm11 rolling I'll contact one of you to set up a build.
I know the fact that slim doesn't support dual sim is a disappointment, so here's the deal. If I get hold of a dual sim moto e, I will bring support for dual sim devices to Slim (probably unofficially).

cybojenix said:
Ok thankyou to all the people who replied regarding dual sim. You truly are the best community I've been in so far.
Once I've got cm11 rolling I'll contact one of you to set up a build.
I know the fact that slim doesn't support dual sim is a disappointment, so here's the deal. If I get hold of a dual sim moto e, I will bring support for dual sim devices to Slim (probably unofficially).
Click to expand...
Click to collapse
Exactly, you can do a weekly(or bi-weeklies) unofficial builds and post them in the same thread.
That would be awesome.:good:

Ok before any mods start messaging me/closing thread, I forgot to push the patched kernel source last night. I get on a computer in an hour or so. Sorry for the inconvenience.

Does it support dual Sim variant as no ROM support dual sim variant
Sent from my XT1022 using XDA Free mobile app

gtsfreak said:
Does it support dual Sim variant as no ROM support dual sim variant
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Please read first page or at least few previous posts always before posting. It should answer your questions.

OSA Development

Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.

OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli

pattyboi:) said:
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
Click to expand...
Click to collapse
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.

OnlySomeDood said:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
Click to expand...
Click to collapse
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop

pattyboi:) said:
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
Click to expand...
Click to collapse
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils

OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere

for sure, that's what this thread is for afterall

OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.

dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.

OnlySomeDood said:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.

no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol

OnlySomeDood said:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty

I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?

OnlySomeDood said:
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
Click to expand...
Click to collapse
can you post one of the errors when you get a sec?
& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?

I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.

OnlySomeDood said:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
Click to expand...
Click to collapse
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it

pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.

dip_spit said:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho

pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.

OnlySomeDood said:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
Click to expand...
Click to collapse
i dont blame you,makes sense to me