yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Original Android Development] cebs:
*****************************************
* BACKUP EFS *
*****************************************
WARNING: Do you wish to Continue? (This will make EFS BACKUP) [Y,N]?Y
--- STARTING ----
--- WAITING FOR DEVICE
--- Backup efs image ---
1046 KB/s (12857 bytes in 0.012s)
13 KB/s (40 bytes in 0.003s)
SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_

Creating filesystem with parameters:
Size: 14680064
Block size: 4096
Blocks per group: 32768
Inodes per group: 896
Inode size: 256
Journal blocks: 1024
Label:
FLEX_BG size: 0
Blocks: 3584
Block groups: 1
Reserved block group size: 0
Created filesystem with 92/896 inodes and 1451/3584 blocks
28672+0 records in
28672+0 records out
14680064 bytes transferred in 0.598 secs (24548602 bytes/sec)
su-mksh: busybox: not found
remote object '/sdcard/efs.img' does not exist
5028 KB/s (14680064 bytes in 2.851s)
remote object '/sdcard/SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9
005XXUBMI6_RF1D94P03GD_EFS.tar.gz' does not exist
bin/tar: efs.img: Cannot stat: No such file or directory
bin/tar: Exiting with failure status due to previous errors

7-Zip (A) 4.65 Copyright (c) 1999-2009 Igor Pavlov 2009-02-03
Scanning

SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_
EFS.tar.gz: WARNING: O sistema não conseguiu localizar o ficheiro especificado.

Creating archive SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9005XXU
BMI6_RF1D94P03GD_EFS.zip

Compressing getprop.txt
Compressing SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9005XXUBMI6
_RF1D94P03GD_EFS.raw.img
Compressing SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9005XXUBMI6
_RF1D94P03GD_EFS.tar.md5

WARNINGS for files:

SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_
EFS.tar.gz : O sistema não conseguiu localizar o ficheiro especificado.

----------------
WARNING: Cannot find 1 file
-
-
Finished. Output file is SM-N9005ZKETPH_N9005XXUBMI6_RF1D94P03GD_SM-N9005ZKETPH_
N9005XXUBMI6_RF1D94P03GD_EFS BACKUP
Prima qualquer tecla para continuar . . .
[Galaxy Note 3 Original Android Development] kryz70fr:
same error for me ...

su-mksh: busybox: not found

remote object '/sdcard/efs.img' does not exist

and now, i have a lot of SM_output_file in the sdcard directory, it is safe to erase them ?

Edit : It's ok now, i just retry ...
[Galaxy Note 3 Original Android Development] tonime:
I lost efs folder.

The solution is to restore efs.tar with Odin. I have a copy of efs.tar with Root Explorer, but someone knows how to do it?
[Galaxy Note 3 Original Android Development] deom2i:
Guys,

What is the best way to backup EFS?
[Galaxy Note 3 Original Android Development] Chalao:
Use EFS Professional v2.0.70 and you will be safe, stay away from the tool promoted in this thread as it is broken.
[Galaxy Note 3 Original Android Development] sewe:
What to do when it's stuck at Initialising adb server?

We are many that can't make a backup because of that

SM-N9005 via Tapatalk 2
[Galaxy Note 3 Original Android Development] ProxyChain:
Can anyone confirm if /efs backups made with TWRP are suitable for restore/working fully? I've made about 3 different backups with various programs but I'm unsure if any of them will work in event of /efs loss, since I'm not able to get the EFS Tools program to work.
[Galaxy Note 3 Original Android Development] deom2i:
Im also stuck on Initializing ADB server.....!! im i missing something?
[Galaxy Note 3 Original Android Development] prank1:
Same here, stuck on initializing adb server

I accept the RSA key request thing but still gets stuck on this problem. No matter what I try it's never gone past this message
[Galaxy Note 3 Original Android Development] A.S._id:
Why criticize what you do not understand? This is the same as in the fable of the monkey and glasses. Check first whether the general connectivity adb ..
[Galaxy Note 3 Original Android Development] prank1:
The program you wrote seems to connect fine without any problems.

But this "adb server is initialising" problem is regarding the EFS Backup Pro program, found in another thread
[Galaxy Note 3 Original Android Development] galaxys2jax:
EFS Backup works for me and I like to share what I have done to work​

Step#1:

Install Busybox in your device! from Play Store

Open application and Grant permission from SuperSu.

Step#2:

Enable Developer Mode - Goto "Settings", press "General" tab, press "About Device", press "Build number" seven consecutive times and you should get messages about having "Developer Mode" being turned on.

