[Guide] (Oreo) Root Note8 (Exynos) + OEM Issue Fix + EFS Backup (Note8/S8/S8+)

Search This thread
By:
Advanced…
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
OK, I ran Odin on my Windows machine and got back into the dark art of flashing with Odin etc... On the first run things went wrong at step 10, probably because my fingers weren't fast enough changing from vol. down + power to vol. up + Bixby + power.

My good news is that now after a factory reset all has gone according to your instructions and I should have a rooted Note 8. OEM unlock is available.

Thanks for all your help!
 
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
Unfortunately, when trying to install 2 versions of Busybox, I get the message "SM-N950F is not rooted (in red)". Have I followed the wrong rooting route? Can you suggest what I have done wrong? How could I fix it? I saw an option flash by for using SuperSU, which if I recall correctly (it was 10 years ago) was an option I used for my original Note. What to do?
 
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
Should I do a factory reset and then root again with SuperSU, following your guide "Root with TWRP (Recommended method)" and then SuperSU using ChainFire auto root? I just need root, not a custom ROM.
 
dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
37,754
73,469
Gujarat, India
drketanrom.com
Samsung Galaxy Note 10+
Samsung Galaxy Note 20 Ultra
syncopath said:
Should I do a factory reset and then root again with SuperSU, following your guide "Root with TWRP (Recommended method)" and then SuperSU using ChainFire auto root? I just need root, not a custom ROM.
Click to expand...
Click to collapse
I wrote this 5 yrs ago and no more have device but below is trick and should work today as well.
1.Flash TWRP
2.Reboot to TWRP and then flash Magisk. Get magisk from here. get Magisk 24.3.apk and rename to Magisk_24.3.zip and flash from TWRP.
 
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
Thank you for your reply. I've done a factory reset but TWRP is still installed. I cannot remove it so have disabled it instead. Is this a problem for flashing TWRP?
 
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
Went ahead with re-flashing TWRP and installing Magisk 24.3 and I now seem to have root. (Need to find a sensible Linux command-line emulator to absolutely confirm, but various root test apps come up positive.) So thank you once again Dr. K.
 
dr.ketan

dr.ketan

Recognized Developer / Recognized Contributor
Apr 9, 2011
37,754
73,469
Gujarat, India
drketanrom.com
Samsung Galaxy Note 10+
Samsung Galaxy Note 20 Ultra
syncopath said:
Went ahead with re-flashing TWRP and installing Magisk 24.3 and I now seem to have root. (Need to find a sensible Linux command-line emulator to absolutely confirm, but various root test apps come up positive.) So thank you once again Dr. K.
Click to expand...
Click to collapse
You may see magisk app in drawer, if not, download magisk 24.3 apk (no rename this time) and simply install as apk file.
 
  • Like
Reactions: syncopath
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
dr.ketan said:
You may see magisk app in drawer, if not, download magisk 24.3 apk (no rename this time) and simply install as apk file.
Click to expand...
Click to collapse
I do see the Magisk app. I read of its many capabilities. I am just happy to have root, so that for instance I can block awful ads (would you believe I suddenly got an awful ad for some game with a tank with massive sound?) by adding my custom hosts file.
 
syncopath

syncopath

Senior Member
Oct 31, 2005
140
25
Amsterdam
Dear Dr. Ketan. Thank you so much for your help. Everything is now working as hoped. I see XDA no longer seems to have the thanks count system, but you had so many thanks anyway what would one more mean?

I will update my footer to acknowledge your help with rooting my Note8

Would adding a note about Magisk 24.3 to your first posts be useful for any other aspiring late Note8 rooters?

All the very best,
Penny aka Syncopath
 
S

stingbandel

Senior Member
Nov 23, 2005
409
44
Do I still need to install this N950F_root_OEM_issue_devices.zip file if I see oem unlock option on my phone? Thanks
 
W

whynotmvp

New member
Jul 15, 2022
1
0
Samsung Galaxy Note 8 (2017 Phone)
My Samsung note 8 is stuck in Recovery mode (Not TWRP)

Failed all attempts of flashing TWRP img.tar, Stock ROM using ODIN.. unable to have the privilege of OEM unlock option since the phone is not going past recovery mode.

