Database Info

need help - how to copy TWRP nandroid backup to device?

how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.

Latest TWRP has MTP mode.

but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB

You'll need to give us more information.
Why did it fail? Why did your phone stop booting?

1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop

gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.

how can you copy using twrp while in recovery? are you able to access your PC from recovery?

gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.

ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??

Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty

No. Do a full flash of userdata.img

Please explain
What would I achieve by flashing it?

gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.

Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working

gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.

I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5

gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup

FlashFire with HTC One A9?

Anyone used ChainFire's FlashFire with the One A9?
I've used it for backups successfully but have yet to restore anything with it (a little squeamish to do so :silly.
And I'll just add, if anyone has used it and could offer any tips or procedures that would be great.

FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
Click to expand...
Click to collapse
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?

theNdroid said:
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
Click to expand...
Click to collapse
Of course. Root is required to use FlashFire. I use Xposed as well, and I've had no problems updating via FlashFire.

CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Click to expand...
Click to collapse
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?

eelpout said:
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
Click to expand...
Click to collapse
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***

CSnowRules said:
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
Click to expand...
Click to collapse
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.

eelpout said:
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
Click to expand...
Click to collapse
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.

CSnowRules said:
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
Click to expand...
Click to collapse
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.

eelpout said:
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
Click to expand...
Click to collapse
Ok, this post will go a bit off topic. That being said, I can offer two courses of action. I take no responsibility for anything in this post.
Safest--almost no risk (my personal preference)
1. Backup your data partition, including internal SD via TWRP to ext SD or USB OTG drive. Flash the latest RUU from HTC. Boot stock and apply OTAs until there are no more updates available. Fastboot flash the latest TWRP, and finally restore your data and flash the latest SuperSU via TWRP. Reboot your fully updated, rooted A9 with all your data still intact.
A little risky and untested to my knowledge--could result in a hard brick if something partially fails. FLASHING BOOTLOADERS IN FLASHFIRE IS STILL ALPHA FOR HTC DEVICES!!! This may work with s-on...but may require s-off.
Your system partition must have never been mounted r/w for this to work.
2. Download the OTA zips for your phone from the first update available to the latest and the latest SuperSU and TWRP. Use FlashFire to do everything in one shot. Select allow flashing bootloaders in FlashFire settings, select your OTAs for installation from oldest to newest (don't select restore boot and recovery), select TWRP and SuperSU for installation, disable everroot and preserve recovery. Cross your fingers and timidly press flash... If all is successful, you should have the same end result as option 1.
I STRONGLY recommend the first method, but if you're feeling lucky and decide to try the second method, please share how it goes, since this post is FlashFire related and this would be the ultimate test of FlashFire for our devices.

For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.

NuShrike said:
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
Click to expand...
Click to collapse
The solution for problem 1 can be handled in TWRP. The files can be deleted via TWRP's file manager or the built in terminal, which may be easier for some people.
Also, the solution for the corrupted data and internal SD is to create an image of the data partition (just like the system image backup option). This can be done via dd in TWRP or adb. It requires a large amount of storage and it takes longer, but I've had to do it, since I use VIP Access by Symantec for work. A normal file based backup in TWRP breaks that app. This also keeps the pin/fingerprint data intact.
If we could have that implemented in a user friendly manner, that would be great, but I'm sure CaptainThrowback and Chainfire both have bigger issues to deal with. I could probably figure out a solution, but the work wouldn't be worth it for my own benefit, since I'm fluent with the Linux command line.

Root, TWRP and Flashing

I recently got an S7 (Exynos) SM-G930F and decided to root it. So I went with the typical CF-Auto-Root method... I used the latest ODIN with the correct auto root file and everything went well. I have root.
But then I noticed that I didn't have any recovery, so I installed TWRP Manager from the Play Store and flashed recovery with that. Everything works fine except for not having access to backup /Data, this was expected.
But despite everything pretty much working, I've read on a few threads here that I was supposed to wipe my phone after flashing TWRP. Now I've also read the TWRP install thread which doesn't mention anything about wiping my device, but it does offer another method of rooting the S7... Flash TWRP first using ODIN, then flash SuperSU and dm-verity/force encryption disabler.
So I have a couple of questions.
In the TWRP guides it mentions this: "By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!". I've never had this issue, does CF-Auto-Root or SuperSU resolve this issue?
Do I need to install the dm-verity/force encryption disabler?
If I do have to wipe my device, am I going for a standard (factory reset) wipe? Advanced wipe (if so, which partitions?) or format data?
Unless there's another way to gain full access to all partitions in order to perform a complete nandroid backup (including data)?
Basically, once I've completely backed up the S7 I'd like to install the Xposed Framework. Will installing this lose any data?

d3adm8n said:
I recently got an S7 (Exynos) SM-G930F and decided to root it. So I went with the typical CF-Auto-Root method... I used the latest ODIN with the correct auto root file and everything went well. I have root.
But then I noticed that I didn't have any recovery, so I installed TWRP Manager from the Play Store and flashed recovery with that. Everything works fine except for not having access to backup /Data, this was expected.
But despite everything pretty much working, I've read on a few threads here that I was supposed to wipe my phone after flashing TWRP. Now I've also read the TWRP install thread which doesn't mention anything about wiping my device, but it does offer another method of rooting the S7... Flash TWRP first using ODIN, then flash SuperSU and dm-verity/force encryption disabler.
So I have a couple of questions.
In the TWRP guides it mentions this: "By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!". I've never had this issue, does CF-Auto-Root or SuperSU resolve this issue?
Do I need to install the dm-verity/force encryption disabler?
If I do have to wipe my device, am I going for a standard (factory reset) wipe? Advanced wipe (if so, which partitions?) or format data?
Unless there's another way to gain full access to all partitions in order to perform a complete nandroid backup (including data)?
Basically, once I've completely backed up the S7 I'd like to install the Xposed Framework. Will installing this lose any data?
Click to expand...
Click to collapse
Of course you are going to want to flash .zips through your Recovery, but as you have recognised there is the DM-Verification that will stop you doing so. In order to get rid of the encryption you will have to firstly have to Factory Reset but as you know this will also delete all apps and data that you have on your Internal Storage.
Then, you need to flash a .zip called 'no-verity-encryption-opt' and this will apply a patch onto your boot so you can flash unknown images and zips through.
If you can't find this no verity zip, leave me your email and I'll try and send it to you.
Good luck!
Also, installing the Xposed Framework will not cause you to lose any of your data.

AzzyC said:
Of course you are going to want to flash .zips through your Recovery, but as you have recognised there is the DM-Verification that will stop you doing so. In order to get rid of the encryption you will have to firstly have to Factory Reset but as you know this will also delete all apps and data that you have on your Internal Storage.
Then, you need to flash a .zip called 'no-verity-encryption-opt' and this will apply a patch onto your boot so you can flash unknown images and zips through.
If you can't find this no verity zip, leave me your email and I'll try and send it to you.
Good luck!
Also, installing the Xposed Framework will not cause you to lose any of your data.
Click to expand...
Click to collapse
Thanks for the info.
I may have already done this, I honestly can't remember. Is there any way to check if I've already installed no-verity-encryption-opt? Because I am already able to install zips in Recovery, so far I've installed a SuperSU update and AdAway. Although I do get a fair amount of 'Failed/Unable to mount /data' messages which may suggest that these zip installs didn't actually work.
I guess I still need to factory reset? And I guess that also means rooting again and installing no-verity-encryption-opt, then finally Xposed?

d3adm8n said:
Thanks for the info.
I may have already done this, I honestly can't remember. Is there any way to check if I've already installed no-verity-encryption-opt? Because I am already able to install zips in Recovery, so far I've installed a SuperSU update and AdAway. Although I do get a fair amount of 'Failed/Unable to mount /data' messages which may suggest that these zip installs didn't actually work.
I guess I still need to factory reset? And I guess that also means rooting again and installing no-verity-encryption-opt, then finally Xposed?
Click to expand...
Click to collapse
I had the same error message you are facing right now. Can you let me know what values you see when you view the Data, System and Cache partition, after clicking on 'Partition Options' - If you're on the latest TWRP you can take screenshots by hitting the Power and Vol Down.
^^^IGNORE^^^
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL

AzzyC said:
I had the same error message you are facing right now. Can you let me know what values you see when you view the Data, System and Cache partition, after clicking on 'Partition Options' - If you're on the latest TWRP you can take screenshots by hitting the Power and Vol Down.
^^^IGNORE^^^
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
Hey man, i'm having that problem.
I want to root my phone but i am not able to acess Internal Storage, on twrp its showing 0mb.
I did what you says in this post but i always have caught in ''Encrypetd phone'' or something like this.
What are the steps? 1- format data (then deletOS) and then? Can you help me please?

[H918] TWRP Flashable Stock Firmwares

with little to no activity lately for the LGV20, specifically the H918 T-Mobile variant I decided to look into creating a TWRP flashable package for the recent H91810k release. these zips flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! I've tested this on my device after backing up and so far so good on the latest 10k release. please report back in this thread on whether it was successful or not.
NOTE: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
Instructions:
download H91810k.zip file listed below and put on microSD card
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
flash your choice of root, either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v11.6 is recommended.
reboot
profit!
Download:
H91810k
md5sum: ab181ec82315b656a7af48f0017f4e8c - version 1 with misc partition included (SORRY)
md5sum: 8ad07ae70c4299b3ea6e2bf747dbec1c - version 2 with misc partition removed
Flashing Process:
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)

