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.
I don't think this is a Moto X (XT1096) specific problem, but more so with TWRP. Phone works fine, just can't backup or restore
I'll try to get a log as soon as I can, just need to figure out how
Problem
I can't backup or restore (and maybe can't delete via TWRP?) from TWRP, getting errors at the start (can't access .../data/cmthemes and can't access .../data/motogallery) and then at the end TarFork() process ended with ERROR=255
Tried Solutions
Reflash TWRP (broke, had to use TWRP app to fix)
Upgrade TWRP (says it failed, but worked)
Enable Compression (no real difference that I can tell)
Cause?
I was on CM13 (2/2 ?), upgraded to most recent (2/6), didn't like it so wiped and flashed to original (1/29 ?) then restored backup (2/2). Probably wasn't the best way to do that, oops. Since then I have wiped and reflashed 2/2 and upgraded to 2/7, haven't done anything since (besides mess with TWRP)
Any help or ideas would be appreciated!
Please lock/delete
Solution: Factory reset, only method that worked for me
Be sure to clear cache
Solution: There is a file on the phone that is preventing the backup. Not sure what is creating it. It could be an artifact of a TWRP backup restoration, which is the first time I had the problem.
Look in the TWRP log ([SDCard]/recovery.log) and scroll near the end - you will find the culprit there, almost always in the [root]/SYSTEM folder but sometimes in multiple folders. It has many names. I've seen it called, simply "999". On my Moto G4, it was "d.addon". Delete the folder and you're good to go.
Hello just a simple question about format data in twrp, i can't find a real answer on google, if i format data to get rid of encryption (not only factory reset) will my os still be there or i'll have to flash a rom to get my device booting as usual?
That means if i format data can i reboot my phone right after normally? I know all my pics apps etc will be lost but os will still be there?
I suggest u upgrade twrp to 3.1.0.1 and you will not have to format data.
if you will saty on your twrp and format data your os will stay there, dont worry....
t.h.i said:
I suggest u upgrade twrp to 3.1.0.1 and you will not have to format data.
if you will saty on your twrp and format data your os will stay there, dont worry....
Click to expand...
Click to collapse
So no need to format data if i want to install lineage for example? I'm already on latest twrp 3.1.0-1 . I ask this cause last time i tried to install lineage it ended up with a softbrick and had to install a fastboot rom and setting up my phone from scratch.
...also, take a look at the FAQ page of twrp website
here: https://twrp.me/FAQ/
from that list: this entry has the title "What should I wipe in TWRP?"
https://twrp.me/faq/whattowipe.html
advice: first do a backup in twrp; a full one chosing sysimage instead of system ...so if something goes wrong you can go back.
note: in the twrp faq page there is an entry related to the backup procedure.
Good read and tell us about your progress.
glogal said:
...also, take a look at the FAQ page of twrp website
here: https://twrp.me/FAQ/
from that list: this entry has the title "What should I wipe in TWRP?"
https://twrp.me/faq/whattowipe.html
advice: first do a backup in twrp; a full one chosing sysimage instead of system ...so if something goes wrong you can go back.
note: in the twrp faq page there is an entry related to the backup procedure.
Good read and tell us about your progress.
Click to expand...
Click to collapse
Thx for the info i already read this, but i'm french and i couldn't find a real explanation between wipe and format and what was left on the system after each operation , even in french forum it wasn't clear!! Anyway i format data and installed last RR build running good so far!!
My phone (3T) has an unlocked bootloader, is encrypted, not rooted, and running stock OOS 5.0.
I flashed TWRP and discovered that stock OOS restores the stock recovery in boot.
I saw the Oreo dm-verity thread by xenet, had a look at the zip file, noticed that it just modified fstab to prevent force encrypt, so I flashed it to see what happens.
And nothing happens. After the system had booted, fstab is unchanged from the original stock copy.
So I'm wondering whether this file is also restored when booting up on stock.
I get aggressive and go back to TWRP and delete /system/etc and /system/bin and modify build.prop.
Surely now the phone won't boot!
Wrong! It boots up and everything is back to normal in /system.
I go back to TWRP and have a look at /system and it shows me one without the etc and bin folders and has the modified build.prop.
What's going on? How can I see one version of /system in TWRP but a different version (ie, stock) when the phone has booted?
By the way I've been an Android user for many years and have rooted and flashed custom ROMs on a variety of phones and I've never seen anything like what's happening on my 3T. I'm sure that dm-verity is somehow involved in this.
Happened to me on my earlier OOS 5.0 attempts...
But i suspected Magisk is involved in my case.
I downloaded Magisk Module "System Terminal Debloater,"
remove some apps like Duo, Chrome, and Google Play Movies.
Some restarts, they magically re-appear again on Apps Drawer...
Haven't touch them yet again after....
nicknacknuke said:
Happened to me on my earlier OOS 5.0 attempts...
But i suspected Magisk is involved in my case.
I downloaded Magisk Module "System Terminal Debloater,"
remove some apps like Duo, Chrome, and Google Play Movies.
Some restarts, they magically re-appear again on Apps Drawer...
Haven't touch them yet again after....
Click to expand...
Click to collapse
Thanks.
I should have mentioned that I'm also not rooted. So stock OOS 5.0.
Sent from my OnePlus 3T using XDA Labs
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Jackhass said:
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Click to expand...
Click to collapse
No, I don't get that message because my phone is encrypted with a password. So the first thing I see in TWRP is the request for the password and then I'm presented with the menus.
However, in the Mounted menu, system isn't mounted and I have the option of mounting it in read-only mode.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
No, I don't get that message because my phone is encrypted with a password. So the first thing I see in TWRP is the request for the password and then I'm presented with the menus.
However, in the Mounted menu, system isn't mounted and I have the option of mounting it in read-only mode.
Click to expand...
Click to collapse
After first time flashing TWRP a folder gets created on your internal storage, with a hidden file called .twrps, go delete it and reboot recovery to trigger the message "allowing system modifications" on TWRP's first boot...
It's not about encryption, it's just that TWRP remember the decision you made due to the file I pointed out...
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
After first time flashing TWRP a folder gets created on your internal storage, with a hidden file called .twrps, go delete it and reboot recovery to trigger the message "allowing system modifications" on TWRP's first boot...
It's not about encryption, it's just that TWRP remember the decision you made due to the file I pointed out...
Click to expand...
Click to collapse
Somehow the attachment strikes on previous post
Edit: still not working, check your TWRP Folder on storage to find the file
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Somehow the attachment strikes on previous post
Edit: still not working, check your TWRP Folder on storage to find the file
Click to expand...
Click to collapse
Thanks, you are correct. I'd forgotten that that TWRP remembers. Deleting .twrps does bring up the RO prompt after decrypting storage.
Jackhass said:
When you boot TWRP for the first time, it should ask you if you want to put the /system in read/write mode or if you want to leave it unchanged, did you choose the right option?
Click to expand...
Click to collapse
I had allowed changes to the system otherwise I couldn't have made changes to it, which includes the ability to restore the system partition.
But I'm still unclear why if I make changes to the system partition and boot with the stock kernel, then after the boot none of the changes are present in the system partition, but if I boot back into TWRP then the changes are all there.
I recall someone in another OOS 5 thread saying that the stock kernal replaces TWRP with stock recovery if you don't flash root (magisk/superSU). Is it possible that the kernel re-flashes system on boot? Another possibility is that TWRP thinks it's making changes to system but it's not actually? Not quite sure, I've never heard of anything like this before either, just throwing other ideas out there.
I've never read anything about the OP3T or any oneplus phones for that matter having A/B system partitions like the pixels. *shrug*
@nhshah7, something's like what you suggest must be going on to account for what I'm seeing. I'm hoping that someone can confirm my observations and provide a definite answer.
@BillGoss
My thread has been updated relating to all your queries...
Thank you...
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Xennet said:
@BillGoss
My thread has been updated relating to all your queries...
Thank you...
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Click to expand...
Click to collapse
Actually it doesn't explain how TWRP can make changes to system yet the phone boots up on an unmodified system if using the stock kernel. And then, when you boot back into TWRP and look at system, the changes are still there.
Where does the unmodified system come from?
Where does the modified system live?
Why doesn't modifying system result in a failed boot due to dm-verity, while restoring a backup of system does result in a failed boot?
So many questions with no answers.
BillGoss said:
....So many questions with no answers.
Click to expand...
Click to collapse
Not sure if this is applicable in your case but the following possibilities may be worth considering for you:
1. Are you sure that the system image is actually getting modified? If the system partition is not mounted before flashing the zip and the zip being flashed does not mount the system partition in read / write, then no changes to system partitions will actually be written.
2. If dm-verity is enabled, then restoring system could result in an error as this is different from restoring a system-image (nandroid copy of the whole partition and not just the files in the system partition). DM-verity can be triggered if the files are all the same but the dm-verity signature computed by hashing the system partition has changed.
3. For boot partitions, strange behaviour can occur if remnants of the previous boot.img are still in the partition (...e.g. if the previous boot.img was of larger size and a new boot.img of a smaller is flashed, then there will be some bytes after the new boot.img that are from the previous boot.img). To verify this, format the boot partition from fastboot and see if you notice anything different with the new boot.img.
4. In Oreo / 8.0, dm-verity flags are stored in dtb (device tree blobs) inside the kernel and not in the fstab file. Only data encryption can be changed from the fstab file and dm-verity needs to be changed from changing the dtb (...Magisk beta v1456 and SuperSu 2.82 SR4 do this, I think).
rk2612 said:
Not sure if this is applicable in your case but the following possibilities may be worth considering for you:
1. Are you sure that the system image is actually getting modified? If the system partition is not mounted before flashing the zip and the zip being flashed does not mount the system partition in read / write, then no changes to system partitions will actually be written.
2. If dm-verity is enabled, then restoring system could result in an error as this is different from restoring a system-image (nandroid copy of the whole partition and not just the files in the system partition). DM-verity can be triggered if the files are all the same but the dm-verity signature computed by hashing the system partition has changed.
3. For boot partitions, strange behaviour can occur if remnants of the previous boot.img are still in the partition (...e.g. if the previous boot.img was of larger size and a new boot.img of a smaller is flashed, then there will be some bytes after the new boot.img that are from the previous boot.img). To verify this, format the boot partition from fastboot and see if you notice anything different with the new boot.img.
4. In Oreo / 8.0, dm-verity flags are stored in dtb (device tree blobs) inside the kernel and not in the fstab file. Only data encryption can be changed from the fstab file and dm-verity needs to be changed from changing the dtb (...Magisk beta v1456 and SuperSu 2.82 SR4 do this, I think).
Click to expand...
Click to collapse
I'll come back to 1.
2. That makes sense and accounts for why a restore of the system partition with the stock boot image causes me to get dumped back in fastboot mode. If I flash the stock system zip file then the system boots properly.
3. I've not had any issues with strange boot behaviour. I'm always starting with stock or flashing kernels that modify the stock boot image, like Blu Spark.
4. I gathered this from my reading of various threads. If I want to make changes to the system partition and get them to stick and not fail dm-verity then I have to flash a custom kernel. I've proven this in my testing. (A rooting solution would also work, but I've not done this).
Back to 1:
Here's what I've done:
Starting with pure stock image (flash OOS 5.0).
Boot into fastboot and flash TWRP.
Boot into recovery.
Mount system as rw. (In ro mode the next step fails)
Delete the bin, etc, and lib folders in system using the TWRP file manager. (Screenshot a)
Reboot system.
... First interesting fact ...
System boots ok, deleted folders are present in file manager. (Screenshot b)
Boot into fastboot and flash TWRP. (Booting with stock restores stock recovery)
Mount system.
... Second interesting fact ...
TWRP file manager shows that deleted folders are missing. (Screenshot c)
Flash custom kernel or patched boot image
Reboot system
... Third interesting fact ...
System fails to boot. Hangs on splash screen.
So TWRP made the changes (otherwise how could they be visible between reboots, including a replacement of recovery) and I only did them once.
Yet they don't actually take effect until I replace the stock boot image.
So, where are the changes hiding? What did TWRP actually change?
Screenshots (note that TWRP has the wrong timezone set so the time shown is wrong):
BillGoss said:
....
Back to 1:
Here's what I've done:
Starting with pure stock image (flash OOS 5.0).
Boot into fastboot and flash TWRP.
Boot into recovery.
Mount system as rw. (In ro mode the next step fails)
Delete the bin, etc, and lib folders in system using the TWRP file manager. (Screenshot a)
Reboot system.
... First interesting fact ...
System boots ok, deleted folders are present in file manager. (Screenshot b)
Boot into fastboot and flash TWRP. (Booting with stock restores stock recovery)
Mount system.
... Second interesting fact ...
TWRP file manager shows that deleted folders are missing. (Screenshot c)
Flash custom kernel or patched boot image
Reboot system
... Third interesting fact ...
System fails to boot. Hangs on splash screen.
So TWRP made the changes (otherwise how could they be visible between reboots, including a replacement of recovery) and I only did them once.
Yet they don't actually take effect until I replace the stock boot image.
So, where are the changes hiding? What did TWRP actually change?
Screenshots (note that TWRP has the wrong timezone set so the time shown is wrong):
Click to expand...
Click to collapse
Some more thoughts for you to consider:
1. Have you tried this with the official TWRP recovery version 3.2.0-0?
2. Is there anything inside the folders that you see using the file manager after a regular boot? Folders of same name may exist in the boot ramdisk and these are merged with system folders after boot.
3. Try wiping cache between reboots and see if that changes any of your observations.
rk2612 said:
Some more thoughts for you to consider:
1. Have you tried this with the official TWRP recovery version 3.2.0-0?
2. Is there anything inside the folders that you see using the file manager after a regular boot? Folders of same name may exist in the boot ramdisk and these are merged with system folders after boot.
3. Try wiping cache between reboots and see if that changes any of your observations.
Click to expand...
Click to collapse
Good questions. They got me thinking more about how this could possibly work.
I had a look at the cache and there's definitely no copy of the system hiding there.
I also unpacked the ramdisk in the boot image and it had nothing in system. Furthermore, the boot position is only 64 MB, no where near enough to hold the system.
Then I installed Magisk so that I could browse around the phone's partitions and take copies.
I learnt two things from this:
1. If there's a second copy of the system there are only three partitions large enough to hold it (/proc/partitions shows the sizes in 1 kB blocks). The system is about 1 GB. There is space in the system partition (sde20) for 3 GB. There's also space in the data partition (sca15). And there's space in the major partition holding the modems (sdf).
I could eliminate the data partition by formatting it but restoring the internal storage (sdcard) is such a a pain.
So I'll just accept that there is space for a copy, but I'm unlikely to find out exactly where.
2. When I had Magisk installed installed and the system boot, I added a folder and file to /system/priv-app using a file manager (so not using TWRP). I then booted into recovery, flashed the stock boot image, and rebooted. I was expecting it to fail dm-verity (modified system) but it didn't. After booting up there's no evidence of the folder I added to priv-app.
And if I restore the Magisk boot image then the additions show up again.
I'm actually very impressed with how the stock system (kernel, recovery, system) protects itself from modification. Very cool!
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).