Database Users

[Q] set_metadata_recursive: some changes failed

HI! I'm building Android 4.4 but when I try to flash the ROM via TWRP, I get the following error:
minzip: Extracted 1226 file(s)
ApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/box/i9305/omni-4.4-20131107-i9305-HOMEMADE.zip'
Error flashing zip '/external_sd/box/i9305/omni-4.4-20131107-i9305-HOMEMADE.zip'
Any advice on what is needed to fix this fault is appreciated!
Is the recovery.img produced during ROM build flashable? It is 2MB smaller than the TWRP recovery image.

Hey, so I went through this yesterday (see the Q & A section) and while I didn't resolve it completely, I know that it's because of selinux, and you need a newer version of TWRP. Right now in the Omni 4.4 manifest it actually has the AOSP recovery so you'll wanna change that to Omni 's TWRP on a local manifest. Beyond that it depends on your BoardConfig.mk whether your recovery is flash able, if you configured it ok then yes!
Check the links Entropy512 posted in this thread for more on TWRP configuration: http://forum.xda-developers.com/showthread.php?t=2499514
In particular make sure you have a proper fstab in v1 format (see my last post in that thread for more details as well). My recovery built after I fixed the twrp.fstab at least looks and acts like a proper recovery, but haven't done anything with it yet for lack of time.

The reason for that message can be in the kernel configuration.
If those options are not set, this will cause this message:
Code:
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
regards Uwe

I used for fix that ROM Manager app from Play Store and update to the latest CWM recovery. DO NOT USE TWRP!!! Just update that.

u.k-f said:
The reason for that message can be in the kernel configuration.
If those options are not set, this will cause this message:
Code:
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
regards Uwe
Click to expand...
Click to collapse
Thanks.. I have all those set for Ext4 (the only FS used) and still no luck ....

mcampbellsmith said:
Thanks.. I have all those set for Ext4 (the only FS used) and still no luck ....
Click to expand...
Click to collapse
Did you enable SELINUX in the kernel used for recovery?
The xattributes to be written are SELINUX Attributes...
Regards Uwe

u.k-f said:
Did you enable SELINUX in the kernel used for recovery?
The xattributes to be written are SELINUX Attributes...
Regards Uwe
Click to expand...
Click to collapse
Thanks for your help everyone.
Recompiled TWRP and it works.
CWM also works when updated.
Cheers!

It is weird. I have compiled TWRP in the omni tree. The kernel config does contain the selinux settings:
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
But i am still getting the set_metadata_recursive stuff. Do i have to include HAVE_SELINUX ? I thought that was for android versions <4.3
I did a clean / clobber before building, but i added also a kernel command to make selinux permissive
Do i have to cherrypick something to make it work?
EDIT:
Hmm somehow the new recovery image is not flashed ?

With the change from Android 4.2 to Android 4.3 I needed to enable SELINUX in the Kernel-Config.
Did you do this?
And, by the way, you do not need to install your new recovery, you can start ist from bootloader with
Code:
fastboot boot recovery.img
without installing it any time you build a new version
regards uwe

u.k-f said:
With the change from Android 4.2 to Android 4.3 I needed to enable SELINUX in the Kernel-Config.
Did you do this?
And, by the way, you do not need to install your new recovery, you can start ist from bootloader with
Code:
fastboot boot recovery.img
without installing it any time you build a new version
regards uwe
Click to expand...
Click to collapse
I fixed the problem. It was because of the fact that the image was bigger then the partition size. Using another kernel compression solved it.
Sent from my Xperia T using Tapatalk

mcampbellsmith said:
Thanks for your help everyone.
Recompiled TWRP and it works.
CWM also works when updated.
Cheers!
Click to expand...
Click to collapse
Can you explain what you changed in the CWM tree to successfully flash 4.4?

scanno said:
I fixed the problem. It was because of the fact that the image was bigger then the partition size. Using another kernel compression solved it.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
hi
please explain all fix do, others dev have solution and clue...
we have to leave answer for duture and actual dev
thank you very much

lordtillt said:
Can you explain what you changed in the CWM tree to successfully flash 4.4?
Click to expand...
Click to collapse
Nothing.
The latest version of CWM that was available from the website was quite old. Recompiling it with latest sources worked fine.

