Backup Error - Copying Keychain Data

Hey, I'm still on iOS 5.1.1, haven't backed up for months and also get this error all the time.

Can I delete the keychain-2.db only when I have jailbreaked or is this also possible without modifying my iPhone?

Thanks in advance!

@sdschramm You are a genius.

This had been happening on my iPhone and not my iPad so I knew it was a device error.

I read SimX's solution but that was too difficult for me. Then I read your post, so connected my phone 4S , ran iTools (Great Chinese App = get it from http://www.itools.hk - free.)

I navigated to the folder as you described except it is called /Keychains (with a "S") and renamed the keychain-2.db to BADkeychain-2.db.

Fired up iTunes and clicked Backup and lo and behold, the Backup WORKED!!!

Thanks so much. However did you figure that out?

Real genius I have to say.

Cheers mate.

Sorry for the 2nd post but this forum will not allow me to edit my post.

Just a note that after removing the keychain-2.db file when I unlocked the iPhone it asked me for my rmail password. Obviously this is stored in this file. I just entered it again and mail was fine.

I want to collectively thank Loren Ryter, sdschramm and Bernbout for their efforts in documenting these issues, because after weeks of not being able to either log into any encrypted WIFI ("incorrect password" issue) as well as being unable to backup to iTunes (or any other backup program for that matter), I have finally solved the problem by deleting the keychain-2.db file in var/keychains/.

I think if you have any of the two above issues or more, you can be safely assured that it's most likely due to your phone's corrupt keychain file. I asked some professionals about this and what they said was to backup to iCloud and then restore. Due to multiple reasons this was my last resort, not to mention my phone was unable to get my house's encrypted wifi to do an iCloud backup, so I am so happy I found a solution!

Not to mention that I have ignored the backup problem since my phone first/last backed up in January - it was the wifi problem that was driving me nuts. I had deleted all backups in case they were corrupt as well, so was left with little alternative.

Others above have used PhoneView (which I also have) and iTools. Personally, I prefer using DiskAid, which can connect/SSH to your phone by USB or Wifi - very useful if you have no internet access. From there, access var/keychains/keychain-2.db and delete that file.

I haven't encountered any problems with the push notifications so far - all I've been prompted to do is to re-enter my various email/exchange passwords, etc.

Hope this helps someone!

- Joey

@princeling

Hey Joey

What I ended up doing and still have to do is I rename my keychain-2.db file and do the Backup and after it is complete I rename it back again. This way I did not have to re-enter the mail, wifi, facetime, iTunes, iCloud etc.etc PW that are stored here.

Cheers

BB

@bernbout

Hi BB,

That sounds like a possible solution except that the keychain file is corrupt, isn't it? So after you do the backup, if you rename the keychain file back into the system, isn't it still corrupt, i.e. same problems again?

Cheers,

Joey

Yes, same problem in that you will need to rename it each time you backup. I just did not want to have to re-enter passwords again, some which I have forgotten over time 😟

Anyway if you had no problems then that is the way to go.

However I did find one problem with using a new keychain file instead of the old one and that was that I could not get my phone to connect to Facetime and iMessage. It would just sit there for days with the message "Waiting to confirm the id with the Apple server" or some such. That is why I ended up going the rename route rather than the delete route. Facetime now works fine.

I did try solutions for the Facetime issue like removing Facetime and reinstating it etc but none worked.

If it works for you then the delete is the way but for me I have to go the rename route.

BB

Ahh, I see. I see how renaming would be the most viable option if you have no other problems and backing up is the only thing you want. Unfortunately, it is also preventing me from accessing any encrypted WIFI, which is a huge issue so. Unless I encounter any other devastating consequences, I think I'll do this for now.

It's also interesting to know you have these issues with Facetime and iMessage. I can't really confirm this because I pretty much have never used either, but I'll let you know if the issue crops up for me too.

Cheers,

Joey

i just wanted to ask where i could find the keychain-2.db file:/ had this problem for months and it's driving me nuts

Its in /var/Keychains/

Not sure what your question is, aasdfghjkll. If you read our posts above, we clearly state many times that it's in var/keychains/. I also state in my first post that you need to SSH into your phone in order to be able to access this. I use DiskAid, and there's also PhoneView - which I don't think requires your phone to be jailbroken. There are tons of applications and possibilities just a Google search away if you still haven't found a solution.

Thanks for all this info. I've struck the keychain/back-up problem - don't know why. There I was thinking Apple was perfection perfected.

I've used several of the apps mentioned (e.g. Diskaid, Phoneview) to find the mysterious var/keychains/ file. But once I connect the phone to these apps, I don't know where/how to find this file?? Any help appreciated.

Is it possible that only jailbroken phones can access this file? Has anyone accessed without a jailbroken phone?

Thanks!

Hi Paddlesnz

I have exactly the same problem as described here.

I have downloaded Phoneview but cannot locate the var/keychains/file. Sorry for being stupid but can someone help me find it?

My phone is not jailbroken - is this why I cannot find it?

Any help would be much appreciated.

Thanks!

Hi Matt - I note that Princeling above says:

I also state in my first post that you need to SSH into your phone in order to be able to access this.

Had a quick look at "SSH iphone" on google and it is beyond my level of skill. I'm tapping my fingers on the desk wondering what to do next really.

So good news with ios 7 on this backup/keychain error.

I was able to back-up to icloud (just not manually back-up through itunes).

Then on the iphone I updated to ios 7 (needed 3.3GB storage available to do this). I actually tried to update through itunes first but because it needs to back-up as part of the update it comes up with the error message. Hence I used the update software function under the phone settings.

With a succesful install of ios 7, I then back-uped succesfully to itunes. So, as part of the new software update it looks as though Apple has fixed this keychain error. Hopefully others have success here too.