Delayed Notification after Data Backup Restore [Fix]

In this guide, we will show you the steps to fix the delayed notification issue on your Android device after restoring a data backup. There exist quite a few methods of restoring the data on your device after setting it up. While the default Google Drive is sufficient for everyday users, however, if you have a rooted device, then you could take it to the next level altogether.

Using apps like Titanium or Swift backup, you could take a backup of all the partitions [Nandroid backup], app data, and even minute details like the calls logs and the recent apps screen. However, restoring data from such apps is causing an issue or two for some.

In this regard, many users have voiced their concern that they are facing delayed notification issues on their Android devices after restoring a data backup from such sources. If you are also in the same boat, then this guide will make you aware of a nifty workaround to rectify this bug. Follow along.

Fix Delayed Notification after Data Backup Restore

In order to carry out this task, your device needs to be rooted. If you haven’t done so yet, then please check out our guide on How to Root Android via Magisk Patched Boot . Once done, you may then get started with the below steps.

1. To begin with, download a root-supported file explorer, such as MiXplorer [ direct link ].
2. Then launch it tap on the hamburger menu situated at the top right, and select Root.
3. You will now get a Magisk prompt, tap on Grant. Now go to the below location [replace folder_name accordingly]: /data/data/folder_name/shared_prefs/com.google.android.gms.appid.xml
4. If the app folder is not there, then check out this location instead [replace folder_name accordingly]: /data_mirror/data_ce/null/0/folder_name/shared_prefs/com.google.android.gms.appid.xml
5. Now delete that com.google.android.gms.appid.xml file. Once done, force stop that app as well.
6. Now launch the app and that file will be re-created. With this, the underlying issue would be rectified.

• Enable Google Photos Backup while charging only
• Google Backup not working on Android: How to Fix
• Take a Backup of Persist Partition: Fix Fingerprint Not Working
• Backup Qualcomm Firmware via Firehose MBN/ELF File and QFIL Tool

(Cancel Reply)

Δ

Take a Backup of Persist Partition: Fix Fingerprint Not Working

In this guide, we will show you the steps to take a backup of the persist partition on your Android device. Stepping into the custom development brings in a plethora of goodies with itself. Right after you have unlocked the bootloader, you will be in a position to dive deep into the custom ROMs, custom recoveries, or gain administrative privileges by rooting the device via Magisk. However, this is just one side of the coin. Carrying out these tweaks could prove to be a risky bet as well.

For OnePlus users, it is usually issues with the fingerprint sensor that seems to be bugging quite a few users. As a result of which, they are unable to register or enroll their fingerprint or use the already registered ones to unlock their device. So right before you step into the modding domain, your first course of action should be to take a backup of the persist partition. In case you end up messing with the fingerprint, then you could easily fix it by restoring the backed up persist. On that note, let’s get started with the steps to take a backup of the persist partition.

• How to Take a Backup of Persist Partition STEP 1: Root your Device STEP 2: Install Android SDK STEP 3: Enable USB Debugging STEP 4: Grant SuperUser Request STEP 5A: Backup Persist Partition via ADB [Automated Method] STEP 5B: Backup Persist Partition via SU [Manual Method]
• How to Restore Persist Partition

How to Take a Backup of Persist Partition

The below instructions are listed under separate sections for ease of understanding. Make sure to follow the same sequence as mentioned. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.

STEP 1: Root your Device

First and foremost, your device needs to be rooted. If you haven’t done so, then you may refer to our guide on How to Root Android via Magisk Patched Boot.img .

STEP 2: Install Android SDK

First and foremost, you will have to install the Android SDK Platform Tools on your PC. This is the official ADB and Fastboot binary provided by Google and is the only recommended one. So download it and then extract it to any convenient location on your PC. Doing so will give you the platform-tools folder, which will be used throughout this guide.

STEP 3: Enable USB Debugging

Next up, you will have to enable USB Debugging so that your device is recognizable by the PC in ADB mode. This will then allow you to execute the ADB Shell and henceforth the su command . So head over to Settings > About Phone > Tap on Build Number 7 times > Go back to Settings > System > Advanced > Developer Options > Enable USB Debugging.

STEP 4: Grant SuperUser Request

1. Connect your device to the PC via USB cable. Make sure USB Debugging is enabled.
2. Then head over to the platform-tools folder, type in CMD in the address bar, and hit Enter.
3. This will launch the Command Prompt. Now type in the below command to open the shell environment. adb shell
4. After that, execute the following command to invoke the superuser request su
5. You will now get a prompt on your device, tap on Allow/Grant.

STEP 5A: Backup Persist Partition via ADB [Automated Method]

1. Now execute the below command in the CMD window to take a backup of the persist partition su -c dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/Download/persist.img
2. The persist partition will now be backed up in the Downloads folder on your device. It is recommended to transfer it to your PC.

STEP 5B: Backup Persist Partition via SU [Manual Method]

1. To begin with, type in the below command to open the shell environment: adb shell
2. Then type in the below command. You’ll get a Magisk request, tap on Grant. su
3. Now type in the below command to bring a list of all partitions on your device ls -la /dev/block/by-name
4. Check out the sda address for your persist partition. In our case, it is sda8.
5. Now use the below command, replacing location with the sda address: dd if= location of=/sdcard/persist.img bs=4096
6. In our case, the aforementioned command will transform to: dd if= /dev/block/sda8 of=/sdcard/persist.img bs=4096
7. The persist.img will be placed in your device’s Internal Storage. Transfer it to your PC.

How to Restore Persist Partition

So you have messed up the fingerprint on your device? Well, not an issue as you could easily fix it just by flashing the backed-up persist.img file.

1. To begin with, carry out steps 1 to 4 as mentioned above.
2. Then transfer the persist.img file to the platform tools folder on your PC.
3. Next up, connect your device to the PC via USB cable. Make sure USB Debugging is enabled.
4. Now head over to the platform-tools folder, type in CMD in the address bar, and hit Enter.
5. This will launch the Command Prompt. So type in the below command to boot your device to Fastboot Mode adb reboot bootloader
6. Finally, execute the below command to flash the persist.img file fastboot flash persist persist.img
7. That’s it. You may now reboot your device to the OS via the below command- fastboot reboot

So these were the steps to take a backup of the persist partition on your Android device. If you hadn’t taken the persist backup beforehand and your device is currently facing fingerprint issues, then there’s no point in taking the backup of the persist partition and flashing it. This is because the said partition has already been corrupted. Moreover, you cannot use the persist partition image from another user, even if they have the same device and belong to the same region.

• How to Fix Loss Of Fingerprint Sensor Issue on any OnePlus Device
• How to Enable Google Call Screening on any Android Phone
• Pixel 6 Fingerprint Sensor Not Working: How to Fix
• Pixel 6/Pro Device was locked manually: Enter PIN instead of Fingerprint

(Cancel Reply)

Δ