Database Info

[Solution] MD5 mismatch error

Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.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 mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Credit goes to UsmanJ member. I have just shared with you guys with more good explanation.
Original thread HERE
Click to expand...
Click to collapse

No need these at all you need "root toolbox". and ut works perfectly by the way thanks for sharung this way too
Tapatalk 2 ile GT-I9003 cihazımdan gönderildi

If you do this you can't be sure that your backup isn't broken. md5 needs exactly for checking this. Yes, you cheated the check system, but are you sure that your backup integrity is fine?

This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.

silentvisitor said:
This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.
Click to expand...
Click to collapse
Ya but sometimes we have to face this problem even if we dont change folder name like how it was happened in my case few days ago.

Well, I think this is no hint you should use. When creating a new backup md5 hashsums are calculated for each file. If you now want to restore it these hashsums are calculated again and compared to the previous ones. Only if the data is the same as before , in other words your backup hasn't been damaged, the checksums match. You may have had some luck that the error happened in a file that does not get used very often but in general you do not want to do that, just imagine your kernel backup is broken!
Sent from my GT-I9003 using XDA

Thanks, worked just fine for me.:good:

The error is not only because of changing the name of folder, as vishal says md5 mismatch can occur.
I even encountered the following problem with nandroid backup.
stock gb,xxkpu nandroid not compatible over cm9 or miui.
Or miui/CNET not compatible over stock rooted ROM.
I'm not sure of the reason why this error occurs while reporting the nandroid backup, but according to my limited knowledge of Android, I suppose either ext4 partition is not compatible over rfs of stock and vice versa or, out might be a kernel clash.
To be true, I didn't even try to search much about the issue as I'm mostly free and take the pain of customizing three new firmware as power my preference and reinstalling the app
Sent from my GT-I9003 using xda premium

If anyone is sure of the error and it's solution, the answer is most welcome.
P.s. while restoring out doesn't say md5 mismatch (I've also come across this though), the error I stated cannot restore the boot image atty the first place.
Sent from my GT-I9003 using xda premium

@ Iambalvindar
You are right bro. There can be number of reasons about this md5 mismatch error. Actually the solutuion which I have provided is just an option to correct error If error is due to other reason such corrupted backup then obviously the solution given in my thread will not be applicable.

