Database Users

Restoring a dd backup with Odin (A fix for a badly broken EFS)

I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam

how to obtain stl3 and bml3
in adb
adb shell
su (allow the root access)
cat /dev/block/stl3 > /sdcard/stl3.bak
cat /dev/block/bml3 > /sdcard/bml3.bak
rename .bak by .bin
sorry for my english.

Da_G said:
I was reading rotohammer's post
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.

trip007in said:
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.
Click to expand...
Click to collapse
hi please use the search button , you will easily find how to , this is a 5 month old thread ....

Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.

whiteguypl said:
Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.
Click to expand...
Click to collapse
I dunno how they used it but htere s a 2 weeks old post by darky in the i9000 section .

can someone upload efs.rfs?efs.tar?
i screwd mine and i dont have backup

Every device has there own efs folder (IMEI and stuf).
So if you don't have a backup I don't know what to tell you...

thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin

This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.

Truckerglenn said:
This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.
Click to expand...
Click to collapse
Someone gets it lolz .
Sent from my SAMSUNG-SGH-I897 using xda premium

moeinf said:
thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin
Click to expand...
Click to collapse
Sorry im late...but adamoutler was going to post a blank efs partition in another thread . Dont know what happenwd to it tho.
Sent from my SAMSUNG-SGH-I897 using xda premium

Da_G said:
I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
If I could Ill kiss you! Thank you it really did the trick!

[GUIDE] Backup your /efs folder before flashing any ROM (IMPORTANT!)

