If u get a md5 mismatch error During a restore thing type via command promt ( ADB iinstalled)
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53(THE name of your backup stored in /clockworkmod/backup )
# rm nandroid.md5
# md5sum *img > nandroid.md5
awesome idea
raunakrajvanshi 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
Ok, so maybe a stupid question, but on the second line, do you change the command to your backup name?
terthii said:
Ok, so maybe a stupid question, but on the second line, do you change the command to your backup name?
Click to expand...
Click to collapse
Not a stupid question But the answer is yes (or at least it should be)
Ah, OK. Thanks!
EDIT: Ok, yet another possibly stupid question! Can I run this through a terminal on the phone, or do I need to do this through a command prompt on the computer?
EDIT 2: Er, I just looked at my recovery that I have the md5 error for. There's nothing in the backup folder! It's empty! Like, crap! Back when I made the backup, the recovery said it backed up successfully. I even recovered using that backup once before. Is this normal? Or is there something jacked up here?
great job ..well done
Command promt
terthii said:
Ah, OK. Thanks!
EDIT: Ok, yet another possibly stupid question! Can I run this through a terminal on the phone, or do I need to do this through a command prompt on the computer?
EDIT 2: Er, I just looked at my recovery that I have the md5 error for. There's nothing in the backup folder! It's empty! Like, crap! Back when I made the backup, the recovery said it backed up successfully. I even recovered using that backup once before. Is this normal? Or is there something jacked up here?
Click to expand...
Click to collapse
Command promt oviusly u need to have adb installed Did you delete it
Related
I've got 3 CWM backups on the internal memory of my Samsung SG2.
I tried to restore one and it failed on md5 mismatch/error (or something to that effect...) - tried the others - all returned the same error, yet when I'd actually backed them up, they all completed successfully.
The one thing I did to them all, was give them a more recognisable name, rather than just the date & time so I knew which ROM they were...so out of interest, I backed up my existing (new) Cognito ROM while still in CWM, then when it had finished the back up, immediately tried to restore the newly backed up ROM....and it worked! Is it failing on the others because I've renamed the CWM backup folder?? I'm sure I've done this in the past on my old HTC Desire, and had no problems
Also, is there a way to rescue the backups I've done by generating a new md5 checksum for the renamed backups...or are they toast now??
Thanks for any help...
Willie_Heckerslyke said:
Also, is there a way to rescue the backups I've done by generating a new md5 checksum for the renamed backups...or are they toast now??
Thanks for any help...
Click to expand...
Click to collapse
Google and you will find:
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53 (Which is your clockwork mod backup folder)
# rm nandroid.md5
# md5sum *img > nandroid.md5
Do this from a terminal emulator or from adb...
Thanks karendar...but I'm afraid I'm a bit crap at adb and that kinda stuff
I've downloaded an emulator off the market and when I fire it up, I got a $ prompt; found out how to get # prompt but when I put all that in, it gives the following error:-
"md5sum: can't open '*Img': No such file or directory"
When I looked inside the backup folder, there are a series of img files so is the wildcard * is to be put for each file in the back up folder? (I tried one of them - the boot.img file in there, this time there was no error brought up....but I also never got any 'success' confirmation or anything
Help
(BTW....whenever I type the letter 'i' - it changes into a capital 'I' all the time... What's that all about??)
**Bump** anyone??
Rename your backups and make sure there are no spaces in the names. Or keep them to a maximum of one space.
That way there will be no problem with md5 mismatch.
Considering your issue with md5sum: turn off autocorrection in your keyboard settings, and then make sure the command you are typing is
Code:
md5sum *.img
Note that as Android is Linux, capitalisation matters, and *Img will return no results at all.
Thanks dude, i had the same problem on my P500, and your tip helped a lot!
Especially since my phone was stuck in a bootloop and my recoverys wouldnt work... You learn something every day!
Gasai Yuno said:
Rename your backups and make sure there are no spaces in the names. Or keep them to a maximum of one space.
That way there will be no problem with md5 mismatch.
Considering your issue with md5sum: turn off autocorrection in your keyboard settings, and then make sure the command you are typing is
Code:
md5sum *.img
Note that as Android is Linux, capitalisation matters, and *Img will return no results at all.
Click to expand...
Click to collapse
..
Hello,
I am having a major problem... earlier today i made a backup of my ics'd out v8 rom in order to try the new CM7 Kang. I got the kang running but needed to install gapps. For some reason rom manager was not letting me install it from there because it wasn't an updated version of rom manager and i couldn't get an updated version. So i figured I would go back to my ics'd rom, download gapps on the sdcard, and then go back to cm7 to install... NOPE.
Every time I try to restore my backup I get md5 mismatch error. I went through a bunch of different threads for different phones and tried all the adb stuff it said and nothing worked. For some reason when I ran the command (given here http://forum.xda-developers.com/showthread.php?t=714114) "cd /sdcard..." the pound # changed to a > and everything I typed would just be repeated back at me. The phone never even asked for superuser permission. I am pretty sure that I have the adb stuff right since when I type in "adb devices" in command I see the device, but I just have no clue how to fix this. Maybe the instructions given on this page only applies to that particular phone?
I would really like to be able to recover this backup and if anyone has instructions on how to fix this error on this phone it would be very much appreciated.
Thanks!
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Artimus009 said:
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Code:
adb push
is your friend - great way to put a file on the phone when it's in recovery
Entropy512 said:
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Click to expand...
Click to collapse
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
getbuzzin said:
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
Click to expand...
Click to collapse
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference? I mean I have done this before without issue.
Shadow12347 said:
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference?
Click to expand...
Click to collapse
Change it back and see if it works
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Well I deleted the beginning and it looked like it was going to work because it was checking md5 sums for a while and then it said md5 mismatch. But it wasn't instant like the other times.
I think I read on one of the pages that you could take the nandroid.md5 from another backup and replace it with the one in the nonworking backup, is this true and would it work?
Ok nevermind, I forgot to do the ADB thing again xD it worked... THANK YOU SO MUCH!
karth500 said:
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
Most likely.
I usually rename my backups manually to something like romname_date in ADB
e.g.
villainrom_1224
I NEVER put spaces or other characters in the rom name
Right now I think I have:
modstock_1128
villainrom_1224
uckk6_1224
one other ROM...
Ok guys I'm sorry, it happened again... except this time I think it may be a problem with ADB. When I am in adb shell, it shows up as "~ #" instead of just "#", however, typing "su" changed it to just "#". However, in both instances ("~ #" and "#") it gets an error:
~ # cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
/sbin/sh: cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
and
# cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
This is the original name, there are no spaces, I checked the driver for the phone, etc.
Anyone got any ideas?
Oops double post -_-
Try tab-completion (type part of a directory name and hit tab - sometimes it works and sometimes it doesn't, usually should work when ADBing into CWM), and use "cd" and "ls" to navigate through directories instead of just pasting the whole path.
ls = same thing as dir in DOS
Alright so I did that and found out the sdcard isn't mounting...
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
# ls
ls
acct fota.rc recovery.rc
app-cache init res
cache init.goldfish.rc sbin
config init.rc sdcard
customkernel init.smdkc210.rc sys
d init.smdkv310.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.rc
default.prop lpm.rc ueventd.smdkc210.rc
dev misc ueventd.smdkv310.rc
efs mnt vendor
etc proc
# cd /mnt
cd /mnt
# ls
ls
asec obb sdcard secure usb
# cd /sdcard
cd /sdcard
# ls
ls
#
I also went into root explorer and it said "SD card is not currently mounted"
...uhhh I feel like a noob to ask this but, how do you mount it? xD
The thing is, though, that it dismounts when I plug it into the computer to transfer files/adb, but it is mounted afterwards...
hi
im very new in the forum thats my first post
i tried to install an app that required a rebbot in my gt-i9300, i rebooted and i got an pop-up window said that factory mode has crashed.
i searched for days in the internet and i found this thread: http://forum.xda-developers.com/showthread.php?t=1762204&page=53
i did all but my galaxy says that its unable to chmod /efs/FactoryApp/factorymode: no such file or directory
then i realised that i have no efs directory and that i can download one from here http://forum.xda-developers.com/showthread.php?t=888193
so' my question is,
if i will flash it with odin, will the error will dissapear?
and if the answer is yes,
i understand that some people flash it because they have no imei and the phone dont recognize their sim card.
and my fear it can happen to me if ill flash it
some help please?
What app did you try installing?
slaphead20 said:
What app did you try installing?
Click to expand...
Click to collapse
the swapsd app.
but theres no matter what app i installed
i just want to know if i can install the efs directory without problems
so please help me everyone!
You have a backed up EFS on your phone ???
jje
JJEgan said:
You have a backed up EFS on your phone ???
jje
Click to expand...
Click to collapse
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
arimal199 said:
yes i have a backup named efs.tar in my root directory
can i restore the folder from it?
Click to expand...
Click to collapse
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
familyguy59 said:
Well, obviously you can. That's what an efs backup is for
Copy the tar file to your PC and download the Android SDK.
Once the Android SDK is installed, open up a command prompt.
Once you're in the command prompt, CD to the directory where the ADB executables and libraries are.
Usually it's here:
Code:
cd C:\android-sdk\platform-tools\
Once you're in the directory where the files are, unpack the TAR file and type the following code:
Code:
adb start-server
adb push <path-to-your-unpacked-TARfile> /efs/
adb kill-server
If you need further assistance, feel free to PM or email me
Hope I could help!
Lg
Click to expand...
Click to collapse
wow
thanks man ill try it
arimal199 said:
wow
thanks man ill try it
Click to expand...
Click to collapse
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
arimal199 said:
oh i forgot
my pc doesnt recognize my galaxy
maybe i can go to someone that already has a adb and see if he can fix it
but really thanks
Click to expand...
Click to collapse
Check out the links in my description. (Win8 help - ADB etc. etc. ...) that works with Windows Vista, 7 and 8. If you need the ADB binaries, in that same thread, you can donate a bit of money to me and I'll license you a program (Always with updated binaries) that installs ADB and fastboot to your system's root. With the click of a button
Lg
Edit: You can also download my universal Android tool kit and with the next update, all the Samsung Galaxy S III variants will be supported and you can easily backup/restore your /efs partition from there (With the Pro version, that is)
spocky12 said:
I believe you'll also need to change files owners and access rights for it to work.
Edit : if you don't have any efs folder, I think your efs partition might not be mounted. Type "mount" in a terminal emulator and check if a line refers to /efs (that should be block 3)
Click to expand...
Click to collapse
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
arimal199 said:
i looked in mounts and storage in cwm and saw that efs is not mounted.
can i mount it and it will work?
Click to expand...
Click to collapse
no i understood' i wasnt at factory mode at all!
all the time i had imei and call function , the only problem was that factory test has stopped.
so, i downloaded titanum backup pro and turned factory test app off.
now my galaxy went back to normal all works as well!
thanks for trying to help guys!
Hello Everybody,
I'm new to this forum and I hope posted this in the right section.
I have a Coolpad F1 TD-SCDMA. Today I flashed a custom ROM but I want my original ROM back.
So I wanted to restore the backup I earlier made today. When I am in CWM and choose restore it gives me: MD5 Mismatch!
I went to check for it in the directory but i didn't see any .md5 file.
Here is a guide for a similair problem, but since I am new to this and as he said in the topic: he ported it for One V. I am not sure if it will work.
I hope someone can help me with this.
Thanks in advantage!
HarlemOrange said:
Hello Everybody,
I'm new to this forum and I hope posted this in the right section.
I have a Coolpad F1 TD-SCDMA. Today I flashed a custom ROM but I want my original ROM back.
So I wanted to restore the backup I earlier made today. When I am in CWM and choose restore it gives me: MD5 Mismatch!
I went to check for it in the directory but i didn't see any .md5 file.
Here is a guide for a similair problem, but since I am new to this and as he said in the topic: he ported it for One V. I am not sure if it will work.
I hope someone can help me with this.
Thanks in advantage!
Click to expand...
Click to collapse
Yea, that SHOULD work.
Just tried it when typing in: 'adb shell' in cmd I get: 'error: device not found'.
Drivers are installed I think, I can see the files on my phone of my SD and emulated SD card.
Any suggestions?
Edit: It WILL find my device when turing on Mass Storage (MTP) instead of charging only.
I tried this using MTP.
Code:
# cd /sdcard/clockworkmod/backup/2014-10-08.08.47.17/
# rm nandroid.md5
# md5sum *img > nandroid.md5
Then I went back to CWM to restore the backup but still the MD5 mismatch.
Edit:
I wonder how this MD5 mismatch error even started.
HarlemOrange said:
I tried this using MTP.
Code:
# cd /sdcard/clockworkmod/backup/2014-10-08.08.47.17/
# rm nandroid.md5
# md5sum *img > nandroid.md5
Then I went back to CWM to restore the backup but still the MD5 mismatch.
Edit:
I wonder how this MD5 mismatch error even started.
Click to expand...
Click to collapse
Did you start with adb shell while connected in MTP? Did you look with a file manager to see if it is creating the md5 file? Did you try Method 3 with busybox? As far as what causes it, it's explained in the first post of that thread.
es0tericcha0s said:
Did you start with adb shell while connected in MTP? Did you look with a file manager to see if it is creating the md5 file? Did you try Method 3 with busybox? As far as what causes it, it's explained in the first post of that thread.
Click to expand...
Click to collapse
Thanks for the response. First I started try with charge only. When that didn't work I start with adb shell whil connected in MTP.
Yes, but unfortunatly it isn't. No, did not try method 3 yet.
But I did try this. It is the same method but without adb. But as you can see in the other topic:
HarlemOrange said:
When I try the following command:
Code:
#cd /sdcard/clockworkmod/backup/2014-10-08.08.47.17
I get this:
Code:
No such file or directory
Did it like 3/4 times now and I'm pretty sure I did not make mistakes when typing.
Click to expand...
Click to collapse
Looks like this (third paragraph) is the problem: Not enough space to finish the backup. I will install the sotck rom shortly and try to restore the data.
I'm trying to make an AOSP ROM, and while doing so, I now have a dysfunctional bootloader. If your tablet is rooted, please duplicate the boot.img from your system and share it with me. Would very much appreciate.
Instructions:
Use CMD and paste these 2 lines:
adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img"
adb pull /sdcard/boot.img
Then from ADB directory, upload to somewhere easily accessible.
Does it matter if we have updated to 7.0 or not? I'm rooted and have updated to 7.0 and would be happy to help.
That would actually be a good idea. The ROM is supposed to be 7.0.0 anyways.
Running the first command comes up as " no such file or directory"
Do you already have ADB?
mr_verystock said:
Do you already have ADB?
Click to expand...
Click to collapse
Yep. I do adb devices to make sure it recognizes the tablet and all is good there.
Maybe so I'm the same page i just open up ADB as normal : open the command prompt in my platform tools. I paste the first line in : adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img" I get no file or directory.
Unable to get the dumb file:
adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img"
dd: /dev/block/platform/soc.0/by-name/boot: No such file or directory
Edit: does a backup from the recovery could make the task done ? I backup the boot from the TWRP and I get a file of 32Mb with the name: boot.emmc.win
adb shell
cd /dev/block/platform
ls
And tell me the output. I appreciate your help!
mr_verystock said:
adb shell
cd /dev/block/platform
ls
And tell me the output. I appreciate your help!
Click to expand...
Click to collapse
Nothing, it returns an empty result
Unusual... Normally there's soc.0 or msm_sdcc.1.
mr_verystock said:
Unusual... Normally there's soc.0 or msm_sdcc.1.
Click to expand...
Click to collapse
That command never worked for me on this tablet. Yes the default kernels is 32mb.
You can get it from twrp backup as .win and then rename it (if it is not compressed) or use AUT or SuperR's kitchen to obtain it.
Another method would be flashifire>backup.
Im still on MM so I can not help you.
Try these: https://drive.google.com/file/d/0Bz54O_w1LEYpQ1k0aDVHX29NbkE/view?usp=sharing
the rooted files I grabbed from TWRP backup, should be idential to the ones get using dd method.
the stock files I extracted from stock kdz file using WindowsLGFirmwareExtract-1.2.6.1-Release