yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.6 released.

Change log

Updated to upstream Linux 4.9.152.

BFQ I/O scheduler updated to v8r10. (Thanks to [MENTION=9116297]Eamo5[/MENTION] for alerting me to the newer version.)
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.7 released.

Change log

Updated to upstream Linux 4.9.153.

Updated WireGuard to v0.0.20190123.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sora94:
As always the fastest, unfortunately I upgraded to Pie.

Still, good work!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.8 released.

Change log

Updated to upstream Linux 4.9.154.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.9 released.

Well, well, well. Samsung have surprised me by releasing a further Android 8.0 (Oreo) firmware update for these devices. The only (obvious) change is the inclusion of the January 2019 Android security patch.

It's currently unknown whether there are any changes to the kernel in BSA1, but a request has been made by me and at least one other person to release the source code, so we'll find out in due course.

In the meantime, this release brings you the latest Linux kernel and utilises the latest boot images from the BSA1 firmware, which are virtually identical to those found in BRL3.

Change log

Updated to upstream Linux 4.9.155.

Rebased to Samsung's BSA1 boot images.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.10 released.

Change log

Updated to upstream Linux 4.9.156.
[Samsung Galaxy S9 & S9+ Cross Device Development] maryus1010:
thanks!
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.11 released.

It turns out that Samsung's BSA1 firmware contained no new kernel changes. As a matter of fact, the source is identical to that of BRK3, which means that it doesn't even contain the few changes that were made for BRL3. So, APGK is holding steady with the BRL3 kernel source, as I see no reason to revert the changes made for that version.

Change log

v1.0.11 (2019-02-16)

Updated to upstream Linux 4.9.158.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.12 released.

Change log

v1.0.12 (2019-02-20)

Updated to upstream Linux 4.9.159.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.13 released.

Change log

v1.0.13 (2019-02-23)

Updated to upstream Linux 4.9.160.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.14 released.

Change log

v1.0.14 (2019-02-27)

Updated to upstream Linux 4.9.161.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.15 released.

Change log

v1.0.15 (2019-03-05)

Updated to upstream Linux 4.9.162.

Built without process authentication code (CONFIG_FIVE_PA_FEATURE), since this doesn't work with custom kernels anyway. This change was accidentally omitted from v0.99.23.

Updated WireGuard to v0.0.20190227.

Rebased to Samsung's BSB1 boot images.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.16 released.

Change log

v1.0.16 (2019-03-14)

Updated to upstream Linux 4.9.163.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.17 released.

Change log

v1.0.17 (2019-03-20)

Updated to upstream Linux 4.9.164.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.18 released.

Change log

v1.0.18 (2019-03-24)

Updated to upstream Linux 4.9.165.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.19 released.

Change log

v1.0.19 (2019-03-31)

Updated to upstream Linux 4.9.166.

Fixed disk I/O performance regression introduced in 1.0.18.

Fixed a small bug introduced in 1.0.16.
[Samsung Galaxy S9 & S9+ Cross Device Development] Ogy77:
Work on Pie?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.20 released.

Change log

v1.0.20 (2019-04-05)

Updated to upstream Linux 4.9.167.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.21 released.

Change log

v1.0.21 (2019-04-06)

Updated to upstream Linux 4.9.168.

Updated WireGuard to v0.0.20190406.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.22 released.

Change log

v1.0.22 (2019-04-17)

Updated to upstream Linux 4.9.169.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.23 released.

Change log

v1.0.23 (2019-04-21)

Updated to upstream Linux 4.9.170.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.24 released.

Change log

v1.0.24 (2019-05-02)

Updated to upstream Linux 4.9.171.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.25 released.

Change log

v1.0.25 (2019-05-02)

Updated to upstream Linux 4.9.172.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.26 released.

Change log

v1.0.26 (2019-05-04)

Updated to upstream Linux 4.9.173.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.27 released.