Hi everyone!
The reason why I post this threat is that there is no clearly mention about the /efs folder in the rooting/how-to guides in here. In my opinion, it's the MOST IMPORTANT thing to know for all Samsung devices with Android OS before flashing any custom ROM. There is a really good threat posted in Original Android Development by Rawat, which I'm going to quote right here. Unfortunately, it's not a sticky threat so it's gone somewhere deeper in the forums.
I really beg you for a sticky of this thread, or Rawats to prevent all new users of damaging their phones.
My point is: many of you can agree, the /efs folder is very sensitive. If it get corrupted and you have no backup of it, well.. let's just say it's nearly impossible to get you phone working again. It contains your IMEI number and some other important things! There have been some situations when it get corrupted after flashing some ROMs. Without a backup, your IMEI is gone. The only way to get your phone working again is to send it back to Samsung Service.
Here is the guide, originally posted by Rawat! Thank you very much:
This guide is based on a guide by Candanga on the i9000 forums, and some commands from supercurio
Please hit thanks on their posts and show them some love for the write up.
-----------------------------------------------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centres.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
What you will need:
* Rooted SGS II to get permissions as a SU (Super User) and perform the backup
* I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile. <- Busybox Commands(or Google them)
* Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS II during this process, because it may request SU permissions [currently doesn't on CF-root]; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS II.
Here are 3 methods, I recommend that you do both Clean and RAW.
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD in sdcard/efs/, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can greatly support in recovering your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
alternative
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
--------------------------------------
original thread by Rawat @ xda: click here

matee89 said:
Without a backup, your IMEI is gone. The only way to get your phone working again is to send it back to Samsung Service.
Click to expand...
Click to collapse
Not 100% true, there are other ways, for example I know how to generate valid nv_data files.
matee89 said:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
Click to expand...
Click to collapse
I think using dd is better than cat, I dont know why but I have a feeling cat could do some character conversion in some circumstances, so :-
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs/efs_dev-block-mmcblk0p1.img
or better still do both, cannot have too many backups

Thanks for info Odia! Well, the backup is still important. Saves a lot of time for newbies, so i think that this guide should be sticky. Everyone can see it clearly then

There is already a thread about this...
rawat thread
And there's an app on the way apparently..
app thread

Yes, but this thread is not sticky. If you at least read a little part of mine post you should see that I quoted Hawats thread and put a link to it. My point is that this should be more visible for everyone. To be honest, it should be sticky like the rooting guides and other how to's, because it can give you serious problems with the device when files inside /efs get corrupted. Myself I haven't know about the purpose of /efs since yesterday, because it wasn't clearly mentioned in here. Just want to help other newcomers to Samsung devices.
This app will do exacly the same thing like you will do right now following this guide. It's not released yet, so this guide should be used meanwhile.

matee89 said:
Thanks for info Odia! Well, the backup is still important. Saves a lot of time for newbies, so i think that this guide should be sticky. Everyone can see it clearly then
Click to expand...
Click to collapse
Sure the backup is important, is why I added some input to your thread about using the dd command to make double sure the backup taken was valid.
Can an admin or mod make Rawat's thread sticky pls?

Okay, shall edit and post the alternative backup method with dd comand instead of cat.
Would be great with sticky. I don't think that majority of people who's flashing ROM's know how important this folder is. From what I've heard the nandroid backup in CWM recovery does not backup the /efs so it's needed to be done manually.

before using this comands you should use mkdir /sdcard/efs if you don't want to get an error
I made clean, raw and dd back up. Now I have two files of 20 MB each and one of 28Kb is it ok?

Yes, it seems okay. I saved my efs backup files on my PC as well in case something happens to the internal sdcard storage.

Thank you for that. I will backup mine tonight.

Thank you got the backup with my Note

Re: mp1806
Probably some of the ROMs that you flashed had an automatic backup script included, so you already got a working efs backup on your sd card. If you want to be completly sure if the backup is correct, you can make it manually by following the steps in my first post. Later you can even copy your backup to your PC if you like to.

There is three or four apps by now that aid you in creating EFS backups.
Most have been mentioned in the other (older) EFS backup thread.
It's one app i forgot the name of, EFS-Pro that works from your computer and my own one (see sig).
If you search for "efs backup" on the market you will find "Nitrality" (or however it's spelled, forgot the exact name right now) and my one.
Mine also offers an option to check the EFS backup if it's OK or corrupted, so can be really sure to have a good one when the check succeeds.
Point beeing:
No real need to tinker on the shell anymore

Great Thanks for this

Hi, I am using the RAW method on my Galaxy Note, rooted, but I keep getting a file not found error. Anyone able to help? I got the su and the prompt changed correctly, but after:
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
It just says file not found. What am I doing wrong?

Another way is to use ktool made by Hellcat to backup your efs and even restore.
http://forum.xda-developers.com/showthread.php?t=1314719&highlight=ktool
Anyone knows if this tool is as good as command line way?

(nvm)

Odia said:
Not 100% true, there are other ways, for example I know how to generate valid nv_data files.
Click to expand...
Click to collapse
Can you please let me know how to generate it? I HAVE LOST THE EFS FILES ON MY PHONE!

Samsung Tool
Samsung Tool is the easiest and more safe method

how do you restore it?

[Q] N910F EFS messed up, lost network access help???

Well, first of all.... I made a clean copy of my EFS folder before having this problem but.....using the lovely and simple commands copy and paste and now the files don't have the correct permissions and owners so nothing changes when I copy them back so my question is...
Could you guys please provide me a list with all the N910F EFS files + permissions and owners?
*EDIT*
My IMEI, serial number, baseband..... are all correct.
Thanks:crying:

Have u tried flashing stock rom through odin.Many users have fixed this problem by using the method
Sent from my SM-N910G using XDA Premium 4 mobile app

RISHI RAJ said:
Have u tried flashing stock rom through odin.Many users have fixed this problem by using the method
Sent from my SM-N910G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I tried 3 different stock roms, I also downgraded to stock kitkat and then flashed a stock lollipop rom and... same problem.

ANTONIOPS said:
Yes, I tried 3 different stock roms, I also downgraded to stock kitkat and then flashed a stock lollipop rom and... same problem.
Click to expand...
Click to collapse
same problem here also, except, i have original imei intact and can make calls, send sms etc. flashed original firmware through odin and through kies, no luck, efs file 0mb. I have lost finger print scan and my serial number is wrong.

I had a similar problem a while back, came across this info here, the 'dev' files mentioned are for a N910G, just type 'mount' at a terminal to see which 'dev' file the efs partition mounts on. I used Method 1, but Method 2, does essentially the same thing in the end, so which ever you find easiest. Damn saved my phone, I even bought a replacement online before I found this solutionl.
Fix screwed up EFS Partition.
-------------------------------
posted by Steve Lazarus on XDA Dev on 5th October 2013
http://forum.xda-developers.com/showthread.php?t=2471421
(Used METHOD 2 on 09-01-2015, worked a treat, RaSTuS)
(Will try METHOD 1 next time)
METHOD 1
1. Install stock Firmware via Odin then rerun autoroot (to regain root)
2. Install TWRP via Odin, reboot to recovery.
3. Install SuperSU from external SD Card.
4. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Reset the EFS partition with the following commands:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the
mobile network, and my IMEI is there and correct. Seems like the EFS partition
can rebuild itself now I guess...
Gotta love the XDA community !!!
METHOD 2
You can also try just running Commands via TWRP before using Odin to revert to
stock, re-rooting etc..Worked for me while I was doing some restore testing with
Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command".
3. Hit "Select" (lower right corner) to select root (/) folder.
4. keyboard will open, type in the following commands, make sure you put the
spaces and / where they need to be, it needs to look exactly as outlined.
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
Hit Go - The command will run.
Clear the input box, type the following command:
mkdir /efs
Hit Go - The command will run.
Clear the input box, type the following command:
mount -t ext4 /dev/block/mmcblk0p13 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the
directions.

rastus.rob said:
I had a similar problem a while back, came across this info here, the 'dev' files mentioned are for a N910G, just type 'mount' at a terminal to see which 'dev' file the efs partition mounts on. I used Method 1, but Method 2, does essentially the same thing in the end, so which ever you find easiest. Damn saved my phone, I even bought a replacement online before I found this solutionl.
Fix screwed up EFS Partition.
-------------------------------
posted by Steve Lazarus on XDA Dev on 5th October 2013
http://forum.xda-developers.com/showthread.php?t=2471421
(Used METHOD 2 on 09-01-2015, worked a treat, RaSTuS)
(Will try METHOD 1 next time)
METHOD 1
1. Install stock Firmware via Odin then rerun autoroot (to regain root)
2. Install TWRP via Odin, reboot to recovery.
3. Install SuperSU from external SD Card.
4. Do an "adb shell" when phone is in recovery mode to run commands via TWRP.
From the ADB shell: Reset the EFS partition with the following commands:
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p13 /efs
Do a factory reset, reboot system
Afterwards, no more boot looping, the phone successfully registered on the
mobile network, and my IMEI is there and correct. Seems like the EFS partition
can rebuild itself now I guess...
Gotta love the XDA community !!!
METHOD 2
You can also try just running Commands via TWRP before using Odin to revert to
stock, re-rooting etc..Worked for me while I was doing some restore testing with
Jovy's modded kernel ..Just trying to save you some time..
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command".
3. Hit "Select" (lower right corner) to select root (/) folder.
4. keyboard will open, type in the following commands, make sure you put the
spaces and / where they need to be, it needs to look exactly as outlined.
mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)
Hit Go - The command will run.
Clear the input box, type the following command:
mkdir /efs
Hit Go - The command will run.
Clear the input box, type the following command:
mount -t ext4 /dev/block/mmcblk0p13 /efs
Hit Go - The command will run.
You can now back out of the terminal command, and follow the rest of the
directions.
Click to expand...
Click to collapse
I tried that and those solutions didn't work because I'm the biggest idiot in this galaxy:laugh:, some time ago I deleted the EFS golden backup in the service menu and I think that's why it didn't rebuild after I erased the main EFS partition but the good thing is that I made a clean backup of it so I can copy the files back to the EFS folder, the thing is that I just copied and pasted them so now all files have root as the owner and I know some of them had system, radio, wifi... as owners but I can't remember which ones, I think I could fix it if I see a list with the files, permissions and owners. Thanks anyway:good::good:
*EDIT*
Oh!! also I forgot to tell you that my imei, baseband, serial number bla, bla, bla are correct.

please help guys i have same problem but my note is n910f
hello ... its my first comment here ... and i whant to ask ...if i have the same phone ...but ... its a n910f ... its working this metods ? please guys i need help ... thx ...

Hi, I have a N910C and my IMEI got changed when i flashed offical lolipop 5.1.1, and now it wont register on any network, the IMEI isn't fake or corrupted i tried imei analyzer and it says its valid but for a 2005 Phone. I tried deleting /efs entirely/ flash diff firmwares / factory reset / clean kies install, nothing worked. my .nv_data.bak/nv_data.bak is missing. Please help

N910F EFS lost
florinhrib said:
hello ... its my first comment here ... and i whant to ask ...if i have the same phone ...but ... its a n910f ... its working this metods ? please guys i need help ... thx ...
Click to expand...
Click to collapse
i'm new too i'm from Algeria, i have a GN4 with no IMEI, i lost the EFS foldier, the wifi and blueth work but no finger print and no health app, please help

IMEI (EFS) BAckup Tool Note 7

IMEI (EFS) BAckup Tool Note 7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 this.
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
Download :
PRO Version
XDA version (free)- Attached at end of this post.
Difference between Free/PRO version
-Both version makes backup in same format and no difference in backup.
-Pro version have option to Restore with single click
-Free version will save file in MyEFS and if you make next backup it will replace older one. While play store version everytime creates new folder with date ,Time and your IMEI stamp so you can keep multiple backup as well no confulsion about which backup is made when and on which device. Also it makes copy of build.prop so you can get idea you were on which ROM when backup created)
-Play store version give notification in case backup not created.
-Weekly Auto backup feature available on play store version.
-PIT creator. Play store V1.1 added option to create PIT file from existing layout
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
ChangeLog
1.0 - Initial release.
In case backup is not created then post your device details here.

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
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. Here this is for just visual representation. Block number/Name may be completely different on your device.
PS : It needs CWM and busybox installed.

