I use twrp-3.5.1_9-0-gts4lvwifi.img.tar and LineageOS 16.1 on B1, nandroids do not work, after backing up the file, the device will bootloop.
Even if encrypted, this should not be problem, and backups are not encrypted, although there is strange behavior
It seems to change from 'arm64' into 'arm' and the system partition shrinks.
I don't understand
Related
I'd like to back up my new Nook and also backup periodically the rooted Nook. I'm aware of a method using diskimage and mini-partition wizard, but that seems overkill because it requires deleting all partitions of the Nook, thus if anything goes wrong with the backup the nook is destroyed. Besides, I think the image produced by diskimage will be a total backup whereas I think only the rooted part needs to be backup up periodically.
Is there any way to do periodic backups without using the diskimage/partition wizard procedure?
Well, you only need to delete all the partitions to restore the backup.
Or you can use CWM
won't Titanium work on the nst / glowworm?
backups
Yes, I have titanium backup and back up all my apps, etc. Works very well. But what if the system root becomes corrupt? I'm not very knowledgeable about android, but by analogy with a windows system, backing up up my programs and data will make it easier to restore many things after a system crash, but won't help to restore the system to working condition.
As I understand rooting, the original nook system is not altered but some partitions are changed or added by rooting. Only the boot program is changed to allow choice of either nook original or nook rooted. Is that correct?
What I'm looking, then, for is some way to restore all the rooted partitions only, without first destroying all the nook partitions if the root becomes corrupted (but not the original nook part of the system). If I knew which were the root partitions, I could choose those partitions that had been backed up with diskimage, but how would I restore only those partitions - mini partition wizard won't do that apparently. It requires all partitions be deleted before it will restore the disimage backup; I can't pick and choose partitions, as far as I understand from directions about that app.
I'm worrying about in destroying all the nook partitions is that something goes wrong with my restore procedure. If that happens, then the nook is bricked, probably forever. If only the rooted partitions were replaced, then the restore could be repeated (or I could re-root the Nook).
Perhaps cwm does what I need?
The image based backup (boot from noogie; dd the image of the complete device) is your complete backup.
The Titanium backup is your incremental backup.
Keep a couple of full image backups around and back up more often with Titanium. Restore your rooted backup, then run Titanium to restore your apps.
Rooting changes /boot, /system and /data and the best way to get a reliable /boot backup is to boot from a different disk (noogie) and do the full backup.
As long as you have a viable restore to how the device was shipped, you should in a pinch be able to re-root, reinstall Titanium and then restore your programs and data. I have ~36 gig of NST and glowworm backups in the house and am very glad that I do. Disk is cheap and I think the restore is faster from an image based backup than from a CWR backup.
Hello
I made a full backup with philz and transferred it to my pc. Tried to delete the backup folder from my internal sd card but can't. Get this message:
Cannot delete backup: the storage is write-protected. Remove the write-protection and try again.
BTW, I'm on stock kk 4.4.2
Thanks for your help
By default, CWM and Philz protect the nandroid data from being deleted since they utilize an incremental backup scheme rather than the older image file setup. For example, let's say you have three nandroid backups: A, B, and C. If the nandroid data wasn't write protected and you delete backup A, you would screw up ALL your nandroid backups. A is the master backup. When the recovery makes backup B, it only backs up the changes made between A and B. If you then made backup C, it would back up the changes between A AND B, and C. Since the possibility of screwing up all your backups by deleting the oldest is a major problem, CWM and Philz write protect the storage.
Go into Philz, then enter the backups menu. Delete the existing backups using its delete function, then select "free unused storage data" to recover the space. After doing that, switch to TWRP 2.8.6.0, as it doesn't make incremental backups and thus doesn't write protect the storage space. Also, unlike CWM and Philz, you can place the backups on your MicroSD card..
Done....thanks very much Strephon
hi, i have the same problem and it work, thanks!
So you thought that encrypting your OnePlus One was a good idea? So did I. I had so many issues after having encrypted my One that I simply wanted to get rid of it. After a lot of searching, I didn't come across a simple guide to decrypt it. And here I am
First thing first. Did you know that TWRP doesn't do a _full_ nandroid backup? It backs up everything _except_ /data/media. That was basically the reason why I'm writing this.
What you need:
An unlocked bootloader
TWRP recovery (I was using 2.8.6.1 but any version might just work)
An USB-OTG dongle with a memory stick that is large enough to hold all the data
A full battery
Here are the steps:
Go into TWRP recovery and make a backup. Be sure to select the usb_otg as the target location for your backup
Go into TWRPs terminal and make a backup of your /data/media folder. When starting the terminal, you will be asked in which folder you want to start. Navigate to "/data/media" and ckicl "select". I used tar to achieve this. Simply type in "tar cvpzf /usb_otg/datamedia.gz ." (Note: there is a dot a the end!) and it will create an archive with everything in it including permissions.
Now wipe your device. *scary* I know... Still in TWRP go to "Wipe", "Format Data" and type in "yes". This won't just wipe your data but also wipe the encryption
Since our device is basically empty, we just have to restore eveything. Let's start by restoring the nandroid backup
After the nandroid backup, let's restore /data/media. For this go back into TWRP terminal. Starting folder will be "/data/media" again. Type in "tar xvpzf /usb_otg/datamedia.gz ." (Note: there is a dot a the end!) to restore everything.
There you go... OnePlus One decrypted!
Simple and clear guide. Just what I was looking for. A couple of questions before I begin:
File size limit. Most USB drives are FAT32 (4GB file limit) so how do you split the tarball into <4GB files?
Will TWRP (or Android or whatever recognizes filesystems) recognize exFAT, NTFS or other filesystems that don't have file size limitations?
If you do split the tarball into smaller sizes, how do you restore them?
Thanks again for the guide and info
Hello everyone,
I encounter a problem when trying to restore backup in TWRP. All md5 checksums are successfully verified, backup restores "Boot" and "System" partitions, then proceeds to "Restoring Data". After about 85% the process stops, and "Restore Complete Failed" message appears. The phone reboots OK but all data is missing. Essentially, that's like a fresh install: the basic setup has to performed. All apps are there but all settings are gone.
I see that people have similar problems but unfortunately I could not find a solution how to restore data partition. Is there a way to successfully restore data? What is causing the problem?
Here is just a bit more info about the device:
1. Rooted LG G2 D801 (lollipop, Android version 5.0.2)
2. Custom recovery TWRP 2.8.6.1 installed with AutoRec.
3. After rooting and installing the device was fully functional.
4. The initial backup was done in TWRP. The process completed successfully with no warning or errors.
Hope someone could help. Thanks.
Try to update TWRP to 3.0.2-1 and check will it help. Also... do you have enough of free space on your device? TWRP zip backups so it need to have a place to unzip it.
Try to update TWRP to 3.0.2-1 and check will it help.
Click to expand...
Click to collapse
Where do you get TWRP 3.0.2-1 for LG G2? The TWRP website says that LG G2 is no longer updated and the latest version for D801 is 2.8.6.0.
Also... do you have enough of free space on your device? TWRP zip backups so it need to have a place to unzip it.
Click to expand...
Click to collapse
That might be the issue.
I was trying many different ways to restore the data partition. The only way I was able to successfully do it if I wiped or formatted the internal storage (/data/media) in addition to TWRP defaults (data and cache; TWRP excludes /data/media). Somehow, the internal storage interferes with the restore process. I had to backup the internal storage separately to my computer before all the wipes.
The cause might be insufficient disk space (there is less than 1GB available). However, TWRP backups are uncompressed and kept on external storage via USB-OTG. The backups for data, cache and system seem to be regular TAR archives:
Code:
$ file data.ext4.win000 cache.ext4.win system.ext4.win000
data.ext4.win000: POSIX tar archive (GNU)
cache.ext4.win: POSIX tar archive (GNU)
system.ext4.win000: POSIX tar archive (GNU)
One would think the data is directly extracted from TAR archives to the data partition. Even with compressed TAR archives, decompression can be be done "on the fly" (eg. tar xzvf) without decompressing to disk first.
Not sure what exactly happens. The restore sort of works now (I do have to backup internal storage prior to this, which is a big inconvenience). I should have examined recovery.log after failed restore.
sakej said:
Also... do you have enough of free space on your device? TWRP zip backups so it need to have a place to unzip it.
Click to expand...
Click to collapse
Just did few more experiments and insufficient disk space is certainly the issue. This time I did nothing to the internal storage (/data/media). I have two backups: a larger one (includes an initial state of the device) and a smaller one (in which a lot of pre-installed LG G2 stuff was purged from the device). The larger backup consistently fails, the smaller one works like a charm. Of course, it would be great to know in advance whether the backup is going to fail during restore
Thanks for the help!
I've had bad backups in the past, despite completing successfuly.
ursus107 said:
Where do you get TWRP 3.0.2-1 for LG G2?
Click to expand...
Click to collapse
You will find it here on XDA
https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
But if you using it, KEEP IN MIND THAT: https://forum.xda-developers.com/showpost.php?p=70091412&postcount=9
ursus107 said:
One would think the data is directly extracted from TAR archives to the data partition. Even with compressed TAR archives, decompression can be be done "on the fly" (eg. tar xzvf) without decompressing to disk first.
Click to expand...
Click to collapse
It's more the case of how recovery works I think, it cannot directly override files from backup in case if anything went wrong, so rollback is possible.
Turbine1991 said:
I've had bad backups in the past, despite completing successfuly.
Click to expand...
Click to collapse
Restoring from the larger backup only fails if I do not wipe '/data' entirely (including '/data/media'). Otherwise, everything completes successfully. So it has something to do with the available disk space.
Hello,
I've installed twrp 3.0.2-r5 on my Moto G4 Play reteu.
In the last months I was running a Lineage OS based on 7.1.2.
Before I did this installation I created a backup with TWRP.
As there is now the official release of Android 7.x from Moto I want to switch back to stock rom.
The old backup is currently placed on SD\TWRP\BACKUPS\ZY223PZFVW\2016-10-16--23-17-52
and contains these files:
boot.emmc.win
boot.emmc.win.md5
data.f2fs.win
data.f2fs.win.md5
data.info
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
system.info
So started twrp and tried to recover the backup.
I can choose to restore:
Data
System
Boot
System 1882MB and Boot 16MB can be restored without any problem.
But while restoring DATA (54MB) Twrp says:
Code:
E: Unable to find file system (first period).
E: Unknown restore method for '/external_sd
So what does this error mean? I tried to solve by copying the whole backup to internal storage but if I do so I will not be recognized by TWRP as a backup to be restored.
In which folder has the backup, an which files, to be placed on the internal storage?
Thank you for you help
Paul84 said:
Hello,
I've installed twrp 3.0.2-r5 on my Moto G4 Play reteu.
In the last months I was running a Lineage OS based on 7.1.2.
Before I did this installation I created a backup with TWRP.
As there is now the official release of Android 7.x from Moto I want to switch back to stock rom.
The old backup is currently placed on SD\TWRP\BACKUPS\ZY223PZFVW\2016-10-16--23-17-52
and contains these files:
boot.emmc.win
boot.emmc.win.md5
data.f2fs.win
data.f2fs.win.md5
data.info
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ext4.win001
system.ext4.win001.md5
system.info
So started twrp and tried to recover the backup.
I can choose to restore:
Data
System
Boot
System 1882MB and Boot 16MB can be restored without any problem.
But while restoring DATA (54MB) Twrp says:
So what does this error mean? I tried to solve by copying the whole backup to internal storage but if I do so I will not be recognized by TWRP as a backup to be restored.
In which folder has the backup, an which files, to be placed on the internal storage?
Thank you for you help
Click to expand...
Click to collapse
Although not a direct answer I have found TWRP 3.x has difficulty restoring if the underlying files/folders are separated from the parent.
As for the data partition you can probably skip that and simply wipe in TWRP. Boot, recovery and system are the most important if your goal is returning to stock.
Not sure how important stock recovery is if manually flashing vs accepting an OTA update. More experienced minds will need to weigh in.