As of this version, my S9+ has passed to my wife and I am therefore no longer able to test kernel builds prior to release.

I will, however, continue to issue maintenance releases of APGK for as long as there is interest in them.

Change log

v1.0.27 (2019-05-08)

Updated to upstream Linux 4.9.174.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.28 released.

Change log

v1.0.28 (2019-05-11)

Updated to upstream Linux 4.9.175.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.29 released.

Change log

v1.0.29 (2019-05-15)

Updated to upstream Linux 4.9.176.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.30 released.

Change log

v1.0.30 (2019-05-17)

Updated to upstream Linux 4.9.177.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.31 released.

Change log

v1.0.31 (2019-05-22)

Updated to upstream Linux 4.9.178.
[Samsung Galaxy S9 & S9+ Cross Device Development] QBANIN:
I've been using your kernel since early versions without any issue, until 1.0.31. This one is very unstable. My S9+ won't wake up shortly after reboot or restart by itself few minutes later. Going back to rock stable 1.0.30 :)
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Thanks for the report. Can anyone else confirm these problems with 1.0.31?

You probably saw my note when I released 1.0.27 that, "as of this version, my S9+ has passed to my wife and I am therefore no longer able to test kernel builds prior to release". So, I've been flying blind since then. The alternative is to stop releasing, but I don't want to do that so long as there remains demand.

You can send me a logcat if you want, but I can't guarantee a fix, because I don't have a device to test on.

I hope 1.0.32, when it comes, will fix whatever's wrong with 1.0.31. If not, we may have to earmark 1.0.30 as the final stable release if no-one else is able/willing to take over the work.
[Samsung Galaxy S9 & S9+ Cross Device Development] QBANIN:
Perhaps this will help https://cloud.sobczyk.in/index.php/s/FxxL8Yg4bRTH4gK

EDIT: Don't get me wrong. I don't blame you and I'm not asking you to stop posting new builds... just reporting an issue :)
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Can you test a kernel build for me? You can contact me on Telegram using the same username as here.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.32 released.

Change log

v1.0.32 (2019-05-27)

Fixed serious bug in v1.0.31 that caused failure of zswap.

Updated to upstream Linux 4.9.179.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.33 released.

Change log

v1.0.33 (2019-05-31)

Updated to upstream Linux 4.9.180.

Updated WireGuard to v0.0.20190531.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.34 released.

Change log

v1.0.34 (2019-06-11)

Updated to upstream Linux 4.9.181.

Updated WireGuard to v0.0.20190601.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.35 released.

This is the 365th day of APGK's existence. The (public) project turns 1 year old tomorrow.

In that time, APGK saw 39 releases whilst in beta and has so far seen a further 36 production releases.

I hope that those of you still using the kernel continue to enjoy its benefits.

Change log

v1.0.35 (2019-06-18)

Updated to upstream Linux 4.9.182.
[Samsung Galaxy S9 & S9+ Cross Device Development] prema108:
Is this kernel suitable for android oreo?
[Samsung Galaxy S9 & S9+ Cross Device Development] QBANIN:
Yes. Oreo only.
[Samsung Galaxy S9 & S9+ Cross Device Development] prema108:
Thank! And one more question. Does this kernel support init.d?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.36 released.

Change log

v1.0.36 (2019-06-22)

Updated to upstream Linux 4.9.183.
[Samsung Galaxy S9 & S9+ Cross Device Development] mustrfafare70@gmail.com:
9:(
[Samsung Galaxy S9 & S9+ Cross Device Development] QBANIN:
1.0.36 broke Super Slow motion recording. Stock camera app freezes for a while then quit when ssm mode is selected. Reverting to 1.0.35 fixes this issue.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Thanks for the report. I will strive to find a solution.
[Samsung Galaxy S9 & S9+ Cross Device Development] j1gga84:
I guess [MENTION=9116297]Eamo5[/MENTION] has fixed it already because his kernel had the same issue ;)

