Yeah, I totally get it! Fingers crossed 🤞-since Noble ROM gets updates so frequently, this might get fixed in the future too. After all, Alexis, the developer, has been doing an amazing job with the ROM! Make sure to subscribe to the channel-I’ll give an update and a detailed video as soon as it’s fixed!
It makes me wanna buy a note 9 and do the same. I really love the hardware, but the software was outdated and was the only deal breaker for me. Now, it can be a great secondary phone.
That’s an awesome idea! The Note 9 hardware is still top-notch, and custom ROMs really bring it back to life. Glad you’re considering it as a secondary phone! 😊 More content on the Note 9 is on the way, so make sure you’re subscribed to stay updated!
Hey, if your phone is stuck on “Emergency Calls Only” after installing Noble ROM 6.1.1, try the following fixes: 1. Restart the Phone: Sometimes, a simple restart can fix network issues. 2. Check SIM Card: Ensure the SIM card is properly inserted. Remove and reinsert it to be sure. 3. Toggle Airplane Mode: Turn on Airplane Mode for 10-15 seconds, then turn it off to reset your network connection. 4. Network Settings Reset: Go to Settings > System > Reset Options and choose “Reset Wi-Fi, mobile & Bluetooth.” 5. Manual Network Selection: Go to Settings > Mobile Networks > Network Operators and select your carrier manually. 6. Reflash the ROM: If the issue persists, consider reflashing the ROM using a clean flash, making sure to wipe data/cache before reinstallation. 7. Check for ROM Updates: Sometimes, bugs are fixed in newer builds. Check for OTA updates in Settings > System > Updates. 8. Check Baseband Version: Go to Settings > About Phone > Baseband and ensure it’s correct. If all else fails, you may need to contact the ROM developer or try a different version. Let me know if this helps!
@techtuned025 i have patched imei, thats why i guess i am facing the problem, Do you have any fix for that? I have already checked like everything, did every steps here. But all in vain.
If your Galaxy Note 9’s power button is not working, you can try these alternative methods to boot into TWRP: 1. ADB Command (Requires a PC) • Make sure USB Debugging is enabled on your phone. • Connect your phone to a PC with ADB installed. • Open a command prompt or terminal on your PC and type: adb reboot recovery • This will boot your device into TWRP. 2. Using a Magisk Module (If Rooted) • Install the “Recovery Reboot” module via the Magisk app. • Reboot directly into TWRP using the module. 3. Third-Party Apps (If Rooted) • Download apps like Reboot Manager or Quick Reboot from the Google Play Store. • Use these apps to reboot into recovery mode. 4. Key Combination Without Power Button If the power button is non-functional but can still register presses: • Use Volume Up + Bixby button. • Connect your phone to a charger or PC, which will simulate a power button press. 5. Autoreboot to Recovery After Flashing TWRP • While flashing TWRP via Odin, check the Auto Reboot option. • After flashing, the phone should boot directly into TWRP. If these solutions work for you, reply with a confirmation! Please like share and subscribe to the channel
I have a sm-g960f the phone RMM STATE : Prenormal KG STATE : Checking(wasn't there after 168hrs) Frp off Oem off a error saying only official binaries are allowed to be flashed.. I cant flash twrp..
To fix the “only official binaries are allowed to be flashed” issue and proceed with flashing TWRP on your SM-G960F, follow these steps carefully: 1. Understand the Problem: • RMM State: Prenormal and KG State: Checking indicate that your device’s security mechanism (Samsung Knox) is active, preventing you from flashing custom binaries. • OEM Unlock is disabled, and you need to enable it to proceed. 2. Fixing RMM and KG State Issues: • Wait for 168 hours (7 days) with the device powered on and connected to a Wi-Fi network. This will allow the RMM and KG State to change to “Normal.” • Once this period is over, enable OEM Unlock in Developer Options. 3. Enable Developer Options: • Go to Settings > About Phone > Software Information and tap Build Number 7 times to unlock Developer Options. • Go back to Settings > Developer Options and look for OEM Unlock. Enable it. 4. Flash TWRP: • Download the correct TWRP image for your device model. • Boot your device into Download Mode (press and hold Volume Down + Bixby + Power buttons). • Use Odin (v3.13.1 or later) on your PC. • Load the TWRP .tar file in the AP section of Odin. • Uncheck Auto Reboot in Odin settings. • Click Start to flash TWRP. 5. Reboot into TWRP: • After flashing, reboot directly into recovery mode (press and hold Volume Up + Bixby + Power buttons) to prevent the stock recovery from overwriting TWRP. 6. Additional Notes: • Ensure FRP Lock is OFF. If it’s not, remove your Google account from the phone before proceeding. • Backup all important data, as unlocking the bootloader or flashing TWRP can result in a factory reset. If this guide helps, please like, share, and subscribe to TECH TUNED for more such tutorials and updates! Let me know if you face any further issues.
@techtuned025 huge thank to you bro for reply really appreciate....I have already enabled oem unlocking n waited 168hrs KG STATE checking was gone but RMM STATE prenormal is still there..
If you’re still encountering the “only official binaries are allowed to be flashed” error after following the basic steps, it’s time to dive deeper into the issue. Here’s what you need to do: 1. Verify Bootloader Status • Double-check if the bootloader is unlocked. Sometimes, even after enabling OEM Unlock, the bootloader might not unlock fully. • To unlock the bootloader: • Boot into Download Mode (Volume Down + Bixby + Power). • Look for a prompt saying “Press Volume Up to Unlock Bootloader.” • If this appears, press Volume Up and confirm. • Note: This will factory reset your phone. If this step is skipped or incomplete, Samsung’s firmware protection will block custom binaries. 2. Remove RMM/KG Lock Permanently (Bypass Method) If the RMM state remains Prenormal, use a custom patched method: Option A: Flash a Patched Firmware 1. Download a pre-rooted firmware or a patched Odin file specifically designed to bypass RMM and KG state restrictions. • Example: Custom firmware like Combination ROM. 2. Flash the firmware using Odin: • Load the patched firmware in respective Odin slots (AP, BL, CP, CSC). • Ensure “Auto Reboot” and “Re-Partition” are unchecked. 3. Reboot and reattempt enabling OEM Unlock in Developer Options. Option B: Use Magisk and ADB If flashing TWRP is still blocked, you can root the phone using Magisk: 1. Patch your stock boot image using Magisk Manager. 2. Flash the patched boot image via Odin. 3. Once rooted, use ADB commands to remove the RMM lock directly: • Connect your phone to a PC and open a terminal. • Run: adb shell su pm disable-user --user 0 com.samsung.android.rlc • This disables Samsung’s RMM/KG service. 3. Verify Binary Compatibility Ensure the TWRP file you’re using matches your exact device model and firmware version. Samsung devices are picky with binary compatibility. • Check your current firmware version in Settings > About Phone > Software Information. • Download the correct TWRP version for your region and variant (Exynos/Qualcomm) from trusted sources like TWRP.me. 4. Use Odin Alternatives If Odin fails repeatedly: • Try tools like Heimdall (Linux-based) or patched versions of Odin (like Odin3 Prince Comsy) to bypass Samsung’s signature verification. 5. Final Resort: Downgrade Firmware If the latest firmware has strong protection mechanisms: 1. Download an older, supported firmware version for your device from sources like SamMobile or Frija Tool. 2. Flash it with Odin, ensuring Re-Partition is disabled. 3. Once downgraded, reattempt the OEM Unlock and TWRP flashing. Pro Tip for Long-Term Success: • After flashing TWRP, immediately flash a custom ROM or Magisk to prevent the stock firmware from re-locking the bootloader. • If you experience boot loops, clear Dalvik/Cache in TWRP and reflash the ROM. If these steps help, don’t forget to like, share, and subscribe to TECH TUNED for more advanced fixes and troubleshooting tips!
You can make Google Wallet work on a rooted phone with Magisk by hiding root from the app using MagiskHide (or the DenyList in newer Magisk versions). If you’d like a detailed step-by-step guide, let me know-I can make a video on it!
@@techtuned025 The issue isn't magic, it's Safetynet device integity check. My install is broken because google added "noble" kernel name in the blacklist, nothing you can do against it. I don't know if there is new work around on newer version of the rom
Hello! No, Noble ROM is not compatible with devices that have the Snapdragon 845 chipset. Specifically, it supports the following devices from the Note 9 series: • Samsung Galaxy Note 9 (SM-N960F/FD/N) If you are using a Note 9 with the Exynos variant, you should be good to go. For the Snapdragon variant, it may require additional adjustments. Let me know if you have any more questions!
@Héctor2009-g2k Thanks for your comment! Please check out XDA forums; you’ll find detailed information about ROMs, including the one you’re looking for with Android 13 for the Snapdragon 845 variant.
If you install a Galaxy Note 9 Exynos ROM on a Galaxy Note 9 with a Snapdragon chip, it won’t work because the two variants have entirely different hardware architectures. The Exynos and Snapdragon processors use different kernels, drivers, and hardware configurations, making their ROMs incompatible. Attempting this could result in a soft brick, leaving your device stuck in a bootloop or unable to boot altogether. To recover, you’d need to re-flash the correct ROM or firmware designed specifically for the Snapdragon variant of the Galaxy Note 9. Always double-check the compatibility of the ROM with your device variant before flashing!
Hey! Thanks for reaching out! For the Snapdragon 845 variant of the Galaxy Note 9 (SM-N9600/SM-N960U), there are several compatible custom ROMs available. Some popular ones include: 1. Pixel Experience - Offers a clean, stock Android experience with minimal bloat. 2. LineageOS - A reliable ROM focused on performance and privacy. 3. HavocOS - Known for its features and customizations. 4. Evolution X - A feature-packed ROM inspired by Pixel devices. 5. ArrowOS - Lightweight and simple, with a focus on stability. You can find these ROMs on the XDA Developers Forum under the Galaxy Note 9 Snapdragon (SM-N9600) section. Make sure to check for the exact ROM thread and follow the instructions provided there for installation.
I've been stuck to an old version of noble because i use my spen bluetooth daily to take picture.
I'm hopping soon soon this will be fixed :D
Yeah, I totally get it! Fingers crossed 🤞-since Noble ROM gets updates so frequently, this might get fixed in the future too. After all, Alexis, the developer, has been doing an amazing job with the ROM! Make sure to subscribe to the channel-I’ll give an update and a detailed video as soon as it’s fixed!
I do the same as you did but I stuck at boot Galaxy Logo and restarting again please how can i fix
Any android 15 rom for galaxy A51 ???
This ROM has many problems; it reboots randomly, and the AI feature is not working.
Noble rom for S9 Snapdragon please
It makes me wanna buy a note 9 and do the same. I really love the hardware, but the software was outdated and was the only deal breaker for me. Now, it can be a great secondary phone.
That’s an awesome idea! The Note 9 hardware is still top-notch, and custom ROMs really bring it back to life. Glad you’re considering it as a secondary phone! 😊 More content on the Note 9 is on the way, so make sure you’re subscribed to stay updated!
Bro i have done it, its now stuck on emergency calls only, any fix?
Hey, if your phone is stuck on “Emergency Calls Only” after installing Noble ROM 6.1.1, try the following fixes:
1. Restart the Phone: Sometimes, a simple restart can fix network issues.
2. Check SIM Card: Ensure the SIM card is properly inserted. Remove and reinsert it to be sure.
3. Toggle Airplane Mode: Turn on Airplane Mode for 10-15 seconds, then turn it off to reset your network connection.
4. Network Settings Reset: Go to Settings > System > Reset Options and choose “Reset Wi-Fi, mobile & Bluetooth.”
5. Manual Network Selection: Go to Settings > Mobile Networks > Network Operators and select your carrier manually.
6. Reflash the ROM: If the issue persists, consider reflashing the ROM using a clean flash, making sure to wipe data/cache before reinstallation.
7. Check for ROM Updates: Sometimes, bugs are fixed in newer builds. Check for OTA updates in Settings > System > Updates.
8. Check Baseband Version: Go to Settings > About Phone > Baseband and ensure it’s correct.
If all else fails, you may need to contact the ROM developer or try a different version.
Let me know if this helps!
@techtuned025 i have patched imei, thats why i guess i am facing the problem, Do you have any fix for that? I have already checked like everything, did every steps here. But all in vain.
how do i enter twrp cause my power button doesnt work ! please help
If your Galaxy Note 9’s power button is not working, you can try these alternative methods to boot into TWRP:
1. ADB Command (Requires a PC)
• Make sure USB Debugging is enabled on your phone.
• Connect your phone to a PC with ADB installed.
• Open a command prompt or terminal on your PC and type:
adb reboot recovery
• This will boot your device into TWRP.
2. Using a Magisk Module (If Rooted)
• Install the “Recovery Reboot” module via the Magisk app.
• Reboot directly into TWRP using the module.
3. Third-Party Apps (If Rooted)
• Download apps like Reboot Manager or Quick Reboot from the Google Play Store.
• Use these apps to reboot into recovery mode.
4. Key Combination Without Power Button
If the power button is non-functional but can still register presses:
• Use Volume Up + Bixby button.
• Connect your phone to a charger or PC, which will simulate a power button press.
5. Autoreboot to Recovery After Flashing TWRP
• While flashing TWRP via Odin, check the Auto Reboot option.
• After flashing, the phone should boot directly into TWRP.
If these solutions work for you, reply with a confirmation! Please like share and subscribe to the channel
@techtuned025 thank you so much 💗.
Alexis cooked once again!!! Such a W!
Absolutely agree! Alexis is an amazing developer-always delivering top-notch work!
I have a sm-g960f the phone
RMM STATE : Prenormal
KG STATE : Checking(wasn't there after 168hrs)
Frp off
Oem off
a error saying only official binaries are allowed to be flashed..
I cant flash twrp..
To fix the “only official binaries are allowed to be flashed” issue and proceed with flashing TWRP on your SM-G960F, follow these steps carefully:
1. Understand the Problem:
• RMM State: Prenormal and KG State: Checking indicate that your device’s security mechanism (Samsung Knox) is active, preventing you from flashing custom binaries.
• OEM Unlock is disabled, and you need to enable it to proceed.
2. Fixing RMM and KG State Issues:
• Wait for 168 hours (7 days) with the device powered on and connected to a Wi-Fi network. This will allow the RMM and KG State to change to “Normal.”
• Once this period is over, enable OEM Unlock in Developer Options.
3. Enable Developer Options:
• Go to Settings > About Phone > Software Information and tap Build Number 7 times to unlock Developer Options.
• Go back to Settings > Developer Options and look for OEM Unlock. Enable it.
4. Flash TWRP:
• Download the correct TWRP image for your device model.
• Boot your device into Download Mode (press and hold Volume Down + Bixby + Power buttons).
• Use Odin (v3.13.1 or later) on your PC.
• Load the TWRP .tar file in the AP section of Odin.
• Uncheck Auto Reboot in Odin settings.
• Click Start to flash TWRP.
5. Reboot into TWRP:
• After flashing, reboot directly into recovery mode (press and hold Volume Up + Bixby + Power buttons) to prevent the stock recovery from overwriting TWRP.
6. Additional Notes:
• Ensure FRP Lock is OFF. If it’s not, remove your Google account from the phone before proceeding.
• Backup all important data, as unlocking the bootloader or flashing TWRP can result in a factory reset.
If this guide helps, please like, share, and subscribe to TECH TUNED for more such tutorials and updates! Let me know if you face any further issues.
@techtuned025 huge thank to you bro for reply really appreciate....I have already enabled oem unlocking n waited 168hrs KG STATE checking was gone but RMM STATE prenormal is still there..
If you’re still encountering the “only official binaries are allowed to be flashed” error after following the basic steps, it’s time to dive deeper into the issue. Here’s what you need to do:
1. Verify Bootloader Status
• Double-check if the bootloader is unlocked. Sometimes, even after enabling OEM Unlock, the bootloader might not unlock fully.
• To unlock the bootloader:
• Boot into Download Mode (Volume Down + Bixby + Power).
• Look for a prompt saying “Press Volume Up to Unlock Bootloader.”
• If this appears, press Volume Up and confirm.
• Note: This will factory reset your phone.
If this step is skipped or incomplete, Samsung’s firmware protection will block custom binaries.
2. Remove RMM/KG Lock Permanently (Bypass Method)
If the RMM state remains Prenormal, use a custom patched method:
Option A: Flash a Patched Firmware
1. Download a pre-rooted firmware or a patched Odin file specifically designed to bypass RMM and KG state restrictions.
• Example: Custom firmware like Combination ROM.
2. Flash the firmware using Odin:
• Load the patched firmware in respective Odin slots (AP, BL, CP, CSC).
• Ensure “Auto Reboot” and “Re-Partition” are unchecked.
3. Reboot and reattempt enabling OEM Unlock in Developer Options.
Option B: Use Magisk and ADB
If flashing TWRP is still blocked, you can root the phone using Magisk:
1. Patch your stock boot image using Magisk Manager.
2. Flash the patched boot image via Odin.
3. Once rooted, use ADB commands to remove the RMM lock directly:
• Connect your phone to a PC and open a terminal.
• Run:
adb shell
su
pm disable-user --user 0 com.samsung.android.rlc
• This disables Samsung’s RMM/KG service.
3. Verify Binary Compatibility
Ensure the TWRP file you’re using matches your exact device model and firmware version. Samsung devices are picky with binary compatibility.
• Check your current firmware version in Settings > About Phone > Software Information.
• Download the correct TWRP version for your region and variant (Exynos/Qualcomm) from trusted sources like TWRP.me.
4. Use Odin Alternatives
If Odin fails repeatedly:
• Try tools like Heimdall (Linux-based) or patched versions of Odin (like Odin3 Prince Comsy) to bypass Samsung’s signature verification.
5. Final Resort: Downgrade Firmware
If the latest firmware has strong protection mechanisms:
1. Download an older, supported firmware version for your device from sources like SamMobile or Frija Tool.
2. Flash it with Odin, ensuring Re-Partition is disabled.
3. Once downgraded, reattempt the OEM Unlock and TWRP flashing.
Pro Tip for Long-Term Success:
• After flashing TWRP, immediately flash a custom ROM or Magisk to prevent the stock firmware from re-locking the bootloader.
• If you experience boot loops, clear Dalvik/Cache in TWRP and reflash the ROM.
If these steps help, don’t forget to like, share, and subscribe to TECH TUNED for more advanced fixes and troubleshooting tips!
@@techtuned025 ill try n let u know bro 🫡
Will Google wallet app work on this custom ROM, if I have to root the phone?
You can make Google Wallet work on a rooted phone with Magisk by hiding root from the app using MagiskHide (or the DenyList in newer Magisk versions). If you’d like a detailed step-by-step guide, let me know-I can make a video on it!
@@techtuned025 The issue isn't magic, it's Safetynet device integity check.
My install is broken because google added "noble" kernel name in the blacklist, nothing you can do against it.
I don't know if there is new work around on newer version of the rom
Hello, this custom rom is available for snapdragon 845 chip
Hello! No, Noble ROM is not compatible with devices that have the Snapdragon 845 chipset. Specifically, it supports the following devices from the Note 9 series:
• Samsung Galaxy Note 9 (SM-N960F/FD/N)
If you are using a Note 9 with the Exynos variant, you should be good to go. For the Snapdragon variant, it may require additional adjustments.
Let me know if you have any more questions!
@techtuned025 Thanks for answering but there is another rom for this variant of the snapdragon 845 chip, a rom with Andrid 13
And another question, what happens if I put that rom on the phone but with the snapdragon 845 chip, would it work?
@Héctor2009-g2k Thanks for your comment! Please check out XDA forums; you’ll find detailed information about ROMs, including the one you’re looking for with Android 13 for the Snapdragon 845 variant.
If you install a Galaxy Note 9 Exynos ROM on a Galaxy Note 9 with a Snapdragon chip, it won’t work because the two variants have entirely different hardware architectures. The Exynos and Snapdragon processors use different kernels, drivers, and hardware configurations, making their ROMs incompatible.
Attempting this could result in a soft brick, leaving your device stuck in a bootloop or unable to boot altogether. To recover, you’d need to re-flash the correct ROM or firmware designed specifically for the Snapdragon variant of the Galaxy Note 9.
Always double-check the compatibility of the ROM with your device variant before flashing!
Snapdragon
Hey! Thanks for reaching out! For the Snapdragon 845 variant of the Galaxy Note 9 (SM-N9600/SM-N960U), there are several compatible custom ROMs available. Some popular ones include:
1. Pixel Experience - Offers a clean, stock Android experience with minimal bloat.
2. LineageOS - A reliable ROM focused on performance and privacy.
3. HavocOS - Known for its features and customizations.
4. Evolution X - A feature-packed ROM inspired by Pixel devices.
5. ArrowOS - Lightweight and simple, with a focus on stability.
You can find these ROMs on the XDA Developers Forum under the Galaxy Note 9 Snapdragon (SM-N9600) section. Make sure to check for the exact ROM thread and follow the instructions provided there for installation.