yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] Belco02:
The software is nice, thank you by the way, but the system lib lib64 is not supported, the vendor is very missing in the camera section, it would be better if you carry vendor of the S20.
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Why should I do it? Most of s20 hw blobs won't work on our device
[Samsung Galaxy S9 & S9+ Cross Device Development] gezginimben:
Hello sir.

Versiyon 3.7.1 Errors;

1-) Bluetooth pairing problem

2-) Twrp full backup problem

3-) Blue light filter sometimes turns off by itself

Have these bugs been fixed in version 3.8?

Thanks.
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Not related to vendor mate
[Samsung Galaxy S9 & S9+ Cross Device Development] Nobody2050:
Hi there,

Where can I find the APPS_REMOVER.zip?

I don't see a link for download.

View attachment 6024356

Greetz Nobody2050
[Samsung Galaxy S9 & S9+ Cross Device Development] gezginimben:
Is there a solution? Thanx
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
oneui 6 apps link
[Samsung Galaxy S9 & S9+ Cross Device Development] Mr. A:
Hey thanks for the amazing ROM. Stupid question but how do I know if I installed one UI 6 or 5.1? I had to install and reinstall it many times while flashing 7.1 and I forgot if I used one UI 6 or just 5.1. Thanks. I'll flash it soon.
[Samsung Galaxy S9 & S9+ Cross Device Development] Atanassoww:
Only 5.1 is available.
[Samsung Galaxy S9 & S9+ Cross Device Development] Mr. A:
Thank you. I meant UI 5.1 or 6 apps. Cause the installation methods is different so. I'm sorry I should have cleared properly.
[Samsung Galaxy S9 & S9+ Cross Device Development] thongfybd:
Hello. Unlucky for me. I installed it cleanly and the device started up fine, fully installed call fix, the interface is very nice but there is an error of no phone signal in this rom. Can you tell me where the error is? Thank.
[Samsung Galaxy S9 & S9+ Cross Device Development] huanngo3011:
Check your imei then google to restore
[Samsung Galaxy S9 & S9+ Cross Device Development] Mr. A:
Is anyone facing random reboots and overheating and app crashes? I dirty flashed 3.8 over 3.7. I'm having random reboots and while rebooting the phone heats too much. I can literally feel it in my pockets heating up. I was having this issue on 3.7 as well. Do I have to clean install again? Also some heavy apps & games crashes and reboots the device. Am I the only one?
[Samsung Galaxy S9 & S9+ Cross Device Development] huanngo3011:
Clean flash again.
[Samsung Galaxy S9 & S9+ Cross Device Development] erpl:
Is there any way to get Google Wallet or my banking app to use NFC payments? I didn't choose to root it but even though it doesn't work, Help?
[Samsung Galaxy S9 & S9+ Cross Device Development] gros_rouge:
Hello, I have installed version 3.8. Clean installation. I have experienced crashes for the banking app and other apps that don't work with root. I thought I had configured Magisk as usual: app hiding, Zygisk enabled, exclusion list enabled, banking/government apps and others checked in this list. But maybe not. Maybe I've turned on the deny list, witch is not recommended nowadays.

I have uninstall Magisk and reinstall it from zero:

Download Magisk.v26.3.apk from https://github.com/topjohnwu/Magisk/

Rename the file as Magisk.v26.3.zip

Install it thru TWRP (reboot in recovery mode)

Reboot system

Open Magisk app and finish installation - the app will guide you.

Reboot

Install module Shamiko: https://github.com/LSPosed/LSPosed.github.io/releases

Install module Safetynet_fix: https://github.com/Displax/safetynet-fix

Enable Zygisk

Reboot

Configure deny list with your banking apps and other stuff that do not support rooting devices and turn on denylist enforcement.

Hide Magisk app and add shortcut on screen.
[Samsung Galaxy S9 & S9+ Cross Device Development] gleurp:
Hello,

First, thank you very much for this amazing ROM !

