Database Users

updating to newest sprint code.. errors!

so i did a nandroid restore.. downloaded the update and it fails with:
Finding update package...
I:Update location: CACHE:fumo/update.pkg
Opening update package...
I:Update file path: /cache/fumo/update.pkg
Verifying update package...
W:Can't verify META-INF/CERT.RSA
E:No signature (265 files)
E:Verification failed
Installation aborted.
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""

slackwaresupport said:
so i did a nandroid restore.. downloaded the update and it fails with:
Finding update package...
I:Update location: CACHE:fumo/update.pkg
Opening update package...
I:Update file path: /cache/fumo/update.pkg
Verifying update package...
W:Can't verify META-INF/CERT.RSA
E:No signature (265 files)
E:Verification failed
Installation aborted.
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Click to expand...
Click to collapse
Based on your errors (thanks for putting them all in there) it looks like you downloaded the update directly from Sprint (OTA), so you would think that the download itself was fine. But if it's saying it's not signed then the download must be corrupted. Try going back through the menu and saying firmware update again. If it says there isn't one available then you may need to delete update.pkg and reboot and try again.
Also just an FYI, Fresh ROM 4.0+ has the new update already in it.

ya.. ive was on modaco.. just didnt like it. is the fresh really that good?? i had problems with modaco when i goto edit a contact, it says social network not available, and doesnt let me edit it.

flipzmode said:
Based on your errors (thanks for putting them all in there) it looks like you downloaded the update directly from Sprint (OTA), so you would think that the download itself was fine. But if it's saying it's not signed then the download must be corrupted. Try going back through the menu and saying firmware update again. If it says there isn't one available then you may need to delete update.pkg and reboot and try again.
Also just an FYI, Fresh ROM 4.0+ has the new update already in it.
Click to expand...
Click to collapse
fresh rom 4.0+???? i only see 0.6b..

slackwaresupport said:
fresh rom 4.0+???? i only see 0.6b..
Click to expand...
Click to collapse
I meant it's been included since 4.0. Grab 0.6b if you like the blue theme (check the screen shots) or just 0.6 if you don't want the theme.
And you can't ask if I think it's that good... I make it.

slackwaresupport said:
ya.. ive was on modaco.. just didnt like it. is the fresh really that good?? i had problems with modaco when i goto edit a contact, it says social network not available, and doesnt let me edit it.
Click to expand...
Click to collapse
It is the best at the best at this time. With updates that are very praid . usually with in a few hours of changes

OTA to 4.4.2 failed ["/system/bin/app_process" has unexpected contents.]

Can anyone help me.
Having problems with the OTA update from 4.4 to 4.4.2
I'm running Stock OS rooted with TWRP, BusyBox 1.2.1.1 & SuperSU 1.80
When I run the update TWRP gives the following error in the log:
Code:
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip'...
Checking for MD5 file...
I:Cannot find file /cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Verifying current system...
file "/system/bin/app_process" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/app_process" has unexpected contents.
"/system/bin/app_process" has unexpected contents.
E:Error executing updater binary in zip '/cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip'
Error flashing zip '/cache/4f6d2fc7377dbb48caecaa658bb139da2b063b33.signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip'
Updating partition details...
I:Data backup size is 2457MB, size: 13231MB, used: 8064MB, free: 5299MB, in data/media: 5606MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Think it's something to do with BusyBox and how it installs, is it fixable without a total wipe?
Had the same issue with the OTA upgrade to 4.4 (had to do a total wipe and lost a lot of files on the virtual SDcard as a result).

Not sure if it is busybox causing your issue or not. What the error means is that something in your system is not as it should be. Did you remove or modify any system apps?
You can have root and a custom recovery, but you must be TOTALLY stock in order for the OTA to work.

*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.

s0litaire said:
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
Click to expand...
Click to collapse
Yep, I did the same thing. It's even worse when you notice it clearly says "app_process" in the Xposed installer.

korockinout13 said:
Yep, I did the same thing. It's even worse when you notice it clearly says "app_process" in the Xposed installer.
Click to expand...
Click to collapse
same here i still cant update altough i do factory reset and get this message
"/system/bin/app_process" has unexpected contents.
E:Error in tmp/update.zip
(Status 7)
Instalation Aborted
what should i do?