https://xdaforums.com/showpost.php?p=79783938&postcount=675

regards
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
I'm compiling a fix now. Would you test it for me? Or [MENTION=337699]QBANIN[/MENTION]?

Are you on Telegram?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.37 released.

Change log

v1.0.37 (2019-06-24)

Fix for super slow motion recording, which was broken in v1.0.36.

Many thanks to [MENTION=337699]QBANIN[/MENTION] for testing the alpha versions, which was crucial to finding the fix.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.38 released.

Change log

v1.0.38 (2019-06-28)

Updated to upstream Linux 4.9.184.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.39 released.

Change log

v1.0.39 (2019-07-10)

Updated to upstream Linux 4.9.185.

Updated WireGuard to v0.0.20190702.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.40 released.

Change log

v1.0.40 (2019-07-23)

Updated to upstream Linux 4.9.186.
[Samsung Galaxy S9 & S9+ Cross Device Development] bigtom624:
Is this for CSG8
[Samsung Galaxy S9 & S9+ Cross Device Development] EagleSoldier:
No, OREO

csg8 is PIE
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.41 released.

I'm not 100% sure about how I've merged one of the changes in 4.9.187, so please proceed with caution. Please report success/failure after flashing.

Change log

v1.0.41 (2019-08-05)

Updated to upstream Linux 4.9.187.
[Samsung Galaxy S9 & S9+ Cross Device Development] comkioxd:
Is this kernel compatible with Lineage 16.0 for S9?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Can anyone confirm 1.0.41 working? I have 1.0.42 ready for release, but won't go ahead with it until I know that 1.0.41 correctly merged Linux 4.9.187.
[Samsung Galaxy S9 & S9+ Cross Device Development] QBANIN:
Flashed 2 hours ago. So far so good.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Thanks for confirming this.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.42 released.

Change log

v1.0.42 (2019-08-07)

Updated to upstream Linux 4.9.188.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.43 released.

Change log

v1.0.43 (2019-08-12)

Updated to upstream Linux 4.9.189.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.44 released.

Change log

v1.0.44 (2019-08-26)

Updated to upstream Linux 4.9.190.
[Samsung Galaxy S9 & S9+ Cross Device Development] amakuramio:
Does this work on CSGD?

Nvm its oreo
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.45 released.

Change log

v1.0.45 (2019-09-06)

Updated to upstream Linux 4.9.191.

Updated WireGuard to v0.0.20190905.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.46 released.

Change log

v1.0.46 (2019-09-11)

Updated to upstream Linux 4.9.192.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.47 released.

Change log

v1.0.47 (2019-09-16)

Updated to upstream Linux 4.9.193.

Updated WireGuard to v0.0.20190913.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.48 released.

Change log

v1.0.48 (2019-09-21)

Updated to upstream Linux 4.9.194.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.49 released.

Change log

v1.0.49 (2019-10-07)

Updated to upstream Linux 4.9.195.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.50 released.

Change log

v1.0.50 (2019-10-08)

Updated to upstream Linux 4.9.196.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.51 released.

Change log

v1.0.51 (2019-10-18)

Updated to upstream Linux 4.9.197.

Updated WireGuard to v0.0.20191012.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.52 released.

Change log

v1.0.52 (2019-10-31)

Updated to upstream Linux 4.9.198.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.53 released.

Change log

v1.0.53 (2019-11-06)

Updated to upstream Linux 4.9.199.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Final ianmacd version 1.0.54 released.

This 94th release of APGK constitutes the final one with my involvement.

It's been almost a year and a half since APGK first appeared in beta form. A further 38 beta releases would follow before version stable release 1.0.0 finally saw the light of day. Since then, another 54 incremental stable versions have succeeded it.

In the meantime, most of APGK's S9/S9+ user base have either updated their device to Pie or moved to a different device altogether. That includes me as APGK's maintainer. It's been about 8 months since I have had an S9+ on which to test new APGK builds before release, but I kept releasing anyway, due to the demand and loyalty of a small but dedicated group of users.

