[NOBLE ROM 3.2 PIZZO OneUI 5.1 FULL PORT][03/23 Patches][14/03/2023][SM-N960F/FD/N--SM-G96xF/FD/N]

[innocent_pigeon]

Hi, I hope that someone else has tried to get this done and was successful unlike me. I tried to NFC working with support for extended length. Some apps from the government in Germany make use of this.

@innocent_pigeon mentioned earlier in this thread that he got it working by taking all files from the official s10 rom (I use this ROM on an S9), copying them over to his device. I tried the same: looking for any file in system.img (were like a dozen files) that had "nfc" in its filename or foldername and copied it to my phone (using file manager in TWRP).

Was someone else successful? Maybe I just miss a single file that is not clearly related to NFC?

Thanks in advance

Hi together

First of all, big thank you and respect to @AlexisXDA!
I'm a loyal user since Version 1.7 or 1.8 and no matter what Smartphone or ROM I try, after max three days I'm back with Noble!

In three weeks I'm 4 years with my Note9 and I even bought it used!
Thanks to you is my noble-device still very up-to-date and except of the battery and a dying the dying USB-C-connectors have no complaints! @AlexisXDA: xda's Oeco-warrior

Sadly I couldn't reproduce my solution from last year. BUT I found another workaround and wanted to share:
@elfrawg it's not just one file.....just a SINGLE NUMBER you have to change to get it to work (supposedly there's even a workaround for non-root)!

Navigate to /vendor/etc/libnfc-sec-vendor.conf
Scroll down to the end, where you should see the entry for the extended length.
Rise it over 500, save, reboot and it worked on my phone as well as from @elfrawg's

In my config-file stood the default length 261. Theoretically one has just replace the 2 with 5 and done.
It is so easy, I still suspect a catch or whatever....



Here the original entry, where I found it:

Samsung A5 + NFC + extended Length

Mein Samsung Galaxy A5 konnte früher mit NFC den Personalausweis auslesen: - es funktionierte mit Android 8, - es funktionierte mit LineageOS 16, - es funktionierte mit LineageOS 17.1 bis einschl. Ver

www.lineage-os-forum.de

Have a good start in the week

 

[longkaka23]

NOBLE ROM 3.0 TROPEA IS ONLINE!
REPARTITION needed! Dirty flash from 3.0 BETA is allowed. If you have problems just CLEAN INSTALL

Since this build I decided to add a codename to every major build (3.x). The codename comes from places from my Region in order to promote its wonderful beauties!
Announcement REEL here: https://www.instagram.com/reel/CoSNN4jg-Wj/?igshid=YmMyMTA2M2Y=

CHANGELOG:
Added fix for 2nd Audio on Whatsapp
Added fix for keyboard lagging
Added fix for camera night mode
Added Secure Private Share
Added Outdoor Mode in Settings
Added Fingerprint Gesture Option
Added back Night Mode toggle
Added 130+ CSC to choose and fixed csc tweaks not applied
Added Bixby Button Remapper option in aroma
Added new kernel menu in aroma
Added S23 Wallpapers
Added DeX Mode to use directly on phone's display
Added Translation and Bixby Vision options for SPen
Added OneUI 5.1 Launcher
Added OneUI 5.1 Weather App
Added OneUI 5.1 Keyboard
Fixed weird animations (thanks to duhan)
Fixed Edge Lighting corners
Fixed HDMI connection (audio issue still persists)
Improved dolby sound quality
Improved general stability and performance


HOW TO INSTALL:
Follow these steps carefully!

In order to prevent TWRP crash that make Magisk not installable, use this TWRP Patched: https://forum.xda-developers.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

TWRP 3.7.0_9-0
0. Make a Backup of EFS and of all your stuffs before proceeding
1. Open TWRP by pressing volume up+ bixby + power buttons
2. Press on "Install" and select Universal9810_Repartitioner https://forum.xda-developers.com/attachments/universal9810_repartitioner-zip.5816841/
3. Reboot to TWRP
4. Press on "Wipe" and select "Format Data" then type "yes"
5. Reboot again to TWRP
6. Press on "Install" and select Universal9810_Cleaner https://forum.xda-developers.com/attachments/universal9810_cleaner-zip.5809289/
7. Reboot again to TWRP
8. Press "Install" and select NOBLEROM zip
9. Follow AROMA instruction and at the end of installation, reboot
10. Enjoy Noble ROM