I installed SILA 3.8 (clean installation) and i choose Magisk ... BUT several applications cannot be installed because the smartphone is rooted. So is it possible to switch to NO-ROOT ... or do I have to reinstall everything !?!
[Samsung Galaxy S9 & S9+ Cross Device Development] gros_rouge:
Hello, just follow my post above yours. Follow point 5 to last. It shall work.

This ROM, even without Magisk, will not run apps that need non root devices.
[Samsung Galaxy S9 & S9+ Cross Device Development] erpl:
Are there option to lock the bootloader with this rom so my bank app could work?
[Samsung Galaxy S9 & S9+ Cross Device Development] giuseppe f:
salve, ho la 3.7.1 e funziona tutto, walket bank e google hanno certificato il dispositivo per me. C’è una procedura da fare ed è un po’ complessa
[Samsung Galaxy S9 & S9+ Cross Device Development] umbi9888:
Dirty flash from NOBLE 3.6 to 3.8: Is it possible?
[Samsung Galaxy S9 & S9+ Cross Device Development] Mutaal._:
Yes but u will have to follow dirty flash instructions mentioned in the post 👍
[Samsung Galaxy S9 & S9+ Cross Device Development] LeapingLamb:
Edit wrong thread
[Samsung Galaxy S9 & S9+ Cross Device Development] U.D.O.M:
Hi All! Instal 3.8 over 5 times by instruction... app in denilist allways crushed.... 3.7.1 work good. Enybody know what problem it can be?
[Samsung Galaxy S9 & S9+ Cross Device Development] gleurp:
Hello, Merci beaucoup for your reply BUT I follow your point 5 to last ... and now all the apps in the deny list freeze when they start :-(
[Samsung Galaxy S9 & S9+ Cross Device Development] gros_rouge:
I finally have the same problem. I tried to install several times, it never works with Magisk installed on Noble ROM. And it works one over three when perfoming desinstall and reinstall ... I don't know why. I thing, there is a bug here.

I haven't access to the Telegram group of this ROM. Maybe, it's an indentified bug and there a patch or somethings to do ...
[Samsung Galaxy S9 & S9+ Cross Device Development] gleurp:
OK , so we just have to wait ROM 3.8.1 ! ;-)
[Samsung Galaxy S9 & S9+ Cross Device Development] Razorblade1777:
After installing this rom, everytime i connect any bluetooth device and restart the phone, all the bluetooth devices get removed. I use a galaxy watch and pairing it everyday is really tough. If anyone has a solution please let me know. This also happened with 3.7, and in 3.6, but after a couple restarts, it fixed 3.6 @AlexisXDA
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Just flash Bluetooth Library Patcher again
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
I think could be an issue with newer Magisk and newer security patches, using provided magisk version shouldn't cause any issue
[Samsung Galaxy S9 & S9+ Cross Device Development] yigitqweqew:
One ui 6 please
[Samsung Galaxy S9 & S9+ Cross Device Development] Razorblade1777:
Hello, where can i find this bluetooth patcher file? I also have not rooted the phone, as i am not that advanced at roms. @AlexisXDA
[Samsung Galaxy S9 & S9+ Cross Device Development] huanngo3011:
Release v2.6.5 · 3arthur6/BluetoothLibraryPatcher

Add KernelSU support Fix some issues

github.com
[Samsung Galaxy S9 & S9+ Cross Device Development] equatorius:
Does anybody know how to enable GALILEO L1 tracking? (I know L5/E5(a) will probably never work with this chipset.)

It always bothered me that I can't see anything else beyond GPS and GLONASS (much less satellites pop up for the latter) because the Exynos variants should support: "GPS, Galileo, Glonass, BeiDou (*Galileo and BeiDou coverage may be limited. BeiDou may not be available for certain countries.)."

