Greetings,
I happened to restore a nandroid backup i created but encountered an "md5 mismatch" error. Here is a solution that my geeky cousins handed me.
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-04-17.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME)
su
# mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors.)
Reboot your phone and enter Recovery (Home+Power)
Restore.
Hope this helps,
UsmanJ
That was what I quoted much earlier in my newbie guide
Defy-ing all limits.
little clearance before i proceed :
1. for example i have a folder name : 2012-04-17.10.09.36
2. now i have to rename it something like XYZ so now 2012-04-17.10.09.36 will be XYZ
3. now i will do this :
su
# mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/XYZ
#rm nandroid .md5
#md5sum *img > nandroid.md5
4. thats all or did i do something wrong ?
---------- Post added at 10:00 AM ---------- Previous post was at 09:56 AM ----------
i got this thing as i typed this and press enter
su
# mount -o remount rw /sdcard
{
"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 check there is some problem
new error but files are there :
Your 3rd screenshot, your proceeding fine, except that there should NOT be a space between nandroid and .md5. This causes Terminal Emulator to recognize the command to be applied on two different files.
It is supposed to be "#rm nandroid.md5"
This type of problem occurs when U try to rename your nandroid data!
Sent from my GT-S5830 using xda premium
wow thnkx buddy yes i had remove space from it thank you.
It Works!! Thanks Mate!!
Same here...thanks!
Thanks
Thanks alot bro now i can give my phone to the customer care
I can confirm this procedure worked on my SGS2.
I had a backup that I decided to rename it to something more meaningful than 2012.09.12.... to jbrom a.k.a. jelly bean ROM and when I tried to restore from this backup Igot the MD5 error mismatch message.
This solution worked great on my JB SGS2...
I only had to use the backup on my SD card which was located on this path
/mnt/extSdCard/clockworkmod/backup/jbrom
I found out my backup did not have a nandroid.md5 file on the folder. Somehow it got deleted.
Thanks for this solution:good:
Thanks for this, this helped me restore my backup.
How to know if backup works?
So I have a question.
How do you actually know if a backup does actually works?
Because I sometimes read that when a back-up is bad itself it could brick your phone.
Or a file is missing and you still get nowhere.
And since there is a md5 mismatch error, I guess something went wrong.
It's my first back up ever and I can't seem to find a answer to this question.
I back it up with CWM (5.0.2). And have a Samsung s5830i.
When in the folder backup (sd/clockworkmod/backup) I see a folder with a date and time.
I assume that's where my back up is.
In this folder there are 4 files.
Cache.rfs 5.3kb
data.rfs 25.5kb
nandroid.md5 1kb
system.rfs 221.9kb
Are those files as big as it should be?
Some web sites says that it should be around 1 Gb.
And is there a file missing?
Thanks in advance.
Thanks.
ironwolf42km said:
So I have a question.
How do you actually know if a backup does actually works?
Because I sometimes read that when a back-up is bad itself it could brick your phone.
Or a file is missing and you still get nowhere.
And since there is a md5 mismatch error, I guess something went wrong.
It's my first back up ever and I can't seem to find a answer to this question.
I back it up with CWM (5.0.2). And have a Samsung s5830i.
When in the folder backup (sd/clockworkmod/backup) I see a folder with a date and time.
I assume that's where my back up is.
In this folder there are 4 files.
Cache.rfs 5.3kb
data.rfs 25.5kb
nandroid.md5 1kb
system.rfs 221.9kb
Are those files as big as it should be?
Some web sites says that it should be around 1 Gb.
And is there a file missing?
Thanks in advance.
Click to expand...
Click to collapse
I had the same problem, I followed every step and it worked like a charm
Thanks UsmanJ!!!
thx so much. i did follow and it work for me.
i have a question,
my problem is a bit different but not at all.
i did a nandroid back up of my hugoboss stock rom. when i tried to restore it, it says that there was an error to restore system because of rfs format.
then i discovered that the problem was because recovery format in ext4.
so i used cf-root app ( i can't remeber the real name) that reboots my ace is recovery and format system in rfs, but now when i tried to restore stock nandroid back up it says me the problem of md5 sum mistmatch.
now i can try this guide?? or my problem is another cause first it gave me the other error??
i will have some risks doing that?
thanks
EDIT:
i read ( i can't rember where) of another way to fix this problem. it says to open nandroid back up with an edit-test app and to modify some lines.
what metod is better for my problem??
UsmanJ said:
Greetings,
I happened to restore a nandroid backup i created but encountered an "md5 mismatch" error. Here is a solution that my geeky cousins handed me.
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-04-17.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME)
su
# mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors.)
Reboot your phone and enter Recovery (Home+Power)
Restore.
Hope this helps,
UsmanJ
Click to expand...
Click to collapse
i cant find md5 file help plz
md5 mismatch
hii...i have updated my galaxy s3 to android 4.2 and now i want to restore it back to 4.1 but when i tried to restore it says "md5 mismatch" help please.......
sid343 said:
hii...i have updated my galaxy s3 to android 4.2 and now i want to restore it back to 4.1 but when i tried to restore it says "md5 mismatch" help please.......
Click to expand...
Click to collapse
Wrong place to post this in. Post in s3 section
Sent from my GT-S5830 using xda app-developers app
thanks...its work:good::good::good::good::good:
Related
Alright, so here is my explanation. I'm pretty experienced with flashing ROMS and what not just made a boneheaded mistake. So I've been running CM7 for awhile on my Vibrant. When the latest OFFICIAL CM7(05-19-11) came out it left me with no storage for applications. So I thought to myself, I'll just partition some of my External SD so I can. Well not using my head it partitioned the Internal SD, and now I'm in a bit of a pickle. When I tried to flash back to JFD was caught in a bootloop and had to ODIN Eugene's No Brick Froyo with Repartition unchecked and then ODIN JFD again. Well I've got my phone up and running again but when I try to go into ClockworkMod Recovery it gives me the MBR Checksum Error and now I can't flash any other ROMS. I've tried Formatting the Internal SD, but not helping. Any answers would be greatly appreciated.
Sent from my SGH-T959 using XDA Premium App
Did you ever get a reply or a way to fix? I see throughout the forum that many have similar issues. Thanks!
bump would love to get an answer on this.
To fix this you need to erase the extra partitions you created on the internal sd card.
Use parted with adb to fix it, 100% fixable
parted rm 2
parted rm 3
Then odin to 2.1 with repartition checked
http://forum.xda-developers.com/showthread.php?t=534714
I will try it later this week, unfortunately can't right now. I hit the thanks button, and if I could hit it 100 more times I would! Hope this works...the guide is a little intimidating ;-)
I have tried for hours now to get this to work with no success. I have errors every step of the way, adb is not letting me do anything, and I have followed the directions to a T. Is there anyway of doing this?
Ultimately this will help a LOT of people, so if there is a way to fix this issue without adb, that is preferred. If not, then a detailed instruction from beginning to end would help (or video! . I am not a n00b when it comes to this, but I literally have tried everything through adb and cannot get to format my internal sd. I am thankful to be able to have stock on my phone for use. Thanks again!
Hi,
Sorry for the late reply..
adb is for pushing parted into phone sbin folder then chmod 755 then run parted from phone.
here is parted for you
http://www.multiupload.com/CA5NCRMBPC
adb push c:xxx/sbin
do it for all files in the parted.zip after you unzip it
su for become superuser
then
chmod 0755 /sbin/xxx for every file in parted.
cd /sbin then run parted
you will have this:
>(parted)
type print
>(parted)print ->enter
Now you will see 3 partitions
/system /data /swap
>(parted) rm 2
>(parted) rm 3
You cannot remove system
Then
>(parted)quit
exit
exit
run odin with repartition enabled! <-you need pit file
Enjoy and hit thanks button again lol
Regards
Edit: If this dont work you need cwm then format \system from cwm then re-run odin with repartitions enabled
Can't wait to try it (lol). Thanks I will update and let you know if this worked.
I am sad to say that nothing worked. I followed the instructions and did the rm steps, flashed stock via odin and it still had the error. formatted system through cwm, still the error. I am at a loss
Hi,
after you rm the partitions did you check "print" again?
Make sure they are removed
Dont get desperate i can help you more privately if you want just pm me you skype details, so we can fix this once and for all.
Regards
I didn't check it...sent pm.
This is what I am getting when I get into parted. Also to get into parted I have to type in
parted /dev/block/mmcblk0
If I just type in cd /sbin then parted it says the device is not found. So as you can see the picture shows only two partitions. Thoughts?
{
"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"
}
bump...I feel I am so close to fixing this! Anyone?
weekend bump...any help is greatly appreciated!
bump...there must be someone who can help!
you here?
I'm also trying to get rid of this MBR error.
Yes I am here! PM if need be, but as you can see there are a couple of us that need your help demetris!
Please post a screenshot here like mine attached to check something out.
Btw you dont cd /sbin you just cd sbin type ls you will see the folders then cd sbin.
Hi,
here comes Recovery for Play of Team FreeXperia.
Download here: (Beta1 - Update 20.06.2011 - 18:28h GMT+1)
http://www.multiupload.com/VC3JRZ74H0
Broken:
Cannot backup&restore boot partition (kernel related)
To test use this command:
fastboot boot recoveryPLAY.img
Button mapping: (thanks Logseman)
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search - OK
Please DO NOT FLASH! This recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore!
Please test and report functions. If there are errors please include EXACT outpot of errormessage.
Thanks to Blagus for his Xperia Play Kernel!
To gain root on every ROM (Stock ones too) just flash the attached RootXperia.zip via Recovery
Regards
Bin4ry & Team FreeXperia
I assume we need to install the custom kernel first?
No! You have NOT to install custom kernel to use this.
Just issue the command i wrote on your windows console. Then phone boots into recovery!
Regards
Logseman said:
I assume we need to install the custom kernel first?
Click to expand...
Click to collapse
The recovery image is structured exatcly as boot.img, with the difference in executable files - regular boot.img boots Android system from /system partition, while recovery boots into... well, recovery
So, since it's structured just as boot.img, you have to pack kernel inside as well. That's where, in this case mine, zImage comes in handy instead of unpacking SE's special boot.img structure, it was easier to take zImage from standard boot.img.
ive just tried it now, boots into CWM fine, im going to try a nandroid and report back
It looks weird in this DDMS capture, but in the phone it looks all right (black background, orange text). I've had no error messages of any kind.
Button mapping:
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search/Power - OK
{
"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 capture looks funny
But important is how it looks on device. I doubt that ddms cannot capture 32bit framebuffers
Regards
Bin4ry
Ok, i did a nandroid, rebooted, booted back into bootloader and fastboot erased /system/, pushed the recovery back and tried to restore /system/ but i get the error " Error formatting system " i also get the same error in the mounts & storage menu can i flash the nandroid image from fastboot?
*edit* no it wont let me flash it from fastboot, it tells me the image is too large lol probably because i moved some widgets and lwp's to /system/, no worries i'll flash the image in the development section.
Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue
mehmehmen said:
Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue
Click to expand...
Click to collapse
try and clear cache, see if you get the same error? if the action works it wont matter if cache gets formatted
I hope you can help me figure this out, because right now I am astonished at least.
I've been poking around with ClockworkMod, and getting a couple of errors. I know there is an error reporting utility inside CWM, "Report Error" in "advanced" so I made use of it. However, the log would save to "/sdcard/clockworkmod/recovery.log".
Since I'm using the custom kernel, I'm not able to use the sdcard as it seems to be improperly mounted. It shows as mounted in CWM, I unmounted it and remounted it again to no avail... though it can be mounted on the computer properly.
However, that's not the point. I thought I'd do a search on "recovery" with Root Explorer, wanting to find the Recovery.log somewhere else. And boy, did I find it. I found the two recovery logs I saved inside the folder /data/system/dropbox . I happen to have DB installed in my Android. But not only that, I found my kmsg logs, and boot logs, registered there as well.
Hereby I attach the two recovery logs. Does it make sense that these kinds of logs are saved in such a folder? Am I worrying unnecessarily?
this is one of the reaons why google take root access off us in the first place isnt it?
Thanks for the logs.Dunno why they was stored in DB folder
@AndroHero:
Yes just restore the img files from backup via fastboot flash.
Regards
Bin4ry
where excatly do i put the play recovery.img?
crispyduckling said:
where excatly do i put the play recovery.img?
Click to expand...
Click to collapse
just put it in the same folder as fastboot.exe
When backing up the progress bar doesn't work and it can take some minutes, so just be patient when doing a back-up.
Are their any specific options you like us to play with?
AndroHero said:
just put it in the same folder as fastboot.exe
Click to expand...
Click to collapse
cheers mate
okay so i formatted the cache and it comes back
Cach wipe complete.
E:Can't Mount /cache/recovery/log
E:Can't Open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant Open /cache/recovery/last_log
it wiped cache ok but is this error something i need to be worried about in away before attempt wipe and restore of system with my nandroid?
Do not bother trying to restore a nandroid backup: the /system partition won't get formatted and the operation will be cancelled.
The back-up made a cache.img, data.img, system.img and a .android_secure.img
I assume I can flash the system.img with fastboot like I used to do when rooting through fastboot? Could safe me the bloatware removal trouble after I get into a bootloop (yet again ).
Heya!
Some know my little kTool already, some love it, some hate it.
Well, let's try to get some more love for it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
>> Now with support for the Galaxy-Nexus and the Galaxy-S3! <<
So, what does this do?
Dump current kernel (and recovery on devices having a seperate one)
Flash kernel from /sdcard/zImage
Flash recovery from /sdcard/recovery.bin
Backup EFS
(as raw .IMG dump and as .TAR archive)
Check/Verify EFS backup (i.e. compare to "live" EFS)
Restore EFS from either .IMG or .TAR
Open stock update .TARs and flash from from it:
- Modem Firmware
- PARAM.LFS
- Kernel
Reboot device
- normally
- to recovery
- to download mode
*) When you check the EFS backup right after you made it, it should show a 100% match to the current phone's EFS.
However, after a reboot, the EFS *does* start to differ a bit - that seems to be normal, during my tests the EFS differed for 80bytes more after each reboot, my original EFS dump even differed by ~150k already
kTool companion tool market link [ Show ]
Hope you like it.
If anyone has more suggestions on what would need to be checked/verified during the check operation, do tell
After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason?
Sent from my GT-I9100 using XDA App
koolshubh said:
After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason?
Click to expand...
Click to collapse
For the .img and the .tar or only for one of them?
What does it say for "mount returned:"?
"nv_data.bin not found" means a bad/corrupted backup.
// EDIT
Just saw the screenshot.
Something went wrong making the raw .img dump (weird....).
But the .tar backup is OK (100% match to the phone's one).
Hmm.... gotta investigate the .img issue some more.
Check this;
Sent from my GT-I9100 using XDA App
OK, that helps a lot already.
The efs.img dump might be all fine and OK, it's actually a problem getting it mounted to "look into it".
Dug around some more and also found this:
Code:
2: system error (out of memory, cannot fork, no more loop devices)
"2" was the returncode you got during the check, fits with the verbose error message you get when trying the mount from a shell.
Cool, at least I know where to look, not exately sure why this happens, but we'll find out.
Maybe a busybox thing, maybe I'll bundle one with the app....
thanks for updating~~~
I have used the old one from here
f.lui.li/get_99_f13d.html
Updated to v1.21
Everything is working from my end. Thanks for the tool!
Sent from my GT-I9100 using XDA App
HellcatDroid said:
Updated to v1.21
Click to expand...
Click to collapse
it just works!
thx!
Thanks and cheers.
Thanks, HellCat. Great little kTool you've made --- love the kernel dump feature, so more love for your app! ; )
Tiny update to v1.22.
"Restore EFS" now lets you chose if you want to restore the raw .IMG dump or from the .tar archive.
Hi. thanks for your work. I kept getting the error shown in the attached pic when on xxki4 so I flashed back to official wxki4 but get the same error.. can u help?
rasinell said:
Hi. thanks for your work. I kept getting the error shown in the attached pic when on xxki4 so I flashed back to official wxki4 but get the same error.. can u help?
Click to expand...
Click to collapse
Are you rooted?
// EDIT
Hmm, and what version of the app are you using?
Tried making the EFS backup again?
I take it the phone does work fine (correct IMEI and all)?
Stock Samsung ROM or a custom ROM?
HellcatDroid said:
Are you rooted?
// EDIT
Hmm, and what version of the app are you using?
Tried making the EFS backup again?
I take it the phone does work fine (correct IMEI and all)?
Stock Samsung ROM or a custom ROM?
Click to expand...
Click to collapse
Hi. Thanks for the response. Yeah I'm rooted running official stock Rom and kernel. Everything seems fine with phone n imei ect. Tried twice on unofficial stock Rom n kernel and twice on this Rom but get the same every time :-\ I'm using v1.22
Sent from my GT-I9100 using xda premium
-scrap initial post-
// EDIT
HAHAA! I think I found something!
Thought some more about this, behaviour/differences of stock kernels and double checked a few things in my code.
I think (i.e. hope) I found the reason for this - and if my theory is correct I will be able to reproduce the app's misbehaviour you are getting and can then fix it.
I'll make a new build tonight.
HellcatDroid said:
What's the version of kTool you are using?
You tried doing the backup as well again, not only the check?
I'll flash a stock kernel and try to reproduce this later tonight.
Click to expand...
Click to collapse
I'm using v1.22. Yeah tried that. I was wondering if it was the kernel that was problem, not had chance to try with another yet. Thanks
Sent from my GT-I9100 using xda premium
HellcatDroid said:
What's the version of kTool you are using?
You tried doing the backup as well again, not only the check?
I'll flash a stock kernel and try to reproduce this later tonight.
// EDIT
HAHAA! I think I found something!
Thought some more about this, behaviour/differences of stock kernels and double checked a few things in my code.
I think (i.e. hope) I found the reason for this - and if my theory is correct I will be able to reproduce the app's misbehaviour you are getting and can then fix it.
I'll make a new build tonight.
Click to expand...
Click to collapse
Cool. Thank you
Sent from my GT-I9100 using xda premium
rasinell said:
I'm using v1.22. Yeah tried that. I was wondering if it was the kernel that was problem
Click to expand...
Click to collapse
Well, in a way.
IIRC the shell command "cp" (to copy files) is not available on stock Samsung kernels, and the app just calls "cp" instead of (like for most of the other shell commands used by the app) using "busybox cp" to call/use the busybox applet of the command.
As said, I'll try, check and hopefully fix this later tonight and if all goes well will have an update ready by tomorrow
Published v1.23 with the above issue fixed
The update should show up on the market soon.
left on old v1.22, right on new v1.23:
.
Noobie needs help here
Galaxy s2 sgh t989 rooted followed all steps.
I ran hc-ktool to backup efs.img and efs.tar.gz. When i ran the backup check i got this:
Checking current EFS backup....
/sdcard/efs.img found
______________
mount returned:255
(unable to mount image - image corrupted?)
/!\ nv_data.bin NOT FOUND in backup!!!
/sdcard/efs.tar.gz found
________________
/!\ nv_data.bin NOT FOUND in backup!!!
Does anyone know what the hell this is about? I have not flashed any ROM for fear of turning my s2 into a paper weight. I downloaded root browser from play store to try and look deeper. That is when i noticed my efs folder was empty. I have been scouring my files but feel like a blind man looking for a needle in a haystack.
Surely there must be something i can do! Also, i still have a good imei and broadband version...everything seems okay. I am reluctant to do anything for fear of bricking. I no longer have lockscreen or power off menu either.
Can i reset the phone to factory default and restore my efs? If so, do i have to unroot my phone? Or am i stuck like this forever and ever? Any help and i will give you my firstborn
Thanks
Sent from my SGH-T989 using xda app-developers app
Sent from my SGH-T989 using xda app-developers app
tapuout27 said:
Noobie needs help here
Galaxy s2 sgh t989 rooted followed all steps.
I ran hc-ktool to backup efs.img and efs.tar.gz. When i ran the backup check i got this:
Checking current EFS backup....
/sdcard/efs.img found
______________
mount returned:255
(unable to mount image - image corrupted?)
/!\ nv_data.bin NOT FOUND in backup!!!
/sdcard/efs.tar.gz found
________________
/!\ nv_data.bin NOT FOUND in backup!!!
Does anyone know what the hell this is about? I have not flashed any ROM for fear of turning my s2 into a paper weight. I downloaded root browser from play store to try and look deeper. That is when i noticed my efs folder was empty. I have been scouring my files but feel like a blind man looking for a needle in a haystack.
Surely there must be something i can do! Also, i still have a good imei and broadband version...everything seems okay. I am reluctant to do anything for fear of bricking. I no longer have lockscreen or power off menu either.
Can i reset the phone to factory default and restore my efs? If so, do i have to unroot my phone? Or am i stuck like this forever and ever? Any help and i will give you my firstborn
Thanks
Sent from my SGH-T989 using xda app-developers app
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
If you can get IMEI number (settings -> about device -> status), then your efs is OK.. The reason why you saw empty efs folder is that you need to run file explorer in root mode.
To backup your efs, download Terminal Emulator from Google play, open it and type the following entry:
Code:
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img
You will find efs.img file in your internal sdcard as efs backup
Heres what came back.
204800+0 records in
204800+0 records out
104857600 bytes transferred in 21.216 secs (4942383 bytes/sec)
I have root browser and looked in mu efs folder. It was empty. I then looked on sdcard and found a backup efs.img and efs.tar.gz but im guessing that they are both bad because when i check them with hc-ktool i get the exact same message...
Sent from my SGH-T989 using xda app-developers app
tapuout27 said:
Heres what came back.
204800+0 records in
204800+0 records out
104857600 bytes transferred in 21.216 secs (4942383 bytes/sec)
I have root browser and looked in mu efs folder. It was empty. I then looked on sdcard and found a backup efs.img and efs.tar.gz but im guessing that they are both bad because when i check them with hc-ktool i get the exact same message...
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
OK sir, try using the following as a test to see is it really efs.img corrupted or not:
Copy efs.img to your computer.
If you are using Linux OS:
- Open terminal and type:
Code:
su -
mkdir -p /mnt/disk
mount -o loop efs.img /mnt/disk
cd /mnt/disk
ls -l
If you are using Windows OS:
- Download LinuxReader from this site here.
- Open it -> Drives -> Mount Image -> Then choose efs.img and hit Mount. A new driver will appear that contains all files inside the dumped image called "Linux native Volume 1". Just double click it to get inside the dumped image.
{
"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 you got files inside efs image then hopefully your efs.img is not corrupted.
Hi!
Story goes like this. I have here clone Samsung S4 that I wanted to update the software trough CWM. Unfortunately phone died at some point and now is dead. But, I made backup of the flash with MTKDroidTools and with SP flash tool... and here comes the problems... I can not flash backup back to phone because yaffs2 files are not good page/spare ratio. Thanks to members rua1 and Alex1948 now it is more clear how to change spare ratio on yaffs2 files. Unfortunately I'm not very good with Linux, last night I boot Mint 16 from USB stick and was trying to repair my files but without success.
So, my question is: is someone willing to repair my files in Linux (who understand Linux terminal better)?
Here are some details from phone
View attachment 2574910
View attachment 2574911
{
"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"
}
I only have problem with flashing yaffs2 files and secro.img all other are OK. If I try to flash those files I get this error
In attachment is mtd, dumchar_info, MTKDroidTools log and Sp flash tool log so you can see my file structure.Log from MTKDroidTools is from version 2.5.2 because I was using this version when I was making backup from my original phone (you will see other phones data just scroll down to MT6575)
I'm uploading original yaffs files to google drive so later I will update this post with some links.
Thank you all in advance.
Best regards
P.S. INFO FROM MTKDroidTools IS TAKEN FROM SAME PHONE LIKE MINE (FRIENDS PHONE) YES, SAME ONE HARDWARE AND SOFTWARE IS 100% SAME.
Files on Google drive link
https://drive.google.com/file/d/0Bx8Xjd1q6dr3YnFISVJBZFZPSUU/edit?usp=sharing
Little update (memory type)
View attachment 2575196
from guide:
Аttention! Yaffs2 type blocks from this backup can't be Downloaded to phone, they aren't correct! Use backup on 9th step if phone have yaffs2 type blocks!
Click to expand...
Click to collapse
files from archive is wrong
from your log:
10/02/14 11:43:23 Free space: system- 113.7M; data- 54.3M; sdcard- 16.7M; D:\ 170861M
10/02/14 11:43:46 - ERROR - tar: write error: No space left on device
Click to expand...
Click to collapse
it was necessary to release the free memory on SD card before
Hi!
First, thank you for your reply.
Yes , I did figure it out that my files are not OK. I was trying to make them manually in "yafey" for windows (software to create and edit yaffs2 images) but this software have to much bugs so one time it create system.img with full lib folder second time only half of lib files are there and also there is no option for spare ratio change.
So, MTKDroidTools did make my system backup in a folder on my PC but I can not make yaffs2 file from it because there is no software for windows that works fine (I don't use Linux). On Linux it is easy to do (at least for someone who understand Terminal commands).
So, I can send you my backuped system folder if you are willing to make yassf2 file from it (in Linux). Data and Cashe files I have create in yafey and thay are ok.
In yafey if I make new yaffs2 file and insert lib,etc,app,framework... it will not create all files in folders... and after that when I try to flash that created system.yaffs2.img I have error from BROM s_ft_readlen_not_page_aligment (4017) again problem with spare ratio.
I still have here my friends phone so if you have any idea what to do and how to do please tell. I made backup from my friends phone but same thing data,cache,system,secro files are not created correctly. I don't know why is this is it because of the MTKDroiTools or is it because of the phone?
Aaaaaaaaaarghh!!!!!
You wouldn't beleive what I just discover I just try to put my friends phone in recovery so I give a try to make backup.
NORMALY my friends phone don't want to go in recovery (just light on screen), so I have call my friend to ask him does he do something with phones recovery and he said YES i flash some recovery from net trough CWM and after that he can not go in the recovery.
CAN YOU BELEIVE HOW UNLUCKY I AM????????
If someone have any idea???