Hey guys, just 2 quick questions about nandroid.
Is it possible to either bypass the MD5 checksum right at the start of every nandroid restore? OR, is it possible to generate your own one somehow?
The reason I ask is, I wanna try and replace the backed up files made by nandroid such as "boot.img", "system.img", "cache.img", "recovery.img" etc with the ones that I have extracted from a stock rom.
The stock rom I have can only be flashed through USB connected to PC, by using "SP Flash Tool". However, I have 2 problems using it. The first is that it doesn't work properly for me. I can only flash the "system.img" file but not the other .img files. It seems I need a USB-to-UART cable to flash ALL the .img files, which I don't have and I don't plan on wasting my money buying it either. Besides, I find flashing on a PC a lot more risky than from memory card.
The 2nd problem I have is that I often have problems getting my phone detected by "SP Flash Tool". I tried using Windows 7 and XP and it's hard to get a connection properly. It's most likely because the phone i'm using a chinese clone, called "STAR A1000". It's cheap and crap, so I'm not surprised that I can't establish a stable connection to my PC. I only got lucky like once or twice but haven't been able to flash from my PC ever since.
So anyway, the stock rom I have contains all the .img files. I wanna try and replace those files with the files generated by nandroid, but of course there's the problem with the MD5 checksum file that will check if the file matches or not. So I need a way to bypass the MD5 checksum completely or force nandroid to perform a restore regardless of the conditions. Either that, or I need a way to generate a MD5 checksum for the .img files from the stock rom, and use that for my nandroid backup.
My last question is, I also have custom roms that are made to be flashed on the memory card. Of course, they contain the "boot.img" file, and so I wanna try and replace that with my own working "boot.img" file. I want to know if this will work when I try to flash it in the recovery, or will it fail and brick my phone?
I backed up my rom with Clockworkmod v6.0.1.4 and when I went to restore it, it said md5 mismatch checksum. I checked in the advance restore options and it shows the default restore format is .DUP instead of .TAR so it saved it in the .dup format. Now, when I went to check up on the folder on my SDCARD it never showed an md5 file because it never created one. I read all of the " 20-second md5 fix " posts and I created an md5 file and made them blank off of a YouTube video and I also installed RapidCRC to attain md5 checksums from the img files in the backup folder to add to the new nandroid md5 file and out in the backup root folder and I even tried the SDCARD root, but to no avail, they all failed and I still get the md5 mismatch error. I have attached pictures that show my folders and files. I need some help on restoring please!
http://forum.xda-developers.com/showthread.php?t=2096556
Dude, you don't need another thread for this....
I made the silly mistake of not doing a complete backup of my EFS folder before flashing my cellphone with a custom ROM:crying:
and now my EFS folder is empty;if I delete it with ES File Manager (my phone is rooted) as soon as I reboot the phone, the EFS folder is created again,
but it is empty.I'm able to make and receive phone calls,send and receive sms,use wireless,bluetooth and gps,but if I dial *#06# my IMEI is blank.
With Galaxy Tool Box (the Rom installed it) --> Device Information I can see my correct IMEI (same number write in the battery slot).
I have a CWM backup and these files are in the backup folder: .android_secure.vfat.tar / boot.img / cache.rfs.tar / data.rfs.tar / nandroid.md5 / system.rfs.tar
Could one of these files help me restore my EFS folder (with all the files ofc)? Even the Product code is gone (KIES doesn't recognize the device)
I've got the the original stock firmware for my italian GT-S 5830i ,and I've tried to flash it with ODIN (PDA/MODEM/CSC) but that was pointless.
Thanks in advance for your time and consideration.
Have a nice day.
[email protected] said:
I made the silly mistake of not doing a complete backup of my EFS folder before flashing my cellphone with a custom ROM:crying:
and now my EFS folder is empty;if I delete it with ES File Manager (my phone is rooted) as soon as I reboot the phone, the EFS folder is created again,
but it is empty.I'm able to make and receive phone calls,send and receive sms,use wireless,bluetooth and gps,but if I dial *#06# my IMEI is blank.
With Galaxy Tool Box (the Rom installed it) --> Device Information I can see my correct IMEI (same number write in the battery slot).
I have a CWM backup and these files are in the backup folder: .android_secure.vfat.tar / boot.img / cache.rfs.tar / data.rfs.tar / nandroid.md5 / system.rfs.tar
Could one of these files help me restore my EFS folder (with all the files ofc)? Even the Product code is gone (KIES doesn't recognize the device)
I've got the the original stock firmware for my italian GT-S 5830i ,and I've tried to flash it with ODIN (PDA/MODEM/CSC) but that was pointless.
Thanks in advance for your time and consideration.
Have a nice day.
Click to expand...
Click to collapse
The EFS Partition doesn't contain any files, it only contains raw HEX Data so it is normal for it to be empty. I recommend you install a custom kernel then flash the stock ROM via Odin as this has worked for me in the past.
Problem solved!
**********************
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
**********************
Original question
Hello devs,
I have Siyah kernel which auto backup my EFS, i have backup named "efs_28Aug2013-1852.tar.gz"
I want to restore from this backup because I lost my IMEI when I flashed UltimaROM
I renamed it to "efsbackup.tar.gz" and put it in the root of the sdcard
then I started adb shell & run the code
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/ efsbackup.tar.gz -C /
I granted ADB shell root access
then i went to recovery and run the command (because I can't run umount /efs while device's running it gives resource busy message)
However when I run the first command "su" in gives me this message
Code:
/sbin/sh: su: not found
so I skipped to the next command
but I get the message
Code:
umount: can't umount /efs: Invalid argument
Please guys any help appreciated
Click to expand...
Click to collapse
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
.
I've backup my efs with adb but how do you have a file on tar format, i've got a file on .img, it's normal ?
There's about nine different ways to backup the efs, .img is fine but a little on the large side at 20mb. A .tar of the same is only 5mb.
rootSU said:
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for your reply, I did as you said but this only changed my IMEI from "Unknown" to the generic IMEI "004999..."
Is there something wrong in the method or my backup may be corrupt
Sent from my Nexus 7 using Tapatalk 2
Read the imei / efs thread in general.
Sent from my GT-I9300 using Tapatalk 4
Thank you again, I read the thread in the past but it looks like it has been updated recently.
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
Thank you RootSU for your help.
hey bro,
i am stuck
help me out
- my efs(folder) is blank
- i installed stock with pit file but no help!
- right now my cell is in bootloop!
- it goes to recovery, download mode.
i have efs.tar.gz file and a folder named efs in my ext sd
how do i copy that to int memory?
can't even create a cwm flashable zip file of the same?????
help me bro.....
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
boomboomer said:
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
Click to expand...
Click to collapse
Dear boomboomer,
i am sorry, but my phone is in "bootloop" how am i suppose to delete the "EFS" ? that s what i am asking!!!!!
i have both efs.tar.gz and extracted folder ready in my ext-sd......
i wonder if somebody can help me with creating a cwm.zip from the .tar file
thanks ....
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
i already did so
almousawi said:
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
Click to expand...
Click to collapse
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
hello
mikks said:
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
Click to expand...
Click to collapse
hello nobody is here to help......??????
mikks said:
hello nobody is here to help......??????
Click to expand...
Click to collapse
Correct this is not a paid for service .
Suggest you take it to a service centre .
know that i did that already....
JJEgan said:
Correct this is not a paid for service .
Suggest you take it to a service centre .
Click to expand...
Click to collapse
thanks for the reply, respect to your reply and interest no disrespect ...
i took that to the center but they failed and by the way they come to me in some cases... so they give me free service...
my phone is in boot loop, i have efs.tar.... can i use phills recovery ????? or can i use someone elses backup... just to boot up my device ...then i'll be good .... i just need to get my device booted up.....
Can I restore data that I have backed up in CWM form my device to another?
As long as the model is same, yes. What device exactly?
I don't think so, even if they're the same. i've done it once and the cwm log says 'md5sum mismatch!'
azzazelium said:
I don't think so, even if they're the same. i've done it once and the cwm log says 'md5sum mismatch!'
Click to expand...
Click to collapse
If you insist on restoring the backup file do this simple trick on md5 mismatch: open the md5 file in your CWM backup folder, erase its contents. Leave the file empty (0 byte) then restore in peace
Keep in mind md5 mismatch means something changed in the backup file, doesn't matter which device it previously on. Do this on your own risk.
Note: CWM will skip verifying the backup if md5 file is empty.