Whatsapp Restore stuck at 24% , restoration failed / google drive and local back up

Search This thread

iqmyst87

New member
Dec 29, 2019
1
2
Well, i figured that whatsapp has actually completed the restore at 24%. There are just something preventing the apps from loading normally.

What i did was let it load at 24% for about 10 minutes, then i force close the apps and restart the phone.

Once restarted, open back whatsapp, and it will continue with initialising process and once completed, all chats are actually restored. Wasted almost a month to figure this out.
 

Bolt__

New member
Apr 8, 2020
1
0
Solution for Whatsapp restore stuck ar 24% when changing phones

Hi, I apologize in advance for any grammar misaktes.
I had the same issue when changing from an android phone to another, it seemed like the backup file was corrupted. This solution only works if you still have acces to the old phone whatsapp data.
The solution was:
1. Go to whatsapp app settings and erase all data from from the new phone.
2. Go to your google drive >> backups and erase all whatsapp backups.
3. On your old phone make a new backup.
4.Restore the new backup on the new phone.
 

Mighty

Senior Member
Mar 17, 2018
547
252
Well, i figured that whatsapp has actually completed the restore at 24%. There are just something preventing the apps from loading normally.

What i did was let it load at 24% for about 10 minutes, then i force close the apps and restart the phone.

Once restarted, open back whatsapp, and it will continue with initialising process and once completed, all chats are actually restored. Wasted almost a month to figure this out.

Duuuude Thank you sooo much
I also faced the 24% issue when my phone decided it would automatically reset
What I did was rename the decrypt files to msgstore.db.decrypt8 to .decrypt 13 by copy-pasting
Then i let it restore and saw the app data it increased ffirst then decreased
i did it again and when the app data was max i force closed it and re opened whatsapp
BOOM, my chats are back
 

ArturesS

New member
Mar 14, 2017
1
0
You've made it!

My problem has been solved just by uninstalling WA from new phone and deleting WA folder using MyPhoneExplorer. Anyway way you've did a lot of great work and your HowTo end up in my Opera's bookmarks just in case. Respect :)

Hi guys!

I have been facing this issue this whole week while trying to move all my chats to a new phone I just bought as with the old one the charging port was dying and I could not bear it anymore. So almost everything restored smoothly from Google Backup and it was like being in my phone again with a few wizard steps but then I Installed WhatsApp (WA) and gone through the typical activation and restoring process and. as many, I got stuck at the 24% sometimes, some others 31% and 39%, and never got past the 39%.

I Tried almost everything: restoring from Google Drive, transfer all WhatsApp directory to internal storage and trying to restore from there, etc. Going back to the old phone to create fresh backups just in case they were corrupted as many people suggests, getting every time more delay to be able to activate WhatsApp again up to 12h for both SMS and call activation... just to mess again and feel back at square one, I guess you all feel the pain.

Well, the good news is that I finally managed to restore all the chat history!!! (well, cannot be certain that 100% was restored but I do not miss anything ATM and I can go back up to 2012 chats so I guess that qualifies as "everything" hehe).

So, I'm posting here because I've been searching a lot on the forums and the reddit and for all the people that is having this issue recently, almost no body came back to report success and I know it feels really discouraging :( It certainly gives the impression that this issue has no fix at all, and that you should accept losing all the chat history and starting from the start again. But from all the data I've been gathering during this week, at least two or three people reported to eventually being able to restore the chat; they fell in one of these two categories: they either transferred to a different phone where the backup seemed to restore okay, and then exported and restored in the target phone with success (something like a "bridge" restore mode, most of the cases I've read did it this way) or they finally succeeded by sheer brute force by trying again and again and again.

I fall in this 2nd category. In the most recent attempt I was doing what I've been doing again and again and again with just minor variations in the workflow and finally succeeded. TL; DR; I think in reality in many cases attempts could succeed by just letting the phone restore the backup endlessly, by not giving up and assuming the restore process went wrong when it has been stuck forever at either 24, 31 or 39% and force closing..

But I know in the midst of desperation OCD kicks in and you want step-by-step success case scenario reproduction so I will tell you all the steps that I followed that I can remember that got me to finally have the backup to end successfully:

0. First of all, in the winning attempt I had already uninstalled WA from the new phone and removed totally the WA folder in the internal storage / sdcard storage. Not sure this is mandatory but just to tell this was the case.

