yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
But, there is problems with the kernel on a530w even though it's on a530f firmware, it looks like we need a530w defconfig/ramdisk
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
Still seeing some freezes and random reboots with v1.1. I'm gonna try a clean reinstall to see if it makes a difference, because I installed this one over the old stuff.

I've tried copying adbkeys.pub to /data/misc/adb but no change, I still can't connect over adb.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Which variant you got? Which ROM you got? Did you flashed Xposed? Could you provide some logs about the issue?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] ervius:
hi, same problem for second part, I cannot connect my device with pc in USB debug mode, also copied adbkey.pub, but no success, maybe you have to make some changes on your kernel, btw, I thank you, cos without your kernel I wasn't able to root my Samsung A8, this little fix, made the kernel perfet, in my opinion!

Partially solved. Before install your kernel, connected phone by debug usb to pc, saved adbkey stored on pc, installed kernel, putted key on device, renamed to adb_keys perm:644, rebooted and now phone is finally connected in usb debug with the pc.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
MCK v1.2 with the fix for ADB pop-up not showing has been released now. Check it out ;)
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] ervius:
just flashed 1.2 (and immedially after, reflashed also magisk superuser), all seems to work well! thanks!
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
I'm on A530F with an official Oreo ROM for Romania. Does the exact version matter? I can look it up. Is there an official Oreo ROM that you guys would recommend that's known to work well?

I installed Xposed from Magisk, but without any modules. Is that known to cause issues?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Just wanted to know if you are using a Custom or Official ROM. Your issue is Xposed, already explained some posts ago it isn't compatible with Samsung firmwares so it causes different issues on each different phone, not just A8 (you got lags/freezes, another user here got not working baseband). And no, till now there isn't a custom build compatible with Samsung's Art libs, there was in LP/MM but Wanam isn't working on a new custom build for N/O
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] philcoo2:
Hi BlackMesa,

thanks for you work on the kernel.

I have downloaded and noticed it is named V2.1 instead of V1.2, will this possibly cause problems later on if you then release a version V2.1.

thanks

Phil
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Where do you see it "named" v2.1?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] :
V 1.2 is for me.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] philcoo2:
Hi sorry just realised I had also previously downloaded your custom kernel which was V2.1, and was looking at that instead of the correct file which is indeed V1.2,

thanks for the quick reply, I will look a bit better next time before putting my keyboard into use .
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
Thanks. I've been running without Xposed and I'm not seeing any more problems, indeed. The ADB prompt is working perfectly in v1.2 as well.

I'm going to look for (or open) a thread specifically for Xposed, to keep track of it. Edit: Here's the thread.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Alright gentlemans, got some things to ask/say:

- I'm curious to see how the battery life is with the beast. If you want, share here your best battery cycle, with Battery Stats Screenshots!

- Feel free to ask new features or to fix issues on the kernel, I'll be happy if you report some bugs or have nice ideas about the kernel; I don't have in mind to release more v1.x updates, gonna instead merge all on v2 with new Sammy source code once it's released. About the new upcoming firmware...

- Next firmware coming Soon™ this month with build number XXU3BRH5, other than a security patches update and some fix, will bring a new bootloader revision (Rev 3). This means if you flash this new bootloader once it's out, another Rollback Prevention fuse will be burned, preventing you to downgrade back to Rev 2 Bootloader and lower (you can't even downgrade to Nougat anymore), so once it's out be careful if you get any OTA and choose wisely if upgrade your bootloader or not.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
I'm seeing freezes and reboots again with v1.2 after a couple of days of the phone sitting mostly idle, and this time there's no Xposed installed. I'm only fiddling with it on the evenings at home, not actively using it throughout the day.

I'll try capturing logs through "adb logcat". Not sure if logs survive over reboot, I'm guessing my best bet is to keep it connected and dumping logs, and hope I catch it in the act?

Should I wipe the phone and reinstall v1.2 clean? So far I've installed v1.1 and v1.2 without complete stock reflash (but I've reflashed a TWRP dump of the boot partition each time).
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
There's no need to reflash the whole ROM and to restore the stock kernel. Does older versions give you the same issues without Xposed?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
I will retest v1, v1.1 and v1.2 individually and get back to you.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
confused

Hi Mesa,

On the page where you put three files with version 1.2, I found three files. One has extension tar.gz and the other two have extensions zip. Which of these two files are the right file? Maybe I had to flash both of them via TWRP? Or I am in wrong...?

For what is the file with tar.gz ekstension?

