yashsingh1/xdaforums huggingface dataset:
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
Sorry for the delayed response =/

I tried TeslaRom for sometime. It ran into conflicts with some sepolicies inside device tree, some issues regarding some config inside some make files. In the end, it got until 90% compiled and I couldn't figure out what was causing the (I assume) the last issue. I tried some help in that telegram group you linked me, but couldn't get any help as the guys didn't know for sure what was causing my issue (I googled a lot too). It was some functions that the compiler was saying weren't used but they were. As solving it implied a lot of experience with c++, I gave up and tried to use your base (device, kernel and vendor trees) to compile an Oreo rom (ValidusOs). And here I'm =P facing caf issues (errors inside this folder hardware/qcom/display-caf/msm8996/sdm/libs/core/drm/ - I tried to find a file named sde_drm.h but I didn't found anywhere. It seems the root of these errors). I have a lot of work to do (some exams to grade, exercises lists to prepare for my students and russian homework to do) so I'm not working in anything by now. But as soon as I'm free, I pm you at telegram ^^

I want to flash your new LOS build (I'm using AEX for substratum support) but I need to finish those things first xD

Sorry if I went a bit OT here :p
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] salama_ahmed:
h follow the istruction and flash this rom in my nova plus (mla-l11)

its about an hour and half now my phone stick on ligea os logue now thing happin after that just lingea os logue

please any one help me what should i do

and iam sorry for my bad english language
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
If the phone doesn't boot in the first 15 minutes, it probably won't. There is no need to wait so much.

Go to twrp. Check the terminal output (the key in bottom right). I had problems with custom ROM because my cust partition was corrupted, so I suggest you to look if the twrp terminal has a message about cust partition. If so, download the attachment from this post and restore it via twrp. If you don't have a message about cust partition, this backup probably won't solve anything. Also, tell me that you did a backup before flashing the ROM.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] salama_ahmed:
no my phone was brick i try to solve it by flasing any rom

rom flash normally there is no error just stock on lingea os logue

i try every thing i dont know what should i do to get this phone alive again
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
the error I said isn't from the flashing process. If you just boot into twrp it should say "failed to mount cust partition" or something like that. You can check in the mount option from twrp if cust is mounted. If not, try to mount and see if gives an error. If so, do what I said, maybe it helps to solve your problem.

EDIT:

Also, did your wipe system and data partitions? If not, wipeing it may solve. If yes, maybe you have to format data, but be warned that it will clean all your data (personal files too. You have to backup things if doesn't want to lose photos, videos and so). You can if one this official ROM help you (try the fullota package)
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] salama_ahmed:
Everything is mounted except product is not mounted

I try to flash custom framework

But it not boot

So I tried every stock rom but as I said the phone stick on Logue

I will try to flash another custom framework by hauwei multiple tool or fast boot

I wish it work

I'm very said for my phone

It's make my tired ?

I tried everything no thing works till now

---------- Post added at 11:47 PM ---------- Previous post was at 11:13 PM ----------

I check everything now I change TWRP recovery

I wipe every thing data factory reset even advanced wep I wip every thing

Then I flash the rom again

The same problem not solved

First of all the phone was work good then he brick for unknown cause

I open its boot loader by hauwei multiple tool

Then I tried every rom in xda

The only thing I get rom Logue without booting
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
don't try to flash custom ROM via fastboot or huawei tool, it won't work.

I don't know... did you try to flash via fastboot this twrp? Sorry if yes, I'm just trying to help. You said that product partition doesn't mount. Download this file, unzip it inside your twrp backup folder and restore it. Maybe it can help.

The sad thing is that if I'm not mistaken, there are people with same model as yours who could flash this ROM.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] salama_ahmed:
It's work

I restore back up you send to me then I mount device

And it's working my phone is alive again thank you very much my bro

But is there any way to flash custom framework

In my phone ??
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I've just tried front camera with Snap camera and the pic looks similar as yours. Then I've tried Open Camera and there's no green color in the pic. Did you try another camera? I'll look into the issue, but not now because I'm working on Oreo.

Thank you for your feedback! Can you mention the XDA threads for those cameras so others can benefit too? You can also make a thread at apps section if you add "[SHARE]" in the thread name and add the "official" XDA links from cameras there.

Thank you! Yes, I'll build AEX too after LOS15 because it's kinda my favorite ROM too hahaha. It's second ROM after LOS which I'd consider.

I don't have those issues. Try to restore this /product backup in TWRP or update to N and then flash the ROM again.