BUG LIST:
Check this to know which bugs are currently on NOBLE ROM. This list will be constantly updated once we find new bugs or we fix new stuffs.

BUGS LIST NOBLE ROM

Foglio1 ALL VARIANTS,WORKAROUND,PRIORITY (1=High, 2= Medium, 3= Low),LEGEND v3.1 VIBO ONEUI 5.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 OK Google Voice Command,Don't ...

docs.google.com

6 THINGS TO KNOW ABOUT NOBLE ROM 3.0
- It's based on S20 and N10 Lite OneUI 5.0 bases
- It's a unique zip for all variants
- Will be released as BETA because:
- Front camera issue and HDR Force Close are back
- Face unlock doesn't work
- Since space needed has increased now it needs REPARTITION
- Repartition method it's very easy, it has to be done just once and it will erase all your datas
- Repartition allows you to go back to any ROM, so it's not useful just for Noble ROM 3.0

DOWNLOAD LINKS:
NOBLE ROM 3.0 TROPEA:
OneDrive MIRROR: https://1drv.ms/u/s!AqGdTk4hyeaFiLF_mrzAgBzdRpbDSQ?e=WqMJ58
MEGA: https://mega.nz/file/eNhmTZpI#ZzbKeSuvuS0snO_L8GYobnSaQsjkxyFvdq6QHZVXFoo
MEDIAFIRE: https://www.mediafire.com/file/lct3jwjw940hwev/NOBLEROM3.0_TROPEA.zip/file
Google Drive MIRROR: https://drive.google.com/file/d/15Iuc8TWx_fz0RVmqLyE9yM5GIDTj9dwm/view?usp=share_link

VIDEO TUTORIAL ON HOW TO ENABLE RAM PLUS ON NOBLE 2.0+ IS HERE:

TELEGRAM GROUP:

S9-S9+ and Note9 Noble ROM

⚠️⚠️RULES⚠️⚠️ 1- Only Noble ROM support. 2- Only English allowed 3- Don't talk about other Roms 4- Don't go off topic 5- Don't ask for ETA 6- Respect other members

t.me

TELEGRAM CHANNEL:

Noble ROM Channel

Updates' Notifications, Bugs Fixes, Informations, Comunications and ALL YOU NEED for the best Noble ROM's experience!

t.me

FOLLOW ME ON MY INSTAGRAM's PROFILE: https://www.instagram.com/invites/contact/?i=wehmn6h8vftx&utm_content=ibotzda

Follow me on Twitter:

https://twitter.com/AlexisDevXDA?s=09

I successfully booted the Rom. In my pov, the Rom is great, but there are some small issues like delay app setting when open App info from recent or home screen/app screen and front Ar doodle does not regconize face and it asks for AR Core or something I don't know, but I am not able to install it on my device.

 

[longkaka23]

Does anyone use Samsung Quick Share and encountered issues? When I use it, it can receive files, but cannot send files.

The same for me, I tested it. On another device, it shows my phone and can send files, but my phone does not display other devices even the device I use to send files.

 

[cuatuinha]

I successfully booted the Rom. In my pov, the Rom is great, but there are some small issues like delay app setting when open App info from recent or home screen/app screen and front Ar doodle does not regconize face and it asks for AR Core or something I don't know, but I am not able to install it on my device.

I thought only I had a delay issue. I was about to perform a fresh install once more, but perhaps there is a problem now.

 

[zeroomhert]

The same for me, I tested it. On another device, it shows my phone and can send files, but my phone does not display other devices even the device I use to send files.

Noble 3.0 is still in Beta version. Hope @AlexisXDA will have a fix on it soon. I am always using that Quick Share thing since in my workplace it requires transfer of important files from my phone to our company phone and vice versa. But Samsung Workflow works well without issues. Only the Samsung Quick Share that can receive files but cannot send files.

 

[remmie$$]

hello guys, how can I overcome the symlinks failed error? I have installed the TWRP patch and the repartitioning tool as well. the first beta version booted before but now it also fails some symlinks. if I choose the no root option, it flashes successfully but gets stuck on a boot loop. I had the 3.0 beta installed before flashing the Tropea version. Device: crownlte

 

