just rooted my evo3d, everything went great and i even git CWM to install the first time correctly. heres where i think i went wrong-
i downloaded rom manager and i attempted to use it and it worked great. to me it seemed like it worked because i was able to choose my phone and even flashed the CWM over the original one i had. i made a backup of my stock rom and tried a rom from the dev forum, didnt like it and tried to switch back and got the MD5 mismatch error when i tried to restore my stock rom. now, i thought i would try to flash the original CWM which was blue over the CWM(orange) and then attempted to get the rom to restore. that was also a fail. what can i do? i read that installing busy box could effect this? any help would be appreciated.
sucks but it happens download the RUU from here and reroot if you need too
FIXING MD5 MISMATCH
adb shell
# cd /sdcard/clockworkmod/backup/name_of_backup
# rm nandroid.md5
# md5sum *img > nandroid.md5
gaaah i dont have ADB installed on my mac. is there not a simpler way? anyway to fix this?! i dont think i need to reroot honestly..
Nope sorry.
I may have found a way to fix the MD5 issue.
Well, it worked for mine.
I saved a backup of the stock ROM before I installed the needle kernel.
it was named 2011-08-01-23.53.47
The I saved another backup of the ROM with the needle kernel/
it was named 2011-08-02-19.06.28 w/ needlekernel
What happened was that on the sd card the backup folder was named 2011-08-02-19.06.28 w/ then inside that folder was another folder named needlekernel . And that folder contained the backup files.
It seems that putting the space in the name caused it to create another folder within the backup folder instead of just having the backup files in there. I kept getting the MD5 mismatch when I tried to restore that backup.
So I took the files out of the needlekernel folder and put them in the 2011-08-02-19.06.28 w/ folder. I then deleted the needlekernel folder. The last thing was to take the (space)w/ off of the end of the folder name so it was just as the program named it to begin with.. 2011-08-02-19.06.28
After doing that I was able to restore the backup through ROM Manager. So apparently it's best not to add anything to the backup name when saving it.
One other thing I'll mention. When I restored the backup with the needle kernel in it it put the stock kernel back in the ROM.
Hope this helps anyone with the MD5 issue.
Hello,
Searched alot how to restore my efs, after checking my imi is a generic one with 0049...but didn't find any clear ones
I found this file efs.autobackup.img which most probably was generated by a custom rom with paulobrien script in link: http://forum.xda-developers.com/showthread.php?t=1223857
the date of file creation is just the same date of my phone purchase which is correct because I flashed in the first day so it should be a good backup (I hope)
Thanks,
Ok soo I used dd mode in terminal, waited a while until I got the message that the files were wrote but when I look in the efs folder it was only one file and ended up with no service phone. Copied back all the files and the phone is fine but the imei is still the generic 0049... Is there any way to check if the img file is ok?
Thanks again,
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.
Hello, i have used ktool to restore my imei, but it ereased all my efs folder files, so now it is empty. I have made my imei backup using ktool app, so i have efs.img and efs.tar.gz files.
I have tried to flash stock rom with odin but not only one of them boots, they all get bootloop. My phone only works with cm9 but it has no imei and no network.
So i need these files from efs folder, could any one help with this? Or is it possible to restore them with my back up files?
cH5 said:
Hello, i have used ktool to restore my imei, but it ereased all my efs folder files, so now it is empty. I have made my imei backup using ktool app, so i have efs.img and efs.tar.gz files.
I have tried to flash stock rom with odin but not only one of them boots, they all get bootloop. My phone only works with cm9 but it has no imei and no network.
So i need these files from efs folder, could any one help with this? Or is it possible to restore them with my back up files?
Click to expand...
Click to collapse
A simple copy and paste worked for me using root explorer.
If you have efs back ups:
Delete entire efs file on the root of you phone and reboot. Upon reboot a new efs file will automatically be created.
Copy the efs file back up and place into the newly created efs file at the root of your phone. Reboot into recovery and wipe cache.
This method restored a corrupted efs file on my s3.
alaska_ryder said:
A simple copy and paste worked for me using root explorer.
If you have efs back ups:
Delete entire efs file on the root of you phone and reboot. Upon reboot a new efs file will automatically be created.
Copy the efs file back up and place into the newly created efs file at the root of your phone. Reboot into recovery and wipe cache.
This method restored a corrupted efs file on my s3.
Click to expand...
Click to collapse
I have only two back up files: efs.img and efs.tar.gz, but efs folder should contain much more files.
I delete efs folder in the root and restart phone, but anfter restart it only creates the efs folder which is empty.
cH5 said:
I have only two back up files: efs.img and efs.tar.gz, but efs folder should contain much more files.
I delete efs folder in the root and restart phone, but anfter restart it only creates the efs folder which is empty.
Click to expand...
Click to collapse
Ok so click on efs.tar.gz and there should be the efs file. Copy that and and place into efs file at the root of your phone. Click on 'yes' when it asks if you would like to overwrite the file
alaska_ryder said:
Ok so click on efs.tar.gz and there should be the efs file. Copy that and and place into efs file at the root of your phone. Click on 'yes' when it asks if you would like to overwrite the file
Click to expand...
Click to collapse
I have done this, but after reboot all these files are deleted and efs folder remains empty.
cH5 said:
I have done this, but after reboot all these files are deleted and efs folder remains empty.
Click to expand...
Click to collapse
Ktool must of made a back up an empty folder. Don't know what to tell you. Do you have any files in storage called efs_backup? I think some recoveries or kernels automatically back up the efs file when doing a nandroid. Find the earliest back up and copy and paste.
alaska_ryder said:
Ktool must of made a back up an empty folder. Don't know what to tell you. Do you have any files in storage called efs_backup? I think some recoveries or kernels automatically back up the efs file when doing a nandroid. Find the earliest back up and copy and paste.
Click to expand...
Click to collapse
The back up is made correctly, i open .tar file and there are all these files, but when i copy them into the efs folder in root and reboot phone, these copied files are just gone.
cH5 said:
The back up is made correctly, i open .tar file and there are all these files, but when i copy them into the efs folder in root and reboot phone, these copied files are just gone.
Click to expand...
Click to collapse
I read on some other efs problem threads that flashing some newer firmware (ending with mg4 or something like that) reformats the efs file and you have to flash different firmware in order to fix from back ups. Look into other threads, they might have the proper procedures to fixing efs.
alaska_ryder said:
I read on some other efs problem threads that flashing some newer firmware (ending with mg4 or something like that) reformats the efs file and you have to flash different firmware in order to fix from back ups. Look into other threads, they might have the proper procedures to fixing efs.
Click to expand...
Click to collapse
Trying to flash firmwares and roms with these endings, but the phone doesnt boot, just stucks on samsung logo and repeats animation. It might be because i was installed leaked 4.2.2 xxufme7 firmware so it cant downgrade to 4.1.2 firmware.
cH5 said:
Trying to flash firmwares and roms with these endings, but the phone doesnt boot, just stucks on samsung logo and repeats animation. It might be because i was installed leaked 4.2.2 xxufme7 firmware so it cant downgrade to 4.1.2 firmware.
Click to expand...
Click to collapse
Just a thought are you doing a factory reset between flashes also doing a factory reset with stock recovery will wipe your entire internal sd
Have a look at EFS Pro to restore a tar .
http://forum.xda-developers.com/showthread.php?t=1308546
neilster2020 said:
Just a thought are you doing a factory reset between flashes also doing a factory reset with stock recovery will wipe your entire internal sd
Click to expand...
Click to collapse
This might be my misstake.
By the way, this is solved already. I flashes stock 4.0.4 version and used ktool to restore .img and .tar files, after reboot network came back and all efs folder files were also back, then flashed atock MG6 So now i am on this stock firmware.
But i still cant install leaked version FMU7, it gives me fake IMEI and no network, any ideas?
hey guys,
I have made a nandroid backup of my nexus 7 (2012) and I need to get access to contents of the data partition without actually applying the nandroid backup to the device. I found this "unyaffs" tool, but it requires .img files if I understood it correctly. However, in my nandroid backup directory, I have a couple of files that end in ".win" or ".win000" etc (along with corresponding md5-files)...these must be image files of some sort I guess, but Windows describes them as "Adobe CMS Extensions" for some reason.
So...anyone knows how I can access this data? Any help appreciated!
cheers
brokaaa