Limited time on my part and a slowly declining number of users have, however, inevitably led to the point that I must now pass the reins to a new maintainer. I can't stress enough that this need not be the end of APGK. It's merely at the end of its phase of life with me at the helm. Whether that is also APGK's final phase is up to you, dear user. APGK just needs an interested party to take over maintenance from me. That's the power of free software.

Thank you for using APGK and all of your support and kind words over the last year and a half. It's been a great experience maintaining this project for you.

Change log

v1.0.54 (2019-11-11)

Updated to upstream Linux 4.9.200.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Surprise! Version 1.0.55 released.

OK, one more release for good measure, because old habits die hard and Linux 4.9.201 followed 4.9.200 very quickly.

Enjoy.

Change log

v1.0.55 (2019-11-14)

Updated to upstream Linux 4.9.201.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 1.0.56 released.

"Just when I thought I was out, they pull me back in."

It's the boy who cried wolf here with yet another bonus kernel. I had to build another new kernel for the Tab S4, so I thought I may as well downstream the latest Linux for APGK, too.

Again, I envisage that this will be the final release, but you never know.

Change log

v1.0.56 (2019-11-16)

Updated to upstream Linux 4.9.202.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
The recent release of APGK v1.0.56 is, indeed, my last. I have updated the OP to reflect this fact.

Once again, thank you for your support of this project.
[Samsung Galaxy S9 & S9+ Cross Device Development] kgr:
thanks bud. appreciate your work
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.2 released

Version 0.99.2 of APGK has been released.

By popular request, this version adds support for the G960F (S9). Many thanks to [MENTION=7281938]Maxiroe1912[/MENTION] for his enthusiastic assistance in testing kernel builds for this device, as well as the dual installer ZIP.

WireGuard has also been updated to version 0.0.20180620.

With this release, the dual G960F/G965F installer ZIP has become too large for inclusion on XDA. The OP has therefore been updated with an external download link, reproduced here for your convenience.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Custom kernel companion Magisk module released

A companion Magisk module has been released to alleviate the Bluetooth issues that arise when booting a custom kernel on stock (or quasi-stock custom) firmware.

The module contains modified lib_secure_storage.so library files. Rather than have the kernel installer silently place these onto your device, thereby irrevocably modifying its file-system, I have instead prepared this module, which fools the system into using the modified libraries at boot time without making alterations to your device's system partitions.

The module is attached to the OP. Note that it may be used with any custom kernel, not just APGK.

Many thanks to [MENTION=7281938]Maxiroe1912[/MENTION] for testing it on the G960F (S9).
[Samsung Galaxy S9 & S9+ Cross Device Development] Noxxxious:
i.e. systemless mounting by Magisk. Sad thing is that it is still no solution for supersu users.
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
any battery life review?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
My anecdotal evidence suggests that SuperSU users are a tiny percentage of rooted S9/S9+ devices at this point.

The solution for SuperSU users runs to two steps, just one more than for Magisk users:

Migrate to Magisk.

Install the libsecure_storage.so module attached to the OP.

I'm not even being facetious. SuperSU is evidently at the end of its productive life and yielding diminishing returns at this point. Adhering to it is going to become more difficult over time, while the number of reasons to bother labouring over the endeavour continues to shrink. Magisk has its own problems, of course, and it was with reluctance that I recently started to install it on my systems, but it's not dead code, and that is not to be underestimated. Not to mention Magisk's unique features, such as its plug-in module facility.

Anyone determined to cling with white knuckles and screeching fingernails to SuperSU has the option of copying the modified libsecure_storage libraries directly onto the file-system. Yes, that modifies the /system partition, but that's a compromise such users are forcing on themselves.
[Samsung Galaxy S9 & S9+ Cross Device Development] Noxxxious:
You have a very nice way of speech, but that doesn't make anything you say more true. For example it is the /vendor partition that the libs must be put in.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
You seem determined to disagree about something, but it's unclear why.

