[Q] Problem with EFS Pro & GT-i9300 - General Questions and Answers

Hello,
i've tried to backup the EFS Partition of my new Galaxy S3 with EFS Pro v1.8.3. My Busybox version is 1.20.2.
While trying to backup I get the following error:
Code:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'mountpoint:'
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!
Device-Info:
Code:
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
ROM Build: m0xx-user 4.0.4 IMM76D I9300XXALE8 release-keys
Android Version: 4.0.4
BusyBox Version: 1.20.2-Stericson
SU Binary Version: 0.91:SUPERSU
I tried to post in the EFS Pro Thread, but I don't have ther permission to.
So maybe you can help me here?
Yours
Cryptomaniac

I also get this too!

I have the same problem:
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
ROM Build: m0xx-user 4.0.4 IMM76D I9300XXALE8 release-keys
Android Version: 4.0.4
BusyBox Version: 1.20.2-Stericson
SU Binary Version: 0.93:SUPERSU
This error shows up when I choose the img format: (on local and device backup path)
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'mountpoint:'
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!
When I choose the tar format or disable the MD5 check the procedure runs through but only creates a faulty file with about 4k size:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Copying EFS Backup To PC Storage... Okay.
Copied: remote object '/sdcard/EFSProBackup/EFS_201275_185620.img' does not exist
Deleting Temporary EFS Backup From Device... Okay!
Operation Finished!
any help is much appreciated

the new version fixed the problem for me
EFS Pro v1.8.6 has now been released!
Improved Nexus S / Galaxy Nexus Support and fixed the bug that caused the detection of the partition location to fail for some devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1308546

I am facing some issues with my Galaxy Note, I can't write in EFS Pro thread too. I backup my efs with EFS Pro. Now my imei become null and baseband unknown because of flashing roms. I can't restore backup, it show mount point error. Someone help me.

EFS Pro 2.0.12: Unable to Create Archive
I am a new user to EFS Pro, and am using v2.0.12. I tried other older versions, and am getting the same error, and that is when I start the backup, I get an error that it cannot create the archive.
My S3 Tmobile (SGH-T999) is rooted and currently running CM10.1 1/24 nightly. I also enabled USB & ADB debugging. The program accesses the phone OK, it seems that the problem is just in the final saving of the file.
I thought perhaps it was a permission issue with the program not being able to write to my disk, however I have it running with Administrator privileges. I'm stumped. Oh and my O/S is Windows 7 Pro, 64-bit.

grogargh said:
I am a new user to EFS Pro, and am using v2.0.12. I tried other older versions, and am getting the same error, and that is when I start the backup, I get an error that it cannot create the archive.
My S3 Tmobile (SGH-T999) is rooted and currently running CM10.1 1/24 nightly. I also enabled USB & ADB debugging. The program accesses the phone OK, it seems that the problem is just in the final saving of the file.
I thought perhaps it was a permission issue with the program not being able to write to my disk, however I have it running with Administrator privileges. I'm stumped. Oh and my O/S is Windows 7 Pro, 64-bit.
Click to expand...
Click to collapse
I have the same problem. Help please. Thanks!
Edit: solved the problem downgrading busybox to the latest stable version.

BrMBr said:
I have the same problem. Help please. Thanks!
Edit: solved the problem downgrading busybox to the latest stable version.
Click to expand...
Click to collapse
I have the same issue, but the busybox change didn't help
Device Info:
---------- Hardware Information ----------
Connected Device SN.: 3832E63FECEC00EC
Device Manufacturer: SAMSUNG
Device Model: GT-I9000
Product Code: GT-I9000HKDKOR
Hardware Version: MP 0.800
---------- Firmware Information ----------
PDA Version: I9000XXJVQ
Baseband Version: I9000XXJVQ
CSC Version: I9000OXAJVQ
---------- Software Information ----------
Kernel Release: 2.6.35.7-I9000XXJVQ-CL281085
Kernel Version: #DarkCore_2.9.2_JVQ PREEMPT Sat Jul 23 19:19:57 EEST 2011
ROM Build: GT-I9000-user 2.3.4 GINGERBREAD XXJVQ release-keys
Android Version: 2.3.4
BusyBox Version: 1.20.0-Stericson
SU Binary Version: 2.3.1-ef
LOG
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Okay.
Checking backup folder location... Okay.
Backing up selected partition(s)...
Creating archive: GT-I9000_201366_154523.tar.gz...
Operation failed!
Any Idea ?

Related

[Q] EFS Professional backup PROBLEM

