NANDROID restore stock md5 Mismatch - Nexus S Q&A, Help & Troubleshooting

Hi guys!
I suppose the thread was close so I hope it isn't wrong posting here.
after carefully reading the 12 pages of http://forum.xda-developers.com/showthread.php?t=884093&page=12
I'm still getting the "mismatch md5" error, it's really frustrating...
These are my procedures:
(right now I'm using MIUI 1.4.29 + EN Pack1_2.3) and CWM 3.0.1.4, and of course the SNS is unlocked.
-Download the stock rom "twice" from the two links from mediafile posted in the first thread. just to be sure they are the same files. First open the zip file with 7zip and run the "test" no error. Second test, compare md5 hashes from the 2 zip files downloaded --> matched. Third, extracted them (PC) and open the nandroid.md5 files with notepad++ and verify every files hashes -> matched
-Booted to recovery --> CWM 3.0.1.4 --> mounted usb storage
-extracted directly from the zip file to maintain the "clockwork\backup\2010-12-22.21.06.07" directory structure.
-unmount. restore --> mismatch md5
-open the zip file manually drag the clockwork to sdcard (extract and copy) --> unmount --> restore from 2010-12-22.21.06.07 --> mismatche md5
-deleted the previous folders, and create folder one by one manually the drag each file inside --> mistmach md5
Those are the steps I tried, I'm running out of ideas.
googled the issue and couldn't a single concrete answer to this problem... My guts is telling me is a directory bad naming, but I'm keeping it just as it is.
any help is appreciated!
Thx in advance

be sure you've got busybox
Code:
adb shell
cd /sdcard/clockworkmod/backup/[COLOR="Blue"]YourDate[/COLOR]
busybox md5sum *.img > nandroid.md5
then reboot to recovery to do a nandroid restore,does it do your job?

jonirrings said:
be sure you've got busybox
Code:
adb shell
cd /sdcard/clockworkmod/backup/[COLOR="Blue"]YourDate[/COLOR]
busybox md5sum *.img > nandroid.md5
then reboot to recovery to do a nandroid restore,does it do your job?
Click to expand...
Click to collapse
This will definitely do the job except in case the backup actually is corrupted.

I'm guessing that the backup is corrupted. It happened to me once when I backed up to try a new rom and decided to restore. Like what you had I got an error on md5 also.
Sent from my infin1ty powered Nexus S c",) using XDA Premium App

Related

[Need Help] Galaxy 3 Backup Tool

Hi,
i hope anybody can help me to make a Galaxy 3 Rom Backup Tool.
I made a little script for the German Forum, and it works fine but i can not flash the backupped Rom files.
Can somebody help me how i can push the backupped /data partition in datafs.rfs to the Phone without getting a Bootloop?
Here is a link to the Script http://www.multiupload.com/TAIJ9Z53J7
Sry for my english ^^
Nice work!
Will try ASAP...
And btw your english is good enough!
Ok, translated for you :
Code:
Install Total Commander and connect your Galaxy 3 to your PC in USB debugging mode
Next run Backup.bat
Your backup is finished when the window closes by itself. You can find the data in the folder backup on your SD
Copy the whole folder to your PC
Open the ROM Image.tar in total commander
Now you can flash your backup as One Package in Odin.
WARNING: please mention my name when you upload or translate the tool
Thanks for the code, I was just thinking along the same lines. You can skip the Total commander thing if you'd include something like 7zip commandline which is free. You can then call it from your batch file. Or tar it in the phone itself or is this too slow/bad for SD ?
You pull the files over with adb pull, but instruct to copy them from the SD as well.
As for why it bootloops : need to test it, but will probably wait for a fresh rom.
You can also put it back with dd ?
hmm
with which adb command i can put all 5 files in a flashable .tar file?
and how i can put the whole /data partition from the datafs.rfs in the /data folder and overwrite the files in the data folder?
Hmm, I see it's Busybox responding on my Galaxy, maybe it's not installed by default, but it was included in a custom ROM ?
Code:
BusyBox v1.18.4 (2011-03-20 15:16:04 CDT) multi-call binary.
Usage: tar -[cxtzjamvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
Options:
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
You'd have to remount /data r/w to make any changes to it. But if you're dd-ing, it'll talk to the block device directly. Not sure how to clear it though, maybe dd does it by itself. Have a google for linux commands.
hmm ok,
and why i get a bootloop when i want to flash the files with odin?
one more question ^^
how i can pull the complete /data partition to SD card?
And Creating a .tar file with 7zip commandline works, but the File is not flashable.
you can find the info in i9000 forum
http://forum.xda-developers.com/showthread.php?t=943588
http://forum.xda-developers.com/showthread.php?t=960946
http://forum.xda-developers.com/showthread.php?t=965190
Okay i have a 1 click Rom backup now ^^
But its still the problem that i get a bootloop after flashing...
Ok, I tested it and /data was wiped, phone can't mount sd card etc. etc.
tgm28 said:
Ok, I tested it and /data was wiped, phone can't mount sd card etc. etc.
Click to expand...
Click to collapse
Use THIS from HERE.
Quoting deskjeti.
deskjeti said:
Hi,
I made a Backup & Recovery Script in the German Android Hilfe Forum for the Galaxy 3.
The Tool make a flashable Rom with 3 Clicks and Restore the Backup with one Flash and one Click.
The Script restores all Apps, app Data Google Account and Wifi key´s.
How To:
Unzip the zip file wherever you want and plug in your Phone with USB Debugging Mode.
Run the Step1 and wait, after Step1 is finished run Step2 and if Step2 finished Run Step3
In the "Alexgalaxys G3 Recovery v2 Final" Folder now is a CustomRom.tar.
Flash it as One Package.
If the Phone is started plug the Phone in Usb debugging mode and Run the Recovery.bat after it is complete you have to reboot you Phone.
Link: http://www.multiupload.com/NV0CFVYV2I
Click to expand...
Click to collapse
Although I edited the files to just be one click.

[FULL-HOWTO][DEV] Make Your Own CWM-Flashable Custom ROM -Edited on 14th Jan!

Code:
THIS TUTORIAL IS MEANT FOR DEVELOPERS.
NOOBS WHO ARE TRYING THIS OUT,
BE READY TO RISK YOUR BRAINS.
AND, THIS METHOD CAN HARM YOUR PHONE. ON WRONG BUILDING OF ROMS,
YOU MAY BE STUCK ONTO A BOOT-LOOP.
ALWAYS, HAVE A NANDROID BACKUP FOR SAFETY!
FEEL FREE TO ASK QUESTIONS. AND, YOUR WARRANTY IS NOW OFFICIALLY VOID. CONGRATS.
What You Need?
->Cygwin
-> DSIXda Kitchen
-> A windows/ Linux environment.
-> MagicISO
-> Base ROM --NOT CUSTOM ROM-- --AN OFFICIAL ROM--
*Dont take works of Developers of Custom ROM. Develop your OWN custom ROM*
->7Zip
Basic Thing.
Extraction of RFS.
Well, THis is the First thing you should do.
Here are the steps:
-> Download a Firmware of your choice from the above link.
-> If you Firmware is in .zip format, be sure to extract the FW to a folder.
-> In the folder, you should find a PDA file ( The file which use put in the PDA place when you flash using ODIN)
-> Install 7-Zip if you dont have it, if you have it...Proceed to next step
->Right Click on the PDA file and open the archive using 7-zip.
-> Now, you can see a file named "system.rfs" or "factoryfs.rfs" or "systemFS.rfs", just copy the file to your C:\ (YOU CAN COPY IT ANYWHERE. I am taking C:\ as my base location)
Part II - Extracting RFS
-> Download and Open MagicISO.
->Click on File-> Open and browse to the place where you have your extracted system.rfs or factoryfs.rfs or systemfs.rfs.
-> Now, you should be able to see many folders like lib,system,xBin,vendor,etc.
-> Copy ALL the folders to your desired location. Be sure to put all of them in a folder called system. For example, In C:\ , create a folder called ROM and create a sub-folder called "system" and put the files there.
In my case, The Extraction is placed at C:\ROM\system
P.S-> You Just finished Step 1
Step 2-> Editing your ROM and Removing and addition of System Apps
First, Go to the folder where you extracted the ROM and then go to \System\App.
Here, you can find ALL the applications which are un-installable by the user.
So, If you want to REMOVE apps, you can remove them and their .odex's. But, be sure, For what apps you are planning to keep, DONT REMOVE THE ODEXES.
------
If you want to add up apps, just copy the .apk of that app and put it to \system\app. But, the User can not uninstall this app.
For any Theme changes, replace the Framework-res.apk in the \system\framework.
For Status Bar Changes, replace the systemui.apk in the \system\app.
Do Not Change Anything in xBin and Vendor folder.
On changing stuff there, your ROM will not boot.
-----
If you want to put apps which the user can un-install, here's how to do it.
-> Go to your BASE FOLDER. In my case C:\ROM
-> Create a folder called Data and a sub-folder called \data\app.
-> Put ALL your .apks in here. On doing so, the user of the ROM can un-install the app.
------
Just copy the META-INF folder of any other ROM and put it in your base folder. (C:\ROM in my Case)
Custom Boot Animation And Boot Sound
Cutom Boot sound
First, navigate to /system/etc and find PowerOn.wav. This will enable you to change the boot sound. Replace it with a short tone of .wav format only. Now you,have changed the boot sound
To change the boot animation
1) Download the bootanimation and samsungani file attached in the Downloads Section
2) Put them in the /system/bin folder and replace the existing files there
------------->>>> The Above two steps are not needed<<<<------------------ Only if the bootanimation does not work, use these files >>>>>>>>>-----------<<<<<<<<
3) Now download any boot animation, and rename the bootanimation to “sanim.zip”.
4) Now, navigate to /system/media and replace the “ODEanim” with “sanim.zip”
You are done with the bootanimation change
Installing the Cygwin and Setting up the Kitchen
Download the Cygwin files attached below. Extract the zip to a folder. Now, you can see 3 icons, a read-me,a setup, and a folder. Choose the setup. Here You will choose install from local directory. Next, Navigate to the the folder of extraction of cygwin and choose the folder Cygwin_packages inside the cygwin extraction folder. Wait for some time. Then, You will come across a list of file. Click the 2-circle-arrows,untill, it displays “install”
After the procedure is complete, run the batch file. Now, minimise it and extract the android kitchen.
Keep it in some location like C:\Kitchen
Now, open the batch file window and type
cd C:\Kitchen
Wait for some time and then when the location the changed, type
./menu
As this is a HTC kitchen, you can't use all the features,
Now, go back to the base folder (C:\ROM in my case) and create a zip (Recomended to use Winzip) ( I repeat zip and NOT rar) of all the folder in the “Bse Folder”(C:\ROM in my case). After that is done, navigate to the kitchen folder (C:\Ktichen) and palce the .zip in the “original_update” folder.
Come back to the Cygwin Batch window. Now you select 1 (i.e. the first option and press enter.
Then, again press 1 twice!
Now after this is done, you can also use option 2 (rooting). You can change the ROM's name using option 8.
De-odexing the FW.
In the batch window, choose option 0 and then choose 1.
Using this you can de-odex your FW.
Next, choose 99 to build and pack you ROM.
You are now Done with the custom ROM and can find your build in the Output_zip folder of the Kitchen (C:\Kitchen in my case)
WARNINGS::
-> IF you are asked to add a fake boot.img, choose yes.
-> If you are asked to change updater-script to update-script, choose NO.
Awesome
Sent from my SGH-T959V using XDA App
For EXPERIENCED DEVS and LINUX USERS.
No n00b Post
Extracting and odin build
xvf ODIN_FILE.tar.md5
NOTE:.md5 is optional
Rebuilding
Code:
$ tar -H ustar -c amss boot.img csc.rfs recovery.img system.rfs >ODIN_FILE.tar
$ md5sum -t ODIN_FILE.tar >>ODIN_FILE.tar (signing the file)
$ mv ODIN_FILE.tar ODIN_FILE.tar.md5
Of course,u Have to put the name of ur file in place of ODIN_FILE
Mounting rfs(on linux)
Code:
mkdir system_mount
$ mount -o loop system.rfs system_mount
$ cp /folder/application.apk system_mount/app/ (adding aplications)
$ rm system_mount/app/application.apk (removing applications)
$ cp /folder/application.apk system_mount/app/application.apk (replacing aplications)
$ umount system_mount
:: Downloads ::
Cygwin
MagicISO
Kitchen (Thanks to dsiXDA)
--
Optional
Custom booting Files
Reserved.......
--For the Future!
Last one!
Press The THANKS!
Thank you for writing this but wrong section. Guides should go in the general section. You could probably ask for it to be stickied.
Kool. Is to understand lol well if u understand the basic. I try other devs Rom for base but of course all credit goes to them. Its just fun to experiment sometime
Sent from my SGH-T959V using xda premium
Funny i just linked you like yesterday in general forum haha
Sent from my SGH-T959V using xda premium
ericmpanda said:
Funny i just linked you like yesterday in general forum haha
Click to expand...
Click to collapse
Maybe it should have stayed there and just linked to the one in the general forum in the wiki.
Oh well.
ericmpanda said:
Funny i just linked you like yesterday in general forum haha
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I did not quite get you? :-/
Sent from my I9100 using XDA Premium App
bangalorerohan said:
I did not quite get you? :-/
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1441619
bhundven said:
http://forum.xda-developers.com/showthread.php?t=1441619
Click to expand...
Click to collapse
Bahaha! Lol!
Thats what i was like at first i thought you stole it then checked the original I saw and it was you lol
Sent from my SGH-T959V using xda premium
bangalorerohan can you please upload the kitchen and all files again in a pack since megaupload got out of you know bussiness i dont really know which versions i should use in order to follow your guide .
and Thanks for your guide man :3

[SCRIPT]md5sum mismatch error fix for cwm's nandroid

get to know what is md5 here
md5sum mismatch occurs only when something have be done to the backup, fixing error doesn't mean backup is fixed, anything can happen after restore
almost every cwm backup is supported, different names of the backup file is not a problem for this script, this script handles every file name
using the script is very simple
download the script from here
execute with the help of script manager
if you execute it from terminal emulator then script may not function correctly
if it gives any error I will be happy to fix it
Requirement:-
1. busybox
2. cwm backup
root is not required but if you don't have busybox then you will need root to install busybox
if you want to do it manually or don't have busybox
1. open terminal
2 type
Code:
cd /sdcard/clockworkmod/backup/backup_which_you_want_to_fix
md5sum .* c* d* s* > nandroid.md5
and the md5sum will be fixed
Click to expand...
Click to collapse
hope you like my work
changelog:-
v2
1. will check for nandroid.md5, if not available script will inform you
2. md5sum will be checked before and after fixing
3. layout is changed and now more clear
4. script will provide more info to the end user

Status 7 - bricked?

Hi there, i rooted my phone and have tried to install cm 9 but the phone returns with a status 7 aborted message, ive followed all the guides the the letter, and when i now try and restore my cwm back up i get a check sum error 5 or summat. Is it bin material?
You can do this:
1. boot in recovery
2. go to mounts & storage > mount usb storage
3. now browse to your backup folder (/clockworkmod/backup/.../)
on your computer open nandroid.md5 with notepad ++
then place md5sum.exe (search for it) in that dir and open the command window there.
Delete
now enter:
md5sum *img
and you will get something like thiS:
aae16b35136591c93c56bcc42069ffb6 boot.img
aae16b35136591c93c56bcc42069ffb6 recovery.img
Now in the nandroid.md5 file, delete all lines and place the lines you got from md5sum in there, (be sure to save it in linux format)
Then save the file and restore your backup!
cheers, worked great. Any idea why i am getting error 7 when i go to install a new rom or kernal through clockwork mod?
thebarraster said:
cheers, worked great. Any idea why i am getting error 7 when i go to install a new rom or kernal through clockwork mod?
Click to expand...
Click to collapse
which recovery do you have ?

Nexus Root Toolkit - Nandroid Backup always fails MD5 check 'not found'

This appears to be a problem which is not device specific, as it happens on my Nexus 4, Nexus 5X, and a Nexus 7 (2013) LTE...
All the devices are running their latest stock Android and rooted using NRT with the relevant SuperSU, TWRP recovery and with Busybox installed.
On each device, when I run Nandroid backup using NRT, the files all appear to be copied successfully to the PC, but the md5 cross-checks fail because the backup files are not found on the device. Here's an example from the Nexus 5X:
This is the first part of the wugcheck.md5 file sent to the device:
7c6e0c3198e422ac72122f63cf9e6859 /data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/boot.emmc.win.md5
431c7e261fbf14b3d157d2281b9e1aa1 /data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/cache.ext4.win.md5
114ea20eb1ad4b7cd9ba4b0c38764798 /data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/cache.info
...
And the first part of the log returned showing the md5 check failure:
Pushing "wugcheck.md5" to your device...
adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\MD5check_Depot\wugcheck.md5" "/sdcard/wugcheck.md5"
Verifying hash of transferred directory...
adb shell /sbin/busybox md5sum -c "/sdcard/wugcheck.md5"
md5sum: can't open '/data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/boot.emmc.win.md5': No such file or directory
/data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/boot.emmc.win.md5: FAILED
md5sum: can't open '/data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/cache.ext4.win.md5': No such file or directory
/data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/cache.ext4.win.md5: FAILED
md5sum: can't open '/data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/cache.info': No such file or directory
/data/media/0/TWRP/BACKUPS/00edb5af33a9b510/2016-03-20--01-04-55/cache.info: FAILED
...
All the subsequent md5 checks fail in the same way.
My understanding is that /sdcard/ and /data/media/0/ should map to the same directory, and according to ES File Explorer all the relevant files are present in /sdcard/TWRP/BACKUPS/etc. (though ES File Explorer seems to give the mapping as /storage/emulated/0/TWRP/BACKUPS/etc.). Can anyone explain what's happening and how to fix or circumvent it?

Categories

Resources