I know that GALILEO usage is (or at least was for some years) not permitted by the FCC in the US (I read people reporting seeing GALILEO satellites on their S9 in the EU but not in the US while traveling). But I am in the EU (Hungary), so it should have been working since the beginning. But it still isn't (not even with this custom OS). I bought this phone on the second-hand market, so it's possible it wasn't originally meant to be sold in Hungary or even anywhere inside Europe. But as far as I know, only the US FCC regulations blocked GALILEO and only while inside the US. And Samsung used a Snapdragon chipset for the US market, so this clearly Exinos-based S9 of mine most probably wasn't meant for the US market. That rules out a hardware-fused / deep GNSS-firmware-level GALILEO blacklisting based on FCC regulations and I am not aware of any other similar legislation issues regarding GALILEO. I used to have a Xiaomi Mi8 for a few months (until I dropped and broke it) and that picked up L1 / L5/E5a for various GNSS constellations (at least 3 if not 4 by memory) with the original MIUI OS.

I opened the /vendor/etc/GNSS/GPS.xlm file. I found lines like EnableBeidu="True" and EnableGalileo="True". So what else could be at play here?

View attachment 6028951

I only remembered this now because I plan to try doing a long-term RAW GNSS logging with my phone to augment the position of my GPS antenna that is meant for time synchronization only (I bought a very old, GPS.L1-only timing module that can't reach <10m accuracy on its own but has a presumably accurate PPS over RS-232 --- however, the clock signal would be presumably more accurate with fixed relieable coordinates saved to its flash and the received put into "timing mode"). So I decided to look into the GNSS capabilities of my phone yet again after a few years (in the hope somebody might came up with a hack to unlock L5/E5a as well).
[Samsung Galaxy S9 & S9+ Cross Device Development] equatorius:
Whops... I just noticed this after I tried to use GNSSLogger (from Google): The GPS time is 2004 March 20. That's obviously incorrect. According to the information here: https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html#TIME-INTRO

Seeing 2004 in 2023 implies that the GNSS system on my S9 thinks it's still in the 1999-2019 epoch (when the chip was manufactured). I have never seen this issue before on any device. I think a well-connected device like a smartphone should easily devise the correct GPS time epoch. The auto system time (fetched from either the mobile network or the internet by the Android system) is correct down to the second. This error makes me unable to feed the GNSS logs into external software for analysis (since those try to download ephemeris and ionospheric data from a NASA server that matches the logged GPS dates and I really don't want to figure out how to manually offset all the numbers in the long file with nanosec accuracy -> I couldn't find the rollover date down to that precision).

Does anybody else see this issue on their devices?

I guess this could be an issue with this custom OS/firmware because the stock S9 OS was made for a device manufactured during the previous GPS epoch (so it needs a different starting date to calculate UTC time from GPS time) while the S20 was made during the current one.
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Gps drivers are from stock s9, that could explain all
[Samsung Galaxy S9 & S9+ Cross Device Development] phanson154:
AlexisXDA I'm using Rom Noble 2.8 on Note 9. If I want to upgrade to Noble 3.8 SiLa, where should I start investing? Thank you very much.​
[Samsung Galaxy S9 & S9+ Cross Device Development] Marvfit213:
Hi I have a question

If i only replace from Ivan Rom one ui 5.1 s10+ the System.img of One ui 5.1 with the one ui 6.0 one from s23 u BWJM

And leave the rest like it is same kernel engorcing

Wold it boot into one ui 6 or would bootloop ?

Could I try one ui 6 then ?
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Bootloop, other changes are needed to boot A14 afaik
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Read in first page 'Clean Install' instructions

You need repartition, then you can move to 3.8 and also you will able to come back to 2.8 if you are not satisfied
[Samsung Galaxy S9 & S9+ Cross Device Development] giuseppe f:
I read that Samsung S 20 will not be updated to Android 14 UI 6. So there will be no update to UI 6???
[Samsung Galaxy S9 & S9+ Cross Device Development] Dissocioo:
Hello Sir, i got a problem. Had previously installed 3.8 SILA with the partitioning scripts, by instruction, now i want to switch to pixel experience, i do:

Format system, dalvik, cache

Flash pixel expirience from TWRP

after installation i get bootloop, is something related to re-partition? What should i do to be able to install other roms after this "SILA"?)