Thank you and apologize for mu bad English
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Well, the files are named. If you want to download and install the kernel, download the MCK zip. If you want the source code (even if I doubt lol) download the Source Code zip/tar.gz. What's so hard with it?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
Just flash the 1st zip, source code zip and tar.gz are only for developers
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
Thank you. I am beginner in this, and only the 1st file will be the right thing fom me :cyclops:
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] explorer1234:
So i install this ! how i can Root without any problem same bootlop or somethings?

i read Somewhere that magisk16.7 is not working and baseband or simcard are going too Null!

(Sorry for Bad english)
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Post #83:

Since v1 MCK is full compatible with any Magisk version: just flash MCK, flash the Magisk version you want and you're ready to go, without any issue?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
Question, do versions 1.1 and 1.2 undervolt by default?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Undervolt? You maybe mean underclock. It's there since v1 and as I saw it doesn't gives problems, instead it's helpful with idle since CPU uses a lower clock (200/700 instead of 400/900)
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
My impressions and experiences after 2 days of using version 1.2:

The installation went smoothly. After installing Magisk Manager, the manager checked that the phone was routed.

All the applications I installed required root permission and I confirmed through the magic manager.

Battery drain a little faster than with the stock version, about 10% faster. Everything is OK.

The only problem I've had is with the Titanium Backup application. It constantly reports that the phone is not rooted with the SuperSu and can't function. Even the Lucky patcher could not patch it to the Pro version.

Did anyone of you have problems with the Titanium backup installation? Maybe I'm using the wrong version of app and the key?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
SuperSU is outdated, use Magisk instead. Question about battery: can you send your battery stats of the day screenshot? Also do you use AOD?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] :
Use Magisk Manager. Not use SuperSU. I not have problem with Titanium Backup and Lucky Patcher.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
You did not understand me :)

I used only Magisk, this is OK. I root phone with it. The Magisk Manager confirm that too.

Problem is in the fact that my Titanium want SuperSu, and say: You dint root your phone with Super Su. :)
[MENTION=4688478]MESA[/MENTION] I am beginner in all this, and If you want anything, please write to mi step by step how to find battery status and that analytics (maybe on pm?)

@ZmisaS Can you send me link or Titanium app on private msg, if you have a good version that works?

Thanks
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
It's not an app issue since it works good on latest version of Magisk, instead which version of Magisk are you using? Also I don't think you don't know that you can see your battery stats inside Settings>Device Maintenance>Battery>Battery Usage. You didn't answered if you use AOD during your cycle :rolleyes:
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
-I am using v16.7

-Battery usage is on screenshot

-Can you plesase tell me what is AOD? (soory again, I am noob)

tnx[IMG="Battery usage screenshot"]https://we.tl/t-ThDvoF3YcA[/IMG]
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
-Using official build from its xda thread?

-I can't see nothing since text is too big. Drain in the graph seens normal tho

-Always On Display, the clock shown when display is off.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] wirespot:
You can also try Magisk 16.7.3 or 16.8 suggested in this thread, it's supposed to fix baseband.

[MENTION=3168611]andrejic[/MENTION]: Try following this install procedure, using that I haven't had issues with Titanium ever since MCK v1.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
- yes

- below the graph is the list of app which use energy. The "Display" is on the top of the list (7%)

- AOD is disabled. I dont like this feature, becayse it is in conflict with other features that I use (like Tap to zoom screen option :)
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Strange Titanium doesn't works, it should with latest Magisk version; You can try the custom build wirespot linked ya but I don't think the issue will be solved. Regarding the drain try to do another cycle, if drain is still there then see if there's some app that drains the battery via Battery Stats in Settings (there could be an app that has a wakelock active and doesn't sends the phone in Doze mode). Another thing: did you flashed something else more than MCK v1.2 and Magisk?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
Now it is OK. I Installed Titanium v8.1.0 and this is the right version. (Thanks to [MENTION=4398224]ZmisiS[/MENTION] )

- No I flashed only MCK v1.2 and Magisk 16.7. After that, I installed Magisk manager and, Lucky pather. And the last app is Titanium backup
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] mecoromeo:
When rooted can we still get OTA or do I need to flash updates manually after rooting?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] mchlbenner:
No you will use Odin to update your phone.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
OTA are broken since SysScope detects you're using custom binaries and modified your phone, even too you use a custom SysScope with spoofed status you can mess your phone by flashing back stock kernel/recovery. The only way, if you know how to play with tar fw files, is by flashing newer firmwares via Odin. It is annoying if you don't know how to repack tar fw files since you'll need to flash again TWRP and install back all the zips you installed previously
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrejic:
Just to report one issue:

In the sound settings, there is no possibility to activate Dolby Atmos.

