Develop Bugs

30/Jun r1 (JFB) - MoDaCo Custom ROM for Samsung Galaxy S with Online Kitchen

I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/

Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.

Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!

woohoo custom ROMs already. Guess I'll be getting myself the phone after all.

umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?

Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.

Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?

Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean

psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.

Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.

That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.

psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?

what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.

Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?

dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?

raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.

they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?

Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?

well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here

Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..

[ROM] Guardian Rom [Secure] [Privacy] [Milestone 1]

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 AOSP. It is Milestoneso 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.
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Click to expand...
Click to collapse
Coming Soon:​
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:
Added Deniable Encryption using Mobiflage
Encryption is now AES-256bit-XTS instead of 128bit-CBC
.​

I'll be keeping an eye on it. Good work.

While this looks like a very interesting project and could have very promising applications (particularly in the military/government sector), most users on this site will undoubtedly complain about the horrendously slow speeds this many layers of encryption will bring.
Best of luck to you, though.

Hungry Man said:
I'll be keeping an eye on it. Good work.
Click to expand...
Click to collapse
:good:
psyren said:
While this looks like a very interesting project and could have very promising applications (particularly in the military/government sector), most users on this site will undoubtedly complain about the horrendously slow speeds this many layers of encryption will bring.
Best of luck to you, though.
Click to expand...
Click to collapse
True. Speed is not the goal. Although there isn't to much slow down actually. But it is a sacrifice for security.

thanks. looking very interesting.

un.droid said:
thanks. looking very interesting.
Click to expand...
Click to collapse
Thanks! Milestone 1 is now up.
Brings Mobiflage (Deniable Encryption) and a easy installer. New base is AOSP.

Interesting
x942 said:
Thanks! Milestone 1 is now up.
Brings Mobiflage (Deniable Encryption) and a easy installer. New base is AOSP.
Click to expand...
Click to collapse
Are you working this still? This is an interesting concept. Has anyone out there been using this over time?

tt100b said:
Are you working this still? This is an interesting concept. Has anyone out there been using this over time?
Click to expand...
Click to collapse
Yup. Everything is moving quickly on twitter and my website. I only post here when new version are released. Stable version is underway just testing and fixing last Minute bugs. :good:
Main features coming:
PDroid is enabled now with GUI present
SuperUser works properly
Encryption GUI is present in some form or another*
Windows and Linux installers
*Encryption GUI will either be an APK that calls vdc on the device. OR will be baked into the Installer on Windows, Linux, and Mac OS X.

[Rom][6.0.0/5.1.1(Not Sure)][DM][OMNIROM Build Modified][BigPart][Alpha]

