I'm running MIUI 2.1.20 , and made a backup of it using the backup option in CWM (recovery mode, not the app).
The files I got though where:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
recovery.img
system.ext4.tar
notice how there is no nandroid.md5 ? Is that normal?
Also I'm used to getting files like:
.android_secure.img
boot.img
cache.img
system.img
nandroid.md5
does it mean anything that some of the files are tar balled?
Cheers.
I ran a backup of 2.1.20 two nights ago before I flashed 2.2.1 & I have a nandroid.md5 file in that backup folder. I'd be surprised if the backup you made restores properly (or at all) given you don't seem to have that file in your backup (Have you tried to restore it ?).
There's a nandroid backup patch that works when you get a md5 checksum error when running a Nandroid backup on Galnet Miui. I attached it to a post I made a few hrs ago, it may/may not work for other builds/flavours of Miui. Obviously if you do use the patch you do so at your own risk (I doubt it would do anything "bad" other than make the backup you run after flashing it bork at worst).
Edit to add - In the backup I made of 2.1.20, I have - boot.img, nandroid.md5, android_secure.vfat.tar, cache.ext4.tar, data.ext4.tar & system.ext4.tar.
.android_secure.img
boot.img
cache.img
system.img
nandroid.md5
Thats what i have for yesterdays backup .
jje
I've too nandroid.md5 both on CM9 (01292012) and on MIUI (2.1.20) backups...
does that mean my clockworkmod is goofing?
After making another backup to check the log I saw this.
http://cl.ly/2v3s0v1423252o2o0e2J
Notice the "Error while generating MD5 sum" ? ...what would you suggest I do?
ps. should I open another thread now that the question has changed?
any ideas guys? Cheers.
In answer to your question, yes, it would seem CW is not working properly for you for whatever reason.
If you've got Rom Manager on your phone, you need to make a choice. Either have/use Rom Manager or CW Recovery. Both cause problems, Rom Manager tends to break recovery & can cause bootloops.
If not, reinstall your kernel (or whole rom if you're using the kernel supplied with Miui), or install a CFRoot kernel, then reinstall your rom.
Or...Do a search for that post I made last week or whenever it was & flash that Nandroid backup fix patch.
A couple of options there for you.
Thank you very much. I'll check them out. Cheers.
Related
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.
I recently tried a new ROM and made a Rom Manager recovery restore file prior to changing. Things didn't work out as well as I had hoped and when attempting to restore, it fails at the checking MD5 sum process.
Any way to work around this? I really would like to restore to the previous ROM without starting over.
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
sandiegopaneraiguy said:
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
Click to expand...
Click to collapse
depending on the type of file format used to backup, the restoring could be done manually but a changed md5sum generally means the files are not the same as the original. this could result in corruption and generally it isnt recommended to restore corrupted files as you run the risk of nothing working.
if you're still wanting to proceeding with attempting to restore files which are different than the original and could be corrupted, off the top of my head, you can probably dd the .img files back and untar the .tar files back.
i would suggest starting over and perhaps copying the backup files over to your desktop instead of only leaving on the sdard. this should help ensure at least one of the copies maintains their integrity.
hope that helps!
You can boot into recovery, and run nandroid via adb shell command line, no md5 checksum file needed. Now if the image is bad, you of course get bad results, but if the checksum is just hosed for some reason, it will work fine.
Put the .win files for the partitions you want to restore in /sdacrd
then issue the command "tar xvpf /sdcard/data.win" or "tar xvpf /sdcard/system.win" from the adb shell while in /data or /system respectively. .win files are what TWRP creates for backups.
I had this happen with TWRP 1.01 or 1.02 once on a good backup that passed the checksum tests when I backed it up.
I was testing the reliability of the TWRP package's nandroid and first one failed.
Once I moved to the newer version, I've not had that issue.
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?
Hi
Back here....
http://forum.xda-developers.com/showpost.php?p=22413842&postcount=4299
I found my Nandroid backup may have been truncated due to a full sdcard. I've since flashed ics but want to check I can get back. There is no nandroid.md5 so I guess the process may have terminated.
Is there any way to find out if the backup files it did take are complete?
I have boot.img (8mb) data.ext4.tar (1.2GB) .android_secure.vfat.tar (89.2MB) and system.ext4.tar (454.95MB) files. no nandroid.md5 or cache (presumably not needed).
Is there a way to get a partial restore without say taking the data partition (which I suspect maybe incomplete)?
Thank you for any help you can provide
Cheers
Chris
I have serious problems with my phone, INVALID IMEI, NO SIM, everything is described in my other thread: http://forum.xda-developers.com/and...tex-aqua-5-t3006568/post58266157#post58266157
Tried everything possible, but no luck. Now I'm turning back to my nandroid backup as my only hope... But I'm stuck with error :
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error while flashing boot image!
Backup itself looks fine, it is Online Nandroid v9.52, and there was no errors in backup process (as I can see in recovery.txt) its located in folder clockworkmod - backup. It's made of these files:
boot
cache.ext4
data.ext 4
modem
nandroid.md5
recovery
system.ext4
Whats causing this error message, and what can i do about it?
Also in data.ext.4 among others there is nvram folder with these files: md, md2,dm,APCFG,Restore Flag (if anybody knows how to flash it maybe that is solution for my INVALID IMEI).
My phone is rooted, there is custom ROM on it. (MIUI V5 FOR INTEX AQUA I-5 ). And CWM recovery for this ROM. (CWM v5.5.0.4 )
IMPORTANT: Cant connect phone to PC, pins for data transfer are damaged. But can transfer files from PC to Phone - Wifi transfer.
Try to Flash stock rom ....
May be all problem are solved...?
Rajaks said:
Try to Flash stock rom ....
May be all problem are solved...
Click to expand...
Click to collapse
Not so easy without usb connection, there is just one version of stock rom for this phone on the Internet, It is made from two rar files, and as I see It's made for flashing SP Flash Tool. I even tried to make zip file from it, and flash via cwm but no luck, error pops out. Just started thread (http://forum.xda-developers.com/general/help/stock-rom-intex-aqua-5-t3007603) hoping someone will post new stock rom, until then looking for solution here.
Figured out why my nandorid backup cant be restored, and gives an error "error while flashing boot image". When I made a backup there was no boot.img file in it. (as you cant see below in log file) So I added a file from only stock rom found on the net (that stock Is not made for cwm and cant be flashed via cwm, just via SP Flash Too so I cannot use it). but my logic was that I can borrow missing boot.img and put it in my backup folder). So obviously its not solution.
Log file: (nandroid backup)
Backing up /boot...\c
02:18:25 Backing up /recovery...\c
02:18:25 Backing up /modem...\c
02:18:26 Backing up /system...\c
02:19:59 Backing up /data...\c
02:21:28 Backing up /cache...\c
02:21:30 Backing up /.android_secure...\c
02:21:34 Replacing old backup with new backup...\c
02:21:36 Generating md5sum...\c
02:22:04 Verifying md5sum...\c
02:22:05 Online Nandroid Backup Completed in 3 minutes 43 seconds!
###########################
But after this there is no boot.img at all in backed up files as you can see.
Files Backed-up:
"----rwxr-x 1 11264 Dec 8 02:21 cache.ext4.tar
----rwxr-x 1 530526720 Dec 8 02:21 data.ext4.tar
----rwxr-x 1 1024 Dec 8 02:18 modem.img
----rwxr-x 1 191 Dec 8 02:22 nandroid.md5
----rwxr-x 1 553781248 Dec 8 02:19 system.ext4.tar"
Why I dont have file boot.img in my backup and how can i fix it? :/
Someone said that I make another backup via cwm and keep just boot.img in it, then copy my old files in that new created folder , but i doubt it will work cause Im on custom ROM now (MIUI) and i want to restore stock (Andorid 4.2.1).