IMEI (EFS) BAckup Tool Note 7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read this.
You needs root access to use this tool otherwise app won't open..
Location of stored file :
Device storage/MyEFS
If you unable to see backup, contact me with details of your device variant
Download :
PRO Version
XDA version (free)- Attached at end of this post.
Difference between Free/PRO version
-Both version makes backup in same format and no difference in backup.
-Pro version have option to Restore with single click
-Free version will save file in MyEFS and if you make next backup it will replace older one. While play store version everytime creates new folder with date ,Time and your IMEI stamp so you can keep multiple backup as well no confulsion about which backup is made when and on which device. Also it makes copy of build.prop so you can get idea you were on which ROM when backup created)
-Play store version give notification in case backup not created.
-Weekly Auto backup feature available on play store version.
-PIT creator. Play store V1.1 added option to create PIT file from existing layout
Click to expand...
Click to collapse
This tool using generic name of partition block and you can restore with simple adb shell
dd if=/path of backup files/ of=/partition block according your device
ChangeLog
1.0 - Initial release.
In case backup is not created then post your device details here.
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot
Here is different method to remove it.
Method1 :
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Code:
OFF
To:
Code:
ON
Reboot device.
Method2:
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Method3
Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.
e:failed to mount /efs(invalid argument) error with bootloop
This condition usually happens with using unsupported tool (usually from play store).
To recover this, needs to use adb shell
Code:
adb shell
mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs
x means your device EFS partition number. Here this is for just visual representation. Block number/Name may be completely different on your device.
PS : It needs CWM and busybox installed.
Last
Doctor is unbelievable your continue effort and dedication, could you solve your brick problem on your device??
N7, SM-N930F.
charlypaez said:
Doctor is unbelievable your continue effort and dedication, could you solve your brick problem on your device??
N7, SM-N930F.
Click to expand...
Click to collapse
Yes fixed soon after making this tool
I have updated details on my ROM thread.
dr.ketan said:
Yes fixed soon after making this tool
I have updated details on my ROM thread.
Click to expand...
Click to collapse
What a great new!!! The notice of the day... Thank you for all you support... You will be a create telegram support group for N7 Rom doctor?
N7, SM-N930F.
charlypaez said:
What a great new!!! The notice of the day... Thank you for all you support... You will be a create telegram support group for N7 Rom doctor?
N7, SM-N930F.
Click to expand...
Click to collapse
Nope. Not possible for me to manage. I have telegram broadcast for my PRO ROM users but only broadcasting channel.
dr.ketan said:
Nope. Not possible for me to manage. I have telegram broadcast for my PRO ROM users but only broadcasting channel.
Click to expand...
Click to collapse
Understood doctor.. Thanks again for all!
Hi Dr, I tried method one and all them settings were already set to on? what does that mean exactly
turilo said:
Hi Dr, I tried method one and all them settings were already set to on? what does that mean exactly
Click to expand...
Click to collapse
Your device is stuck to safe mode?
Why are you doing that?
dr.ketan said:
Your device is stuck to safe mode?
Why are you doing that?
Click to expand...
Click to collapse
I did not put it in safe mode, right after i followed your root guide (which worked well) i am trying to backup efs. It does not say my device is in safe mode anywhere..
EDIT: all done and saved using your new tool, will get Pro once released for your support. Thanks Dr.
turilo said:
I did not put it in safe mode, right after i followed your root guide (which worked well) i am trying to backup efs. It does not say my device is in safe mode anywhere..
EDIT: all done and saved using your new tool, will get Pro once released for your support. Thanks Dr.
Click to expand...
Click to collapse
Omg don't do that 4 methods
Those are for those who have efs issue.
To backup simply download app and create backup with that.
dr.ketan said:
Omg don't do that 4 methods
Those are for those who have efs issue.
To backup simply download app and create backup with that.
Click to expand...
Click to collapse
yea i edited my last post lol all good Dr ty
Hey dr.ketan,
I've always used TWRP to backup the EFS partition, when I flash a ROM from other country and I dont have connection to my carrier I restore this partition using TWRP and it works again..... So my question is, is this a safe mode of doing it too?
I have never used twrp for this so no much idea.. Regarding safety yes this method is safe. Also twrp should safe. This is useful for those who don't have twrp.
Thank you...
Actually about the safe method I was asking if TWRP method was safe, I know yours is
I'd like to purchase the pro version of this app to go towards the tweaks pro for note 7.
I have already purchased donate dev and utilities pro for note 4.
Looking for an app that be useful to purchase for my note 7 instead of the others to go towards tweaks pro note 7
Thanks
turilo said:
I'd like to purchase the pro version of this app to go towards the tweaks pro for note 7.
I have already purchased donate dev and utilities pro for note 4.
Looking for an app that be useful to purchase for my note 7 instead of the others to go towards tweaks pro note 7
Thanks
Click to expand...
Click to collapse
If you have purchased Donate Dev then no need to purchase anything more because it covers almost utilities for N7 in one app.
Simply download Request code for Note7 from here - Install it and send me mail through it. Before sending mail you have to write Google Order ID of Donate Dev app (you get it on mail you received from google)
After this you will get complete instructions and Pro key in 24-48hrs.
Also once you have Pro Key, you will able to get Pro version of IMEI app (I will release soon)
Reagrds
Dr.Ketan
Pro version (Complimentary) available for (Dr.Ketan Tweaks) Pro Users
Open dr.Ketan Tweaks Pro - Download Latest Tweaks Pro - Latest version of tweaks Pro - N930 Note7 - IMEI Tool SGN7 Pro_Complimentary 1.1.apk
Download and Install as regular apk.
Good job Dr... Only the best!
Related
Credits/Disclaimer
Code:
[U][B]
This is not my guide, you dont have to thank me for this.
Thanks to Ocnbrze over at AndroidForums for this.
we are not responsible if your device(s) cause(s) a nuclear war[/B][/U]
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Please read thru this guide once or twice before actually taking steps !
Your phone MUST be on a stock sense rom so go get that installed now !
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Before you do anything else, your phone MUST be on a stock sense rom !
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
{
"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"
}
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
XenonV said:
First things first- Not my guide, You are fully responsible for whatever happens. It is not XDA's fault, its not my fault, its all on you.
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Now lets begin
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
Click to expand...
Click to collapse
I've actually been dealing with this most of the day trying to unroot and go back 100% stock and have had no success. It was suggested elsewhere that I need to be on a stock rom? I'm dl'ing one now to try as I am currently on an ics rom.
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
XenonV said:
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
Click to expand...
Click to collapse
Perhaps a good bit of info to add to the op
Relentless D said:
Perhaps a good bit of info to add to the op
Click to expand...
Click to collapse
already on it, thanks
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Captain_Throwback said:
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Click to expand...
Click to collapse
i dont know who the original writer is, which is why. if i know then i always list that info :good:
XenonV said:
i dont know who the original writer is, which is why. if i know then i always list that info :good:
Click to expand...
Click to collapse
Where did you get it from, then?
It looks strikingly similar to this guide:
http://androidforums.com/evo-4g-all-things-root/526575-guide-unrooting-gingerbread-2-3-5-a.html
In fact, the inordinate number of exclamation points and the use of my command prompt screenshot makes me think it originated over there.
Captain_Throwback said:
Where did you get it from, then?
Click to expand...
Click to collapse
somebody PM'd me the guide on another website (the tech game) , just the text, no link
XenonV said:
somebody PM'd me the guide on another website (the tech game) , just the text, no link
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Relentless D said:
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Click to expand...
Click to collapse
problem solved thanks :good:
and yes this is my guide. however, you do not need to be on stock sense, just not on ics roms for this to work. just throwing that out there.
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
Are you running a rooted ROM? You need to have root access for this to work. Try typing "su" at the prompt and see if it changed to a #.
thanks
Can this be done using a Mac?
XenonV said:
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
Click to expand...
Click to collapse
i have tried that and it still doesnt work, any help!?
im running a brand new computer like seriously out of the box, windows 7 ultimate and it wont give the #
Chirpout said:
Can this be done using a Mac?
Click to expand...
Click to collapse
yes, i believe the guide states something about that..not exactly sure, you can also use google for more help
Hi, I know this is really out of date, but I have to send my phone back because the screen is cracked (inner touch screen) and I wanted the phone to be completely stock. I never rooted the phone. I only unlocked the bootloader. I found this thread hoping I could relock the bootloader to make it look like I never unlocked it in the first place. Of course once I reached Step 7, I don't get the # sign. I get the $ sign and I don't know what to do :/
Note from the Author -
I am moving on to the N5 now and ditching my S3. I will continue to maintain this thread, however - please do PM me if you think that something needs to be changed or updated in this thread as I doubt I will be answering questions within the thread as much. Please don't PM support questions to me. Only PM updates that need to be made in the thread.
It's been a blast!
Regards
Dan
Please read this thread. Do not dismiss the "send for repair" option. Please do not create further threads asking for help because "nothing worked". I have included everything we know to be a working fix. If nothing here fixed your issue, send it for repair. Don't create yet another pointless thread like the 10 others a day we have to read...
IMEI
A unique identification number programmed onto your phone. It is required in order to be correctly identified on a mobile network. Without one, you cannot make calls, send SMS or use mobile data. Important stuff.
/efs
A partition on your internal memory containing important data including the IMEI. If the data in this partition gets corrupt, you will lose your IMEI
0049*** or 0000 IMEI
A generic IMEI, meaning your real IMEI is not readable, presumably because it is corrupt but there are other reasons too.
This thread aims to give you as much basic information as possible in an attempt to prevent the 10 - 20 threads we're getting per day about this issue.
I have a 0049 or 0000 IMEI. Why?
This means your phone cannot read your IMEI. There are 2 main reasons for this.
1) /efs is corrupt.
Whenever you flash a ROM, be that a custom ROM via a custom recovery or an official ROM via Odin, you risk corrupting your /efs partition and losing your IMEI.
There are 3 main steps to take to try to resolve this
Restore your EFS from a backup - A logical first step
No backup? Reflash the latest stock ROM using Odin*
Send the device for repair**
*Ultima rom users (prior to v15), first reflash the rom, choosing a non-stock kernel during the aroma install wizard first. Boefla is a good choice to test.
** a couple with "cannot mount /efs" errors have fixed their device by flashing ics. If you know you haven't got a VTU00M eMMC firmware 0xf1 - go for it. However for those of you who don't know, this would be extremely dangerous. You could get SDS so I do not recommend this action. If you are foolish enough to try it, flash 4.1.2 immediately afterwards.
2) /efs partition format changed
A quick note before going forward... when looking at a ROM build number, the last 3 characters mean Year, Month, Revision. Let's take XXEMG4 for example. M = 2013, G = July, 4 = revision 4. See "Other" section at the end of this post for more info
From July 2013 (XXEMG4) onwards, official Samsung ROMs change the format of your EFS Directory/Partition. Let's say these ROMs change from EFS v1 to EFS v2. Only basebands from July 2013 (MG2) onwards can read EFS v2.
Quick info rules:
EFS v2 Basebands can read EFS v2 and EFS v1
EFS v1 basebands CANNOT read EFS v2, ONLY EFS v1
This means if you have flashed an official ROM (or custom ROM based on official) From July 2013 (MG* or newer), you are now in a situation whereby only an EFS v2 baseband (MG* or newer) can read the IMEI in /EFS.
If you have ever flashed XXEMG* (or newer) ROM, to keep your IMEI working, you must:
Stay with the EFS v2 basebands (MG* or newer). You may flash other ROMs but must return to the MG* (or newer) baseband
Restore your EFS backup (taken before XXEMG* or newer ROM install) to use older (EFS v1) basebands. EFS backup must be an EFSv1 backup to use an EFS v1 baseband
If the above don't work, consider sending for repair...
*Ultima rom users (prior to v15), first reflash the rom, choosing a non-stock kernel during the aroma install wizard first. Boefla is a good choice to test.
Please note, it is flashing the ROM that alters EFS format, not the basebands themselves. You can flash the MG* or newer basebands safely on their own and return to an older baseband without issue.
You can download an EFS v2 baseband (CWM) flashable package HERE - updated to MJ3 by @maatsby
Aroma installer, choose between MG2, MG4, MH1 and MJ3 basebands
Basebands alone do not alter efs format
Backs up EFS in an uncompressed format (Use Root Explorer to restore)
Does NOT include RIL, works on AOSP and Sammy
For discussion of the efs format issue, see this thread.
How do I backup and restore /efs?
There are a few methods to backup /efs, but they all require customisation of your phone. Either root access, or a custom recovery. I appreciate that many of you do not wish to root your phones and just want to flash official ROMs via Odin... Well here are your choices:
Only use OTA or KIES to update (Official Method)
Root using CF auto root / Framaroot - backup efs and THEN flash via ODIN
Flash a custom recovery via Odin, backup efs and THEN flash a ROm via Odin
Risk it. Don't backup efs. Simply flash via Odin and hope for the best
...and here are the options for backing up / restoring efs (this list is not exhaustive)
EFS Pro - App needs root
SGSIII EFS backup / Restore - app runs from Windows / Linux and needs root
kTool - app needs root.
Philz advanced CWM rewcovery - custom recovery can take efs backups using the "Custom Backup" feature.
It's worth noting that some custom ROMs will give the option to backup efs, but you can never have too many backups!
.tar and .tar.gz backups can be extracted on /sdcard and then manually used to replace the files in /efs using a root explorer or adb as a last resort. Some people have reported more success deleting the /efs folder contents before hand. This is risky though, so only those of you who can backup the /efs with Philz recovery before trying this - should try it. Why Philz recovery backup the already broken EFS? well you can restore it if the phone doesn't boot and at least you are no worse off than before attempting this method. Messing woith EFS can cause your phone to not boot up so be CAREFUL!!!
Please see below for step-by-step instructions to restore a folder dump* of EFS using adb. Do so at your own risk!!!
This is useful if you cannot boot.
*An example of a folder dump would be an efs backup created using my mg baseband pack linked earlier in this thread.
Pre requisite is having adb "installed" on yoru windows PC. Download THIS file and follow the instructions in the readme.
1) Boot into recovery, connect usb and go to "mounts and storage". Toggle the "mount efs" and "mount data" options to mount these partitions. Tip, when mounted, the option then becomes "unmount x"
2) Open "cmd" in Windows and type "adb shell" to get to your adb prompt.
3) If you don't know where your efs folder dump is, you'll need to look for it using the list command. I know mine is on internal SD but I forget the name of it... (if you already have this on a computer, skip to step 4...
Code:
ls /data/media/0
lists all directories on my internal sd card. I now see it's called MG_EFS
Code:
exit
adb pull /data/media/p/MG_EFS c:\users\rootsu\desktop\MG_EFS
Now your folder dump is on your windows desktop.
It should look like this:
{
"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"
}
Please note at this stage, my MG_EFS contained dated folders each with backups. I took the content of one of these dated folders and dropped them directly inMF_EFS
4) type "adb shell" again to get into adb and check your efs contents is visible
Code:
ls -lh /efs
This will list your efs contents and permissisons:
Code:
-rw-rw-r-- 1 radio radio 152 Jan 1 2012 00000000.authtokcont
drwxr-xr-x 2 system system 4.0K Aug 10 17:37 FactoryApp
drwxrwxr-x 2 radio system 4.0K Aug 10 17:37 bluetooth
drwxrwxr-x 3 drm system 4.0K Aug 10 17:37 drm
-rw-rw-rw- 1 system system 6 Aug 13 2012 gyro_cal_data
-rw-r--r-- 1 radio radio 1.1K Jan 1 2012 h2k.dat
drwxrwxr-x 2 radio system 4.0K Aug 10 17:37 imei
drwx------ 2 root root 4.0K Jan 1 1970 lost+found
-rw------- 1 radio radio 7.6K Sep 10 06:45 nv.log
-rwx------ 1 radio radio 2.0M Sep 10 12:59 nv_data.bin
-rwx------ 1 radio radio 32 Sep 10 12:59 nv_data.bin.md5
drwxrwxr-x 2 radio system 4.0K Aug 10 17:37 wifi
-rw-r--r-- 1 radio radio 220 Jan 1 2012 wv.keys
5) Once confirmed you get a list similar to above (as opposed to nothing) take a screenshot of the files and remove the efs contents...
Code:
rm -Rf /efs/*
and use the list command again to confirm nothing is returned when looking in the efs parrtition
Code:
ls -lh /efs
6) Push your folder dump back to place and ls to check it worked
Code:
exit
adb push c:\users\rootsu\desktop\MG_EFS /efs/
adb shell
ls -lh /efs
7) You will probably notice that the permissions differ to those in your screenshot. If so, paste the below block command to grant the permissions back into the /efs
Code:
chmod 664 /efs/00000000.authtokcont
chmod 755 /efs/FactoryApp
chmod 775 /efs/bluetooth
chmod 775 /efs/drm
chmod 666 /efs/gyro_cal_data
chmod 644 /efs/h2k.dat
chmod 775 /efs/imei
chmod 700 /efs/lost+found
chmod 600 /efs/nv.log
chmod 700 /efs/nv_data.bin
chmod 700 /efs/nv_data.bin.md5
chmod 775 /efs/wifi
chmod 644 /efs/wv.keys
8) Exit and reboot
Code:
exit
adb reboot
There you have it, folder dump restored. If you're wondering if I did this myself before writing this guide, the answer is YES. I happily guinea pigged my device for you
Here is the full command list I used.
adb shell
ls /data/media/0
exit
adb pull /data/media/0/MG_EFS c:\users\rootsu\Desktop\MG_EFS
adb shell
ls -lh /efs
rm -Rf /efs/*
ls /efs
exit
adb push c:\users\rootsu\desktop\MG_EFS /efs/
adb shell
ls -lh /efs
chmod 664 /efs/00000000.authtokcont
chmod 755 /efs/FactoryApp
chmod 775 /efs/bluetooth
chmod 775 /efs/drm
chmod 666 /efs/gyro_cal_data
chmod 644 /efs/h2k.dat
chmod 775 /efs/imei
chmod 700 /efs/lost+found
chmod 600 /efs/nv.log
chmod 700 /efs/nv_data.bin
chmod 700 /efs/nv_data.bin.md5
chmod 775 /efs/wifi
chmod 644 /efs/wv.keys
ls -lh /efs
exit
adb reboot
I heard I can manually modify my IMEI, transplanted from another device?
Modifying an IMEI is illegal in many countries. Even if this was possible, discussion here would be against the rules. Your IMEI must not be modified. Either restore a backup or send for repair.
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymode
If they fail, use the more detailed commands:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
This should hopefully return you to user mode. If not, the last thing you can try, which reportedly works is to delete /efs/FactoryApp/ folder, then factory reset from recovery. This *should* regenerate the folder. Your factory mode will still need "echo -n ON >> /efs/FactoryApp/factorymode" doing though, which can be done as described above or opening the file in a text editor and changing the content of the file to "ON"
Failing that, flash stock and send for repair.
See here for more info on factory mode
How does "Ariza patch" fit in to this?
Ariza patch does not fix IMEI issues. It fixes "00000" Serial number issues, which has similar symptoms. This patch does not work on EFS v2 ROMs. If you use it, you may irreparably break your phone.
Also it would seem, Phones that had this patch ON EFS v1 ROMS will break their IMEI if they upgrade to EFS v2 ROMS.
As yet, there is nothing proved to resolve this issue fully. Search the Ariza thread for posts by zuluman for potential fixes. This Page is hopefully the most useful or one of the patched modems posted
It would probably be best to get the serial number professionally restored either under warranty or by sla mobile repair shop. The Ariza patch was always only fixing something that should have been fixed under warranty anyway.... now we are seeing this issue - cut your losses
Send for repair
A couple of notes on this. Firstly, "Send for repair" does not necessarily mean you must return it to Samsung / Your carrier. It is simply a phrase. Many EFS issues can be resolved by taking it to a mobile repair shop.. In the UK, There's one on almost every street in a town / city centre, and they will charge about £20 to get it repaired. Around $25 USD / EUR. If you are out of warranty or are in a rush for the repair, this is a good option and yes, people are known to have been successful with this...
Secondly, a more personal note. If I suggest "send for repair" as a solution for you, it is not because I am unwilling to get involved in troubleshooting or helping (although this is all already covered in this post) - It is because I truly believe this is the best or only option for you. Mostly I will only recommend it if it is the only option. Seeing me say this a lot in this thread is because we need people to accept that there can only be a finite amount of approaches to fixing the issue. In some cases, I will recommend it if it is the BEST option. An example of that would be the ariza patch situation. The Change in EFS format broke all those serial number 000000 phones that were fixed with the ariza patch. It was my opinion before MG4 that serial number 000000 should have been the resolution to this issue. It still is. At the moment, there are not many options for broken ariza patched phones. My opinion is this is the order of best solutions.
1) Repair
2) Wait for ariza update
3) Try Zuluman patch.
I have said this a lot but it needed to go here too..
Other
How to work out when your baseband / ROM was released.
1) Take the last 3 characters from the name.
2) Compare the first of these characters against the below to get the year
L=2012
M=2013
3) Compare the second of these characters against the below to get the month
A=January
B=February
C= March
D=April
E=May
F=June
G=July
H=August
J=September
K=October
L=November
k=December
4) take the last of the 3 characters and compare against the below to get the revision number
1=Revision 1
2=Revision 2
3=Revision 3
4=Revision 4
5=Revision 5
6=Revision 6
7=Revision 7
8=Revision 8
9=Revision 9
A=Revision 10
B=Revision 11
C=Revision 12
D=Revision 13
E=Revision 14
F=Revision 15
etc
example:
MG4 = 2013 - July - Revision 4
This is a work in progress. None of this is my work, I am just compiling it into a single thread, so thanks to everyone answering questions in Q&A. If there is anything missing that you think should be added, please say so.
I used the app kTool to backup my efs. Won't that work?
Nice one :thumbup::thumbup:
rootSU said:
*note - efs | backup your efs | backup your efs | backup your efs | backup your efs | backup your efs | backup your
IMEI
A unique identification number programmed onto your phone. It is required in order to be correctly identified on a mobile network. Without one, you cannot make calls, send SMS or use mobile data. Important stuff.
/efs
A partition on your internal memory containing important data including the IMEI. If the data in this partition gets corrupt, you will loose your IMEI
0049*** IMEI
A generic IMEI, meaning your real IMEI is not readable, presumably because it is corrupt but there are other reasons too.
This thread aims to give you as much basic information as possible in an attempt to prevent the 10 - 20 threads we're getting per day about this issue.
I have a 0049 IMEI. Why?
This means your phone cannot read your IMEI. There are 2 main reasons for this.
1) /efs is corrupt.
Whenever you flash a ROM, be that a custom ROM via a custom recovery or an official ROM via Odin, you risk corrupting your /efs partition and losing your IMEI.
There are 4 main steps to take to try to resolve this
Restore your EFS from a backup - A logical first step
No backup? Reflash a stock ROM using Odin
Send the device for repair.
2) /efs partition format changed
The latest UK (BTU) 4.1.2 release (XXEMG4) which comes with the baseband of the same name, actually changes the format of efs.
If you have flashed XXEMG4 at any point, you are now in a situation whereby only the MG4 baseband can read the IMEI in /efs. The new efs format is not backwards compatible with older basebands. Probably, all new basebands will be compatible so in time this issue should diminish I expect.
If you have ever flashed XXEMG4, to keep your IMEI working, you must:
Stay with the baseband MG4. You may flash other ROMs but must return to the MG4 baseband.
Restore your efs backup (taken before MG4) to use older basebands.
For discussion of this issue, see this thread.
How do I backup and restore /efs?
There are a few methods to backup /efs, but they all require customisation of your phone. Either root access, or a custom recovery. I appreciate that many of you do not wish to root your phones and just want to flash official ROMs via Odin... Well here are your choices:
Only use OTA or KIES to update (Official Method)
Root using CF auto root / Framaroot - backup efs and THEN flash via ODIN
Flash a custom recovery via Odin, backup efs and THEN flash a ROm via Odin
Risk it. Don't backup efs. Simply flash via Odin and hope for the best
...and here are the options for backing up / restoring efs (this list is not exhaustive)
EFS Pro - App needs root
SGSIII EFS backup / Restore - app runs from Windows / Linux and needs root
Philz advanced CWM rewcovery - custom recovery can take efs backups using the "Custom Backup" feature.
I heard I can manually modify my IMEI, transplanted from another device?
Modifying an IMEI is illegal in many countries. Even if this was possible, discussion here would be against the rules. Your IMEI must not be modified. Either restore a backup or send for repair.
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymode
If they fail, use the more detailed commands:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
This should hopefully return you to user mode. If not, restoring to stock and / or restoring an efs backup may be the next things you try before sending for repair.
See here for more info on factory mode
Other
This is a work in progress. None of this is my work, I am just compiling it into a single thread, so thanks to everyone answering questions in Q&A. If there is anything missing that you think should be added, please say so.
Click to expand...
Click to collapse
Nice information here again, I would add that some custom roms allow you to backup your efs
Sent from my GT-I9300 using Tapatalk 4 Beta just to annoy Gus
sidh10 said:
I used the app kTool to backup my efs. Won't that work?
Click to expand...
Click to collapse
As I said the list is not yet exhaustive
With kernels like siyah they create 2 efs files on the Internal SD card, is it enough to copy these to drop box or something and restore only if they are ever needed?
Sent from my GT-I9300 using xda app-developers app
Should be enough although I personally keep 3 separate backups
Sent from my GT-I9300 using Tapatalk 4
I was wondering.
I had a Galaxy Nexus, and Galaxy S III
What if I restore their backup efs into my current Galaxy S III
Will my second 9300's IMEI changed into old i9300 or i9250? Or just mess it up?
Sent from my GT-I9300 using xda premium
Doubtful. You cannot use someone else's efs backup to restore your own.
Sent from my GT-I9300 using Tapatalk 4
What happen in case my imei is correct and no have network connection? No registre network in case of arizapatch?
Sent from my GT-I9300 using xda app-developers app
Patch it
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Patch it
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
sorry I did not express well my question is why does that happen imei correct and no registre network
Sent from my GT-I9300 using xda app-developers app
No idea. Not to do with this thread. Try arizapatch?
Sent from my GT-I9300 using Tapatalk 4
Very neat, although I'd fix the 'loose' to 'lose'.
rootSU said:
No idea. Not to do with this thread. Try arizapatch?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
I have a lot of time using the patch but I have no answer because it passes / thanks anyway for the explanation of efs
Sent from my GT-I9300 using xda app-developers app
Choristav said:
Very neat, although I'd fix the 'loose' to 'lose'.
Click to expand...
Click to collapse
Thanks. Typo
Sent from my GT-I9300 using Tapatalk 4
qtwrk said:
I was wondering.
I had a Galaxy Nexus, and Galaxy S III
What if I restore their backup efs into my current Galaxy S III
Will my second 9300's IMEI changed into old i9300 or i9250? Or just mess it up?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You could potentially brick your device as is the case when flashing anything from another device onto your own, it would definitely cause problems with registering on your network.
If your network finds out as well you could also have a friendly visit from the police for cloning an IMEI. (it doesn't matter if you own the other device you are trying to change the ID of the device which is illegal.
Sent from my GT-I9300 using Tapatalk 4 Beta just to annoy Gus
@rootSU and others ,
guys i'm in trouble , i lost my imei and the classic "No service" error is haunting me,
i do have the back up efsbackup.tar.gz and efsdev-mmcblk0p3.img.gz in sdcard but how do i restore (the easiest way ? btw i have no idea by what action these backups are created , they were just there when i looked) plus, do i need to get back to stock before restore ? currently on a 4.2.2 rom . Thank you
Try
http://forum.xda-developers.com/showthread.php?t=1308546
chris_marsh said:
@rootSU and others ,
guys i'm in trouble , i lost my imei and the classic "No service" error is haunting me,
i do have the back up efsbackup.tar.gz and efsdev-mmcblk0p3.img.gz in sdcard but how do i restore (the easiest way ? btw i have no idea by what action these backups are created , they were just there when i looked) plus, do i need to get back to stock before restore ? currently on a 4.2.2 rom . Thank you
Click to expand...
Click to collapse
I've linked 3 apps in post 1. One of those should help
Sent from my GT-I9300 using Tapatalk 4
{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
Hi guys,
I present here with small tutorial to backup your sdcard and your applications with their data. For this you'll required to know adb commands which I've posted in Moto G Index thread which can be found here. (I've too referred it and learnt about this process. Even you can create many more if you are crazy like me )
Backing up sdcard and your applications with their data is essentially process to keep them safe in case something goes wrong with your phone and need to be wiped.
I know that there are lot of other third party apps like Titanium Backup, Helium etc which are available in Google Play Store which can do this task.
But this method is safe, easy, reliable and works on stock and rooted devices.
Before starting, you need to download the zip which is attached in this post or you can also download Android SDK and install it on you PC and work on this commands.
Now, Go to Settings --> Developer options --> Check "usb debugging".
Connect your device to pc.
Backup & Restore sdcard
Backup :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb pull /sdcard/ /sdcard/
This command will pull your sdcard (not move or cut) to "c" directory under "sdcard" folder.
This process may take time depending upon the size of your sdcard. Please don't abort it until finishing.
Restore :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb push sdcard /sdcard/
This command will push the "sdcard" to your device.
This process may take time depending upon the size of your sdcard. Please don't abort it until finishing.
Hit thanks if you find this useful.
Backup & Restore Applications and Their Data
Backup :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb backup -apk -noshared -all -nosystem
Now look at your device and accept backup process. (You can continue without entering the password)
Wait until finishing.
This will backup your apps and their data to the PC (a "backup.ab" file will be created in the same folder).
Restore :
Open a command prompt (shift + mouse right click) in "sdk platform" or in the folder downloaded from here, and type
Code:
adb devices
Press ENTER Key. You must see your device serial number. If you don't see it, probably your device drivers are not installed properly on your PC.
Now type
Code:
adb restore backup.ab
Now look at your device and accept restore process. (If you entered the password while backing up, you need to enter it while restoring)
Wait until finishing.
This will restore your applications and their data to device.
Hit thanks if you find this useful.
It will be useful to change rom and not lose the progress of the games and some configurations?
Excuse my bad English.
Ivan!
Leproso_Ivan said:
It will be useful to change rom and not lose the progress of the games and some configurations?
Excuse my bad English.
Ivan!
Click to expand...
Click to collapse
AFAIK, some of the app's data is not properly restored. (Experienced this when my device was not rooted)
Mr hOaX said:
AFAIK, some of the app's data is not properly restored. (Experienced this when my device was not rooted)
Click to expand...
Click to collapse
I will try when I change the rom.
Iván!
{
"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"
}
took a long time and that was only backing up SD card lol. but I can say it can successfully backup
bublz654 said:
took a long time and that was only backing up SD card lol. but I can say it can successfully backup
Click to expand...
Click to collapse
It depends upon your SD Card size
Good job for uploading screenshot for others
Credits given
Mr hOaX said:
It depends upon your SD Card size
Good job for uploading screenshot for others
Credits given
Click to expand...
Click to collapse
I had 7.18 GB on my SD card lol. no problem for screen shot I'll try n backup app+data soon
please help, I'm trying to do backup the fourth time now and I keep getting that, I rebooted phone deleted. c:/sdcard directory its not working. what can I do ?
never mind I got 5th time lucky
I finished backing up my apk + data it didn't show any successful pop-up but I guess it works
where the backup.ab file ?
wouldn't pulling the whole data partition do the same job in one shabang?
meangreenie said:
wouldn't pulling the whole data partition do the same job in one shabang?
Click to expand...
Click to collapse
don't think so, in just trying to find where the backup. an file is for my backed up apps and their data
bublz654 said:
don't think so, in just trying to find where the backup. an file is for my backed up apps and their data
Click to expand...
Click to collapse
Sorry for late reply mate.
But your backup file is saved where you adb and fastboot files are present!
It's in the directory where you had launch adb cmds to start the backup process.
If you don't find it still search it in C:\ drive or else your backup process was aborted because of failure.
It works for me, and you usually get prompts on your device to start the backup process and also get the prompts to restore the backup.
If you are facing more issues, PM me
Mr hOaX said:
Sorry for late reply mate.
But your backup file is saved where you adb and fastboot files are present!
It's in the directory where you had launch adb cmds to start the backup process.
If you don't find it still search it in C:\ drive or else your backup process was aborted because of failure.
It works for me, and you usually get prompts on your device to start the backup process and also get the prompts to restore the backup.
If you are facing more issues, PM me
Click to expand...
Click to collapse
Ok man thanks for explaining, i will look for the backup.ab wheres the adb n fastboot files tomorrow. This guide is great
Sent from my iPod touch using Tapatalk
Hello! Does it work if I do a backup on a motoG Lte then I restore it in another one motoG Lte? Becouse I have to send it back to where I've bought it and they're shipping me a new one
Thanks in advance!
is that the backup.ab folder ? (6th file from top )
bublz654 said:
is that the backup.ab folder ? (6th file from top )
Click to expand...
Click to collapse
Yes mate. I'm extremely sorry for late reply. I was unavailable these days.
If you are not able to restore that *.ab file, then it is "corrupted" due to incomplete process of backup!
bazuzu666 said:
Hello! Does it work if I do a backup on a motoG Lte then I restore it in another one motoG Lte? Becouse I have to send it back to where I've bought it and they're shipping me a new one
Thanks in advance!
Click to expand...
Click to collapse
Yes mate
Mr hOaX said:
Yes mate. I'm extremely sorry for late reply. I was unavailable these days.
If you are not able to restore that *.ab file, then it is "corrupted" due to incomplete process of backup!
Yes mate
Click to expand...
Click to collapse
The .an file worked when restoring. When trying to restore SD card it says could not find SD card folder. So I had to move everything manually
@MikeChannon removed OP. please close
what? lol
Good good. Can't wait! :silly:
workdowg said:
Good good. Can't wait! :silly:
Click to expand...
Click to collapse
i'm working on an automated deploying (kind of the one for restoring the bios) and i will start with the 1050f one. automated because otherwise things can get messy
maybe you can prepare some tutorial for the X part based on your experience (tho i, as a proud windows user, didnt believed people use that stuff and i'm sure goes the other way around )
ionioni said:
i'm working on an automated deploying (kind of the one for restoring the bios) and i will start with the 1050f one. automated because otherwise things can get messy
maybe you can prepare some tutorial for the X part based on your experience (tho i, as a proud windows user, didnt believed people use that stuff and i'm sure goes the other way around )
Click to expand...
Click to collapse
Will do Master Chef! It really was simple once the base is done...
Proof of concept (Actually it just plain works...):
Arch x86_x64 - LXDE (with Pulse sound) running on Xsdl
{
"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"
}
If Installed, Can I steam game?
neverapple88 said:
If Installed, Can I steam game?
Click to expand...
Click to collapse
Most likely, if the linux graphics driver works with the embedded SoC graphics driver. And it seems Android also uses the same i915 driver.
update: need a 1050F owner to test the AoL deployment tool... my device is a 1380F so i cannot test thoroughly, i want to test it with a real owner. pm for details. worst case: you will have to flash kitkat rom back, best case: it keeps all the existing files in place, stealing space from data partition for the new linux. waiting...
ionioni said:
update: need a 1050F owner to test the AoL deployment tool... my device is a 1380F so i cannot test thoroughly, i want to test it with a real owner. pm for details. worst case: you will have to flash kitkat rom back, best case: it keeps all the existing files in place, stealing space from data partition for the new linux. waiting...
Click to expand...
Click to collapse
Anyone??? Everybody was so excited and no one wants to try? I'll do it if nobody else will. For me it means backing up my current Linux and Android partitions (been working hard at getting them lean and mean) partitions and going through the whole flash from kitkat ordeal again... for probably the 10th time at least...
Sent from my YOGA Tablet 2-1050F using Tapatalk
workdowg said:
Anyone??? Everybody was so excited and no one wants to try? I'll do it if nobody else will. For me it means backing up my current Linux and Android partitions (been working hard at getting them lean and mean) partitions and going through the whole flash from kitkat ordeal again... for probably the 10th time at least...
Sent from my YOGA Tablet 2-1050F using Tapatalk
Click to expand...
Click to collapse
yeah, funny thing...
upped a first version of the tutorial
and the first batch of files (for 830 and 1050)
I could not wait a few days ago. I excited.
But I can't English well. So it is difficult to test.
I wanted the first Windows. But if Linux works reliably, I would choose Linux. (I'm ubuntu user)
I think Intel graphics drivers are going to be good as the performance by Android. (for steam game!)
However, one problem occurred.
I used data parted More than 20GB. (sry my english)
This space is insufficient to install Linux and applications and steam game.
The workaround is to install a Linux partition on the sd card.
Can I install a Linux partition on the sd card? (and run)
ps. After entering the text has been changed the post. I'll go to see the Thread.
neverapple88 said:
I could not wait a few days ago. I excited.
But I can't English well. So it is difficult to test.
I wanted the first Windows. But if Linux works reliably, I would choose Linux. (I'm ubuntu user)
I think Intel graphics drivers are going to be good as the performance by Android. (for steam game!)
However, one problem occurred.
I used data parted More than 18GB. (sry my english)
This space is insufficient to install Linux and applications and steam game.
The workaround is to install a Linux partition on the sd card.
Can I install a Linux partition on the sd card? (and run)
Click to expand...
Click to collapse
this IS ONLY FOR UNCHANGED STOCK PARTITIONS LAYOUT (it will refuse to install if it detects that your data partition is not having the original configuration), it CHANGES your partitions by adding two more partitions a big one (min. 1024MB but you can make it bigger durin installation) and a small one for the original Android initramfs (read the tutorial to understand more) and that space is taken (ripped off) from the data partition. and whenever you will uninstall it will remove the two new partitions and restore the data partition to the original size
i did not did (i had a manual setup at some point) a setup to sdcard s it is too slow ( @workdowg can give you more details, as he stayed on that configuration more i went for the on the internal partition variant quickly when i've seen how much it takes to work with files when you 're having linux on sdcard)
also on the X related issues you should talk with him (i didn't used X on AoL, i only use shell tools/servers)
you should flash back your Android and check that you have the original partitions (number, size and names) before trying to install.
I have made a mistake when installing. (no insert rootfs file, uninstall, etc ...)
now. my /data partition 11.11GB (OMG,,,)
I've tried a factory reset. but no change. (GB)
how to? ...
ps. I want to work with the command.
neverapple88 said:
I have made a mistake when installing. (no rootfs file, uninstall, etc ...)
now. my /data partition 11.11GB
I've tried a factory reset. but no change.
how to? ...
Click to expand...
Click to collapse
use the corresponding tool from this post (if youre on lollipop use the lollipop one) it will open a root shell on a very early boot (without Android loading), you have to start in DnX mode then start the tool
after the shell opens, open another command window and push the extracted (attached) gdisk (it's a static IA32 version i compiled for working with GPT partitions) to your tab
adb push gdisk /tmp/gdisk, return to the root shell and input
chmod 755 /tmp/gdisk
/tmp/gdisk -p /dev/block/mmcblk0
and post the result
the partition.txt attached shows how ot should be default configurations of the partitions on a 1050 (830) device
ionioni said:
use the corresponding tool from this post (if youre on lollipop use the lollipop one) it will open a root shell on a very early boot (without Android loading), you have to start in DnX mode then start the tool
after the shell opens, open another command window and push the extracted (attached) gdisk (it's a static IA32 version i compiled for working with GPT partitions) to your tab
adb push gdisk /tmp/gdisk, return to the root shell and input
chmod 755 /tmp/gdisk
/tmp/gdisk -p /dev/block/mmcblk0
and post the result
the partition.txt attached shows how ot should be default configurations of the partitions on a 1050 (830) device
Click to expand...
Click to collapse
I first start DnX mode -> run tmp-root-1050F-lollipop -> run normal cmd
(cmd) >adb push gdisk /tmp/gdisk
adb server is out of date. killing...
* daemon started successfully *
5597 KB/s (492988 bytes in 0.086s)
after root cmd is shutdown(end)
neverapple88 said:
I first start DnX mode -> run tmp-root-1050F-lollipop -> run normal cmd
(cmd) >adb push gdisk /tmp/gdisk
adb server is out of date. killing...
* daemon started successfully *
5597 KB/s (492988 bytes in 0.086s)
after root cmd is shutdown(end)
Click to expand...
Click to collapse
but the root shell opens??? you must wait until it opens the root shell yeah, it opens otherwise you would not be able to push (i was reading too fast)
the window gets killed because the temp_root has a differnet version of adb and on your pc there is another and when you try to do the adb push you kill the adb from the tmp_root, but that is not a problem, just do a adb shell after you did the push and it will open anothe root shell and you can enter and input the other commands
also, have you seen the text file with the partitions? you seemed surprised and i don't know why, on the default configuration the data has around 11GB, do not confuse that with the whole mmc that has 16
ionioni said:
but the root shell opens??? you must wait until it opens the root shell yeah, it opens otherwise you would not be able to push (i was reading too fast)
the window gets killed because the temp_root has a differnet version of adb and on your pc there is another and when you try to do the adb push you kill the adb from the tmp_root, but that is not a problem, just do a adb shell after you did the push and it will open anothe root shell and you can enter and input the other commands
also, have you seen the text file with the partitions? you seemed surprised and i don't know why, on the default configuration the data has around 11GB, do not confuse that with the whole mmc that has 16
Click to expand...
Click to collapse
Thank you! It has been recovered.
This was a fun experience. (and risk...) XD
I'd like to know more, but do not know the English language. :silly:
So I'll use the Arch Linux.
Your articles are hard to read, But Thank you for your time.
neverapple88 said:
Thank you! It has been recovered.
This was a fun experience. (and risk...) XD
I'd like to know more, but do not know the English language. :silly:
So I'll use the Arch Linux.
Thank you for your time. : D
Click to expand...
Click to collapse
Theres an Ubuntu too now...
ionioni said:
Theres an Ubuntu too now...
Click to expand...
Click to collapse
C
===============================================
Found ready-made linux rootfs.tgz file, pushing to device...
Checking for valid deployment enviroment
Error! Invalid <failed check> data partition end sector.
Have you already deployed Linux? If so try restoring first.
ABORTING! Nothing was changed!
OMG.. (I try fix)
neverapple88 said:
C
===============================================
Found ready-made linux rootfs.tgz file, pushing to device...
Checking for valid deployment enviroment
Error! Invalid <failed check> data partition end sector.
Have you already deployed Linux? If so try restoring first.
ABORTING! Nothing was changed!
OMG..
Click to expand...
Click to collapse
nothing to be scared of, it has not changed anything, just detected that something is wrong and exited
what is your partition layout? it compares what he reads against the stock values and if they don't match he gives error.... can you run a command so that we see the EXACT layout of your partitions? (number, start_sector, end_sector, name)
you could use the commands i asked you previously to run
temp_root -> adb push gdisk... etc and you will get a print of the partitions on your device
what is your mmc capacity (16GB?) if your mmc is a 32GB one then download and use this