[Wengxams]

Hi Alex. Since installing Noble rom in my s9+, Ive had charging connected device via Usb notification. How do i fix it? I have clean install

Someone help

 

[AlexisXDA]

I verified it in the installation file, but the Google services for augmented reality are missing. I believe that is why I attempted to reflash, but it was unsuccessful. Manually installing was unsuccessful as well; perhaps there is a problem with the Arcore library and API that prevents the app from working. Would you mind creating a patch for Arcore's installation only?

It is in odm path

 

[thanhLong25]

It is in odm path

I apologize if it came across a little muddled. The Samsung AR apps are still available, but you might not have added the AR service, which I'm sure is in the system path. As you can see in the picture. Although Play Store forbids me from doing so, I'm not sure if it works if we can install it on the Play Store.

 

[thanhLong25]

I apologize if it came across a little muddled. The Samsung AR apps are still available, but you might not have added the AR service, which I'm sure is in the system path. As you can see in the picture. Although Play Store forbids me from doing so, I'm not sure if it works if we can install it on the Play Store.

I also looked at the firmware. You may have forgotten to put it in, or you may have accidentally debloated it. Would you mind double-checking it?

 

[AlexisXDA]

I also looked at the firmware. You may have forgotten to put it in, or you may have accidentally debloated it. Would you mind double-checking it?

I will check but what happens if you install manually from apkmirror for example?

 

[zeroomhert]

hello guys, how can I overcome the symlinks failed error? I have installed the TWRP patch and the repartitioning tool as well. the first beta version booted before but now it also fails some symlinks. if I choose the no root option, it flashes successfully but gets stuck on a boot loop. I had the 3.0 beta installed before flashing the Tropea version. Device: crownlte

Try to use the TWRP you used when you install the first 3.0 Beta and just manually root the phone. Maybe the patched TWRP is for S9 or S9+ that's why it won't work.

 

[OffsetPikachu55]

Everything flashes ok until root, it just restarts recovery. I tried flashing magisk canary and got Unsupported/Unknown image format, it then ended with error 1.
SM-G960F

 

[thanhLong25]

I will check but what happens if you install manually from apkmirror for example?

AR apps freeze, and sometimes they crash. Upon activation of the AR emoji camera and initiation of play, the display of the AR icon was immediately followed by a blackout and a switch back to the front camera (mask). An attempt to utilize the AR function through the AR playground on Google search resulted in another crash and disappearance of the play button. It is worth noting that while the application can be installed, it fails to function properly, and its status as an installed app is not reflected in the Google Play Store.

 

[thanhLong25]

I will check but what happens if you install manually from apkmirror for example?

I extend my sincerest gratitude for your prompt attention to this matter. I eagerly anticipate your examination and hopeful resolution of the issue at hand.

 

[OffsetPikachu55]

Everything flashes ok until root, it just restarts recovery. I tried flashing magisk canary and got Unsupported/Unknown image format, it then ended with error 1.
SM-G960F

Turns out the rom may have corrupted itself while sleeping, I selected clean flash and it didnt wipe anything off my phone.

 

[AlexisXDA]

I extend my sincerest gratitude for your prompt attention to this matter. I eagerly anticipate your examination and hopeful resolution of the issue at hand.

was it working in beta version?

 

[thanhLong25]

was it working in beta version?

No. I regret to inform you that I installed the beta version approximately 5 to 6 hours prior to your upload. Despite encountering errors, I attempted to resolve the issue through a clean flash and re-flash of this Rom's version, however it did not resolve the situation. As a result, I am reaching out to seek assistance.

 

[AlexisXDA]

No. I regret to inform you that I installed the beta version approximately 5 to 6 hours prior to your upload. Despite encountering errors, I attempted to resolve the issue through a clean flash and re-flash of this Rom's version, however it did not resolve the situation. As a result, I am reaching out to seek assistance.

Mmmh ok. Because just the "Games" section of AR is not working. The other function like AR Emoji are working fine

 

[thanhLong25]

Mmmh ok. Because just the "Games" section of AR is not working. The other function like AR Emoji are working fine

That's correct. But in addition to that "games" component of the AR emoji as well as AR Doodle, this issue also ruins the AR experiences of other AR apps available on the Play Store. For that reason, I always expect a fix to be available in the future.