Last

Doctor is unbelievable your continue effort and dedication, could you solve your brick problem on your device??
N7, SM-N930F.

charlypaez said:
Doctor is unbelievable your continue effort and dedication, could you solve your brick problem on your device??
N7, SM-N930F.
Click to expand...
Click to collapse
Yes fixed soon after making this tool
I have updated details on my ROM thread.

dr.ketan said:
Yes fixed soon after making this tool
I have updated details on my ROM thread.
Click to expand...
Click to collapse
What a great new!!! The notice of the day... Thank you for all you support... You will be a create telegram support group for N7 Rom doctor?
N7, SM-N930F.

charlypaez said:
What a great new!!! The notice of the day... Thank you for all you support... You will be a create telegram support group for N7 Rom doctor?
N7, SM-N930F.
Click to expand...
Click to collapse
Nope. Not possible for me to manage. I have telegram broadcast for my PRO ROM users but only broadcasting channel.

dr.ketan said:
Nope. Not possible for me to manage. I have telegram broadcast for my PRO ROM users but only broadcasting channel.
Click to expand...
Click to collapse
Understood doctor.. Thanks again for all!

Hi Dr, I tried method one and all them settings were already set to on? what does that mean exactly

turilo said:
Hi Dr, I tried method one and all them settings were already set to on? what does that mean exactly
Click to expand...
Click to collapse
Your device is stuck to safe mode?
Why are you doing that?