Is there any way I can bring this phone back to life?

Definitely don't care about data on the phone which I am assuming is already wiped at the point

So if anyone can help, I would appreciate it much
 
Q

qadd

Member
Nov 4, 2022
8
1
ineed stop frp oem
file tools combo
efs error not work my device
restart all time
pleas help me
thanks for all
 

Attachments

  • ٢٠٢٢١١٠٤_٠٩٢٤١٦.jpg
    ٢٠٢٢١١٠٤_٠٩٢٤١٦.jpg
    1.3 MB · Views: 2
  • ٢٠٢٢١١٠٤_٠٩٢٧٢٠.jpg
    ٢٠٢٢١١٠٤_٠٩٢٧٢٠.jpg
    2.4 MB · Views: 3
B

billa

Senior Member
Mar 30, 2006
769
363
qadd said:
ineed stop frp oem
file tools combo
efs error not work my device
restart all time
pleas help me
thanks for all
Click to expand...
Click to collapse


Flash with combination firmware matching the current boot/binary version
Factory reset in Settings > Backup/Reset
Create a new TAR file from the latest stock firmware with only: boot, sboot, and system
Flash the above file
Enable OEM unlock in Settings > Developer Options
Factory reset in Settings > Backup/Reset
Flash the latest full stock firmware
Factory reset in Settings > Backup/Reset

You can use 7Zip to extract the stock firmware files, and create a new TAR with the 3 files.
If all done correctly, the FRP and OEM should be unlocked. ;)
 
Q

qadd

Member
Nov 4, 2022
8
1
billa said:
Flash with combination firmware matching the current boot/binary version
Factory reset in Settings > Backup/Reset
Create a new TAR file from the latest stock firmware with only: boot, sboot, and system
Flash the above file
Enable OEM unlock in Settings > Developer Options
Factory reset in Settings > Backup/Reset
Flash the latest full stock firmware
Factory reset in Settings > Backup/Reset

You can use 7Zip to extract the stock firmware files, and create a new TAR with the 3 files.
If all done correctly, the FRP and OEM should be unlocked. ;)
Click to expand...
Click to collapse
my friend
I tried to make a combination
files but not working
The device restarts
I want a combination that works
I sent you a picture of the problem
Please Help
Thank you
 

Attachments

  • ٢٠٢٢١١٠٤_٠٩٢٤١٦.jpg
    ٢٠٢٢١١٠٤_٠٩٢٤١٦.jpg
    1.3 MB · Views: 4
  • ٢٠٢٢١١٠٤_٠٩٢٧٢٠.jpg
    ٢٠٢٢١١٠٤_٠٩٢٧٢٠.jpg
    2.4 MB · Views: 5
B

billa

Senior Member
Mar 30, 2006
769
363
qadd said:
my friend
I tried to make a combination
files but not working
The device restarts
I want a combination that works
I sent you a picture of the problem
Please Help
Thank you
Click to expand...
Click to collapse

What do you mean by "restarts"?
When exactly, before or after your start flashing?
Does flashing even finish without errors?

If your device keeps restarting on the download screen without even flashing it, then you have a defective main board, no much you can do other than replace the board. On the download screen it should never restart by itself.

Based on the download picture, looks like your bootloader version is 12/C, make sure that the combination file has the same boot/binary version. But, I think you will have a hard time finding version 12/C, I've only seen up to 6 only. :(

If you can't find the right combination version, I would try flashing it with the latest firmware SM-G955F/XEU/G955FXXUCDVG4. Download it with Frja or SamFirm apps by entering model SM-G955F and region XEU (or whatever your region is. Then you can try to unlock the FRP using something like FRP-Tool ( https://samfw.com/blog/samfw-frp-tool-1-0-remove-samsung-frp-one-click ), and finally unlock the OEM.
 
Q

qadd

Member
Nov 4, 2022
8
1
billa said:
What do you mean by "restarts"?
When exactly, before or after your start flashing?
Does flashing even finish without errors?

If your device keeps restarting on the download screen without even flashing it, then you have a defective main board, no much you can do other than replace the board. On the download screen it should never restart by itself.