Hit back and you should now see "Developer options" selection in the menu. Press "Developer options" and check mark "USB debugging".

Step3:

Connect your device to the computer/Laptop using USB

Step#4:

Download the Zip file for your model SAMSUNG NOTE 3 EFS BACKUP/RESTORE and extract it to a specified folder.

Step#5:

Open EFS-BACKUP.bat file (as administrator), Press 1 (backup) >> then Press Y (confirm)

Step#6:

Now look on your device screen, ABD shell might be asking you root permission in SuperSu, Press Grant.

Congrats, you will see a long named file under the EFS extracted folder.:good:​
[Galaxy Note 3 Original Android Development] mirek190:
Ehhh you do not understand ....

Efs backup needs copy 3 partitions.

This program doing a copy only from one partition ....

Evan if you even have copy from those 3 partitions is still useless.

Not working after recover ....
[Galaxy Note 3 Original Android Development] galaxys2jax:
Can you explain more in detail? What to do you mean by 3 partition?

What's the successive method?

Have you tried this: EFS Professional v2.0.70 - With Qualcomm NV Tools!
[Galaxy Note 3 Original Android Development] mirek190:
Look here

http://xdaforums.com/showthread.php?p=47586640

EFS Professional doesn't work with note 3 at all. I

tried - works with my S2 , note 10.1 but not with note 3.
[Galaxy Note 3 Original Android Development] Chalao:
Before starting, check the following:

Device is fully rooted

SuperSU (or equivalent) is active

USB debugging is ON (Settings->More->About device: Tap several times on "Build number" to enable Developer options and tick USB debugging)

Busybox downloaded AND installed (normal or smart) on your device

Microsoft .NET Framework 4.0 installed on your PC

Samsung USB driver is installed (either by installing Kies or just the driver alone.

Kies is not active (neither as application nor process, check Windows Taskmanager)

ADB fully functional ("adb devices" recognises your phone) -- (look here for a basic ADB tutorial/how to)

In case ADB is not running you need to install the ADB driver

Run EFS Professional as administrator.

Make sure to grant SuperSU access to Shell and confirm the RSA fingerprint request once they pop up on your screen.

Of course, your device should be on the home screen, not on the lock screen ;)

Now you should be able to access the features of the programme and make an EFS backup.
[Galaxy Note 3 Original Android Development] galaxys2jax:
Result is same

