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 : )

Nexus 7 MultiROM problem while starting Ubuntu Desktop

Hello Community,
When i try to start the Ubuntu Desktop OS for Nexus 7 i get the following error:
Code:
mount: mounting /dev/mmcblk0p9 on /root failed: No such device
Could not mount the partition /dev/mmcblk0p9.
This could also happen if the file system is not clean because of an operating system crash, an interrupted boot process, an improper shutdown, or unplugging of a removeable device without first unmounting or ejecting it. (filesystem = f2fs, error code = 255)
BusyBox v1.20.2 (Ubunti 1:1.20.0-8ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
The file system is according to TWRP ext4.
Any ideas what i could do to get this working?
Regards,
FunnyItsElmo

push

no one? Am i in the wrong forum?

FunnyItsElmo said:
Hello Community,
When i try to start the Ubuntu Desktop OS for Nexus 7 i get the following error:
Code:
mount: mounting /dev/mmcblk0p9 on /root failed: No such device
Could not mount the partition /dev/mmcblk0p9.
This could also happen if the file system is not clean because of an operating system crash, an interrupted boot process, an improper shutdown, or unplugging of a removeable device without first unmounting or ejecting it. (filesystem = f2fs, error code = 255)
BusyBox v1.20.2 (Ubunti 1:1.20.0-8ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
The file system is according to TWRP ext4.
Any ideas what i could do to get this working?
Regards,
FunnyItsElmo
Click to expand...
Click to collapse
I also got the same error. It's probably because the newer version of multirom doesn't support it. Try multirom v28. It worked for me.

FunnyItsElmo said:
Hello Community,
When i try to start the Ubuntu Desktop OS for Nexus 7 i get the following error:
Click to expand...
Click to collapse
ClawSpark said:
I also got the same error. It's probably because the newer version of multirom doesn't support it. Try multirom v28. It worked for me.
Click to expand...
Click to collapse
Hi, I also got the same.
Did you try with multirom v28 or if you have found some other solution I would be happy to try as well Thanks

I get the same error even after installing Multirom v28. Any ideas? I didn't have this problem before and I was using Multirom v32 but suddenly the installed Ubuntu showed this error after boot. I thought that deleting ubuntu and installing again will help but it didn't.

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?

Thread Closed

Thread Closed

Thread Closed

What is the difference between the version treble and the treble cust ?
Good work sir

Junier120 said:
What is the difference between the version treble and the treble cust ?
Good work sir
Click to expand...
Click to collapse
First of all Do Not Quote Whole -OP- and few users uses Redwolf recovery and few uses standard TWRP Recovery. sometimes you can't mount /vendor or /cust partition in recovery. You were ended up with "unable to mount vendor partition and so on". So i made two zips for same partition comes with two names in your twrp recovery shows "Vendor" or "Cust" when mounting.
In reality the folder name is vendor and the block device name is cust. You can fix this by editing the recovery.fstab file.

Can i skip the google account when i first boot?

SFSoFar said:
Can i skip the google account when i first boot?
Click to expand...
Click to collapse
Yes. You can.
It doesn't have Google Launcher app. So you won't get it on the first boot.

TheHitMan said:
Yes. You can.
It doesn't have Google Launcher app. So you won't get it on the first boot.
Click to expand...
Click to collapse
Emmmm,I mean the setupwizard.
Just forget its name.

SFSoFar said:
Emmmm,I mean the setupwizard.
Just forget its name.
Click to expand...
Click to collapse
It does not contain any setupwizard app.

TheHitMan said:
It does not contain any setupwizard app.
Click to expand...
Click to collapse
Thanks for the great work!
Next time I will try this gapp pack.

Good one. I used open gapps pico. This is even smaller than pico. Very minimal install. no setup wizard, also can enable battery optimization on play services.

When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
Me too

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
A log file would be a better option.
Get it from here "/cache/recovery/log or last_log" whatever the name is. Some permissions are failed to set. Vendor or cust partition error.

sokolataki said:
Me too
Click to expand...
Click to collapse
Get log file from here /cache/recovery/log or last_log.

TheHitMan said:
Get log file from here /cache/recovery/log or last_log.
Click to expand...
Click to collapse
After that I install opengapps but check it

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
me too..but is working dude..

sokolataki said:
After that I install opengapps but check it
Click to expand...
Click to collapse
Cust Partition Error. I am fixing this problem right now.
package_extract_file: can't open /cust/lib/libfrsdk.so for write: No such file or directory
package_extract_file: can't open /cust/lib64/libfrsdk.so for write: No such file or directory
- Set Permission
set_perm: chown of /cust/lib/libfrsdk.so to 0 0 failed: No such file or directory
set_perm: chmod of /cust/lib/libfrsdk.so to 644 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
Thread Updated.

BiTGApps Update :
- Fix Failed to install Vendor or Cust files.
- Check OP

TheHitMan said:
Thread Updated.
Click to expand...
Click to collapse
Okay thanks, i check it again. Btw, the none treble gapps is working fine on non treble rom. Working perfectly no more google setup wizard automatic homescreen show up after first boot.

Error Flashing Lineage OS on Oneplus 6T

Haven't done anything with root since KitKat but, I'm stumped on how to get around this.
Iperation_start: 'Flashing'
I:Unable to find a directory to store TWRP logs.Installing zip file '/sdcard/lineage-17.1-20200605-nightly-fajita-signed(1).zip'
Checking for Digest file...
I:AB zip
I:has_legacy_properties: Could not open /tmp/updater: No such file or directory!
I:Legacy property environment not used in updater.
Failed to parse build number in post-build-incremental=1140221e8d.
Package is for product OnePlus6T but expected OnePlus6
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20200605-nightly-fajita-signed(1).zip'
Updating partition details...
Iata backup size is 0MB, free: 110186MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
Everything I've done is installed TWRP on the phone and unlock the bootloader.
Anyone have anything?
Thanks in Advance

You are on the latest OOS currently? What TWRP exactly are you using?
Guide: Installing Lineage

OhioYJ said:
You are on the latest OOS currently? What TWRP exactly are you using?
Guide: Installing Lineage
Click to expand...
Click to collapse
Im using twrp-3.3.1-18-enchilada-Q-mauronofrio because it was the only one that would work for me and yes its the latest version of OOS. I've tried ADB Sideloading and it didn't work either.

jaguarxj said:
Im using twrp-3.3.1-18-enchilada-Q-mauronofrio
Click to expand...
Click to collapse
There's your problem. It thinks your phone is a OP6, not a 6T. You need to use a 6T recovery. You must be missing a step during the recovery installation.
FunkWizard has an excellent guide.
My Lineage install guide above also has a section on installing TWRP.