Yes, the libs end up in /vendor, but the Magisk module installs them to /system/vendor, which is a symlink to /vendor. In any case, any objection to modifying /system apples to /vendor in equal measure. You're still modifying the system, even when not technically modifying /system.
[Samsung Galaxy S9 & S9+ Cross Device Development] Noxxxious:
Yes thats how the module works. When you manually need to put the libs they should be in /vendor/lib and /vendor/lib64. The symlink is just a reference. In conclusion you are truly modifying the vendor partition only and there is no such thing as theoretically X while practically Y.

The determination is caused by the fact that I cannot swallow nonsense that is packaged with a gold wrapper when I read it, e.g. "EAS is a major overhaul, invasive causing instabillities" or 'there are lots of mods not worth the risk such as advanced reboot menu being dangerous because it can cause instabilities'. A lot of politiek talk with no arguments that are truly fact based, just scare tactics or an evasive way of not knowing a lot but wanting to say a lot. But then again I am reminded you have a blog for that.
[Samsung Galaxy S9 & S9+ Cross Device Development] Muntasir Mahmud Saif:
notification light control maybe in future?
[Samsung Galaxy S9 & S9+ Cross Device Development] kgr:
Has anyone reported camera issues since flashing this kernel? I'm on RiCE and had no camera issues til now. Camera app opens but all black (960FD)
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
For someone who doesn't like what I have to say, you certainly spend a lot of time reading and responding to it. I'm flattered. Stay as long as you want.
[Samsung Galaxy S9 & S9+ Cross Device Development] kgr:
What firmware/vendor do I need to be on for this?
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
You can always see this from the thread header. The kernel was built against BRE5, but should also work fine with the update from a few days ago (BRF3, I think). One 960 user I know of is running it on BRF3.

Anything else is untested, which doesn't mean it won't work. If in doubt, make a back-up of your boot partition and try it. If it crashes and burns or you see symptoms that suggest a firmware mismatch, just restore the back-up.

Of course, having a back-up to fall back to is advisable when flashing any new boot image, even one that should theoretically work without issue.
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Version 0.99.3 released.

Updated to upstream Linux 4.9.110.

Updated WireGuard to v0.0.20180625.

Download link in OP.
[Samsung Galaxy S9 & S9+ Cross Device Development] KennyG123:
Thread cleaned

Reminder to keep personal drama off of this private development site

No further personal attacks will be tolerated

Posting on XDA is a privilege of membership #hint

Thank you all for making XDA the greatest development forum with your cooperation
[Samsung Galaxy S9 & S9+ Cross Device Development] emphazer:
your kernel works very well with lightrom and supersu on my s9+

thx for all the lovely details and cherry picks!
[Samsung Galaxy S9 & S9+ Cross Device Development] FdeKlerk:
Hi Dev.

I am unable to boot after i have flashed this kernel.

On BRE5 firmware and vendor and using renovate ice r79 nightly.

After flashing with and without su i get stuck at Samsung logo and there it will stay.
[Samsung Galaxy S9 & S9+ Cross Device Development] emphazer:
any chance to get the base updated to BRF8? its necessary for camera :p
[Samsung Galaxy S9 & S9+ Cross Device Development] Chrispearson172512:
Brf8 source hasn't been released yet so no update until it is
[Samsung Galaxy S9 & S9+ Cross Device Development] ianmacd:
Please grab a logcat with adb after it hangs. That's the only practical way to troubleshoot this.
[Samsung Galaxy S9 & S9+ Cross Device Development] FdeKlerk:
APKG

I think i might have messed up with my setup of rom and so on because i noticed that none of the kernels will boot except Flashkernel v1.1.0.

So will wait for BRF8 source to release and for future update of this kernel and try again.

I want to do clean rom from scratch however i have BRF8 rom downloaded.

Thanks Dev.