Related
Hi,
I unlocked and installed TWRP recovery yesterday, and then I flashed CM10.2. All went without problems.
Now I tried to make a backup from within TWRP (2.6.3.0), but it always ends with an error;
Backing up System is fine.
Backing up Data is fine.
But, when Backing up Boot...it ends with the error:
E:Backup file size for '/data/media/0/TWRP...........
I'm 100% sure I installed the correct recovery (-4,2-version)
I also see this on the terminal screen in TWRP:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Any ideas?
realgreef said:
Hi,
I unlocked and installed TWRP recovery yesterday, and then I flashed CM10.2. All went without problems.
Now I tried to make a backup from within TWRP (2.6.3.0), but it always ends with an error;
Backing up System is fine.
Backing up Data is fine.
But, when Backing up Boot...it ends with the error:
E:Backup file size for '/data/media/0/TWRP...........
I'm 100% sure I installed the correct recovery (-4,2-version)
I also see this on the terminal screen in TWRP:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
Any ideas?
Click to expand...
Click to collapse
I always have gotten those last two error and I thought the latest TWRP was supposed to have fixed them.
Make sure you have the correct filesystems mounted before starting the backup and you have enough space free on them.
I'm having a similar issue but with restoring any backups. The "boot" partition fails the recovery, but if I choose to restore the other three positions (system cache and data) it goes through.
In "mount" the only options are system (default unchecked), cache, data, Micro SDcard, and SD-Ext (unchecked).
Even with all checked (except sd-ext, which is not able to be checked) /boot partition size is not found.. twrp 2.6.3.0 was on grimlock cm10.2 and got bootloop tried flashing, wiping caches.
I flashed cm 10.2 over the partial restore and got it to work. Flashed twrp again, but the boot and recovery errors remained, thinking of going down to 2.6.1.0, maybe.
Anyone have a solution or idea?
DaringDomino3s said:
I'm having a similar issue but with restoring any backups. The "boot" partition fails the recovery, but if I choose to restore the other three positions (system cache and data) it goes through.
In "mount" the only options are system (default unchecked), cache, data, Micro SDcard, and SD-Ext (unchecked).
Even with all checked (except sd-ext, which is not able to be checked) /boot partition size is not found.. twrp 2.6.3.0 was on grimlock cm10.2 and got bootloop tried flashing, wiping caches.
I flashed cm 10.2 over the partial restore and got it to work. Flashed twrp again, but the boot and recovery errors remained, thinking of going down to 2.6.1.0, maybe.
Anyone have a solution or idea?
Click to expand...
Click to collapse
Instead of restoring the boot partition, you could flash the target ROM to the the boot partition you want and the restore the data and cache and system.
I am having this problem on my tf300t with twrp 2.6.3.0 running cm-10.2. Is there a more recent version that fixes this for this unit?
Also, with 2.6.3.0 (if there is no tf300t upgrade) can I install cm-11?
kmoffat said:
I am having this problem on my tf300t with twrp 2.6.3.0 running cm-10.2. Is there a more recent version that fixes this for this unit?
Also, with 2.6.3.0 (if there is no tf300t upgrade) can I install cm-11?
Click to expand...
Click to collapse
Unofficial twrp 2.6.3.2 has this fixed and can install cm11. 2.6.3.0 will not work with kitkat ROMs; look in scannos omnirom thread for the twrp download.
Sent from my GS3 on AOSB 4.4.2 using Tapatalk 4
fixed backup problem
I saw a post elsewhere that has fixed my backup problem. Uncheck data, run backup (success) then recheck data, run backup (success!)
Thought to share.
QUOTE:
Walter DeMoss
• 22 days ago
−
I have asus tf300t with twrp 2.6.3.0-4.2 and cm10.2 stable. All works well but backup fails every time. Backup of system and data seems to go well and generate the MD5 sum. But then immediately it fails.
Have tried backing up to internal and external. Same every time. What am I doing wrong?
Thanks in advance.
•
Reply
•
Share ›
Avatar
Jason Lenz Walter DeMoss
• 9 days ago
−
I was having the same issue trying to backup the stock rom and it was driving me crazy. When I went to backup and left the default partitions selected (System and Data checked with Cache unchecked) it tried to backup three partitions!? It looks like the third partition it was trying to backup was the Boot partition and it was getting some sort of zero file size error at the end of the backup process. I'm not sure why it was trying to backup Boot. Anyway I retried backup only checking the "System" partition, and it correctly backed up only 1 partition. I then tried again selecting System and Data (same as what showed up with the original default) and this time it correctly backed up two partitions. Must have been some leftover spurious setting that was correctly updated when I started manually selecting the partitions. Hope that helps.
1
•
Reply
•
Share ›
Avatar
Walter DeMoss Jason Lenz
• 9 days ago
−
Jason,
Thanks, that was exactly it. Well done.
Walt
UNQUOTE
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
http://teamw.in/project/twrp2/97
ebildude123 said:
Unofficial twrp 2.6.3.2 has this fixed and can install cm11. 2.6.3.0 will not work with kitkat ROMs; look in scannos omnirom thread for the twrp download.
Click to expand...
Click to collapse
Sorry, pretty new... So, I would need to flash this using fastboot? but the format is different when I unzip it. I see a "recovery.img" file in the unzipped folder, along with a META-INF folder containing files. Do I just use fastboot to flash the "recovery.img" file? Do I need to move this to a folder containing fastboot files? Should I rename it to twrp-2.6.3.2?
Also, to revert I would need to flash 2.6.3.0 first?
Thanks again!
kmoffat said:
Sorry, pretty new... So, I would need to flash this using fastboot? but the format is different when I unzip it. I see a "recovery.img" file in the unzipped folder, along with a META-INF folder containing files. Do I just use fastboot to flash the "recovery.img" file? Do I need to move this to a folder containing fastboot files? Should I rename it to twrp-2.6.3.2?
Also, to revert I would need to flash 2.6.3.0 first?
Thanks again!
Click to expand...
Click to collapse
You flash the img file via fastboot or you can flash the zip file in an older version of TWRP, both assuming your bootloader is up to date. To flash old JB ROM, reflash 2.6.3.0 TWRP.
Thanks! (no thanks button in tapatalk....)
Sent from my TF300T using Tapatalk
kmoffat said:
Thanks! (no thanks button in tapatalk....)
Click to expand...
Click to collapse
There is!
Just select the post by touching it, then use the thumb-up icon on the top-right of the screen.
Sent from my TF300T using Tapatalk
Hello,
I am using TWRP 2.5.0.0 but I'm not able to make any nandroid backups of SD-EXT partition made by TWRP itself.
Sd-Ext mounts successfully but whenever i try to do a nandroid ,it successfully backups all partitions except Sd-Ext.
And it dosen't fix permissions also.I have attached the recovery log if it helps in solving the problem.
With TWRP 2.5.0.0 it shows Backup Completed in '0' seconds.
With TWRP 2.4.4.0 it shows backup failed,the same case is with TWRP 2.6
sushant18596 said:
Hello,
I am using TWRP 2.5.0.0 but I'm not able to make any nandroid backups of SD-EXT partition made by TWRP itself.
Sd-Ext mounts successfully but whenever i try to do a nandroid ,it successfully backups all partitions except Sd-Ext.
And it dosen't fix permissions also.I have attached the recovery log if it helps in solving the problem.
With TWRP 2.5.0.0 it shows Backup Completed in '0' seconds.
With TWRP 2.4.4.0 it shows backup failed,the same case is with TWRP 2.6
Click to expand...
Click to collapse
Change the reovery I have heard this problem of twrp not bcking up sd ext.. In some device it works..
Change the recovery..
same faced....
shubhojit89 said:
Change the reovery I have heard this problem of twrp not bcking up sd ext.. In some device it works..
Change the recovery..
Click to expand...
Click to collapse
i faced the same problem...in twrp while doing restore...from that i'm using cwm
Yeah ,switching to CWM worked.
Thanks.
Twrp Error
The problem was with the auto backup name,whenever I changed the name it gave me the error, just not giving a manual name worked fine for me.
Hi, I have recently tried to revert my Moto G from Cyanogenmod to stock firmware using a zip file I downloaded called "RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.modaco.r3". That got me stuck in a boot loop so I tried to boot into recovery, which had been uninstalled, so I reinstalled twrp from my computer.
I then tried to reinstall Cyanogenmod 12 but it said it couldn't mount storage and data and failed every time. Please help me because I don't think my parents are going to be getting me a new phone anytime soon because i'm on a contract.
Phone
-Moto G (falcon)
-Recovery = TWRP
-Bootloop
EDIT: Does anyone know how to fix the no service problem?
Try flashing the Retail GB 4.4.4 using fastboot or mfastboot.
mrbrokenphone said:
Hi, I have recently tried to revert my Moto G from Cyanogenmod to stock firmware using a zip file I downloaded called "RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.modaco.r3". That got me stuck in a boot loop so I tried to boot into recovery, which had been uninstalled, so I reinstalled twrp from my computer.
I then tried to reinstall Cyanogenmod 12 but it said it couldn't mount storage and data and failed every time. Please help me because I don't think my parents are going to be getting me a new phone anytime soon because i'm on a contract.
Phone
-Moto G (falcon)
-Recovery = TWRP
-Bootloop
Click to expand...
Click to collapse
In twrp you have to format data partition
Remember wiping is different from format
After format it will mount data partition and flash whatever you want it will work
Sent from falcon
PRESS THANKS IF HELPED?
sjandroiddeveloper said:
In twrp you have to format data partition
Remember wiping is different from format
After format it will mount data partition and flash whatever you want it will work
Sent from falcon
PRESS THANKS IF HELPED
Click to expand...
Click to collapse
Thanks, I wiped the data. When I tried to install CyanogenMod again, it said:
Installing '/sdcard/cm.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package supports bootloader(s): 0x4118, 0x4119; this device has bootloader 0x4113.
E: Error executing updater binary in zip '/sdcard/cm.zip'
Error flashing zip '/sdcard/cm.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/system'
...done
The install failed but took longer than my other attempts before your advice. Is this good or bad?
mrbrokenphone said:
Thanks, I wiped the data. When I tried to install CyanogenMod again, it said:
Installing '/sdcard/cm.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package supports bootloader(s): 0x4118, 0x4119; this device has bootloader 0x4113.
E: Error executing updater binary in zip '/sdcard/cm.zip'
Error flashing zip '/sdcard/cm.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/system'
...done
The install failed but took longer than my other attempts before your advice. Is this good or bad?
Click to expand...
Click to collapse
It says your bootloader is outdated, you have a kitkat bootloader, for newer versions of cyanogenmod-based lollipop ROMs you need the lollipop bootloader, wich is 41.18 for the versions XT1032,XT1033,and google play edition of motorola, and 41.19 for the CDMA version of the phone. You can search in Original development thread of CM12 on how to upload the bootloader the safest way, because it's the most easiest and risky way to brick your phone permanently. In the thread you have precise instructions on how to do that the most safe way, so i won't write any tutorials to you here.
Good luck and hope i helped!/
mrbrokenphone said:
Thanks, I wiped the data. When I tried to install CyanogenMod again, it said:
Installing '/sdcard/cm.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package supports bootloader(s): 0x4118, 0x4119; this device has bootloader 0x4113.
E: Error executing updater binary in zip '/sdcard/cm.zip'
Error flashing zip '/sdcard/cm.zip'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/system'
...done
The install failed but took longer than my other attempts before your advice. Is this good or bad?
Click to expand...
Click to collapse
The installation took longer because now the phone was able to mount data partition, which is obviously a good thing
Your error is because of older bootloader
U can either update the bootloader which I would suggest is better option or you can install a nightly older than 24th March which is compatible with even older bootloader
PS : I told you to format and not wipe, what did you do exactly ?
Sent from falcon
PRESS THANKS IF HELPED?
Howdy folks! New to android/honor 8 and I've been fiddling with it some. So far I've rooted, installed TWRP, SU and Xposed successfully. I've been trying to make a nandroid before completely ****ing up my device, but each time I try I get errors before completion...mainly at the end of the backup I get an error 255 or an error opening the backup directory (internal).
Anyone successfully back up their honor 8 with TWRP?
Appreciate any advice!
I have a copy of my stock rooted ROM with Xposed. What error are you getting? I'm backing mine up to the External SDcard.
Ascertion said:
I have a copy of my stock rooted ROM with Xposed. What error are you getting? I'm backing mine up to the External SDcard.
Click to expand...
Click to collapse
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
fauxfive55 said:
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Click to expand...
Click to collapse
Try backing up to external SD.
Sent from my Galaxy Tab 3 using XDA Labs
I have the same issue. I can't do a backup with TWRP. System, data and boot. It always ends with an error.
I have tried every storage, internal, SD, and OTG drive. Reflashed TWRP. Nothing seems to do any difference. Drives me crazy. Any solution?
just flash stock recovery then flash again TWRP . format SD throw recovery only then try backup should work . happened with me before ! .
Romiui said:
just flash stock recovery then flash again TWRP . format SD throw recovery only then try backup should work . happened with me before ! .
Click to expand...
Click to collapse
Unfortunately that didn't work. Tried flashing stock recovery and back, same thing. Then I flashed latest firmware (total reset), unlocked bl, flashed official TWRP and latest SuperSU. No success. ?
The issue is (or seem to be) data partition fail to mount, or does unmount during backup.
Can't be just me and OP struggling with this.
its really rare issue . i got that problem but honestly it get fixed after that solution !
Backup all other partitions except for the one that fails for now then as that is all you need to fix a bootloop etc and use Ti backup to get the apps etc
Hello,
I'm experiencing the same error when trying to backup to internal memory. I haven't yet tried to flash stock recovery back and after flash TWRP again to check if it solves the problem though.
RM
fauxfive55 said:
Most recently I'm getting this -
Backing up System...
createTarFork() process ended with ERROR: 255
Been trying to backup 3 partitions - data, system & boot using compression.
Here's some of the recovery.log file too -
Backing up System...
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000'
I:Using compression...
Error opening: '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' (No such file or directory)
I:Error creating tar '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.ext4.win000' for thread 0
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/RNV0216A31000896/2016-12-10--18-31-32/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Click to expand...
Click to collapse
I think this has been suggested already but I'm not certain:
Since the only error you're showing us (and maybe getting) is on /system partition Target (backup target), then how about trying unchecking that and doing the backup and seeing if you can get the same error (or not) on the other two (/data and /boot). ? Another thing maybe worth a shot is a completely benign partition like /cache and it's small for a quick test, maybe just give that a try. It'd be good to know that anything at all can be backed up in your version of TWRP.
Just want to see if it's something special about /system [target]. Also have you told us here which version from which thread you got TWRP from? Just curious. For Honor8 there seems to be so many TWRP authors that aren't too sure of their versions of TWRP (yet). Good luck.
hachamacha said:
I think this has been suggested already but I'm not certain:
Since the only error you're showing us (and maybe getting) is on /system partition Target (backup target), then how about trying unchecking that and doing the backup and seeing if you can get the same error (or not) on the other two (/data and /boot). ? Another thing maybe worth a shot is a completely benign partition like /cache and it's small for a quick test, maybe just give that a try. It'd be good to know that anything at all can be backed up in your version of TWRP.
Just want to see if it's something special about /system [target]. Also have you told us here which version from which thread you got TWRP from? Just curious. For Honor8 there seems to be so many TWRP authors that aren't too sure of their versions of TWRP (yet). Good luck.
Click to expand...
Click to collapse
This is interesting, because I have the same problem as well. I've tried backing up to internal as well as SD. I've also tried doing a full reset, flashing back to TWRP and same issue. No matter what partition I try, it always fails with the same error 255. I followed this thread exactly: http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946.
Doesn't seem as rare of an issue as initially thought. Any ideas?
joesee said:
This is interesting, because I have the same problem as well. I've tried backing up to internal as well as SD. I've also tried doing a full reset, flashing back to TWRP and same issue. No matter what partition I try, it always fails with the same error 255. I followed this thread exactly: http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946.
Doesn't seem as rare of an issue as initially thought. Any ideas?
Click to expand...
Click to collapse
It looks like only 2 of the replies in this thread show any hint of success, and even they didn't specifically say they'd done a backup and recovery. I'd kind of like to see a log from a successful backup & recovery before spending much time on this version of TWRP. If it just doesn't work and from every TWRP thread I've read, lots of people are having problems on this phone, so it might not work. I still don't know which version of recovery you all are using and am wondering if it's the official one from twrp.me site? Also, I suppose you'd have to be on android 6 for that to work.
Anyway, I just got mine today (H8), and am seeing if I can live with the size (I really like the 4.6" form factor better), but I really like how things function so far. If I get to the point where I've got Nougat installed without rooting it and still haven't decided to get a refund, then I'll go ahead and do all this stuff and see if I can help. I worked on a bunch of variants of Philz recovery long ago (and it could be completely irrelevant) so I need to look at the TWRP code and try another take on it. For me, one of the best things about rooting is the custom backup and recovery where it actually does those two things perfectly. I guess with the different CPU that there's still a lot of flailing in development land.
One of the few things I really recall being possibly relevant from Philz was how often people who were writing for various devices screwed up the only path to the root of the target by picking one that was either a) a soft link with bad permissions or b) not exactly the right spot. Just because TWRP says "external SD" (or whatever it says) doesn't mean much it's not pointing to something you can write to. I was using a Synology app named DS files today to get some stuff on the H8 and it wouldn't let me put them on the sdcard because it thought I hadn't given permissions to the DS File app. Does that make any sense? I just navigated around until I found a better path to the sdcard that had permissions because there was no way to give sdcard permissions to that app.
Has anyone pointed this out to @LastStandingDroid ?
those were all the same problems I had.
clsA said:
Has anyone pointed this out to @LastStandingDroid ?
those were all the same problems I had.
Click to expand...
Click to collapse
I found LSD seem to be aware about this in his nougat 3.0.2.0 recovery.
He wrote something about data partition unmounting being fixed.
Not sure if this is a known Marshmallow issue though.
Hello!
I've followed the suggestion of flashing stock recovery and after that TWRP but it did not made any difference, same error while backing up DATA.
But, after that I tried disabling compression and it worked OK. I've made a second try and it worked again. After this second successful run, I've tried a third time, but this time with compression enabled again, result.. Error...
Not a very scientific test, but it suggests the error has something to do with the compression.
RM
omartins said:
Hello,
I'm experiencing the same error when trying to backup to internal memory. I haven't yet tried to flash stock recovery back and after flash TWRP again to check if it solves the problem though.
RM
Click to expand...
Click to collapse
Currently there is no data partition backup support
Sent from my KIW-L22 using Tapatalk
I've not tried to restore the backup I've made supposedly successfully with compression disabled, but, I didn't get any error during the backup operation...
RM
Thanks
Thanks Boss love u
Hi there!
Today I've used TWRP Data backup to restore app settings, using TiBu. I can confirm the backup was useful, hence well successfully made.
RM
I have Lenovo a6000 and got flashed TWRP RECOVERY 2.8.6.0. I need to back up my stock ROM. When I go to TWRP>backup>select, system, data, boot> checking md5 and swiping. But result failed. It shows *cannot create backup folder* and *failed to make backup folder*. Don't know what to do further. Need help.
And today I flashed 3.0.2-0 of TWRP. Same error. Cannot unmount sdcard, and shows something * device busy* like this.
Hi !
First , try to chose the backup location on the internal storage
Second , be sure that the removable sdcard it is supported by the rom and it is recognised in settings/storage
The problem may be with the recovery itself or with the sdcard , head over the recovery thread you have downloaded for more info or use a newer version https://forum.xda-developers.com/le...ecovery-twrp-3-0-2-lenovo-a6000-plus-t3543596
Good luck !