[Samsung Galaxy Note FE Guides, News, & Discussion] RicePlay33:
UPDATE OF JULY, 13th 2019

: IMPORTANT INFO : This guide is no longer updated. The recent update of June 2019 broke compatibility with my Bootloader Ver. 2 I was using which worked fine from the first Nougat release to the first Pie update (included). As I'm still daily running Android Nougat (7.0), I can't risk to upgrade to BL Ver. 5 and find myself locked under Pie. And the main risk is that I can't know if BL v5 is breaking modem compatibility or not and if it does it means that I'll lose all wireless connectivity under Nougat. So, as I can't risk my device (which is my daily) I have no choice other than dropping the support of this device. I apologize.

SAMSUNG Galaxy Note Fan Edition

Exynos 8890 - International Ver. [SM-N935F/DS]

Current Status

:

(Pie 9.0) -

POST 06/21/2019 Update

-

Unknown

(Pie 9.0) -

PRE 06/21/2019 Update

-

Rootable

(Oreo 8.0) -

Rootable

(Nougat 7.0) -

Rootable

Latest Ver. of TWRP: v3.3.1-0

Latest Ver. of Android: Pie (Android 9.0)

1 - ▼

DISCLAIMER

▼​

- I DECLINE TOTAL RESPONSIBILITY IF YOU DAMAGE OR BRICK YOUR PHONE WHILE TRYING THIS METHOD ! YOU'RE DOING IT AT YOUR OWN RISKS !

- THIS METHOD IS ONLY VALID FOR THE GALAXY NOTE FAN EDITION (EXYNOS Ver.) SM-N935

F/DS

VERSION ! IT'S

NOT

SUITABLE FOR THE KOREAN VARIANTS !

- FLASHING ANY CUSTOM BINARY

WILL IRREMEDIABLY VOID YOUR WARRANTY

AND KNOX COUNTER WILL BE TRIGGERED (0x1).

- MAKE SURE THAT YOUR DEVICE HAS AT LEAST 70% BATTERY BEFORE ATTEMPTING ANY STEPS !

-

ALL THE DATA ON THE INTERNAL STORAGE WILL BE DELETED ! BACKUP ALL YOUR FILES IN A SAFE PLACE BEFORE PROCEEDING !

2 - ▼

Important Infos

▼​

To avoid making any mistakes, I

HIGHLY

recommend you to

READ CAREFULLY

the

WHOLE

guide

BEFORE

attempting anything! Prevention is better than cure remember

;)

The Galaxy Note FE (like many other Samsung devices) use

dm-verity

and

data partition encryption

.

►

Android 9.0 (Pie) - UPDATE OF THE 06/21/2019 (Bootloader V5) :

The Note FE (International Ver.) Android Pie update of (June 2019) support is unknown.

As I can't try if my patch works, (see above), I can't test if the latest update is rootable or not.

However, the problem is probably similiar to the first Pie release of March 2019, the fix is also probably the same

but due to changes to the kernel or boot routines, the old fix dosen't work anymore.

If you're under an older Pie release (typically with a

v4 BL

or less) or even under an other Android version, you can still follow this guide.

►

About RMM State :

The Note FE (International Ver.) is shipped with a component called "RMM".

This component is able to prevent the end-user from flashing any custom binary on the device while it's active.

You can check if your RMM is enabled or disabled by putting your device in Download Mode :

- If the line

"RMM State: Prenormal"

is present, then RMM is

enabled

and you won't be able to flash any custom binary.

- If it's absent, then it has already been

disabled

which means that you'll be able to flash any custom binary.

This component suddenly disable itself after 7 days of

continuous uptime

since the device has been last powered on.

You can check your device actual uptime by going into : "Settings" > "About phone" > "Status" > "Uptime"

Or use CPU-Z : "System" tab and "System Uptime". (CPU-Z displays the uptime in days rather than hours.)

Once 7 days are elapsed, it will be desactivated

BUT!

If you format the data partition for example, which's required to disable data encryption for rooting, it will be back!

Even worse, if you reboot once you've setup your phone, you'll get blocked with a message when you'll powering it on saying ("custom binary has been block due to remaining installment balance") and you'll have to reflash stock to get your device working again...

To avoid that, once the /data partition has been wiped, you'll need to apply the RMM fix (prerequisites section, see below) which prevents the device from re-self-locking itself after rebooting, once the initial setup has been completed.

Everytime you install a new official firmware, RMM might be active again.

It is triggered by an hidden system app called "Rlc" which acts on the bootloader lock.

If your Rlc app is still present, the best thing to do is to simply delete it ASAP to prevent any unpredictable action on your bootloader. (system/priv-app/Rlc)

For custom ROMs, normally they're safe. But still, check if the dev has already deleted Rlc, otherwise you'll have to do it by yourself.

3 - ▼

Prerequisites

▼​

1 - A SAMSUNG Galaxy Note FE [SM-N935F/DS]

2 - The Samsung USB Drivers (If not already installed, => [HERE] <= )

3 - Download the lastest Odin (v3.13.1) => [HERE] <=