I checked everything, Still have same issue
[Galaxy Note 3 Original Android Development] prank1:
Have you actually gotten this program to work on your N9005?
[Galaxy Note 3 Original Android Development] red_brindle:
+1 cannot pass thru that screen :(
[Galaxy Note 3 Original Android Development] mirek190:
And still not work with note 3 ....

On the other my Samsung devices work fine.

Maybe is problem with SELinux

kernel ?

On my other devices I have normal android kernel not SELinux android kernel.
[Galaxy Note 3 Original Android Development] Khizar:
I used this when I was completly stock and rooted, it worked perfectly and backed up my efs.

PS - IF you have a n9005 backup the efs in twrp.. I restored it there as well LOL
[Galaxy Note 3 Original Android Development] Chalao:
I did some tests, it seems SELinux status needs to be set to either permissive or disabled. It does work on Stock JB 4.2.2 and below as well as on CyanogenMod.

Of course, another option is a custom recovery backup.
[Galaxy Note 3 Original Android Development] cosmote:
Solve the problem:

1. Download and flash original software prerooted. Not turn on the phone

2. Donwload and flash from sdcard Brick Loop FIX after Restoring Backup

3. Follow the steps for backup from EFS backup tutorial

4. Flash original rom stock , without turn on the phone - put in download mode

5. Restore backup EFS (from step 3)

That's all. The phone works perfectly!!! :highfive:
[Galaxy Note 3 Original Android Development] galaxys2jax:
You mean here:: http://xdaforums.com/showthread.php?t=2507403

If the op edit his post by giving the above reference will do more better to other user.
[Galaxy Note 3 Original Android Development] iGebriel:
what this means !!!!!!!!!!!!
[Galaxy Note 3 Original Android Development] Rukbat:
I didn't check through all 21 pages, but it works on the infamous N900A, the AT&T "locked, welded and glued" model. I don't know if the backup is usable (I haven't studied this enough to know what to look for in the .tar.md5 file), but it's there, and it recognized the model of the phone.
[Galaxy Note 3 Original Android Development] brockyneo:
hi guys ive done a backup through this and through aroma (omega rom) but i think ive corrupted my efs everything is ok but wifi with the 2 back ups i have how do i flash the backup on my phone its driving me crazy now been at it 9 hours heelllpp lol
[Galaxy Note 3 Original Android Development] prank1:
I wonder if the EFS fix from this thread will help you; practically everyone is reporting success when they flash this zip in recovery.

That's assuming your problem is related to the EFS; something wrong with the kernel can result in loss of WiFi. If other things like phone, mobile internet works then it's probably not related to the EFS and I would try flashing the ROM again.

But if it is related to the EFS try this:

http://xdaforums.com/showthread.php?t=2507403

Try it and please reply if it works or not
[Galaxy Note 3 Original Android Development] brockyneo:
i read somewhere that random lock ups ect can be from a currupt file is efs so i tried flashing my backup and flashed stock rom thats where my problem started i dont think its rom or kernel as ive tried about 5 roms with all wipes ect all the same
[Galaxy Note 3 Original Android Development] prank1:
Did you try flashing the EFS Fix found in this thread:

http://xdaforums.com/showthread.php?t=2507403
[Galaxy Note 3 Original Android Development] brockyneo:
yes just done it still no good im totally out of ideas now :crying:
[Galaxy Note 3 Original Android Development] prank1:
Do you have an IMEI? Can you still make calls / use mobile internet
[Galaxy Note 3 Original Android Development] brockyneo:
ya i have IMEI and still make calls and use mobile internet just not wifi and its since i tried flashing efs backup and returning to stock
[Galaxy Note 3 Original Android Development] prank1:
Think your motherboard is messed up

If I were you and I had truly ran out of options I would:

Flash stock ROM through KIES emergency mode then send to Samsung for repair. If they tell you the warranty is void because of 0x1 either play the dumb card or say the phone has been restored to fully stock and the problem is still there, therefore it is a hardware problem. Although if you are not in Europe their blanket voiding statement may apply, in which case the dumb card may be a better option.

By the way, what exactly did you do before you ended up getting this problem?
[Galaxy Note 3 Original Android Development] brockyneo:
lol ya i thought it might be just strange its worked fine till i did that i even have my wifi mac adress still and wifi switches on and find networks and put password in then it freezzes and say cannot conect to network
[Galaxy Note 3 Original Android Development] prank1:
Try connecting to a friends router. Maybe the problem is with your router? Unlikely but might as well try and rule it out.
[Galaxy Note 3 Original Android Development] brockyneo:
WELL FINALLY DONE IT :victory::victory::victory:

all this time i needed to install busybox then flash the efs back on the phone and to might mighty supprise i now have working wifi just when i pritty much give up hope and was going on ebay ha ha

thanks guys for all your help
[Galaxy Note 3 Original Android Development] prank1:
That's great. Did you restore using the EFS using the program in this thread?
[Galaxy Note 3 Original Android Development] brockyneo:
ya i backed up with this tool from the begining and used it to restore i selected option 4 and it flashed the efs file back on

think the key to most peoples problems is busybox make sure its installed as well as the usual (usb debugging ect)
[Galaxy Note 3 Original Android Development] cassinni:
I had adb running but it couldnt find a device. all the other stuff i did. This tool cant find my phone i guess..

how do i make adb find my cell and does that tool always have to run?

its weird cos win 8.1 x64 finds my phone once its connected.
[Galaxy Note 3 Original Android Development] Chalao:
WARNING: Do not use the programme promoted in this thread!

It will backup your EFS incompletely and the backup is useless if you want to restore your EFS partitions later. I had my N9005 bricked and the backup I made before was useless and didn't work at all, I also saw other users making the same experience. Just stay away from it.

EFS Professional v2.0.70 is only an option if you are running on JB 4.2.2 or below with SELinux status set to permissive. If you have a locked bootloader (MJ3 firmware and above), downgrading will trip Knox 0x1 and your warranty is void.

You can also do a backup using a custom recovery but flashing it will also trip Knox 0x1.

If you don't care about Knox and have already tripped it then just do a backup with TWRP or CWM as it is the easiest way to restore your EFS in case you need it later at some point.
[Galaxy Note 3 Original Android Development] cassinni:
Thanks bro. Does titanium backup pro do efs backups?
[Galaxy Note 3 Original Android Development] Moscow Desire:
A note about development.

As with ALL development tools, ROMs, kernels, Root, Recoveries, etc, When you use these tools, there is always a chance things don't go well. Trust me, I've bricked a new tablet before, so I know.

We ALL know the risks when doing these things. If you are not prepared to take the risks, then don't do it. Nobody is forcing you to.

Although Dev's usually try and minimize the chances of a bricked device, the risk still remains. This is inherent with most tools.

I've had a report to close this thread due to bricked devices. From what I've seen, I really haven't seen a lot of bricked devices, but more so some refinement of the app itself. (busybox, USB Debug, improper naming of file)

At this point, I am inclined not to close the thread based on what I've read. Seems the tool works for most people (with some changes). However, any more bricked devices and I might change my mind.

Be Aware of the RISKS before you use the tool. If you'e not prepared, then Don't do it. Simple.

MD
[Galaxy Note 3 Original Android Development] brockyneo:
Well I backed up with this app and I've just restored with the app too after I corrupted my efs and it's went fine the mistake I was doing was not having busy box installed when running the app I've done a backup through aroma and twrp just to be safe but as far as I'm aware when used properly the app seems to work or at least for me
[Galaxy Note 3 Original Android Development] prank1:
I believe the author of this program deserves some credit at least, it has helped brockyneo fix his device.

For other EFS related problems, the infamous EFS fix tool would probably sort it out.

Would it be safe to downgrade from MJ7 to MJ3 via Odin? With how sensitive the EFS partition seems to be, I could easily see a downgrade borking the EFS partition in the process. Although the EFS fix tool would probably fix it.
[Galaxy Note 3 Original Android Development] Ratata82:
Can anyone post the FactoryApp folder?? I have one here, which misses the entire folder...

Thx
[Galaxy Note 3 Original Android Development] brockyneo:
Maybe a tip in the op a guide on what to do before using app ie installed busybox when backing up and restoring and use debugging the usual stuff

When I get back home I'll write what I did and see if it helps others as I was at it for about 9 hours lol

had great help from others I must say :laugh:
[Galaxy Note 3 Original Android Development] Chalao:
Sorry mate, it doesn't. You can do a lot of nice things with Titanium but not backing up your EFS.

I am happy for you that it worked in your case. If you have a bricked device rebooting every 20 seconds or so with unknown baseband and IMEI gone etc. like [MENTION=2198172]mirek190[/MENTION] (also look at his post for further info), [MENTION=2272159]atinder[/MENTION], [MENTION=2120161]sushiii[/MENTION] and other users in this thread including myself, the restore does not work as the backup appears to be incomplete.

If you're not rooted with Root de la Vega and, thus, running MJ7 with a locked bootloader (introduced with MJ3), I would not dare trying to downgrade using Odin. What is better with MJ3 than with MJ7 and to which EFS fix tool are you actually refering? From what I've seen, the safest option so far to backup and restore successfully EFS is a NANDroid using CWM or TWRP.
[Galaxy Note 3 Original Android Development] A.S._id:
Im used this method of backup and restore on device

I9000

P1000

I9300

N7100

I9500

I9505

N900

N9005

and never heard that this method can turn any devices into a brick. Your case first. Maybe it's just a series of coincidences?
[Galaxy Note 3 Original Android Development] prank1:
Sorry, I misread; I thought MJ3 was 4.2.2 and hence had a permissive kernel.

I am currently running a 4.3 Custom ROM (so is rooted and 0x1), however it came with stock MJ7 pre-installed.

How can I safely downgrade to 4.2.2 in order to be able to use EFS Professional ?

Also CWM doesn't back up the EFS.

And TWRP restore seems to cause a problem with the EFS partition - that can be fixed with that flashable zip, but is this what you'd do to restore your EFS?
[Galaxy Note 3 Original Android Development] raitospk:
So can backup EFS?
[Galaxy Note 3 Original Android Development] revized:
my main purpose fis to use cdmaws or dfs using get diag mode on a sm-n900t

i just wanted to ask before i started this bat, i wanted to just do 2 things , now 3 with the esf backup.

already done

1.) http://xdaforums.com/showthread.php?t=2470551&page=5

ran [APP][2013.11.04] RegionLock Away v1.3 [ROOT]

inserted verizon sim and everything seems fine.

2.)http://www.note2forum.com/forum/gal...dden-menu-dialer-verizon-galaxy-note-3-a.html