The first two commands ('su' and 'mount') are not necessary because:
You don't need root permissions to edit stuff in /sdcard
/sdcard is always mounted as RW (that's what the second command does.)
EDIT:
I've just remembered that if you don't have busybox installed you don't have the 'md5sum' command avaible for the user.
However our CF-root kernels come with an inbuilt busybox, but it can't be used as normal user, because if I remember correctly all the symlinks are in /sbin, where the user has no access. So, probably, you need to do this as root (= type the 'su' command as in the OP).
Anyway, nandroid.md5 is the last thing made during a backup. That means if you don't have enough space for the backup and it stops, this file is not created. So, when you go to restore that backup, you have the mismatch error. In this case, if you create the nandroid.md5 as vishal wrote, you'll have a usable and damaged backup. So, before doing this, check if nandroid.md5 is there or, when you run "rm nandroid.md5", make sure the output is not "No such file or directory", because it means that most likely the backup is not complete.
All of these to say: be careful and do this if necessary (unless you know what you are doing of course).
A suggestion:
In this situation you can do an "advanced restore" and restore only /data and /datadata if you are using the same ROM you used for the backup (maybe a slightly different ROM is good too). The only things not restored are the mods you applied and system apps, but for the mods, simply reflash them, for the system apps, well, they are always the same. All the apps installed through the market are in /data.
Maybe this will cause bootloops, but in this case you can simply reboot in recovery and do a data wipe/factory reset. This will let you boot without the need of a reflash. You have of course to reinstal all your apps etc, but it's better than starting from scratch.
Or, even better, do a backup before the restore of /data and /datadata, so that in case of problems you can always restore everything.
EDIT 2:
I think you can do this even when you change ROM, as long as it's a stock ROM. That's because stock ROMs are intended to be flashed over another stock ROM and they are made in a way that you don't need to wipe your /data partition. When you use kies to upgrade, you don't loose anything. Restoring /data and /datadata should have the same effect (it's better to wipe the dalvik-cache after this).

@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium

iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Ya its because different kernels have different cwm version & also different kernels creat different md5 code as per backup.

iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .

loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore from a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backup are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Cool, thx for the info. Nv knew the difference between the kernels
Sent from my GT-I9003 using xda app-developers app

loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Yeah, most probably be that was the issue... Kernels needed to be changed.
Thanks
And I already saw that my backup was not corrupted with md5 check.
Moreover, I also don't use nandroid much, I always configure new ROM I try, from the scratch.
It's just that I needed to use USB storage urgently, which sadly doesn't work on any ics based ROM. So tried to restore the backup. Alas !
Had to flash again from scratch to get to stock gb, as I didn't have any gb.zip in sd card or computer.
Sent from my GT-I9003 using xda premium

i am not able to restore my backup due to mismatch md5
vishal24387 said:
Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.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 mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Click to expand...
Click to collapse
i was using another bootloader and another cwm

Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium

ganeshbiyer said:
Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
ok buddy I will update information in few minutes
I am still waiting for ur test kernel with modules inbulit in it.

I was on the same issue as all people with MD5 failure, then I rename my backup name with a short name with no space or blank and the it run like a charme !.
Hope it could help.

[Q] Help! Need to flash a working ROM [SOLVED]

So I just bought this phone, came in Monday, got it activated the same day, was excited! I had many Android phones and rooted without any problems. This one was far easiest the root. I had the stock ROM of course, followed the easy bootloader unlock method, bam! Phone fully unlocked! Fast boot and ADB were openly available, used ADB to reboot into bootloader again to flash CMW with fast-boot. Sweet, now I have recovery! That was a lot less painful process then I had with any phone. After reaching the recovery menu via ADB reboot recovery, I flashed SuperUser for root, and was cheering in victory, then did a clean factory reset to start using my phone as if new (with SU and CMW). At this point I had no idea I could access CMW without a computer (which I should I knew I could after so many roots and unlocks), and this option for a extended reboot to recovery menu was infront of me, waiting to be flashed. http://forum.xda-developers.com/showthread.php?t=1884282 .
Now, I went ahead and try to flash this zip for those extended options, and that is where I went wrong. The zip file screwed my phone so that it would get stuck on the Sprint Logo, and then I realized I forgot to make a nandroid backup. I went ahead and try to fix it, I didn't want to deoxed my phone, wanted to keep it as Factory OEM as possible. Look a glance at the guy's update script, and realized he removed a necessary .odex file and did not include it in the stock power menu to flash back to normal, so now I was stuck w/o that necessary .odex file and a phone that gets stuck at the sprint loading screen. At this point I was still okay, but was questioning this uploader's work, he never mentioned that a deoxded was needed, and his "stock" wasn't stock, it was deoxded without the .odex.
I wanted to clean the "contamination" and start over without a clean untouched ROM, which was a terrible idea. Still forgetting to make a nandroid backup though, and went ahead and found a system dump and system images (system.img.ext4, etc), did a FULL Wipe with (no nandroid backup!) And now my system partition and user data partition in wiped clean. Of course I tried flashing the system.img.ext4 and userdata.img.ext4 and what not with fastboot to get back to clean slate but that wasn't the case. Now I got stuck on WARNING BOOTLOADER UNLOCKED, and it will not even go to a sprint logo boot.
Now I realize I never made a nandroid backup, and kept putting myself in a bigger hole without making one from the start. I tried everything, fastboot flashing, I even make a system.zip update file for CMW to copy a system dump directly to the system partition, phone boots up, flickers, goes to CMW (thought that was going to work for a second). Now I'm stuck with a semi-bricked phone not-so-brand-new-anymore Motorola Photon Q, desperately searching for a way to flash it back in working order.
I have tried and flash various system dumps from users to no avail, and there not any full roms available that can get me out of this mess. Is it anyway method I'm missing to flashing these system dumps to get my phone back online, or will I be stuck without a phone until a rom comes out? I have been using these provided dumps
http://forum.xda-developers.com/showthread.php?t=1856456
http://forum.xda-developers.com/showthread.php?t=1874359 (Bought a Hotfile prem to download this, regular was taking forever, I could reup on my faster FTP if someone wants to give it a shot).
Please help if you know a way to get my beloved phone online! I only had it for a day and I'm in love with it, have no idea where I don't hear more about this awesome phone, I was sold when I saw it in the sprint store. (Reminds me of my old galaxy s1, it was a champ!)
*EDIT*
Problem solved! Thanks arrghhh for his backup files!
1. Use fastboot to flash TWRP to recovery.
2. Make a folder and put these files in that folder!
https://dl.dropbox.com/u/12691845/system.ext4.win
https://dl.dropbox.com/u/12691845/system.ext4.win.md5
https://dl.dropbox.com/u/12691845/boot.emmc.win
https://dl.dropbox.com/u/12691845/boot.emmc.win.md5
3. Place this folder in the following directory.
[Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / [your folder] ( so if your folder is called "argh_restore", it should be found in [Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / argh_restore ) , and inside that folder, the files you downloaded.
4. Boot into recovery, I assume you know how to do this since you unlocked your bootloader to mess up your phone in the first place .
5. TWRP should load, press restore, your folder should show up, select it, select system and boot, enable MD5 checking, and restore your phone.
**IF YOUR FOLDER DOES NOT SHOW UP, directory may be incorrect. You can make a backup and see where it goes to figure out where to place your backup folder!
6. Reboot your phone, your good to go!!
PS. This backup is NOT CLEAN stock! It is stock with deoxed, battery & toggle mod, and extended menu mod, I BELIEVE. Those are the only mods really available so that's my assumption, but arrghhh may know since it is HIS backup that he provided. So far, I've been using phone all day, seems to be running well. Just like stock! Also, I can't forget, shabby's awesome SuperUser mod for root! (You won't need CMW since you have TWRP, but if you want to swtich recovery, thats up to you. CMW is most popular recovery but TWRP is really great as well)!

I'd say you're going to NEED a nandroid backup to restore...
I was hoping flashing the de-odexed would work for ya. Would a nandroid backup of the system partition work? Hopefully it does, because that's about all I can think of to provide for you...
And lesson learned, I hope. Anytime, you do ANYTHING in recovery - MAKE A BACKUP!!
Edit - I re-read your post, did you try flashing the full de-odexed version? Seems like you have some hatred of it, lol... but if it saves your butt who cares.

I did flash a odex system dump, a deoxed system dump, and a system.img.ext4 dump to no avail.
But when the issue first occurred after I flashed the new power menu, I never flash the deoxed version to get the new menu to work. I know it was needed the issue but wanted to restore the original odex. I wanted to keep the phone system as OEM as possible (had some bad experience with modding to much, things don't work they way they use too). I could have done that to fix the issue before, but since I wiped it won't make a difference now (formatted /system /data /cache in CMW).
A Nandroid backup should definitely work I can though!!!!
If I can use someone working Motorola photon Q Nandroid backup I should be able to do a restore all of the system files I wiped (I'm not sure if any other partition other then the /system in the Nandroid backup would have to be restored to get the phone working, I know there /data but I think /system adds the files on first boot to /data?). I can still fully boot into recovery/fastboot but just need recover the system files back.

Sorry to hear you had problems i have supplied links in previous posts to all files Deodexd and back to original odex
PhotonQ stock Deodexd
PhotonQ stock Odexd
hope one of these help you get going

Yea, I meant try flashing the de-odexed version... even now after you're busted. Rangerbry kindly posted both tho. Hopefully that gets you back in business.

Just read he formated /system tho i can upload all that unless someone beats me to it
Sent from my XT897 using Tapatalk 2

Rangerbry said:
Just read he formated /system tho i can upload all that unless someone beats me to it
Click to expand...
Click to collapse
I get that he wiped /system. I thought what you posted would restore that? I guess not "all" of it eh?
I can take a nandroid backup of /system, but at this point it's been modified - it's far from OEM...
I have a few old nandroid backups, but I don't know if I kept the completely stock one. I should have in retrospect, so I'm going to hope I can find it...
Edit - the only backup of /system I have is a .win file for TWRP... sorry.

If it works I'll take it! lol. Stock would be nice but I have no choice at the moment. I could use a modded rom until a stock rom comes out, just don't want to be with a paper weight lol. I'm trying the Photon Q stock Odexed.zip right now though.

I have a full stock pull i keep on hard drive but cant get it till after work
Sent from my XT897 using Tapatalk 2

Ya may need full stock pull, flashed odex with no avail .

SleepyPanchoo said:
Ya may need full stock pull, flashed odex with no avail .
Click to expand...
Click to collapse
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...

I know shabby has stock images pulled from the Motorola Photon Q here : http://forum.xda-developers.com/showthread.php?t=1856456
I did fastboot flash the system.img.ext4 (523 mb - seems like a full system image!) he has provided to no avail. But I'm thinking it should have worked? Its looks like a full system.img that should write all the necessary data to the /system partition to get me going, unless I have to rename system.img.ext4 to system.img before flashing, I'd have to get that a try and see if that makes a difference.

I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!

SleepyPanchoo said:
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
Click to expand...
Click to collapse
No prob and last i checked this is XDA no ones ever alone in getting problems fixed here. Still going to be several hrs until i get home tho
Sent from my XT897 using Tapatalk 2

arrrghhh said:
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
Click to expand...
Click to collapse
Just flashed TWRP 2.2.2.2 gonna give your system.img a shot!

Looks like it help me resotre your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
*EDIT*
I'm using shabby's stock images to fastboot flash userdata.img.ext4 but does not seem to have any effect. Data is still the same size. I may need a full nandroid backup to get this phone recovered, guess I will have to wait Rangerbry to upload that backup. hopefully that will work.

SleepyPanchoo said:
Looks like it restored your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
Click to expand...
Click to collapse
Did you restore "everything" or what was checked on restore?

I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?

SleepyPanchoo said:
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
Click to expand...
Click to collapse
Why would you need my /data? Or /cache!?! That doesn't make any sense.
I can provide a backup of /boot and /recovery.
Edit - Hrm... Well, /recovery shouldn't be needed. boot.emmc.win / md5

Wouldn't data have some required files for android to work? I know it contains user data as well (such as apps) but a nandroid backup, factory reset, then 2nd android backup that is given out can be made. Im sure cache is not necessary, but I'm trying everything at the moment, nothing seems to work when it feels like it should...!! I guess I can give your /boot a try. Don't think its /recovery since Im using your recovery now lol.

[Q] Newer CWM, md5 mismatch won't allow recovery.

I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:

LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.

SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)

LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta

Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.

Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2

LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.

[XT1032] CM 12 - Flashing TWRP v2.8.6.0 has caused bootloop

Hello,
XT1032 CM 12 latest nightly (I think)
I flashed TWRP v2.8.6.0 using their manager app. I entered recovery mode and everything seemed to work fine. I made a NANDroid backup then rebooted. Unfortunately the device was then stuck at the bootlogo and kept looping. I can still access recovery and fastboot but for some reason adb doesn't see the device, nor can my device's data be access under Windows 7. I don't recall if I had USB debugging on or not. I would like to try to backup a few files to my computer (the backup for instance) but I am unable to since I can't use adb as the device is not recognized. MTP through TWRP doesn't seem to work either. I do have the Universal drive pack installed already on Windows.
Any help would be greatly appreciated. Thanks for your time.

To start with, let's make sure the files you want still exist.
1. Boot into TWRP recovery
2. Go to "Mount" and check that your "Data" partition is selected
3. Go back and then go to "Advanced" and then to "File Manager"
4. Navigate around (maybe /sdcard/ ? Depends what you're looking for) and find the files you need
If you can't find your file, you'll need some more help. Let's say you do see your file. Do you have a USB-OTG cable? You could plug a USB drive into your phone and mount that. Then you could copy your file to that drive. If you don't have the cable you do have some other options, but let us know how far you get.
EDIT: I know I haven't addressed the problem of the bootloop at all. Many of those solutions involve wiping so we need to make sure you've backed up all the files you need first.

First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:

frustratedwhiteman said:
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
Click to expand...
Click to collapse
I'm not really a Nandroid expert, but I can take a few shots in the dark. When you did your backup you got a TAR file for System and one for Data, etc., right? Then you convert those to IMGs? If you upgraded and then restored the system backup I can see why that would result in a boot loop. Restoring the data image shouldn't cause such problems though. Is this what you've tried so far? You're right, though. The safest method is to manually restore the data of just the apps where you need that data, and do it one at a time. This would allow you to pinpoint what is causing the issue. Of course, I may have no idea what I'm talking about. I've never actually needed to restore a Nandroid backup! Hopefully someone with more experience there will chime in.

I thought to hell with it I went and solved the issue by installing CM13
Thanks for taking the time to help and see you next time

Oneplus 6 bootloop after upgrade to 9.0.4 (+failed to restore the nandroid backup!)

So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.

b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.

Thank you for making the time writing this, it is relief to hear that you figure this out. Will try this first in the morning.

I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.

tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
This guide can also be used to restore from other roms;

b217260 said:
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
Click to expand...
Click to collapse
What did you do?
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
petran07 said:
This guide can also be used to restore from other roms;
Click to expand...
Click to collapse
I guess so. I never had to use a backup to restore on a custom ROM yet.

tabletalker7 said:
What did you do?
Click to expand...
Click to collapse
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.

b217260 said:
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
Click to expand...
Click to collapse
It's my bad. I always store my backups on an SD card with my OTG card reader. I forget others don't think like I do sometimes

tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.

b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Had faced this many times. ...after trying diff options and failed Qualcome MSM method works perfectly.
Yep, You cant restore data i think as it being already formated as per knowd based on your steps above on diff posts

ahacker said:
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
Click to expand...
Click to collapse
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.

tabletalker7 said:
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
Click to expand...
Click to collapse
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.

ahacker said:
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
Click to expand...
Click to collapse
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble

tabletalker7 said:
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
Click to expand...
Click to collapse
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.

ahacker said:
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
Click to expand...
Click to collapse
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.

tabletalker7 said:
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
Click to expand...
Click to collapse
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.

ahacker said:
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
Click to expand...
Click to collapse
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.

tabletalker7 said:
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
Click to expand...
Click to collapse
-It is as horrible as not being able to restore a full backup. No more, no less.
-Twrp has an ability to encrypt your backups, with your experience you must know this.
-You are suggesting someone to switch to iphone only because they point out that the things are wrong or dont add up.
-It is quite a common knowlege that you get good security out of encryption if you make things explicit and clear. And not how you may think it is. Cause you don't seem to know where the keys are stored for the data partition. Obviousely, because the phone eventually decrypts your data, the keys must be stored somewhere or derived from you swipe pattern.

tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
Following these instructions seems to be the only way of restoring a nandroid backup (at least for my Op6 bought on AliExpress from China). Important: step 1 wipes your sdcard, so the backup you want to restore must be on otg usb stick.
After spending many hours I managed to restore a backup at least once. Fortunately for me I have no plans of upgarding Android and will likely forever stick with the following set:
1) 5.1.11-OREO-OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip (found here)
2) twrp-3.2.3-x_blu_spark_v9.85_op6.img + twrp-3.2.3-x_blu_spark_v9.85_op6.zip (found here)
3) Magisk-v18.1.zip (found here)
My plan is to fully debloat the phone and then I will keep everything unchanged for years, because nowadays updates are more about twisting your arms than giving you usefull features. I almost got to that state, but one little glitch forced me to roll back and the whole hell with the Nandoid backups on Op6 started.
PS: It's very interesting what is really going on with this A/B system. There must be a storage where the encryption keys are stored (if it is the encryption that does prevent the phone from restoring. Which I doubt because Twrp sees the files fine). There also probbaly stored what slot is used. That information does not get captured by the Nandroid backup.

(Btw, It seems that blu_spark Twrp is really NOT encrypting your backups with the passwod you supply. Official Twrp does. I have plenty of old encypted backups, from wich I could not extract any personal data (/data/data folder) but yesterday I could extract my private information from a backup done by blu_spark Twrp. This is serious iussue. I'll double check and will post if confirmed.)
Not confirmed, I was looking at unencrypoted file.