[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [VS986]

[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [VS986] - Verizon LG G4

Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
- Specials
- UsU compatible build so no need for a baseband package to be flashed!
- Using latest TITAN kernel sources
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable MM modems (recommended)
- TWRP flashable N modem
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
kessaras
steadfasterX
and more..
Sources
Kernel
device tree

reserved 1

reserved 2

No luck with the N modem yet, even with a full wipe. AOSCP just won't boot with it. I do have a full backup now, so that'll make future testing a lot easier.

I have a cuestion, is necesary install the kernel AOSCP?

OK, so I gave the 4.1 debug build another shot, following the guide here. Still can't get into Android.
Would a logcat help? I have one, but it's too big to attach. I suppose I could zip it to bump up the limit to 20MB, but I don't know if that's common practice here.
I think I'll just be patient and stick with 4.2 until someone reports that Verizon cell service works on their VS986, on Nougat or Oreo.
Stock Lollipop was starting to be unsatisfying, even with root and xposed. I was having overheating issues, Facebook would stop working, and it was just really getting bad performance overall. I think it's safe to say that so far, this ROM's benefits have outweighed losing call & text.

Nitram126174 said:
I have a cuestion, is necesary install the kernel AOSCP?
Click to expand...
Click to collapse
Read the OP. No.
EA801 said:
OK, so I gave the 4.1 debug build another shot, following the guide here. Still can't get into Android.
Would a logcat help? I have one, but it's too big to attach. I suppose I could zip it to bump up the limit to 20MB, but I don't know if that's common practice here.
I think I'll just be patient and stick with 4.2 until someone reports that Verizon cell service works on their VS986, on Nougat or Oreo.
Stock Lollipop was starting to be unsatisfying, even with root and xposed. I was having overheating issues, Facebook would stop working, and it was just really getting bad performance overall. I think it's safe to say that so far, this ROM's benefits have outweighed losing call & text.
Click to expand...
Click to collapse
Yes logcat would help a lot!
dmesg too ofc..
Sent from my LG-H815 using XDA Labs

Okay, already install this rom and it works very well, thank you very much.

Like i mentioned in the other thread, AOSCP will not work correctly on VS986 if you're using Verizon as your carrier. It pulls the wrong APN. Only option for Verizon users right now is stock L or stock MM. Maybe a rom developer can figure out what needs to be done, shouldn't be that hard since plenty of custom roms have been developed for other Verizon devices for Verizon users.

fates13 said:
Like i mentioned in the other thread, AOSCP will not work correctly on VS986 if you're using Verizon as your carrier. It pulls the wrong APN. Only option for Verizon users right now is stock L or stock MM. Maybe a rom developer can figure out what needs to be done, shouldn't be that hard since plenty of custom roms have been developed for other Verizon devices for Verizon users.
Click to expand...
Click to collapse
@steadfasterX Can you comment on this post? I would love to start using a custom ROM, but I do have Verizon. Thank you.

Hi again, I have a problem, the video camera option in any app not work, how resolve this problem?

Do you have the Android 6.0 modem installed! (Did you flash from LP ) If you did you need to flash the modem.
https://drive.google.com/open?id=1kfa8z0WHVoU2u8PtTbXYEHGYcpFFmbmE
go to fastboot mode and type this: fastboot flash modem modem.bin

ANDROID2468 said:
Do you have the Android 6.0 modem installed! (Did you go from Lp to MM?) If you did you did you need to flash the modem.
https://drive.google.com/open?id=1kfa8z0WHVoU2u8PtTbXYEHGYcpFFmbmE
go to fastboot mode and type this: fastboot flash modem modem.bin
Click to expand...
Click to collapse
Is necessary install again the modem file? in my case i install the rom in android 6 stock

No but if you flash the baseband package then you need to flash the modem

ANDROID2468 said:
No but if you flash the baseband package then you need to flash the modem
Click to expand...
Click to collapse
this rom has a conflict with VS986 modem, thus if flash vs986 modem, camera video stops working. But w/o vs986 modem, it is stuck at boot.

Deleted

Nitram126174 said:
Is necessary install again the modem file? in my case i install the rom in android 6 stock
Click to expand...
Click to collapse
If you need the camera or you are using Verizon just stay stock for now

I will redo the blobs for the vs986 once LOS 15 is ready.
But I have only 2 hands..
Sent from my LG-H815 using XDA Labs

First, thanks for your work, my phone feels like new now with Magisk installed, I'll send you a few bucks as thanks.
As for this ROM, I tested it during the week, almost everything worked for me: phone calls, 4G LTE, both cameras, bluetooth. Sadly I coudn't get the GPS to work.

steadfasterX said:
I will redo the blobs for the vs986 once LOS 15 is ready.
But I have only 2 hands..
Click to expand...
Click to collapse
Thanks so much for all this work you've put in steadfasterx, can't imagine how much effort had to go into this, and is still going into this. Many thanks.
If I'm understanding correctly after the blobs are fixed we should be able to install this Rom successfully on the Verizon device? Will this also mean that it will be easier for a LOS 15 vs986 rom to get created?
I've got $15 donation on being able to run LOS or this Rom on my Verizon (hold me to it)

Related

[ROM][7.1.2[UNOFFICIAL] LineageOS 14.1

Official status guys! That was quick. Remember to post some good logs if any problems so we can attempt a fix... https://review.lineageos.org/#/c/167878/

Flyhalf205 said:
Official status guys! That was quick. Remember to post some good logs if any problems so we can attempt a fix... https://review.lineageos.org/#/c/167878/
Click to expand...
Click to collapse
Awesome news, I can't wait to download the first build once the build servers spit it out! Thanks for everyone's continued work on the m9! I'm sure a lot of non-VZ folks will be excited as well!
I'm assuming we should be on the latest Verizon 6.0 firmware for this, 3.37.605.19? (Edit: At time of posting)

I cant wait

Rain__ said:
Awesome news, I can't wait to download the first build once the build servers spit it out! Thanks for everyone's continued work on the m9! I'm sure a lot of non-VZ folks will be excited as well!
I'm assuming we should be on the latest Verizon 6.0 firmware for this, 3.37.605.19? (Edit: At time of posting)
Click to expand...
Click to collapse
As long as you are on any MM firmware. It might not be till next week for official build. You can go ahead and download my custom build to make sure all the bugs are out before official builds get here.

Flyhalf205 said:
As long as you are on any MM firmware. It might not be till next week for official build. You can go ahead and download my custom build to make sure all the bugs are out before official builds get here.
Click to expand...
Click to collapse
Does official Lineage mean official Resurrection Remix (7.1.1)?
If not, I have it ready and will make a thread once you verify.
Thanks

klabit87 said:
Does official Lineage mean official Resurrection Remix (7.1.1)?
If not, I have it ready and will make a thread once you verify.
Thanks
Click to expand...
Click to collapse
Post away.
Sent from my HTC6535LVW using Tapatalk

is VoLTE working with this????

GohanBurner said:
is VoLTE working with this????
Click to expand...
Click to collapse
volte will probably never work on hima aosp roms. HTC have weird modems.

Looking forward to the official LineageOS 14.1 release for the Verizon HTC M9. Thanks for all your hard work, Flyhalf.
In addition to the OS update, I was also looking to update to the latest firmware, 3.37.605.19. I'm currently on the latest unofficial LineageOS 13.0 release from 03/16 with firmware 3.37.605.15.
2 part question--to simply update the firmware, is the correct firmware to flash the 3.37.605.19_NoBoot-NoRecovery_firmware.zip from santod's thread? And is it safe to flash future firmware updates as they are released?
Just trying to avoid any incompatibility with LineageOS (if that's even a thing) and a bricked device.
Thanks!

lithophone said:
Looking forward to the official LineageOS 14.1 release for the Verizon HTC M9. Thanks for all your hard work, Flyhalf.
In addition to the OS update, I was also looking to update to the latest firmware, 3.37.605.19. I'm currently on the latest unofficial LineageOS 13.0 release from 03/16 with firmware 3.37.605.15.
2 part question--to simply update the firmware, is the correct firmware to flash the 3.37.605.19_NoBoot-NoRecovery_firmware.zip from santod's thread? And is it safe to flash future firmware updates as they are released?
Just trying to avoid any incompatibility with LineageOS (if that's even a thing) and a bricked device.
Thanks!
Click to expand...
Click to collapse
Not sure about the firmware version, but keep in mind if you flash the "NoRecovery" firmware, you'll need to flash twrp separately. I just installed "3.37.605.19_NoBoot_TWRP3.0.2-0_firmware.zip" without any issues. I'm on latest LOS 13.0

lithophone said:
Looking forward to the official LineageOS 14.1 release for the Verizon HTC M9. Thanks for all your hard work, Flyhalf.
In addition to the OS update, I was also looking to update to the latest firmware, 3.37.605.19. I'm currently on the latest unofficial LineageOS 13.0 release from 03/16 with firmware 3.37.605.15.
2 part question--to simply update the firmware, is the correct firmware to flash the 3.37.605.19_NoBoot-NoRecovery_firmware.zip from santod's thread? And is it safe to flash future firmware updates as they are released?
Just trying to avoid any incompatibility with LineageOS (if that's even a thing) and a bricked device.
Thanks!
Click to expand...
Click to collapse
Well technically the latest firmware is 3.37.605.28 as of a day or two ago... But to answer you question, yes. All you have to do is flash the NoBoot-NoRecovery_firmware.zip and is perfectly fine to flash future updates.
Remember: Make sure you use the NoBoot No Recovery or else you'll have to find a computer to flash twrp back onto it and flash LineageOS before your phone can boot again.

Thank you both for your replies. Slightly different answers, so I just need 1 thing clarified.
I currently have TWRP installed. If I flash the No Boot-No Recovery, will it only update the firmware and leave TWRP in place and untouched?

lithophone said:
Thank you both for your replies. Slightly different answers, so I just need 1 thing clarified.
I currently have TWRP installed. If I flash the No Boot-No Recovery, will it only update the firmware and leave TWRP in place and untouched?
Click to expand...
Click to collapse
Yes

Battery life seems slightly worse than 13.0 was for me. I'm not a heavy screen-on-time user, so most drain is just passive standby screen off time. If I had to randomly guess, the screen-off drain rate is maybe 35% faster on 14.1 so far.
I have the performance profile set to Efficiency, as I did in 13.0. I may root (or use ADB) and have a look at wakelocks, but based off the battery "History Details" in Settings, the phone does not seem to be getting stuck awake for extended periods of time or anything. I periodically monitored battery voltages too and the battery percentage seems to be accurate, though I don't really have anything to base that on other than knowledge of LiPo/Li-ion batteries.
I'll follow up if I discover anything helpful, but has anyone else noticed slightly worse screen-off battery performance too?

Ok, can someone here tell me how to get root access on this rom? I have tried flashing the armsupersuaddon and armsupersux64 zips, neither worked. Then I tried enabling root access in the dev options and installing SuperSu from the store, that seemed to and went ahead and attempted to install binaries, but now my phone is bootlooping...I am on the latest nightly if that helps, but the first one didn't work with the flashable zips either.

I got root by installing "the LineageOS su add-on", as described in the wiki: https://wiki.lineageos.org/devices/himawl/install#installing-lineageos-from-recovery (addon zip comes from https://download.lineageos.org/extras, "addonsu-arm64-signed.zip").

I tried that one...didn't work. Might try it again after I get my phone setup again, but that's going to take a long while. Ended up having to factory reset, so I need to download a hundred apps and reset all my 2 factor authentications...all for root. Not keen to go through this again.

soulshot96 said:
I tried that one...didn't work. Might try it again after I get my phone setup again, but that's going to take a long while. Ended up having to factory reset, so I need to download a hundred apps and reset all my 2 factor authentications...all for root. Not keen to go through this again.
Click to expand...
Click to collapse
After you flash the root addon zip you have to enable root in developer settings and it should work after that. I know it is a pain but you may want to try to start over again.
But a lot of users are using root less and less these days. I don't have root currently on mine. Don't need it.

Flyhalf205 said:
After you flash the root addon zip you have to enable root in developer settings and it should work after that. I know it is a pain but you may want to try to start over again.
But a lot of users are using root less and less these days. I don't have root currently on mine. Don't need it.
Click to expand...
Click to collapse
Thanks, I'll give it a shot...and I agree about root. I only wanted it because I have the Pixel launcher flashed to my phone as a system app, but its been glitching up and making it to where I cannot swipe cards away on google now, so I was going to install pixelize and use that to see if it's version of the launcher didn't have the issue. So I found myself needing root for the first time since my M7.

[ROM][Joan][UNOFFICIAL]ResurrectionRemix v6.1.0[8.1.0]

{
"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"
}
Resurrection Remix Oreo
Installation Files
ROM
Open GApps
Changelog
Resurrection Remix Github Source
Big thanks to:
XDA developers
LineageOS team
Dirty Unicorns
Omni team
AND OF COURSE TO ALL THE SUPPORTERS, DONATORS AND USERS
Code:
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.
A lot.

XDA:DevDB Information
RR for LG V30, ROM for the LG V30
Contributors
SGCMarkus
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Version Information
Status: Stable
Current Beta Version: 1
Beta Release Date: 2018-06-01
Created 2018-06-01
Last Updated 2018-07-02

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 01.06.2018
- Initial release
Release 08.06.2018
- Source updates
- Added back sysnode (camera stuff)
- thermal/lights HAL are now bindarized
- setting right model name on boot (zip is still called h930 though)
Release 01.07.2018
- Source updates
Release 19.07.2018
- Source updated
- Fixed vibrator
- Updated vendor files to H930V20R
- Allowed access to Snap, SnapCam and Gcam Wide angle mod by default
Release 29.08.2018
- Updated Source
- Updated blobs to H930 21a

Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Which Models are supported?
A. So far it works well on the H930(G), US998, VS996 and LS998. Other models may have broken RIL or bootloop. Im open for solutions regarding that.
Q. Why is my phone restarting during the Setup? Or early after it booted?
A. If you use a MicroSD in exfat, that can be the cause. The exfat drivers are for some reason really picky when it comes to that. Change to ext4 or NTFS or so.

Dis developer is crazy!!! ..... In a good way <3
Tested all Roms, running perfectly fine.
*twinkle @ vibration*

I probably should wait for noobs unbrick guide before installing. I have been looking for info if H930 roms are compatible with H930DS, but not found yet.
Thank you for your awesome work SGCMarkus!

Man you're the best...

okaiuz said:
Man you're the best...
Click to expand...
Click to collapse
Nummber 1. LG V30 Dev!

Jimzamjimmyy said:
I probably should wait for noobs unbrick guide before installing. I have been looking for info if H930 roms are compatible with H930DS, but not found yet.
Thank you for your awesome work SGCMarkus!
Click to expand...
Click to collapse
First we need more info how the single and dual SIM device differ in kernel ramdisk and built kernel itself,
I'm sure there are RIL/services <-> ramdisk (ROM) and kernel config changes necessary to make it work on the H930DS.
Anyone on H930DS tried one of the ROMs out ?
Is access to microSD working ?
According to amazon.de it's supposedly a hybrid slot so you either have microSD or SIM 2,
that needs to be taken care of in hard- and software (ROM, kernel, etc.).
There were quite a few changes necessary to get it working on e.g. Sony Xperia Z5, not sure how it's set up on the LG V30 / V30+

OMG!!!!!!!! BTW, The libnk for GAPPS takes you to 8.0 GAPS. Just letting everyone know.

suzook said:
OMG!!!!!!!! BTW, The libnk for GAPPS takes you to 8.0 GAPS. Just letting everyone know.
Click to expand...
Click to collapse
You just have to select the right gapps on the opengapps website .-.
nothing i can influence
(8.1, arm64 btw)


SGCMarkus said:
You just have to select the right gapps on the opengapps website .-.
nothing i can influence
(8.1, arm64 btw)
Click to expand...
Click to collapse
NP, Was just trying to help others out. Thanks so much for this.
I have no quick setting tiles..I tried adjusting, also a reboot. Its blank

I tried installing on H931 converted to us998 and it wouldn't pass the bootanimation.
Coming from Boombox Rom My Process: Wipe System > Factory Reset > Flash Rom + Gapps(pico arm64) + Magisk 16.4.

suzook said:

NP, Was just trying to help others out. Thanks so much for this.
I have no quick setting tiles..I tried adjusting, also a reboot. Its blank
Click to expand...
Click to collapse
Clean flash?
Gapps packages?
Give us more information

Totally going to try this on my US998. I love this Rom. Thank you so much for everything you're doing!

topolovich said:
Totally going to try this on my US998. I love this Rom. Thank you so much for everything you're doing!
Click to expand...
Click to collapse
Let me know how it runs!?

francois amon said:
Clean flash?
Gapps packages?
Give us more information
Click to expand...
Click to collapse
Clean flash, open gapps. Same issue on dotos.

This ROM is only for h930 device. No luck flash it on us998
Stuck on boot animation as well

darkidz555 said:
This ROM is only for h930 device. No luck flash it on us998
Stuck on boot animation as well
Click to expand...
Click to collapse
I'm running it on us998. Only issue i have is no quick pulldown tiles.

darkidz555 said:
This ROM is only for h930 device. No luck flash it on us998
Stuck on boot animation as well
Click to expand...
Click to collapse
Sorry my bad haha bad flash I reflash again and it works
But encounter black screen when try to turn on the screen by pressing power button I need to double click to go in camera and press home button then it will bring me to home screen or else is black screen
Thanks a million.

Running on VS996 converted to US998. I factory reset and wiped all data. Boots up and somewhere in the setup (this happened twice when done setting up wifi and continuing) it just freezes, goes to a black screen (does have nav bar and status bar) but then restarts. Still trying to get it setup. I did not root, but I used BeansGappsMini-arm64-8.1-5X6P for gapps and that is all I flashed.
Edit: Seems to bug out everytime when you go passed wifi setup even if you skip the setup.

[ROM][UNOFFICIAL][O][UsU] LineageOS 15.1 [VS986] DEPRECATED

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the Suicide Squirrel and LineageOS Github repos.
If you would like to contribute to do not hesitate to submit patches
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on latest MM with ARB-2 (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you have no backup: TWRP flashable MM modems (N will not work)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Flash GApps (8.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Download
Get your builds from my leech server
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Known issues:
blobs update needed (nothing you can do - must happen in the ROM)
Check the current issues at the github tracker (feel free to help, provide logs etc!)
Credits
LineageOS
ThePiGuy
kessaras
steadfasterX
and more..
Sources
LineageOS
Kernel
device tree
build manifest
XDA:DevDB Information
lineage-usu-vs986, ROM for the Verizon LG G4
Contributors
steadfasterX, ThePiGuy, kessaras
Source Code: https://github.com/Suicide-Squirrel/local_manifests/tree/los-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: latest ARB-2 MM firmware
Based On: pure LineageOS
Version Information
Status: Alpha
Created 2018-06-20
Last Updated 2019-07-10

Reserved

So for this rom I am supposed to use the MM modem, not the N modem as stated in the Unlock thread?

Yoyodude1124 said:
So for this rom I am supposed to use the MM modem, not the N modem as stated in the Unlock thread?
Click to expand...
Click to collapse
Its clearly stated in this OP.

I Installed it yesterday, so far almost everything works out of the box, I've tested:
-4G LTE
-Roaming
-Phone Calls
-Wi-fi
-Bluetooth
-GPS
-Both cameras
The only thing that doesn't work is the flashlight button in the quick settings, although it works in the camera app.
I was unable to test NFC and wireless charging since I no longer have the original back cover.
As a side note, it fails Google's Safety Net even after completely removing root support from LOS, so banking apps are gonna be an issue.

lkeeler said:
I Installed it yesterday, so far almost everything works out of the box, I've tested:
-4G LTE
-Roaming
-Phone Calls
-Wi-fi
-Bluetooth
-GPS
-Both cameras
The only thing that doesn't work is the flashlight button in the quick settings, although it works in the camera app.
I was unable to test NFC and wireless charging since I no longer have the original back cover.
As a side note, it fails Google's Safety Net even after completely removing root support from LOS, so banking apps are gonna be an issue.
Click to expand...
Click to collapse
As long as this ROM is in permissive mode you will never pass safety net for sure. This is listed in the known issues in the OP. Torch is a known issue as well and have been added to the same link of the OP. As far as I know NFC will not work in any custom ROM at least it doesn't even in aoscp
Sent from my LG-H815 using XDA Labs

Hello everyone. Tell me how to switch to CDMA

lkeeler said:
I Installed it yesterday, so far almost everything works out of the box, I've tested:
-4G LTE
-Roaming
-Phone Calls
-Wi-fi
-Bluetooth
-GPS
-Both cameras...
Click to expand...
Click to collapse
I see you got phone calls to work. Do you still have Verizon?

ANDROID2468 said:
I see you got phone calls to work. Do you still have Verizon?
Click to expand...
Click to collapse
No, I'm on Virgin Mobile.

New build up
Happy leeching
Sent from my LG-H815 using XDA Labs

steadfasterX said:
New build up
Happy leeching
Click to expand...
Click to collapse
Is the blobs fixed yet?

ANDROID2468 said:
Is the blobs fixed yet?
Click to expand...
Click to collapse
Still working on this.. It's not a quick task
if you want to help :
Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Still working on this.. It's not a quick task
if you want to help :
Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
Click to expand...
Click to collapse
Ok i will try it tonight! I understand that it's not easy to build something from the ground up! I appreciate that someone is willing to develop firmware for a 3 year old phone that's lock down!

steadfasterX said:
Still working on this.. It's not a quick task
if you want to help :
Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Installed on my VS986 running MM 27c with 2BA bootstack (as in FAQ #20; verified FAQ #26)
No Gapps yet, but did flash SuperSU.
Booted quickly, no bootloops.
Tested camera, browser on Wi-Fi… looks good so far!
But, as usual there is no cell service- the phone isn’t seeing the SIM card.
This is the first LOS Oreo that would boot for me, so thank you!

cowsngrass said:
Installed on my VS986 running MM 27c with 2BA bootstack (as in FAQ #20; verified FAQ #26)
No Gapps yet, but did flash SuperSU.
Booted quickly, no bootloops.
Tested camera, browser on Wi-Fi… looks good so far!
But, as usual there is no cell service- the phone isn’t seeing the SIM card.
This is the first LOS Oreo that would boot for me, so thank you!
Click to expand...
Click to collapse
wow great! didnt expect that it even boots.. yea cool the blobs I use are taken from 2BA!
for the SIM:
dialer: type *#06# (do you see your imei?)
settings: phone info -> do you see your imei? do you see your mobile phone number?

the experimental rom did not boot for me. it was close the welcome screen pop up for a couple seconds

ANDROID2468 said:
the experimental rom did not boot for me. it was close the welcome screen pop up for a couple seconds
Click to expand...
Click to collapse
then its very likely the firmware. whats yours?
.

steadfasterX said:
wow great! didnt expect that it even boots.. yea cool the blobs I use are taken from 2BA!
for the SIM:
dialer: type *#06# (do you see your imei?)
settings: phone info -> do you see your imei? do you see your mobile phone number?
Click to expand...
Click to collapse
*#06# I get MEID, which is a different number from the IMEI
Settings> System> About phone> Status> SIM status: both IMEI and phone number show correctly

cowsngrass said:
*#06# I get MEID, which is a different number from the IMEI
Settings> System> About phone> Status> SIM status: both IMEI and phone number show correctly
Click to expand...
Click to collapse
thats... weird.. is the IMEI correct when going to the imei boot screen? --> poweroff phone, disconnect USB, press vol+up and vol+down the same time
.

steadfasterX said:
thats... weird.. is the IMEI correct when going to the imei boot screen? --> poweroff phone, disconnect USB, press vol+up and vol+down the same time
.
Click to expand...
Click to collapse
IMEI boot screen shows correct IMEI with barcode.
Serial number is blank with a short barcode.

[ROM][11.0] WaveOS 4.1 Rasmalai for realme C11/C12 [UNOFFICIAL][RMX2185/89]

{
"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"
}
WaveOS 4.1 - Rasmalai
WaveOS is an android custom ROM based on AOSP, focused on delivering a perfect blend of aesthetics, functionality and performance out of the box. This version (4.X) is based on Android 11. Various optimizations and enhancements have been merged from CAF and upstream AOSP to maximize performance and battery backup, and improve OS functionality. We provide a unique and beautiful user interface out-of-the-box that's inspired by OnePlus' OxygenOS and can be tweaked to your liking. We've also added handy features and customizations that improve user experience and prove to be useful at the end of the day, rather than bloating the ROM with unwanted features and customizations that could cause stability issues. We hope you like it! #NeverBetter
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.
*/
Features
Head over to our full features list at GitHub | Changelogs
GApps included
Device-specific features
- Fixed VoWiFi
- Fixed ViLTE ( Carried Video Calling)
- Fixed Wifi and Bluetooth Dead on CONSYS_MT6765 Wifi Card Device
What works?
Almost everything
What's broken?
- DT2W
You tell me!
ROM: https://sourceforge.net/projects/re...R-v4.1-20210306-0721-UNOFFICIAL.zip/download/
Magisk: https://github.com/topjohnwu/Magisk/releases
INSTRUCTIONS
Reboot to recovery
Wipe data, cache, and dalvik if coming from another ROM
Flash ROM zip
(optional) Flash Magisk
Format data if encrypted
Reboot and voila!
Upgrading to a Newer Build
Reboot to recovery
Wipe cache and dalvik
Flash ROM zip
(optional) Flash Magisk
Reboot and voila!
Screenshots in post #2
Follow us on Twitter | Telegram
ROM Source: https://github.com/Wave-Project/
Device Sources: https://github.com/techyminati/android_device_realme_RMX2185/
Kernel source: https://github.com/techyminati/android_kernel_realme_mt6765
Cheers and #NeverBetter 
If you like my work, Please Press Thanks on this Thread

if u have Firmware will u Post Link for Stock Boot File with Scatter.?

Thanks for this Custom ROM. Seems the other Custom ROMs in the main thread suffer bad bugs. Are there any significant bugs in this ROM? This is available for Realme C12 too (RMX2189), can you confirm that?

youcancallmekhen said:
Thanks for this Custom ROM. Seems the other Custom ROMs in the main thread suffer bad bugs. Are there any significant bugs in this ROM? This is available for Realme C12 too (RMX2189), can you confirm that?View attachment 5258343
Click to expand...
Click to collapse
I would suggest you to not flash this custom rom or any other custom rom in this thread. I've flashed all of them and every one of them has bugs. With that many apps doesn't work either and no apps run in the background like music app, games etc. Aside from the bugs everything else is smooth in wave os but not in the other roms. Specially Google pixel one which has serious performence issue. If you still want to flash them then don't forget to keep a backup of your original rom.

@Mahmudur_Rashid
Have you flashed stock rom with the guide I have given at https://forum.xda-developers.com/t/...rp-3-5-0-for-realme-c11.4236095/post-84693107 ?

HemanthJabalpuri said:
@Mahmudur_Rashid
Have you flashed stock rom with the guide I have given at https://forum.xda-developers.com/t/...rp-3-5-0-for-realme-c11.4236095/post-84693107 ?
Click to expand...
Click to collapse
Unfortunately no, the stock recovery image you provided didn't work. After I flashed the recovery image, I could no longer access my recovery so I re flashed the twrp image and it worked again. Since I couldn't even use the image you provided I didn't even have the chance to flash the stock rom. However, the good news is I did manage to go back to stock rom after I gave my android to the official oppo service center 2 days ago. And as expected, they did it free of cost but my warranty is now void.

Mahmudur_Rashid said:
the stock recovery image you provided didn't work
Click to expand...
Click to collapse
Have you extracted the zip and flashed like TWRP?
Didnt work means it goes to fastboot mode?
Thanks

HemanthJabalpuri said:
Have you extracted the zip and flashed like TWRP?
Didnt work means it goes to fastboot mode?
Thanks
Click to expand...
Click to collapse
Yes, I extracted the zip file and flashed the stock img using my pc just like how I flashed twrp but it still didn't work. So I re flashed twrp

Is this rom better than stock rom for stability and performance. Are there any bugs other than d2w.

babisai said:
Is this rom better than stock rom for stability and performance. Are there any bugs other than d2w.
Click to expand...
Click to collapse
Not at all...It's unstable

Mahmudur_Rashid said:
I would suggest you to not flash this custom rom or any other custom rom in this thread. I've flashed all of them and every one of them has bugs. With that many apps doesn't work either and no apps run in the background like music app, games etc. Aside from the bugs everything else is smooth in wave os but not in the other roms. Specially Google pixel one which has serious performence issue. If you still want to flash them then don't forget to keep a backup of your original rom.
Click to expand...
Click to collapse
Oh, too bad. But it seems an official build of ChiperOS is now usable on Realme C12 and C11, have anyone tried that?

youcancallmekhen said:
Oh, too bad. But it seems an official build of ChiperOS is now usable on Realme C12 and C11, have anyone tried that?
Click to expand...
Click to collapse
I didn't try that one yet so I can't tell

Mahmudur_Rashid said:
I didn't try that one yet so I can't tell
Click to expand...
Click to collapse
Mahmudur_Rashid said:
I didn't try that one yet so I can't tell
Click to expand...
Click to collapse
Got it. Thanks!

Mahmudur_Rashid said:
I would suggest you to not flash this custom rom or any other custom rom in this thread. I've flashed all of them and every one of them has bugs. With that many apps doesn't work either and no apps run in the background like music app, games etc. Aside from the bugs everything else is smooth in wave os but not in the other roms. Specially Google pixel one which has serious performence issue. If you still want to flash them then don't forget to keep a backup of your original rom.
Click to expand...
Click to collapse
Did You ever care to attach a logcat for bugs? we aren't paid for this & neither we are magicians that we would know what bugs you are experiencing !
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed any root implementation
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless). Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

babisai said:
Is this rom better than stock rom for stability and performance. Are there any bugs other than d2w.
Click to expand...
Click to collapse
try it yourself instead asking here

Mahmudur_Rashid said:
Not at all...It's unstable
Click to expand...
Click to collapse
Telling the ROM is unstable without giving a single logcat/issue description, All Bug reports without description & logcats would be ignored

TechyMinati said:
Did You ever care to attach a logcat for bugs? we aren't paid for this & neither we are magicians that we would know what bugs you are experiencing !
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed any root implementation
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless). Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Click to expand...
Click to collapse
If you are offended in some way by my words then I apologize. I didn't mean to offend you. I was just simply telling people what I experienced during my usage. And sorry I can't provide you with the necessary logs anymore. The reason is, I took my android to a service center a few weeks ago to flash the official stock firmware. As a result, currently I'm not using any of the custom roms made by you so I can't use a logcat on them. FYI I didn't flash any custom kernel or rooted my device when I used the custom roms.

Hello sir

Plz port a linux os, touch ubuntu, or selfish os, plz plz , for realme c11

rjsheesh said:
Plz port a linux os, touch ubuntu, or selfish os, plz plz , for realme c11
Click to expand...
Click to collapse
Realme C11 is an Android device. While it's possible to use Linux operating systems, it's really damn hard to port one.

CherishOS V4.8 [13] [Gapps/Vanilla] [NB1] [Unofficial]

{
"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!

Develop Bugs

welcome