Temasek's UNOFFICIAL CM13.0 BUILDS
{
"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"
}
I will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
...not ready yet
A WORKING version TWRP is required i use Official TWRP 2.8.7.2
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Ensure you’re on the latest vendor image from google - https://developers.google.com/android/nexus/images
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
probably something i havn't found as yet
@temasek
@apascual89 - Developer of nexus 9 temasek dark
@Chainfire
CM Team, CyanogenMod
@DrawnToLife
@zawata
@joshuabg
@craigacgomez
Source
Orignally forked from CyanogenMod
Kernel Source
Device Tree
Temasek Source
Rom Source
Changelogs
https://github.com/temasek/Changelogs/blob/cm-13.0/cm_hlte-Changelog.txt
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65562191&postcount=652
Basketbuild Download - Backup Download Location (OR for those not in Google Shares)
https://basketbuild.com/devs/Joshndroid/Temasek Roms/flounder
GApps - Lollipop 5.1 64 Bit GApps Package
http://opengapps.org/
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to Chainfire
http://download.chainfire.eu/supersu
and one more.
okay rom is now uploaded onto basketbuild. Please follow link in post 2.
i recommend clean flash from another rom as usual. If dirty flashing in the future there is no necessity to flash gapps again, however sometime i do notice supersu goes a bit funny so i would recommend reflashing supersu just to be safe. failing that you can just install it again from market and cause it to update via openrecovery script.
awesome !!! love this rom on my N6 . and now also on my N9 thanks !!!
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
nericollin said:
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
Click to expand...
Click to collapse
Let me know otherwise I will full wipe again and try again myself
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
I know the change log is on the device once you flash the ROM. But I would like to know the changes that have been made besides what is in CM12 already.
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Does LTE work on this ROM?
Alright. Thanks man. I'll just flash it and play around
Edit:: Flashed it. Everything running great. One thing I have been looking for in several ROMs is the ability to put the nav bar on one side while in landscape. I kinda sucks having the bar at the bottom of my screen when it would be much more convenient right by one of my hands whole holding in it landscape. Is that possible here or in any rom yet.
joshndroid said:
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Click to expand...
Click to collapse
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
joshndroid said:
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
Click to expand...
Click to collapse
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
Click to expand...
Click to collapse
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
zawata said:
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
Click to expand...
Click to collapse
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
Click to expand...
Click to collapse
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I was! I figured it must have been that because I remember changing it from F2FS to ext4 when development for the N9 was still in early stages.
The ROM runs amazingly now though! Awesome job! Will report feedback if any issues arise!
andreglud said:
Does LTE work on this ROM?
Click to expand...
Click to collapse
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
joshndroid said:
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
Click to expand...
Click to collapse
So in short, I shouldn't expect it yet?
Not necessarily. I don't have a LTE device to try it on, so I can't just flash it and let u know.
disregaurd, didnt realize there were more replys
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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2.x (JB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Githubs:
Andromadus
CyanogenMod
Rukin5197
Mustaavalkosta
Changelogs:
BBQLog
CM Gerrit
CM Google+
Github (see above)
Donations:
codefi.re (use the donation button at the bottom of the page)
Mustaavalkosta
Rukin5197- (Use "Donate To Me" underneath my avatar")
Flashing Instructions
Fresh installation instructions:
Download Nightlies
Download gapps (goo.im/gapps)
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-primoc.zip
Flash gapps-jb-xxxxxxxx-signed.zip
Reboot into bootloader
fastboot flash boot boot.img (Grab the one from the ROM zip)
Reboot and enjoy.
Update installation instructions:
Download Nightlies
Put the file on SD card.
Reboot to recovery.
Format /cache
Flash cm-10.1-xxxxxxxx-UNOFFICIAL-primoc.zip
No need to flash gapps as CM backuptool script should take care of them.
Reboot and enjoy.
Status
Not working (In order of importance):
- 5mp Camera/720p Video Recording (On Native camera app)
- Lockscreen glitches and random reboots upon unlock
GooManager Support
My ROMs now have GooManager OTA support, so when I release a new update, it will tell you via notification. All you need to do is go into Play Store and download the GooManager app and everything will take over from there.
Q&A:
Q: I have not read the OP, but I have this issue
A: If it is already listed in the OP as an issue, please don't add to the thread. Read first por favor
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: How about them Ravens right guys?!.
A: Leave.
rukin5197 said:
Guys don't download the latest build just yet. I'm still figuring out the kinks
Click to expand...
Click to collapse
Credits:
simonsimons34 for the kernel
beyond for getting it booted/fixing a lot of things
Lloir for helping as well
jmz for the device tree start
CyanogenMod team
sellers86 for helping me pass a very tedious error
|0xD34D| for basically mentoring me
Rohan32 for giving me all his findings
Andromadus/CodeFireX guys for giving me bases and advice
Mustaavalkosta for the local_manifest.xml
Changelog:
Code:
[B]2-10-2013-[/B] Back to the CM10.1 base, Fix native camera app, now better performance/stability
[B]2-8-2013-[/B] New Andromadus base. Fix Camera/Camcorder/PlayStore
[B]2-5-2013-[/B] New PMEM kernel,
[B]2-4-2013-[/B] First ION build, updated OP
[B]1-27-2013-[/B] WiFi Fixed
[B]1-25-2013-[/B] Initial Release
Can somebody please confirm that WiFi is broken? I need to be 100% positive
Thank you Rukin, your a beast... Backing up my SD right now. will flash in a sec. and let you know about WIFI.
Edit:
No just sits at turning WIFI on. very smooth though, i like the statusbar and transitions.
rukin5197 said:
Can somebody please confirm that WiFi is broken? I need to be 100% positive
Click to expand...
Click to collapse
confirmed.....WIFI borked....I'm gonna flash evervolve kernel just to see what happens....
WiFi is confirmed working in the latest nightly.
Running newest nightly, no wifi. Also, SD card will not mount. I am using the 1-27 build with its internal boot.img. I did a total clean reflash.
jcru53 said:
Running newest nightly, no wifi. Also, SD card will not mount. I am using the 1-27 build with its internal boot.img. I did a total clean reflash.
Click to expand...
Click to collapse
Flash the boot.img I provide in the thread please
Flashed provided boot.img and SD problem went away, but still no wifi. Attached logcat.
jcru53 said:
Running newest nightly, no wifi. Also, SD card will not mount. I am using the 1-27 build with its internal boot.img. I did a total clean reflash.
Click to expand...
Click to collapse
same here
x3reme85 said:
same here
Click to expand...
Click to collapse
LOL I'm so sorry guys, I've been holding out on your guys
I forgot to put in beyond's wifi modules. If any of you guys have beyond's builds, just take his /system/lib/modules and put them in yours. I'm going to put them into the build for the next release.
Sincere Apologies
This is a beautiful piece of work, Rukin.
I have encountered a slight annoyance and I am curious if anyone has experience with this but last night, when I went to search for the update, it was unable to find it. I originally did this through the "About Phone" section of the settings and then tried it through ROM Manager and it didn't even execute a search at all. I've searched the forums to see if this is a common problem since this is my first experience with nightly builds but did not have any luck, likely because of the quite-common key words of my search.
Anyone have some ideas or is this a corner that needs polished still in this build and it isn't special to just me?
blameitonchemo said:
This is a beautiful piece of work, Rukin.
I have encountered a slight annoyance and I am curious if anyone has experience with this but last night, when I went to search for the update, it was unable to find it. I originally did this through the "About Phone" section of the settings and then tried it through ROM Manager and it didn't even execute a search at all. I've searched the forums to see if this is a common problem since this is my first experience with nightly builds but did not have any luck, likely because of the quite-common key words of my search.
Anyone have some ideas or is this a corner that needs polished still in this build and it isn't special to just me?
Click to expand...
Click to collapse
You're going to need to download the GooManager app off the Play Store. I have not made this ROM compatible with the GooManager app though, but thanks for reminding me as I will implement it into the next update
Also for all the people wondering: I have just about fixed AOKP up to date with this ROM, so I will be releasing that today
Okay guys, try the Jan 27 build again and tell me if WiFi works
rukin5197 said:
Okay guys, try the Jan 27 build again and tell me if WiFi works
Click to expand...
Click to collapse
It does not but I am again new at this so I could be wrong. Would I need to flash the boot.img once again as well?
blameitonchemo said:
It does not but I am again new at this so I could be wrong. Would I need to flash the boot.img once again as well?
Click to expand...
Click to collapse
Yes but I would also try a full wipe if it doesn't work. It worked for me
rukin5197 said:
Yes but I would also try a full wipe if it doesn't work. It worked for me
Click to expand...
Click to collapse
Unfortunately I ended up trying a full system wipe and reinstall and it still didn't work. Thank you for your persistence in figuring this out.
I should also mention since it seems relevant at this point that is says my radio is .0521_2 so there is no problem there.
---------- Post added at 05:52 PM ---------- Previous post was at 05:36 PM ----------
blameitonchemo said:
Unfortunately I ended up trying a full system wipe and reinstall and it still didn't work. Thank you for your persistence in figuring this out.
I should also mention since it seems relevant at this point that is says my radio is .0521_2 so there is no problem there.
Click to expand...
Click to collapse
Some other things I have noticed from poking around. It does not allow me to slide the Wi-Fi button to on most of the time. It's not even active EXCEPT for when I go into Advanced and go to specify a region code. Europe is the default so I set it to United States and 60-90 seconds later, I am able to move the Wi-Fi slider to on. It never actually turns blue to indicate it is on, nor does it turn on, but I am able to slide it over. When I go back to advanced and region code, it has reverted back to Europe.
I doubt this helps at all but I know it's good to have as much information as possible.
Okay, try the next download. I'm getting tired of this
rukin5197 said:
Okay, try the next download. I'm getting tired of this
Click to expand...
Click to collapse
Please don't consider this a "needless" post. Rukin you are a well respected DEV and all around good guy here and please don't abandon your efforts due to some off the wall remarks. At that thanks for ALL your contributions thus far sorry if I clogged the thread
blameitonchemo said:
Heh, I don't think anyone blames you for getting tired of it.
---------- Post added at 06:59 PM ---------- Previous post was at 06:53 PM ----------
Is the file up now or is it going up with 1/28?
Click to expand...
Click to collapse
It's 1/27. Although I think a 1/28 build should be up soon because I'm compiling a new build right now
{
"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 5.1.1 coming to a xoom near you!
This ROM is for wingray.
Based on:
OmniROM "omnirom-5.1.1"
Kernel ElementalX-Xoom-2.1 by flar2
Download
omni-5.1.1-latest-wingray.zip (md5sum)
Download GAPPS
p75xx-gapps-L-5-6-15.zip
Download SuperSU
UPDATE-SuperSU-v2.XX.zip
Download Deprecated Versions
Browse deprecated
Install
You will need bigPart TWRP and execute the repartitioning as described in
Source
Prerequisites
TWRP 2.8.6.0 BigPart Edition Recovery
The ROM you want to flash
Instructions
Your data will be totally wiped! If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.
Put TWRP 2.8.6.0 BigPart version and your desired rom on your microsd card.
Reboot into recovery. Flash TWRP BigPart.
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
Internal Storage
and wipe them. Don't reboot just yet.
Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". You can now follow the steps below, starting with Flash omni-5.1.1-XXX-wingray.zip.
If updating from older ROM version in this thread, you don't have to wipe anything
If updating from an different ROM, wipe
Dalvik Cache
System
Cache
Data
Flash omni-5.1.1-XXX-wingray.zip
Flash p75xx-gapps-L-5-6-15.zip
Flash UPDATE-SuperSU-v2.XX.zip
Reboot
Wait a long time...
Copy SuperSu and Gapps zip to /sdcard/OpenDelta/FlashAfterUpdate so that they are automatically applied after OTA update. (Internal storage/OpenDelta/FlashAfterUpdate)
Issues
Camera not working
HW Videodecoding not working
HDMI output not working
BT audio not working
Microphone not working
...
Tips'N'Tricks
Show Developer and Performance settings
Go to the settings menu, and scroll down to "About phone." Tap it.
Scroll down to the bottom again, where you see "Build number."
Tap it seven (7) times, and *poof*, you've got the developer settings back.
Reduces lagging
Overclock to 1.4Ghz (Performance menu)
Decrease Window/Transition animation scale and Animator duration scale to Animation off (Developer options menu)
Source
https://github.com/Schischu
Thanks
dreamcwli
DJNoXD
bubor
michie
flar2
Adler12
realjumy
rchtk
bigrushdog
Special thanks to everybody who donated, You guys rock!
Code:
/*
* Your warranty is now void.
*
* I will not accept responsibility for any adverse effects to your device,
* including, but not limited to: bricking, dead SD card, bootloops etc.
*
* You mod your device at your own risk.
*/
Please Donate
If you like my ROMs please donate by pressing the "Donate to Me" button below my name on the left side. It takes a lot of my spare time developing these ROMs for the community and every penny is greatly appreciated .
XDA:DevDB Information
[ROM][5.1.1] OmniROM - Wingray - bigPart, ROM for the Motorola Xoom
Contributors
Schischu
Source Code: https://github.com/Schischu
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 2.6.x
ROM Firmware Required: TWRP 2.8.6.0 for BigPart
Based On: OmniROM
Version Information
Status: Alpha
Created 2015-06-30
Last Updated 2015-10-25
Reserved
Changelog
20150726.203925
Fix standby.
20150704.112502
Fix minimum brightness.
Fix setting cpu clock.
20150630.183925
Initial Release
How to build
repo init -u https://github.com/Schischu/android.git -b android-5.1
repo sync
./build.sh wingray clean
And uploaded.
This ROM is an alpha release, so definitely backup your old ROM before flashing.
I had to rewrite the audio library from scratch as our old one just wasn't compatible anymore with 5.1. Lots of work....
It's still not finishes so there are probably some audio issues.
For the moment the biggest bug is that video playback is not working, but I have a pretty good idea what the issue is.
Also Google Photos crashes with "java.lang.IllegalArgumentException: No config chosen". I am pretty sure that we also had this error on omni-4.4 and fixed that. Need to check old commits.
In total it feels pretty smooth with one exception. Somehow opening the App Drawer takes a lot of time. Need to check if the annoying animation can be deactivated.
As 5.1 uses ART instead of Dalvik the boottime after an update is pretty bad. Up to 10min depending on how many apps are installed.
Schischu said:
And uploaded.
This ROM is an alpha release, so definitely backup your old ROM before flashing.
I had to rewrite the audio library from scratch as our old one just wasn't compatible anymore with 5.1. Lots of work....
It's still not finishes so there are probably some audio issues.
For the moment the biggest bug is that video playback is not working, but I have a pretty good idea what the issue is.
Also Google Photos crashes with "java.lang.IllegalArgumentException: No config chosen". I am pretty sure that we also had this error on omni-4.4 and fixed that. Need to check old commits.
In total it feels pretty smooth with one exception. Somehow opening the App Drawer takes a lot of time. Need to check if the annoying animation can be deactivated.
As 5.1 uses ART instead of Dalvik the boottime after an update is pretty bad. Up to 10min depending on how many apps are installed.
Click to expand...
Click to collapse
Awesome! Looking forward to flash. You are unbelievable![emoji12]
fantastic
got an error when trying to flash the gapps though
ApplyParsedPems: lsetfilecon of /system/addon.d/50-hosts.sh to ubject_r:system_file:s0 failed :
Operation not supported o
set_metadata_recursoce: some changes failed
E:Error executing updater binary in zip...
Error flashing zip
p.s. the error seem to be harmless
everything seems to be working including playstore
after changing the animation / transition and co like mentioned in the op i got a pink graphic
flicker -> rebooting fixed that
Wow, this is so impressive. Cannot believe the Xoom is on 5.1.1. Amazing work!
matt4321 said:
Wow, this is so impressive. Cannot believe the Xoom is on 5.1.1. Amazing work!
Click to expand...
Click to collapse
That's the awesome develpment this tablet have... Still don't know how this don't went to front page yet, is amazing what a 2011 hardware can achieve these days
Schischu said:
And uploaded.
This ROM is an alpha release, so definitely backup your old ROM before flashing.
I had to rewrite the audio library from scratch as our old one just wasn't compatible anymore with 5.1. Lots of work....
It's still not finishes so there are probably some audio issues.
For the moment the biggest bug is that video playback is not working, but I have a pretty good idea what the issue is.
Also Google Photos crashes with "java.lang.IllegalArgumentException: No config chosen". I am pretty sure that we also had this error on omni-4.4 and fixed that. Need to check old commits.
In total it feels pretty smooth with one exception. Somehow opening the App Drawer takes a lot of time. Need to check if the annoying animation can be deactivated.
As 5.1 uses ART instead of Dalvik the boottime after an update is pretty bad. Up to 10min depending on how many apps are installed.
Click to expand...
Click to collapse
@Schischu, you are awesome, man.
andPS2 said:
fantastic
got an error when trying to flash the gapps though
ApplyParsedPems: lsetfilecon of /system/addon.d/50-hosts.sh to ubject_r:system_file:s0 failed :
Operation not supported o
set_metadata_recursoce: some changes failed
E:Error executing updater binary in zip...
Error flashing zip
p.s. the error seem to be harmless
everything seems to be working including playstore
after changing the animation / transition and co like mentioned in the op i got a pink graphic
flicker -> rebooting fixed that
Click to expand...
Click to collapse
I just flashed the new build and got the same fail message, but the tablet booted fine and most items are working as expected.
working ok
dolphin browser only works when jetpack is turned off
doesnt go into deep sleep mode yet at least for me
does it work for you guys?
switched launcher to nova - seems to be a little bit faster
overall thanks a lot @Schischu!
Unbelievable! ! Nice job and fixes will b fix very soon I hope so.
I will update very soon till fixes not comes out. @Schischu thanks man for your hard work!
Sent from my SM-G925I using Tapatalk
Amazing work!
andPS2 said:
working ok
dolphin browser only works when jetpack is turned off
doesnt go into deep sleep mode yet at least for me
does it work for you guys?
switched launcher to nova - seems to be a little bit faster
overall thanks a lot @Schischu!
Click to expand...
Click to collapse
Oh you are right. The battery drain is huge, need to investigate.
This is awesome.
Now, I just hope that camera and video works.
The tablet is used by my parents for video calling (Skype etc.) and watching YouTube videos.
If I want to upgrade from omniROM 4.4.2 (February 2014) to 5.1.1, do I not wipe anything at all?
4.4.2 is laggy (as reported by my parents) on that tablet.
Very happy, u r d MAN !
This ROM is great.... Running so smooth
Uploaded small update:
- Fix minimum brightness.
- Fix setting cpu clock.
Great work
So glad there's still xoom love. As it's an alpha issues are expected. Just reporting that I can't seem to install any gapps package. Wiped everything first and formated data to start with a clean device before copying zip files and flashing. Keeps saying "Error executing updater binary in zip '/emmc/Download/p75xx-gapps-L-5-6-15.zip" Thanks again for the great work and I look forward to future updates.
---------- Post added at 06:05 AM ---------- Previous post was at 05:55 AM ----------
Spoke too soon. Not sure how but I managed to get it to work.
Nuny0biznes said:
So glad there's still xoom love. As it's an alpha issues are expected. Just reporting that I can't seem to install any gapps package. Wiped everything first and formated data to start with a clean device before copying zip files and flashing. Keeps saying "Error executing updater binary in zip '/emmc/Download/p75xx-gapps-L-5-6-15.zip" Thanks again for the great work and I look forward to future updates.
---------- Post added at 06:05 AM ---------- Previous post was at 05:55 AM ----------
Spoke too soon. Not sure how but I managed to get it to work.
Click to expand...
Click to collapse
Others have posted with the same gapps report. When this happened to me, I did another clean install and flashed the stock package from http://forum.xda-developers.com/android/software/tk-gapps-t3116347. It flashed perfectly and seems to be working fine.
I have a WiFi only Xoom, but I've never heard of WinGray. Is that all WiFi Xooms? I actually won this Xoom in a Twitter contest. It would be awesome if I could keep it going.
Code:
/*
* Your warranty is now void.
*
* Neither me nor Resurrection Remix nor anyone else mentioned in this post is
* responsible for bricked devices, dead SD cards, thermonuclear war, or you
* getting fired because the alarm app failed. Please do some research if you
* have any concerns about features included in this ROM before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at
* us for messing up your device, we will laugh at you.
*
*/
This is my first ROM built with help from jdelano who used to build this ROM for these devices.
Even if this is quite new to me, issue reports are welcome and I'm trying to help as good as I can.
About Resurrection Remix
Resurrection Remix has been based on CM, slim, omni and original Remix ROM builds creating an awesome combination of performance, customization, power and the newest features while being completely open source.
Features
Statusbar customization (Centered clock, custom battery icon, battery bar,...)
Navigationbar (activate navigation bar, rearrange buttons, custom actions,...)
Hardware buttons customization
Lockscreen customization (shortcut custumization, hide emergency button,...)
Gestures
Quicksettings customization
Interface customization (custom dpi, ambient display,...)
Themes (OMS support)
and many more
Changelog
Known issues
MHL out to TV doesn't work
Mentioning issues
Before mentioning issues, please make sure you followed the instructions mentioned below and you're not using custom kernels or mods modifying system files.
Installation instructions
First install/Clean Flash
Download latest ROM zip file
Download GApps
(Download latest TWRP and install it) - T900 users need to use a special TWRP linked in Downloads section
Reboot into recovery
Make Nandroid backup (recommended)
Wipe Data, System and (Dalvik) Cache
Flash ROM and GApps
Reboot
Enjoy Resurrection Remix!
Update/Dirty Flash
Download latest ROM zip file
Reboot into recovery
Make Nandroid backup (not needed in most cases, but better to be save if something went wrong)
Flash ROM
Reboot
Enjoy the update!
Downloads
ROM
P900 (v1awifi)
T900 (v2awifi)
TWRP
P900
T900: Your TWRP is linked in this thread under Installation - step 3
Open GApps
Download latest GApps from Open GApps official website using
Platform: arm
Android: 7.1
Variant: the one you prefer (I use stock without issues but on another device I had issues with GBoard settings force closing)
Credits
RR Team
CyanogenMod/LineageOS Team
OMNI Team
SLIMROMS Team
Substratum Team
Open GApps Team
Exynos5420 Team
and of course all the contributers, supporters and donators
Sources
P900 device sources
T900 device sources
RR sources
Screenshots
{
"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"
}
I just updated my phone to 5.8.2 last night. It'll be interesting to run the same ROM on both of my devices. Thanks for your contribution...I look forward to trying it out this evening.
So happy that you took this on @Schrolli97 I love RR and our device deserves the best in software, it's really that good. Best of luck
New builds are up and linked in OP.
Next update should show up in OTA updates
Has anyone run into issues with their external sd card -- "corrupted sd card" -- after updating to the last couple versions of RR? This happened as well in the Lineage 14 version (and is discussed there at length). I'd hoped it was avoided in RR, but alas, no. At least, not for me. The card is *not* corrupted; rather the OS isn't reading it correctly. I had to back off with RR to an earlier version capable of still reading exfat (the default microsd card format).
shonkin said:
Has anyone run into issues with their external sd card -- "corrupted sd card" -- after updating to the last couple versions of RR? This happened as well in the Lineage 14 version (and is discussed there at length). I'd hoped it was avoided in RR, but alas, no. At least, not for me. The card is *not* corrupted; rather the OS isn't reading it correctly. I had to back off with RR to an earlier version capable of still reading exfat (the default microsd card format).
Click to expand...
Click to collapse
I had this some time ago. I moved all data to my PC. Formatted the card in my tablet and moved it all back. Now it works fine
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" message. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Anybody wants great sound on your tablet? Tested by me. Works great. I installed the whole choobang. Damn! I have bass on my speakers now!
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Schrolli97 said:
New builds are up and linked in OP.
Next update should show up in OTA updates
Click to expand...
Click to collapse
@Schrolli97 thanks for carrying on with this great RR Rom! I clean installed the 2017/02/24 version, and it has been working great. Donation sent!
There is a fix to the lock screen non-rotation issue (which you may know about). Posting here for others, FYI...
Add the following code to the root/system/build.prop file, then save it and reboot.
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
You can use the included Deathly Adiutor app to edit the build.prop file (under Tools / Build prop Editor).
Gary_O said:
@Schrolli97 thanks for carrying on with this great RR Rom! I clean installed the 2017/02/24 version, and it has been working great. Donation sent!
There is a fix to the lock screen non-rotation issue (which you may know about). Posting here for others, FYI...
Add the following code to the root/system/build.prop file, then save it and reboot.
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
You can use the included Deathly Adiutor app to edit the build.prop file (under Tools / Build prop Editor).
Click to expand...
Click to collapse
Very happy that you guys enjoy this. Hope that I can contribute to making this device even more awesome
Thanks for mentioning this fix. Just added it to the OP :highfive:
Let's see if I can get it to work that you don't need to edit build.prop anymore.
shonkin said:
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" uu. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Click to expand...
Click to collapse
For me it's working fine so I can't say much about it. I guess the only fix at this time is disabling sdcardfs via build.prop...
For anyone else having this problem:
Changing "ro.sys.sdcardfs=true" to "ro.sys.sdcardfs=false" in build.prop and rebooting should fix this.
shonkin said:
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" message. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Click to expand...
Click to collapse
Same issue to me, it report SD card (exfat) corrupted after upgrading to 2/28 version.
Schrolli97 said:
For me it's working fine so I can't say much about it. I guess the only fix at this time is disabling sdcardfs via build.prop...
For anyone else having this problem:
Changing "ro.sys.sdcardfs=true" to "ro.sys.sdcardfs=false" in build.prop and rebooting should fix this.
Click to expand...
Click to collapse
Super-appreciate this rom.... but no, this is not a fix. Identical message "corrupted sdcard" before and after changing the above in Deathly Adiutor. I had to revert to an earlier version of the rom before the sdcardfs setting came into play. Is there any way to remove that code from my end? As in, remove it altogether, or somehow having it revert to what worked just fine before it came along?
An interesting corollary is my Samsung Note 4 phone, which I also run Resurrection Rom on (the 3/7/17 version). No issues with the micro sd card in it... and interestingly, that RR build has no Deathly Adiutor in it. I'm in over my head at this point, but pass on that info for what it is worth.
shonkin said:
Super-appreciate this rom.... but no, this is not a fix. Identical message "corrupted sdcard" before and after changing the above in Deathly Adiutor. I had to revert to an earlier version of the rom before the sdcardfs setting came into play. Is there any way to remove that code from my end? As in, remove it altogether, or somehow having it revert to what worked just fine before it came along?
An interesting corollary is my Samsung Note 4 phone, which I also run Resurrection Rom on (the 3/7/17 version). No issues with the micro sd card in it... and interestingly, that RR build has no Deathly Adiutor in it. I'm in over my head at this point, but pass on that info for what it is worth.
Click to expand...
Click to collapse
If changing build.prop values doesn't work, I don't think there's a way to revert this from your end. I don't even know if (i.e. how easy) I can revert it. So I guess I will read about it. It may take a while, though, as I'm quite busy for the next week.
Deathly Adiutor is an altered version of kernel Adiutor that only works with devices using the processor of our tablet. I don't think the note 4 is one of those devices. Also it probably has another maintainer who's maybe just not including it in the ROM.
I guess sdcardfs is also just included by lineage maintainers whose device drivers I'm using. Though, I didn't have enough time to check, yet.
I'll keep my eyes open. Will tell you when I know more.
New builds are up and should show up in Settings > Configurations > Miscellaneous > Updates.
Non-rotating lockscreen is fixed.
For the next update I'll target the SD card if the problem is still present.
Schrolli97 said:
New builds are up and should show up in Settings > Configurations > Miscellaneous > Updates.
Non-rotating lockscreen is fixed.
Click to expand...
Click to collapse
Thanks, and thanks for incorporating the non-rotating lockscreen. :good:
I have noticed a problem with Substratum with this 20170317 version of the RR ROM. Substratum is running in Legacy mode, and not OMS mode. On the previous version 20170228 RR ROM, Substratum was running fine in OMS mode. I did a full wipe / clean install of the 0317 ROM. I have installed the same version of Substratum (604) on both 0228 and 0317 ROMs.
Per some other forum suggestons, I tried force closing Substratum, then clearing the data and cache for substratum and reopening it. Still in Legacy mode. Anyone else experiencing this?
Quick question, is anyone else having Bluetooth issues? I'm not able to connect to any Bluetooth devices
JodyBreeze901 said:
Quick question, is anyone else having Bluetooth issues? I'm not able to connect to any Bluetooth devices
Click to expand...
Click to collapse
I have not experienced any Bluetooth issues. Although so far only connected to my Mpow bluetooth headphones, worked first time.
Alrighty then.......looks like it's time for a clean install
Sent from my SM-N920C using Tapatalk
I dirty - flashed the 0317 update, and I wasn't going to say anything... But since someone else clean-flashed and has the same problem with substratum, I decided to post.
It is running in legacy mode, and isn't applying anything. I've cleared data on substratum, disabled/rebuilt the themes, and uninstalled all/reinstalled all. Of course, the tab has been rebooted in between many times.
{
"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
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CherishOS is an AOSP based rom focusing on a Unique UI with many customizations.
Known bugs
- Loudspeaker is loud and creates some echo in calls
- Wifi is known to have lower signal than stock through all custom roms for NB1
- you tell me
Please ensure T-virus-2.0 is installed before attempting to flash this rom! follow this guide here: https://forum.xda-developers.com/t/nokia-8-nb1-full-rom-installation-guide.4349525/
Selinux status: Enforcing
Download
ROM
https://github.com/megafire91/NB1-CherishOS_Releases/releases/
Recovery
TWRP:
https://github.com/log1cs/android_device_nokia_msm8998-twrp/releases/tag/3.7.0_12.0
Flashing instructions
Clean Flash:
1. Take a full backup of both your data and internal storage as it may be wiped.
2. Download the ROM from above link and flash the recovery zip (optional)
3. Download the recovery zip of your choosing and flash it if not already on latest twrp.
4. flash the rom zip and recovery zip again right after the rom zip before rebooting , it will reboot you to recovery automatically in other slot. (optional) cherish recovery included.
5. Flash any mods you may want
6. run factory reset from recovery, or wipe /data and /dalvik if you don't want internal wiped.
7. reboot to system and enjoy!
Installing an OTA (Dirty flash):
1. Download the ROM from above link
2. flash the rom zip and twrp zip (optional) and let it reboot into recovery.
3. wipe Dalvik cache only
4. flash any mods you had previously flashed.
5. reboot to system and enjoy!
Device support:
https://t.me/HMD_Nokia_8
Credits
Me for building the rom
@emufan4568 for the NB1 device and vendor tree, atomix kernel and TWRP.
@Log1cs for his device trees and latest TWRP
@NobodyDbg for always assisting me with build issues & fixes
@CherishOS team for the amazing ROM
@THMSP for T-virus
all users in our telegram groups that helped us contribute and find bugs as well as sent us logs.
if i missed anyone in credits please let me know and ill add you to this list.
coffee:
Pay Marcel Dos Santos using PayPal.Me
Go to paypal.me/marceldossantos91 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
paypal.me
if you do decide to donate, thank you, appreciate it more than you know.
Sources:
CherishOS: https://github.com/CherishOS
Device trees: https://github.com/megafire91
https://github.com/GPUCode
https://github.com/log1cs
Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,
Kasi1906 said:
Hello forum, hello developers,
I am very happy that the Nokia 8 still finds support here.
For the work done and providing this great ROM my heartfelt thanks! Everything works wonderful. In my opinion even better than the Anfroid 12 version.
Perfect. I am very happy with it.
Because of this great work, hopefully my Nokia will work well for a while,
Click to expand...
Click to collapse
hey, thank you i am glad you are happy with it, always nice to see things like this, appreciated.
4.2 build is up, happy flashing, changelog in git page
marceldossantos91 said:
4.2 build is up, happy flashing, changelog in git page
Click to expand...
Click to collapse
Thank you for the timely security update! My gratitude is still very high. The ROM works perfectly. So far I have not had any problems.
I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear
satanvade said:
I have an unlocked bootloader
I don't have twrp
I wish it will be updated
where to begin?
sew up twrp? which version?
infect with a virus through nost?
instructions are not clear
Click to expand...
Click to collapse
Hi, you can follow the guide in the Q & A section linked above or in our telegram support group, but the basic idea is:
Unlock bootloader + critical
Flash Tvirus 2.0, which includes twrp 3.6 already (there is however a 3.7 update available, which supports decryption in A12/13, but 3.6 can flash fine)
Flash the rom
Wipe data
Reboot to system
If you need further support, we are more responsive in our support group
It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock
guorium said:
It is a beautifully crafted system. Some issues make it a deal breaker for me though.
1. Pop up about something is wrong contact manufactruer every time you boot up.
2. Android auto will not launch. Car detects phone and phone detects car but nothing will launch.
3. No face unlock
Click to expand...
Click to collapse
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added
marceldossantos91 said:
Hey.
1. don't worry about this error, it does no harm in any way, we hid it before but sources have patched against our patch, we're trying to find a new way to hide it.
2. are you using Gapps or vanilla version? I will look into this
3. Face unlock is a feature that usually gets added on at some point, it's starting to get added in some A13 roms now, please be patient it will get added
Click to expand...
Click to collapse
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!
guorium said:
I flashed vanilla first then flashed Gapps in one go. Rebooted to CherishOS afterward. Updated android auto app through google play store. I also had this issue with Pexiel Experience A12. It can be hard to test as a car stereo is needed. Thanks!
Click to expand...
Click to collapse
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me
marceldossantos91 said:
Would there be any chance you can post a log? So i can look into it, as i dont have an android auto compatible car to test with, would be most helpful if you could.
Feel free to join our support group & talk to me
Click to expand...
Click to collapse
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.
guorium said:
Sadly I don't have a forest around me. Hard to find a log. Jks. I will find log later.
Click to expand...
Click to collapse
thanks
marceldossantos91 said:
thanks
Click to expand...
Click to collapse
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.
guorium said:
Thanks for looking into this. Nokia 8 somehow spams the crap out of the log. Got the log with logcat[NO ROOT] app on wireless debugging mode. The file is very long but I believe the useful bit is at 12-16 01:10:31.019. I roughly plugged it into the car stereo at 12-16 01:10:30. Guess it takes a while for system to detect it.
Click to expand...
Click to collapse
thank you for the log i will look into it and see if i can resolve it in updated builds
marceldossantos91 said:
thank you for the log i will look into it and see if i can resolve it in updated builds
Click to expand...
Click to collapse
No problema. PE A12 has the same problema. Must be easy to miss.
4.4 build is up, happy flashing
marceldossantos91 said:
4.4 build is up, happy flashing
Click to expand...
Click to collapse
Thank you!
Enjoy
Kasi1906 said:
Thank you!
Enjoy
Click to expand...
Click to collapse
tysm appreciate it
4.6 build is up, happy flashing!