During the backup restore, the system partition fails and gives me error 255. I'm restoring from PAC B322 to Stock B322, so there shouldn't be a partition size problem like I was having before... Has anyone else had this error?
Bueller?
Nobody has seen this before? Google hasn't been very helpful..
Please give more info around the error 255. So others didn't have this problem may be able to help.
xordos said:
Please give more info around the error 255. So others didn't have this problem may be able to help.
Click to expand...
Click to collapse
Well, that's really all there is to it... I try to restore a backup and as it is running through the system partition, it stops and says "error 255", failure to restore. I was hoping that was a more common issue
I tried at least 5 times, made separate/new backups, different ROMs, all the same error.
chill8888 said:
Well, that's really all there is to it... I try to restore a backup and as it is running through the system partition, it stops and says "error 255", failure to restore. I was hoping that was a more common issue
I tried at least 5 times, made separate/new backups, different ROMs, all the same error.
Click to expand...
Click to collapse
A few things you can try, save the twrp log and upload to this thread; use a different sd card; reformat the card then try backup/restore.
Uhm, what version of TWRP?
Also, try without MD5.
Related
Hi,
So I need some help. I rooted my Evo 3D using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1192525
and everything went fine. I created a backup using nandroid (in clockwerkmod in preparation for trying out some custom roms, but upon reboot I got the message:
"the process android.process.acore has stopped unexpectedly. FORCE CLOSE"
at startup. This message repeats if I simply try to acknowledge it and move on.
I tried simply restoring to the backup I created but I get the same message.
I'm not sure what to do next, any help or advice would be greatly appreciated!
ICHNIMBY said:
Hi,
So I need some help. I rooted my Evo 3D using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1192525
and everything went fine. I created a backup using nandroid (in clockwerkmod in preparation for trying out some custom roms, but upon reboot I got the message:
"the process android.process.acore has stopped unexpectedly. FORCE CLOSE"
at startup. This message repeats if I simply try to acknowledge it and move on.
I tried simply restoring to the backup I created but I get the same message.
I'm not sure what to do next, any help or advice would be greatly appreciated!
Click to expand...
Click to collapse
i'm making the assumption you're on a completely stock ROM w/only nand unlock and superuser.apk as you haven't mentioned any other changes. if you've made any other changes, then i would look into reverting those first.
i'm going to give two routes to approach this issue and let you decide which works best for you.
shorter route:
background:the way android is designed is for the /system partition, where all stock apps and stock settings are located, to stay in a read-only state. due to android's setup of having /system stay in a read-only state, all changes/modifications/settings are to be stored on the /data partition. /data is mounted as read/write and /system is mounted as read-only. of course with root access and nand unlock, these can be changed.
suggestion: if restoring your /data partition still results in those FC (Force Close) alerts, i would restore it from a backup as the guide you linked instructs to make before starting.
if restoring the backup still results in the FC message, i would then proceed to erase your /data partition. erasing the /data partition will wipe out all your settings/modifications/changes to all your apps and the system. it should revert the phone to a clean stock state and clear out the issue causing the FC.
long more technical route: logcat contains all the debug output from every application on the phone. it can be accessed through the android sdk, with either of two tools, ddms or adb logcat.
using logcat is definitely a bit technical and it isn't the easier thing to read, become familiar with and research, but its definitely do able! logcat should show what is causing the FC message, but it will be given in java debug code and probably require some researching.
hope that helps! good luck and let us know if you have any other questions/how it turns out!
joeykrim said:
suggestion: if restoring your /data partition still results in those FC (Force Close) alerts, i would restore it from a backup as the guide you linked instructs to make a before starting.
Click to expand...
Click to collapse
I just did this and the problem is gone. I guess sometimes you need someone to point out the obvious to you.
Thanks so much!
ICHNIMBY said:
I just did this and the problem is gone. I guess sometimes you need someone to point out the obvious to you.
Thanks so much!
Click to expand...
Click to collapse
wonderful! glad the solution was my simple fix suggestion as the more complex route takes a lot more time!
lesson learned .. backup backup backup! ive got to the point where i'd rather have tons of backups and no issues .. then a few insufficient backups and issues!
so im having trouble making backups in CWM based recovery 5.5.0.4. It always gets to backing up data, but ends with "error while making backup of data/"
Ive cleared up 9gb of space on my external sdcard and that didnt work. Ive tried the internal sd which has 6gb. Ive wiped cache/dalvik and fixed permissions and still I cant get a full backup.
any suggestions? I read somewhere that i might need to format my sdcard, but then shouldnt my internal sd work?
any help would be much appreciated.
Looks like you have too many apps saved within this backup image.
Look here, reply #9
Try to backup from a lighter image to see how it goes.
yairku said:
Looks like you have too many apps saved within this backup image.
Look here, reply #9
Try to backup from a lighter image to see how it goes.
Click to expand...
Click to collapse
I only have 76 apps installed :/
Sent from my MB855 using xda app-developers app
And you have the same problem? Try other recovery, but not an old one.
yairku said:
And you have the same problem? Try other recovery, but not an old one.
Click to expand...
Click to collapse
yeah i just posted a similar post ... and i tried another recovery and still same issue
This new idea is taken from senior member Immix:
I think it's a problem in the backup using this CWM version.
Get Jokersax's recovery from here, and flash it with fastboot.
Now, flash the ROM you want without any data or cache. Clean everything and make a clean install.
Get Titanium backup and restore all your apps from the backup file you tried to use first. Just select "Import from Nandroid Backup" within Titanium backup.
Source
sounds promising, ill give it a shot.
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
i have problem when i restore my backup its
-checking MD5 sum
-restoring boot image
-restoring system
-restoring data- in the end off restoring data i have error
Error data/data
any ideas?
its fault cwm?
backup is good for sure
maybe i need different cwm?
please help me
ps. i write on this forum because on others people dont help me
please i want my backup back
I had the same problem. Just reboot to recovery and do it again. On your way doing it your custom recovery may inform you that you have lost root and ask you to reroot.
Sent from my GT-N7100 using xda premium
dont work
iRouk said:
I had the same problem. Just reboot to recovery and do it again. On your way doing it your custom recovery may inform you that you have lost root and ask you to reroot.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
the same problem all time
i cant wastle my work i make some many changes i cant loose it
different backup
deusson said:
the same problem all time
i cant wastle my work i make some many changes i cant loose it
Click to expand...
Click to collapse
i flash another rom and next do another backup of new rom , and when i restore this new one restore is complete.
but old one i want always the same problem
maybe problemn is in folder clocworkmod
because in old one i have more files like for example data.ext4.tar.g
please some ideas?
maybe i dont have enough space to bring back backup(restore)?
my backup have 8 gb
You could try advanced restore and specify the part of the backup you want to restore, on cwm. My reasoning is that since the md5sum check completes, the integrity of your back up is verified, so that's to mean that all should work just fine. But since it doesn't go past the data restoration, maybe you could try restoring just the data part of the backup; assuming that the phone already has a rom that it is booting to and functioning as expected in order to be able to see the restored data when you boot the phone after the restore.
i find solution
knoknot said:
You could try advanced restore and specify the part of the backup you want to restore, on cwm. My reasoning is that since the md5sum check completes, the integrity of your back up is verified, so that's to mean that all should work just fine. But since it doesn't go past the data restoration, maybe you could try restoring just the data part of the backup; assuming that the phone already has a rom that it is booting to and functioning as expected in order to be able to see the restored data when you boot the phone after the restore.
Click to expand...
Click to collapse
error was because of space on device
i flash a rom once again, than delete all folders that i dont needed
and then go to recovery, than restore was complete
so its was because i dont have to much space on device-its for sure because i try many things and in the end i find this solution off my problem
i hope it be helped to somebody else
deusson said:
error was because of space on device
i flash a rom once again, than delete all folders that i dont needed
and then go to recovery, than restore was complete
so its was because i dont have to much space on device-its for sure because i try many things and in the end i find this solution off my problem
i hope it be helped to somebody else
Click to expand...
Click to collapse
Great news man...good for you.
i have two huge problems like i mention in thread title. Whenever i restore my TWRP backup it gives error and says "Extractfork 255 error" and nothing in internet solved my issue.
My other and biggest problem is phone info says "encrypted" how to disable force encrypt?
Not even a single answer??
You can only disable force encrypt by flashing "patch no fde" file available on most rom threads.
But you will have to format data which will wipe your whole phone and flash the file before rebooting.
The reason your getting the other error is most likely twrp can't decrypt your data seeing as force encrypt is enabled.
And don't expect an answer, nobody here on xda is entitled to get questions answered. Alot of this information could have been accessed online if you just researched yourself instead of waiting over a week for a reply. It's not hard to type into a search engine
You haven't provided much information. Which TWRP version, what are you trying to restore, which steps have you tried and failed, what do you see in the TWRP logs etc. We do not have a crystal ball to guess the answers.
To decrypt the data, flash verity disabler and format data partition from TWRP. https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Edit: garylawwd was a bit faster in reply
garylawwd said:
You can only disable force encrypt by flashing "patch no fde" file available on most rom threads.
But you will have to format data which will wipe your whole phone and flash the file before rebooting.
The reason your getting the other error is most likely twrp can't decrypt your data seeing as force encrypt is enabled.
And don't expect an answer, nobody here on xda is entitled to get questions answered. Alot of this information could have been accessed online if you just researched yourself instead of waiting over a week for a reply. It's not hard to type into a search engine
Click to expand...
Click to collapse
Of course i did search of course i didnt sit and wait for a response but as you can clearly see i flashed no fde patch even though it say succesfull but it always getting encrypted by itself again. Thanks for reply by the way
_mysiak_ said:
You haven't provided much information. Which TWRP version, what are you trying to restore, which steps have you tried and failed, what do you see in the TWRP logs etc. We do not have a crystal ball to guess the answers.
To decrypt the data, flash verity disabler and format data partition from TWRP. https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Edit: garylawwd was a bit faster in reply
Click to expand...
Click to collapse
Correct me if im wrong but we have just 1 really working twrp and its 3.3.1.2 by Nikesh and im using it. I was really thinking its very simple question. i didnt get why it looks like so complicated ) i tried to restore my nandroid backup and all of sections are succesfull exept /data partition. when it comes to /data partition it gives "extracttark error 255 ". Im still confused why you didnt get my question
sasukeob said:
Of course i did search of course i didnt sit and wait for a response but as you can clearly see i flashed no fde patch even though it say succesfull but it always getting encrypted by itself again. Thanks for reply by the way
Click to expand...
Click to collapse
What you mean that you flashed patch no fde because no where have you mentioned that you had flashed anything. You won't be able to restore the backup now because your data is encrypted and this twrp can't restore encrypted data.
You need to format data and then flash patch no fde like both of us already said. Then you can make a backup that you can restore later. You can't do anything about your encrypted data now
sasukeob said:
Correct me if im wrong but we have just 1 really working twrp and its 3.3.1.2 by Nikesh and im using it. I was really thinking its very simple question. i didnt get why it looks like so complicated ) i tried to restore my nandroid backup and all of sections are succesfull exept /data partition. when it comes to /data partition it gives "extracttark error 255 ". Im still confused why you didnt get my question
Click to expand...
Click to collapse
You are right, the answer to your question is very simple and obvious, I don't get why do you find it so complicated that you must ask here in such a nice manner.
---------- Post added at 07:18 PM ---------- Previous post was at 07:10 PM ----------
garylawwd said:
What you mean that you flashed patch no fde because no where have you mentioned that you had flashed anything. You won't be able to restore the backup now because your data is encrypted and this twrp can't restore encrypted data.
You need to format data and then flash patch no fde like both of us already said. Then you can make a backup that you can restore later. You can't do anything about your encrypted data now
Click to expand...
Click to collapse
From what I read, once you enter the correct password in TWRP and it can read data correctly, backup of /data is unencrypted. After the restore, data gets encrypted by system upon the first boot. This can be verified easily with Titanium backup app, which can read and use TWRP backups. At least that's the theory, but I'm too lazy to verify it
If you perform data backup with incorrect password (or TWRP doesn't support decryption), then your backup remains encrypted and is useless as you said.
_mysiak_ said:
You are right, the answer to your question is very simple and obvious, I don't get why do you find it so complicated that you must ask here in such a nice manner.
---------- Post added at 07:18 PM ---------- Previous post was at 07:10 PM ----------
From what I read, once you enter the correct password in TWRP and it can read data correctly, backup of /data is unencrypted. After the restore, data gets encrypted by system upon the first boot. This can be verified easily with Titanium backup app, which can read and use TWRP backups. At least that's the theory, but I'm too lazy to verify it
If you perform data backup with incorrect password (or TWRP doesn't support decryption), then your backup remains encrypted and is useless as you said.
Click to expand...
Click to collapse
Ya I apologise this twrp does in fact support data decryption it must have been the older version that didn't support it.
Without twrp logs I doubt there is anything we can do.
But like you suggested it may very well be a password error..but we will never know :silly:
i dont understand what im doing wrong. I installed havocos flashed no fde patch. i tried 3 times installed rom and tried. still encrypted
_mysiak_ said:
You haven't provided much information. Which TWRP version, what are you trying to restore, which steps have you tried and failed, what do you see in the TWRP logs etc. We do not have a crystal ball to guess the answers.
To decrypt the data, flash verity disabler and format data partition from TWRP. https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Edit: garylawwd was a bit faster in reply
Click to expand...
Click to collapse
gary thanks for reply but i flashed it and it caused bootloop
sasukeob said:
gary thanks for reply but i flashed it and it caused bootloop
Click to expand...
Click to collapse
Tell us what actions exactly did you do, step by step, in chronological order.
_mysiak_ said:
Tell us what actions exactly did you do, step by step, in chronological order.
Click to expand...
Click to collapse
Ok. I have twrp 3.3.2.0 by nikesh installed. i format data and wipe dalvik cache and data. and i tried to restore my twrp backup. It restoring good but when it comes to restoring /data partition. it gives "Extracttrakfork Error 255" in red characters. I format data flashed nofde.zip but device encrypts itself again. So i tried to instal HavocOs and flash gapps and flash nofde patch. Havocos install succesfull but gapps flash gives error " Unmounting /vendor update process ended with error 25" :/
i flashed Orangefox recovery problem is still same :/
sasukeob said:
Ok. I have twrp 3.3.2.0 by nikesh installed. i format data and wipe dalvik cache and data. and i tried to restore my twrp backup. It restoring good but when it comes to restoring /data partition. it gives "Extracttrakfork Error 255" in red characters. I format data flashed nofde.zip but device encrypts itself again. So i tried to instal HavocOs and flash gapps and flash nofde patch. Havocos install succesfull but gapps flash gives error " Unmounting /vendor update process ended with error 25" :/
i flashed Orangefox recovery problem is still same :/
Click to expand...
Click to collapse
Oh boy, you're doing too many things at once First of all, what do you want to achieve? Restore stock data? Install custom ROM? Just fooling around?
Data restore -
Are you sure that your data backup is decrypted and functional? Try to restore data from nandroid backup in Titanium backup or simply open the twrp backup files (they are tar archives) and check if you see individual files or just garbage.
You mentioned that you tried "everything", but you haven't mentioned this workaround https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Provide full twrp.log after failed restore.
Data encryption -
Have you followed steps described here? https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Provide full twrp.log after zip installation.
Custom ROM -
Find support in the specific ROM topic (and provide twrp.log after failed installation).
_mysiak_ said:
Oh boy, you're doing too many things at once First of all, what do you want to achieve? Restore stock data? Install custom ROM? Just fooling around?
Data restore -
Are you sure that your data backup is decrypted and functional? Try to restore data from nandroid backup in Titanium backup or simply open the twrp backup files (they are tar archives) and check if you see individual files or just garbage.
You mentioned that you tried "everything", but you haven't mentioned this workaround https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Provide full twrp.log after failed restore.
Data encryption -
Have you followed steps described here? https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Provide full twrp.log after zip installation.
Custom ROM -
Find support in the specific ROM topic (and provide twrp.log after failed installation).
Click to expand...
Click to collapse
I dont know how i did but after 1 month of try and fail im not quite sure but it seems i succeed now @_mysiak_ I really appreciate bc you spend time for replying my thread. Thank you so much man When you need help about anything just pm me i will try to help you bc you spend your time for me
my only problem is dm-verity now i guess. i dont know how to solve it but i will try