I've put your quote between hide tags because it's kinda big :D As a beginner, I'd say that you should build a ROM which is more common / popular because just as you see, building TeslaROM or whatever can be a pain in the ass. There's ROMs which doesn't even build because they're left outdated, abandoned. I've experienced it myself before and I had to fix the problem(s) on my own. Of course you'll learn some things while building such ROM, but it's just troublesome, especially if it's the first ROM you're building. That's my opinion though. That telegram group no longer exists, but it looks like a new one got created.

As for Oreo, the kernel you've used is "broken" :D. That's why you're getting those build errors about SDM. The only kernel source which is working is the N one updated with few commits for O which you can find in the "los15" branch at the same repo from first post. However, building this kernel in LOS15 sources will result in build errors. I have one made for LOS15 (based on a newer CAF tag), but I haven't uploaded it to github because the kernel it's a mess, but it boots. I'm using this one to make a build of LOS15 and then I grab the zImage of the other kernel updated for O (after building it under LOS14 sources) and repack boot.img, so everything is supposed to work fine. Maybe I'll add it as prebuilt, so I don't have to repack it everytime I make a new build. Anyway, this is temporary though, until I rework that kernel based on the newer CAF tag.

Also, the device and vendor trees needs to be updated for Oreo, so you can't simply use the N ones xD.

By the way, the cust partition backup from attachments at your post has only 954 bytes haha. I have it on mediafire.

Thank you for your reply and for helping others!
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] stijm:
Great work!

Thank you so mutch for the hard work you have put into this ROM! It works very smooth, and I do not longer have the wifi-problems I had with the stock ROM.

Speaking of the stock ROM:

I had to use the stock recovery to wipe the cache and system partition, as TWRP gave me "Error 7".

It turned out that the system partition was encrypted, and only the stock recovery could decrypt the partition..

So, if you've got " error 7", find the stock firmware your your model, flash "system.img" and "recovery.img" back to your phone using fastboot and wipe the system and cache partition.

Than use the instructions provided by the maintainer of this ROM.

Just in case, now you know how to fix this particular error. Now you won't have to google around for a couple of hours to find a solution :)
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
hi man!

in fact, error 7 is a bit generic, as TWRP return it when the flash process fails. I already had my error 7 too, where for me it was wrong TWRP version being used.

With that being said, if you need to wipe your partition (any of them) there is no need to flash them over. What seems to have solvded your particular issue was fastboot flashing system because, if I'm not mistaken, fastboot writes the image to the partition as dd command do, it writes over any content inside there. TWRP wipe should solve, as it uses mkfs.ext4 to format the partition, but who knows what really happened.

and about cache partition, I find very hard to it being encrypted. Cache is composed of volatile files, they get erased some time. I don't see why it should be encrypted. I don't see why system files would be encrypted too, as personal data it is not stored there. But whatever you say ^^

edit (what I really think would've solved):

stock recovery doesn't wipe system partition. Its option to "wipe system" formats data. I don't know, I'm guessing here, but if you tried to format data (not wipe) in TWRP, it should've worked the same - it wouldn't need to do all other process
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] stijm:
The only text that was red was "error 7' my mistake for getting this conclusion too fast, im sorry!

I got the error "the system partition had not been found", or something along those lines.

I tried changing the partition type from ext4 to something else and back, and even tried multiple system.img files, but none worked :/

I am not sure rather or not the cache partition was encrypted, but the stuck recovery gave me the option, so I just wiped that partition as well...

I am not sure what made it work, but it works now, and I am loving the experience I've got this far!

Someone might run into the same fault, and this worked for me. I thought I would share it to save someone else's time :p

Still, thanks for providing the information vinnom!

It might help some one!
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
maybe system was somewhat corrupted. I had corruption in cust partition and it seems that another guy here had it in product partition. Then, when you flashed a system.img, it fixed the corruption and everything went fine. But it is only a guess from me. Anyway, I'm glad that you solved your problem, even looking by yourself in the net ^^ a lot of guys here doesn't do that :/ although I'm not complaining of providing help, it is good when people search about things before asking :)

and I'm glad you're liking #Henkate's work ^^ he really puts a lot of effort developing and learning things :D
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
Please share the full logcat, by uploading it to the attachments or paste it on del.dog / pastebin.com

Thank you for your words and for sharing the solution to the problem you've encountered!

I'm just curious, what WiFi problems did you have with stock ROM?

