Database Info

ClockworkMod Recovery Issue - MD5 mismatch!.

I do regular Nandroid backups via ClockworkMod Recovery 3.1.0.2. I also do regular flashing and config mods so I do recoveries often. I am starting to see "MD5 mismatch!" errors when trying to run recoveries. Some work, while others do not.
I do use ES File Explorer and rename the recovery file so I know what is what, but that shouldn't effect the checksum.
Any input greatly appreciated. thanks.
UPDATE: UGH this is KILLING me. I just lost my 3 of my 4 CM7 backups including my most recent 2 one of which was made last night. I cannot recover into them - I get "MD5 mismatch!" when trying to recover into them. What the BLEEP is going on.

I had the MD5 mismatch problem too. I renamed the backup to what it originally was, and I was able to restore from it again. Don't know if it will help, but it worked for me. I'm using ES File Explorer too.

If you use a space or special character it will change the md5.
When I nandroid, I put the type of ROM it is preceding the date/time.
Ex. th3oryXXXXXXXX, bamfXXXXXXXXX

I have never had problem but I use root explorer, so might be different but I do similar put rom name after date.
I have been using the team win recovery and is pretty nice, and devs are pretty responsive to user request for different features
Sent from my ADR6400L using XDA Premium App

[Recovery] Rogue XM Touch Recovery v1.5.0-R1 (CWM-based v5.0.2.8) [2012-05-25]

Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101​
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010​
All I did slap together all their hard work to make it work on the TF101.​
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123​
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723​
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly​
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.​
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch​
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)​
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.​
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.

Thank you, looks nice. Doing a nand backup right now with it.

there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App

Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk

baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.

Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!

Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver

Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..

luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.

Worked for me. Way way way better color scheme and it booted quick! Thanks!

wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x

Just awesome!!! Thanks so much!

this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium

Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!

New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.

Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --

I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.

jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.

jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?

hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!

[Q] CWM recovery filenames

This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.

phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.

I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?

Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit

ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.

dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.

That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!

The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.

bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.

I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.

well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..

garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress

im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA

Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces

[TOOL] EFS Pro - Advanced '/efs' Backup, Restore, Repair!

I created a tool a while back for Galaxy S II owners to backup and restore the '/efs' partition and perform basic NV Repair on their devices.
This proved so popular that I recently updated the application which now includes a feature to automatically detect the mount point of the '/efs' partition. This allows any supported device to be used with EFS Pro and also adds support for future devices.
Check out the link below for more info and download:
http://forum.xda-developers.com/showthread.php?p=18524176
Enjoy!
Sent from my GT-I9100 using Tapatalk 2

Hi!
I tried 1.6.8 with my R (GT-i9103). I selected Galaxy S II as device profile because my efs partition is the same (mmcblk0p1, as shows the mount command for the efs partition). And it says "Device Partition Location appears to be invalid! Make sure you have selected the CORRECT Device Profile then try again!".
If I choose "Add Device..." button, I write "Galaxy R" for the Device Name and "mmcblk0p1" as the location and the response is "Partition Location is Invalid! Please try again a VALID Partition Location."
PD: If you prefer, I could copy&paste this post on your original thread, but I imagine you prefer answers per device in their respective places.

coldbeermt said:
Hi!
I tried 1.6.8 with my R (GT-i9103). I selected Galaxy S II as device profile because my efs partition is the same (mmcblk0p1, as shows the mount command for the efs partition). And it says "Device Partition Location appears to be invalid! Make sure you have selected the CORRECT Device Profile then try again!".
If I choose "Add Device..." button, I write "Galaxy R" for the Device Name and "mmcblk0p1" as the location and the response is "Partition Location is Invalid! Please try again a VALID Partition Location."
PD: If you prefer, I could copy&paste this post on your original thread, but I imagine you prefer answers per device in their respective places.
Click to expand...
Click to collapse
Hi there, download the latest version, v1.7.13 as automatic partition location detection has been implemented which should resolve your issue.
Sent from my GT-I9100 using Tapatalk 2

Ok, Thank you very much, lyriquidperfection, it works like a charm right now (1.7.14)... at least to backup the efs partition. Good job, man!!!

What if I flash efs.img from some other SGR... Then two or more devices will have same imei.... Will it be an issue?
I know it may not be great benefit....
Sent via XDA App...
I am a noob here... but....I am a geek.... ;-)

