Hi there, after upgrading from 5.0 to 5.0.1, i am experiencing a problem during backup via twrp. I get createTarFork() process ended with ERROR=255 error when processing data partition... I have tried both latest cheeseburger and blue spark recoveries without solving...
Anyone else got this? Any ideas?
I am not rooted, crypted and stock kernel
I am getting the same error when I try to restore a backup any help would be really appreciated
i think it has to do with parallel apps.
had the problem for quite a while without noticing i have a second user registered (user 999, like with parallel apps). deleted the user and the nandroid was succesful again.
Then i created a parallel version of WhatsApp and tried to make a nandroid backup and i got the createTarFork() process ended with ERROR=255 error for data partition again.
Didn't really have time to try to fix it and get backups working again, but I'm pretty sure that parallel apps by oneplus are causing this
finally i got it working!
flashed latest twrp (cheeseburger or blue spark), then advanced, filemanager
delete every "999" folder:
sdcard
/data/user/999
/data/user_ce/999
/data/user_de/999
/data/misc_ce/999
/data/misc_de/999
/data/system_ce/999
/data/system_de/999
after try to backup again. it's working for me
so that means if you use parallel apps you can't have nandroid backups?
tukiii said:
so that means if you use parallel apps you can't have nandroid backups?
Click to expand...
Click to collapse
probably... at the moment we need to delete all the '999' folders before backup and maybe even restore (havent tried to restore yet).
curious fact is that even if i disable parallel apps, the system recreates the 999 folders in any case at every restart
Anyone have more info on why the backup fails for user 999/ parallel apps?
I can't find it and I would like to know if I will be able to both use nandroid backups and parallel apps in the future...
I'm giving this a try now. Backup failing with createTarFork() process ended with ERROR=255 when processing data partition. Have deleted the 999-folders, and started the backup process again.
---------- Post added at 08:23 PM ---------- Previous post was at 08:12 PM ----------
krugm0f0 said:
I'm giving this a try now. Backup failing with createTarFork() process ended with ERROR=255 when processing data partition. Have deleted the 999-folders, and started the backup process again.
Click to expand...
Click to collapse
And that worked like a charm!
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
exgtigsr said:
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
Click to expand...
Click to collapse
It seems that you have multiple users on your phone. Nandroid backups fail with multiple users setups (on a side note, the Parallel app creates an invisible user with the id 999, and thus brings the issue of multiple user nandroid backup).
If you wish to backup your data, your only option is to boot Android, switch to the 2nd user and backup via MTP.
Bakuryu91 said:
It seems that you have multiple users on your phone. Nandroid backups fail with multiple users setups (on a side note, the Parallel app creates an invisible user with the id 999, and thus brings the issue of multiple user nandroid backup).
If you wish to backup your data, your only option is to boot Android, switch to the 2nd user and backup via MTP.
Click to expand...
Click to collapse
Hi Bakuryu91,
Thanks for the reply.
That's the thing. I don't have multiple user on the phone.
As mentioned, i searched for folder 999 and looked in /data/user/ there is only folder "0" as the single user.
Really baffled since as mentioned, i'm not using Parallel Apps and not using App Locker.
exgtigsr said:
Hi Bakuryu91,
Thanks for the reply.
That's the thing. I don't have multiple user on the phone.
As mentioned, i searched for folder 999 and looked in /data/user/ there is only folder "0" as the single user.
Really baffled since as mentioned, i'm not using Parallel Apps and not using App Locker.
Click to expand...
Click to collapse
Could you send me your log in PM? (/tmp/recovery.log)
Bakuryu91 said:
Could you send me your log in PM? (/tmp/recovery.log)
Click to expand...
Click to collapse
done ??, thanks for this help.
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.
Related
thread closed.
!!! Seems suspicious -- lol
Willy318is said:
!!! Seems suspicious -- lol
Click to expand...
Click to collapse
I don't understand.
it might working but sometimes some data wont work well with new firmware
but you seem to forget one bigggggg step.... to backup the old data using cwm...
edan1979 said:
it might working but sometimes some data wont work well with new firmware
but you seem to forget one bigggggg step.... to backup the old data using cwm...
Click to expand...
Click to collapse
Yes I wrote in red. There MIGHT have problem between versions. If you're on 4.0 and you flash 4.1. But even so I did it many time without problems
I didn't separate CWM & TWRP for the backup because it's basically same thing.
Kremata said:
I don't understand.
Click to expand...
Click to collapse
Sorry, I just felt it could not be that easy, ROMs are being heavily optimized and tweaked from Dev-to-Dev, let alone the Official releases with different bases and Radios, so I just think that doing your method might pick-up some old cranky stuff from earlier backups, but yet again, its just my theory, which might be totally messed up
Will give it a shot though, it could save me hours.
Willy318is said:
Sorry, I just felt it could not be that easy, ROMs are being heavily optimized and tweaked from Dev-to-Dev, let alone the Official releases with different bases and Radios, so I just think that doing your method might pick-up some old cranky stuff from earlier backups, but yet again, its just my theory, which might be totally messed up
Click to expand...
Click to collapse
The "Restore Data" in CWM or TWRP will restore your apps/contacts/sms/etc.. But, for example if you restore a backup that had your gmail but your new ROM doesn't have gmail. The restore will just skip it.
Willy318is said:
Will give it a shot though, it could save me hours.
Click to expand...
Click to collapse
You won't regret it.
For restoring data Titanium OR similar application is better than Nandroid
Another advantage of Titanium is schedular backup
Above said method you need to backup just before flashing ROM, while if you schedule titanium you will ready to go anytime.
As well titanium data restore is quite clear then data restore from nandroid.
Nandroid is best for return to point where you were in case you messup things while testing something.
dr.ketan said:
For restoring data Titanium OR similar application is better than Nandroid
Another advantage of Titanium is schedular backup
Above said method you need to backup just before flashing ROM, while if you schedule titanium you will ready to go anytime.
As well titanium data restore is quite clear then data restore from nandroid.
---------- Post added at 12:36 PM ---------- Previous post was at 12:35 PM ----------
For restoring data Titanium OR similar application is better than Nandroid
Another advantage of Titanium is schedular backup
Above said method you need to backup just before flashing ROM, while if you schedule titanium you will ready to go anytime.
As well titanium data restore is quite clear then data restore from nandroid.
Nandroid is best for return to point where you were in case you messup things while testing something.
Click to expand...
Click to collapse
I think they both have their advantages. Titanium will only restore apps but the method above will restore Apps/contacts/sms/gmail acounts/etc...
Titanium can restore contacts, bookmarks call logs as well sms too
And sms call logs are store in xml which is more clean when you restore trans OS./device
Sent from my GT-N7100 using xda premium
The reason I only use titanium for restoring: I heard it is the cleanest, and as mentioned above nandroid restoring restores some weird **** from old roms
Sent from my GT-N7100 using xda app-developers app
I have transfered my sms contacts from galaxy S - S2 - note1 and now on note2 (froyo to JB)
I still have some sms. 3yr old and titanium never failed to restore
Sent from my GT-N7100 using xda premium
---------- Post added at 12:58 PM ---------- Previous post was at 12:51 PM ----------
klect said:
The reason I only use titanium for restoring: I heard it is the cleanest, and as mentioned above nandroid restoring restores some weird **** from old roms
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Exactly, titanium restore only what you want. And it's totally under your control, you can mess only if you don't know how to use it.
Sent from my GT-N7100 using xda premium
dr.ketan said:
I have transfered my sms contacts from galaxy S - S2 - note1 and now on note2 (froyo to JB)
I still have some sms. 3yr old and titanium never failed to restore
Sent from my GT-N7100 using xda premium
---------- Post added at 12:58 PM ---------- Previous post was at 12:51 PM ----------
Exactly, titanium restore only what you want. And it's totally under your control, you can mess only if you don't know how to use it.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yes when restoring between devices or versions(ICS to JB etc..) The OP method is not the best. But if you flash a lot of ROMs all the same version this method is very quick and trouble free.
Yes, this method is quick, but I wouldn't use it for everyday ROM, maybe for testing etc. With Titanium you can backup/restore only USER apps. I think it is bad idea to restore system apps' data. So still the "cleanest" way is to back up everything with Titanium, flash ROM and then install Titanium and restore selected user apps+data.
Kremata said:
this method is very quick and trouble free.
Click to expand...
Click to collapse
Not convincing,
See for nandroid you have to make recent backup if you want to have backup of latest stuff like SMS, call logs, newly installed App, contacts
AFAIK nandroid takes nearly 20 min to backup (depends on data it may take more)
Now again restoring as per you said takes 15 min for data.
For titanium if you have schedule, need not to make backup before flashing, even you want to make just run backup of modified data and it will finish in 1-2 min.
For me titanium takes just 15 min to restore
- >115 user app
- Contacts, SMS,Settings,Launcher home (desktop),Bookmarks
so it is more faster then nandroid ultimately
Nandroid is the choice as i said earlier,
If your device is working perfect just make nandroid, Try you want to test anything and if you are not happy with testing just restore Nandroid (full) you have made just before test and you are back.
---------- Post added at 01:28 PM ---------- Previous post was at 01:23 PM ----------
dalanik said:
Yes, this method is quick, but I wouldn't use it for everyday ROM, maybe for testing etc. With Titanium you can backup/restore only USER apps. I think it is bad idea to restore system apps' data. So still the "cleanest" way is to back up everything with Titanium, flash ROM and then install Titanium and restore selected user apps+data.
Click to expand...
Click to collapse
But we never need to restore system application
Best scenario in titanium is restore 'Missing application with data', this will by default excludes any system application (from previous OS and absent in new ROM) still you will have choice to uncheck any application you don't want.
Contacts,settings - you can restore just data (green colored) and won't replace system files
while call log, SMS, browser (yellow color) are just xml format and best to restore without any issue
Just you need system data is only TW launche(stock), but we needs just data only not system.
dr.ketan said:
But we never need to restore system application
Best scenario in titanium is restore 'Missing application with data', this will by default excludes any system application (from previous OS and absent in new ROM) still you will have choice to uncheck any application you don't want.
Contacts,settings - you can restore just data (green colored) and won't replace system files
while call log, SMS, browser (yellow color) are just xml format and best to restore without any issue
Just you need system data is only TW launche(stock), but we needs just data only not system.
Click to expand...
Click to collapse
No, not application, but data of system applications. That would be able to cause problems.
Yes that I said usually we need not to restore data of system application in normal way. Except for tw launcher home (desktop)
Usually people do restore everything and facing issue later by messing system junks.
Sent from my GT-N7100 using xda premium
Advance restore data will not restore system apps. It will only restore user apps. Like I said this method is quick and simple and I never had any problem. Can save you a lot of time. 20 minutes for a backup must be a very old phone. I have 108 apps on mine and it takes only 5 minutes to backup
dr.ketan said:
Here thing is totally different, what I know about your recovery guide is no one gave you discredit. When you publish any guide on public forum, sure someone will put their ideas and only that way discussion goes on. Basically public forum is meant for such things. I have wrote many guides having million viewership, thousand thanks, still people suggest me when something better they found, and I love to exchange idea, but it's ultimately you have to decide which one is better. We should have to remain open to discuss on topic we have created.
As far as my comments have concerned, I have discussed point to point why I found other thing is better, if you targeting that then better if you show some nice point to make me convince on your point of view rather complaining to other post. If you targeting else I am sorry.
Does you feel anyone have troll on your post?
I don't think so.
Click to expand...
Click to collapse
Ah ok, I was not targeting you at all, I was refering to my other (same)guide on SGS3. I was discredit because I didn't have enough THANKS.
Posted by someone who really has not helped the novice user
Click to expand...
Click to collapse
I know the difference between trolling and discussing. Like you said people can make their choice and I beleive Titanium is good and my(it's not really mine I just transfered the information) way is also good. It just depends on the situation.
Kremata said:
Ah ok, I was not targeting you at all, I was refering to my other (same)guide on SGS3. I was discredit because I didn't have enough THANKS.
I know the difference between trolling and discussing. Like you said people can make their choice and I beleive Titanium is good and my(it's not really mine I just transfered the information) way is also good. It just depends on the situation.
Click to expand...
Click to collapse
I misunderstood and sorry again.
Yes I never said nandroid is not good, it's definitely best in certain situations. I mean to say overall titanium is cleaner way to restore data particularly when restoring trans rom/device.
Sent from my GT-N7100 using xda premium
I was hoping to learn the differences between certain backup methods. The most common i saw is via recovery (in my case twrp), via titanium backup and another via adb command even without root which i saw in one of the threads here in xda.
First, in terms of "backup coverage" how do they compare to one another? Secondly, which among the three would most put ur phone back the way it was before u wipe or factory reset it
I hope you could input your opinions on this and suggestions.
Thanks in advance!
Sent from my Nexus 4 using xda premium
A backup through recovery is a called a nandroid. This backs up everything on your phone including your ROM, kernel, apps, settings, etc. This will allow you to restore back to the previous state of your phone after doing a full wipe.
Titanium backup only backs up your apps and app data. This is useful when you want to switch ROMs and restore your apps in the new ROM.
Usually when switching ROMs I first use titanium backup, then I create a nandroid backup, and finally I flash the ROM. If I like the ROM I use titanium to restore the apps that I previously backed up, and if I don't like the ROM I restore my nandroid
Sent from my HTC Desire using xda app-developers app
Doing a backup with twrp, cwm or thru adb (nandroid backups) are basically image files of your phone at any given moment in time. If you restore one of these backups your restoring your phone to exactly how it was at that moment in time. Titanium backup and Helium backup just backup cached data at that particular moment in time. Using these apps will only restore the data you specified when you did the backup and nothing else. Say you borked an install of a ROM, Titanium backup would be of no use in getting your phone working again as it only has data and not a system image. You would need the images backed up by twrp to get the phone working again then you could use the titanium backups to restore any newer data saved if say you used an old twrp backup.
whoah! thanks guys! I was supposed to quote you but since both of you really helped me understand it now, this thanks goes to the both of you.
I've hit the thanks button on both you guys.
Thank you very much for explaining this.
One last thing, when using a Titanium backup ( im using the pro version), how do i backup to make sure I cover all that needs to be backed up? There are a lot of options im not sure which to select and what to do. I hope you could enlighten me on this one as well.
Thanks again in advance!
vinz_bangiz said:
whoah! thanks guys! I was supposed to quote you but since both of you really helped me understand it now, this thanks goes to the both of you.
I've hit the thanks button on both you guys.
Thank you very much for explaining this.
One last thing, when using a Titanium backup ( im using the pro version), how do i backup to make sure I cover all that needs to be backed up? There are a lot of options im not sure which to select and what to do. I hope you could enlighten me on this one as well.
Thanks again in advance!
Click to expand...
Click to collapse
With the pro version u can run a batch backup of all apps.
To do this open the app, press the menu button in the top tight corner, and select Batch.
Then choose Backup all user apps. From there you can select/deselect apps. When you are done choosing the apps that you would like to backup, click on the green check mark in the top right corner to start the backup.
vinz_bangiz said:
whoah! thanks guys! I was supposed to quote you but since both of you really helped me understand it now, this thanks goes to the both of you.
I've hit the thanks button on both you guys.
Thank you very much for explaining this.
One last thing, when using a Titanium backup ( im using the pro version), how do i backup to make sure I cover all that needs to be backed up? There are a lot of options im not sure which to select and what to do. I hope you could enlighten me on this one as well.
Thanks again in advance!
Click to expand...
Click to collapse
I stopped using Titanium and switched to Helium a while back and can't really remember how Ti works exactly. I do know you should never restore system apps data just user apps data so I don't even bother backing up systems apps. I think with Ti I would just do an initial backup of all user data and apps and then periodically do a backup of newer user data and apps, or something to that effect in the menu. I do like Helium better as its interface is better, never could figure out how to backup or restore sms, call logs and the dictionary using Ti. Helium is much more straight forward and simpler (not as many options) and it does backups on a set schedule to my box account. I'm sure you can do all that with Ti too it was just not a very clean app.
thanks again for the replies..
@ chromium96
i think it is the same as clicking the box with check icon beside the menu, it brings me to the page the same as where you are leading me to but in just one click. Though im not so sure if it is really the same one.
I did a backup now but made a user app + system data.
kzoodroid mentioned not to backup system. Should I really not backup the system? Im quite confused with the terminologies of TI coz it says backup "user apps". Does this only refer to the apps and not the settings or data in my phone? does the backup "system data" refer to the settings and other data on my phone? if I choose only backup "user apps", would this only backup the apps and nothing else?
@ kzoodroid
could you explain further why I should never backup systems apps?
Lastly, is Helium really better than TI? or it depends on user preference?
Thanks again!
there are 2 kind of apps stored in your phone, system apps, only accesible with root privilege, and user apps,
system apps are phone, browser,wallpapers, etc, this are the basic apps to make your phone to work
user apps are all the stuff you, the user, install on your phone
the first one can be found, via file managers on /system/app
user app in /data or in sdcard for apps can use this option
the user app back-up, via Tb or others create a back-up of /data and apps you choose to install
restoring a system app via Tb is dangerous cause if you've switched rom the /system/app can be different, so restoring can cause trouble or misbehavior on your phone
/system/app back.up can be used only if you, before deleting a system app, want to have a copy to restore in future, but only if you still on the same rom
stremax said:
there are 2 kind of apps stored in your phone, system apps, only accesible with root privilege, and user apps,
system apps are phone, browser,wallpapers, etc, this are the basic apps to make your phone to work
user apps are all the stuff you, the user, install on your phone
the first one can be found, via file managers on /system/app
user app in /data or in sdcard for apps can use this option
the user app back-up, via Tb or others create a back-up of /data and apps you choose to install
restoring a system app via Tb is dangerous cause if you've switched rom the /system/app can be different, so restoring can cause trouble or misbehavior on your phone
/system/app back.up can be used only if you, before deleting a system app, want to have a copy to restore in future, but only if you still on the same rom
Click to expand...
Click to collapse
Thanks for the reply! kinda getting an idea what you mean.. if I backup the system also, then i put a new rom and it may be different from my current roms system so it might mess it up. so just backup user app and restore this after installing new rom then it would be ok and back to how it was before i installed a new rom? Do i understand it right?
vinz_bangiz said:
Thanks for the reply! kinda getting an idea what you mean.. if I backup the system also, then i put a new rom and it may be different from my current roms system so it might mess it up. so just backup user app and restore this after installing new rom then it would be ok and back to how it was before i installed a new rom? Do i understand it right?
Click to expand...
Click to collapse
right man,
only back-up user apps and data, if you like you can also back-up call log and messages, I usually do this, so when I flash a new rom I usually restore apps +apps data, messages and call log via Tb
vinz_bangiz said:
another via adb command even without root which i saw in one of the threads here in xda.
Click to expand...
Click to collapse
I found the ADB backup doesn't work as well as the other methods. I found some apps didn't seem to get backed up, and at least one didn't work after restoring (though this could be because I used Titanium Backup to restore the app from the ADB backup file).
Hello!
I've just decided to start experimenting with custom ROMs on my new GS4, and I've been trying to begin by backing up all the crucial stuff on my stock device.
When it comes to backing up my 'efs', however, nothing works for me at all. I've tried doing it with Terminal Emulator and a bunch of different commands, all of which come up with errors, and I've tried doing it through custom recoveries like CWM and TWRP.
When I try to do it with the custom recoveries, the process ends almost instantly and it's impossible for me to find the backup files anywhere when I connect my phone to my PC - according to the custom recovery menus, the backups also have virtually no filesize.
My phone is currently running stock TouchWiz 4.2.2, it's rooted and I'm also using Nova launcher. In the past I installed PACMAN ROM but returned to stock by re-installing my old stock firmware with Odin.
Any help would be appreciated - I really wanna let loose and keep experimenting with Android!
Squiddo said:
Hello!
I've just decided to start experimenting with custom ROMs on my new GS4, and I've been trying to begin by backing up all the crucial stuff on my stock device.
When it comes to backing up my 'efs', however, nothing works for me at all. I've tried doing it with Terminal Emulator and a bunch of different commands, all of which come up with errors, and I've tried doing it through custom recoveries like CWM and TWRP.
When I try to do it with the custom recoveries, the process ends almost instantly and it's impossible for me to find the backup files anywhere when I connect my phone to my PC - according to the custom recovery menus, the backups also have virtually no filesize.
My phone is currently running stock TouchWiz 4.2.2, it's rooted and I'm also using Nova launcher. In the past I installed PACMAN ROM but returned to stock by re-installing my old stock firmware with Odin.
Any help would be appreciated - I really wanna let loose and keep experimenting with Android!
Click to expand...
Click to collapse
Maybe this site http://forum.xda-developers.com/showthread.php?t=1068193 is helpfull.
Squiddo said:
Hello!
I've just decided to start experimenting with custom ROMs on my new GS4, and I've been trying to begin by backing up all the crucial stuff on my stock device.
When it comes to backing up my 'efs', however, nothing works for me at all. I've tried doing it with Terminal Emulator and a bunch of different commands, all of which come up with errors, and I've tried doing it through custom recoveries like CWM and TWRP.
When I try to do it with the custom recoveries, the process ends almost instantly and it's impossible for me to find the backup files anywhere when I connect my phone to my PC - according to the custom recovery menus, the backups also have virtually no filesize.
My phone is currently running stock TouchWiz 4.2.2, it's rooted and I'm also using Nova launcher. In the past I installed PACMAN ROM but returned to stock by re-installing my old stock firmware with Odin.
Any help would be appreciated - I really wanna let loose and keep experimenting with Android!
Click to expand...
Click to collapse
I think I've made some success! I can now see my TWRP efs backup files when I connect my phone to my PC... but they're very small. An entire backup folder is only 50.9KB in size. Is this typical for an EFS backup?
Search for EFS Professional on xda. It's a great application that backs up your EFS folder and stores it on your computer where you can restore it if necessary. Simply download it, make sure you have root and busybox installed, along with the Samsung drivers, when it loads, select backup, choose the i9505 filter, choose the partition block which has EFS on the end, and click backup, job done!
The file you may have backed up might be alright, but I've read about the permissions for the folder not being correct, this application ensures everything is ok.
Sent from my GT-I9505
themadba said:
Search for EFS Professional on xda. It's a great application that backs up your EFS folder and stores it on your computer where you can restore it if necessary. Simply download it, make sure you have root and busybox installed, along with the Samsung drivers, when it loads, select backup, choose the i9505 filter, choose the partition block which has EFS on the end, and click backup, job done!
The file you may have backed up might be alright, but I've read about the permissions for the folder not being correct, this application ensures everything is ok.
Sent from my GT-I9505
Click to expand...
Click to collapse
Thanks for your quick response. I'll give that application a whirl now and see how it works for me. On the side, though, I've noticed that each efs backup I've done with TWRP has a slightly different size (deviation of around 3KB each time). Is this, and the fact that each backup is only ~50KB in size normal?
Thanks again for you time!
Squiddo said:
Thanks for your quick response. I'll give that application a whirl now and see how it works for me. On the side, though, I've noticed that each efs backup I've done with TWRP has a slightly different size (deviation of around 3KB each time). Is this, and the fact that each backup is only ~50KB in size normal?
Edit - my EFS partition is only 36KB, whereas the backup on my i9100 was 135KB. The application said the backup was completed successfully, so I'm happy enough. It must be that small.
Thanks again for you time!
Click to expand...
Click to collapse
I'll check my backup on my computer now to see what the file size is. As far as I can remember, it may be around that size, and I noticed that the partition is a lot smaller than the i9100 partition.
Sent from my GT-I9505
themadba said:
Search for EFS Professional on xda. It's a great application that backs up your EFS folder and stores it on your computer where you can restore it if necessary. Simply download it, make sure you have root and busybox installed, along with the Samsung drivers, when it loads, select backup, choose the i9505 filter, choose the partition block which has EFS on the end, and click backup, job done!
The file you may have backed up might be alright, but I've read about the permissions for the folder not being correct, this application ensures everything is ok.
Sent from my GT-I9505
Click to expand...
Click to collapse
I'm attempting this method now using EFS Professional 2.0.46 and the instructions here (http://www.galaxys4manual.com/tips-backup-and-restore-efs-folder-in-samsung-android-devices/). I've installed BusyBox and enabled USB debugging, but EFS Professional keeps giving me this error:
"readlink: applet not found. Please install a BusyBox binary that contains the required applet. BusyBox v1.20.2-Stericson is recommended for compatibility."
Squiddo said:
I'm attempting this method now using EFS Professional 2.0.46 and the instructions here (http://www.galaxys4manual.com/tips-backup-and-restore-efs-folder-in-samsung-android-devices/). I've installed BusyBox and enabled USB debugging, but EFS Professional keeps giving me this error:
"readlink: applet not found. Please install a BusyBox binary that contains the required applet. BusyBox v1.20.2-Stericson is recommended for compatibility."
Click to expand...
Click to collapse
Download the busybox installer from the play store made by Stericson, open it, give it root access, when the install busybox option comes up, select the version EFS Professional application suggests, then try again.
Also, I did post the file size for my backup but it clearly didn't work, it was only 36KB.
Sent from my GT-I9505
themadba said:
Download the busybox installer from the play store made by Stericson, open it, give it root access, when the install busybox option comes up, select the version EFS Professional application suggests, then try again.
Also, I did post the file size for my backup but it clearly didn't work, it was only 36KB.
Sent from my GT-I9505
Click to expand...
Click to collapse
Thank you yet again for your help. I've now got the correct version of BusyBox running and EFS Professional seems to be interfacing with it happily. At this point I realize that the site I linked gives incredibly poor instructions on how to run the EFS Pro program.
I've screencaptured my current situation: http://i.imgur.com/CgHZdiM.png
Do I want to tick only the box with the 'efs' partition name, or do I also want to include the three below it with 'efs' included in the middle of a bunch of other letters and numbers?
Squiddo said:
Thank you yet again for your help. I've now got the correct version of BusyBox running and EFS Professional seems to be interfacing with it happily. At this point I realize that the site I linked gives incredibly poor instructions on how to run the EFS Pro program.
I've screencaptured my current situation: http://i.imgur.com/CgHZdiM.png
Do I want to tick only the box with the 'efs' partition name, or do I also want to include the three below it with 'efs' included in the middle of a bunch of other letters and numbers?
Click to expand...
Click to collapse
See I wasn't sure either, so I've asked on the applications thread on xda here. For the record, I didn't even notice the other three had efs in them, and I only chose the one that has efs at the end. I'll update if any news comes back from the application thread. Also, a simple click of the thanks button is appreciated :thumbup:
Sent from my GT-I9505
---------- Post added at 11:07 AM ---------- Previous post was at 10:52 AM ----------
Well it turns out you select all of the partitions and then back up. I've never done this, and I clearly have never been doing this right. Time to make another back up haha.
Sent from my GT-I9505
themadba said:
See I wasn't sure either, so I've asked on the applications thread on xda here. For the record, I didn't even notice the other three had efs in them, and I only chose the one that has efs at the end. I'll update if any news comes back from the application thread. Also, a simple click of the thanks button is appreciated :thumbup:
Sent from my GT-I9505
---------- Post added at 11:07 AM ---------- Previous post was at 10:52 AM ----------
Well it turns out you select all of the partitions and then back up. I've never done this, and I clearly have never been doing this right. Time to make another back up haha.
Sent from my GT-I9505
Click to expand...
Click to collapse
Looks like we both got something out of this, then! I appreciate your time and input - I was losing my mind over all the obstacles I was running into. Gave you all the thumbs up I could.
Cheers!
EDIT: Oh, wait! Do you mean that you have to select ALL partitions or just those that mention efs in their names?
Squiddo said:
Looks like we both got something out of this, then! I appreciate your time and input - I was losing my mind over all the obstacles I was running into. Gave you all the thumbs up I could.
Cheers!
Click to expand...
Click to collapse
You're very welcome, if you have any other problems, don't hesitate to message me and I'll try my best to help you out, this is a community after all
Edit - all partitions
Sent from my GT-I9505
For some reason it doesn't seem to work. When I look at the play store reviews, they say that Titanium Backup doesn't work well restoring apps with 4.3. For me it just hangs at 0%. 4.3 has been out for a while, what have people been using?
Sent from my Nexus 7 using XDA Premium 4 mobile app
andrewdroid said:
For some reason it doesn't seem to work. When I look at the play store reviews, they say that Titanium Backup doesn't work well restoring apps with 4.3. For me it just hangs at 0%. 4.3 has been out for a while, what have people been using?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, andrewdroid...
Yes, I've just been looking at the reviews you mention, and I must admit, I'm puzzled.
I've been running Jellybean 4.3 (recently updated to build JWR66Y) since the beginning of August, and I've had no problems with restoring apps from Titanium.
I recall, during the first few days of JB 4.3, there where issues with Titanium, and the recommended advice was to change the backup path (where you're backups are stored) as follows...
Go to... Titanium>>Menu>>Backup folder location...
...and navigate (using the back button) to /storage/emulated/legacy/TitaniumBackup ...and select 'Use the current folder'.
And at the time, this worked for me. But subsequent updates to Titanium fixed the problem, and my backup path is now the more technically correct /storage/emulated/0/TitaniumBackup.
Titanium will offer to move the files to the new location, but in the event, nothing actually gets moved, because the locations are actually identical... just different ways of specifying the same location.
So, you could try modifying your backup path location in Titanium settings as outlined above, using either of the two 'paths' I've given. I've just tried both, and in both instances, my backups restored flawlessly.
I've no idea if this will work for you, but I do know there was an issue back in the early part of August, and the 'legacy' path fixed it for me... maybe it might for you.
Hope this helps... and good luck.
Rgrds,
Ged.
Just completed my first root and flashed my tablet to cyanogenmod. I'd like to thank this community for making it so simple. It seemed like a lot of reading but every instruction had a purpose and i understood it more as the process went along. I had no problem throughout the process due to the very detailed instructions here on this forum.
However, I seem to have made one mistake. I used TiBu to backup my apps and data. However, i failed to make the update.zip folder as i didn't think about losing the app when i flashed to the new rom. When i check my device, there is a huge titanium backup folder.
Is there a way i can restore my apps and data from the tibu folder, or did i lose it all by not creating the update.zip folder?
Im afraid to just reinstall TiBu in case it overwrites the old folder.
This is the only problem I had with the whole process and appreciate any help or suggestions.
giusti825 said:
Just completed my first root and flashed my tablet to cyanogenmod. I'd like to thank this community for making it so simple. It seemed like a lot of reading but every instruction had a purpose and i understood it more as the process went along. I had no problem throughout the process due to the very detailed instructions here on this forum.
However, I seem to have made one mistake. I used TiBu to backup my apps and data. However, i failed to make the update.zip folder as i didn't think about losing the app when i flashed to the new rom. When i check my device, there is a huge titanium backup folder.
Is there a way i can restore my apps and data from the tibu folder, or did i lose it all by not creating the update.zip folder?
Im afraid to just reinstall TiBu in case it overwrites the old folder.
This is the only problem I had with the whole process and appreciate any help or suggestions.
Click to expand...
Click to collapse
Rename the huge titanium backup folder, install TiBu, delete new folder and rename huge titanium backup folder back to original name.
I have a Nexus 6P, and need to transfer everything on it (settings, apps, data, etc.) to a new replacement device (also a 6P). Both devices are rooted and have TWRP installed.
I have a TWRP nandroid backup from the original device, and I'm having issues restoring it onto the replacement. When I restore the cache, data, and system backup options, everything seems to work perfectly except for the screen lock and fingerprint security settings. (In addition to the nandroid backup, I also copied the Internal Storage partition of the old device to the new one.)
When I restore the backup and boot up the new device, it has all my settings except for the fingerprints I had saved in Nexus Imprint. I have tried to set up the fingerprints again, and get a "fingerprint not enrolled" error that prevents me from registering my fingerprints again.
I've experimented a little, and have made two backups on the original device -- one with my original screen lock and fingerprint settings, and a second with the finger prints deleted and no screen lock. I've also tried deleting the *.key files locksettings.db from /data/system with no luck. I can access the new device and set up the screen lock again, but can't figure out how to register my fingerprints to use the sensor again.
Please help me get this figured out. I still have the original device on hand, if there's anything I need to change or I need to make a new backup with different settings. (I also have Titanium Backup pro, or could try Helium if that would do it.) Ideally I'd like to find a way to transfer everything without having to set everything up manually on the new device -- user apps, settings, and data (as well as system settings like homescreen setup, widgets, etc.).
Thanks!
indiecognition said:
I have a Nexus 6P, and need to transfer everything on it (settings, apps, data, etc.) to a new replacement device (also a 6P). Both devices are rooted and have TWRP installed.
I have a TWRP nandroid backup from the original device, and I'm having issues restoring it onto the replacement. When I restore the cache, data, and system backup options, everything seems to work perfectly except for the screen lock and fingerprint security settings. (In addition to the nandroid backup, I also copied the Internal Storage partition of the old device to the new one.)
When I restore the backup and boot up the new device, it has all my settings except for the fingerprints I had saved in Nexus Imprint. I have tried to set up the fingerprints again, and get a "fingerprint not enrolled" error that prevents me from registering my fingerprints again.
I've experimented a little, and have made two backups on the original device -- one with my original screen lock and fingerprint settings, and a second with the finger prints deleted and no screen lock. I've also tried deleting the *.key files locksettings.db from /data/system with no luck. I can access the new device and set up the screen lock again, but can't figure out how to register my fingerprints to use the sensor again.
Please help me get this figured out. I still have the original device on hand, if there's anything I need to change or I need to make a new backup with different settings. (I also have Titanium Backup pro, or could try Helium if that would do it.) Ideally I'd like to find a way to transfer everything without having to set everything up manually on the new device -- user apps, settings, and data (as well as system settings like homescreen setup, widgets, etc.).
Thanks!
Click to expand...
Click to collapse
Use titanium backup for apps. And then just restore from last android backup during setup. You can choose to restore your 6P settings and which apps you use. It remembers where you put everything on MM. Even your folders and where they where. Then when it's done restore app data with TB.
Thanks, the built-in Android backup/copy from nearby device worked a lot better and more thoroughly than I'd assumed. Between Helium, TiB, and nandroid backups on hand just in case I need to get more restored for an app or two (which I can extract in Titanium Backup), I think I'm set.
I did realize that the fingerprint and/or screen lock information is saved somewhere in the data partition in TWRP backups. It'd be great if someone can find them and come up with a way to remove them before restoring. Since I was transferring between two of the same devices, using TWRP to restore a nandroid backup should've worked except for the lock features. I wouldn't have restored system (and especially not EFS and Vendor) onto the new device. But data is mostly stuff for user-setup, so it'd be good to be able to have the option to remove or replace the few device-specific contents so it can be used to restore after RMAs, etc. At least for Nexus devices, that'd be a nice way to do a one-shot backup and restore.
indiecognition said:
Thanks, the built-in Android backup/copy from nearby device worked a lot better and more thoroughly than I'd assumed. Between Helium, TiB, and nandroid backups on hand just in case I need to get more restored for an app or two (which I can extract in Titanium Backup), I think I'm set.
I did realize that the fingerprint and/or screen lock information is saved somewhere in the data partition in TWRP backups. It'd be great if someone can find them and come up with a way to remove them before restoring. Since I was transferring between two of the same devices, using TWRP to restore a nandroid backup should've worked except for the lock features. I wouldn't have restored system (and especially not EFS and Vendor) onto the new device. But data is mostly stuff for user-setup, so it'd be good to be able to have the option to remove or replace the few device-specific contents so it can be used to restore after RMAs, etc. At least for Nexus devices, that'd be a nice way to do a one-shot backup and restore.
Click to expand...
Click to collapse
If you were looking for just that its in
data/system/locksettings.db
If you erase that with twrp file manager after a restore you can log in and change your lock settings. There are more lock setting files in the same directory you can delete but the locksetting.db is what keeps you locked out even with the right pin/pattern/password. I have heard it doesn't play nice across devices though. So the route you took should be better IMO.
That only works when restoring a backup to same device. There is a hardware key for the fingerprint reader somewhere else in Data partition tied to device. So, like OP found, when restoring a nandriod to a new device the fingerprint reader won't register fingerprints or work at all bc the hardware is different.
Gizmoe said:
If you were looking for just that its in
data/system/locksettings.db
If you erase that with twrp file manager after a restore you can log in and change your lock settings. There are more lock setting files in the same directory you can delete but the locksetting.db is what keeps you locked out even with the right pin/pattern/password. I have heard it doesn't play nice across devices though. So the route you took should be better IMO.
Click to expand...
Click to collapse
I found that, and it works fine to access the device and setup the lockscreen. But the Nexus Imprint settings are separate from locksetting.db (and the *.key files in the same folder). I just wish there was a way to easily or automatically remove all of the security or lock settings from a TWRP backup and keep the other app and user settings and data. Maybe an option in TWRP or TiB for restoring a backup archive onto a new device that filters out anything that's unique to each device. Or prior to restoring the data parition, TWRP could merge any device-specific files/folders from the new device into an additional file to be kept with the original backup. Something like that.
Some things like call/SMS history, widgets, and a few app settings didn't transfer perfectly using the combo of google's Android backup and Titanium Backup that I went with. And a selective restore from TWRP files might not be hard to develop.
StephenMSmith said:
That only works when restoring a backup to same device. There is a hardware key for the fingerprint reader somewhere else in Data partition tied to device. So, like OP found, when restoring a nandriod to a new device the fingerprint reader won't register fingerprints or work at all bc the hardware is different.
Click to expand...
Click to collapse
I covered that. It's in the last part of what I wrote. But you were more elaborate.
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
indiecognition said:
I found that, and it works fine to access the device and setup the lockscreen. But the Nexus Imprint settings are separate from locksetting.db (and the *.key files in the same folder). I just wish there was a way to easily or automatically remove all of the security or lock settings from a TWRP backup and keep the other app and user settings and data. Maybe an option in TWRP or TiB for restoring a backup archive onto a new device that filters out anything that's unique to each device. Or prior to restoring the data parition, TWRP could merge any device-specific files/folders from the new device into an additional file to be kept with the original backup. Something like that.
Some things like call/SMS history, widgets, and a few app settings didn't transfer perfectly using the combo of google's Android backup and Titanium Backup that I went with. And a selective restore from TWRP files might not be hard to develop.
Click to expand...
Click to collapse
Yeah security is good, but it's making the days of transferring data and modifying partitions much harder.
Gizmoe said:
I covered that. It's in the last part of what I wrote. But you were more elaborate.
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
Yeah security is good, but it's making the days of transferring data and modifying partitions much harder.
Click to expand...
Click to collapse
I had these problems too. How exactly do I disable those security settings? In the my file manager, I can't seem to find what I need. Can someone please explain how I go about disabling these settings so I can make a nandroid? Thanks so much.
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
This works!!! Thank you!!!!
myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
u are awesome
thanks
myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
Just got an N6P RMA. Deactivated screen lock and fingerprints on the old device, then made a full nandroid backup in TWRP. Restored boot, system, data, and cache partitions onto the new device.
Initially the new phone couldn't register fingerprints after the restore. Deleted the folders that myshen suggested. Had to reboot, but was able to add my fingerprints with no problem after that. :good: Worked like a charm.
Thanks for the great tip!
myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
I can't believe this isn't pinned. This is a major, major issue for anyone RMAing their phone or anything like that. Thank you so much for this solution, it was not easy to find!!!
kwest12 said:
I can't believe this isn't pinned. This is a major, major issue for anyone RMAing their phone or anything like that. Thank you so much for this solution, it was not easy to find!!!
Click to expand...
Click to collapse
It is pinned.
https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
after multiple attempts of using TB to restore phone, i did a twrp backup, and this worked. thank you
myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
you got any idea where "fpc" went with android 9 on the pixel 3? i'm having the the same problem .. could only find "settings_fingerprint.xml" and deleted this, but problem persits .. thx in advance!
androidfreak11 said:
you got any idea where "fpc" went with android 9 on the pixel 3? i'm having the the same problem .. could only find "settings_fingerprint.xml" and deleted this, but problem persits .. thx in advance!
Click to expand...
Click to collapse
Amazing how we all run into issues which have been looked at by many people and solutions proposed over a period of time....
Anyhow, I faced the same issue. The trick as outlined above didn't seem to work at first.I did a 'find /data -name fpdata'. It turned its now living in a different folder: /data/vendor_de/0/fpdata. A quick 'mv /data/vendor_de/0/fpdata /data/vendor_de/0/fpdata.org' from root shell, followed by reboot fixed the issue.
There seems to be no 'fpc' folder anywhere in 9.
devsk said:
Amazing how we all run into issues which have been looked at by many people and solutions proposed over a period of time....
Anyhow, I faced the same issue. The trick as outlined above didn't seem to work at first.I did a 'find /data -name fpdata'. It turned its now living in a different folder: /data/vendor_de/0/fpdata. A quick 'mv /data/vendor_de/0/fpdata /data/vendor_de/0/fpdata.org' from root shell, followed by reboot fixed the issue.
There seems to be no 'fpc' folder anywhere in 9.
Click to expand...
Click to collapse
All I ever did is erase locksettings.db in /data/system and all was fine. Haven't used the 6p in a bit though.
Gizmoe said:
All I ever did is erase locksettings.db in /data/system and all was fine. Haven't used the 6p in a bit though.
Click to expand...
Click to collapse
I faced this issue on Pixel 3, where I restored from a /data backup from my earlier Pixel 3.