I've made a new build with the same trees which I've used in February (before I've broke my Nova) and it no longer boots lol. Phone gets stuck at unlocked bootloader message, but I'm able to get logcat though. I've took logs, but I couldn't find anything else beside a line which says that's waiting for SurfaceFlinger to start, something like that. I'll look more closely into the log today. I think I need to use newer display blobs. I think the reason it no longer boots is because there were some changes / updates in LOS sources, otherwise I can't explain myself. It would've been much easier if Huawei would've updated Nova to Oreo so I could use blobs from stock, but now I have to find ones from other phones which work for Nova. Well, I can't complain about this since I should learn more things, but yeah, it would've been easier.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vercety87:
Thanks, here the full logcat https://del.dog/noceyeheqa
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] xcdahai:
Fingerprint unlock must now be lit on the screen.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] xcdahai:
This ROM is the card brush ROM, using a third party TWRP brush machine, brush machine finish do not Shuang Qing ROM Brush Vendor Partition

Does the Chinese version of the three-party firmware have this partition, which means it will support project treble?Sorry, English is poor
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I don't really understand what you've meant. Regarding the vendor partition, yesterday I've built latest TWRP with vendor partition supported, so I could flash a test build of LOS15 which was using the vendor partition. Unfortunately, it isn't booting (I get stuck at bootloader screen), I'm not able to take any logs and I don't have any idea anymore why it isn't booting.

It can support project Treble and I'll add it in future (thanks to [MENTION=6070905]abhishek987[/MENTION] who added Treble support for mido), but for now I need to boot LOS15 again and I think I'll make new trees.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
Brush is a translation from Chinese for flash. I think you kind of answered him but it is a bit confusing. [MENTION=8055575]xcdahai[/MENTION] You can post your English translation with the original Chinese, I might be able to help more.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] xcdahai:
我的意思是5月25日更新的黑屏下无法用指纹解锁点亮屏幕，

第二个我在国内论坛上看到一个三方ROM，他说明先刷rom，然后加刷了vendor分区，我想问的是是否官方会支持PT
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] wangdaning:
I think [MENTION=4471434]#Henkate[/MENTION] answered this mostly. He is still working on getting oreo to work right on the device and then can work on bringing project treble. I am not sure which rom you found, so can't really help with that.

Not sure why fingerprint is not working for you, I think you mean to control brightness? Are you using an app for that, or xposed?

中文不是我的母语，所以对不起要是不清楚。#Henkate在办 Lineage 15办好了他会支持PT。你说的三方ROM我没看到所以没办法帮忙。

你说指纹的不会管屏幕的亮吗？你是用什么APP/XPOSED吗？
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] lyf123:
Hi God

I am Chinese, English can not understand, English can not understand Google browsers can be translated, this ROM I used, why the black screen, the mobile phone model caz-tl10 4+64gb brush this ROM can enter the system, but sometimes restarted the phone on the black screen, there is light, according to the volume will have sound, so turn over the ocean to feed back to the sea to feed back.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] stijm:
The fault with the stock rom

The problem I had with the stock ROM was that at I had to restart my phone, as there would be no WiFi networks found... None at all.

When I tried to just restart the WiFi by turning it off, the power slider would slide back on without any input of me. A restart would fix this problem for a hour, after which I would have to restart my phone ones again.

But your ROM fixed it! Great work!

Keep it up, so our phones will stay functional :p
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] iamafkup:
The default camera in lineage os gives me a green image and the google camera from open gapps crashes. Is there any alternative camera or any google camera port for the nova plus?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
What kind of nova do you have? CAN-L11? I just ask, because I never had any problem with the cam. Not on this or any older build (except old, now fixed bugs with zooming / video).

I really like 'open camera' as an alternative. you can get it from e.g. f-droid.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] iamafkup:
I have a mla-l03 fido canada edition. The default camera included with lineage os gave me really green selfies but the rear camera was fine.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
i think that is more a issue with sensors than with device model :p

mine, for example, is caz-tl10 and I have same issue he has. (google camera is crashing too for me :( I think that is because some update. Gcam from February works well)
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] iamafkup:
did you figure out any fix for the latest version of gcam? The old version works for me as well.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
there is no fix :(

it seem that even the legacy gcam is using some hal our device doesn't support. If I'm right, then there is no fix...

I'm using open camera for now
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] GNUDroid:
Did you both already tried with the build.prop parameter persist.camera.HAL3.enabled=1?
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
I'm also having this issue. It looks like it's related to HDR. If I switch to the front camera and enable HDR, the pics are no longer green, but the camera gets sort of "not responding" and you have to force close it and reopen it. Then after I've disabled HDR, the taken pics weren't green and the problem with "not responding" was gone. However, I've switched back to rear camera to take a pic and ... surprise! It was taking green pics lol. Then I've enabled HDR, took a pic, force closed camera, reopened and taken pics weren't green anymore, but the front camera was taking green pics again.

It looks like with Open Camera for example, the pics are fine with both cameras. I've also tried HDR in Open Camera and it seemed to work fine.