dr.ketan said:
Your device is stuck to safe mode?
Why are you doing that?
Click to expand...
Click to collapse
I did not put it in safe mode, right after i followed your root guide (which worked well) i am trying to backup efs. It does not say my device is in safe mode anywhere..
EDIT: all done and saved using your new tool, will get Pro once released for your support. Thanks Dr.

turilo said:
I did not put it in safe mode, right after i followed your root guide (which worked well) i am trying to backup efs. It does not say my device is in safe mode anywhere..
EDIT: all done and saved using your new tool, will get Pro once released for your support. Thanks Dr.
Click to expand...
Click to collapse
Omg don't do that 4 methods
Those are for those who have efs issue.
To backup simply download app and create backup with that.

dr.ketan said:
Omg don't do that 4 methods
Those are for those who have efs issue.
To backup simply download app and create backup with that.
Click to expand...
Click to collapse
yea i edited my last post lol all good Dr ty

Hey dr.ketan,
I've always used TWRP to backup the EFS partition, when I flash a ROM from other country and I dont have connection to my carrier I restore this partition using TWRP and it works again..... So my question is, is this a safe mode of doing it too?

I have never used twrp for this so no much idea.. Regarding safety yes this method is safe. Also twrp should safe. This is useful for those who don't have twrp.

Thank you...
Actually about the safe method I was asking if TWRP method was safe, I know yours is

I'd like to purchase the pro version of this app to go towards the tweaks pro for note 7.
I have already purchased donate dev and utilities pro for note 4.
Looking for an app that be useful to purchase for my note 7 instead of the others to go towards tweaks pro note 7
Thanks

turilo said:
I'd like to purchase the pro version of this app to go towards the tweaks pro for note 7.
I have already purchased donate dev and utilities pro for note 4.
Looking for an app that be useful to purchase for my note 7 instead of the others to go towards tweaks pro note 7
Thanks
Click to expand...
Click to collapse
If you have purchased Donate Dev then no need to purchase anything more because it covers almost utilities for N7 in one app.
Simply download Request code for Note7 from here - Install it and send me mail through it. Before sending mail you have to write Google Order ID of Donate Dev app (you get it on mail you received from google)
After this you will get complete instructions and Pro key in 24-48hrs.
Also once you have Pro Key, you will able to get Pro version of IMEI app (I will release soon)
Reagrds
Dr.Ketan