I have been trying to backup the efs folder on Samsung galaxy Music GT-S6010 using EFS Professional v2.0.62 and when the software is "Extracting PIT from device for mapping ..." it shows "operation failed" and gives a prompt showing it was "Unable to extract PIT from device!".
I have attached a screenshot of the issue, anyone kindly help.
Similar problem on Galaxy S GT I9000, MORE DETAILS given
Hello,
I have a problem with EFS Professional. I searched the development thread (http://forum.xda-developers.com/showthread.php?t=1308546) and googled it as well. Although some solutions were offered my problem is not solved. I am not a complete newbie but not an expert either, so maybe I have a really simple issue here?
I am simply trying to backup the EFS partition on Samsung Galaxy S GT I9000.
The problem in short:
1. All seems to be well on welcome tab.
2. While running the backup, I get “Unable to read PIT file!” and the process stops.
3. If I run it again it skips the PIT file part saying “Skipped, already exists.” And then a popup shows saying “unable to create archive!”
4. Note: a tar.gz file is actually created and placed in a new EFSProBackup folder on the phone under /mnt/sdcard. The size of this file is only 29 Bytes and I think its basically an empty file).
Note that I did change my Busybox to version 1.20.0.git (but not 1.20.0 if it makes any difference?) as was suggested).
Can anyone help?
Please see a detailed description below.
Many thanks!
Detailed description:
• Using Windows XP
• EFS Professional 2.0.70
• Busybox 1.20.0.git
• Samsung USB Driver: 1.5.27.0_2
• Firewall – OFF
• USB Debugging – ON
• Mass Storage – OFF (I tried it with Mass Storage ON as well and it gives only the result as in step 2 described above no matter how many times I run it)
• Unknown Sources (if at all relevant) – ON
• Allow mock locations (if at all relevant) - ON
EFS Professional selections, logs & popups:
Welcome tab:
Log:
Checking application environment... Okay.
Initializing ADB server... Okay.
-----------------------------------
Performing device checks...
-----------------------------------
Root status: Perm Rooted.
SU binary version: 3.1.1
-----------------------------------
BusyBox status: Installed.
BusyBox binary version: 1.20.0.git
-----------------------------------
EFS Professional is ready for use.
-----------------------------------
Backup tab:
• device filter set to “*** All Partitions ***”
• selected the (only) one EFS partition found: /dev/block/stl3
• Pressed Backup
Log:
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Okay.
Operation failed!
A popup comes up saying: “Unable to read PIT file!”
• When I press Backup again
Log:
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
Creating archive: GT-I9000_20130928_114424.tar.gz...
Operation failed!
A popup comes up saying: “Unable to create archive”
Efs backup
Try online Nandroid backup app. It will back up everything including the EFS folder.
Perfect!
It's so much simpler and works like a dream! I just hope it will work as promised if anything goes wrong while flashing a new ROM!
Many thanks for your reply!
:good:
backup IMEI on galaxy ace 2 i8610
Hello
I have the same problem with my galaxy ace 2 i8610
I get a popup shows saying “unable to create archive!”
Does anyone can help me ?
Thanks
---------- Post added at 03:38 AM ---------- Previous post was at 03:29 AM ----------
Hello
I have a galaxy ace 2 i8610 and when I try to backup on EFS pro 2.0.70, I get this message :
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
Creating archive: GT-I8160_20131105_101505.tar.gz...
Operation failed!
Does anyone can help me ?
Thanks[
efs professinal erorr!
hiii....I was backuping my efs or radio's data from tablet n8000 but today i see this erorr!!! my efsprofessinal is in c:\ and adb devicse is working!!please guide mi...tanks

[Q] Help needed to restore bricked/dead N9776 MT6577 phone

Hi XDA members,
Some help needed here to restore/revive my dead smartphone. Here's some information that I was able to get from MTKDroidTools before it went dead:
Hardware : MT6577
Model : e1911_v77_gq2000_a41_6628_v20
Build number : e1911_v77_gq2000_a41_6628_v20_20130424
Build date UTC : 20130424-072257
Android v : 4.1.1
Baseband v: MAUI.11AMD.W12.22.SP.V15.P2, 2012/12/24 13:28
Kernel v : 3.4.0 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Apr 24 15:19:34 CST 2013
Click to expand...
Click to collapse
I believe the phone is Ulefone / Star N9776 though the site that I purchased from stated it as Triton Pad 6": http://www.lightinthebox.com/i9977-mt6577-android-4-0-dual-card-quand-band-6-0-inch-cpacitive-touchscreen-cell-phone-wifi-fm-gps-3g_p520179.html
Here's the chronology of what I've done 'til the phone went dead:
- Rooted the phone using Kingo Android Root
- Added CMW Recovery using MTK Droid Tools (v2.4.5)
- Made a backup via MTK Droid Tools
- Tried to flash a LEWA ROM provided on http://forum.xda-developers.com/showthread.php?t=2260653 via SP Flash Tool (v3.1312), but can't get the phone to work (boot loop on Android animation)
- Tried to recover from backup created by MTK Droid Tools inside clockworkmod folder via CWMR, but got MD5 sum error
- Tried some more Star N9776 ROMs found on NeedROM site via SPFT, with no luck
Somewhere in this process, I've clicked on the Format Whole Flash without realizing what I was doing
- Phone completely bricked/dead! Unable to access CWM recovery mode, battery charging unrecognized.
Additional note, I still have the full backup that was created by MTK Droid Tools on my PC, about 2 GB in size. Tried to create blocks for SPFT but it gave errors. Here's the report:
The signature isn't found! ... File Size Too Small!
-- DSP_BL: md5 OK; ... it is copied ... cut OK
-- MBR: md5 OK; ... it is copied
-- EBR1: md5 OK; ... it is copied
-- pmt: md5 OK;
-- userdata_nvram_only.ext4.tar: md5 OK;
-- seccfg: md5 OK;
-- uboot.bin: md5 OK; ... it is copied
-- boot.img: md5 OK; ... it is copied
-- recovery.img: md5 OK; ... it is copied
-- secro.ext4.tar: md5 OK;
-- misc: md5 OK;
-- logo.bin: md5 OK; ... it is copied
-- expdb: md5 OK;
-- system.ext4.img: md5 ERROR;
-- system.ext4.tar: md5 ERROR;
-- cache.ext4.img: md5 ERROR;
-- cache.ext4.tar: md5 OK;
-- data.ext4.img: md5 ERROR;
-- data.ext4.tar: md5 ERROR;
--- copying is complete ---
Click to expand...
Click to collapse
My last resort to resolve this problem which is to push up a stock ROM provided by yuweng (http://forum.xda-developers.com/showthread.php?p=37157380#post37157380) via SPFT gave me no luck either. I've always got this BROM 3004 error stating that my phone doesn't support DRAM
Help and assistance from experienced members is greatly needed, hopefully those who have a phone with similar specs to mine. Thanks!
have you tried a higher version of sp flash tool?

Tab 7.7 Restars every 5 minutes. Deleted data reappears after restart.

Dear All,
I am using Samsung Galaxy Tab 7.7 (GT-P6800) with the below Items :
Android Version : 4.1.2 (Jelly Bean)
Baseband Version : P6800DXMD3
Kerner Version : 3.0.31 - 1157844
[email protected] - 133 #3
SMP PREEMPT MON APR 22 22:19:00 KST 2013
Build Number : JZO54K.P6800DXMD3
EMMC Type : MAG2GA
CID : 1501004d4147324741076f07993b5f91
Revision : 0X7
The EMMC data has been extracted from gotbrickbug app.
Also I was using Framaroot 1.5.3 with the Aragorn exploit and was using gamehacker application and lucky patcher. Some days before I did framaroot exploit and forgot to unroot the device and kept the device idle for some time. After a while, my device got restarted automatically and after that it is working in weird fashion. Whatever I delete reappears and what ever i add is getting deleted once i restart my device. Also the device is restarting every 5 minutes once. I installed various applications to find whether my device got the EMMC Bug but most of the applications didn't gave any error. Then I looked into the MAG2GA Trim bug and it looks like I had got one as some of the mp3 files gets corrupted now and then for a while. So it looks like memory is getting corrupted for some or the other reason. I tried to flash Samsung Stock version of Jelly Bean and Honey Comb. Odin gave success message but no change happened. Looks like the EMMC is in read only mode. I tried SU and mounted my /system with read write mode and restarted the device. But nothing happened after that also. I tried factory reset / wipe data / wipe cache partition but nothing is working. Also in recovery mode I am getting a line in Red color : "did not match sized '/system/csc/common/system/cc/others.xml'(No data available)". I went to this path via su and found the file was present. I tried to install TWRP, CWM etc., but everything got erased once i restarted my device. Is there any way where I can get my tablet in working condition other than hardware change.
I tried installing cyanogenmod through sdcard from recovery mode but I am getting difference in signature as I am not able to install CWM / TWRP to change that.
Hoping for a valuable feedback.
Regards,
bhaarn.

EFS Pro 2.1.80.0 All Backup Functions don't work

Open EFS Pro, starts up....
Checking application environment...
-----------------------------------
Terminating process: adb.exe, PID: 7204 ...
Initializing ADB server... Okay.
ADB server is running!
Searching for device... Okay.
Connecting to device... Okay.
Checking device status... Okay.
-----------------------------------
Performing device checks...
-----------------------------------
Root status: Perm Rooted
SU binary version: 3.26:kinguser_su
-----------------------------------
BusyBox status: Installed
BusyBox version: 1.20.1-Stericson
Checking BusyBox applets... Okay.
-----------------------------------
EFS Professional is ready for use.
-----------------------------------
Device info works and displays:
---------- Hardware Information ----------
Connected Device SN.: S567018180b68
Device Manufacturer: SAMSUNG
Device Model: GT-S5670
Product Code: GT-S5670PWATHR
Hardware Version: MP 0.301
---------- Firmware Information ----------
PDA Version: S5670JPKQ7
Baseband Version: S5670XWKQ4
CSC Version: S5670OJPKQ4
---------- Software Information ----------
Kernel Release: 2.6.35.7-perf-CL577623
Kernel Version: #1 PREEMPT Sun Sep 18 18:34:47 KST 2011
ROM Build: GT-S5670-user 2.3.4 GINGERBREAD JPKQ7 release-keys
Android Version: 2.3.4
BusyBox Version: 1.20.1-Stericson
SU Binary Version: 3.26:kinguser_su
When I select 'All Partitions' in device filters, I get the following messages:
Enumerating device partitions...
Extracting PIT from device for mapping... Skipped, already exists.
Checking PIT file integrity...
Operation Failed!
This is stock ROM for Galaxy Fit GT-S5670. I want to make sure I can correctly backup my IMEI and the EFS data before pushing modified ROM image to the device. I used mobogenie to do initial push of .apk files for rooting, and also ran the Mobogenie ROOT tool.
On EFS Pro (Beta) (couldn't find a stable OLDER version...I would like to try an old one.) I go to the Backup Tab, and under device filters I don't see my version of Samsung Galaxy FIT In the Manage section of device filters. Anytime I try to do anything with the Device Partitions or Device Filters I get the message: Number was less than the array's lower bound in the first dimension. Parameter name: srcindex
Please advise me if this is just a dumb question of a newbie?

How To Guide [Tutorial] Recover from IMEI or GPS not working due to corruption (restoring efs and sec_efs)

I was trying to enable the privacy wifi feature that changes the MAC address of the wifi adapter on every connection (see https://github.com/phhusson/vendor_hardware_overlay/pull/610 as an alternative to https://github.com/Magisk-Modules-Alt-Repo/MacRandomizationEnabler).
While doing this, I encountered an issue that all of a sudden, the phone would not connect to cellular (IMEIs were gone) and GPS would not work anymore. This is quite frustrating and could essentially render your phone unusable with respect to its main functionality.
I was not aware of the fact an efs backup is required. However, I had backed up efs and sec_efs right after the problem.
I also found that the problem could occur just due to the use of Magisk (after some weeks).
The public documentation on efs in general is already sparse, but the one for the Exynos based models is close to non-existent from what I found. That's why I thought I would share my journey and findings.
This is how I went ahead to restore the functionality. In particular, due to the Exynos chip, things are different to other tutorials which either rely on MediaTek or Qualcomm chipsets, which store the NVRAM (responsible for IMEI, ...) in a different way (not in Samsungs own encrypted and obfuscated .bin format) and have more accessible ways of setting IMEI (via serial console, external tools, ...). There, the restore process is different.
Prerequisites
Backup (potentially corrupted) of efs and sec_efs
TWRP
How to proceed
Code:
- Remove any root app that might infringe with the "efs" data, such as MAC address changers, ...
- Restore both "efs" and "sec_efs" partitions with TWRP (with no intermediate reboot)
In my case, the most recent "nv_data.bin" inside the "efs" backup was corrupt (as I backed it up AFTER the corruption), so I needed to continue as follows
Code:
- Do not reboot to system directly after restore
- In TWRP, reboot to "fastboot" and enter ADB
- Run "adb shell"
- cd /mnt
- mkdir test
- mount /dev/block/by-name/efs test
- cd test
- ls -al
in addition to "nv.log" (just a log file), "nv_data.bin", "nv_data.bin.md5" (the corrupted ones), ensure there is also ".nv_data.bak", ".nv_data.bak.md5" (the timestamps of which were in the future, but that's ok)
- mv nv_data.bin nv_data_corrupt.bin
- mv nv_data.bin.md5 nv_data_corrupt.bin.md5
this will cause "nv_data.bin" and "nv_data.bin.md5" to be restored from the ".nv_data.bak", ".nv_data.bak.md5" files on the next reboot, observe this later in the "nv.log" by the following lines
[none]DATE:Not exist secure efs
[none]DATE:Nv restored 3
- cd ..
- umount test
- rmdir test
- Turn the phone FULLY off
- Reboot
- Cellular connectivity and GPS should be working again!
- Make an immediate backup of "efs" and "sec_efs"
In theory, you should also backup "persist", but I didn't find a corresponding partition.
- (Optional) Remove the corrupt ".bin" and ".bin.md5" files in "efs"
I hope this gives some insights on nv_data on Exynos chips and potentially helps anybody in a similar situation.
Spoiler: Useful resources that helped me along my journey
Fix for missing IMEI & Baseband
https://forum.xda-developers.com/t/imei.4419517/#post-86621473 Thanks to @MauriJ2001 for suggesting this guide. It worked for A12 too. I am currently on BVB4 firmware version with IMEI & Baseband working. Hopefully it works for everyone else tho.
forum.xda-developers.com
Imei
I lost imei/baseband after flashing stock ROM Build number: A125FXXU2BVB4
forum.xda-developers.com
[fixed] rooted a325m suddenly no imei, no sim
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now...
forum.xda-developers.com
Need nvram donors
We need a donor nvram. All you need is files: nvram.bin, nvdata. img, persist. img, nvcfg. img, protect1. img, protect2. img, as well as pc. Goal: We will not take your imei. The most important thing for us is to understand what imei format miui...
forum.xda-developers.com
Wifi don't work? Flash this! /Persist Repair
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions). Before this zip, you have to copy the...
forum.xda-developers.com
reverse-engineering nv_data.bin
I have a rooted Galaxy Nexus GSM (Maguro) running ClockworkMod and the stable version of CM9. I've been trying to find out how exactly the IMEI is stored --- whether it's baked into the radio component or whether it's controllable from firmware...
forum.xda-developers.com
Docomo SIM unlock: Jup's Grand Theory of Permanent SIM Unlock
This theory now seems to be confirmed by number of successful applications & my additional research. It should be generally safe to try both experiments. However, it still requires you know basics of shell. Above all, backup. And as allways, I am...
forum.xda-developers.com
[SOLVED] suddenly unknown imei
ok so, i was using my phone normally yesterday, but out of nowhere, my SIM card stopped working and i couldn't use mobile internet/calls anymore. So i checked my settings and i saw my IMEI was marked as unknown, the same with baseband. The A32...
forum.xda-developers.com
[Fixed] Repair IMEI and fix deleted EFS folder for Note10+ N975F
Hi bros First of all I am not a developer, the EFS folder of my Note10+ was deleted by mistake and I lost my IMEI numbers, after a lot of concern, researches and tests I fixed my Note10+ and I want to share my very hard and bad experience maybe...
forum.xda-developers.com
Lost my efs backup.. can I use another one?
So basically I dont have my efs backup.. and twrp messed up my efs partition.. Is it possible to use another efs?
forum.xda-developers.com
How to mount TWRP backup files in Linux
Hello, I want to inspect backup files create by TWRP backup. The file structure is this: $ ll /mnt/HD403LJ/oneplus5t/TWRP/BACKUPS/b94a5888/2019-05-27--00-44-45 .rwxr-xr-x root root 1.0 MB Fri Apr 3 20:13:36 2020  bluetooth.emmc.win .rwxr-xr-x...
forum.xda-developers.com
[V1.0]01.05.14 EFS/IMEI Tool G900M/F/T Cmplete backup EFS + Modemst1 and 2 - Galaxy S 5 Android Development (Snapdragon)
[V1.0]01.05.14 EFS/IMEI Tool G900M/F/T Cmplete backup EFS + Modemst1 and 2 - Galaxy S 5 Android Development (Snapdragon)
www.bettermobileapp.com
subject:"\[Replicant\] \[libsamsung\-ipc\] \[PATCH\] nv_data\-imei\: indicate that write\-imei may or may not work"
[HOW-TO] Sim-Unlock via nv_data.bin!
Also den xdaLeuten hats geholfen! Ich dachte mir ich übersetze es für euch! Edit: Hier gibt's eine App die das ganze erleichtern soll: https://play.google.com/store/apps/details?id=org.projectvoodoo.simunlock&hl=de ALS ERSTES: Android Hilfe.de und Ich übernehmen keine Haftung wenn etwas schief...
www.android-hilfe.de

Categories

Resources