Based on the download picture, looks like your bootloader version is 12/C, make sure that the combination file has the same boot/binary version. But, I think you will have a hard time finding version 12/C, I've only seen up to 6 only. :(

If you can't find the right combination version, I would try flashing it with the latest firmware SM-G955F/XEU/G955FXXUCDVG4. Download it with Frja or SamFirm apps by entering model SM-G955F and region XEU (or whatever your region is. Then you can try to unlock the FRP using something like FRP-Tool ( https://samfw.com/blog/samfw-frp-tool-1-0-remove-samsung-frp-one-click ), and finally unlock the OEM.
Click to expand...
Click to collapse
my friend
Thank you for your interest. I have tried every way
The device reboots on the first logo
When downloading flash

G955F Binary U12 UC Android 9 Pie FIX DRK - dm-verity Failed Frp On Oem On (G955FXXUCDUB1)​

The device freezes on the second Samsung logo
I can not believe that there is no file or way to turn off protections

So I'm looking for Flash Combination

or efs file
thanks
 

Attachments

  • 20230115_112505.jpg
    20230115_112505.jpg
    1.3 MB · Views: 1
B

billa

Senior Member
Mar 30, 2006
769
363
qadd said:
my friend
Thank you for your interest. I have tried every way
The device reboots on the first logo
When downloading flash

G955F Binary U12 UC Android 9 Pie FIX DRK - dm-verity Failed Frp On Oem On (G955FXXUCDUB1)​

The device freezes on the second Samsung logo
I can not believe that there is no file or way to turn off protections

So I'm looking for Flash Combination

or efs file
thanks
Click to expand...
Click to collapse


Were you able to flash the latest full stock firmware U12? Did it go though fully with no errors?
If yes, and it's still rebooting on the Samsung logo, then you either have a DM-Verity or hardware failure.
If you put the phone into recovery mode and at the bottom it shows "DM-Verity Failed", then you need to fix that. Unfortunately it's not easy without a programming box like Z3X or Octopus. If the combination was available for U12, that should fix all the issues including DM-Verity, FRP, and OEM.

I would flash TWRP, then flash a "DM-Verity disabler" file through its menu. But probably flashing TWRP will fail due the FRP lock... it's a catch-22 situation. :(
 
Last edited:
Q

qadd

Member
Nov 4, 2022
8
1
billa said:
Were you able to flash the latest full stock firmware U12? Did it go though fully with no errors?
If yes, and it's still rebooting on the Samsung logo, then you either have a DM-Verity or hardware failure.
If you put the phone into recovery mode and at the bottom it shows "DM-Verity Failed", then you need to fix that. Unfortunately it's not easy without a programming box like Z3X or Octopus. If the combination was available for U12, that should fix all the issues including DM-Verity, FRP, and OEM.

I would flash TWRP, then flash a "DM-Verity disabler" file through its menu. But probably flashing TWRP will fail due the FRP lock... it's a catch-22 situation. :(
Click to expand...
Click to collapse
Thank you my friend
recovery mode


#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
E:failed to mount /efs: Invalid argument
Supported API: 3
E:failed to mount /efs: (Invalid argument)
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory


I was trying to fix the problem without box

((Were you able to flash the latest full stock firmware U12? Did it go though fully with no errors?))

yes no error

I want to fix the problem without box
I will keep searching
 
B

billa

Senior Member
Mar 30, 2006
769
363
qadd said:
Thank you my friend
recovery mode


#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
E:failed to mount /efs: Invalid argument
Supported API: 3
E:failed to mount /efs: (Invalid argument)
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory


I was trying to fix the problem without box

((Were you able to flash the latest full stock firmware U12? Did it go though fully with no errors?))

yes no error

I want to fix the problem without box
I will keep searching
Click to expand...
Click to collapse


Don't worry about any of the other errors, the most important to fix is "dm-verity verification failed".
Maybe you can find a local repair shop which has a Z3X or Octopus box to help you fix it.
Once that's fixed, you have to remove the FRP, and check if the EFS has not been corrupted.
OEM is the last step.
 
Q

qadd