ditrix99 said:
same here i still cant update altough i do factory reset and get this message
"/system/bin/app_process" has unexpected contents.
E:Error in tmp/update.zip
(Status 7)
Instalation Aborted
what should i do?
Click to expand...
Click to collapse
Did you read this thread? It clearly explains in several posts above. You need to uninstall Xposed framework.

Same problem but a little different
korockinout13 said:
Did you read this thread? It clearly explains in several posts above. You need to uninstall Xposed framework.
Click to expand...
Click to collapse
So I am trying to upgrade to 4.4.3 and having the same issue however i cannot uninstall Xposed. The xposed uninstaller does not find process_app.orig to uninstall/resotre the original file. Where can I get this original file. Any suggestion on what to do next?

buysellonline said:
So I am trying to upgrade to 4.4.3 and having the same issue however i cannot uninstall Xposed. The xposed uninstaller does not find process_app.orig to uninstall/resotre the original file. Where can I get this original file. Any suggestion on what to do next?
Click to expand...
Click to collapse
Have you installed xposed right? You have to open Xposed App and tap to "Install/Update" then "Uninstall". Remember to remove also all modules.
You should remove also ROOT files, just open SuperSU and uninstall it from SuperSU settings.

Agosh13 said:
Have you installed xposed right? You have to open Xposed App and tap to "Install/Update" then "Uninstall". Remember to remove also all modules.
You should remove also ROOT files, just open SuperSU and uninstall it from SuperSU settings.
Click to expand...
Click to collapse
- Yes, I have installed xposed correctly and have been using it for months.
- Yes, I have deleted all modules from within xposed prior to attempting to uninstall.
- Yes, I have used xposed to do the uninstall - it fails, to restore the process_app.
- Uninstalling from any other app will not restore the original process_app file.
I need to push the file to my phone manually but I do not where I can get it from and unfortunately xposed did not make a copy of it for some odd reason. So here you have it. I guess if I cannot locate the file, my only option to fastboot a full version of the 4.4.3 losing everything on the phone. I know how to do that, I hope

s0litaire said:
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
Click to expand...
Click to collapse
I can't believe I didn't think of that... I'm glad I'm not the only one that's done this though!

buysellonline said:
- Yes, I have installed xposed correctly and have been using it for months.
- Yes, I have deleted all modules from within xposed prior to attempting to uninstall.
- Yes, I have used xposed to do the uninstall - it fails, to restore the process_app.
- Uninstalling from any other app will not restore the original process_app file.
I need to push the file to my phone manually but I do not where I can get it from and unfortunately xposed did not make a copy of it for some odd reason. So here you have it. I guess if I cannot locate the file, my only option to fastboot a full version of the 4.4.3 losing everything on the phone. I know how to do that, I hope
Click to expand...
Click to collapse
I have the same problem. There is no app_process.orig file in the /system/bin directory. Does anyone have an original 4.4.2 app_process file for the Nexus 10?
This link shows how to use the full image without losing your data. I haven't tried it myself and would have preferred to just use the OTA image instead. But I may end up having to fall back on that approach.

