[ROM][5.1.1_r24][Official][Nightlies]Team-Exodus for Bacon

Search This thread


Senior Member
Mar 30, 2012
Google Pixel 6 Pro


Senior Member
May 14, 2015
dpi change is broke as f*
pictures are in 440. but 460,420,400 is the same,or even worse.
clean flash,everything stock.





Inactive Recognized Contributor
Mar 10, 2013


Senior Member
Aug 2, 2007
dpi change is broke as f*
pictures are in 440. but 460,420,400 is the same,or even worse.
clean flash,everything stock.

You dum fuc k (read back to yourself in Chinese accent).

create build.prop (permissions 644 owner root) in /system/vendor/ put qemu.sf.lcd_density=xxx << **** size in there (SAME VALUE AS YOU SET THROUGH SETTINGS).
Last edited:


Senior Member
Aug 2, 2007
I am surprised that why people are talking for exodus 6.0 in this thread when there is separate thread is available. Please don't post exodus 6.0 issues here, so that dev can easily look over issues related 5.1.1 and issues may not be messed up.

5.1 dead.

No development.

But your right..

Read back in Russian accent.

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

All the hype is dead. Thank god Dirty Unicorns version is amazing.
Test running it, they done some very cool things with the ROM..
Last edited:
  • Like
Reactions: TheCrazyLex

Top Liked Posts

  • There are no posts matching your filters.
  • 258



    Team Exodus brings you EXODUS Rom, coded by professional level developers with additional support from the community, focusing on improved versions of common features and improvements found in the open-source community while bringing new, original improvements and coding with the highest standards.


    • Take necessary backups
    • Be rooted w/ a custom recovery
    • Download EXODUS Rom & Gapps for your device and move them to your phone
    • Reboot to Recovery
    • Wipe (Full wipe if coming from another Rom)**
    • Flash the Rom
    • Flash the Gapps**
    • Reboot to System
    • Setup and Reboot System
    These directions are not necessary after the first install if you use the Exodus Updater, included in the ROM. It can notify you of updates, download, and install them for you automatically.

    **This is automated if coming from a previous Exodus build (Dirty Flashing).


    EXODUS - official: http://www.exodus-developers.net/exodus-5.1/
    GApps: Any 5.1.x GApps of your choice

    Rom source: https://github.com/TeamExodus
    Gerrit: http://exodus-developers.net:8000


    For additional support, info, and updates please join us in the official Google+ community:

    We recommend using our stock (preinstalled) kernel for best results and usage of all features!


    Crowdin project:
    Help us with translating to support your native language!


    Thank you to all the members, contributors, and maintainers on the Exodus Team. Please
    see our source for an unabridged list of contributions, authorship, and cherry-picks.


    If you would like to thank us for our hard work or help support server costs you can do so here:
    MartinRo (Server hosting)
    Primedirective (Team Leader / Main developer)

    Follow us on twitter: https://twitter.com/ExodusAndroid


    Some videos created by savadam (all credits to him):

    XDA:DevDB Information
    ExodusAndroid Bacon, ROM for the OnePlus One

    Martin_Ro, PrimeDirective, Raja.M, TheCrazyLex
    Source Code: http://github.com/TeamExodus

    ROM OS Version: 5.1.x Lollipop
    ROM Kernel: Linux 3.4.x
    Based On: AOSP,CyanogenMod

    Version Information
    Status: Nightly

    Created 2014-09-29
    Last Updated 2015-10-11
    Import Informations

    Changelog for every EXODUS nightly build are here: http://www.vanir-exodus.net/exodus/bacon
    I would like to put this into perspective for those who are asking questions but are not familiar with development.

    Team Exodus's decision to switch from a CM base to an AOSP base is a very good move, but it takes time. AOSP does not build for any device tree natively. One way of building AOSP for a device is by creating or heavily modifying an existing device tree. Of course, to support multiple devices, it is easier to modify the base source than adapt a bunch of device's trees (some devices cannot even have AOSP built for them no matter what). A lot of ROM teams choose to base on CyanogenMod or any pre-existing ROM because they have most of the device changes implemented in their source. When a ROM chooses to base off of AOSP, they must implement the changes by themselves.

    What's the reason for basing on AOSP rather than CM, Slim, or Omni?
    First of all, it is a cleaner source to work with (not saying those ROMs sources are "dirty", I mean it strictly as easier to work with). It is like building a car from scratch the way you like it rather than buying a pre-assembled car and tearing it down to modify the parts. Features can be implemented easier with an AOSP source.

    Also, like the devs mentioned earlier, it is easier to merge AOSP updates. Future revisions of +6.X will come faster. Even Exodus 7.X will probably come faster, too.

    Hopefully this answers the question on why the wait is "too long".
    This rom+kernel indeed supports full f2fs for data and cache ;)

    We work hard on exodus 5.1, especially as we now have an additional developer (Raja) on board. But as we currently also work on an additional complete new wallbreaking new feature (it's called Morph), we still need some time to make everything working. But we are pretty confident that this feature will be liked by a lot of ppl, especially as it will give you a new level of customization on an rom.

    And yes, this is completely new, nothing like that has been done before by any other rom dev ;)
    Hey Guys

    Sorry, was not updating anything from my side for a long time. Please understand was busy with personal stuff ...

    I am still working on 6 for bacon, I know outside 6 based ROMs came out..

    Request you all to be patience for few more days until then please enjoy the experience of exodus 5.1.1

    BTW very important update: Its privileged to welcome @IvanMeler (Exynos Expert) in our team indeed his expertise we can use for OPO to improve few critical areas to bring up 6 with proper working stuff..

    Kindly welcome him ...:)

    Cheers !!!