IMEI (EFS) BAckup Tool Note 5
{
"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/Play store
-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. (3644)
1.1 - Fixed for systemless root users.
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
PS : It needs CWM and busybox installed.
Reserved 3
Reserved 4
Reserved 5
Thank you
Sent from my SM-N920T using Tapatalk
Yet another useful contribution
Thanks
Nothing happens when i try to launch the app. Is that normal, or should there be a GUI? Also tried pro version.
Sent from my SM-N920T using Tapatalk
daftlush said:
Nothing happens when i try to launch the app. Is that normal, or should there be a GUI? Also tried pro version.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Are you sure you have rooted device? As said in op it won't open without root access.
Sent from my SM-N920I using xda premium
dr.ketan said:
Are you sure you have rooted device? As said in op it won't open without root access.
Sent from my SM-N920I using xda premium
Click to expand...
Click to collapse
ohh yeah. root is 100%.
Sent from my SM-N920T using Tapatalk
daftlush said:
ohh yeah. root is 100%.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Which is your device model ?
Reinstall and click on app icon and wait till it ask for supersu. Once you grant permission then only app will show ui
Sent from my SM-N920I using xda premium
dr.ketan said:
Which is your device model ?
Reinstall and click on app icon and wait till it ask for supersu. Once you grant permission then only app will show ui
Sent from my SM-N920I using xda premium
Click to expand...
Click to collapse
t-mo. rooted. su set to auto allow.
Sent from my SM-N920T using Tapatalk
Check Super su log and see it has granted su permission to app.
i have no baseband and imei unknown after updating to latest tmo firmware and installing DarthStalker. Have backup from when i first rooted phone. will purchasing your app fix you think?
do i need to downgrade to old firmware and restore?
many thanks for all your hardwork for the community,!
Try Restoring directly if doesn't work then flash same firmware on which you made backup. If any issue or doesn't work pm me.
Before doing anything make copy of backup on multiple storage.
Sent from my SM-N920G using xda premium
Thank you so much for all the help. I am now back up and running. You are awesome ,sir.!
Got it to work. How do i find out what to type in promt to restore?
Sent from my SM-N920T using Tapatalk
nice tool, but how to restore a backup ?
nmx87 said:
nice tool, but how to restore a backup ?
Click to expand...
Click to collapse
the same question
Guys it's in the OP...use Terminal Emulator with the commands in the OP. .
Related
{
"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"
}
Everytime after i turn off my wifi connection, i will have this 'dumpstate_sys_WIFI_OFF_20134...error.log.txt' log in my data folder..i wonder why this log appear and how to prevent it from automatically arise?? It can be delete with root explorer but i just wanna know is there any way to ultimately stop this log from happening.tq
Sent from my GT-I9100G
Sent from my GT-I9100G
rascal123 said:
Sent from my GT-I9100G
Click to expand...
Click to collapse
I also got this error file, and today I notice my phone keep hanging when turning on the wifi.
same for me with Stock LB1 rooted
The problem is if we not delete them..they will consume a lot of space..eating our internal memory..
Sent from my GT-I9100G
i am experiencing this too, even up to 1gb space is consumed T_T
it is like some kind of debug function is still enabled in LB1 firmware, maybe the samsung dev forgot to disable it
Sent from my GT-I9100G using Tapatalk
I also got this on superRomv3. when i flashed stock xxla1, the problem disappear...
Is it bcos of rom or kernel?anyone knows??
Sent from my GT-I9100G using Tapatalk 2 Beta-6
fauzi_91 said:
Is it bcos of rom or kernel?anyone knows??
Sent from my GT-I9100G using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
i think it's the base of LB1 Roms ...
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated.
Click to expand...
Click to collapse
Thanks a lot! It working perfectly, no more wifi error dump file, some more it seems fix my hanging issue as well, previously I keep facing phone hanging when switching between wifi on and off.
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
thanks so much...it works..
c. Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Thanks for the workaround..... this one really was eating up space.
help !
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Thanks for that. But whenever I try method b and c , what I get is that the dumpstate is a read only file, any idea what I should do ?
thanks
System memory continously decreasing
Hi all,
I'm having this same issue of system memory decreasing at a rapid rate. Had to do a factory reset once. Phone is non rooted. Checked the dump state file but it's really small in size. And i can't change executable permissions for that using es explorer without root. Any solution please?
zidhu said:
Thanks for that. But whenever I try method b and c , what I get is that the dumpstate is a read only file, any idea what I should do ?
thanks
Click to expand...
Click to collapse
Root. Sounds like you don't have root. You need root to do the above.
Geekeek said:
Hi all,
I'm having this same issue of system memory decreasing at a rapid rate. Had to do a factory reset once. Phone is non rooted. Checked the dump state file but it's really small in size. And i can't change executable permissions for that using es explorer without root. Any solution please?
Click to expand...
Click to collapse
Same as above. To change permissions on files in the system partition, you need root.
Thanks. What is causing the continual decrease? Can't root at least until the weekend but internal memory will be over in a day by the looks of it. :what:
Sent from my GT-I9100G using XDA
Geekeek said:
Thanks. What is causing the continual decrease? Can't root at least until the weekend but internal memory will be over in a day by the looks of it. :what:
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
You said system memory in post 15, and internal memory above in post 17. Which is it?
In any case, I don't know what all you have installed and how you use your phone, so I can only guess what the cause would be.
If you for sure want it to stop, do a factory reset, (but you will lose all apps and user data) and carefully monitor what apps you re-install.
Sorry, it's obviously the system memory I am referring to. Already did a factory reset once and hardly installed anything later on. Still 1 gb used up.
Sent from my GT-I9100G using XDA
Geekeek said:
Sorry, it's obviously the system memory I am referring to. Already did a factory reset once and hardly installed anything later on. Still 1 gb used up.
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
Not so obvious, really. Exactly how are you seeing the space remaining? Are you looking at Menu > Storage > Device memory?
REMOTE TERMINAL
Execute any shell command by SMS
Introduction:
This app will read receiving sms and executes shell commands in them. It is very useful in many ways. You can delete your private data from your device in case you lost your phone. You can even turn off your device by this method. Every command that you execute in terminal emulators in your devices can be executed by this method. Every command is executed with super user permissions. So you have full control over your device by a simple sms. To stop any other people using this other than the owner, I added password protection for it.
Instructions:
1. Open the app (Remote Terminal)
2. Enter "null" as the current password. (case sensitive)
3. Enter anything as you wish as your password. (case sensitive)
4. Start typing a sms from any device, anywhere in the world starting with your password. (CASE SENSITIVE)
5.Enter your set of commands - each command in a NEW line
(when starting terminal session it's in the root folder)
Example: making a folder in sdcard named ravindu
Code:
yourpassword
cd sdcard
mkdir ravindu
or
Code:
yourpassword
mkdir sdcard/ravindu
6.Send the sms to your device.
7. You will be asked to grant SuperUser access to the app. Give permanent superuser permissions (only for the first time)
You don't have to waste your sms by sending 1 sms for 1 command. Send all commands in 1 sms
Requirements:
A ROOTED device
NOTE:
Password is case sensitive in every place.
Give me your comments and suggestions about this app. If I have any time, I will try to develop this app.
See the 2nd post for a list of some useful commands
SCREENSHOT:
{
"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"
}
Flash it & enjoy!!!
If you like my work, hit the THANKS button!!!
Donate me if you think my work is valuable
List of Useful Commands
1. reboot - reboot your device
2. reboot -p - turn off your device
3. rm data/dalvik-cache/*.* - clear dalvik cache
4. rm sdcard/pictures - delete entire pictures folder from sdcard ( change the path to your desired folder to delete it )
5. rm data/system/gesture.key - reset your pattern lock ( accepts any pattern you input )
6.rm data/system/password.key - reset your password lock
I'll update the list when I get more free time
U are determined to make some remote apps...
Good going..
Sent from my Sk17i using xda premium
sandy7 said:
U are determined to make some remote apps...
Good going..
Sent from my Sk17i using xda premium
Click to expand...
Click to collapse
Thanks bro!!
Broadcast receivers! I love playing with them
keep it up bro!!! I love that GUI
codfx said:
keep it up bro!!! I love that GUI
Click to expand...
Click to collapse
Thanks bro!!!
This sounds....secure
Use a strong password... then send it via SMS. Hmmmmm...
question....
Is it compatible with gryphon secure messaging platform? Or does it listen to default SMS app only...?
I use gryphon a lot, and would prefer to use it to send the commands; just as an extra precaution...
when you loss your phone, your SIM card was replaced! and you can not know Phone number, can we control by 3G or wifi?
and can you give us all command of emulator?
dynamic503 said:
when you loss your phone, your SIM card was replaced! and you can not know Phone number, can we control by 3G or wifi?
and can you give us all command of emulator?
Click to expand...
Click to collapse
By default the only available commands for the emulator are :-
Code:
echo -- prints text to stdout.
set -- sets shell variables
export -- makes shell variables available to command-line programs
cd -- change the current directory.
pwd -- print name of the current directory.
But if you have busybox installed on your device then you have many more commands like cp, rm and many more Linux commands
@RavinduSha- Nice work bro. Happy programming
super user request?
(deleted post as i figured out i had a setting on go sms pro interfeering with it opps both apps work now)
abcdjdj said:
By default the only available commands for the emulator are :-
Code:
echo -- prints text to stdout.
set -- sets shell variables
export -- makes shell variables available to command-line programs
cd -- change the current directory.
pwd -- print name of the current directory.
But if you have busybox installed on your device then you have many more commands like cp, rm and many more Linux commands
@RavinduSha- Nice work bro. Happy programming
Click to expand...
Click to collapse
thanks bro!
How should i turn off my phone using shell command?
Which command should i use?
Sent from my SK17i using xda premium
mdsohail98 said:
How should i turn off my phone using shell command?
Which command should i use?
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
"reboot -p" command will work or you can just use my other app "Remote Turn Off"
Thanx.....
Can you provide me commands for better use of this app because i want some new commands apart from cd,cp,mkdir,dd,df,rm,mv.....
Is there any command from which I can open an app which is installed in my phone....
Sent from my SK17i using xda premium
mdsohail98 said:
Thanx.....
Can you provide me commands for better use of this app because i want some new commands apart from cd,cp,mkdir,dd,df,rm,mv.....
Is there any command from which I can open an app which is installed in my phone....
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
Bro there are many guides for using shell commands. Just search.
I can give the code for opening an app. For that you have to provide me the AndroidManifest.xml file from that package. If it's a stock app tell me the package name.
(AndroidManifest.xml file is needed for identifying the package name and the main activity)
Can you try for stock walkman app??
I want to play music remotely.....
Sent from my SK17i using xda premium
mdsohail98 said:
Can you try for stock walkman app??
I want to play music remotely.....
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
here is the code
am start -n com.sonyericsson.music/.PlayerActivity
this will open your walkman app.
Hey thanx allot.....
Can do me one more favour????
I just want to know, how to delete messages using remote terminal?????
Please do me this as a last favour
Sent from my SK17i using xda premium
This is a guide which will allow you to backup your phone via ADB using one simple command. Its commonly used when flashing another firmware or ROM. Keep in mind this is experimental and not exactly publicized as a feature of ICS/JB, so don't count on this as your only method of backup! Firstly you need to have ADB, if you dont have, download and install/extract from here; JDK (Java Development Kit) if you dont have that, you can download it from here and updated Android SDK Platform Tools via SDK Manager and last but not least a drivers for your phone, you can download them from the Sony Development site. OK, let's start :victory:
1. Connect your device via USB, and go to C:\adt-bundle-windows-x86\sdk\platform-tools. Hold Shift and right click. Choose open command window here.
2. Optionally, type the command 'adb devices' to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
The following text its about the adb backup command and all about it. I recommend reading it. Thanks to copkay for the further backup process.
In ADB there is a command 'adb backup' which this thread is all about. The command parameters format is:
Code:
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
The most basic command you can use* is:
Code:
adb backup -all
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
* This may not work for every setup. If you get an error such as "adb: cannot open file ./backup.ab", use:
Code:
adb backup -all -f C:\backup.ab
Or substitute the path of your choice in place of C:\.
To explain the parameters:
Code:
-f <file>
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
Code:
-apk|-noapk
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
Code:
-shared|-noshared
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Xperias I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
Code:
-all
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
Code:
-system|-nosystem
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
Code:
<packages...>
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
Click to expand...
Click to collapse
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
Code:
adb backup -apk -shared -all -f C:\backup.ab
^ It backs up all data including music, pictures, videos, APKs etc. ^
Code:
adb backup -apk -all -f C:\backup.ab
^ It backs up ONLY the APKs, system and user ones ^
4. You will see a screen like the following:
{
"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"
}
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you will get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your phone returns to the home screen.
9. To restore, with your device connected open your command prompt again, and type:
Code:
adb restore C:\backup.ab
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, Enjoy !
Could I restore my data using this method after I rooted my device (xperia P, LB)? Will I lose root if I do?
Sent from my LT22i using xda app-developers app
good post. very helpful.
didn't use adb before so maybe iam doing somethings wrong.
usb debugging on, stock ics rooted. adb devices shows my device (xpgo).
after adb backup -apk -shared -all -f C:\backup.ab console outputs : unlock device and confirme...
but there is now backup screen on my device.
any ideas what iam doing wrong ???
thanx
stavro said:
didn't use adb before so maybe iam doing somethings wrong.
usb debugging on, stock ics rooted. adb devices shows my device (xpgo).
after adb backup -apk -shared -all -f C:\backup.ab console outputs : unlock device and confirme...
but there is now backup screen on my device.
any ideas what iam doing wrong ???
thanx
Click to expand...
Click to collapse
Thats normal, you should get a new output line when finished. It takes a hour or two
Sent from my LT22i using Tapatalk 2
DavidMKD said:
Thats normal, you should get a new output line when finished. It takes a hour or two
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
i mean this screenshots that you posted. i don't get to them.
i guess they should popup after entering the command in the console, right ?
in my case nothing happens on the phone.
Mis-typed link for ADB
Thanks DavidMKD for the info...
I know the thread is over a year old, but I was referred here by XDA for assistance. For the benefit of others who might arrive here for similar help... the ADK link properties show it to be ending in "htmll" (can't post full link due to forum spam rules), and clicking on it comes up with an error 404, probably due to the extra "l" in html ?
Haven't yet gone through the process, but hoping to have a working solution soon. I read stuff from cover to cover and follow instructions to the letter, so here goes....
Cheers
As title suggests I can't copy my nandroid backup folder contents from TWRP to my PC. Seems to be just the large data and system files that are around 1.3 gig each.
in windows 7 it never copied, no error. in windows 8 I receive an 'unspecified error' and it just stops.
I can copy other large files back and forth but just not these from my backup.
Any ideas?
Sent from my HTC One using Tapatalk 2
I have the same problem with my Galaxy Nexus... waiting for a solution .
terega said:
I have the same problem with my Galaxy Nexus... waiting for a solution .
Click to expand...
Click to collapse
Edit - Feature of TWRP 2.6. Encryption and permissions.
Currently only way to backup contents is to change permissions of the Backup folder contents, or boot phone back into recovery and do an an ADB pull.
I did ADB pull and that went fine.
gustav30 said:
Edit - Feature of TWRP 2.6. Encryption and permissions.
Currently only way to backup contents is to change permissions of the Backup folder contents, or boot phone back into recovery and do an an ADB pull.
I did ADB pull and that went fine.
Click to expand...
Click to collapse
Changing permissions didn't work for me at all... however, ADB pull did. Any other ideas to get this working again without having to use ADB pull?
This post in this thread is what worked for me to change permissions. Also more discussion about this in that thread.
http://forum.xda-developers.com/showthread.php?p=43453295
Sent from my HTC One using Tapatalk 4 Beta
gustav30 said:
This post in this thread is what worked for me to change permissions. Also more discussion about this in that thread.
http://forum.xda-developers.com/showthread.php?p=43453295
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sweet! That worked. Thanks! I was trying 644, not 777.
Sorry to kind of hijack this thread, but I am having issues with trying to copy the backups using ADB. Whenever I am booted into TWRP my computer will not recognize the device as an ADB device. Running Windows 8 with the SDK/Google USB Drivers installed.
Permissions do not change via shell. ADB Pull permission denied. Mounted get "unspecified error". Cannot change permissions with Root Explorer.
I am rooted, ADB working, device connected, TF700t
Any help to backup my backup would be appreciated.
(This is what I did:
C:\Users\Chad\Desktop\Android SDK\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod -R 777 /sdcard/TWRP
chmod -R 777 /sdcard/TWRP
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Chad\Desktop\Android SDK\sdk\platform-tools>adb pull /sdcard/TWRP/BACKU
PS c:/Users/Chad/Desktop
pull: building file list...
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/recovery.log -> c:/Users
/Chad/Desktop/015d29955a581616/first071613/recovery.log
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/boot.emmc.win.md5 -> c:/
Users/Chad/Desktop/015d29955a581616/first071613/boot.emmc.win.md5
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/boot.emmc.win -> c:/User
s/Chad/Desktop/015d29955a581616/first071613/boot.emmc.win
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/data.ext4.win.md5 -> c:/
Users/Chad/Desktop/015d29955a581616/first071613/data.ext4.win.md5
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/data.ext4.win -> c:/User
s/Chad/Desktop/015d29955a581616/first071613/data.ext4.win
failed to copy '/sdcard/TWRP/BACKUPS/015d29955a581616/first071613/data.ext4.win'
to 'c:/Users/Chad/Desktop/015d29955a581616/first071613/data.ext4.win': Permissi
on denied
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/system.ext4.win.md5 -> c
:/Users/Chad/Desktop/015d29955a581616/first071613/system.ext4.win.md5
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/system.ext4.win -> c:/Us
ers/Chad/Desktop/015d29955a581616/first071613/system.ext4.win
failed to copy '/sdcard/TWRP/BACKUPS/015d29955a581616/first071613/system.ext4.wi
n' to 'c:/Users/Chad/Desktop/015d29955a581616/first071613/system.ext4.win': Perm
ission denied
7 files pulled. 0 files skipped.
2233 KB/s (8538070 bytes in 3.732s)
gustav30 said:
This post in this thread is what worked for me to change permissions. Also more discussion about this in that thread.
http://forum.xda-developers.com/showthread.php?p=43453295
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks a million.
sundoulos said:
Permissions do not change via shell. ADB Pull permission denied. Mounted get "unspecified error". Cannot change permissions with Root Explorer.
I am rooted, ADB working, device connected, TF700t
Any help to backup my backup would be appreciated.
Click to expand...
Click to collapse
I had this same problem for a while on my Nexus 4. I found this thread and tried to figure out what I was doing wrong. Turns out the adb pull doesn't work with the device booted up normally, as most adb commands do! Once I went into recovery and used adb there, everything transferred over. Hope it helps.
I want to know I have same problem but I just move the folder and went I try to use I only have the boot backup, that mean I don't have my backup?
Removed.
Hi,
I started having this issue on my Nexus 4 but I can't remember if it was after 4.3 update. I could not copy the large files from the TWRP folder through windows explorer, wifi pro, Nexus Toolkit or any other method with the mobile turned on.
Permissions were already to 777 and still nothing.
For me the pull command with the mobile into recovery mode did the job.
Thanks
orangeyes said:
Hi,
I started having this issue on my Nexus 4 but I can't remember if it was after 4.3 update. I could not copy the large files from the TWRP folder through windows explorer, wifi pro, Nexus Toolkit or any other method with the mobile turned on.
Permissions were already to 777 and still nothing.
For me the pull command with the mobile into recovery mode did the job.
Thanks
Click to expand...
Click to collapse
For me it was TWRP ver. 2.6. that prevented me from a PC transfer. An adb pull resolved the issue. I believe changing permissions has the potential of opening a can of worms later on.
Yes indeed it must be the TWRP update for me as wel that caused the issuel because I updated the TWRP before going into 4.3.
pjc123 said:
For me it was TWRP ver. 2.6. that prevented me from a PC transfer. An adb pull resolved the issue. I believe changing permissions has the potential of opening a can of worms later on.
Click to expand...
Click to collapse
orangeyes said:
Hi,
I started having this issue on my Nexus 4 but I can't remember if it was after 4.3 update. I could not copy the large files from the TWRP folder through windows explorer, wifi pro, Nexus Toolkit or any other method with the mobile turned on.
Permissions were already to 777 and still nothing.
For me the pull command with the mobile into recovery mode did the job.
Thanks
Click to expand...
Click to collapse
Hi,
Could you please explain what an Adb pull is and how I can do it ? I've never done it before and need some help. I use a Rooted Nexus 4 (4.3), with the latest version of TWRP (flashed the recovery only today).
veeravar said:
Hi,
Could you please explain what an Adb pull is and how I can do it ? I've never done it before and need some help. I use a Rooted Nexus 4 (4.3), with the latest version of TWRP (flashed the recovery only today).
Click to expand...
Click to collapse
Hello,
Assuming that you are in the same folder with the adb.exe (can be found in the sdk or standalone online) and have the proper drivers installed:
1) Reboot phone into recovery.
2) COnnect it to your PC. A driver installation will take place if this is the first time.
3) Hold shift in the folder with the adb.exe and select "open command window here"
4) Type
Code:
adb pull /mnt/sdcard/TWRP C:\
You can continue after the C:\ if you want to copy the files elsewhere. Also fi you get error of the type that the target is not found propably your backups are saved in another directory. You can easily get the complete location to them by going into the advanced options of TWRP and the use the file manager to browse to your backups. You will see the target directory on top.
Edit: Sorry I did not include what adb is. here you go http://developer.android.com/tools/help/adb.html
I think that's all :good:
Hi,
Thank you for that tutorial. I tried using the code you mentioned. I need to move the TWRP folder on my sdcard to the platform-tools folder on the D:/ on my pc. I executed the following code (with cmd opened in the platform-tools folder):
adb pull /sdcard/ twrp
Only 24.6mb of files are being pulled into the said folder. Whereas the actual size of the TWRP folder is 1.5gb. The phone is booted into TWRP recovery.
Could you please explain why this is happening? and it would be great if you tell me the code to execute if i want to copy the TWRP folder to a folder called ANDROID in my D drive.
nope not working.....it shows this when i boot my phone into TWRP recovery and did an adb pull
{
"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"
}
zixian96 said:
nope not working.....it shows this when i boot my phone into TWRP recovery and did an adb pull
Click to expand...
Click to collapse
Connected from recovery:
adb pull /sdcard/TWRP/BACKUPS C:\
Then wait for it to finish.
[IMPORTANT] HOW TO DO EFS BACKUP AND RESTORE FOR GT-I8552
I Got PM Very Long Ago For Way To Backup Of "EFS" But In Last Two Weeks I Started Getting Request Again So Here Is The Simple Way I Wanna Share "How To Backup "EFS" For GT-I8552
As There Is No CWM For Our Device That Supports "EFS" Backup And Also Third Party Apps Ain't Working Now What To Do
So Here We Go Then :-
Q :- What is "EFS" ?
A :- "EFS" Folder Is The Very Sensitive System Folder That Contains Phone-Specific Information Such As The IMEI, Wireless Devices MAC Addresses, Product Code, And Much More. If This Thing Not Handled Properly, Can Turn Your Device Completely Useless As It Will No Longer Be Recognized By Your Carrier.
Problem Is, Flashing Custom ROMs Sometime Can Corrupt Contains Within "EFS" Folder. That’s Why Backing Up "EFS" Folder Is Very Important If You Love To Flash New ROM.
NOTE :- ROOT IS REQUIRED..!!
INSTRUCTIONS :-
EFS BACKUP
1. Download Android Terminal Emulator Or Download ROM Toolbox Pro Or ROM Toolbox Lite.
2. Open Terminal Emulator Or Terminal Emulator In ROM Toolbox App.
3. Use This Code To Backup "EFS"
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img
And hit Enter In Keyboard..
4. You Will Get efs.img In Your SDCard, Copy It To PC Or Upload On Storage Sites Like 4shared.com , Mediafire.com etc
EFS RESTORE
1. Download Android Terminal Emulator Or Download ROM Toolbox Pro Or ROM Toolbox Lite.
2. Open Terminal Emulator Or Terminal Emulator In ROM Toolbox App.
3. Use This Code To Restore "EFS"
Code:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p16
And hit Enter In Keyboard..
4. Guess What You Restored Your "EFS"
Please Hit "THANKS" or "DONATE" To Support.
bro did u try restoring ? r u sure it restore successfully?
tonyjs007 said:
bro did u try restoring ? r u sure it restore successfully?
Click to expand...
Click to collapse
Yes buddy it will restore u need root access for that thats all :good:
I already flashed jasp hd Rom before backing up efs partition now what should I do
ZANKRUT.DOSHI said:
I already flashed jasp hd Rom before backing up efs partition now what should I do
Click to expand...
Click to collapse
Np u can backup now efs.img just in case
We have to put backup of efs (.img file in internal storage or external while restoring it?? :|
Sent from my GT-I8552 using XDA Premium 4 mobile app
Jaspreet_Singh said:
Yes buddy it will restore u need root access for that thats all :good:
Click to expand...
Click to collapse
Bro did u restore it by this way? And can u tell me which information stored on mmcblk0p3 ?
Sent from my GT-I8552 using Tapatalk
kinchit1495 said:
We have to put backup of efs (.img file in internal storage or external while restoring it?? :|
Sent from my GT-I8552 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
internal as above command is for internal only
coolkoushik07 said:
Bro did u restore it by this way? And can u tell me which information stored on mmcblk0p3 ?
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
yes its working and p3 is for modem for our device..
Jaspreet_Singh said:
internal as above command is for internal only
yes its working and p3 is for modem for our device..
Click to expand...
Click to collapse
Ur given command is wrong. There is no sdcard directory, it would be sdcard0 or extSdCard. By the way can u tell me what is the work of bs command. Somewhere i saw people use bs=4096 while using dd command. Can u please explain it?
{
"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"
}
Sent from my GT-I8552 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 07:53 PM ----------
Edit : my bad. Ur code is working too. I did a mistake by /storage/sdcard/ so it gave error. So ignore that part. But if u can please explain bs parameter.
Sent from my GT-I8552 using Tapatalk
I think it ws wrong it should be sdcard0
Sent from my GT-I8552 using XDA Premium 4 mobile app
kinchit1495 said:
I think it ws wrong it should be sdcard0
Sent from my GT-I8552 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. mine works fine, the output should be efs.img
I think bs stands for block size. But can anyone explain what it does?
Sent from my GT-I8552 using Tapatalk
thnxs bro for great in gt-i8552
Gt-i8552 rocksss!!!
coolkoushik07 said:
Ur given command is wrong. There is no sdcard directory, it would be sdcard0 or extSdCard. By the way can u tell me what is the work of bs command. Somewhere i saw people use bs=4096 while using dd command. Can u please explain it?
Sent from my GT-I8552 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 07:53 PM ----------
Edit : my bad. Ur code is working too. I did a mistake by /storage/sdcard/ so it gave error. So ignore that part. But if u can please explain bs parameter.
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
The /sdcard/ *should* be universal on many samsung devices (at least I know it IS like that on the Galaxy Ace and on the Galaxy Win, i8550L that I own).
Regarding the bs operand of the dd command, in this case you don't need it, as you're acting directly over the EFS partition. In the use of this command the bs operand is used for when you're working with a whole disk.
Technical stuff below:
For example, if you don't have the precise /dev/block/mmcblk0pXXX of a partition (taking in consideration that /dev/block/mmcblk0 is the disk you want to read from), you can use dd in this way:
Code:
dd if=/dev/block/mmcblk0 bs=4096 of=/sdcard/kernel.img
In the example, we're backing up the Kernel part of the phone (note that this is not real information, just an example, so don't blame me if you try to dump that command back in the phone assuming things you don't know xD), as you may (or may not) know, a disk is comprised of many blocks, you can google about that later it's quite late and don't wanna go on too deep so i'll try to be brief; if your disk is 512 mb in size, probably the first 32MB would be for boot, kernel, recovery, modem and NVRAM (not to be confused with modem), these 32 MB might be distributed this way:
1-1024MB Bootloader
1024-6144 Kernel+Recovery
6144-18432 Modem
18432-32768 NVRAM
and so on
Long story short, don't mess with DD
Backing Up EFS Partition
Dear Jaspreet,
Myself and CoolKoushik07 tested this procedure long before. However this is not working solution. This is due to the natture of the EFS filesystem.
Please go through my Post # 39,40,41,42,43,44.
http://forum.xda-developers.com/showthread.php?t=2541198&page=5
Please correct me if I am wrong.
Regards
Arinio said:
Dear Jaspreet,
Myself and CoolKoushik07 tested this procedure long before. However this is not working solution. This is due to the natture of the EFS filesystem.
Please go through my Post # 39,40,41,42,43,44.
http://forum.xda-developers.com/showthread.php?t=2541198&page=5
Please correct me if I am wrong.
Regards
Click to expand...
Click to collapse
Check ur command "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img"
and mine "dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img"
Two mistakes ? first is our mounting point for efs is mmcblk0p16 and there is no storage "of=/storage/extSdCard/efs.img" it shud be either to sdcard directly or of=/extSdCard/efs.img
Jaspreet_Singh said:
Check ur command "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img"
and mine "dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img"
Two mistakes ? first is our mounting point for efs is mmcblk0p16 and there is no storage "of=/storage/extSdCard/efs.img" it shud be either to sdcard directly or of=/extSdCard/efs.img
Click to expand...
Click to collapse
Just a lil correction.. /storage/extSdCard/ is not wrong directory..
Sent from my GT-I8552 using Tapatalk
Backing Up EFS Partition
Dear Jaspreet,
Please check my Post #43.
Regards
Jaspreet_Singh said:
[IMPORTANT] HOW TO DO EFS BACKUP AND RESTORE FOR GT-I8552
Click to expand...
Click to collapse
hello @Jaspreet_Singh
Im forget to make a backup by my efs folder I8552 again after formated my PC.
Now its empyt cause i had troubles flashing test by custom rom
Important
Except the stock lockscreen and stock setupwizard inicial everything works even empty folder cause I managed to recreate the mac adress, retrieve the IMEI
3G signal ok
calls Ok
IMEI ok
IP/Wi fi ok
Is it something can u do , like send files folders attachment and i using sdk put my mac adress, ip and imei to restore files?
tks
@mjraogr....
Add facebook.
https://m.facebook.com/GlaMsP?ref=bookmark
I also had the same problem, I was looking for solutions to this problem and in one of these search found an EFS file from another machine and tried their luck to restore my folder ..
Following the steps in this link posted by @manojkumar8552 my work out and now is working perfectly.
Download these files, extract the desktop.
https://drive.google.com/file/d/0B6t2vRswL0dHVXRKYXZncGd1WVU/view?usp=sharing
1 - run the Backup_EFS ...
2 - Once completed Backup your EFS.img, rename such as EFS MY or something.
3 - Inside the folder contains another file (efs Restore.img) change the name to EFS.img.
4 - Run the Restore_EFS ...
5 - Restart the device ...
6 - Enter the ROOT folder with Explorer, find the EFS / Factoryapp folder, edit the file (factorymode) will contain OFF switch to ON all upper case, reset the unit ....
Good luck ... these steps have worked in the mine, hope it helps ...
NOT TO THANK !!