desalesouche said:
hi
please explain all fix do, others dev have solution and clue...
we have to leave answer for duture and actual dev
thank you very much
Click to expand...
Click to collapse
My changes were for the TF300T. The commits are on gerrit. You can see the TWRP configuration and the changes needed in the kernel.
Sent from my Xperia T using Tapatalk

scanno said:
My changes were for the TF300T. The commits are on gerrit. You can see the TWRP configuration and the changes needed in the kernel.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
can you send a link please?...thank you...

In short, if you want to flash KitKat Android 4.4, you'll have to upgrade to a version of CWM greater than v6.0.4.5. Or, use an alternate bootloader.

Try out another recovery.
I got this pb with phil touch, then I try it on TWRP and the ROM is now installed correctly : )

testing AOSP Marshmallow 6.0 for Z2 following Ev3rtH's

I tried to make rom working modem following Ev3rtH's result "AOSP Marshmallow 6.0 for Z1 Compact"
when i test in my z2, modem works (IMEI,SIM,Data,call...)
and the working and not working are same as Ev3rtH's posting
Working and Not working :
Working:
-Boots
-Screen
-Brightness
-Orientation sensor
-Ambient light sensor
-Wifi
-Bluetooth
-IMEI shows up, still have to test with SIM
Not working:
-Camera
-NFC
-GPS (haven´t tested yet)
-Internal SD doesn´t mount right - As pointed out by tgascoigne, if you´re playing around with the mount points and Android asks you to format it, DON´T. You will wipe the boot and system partitions.
It is not official build and unstable
Is there any problem in this post, please give a comment
contributors and reference
Ev3rtH, nickholtus
Download :
dropbox:
IMGs : https://www.dropbox.com/sh/yb3l8j5gjtx0zo6/AACT8LdwfiXGKxo29VxNd5oQa?dl=0
IMGs zip : https://www.dropbox.com/sh/yb3l8j5gjtx0zo6/AACT8LdwfiXGKxo29VxNd5oQa?dl=1
flashable .zip (cannot use because of error) : https://www.dropbox.com/s/lbdm3vxiikqzp3n/aosp_d6503-ota-eng.choirakwon.zip?dl=0
Google drive:
IMGs : https://drive.google.com/folderview?id=0ByjmFQapr1xqOWY0ZmM2aHUxaU0&usp=sharing
flashable .zip (cannot use because of error) : https://drive.google.com/file/d/0ByjmFQapr1xqWk5wLVZQYkF5eDg/view?usp=sharing
Changelog :
Adding /vendor/sony/sirius/proprietary/etc/firmware/modem.bxx from 23.4.A.1.232
Modify /vendor/sony/sirius/sirius-partial.mk
Modify /vendor/sony/sirius/proprietary/Android.mk
Modify /vendor/qcom/prebuilt/proprietary/common/vendor/lib/libaudcal.so
It is almost same as https://github.com/tg-togari-marshmallow in http://forum.xda-developers.com/xpe...marshmallow-6-0-z-ultra-t3224321/post63278643

That's only a preview version, or a Concept version? all the Marshmallow features are working?

stayawake said:
That's only a preview version, or a Concept version? all the Marshmallow features are working?
Click to expand...
Click to collapse
It is same build as sony developer world's AOSP build instruction Android6.0.0_r1 except modem fix
I have not tried all the features, after trying i'll comment about that

nakwonelec said:
It is same build as sony developer world's AOSP build instruction Android6.0.0_r1 except modem fix
I have not tried all the features, after trying i'll comment about that
Click to expand...
Click to collapse
I was thinking it was the same build from this topic
http://forum.xda-developers.com/z3/general/sonys-android-concept-marshmallow-t3229030

i think that is not, Sony's Android™ Concept is official test build but this is unofficial build
and there is no Concept build for Z2 as i know

Is there a way to flash imgs with multiROM? I mean install the ROM on the internal storage without screwing up my other two installations.

Well, I tried this build, but gapps doesn't work... btw root is working (Booted a custom kernel with TWRP, install SuperSU 2.52, then back to original Kernel)...
Can't test permissions per app
System UI Tuner is working.
another new function, when you login with your google account (at least this was possible with gapps), a new menu appear on your settings, called "Google" or something like that, it shows and let you configure in a simple way lots of settings from your google acccount, like, youtube historic, location, voice commands, etc

