Hello folks,
Now that Pixel XL is not going to get any updates from google, I am ready to switch over to the ROMs. I thought I should take a nandroid backup before proceeding. This device has unlocked bootloader and rooted with Magisk. Its running September update. I didn't install the October update.
Booted Pixel XL into TWRP using fastboot. Used twrp-3.3.1-3-marlin.img. When I try to backup, I get an error
Failed to mount '/system' (invalid argument)
Failed to mount '/vendor' (invalid argument)
It manages to generate the digest but again gives an error, failed to mount system. Backup failed.
I even restored the phone to factory settings and I get the same error.
Is there anything else I should be checking?
Edit: Tried older TWRP, 3.3.1.0. Now I get an error with the same two, device or resource is busy.
Thanks in advance.
You probably only need to backup your data (which may require you to remove your screen lock before boring into TWRP). Optionally backup the boot partition so you have any custom kernel and Manish backed up as well.
The system, vendor, and other partitions can be restored by fastboot. Less than ideal, but that's what I've been doing.
NZedPred said:
You probably only need to backup your data (which may require you to remove your screen lock before boring into TWRP). Optionally backup the boot partition so you have any custom kernel and Manish backed up as well.
The system, vendor, and other partitions can be restored by fastboot. Less than ideal, but that's what I've been doing.
Click to expand...
Click to collapse
Thanks. So you started having this problem with Android 10 only or it was before android 10 as well?
The second question I have, if it won't mount system, is that partition the same as the data, because android has Slot A and B. This is the first phone I am dealing with that has 2 slots. Any idea if this create any issues at the time of ROM / Lineage OS install?
fuzzychicken said:
Thanks. So you started having this problem with Android 10 only or it was before android 10 as well?
The second question I have, if it won't mount system, is that partition the same as the data, because android has Slot A and B. This is the first phone I am dealing with that has 2 slots. Any idea if this create any issues at the time of ROM / Lineage OS install?
Click to expand...
Click to collapse
Myself I haven't tried mounting either as writable, but read only for system is fine. I've never flashed a custom rom. I do see posts from other people with the issue though.
There is only one data partition, and it is completely separate from system etc, and slots don't affect it.
Just follow the instructions for the custom rom you end up installing.
Related
Q&A for [REF] LVM Partition Remapping
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [REF] LVM Partition Remapping. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
When I try flashing the setuplvm, it fails with error message "unable to mount /data." I am using TWRP 2.8.0.1 and have tried wiping the data. Is there anything I can do to fix this issue?
alpha_5 said:
When I try flashing the setuplvm, it fails with error message "unable to mount /data." I am using TWRP 2.8.0.1 and have tried wiping the data. Is there anything I can do to fix this issue?
Click to expand...
Click to collapse
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Entropy512 said:
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Click to expand...
Click to collapse
I have the same problem. I had the ZIP on external SD with omni nightly and gapps.
Same error and no LVM.
Try the twrp from omni thread. Flash setuplvm and than update to twrp 2.8.0.1.
jebulol said:
I have the same problem. I had the ZIP on external SD with omni nightly and gapps.
Same error and no LVM.
Click to expand...
Click to collapse
Also, the other question is: Did you reboot recovery after flashing setuplvm???
Entropy512 said:
Also, the other question is: Did you reboot recovery after flashing setuplvm???
Click to expand...
Click to collapse
Yup.
I flashed TWRP 2.8.0.1, tried to install setuplvm and got "unable to mount /data." Rebooted and flashed latest Omni and realized it didnt work.
Entropy512 said:
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Click to expand...
Click to collapse
Yes, I am flashing from the external SD card. Here is what I see when I try it.
E: Could not mount /data and unable to find crypto footer.
Updating partition details...
E: Unable to mount '/data'
Full SELinux support is present.
Installing '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'...
Checking for MD5 file...
Skipping MD5 chck: no MD5 file found
Unmounting data partition
Extracting LVM tools
Unmounting sdcard partitions
Creating LVM physical volumes
Adding LVM physical volumes to volume group
Creating userdata logical volume
Rescanning and activationg LVM volumes
Formatting LVM volume
E: Error executing updater binary in zip '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'
Error flashing zip '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'
Updating partition details...
E: Unable to mount '/data'
I will also add that if I go to "Mount" in TWRP I am unable to select "data." The phone boots up fine and seems to be working properly otherwise.
Hi,
This happened to my X9076 too about a week back and that was due to my mistake of installing the rom right away without rebooting the recovery first.
If you also missed that very crucial part, I'm pretty sure all you have to do is clear the data, run the reversal LVM zip, boot to recovery again, run the partition mapping, then boot recovery one more time and after that just install the rom + gapps as usual.
I however accidentally booted up the system directly after the failed install which got me the Android is encrypting splash screen for 1 minute or 2 then telling me it failed and booted. After that TWRP couldn't access the /DATA at all.
I eventually got around it by flashing stock recovery and colorOS. The newer releases didn't work though, I took the oldest ones from OPPOforums and that worked.
After that I could flash back to TWRP, run the partitioning as supposed to and install Omni.
i've been wanting to try out omni with lvm for a while, but is lvm complete?
i also read that there's some issues with twrp, i'm a bit confused, which twrp version do i use?
i'm currently running a rom with an unified partition
i just have to return to split layout then flash the setup lvm in latest twrp recovery?
thanks in advance
binaryfalcon said:
i've been wanting to try out omni with lvm for a while, but is lvm complete?
i also read that there's some issues with twrp, i'm a bit confused, which twrp version do i use?
i'm currently running a rom with an unified partition
i just have to return to split layout then flash the setup lvm in latest twrp recovery?
thanks in advance
Click to expand...
Click to collapse
There have been some odd issues with the following:
1) setuplvm does not play nice with newer TWRP. I have some guesses why... In a few places in the Omni thread I gave manual instructions for doing the conversion in an ADB shell, those will work
2) For some reason, the app "TWRP Manager" flashes a bogus version of TWRP that has issues
Other than those two issues, LVM is complete, I've been running it for two months now. I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Entropy512 said:
There have been some odd issues with the following:
1) setuplvm does not play nice with newer TWRP. I have some guesses why... In a few places in the Omni thread I gave manual instructions for doing the conversion in an ADB shell, those will work
2) For some reason, the app "TWRP Manager" flashes a bogus version of TWRP that has issues
Other than those two issues, LVM is complete, I've been running it for two months now. I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Click to expand...
Click to collapse
appreciate the response
what do I need flash?
which twrp version do I use?
It's just a compatible twrp then setuplvm then flash omni?
any help appreciated, can't wait to try it out
Entropy512 said:
I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Click to expand...
Click to collapse
I downloaded TWRP from http://techerrata.com/browse/twrp2/find7 and flashed using fastboot. Still had issues.
jebulol said:
I downloaded TWRP from http://techerrata.com/browse/twrp2/find7 and flashed using fastboot. Still had issues.
Click to expand...
Click to collapse
That should work fine on a device that is already in the LVM configuration. It does have issues with setuplvm currently though.
Someone who had issues with setuplvm and TWRP 2.8.0.1 finally posted a recovery.log - For some reason, TWRP 2.8.0.1 is not unmounting the sdcard partition, which causes issues when setuplvm tries to convert that partition into an LVM PV.
From now on, anyone with issues with setuplvm (or other issues within recovery) needs to post /tmp/recovery.log - This can be obtained via ADB with:
Code:
adb pull /tmp/recovery.log
when you are in TWRP after you've tried (and failed) to do whatever you're trying to do
Why? This provides MUCH more information about what went wrong than just the basic screen results/console output such as what alpha_5 posted a few posts back.
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
---------- Post added at 03:47 PM ---------- Previous post was at 03:17 PM ----------
Wendigogo said:
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
Click to expand...
Click to collapse
I tried and it's written in TWRP recovery : factory reset doesn't wipe personal data (in /data/media).
AWESOME JOB !
Wendigogo said:
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
---------- Post added at 03:47 PM ---------- Previous post was at 03:17 PM ----------
I tried and it's written in TWRP recovery : factory reset doesn't wipe personal data (in /data/media).
AWESOME JOB !
Click to expand...
Click to collapse
Correct. It's the same way all Nexus devices since the GNex (and most other devices) are - a factory reset does an rm -r of everything outside of /data/media instead of formatting the whole partition.
Of course, it's a good idea to periodically back things up in case the filesystem gets hosed to the point of needing a format. (Extremely rare on ext4 these days, common for f2fs in my experience)
Entropy512 said:
Correct. It's the same way all Nexus devices since the GNex (and most other devices) are - a factory reset does an rm -r of everything outside of /data/media instead of formatting the whole partition.
Of course, it's a good idea to periodically back things up in case the filesystem gets hosed to the point of needing a format. (Extremely rare on ext4 these days, common for f2fs in my experience)
Click to expand...
Click to collapse
Yes, always following the 3 main rules when playing with my devices :
1- Make a backup
2- Make a backup
3- Make a backup
And as I do that oftenly my backups are never outdated.
Enjoy!
Setting up LVM on oppo find 7 from a custom rom?
Hello,
I am tired of my app space always out (I can't update apps now and have limited my apps to about 1/2 of what I normally would have).
From quite a ways back, I had installed Gummy, I think M4, right around when they stopped supporting the rom.
My question is how would I set up LVM from this point in time? I'm unsure how to revert back to any colorOS system (and I would prefer never to go back that way anyway, however I do see cos1.2 in a restore kernal section). I have TWRP 2.7.1.0 currently in use.
update: I see that twrp from the OS, can download the latest TWRP so I am currently DL and will try to install 2.8.7.1. If this successfully gets installed, can I flash the LVM program directly, then a 5.x or later D.U., Nameless, or OMNI rom afterwards?
Your help would be greatly appreciated as I have put this off for way too long however understand it's an amazing phone w/lots of hardware capability.
Update: downloading 2.8.7.1 from the app's interface didn't work well. I had to get back into flashify and install from local file version 2.8.5.0. When I get into bootup>TWRP, i have a split screen where the left side is scrolling slowly downwards. All functionality is normal just screen split flipping is annoying.
Hi.
Anyone give me working download link for "set up LVM" and "remove LVM" flashable zip please.
I can't download them from oppo forum.
Hi Entropy512, All,
I have installed succesfully LVM with the last OmniRoma Available but everytime I try to download something or take a picture with the camera, It says "For use camera, insert and SD Card". I checked the threat and I do not find any clue of how to solve this. Probably I miss something in the configuration process.
Any help?
Thanks in advance
Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks
Hello all-
In the process of trying to upgrade to OOS 5. I made sure to make a backup of the entire system (system image) in TWRP before proceeding. I also backed up the Boot image and Modems. I had the entire OOS 5 rom ready to flash but before doing so I elected t wipe Dalvik/Cache, Cache, Data & System as I always thought you have to do a fresh clean install when changing versions (7.1.1 to 8.0). The first error I encountered was that it couldn't flash the file. Then when I tried to restore my backup...it does the process with no errors yet when I try to reboot I am told no OS installed. What has happened and what can I do since I always make these backups to be safe?
Thanks all!
Plug your phone on a PC (with the phone in recovery mode), move your backup (sdcard/TWRP/backup) on your PC to keep it safe. Next follow the mega unbrick method 2 (just Google it) on OnePlus forum, update your phone to the version that you were and reflash TWRP and copy your backup from your PC to your phone (in the same location than before) and try to restore your backup.
Error installing OOS 5
Thanks all! I thought a System Image backup was all I needed and had no idea I also had to restore my Boot Image backup. Once I restored that backup I was good to go. Oddly though I didn't have all my apps and data on the phone like I thought the system image backup would have. Honestly I don't care as long as I have a phone again.
On a side note, I have the full OOS 5 ROM on my phone and when I try to flash it I receive an error. The error message states as if the file os for a One Plus 3 and that it cant confirm what my device is? I have always downloaded the full ROMS from OP site and nver had issues upgrading in the past. Any ideas? Does the version of my TWRP matter? Please advise.
DroidJay123 said:
Thanks all! I thought a System Image backup was all I needed and had no idea I also had to restore my Boot Image backup. Once I restored that backup I was good to go. Oddly though I didn't have all my apps and data on the phone like I thought the system image backup would have. Honestly I don't care as long as I have a phone again.
On a side note, I have the full OOS 5 ROM on my phone and when I try to flash it I receive an error. The error message states as if the file os for a One Plus 3 and that it cant confirm what my device is? I have always downloaded the full ROMS from OP site and nver had issues upgrading in the past. Any ideas? Does the version of my TWRP matter? Please advise.
Click to expand...
Click to collapse
System image is rarely useful, it's a full Byte by Byte backup of the system partition ( meaning even the empty Bytes are saved). System partition means that boot one isn't concerned. And system partition means that data partition isn't concerned either, so no user apps or data.
Better to stick to /boot /system and /data backup.
You must have latest official TWRP 3.2 for Oreo ROMs. Or blue_spark latest (8.61 version see blue_spark kernel thread OP)
Striatum_bdr said:
System image is rarely useful, it's a full Byte by Byte backup of the system partition ( meaning even the empty Bytes are saved). System partition means that boot one isn't concerned. And system partition means that data partition isn't concerned either, so no user apps or data.
Better to stick to /boot /system and /data backup.
You must have latest official TWRP 3.2 for Oreo ROMs. Or blue_spark latest (8.61 version see blue_spark kernel thread OP)
Click to expand...
Click to collapse
Thanks man! Good information to have moving forward. No sense in backing up partitions that are not useful and only take up space. Can I update to TWRP 3.2 right in the TWRP app or should I download image and flash within TWRP? I am currently on SU 2.82....is that compatible with Android O?
DroidJay123 said:
Thanks man! Good information to have moving forward. No sense in backing up partitions that are not useful and only take up space. Can I update to TWRP 3.2 right in the TWRP app or should I download image and flash within TWRP? I am currently on SU 2.82....is that compatible with Android O?
Click to expand...
Click to collapse
Yes update from within TWRP. I think superSu 2.85 should be good or Magisk 14.0
I would like to recover a video from the internal memory on my (unrooted) Android A5 (2017) [A520F]. I was able to flash TWRP and planning to root my device, so that I can use an external tool to scan the internal storage for deleted files. However, I can see in the TWRP log that it Failed to mount /data (invalid arguments). I'm not 100% sure, but I think that this is connected to the fact that I can't get any custom ROM installed. I used external tools like odin, flashed multiple custom ROMs, Lineage OS, I tried SuperSu, no-verity-no-encrypt, RMM-State Bypass etc etc. I can't get anything to boot. Most of the times my phone just freezes at the boot animation.
I'm not even able to format the /data partition (I wouldn't want to, because I'm trying to restore data, but still.) I also can't flash the official firmware with odin. It just fails in the end. The only way to get my phone back to it's normal state is try to flash the official firmware using odin (which fails), then flash A5-SM-A520F-TWRP-3.0.2.0.tar (AP)
My actual question is How can I get my deleted video back?
Should I use this guide? https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I don't encounter any of the three points listed under "How to know if you are locked".
I faced the same issue too, and the only way I could access /data with TWRP was changing the file system to EXT2 and then back to EXT4. This will delete all your data so probably your video too, but this is the only way to mount /data in TWRP. After mounting, you can try to install HadesROM or something that you can use.
Astone85 said:
I would like to recover a video from the internal memory on my (unrooted) Android A5 (2017) [A520F]. I was able to flash TWRP and planning to root my device, so that I can use an external tool to scan the internal storage for deleted files. However, I can see in the TWRP log that it Failed to mount /data (invalid arguments). I'm not 100% sure, but I think that this is connected to the fact that I can't get any custom ROM installed. I used external tools like odin, flashed multiple custom ROMs, Lineage OS, I tried SuperSu, no-verity-no-encrypt, RMM-State Bypass etc etc. I can't get anything to boot. Most of the times my phone just freezes at the boot animation.
I'm not even able to format the /data partition (I wouldn't want to, because I'm trying to restore data, but still.) I also can't flash the official firmware with odin. It just fails in the end. The only way to get my phone back to it's normal state is try to flash the official firmware using odin (which fails), then flash A5-SM-A520F-TWRP-3.0.2.0.tar (AP)
My actual question is How can I get my deleted video back?
Should I use this guide? https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I don't encounter any of the three points listed under "How to know if you are locked".
Click to expand...
Click to collapse
So you're saying you cannot boot to system?
Just moved from an old Galaxy S6 to the Pixel 2 Xl and I am confused about what partitions i need to select to make a proper backup with TWRP.
Is boot/sytem/data enough?
I dont know what to do with the remaining partitions: system image/vendor/vendor image.
Boot, System, Data is all I ever backup, and I've never had an issue when restoring :good:
Az Biker said:
Boot, System, Data is all I ever backup, and I've never had an issue when restoring :good:
Click to expand...
Click to collapse
I'm getting an error every time I try running a backup using TWRP. There always seems to be a createTarFork() error, specifically for the data partition. How did you work around this? Have tried doing doing the backup with the data partition both mounted and unmounted, still get the same thing,
Running TWRP 3.3.0-0
Kudos in advance
-D
ProoN said:
I'm getting an error every time I try running a backup using TWRP. There always seems to be a createTarFork() error, specifically for the data partition. How did you work around this? Have tried doing doing the backup with the data partition both mounted and unmounted, still get the same thing,
Running TWRP 3.3.0-0
Kudos in advance
-D
Click to expand...
Click to collapse
I believe things and processes have changed with Android 10 (Q) as far as TWRP and backups.
Post your question here as it is permitted here by the OP and there is a lot of help here.