Related
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
I don't have the skills but I'm willing to support the initiative as far as I can!
Sounds like the same issue i had, check google-cert folder that you have it and also build the files so that you edit default storage path. It was a few months ago i tried to build my own and i ended up with similair problem and it was related to missing cert and wrong storage path.
Im no expert, its just a hobby of mine so i might be wrong
Is Cyanogenmod avialable to Honor 6
Is Cm 11 available to Honor 6
Kanth's said:
Is Cm 11 available to Honor 6
Click to expand...
Click to collapse
No Cyanogenmod available yet, we all wait for.
HTC HD2 has CM12 already ^^
spanorg said:
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
Click to expand...
Click to collapse
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Click to expand...
Click to collapse
Go! go! go!
panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
Click to expand...
Click to collapse
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
Ok, thanks for try to build a CM :good:
Let's hope so!
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
I've no doubt about this. @spanorg please help codeworkx (this IP the thread: http://forum.xda-developers.com/showthread.php?p=58283578).
He's searching for a tester whit competences. I think your help could be more precious now, you are a recognized developer and you can do more than a tester. you can collaborate whit him, and finally became our leader.
(we can ask for donations or other, if possible, to support your works)
Thanks.
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Steve Giordano said:
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-6/orig-development/cyanogenmod-dev-thread-t3008138
please don't build if you don't know what you're doing.
This will not boot into android and requires a ton of work.
codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Do you have a link for the kirin stuff for bionic?
spanorg said:
Do you have a link for the kirin stuff for bionic?
Click to expand...
Click to collapse
sorry, my fault.
just stuff for the bootloader.
vendor/hisi/modem/drv/acore/bootable/bootloader/legacy/arch_balongv7r2
Is this project still active? Just curious.
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
Hello everyone,
the question and disscussion is:
Do we get Lineage OS support in the Future? it does not matter if unofficial or official, but what do you think?
I saw the LeEco le Max 2 get some unofficial support, so it could be that some Devs will try it.
It would be awesome *_*
I think the problem is, that the community isn't that big like for the le Max 2, but maybe it will get bigger in the future.
What do you think? :good:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
I think, it's not discussion, but it is a question. So, it should be in "QUESTIONS & ANSWERS". Le Max 2 have bigger community, because this phone is cheaper and cheapest Le Max 2 was for 180-200$. This mobile is older. Our Le Pro 3 have few months and in future it could have more community and ROMs like this.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Wooow! Someone interested?
It would be awesome!
:fingers-crossed:
Who could we talk to in order to get official support?
I dont know, but to get official support there should be at first a stable unofficial lineage OS Version. I do not know much about creating ROMs but i hope someone does and will create a masterpiece for le pro 3
I hope so
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
corvus said:
I'm running my own custom image of LineageOS 13.0. All is working as expected, but I don't have time to clean all the stuff to share it with public. I uploaded my sources that works in https://www.github.com/corvusmod, so if someone wants to build it, feel free
For L14 version, camera is not working already and will not work until Leeco release N for Pro3
Click to expand...
Click to collapse
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Would be awesome. I will try your build!
Good project looking forward to
manuelbvb said:
Would be awesome. I will try your build!
Good project looking forward to
Click to expand...
Click to collapse
I'll edit a link to the thread I make with to-dos based off the source code I can see.
Here's where I'll post progress!: https://forum.xda-developers.com/le-pro3/development/progress-lineage-os-13-t3546126
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
jts2111 said:
I can continue cleaning of the LOS13. I have quite a bit of free time and want to get started on a project. If corvus doesn't mind, I'll make a thread on my progress and, eventually, some stable builds.
Click to expand...
Click to collapse
robertzas said:
Hi Corvus,
I've been trying to build slim from the repo you forked, but it keeps telling me I have no recovery, and ends up erroring out. I tried on ubuntu 16.04 lts though, could be my issue. Gonna try your lineage 13 version.
Click to expand...
Click to collapse
For Slim, please use the fork from where I get the code. See it in github. It's TS source, so it should work.
corvus said:
Hi @jts2111,
No problem from my side. TS team shared with me the sources, I modified them for Lineage, and try to do some tweaks (already uploades) and have some more in local, but causes some problems, so I didn't upload them.
With this image I get more than 3 days of batt time and a sot of 8 hours, so it's good for me. My only concern is that I was not able to make Camera2 HAL working to get manual settings. But I have little time to test, so any help from this side is welcome.
Only one thing, please, share the code in a public repo so TS, me or any other developer can see it and work together.
Thanks
Click to expand...
Click to collapse
I forked your repo and shared it in my post. I'll work on what you mentioned. One of my top (long term) goals is complete CTS compatibility. With safetynet passed, there'd be nothing that would really pull you back to stock.
Definitely, I'm preparing the Kernel code after code to ensure we get a very clean and functional Kernel for the future, instead of just merging the one from LeEco with more than 80% of unneeded bits due to their other devices being at the same place (shameful).
This will get a ~30MB Kernel reduced to around 12MB and thus make custom ROMs perform a lot better and boot immensely faster after all.
I'd only need one sense of common attitude which is asking LeTV to keep the Kernel source up-to-date when they launch OTAs as well, I've seen some comments regarding their image stabilization fix at latest release (OTA) which is only possible at Kernel/blob level and thus if we want to have this feature working (at least partially) we need the source code "right off the bat" to get those fixes. Please, make pressure on their forums for 5.9 x720 Kernel source code and for nougat preview builds, I'd appreciate to even help with their own EUI for that matter, I'll see if I can get in touch with them concerning those points.
Do we have someone from China or someone with experience with Chinese so we can attach our discussions there?
I do hope they keep the open source up to date, but it seems they are doing the bare minimum to apply to Google's open source policy. I'm in the US, so I have the x727 with 1 SIM. We would need someone to test with a x720 as well.
@GalaticStryder, Leeco only will post the sources needed to avoid license problems with GPL, so dont wait much help from them. But we can ask...
@jts2111, I have a 720, so I can test your builds.
@jts2111
I received my X720 this week and I could also test your experimental build.
It would be nice to already start with a LineageOS custom ROM as first ROM to avoid a lot of reinstallation / reconfiguration of apps with other kind of custom ROMs.
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.
When will sailfishos ever appear? I love Linux/GNU and I want to see this OS on whyred
If you port it.
Not worth it. Not enough people will use it
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Not worth it. Not enough people will use it
Click to expand...
Click to collapse
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
TITANIST26 said:
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
Click to expand...
Click to collapse
We have lineageos 14.1
https://www.google.com/amp/s/forum..../development/rom-lineageos-14-1-t3765529/amp/
I think its a pretty good idea. Just because some people don't use them doesn't mean its useless.
Sailfish is already present for redmi note 5 / 5 plus. It would be a great addition for our note 5 pro too
a2p1k02 said:
We have lineageos 14.1
Click to expand...
Click to collapse
Need not assembled ROM * .zip, and you need to have a device tree, branch cm-14.1 (device_xiaomi_whyred, kernel_xiaomi_whyred, vendor_xiaomi_whyred on Github). And it is not there, only lineage 15.1. I will try to collect lineage
karan5chaos said:
reply
Click to expand...
Click to collapse
I did not find the https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484 instruction for building specific files for the device tree and google too not found. Found the old for cm 11 or others do not describe a sufficiently assembly system. Help me find this guide!
I think people have ported sailfish using lineage 15.1 as well. Did you check maemo.org? I'm sure you will find the required guide there.
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
TITANIST26 said:
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
Click to expand...
Click to collapse
You are my hero !
Thank you so much for your efforts and persistence. It's because of members like your this community is thriving. I will gladly be a tester and report back issues and feedback if any.
karan5chaos said:
Reply
Click to expand...
Click to collapse
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
TITANIST26 said:
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
Click to expand...
Click to collapse
I think the question at stack overflow did mention some fix in second answer. Did you try that ?