1. Since I got WA working perfectly on the old phone at every moment, I backed up locally for the Nth f%!?&·( time. This left me with the latest local backup plus a few others in the databases folder as a result of keep messing up.

2. I copied the full WhatsApp directory from the internal storage of the old phone to a safe place. This could be the PC or whatever, but PC transfer via USB seems too sloppy. You maybe could do it via ADB, whatever, I went by the route of coping it to the external SD with some random explorer utility like ES File Explorer. It does not matter, the point is to be able to backup the full WhatsApp folder in order to restore it as similar as possible as the original. What we are more interested right now is in the database folder but having all images, videos etc in place will help in getting it like before the easiest way. (Disclaimer: Ok guys sorry if some steps are too obvious to XDA users which usually are highly educated in the matter, but I was thinking of sharing/linking this text on the reddit and others, so please bear with it).

3. I installed latest WA in the new phone, opened the app (I intended to not open but I somewhat forgot) and got to the welcome screen, immediately closed the app at that step.

3. I restored the full folder to the new phone internal storage, pure copy/paste style (as said, in my case via the SD since both phones have SD slot and was very convenient, but via USB, cloud, etc. can be done).

4. I went to the databases folder and only kept the msgstore.db.crypt12 file and the latest backup with a date (ie: msgstore-2019-11-21.db.crypt12), deleted the rest. Honestly I do not think this is crucial but I somewhat wanted to make it easier for WA to know which one to target, I thought about keeping only the msgstore.db.crypt12 but some random dude pointed that the one with the date was needed. I was under the assumption that file structure is identical in both but just wanted to get done with this and keep both, just in case.

5. Before opening again the WA to try to activate and restore with this full local copy, I opened the Android settings app and went to applications > whatasapp > storage, as suggested by user redweaver, thanks for the tip! by keeping looking at the storage usage of the app during the restore process we could get insight about if it was really doing something or the app was really stuck. Keep open for now. In my case, I saw also on the old phone that my data used for the app was 780+ MB, so I had an idea of what should be on the new phone by the time it finished (if it did!).

5b. I don't think this is really necessary but I did it just in case. I was planning to go to work and let the thing running as long as it would need, and I would make sure that the process would get maximum uptime and nothing would get in the way. So I went to Applications > WhatsApp > Battery usage (or something like it) and disabled the battery optimizations for this app. I also went to the developer mode settings and enabled do not lock the phone while it is charging and everything that looked like it might be relevant. Again, most likely this has nothing to do, but reproducible steps, right? :)

6. Now open WA and activate it as usual, but when it seems that the activation step ended and you go to the next screen, immediately put the phone in air plane mode or disable data/WiFi, whatever. The goal is that it cannot reach Google Drive to look for the online backup. Honestly maybe in the end is not the culprit of GDrive but many people states that the GD backup is broken at this time and suggests going the local route, so we will do it like this.

7. WA should tell you that looking for the backup is going too slow and to skip this step (sorry to not have exact message, I have it in Spanish, but something in these lines, BTW excuse my somewhat limited English :D). The point here is to click on the link that says skip the step and when you are prompted with a popup, click also on Skip.

8. WA will display the typical restore / transfer-like screen where the process starts. At this point you have to enable again data plan / WiFi at least or exit air plane mode, don't know really but even if restoring from local it complains about not having internet connection, maybe needs it to encrypt with the key or something? don't know.

9. Now is the feared moment! Even this time, I got somewhat stuck at 31% again. I left it do its thing, and some time later, it prompted for the popup that has a progress-bar from 0 to 100 (honestly, what is the difference between both?!) which also got stuck at 31%. If you let it be, it starts going back and forth many times, I guess maybe its going chat per chat and the progress-bar represents each one? Dunno. Thing is, even in the prior attempts I got at this point and the backup did not finish successfully. But this time I was decided to let it do its thing as much time as it would take, until the end. In the process the phone might display a pop up saying that WA does not respond. I clicked a few times in the 'keep waiting' option, then I just forgot because I did not have time to mess with it and hoped that it was still working on the background, which bring us to step 10.

10. While we are contemplating the backup process, we can go to the settings app again and look how the internal data is going for the WA. In my case, after some time under the restore process, when I went there I saw WA had occupied 0.91 GB of data space. After going back and forth again between WA and settings, the usage keep growing: 0.96, 1.03, 1.10... I thought it was on the right track, and encouraged me to keep waiting. Maybe in the end the process is too slow for old databases. Note that some people speculates that having messages from very long ago might be the culprit here due to changes in the table structure and that this might be the reason breaking the restore process. And maybe it is the case, but even if it is, in my case I finally succeeded where previously I didn't and without deleting anything, so this does not seem to be a deal-breaker or I would have never succeeded. I say it because some people reported that deleting old conversations and trying again finally made them succeed. Now I suspect the true reason was simply that by making the database smaller the process finished earlier, but YMMV.

11. Cannot be totally sure, but in my case, I noticed that leaving WA on the background and clicking on the WA icon again might stop the process for true and bring a message about not being able to recover the chats, I got this previously, do not try to open the WA normally, only leave it temporally to look to the space usage in the settings to get back to it by swyping between recent apps to keep the same instance open and working, this was a key point in my success trial that did not happen during the previous ones.

12. And finally, while I kept switching between WA and the settings and when I last saw like 1.30GB of space used (almost twice the space compared to the old phone, maybe it leaves a lot of temp data) I don't know if I either messed with the app-switching or it really finished, but then I got prompted to the screen where you enter your name or nickname. And when I completed this step, I finally got to the chats screen and everything was like in the old phone! Where previously I would get to a lot of empty chat rooms with maybe 40 total messages restored according to WA. Hurray!

Notice that in my case it was still reporting 31% on the WA background screen under the progress bar popup when it finished!! so it seems that is not really mandatory to experience the 100% complete to have it work in the end, but YMMV.

OK, maybe not the most elegant "guide" out there but I wrote it in a hurry and my english sucks, I just hope it might help someone to not lose their WA chats forever.

Good luck!

Edit: I almost forgot but, for the sake of completeness. I also tried a certain script that can backup WA from the phone and retrieve the encryption key, it will also leave an unencrypted copy of the chats database that can later be viewed with a WhatsApp viewer like this. The script is called WhatsApp Key/DB Extractor, and it still works as of 2019, just look at the latest posts in the thread. Guys here on XDA most likely know about it but if not, you might give it a try. I tried it because I assumed that maybe I could circumvent the restore issues by going that route and pushing the backup via ADB, but turns out the legacy WA won't prepare the database due to the time out of sync issue, or at least the data seemed to be lost after performing the restore process, and the unencrypted database on the PC cannot be digested by WA latest versions by just putting it into the internal storage directly according to what other users commented. But, if you finally give up trying the restore process, it still could be relieving to know that you keep a local copy in the PC that can be viewed with another PC tool, at least you get a backup and the conversations are there, in a different way though. Maybe in the future there's a process that can restore them again to a different phone, and you could then merge the new chat database with the older backup with tools like Merjeapp.
 

jdip

Senior Member
Jun 10, 2013
69
7
Duuuude Thank you sooo much
I also faced the 24% issue when my phone decided it would automatically reset
What I did was rename the decrypt files to msgstore.db.decrypt8 to .decrypt 13 by copy-pasting
Then i let it restore and saw the app data it increased ffirst then decreased
i did it again and when the app data was max i force closed it and re opened whatsapp
BOOM, my chats are back

How come you changed the file type version to decrypt13? Do you leave it as 13 when you restore? Does that work?
 

Cursed Chico

Senior Member
Jul 9, 2011
432
5
Istanbul
I haveproblem at %31 too.
I disable wifi, skip drive backup restoration and make it to read from local. It says "restoring messages" and at %31 , it stops. Somtimes at%24. There is only crypt file. Please help me to fix.
 
Last edited:

Cursed Chico

Senior Member
Jul 9, 2011
432
5
Istanbul
Well, i figured that whatsapp has actually completed the restore at 24%. There are just something preventing the apps from loading normally.

What i did was let it load at 24% for about 10 minutes, then i force close the apps and restart the phone.

Once restarted, open back whatsapp, and it will continue with initialising process and once completed, all chats are actually restored. Wasted almost a month to figure this out.

Hello.

%24 it says it cant go further. When i force stop, i see in settings, data goes to 70 mb from 3.9 gb. When i restart after force close, it brings the screen to enter my username. should i go on like this?

---------- Post added at 07:59 AM ---------- Previous post was at 07:58 AM ----------

Hi, I apologize in advance for any grammar misaktes.
I had the same issue when changing from an android phone to another, it seemed like the backup file was corrupted. This solution only works if you still have acces to the old phone whatsapp data.
The solution was:
1. Go to whatsapp app settings and erase all data from from the new phone.
2. Go to your google drive >> backups and erase all whatsapp backups.
3. On your old phone make a new backup.
4.Restore the new backup on the new phone.

Hello,

My old phone's wifi is disabled. So i get again local backup and moved to my new phone. But still it stuck at %24. Are you sure?
 

Cursed Chico

Senior Member
Jul 9, 2011
432
5
Istanbul
I fixed. I tried for days. Every time I requested a new verification code, the time I had to wait increased every time. Last time, it was 49 hours. Luckily, I fixed and did not wait so much.

I tried lots of time but i will tell what i did for latest try.

Firstly, I deleted drive backup. I did not disable sycn or google accounts.

I had 2 local backups. Deleted one.

And maybe those are important: I gave all permissions from settings to whatsapp. I gave also autostart permission and I gave no battery restriction.

Sim card is on different phone. This is not important i think.


I started to restore. It restored local backup. When it came to %24, i was worried. So, I switched to screens once a second, to settings screen.

Normally it was showing 3.9 gb at first. But when it reached %24, it was 3.18 gb when I was switching to settings screen, i saw it. And 2.5 millions messages are restored and it is 3.18 gb.

I waited it to be 3.9 gb when it was at %24. So that is why i was switching to check but it did not stuck this time. Maybe because i was switching.

Maybe because i removed from drive. This was the first time i tried after removing from drive.

So, switching a lot of times between settings of whatsapp and restoring screen, showed succesfull screen at last. IT said "restored 2.5 millions messaged"

I was shocked. I went to check. 5 days ago, i wrote last message and that 5 days messages also came.

If it was stuck again, i would force stop and continue without waiting restore. I read it from somewhere. But i fixed, i am happy :)
 