Is it problem only at my phone?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] :
Turn on the headsets.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
Just a notice to all A530W users:

A530W oreo is out, but you still cant be excited to flash this kernel on A530W, because there are problems with this kernel on A530W with a system exception, wifi not working, and more

So please do not report because mesa already knows of this.

The only reason why A530W is in the supported device list is because rarely the kernel works without any issues
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
It will not work anymore if you flash sounds mods like V4a
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
After weeks of tests, I'm proud to announce v2 is finally here! A big thanks goes to my testers team for their big patience and their time to test the 3200 test builds I had sent them (lel). Enjoy!
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
np I'm always interested in flashing stuff ?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] Sascab1:
I have a samsung a8 2018 with rom stock I install the kernel v2 oreo and it tells me that the settings application has stopped when I try to enter developer options my language in the cell phone is Spanish (Spanish United States) why?:confused::confused::confused::confused::confused::confused::confused:
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
You can change the language..

And that bug was here since the release of mck, READ OTHER POSTS FIRST BEFORE POSTING FFS
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] Sascab1:
I have changed the language to English, or what should I change? I still give that error, and I read every answer and do not give the correction a thousand apologies if you can support me I would appreciate it otherwise I will continue looking ... my english is bad use google translator: c
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] :
Is your device rooted? If yes, try re flash Magisk, and maybe and "no-verity-opt-encrypt-6.0.zip" and RMM-State_Bypass_Mesa_v2.zip".
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] Sascab1:
it worked I just made root thank you very much:good::good:;)
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] :
You're welcome.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] solamente:
MCK V2

First of all, Mesa your kernel is amazing!

A'm on (A530F Oreo T-Mobile Netherlands), with MCK V2 kernel.

Everything works smooth for me, battery consumption is good, and I got Xposed with four modules running for a day now, still no problems with it.:laugh:
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
It's ok if you run xposed, but fyi there are a ton of modules that don't work for Samsung devices
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] solamente:
You're absolutely right, many modules don't work, but thats why I tried different modules, and found out which work for me, especially the one I needed.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Please remember you will not get any support from me about any bug/issue reported if you use Xposed. Xposed isn't compatible at 100% with Samsung Experience ROMs, this means 90/100 times you'll get random issues on your phone (from random apps FCs, to bootloops, no baseband etc).
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] solamente:
\

I understand, I am researching, and if it doesn't work out a reverse back will take place.

so far so good!
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] dwane3:
update will be?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] 587.saboor:
Now
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
MCK v2.0.1 is now out! This tiny release contains 3 major improvements:

- Updated kernel source code

A lot of users reported MCK v2 wasn't working with September or greater Stock/Custom firmwares. This has been now fixed and you can now enjoy MCK in the ROM you want!

- Overclock GPU to 1300MHz

Even if I'm not an "overclock lover", this feature has been requested by some users, you'll now have some little improvements in games/media playback.

- Removed SELinux Fake Enforcing

Removed because it's an useless feature (SafetyNet passes anyway without it) and since SELinux denials occur anyway because of the spoofed status. With this new version of the kernel you should also be able to install Samsung Experience Pie Apps Port now! (Remember you'll also need a custom firmware with signature check disabled).

That's all! As always let me know if you find some issues or just share your battery life/experience with the kernel. Enjoy!
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] dwane3:
Overclock GPU is not good fot battery life,please add version with stock freq.Thanks.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
Don't worry: gpu uses interactive governor, so it will use max freq just when needed. If you anyway want stock max freq (1100MHz), you can set it with a Kernel Manager app (such as Kernel Adiutor or Kernel Toolkit).
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] andrea2004:
in the features there is written false knox flag 0x0, so it means that apps like samsung pay and pass will work? the guarantee is lost, however, true? thanks for the wonderful work.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] BlackMesa123:
No, just userspace flag is faked (ro.boot.warranty_bit). Once you blow your Warranty Bit you can't get anymore Knox TZ feature to work and neither reset it. Samsung Pay and other Knox TZ features doesn't works anymore because use Trustonic trustlets to communicate with TrustZone and create the Knox Container. Those bins read the Warranty Bit flag directly from Trusted Boot and not from the userspace flag, so if the Warranty Bit is "blown", trustlet blocks the access to TrustZone.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] riesandyfr27:
i just installed on salimskiy rom . i give feedback later thank u ?
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] :
After I installed MCK v2.0.1, I have managed to install all .apk applications (Samsung Experience Pie Apps Port) on my own Samsung Galaxy A8 (2018) SM-A530F, Android 8.0.0 which is rooted. Just Calendar not working for me.
[Samsung Galaxy A8 (2018) ROMs, Kernels, Recoveries] Davidec01:
Hello im new here

