My Galaxy S2 is only rooted, i had problems with it before, when memory gets full (internal) it refuge to charge, each time i had time to delete apps, yesterday i bought apps from android market and it installed it on my phone, didnt want it to do but it did, it refuge to charge, after a while it boot loops.
I know i can reflash but i dont wanna lose all photos of my family and game saves etc, i know i should make a nan backup and a will do after this, but the problem remains.
HOPE FOR BIG HELP
And i am in original recovery mode and it says:
E:failed to mount /data (unknown error: 0)
-- Copying media files...
Successfully copied meida files. ( yes it says meida files not media)
# MANUAL MODE #
-- Updating application...
E:failed to mount /data (unknown error: 0)
E:install_application_for_customer:Can`t mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed
--Appling Multi-CSC...
Installing Multi-CSC
Can`t access to ´/system/csc/TGY/system/´
Successfully applied multi-CSC.
Yellow is replaced by green cause its to bright here, atleast on my screen.
A FIXED CLOCKWORKMOD 4.0.0.2 to the phone so i must be able to backup now, will wait for advice to backup everything, dunno if an backup is good cause something is wrong with the phone.
Edit: it Backed up, but couldnt back up /data ?
And where to find latest clockworkmod, i want to backup it to sd card, it jsut do to the internal sd card.
Is there any CWM 5.0.2.7 for SG2 yet?
And can i update to 2.3.4 or 2.3.5 using CWM as a ZIP instead of KIES? without loosing anything on the phone?
OK so no one knows?
All i need it latest CWM and Android firmware, some one need to know where to find it.
Hi,
I want to restore a backup I made with TWRP (3.0.2-0 Released), but it fails with the error "mounted read only".
The backup is on the external SD card and I set the related ticks in the "Mount" section.
Some details:
I'm using a Samsung S5
System is rooted and SuperSU is installed
Currently, Cyanogenmod 13 is installed, but I want to switch back o 12.1
I do not have enough internal storage to move the backup
I've attached a picture of the error message and the error log.
Any help is appreciated!
Error:
h**p://w*w.bilder-upload.eu/show.php?file=05dc61-1465516034.jpg
Error log:
h**p://w*w.filedropper.com/recovery_3
OK, after I unticked Modem and EFS(?) of the sections I want to restore, it worked.
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 !
Hi guys,
so the problem is that i cant flash SuperSu thats located on my phone memory because the TWRP is showing 0 MB,also i am unable to mount the storage in TWRP. I tried different solutions that i found on this forum( set a lock pattern,PIN,wipe/format data, change file system ) but none have worked, TWRP newer even asks for a password. Also when i try to format the data in TWRP i get the "unable to mount data,system..." error. Is there another way to flash SuperSU without TWRP, because i also tried sideloading it but it failed?
I'm betting your device is encrypted. Which is always am issue.
Any solutions i could try ?
bump?