Related
Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Edit (1/15/2016):
Thanks to RMarkwald and scryan for the quick responses and info. So it seems that the system image isn't going to be needed, and backing up System, Data, and Boot will be good enough for normal backup of the phone/rom before trying something that might break the current setup.
giantninja said:
Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Click to expand...
Click to collapse
According to TWRP in regards to System Image: The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.
I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.
rocco24 said:
I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.
Click to expand...
Click to collapse
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju
simms22 said:
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju
Click to expand...
Click to collapse
Thanks for the explanation. I meant the system.img not the full factory image my bad.
rocco24 said:
Thanks for the explanation. I meant the system.img not the full factory image my bad.
Click to expand...
Click to collapse
the system.img is in the factory.img, just like the boot.img, cache.img, etc..
Nailed it thanks
RMarkwald said:
According to TWRP in regards to System Image: The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.
Click to expand...
Click to collapse
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again
giantninja said:
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again
Click to expand...
Click to collapse
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...
scryan said:
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...
Click to expand...
Click to collapse
Awesome. That's what I was thinking, but I've been wrong before, so it never hurts to verify.
Thanks!
Opps wrong thread... Lol
Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.
cstokes86 said:
Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.
Click to expand...
Click to collapse
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.
JimSmith94 said:
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.
Click to expand...
Click to collapse
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.
I'm in npd90g preview flashed via twrp.if I want official ota
Just flash system image of mm latest and this downgrade doesn't brick my phone ? Can I get ota? And what other should I flash with system image ? Boot ,data and recovery also ?
I dont no much english like othetr peopel
Promblem is i root my honor5x then device get so heat up . After that i deciede to reset it factory setting i have done it but now my device is stuk in twrp loop its not going back normal condition like factory setting plz help me ........ plz
@Shakil jamali: Wrong forum. Go to Honor 5X forum and ask again.
cstokes86 said:
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.
Click to expand...
Click to collapse
Good question. Is this system image actually a partition? Or something TWRP does combining the system image part with a few others into one file? If it is a partition would it be possible to delete it and resize system partition to make use of the extra space? I'm on a nextbit robin stock 7.1.1. Sys image shows as 3,072mb.
For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA
soyti2x said:
For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA
Click to expand...
Click to collapse
First, for your 255 error, look at this post. Get rid of the corrupted file and a normal nandroid will work.
To answer your main question, you can use the system.img as a backup. It is intended for people who want an complete, untouched system backup to restore prior to attempting a OTA update.
An alternative approach to backup/restore that works very well in N6, is Chainfire's FlashFire.
Until now, no my rooted Samsung Note 3 I have automatic TWRP backups running every night. This just mirrors my paranoia that I will manage to screw up something and recovery via TWRP restore is often faster/easier/more complete than trying to do anything else. I do this using the OpenRecoveryScript and have always used this backup command:
backup DSBCR DailyBackup
Which gets data, system, boot, cache, and recovery. I plan to do the same now that I know to put the OpenRecoveryScript into /data/cache/recovery instead of /cache/recovery on my Note 3.
So my question here is what partitions make sense to backup on the V40? And by "sense" I mean something likely to change or get broken (by errant apps or, more likely, my own doing) AND having the ability to restore using TWRP restore from backup.
There are a ton of partitions on this device - most of which I know little/nothing about. I do know that the system and vendor partitions have duplicates and so those are not needed, I guess. And it seems that the OpenRecoveryScript backup command has no way to handle anything except the following anyway:
S: system,
D: data,
C: cache,
R: recovery,
B: boot,
A: and-sec,
E: sd-ext (I don't need the external SD)
So there would seem to be no way to get modem and all the others I don't know much about anyhow.
When I tried to use the same command as above, I ended up with only boot and data - which is a great start! I think I saw an error that system was not mounted so maybe that explains its absence - perhaps I need to mount it first in my script (which I never have had to do on my Note 3)? Even though my V40 is rooted with Magisk, I am making changes to system so I do want to back that up (so long as I can use it during a restore).
Does it make sense to try and backup recovery since things seem really different recovery-wise on this device? Same question for cache and boot?
Thanks for your tolerance of my newbie questions.
Well from empirical experience, it seems that there is no way to backup anything save boot and data. I was able to mount /system_root but that had no impact on backing up system. And I was unable to mount cache or recovery explicitly so those are out as well.
PS - for anyone using the old 123 special partition for backups, they are no longer supported. I have never used them but decided to try and see what happened - only messages that they are no longer supported.
Perhaps there is some other way to accomplish this? Suggestions welcome. Thanks
Thanks.
That I'm aware of recovery should backup as part of the boot partition....I could be wrong tho
Ainz_Ooal_Gown said:
That I'm aware of recovery should backup as part of the boot partition....I could be wrong tho
Click to expand...
Click to collapse
I guess that does make sense. Thanks. I am still trying to get my mind around the whole new situation (compared to my old Note 3).
twrp-3.6.1_11-1_gta4xlwifi
Descarga
twrp-3.6.1_11-1_gta4xlwifi.img | by Tickbaby for Galaxy Tab S6 Lite
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
en tar
twrp-3.6.1_11-1_gta4xlwifi
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Someone tested?
Yes and works
ARIES4RR said:
Yes and works
Click to expand...
Click to collapse
How did you install it? I tried zipping it to a tar file with 7-zip and flashing it from AP with Odin but that didn't work.
Never mind. Got it with fastboot. But backup fails and that's my reason for wanting TWRP.
Change the name TWRP-3.6.1_11-1_GTA4XLWIFI.IMG by
recovery.img
and create.
recovery.tar
and pass it with Odin
ARIES4RR said:
Change the name TWRP-3.6.1_11-1_GTA4XLWIFI.IMG by
recovery.img
and create.
recovery.tar
and pass it with Odin
Click to expand...
Click to collapse
I didn't rename it, so that's why it didn't work with Odin. But as I said, I managed to flash it with fastboot anyway. But it still won't backup, probably because data is encrypted.
hi
here it is in tar
twrp-3.6.1_11-1_gta4xlwifi
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pass with odin
Why use TWRP when you have Lineage Recovery? Lineage Recovery is better.
Backup option work?
Plzz make for LTE variant
Just made a version for the LTE variant (modified prop.default).
Issues I've found:
Encrypted data partition can't be mounted.
LineageOS fails to install ota updates, because update zip is stored in data partition.
Backup option is not working correctly unless data are decrypted.
Mind the gapps installer fails because it can't mount system_ext partition.
Tested on my SM-P615.
Stelios333 said:
Just made a version for the LTE variant (modified prop.default).
Issues I've found:
Encrypted data partition can't be mounted.
LineageOS fails to install ota updates, because update zip is stored in data partition.
Backup option is not working correctly unless data are decrypted.
Mind the gapps installer fails because it can't mount system_ext partition.
Tested on my SM-P615.
Click to expand...
Click to collapse
#3 I would much prefer to have backup than encrypted data, if that were an option. Is there a way to keep LOS from re-encrypting data? I know that in earlier versions, once you formatted the data partition, it didn't get encrypted again unless you flashed a stock ROM. Or is this a GSI thing?
To prevent lineageos from re-encrypt data open /vendor/etc/fstab.exynos9611 in an text editor, find a line which starts with "/dev/block/platform/13520000.ufs/by-name/userdata" and remove
fileencryption=aes-256-xts parameter (don't forget to remove also the comma!).
WARNING: That should be done after wiping. The instructions are device specific!
Stelios333 said:
To prevent lineageos from re-encrypt data open /vendor/etc/fstab.exynos9611 in an text editor, find a line which starts with "/dev/block/platform/13520000.ufs/by-name/userdata" and remove
fileencryption=aes-256-xts parameter (don't forget to remove also the comma!).
WARNING: That should be done after wiping. The instructions are device specific!
Click to expand...
Click to collapse
Let me see if I have the steps right. I already have LOS up and running. I flash TWRP and boot to it. Then format the data partition to get rid of encryption. Then edit as per the above and reboot. Is that right?
This is why Linux4 abandoned TWRP for the platform. TWRP seems so problematic! Everyone should switch back to Lineage Recovery. Data is encrypted for good reason on the devices. You don't need a backup option in recovery plus why use TWRP when you can use an official looking recovery? OTA updates on LOS Recovery aren't hideous with logs and it looks official and fits with Lineage! Use Lineage Recovery, NOT this crap excuse of a recovery. Lineage Recovery can be found on the official lineage website for the official version of 19.1 and the unofficial version for unofficial 19.1 can be found at lineage.linux4.de
SamDungUser said:
This is why Linux4 abandoned TWRP for the platform. TWRP seems so problematic! Everyone should switch back to Lineage Recovery. Data is encrypted for good reason on the devices. You don't need a backup option in recovery plus why use TWRP when you can use an official looking recovery? OTA updates on LOS Recovery aren't hideous with logs and it looks official and fits with Lineage! Use Lineage Recovery, NOT this crap excuse of a recovery. Lineage Recovery can be found on the official lineage website for the official version of 19.1 and the unofficial version for unofficial 19.1 can be found at lineage.linux4.de
Click to expand...
Click to collapse
You do it your way and I'll do it mine. I DON'T LIKE LOS RECOVERY!! And I DO NEED the backup option, thank you very much.
lewmur said:
You do it your way and I'll do it mine. I DON'T LIKE LOS RECOVERY!! And I DO NEED the backup option, thank you very much.
Click to expand...
Click to collapse
TWRP is unsuitable for the device because /data is encrypted therefore backup won't work and decrypting data is unsafe.
SamDungUser said:
TWRP is unsuitable for the device because /data is encrypted therefore backup won't work and decrypting data is unsafe.
Click to expand...
Click to collapse
I guess you neglected to read the post that tells you how to keep LOS from re-encrypting the data partition. I DON'T WANT IT ENCRYPTED!! I have been using Android devices for close to a decade without encryption and have NEVER had a problem. I have a belt. I don't need suspenders too. (And LOS when it was Cyanogenmod.)
lewmur said:
I guess you neglected to read the post that tells you how to keep LOS from re-encrypting the data partition. I DON'T WANT IT ENCRYPTED!! I have been using Android devices for close to a decade without encryption and have NEVER had a problem. I have a belt. I don't need suspenders too. (And LOS when it was Cyanogenmod.)
Click to expand...
Click to collapse
Due to the issues with TWRP, Linux4 might block your recovery from being able to install LOS.
Would it be possible to backup different images from different GSI ROMs to be able to test and restore each one without losing all the apps, configuration, etc. in the process.
For example:
1. Install "GSI name1" configure it, install apps, my Google account, etc.
2. Somehow, make a backup of the required partitions "backup name1" (At the computer?)
3. Install "GSI name2" configure it, install apps, my Google account, etc. (Not necessarily the same apps than before).
4. Somehow make a backup of the required partitions "backup name2".
5. Continue testing other GSI or restoring one of the previous ones from the backups and be able to use the phone as it was before, including apps, configuration, etc.
I can imagine two ways to face this task:
A. Using a custom recovery to backup partitions to SD card.
B. Using fastboot or mtk_client to backup partitions to the PC.
Would be easy? Possible? Not recommendable for some reason?
I am new on this flashing-bricking-sweating-unbricking thing, so I would appreciate feedback.
Thank you!
Hi
If your goal is to test the GSIs, it's easier to use the DSU-sideloader instead of the backup.
This app enables you to dual boot.
You will be able to move back and forth between images. Even if you get into a boot loop, you can return to the original image just by rebooting.
If you have root, this app will be easier because there will be less operations.
https://github.com/VegaBobo/DSU-Sideloader
I have been taking a look to the DSU concept. It is interesting, but not what I want. Also, it requires the main ROM to be stock ROM (maybe in future is fine to use with custom ROMs).
DSU would be perfect if you want to keep romA and romB working in parallel in your daily life (for example, one for work and business and the other one for gaming and social apps).
What I want to do is to test romA for a while, move to romB for a while, if I prefer romA, reinstall it and forget about romB (literally, delete it). Maybe in few months, backup romA again and check romC for a while...
As I do not want to be swapping from one to another in daily life, it does not make sense to reserve space for having both simultaneously ready to work on the phone.
By now I have been learning about adb and recovery backup options. I need to check more during the next days, but I noticed that from Recovery, I can also use adb (it says not authorized device, but that is for not being rooted yet, I suppose). If it is possible to use adb from recovery after rooting, it would be easy to have a PC software for backing up ROMs easily (system, data and userdata partitions?).
I will keep researching about it...
The DSU does not have to be a stock rom.
It's just desirable.
Currently I have crdroid GSI as the first OS and the second OS is trying several OSs.
If you try it, you'll notice how easy it is.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models.
I have a 128GB model, so it took too long to back up using mtkclient and I quit halfway through.
The problem is time and encryption, keep them in mind.
Currently, TWRP does not support backup or encryption on Android 12. It is the same even if it is the official latest of other models
Click to expand...
Click to collapse
Well, definitely untrue now as most devices have got it sorted out with decryption, Android 12 being a pain some devices got 13 done before 12, but as of the time you wrote this post my device Motorola stylus 22 5g Qualcomm, we hadn't figured out the decryption yet but you could definitely just patch your fstab in vendor either by hand or with DFE neo, to disable the encryption and TWRP would run fine. You would just have to make that first format reboot back to recovery immediately and while it still stays the data from a fresh format flash the other handy RO2RW re zip and DFE neo. Honestly the boot times are so much better without decryption I don't think I would go back as long as I've got a password on orange fox or whatever.
Mi 11T Pro TWRP Backup failed twice on same area ........ Backing up Super (system system_ext product vendor odm)...
I did twice and same spot that failed miserably and I also copied just a small portion of the recovery log that fail:
Backing up Super (system system_ext product vendor odm)...
I:Reading '/dev/block/by-name/super', writing '/usb_otg/TWRP/BACKUPS/5bb27ae4/2022-12-27--06-03-40/super.emmc.win'
I:Error writing destination fd (Operation not permitted)
Backup Failed. Cleaning Backup Folder.
Running on the latest TWRP twrp-3.7.0_12-v6.5_A12-vili-skkk and rooted with lastest Magisk v25.2 with safety net passed.
Any advice is highly appreciated and thanking in advance - -
NDbluewee said:
Mi 11T Pro TWRP Backup failed twice on same area ........ Backing up Super (system system_ext product vendor odm)...
I did twice and same spot that failed miserably and I also copied just a small portion of the recovery log that fail:
Backing up Super (system system_ext product vendor odm)...
I:Reading '/dev/block/by-name/super', writing '/usb_otg/TWRP/BACKUPS/5bb27ae4/2022-12-27--06-03-40/super.emmc.win'
I:Error writing destination fd (Operation not permitted)
Backup Failed. Cleaning Backup Folder.
Running on the latest TWRP twrp-3.7.0_12-v6.5_A12-vili-skkk and rooted with lastest Magisk v25.2 with safety net passed.
Any advice is highly appreciated and thanking in advance - -
Click to expand...
Click to collapse
You have rooted the phone and you must have seen that even with root the system partitions remain in read only which means that you cannot restore the system with the Twrp which must have write permission.
NOSS8 said:
You have rooted the phone and you must have seen that even with root the system partitions remain in read only which means that you cannot restore the system with the Twrp which must have write permission.
Click to expand...
Click to collapse
Thanks @ Noss8
Yes, I do understand this part however, If I use PartitionBackups to back up all the files around 6.7 GB ..... the question is can I restore through PartitionBackup in future? Thank again for the piece of advice!
NDbluewee said:
Thanks @ Noss8
Yes, I do understand this part however, If I use PartitionBackups to back up all the files around 6.7 GB ..... the question is can I restore through PartitionBackup in future? Thank again for the piece of advice!
Click to expand...
Click to collapse
I don't know this app.
The system on devices with A/B partitions with A12 or A13 remain in Read only.
Try to restore only the data without the system/vendor/etc.
Did you remove security on the lock screen and reboot the system before your backup?
This has the effect of decrypting your data.
Micloud can also back up your data, apps (not all and without settings), mms, sms, photo, music, configuration settings, but the free version is limited to 5GB.
There is also backup on PC with Micloud, just a folder to cut / paste.
NOSS8 said:
I don't know this app.
The system on devices with A/B partitions with A12 or A13 remain in Read only.
Try to restore only the data without the system/vendor/etc.
Did you remove security on the lock screen and reboot the system before your backup?
This has the effect of decrypting your data.
Micloud can also back up your data, apps (not all and without settings), mms, sms, photo, music, configuration settings, but the free version is limited to 5GB.
There is also backup on PC with Micloud, just a folder to cut / paste.
Click to expand...
Click to collapse
Thank again @ NOSS8
Yes, I did removing all my security passwords on the lock screen before doing all the backups.
The Twrp was good where I managed to backup everything except the system while the PartitionBackup did backup everything!
Yes, I do fairly backup only folders under Micloud as only 5GB of storage only!
Thank you