Database Users

Nandroid won't restore

I made a nandroid backup of the stock rom I was using. I backed up everything, data, system, etc. I installed a new rom and then rebooted and installed a kernel. The device got stuck on the boot logo. So I factory wiped and tried to restore my backup. No luck. So I did a full wipe and the tried to restore. Still no luck. Stuck at logo. Then I tried to install the rom again, and that worked (no kernel this time)
Why didn't my nandroid restore? What did I do wrong?
Sent from my VS980 4G

Bootloop after CWM restore

My Nexsus 4 was at 5.0.1 updated OTA, I rooted and installed recovery and created a nandriod backup on the internal SD card. The phone was working fine for the most part except it was having issues with the screen going black when making a call and would not come out of that state. I wanted to revert back prior backup so I did a nandriod restore with CWM v6.0.4.7 and now my phone is in a bootloop. I've tried wipe data/factory reset, also tried wipe cache partition, but still stuck in bootloop. I'm not sure what else I can do to get out of this bootloop state/ Any suggestions would be greatly appreciated.

Fixed it by using Nexus Root Tool Kit to flash stock image. Not sure what happened but I'm switching to TWRP. First time using CWM and things didn't work out well for me using it.

Restored Backup not booting properly? "#### has stopped"

Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers

sergeantash said:
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
Click to expand...
Click to collapse
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.

davyleggend said:
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
Click to expand...
Click to collapse
Ok, this has given me an idea - I have flashed fresh Cyanogen and now I'm attempting to restore just the 'data' and 'cache' elements of my backup by using the Philz 'Custom Restore' feature...fingers crossed!

So, my idea worked...my phone is now back up and running, what a relief!

MIUI backup doesn't boot up after restoring through TWRP

So... I installed LOS & it all went fine, but when I restored my MIUI backup with TWRP, the phone is stuck on the very first boot screen (on which it says Redmi by Xiaomi) & won't move any further. I've wiped the system, data & boot partitions yet no luck. What could be wrong? I want to go back to MIUI to backup my apps

it happened to me too.
when i done updating my device to newer nightly update, i got stuck on twrp decrypt data password. trying to restore back to miui, but then getting stuck on the very first boot screen.
i got no luck when trying several times restoring twrp recovery and miui, so i stay in LOS with no other options.
if someone could help please show me the guide.
thanks

Error 255 when restoring a TWRP backup

Hello,
when I try to restore my TWRP backup of Lineage 17 on my Samsung Galaxy A5 2016 I run into the
extractTarFork() process ended with ERROR: 255​issue, and have tried several methods which I have found when googling for fixes, but none has worked so far.
This is what I've tried:
- unmount the data partition before restoring backup
- just restore system, data and boot, tick off the others
- wiped data/system/cache, flashed rom+gapps, flashed backup with all sections activated (radio, system, data,...)
- wiped data/system/cache, flashed rom+gapps, flashed backup with only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, wiped dalvik/cache after, flashed backup w/ only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, reboot, clicking next on every configuration screen, reboot to recovery, restore only data from backup
The issue seems to always occur at the same point in the process, in the progress bar its either at ca 45% or 58%, depending on if only data or everything is supposed to be restored. Restoring everything _BUT_ the data partition works, but the stuff I need to access is the data.
Kind regards

Hello,
I managed to fully restore the backup follwing this guide
Now my phone boots up to the point right after the Lineage logo is shown, where it says "starting the phone" and would probably ask for sim pin if I had a sim card in it. Then it reboots and does the whole thing again.
Does anyone have an idea how to fix this?
Kind regards