First! This is sweet!

I just tried this and it works great. I prefer to use the stock rom and to get a rooted 10k that doesn't have any known security vulnerabilities is awesome. Some notes for others:
Copy SuperSU to the external SD card and flash it after this zip in TWRP.
Make sure to select all the partitions for back up in TWRP.
On the first boot after flashing, the phone will reboot by itself. This is probably normal. You will get an "Android is upgrading..." white screen. This is expected since the cache was wiped by the script. This will take a while to complete. Even when you get back into the system, an "Android is upgrading..." message will appear in the notification bar.
Clarification: The data on /sdcard doesn't get wiped, but it's a good idea to back it up just in case. The TWRP backup of the data partition does NOT include this stuff in the backup.
I had Busybox installed before, but I didn't have to reinstall it after the flash. I'm not sure why. I assumed that wiping out system would have required me to re-install Busybox. I guess Busybox doesn't get installed on the system partition?
Adblocking using apps like AdAway need to be rerun since the hosts.txt file will be reset.
Ignore the stuff under "Process" in the OP. It's explaining what the script does. You don't have to do any of that.
The script disables the updater software. You never have to worry about the next stock release causing you trouble!

I am having problems downloading this? I tried twice and it downloads but I cant find it?
Sent from my LG-H918 using XDA-Developers Legacy app