Thanks in advance. In bocca al lupo😊
[Samsung Galaxy S9 & S9+ Cross Device Development] Dissocioo:
Hello Sir, i got some problem, help me please.

Well ive installed Noble 3.8 SILA with repartitioning scripts, by instructions, everything was fine untill i wanted to switch to pixel experience, now, i did:

Format system, dalvik, cache

Flash pixel experience

Everything done in the latest TWRP, CORRECTLY (i mean ive choosed the right rom wich earlier was going just fine.)BUT

After flashing pixel experience i have just an boot loop. Is the issue related to repartition? Help me swith to other roms as earlier pls
[Samsung Galaxy S9 & S9+ Cross Device Development] Dissocioo:
Sorry for double posting. Its my networks fault.
[Samsung Galaxy S9 & S9+ Cross Device Development] huanngo3011:
Pe is installed by pE recovery mate
[Samsung Galaxy S9 & S9+ Cross Device Development] Marvfit213:
Yes thats right but Any time soon or later beginnt next year someone will Port it I saw someone alredy did for S20 FE so not that long
[Samsung Galaxy S9 & S9+ Cross Device Development] giuseppe f:
how do I update
[Samsung Galaxy S9 & S9+ Cross Device Development] erpl:
Is there banking app support or no?
[Samsung Galaxy S9 & S9+ Cross Device Development] brhoomy101:
(NOBLE 3.8) ,Best ROM Thank you 🤝
[Samsung Galaxy S9 & S9+ Cross Device Development] joyeonu:
https://sourceforge.net/projects/my...8BXXU3BWJM-AB-20231030-MysticGSI.zip/download 다음은 oneui6.0gsi입니다. 이것을 부팅 할 방법이 있습니까?
[Samsung Galaxy S9 & S9+ Cross Device Development] Ea4116:
I did a clean installation of Noble ROM 3.8, but I cannot access the accessibility section from the settings and the device runs slower than Noble ROM 3.6. There are delays and there is a lot of RAM usage. Can you help me fix these?
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Yes, just make sure to pass safetynet
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Install again and make sure to NOT select Accessibility in AROMA if you pressed Advanced Debloat
[Samsung Galaxy S9 & S9+ Cross Device Development] Ea4116:
Thank you by Alexis There is no problem in the accessibility section, the delays still persist even though I have installed it 5 times. Isn't there a kernel update?
[Samsung Galaxy S9 & S9+ Cross Device Development] Frgvid:
Hi Alex,

can you port this noble rom to galax note 8 (greatlte)?

I've installed on my Galaxy S9 (starlte) and works smoothly.

would you ported this rom to Galaxy Note 8?

Thanks.
[Samsung Galaxy S9 & S9+ Cross Device Development] Nobody2050:
Hi,

As mentioned here on page 62.

[NOBLE ROM 4.2 CALABRIA III OneUI 6.1 FULL PORT][06/24 Patches][16/06/2024][SM-N960F/FD/N--SM-G96xF/FD/N]

Disclaimer We are not responsable of any problems caused by root like tripped knox... When you flash something like this you may know about the risks you are going to find in! Always backup your phone before and after flashing TWRP custom...

xdaforums.com

https://www.apkmirror.com/apk/googl...components-2023-08-01-s-android-apk-download/

Good luck.

Greetz Nobody
[Samsung Galaxy S9 & S9+ Cross Device Development] s9+user:
can i put a custom kernel on this rom ?
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
We already use a custom kernel
[Samsung Galaxy S9 & S9+ Cross Device Development] wtosta:
Hello AlexisXDA.

Probably GoodLock modules are broken in Noble ROM 1.3, when you are in a country, where GoodLock is not allowed to work. However GoodLock shows all modules, but all of them are for download which of course cannot be proceeded.

Best regards,