bhargav143 said:
What if I flash efs.img from some other SGR... Then two or more devices will have same imei.... Will it be an issue?
I know it may not be great benefit....
Sent via XDA App...
I am a noob here... but....I am a geek.... ;-)
Click to expand...
Click to collapse
well this is a insane question
i dont think it is possible to flash efs of some other device as md5 sums wont match

xlm13x said:
well this is a insane question
i dont think it is possible to flash efs of some other device as md5 sums wont match
Click to expand...
Click to collapse
Correct plus its illegal anyway.
Sent from my GT-I9100 using Tapatalk 2

He he.... Thanks dudes....and sorry for being foolish.....
Sent via XDA App...
I may be a noob here...
but....I am a geek.... ;-)

EFS Professional v2.0.9 has now been released!
http://forum.xda-developers.com/showthread.php?t=1308546
Sent from my GT-I9305 using Tapatalk 2

Great Tool thank you buddy..:thumbup:
Sent from my GT-I9103 using xda app-developers app

REPLY
lyriquidperfection said:
I created a tool a while back for Galaxy S II owners to backup and restore the '/efs' partition and perform basic NV Repair on their devices.
This proved so popular that I recently updated the application which now includes a feature to automatically detect the mount point of the '/efs' partition. This allows any supported device to be used with EFS Pro and also adds support for future devices.
Check out the link below for more info and download:
http://forum.xda-developers.com/showthread.php?p=18524176
Enjoy!
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hello Friend Trying to backup my efs partition with the version 2.0.17 but it do not show partitions plz help..USING SAMSUNG GALAXY R GT_9103

[Completed] Beginner to Clockwork mod and need help!

Hello, I have been messing around with clockwork mod recently but I'm having some troubles I'll list them below. if anyone could help me that would be great!
Question 1. Not sure what file to use. I am using a galaxy s4 GGt-i9505 and when I try to install CWM from the app it says jfte and if i click phone not listed it says gt19505 not supported. I'm not sure if this is the correct file to use because I looked on the clockwork mod website and seen the manual install files and found the gt-i9505 files on there. So basically my question is for the galaxy s4 do I flash the jfte CWM file or the gt-i9505 file? If I Google search jfte it says it just another name for the galaxy s4 so I'm not sure.
Question 2.I have had an issue with system ui crashing when trying to install the jfte file through the app rather than through Odin and once it says installed and reboot phone i still don't have Clockwork recovery it still is the original recovery that came with the phone. How do I fix this?
Question 3. Every time I do a backup to my external SD card it puts the date of the backup as somewhere in the 1970s and puts the time to 11pm and then when I try to restore to the backup it says MD5 mismatch and tells me the location where it sent the recovery.log and I can't get any of my backups to restore without MD5 miss match Every time. Does anyone know a solution.
I Am rooted and I am running the latest version of lolipop. Is lolipop compatible with CWM?
Thanks for the help! Shaun. :good:

Shaun98 said:
Hello, I have been messing around with clockwork mod recently but I'm having some troubles I'll list them below. if anyone could help me that would be great!
Question 1. Not sure what file to use. I am using a galaxy s4 GGt-i9505 and when I try to install CWM from the app it says jfte and if i click phone not listed it says gt19505 not supported. I'm not sure if this is the correct file to use because I looked on the clockwork mod website and seen the manual install files and found the gt-i9505 files on there. So basically my question is for the galaxy s4 do I flash the jfte CWM file or the gt-i9505 file? If I Google search jfte it says it just another name for the galaxy s4 so I'm not sure.
Question 2.I have had an issue with system ui crashing when trying to install the jfte file through the app rather than through Odin and once it says installed and reboot phone i still don't have Clockwork recovery it still is the original recovery that came with the phone. How do I fix this?
Question 3. Every time I do a backup to my external SD card it puts the date of the backup as somewhere in the 1970s and puts the time to 11pm and then when I try to restore to the backup it says MD5 mismatch and tells me the location where it sent the recovery.log and I can't get any of my backups to restore without MD5 miss match Every time. Does anyone know a solution.
I Am rooted and I am running the latest version of lolipop. Is lolipop compatible with CWM?
Thanks for the help! Shaun. :good:
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Samsung Galaxy S4 at http://forum.xda-developers.com/galaxy-s4 which would be a good starting place. It covers various common models of Galaxy S4, including your I9505. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/galaxy-s4/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.