Hi, been trying to update OTA with no success here. No idea if it's the same issue with app_process but here's what I've done
- Device status: Custom, so installed xposed framework, installed wanam, tick Fake system status and Device status changed to Official
- Choose System Update, and it's working fine up till this point
- Install the update and update will failed since wanam is still enabled (and it deletes the update file, so next time I want to OTA I have to redownload all 600 megs again )
- Now I tried to disable wanam and uninstall xposed (because I don't think I should uninstall xposed without disabling wanam first), however whenever I disabled wanam Device status will then reverted to Custom, preventing the install even if the update has been successfully downloaded (and yes, it deletes the update file again)
So any idea how to do it correctly then? Thanks

Garock said:
Hi, been trying to update OTA with no success here. No idea if it's the same issue with app_process but here's what I've done
- Device status: Custom, so installed xposed framework, installed wanam, tick Fake system status and Device status changed to Official
- Choose System Update, and it's working fine up till this point
- Install the update and update will failed since wanam is still enabled (and it deletes the update file, so next time I want to OTA I have to redownload all 600 megs again )
- Now I tried to disable wanam and uninstall xposed (because I don't think I should uninstall xposed without disabling wanam first), however whenever I disabled wanam Device status will then reverted to Custom, preventing the install even if the update has been successfully downloaded (and yes, it deletes the update file again)
So any idea how to do it correctly then? Thanks
Click to expand...
Click to collapse
First off, next time you get the ota go into /cache and copy the zip file somewhere else so you don't have to download it again. You need to uninstall xposed from within the app
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
First off, next time you get the ota go into /cache and copy the zip file somewhere else so you don't have to download it again. You need to uninstall xposed from within the app
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, tried that as well. However even if I copied update.zip back to /cache/fota, software update still redownload the whole thing again
And yeah, I uninstalled xposed from the app
Question, in my previous post, after each steps (disable wanam, uninstall xposed) I always rebooted to apply the changes and device status reverted back to Custom after I disabled wanam and then reboot. Should I uninstall xposed without rebooting first?
I mean should it be like disable wanam (no reboot) then uninstall xposed (again no reboot) and straight to do software update?
Thanks for the reply though
Edit:
Okay, tried this.
Disable wanam (no reboot) so Device status still at Official. Then uninstall xposed (no reboot), app_process has also reverted to original. Last temporary disable root using Voodoo OTA Rootkeeper. But still software update failed
Any idea what other things causing software update refuse to updating?
I did however modify /system/csc/feature.xml, does it matter?

s0litaire said:
*slap my head and call me stupid*
Just remembered I installed the exposed framework.
That's what's causing the problem. Uninstalled and the ota ran fine.
Click to expand...
Click to collapse
Thanks

[ROM] Kali NetHunter

Go away. This project has been long dead. People continue to necro this for some reason

Screenshots
Just the kernel and desktop. Cywnogenmod shows up as its used as a base

Reserved

Its good that you let us know about this. Do you have link to original thread/development work? Also what is this update-nethunter? size is around 65 mb. Little more info, source will be required before I flash this.

saurabh40629 said:
Its good that you let us know about this. Do you have link to original thread/development work? Also what is this update-nethunter? size is around 65 mb. Little more info, source will be required before I flash this.
Click to expand...
Click to collapse
Uodated the OP with kernel source.
As far as the oringal thread there never was one. I just stumbled on Phreya's work. You could probably contact him here:
https://forums.kali.org/member.php?40476-Phreya
Update NetHunter as you refer to it is the framework required for things such as Chroot along with a few applications included within a normal NetHunter install. The reason it's so small is because you still need to download Kali (done in the NetHunter app)

Some ss will nice!

Some screenies plz
Sent from my OnePlus X using Tapatalk

@RJDTWO , what is this exactly?

sankarshan said:
@RJDTWO , what is this exactly?
Click to expand...
Click to collapse
Its a ROM for penetration testing. Its derived from Kali Linux.

sarthakspiker said:
Some screenies plz
Sent from my OnePlus X using Tapatalk
Click to expand...
Click to collapse
I updated the OP

I've tried googling but can't find what is it ? Is it just a kernel or a new rom ? What's its features ?

namquang93 said:
I've tried googling but can't find what is it ? Is it just a kernel or a new rom ? What's its features ?
Click to expand...
Click to collapse
Its a kernel along with penetration testing tools that runs on top of CM which is why I refer to it as a ROM. It functions slightly different than CM so I can't really call it a modified version of CM. You know Sailfish? Its kind of like that. The difference being Kali works alongside CM versus just using the libraries

fresh install
rebooted it couple of times
cant connect to wifi
also cant seem to find application or option to use kali nethunter?!
Code:
ui_print
Installing NetHunter App
Installing NetHunter Terminal
Installing BlueNMEA
Installing Hacker's Keyboard
Installing RFAnalyzer
Installing Shodan
Installing USB Keyboard
Installing VNCInstalling RouterKeygen
Installing cSploit Nightly
Installing DriveDroid Free
@Freeing up some space on /system
@Running busybox installer...- Installing busybox...
@Installing NetHunter wallpaper
- Found screen resolution: 1080x1920
- NetHunter wallpaper applied successfully
@Installing NetHunter boot animation
Copying nano highlights to /system/etc/nano
Copying terminfo files to /system/etc/terminfo
Copying shared libraries to /system/lib
Installing /system/bin binaries
Installing init.d scripts
@Symlinking Kali boot [email protected] kernel installer...
######################################################
NetHunter Kernel Installer
Phreya Kernel by Phreya (version: 1.0)
######################################################
/sbin/getprop
Checking device compatibility...
Installing busybox applets to /sbinFreeing some space on /system
Copying firmware to /system/etc/firmware
Copying shared libraries and kernel modules to /system/lib
Installing /system/xbin binariesRunning boot image patcher...
- Found boot partition at: /dev/block/platform/msm_sdcc.1/by-name/boot- Dumping & unpacking original boot image...
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.372661 seconds, 42.9MB/s
Android magic found at: 0
BOARD_KERNEL_CMDLINE androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1
BOARD_KERNEL_BASE 00000000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 01000000
BOARD_TAGS_OFFSET 00000100
BOARD_DT_SIZE 2236416
- Detected ramdisk compression format: gzip
/sbin/gzip
6296 blocks
- Running ramdisk patching scripts...- Executing: 01-ramdisk-patch
-- Patching the ramdisk for NetHunter & init.d...- Executing: 02-supersu
-- Patching the sepolicy for SuperSU...supolicy v2.67 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire
Patching policy [/tmp/nethunter/boot-patcher/ramdisk/sepolicy] --> [/tmp/nethunter/boot-patcher/ramdisk/sepolicy_new] ...
- Success
- Building new ramdisk...
- Found replacement kernel zImage!- Found replacement ramdisk image!- Backing up old boot image to /data/local/boot-backup.img...
- Writing new boot image to memory...29420+0 records in
29420+0 records out
15063040 bytes (14.4MB) copied, 2.412514 seconds, 6.0MB/s
Boot image patching complete
@Running Kali chroot installer...
ls: /tmp/nethunter/kalifs-*.tar.xz: No such file or directory
ls: /data/local/kalifs-*.tar.xz: No such file or directory
- No Kali rootfs archive found. Skipping...
************************************************
* Kali NetHunter is now installed! *
* Please ignore any errors in TWRP regarding *
* /data/local/nhsystem/kali-armhf/dev/ *
************************************************
I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Data backup size is 425MB, free: 10209MB.
I:sending message to remove 65537
mtppipe remove storage 65537
I:Message sent, remove storage ID: 65537
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /usb_otg/recovery.log

dark3bod said:
fresh install
rebooted it couple of times
cant connect to wifi
also cant seem to find application or option to use kali nethunter?!
Click to expand...
Click to collapse
WiFi is related to CM itself. For some it works and for others it won't.
Weird. I have it. You flashed the kernel and update???

RJDTWO said:
WiFi is related to CM itself. For some it works and for others it won't.
Weird. I have it. You flashed the kernel and update???
Click to expand...
Click to collapse
flashed only the update sorry

is there any full guide how to install

did the dev approve of this thread tho??

Hakim Farouk said:
did the dev approve of this thread tho??
Click to expand...
Click to collapse
I posted it in general because it was something I found. It isn't official.
I will however be compiling the source myself and building it with an official release soon.

danger-end said:
is there any full guide how to install
Click to expand...
Click to collapse
Wait. I will be releasing the official version soon

error code 7
hi friends i stuck while flashing CM 13
i also did factory reset but same result on onepus x 16gb
error code 7 is the error
thanks RJDTWO waiting
now i downloaded your latest release this gives error can,t install this package on top of incompetible data
please try another package or run a factory reset

Twrp error 255

When I tried do backup in twrp recovery I always end with error 255
There's log if this help.
Thankshttp://cloud.tapatalk.com/s/59dc5f7f153b3/last_log.txt
Odoslané z ONEPLUS A5000 pomocou Tapatalku

Yup, same here! I always getting it while trying doing an restore via ADB (copy backupped TWRP folder via commands to internal device storage)
I would like a solution to for this frustrating Tarfork 255 error!
This is what i asked and mentioned to one of our Team Members and i tried everyting;
First: *I don't like the idea of "wipe data" clean restoring is to me included "format data*
Secondly: *if i backup my data also along with system and all (exclusive recovery, cache and system image) and move it to my pc via ADB and than wipe and format all in twrp and than move my TWRP back up via ADB back to my Device, than restoring fails...*
Thirdly: *So the only way you can restore is NOT to format Data(internal) while restoring. But that just doesn't make sense. Because the Data is dirty if you flash another ROM and than restore your previous ROM*
So in my opinion when you restoring without the Data formatted, it stays dirty when you restoring. Also i don't want dirty data from other ROMs if you know what i mean..
I like to know an very satisfying solution! And hopefully someone can enlightening us:crying:

It's very simple.. If you can find through the log the "guilty" app just uninstall it and re-do TWRP backup.. If you can't find that (or those) app you need to wipe data... When you're 100% sure that the problem is in data partition (try to backup it alone) so the solution is the above... :good:
---------- Post added at 20:15 ---------- Previous post was at 20:13 ----------
lekiaM said:
Yup, same here! I always getting it while trying doing an restore via ADB (copy backupped TWRP folder via commands to internal device storage)
I would like a solution to for this frustrating Tarfork 255 error!
This is what i asked and mentioned to one of our Team Members and i tried everyting;
First: *I don't like the idea of "wipe data" clean restoring is to me included "format data*
Secondly: *if i backup my data also along with system and all (exclusive recovery, cache and system image) and move it to my pc via ADB and than wipe and format all in twrp and than move my TWRP back up via ADB back to my Device, than restoring fails...*
Thirdly: *So the only way you can restore is NOT to format Data(internal) while restoring. But that just doesn't make sense. Because the Data is dirty if you flash another ROM and than restore your previous ROM*
So in my opinion when you restoring without the Data formatted, it stays dirty when you restoring. Also i don't want dirty data from other ROMs if you know what i mean..
I like to know an very satisfying solution! And hopefully someone can enlightening us:crying:
Click to expand...
Click to collapse
If you format Data you'll decrypt partion and when you go restoring a previous backup done with encryption it won't work.. You can even restore a full backup on a fully working system the recovery will wipe everything for you before continue (with everything i mean those partition that yuo've previously backuped)

Aaah i see. This is what i've got;
A backup (stored in my internal and PC) i made this backup on an running "encrypted" device. But in TWRP i had to decrypt it by password so the backup i made in TWRP is automaticly decrypted right? because of the pincode i insert to decrypt my data.
But let's see, if i want to; let say.. switch to another Custom Rom. The only way is to "wipe" all and flash the new Custom Rom? This without Formatting "Data"? (as i suppose) because if i format the "data" i'm not able to restore my backup. This does make completely sense to me. But..... one thing i don't understand is this;
Why is it possible to make an full backup in TWRP, push it via ADB to PC, going back to twrp "wipe" and "format" all, reboot TWRP, pull the backup from PC via ADB again to TWRP and restore. But it won't restore why? why? because i formatted the "data"? so the only way to restore is (with the "dirty" data from previous ROM's than)...
Anyway, i wish it all was easier... Maybe i make it myself to hard to understand, i dunno.... But hey, thanks for your feedback! appreciate

lekiaM said:
Aaah i see. This is what i've got;
A backup (stored in my internal and PC) i made this backup on an running "encrypted" device. But in TWRP i had to decrypt it by password so the backup i made in TWRP is automaticly decrypted right? because of the pincode i insert to decrypt my data.
But let's see, if i want to; let say.. switch to another Custom Rom. The only way is to "wipe" all and flash the new Custom Rom? This without Formatting "Data"? (as i suppose) because if i format the "data" i'm not able to restore my backup. This does make completely sense to me. But..... one thing i don't understand is this;
Why is it possible to make an full backup in TWRP, push it via ADB to PC, going back to twrp "wipe" and "format" all, reboot TWRP, pull the backup from PC via ADB again to TWRP and restore. But it won't restore why? why? because i formatted the "data"? so the only way to restore is (with the "dirty" data from previous ROM's than)...
Anyway, i wish it all was easier... Maybe i make it myself to hard to understand, i dunno.... But hey, thanks for your feedback! appreciate
Click to expand...
Click to collapse
encrypted backup and a backup of a encrypted device is 2 different things.. When you do a TWRP backup you can choose to encrypt it with a password, it will encrypt that archive backup, but you can also do a TWRP backup of your encrypted device without encrypting the backup, hope this is clear
Second point.. Why you need to format every time? Format here on op5 can cause the data partition to switch from ext4 on f2fs and is not really necessary everytime... Example.. I'm on Resurrection Remix but today i want to change rom but first i want to take a backup, so i reboot in TWRP, do the backup (without encrypt the backup itself, it's not really necessary, indeed it can be risky) then i wipe cache-dalvik/art cache-system-data NO INTERNAL STORAGE then i install my new custom rom
It's really easier as you were thinking but maybe you've done some confusion with format/wipe and encrypted/decrypted
Your problem of restoring the backup is due to this ---> Probably, when you do the TWRP backup you're encrypted then you move it to the PC and here there's nothing wrong, but after this you format data and this will decrypt your device, so like i said above, your restoring isnt working because you want to restore an encrypted backup on a decrypted device
Avoid format and instead use the wipe function :good:

