{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For instructions about installing or building for toro, see the wiki: http://wiki.lineageos.org/toro_info.html.
Builds can be found at https://download.lineageos.org/toro.
Bugs:
- No data out of airplane mode; reboot to fix.
- Initiating a new sim may not work; install a kitkat or older ROM to initiate sim.
Google Apps can be found at http://opengapps.org/?api=6.0&variant=pico. Please note that only the pico version will fit, unless you have changed your partitions sizes.
XDA:DevDB Information
LineageOS 13.0, ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs, Ziyan
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-04-19
Last Updated 2017-03-25
After over a year and a half, we once again have official CyanogenMod builds.
Official builds have been bumped up to cm-13.0. A cm-12.1 snapshot is available on get.cm.
thanks much. going to wait for the august patches to get merged in before moving over from your previous unofficial build.
error (failed) flashing cm13
My Nexus (maguro) was bricked (my own fault).
I put back the original android 4.3 with fastboot. That went well. Now I want to put it cm13. It fails. Flashing with recovery ter 8.7.0 failed, also "fastboot -w update ....zip" went wrong "cannot load ...zip". Nexus is rooted.
Then I tried to flash a different zip namely Euphoria 5.1 for maguro. I used to flash the recovery. That went okay. But I prefer CyanogenMod.
So now I real want to flash the latest cm13, but I can not. I get a failed.
Also fastboot -w update "cm13....zip" does not work.
What am I doing wrong?
greeting Lucas
lucascaw said:
My Nexus (maguro) was bricked (my own fault).
I put back the original android 4.3 with fastboot. That went well. Now I want to put it cm13. It fails. Flashing with recovery ter 8.7.0 failed, also "fastboot -w update ....zip" went wrong "cannot load ...zip". Nexus is rooted.
Then I tried to flash a different zip namely Euphoria 5.1 for maguro. I used to flash the recovery. That went okay. But I prefer CyanogenMod.
So now I real want to flash the latest cm13, but I can not. I get a failed.
Also fastboot -w update "cm13....zip" does not work.
What am I doing wrong?
greeting Lucas
Click to expand...
Click to collapse
Are you trying to flash this TORO build to your MAGURO device?
That may be your first problem.
phonetool said:
Are you trying to flash this TORO build to your MAGURO device?
That may be your first problem.
Click to expand...
Click to collapse
I do not think so.
I tried cm-13.0-20160731-NIGHTLY-maguro.zip and other dates. that's maguro and not toro, I think, I hope.
greeting Lucas
lucascaw said:
I do not think so.
I tried cm-13.0-20160731-NIGHTLY-maguro.zip and other dates. that's maguro and not toro, I think, I hope.
greeting Lucas
Click to expand...
Click to collapse
Yes, that is for maguro. This is the toro thread, though. The maguro thread is here.
My first guess is that your recovery is too old to flash cm13.0 Try this build of TWRP.
musical_chairs said:
Yes, that is for maguro. This is the toro thread, though. The maguro thread is here.
My first guess is that your recovery is too old to flash cm13.0 Try this build of TWRP.
Click to expand...
Click to collapse
Thank You, I'll try.
Lucas
Would the latest nightly (08/06) include the full August security patches outlined in https://source.android.com/security/bulletin/2016-08-01.html ?
AceNJ said:
Would the latest nightly (08/06) include the full August security patches outlined in https://source.android.com/security/bulletin/2016-08-01.html ?
Click to expand...
Click to collapse
Yes, it should, the patches were merged several days ago.
musical_chairs said:
Yes, it should, the patches were merged several days ago.
Click to expand...
Click to collapse
thanks for confirming. i've been wanting to do a clean reflash so if this has all the patches as of 08-05 then it's a good time
I am having occasional WiFi drops. Always happens with screen off. Wake up the screen and WiFi is off and no data. I read recently of a similar problem on the Galaxy Note Pro forum and some believe it to be a CM glitch.
http://forum.xda-developers.com/showthread.php?p=68754215
Anybody else having this problem?
My wifi does drop very frequently, even during use. In-fact I really only notice it while using the phone. Interestingly for me, I don't think it's a ROM specific issue but can't really confirm it. Even more odd is that I NEVER drop when connected to an iPhone hot spot, it's only when connecting to actual wifi routers. I thought it might be band based but I struggle with both 2.4 and 5ghz. I just kind of have learned to live with it at this point; spent way too many hours trying to resolve.
Everytime I attempt to flash this with the nano gapps, I get an error 70 stating that there is not enough available space on the system partition. I have wiped system with each flash and wiped dalvik/cache between rom and Gapps. Is there a workaround for this or am I doing something wrong? Its been quite a while since I've flashed anything to this phone, so I'm a bit rusty.
Thanks!
eric2112 said:
Everytime I attempt to flash this with the nano gapps, I get an error 70 stating that there is not enough available space on the system partition. I have wiped system with each flash and wiped dalvik/cache between rom and Gapps. Is there a workaround for this or am I doing something wrong? Its been quite a while since I've flashed anything to this phone, so I'm a bit rusty.
Thanks!
Click to expand...
Click to collapse
Things keep growing and nano gapps no longer fit either. You need to use the pico gapps. I corrected the instructions in the OP.
Thank you.
If any users on Page Plus (and maybe Straight Talk) have lost mobile data, here is a flashable zip that should fix it. Do not flash this if you're on Verizon, and do not flash it if your data is currently working. This fix should work on pretty much any ROM KitKat or newer.
Page Plus has made some changes to their APNs and it breaks data for us. Stock ROMs should be able to load the updated settings themselves, but that doesn't seem to work for this ROM. It's a minor change really; the APN needs to change from VZWINTERNET to TRACFONE.VZWENTP for data to work.
eric2112 said:
Everytime I attempt to flash this with the nano gapps, I get an error 70 stating that there is not enough available space on the system partition. I have wiped system with each flash and wiped dalvik/cache between rom and Gapps. Is there a workaround for this or am I doing something wrong? Its been quite a while since I've flashed anything to this phone, so I'm a bit rusty.
Thanks!
Click to expand...
Click to collapse
There is a note on the very first page of this thread (and in the CM wiki) that the NANO GApps (especially the Open sort) may well be too big - heed it! I used the pico Open GApps without trouble on my own GNex (inherited from my mom as she moved to a Galaxy J3; I'm taking the GNex to Tracfone once I get a SIM kit - replacing an existing Tracfone feature phone). In a word - smirk, smirk, smirk....
will there be no further development on this in 2017?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys, This is my port of the awesome Euphoria-OS.
I stopped supporting this rom
but as of 13th sept 2015, I am back
DOWNLOADS
You can click here DOWNLOADS for the ROM
GApps here (5.1 only)
THIS ROM SUPPORTS LVM, COLDBIRD Unification and Stock.
Installation Instructions
- Make sure you're running Nameless TWRP Recovery
- Make sure you updated your modem (Flash latest CM nightly)
- Make sure you updated your TrustZone firmware (Install latest CM nightly for it)
-No need to flash any modem or any CM nightly. Modem is now included in the ROM
- Copy GApps and ROM to your internal/external SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET
- Flash Euphoria-OS zip
- Flash GApps zip
-Flash Supersu
- Reboot and profit!
LVM UNIFIED
To set up LVM, download this zip and flash it via recovery
To remove LVM, download and flash this zip
COLDBIRD UNIFIED
We are offering unified versions, using Coldbird's unification method. Please have a look at
this thread (http://www.oppoforums.com/threads/tutorial-unified-storage-layout-for-oppo-find-7a.17952)
CREDITSEuphoria-OS Team
CyanogenMod
Euphoria-OS Team
XDA:DevDB Information
[5.1] Euphoria-OS, ROM for the Oppo Find 7a
Contributors
suraj.das
Source Code: https://github.com/Euphoria-OS-Legacy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CM12 Firmware/Modem
Based On: CyanogenMod
Just in case..
Nice, I was planning on making it, but you were faster.
Definately going to give it a try.
your device trees sure helped a lot
Wow yet another port , freking great
Dl ......
Thx a lot
What kind of storage does that rom use ?
Vanilla ?
Unified ?
LVM ?
None of the above ?
thx a lot for bringing more choice to our Find7
theradec said:
What kind of storage does that rom use ?
Vanilla ?
Unified ?
LVM ?
None of the above ?
thx a lot for bringing more choice to our Find7
Click to expand...
Click to collapse
stock partition only..
but it might change in the future..
What a beast you are
New build is up guys! Use the first "download" link in OP to get it.. ill be uploading on the second link too, in a minute!!
Changes - Check Euphoria's gerrit.
Sync was done like 7 hours back!
Used a new toolchain. UBER TOOLCHAIN 4.8 for ROM and 4.9 for kernel!
Everything is frikking smoother and faster now.
SELinux is set to permissive. I like it that way.
I am still looking to implement LVM. Might take time. I am a NOOB
I've tried both beta's and they both run extremely smooth. Only problem I've had with both is when someone sends me a text I get unfortunately messenger has stopped on both beta's. I've tried clean installs on both coming from nameless then tried clean install coming from cyanogen 12. Tried cleaning data and cache from messenger app but nothing has worked. Everything else has worked but receiving texts. Correct APN was verified so I'm at a loss.
JRW 28 said:
I've tried both beta's and they both run extremely smooth. Only problem I've had with both is when someone sends me a text I get unfortunately messenger has stopped on both beta's. I've tried clean installs on both coming from nameless then tried clean install coming from cyanogen 12. Tried cleaning data and cache from messenger app but nothing has worked. Everything else has worked but receiving texts. Correct APN was verified so I'm at a loss.
Click to expand...
Click to collapse
I can say, I am experiencing the same. Using Google Messenger for the meantime.
Smooth builds.
carlsbad28 said:
I can say, I am experiencing the same. Using Google Messenger for the meantime.
Smooth builds.
Click to expand...
Click to collapse
I've seen where people were having same issues with cyanogen 12.1 as well so might be an underlying issue there. Wish they could get it resolved for what time I've played with this ROM I'd love to give it more time as a daily driver but I need to be able to receive texts. Other then this issue the work looks very good and promising.
WiFi is broken when flashing SuperSU for root.
ROM worked fine prior.
carlsbad28 said:
I can say, I am experiencing the same. Using Google Messenger for the meantime.
Smooth builds.
Click to expand...
Click to collapse
JRW 28 said:
I've tried both beta's and they both run extremely smooth. Only problem I've had with both is when someone sends me a text I get unfortunately messenger has stopped on both beta's. I've tried clean installs on both coming from nameless then tried clean install coming from cyanogen 12. Tried cleaning data and cache from messenger app but nothing has worked. Everything else has worked but receiving texts. Correct APN was verified so I'm at a loss.
Click to expand...
Click to collapse
sorry guys. I didnt get that error because I install Hangouts as soon as I boot a new rom.
I will try to see what the problem is.
Next build will come in a day or two. My exams are on so thats why.
Lets hope its fixed on the build. Btw I uploaded a new build on AFH. You could try that for the time being
carlsbad28 said:
WiFi is broken when flashing SuperSU for root.
ROM worked fine prior.
Click to expand...
Click to collapse
which version of supersu? No one else has reported this bug. Could be an issue on your end?
suraj.das said:
which version of supersu? No one else has reported this bug. Could be an issue on your end?
Click to expand...
Click to collapse
Same here, after deep sleep , wifi is gone and need reboot , then it's working again!
Super su 2.46
Thanx for a great build
(Just flashed beta 2.48, wifi speed is back at normal again, it was extremely slow and sluggish on 2.46?)
spoonymoon said:
Same here, after deep sleep , wifi is gone and need reboot , then it's working again!
Super su 2.46
Thanx for a great build
(Just flashed beta 2.48, wifi speed is back at normal again, it was extremely slow and sluggish on 2.46?)
Click to expand...
Click to collapse
Thanks, will try out 2.48
Everything actually works at first boot. ROM backups my apps through cloud. But after restarting, WiFi breaks and am unable to fix the issue until I do another clean install. Only happens on 5.1, can't replicate it on 5.0.2.
EDIT: Scratch that, I actually flashed 2.48 :banghead: Wonder what the issue is.
carlsbad28 said:
Thanks, will try out 2.48
Everything actually works at first boot. ROM backups my apps through cloud. But after restarting, WiFi breaks and am unable to fix the issue until I do another clean install. Only happens on 5.1, can't replicate it on 5.0.2.
EDIT: Scratch that, I actually flashed 2.48 :banghead: Wonder what the issue is.
Click to expand...
Click to collapse
is it working now?
Wifi works with 2.48, but no way rom will enter deep sleep!
Even changing sleep mode in kernel tweaker doesn't change anything!
spoonymoon said:
Wifi works with 2.48, but no way rom will enter deep sleep!
Even changing sleep mode in kernel tweaker doesn't change anything!
Click to expand...
Click to collapse
This deep sleep problem is really weird. Which gapps do you use?
I am using the gapps that I linked in the OP. and phone enters to deep sleep just fine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OmniROM
Android 7.x
Samsung Galaxy Nexus (Unified)
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
TWRP with hardware decryption support can be found here
[#INFOOMNI]
[#DONATETOME]
XDA:DevDB Information
[unified] OmniROM 7.x, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Testing
Created 2017-08-18
Last Updated 2017-08-18
Reserved
Some screenshots attached
Thanks for your work. IDK if it is really useful to setup jenkins as you will probably use official one soon but just for my mental health:
Code:
awk: line 1: syntax error at or near ,
[snip]
cat: vendor/samsung/tuna/NOTICE: Is a directory
build/core/notice_files.mk:71: recipe for target '/var/jenkins_home/workspace/omni/out/target/product/maguro/obj/NOTICE_FILES/src//system/vendor/lib/libfrsdk.so.txt' failed
make: *** [/var/jenkins_home/workspace/omni/out/target/product/maguro/obj/NOTICE_FILES/src//system/vendor/lib/libfrsdk.so.txt] Error 1
make: *** Deleting file '/var/jenkins_home/workspace/omni/out/target/product/maguro/obj/NOTICE_FILES/src//system/vendor/lib/libfrsdk.so.txt'
Why does it add '.txt' near the filename?
I was able to find the target into vendor/samsung (obviously without .txt)
Here is the manifest and as you already know am picking all the open commits to build maguro.
Any advices?
P.S.: leo build find on the same host.
Sorry, forgot to merge a pull request, fixed
https://github.com/DonkeyCoyote/pro...mmit/877e9057145ec602ebfefa74b0fa7dfc05ebb634
And yeah, once I got some feedback here I'll try to get official weekly builds.
I know most user love Lineage, but I think Omni is one of the most interesting ROMs with a lot of own features (most other ROMs are a collection of features from many roms without own features).
I'll watch the Download count on all ROMs I provide and check which ROMs are worth to compile and which aren't.
Android-Andi said:
Android-Andi said:
Sorry, forgot to merge a pull request, fixed
https://github.com/DonkeyCoyote/pro...mmit/877e9057145ec602ebfefa74b0fa7dfc05ebb634
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Code:
Package complete: /var/jenkins_home/workspace/omni/out/target/product/maguro/omni-7.1.2-20170819-maguro-nailyk.zip
Many thanks! Download is available in the link I sent you in a PM. Builds are made every nights.
nailyk said:
Code:
Package complete: /var/jenkins_home/workspace/omni/out/target/product/maguro/omni-7.1.2-20170819-maguro-nailyk.zip
Many thanks! Download is available in the link I sent you in a PM. Builds are made every nights.
Click to expand...
Click to collapse
is GPS working?
any other issues?
"phone.android.com" error message pops up for me every 2 seconds after booting. Went to another ROM for a couple days then reflash Omni but still the same problem. Just me?
Old TWRP? Dirty flash?
Android-Andi said:
Old TWRP? Dirty flash?
Click to expand...
Click to collapse
Factory wipe with twrp-3.1.1-0-toro-decrypt-lzma.img.
I'm on slim now, but I'll try it again to see if it repeats. I have nothing better to do, heh.
edit: oh and the error is "com.android.phone has stopped"
Attach a logcat please if it happens again.
Here ya are.
chinojuice said:
Here ya are.
Click to expand...
Click to collapse
Thx. Does it work in selinux set to permissive? There's on selinux denial maybe related to it.
Android-Andi said:
Thx. Does it work in selinux set to permissive? There's on selinux denial maybe related to it.
Click to expand...
Click to collapse
Yes, still persists.
This maybe isn't the right forum, but what is the overall state of options right now for maguro? I have encrypted storage, and 1) the TWRP version from here, while it sometimes can mount storage (necessary if I want a full install of a new ROM, and not a sideload) more often than not fails to mount storage, and reboots into the OS when trying; 2) I have the last nightly from CM-13 from last year, and it's not very stable.
Is there a version of TWRP that works better than the custom version 3.0.0 that ziyan released for maguro last year?
If so, is the L-OS from here more feature-rich/stable than the one at the official site for Lineage?
Is the Omni-OS you have here more feature-rich/stable than the current L-OS?
If I really like having a slim-ish AOSP OS (ie, stock android with extra features, but stable on maguro), what would be my best option?
Cheers,
ExecutorElassus said:
This maybe isn't the right forum, but what is the overall state of options right now for maguro?
Click to expand...
Click to collapse
Right, this is Development Thread for OmniRom and not a general Question&A Thread
I have encrypted storage, and 1) the TWRP version from here, while it sometimes can mount storage (necessary if I want a full install of a new ROM, and not a sideload) more often than not fails to mount storage, and reboots into the OS when trying; 2) I have the last nightly from CM-13 from last year, and it's not very stable.
Is there a version of TWRP that works better than the custom version 3.0.0 that ziyan released for maguro last year?
Click to expand...
Click to collapse
You should read last pages of https://forum.xda-developers.com/ga...recovery-twrp-2-7-1-0-touch-recovery-t1592689 and find a newer one from some days ago.
If so, is the L-OS from here more feature-rich/stable than the one at the official site for Lineage?
Click to expand...
Click to collapse
Here's no L-OS, wrong Thread
Is the Omni-OS you have here more feature-rich/stable than the current L-OS?
Click to expand...
Click to collapse
Omni has a lot of features, idk if a lot like Lineage, but definitely enough extras.
If I really like having a slim-ish AOSP OS (ie, stock android with extra features, but stable on maguro), what would be my best option?
Cheers,
Click to expand...
Click to collapse
You'll have to find out yourself which rom fits to your needs.
chinojuice said:
Yes, still persists.
Click to expand...
Click to collapse
I'll upload another build later today, if still issues please again post dmesg and logcat from right after boot.
ExecutorElassus said:
This maybe isn't the right forum, but what is the overall state of options right now for maguro?
Click to expand...
Click to collapse
Andi and ziyan are right now maintaining unlegacy, omnirom, and to a lesser extent lineage. Others are building other roms too. It would be simplest for you to dirty flash lineage 13 over cm13 (wipe cache as suggested in twrp) and hope it works. If it doesn't work, you can wipe and try unlegacy because that is the simplest AOSP rom like you asked for.
Some people think android 6 works better than 7. I think 5 works better than both. Some people think 4.4 works better than all three I honestly can't tell what you'd think after testing them all.
Definitely get the newest test build of twrp as Andi mentioned! Good luck!
bamtan2 said:
Andi and ziyan are right now maintaining unlegacy, omnirom, and to a lesser extent lineage.
Click to expand...
Click to collapse
Since Andi rightly pointed out that I am in the wrong thread, I'll reply here and then butt out
bamtan2 said:
Definitely get the newest test build of twrp as Andi mentioned! Good luck!
Click to expand...
Click to collapse
Installed the latest TWRP recovery. Holy crap, it mounts encrypted storage, and now I can dirty-flash LineageOS from the nightlies. Did so, and everything is working great!
Thanks both/all for the great advice. You people are doing Heaven's work.
<3
im having problems com.android.phone crashes every time the phone boots on this rom i am on latest radio and bootloader and am using twrp 3.1.1.0 and did a clean flash i have no sim card in my device if that matters im using super su 2.82 sr3 for root if that matters also i dont have xposed installed either im not sure what the problem is? any ideas?
ps
se linux is enforcing and i am on the 8/27/17 build and my phone is a toro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki.
Important Info
To flash this rom you need TWRP 3.2.0-0 or newer. https://twrp.me/huawei/huaweinexus6p.html
Make sure you have the radio & bootloader img's installed from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
radio & bootloader img's: https://androidfilehost.com/?w=files&flid=286833
Those img's can be flashed with fastboot command.
Note: There's an issue happening to some angler users on custom oreo roms. The first boot after flashing rom your sim card might not be detected. It's easy to fix. Just go to lockscreen security settings and change it to 'none' and then reboot. Then you can change it back to whatever you want. This only happens one time when you first flash oreo.
Download Links
rom: https://download.lineageos.org/angler
Note: LineageOS servers no longer make 15.1 builds for any devices. You can use my unofficial builds here. My older builds are here.
Note#2: if you want to switch from an official build to my unofficial builds, follow instructions here.
google apps (optional): https://wiki.lineageos.org/gapps.html (Use arm64 / 8.1)
root su addon (optional): https://download.lineageos.org/extras Note: Use arm64 15.1 zip. After installing the su addon, you can enable root in developer options.
Instructions
If updating from old unofficial to newer unofficial, follow the steps below:
1. if you don't already have them installed, flash the newest radio and bootloader img's linked above.
2. boot into twrp and flash the rom zip.
Reboot & enjoy.
NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.
NOTE2: if you want to switch from an official build to my unofficial builds, follow instructions here.
If coming from a different rom:
1. if you don't already have them installed, flash the newest radio & bootloader img's linked above. also make sure you have the newest twrp, linked above.
2. boot into twrp and wipe system & data & cache.
3. flash rom & gapps & su addon zips (gapps & su zips are optional).
Reboot & enjoy.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://download.lineageos.org/extras
Grab the one for version 16.0. It also works with 15.1.
Note: You'll need an api key from OpenWeather.
LineageOS Stats
https://stats.lineageos.org/
Credits
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
LineageOS device maintainers:
sam3000, razorloves
Source Code:
Device tree: https://github.com/LineageOS/android_device_huawei_angler/tree/lineage-15.1
Kernel tree: https://github.com/LineageOS/android_kernel_huawei_angler/tree/lineage-15.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_huawei/tree/lineage-15.1
Android version: 8.1.0 Oreo
Kernel version: Linux 3.10.73
Wooh! First!
Sent from my Nexus 6P using XDA Labs
Hey Razor. I used to be on your builds a couple of years ago in the old hammerhead and looking forward to flash your work again when 15.1 is out, this time on angler. Cheers! :fingers-crossed:
Any bugs? Is it suitable for daily driver? Just tired to wait for official build and want to flash as fast as possible. )
Thanks Razorl!!!!!
Error 7 -- make sure to flash the new twrp recovery if you face this issue!!
i42o said:
ERROR 7
Click to expand...
Click to collapse
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
razorloves said:
Try reading the big bright red letters at the top, under "IMPORTANT INFO"
Click to expand...
Click to collapse
haha. Yeah my bad bro, my bad. got it tho, thanks!
Says no SIM card
Clean flash following instructions, TWRP 3.2, latest bootloader/radio/vendor, flashed vendor -> rom -> gapps. Otherwise no errors.
Any suggestions?
telefantastik said:
Says no SIM card
Click to expand...
Click to collapse
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
It's weird though. I have unlock protection and got no issue when flashing this.
Can it also be related to your carrier or something?
ChemoNL said:
I have unlock protection and got no issue
Click to expand...
Click to collapse
Its not just caused by unlock protection. I posted details on the issue in my 14.1 thread about a month ago.
razorloves said:
Forgot to mention in the first post. This has been happening on many custom ROMs.
An easy fix is to go to security settings and change screen lock to swipe or none, then reboot. That will remove the device protection that caused the no sim problem.
After the reboot, the problem is fixed and won't happen anymore. Then you can go back into security settings and change it back to whatever screen lock option you want.
Click to expand...
Click to collapse
Awesome, it worked! Thanks
For those interested...
Another new version of twrp came out yesterday. 3.2.1-0
Here's the changelog for it https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
You can download it here: https://twrp.me/huawei/huaweinexus6p.html
Here's the changelog for 3.2.0-0 that came out last week, incase you missed it.
https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html
Thank you for new thread and ROM.
:fingers-crossed::fingers-crossed::fingers-crossed:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
domacikolaci said:
Hi, looking to potentially begin using custom ROMs on my 6P to help combat some battery and performance issues I get. With future updates, do I have to keep manually flashing the radio, etc firmware or can I just OTA/DL zip of lineage and flash? Seems like a bit of a pain :/
Click to expand...
Click to collapse
Hi, once a month you need to flash the new vendor for security updates
Google release them once a month (usually the first tuesday of the month)
However when you flash an update that does not require new vendor, you don't need to flash it
edit: just realised you're also from Melbourne, hi
Just have installed the last unofficial in my Angler, coming from another custom rom ( with Nougat). All good. Plan to stay here. Thanks !
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Apoena said:
Anyone having problems with the phone shutting down saying 0% battery when in reality you still have plenty of battery left? Just did a clean install and it happened after only installing chrome and whatsapp.
Click to expand...
Click to collapse
Have you been living under a rock for the past year? Lol jk. But see here http://www.androidpolice.com/2016/1...toff-problem-and-its-becoming-a-safety-issue/
tldr; blame Google and Huawei. And get yourself a free replacement or free upgrade.
http://www.androidpolice.com/2017/0...exus-6p-owners-pixel-xl-warranty-replacement/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing
Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.
Is link not posted yet?
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...
Any chance for an MD5
jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f
TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.
Thanks very much for sharing this. I've got it installed and it's running fantastic.
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.
redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview
Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Click for feature list
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM: AndroidFileHost Official | MEGA mirror
GAPPS: GZR Gapps Zero (pico) | Ezio Gapps Mini (nano) | Open Gapps
First time installing crDroid to your Honor 5x, or coming from another ROM:
** Make sure you're running a proper working Recovery (latest TWRP, 3.2.3 or above)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
SELinux is PERMISSIVE
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- @BadDaemon
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community
XDA:DevDB Information
crDroidAndroid, ROM for the Honor 5X
Contributors
coldhans, tenshi_xp
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Official MM (non-VoLTE) firmware
Based On: LineageOS
Version Information
Status: Nightly
Current Stable Version: 4.7
Stable Release Date: 2018-10-10
Created 2018-09-23
Last Updated 2019-01-07
Reserved
Reserved
Lol lineageOs posted sources and here we go great to see another
Rom does not boot in my phone is any possibility of doing a new Zip file (like the old BatPach Zip) thanks in advance
carpes said:
Rom does not boot in my phone is any possibility of doing a new Zip file (like the old BatPach Zip) thanks in advance
Click to expand...
Click to collapse
Unfortunately no, at least not from me. It sounds like you have the wrong firmware. This isn't an issue with the ROM.
Please don't quote the OP in any replies. If you can edit your post to remove the quote, I'd appreciate it.
coldhans said:
Unfortunately no, at least not from me. It sounds like you have the wrong firmware. This isn't an issue with the ROM.
Please don't quote the OP in any replies. If you can edit your post to remove the quote, I'd appreciate it.
Click to expand...
Click to collapse
Actually rom boot but doesn´t recognize my Sim card and I think the touch doen´t responde for seconds
Totally awesome, the ROM works as a charm. I will test this thoroughly.
Thank you (and everyone that works/worked on this project) very much.
rom works fine but magisk failed to flash via twrp and so cant be rooted.
omid_shirzad said:
rom works fine but magisk failed to flash via twrp and so cant be rooted.
Click to expand...
Click to collapse
For me Magisk (17.2 Beta) flashed without a problem via TWRP.
Till now, everything is working without any problems for me.
Thanks coldhans :highfive:
everything working fine.. but when i flashed gapps ... it goes on saying again nd again that google play services stoped working...
Thanks @coldhans.
A new hope for kiwi with your team and baddaemon's one
sheryar rao said:
everything working fine.. but when i flashed gapps ... it goes on saying again nd again that google play services stoped working...
Click to expand...
Click to collapse
Did you reboot after flashing the ROM and before flashing gapps? You have to flash both before your first boot.
Question. Does this ROM make our kiwi treble compatible? Or because of hardware restraints, no.
coldhans said:
Did you reboot after flashing the ROM and before flashing gapps? You have to flash both before your first boot.
Click to expand...
Click to collapse
no .i flashed it after first boot... does flashing befor first boot makes any sense?
sheryar rao said:
no .i flashed it after first boot... does flashing befor first boot makes any sense?
Click to expand...
Click to collapse
You have to flash gapps before first boot or you'll always get those crashes.
reggjoo said:
Question. Does this ROM make our kiwi treble compatible? Or because of hardware restraints, no.
Click to expand...
Click to collapse
Old Huawei phones like ours are actually capable of supporting treble, but we havent started using it yet.
coldhans said:
Old Huawei phones like ours are actually capable of supporting treble, but we havent started using it yet.
Click to expand...
Click to collapse
Thanks, but with devs like you, we won't need it anyway. I can live without that, as long as you guys make great ROMs.
The ROM works fine but it doenst find my wifi (but it shows other ones that are near). I tried many mods but none find my wifi. Mobile data and everything else works fine.
YoungMiner said:
The ROM works fine but it doenst find my wifi (but it shows other ones that are near). I tried many mods but none find my wifi. Mobile data and everything else works fine.
Click to expand...
Click to collapse
Go to your router setting and check which wifi channel it is using. If it's 12 or 13 change it under 10 and see if it fix the problem.