Could someone please mirror the download... the links are not working for me

paxy97 said:
Is there a way to flash imgs with multiROM? I mean install the ROM on the internal storage without screwing up my other two installations.
Click to expand...
Click to collapse
i'm sorry for late, i make flashable zip also (using 'make otapakage' instead of just 'make')
https://www.dropbox.com/s/lbdm3vxiikqzp3n/aosp_d6503-ota-eng.choirakwon.zip?dl=0
maybe .zip version, it can be used in MultiRom.
after flashing 23.4.0.A.232 and AndroPlus ROM and testing this flashable .zip, i comfirm about that

nicholasknicks said:
Could someone please mirror the download... the links are not working for me
Click to expand...
Click to collapse
IMGs :
https://drive.google.com/folderview?id=0ByjmFQapr1xqOWY0ZmM2aHUxaU0&usp=sharing
flashable .zip :
https://drive.google.com/file/d/0ByjmFQapr1xqWk5wLVZQYkF5eDg/view?usp=sharing

nakwonelec said:
IMGs :
https://drive.google.com/folderview?id=0ByjmFQapr1xqOWY0ZmM2aHUxaU0&usp=sharing
flashable .zip :
https://drive.google.com/file/d/0ByjmFQapr1xqWk5wLVZQYkF5eDg/view?usp=sharing
Click to expand...
Click to collapse
Flashable zip not working
"Error executing updater binary in zip"

nicholasknicks said:
Flashable zip not working
"Error executing updater binary in zip"
Click to expand...
Click to collapse
Yes, i confirmed. When I tested in my phone. It make same result.
It maybe related with sdcard problem. So i will find solution. Thanks

nakwonelec said:
Yes, i confirmed. When I tested in my phone. It make same result.
It maybe related with sdcard problem. So i will find solution. Thanks
Click to expand...
Click to collapse
nicholasknicks said:
Flashable zip not working
"Error executing updater binary in zip"
Click to expand...
Click to collapse
But is not a flashable zip, Its just compacted to be easier to download

stayawake said:
But is not a flashable zip, Its just compacted to be easier to download
Click to expand...
Click to collapse
There are both just compacted zip and flashable zip also
"Error executing updater binary in zip" in this case, using just compacted zip
And when i test flashable zip, it make md5 error

nakwonelec said:
There are both just compacted zip and flashable zip also
"Error executing updater binary in zip" in this case, using just compacted zip
And when i test flashable zip, it make md5 error
Click to expand...
Click to collapse
oh you're right, I didnt saw the Updates on the OP

Rom for ALE-L04 US Version?

Is there any roms for US version p8 lite with snapdragon chip? I see few custom roms but doesnt say which version of the phone is for.

https://download.mokeedev.com/?device=chm_cl00
btw any honor 4c (SD version) roms should work

Audriuskins said:
https://download.mokeedev.com/?device=chm_cl00
btw any honor 4c (SD version) roms should work
Click to expand...
Click to collapse
thanks for your help. but got a error when i flash the rom. device is not correct

claudiuslu2011 said:
thanks for your help. but got a error when i flash the rom. device is not correct
Click to expand...
Click to collapse
Are you sure that you have Snapdragon version?

claudiuslu2011 said:
thanks for your help. but got a error when i flash the rom. device is not correct
Click to expand...
Click to collapse
It give you the error becuase your device is not signed in update-script. You need to add it by yourself

Audriuskins said:
Are you sure that you have Snapdragon version?
Click to expand...
Click to collapse
yes snapdragon 615
XTutorials said:
It give you the error becuase your device is not signed in update-script. You need to add it by yourself
Click to expand...
Click to collapse
I went to update-script and add my device id to it, i got another error saying "error executing updater binary in zip"

Also tried this like claudiuslu2011 and got the same error. Before error message, twrp gives the following output
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at /system; no such file or directory
unmount of /system failed; no such volume
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Is this implying the system partition has a different name than /system?

My concept for guide of port treble