Santosh India

New member
Feb 4, 2021
1
0
Hi All,

I have a easy yet not a complete solution for this.

To explain this , let me put my case so that you can correlate with yours !

In October 2020 one fine day suddenly while i was texting, my whatsapp crashed and only i can see is all new whatsapp in my mobile ( i deleted all the latest local back ups in August as my phone has less storage space and later no back up took place as no space to get a back up :( ) and i couldnt restore any latest from local storage.

I tried to restre from google drive ( latest available was Sep 11, 2020 . As my google drive also was full it never took back up to google drive) .

I tried restoring the Sep 2020 backup from drive but it never happend in my phone as it has no storage space and the back up if of 16GB ( yes !! huge as i ve been using whatsapp since 2012 and part of 50 + groups and i hardly clean it up yuck !!))

So i have no option except to use the fresh whatsapp..:( :( . In Jan 2021, i bought a new samsung galaxy phone and wanted to try restoring back up from drive . I tried tens of times till today but it struck at 24% and i rele dint want to loose my earlier data. I kept on trying and reading multiple articles but all in vain.

Finally what i did was -> uninstalled whatsapp includeing the system memory etc.. -> reinstalled whatsapp -> selected to restore the google drive data of Sep 2020 -> Dwnloaded 100% ( took 30 mins appx) -> Restoring started and at 24% it was not progressing after that as usual. Here since the back up is dwnloaded earlier, switchoff the WIFI and Mobile data and that helps to restore in just 10 seconds. Later the media back up restoration follows when you connect to WIFI

Thank me if any one used this and it worked !
 

boeder9

Senior Member
Dec 19, 2011
145
20
Hi guys!

I have been facing this issue this whole week while trying to move all my chats to a new phone I just bought as with the old one the charging port was dying and I could not bear it anymore. So almost everything restored smoothly from Google Backup and it was like being in my phone again with a few wizard steps but then I Installed WhatsApp (WA) and gone through the typical activation and restoring process and. as many, I got stuck at the 24% sometimes, some others 31% and 39%, and never got past the 39%.

I Tried almost everything: restoring from Google Drive, transfer all WhatsApp directory to internal storage and trying to restore from there, etc. Going back to the old phone to create fresh backups just in case they were corrupted as many people suggests, getting every time more delay to be able to activate WhatsApp again up to 12h for both SMS and call activation... just to mess again and feel back at square one, I guess you all feel the pain.

Well, the good news is that I finally managed to restore all the chat history!!! (well, cannot be certain that 100% was restored but I do not miss anything ATM and I can go back up to 2012 chats so I guess that qualifies as "everything" hehe).

So, I'm posting here because I've been searching a lot on the forums and the reddit and for all the people that is having this issue recently, almost no body came back to report success and I know it feels really discouraging :( It certainly gives the impression that this issue has no fix at all, and that you should accept losing all the chat history and starting from the start again. But from all the data I've been gathering during this week, at least two or three people reported to eventually being able to restore the chat; they fell in one of these two categories: they either transferred to a different phone where the backup seemed to restore okay, and then exported and restored in the target phone with success (something like a "bridge" restore mode, most of the cases I've read did it this way) or they finally succeeded by sheer brute force by trying again and again and again.

I fall in this 2nd category. In the most recent attempt I was doing what I've been doing again and again and again with just minor variations in the workflow and finally succeeded. TL; DR; I think in reality in many cases attempts could succeed by just letting the phone restore the backup endlessly, by not giving up and assuming the restore process went wrong when it has been stuck forever at either 24, 31 or 39% and force closing..

But I know in the midst of desperation OCD kicks in and you want step-by-step success case scenario reproduction so I will tell you all the steps that I followed that I can remember that got me to finally have the backup to end successfully:

0. First of all, in the winning attempt I had already uninstalled WA from the new phone and removed totally the WA folder in the internal storage / sdcard storage. Not sure this is mandatory but just to tell this was the case.

1. Since I got WA working perfectly on the old phone at every moment, I backed up locally for the Nth f%!?&·( time. This left me with the latest local backup plus a few others in the databases folder as a result of keep messing up.

2. I copied the full WhatsApp directory from the internal storage of the old phone to a safe place. This could be the PC or whatever, but PC transfer via USB seems too sloppy. You maybe could do it via ADB, whatever, I went by the route of coping it to the external SD with some random explorer utility like ES File Explorer. It does not matter, the point is to be able to backup the full WhatsApp folder in order to restore it as similar as possible as the original. What we are more interested right now is in the database folder but having all images, videos etc in place will help in getting it like before the easiest way. (Disclaimer: Ok guys sorry if some steps are too obvious to XDA users which usually are highly educated in the matter, but I was thinking of sharing/linking this text on the reddit and others, so please bear with it).

3. I installed latest WA in the new phone, opened the app (I intended to not open but I somewhat forgot) and got to the welcome screen, immediately closed the app at that step.

3. I restored the full folder to the new phone internal storage, pure copy/paste style (as said, in my case via the SD since both phones have SD slot and was very convenient, but via USB, cloud, etc. can be done).

4. I went to the databases folder and only kept the msgstore.db.crypt12 file and the latest backup with a date (ie: msgstore-2019-11-21.db.crypt12), deleted the rest. Honestly I do not think this is crucial but I somewhat wanted to make it easier for WA to know which one to target, I thought about keeping only the msgstore.db.crypt12 but some random dude pointed that the one with the date was needed. I was under the assumption that file structure is identical in both but just wanted to get done with this and keep both, just in case.

5. Before opening again the WA to try to activate and restore with this full local copy, I opened the Android settings app and went to applications > whatasapp > storage, as suggested by user redweaver, thanks for the tip! by keeping looking at the storage usage of the app during the restore process we could get insight about if it was really doing something or the app was really stuck. Keep open for now. In my case, I saw also on the old phone that my data used for the app was 780+ MB, so I had an idea of what should be on the new phone by the time it finished (if it did!).

5b. I don't think this is really necessary but I did it just in case. I was planning to go to work and let the thing running as long as it would need, and I would make sure that the process would get maximum uptime and nothing would get in the way. So I went to Applications > WhatsApp > Battery usage (or something like it) and disabled the battery optimizations for this app. I also went to the developer mode settings and enabled do not lock the phone while it is charging and everything that looked like it might be relevant. Again, most likely this has nothing to do, but reproducible steps, right? :)

6. Now open WA and activate it as usual, but when it seems that the activation step ended and you go to the next screen, immediately put the phone in air plane mode or disable data/WiFi, whatever. The goal is that it cannot reach Google Drive to look for the online backup. Honestly maybe in the end is not the culprit of GDrive but many people states that the GD backup is broken at this time and suggests going the local route, so we will do it like this.

7. WA should tell you that looking for the backup is going too slow and to skip this step (sorry to not have exact message, I have it in Spanish, but something in these lines, BTW excuse my somewhat limited English :D). The point here is to click on the link that says skip the step and when you are prompted with a popup, click also on Skip.

8. WA will display the typical restore / transfer-like screen where the process starts. At this point you have to enable again data plan / WiFi at least or exit air plane mode, don't know really but even if restoring from local it complains about not having internet connection, maybe needs it to encrypt with the key or something? don't know.

9. Now is the feared moment! Even this time, I got somewhat stuck at 31% again. I left it do its thing, and some time later, it prompted for the popup that has a progress-bar from 0 to 100 (honestly, what is the difference between both?!) which also got stuck at 31%. If you let it be, it starts going back and forth many times, I guess maybe its going chat per chat and the progress-bar represents each one? Dunno. Thing is, even in the prior attempts I got at this point and the backup did not finish successfully. But this time I was decided to let it do its thing as much time as it would take, until the end. In the process the phone might display a pop up saying that WA does not respond. I clicked a few times in the 'keep waiting' option, then I just forgot because I did not have time to mess with it and hoped that it was still working on the background, which bring us to step 10.

10. While we are contemplating the backup process, we can go to the settings app again and look how the internal data is going for the WA. In my case, after some time under the restore process, when I went there I saw WA had occupied 0.91 GB of data space. After going back and forth again between WA and settings, the usage keep growing: 0.96, 1.03, 1.10... I thought it was on the right track, and encouraged me to keep waiting. Maybe in the end the process is too slow for old databases. Note that some people speculates that having messages from very long ago might be the culprit here due to changes in the table structure and that this might be the reason breaking the restore process. And maybe it is the case, but even if it is, in my case I finally succeeded where previously I didn't and without deleting anything, so this does not seem to be a deal-breaker or I would have never succeeded. I say it because some people reported that deleting old conversations and trying again finally made them succeed. Now I suspect the true reason was simply that by making the database smaller the process finished earlier, but YMMV.

11. Cannot be totally sure, but in my case, I noticed that leaving WA on the background and clicking on the WA icon again might stop the process for true and bring a message about not being able to recover the chats, I got this previously, do not try to open the WA normally, only leave it temporally to look to the space usage in the settings to get back to it by swyping between recent apps to keep the same instance open and working, this was a key point in my success trial that did not happen during the previous ones.

12. And finally, while I kept switching between WA and the settings and when I last saw like 1.30GB of space used (almost twice the space compared to the old phone, maybe it leaves a lot of temp data) I don't know if I either messed with the app-switching or it really finished, but then I got prompted to the screen where you enter your name or nickname. And when I completed this step, I finally got to the chats screen and everything was like in the old phone! Where previously I would get to a lot of empty chat rooms with maybe 40 total messages restored according to WA. Hurray!

Notice that in my case it was still reporting 31% on the WA background screen under the progress bar popup when it finished!! so it seems that is not really mandatory to experience the 100% complete to have it work in the end, but YMMV.

OK, maybe not the most elegant "guide" out there but I wrote it in a hurry and my english sucks, I just hope it might help someone to not lose their WA chats forever.

Good luck!

Edit: I almost forgot but, for the sake of completeness. I also tried a certain script that can backup WA from the phone and retrieve the encryption key, it will also leave an unencrypted copy of the chats database that can later be viewed with a WhatsApp viewer like this. The script is called WhatsApp Key/DB Extractor, and it still works as of 2019, just look at the latest posts in the thread. Guys here on XDA most likely know about it but if not, you might give it a try. I tried it because I assumed that maybe I could circumvent the restore issues by going that route and pushing the backup via ADB, but turns out the legacy WA won't prepare the database due to the time out of sync issue, or at least the data seemed to be lost after performing the restore process, and the unencrypted database on the PC cannot be digested by WA latest versions by just putting it into the internal storage directly according to what other users commented. But, if you finally give up trying the restore process, it still could be relieving to know that you keep a local copy in the PC that can be viewed with another PC tool, at least you get a backup and the conversations are there, in a different way though. Maybe in the future there's a process that can restore them again to a different phone, and you could then merge the new chat database with the older backup with tools like Merjeapp.
Bless you. You saved my chats! This worked for me!
 

elthazor

New member
Dec 9, 2012
1
0
i've read and tried some of the trick and still stuck at 24%, i tried to force close and got luckily progress to 100% but for 4 hours didn't complete and still confuse for 3 days how to restore my 2GB db.cypt12 files to other device.

any other sollutions ?
 

4thflicks

Member
Dec 5, 2013
22
1
Hi, I got to step 9 and it got stuck at 31% as prev but now its asking to either skip or restore from older backup? The storage went up to 1.3gb at one point but is now back to 58mb. Do I skip or restore from older or just leave it idle until it prompts with something else
how are you,any progress on this?
I'm facing the same problem and turns out every chats still missing. Rolling back from scratch and gonna sent a report. Waiting for 14 hours verification for now.
--
so it's done. Here's how :
  1. uninstall WA,reinstall,give all permissions and no batery restriction.
  2. Delete gdrive backup,don't forget to give your local bakup a date. So it's not only "msgstore.db"
  3. Relogin to WA,immediately turn off data & wi-fi when it's looking for online backup.
  4. when it's prompted to skip,skip. It will starting to restore from local.
  5. turn on mobile data or wi-fi.
  6. it's better if you can set a "caffeine" or no sleep option so your phone keep awake.
  7. In my case,it seems to be paused at 24%, switch between WA-it's storage usage in app info and stay sharp of it, it gonna up and down. The progress are sometimes rolled back several times.
  8. occasionally, it will be finished. It should not take long, for me only left it a while for taking a dump. And when I'm finished, voila, it showed 255.897 million chat restored.
  9. a little sad only chat and it's media, your stickers seems not gonna restored too. But for what it's worth I'm only lost 5 days chats.
  10. then you can give permission to your gdrive again so you can upload it.
 
Last edited:

Onimusha999

Member
Sep 13, 2010
17
1
Hello everyone,

I just want share my experience in this issue like other people and hope it will help other user, as till now there is no direct solution for this, even if ask whatsapp support they will give you answer machine to reply same word that not help at all.

First i want say that i try all solution in this topic without any success.

I even try to restore my android whats app backup to iPhone but not working, this related to different encryption type maybe.

I try to restore it in another android phobe.

Try to restore it with other phone number.

I try to restore backup in WhatsApp business.

All my try led to fail.

And unfortunately every time the restore process start and stuck i receive some new message but that i cant see it till the end whatsapp open with group only and no message, then start again from the beginning, so 3 days i am without whatsapp.

After so many try, WhatsApp didn't send me the activation code, whether sms or call, keep me waiting 2 hours, 16 hours, then 36 hours.

Anyway after let me wait for 36 hours i try again to restore but this time:
1- Move data tolder to another location in the phone and keep only database folder that include backup file.
2- Keep my eyes to the storage of whatsapp during restored process then when it reach 31% the storage stop increasing so i forced close the whatsapp and restart my phones.
3- When my phone start again i make it airplane mode and open whatsapp to finde all my chatting restore.
4- After returning the media folder to whatsapp folder i get crash again after some time and do same step to recover again, but this time i didn't return media folder to whatsapp folder, maybe its the reason for the crash, now 1 days and everything looks fine.

There is something wrong in the app make this issue and its not related to corruption of backup file, no, its related to restoring processes as no need to reach 100%, as all my chatting restore at 31% when i force close the app.

Mybe this point it will help to solve the issue for others user in the future.
 
Last edited:

Dutch078

New member
Nov 5, 2021
1
1
Hi Everyone,

After several try outs, I finally succeeded to restore my local backup of Whatsapp. I also discovered and tested some tricks to find out what really works. I hope this information will help you to solve the 24, 31, 35 or 100% backup restore stuck problems of Whatsapp efficiently.

Before starting the whole process: On several websites is given the advice to delete all your Google accounts on your new phone and to delete all your WhatsApp backups made with Google Drive. In my case I did NOT. Probably, this had no important effect on restoring of my local backup of 1,9 GB with Whatsapp.

During the whole process it’s also important that your new phone is always in the active mode. Therefore, in the Settings of your new phone you have to disable the sleeping mode. Your battery should also be charged to 100%. With an adapter your phone could also be connected to an electrical wall socket.

To restore my local backup successfully, my steps were:
  1. I deleted my Google Drive backup on the internet with my personal computer. Then I made a new local backup and a new backup with Google Drive with my old HTC Desire C phone of all my chats, documents, images, video’s and other media, etc. without deleting anything.
  2. On my (new) Samsung Galaxy A5 phone I deleted all the Whatsapp folders and files.
  3. With Play Store I installed the most recent available version of Whatsapp (= 2.21.20.20) on my new phone and opened it only a few seconds. Without pressing on the button Agree & Continue in the Welcome screen of WhatsApp, I closed Whatsapp immediately.
  4. With a USB-connection I copied the whole Whatsapp folder of my old phone to my personal computer. Additionally, I copied the same Whatsapp folder of my personal computer to the internal storage of my new phone. This second step took about 45 minutes.
  5. With a File Manager on my new phone I went to the map WhatsApp/Databases and kept only the 2 most recent local backups. These files were: msgstore.db.crypt12 and msgstore.2021-10-18.1.db.crypt12. All other (backup) files in the folder Databases were deleted.
  6. Via Settings and Apps on my new phone, I went to the app(lication) of WhatsApp and opened the screen App-info of Whatsapp. Being there, I opened the Storage display of WhatsApp. It’s important to monitor the data shown in this display. By frequently sweeping to the Restoring screen and sweeping back to the Storage screen you could monitor what is happening during the restoring process. Earlier, I had noticed, that immediately after the start of restoring my backups the amount of MB’s was quickly increasing and decreasing several times. Without any new actions WhatsApp resulted in a very low amount of MB’s (in my case about 14,75 MB) and an endless during restoring process.
  7. With this new insight, I started (again) to activate Whatsapp on my new phone. After entering my phone number, activation code and confirming the 2 questions of WhatsApp about using my contacts, documents, media, etc., Whatsapp started to search for backups. Sometimes Whatsapp started with my Google Drive backup. But most times with my local backup. It did not matter, as I found out that I could interrupt this process with step 12.
  8. As Whatsapp found my local backup for the first time, I confirmed, that I wanted to restore this local backup. By frequently sweeping to the Restoring and the Storage screen, I discovered what the maximum peak of MB’s of my local backup was, before Whatsapp was decreasing this amount of MB’s. In my case my peak was nearly about 312 MB’s. But on my old HTC phone the amount of data in the internal storage of WhatsApp was only 215 MB’s. It’s an indication that WhatsApp tried to read my (local) backups. The extra temporary MB’s on my new phone were probably necessary to process the whole (local) backup.
  9. After reaching it’s lowest point of MB’s and without reaching the 100% restoring level (= it stopped restoring my messages at 24, 31 or 35%), Whatsapp was showing the message: “Sorry, your backup can not be restored. Would you like to restore another backup?”
  10. After pressing on the buttons “Yes” and “Restore”, WhatsApp started to restore the next backup.
  11. As WhatsApp tried to restore my Google Drive backup, I saw it succeeded to download it. In my case this was 41 MB’s. That’s the same amount of MB’s, that was uploaded with my old phone to Google Drive. But Whatsapp did not succeed to get my Google Drive backup into the internal storage. Finally, this process was endless going on without showing how much % of the messages were restored.
  12. After reaching the endless restoring stage, I interrupted this process in the Storage and Data screen of Whatsapp by pressing on the button “Manage storage”. You could repeat this step every time when you reached the endless restoring process. Please, do not do this in an earlier stage. Otherwise WhatsApp could finish the whole process.
  13. Avoid also pressing on the pop-up of Whatsapp telling you that the Whatsapp App will start again. Too often pressing on that button could also finish the whole process and then you have to start all over again with a new activation code. Instead, just change your screen by sweeping to the Restoring screen.
  14. As a result of step 12: Whatsapp will ask in the Restoring screen to agree to restore another backup. Before confirming that choice, it’s important to clear the cache in the Whatsapp App-info display.
  15. In my case Whatsapp also tried to restore a backup that Whatsapp had never found. Despite this curious message WhatsApp started directly at 24% and continued to 35% and 100% restored messages. But without any result Whatsapp also stopped restoring the never found backup by asking me again to restore another backup.
  16. Now again Whatsapp showed me the information of my local backup (including the time that it was made). After first cleaning the cache in the Whatsapp App-info display again, I confirmed that I wanted to restore this local backup. But now something different happened. In this step Whatsapp started from the beginning directly showing me that 100% of my messages were restored. So everything was there, but Whatsapp could not transform it into it’s own (storage) system. Without any new actions this would also result in an endless restoring process.
  17. Finally, my solution was: “After the start of restoring my local backup, just a few seconds before Whatsapp will reach it’s highest peak of MB’s (= in my case nearly 312 MB’s) shown in the WhatsApp Storage screen, I quickly went to the WhatsApp App Info screen and pressed on the button “Force Stop” (= in my case when the amounts of MB’s were in between 280 to 312). In the following pop-up, I confirmed that choice immediately.
  18. Next I went quickly to the Restoring screen. There was WhatsApp showing me the screen where you have to fill in your (WhatsApp) name.
  19. After typing and confirming my name, WhatsApp started the initializing process. After a few exciting moments Whatsapp showed me all my chats, media, etc..
  20. After checking everything, I found out that all my chats, documents, images, video’s and other media, etc. were 100% complete. Nothing was changed, lost, damaged or corrupted.
 
  • Like
Reactions: aIecxs

edappere

Member
Apr 10, 2020
29
11
how are you,any progress on this?
I'm facing the same problem and turns out every chats still missing. Rolling back from scratch and gonna sent a report. Waiting for 14 hours verification for now.
--
so it's done. Here's how :
  1. uninstall WA,reinstall,give all permissions and no batery restriction.
  2. Delete gdrive backup,don't forget to give your local bakup a date. So it's not only "msgstore.db"
  3. Relogin to WA,immediately turn off data & wi-fi when it's looking for online backup.
  4. when it's prompted to skip,skip. It will starting to restore from local.
  5. turn on mobile data or wi-fi.
  6. it's better if you can set a "caffeine" or no sleep option so your phone keep awake.
  7. In my case,it seems to be paused at 24%, switch between WA-it's storage usage in app info and stay sharp of it, it gonna up and down. The progress are sometimes rolled back several times.
  8. occasionally, it will be finished. It should not take long, for me only left it a while for taking a dump. And when I'm finished, voila, it showed 255.897 million chat restored.
  9. a little sad only chat and it's media, your stickers seems not gonna restored too. But for what it's worth I'm only lost 5 days chats.
  10. then you can give permission to your gdrive again so you can upload it.
To anyone interested, I've (almost) followed these steps which are accurate (as of may 2022). The main thing to me seems to be step 2 : you have to only have one file in the Databases directory and it must be named something like "msgstore-YYYY-MM-DD.db.crypt14" (or crypt12, crypt6, etc.). Restore process does not work if you only have "msgstore.db.crypt14" or if you have "msgstore.db.crypt14" + some dated databases ("msgstore-YYYY-MM-DD.db.crypt14") in the Databases directory

The annoying thing now : although I've restored all my old chats, all recent messages (received between the last time I accessed Whatsapp and the time I restored the backup) were lost...
 

kn0tx

New member
May 15, 2022
2
0
It works, all my chats and media can be recover this way. But occasionally now my whatsapp will out of sudden crash. Not sure if I force stop as it stucked at 24 during restoration that causes it "incomplete" or how.

The weirdest thing is when I tried to delete certain chats, my whatsapp will crash too.

Or when I use whatsapp web to sync and delete my chats, my whatsapp will crash too.

Anyone share the same issue with me after manage to restore using method above?
 

Speedbird2652

Member
Jun 11, 2020
5
0
The described methods here worked okay-ish last time (about mid-end june, 3 weeks ago today) and I only had to try 2 or 3 different dbcrypt-files I had, also it only took like 8 hours for the process to succeed.
Now, I ended up with what seems like 7 recent but all broken backups, and trying to restore one of the mid-June ones (which worked back then!) doesn't seem to work now.
The process starts as described, following the instructions step by step, but instead of the error message that WhatsApp is not responding, the "Sorry mate, unable to restore any of your messages, sucks I know" message pops up. Then when I enter my name and log in, a few messages come up, but a lot, namely all the most recent ones, are missing.

Now what was different than last time? file size in the storage & cache screen never went as high up as it did mid-June. Max I was seeing now was about 4GB, back then it was almost 10. The timestamp on the dbcrypt-files seems odd, too, it's at 17:00 for all but one files, usually the files are dated to 2AM. Does WhatsApp have issues with restoring month-old backups maybe?
 

Albert83BCN

Member
Nov 19, 2019
7
7
The described methods here worked okay-ish last time (about mid-end june, 3 weeks ago today) and I only had to try 2 or 3 different dbcrypt-files I had, also it only took like 8 hours for the process to succeed.
Now, I ended up with what seems like 7 recent but all broken backups, and trying to restore one of the mid-June ones (which worked back then!) doesn't seem to work now.
The process starts as described, following the instructions step by step, but instead of the error message that WhatsApp is not responding, the "Sorry mate, unable to restore any of your messages, sucks I know" message pops up. Then when I enter my name and log in, a few messages come up, but a lot, namely all the most recent ones, are missing.

Now what was different than last time? file size in the storage & cache screen never went as high up as it did mid-June. Max I was seeing now was about 4GB, back then it was almost 10. The timestamp on the dbcrypt-files seems odd, too, it's at 17:00 for all but one files, usually the files are dated to 2AM. Does WhatsApp have issues with restoring month-old backups maybe?

Yep, I have been having problems with my chat history since looong ago, seems that something must be corrupted because every day at 2AM when it performed the local backup always crashed. So I ended up with the habit of powering down the device before 2AM so that it would not crash every day.

But from time to time I would forget to power down, and also being too much time without performing the backup is also call for trouble in case something goes wrong again, so from time to time I would let it do the backup and then crash, because I learned that at that point when I was prompted to restore a backup I could always succeed by clicking OK, let it do it's work with the latest msgstore.db.crypt14 file in the Databases folder and when the WhatsApp internal storage reached a certain amount of data I knew it was ok (1.03 GB in my case), force close the app and the chats would be magically there, all of them that I can tell, back to 2011 (I posted about this in this thread or some similar back in 2019 and also many other people confirmed this).

However since early July I just cannot do this anymore. Now it seems as there is an additional 'preparing data' step (in the "post-activation" state of the app, more on this later) where it checks for integrity or something, and I would never succeed with the force-close method again. I also noticed that the storage used during the restore goes beyond what I used to see before. I don't have a clue about how the WA works internally but to me it seems as if previously this worked because chats where actually restored during the 0-24% portion of the process, and from 24%-31% and/or beyond it was about the references to media, and the two processes were somehow separated and force-closing during the 24% allowed to get up and running again, but now it wants it to complete all the process or otherwise it rolls back (?). It's either this, or my backup just got even more corrupted than before, I don't really know.

The other thing that I noticed (fortunately?) is that if you try the force-close method during the "pre-activation" step, it can still work and you end up with the chats restored... but in that case the app will only run OK for as long I have it in memory. As soon as it closes and the process restarts, does this kind of check again and the chat gets corrupted again... the problem here is that activating every day is not possible as you know because of the cumulative delays that WhatsApp imposes in each attempt... I have been trying to get it to work for a few days days now without success (even trying to restore the unencrypted msgstore.db in an Android VM to see if I can extract a "clean" backup again, without success) and now I have to wait for 36h to activate again and I do not have much hope that I will be able to come up with a solution this time.

Guys, a lot of people has trouble with restoring their/our chat history as you all know first hand, we need to keep this updated or come with a megathread or something, with whatever procedures that any of us find that might still work post July 2022.
 
Last edited:

Speedbird2652

Member
Jun 11, 2020
5
0
I can sort of confirm the "magically appear" part...when restoring a mid-June dbcrypt-file, it somehow found a working Google Drive backup without me doing anything besides the mentioned steps here, and I ended up with all my chats intact up until early July!?
 

Its Pa1

New member
Aug 6, 2022
1
0
Any one please help me im also getting this error
Stucking at 24% i tried all above
Nothing works out
It is very important life and death matter
Pls I urge you every one please help me
Pls
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Hi guys!

    I have been facing this issue this whole week while trying to move all my chats to a new phone I just bought as with the old one the charging port was dying and I could not bear it anymore. So almost everything restored smoothly from Google Backup and it was like being in my phone again with a few wizard steps but then I Installed WhatsApp (WA) and gone through the typical activation and restoring process and. as many, I got stuck at the 24% sometimes, some others 31% and 39%, and never got past the 39%.

    I Tried almost everything: restoring from Google Drive, transfer all WhatsApp directory to internal storage and trying to restore from there, etc. Going back to the old phone to create fresh backups just in case they were corrupted as many people suggests, getting every time more delay to be able to activate WhatsApp again up to 12h for both SMS and call activation... just to mess again and feel back at square one, I guess you all feel the pain.

    Well, the good news is that I finally managed to restore all the chat history!!! (well, cannot be certain that 100% was restored but I do not miss anything ATM and I can go back up to 2012 chats so I guess that qualifies as "everything" hehe).

    So, I'm posting here because I've been searching a lot on the forums and the reddit and for all the people that is having this issue recently, almost no body came back to report success and I know it feels really discouraging :( It certainly gives the impression that this issue has no fix at all, and that you should accept losing all the chat history and starting from the start again. But from all the data I've been gathering during this week, at least two or three people reported to eventually being able to restore the chat; they fell in one of these two categories: they either transferred to a different phone where the backup seemed to restore okay, and then exported and restored in the target phone with success (something like a "bridge" restore mode, most of the cases I've read did it this way) or they finally succeeded by sheer brute force by trying again and again and again.

    I fall in this 2nd category. In the most recent attempt I was doing what I've been doing again and again and again with just minor variations in the workflow and finally succeeded. TL; DR; I think in reality in many cases attempts could succeed by just letting the phone restore the backup endlessly, by not giving up and assuming the restore process went wrong when it has been stuck forever at either 24, 31 or 39% and force closing..

    But I know in the midst of desperation OCD kicks in and you want step-by-step success case scenario reproduction so I will tell you all the steps that I followed that I can remember that got me to finally have the backup to end successfully:

    0. First of all, in the winning attempt I had already uninstalled WA from the new phone and removed totally the WA folder in the internal storage / sdcard storage. Not sure this is mandatory but just to tell this was the case.

    1. Since I got WA working perfectly on the old phone at every moment, I backed up locally for the Nth f%!?&·( time. This left me with the latest local backup plus a few others in the databases folder as a result of keep messing up.

    2. I copied the full WhatsApp directory from the internal storage of the old phone to a safe place. This could be the PC or whatever, but PC transfer via USB seems too sloppy. You maybe could do it via ADB, whatever, I went by the route of coping it to the external SD with some random explorer utility like ES File Explorer. It does not matter, the point is to be able to backup the full WhatsApp folder in order to restore it as similar as possible as the original. What we are more interested right now is in the database folder but having all images, videos etc in place will help in getting it like before the easiest way. (Disclaimer: Ok guys sorry if some steps are too obvious to XDA users which usually are highly educated in the matter, but I was thinking of sharing/linking this text on the reddit and others, so please bear with it).

    3. I installed latest WA in the new phone, opened the app (I intended to not open but I somewhat forgot) and got to the welcome screen, immediately closed the app at that step.

    3. I restored the full folder to the new phone internal storage, pure copy/paste style (as said, in my case via the SD since both phones have SD slot and was very convenient, but via USB, cloud, etc. can be done).

    4. I went to the databases folder and only kept the msgstore.db.crypt12 file and the latest backup with a date (ie: msgstore-2019-11-21.db.crypt12), deleted the rest. Honestly I do not think this is crucial but I somewhat wanted to make it easier for WA to know which one to target, I thought about keeping only the msgstore.db.crypt12 but some random dude pointed that the one with the date was needed. I was under the assumption that file structure is identical in both but just wanted to get done with this and keep both, just in case.

    5. Before opening again the WA to try to activate and restore with this full local copy, I opened the Android settings app and went to applications > whatasapp > storage, as suggested by user redweaver, thanks for the tip! by keeping looking at the storage usage of the app during the restore process we could get insight about if it was really doing something or the app was really stuck. Keep open for now. In my case, I saw also on the old phone that my data used for the app was 780+ MB, so I had an idea of what should be on the new phone by the time it finished (if it did!).

    5b. I don't think this is really necessary but I did it just in case. I was planning to go to work and let the thing running as long as it would need, and I would make sure that the process would get maximum uptime and nothing would get in the way. So I went to Applications > WhatsApp > Battery usage (or something like it) and disabled the battery optimizations for this app. I also went to the developer mode settings and enabled do not lock the phone while it is charging and everything that looked like it might be relevant. Again, most likely this has nothing to do, but reproducible steps, right? :)

    6. Now open WA and activate it as usual, but when it seems that the activation step ended and you go to the next screen, immediately put the phone in air plane mode or disable data/WiFi, whatever. The goal is that it cannot reach Google Drive to look for the online backup. Honestly maybe in the end is not the culprit of GDrive but many people states that the GD backup is broken at this time and suggests going the local route, so we will do it like this.

    7. WA should tell you that looking for the backup is going too slow and to skip this step (sorry to not have exact message, I have it in Spanish, but something in these lines, BTW excuse my somewhat limited English :D). The point here is to click on the link that says skip the step and when you are prompted with a popup, click also on Skip.

    8. WA will display the typical restore / transfer-like screen where the process starts. At this point you have to enable again data plan / WiFi at least or exit air plane mode, don't know really but even if restoring from local it complains about not having internet connection, maybe needs it to encrypt with the key or something? don't know.

    9. Now is the feared moment! Even this time, I got somewhat stuck at 31% again. I left it do its thing, and some time later, it prompted for the popup that has a progress-bar from 0 to 100 (honestly, what is the difference between both?!) which also got stuck at 31%. If you let it be, it starts going back and forth many times, I guess maybe its going chat per chat and the progress-bar represents each one? Dunno. Thing is, even in the prior attempts I got at this point and the backup did not finish successfully. But this time I was decided to let it do its thing as much time as it would take, until the end. In the process the phone might display a pop up saying that WA does not respond. I clicked a few times in the 'keep waiting' option, then I just forgot because I did not have time to mess with it and hoped that it was still working on the background, which bring us to step 10.

    10. While we are contemplating the backup process, we can go to the settings app again and look how the internal data is going for the WA. In my case, after some time under the restore process, when I went there I saw WA had occupied 0.91 GB of data space. After going back and forth again between WA and settings, the usage keep growing: 0.96, 1.03, 1.10... I thought it was on the right track, and encouraged me to keep waiting. Maybe in the end the process is too slow for old databases. Note that some people speculates that having messages from very long ago might be the culprit here due to changes in the table structure and that this might be the reason breaking the restore process. And maybe it is the case, but even if it is, in my case I finally succeeded where previously I didn't and without deleting anything, so this does not seem to be a deal-breaker or I would have never succeeded. I say it because some people reported that deleting old conversations and trying again finally made them succeed. Now I suspect the true reason was simply that by making the database smaller the process finished earlier, but YMMV.

    11. Cannot be totally sure, but in my case, I noticed that leaving WA on the background and clicking on the WA icon again might stop the process for true and bring a message about not being able to recover the chats, I got this previously, do not try to open the WA normally, only leave it temporally to look to the space usage in the settings to get back to it by swyping between recent apps to keep the same instance open and working, this was a key point in my success trial that did not happen during the previous ones.

    12. And finally, while I kept switching between WA and the settings and when I last saw like 1.30GB of space used (almost twice the space compared to the old phone, maybe it leaves a lot of temp data) I don't know if I either messed with the app-switching or it really finished, but then I got prompted to the screen where you enter your name or nickname. And when I completed this step, I finally got to the chats screen and everything was like in the old phone! Where previously I would get to a lot of empty chat rooms with maybe 40 total messages restored according to WA. Hurray!

    Notice that in my case it was still reporting 31% on the WA background screen under the progress bar popup when it finished!! so it seems that is not really mandatory to experience the 100% complete to have it work in the end, but YMMV.

    OK, maybe not the most elegant "guide" out there but I wrote it in a hurry and my english sucks, I just hope it might help someone to not lose their WA chats forever.

    Good luck!

    Edit: I almost forgot but, for the sake of completeness. I also tried a certain script that can backup WA from the phone and retrieve the encryption key, it will also leave an unencrypted copy of the chats database that can later be viewed with a WhatsApp viewer like this. The script is called WhatsApp Key/DB Extractor, and it still works as of 2019, just look at the latest posts in the thread. Guys here on XDA most likely know about it but if not, you might give it a try. I tried it because I assumed that maybe I could circumvent the restore issues by going that route and pushing the backup via ADB, but turns out the legacy WA won't prepare the database due to the time out of sync issue, or at least the data seemed to be lost after performing the restore process, and the unencrypted database on the PC cannot be digested by WA latest versions by just putting it into the internal storage directly according to what other users commented. But, if you finally give up trying the restore process, it still could be relieving to know that you keep a local copy in the PC that can be viewed with another PC tool, at least you get a backup and the conversations are there, in a different way though. Maybe in the future there's a process that can restore them again to a different phone, and you could then merge the new chat database with the older backup with tools like Merjeapp.
    2
    Well, i figured that whatsapp has actually completed the restore at 24%. There are just something preventing the apps from loading normally.

    What i did was let it load at 24% for about 10 minutes, then i force close the apps and restart the phone.

    Once restarted, open back whatsapp, and it will continue with initialising process and once completed, all chats are actually restored. Wasted almost a month to figure this out.
    1
    Hi, I got to step 9 and it got stuck at 31% as prev but now its asking to either skip or restore from older backup? The storage went up to 1.3gb at one point but is now back to 58mb. Do I skip or restore from older or just leave it idle until it prompts with something else
    1
    Hi Everyone,

    After several try outs, I finally succeeded to restore my local backup of Whatsapp. I also discovered and tested some tricks to find out what really works. I hope this information will help you to solve the 24, 31, 35 or 100% backup restore stuck problems of Whatsapp efficiently.

    Before starting the whole process: On several websites is given the advice to delete all your Google accounts on your new phone and to delete all your WhatsApp backups made with Google Drive. In my case I did NOT. Probably, this had no important effect on restoring of my local backup of 1,9 GB with Whatsapp.

    During the whole process it’s also important that your new phone is always in the active mode. Therefore, in the Settings of your new phone you have to disable the sleeping mode. Your battery should also be charged to 100%. With an adapter your phone could also be connected to an electrical wall socket.

    To restore my local backup successfully, my steps were:
    1. I deleted my Google Drive backup on the internet with my personal computer. Then I made a new local backup and a new backup with Google Drive with my old HTC Desire C phone of all my chats, documents, images, video’s and other media, etc. without deleting anything.
    2. On my (new) Samsung Galaxy A5 phone I deleted all the Whatsapp folders and files.
    3. With Play Store I installed the most recent available version of Whatsapp (= 2.21.20.20) on my new phone and opened it only a few seconds. Without pressing on the button Agree & Continue in the Welcome screen of WhatsApp, I closed Whatsapp immediately.
    4. With a USB-connection I copied the whole Whatsapp folder of my old phone to my personal computer. Additionally, I copied the same Whatsapp folder of my personal computer to the internal storage of my new phone. This second step took about 45 minutes.
    5. With a File Manager on my new phone I went to the map WhatsApp/Databases and kept only the 2 most recent local backups. These files were: msgstore.db.crypt12 and msgstore.2021-10-18.1.db.crypt12. All other (backup) files in the folder Databases were deleted.
    6. Via Settings and Apps on my new phone, I went to the app(lication) of WhatsApp and opened the screen App-info of Whatsapp. Being there, I opened the Storage display of WhatsApp. It’s important to monitor the data shown in this display. By frequently sweeping to the Restoring screen and sweeping back to the Storage screen you could monitor what is happening during the restoring process. Earlier, I had noticed, that immediately after the start of restoring my backups the amount of MB’s was quickly increasing and decreasing several times. Without any new actions WhatsApp resulted in a very low amount of MB’s (in my case about 14,75 MB) and an endless during restoring process.
    7. With this new insight, I started (again) to activate Whatsapp on my new phone. After entering my phone number, activation code and confirming the 2 questions of WhatsApp about using my contacts, documents, media, etc., Whatsapp started to search for backups. Sometimes Whatsapp started with my Google Drive backup. But most times with my local backup. It did not matter, as I found out that I could interrupt this process with step 12.
    8. As Whatsapp found my local backup for the first time, I confirmed, that I wanted to restore this local backup. By frequently sweeping to the Restoring and the Storage screen, I discovered what the maximum peak of MB’s of my local backup was, before Whatsapp was decreasing this amount of MB’s. In my case my peak was nearly about 312 MB’s. But on my old HTC phone the amount of data in the internal storage of WhatsApp was only 215 MB’s. It’s an indication that WhatsApp tried to read my (local) backups. The extra temporary MB’s on my new phone were probably necessary to process the whole (local) backup.
    9. After reaching it’s lowest point of MB’s and without reaching the 100% restoring level (= it stopped restoring my messages at 24, 31 or 35%), Whatsapp was showing the message: “Sorry, your backup can not be restored. Would you like to restore another backup?”
    10. After pressing on the buttons “Yes” and “Restore”, WhatsApp started to restore the next backup.
    11. As WhatsApp tried to restore my Google Drive backup, I saw it succeeded to download it. In my case this was 41 MB’s. That’s the same amount of MB’s, that was uploaded with my old phone to Google Drive. But Whatsapp did not succeed to get my Google Drive backup into the internal storage. Finally, this process was endless going on without showing how much % of the messages were restored.
    12. After reaching the endless restoring stage, I interrupted this process in the Storage and Data screen of Whatsapp by pressing on the button “Manage storage”. You could repeat this step every time when you reached the endless restoring process. Please, do not do this in an earlier stage. Otherwise WhatsApp could finish the whole process.
    13. Avoid also pressing on the pop-up of Whatsapp telling you that the Whatsapp App will start again. Too often pressing on that button could also finish the whole process and then you have to start all over again with a new activation code. Instead, just change your screen by sweeping to the Restoring screen.
    14. As a result of step 12: Whatsapp will ask in the Restoring screen to agree to restore another backup. Before confirming that choice, it’s important to clear the cache in the Whatsapp App-info display.
    15. In my case Whatsapp also tried to restore a backup that Whatsapp had never found. Despite this curious message WhatsApp started directly at 24% and continued to 35% and 100% restored messages. But without any result Whatsapp also stopped restoring the never found backup by asking me again to restore another backup.
    16. Now again Whatsapp showed me the information of my local backup (including the time that it was made). After first cleaning the cache in the Whatsapp App-info display again, I confirmed that I wanted to restore this local backup. But now something different happened. In this step Whatsapp started from the beginning directly showing me that 100% of my messages were restored. So everything was there, but Whatsapp could not transform it into it’s own (storage) system. Without any new actions this would also result in an endless restoring process.
    17. Finally, my solution was: “After the start of restoring my local backup, just a few seconds before Whatsapp will reach it’s highest peak of MB’s (= in my case nearly 312 MB’s) shown in the WhatsApp Storage screen, I quickly went to the WhatsApp App Info screen and pressed on the button “Force Stop” (= in my case when the amounts of MB’s were in between 280 to 312). In the following pop-up, I confirmed that choice immediately.
    18. Next I went quickly to the Restoring screen. There was WhatsApp showing me the screen where you have to fill in your (WhatsApp) name.
    19. After typing and confirming my name, WhatsApp started the initializing process. After a few exciting moments Whatsapp showed me all my chats, media, etc..
    20. After checking everything, I found out that all my chats, documents, images, video’s and other media, etc. were 100% complete. Nothing was changed, lost, damaged or corrupted.