Pro version (Complimentary) available for (Dr.Ketan Tweaks) Pro Users
Open dr.Ketan Tweaks Pro - Download Latest Tweaks Pro - Latest version of tweaks Pro - N930 Note7 - IMEI Tool SGN7 Pro_Complimentary 1.1.apk
Download and Install as regular apk.

Good job Dr... Only the best!

[GUIDE] Fix screen rotation / device sensors

If your persist partition gets damaged this can break your sensors. Sometimes that just happens during a faulty operation while flashing.
Some ROMs might even fail to boot and in some weird situations the screen may rotate to the opposite direction.
To fix persist you can try these methods. If none of them work flash the lastest OxygenOS (v3.1.4) and try again. This doesn't work with all ROMs.
Sensors can be checked using apps like CPU Info (Google Play), CPU Info (F-Droid) or SatStat (F-Droid).
Method A) Restore an older TWRP backup of persist
If this does not work or you never made a backup, keep reading for advanced options.​Method B) Flash the lastest OxygenOS and reboot.
OxygenOS can recreate missing sensor calibration data. Some custom ROMs can but not all of them.​If this does not work, keep reading for advanced options.​
Once everything works again take a TWRP backup of persist you can always return to.
While you're at it, back up EFS as well if you don't know where to find a backup or you never made one.
More about what every partition does, including EFS and persist.
Congrats, you're done!
If you need to move to the advanced methods, take a TWRP backup of your current persist and keep it no matter what.
If none of them fixed your issues, restore this backup of persist before trying any other approach.
Copy the backup to your PC now to make sure you don't lose it on accident!
To open a shell on TWRP go to Advanced > Terminal or run adb shell on your PC.
If you really can't use TWRP or another custom recovery for this you can also try the following methods at runtime if your ROM is rooted.
Do this at your own risk.
If you can't take a TWRP backup of persist, e.g. because it is unmountable:
cd /sdcard; backup=persist_$(date +%Y-%m-%d_%H-%M-%S)_broken.img
dd bs=64k if=/dev/block/platform/msm_sdcc.1/by-name/persist | gzip > "$backup".gz
sha256sum /dev/block/platform/msm_sdcc.1/by-name/persist "$backup".gz > "$backup".sha2
To restore:
(gzip -d | dd bs=64k of=/dev/block/platform/msm_sdcc.1/by-name/persist) < <backup>.gz
sha256sum -c <backup>.sha2
Copy the backup to your PC now to make sure you don't lose it on accident!
These methods were tested with TWRP v3.4.0-0
Method C) Repair the filesystem on persist
- This may or may not work. This can help if you get the TWRP error Failed to mount '/persist'​- Make sure that Persist is unchecked in the Mount section in TWRP.​e2fsck -f /dev/block/platform/msm_sdcc.1/by-name/persist​If e2fsck asks questions you don't know how to answer cancel with Ctrl+C and ask someone for help. Otherwise just try whatever is available, restore your backup and try again if needed.​mount /persist (this should give no errors)​- Reboot​Method D) Restore file permissions
- This may or may not work. This only works if persist is mountable.​- It is possible that this method works better at runtime on a rooted ROM.​- If you want to know what file contexts are​mount /persist (this should give no errors)​restorecon -R /persist/sensors/ /persist/sns.reg​chmod u+rwx /persist/sns.reg; chmod 775 /persist/sensors/; chmod u+rw /persist/sensors/*​- Reboot​It is recommended to try the following methods with OxygenOS 3.1.4 installed. Not all custom ROMs are able to regenerate sns.reg
Method E) Delete sensor related files from persist
- This may or may not work. This only works if persist is mountable.​mount /persist (this should give no errors)​rm -fr /persist/sensors/ /persist/sns.reg​- Reboot​Method F) Reformat persist, if all else fails, known to work
This method was tested to fix sensors without creating obvious issues but wiping persist could have unknown side-effects in the long run.
Only do it if you have to. Make sure you know what persist if used for so you can recognize possbile issues if they occur and keep your initial backup around.
- Tested with OxygenOS 3.1.4 and TWRP v3.4.0-0​- This will get you a completely fresh start. This helps if you get the TWRP error Failed to mount '/persist'​- Make sure that Persist is unchecked in the Mount section in TWRP.​make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist​reboot​- Note: Recent TWRP builds for the OnePlus X store settings in /persist/.twrps and /sdcard/TWRP/.twrps and will reset when wiping both at the same time.​
That's it!
Remember to take a backup of EFS and Persist now if everything is working or restore the backup you took at the start if you're still having issues and want to try other solutions.