this is where i suppose i wanted to set *#9090#* to say diag config "enabled"

so now i am at xda becasue the tut said

It is also Recommended that you Backup your "EFS" Partition before making a changes. Thanks for the Reminder -> grenefroggie

anywho , using a xp 64 bit i7 ;) ssd it hangs on the second thing i forgot what it was after starting deamon and port , and since i cannot install sp3 on my os and therefore kies 3 wouldnt install so i am going to try using my win8 laptop although it started to install updates upon boot of win 8 (lol worst os ever)

i just read almost all the post in this thread and wondered since i already ran RegionLock Away v1.3 [ROOT] and when running this efs bat it will not have a sim inserted just incase , is it still safe to try a efs back up after using RegionLock Away v1.3 ?

oh well couldnt wait , everything worked on laptop right away.installed kies 3 & USB_Drivers_1.5.27.0 then ran bat & allowed usb debugging & super user request on cell ,said finished ok

thanks OP ! now off to try and unlock hidden menu command changes ! ;)
[Galaxy Note 3 Original Android Development] h3nyr:
thank you for making this great software! I just backup my efs tyty
[Galaxy Note 3 Original Android Development] mirek190:
You should change ( fix ) your program.

WHY ?

I'm explaining :

Qualcomm devices not keep imei number in EFS !!!

