Related
Hey ,,
I have HTC Desire with s-off and 2.3.3 custom ROM.
I woke up and the phone was freezing ,, take the battery out and start the phone it is not working - freezing after a few seconds -. I toke a backup , then, wipe all data .. It works ,, when I restore my backup it not working ,, Freezing on "Why so serios?" screen. try I again to restore it says there is a problem with md5 file .. I compare old update with the new there is a file missing "nandroid.md5" I copied it from old update to the new one ,, the same problem with md5 .. I opened it .. it has "
14fa55a021bf4d27d9c9f2f26b4f832d boot.img
db8dd13c067592b11a3e657737eb9d2c cache.img
97d100af63d227762276163a57263977 data.img
c3c1ed764a5d0c830d36ed5a262836c3 recovery.img
8d523becbc91b3b4c406775e9e39b384 sd-ext.img
c64cd9c27cd00d8eaf3bb5e890b0ad58 system.img
"
I get the md5 for the new update and edit the file nandroid.md5 .. It not working
I have very importance messages ..
What can I do ??
Thanks .. sorry for my bad language.
ok so you have no nandroid md5 file?? Do you have a pc backup of your backup?
If not, you should
I was going to suggest md5 mismatch but since the file is missing it must be a bad backup - are you using CWM recovery by any chance?
Do you have a pc backup of your backup?
Click to expand...
Click to collapse
Do you mean I copied the backup from SDCard to PC. If you mean that . YES I have ..
I'm using CWM.
SHS2000 said:
Do you mean I copied the backup from SDCard to PC. If you mean that . YES I have ..
I'm using CWM.
Click to expand...
Click to collapse
Firstly, this has only happened to me using CWM so I recommend swapping to Amon-RA - which I've never had a single issue with...
BUT BE AWARE - YOU CANNOT RESTORE A CWM BACKUP WITH AMON-RA OR VICE VERSA
If your pc backup is up to date enough could you not restore that backup to get your data back? Or is the nandroid.md5 missing from there too?
BigMrB said:
Firstly, this has only happened to me using CWM so I recommend swapping to Amon-RA - which I've never had a single issue with...
BUT BE AWARE - YOU CANNOT RESTORE A CWM BACKUP WITH AMON-RA OR VICE VERSA
If your pc backup is up to date enough could you not restore that backup to get your data back? Or is the nandroid.md5 missing from there too?
Click to expand...
Click to collapse
Hey .. I have fixed the md5 file .. Now when I restore the last backup It restored but the phone freezing on Why so serios?" screen. I tried to restore only data by Advanced restore the phone restarting on HTC screen. it no restart from the beginning only HTC screen.
the update that on my PC is not up to date enough. the important messages not in it.
I will travel in two days . I have to get the messages
waiting your answer
Do you not have scheduled Titanium backups?
If your backup is corrupt you may be screwed .... are you talking about text messages that are so important? Recieved or sent?
With vodafone i can see all txt messages ive sent out on my online account don't know if you can do something similar?
When you say you have fixed the md5 file... do you mean you had an md5 mismatch?
He had a mismatch. Not sure how he "fixed" it.
Easy to fix takes 20 seconds in terminal emulator... but if his phone won't boot.... lol
Everytime I fix a mismatch it worked fine after
BigMrB said:
Easy to fix takes 20 seconds in terminal emulator... but if his phone won't boot.... lol
Everytime I fix a mismatch it worked fine after
Click to expand...
Click to collapse
Oh cool. Can you let me know how please?
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
BigMrB said:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
Hey ..
Yes, Text messages received and sent. We don't have a service to see them online.
I fixed it but not like you.
I replaced the backup files except nandroid.md5 . then I opened "nandroid.md5" and change the md5 for files.
"
[email protected]:~$ cd Desktop/01-09-2011.0050
[email protected]:~/Desktop/01-09-2011.0050$ md5sum data.img
97d100af63d227762276163a57263977 data.img
"
I did this for all files ...
Now when I restore the backup It won't boot
what can I do ..
BigMrB said:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
Click to expand...
Click to collapse
Ah Right. Thanks. So by fixing it, you're creating a new MD5 checksum for the files.
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
SHS2000 said:
Hey ..
Yes, Text messages received and sent. We don't have a service to see them online.
I fixed it but not like you.
I replaced the backup files except nandroid.md5 . then I opened "nandroid.md5" and change the md5 for files.
"
[email protected]:~$ cd Desktop/01-09-2011.0050
[email protected]:~/Desktop/01-09-2011.0050$ md5sum data.img
97d100af63d227762276163a57263977 data.img
"
I did this for all files ...
Now when I restore the backup It won't boot
what can I do ..
Click to expand...
Click to collapse
There is obviously some sort of data corruption. If you havent got a titanium backup of it or anything, I'm afraid to say you may be screwed. You could try to use unyaffs to unpack the data image on a computer and browse the files.
http://code.google.com/p/unyaffs/
Sms should be somewhere like:
Code:
/data/data/com.android.providers.telephony/databases/mmssms.db
rootSU said:
Ah Right. Thanks. So by fixing it, you're creating a new MD5 checksum for the files.
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
There is obviously some sort of data corruption. If you havent got a titanium backup of it or anything, I'm afraid to say you may be screwed. You could try to use unyaffs to unpack the data image on a computer and browse the files.
http://code.google.com/p/unyaffs/
Sms should be somewhere like:
Code:
/data/data/com.android.providers.telephony/databases/mmssms.db
Click to expand...
Click to collapse
Unfortunately I don't have titanium backup at all, so Don't be a afraid say it.
I didn't know how to use unyaffs.
The only other option i could see....
Data recovery from sd card, I did this last week and it took about 10 hours!! And took a long time piecing all the info together... don't get the raw data though because that would take 70 + hours lol
SHS2000 said:
Unfortunately I don't have titanium backup at all, so Don't be a afraid say it.
I didn't know how to use unyaffs.
Click to expand...
Click to collapse
Its easy
Code:
mkdir /home/moj/android/
Download it to that new directory and also put your data.img in there:
http://code.google.com/p/unyaffs/downloads/list
download all 3 files and use the command it says to use in Terminal on ubuntu
Code:
gcc -o unyaffs unyaffs.c
then:
Code:
./unyaffs /home/moj/android/data.img
rootSU said:
Its easy
Code:
mkdir /home/moj/android/
Download it to that new directory and also put your data.img in there:
http://code.google.com/p/unyaffs/downloads/list
download all 3 files and use the command it says to use in Terminal on ubuntu
Code:
gcc -o unyaffs unyaffs.c
then:
Code:
./unyaffs /home/moj/android/data.img
Click to expand...
Click to collapse
Thanks,,
I extract the files.
How can I restore the messages to phone ???
and how can I repackage it ?
Just flash the Rom and do a data wipe. You're not going to be restoring that, but you can at least copy the data into the same place on your fresh install.
Sent from my HTC Desire using XDA App
Or use a working nandroid
Edit> When do I get to know if this fixed it?
Sent from my HTC Desire using XDA App
After Two days ... It restored
Thank you very much ...
I edited a configuration file for Bluetooth(main.conf) in which i changed the device discoverable for value to be 0 (by default 120). then i left the folder as is (r/w) mode and saves and rebooted.
rescue mode is available(volume up - home -power)
boot loops continously
Kies not recognising when connecting when the device is turned off
there is a backup of the file at the same folder..
if you can provide me too ..how do i upload to my phone.
need help ASAP.
try installing firmware with odin
Other better ideas!
I am pretty sure that this matter was triggered because of that tweak..(editing of the file). I hope that restoring the original file would help.
Do you know about adb...?
Also i forgot where the actual bluetooth configurations file was in the root folder structure
adb will not work on device in recovery/download mode
to use adb mobile needs to be running
you can flash cwm in your mobile then upload the file and send me the link i will make a flashable zip and upload it then you can flash it
adb is running...just
Adb is running (while the phone keeps on showing boot animation-samsung logo-bootanimation-samsung logo-bootanima....) but it seems that it has permissions issues..i unrooted my phone before using adb .
i can access adb shell and list root directories but cannot enter further directories such as data\ permission denied
I donot have the file that i changed and quiet cannot remember it..
Check on your mobile and see for
data/misc/bluetoothd/
if it has files such as music.conf,main.conf etc etc..then this is the needed folder..
can you create a update.zip
like i used for rooting/ unrooting .that doesnt need CWM
that empties the directory ,because it has some backup files .bak created by root explorer
loads files from your mobile
i am currently unrooted ..do i need root?
actually adb works during splashscreen
get the original file and push it through the system, set permission and it should work
if all else fails,..... odin
download update.zip from http://dl.xda-developers.com/attach...5498d4d803e6a/4fcc0dd2/7/6/3/0/8/8/update.zip and place it in the root of your sdcard
go to recovery flash it you will get root then you can use adb
if it is not flashing first flash cwm through Odin then flash this update.zip through cwm
The file you sent is invalid. corrupt..?
what does this do..exactly.
i already have a update.zip and update-unroot.zip to root unroot my device
so
do i need root permission to use adb..because commands like
adb root gives"error not available in production devices"
&
adb shell
$ su
etc are showing permission denied.
if you have the original files on your galaxy y.. can you make update.zip with the above instruction
if adb works..i dont exactly remember the file path that i changed..so using the hints above please can you send me the file path
My aim here is to use odin or factory reset only at the last.
just root the device by flashing the root.zip in recovery and then use
adb shell
su
and it will work
No still get permission denied.... like always.
cd data
ls
open directory failed, Permission denied.
1. flash cwm recovery through odin
2. then upload the original file
3. I will create a update.zip and will upload it
4. you will need to flash it in cwm recovery
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
y2k2r2d2 said:
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
Click to expand...
Click to collapse
http://db.tt/2NStXBF8
flash it in recovery but it may not work as I don't have galaxy y I have a different mobile
it didnt allow installation both through cwm and recovery mode
& now
i messed up with CWM
backup-restore feature
create backup
edited the system.tar
put the original file
calculated md5 for new system,tar
edited the nandroid.md5 with appropriate editor and filled with the new calculated md5 of system.tar
advance restoore....select system files...
md5 check pass
restore fail
now boot stuck at initial screen
pretty sure even wipe data wont work
So i Had to resort to ODIN..Thanks for your time mate...
humm
I also think Odin is the last choice
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz
Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
{
"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"
}
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9505 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing/downgrading firmwares, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on the latest version, latest modem and latest stock kernel, recommended is XXUBMH1(right to 05/09/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
When installing modem via odin, make sure you select PHONE and not PDA
You will find at least one method that works on your device, so don't give up after one method.
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
I9505 EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
What is EFS, Why it is necessary to backup
Click to expand...
Click to collapse
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img bs=4096
Then click enter.
When it finishes, check if you have efs.img on your phone memory. If so, copy it to comupter, if not, you did something wrong try again.
Click to expand...
Click to collapse
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Download this and copy it to your device:
http://d-h.st/SaK
Reboot into recovery
Flash the zip
Reboot your device.
Connect your device to your pc, and copy the backup in "efs_backup" folder.
Click to expand...
Click to collapse
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
With root explorer, go to your efs folder and delete all files inside
Long press on power button will turn off your device.
Then turn on the device, you will be in "Permanent Safe Mode".
Continue to one of the following methods.
Click to expand...
Click to collapse
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
I9505 EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
What is EFS, Why it is necessary to backup
Click to expand...
Click to collapse
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p10 bs=4096
Then click enter.
Now, reboot your device. If you still don't have IMEI/You are still in Safe Mod, reboot again.
In the second reboot, the bootanimation might stuck and the device will reboot automatically again. Don't worry, it is ok because it installs your efs.img.
Click to expand...
Click to collapse
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Download this script & copy it to your device:
http://d-h.st/zwR
Reboot into recovery
Go to mount section and click on(Very important!):
Mount /efs
Click to expand...
Click to collapse
Now install the script you have downloaded.
After it finishes, reboot.
Now everything should be fixed, of course if your backup is 100% ok.
If it doesn't work, try method 4.
Click to expand...
Click to collapse
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Using root explorer, go to "efsbackup folder, select all files & folders there, and click Copy.
Still in root explorer, go to "efs" folder of your device(It is located where all main folders like data, system, etc.).
In "efs" folder, click paste. It will ask you if you want to replace your files, select replace to all files(So all your files from "efsbackup" folder will be in "efs" folder)
Now open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Now write:
Code:
busybox chown 1001:1001 /efs/nv_data.bin
Then click enter.
Now write:
Code:
busybox chmod 06755 /efs/nv_data.bin
Then click enter.
Reboot device. Now everything should work.
Click to expand...
Click to collapse
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
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:
Change this:
Code:
OFF
To:
Code:
ON
Reboot device.
Click to expand...
Click to collapse
Method 2
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
Click to expand...
Click to collapse
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button & Rate this thread 5 Stars.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode - I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05
Amm i guess no one need it?
they do need it and i for one would like to thank you for the guide and time and effort in sharing ..mods and fixes are always welcome on xda thanks man:thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app
port76 said:
they do need it and i for one would like to thank you for the guide and time and effort in sharing ..mods and fixes are always welcome on xda thanks man:thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks first real comment in the thread
Sent from my GT-N7100 boosted by PhoeniX ROM
:thumbup:its ok any time my friend ....iv told my friends about the fix and I'm sure they will pop into this very useful and informative thread .. Thanks again iv added it to my subscribed topics and I'm sure people will be popping in to view and post on the thread thanks :thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app
Nice guide, the command line is the best! :good:
Will heimdall work as an alternative to restore the efs.img? Like this: heimdall flash --efs efs.img ?
It is used from download mode, like odin, so would work even if you cannot boot.
This Method, in Moto x?
tamirda said:
Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9505 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing/downgrading firmwares, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on the latest version, latest modem and latest stock kernel, recommended is XXUBMH1(right to 05/09/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
When installing modem via odin, make sure you select PHONE and not PDA
You will find at least one method that works on your device, so don't give up after one method.
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Method 2
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button & Rate this thread 5 Stars.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode - I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05
Click to expand...
Click to collapse
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Pika71 said:
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Click to expand...
Click to collapse
?????
slugthru said:
Will heimdall work as an alternative to restore the efs.img? Like this: heimdall flash --efs efs.img ?
It is used from download mode, like odin, so would work even if you cannot boot.
Click to expand...
Click to collapse
You can try and share your experiences.
From my personal experience with another device the dd method in terminal works just fine
Sorry but null IMEI isn't fake IMEI
Difference:
Null IMEI means you don't even have any data for the IMEI oh and it's bad!
fake IMEI means you do have a data which is corrupt. Nothing more only digits has been changed.
There's a different between those
I remember having null IMEI and my backup didn't help at all service center was forced to swap motherboard to get IMEI working.
---------- Post added at 02:26 PM ---------- Previous post was at 02:26 PM ----------
Pika71 said:
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Click to expand...
Click to collapse
It depends if it uses same permission. Also there is a way to fix a corrupt IMEI while in recovery
Also don't quote whole op
My brothers phone is in safe mode could i backup my efs folder and restore onto his device?
ok, i am stuck in factory mode but none of the methods described work because there is nothing in my efs folder - it is empty so there are no files to actually edit.
Hello,
I was trying to edit my note 3 settings.db file to add the MobileData toggle at the notification panel.
After I edited the file, I rebooted the phone and Now I am stucked at the Tmobile 4G lte screen.
I have saved the original settings.db file so I can replace the modified one but the problem is that now that the phone doesn't turn on I can't replace it.
Is there anyway to fix this without installing everything from zero again???
Thank You
P.s
I tried to boot in safe mode but the phone doesn't boot even like this.
I tried to wipe cache, but nothing changed
As for the recovery mode, I can boot there
Boot to recovery and use adb console from your pc to swap the files. Learn some Linux command line commands if you don't know how. Primarily you will use cp target.file destination . file. Make a backup if you want via mv.
Sent from my SM-N900T using Tapatalk
howetechnical said:
Boot to recovery and use adb console from your pc to swap the files. Learn some Linux command line commands if you don't know how. Primarily you will use cp target.file destination . file. Make a backup if you want via mv.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Any help will be very appreciated as I never worked with Linux.
My original files are located at Downloads folder of my device.
and the files that I changed are located at /data/data/com.android.providers.settings/databases/
What command should I use to copy settings.db from downloads to the databases location
Thnx again for your reply
Cheers
I am trying something like this:
adb push /sdcard/downloads/settings.db sdcard/data/data/com.android.providers.settings/databases/
But I am getting error:closed
Maybe I am entering the paths on the wrong way
howetechnical said:
Boot to recovery and use adb console from your pc to swap the files. Learn some Linux command line commands if you don't know how. Primarily you will use cp target.file destination . file. Make a backup if you want via mv.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Another question, as I am not managing to over pass this error close message from adb.
If I install 4.4.2 again from download mode will I lose my settings, applications and everything else that I have installed before???
Odin doesn't wipe anything, but the re install would overwrite much of your personalizations. Boot into recovery, do a nandroid backup, then boot into download and Odin and restore. When you're up again, download nandroid manager from play store and select what you want to restore from your nandroid backup you made. Be sure to save it in a persistent partition, external SD if possible.
Sent from my SM-N900T using Tapatalk
howetechnical said:
Odin doesn't wipe anything, but the re install would overwrite much of your personalizations. Boot into recovery, do a nandroid backup, then boot into download and Odin and restore. When you're up again, download nandroid manager from play store and select what you want to restore from your nandroid backup you made. Be sure to save it in a persistent partition, external SD if possible.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Before I try this, another idea that came to my mind.
Is there any program that I can install to my computer and allows me to browse my phone files even when it is in recovery mode???
Adb, like I suggested first. Look on YouTube if you're not sure how to use it.
Sent from my SM-N900T using Tapatalk
howetechnical said:
Adb, like I suggested first. Look on YouTube if you're not sure how to use it.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
THNX for your help.
I was forced to do a factory reset through recovery mode and right now phone is up and running.
Just did a restore from kies but it was an old backup that didnt have everything, so trying to install the other tolls that I need.
Thnx again for you help
Cheers