How dex support works? I must download the samsung dex app?
[Honor 9  Questions & Answers] mightyjcb:
Hi all,

Currently running Oreo (via OldDroid manual update) then LOS 15.1 (Berkley unofficial) on top, which is great but would like NFC, buttons, flashlight.

What is the best method to reinstate this functionality? I have tried the rollback for OldDroid rollback to no avail. I believe this method assumes you are rooted, which i am not.

Happy to be on EMUI 5 if necessary as i believe i can now update to Oreo OTA.

Cheers
[Honor 9  Questions & Answers] mightyjcb:
Can i provide further pertinent information or ask elsewhere to get replies?
[Honor 9  Questions & Answers] oslo83:
What did you do in the fist place to go from stock oreo to LOS 15.0 ; any links ?
[Honor 9  Questions & Answers] mightyjcb:
Thank you.

I flashed the system image using "fastboot flash system system.img" via article https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/

Cheers
[Honor 9  Questions & Answers] oslo83:
I think, once unrooted, you'll have to flash back stock system.
[Honor 9  Questions & Answers] mightyjcb:
Great, thank you. I am not rooted so I extracted the system.img from STF-L09SC432B360a (from http://pro-teammt.ru/firmware-database/?firmware_model=STF-L09&firmware_page=0) using this guide https://xdaforums.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733

Then using that stock emui 8 system image:

"fastboot flash system system.img"

I receive the following error:

error: cannot load 'SYSTEM.img'

Any ideas?

Cheers
[Honor 9  Questions & Answers] mightyjcb:
Another attempt at system.img extract using my windows box and the windows software referred to in https://xdaforums.com/mat...files-t3756733.

This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :

Huawei eRecovery :

"Serious problems occurred when the phone boot, you are recommended to do factory data reset

NOTE: user data will be wiped after recovery".

I performed this reset and device booted to TWRP some commands took place but too quick (saw selinux buts thats it). Device rebooted twice then loaded Huawei eRecovery where the only option is :

Download latest version and recovery

Restore system with wifi

Entered wifi details

Getting package info from server

Getting package info failed.
[Honor 9  Questions & Answers] mightyjcb:
Booting into TWRP the 'Factory Reset' option performs the same process that i saw when Huawei eRecovery recommended the factory data reset. Some i'm confident in what happened at that point now. Unsure as to what to try at this point. The phone does not boot into EMUI and will only boot to Huawei eRecovery.

The bootloader is unlocked, as per the process to install LineageOS 15.1 in the link in the OP. I've not checked if its still unlocked, but guess that could be causing a problem?
[Honor 9  Questions & Answers] mightyjcb:
Just checked and bootloader is unlocked.

Interestingly the process to re lock it from the Huawei site (https://emui.huawei.com/en/unlock_step) shows that you have to use the same command to lock the bootloader as to lock it again:

Note: to re-lock the bootloader after unlocking it, restore the device’s software to the Huawei official version using a microSD card then switch the device to fastboot mode and enter “fastboot oem unlock ****************” in the computer’s command prompt, where * refers to the 16-digit unlock password. The device will then restart, and the bootloader lock status will change to “Bootloader Lock State: RELOCKED”.

If i follow those instructions i get the below error:

fastboot oem unlock **************** <-my 16 digit code
...
FAILED (remote: already fastboot unlocked)
[Honor 9  Questions & Answers] oslo83:
Stop trying to lock your bootloader, it won't help you. Interresing info though.

Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?

This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.

I think a format system from this stock recovery, not twrp, would have solve your problem.
[Honor 9  Questions & Answers] mightyjcb:
Thanks. So I can leave the boot loader unlocked at this point and run stock emui? I'll flash stock recovery. Perhaps that will suggest factory reset and then I'll be able to boot.

Thanks again.
[Honor 9  Questions & Answers] mightyjcb:
In order to revert to the stock recovery is it necessary to flash all three recovery images from the update.app file? :

recovery_ramdisk

recovery_vendor

recovery_vbmeta
[Honor 9  Questions & Answers] mightyjcb:
Looking at flashing the recovery_ramdisk image with the stock version i have extracted using the below:

fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img

Noticed the stock recovery_ramdisk i extracted has a filename of 'RECOVERY_RAMDIS.img', not ending in 'K' for 'RAMDISK. Presumably i can simply rename my recovery_ramdisk to "RECOVERY_RAMDISK.img" unless a 15 character filename is a limitation, or adjust my fastboot command to :

fastboot flash recovery_ramdisk RECOVERY_[B]RAMDIS[/B].img