Witek
[Samsung Galaxy S9 & S9+ Cross Device Development] effry:
They are working. The good lock app that comes with the rom is patched and you should be able to downlaod the apks. Otherwise download the mfrom apkmirror and launch them with this https://play.google.com/store/apps/details?id=com.bluehorizonapps.nicelock3&hl=it&gl=US
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Just because of this? ahahah

They are removed from this ROM but they are stored in ODM partition which is not touched by this ROM since CSC stuffs got moved in system, that's why you get them installed

Clean your ODM partition and reinstall the Noble ROM

Also if I made a really hard debloat why should I keep those apks in the ROM?
[Samsung Galaxy S9 & S9+ Cross Device Development] wtosta:
They are working indeed. I didn't have web browser installed therefore every try of Good Lock module installation ended up with an error and application termination. False alarm, my mistake.
[Samsung Galaxy S9 & S9+ Cross Device Development] erickchakilo:
hello good thanks for the rom is very good I only have a few small problems, the fingerprints do not work in the applications and neither does the samsung pass, and some bank applications continue to recognize that the phone is root and I cannot use it
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Samsung pass won't ever work on rooted device. Instead use Google Autofill

For bank apps and fingerprints the problem is safetynet and Magisk

Enable magisk hide and hide every bank apps + google play services

Then rename magisk app as well

Clear data and cache of any bank app and reboot

If you don't know how magisk works, there are a lot of guides around google
[Samsung Galaxy S9 & S9+ Cross Device Development] Reag:
Oh i see. I honestly didn't know this was stored in the ODM partition. Thanks for letting me know
[Samsung Galaxy S9 & S9+ Cross Device Development] Ur_strom:
Hey,

I've flashed the rom to my wifes S9 according to the manual.

First of all: great work, its runs super smooth and without bigger problems yet.

But i may have two minor bugs: the always on display always shows the phone is charging, even when running on battery.

Second: the power button works only partially, pressing it once turns the display of like it's supposed to. But holding it doesn't come up with the power menu.
[Samsung Galaxy S9 & S9+ Cross Device Development] huismeester:
You must read AOD is fix but you must the app not update go back in optioneel apps and set is back to old setting
[Samsung Galaxy S9 & S9+ Cross Device Development] huismeester:
You can choose not to install and after flashing the rom install in the galaxy store separate
[Samsung Galaxy S9 & S9+ Cross Device Development] PcO7:
When coming from an other Android11 custom rom, do i have to update modem+bootloader?

And in the flashing instructions there is only advanced wipe (system, data, cache, dalvik + vendor) mentioned. So no need to format data? (Because this is also mentioned in this thread - confusing)
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
"Format data" is needed when you install for the first time the TWRP

And if you are on latest Modem and BL you are fine
[Samsung Galaxy S9 & S9+ Cross Device Development] PcO7:
so 'first time' does not mean when updating or downgrading twrp? (because i have to downgrade twrp to 3.3.1.1.)

i've now downloaded the latest fw via 'samsung firmware downloader tool'. can i use these files 'cp' and 'bl' with odin? (because in the last download step the tool said something of decrypting)

otherwise can someone give me link for the correct modem + bootloader?

thanks a lot :)
[Samsung Galaxy S9 & S9+ Cross Device Development] zombie149:
Unfortunately, the heart rate sensor does not work
[Samsung Galaxy S9 & S9+ Cross Device Development] huismeester:
If you want everything to work, buy an S21
[Samsung Galaxy S9 & S9+ Cross Device Development] zombie149:
What for? Works on stock.