4 - Download TWRP for the Galaxy Note7 [SM-N930F] (v3.2.1-0.img.tar) => [HERE] <=

5 -

For Android Nougat (7.0)

:

5 -

For Android Oreo (8.0)

:

5 -

For Android Pie (9.0)

:

6 - A PC and a USB-C Cable

7 - A brain, a pair of eyeballs and some fingers (Yeah, that could help... especially the first one..)

4 - ▼

Flashing TWRP 3.2.1-0 on the Galaxy Note FE

▼​

If Your RMM is locked you will have to wait 7 days (or 168 hours)

while maintaining your device up and running.

(NEVER REBOOT DURING THIS TIME ! IT WILL RESET THE RMM TIME COUNTER!)

=> For more info and/or if you don't understand what I'm talking about, please refer to section 2 of this page and read it all.

Once RMM is desactivated (or already desactivated), you can proceed to the next steps :

Now TWRP is successfully installed.

But we're not done yet ! We still have to deal with the data encryption and disable dm-verity in order to boot properly.

5 - ▼

[9.0] Rooting the Galaxy Note FE under Android Pie

▼​

Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.

Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide ;)

6 - ▼

[8.0] Rooting the Galaxy Note FE under Android Oreo

▼​

Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.

Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide ;)

7 - ▼

[7.0] Rooting the Galaxy Note FE under Android Nougat

▼​

Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.

Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide ;)

8 - ▼

Disable SecurityLogAgent pop-up & Samsung Anti-Malware

▼​

Samsung provides an anti-malware on their phones and the Note FE is one of them. The system will detect that Magisk has been installed and a service called "SecurityLogAgent" will regularly

pop-up in your notification bar to invite you to launch the Device Maintenance app and reboot the device using an orange button to "eliminate" the threat.

=> DO NOT REBOOT USING THIS BUTTON ! <=

You'll end up soft-brick your phone. And this, won't disappear on it's own.

Here's how to disable and definitively hide that anti-malware crap from the Device Management app

:

The Samsung Anti Malware is now disabled as well as the annoying pop-up.You're good to go, enjoy!

9 - ▼

Fix Samsung Health

▼​

For whatever reasons, Samsung locks-up Samsung Health once Knox has been triggered.. But go figure why, there's only a simple thing to do to re-enable the app and be able to use it again easily.

You can either use a file manager or the app "BuildProp Editor".

Samsung Health is now working again.

:good:

10 - ▼

Troubleshooting

▼​

You have a problem with your Note FE ? Take a look at those answers before posting :

Q: I try to flash TWRP with Odin but a message pops up on my device and says "custom binary has been block due to remaining installment balance". What's happening ?

A: RMM. This message is more likely to appear if you still have RMM enabled. Boot your phone, keep it powered on and running and never reboots during 7 days and it should disappear.

Q: I've flashed TWRP with success, formatted data and stuff but I see the message "custom binary has been block due to remaining installment balance" at boot and I can't boot ! What's happening ?

A: RMM again ! Once data has been formatted and Android first reinstalled, RMM lock is back! Same thing can happen if you did not install the RMM fix with TWRP. To unbrick it, you have 2 options : 1 - Flash stock BUT with HOME_CSC. (It will keep the RMM elasped time, but you'll have to keep in mind since how much time has elapsed already.) or 2 - Reflash stock and follow the entire procedure again and the waiting again. The first one might work, if not, then try the 2nd one.

Q: I've managed to install TWRP, root and get my phone up and running but I've clicked on the orange "Reboot" in the Anti-Malware tab in the Device Management app.

Now my phone bootloops (or) shows the message "custom binary has been block due to remaining installment balance" and I'm stuck with it.

A: You've got trapped into Samsung Anti-Malware crap. This utility can't delete Magisk. Any solutions ? Restore one of your previous TWRP backup but if you have none, the only solution is to re-flash stock, repeat the entire procedure, disable SecurityEventLog service to get rid of those annoying security pop-ups

AND stay away

from the anti-malware utility !

11 - ▼

Extras

▼​

Thanks. If there is any mistakes or errors, please feel free to report them to me, I'll correct them :)

Credits goes to :

Magisk (@topjohnwu & [MENTION=1915408]phhusson[/MENTION], [MENTION=631273]Chainfire[/MENTION], [MENTION=2605798]nkk71[/MENTION], [MENTION=4544860]osm0sis[/MENTION], [MENTION=1162986]Captain_Throwback[/MENTION], [MENTION=4667597]Didgeridoohan[/MENTION], [MENTION=8340552]jenslody[/MENTION], [MENTION=3400685]digitalhigh[/MENTION], [MENTION=5345056]DVDandroid[/MENTION])

TWRP Recovery (@TeamTWRP)

The RMM Fix (@BlackMesa123)

The /data partition Fix (@dr.ketan & [MENTION=8657184]RicePlay33[/MENTION])

Odin Soft (@anycallmongolia)

MiXplorer File Manager (@HootanParsa)

How to keep the elasped time (@societyragdoll)

SAMSUNG... (@Samsung) (duh)

Author : RicePlay33​