Difficulty restoring corrupt .sqlite files.
I installed the IDM addon and it caused my browser to revert back to an earlier version, thus corrupting my places and favicons files and causing me to lose five years worth of history. I have sqlite3 and I have tried seeking help from many different places, but I'm a neophyte when it comes to command line stuff and a lot of the information I have come across is either impertinent to those specific files, outdated, or has dead links. At this point, I'm willing to give the files to someone more tech savvy than I am so that they can fix them for me if I have to.
Please help me, either through instructions, or through direct repairs. If it's not possible, I can sync with my other devices and import six months worth of largely similar browsing history, but I'd rather it not come to that.
被選擇的解決方法
Nope, but I never had bookmarks. I only tagged the question as such because I was unsure of what else to tag it.
I just learned that what happened to me was the result of a bug that causes Firefox to reject place.sqlite files if the user crossed a certain downgrade threshold, which I did. (Specifically: Bug 1416506). Apparently, the file's "schema" is now too much for Firefox to accept as legitimate, and the occurrence of this bug was too infrequent to make a priority. It was my fault for leaving around an old version of Firefox, as well as for not backing up my history. It's no severe loss to me, though.
從原來的回覆中察看解決方案 👍 0所有回覆 (11)
See if you windows has recorded a system restore point that can be invoked.
It's possible that the restore point will restore your file system to a prior state when the system was functional for you.
Yes, I tried that. It didn't work, unfortunately.
To what Firefox version did you revert ?
Normally recent Firefox version would refuse to downgrade a Firefox profile due to using a dedicated profile and if you reinstall the current release then Firefox would automatically find an reuse the newer profile.
Did Firefox create a places.sqlite.corrupt file ?
I still don't know how the reversion was possible. It seemed like a different Firefox application was installed entirely. I recognized the old icon and layout. I didn't have much if a chance to check the version as I was preoccupied doing something else at the time and the browser was quick to update itself to the latest version when I next launched it.
Yes, I have a places.sqlite.corrupt and a favicon.sqlite.corrupt. Those are the files I'm trying to fix.
It is possible that you switched from the 64-bit version to an older 32-bit version in case the latter was still installed.
- (64-bit Firefox) "C:\Program Files\Mozilla Firefox\"
- (32-bit Firefox) "C:\Program Files (x86)\Mozilla Firefox\"
Yes, you are right. I remember before doing the system restore, I deleted both versions of Firefox from the locations you mentioned hoping that a clean install would fix the problem. I since restored my system to before the data loss and I see now that I still have the 32 bit version of Firefox, and that I last used it in October of 2017. That may have been what the add-on targeted.
Now that I have it here, I can answer your question from earlier. It is version 56.0
Note that a system restore can be quite harmful and may have caused the problem as Windows doesn't tell you what files get replaced and you should always backup important files beforehand. You can possibly try to rename the .corrupt file extension (places.sqlite and favicons.sqlite) to see if that makes Firefox use them.
I know. System Restore was my last resort before turning to help.
I tried renaming already. I also put it through an integrity check. It checked out OK.
You do not have a backup in the bookmarkbackups folder that you can use ?
選擇的解決方法
Nope, but I never had bookmarks. I only tagged the question as such because I was unsure of what else to tag it.
I just learned that what happened to me was the result of a bug that causes Firefox to reject place.sqlite files if the user crossed a certain downgrade threshold, which I did. (Specifically: Bug 1416506). Apparently, the file's "schema" is now too much for Firefox to accept as legitimate, and the occurrence of this bug was too infrequent to make a priority. It was my fault for leaving around an old version of Firefox, as well as for not backing up my history. It's no severe loss to me, though.