Big thanks for this! Have been patiently waiting for a 10k stock rom with firmware!
Sent from my LG-H901 using Tapatalk

what the hell man! I lost my twrp!!!! Now I only see stock recovery! DONT INSTALL THIS ROM!!!!

Hsinghr said:
what the hell man! I lost my twrp!!!! Now I only see stock recovery! DONT INSTALL THIS ROM!!!!
Click to expand...
Click to collapse
pretty sure if that's the case then YOU did something wrong... the recovery image is NOT in this package at all so TWRP is left untouched.

jason504 said:
I am having problems downloading this? I tried twice and it downloads but I cant find it?
Sent from my LG-H918 using XDA-Developers Legacy app
Click to expand...
Click to collapse
what are you using to download?

I HAD TWRP and and after a while it went back to stock recovery

You did something other than flash the rom in this thread. Maybe you're confusing this thread with this one? https://forum.xda-developers.com/v20/how-to/t-mobile-lgv20-h91810k-kdz-t3618021
If that's what you flashed, you will definitely end up with stock recovery and no root.

I've tried to install this ROM but it skips through each of partition rather quickly and it never installs. I'm on H91810j with root and TWRP installed. Any ideas? Thanks.

ctalbot said:
I've tried to install this ROM but it skips through each of partition rather quickly and it never installs. I'm on H91810j with root and TWRP installed. Any ideas? Thanks.
Click to expand...
Click to collapse
Did you have an external MicroSD card installed in your phone? Are you using that external MicroSD card to store the files to be flashed? What version of TWRP are you using?

