HI all,
I've recently wiped my Redmi 7 to upgrade it to LineageOS 18. I took a backup with TWRP before doing that.
I'm ok with LineageOS18 but I did not realise that my Whatsapp backup was not up to date.
So, I thought I could just reinstall my backup, complete the Whatsapp backup and then go back to LineageOS 18 - via a backup or from scratch.
I took the LineageOS 17 backup using ADB as my SD card was formatted as "internal" - another reason for wiping the phone was that I wanted that formatted as portable. Maybe that is now the issue as the mobile does not have the same storage available?
I reinstalled TWRP on the recovery partition and ran the restore from my PC. It runs but it throws out an error at the end which I can't read as it immediately dumps me on the TWRP home page.
If I reboot, it starts an endless booting cycle.
To restore, I used the TWRP backup tool 1.1 from a command line.
Does anybody have any suggestions? Would there be a way to extract the Whatsapp stuff from the backup so I can run it on a working system maybe?
Thank you!
Related
This is my first thread after a years here without any problems to flash on my i9300.
My condition:
1. Previously use CM 10.1
2. Update to CM 10.2 --> It's OK without problems.
4. Restore all my apps from Titanium Backup --> Still OK
5. Uninstall Xposed framework for Reverse Tethering 3.7 --> Reboot --> Install same Xposed framework --> Reboot --> TADAAA!! problem occured :crying:
6. Stuck at bootloader
7. Have done many things but failed untill reinstall stock recovery and stock rom through ODIN --> Myphone start to breath
8. Done MegaWipe before reinstall TWRP recovery, CM 10.2, Gapps and restore some apps through TB --> No problems.
9. Try to nandroid backup via TWRP and get error log as below :
Backing up Data...
Breaking backup file into multiple archives...
E: Error tarring split files!
abusuffian said:
This is my first thread after a years here without any problems to flash on my i9300.
My condition:
1. Previously use CM 10.1
2. Update to CM 10.2 --> It's OK without problems.
4. Restore all my apps from Titanium Backup --> Still OK
5. Uninstall Xposed framework for Reverse Tethering 3.7 --> Reboot --> Install same Xposed framework --> Reboot --> TADAAA!! problem occured :crying:
6. Stuck at bootloader
7. Have done many things but failed untill reinstall stock recovery and stock rom through ODIN --> Myphone start to breath
8. Done MegaWipe before reinstall TWRP recovery, CM 10.2, Gapps and restore some apps through TB --> No problems.
9. Try to nandroid backup via TWRP and get error log as below :
Backing up Data...
Breaking backup file into multiple archives...
E: Error tarring split files!
Click to expand...
Click to collapse
Maybe sectors in eMMC going bad. My advice would be to have at least 4GB free on internal SD at all times. Backup weekly but only to external SD. Avoid writing to internal SD as much as possible. (also be 100% certain that you have multiple EFS backups). If you are using a dual-boot kernel - try to do most of your extensive work in a ROM that you install as second (and keep 1st as emergency backup).
xclub_101 said:
Maybe sectors in eMMC going bad. My advice would be to have at least 4GB free on internal SD at all times. Backup weekly but only to external SD. Avoid writing to internal SD as much as possible. (also be 100% certain that you have multiple EFS backups). If you are using a dual-boot kernel - try to do most of your extensive work in a ROM that you install as second (and keep 1st as emergency backup).
Click to expand...
Click to collapse
Thank you for your advice..
Is the problems under samsung warranty? how to prove to them?
Is there any way to do nandroid backup?
abusuffian said:
Thank you for your advice..
Is the problems under samsung warranty? how to prove to them?
Is there any way to do nandroid backup?
Click to expand...
Click to collapse
I don't think it is covered - or at least not as long as the phone is non-stock and it still starts
The backups can be done from a custom recovery - for instance with Philz there is a menu called "Backup to external SD". By using external SD you are minimizing the chance that something goes bad on the internal SD.
xclub_101 said:
I don't think it is covered - or at least not as long as the phone is non-stock and it still starts
The backups can be done from a custom recovery - for instance with Philz there is a menu called "Backup to external SD". By using external SD you are minimizing the chance that something goes bad on the internal SD.
Click to expand...
Click to collapse
TWRP also can backup to external drive. Have been tried and failed...
As your suggestion I installed Philz recovery and "Backup to external SD" and it completed nicely without any problem :laugh:
what is the different? i think it should be same backup target. it is external SD card but failed with TWRP.
Thank you
abusuffian said:
TWRP also can backup to external drive. Have been tried and failed...
As your suggestion I installed Philz recovery and "Backup to external SD" and it completed nicely without any problem :laugh:
what is the different? i think it should be same backup target. it is external SD card but failed with TWRP.
Thank you
Click to expand...
Click to collapse
I think it might be a small difference on where the intermediary files are stored but I can't say anything more without studying the source code (and asking Phil what the differences are in the dedicated Philz thread might be simpler).
One day i decided i had enough of cyanogenmod and decided stock samsung was the way to go. I did a full backup with the latest version of clockworkmod, the full backup weights 2.99gb. When i try to restore it using any version of clockwork it gets up to restoring data then says Error while restoring /data!
i can boot back to cyanogenmod however apps are "installed" but they all say that they are not
Please help because i really need this phone
Either the file is corrupt or your sd card card could be damaged. It would be easier to flash stock with Odin and start again.
and if you have to /will go further without old backups, switch to TWRP after having rooted
Strange because i copied it without any errors... oh well. :crying:
I've got 2015052 device from jd.com and flashed stock rom from here: http://en.miui.com/download-274.html using stock recovery. Then I've flashed twrp from here http://en.miui.com/thread-152550-1-1.html using stock recovery again.
Now I have twrp that can do backups but can't restore them. my twrp alsco can't install anything that modifies system partition.
I store backups on 64gb sdcard.
When I restore backup twrp starts restoring system as usual but then dies in few seconds with following message:
Code:
E:extractTarFork() process ended with ERROR=255
Does anybody have recovery for this phone that can do backup/restore? Please report what recovery works for you and where you get one.
nETPOBu4 said:
I've got 2015052 device from jd.com and flashed stock rom from here: http://en.miui.com/download-274.html using stock recovery. Then I've flashed twrp from here http://en.miui.com/thread-152550-1-1.html using stock recovery again.
Now I have twrp that can do backups but can't restore them. my twrp alsco can't install anything that modifies system partition.
I store backups on 64gb sdcard.
When I restore backup twrp starts restoring system as usual but then dies in few seconds with following message:
Code:
E:extractTarFork() process ended with ERROR=255
Does anybody have recovery for this phone that can do backup/restore? Please report what recovery works for you and where you get one.
Click to expand...
Click to collapse
Copy the backup into internal-storage and restore again, it should work now.
jwchen119 said:
Copy the backup into internal-storage and restore again, it should work now.
Click to expand...
Click to collapse
Same error with internal memory. I have a feeling that wiping data from twrp makes it unable to restore and install zips.
nETPOBu4 said:
Same error with internal memory. I have a feeling that wiping data from twrp makes it unable to restore and install zips.
Click to expand...
Click to collapse
DId you ever figure this out? Have the same issue on my Nexus7 2013 Wifi, installed CM, want to move back to backup of stock. But crash in to that proverbial Wall. And given that it's a Nexus, it's on Internal Storage, as it's all one big internal Storage.
thanks...
vevmesteren said:
DId you ever figure this out? Have the same issue on my Nexus7 2013 Wifi, installed CM, want to move back to backup of stock. But crash in to that proverbial Wall. And given that it's a Nexus, it's on Internal Storage, as it's all one big internal Storage.
thanks...
Click to expand...
Click to collapse
Nope. I've tried 4 to 5 twrps for my device but none of them can restore backup reliably.
Отправлено с моего Redmi Note 2 через Tapatalk
Just last week I made a full backup of my current rom (LineageOS 17.1) from inside TWRP 3.3.0.0 saved onto an external SD card.
After some testing, I went to restore my backed up image which completed fine but every time it boots it keeps going back to TWRP.
I have tried wiping the data/system and cache beforehand as well as tested with a fresh copy of the same LineageOS 17.1 version installed and booted then trying the restore again inside TWRP but the same problem occurs.
Recently I installed Twrp by nebrassy with pixel experience plus rom.In the recovery at first i try to backup nandroid in a usb drive via otg.I select all available partition for backup.Everything was fine.But at the ending of backup process, when system part was backing up it shows backup error, deleteing files.Then i try to back up in internal storage.In this senario, Twrp shows backup was successfull at n.. secods.But when I boot into system I found no backup file of twrp in my internal storage.I tried it twice,But same result.Now, is there any way to successfully back up nandroid in my device?