Now i see!!! Finally.. You're second post made it all clear to me! I keep this post in my subscriptions, so i can always look back.
Thanks again! (and for you're time to explain) :highfive:

from recovery log
Enyone can help with this, still ending with error 255
I:addFile '/data/system_ce/0/shortcut_service/shortcuts.xml' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/system_ce/0/recent_images' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
found policy '/data/system_ce/0/recent_images' - '1CE0' - '031a968edf614759'
I:addFile '/data/system_ce/0/recent_images/9416_task_thumbnail.png' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
I:addFile '/data/system_ce/10' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/10' - 'cddc5aeae0e4e778'
I:Error adding file '/data/system_ce/10' to '/data/media/0/TWRP/BACKUPS/d3d80913/2017-10-14--14-19-57/data.ext4.win010'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/d3d80913/2017-10-14--14-19-57/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/d3d80913/2017-10-14--14-19-57/recovery.log
I:Set page: 'action_complete'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Iperation_end - status=1
I:Set overlay: ''
I:Set page: 'clear_vars'
I:Set page: 'backup'
Truncating string cache entries.
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
Iperation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse

chlap said:
Enyone can help with this, still ending with error 255
Click to expand...
Click to collapse
Have you tried to backup Data only partition?
As I said above the 255 error is due to damaged file/s

Hitman478[emoji769 said:
;74161048]Have you tried to backup Data only partition?
As I said above the 255 error is due to damaged file/s
Click to expand...
Click to collapse
Tried backup Data. Same error.
Odoslané z ONEPLUS A5000 pomocou Tapatalku

If you are getting the same error again and qgain, i know its frustrating! And i also know to find the culprit for the error, is very hard. So i suggest start from scratch? I mean wipe all and format data, reboot to recovery, flash the latest "stable" and "improved" blu spark TWRP as recovery. Reboot recovery again, transfer the ROM, Gapps package and root method from PC to Internal and flash, reboot.
I know it's not an solution you'll be waiting for, but i ended up the same way too (as you can see earlier posts) . But since Hitman478 explained all to me, i have no issues anymore! which I'm truly great full for.
Have a nice Sunday (after all) :highfive:

chlap said:
Tried backup Data. Same error.
Odoslané z ONEPLUS A5000 pomocou Tapatalku
Click to expand...
Click to collapse
There's a corrupted file.. if you can't find it out and delete/uninstall that app, you never will be able to backup.. your solution is to clean install again your room (but first look at log and watch where TWRP gives you the error)

I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.

larpoux said:
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users
Click to expand...
Click to collapse
Thanks! That was the clue I needed! I had installed the app Shelter lately which created a work profile (= second user). Uninstalling Shelter and deleting the work profile solved the problem.

Hi, I use App2SD and this error occurs with the date partition. It's probably the symlinks.

TWRP Backup fails with message "createTarFork() process ended with ERROR 9"

Hello,
I've got a problem I couldn't find a solution for: Before trying to flash a custom ROM, I wanted to do a Backup of the "original" system (rooted samsung android 4.4.2 KitKat). As listed by the devs of TWRP on their site (https://twrp.me/faq/whattobackup.html), I selected system, data and boot. System and boot were backuped to card without error (when selected without data), but backing up data always fails with error message "createTarFork() process ended with ERROR 9".
I could find threats about error 255, but nothing about error 9. Can you please help me solving this issue so I can create a backup of media as well?
These are the last lines of recovery.log:
I:InfoManager saving '/external_sd/TWRP/BACKUPS/1633cc05/2019-05-15--20-00-46_KOT49HI9301IXCUAOF1/data.info'
Prozess createTarFork() endete mit Meldung: 9 // createTarFork() process endet with message 9
Sicherung fehlgeschlagen, bereinige Sicherungs-Verzeichnis // creating backup failed. cleaning up...
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/1633cc05/2019-05-15--20-00-46_KOT49HI9301IXCUAOF1/recovery.log
Click to expand...
Click to collapse