Yep, on microsd. TWRP 3.0.2-1

OP says 10k, but you're on 10j?

Correct, currently on 10j

ctalbot said:
I've tried to install this ROM but it skips through each of partition rather quickly and it never installs. I'm on H91810j with root and TWRP installed. Any ideas? Thanks.
Click to expand...
Click to collapse
I would verify the md5sum of the downloaded file you have to what it should be, which is ab181ec82315b656a7af48f0017f4e8c

dimm0k said:
what are you using to download?
Click to expand...
Click to collapse
I got it I had to download it on my PC then send it to my phone. I flashed it and everything went fine thanks. I don't know why I was having problems downloading on my phone.
Sent from my LG-H918 using XDA-Developers Legacy app

-edit- bad cuestion, sorry

dimm0k said:
I would verify the md5sum of the downloaded file you have to what it should be, which is ab181ec82315b656a7af48f0017f4e8c
Click to expand...
Click to collapse
Hmm...the zip I downloaded has a checksum of 76bbccc0c9640d7f0005b529abf3873a and it uncompresses without issue!? Was there an earlier release?
Going to download again...

Hsinghr said:
I HAD TWRP and and after a while it went back to stock recovery
Click to expand...
Click to collapse
Can you provide more detail on what you did? You made a pretty strong statement that you lost TWRP.
Did you follow and flash what was written by the OP? Did you do flash something else after flashing what was provided by the OP? Or did you really have TWRP the whole time?
Not looking to cause an an argument but your 2 posts in this thread have made me hesitate flashing.
Sent from my LG-H918 using Tapatalk

Unable to make nandroid backups due to error 255

Hello guys/gals!
I'm reaching out because I have not been able to make a nandroid backup on my OnePlus 7 Pro. When I attempt to do so in TWRP I get a error 255. I am running Stock OOS Stock rim & stock Kernel.
The only "mod" that I am using is Magisk. Can anyone please help me, I have been afraid to run/flash any mods because I don't want to screw something up and then not be able to restore from a previous backup so aside from Magisk my phone is at complete stock.
I only encounter error 255 when attempting to backup the data partition, all the other partitions backup just fine.
Please & thank you!

Try with latest .65 version from Mauronofrio

peteus said:
Try with latest .65 version from Mauronofrio
Click to expand...
Click to collapse
I'm already running it. During testing I discovered that if I boot twrp from pc via fastboot then I can then backup the data partition with no problem...but,if I boot twrp as usual then i can't backup the data partition because as I have previously mentioned, I get error 255.
Very weird... Any help would be greatly appreciated.
Thanks for trying peteus!

XBlackChaosX said:
I'm already running it. During testing I discovered that if I boot twrp from pc via fastboot then I can then backup the data partition with no problem...but,if I boot twrp as usual then i can't backup the data partition because as I have previously mentioned, I get error 255.
Very weird... Any help would be greatly appreciated.
Thanks for trying peteus!
Click to expand...
Click to collapse
I also had this problem, solved it using this post:
https://forum.xda-developers.com/on...tion-duplicated-google-play-services-t3953839
It was fairly straightforward on which account to remove for me.

If you've ever used the Parallel Apps feature, it's because of this. The Parallel Apps feature when using a cloned app, creates a separate folder for your cloned apps and TWRP can't distinguish what or where this folder is and fails when it gets to a certain point in the backup. There's a way to remove the folder to get a successful backup, I just can't remember how.

To successfully do nandroid backup only select the following in twrp ??
BOOT
DATA
SYSTEM IMAGE
VENDOR IMAGE

jkent900 said:
I also had this problem, solved it using this post:
https://forum.xda-developers.com/on...tion-duplicated-google-play-services-t3953839
It was fairly straightforward on which account to remove for me.
Click to expand...
Click to collapse
Thank you! I saved this in case I ever have 255 error.