Member
Nov 4, 2022
8
1
billa said:
Don't worry about any of the other errors, the most important to fix is "dm-verity verification failed".
Maybe you can find a local repair shop which has a Z3X or Octopus box to help you fix it.
Once that's fixed, you have to remove the FRP, and check if the EFS has not been corrupted.
OEM is the last step.
Click to expand...
Click to collapse
Thank you very much
 
  • Like
Reactions: billa
You must log in or register to reply here.

Similar threads

M
[HOW TO] Install Android OREO!!!!! (Snapdragon Only)
Replies
5K
Views
478K
Rollablunt420
Rollablunt420
S
[DVG5] OFFICIAL STOCK FW-update (Odin) thread (13 Aug 2022) GALAXY Note8 SM-N950F/DS
Replies
2K
Views
470K
A
_Android_1
K
[Guide] Note8 Can Do 4K60FPS [EXYNOS]
Replies
90
Views
85K
乁
乁(Ꝋ⏠Ꝋ)ㄏ
BlueFox721
[GUIDE][All US Firmware][Switch Carrier][Flash Carrier/Unlocked]SM-N950U/U1/W
Replies
3K
Views
379K
S
shabtab
R
Samsung Galaxy Note8 India
Replies
1K
Views
67K
fulcrum1971
fulcrum1971

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 71
    dr.ketan
    dr.ketan
    [Guide] How to Root Note8 + EFS Backup



    Index of post

    • Must Read - You must read this to know about side effects of rooting device.
    • OEM Issue - OEM unlock option is must to root device, know about it
    • PART1: Recommended method to root N8 (exynos)
    • PART2: Other possible methods to root N8 (exynos) - Use this as knowledge base, we still recommend method said in PART1.
    • PART3:EFS Backup - You must backup EFS as soon as you root the device and make a copy to other safe place too
    .

    Must Read :
    READ THIS BEFORE ROOTING DEVICE

    - Any of below said method to root will trip knox and void warranty forever.
    - Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
    - As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, but for that there are some workaround like Magisk Hide or SU hide, google it.
    - OTA likely won't work once you root device.
    - To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
    Click to expand...
    Click to collapse




    OEM issue
    OEM affected device - means OEM unlock option missing out of box and appears 7 days later. If you are uncertain about this, you can consider your device OEM affected .

    Workaround to get OEM unlock option if it is not available (Normally it appears after 7 days of clean install but this trick may bring it without 7 days waiting)

    - Flash latest stock firmware
    - Set clock 8 days prior to current date
    - Check for OTA update (check last check date is set to 8days prior from current)
    - Reboot
    - Set current date
    - Check for OTA update (now last check date should be current day
    - Check Developer option for OEM option
    Click to expand...
    Click to collapse




    PART1 : For Oreo & Pie

    ROOT Note8 (exynos) (Recommended method for all including have OEM issue )

    This method is most convenient and give most options in single pack, like root with magisk/SuperSU also it does patch OEM issue (losing OEM toggle on rooting device, follow below said guide to the letter to work it properly)




    How to Use

    1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
    2.Enable OEM Unlock from developer option (Read above for workaround if you don't have this option)
    3.Download and copy N950F_root_OEM_issue_devices.zip according Oreo/Pie to Ext SD card
    4.Download TWRP for N8
    5.Switch Off device
    6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
    7Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
    8.Select TWRP (tar image) with AP tab of Odin and Start
    9.Once Successfully flashed, you will see 'Passed' in Odin tab
    10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
    11.Select to allow modification
    12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
    13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
    14.Now select Install and navigate path to Ext SD card - N950F_root_OEM_issue_devices.zip, you have copied earlier
    15.Once Magisk flash successfully, Reboot to System
    Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
    Credits and Thanks goes to BlackMesa123 for this post for OEM patch script.

    Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.



    PART2 : (FOR OREO Only)

    ROOT Note8 (exynos) for devices that doesn't have OEM issue
    This method is actually for knowledge base purpose about all possible ways to root N950 (exynos), also to note that you shouldn't use this method if your device have OEM issue. We recommend all to use above said method for all in PART1


    Here is detailed guide about Root Galaxy Note8. Guide made in two sections, One who want root + Custom recovery and second Root without flashing custom recovery.


    1.Root with TWRP (Recommended method) You can root with SuperSU OR Magisk

    Root with TWRP is preferred method as it gives option to flash zip like mods,custom ROMs etc

    Root with SuperSU

    1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
    2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
    3.Download SuperSU (I have used SuperSU 2.82 SR4) to Ext SD card. Here is Original thread to see if any update available.
    4.Download TWRP for N8
    5.Switch Off device
    6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
    7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
    8.Select TWRP (tar image) with AP tab of Odin and Start
    9.Once Successfully flashed, you will see 'Passed' in Odin tab
    10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
    11.Select to allow modification
    12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
    13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
    14.Now select Install and navigate path to Ext SD card - SuperSU, you have copied earlier
    15.Once SuperSu flash successfully, Reboot to System

    Keep patience and allow device to boot, It may take time as we have formated data.

    Once device boot, you will have SuperSU in app drwer with working boot.

    ---------------------------------------------------------------------------------------------------------------------

    Root with Magisks


    1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
    2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
    3.Download and copy latest Magisks zip to Ext SD card
    4.Download TWRP for N8
    5.Switch Off device
    6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
    7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
    8.Select TWRP (tar image) with AP tab of Odin and Start
    9.Once Successfully flashed, you will see 'Passed' in Odin tab
    10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
    11.Select to allow modification
    12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
    13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
    14.Now select Install and navigate path to Ext SD card -Magisks zip, you have copied earlier
    15.Once Magisk flash successfully, Reboot to System

    Keep patience and allow device to boot, It may take time as we have formated data.
    Click to expand...
    Click to collapse

    2. Root with Stock Recovery
    This will give just root access and No custom recovery. (you can't flash custom ROM, mods zip with stock recovery but still can use FlashFire or similar.
    There are two ways, you can root with stock recovery
    1.CF Auto Root (superSU)
    1. Download CF Auto root package Thanks to @ChainFire and MobiFirmware
    2.Extract and read ReadMe.txt for details
    3.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
    4.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
    5.Switch Off device
    6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
    7.Download Odin and open it
    8.Select Image.tar.md5 (From you have download CF root package above) with AP tab of Odin and Start
    9.Once Successfully flashed, you will see 'Passed' in Odin tab
    Device will get Reboot with root access

    2.Magisk

    1.You need to have stock firmware, Extract boot.img file from that firmware with winzip or similar
    2.Install Latest Magisk Manager
    3.Open it and explore settings - Patched Boot Output format - select img.tar
    4.Now again from main page of Magisk Manager click Install - Install - Patch Boot Image File and patched the boot.img
    5.Copy patched_boot.img.tar to a PC from MagiskManager directory on Int Storage
    6.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
    7.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
    8.Switch Off device
    6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
    7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin and
    8.Select patched_image.tar (You copied as step 5 above) with AP tab of Odin and Start
    9.Once Successfully flashed, you will see 'Passed' in Odin tab
    10.The phone restarts and ask to reset to factory settings, This will erase all data from device
    11. Let reboot device and install Magisk manager again and open it. Now you will have root.
    12.You can install FlashFire and re flash Magisk zip again to have magisk module to work.
    Click to expand...
    Click to collapse



    PART3 :

    EFS Backup Tool Note8 /S8 /S8+



    This is simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read post #3 for more Information

    You needs root access to use this tool otherwise app won't open..

    Location of stored file :

    Device storage/MyEFS
    If you unable to see backup, contact me with details of your device variant


    Difference between Free/Play store

    -Both version makes backup in same format and no difference in backup.
    -Pro Version always look for backup, if there is no backup then it will make one just after boot. Also it will make backup if your last backup is made on different ROM than existing. Also it will give warning if backup fails.
    -Pro version keeps all previous backup to MyEFSBackup folder (you can choose to make extra copy on Ext SD too) while XDA version overwrites previous one and you need to make manual copy if you want to have multiple copies.
    -Pro version have option to Restore with single click
    Click to expand...
    Click to collapse

    This tool using generic name of partition block and you can restore with simple adb shell

    dd if=/path of backup files/ of=/partition block according your device



    Download EFS Backup Tool :


    PlayStore version

    XDA version

    ChangeLog :

    1.0
    - Initial Release (4696)
    1.1 (2650)
    - S9/S9+ added to supported list
    - Fix probable issue with SuperSu and Magisk (16.4) on Oreo
    1.2
    - Compatible with latest magisk
    View
    6
    dr.ketan
    dr.ketan
    What is EFS

    This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.

    How it can corrupt :

    - Any bad flashing, mishandling system modification can cause this.
    - Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.

    Impact on device/How I know I have corrupted EFS

    When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
    -Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
    -If you are unable to connect to network in spite of correct IMEI, chance are
    A. Your device is Locked to specific Network OR
    B. Your device is banned due to tempered IMEI
    -If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.

    What care should i take
    Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
    If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
    If you have already updated to newer ROM, make backup on current ROM.

    Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot

    attachment.php


    Here is different method to remove it.

    Method1 :
    Open root explorer.
    Navigate to /efs/FactoryApp/
    Open "factorymode" file as Text and edit it:
    Change this:

    Code: 
    OFF
    To:
    Code: 
    ON

    Open "keystr" file as Text and edit it:
    Code: 
    OFF
    To:

    Code: 
    ON
    Reboot device.

    Method2:

    Open Terminal emulator
    Write the following:
    Code: 
    su
    Then click enter. It will ask for super user permission, give it permissions.
    Write the following & click enter:
    Code: 
    rm /efs/FactoryApp/keystr
    Write the following & click enter:

    Code: 
    rm /efs/FactoryApp/factorymode
    Write the following & click enter:

    Code: 
    echo -n ON >> /efs/FactoryApp/keystr
    Write the following & click enter:

    Code: 
    echo -n ON >> /efs/FactoryApp/factorymode
    Write the following & click enter:

    Code: 
    chown 1000.1000 /efs/FactoryApp/keystr
    Write the following & click enter:

    Code: 
    chown 1000.1000 /efs/FactoryApp/factorymode
    Write the following & click enter:

    Code: 
    chmod 0744 /efs/FactoryApp/keystr
    Write the following & click enter:

    Code: 
    chmod 0744 /efs/FactoryApp/factorymode
    Reboot your device


    Method3

    Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.


    e:failed to mount /efs(invalid argument) error with bootloop

    This condition usually happens with using unsupported tool (usually from play store).

    To recover this, needs to use adb shell


    Code: 
    adb shell
 mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
 mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs

    x means your device EFS partition number

    PS : It needs CWM and busybox installed.
    View
    5
    Torquemada288
    Torquemada288
    nader1450 said:
    samsung live chat:

    that device note 8 after registered also dose not support OEM unlock

    any idea?
    Click to expand...
    Click to collapse
    Samsung Live Chat is staffed by below average imbeciles. You might as well ask your dog.
    Wait 7-10 days after you first turned on the device then check in Developer Options for the OEM Unlock option.
    View
    4
    dr.ketan
    dr.ketan
    Who have OEM unlock option appeared after 7 days and want to root device, Kindly use method from below said link and report back if that keeps OEM unlock option intact even after root
    https://forum.xda-developers.com/showpost.php?p=74763412&postcount=2350







    View
    4
    D
    d_kMT50
    Boodzilla said:
    I did exactly as stated but i'm stuck on the note 8 logo screen. Used to work on Oreo, but now on Pie something is missing. Is anyone having the same issue?
    Click to expand...
    Click to collapse
    Now I have root :)
    1. First of all it was root on my note on android 8. All was done as described by author of that theme, and has OEM unlocked.
    2. Then flash android 9 firmware. Boot to android.
    3. Enable DEVELOPER. Disable OEM unlock and NO REBOOT phone!!!, enable OEM unlock (that was done becauseTWRP flashed with - FAIL).
    4. Reboot to ODIN (download) mode.
    5. Flash TWRP with no reboot.
    6. Boot to TWRP. Format DATA as described, and reboot recovery.
    7. Flash that script-- "no-verity-opt-encrypt-6.0.zip" (sorry but i can`t post links, but google can find it at -- androidfilehost)
    -- Desided to check what i have - phone passed logo but was in bootloop
    8. Flash magisk-v18.1.
    After that phone begin to boot normaly and have ROOT.
    View

New posts