[HomeBrews] Pixel 2: LineageOS/CarbonROM/DirtyUnicorns
- Thread starter Ryche666
- Start date
Well that would be a problem then, that is how i'm doing both of them. SIX would active the touch screen and DU without the kernel would be the same thing. With trying to flash DU with the kernel i have tried the way you suggested. I have also tried flashing the rom then flashing the kernel when it boots to the du setup screen it again stops me from using the touch. Right now on the stop .29 rom the touch screen works fine.
Ok when you get to the DU setup screen, at that point fastboot TWRP and install Flash kernel from March. Reboot and your touch screen should work on setup
Sent from my Pixel 2 using Tapatalk
I got Google Framework forced closed and everything else.. What I'm doing wrong? I flashed the DU build, rebooted, then reboot to TWRP and flashed the kernel.
flashed DU, wiped cache, rebooted du setup came up, rebooted back to twrp, flashed FlashKernel-Walleye-v2.21 in twrp and now it just goes to bootloader menu and won't go past. could it have something to do with the boot slot that its set to?
well i got it so the touch screen works but it fc's constantly both SIX and DU fc. I would love to know what people who successfully installed DU and or SIX what they did differently because from what i can tell neither rom works.
in bootloader set boot slot-a, rebooted to bootloader then booted to twrp flashed du, rebooted to bootloader (made note of slot) allowed du to boot to setup screen rebooted to bootloader, making note of slot-a still booted to twrp, flashed kernel, rebooted to bootloader, set slot b rebooted bootloader, then to twrp flashed du, rebooted let du boot to setup screen rebooted to bootloader still slot b rebooted to twrp flashed kernel, rebooted to du setup and everything fc's
rebooted to bootloader then twrp did a full wipe, rebooted to bootloader set slot a booted to twrp flashed SIX (04/02) rebooted to bootloader set slot b reboted to twrp flashed SIX (04/02) rebooted and everything is fc again. what have i done wrong?
if i don't set both slots the touch screen doesn't work.
Last edited:
I also got Google Services Framework force closing constantly on your DU Rom... Are you sure there isn't an issue with the built in GAPPS?
Do a full wipe flash of April factory image. Let it boot, but don't set up. Boot back into TWRP, install it, then clean flash the rom normally wiping system, cache, and data. Then reboot system, ignore no os message.
Holy **** it worked! Thanks for the help! I was just booting twrp from the img when installing the rom, I didn't know installing it first made a difference.
I'm not sure that made the difference, think it was clean flashing the factory first. But glad it worked. I say install TWRP because I'm sure you'll want to get back to it and that's the perfect time to do it. Always right after the rom.
My original instructions was to install TWRP since my first builds would have the same problem if you booted TWRP and not install TWRP.
DU missed a patch that was needed to correct this issue.
I don't care what anyone says... Frankie's ROMS are always the best! wish people would stop getting so butthurt over stuff, it sets back real development. ( good thing i keep copies of his work 
I don't think it will, fast boot is where I flash, push, and I move files manually once phone booted.
In twrp I fash manually with twrp interface. That's me
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29Dirty 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-Today10Update, day 2 now trying to get AICP working. On the plus side, my ubuntu 18.04 is super stable But still haven't figured out why i keep getting 2 errors during builds. Waiting on the main man from AICP to respond back.
Tried Carbon but that was a headache, so back to AICP. If something big happens with Lineage i'll put out a build.10
I'm repo syncing right now. Sorry, the weekends are usually my family time.
It's pins and needles over here since the last time the wife got mad i lost computer privileges for 2 years and she bought me an Samsung S7 so i couldn't build:/