What do you think about my concept for porting guide treble to non treble devices ???? That was only sample , and I don't do test's on other devices than my . http://80.211.218.7/index.php/rom-porting-guide-for-no-treble-devices/?fbclid=IwAR0qi_JDP0i9tcvBGAcp7lRtNu9QwKWQEGNXm5TG5W9NfeFx1pcIcmxOmZ8 Who want to test ???? I'm waiting for your opinion

I am interested if anyone knows how to create Treble Support for Non-Treble Devices.

zombie_ryushu said:
I am interested if anyone knows how to create Treble Support for Non-Treble Devices.
Click to expand...
Click to collapse
I know . I say how in other than my thread . This method is universal for other devices too .
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886/page91#post79523146

MAREK10747 said:
I know . I say how in other than my thread . This method is universal for other devices too .
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886/page91#post79523146
Click to expand...
Click to collapse
Do you think you can try and see if its possible for the Blu Vivo 5?

zombie_ryushu said:
Do you think you can try and see if its possible for the Blu Vivo 5?
Click to expand...
Click to collapse
I don't know

what are you saying ..porting treble to non-treble already exist ...but you need to repartition the phone ..you need to make a repartition script ..you also need to create a vendor.img

KevMetal said:
what are you saying ..porting treble to non-treble already exist ...but you need to repartition the phone ..you need to make a repartition script ..you also need to create a vendor.img
Click to expand...
Click to collapse
who would I go too that has experience doing that?

I'd be interested, but unfortunately your webserver is no more available
Can you upload your stub guide somewhere?

No I cant reupload because I delete all data from my pc . Re partition ZIP is avalaible to download from XDA and my threads . This ZIP make vendor partition . Image of vendor you must make manually with permissions .

MAREK10747 said:
No I cant reupload because I delete all data from my pc . Re partition ZIP is avalaible to download from XDA and my threads . This ZIP make vendor partition . Image of vendor you must make manually with permissions .
Click to expand...
Click to collapse
Do you have any tutorial to point me on how to move the contents of /system/vendor to the vendor partition and any other necessary modifications (such in boot.img ramdisk/dtb) for GSIs to boot successfully?

KaMyKaSii said:
Do you have any tutorial to point me on how to move the contents of /system/vendor to the vendor partition and any other necessary modifications (such in boot.img ramdisk/dtb) for GSIs to boot successfully?
Click to expand...
Click to collapse
Tutorial don't exist. You need to use zip for create vendor , next step is mount new vendor , next step is mount system and copy files from /system/vendor to /vendor partition . If you device found bugs look for lib's in system . After prepare vendor partition , you need flash GSI and prepare kernel supporting and mounting /vendor as partition . Tables of partitions in kernel too .

link deead

MAREK10747 said:
Tutorial don't exist. You need to use zip for create vendor , next step is mount new vendor , next step is mount system and copy files from /system/vendor to /vendor partition . If you device found bugs look for lib's in system . After prepare vendor partition , you need flash GSI and prepare kernel supporting and mounting /vendor as partition . Tables of partitions in kernel too .
Click to expand...
Click to collapse
Gonna try this on a Huawei P8 Lite. Wish me luck as the USB port has its data pin ripped clean off

I know . I say how in other 8rental.com than my thread

Magisk won't work on treble

Hey!
Whenever I install any Treble ROM on my Axon 7 Magisk won't be able to mount the system mirror. I already followed many instructions and ideas, none worked.
Model: A2017G
Treble: speedy
Kernel: baddar
Magiksk log says:
Code:
mount /sbin/.magisk/block/system->/sbin/.magisk/mirror/system failed with 16: Device or resource busy
Thx for any help!
Edit: Every file operation inside /system results in I/O error

tuxifan said:
Hey!
Whenever I install any Treble ROM on my Axon 7 Magisk won't be able to mount the system mirror. I already followed many instructions and ideas, none worked.
Model: A2017G
Treble: speedy
Kernel: baddar
Magiksk log says:
Thx for any help!
Edit: Every file operation inside /system results in I/O error
Click to expand...
Click to collapse
to conclude this it was a simple bootstack problem

Choose an username... said:
to conclude this it was a simple bootstack problem
Click to expand...
Click to collapse
exactly