Your program copying just efs...

Exynos devices keeping imei in efs but no qualcomm devices.

Qualcoom devices keep imei number in modemst1 and modemst2 ( mmcblk0p12 and mmcblk0p13 )

Efs partition keeps only sn number, bt number or wifi nunber - nothing more imaportant. ( qualcomm devices - n9005 )

At the moment your program is completely useless .

I know what I'm saying - I had completely broken note 3 for two months

http://xdaforums.com/showthread.php?t=2567133

I bought the other one and was trying to repair old one.

Even if you wipe out efs partiotion you just lost sn, bt and wifi numbers ONLY but no IMEI .

Even if you check iin Odin wipe efs imei still remain why ?

It is simple imei it is not in efs ! on qualcomm devices !
[Galaxy Note 3 Original Android Development] revized:
I got n900t, some place says ',*Qualcomm*Snapdragon 800 MSM8974AB, 2265MHz CPU

Does this mean even though this app showed no error that it did not actually back up correctly? Also is it correct that a cwm nandroid backup does not do complete job? I did both and wonder if it was worthless to plan on using these methods as a working restore?

thanks
[Galaxy Note 3 Original Android Development] thermax04:
Note N9005 with root MJ7

the backup file is 274KB!! is this right?!!

during the task the app wrote 1 file is not exist?!!

---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------

how i can get this log to show my error?
[Galaxy Note 3 Original Android Development] mirek190:
Wrothless is only efs backup.

Qualcomm devices store imei in mmcblk0p12 and 13 .

Mmcblk0p11 is for wifi , bt, and SN number NOT FOR IMEI !
[Galaxy Note 3 Original Android Development] Untraceable:
Thank you for this information

but how we can backup the IMEI number for qualcomm devices N9005 ???????
[Galaxy Note 3 Original Android Development] mirek190:
Easily - just backup mmcblk0p11 ( sn,bt, mac) and mmcblk0p12 and mmcblk0p13 for imei through dd ( someone can make a script )
[Galaxy Note 3 Original Android Development] !crazy:
Do you have any info if TWRP backups those correctly on 9005?
[Galaxy Note 3 Original Android Development] revized:
So your suggest someone need to make a script to back up imei , currently no available method to back up imei without script?
[Galaxy Note 3 Original Android Development] mirek190:
I think k TWRP copy should be OK. Because copy 3 partitions 11, 12 and 13.
[Galaxy Note 3 Original Android Development] dhangejr:
anyone try this on a note 2? I can't get any option to work for efs back up on note 2. I been throughout the google guy's results driving me nutz as I wanna flash w/o worrying!
[Galaxy Note 3 Original Android Development] quebec1:
is possible receive this app for Galaxy i9300 international?

the app efs don't start with New android 4.3

sorry for my english
[Galaxy Note 3 Original Android Development] playermty:
this tool works on n900w8?
[Galaxy Note 3 Original Android Development] SonicSamZ:
I ran it on my SM-N900W8 (stock, rooted, MJ1) and a file was generated but the app window said "1 file not found".

Don't have the log as I'm not home now.
[Galaxy Note 3 Original Android Development] revized:
http://xdaforums.com/showthread.php?t=1308546

???????????????????????????????????????????????????????????

Nough said ;)
[Galaxy Note 3 Original Android Development] Dan_Aykroyd:
So... is this safe and actually work to backup/restore efs on a SM-N900?

Thanks
[Galaxy Note 3 Original Android Development] darkelfa2:
2 missing files

hello everyone

i tried backing up my efs but the command window tells that it can't find 2 files, i also tried using terminal emulator on the phone but got "permission denied"

i'm running probam at the moment, there was mistake in the rom where the model number says n9000 while its actually n9005 if that make any difference, i attached the command window below.

edit: i just flashed TWRP recovery and did a backup which seems that it works.