Hi And Welcome To a Non-Tested Version of Android 6.0.0 on the xoom (Maybe 5.1.1 Not Sure) But back to the topic
This is mostly 5.1.1 but maybe with new of fixed features (I've never tested it as I said)
Here is how to install (I found this on another area)
1. ROOT YOUR DEVICE
2. Install BigPart TWRP
3. Wipe your system and flash the zip file
Here is the zip file
(I'm having Issues of Attaching The File So Please Wait)
XDA:DevDB Information
Android 6.0.0 or Android 5.1.1, ROM for the Motorola Xoom
Contributors
MichaelTech, Schischu, dreamcwli, michie
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 2.6.x
ROM Firmware Required: Rooted BigPart
Based On: OmniRom
Version Information
Status: Alpha
Created 2015-11-19
Last Updated 2015-11-19

so is this rom 5.1.1 or 6.0? id love to try it out...

I just resurrected my old xoom and converted it to bigpart.
waiting for the zip....

Waiting for test it.

Did you build this rom? If so, how can you not know what version of Android it is?

MichaelTech said:
(I've never tested it as I said)
Here is how to install (I found this on another area)
Click to expand...
Click to collapse
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!

sdthelord said:
Can you provide more information please?
Just "copy n paste" from "other area" is not very trustworthy... i'm sorry to say.
I would love to have 6.0 on Xoom, but I want it to be wit ha Git Repo or anything and not only an ominous zip file from somewhere...
so please, more information is the key!
Click to expand...
Click to collapse
Based on this post, I think that, best-case scenario, he just kanged Schischu's 5.1.1 build and maybe themed it to look like 6.0. But I'm betting we never see a zip file.

As with everyone else I am curious to this. [6.0.0/5.1.1(Not Sure)] <--- this seems a little strange. It can only be one Android version. If it's 5.1.1 with some cherry picks and tweaks, that's great but just say.
Also some source would be good so we can establish what it actually is. Upload to androidfilehost or something similar if you can't attach.

P.S OmniRom wanted me to make a rom so perfectly fine

MichaelTech said:
P.S OmniRom wanted me to make a rom so perfectly fine
Click to expand...
Click to collapse
Look we shouldn't be fighting about whos rom it is It's just code that matters

MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Here is the error I keep getting
 vBulletin Message
Invalid post specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
but nothing happened to this page so what is this problem

MichaelTech said:
Look we shouldn't be fighting about whos rom it is It's just code that matters
Click to expand...
Click to collapse
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?

brewer75 said:
Speaking of ROM's, when can we expect yours? If the item you posted in #11 is still the zip attachment problem, have you thought about trying the suggestion from Matt4321?
Click to expand...
Click to collapse
I can when you solve my problem I keep having

MichaelTech said:
I can when you solve my problem I keep having
Click to expand...
Click to collapse
The Download is now available in the downloads tab
here is info
Modified Launcher3
Modified SoundRecorder
Modified PackageInstaller
Android 5.1.1 with tweaks
gapps and super su are not included so please download them

If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.

michie said:
If the OP did not do some coding on our outdated kernel and just synced omnirom sources, or even worse, just replaced some apk's in the flashable zip, all bugs are still there. If you did alter the kernel code you have to apply to GPL and post kernel sources.
I don't mean any disrespect but I kinda have the feeling that you don't have alot of experience with coding. (Please correct me if I'm wrong though) Posting untested software can give inexperienced users alot of problems and could be potential dangerous with our altered partion layout.
This wont have any benefit over Schisu's rom for now so I really have to advise you to wait for updated kernel sources before posting.
Click to expand...
Click to collapse
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder

Download not possible. File not found.

MichaelTech said:
First yes that was very mean
second many other roms use these old kernels like OmniRom 5.1.1 for the xoom
third im a level 8 of 10 coder
Click to expand...
Click to collapse
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.

michie said:
Like I said, I don't mean any disrespect my friend. The Xoom needs talented developers but not knowing if your rom is android 6 or 5 raises questions
You should contact the old member of team EOS or Schischu.
Good luck.
Click to expand...
Click to collapse
I mostly belive its android 5.1.1

MichaelTech said:
im a level 8 of 10 coder
Click to expand...
Click to collapse
How many more XP do you need before you level up to 9?
What a joke...

[ROM][SUBSTRATUM][N9] Krexus 7.1.1 [OFFICIAL] [03.09.2017]

krexus_7.1.1-170309-flounder.zip - https://www.androidfilehost.com/?w=files&flid=144667 March security updates & Rootless Substratum
THINGS TO READ BEFORE ASKING:
Use N4F26T Vendor Image for 03/09.2017 build.
Stock kernel does not force encryption.
Not prerooted.
Built for the Nexus 9 Wifi (but it works on Nexus 9 LTE too. Flash latest volantisg vendor IMG and manually set APN)
Originally Posted by @KreAch3R
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested ON HAMMERHEAD, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, mako, shamu builds are provided AS-IS, and bugs/missing stuff/features especially for them will be put on the lowest priority and will depend on my free time. I will only guarantee the nexus 5 ROM and its abilities.
That said, welcome aboard!
Click to expand...
Click to collapse
Google+ Community
PushBullet Channel
DOWNLOAD LINKS:
KREXUS on AndroidFileHost
Previous Builds
CHANGELOG
Source Code: https://github.com/krexus

When @KreAch3R started building this ROM for shamu in 2015, I jumped on board right away. I've got Krexus running on every Nexus in my family: mako, hammerhead, shamu, grouper, and NOW flounder.
It runs beautifully on flounder and I hope you enjoy it too.
I am extremely grateful to @KreAch3R for all of his help and support.
IMPORTANT POINTS:
You have to flash GApps (Open or BaNks recommended)
ROM is not rooted, flash stable SuperSu for root
Busybox is included
Included kernel is stock no-force-encrypt
Flash newest factory vendor.img (I had Layers issues with stock selinux enforcing kernel on an older vendor version. Newest vendor.img works perfectly with stock kernel enforcing and layers)

F.A.Q.
a.k.a questions you shouldn't repost
Check the always updated F.A.Q.:
https://plus.google.com/+GeorgeGian/posts/f9m7zmi42Gy
OR
https://docs.google.com/document/d/1hMX-lQ2iUiNsrhszMIlp0Wwj1tSHWvsaEQ_yT4pD_eE/edit?usp=sharing?
BELIEVE ME, THE QUESTION YOU HAVE IS PROBABLY ANSWERED THERE.

Thank you for supporting the building for flounder, @buffal0b1ll!
For the next build, I will try to make Layers work with the default google kernel, and fix the processor info.
I want to specifically thank @BeansTown106, which device trees and blobs I used for this bringup.
Enjoy Krexus!

Another more conspicuous link for the Krexus G+ community.
https://plus.google.com/communities/117603046007221302455/
You will want to join this community if you like Krexus. It's very beneficial to hear user and developer advice/feedback and experiences across all supported devices.

Firsties!
Sent from my Motorola Nexus 6 using XDA Labs

Finally, we are starting to get some more quality ROM builds for this device. This is just awesome.

KreAch3R said:
For the next build, I will try to make Layers work with the default google kernel
Click to expand...
Click to collapse
Layers actually works fine with the default kernel and SELinux enforcing. An up to date vendor.img flash was all I needed to fix that.

Is charging extremely slow for anyone else? Latest Fire&Ice kernel.

dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
Try the purenexus version of fire & ice
Sent from my Nexus 9 using XDA-Developers mobile app

dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
I'm still using fire-ice 10.2.2 and haven't noticed slow charging. In 18 minutes I went from 27 to 35% just now. Ampere has me charging at 1460 mAh

Thanks for a great rom! Will it work with LTE version?

maelfilk said:
Thanks for a great rom! Will it work with LTE version?
Click to expand...
Click to collapse
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.

KreAch3R said:
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
Click to expand...
Click to collapse
Will try it out on the weekend and report

Works great with LTE version!:good:

maelfilk said:
Works great with LTE version!:good:
Click to expand...
Click to collapse
That's awesome! Any hoops you had to jump thru?

buffal0b1ll said:
That's awesome! Any hoops you had to jump thru?
Click to expand...
Click to collapse
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.

maelfilk said:
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
Click to expand...
Click to collapse
Sweet. Not even a vendor fingerprint mismatch?

buffal0b1ll said:
Sweet. Not even a vendor fingerprint mismatch?
Click to expand...
Click to collapse
I always flash vendorfix in twrp to 100% avoid this error so can't tell

maelfilk said:
I always flash vendorfix in twrp to 100% avoid this error so can't tell
Click to expand...
Click to collapse
Got it. FYI I'd been manually vendor fixing the fingerprint since December on the Wi-Fi flounder and had layers issues on the stock enforcing kernel. Fire ice made it work with the old hacked vendor partition. To make layers work with stock kernel i updated to may factory vendor.img

[HomeBrews] Pixel 2: LineageOS/CarbonROM/DirtyUnicorns

Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Pre-Disclaimer:
THIS IS AN UNOFFICIAL BUILD. The intent is to showcase what is coming up soon. I have been working hard on getting Walleye on a level I consider DD ready, especially from a security side of things.
Please keep any problems with those builds in this thread, I don't accept any bug reports for any other builds other than my HomeBrews.
Disclaimer:
While I make every effort to test these builds as much as possible, I am not responsible for anything that may happen to your device. I ask that you do your part to know your device and know how to recover from problems before you flash or post that you broke your phone!
Support:
I spend an astonishing amount of time developing this device. I 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) Ask a question in this 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.
Notice:
This build includes GApps for now. We're still working on ways to not prebundle it.
Before you flash, make sure you're on the latest 8.1 stock builds (and bootloader), then flash the ROM in TWRP.
Instructions :
Boot to TWRP
Format Data (If you didn't type YES, you did it wrong!)
adb sideload homebrews.zip
reboot system
(to gain root you must first boot homebrewsROM. Then reboot and to TWRP and install Magisk 1 6.0)
See below
Reporting Bugs:
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
What is your--
Build Date:
Did you--
wipe:
all data?
install gapps when you weren't suppose to?
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
WARNING: These are my personal testing builds. They include unmerged, work-in-progress stuff such as SuperUser, Privacy Guard, Google Play services etc. DO NOT FLASH 3RD PARTY GAPPS PACKAGES!
If you see a warning about vendor partition mismatch, you can ignore that in most cases, but before reporting issues you should be on the right version (without the warning).
### RELEASES ###
https://drive.google.com/drive/folders/1NY1j-eH9demisz5Y05jeIPGXipENo5yK?usp=sharing
XDAevDB Information
LineageOS, ROM for the Google Pixel 2
CarbonROM, ROM for the Google Pixel 2
DirtyUnicorns, ROM for the Google Pixel 2
Contributors
Source Code: http://github.com/LineageOS
Source Code: http://github.com/CarbonROM
Source Code: http://github.com/DirtyUnicorns
Source Code: http://github.com/TresReinosDeLeche
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
### DONATE ###
paypal.me/JacobStermer
Created 2018-02-2
Last Updated 2018-03-Today

reserved

Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.

I for one am happy to see it.

iluvamk said:
I for one am happy to see it.
Click to expand...
Click to collapse
Me to ? do we need to flash twrp after the ROM like on pixel 1?

GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.

Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse

Archangel said:
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
Click to expand...
Click to collapse
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?

Let us know how it goes brother.
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse

jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.
right now i am getting FC on Camera APP, X Google, Ok Google, and T Google something. My computer just crashed building the potential fix.

Ryche666 said:
boot to twrp.
wipe all data
adb push lineageos
reboot to bootloader
boot to twrp
adb push magisk
reboot to system.
right now i am getting FC on Camera APP, X Google, Ok Google, and T mobile something. My computer just crashed building the potential fix.
Click to expand...
Click to collapse
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy

jasonsamms666 said:
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
Click to expand...
Click to collapse
Sorry, i got super anxious myself when i finally got playstore, phone, and text messaging working.
Thus the piss poor thread that i copy and pasted from taimen's lineage.

GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.

Ryche666 said:
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Click to expand...
Click to collapse
FWIW this is what's been done with the Essential Phone.

razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
I was the same way. A **** ton of reading and a lot of PMing. It is pretty simple when you get the hang of it. This early in the game you get to see the codes that attract you to certain roms or kernels.
Right now i just need to make sure it is stable before i work on the kernel or choose what rom i am gonna stick with.

NadavCE said:
FWIW this is what's been done with the Essential Phone.
Click to expand...
Click to collapse
That's what i heard. If i knew that last weekend we would have had that much sooner.

Awesome, glad to see some work

Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666

Chronzy said:
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Click to expand...
Click to collapse
Can you share the complete steps and details on how you flashed it? Thank you!

infamousvincci said:
Can you share the complete steps and details on how you flashed it? Thank you!
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.