Maybe Snap's problem is related to this commit, I don't really know. As far as I remember, this problem wasn't present in LOS13 and neither that commit. I haven't really looked in logcat at all about this green problem and nowadays I'm busy with LOS15.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] Vinnom:
I tried it sometime ago, so I could try the new gcam (not the legacy) but if I'm not mistaken, it didn't work. I'll try again :)

UPDATE:

now I remember why the HAL3 thing didn't work for me. In fact, applying it to build.prop and rebooting made gcam work again. But all the pics taking with it looks "grayed". So it isn't a nice solution. It is better to stick with open camera :p

EDIT:

gcam photo with hal3 enabled -> https://photos.app.goo.gl/rAUa7jNj11N8BXbD8

open camera photo without hal3 enabled -> https://photos.app.goo.gl/kw47Kr746EjzvbDo8
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] sk8buoy:
Hey #gt_o can you release a build with the latest security patch ?

No rush, I was just wondering :)

Thanks
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] #Henkate:
LineageOS 15 status

In one of my previous posts, i've wrote what's the status of LineageOS 15. Now calls, SMS, mobile data and hotspot are working too. The others are still not working.

I'm really having an hard time with that and i don't want to move forward to the other bugs unless camera is fixed. I've kinda got frustrated because i'm stuck with the camera, but i've had the same feeling in past too, when i was working on LOS 14. On the other hand, it feels great when you get something working.

Since i'm stuck with the error(s) when using the stock camera blobs, I've tried to switch to the Open Source camera HAL (from CAF) on LOS 14 (so then i can update it for LOS15), but i'm getting "can't connect to camera" when i'm opening the camera app. As for the logs, i've been stuck with the error. I've also tried to switch to the Open Source HAL because i thought that i'll get camera working faster, but just as i've said, i'm stuck. I'm still trying my best though.

I was thinking to share a build as it is, but that's kinda pointless since it isn't good for daily use and i need to rework / make a new kernel. Also, in my test builds from last two days or so (i'm always syncing the sources), i'm having weird colors and i've took few screenshots, but then when i've restored my backup of LOS 14 the screenshots were looking normal. I don't know why, but i assume that's caused by the kernel since i'm using the Nougat one with few patches for Oreo.

That's pretty much what i've wanted to tell y'all.

Gabriel ([MENTION=5418262]gt_o[/MENTION]), i've seen that you haven't answered [MENTION=7880975]sk8buoy[/MENTION]. I don't know if it's due the lack of time or something else, but i just want you to know that you're free to publish new builds. I'm busy with LOS 15 and currently i can't make new builds of LOS 14 (unless i don't have any use for Google Cloud Platform, which wasn't the case for a while). Also, if you'd like to contribute to LOS 15, you know where to find me. I'd be glad to work together with you again. I'm sure that we've both learnt new things during our conversations in past. Let me know if it's ok that i've mentioned your real name. If i'm not mistaken, i've mentioned your real name in past too :D. Again, let me know if it's ok.
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] imkoma:
if you share the build i can try it in MLA-L11 :good: :good:
[Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &] fellowlurker:
Android Auto (AA) bug

Hi Henkate, Hi everyone Sorry for the replying delay, was very busy and impatient and switched back to stock b340 Emui5. Got to say Emui5 is quite good, but then I lost all the sweet control I got from rooting and exposed and init.d.

Back on topic: Android Auto (AA) works fine on stock Nova Plus Android 7 emui 5 (MLA-L03)... except the space bar disappears in google maps on the car's screen, so all text searches don't have spaces (although google still seems to understand without the spaces... and there is "ok google" working and you can dictate new directions... pretty useful).

After rooting with Xelfmade's instructions and connecting to the car I got an error saying that AA was not secure, coudn't be trusted, and couldn't launch (I also had a lot of other bugs due to restoring stuff from Titanium backup... some things such as contacts and call logs totally messed up my dialer, couldn't call anyone. I had NOT restored any data from AA).

You asked about how it connects: AA only connects through usb (AA cannot connect with bluetooth as of yet). When you connect the phone to the car, AA launches. The first time it asks for a bunch of permissions (give up most privacy). Every other time, AA launches on the phone and asks if the car and the phone can share data. In the settings, the phone does not seem to switch to MTP, still says charging mode. I can't really tell you more.

I will to go back to your build this week and will try doing a logcat, although I have never done it before... Are there special steps I should take so that the logcat give you the best diagnostic? I will keep in touch. Keep up the good work everyone!

Edit: forgot to add: on LOS 14, there was no denying of AA or anything about untrusted AA, there was absolutely nothing happening. The untrusted AA message appeared on rooted emui5 only.