Skip to main content

WhatsApp: How to get out of Google Drive backup during restore

Let's say you have accidentally enabled Google Drive backup on your WhatsApp. Now when you want to restore it to a new phone, you find that you have to download 500MB worth of data and wait for an insane amount of time because you don't have fast broadband. What do you do?

I found myself in this situation recently and cracked my head a bit trying to solve it. Thought I'd log this down and save someone else in the same situation a little time.

Firstly, whether or not Google Drive backup is enabled, a local backup file is always created in the SD-card under /WhatsApp/Databases/msgstore.db.crypt8. The full path is typically /storage/emulated/0/WhatsApp/Databases/msgstore.db.crypt8. You have to copy msgstore.db.crypt8 to the the same path on the new smartphone (create the necessary subfolders along the way) before WhatsApp is installed.

The next step delinks WhatsApp from Google Drive so that when you install and run it on the new smartphone, it will not insist on restoring from Google Drive.

From a web browser, login to Google Drive. On the top-right corner, click on the gear icon, then click on "Settings":


 A new popup window will appear.  Select "Manage Apps" on the left.



You should see "WhatsApp Messenger" in the list. Click on "Options, Disconnect from Drive".

You will be given a choice to "Delete hidden app data" in a checkbox. If you leave that unchecked, you can always delete the data later from the "Options" button again.

Once you have disconnected WhatsApp from Google Drive, you can go ahead and install WhatsApp on your new smartphone. When you run it for the first time, it will now search within the local storage for the backup and find msgstore.db.crypt8 if the file is in the right place.

Comments

Popular posts from this blog

Update: Line adapter for Ozito Blade Trimmer

Update (Dec 2021): If you access to a 3D printer, I would now recommend this solution , which makes it super easy to replace the trimmer line. I have been using it for a few months now with zero issue.

Filament Joiner Part 2 (With Display and Knob)

Thanks to the current corona-virus crisis, the parts I ordered for the filament joiner project were taking forever to arrive. But now that they have finally arrived, I can put them to good use. These were the parts ordered: 0.96" OLED display SSD1306 Rotary switch encoder KY-040 Here is the final circuit diagram: The OLED display is connected to the SCK and SDA pins of the Nano (A2 and A3 respectively), and powered by 5V and GND. The rotary switch encoder is connected as follows: VCC => 5V GND = > GND CLK => D9 DT => D8 SW => D2 My prototype board now looks like this: The updated code for driving the knob and display is available in  heater-with-display.ino in the Github repository . We now have a fairly compact (about 7cm x 5cm) and independent filament joiner (no need to connect to PC) that is driven solely by a 12V power supply. Here's how to use it to join printer filaments. More usage details in my previous post .

Adding "Stereo Mixer" to Windows 7 with Conexant sound card

This procedure worked for my laptop (Thinkpad E530) with a Conexant 20671 sound card, but I suspect it will work for other sound cards in the Conexant family. I was playing with CamStudio to do a video capture of a Flash-based cartoon so that I can put it on the WDTV media player and play it on the big screen in the living room for my kids. The video capture worked brilliantly, but to do a sound capture, I needed to do some hacking. Apparently, there was this recording device called "Stereo Mixer" that was pretty standard in the Windows XP days. This allowed you to capture whatever was played to the speaker in all its digital glory. Then under pressure from various organizations on the dark side of the force, Microsoft and soundcard makers starting disabling this wonderful feature from Windows Vista onwards. So after much Googling around, I found out that for most sound cards, the hardware feature is still there, just not enabled on the software side. Unfortunately, to