Now I'll check on Alexis Rom 2.7.1
[Samsung Galaxy S9 & S9+ Cross Device Development] caiejay:
i tried dirty flashing the new update but it seems that it won't work for me.
[Samsung Galaxy S9 & S9+ Cross Device Development] caiejay:
ok so tried fully wiping and clean install but i keep getting stuck on bootloop
[Samsung Galaxy S9 & S9+ Cross Device Development] Vgyid55:
I want to ask why on s9 + and N9 there is bixby and on S9 there is no?
[Samsung Galaxy S9 & S9+ Cross Device Development] s9+user:
Ok but if i want to put another one then can i without breaking the rom ?
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
Depends if the kernel supports newer oneui ports
[Samsung Galaxy S9 & S9+ Cross Device Development] Dragan2221:
will there be one ui 6.0 for s9 or has the end come for s9?
[Samsung Galaxy S9 & S9+ Cross Device Development] erpl:
patience is the key
[Samsung Galaxy S9 & S9+ Cross Device Development] Pekly:
Dude seems like This Is Last Breath Of Noble Rom, s20 and n10+ has not getting One UI 6.0 But I found some dudes ported One UI 6.0 to N10+ here's the link: https://drive.google.com/drive/u/0/mobile/folders/1CwR23DcPkzc-kdE1zjxHlgJADSunUcKO?usp=drive_link
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
More than N10 and S20, N10L isn't getting OneUI 6 which had same soc as our S9/N9. We will see what we can do, but I'm scared it will be harder and even if we boot it we will get serious issues
[Samsung Galaxy S9 & S9+ Cross Device Development] U.D.O.M:
Mr.Alexis what about threads #5, #6?
[Samsung Galaxy S9 & S9+ Cross Device Development] lonelytransistor:
Is there a proper source code for the kernel included? I call bs on the link provided, it doesn't even have the proper config nor is it maintained for ages.

I need to recompile it to fix burn-in on my screen, since I found a way to do it. Please help, provide a proper link.
[Samsung Galaxy S9 & S9+ Cross Device Development] Imotep95:
You can't fix burn in. You can fix image retention, but it's most likely burn in on amoled.
[Samsung Galaxy S9 & S9+ Cross Device Development] cmoinanar630:
hello AlexisXDA I wrote to you on your insta but no news, about noble 3.8 which works well but which does not have an official Samsung rom, I found the same official Samsung rom and I want to know what it is difference with noble 3.8 cila ??
[Samsung Galaxy S9 & S9+ Cross Device Development] huanngo3011:
Offical 5.1 samsung rom for 9 series ?
[Samsung Galaxy S9 & S9+ Cross Device Development] Belco02:
View attachment 6036518
[Samsung Galaxy S9 & S9+ Cross Device Development] AlexisXDA:
View attachment 6036545

Spoiler content hidden.

View attachment 6036546

Updated base to OneUI 5.1 S20 firm with November's security patches (HWJD)

Fixed spen translate feature

Updated Magisk and added new Play Integrity fix

Updated kernel with minor changes

Minor changes and improvements

*FLASH APPS REMOVER BEFORE FLASHING 3.8 IF YOU WERE USING ONEUI 6 APPS!

View attachment 6036548

In order to prevent TWRP crash that make Magisk not installable, use this TWRP Patched: https://xdaforums.com/attachments/patch_twrp_xxtr-zip.5809969/

If you notice the "failed to mount /omr" and "failed to mount /preload" they are common and not a real issue. You can easily solve this by wiping OMR and Preload in Wipe/Advanced Wipe menu

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

View attachment 6036549

BUGS LIST NOBLE ROM

Foglio1 ALL VARIANTS,WORKAROUND,PRIORITY (1=High, 2= Medium, 3= Low),LEGEND v4.2 CALABRIA III - ONEUI 6.1,RED - Will Not Be Fixed GENERAL,YELLOW - High Probability That it Gets Fixed IRIS Scanner,3,GREEN - Fixed! Wait Next Update Face Unlock,1,MANUAL FIX- Follow Instructions HDMI audio output,3 ...

docs.google.com

View attachment 6036550

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

View attachment 6036552

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.
[Samsung Galaxy S9 & S9+ Cross Device Development] cmoinanar630:
yes for my galaxy basic version N960FXXU9FVG2

then sila G980FXXSIHWI7 like the official Samsung version, tell me the difference

THANKS