[Q] Proprietary files missing in CyanogenMod BLOB - Android Q&A, Help & Troubleshooting

I'm building CM12 for XL. While trying to extract proprietary BLOB, I could see that latest NIGHTLY builds (e.g. cm-12-20150308-NIGHTLY-taoshan.zip) have a different structure from earlier EXPERIMENTAL builds (e.g. cm-11-20150112-EXPERIMENTAL-taoshan.zip)
-----------------------------------
Structure of NIGHTLY build:
-----------------------------------
install
META-INF
system
file_contexts
system.new.dat
system.patch.dat
system.transfer.list
boot.img
--------------------------------------------
Structure of EXPERIMENTAL build:
---------------------------------------------
META-INF
system
file_contexts
boot.img
I failed to extract ANY proprietary file from NIGHTLY build, because 'system' directory contains a single file: system\build.prop. On the contrary, the size of system.new.dat is very large: 427MB. I could extract all but three files from EXPERIMENTAL build as 'system' directory contains a collection of other required files, as expected. Ultimately, following three files are missing from the BLOB:
Code:
cp: cannot stat '/home/androbuild/original/system/bin/led_deamon': No such file or directory
cp: cannot stat '/home/androbuild/original/system/bin/led_deamon': No such file or directory
cp: cannot stat '/home/androbuild/original/system/etc/firmware/libpn544_fw.so': No such file or directory
cp: cannot stat '/home/androbuild/original/system/etc/firmware/libpn544_fw.so': No such file or directory
cp: cannot stat '/home/androbuild/original/system/vendor/lib/libtime_genoff.so': No such file or directory
cp: cannot stat '/home/androbuild/original/system/vendor/lib/libtime_genoff.so': No such file or directory
Because of 'libtime_genoff.so' being missing, my build is failing after running for ~7 hours. Any idea how to obtain three files as mentioned above?

Related

Help MultiROM

This MultiROM trying to install but I get the following error:
Log
Installing '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Installing MultiROM for condor
Extracting binaries...
about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p36 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/busybox] with 3 args
minzip: Extracted 40 file(s)
minzip: Extracted 6 file(s)
about to run program [/tmp/extract_multirom.sh] with 1 args
mkdir: can't create directory '/data/media/0/multirom': Permission denied
chown: /data/media/0/multirom: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
mkdir: can't create directory '/data/media/0/multirom/roms': No such file or directory
chown: /data/media/0/multirom/roms: No such file or directory
chmod: /data/media/0/multirom/roms: No such file or directory
touch: /data/media/0/multirom/.nomedia: No such file or directory
chown: /data/media/0/multirom/.nomedia: No such file or directory
rm: can't remove '/data/media/0/multirom/boot.img-ubuntu*': No such file or directory
rm: can't remove '/data/media/0/multirom/infos/*': No such file or directory
rm: can't remove '/data/media/0/multirom/res/*': No such file or directory
cp: can't create '/data/media/0/multirom/adbd': No such file or directory
cp: can't create '/data/media/0/multirom/busybox': No such file or directory
cp: can't create '/data/media/0/multirom/exfat-fuse': No such file or directory
cp: can't create '/data/media/0/multirom/fw_mounter': No such file or directory
cp: can't create directory '/data/media/0/multirom/icons': No such file or directory
cp: can't create '/data/media/0/multirom/kexec': No such file or directory
cp: can't create '/data/media/0/multirom/lz4': No such file or directory
cp: can't create '/data/media/0/multirom/mrom.fstab': No such file or directory
cp: can't create '/data/media/0/multirom/multirom': No such file or directory
cp: can't create '/data/media/0/multirom/ntfs-3g': No such file or directory
cp: can't create directory '/data/media/0/multirom/res': No such file or directory
cp: can't create '/data/media/0/multirom/trampoline': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-init': No such file or directory
cp: can't create directory '/data/media/0/multirom/ubuntu-touch-sysimage-init': No such file or directory
chmod: /data/media/0/multirom/multirom: No such file or directory
chmod: /data/media/0/multirom/busybox: No such file or directory
chmod: /data/media/0/multirom/trampoline: No such file or directory
chmod: /data/media/0/multirom/kexec: No such file or directory
chmod: /data/media/0/multirom/ntfs-3g: No such file or directory
chmod: /data/media/0/multirom/exfat-fuse: No such file or directory
chmod: /data/media/0/multirom/lz4: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-init/local: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/init: No such file or directory
chmod: /data/media/0/multirom/ubuntu-touch-sysimage-init/scripts/touch: No such file or directory
chmod: /data/media/0/multirom: No such file or directory
chown: /data/media/0/multirom: No such file or directory
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/extract_multirom.sh") == 0
assert failed: run_program("/tmp/extract_multirom.sh") == 0
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip'
Error flashing zip '/external_sd/multirom-20140903-v28-UNOFFICIAL-condor.zip
Now edit the build.prop but I get the same error also delete the first lines of updater.script and follows me out the same. I just worked with me but I want to install cm11 in stock
Sorry for my bad English
Which rom you are using as a primary rom
prajapati ravi said:
Which rom you are using as a primary rom
Click to expand...
Click to collapse
I'm using the stock
Then whats the problem add the cm11 and reboot
---------- Post added at 01:20 AM ---------- Previous post was at 01:16 AM ----------
magdeoz said:
I'm using the stock
Click to expand...
Click to collapse
If you use stock as primary rom then will not get any issue's if still get it then you doing something wrong with your hand

[Q] How do I fix a "Read-only file system" error during ROM flashing?

Hi Kitchen Experts ( What's Cookin?)
I do not seem to be able get rid of an error while flashing my phone with a ROM I built from a flashable ROM from SAMMOBILE, which I unpacked and replaced the zImage with one I compiled from opensource.samsong.com Basically the Kitchen ROM's zip file upacks fine, but then I see the following in my phone's logs: ( Below I put relevant sections:
Installing '/sdcard/DCIM/hltespr_signed_111514_202215.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/DCIM/hltespr_signed_111514_202215.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Creating filesystem with parameters:
...
minzip: Extracted file "/system/app/EasyOneHand.odex"
minzip: Error writing 32768 bytes from zip file from 0xbec0437c: Read-only file system
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/EasySettings.apk"
symlink: failed to symlink /system/bin/ionice to toolbox: No such file or directory
I updated permissions of the system folder in my WORKING_DIRECTORY of Android Kitchen, and I also used an App called ES file manager to change all the mount points on my phone to R/W; here are the procedures I followed for changing the mount points to R/W . I also validated that my mount points are correct. I am not sure what else to look at. Please let me know if I should post the permissions for my system folder in Kitchen or the output of any command on my phone. I'll gladly do it to address this issue.
I did a search online and found a number of people who had a similar problem, but the solution is not documented. I searched for "zip file ROM can not write to android", and reviewed all the resulting links. I do wipe the flash data and delivic cache before, try the ROM, and wipe again and try it. There is no change. I get the same result. Am I looking at the right things? I have built my ROM twice using the interactive and quick method each time.

[Q] Rooted KK and not-working AdAway

Hi
I have problem with using AdAway on my Z3TC.
I have successfully rooted my device. Now I'm on stock KK with root and locked back BL.
I installed AdAway but it doesn't want to work. There is problem with hosts file.
I found that I have to change permissions for /system to -rw-rw-rw and for file host too. But the problem is I can't. When I'm trying to change permissions I got info: Changing permissions was not successful. And it doesn't matter what Explorer I use.
Any ideas? Of course there is root permission for explorer... May the locked Bootloader be the problem (I doubt...)
To write in system you have to install from the recovery ricdefeat
https://github.com/dosomder/SonyRICDefeat/blob/master/RICDefeat.zip
I didn't installed TWRP after relocking BL.
I tried now and there is another problem (looks similar)
Code:
##########################################################
#
# Installing XZDR version 2.8.3 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': Read-only file system
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: No such file or directory
chmod: /system/.XZDualRecovery/busybox: No such file or directory
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event3!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event2!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
ADB asked for root permission during installation, I agreed.
And after all recovery is not installed...
I see where the problem is. You can not write in system because you need ricdefeat, but to install XZDualRecovery and flash from there ricdefeat need to write in "system"
I'm afraid you have to start over. Is necessary Flash Ricdefeat from the TWRP recovery before it is erased.
Read here (where it says "To install rooted Stock"):
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534 (relatively speaking there nicely explains the steps to take and what order , replace firmware sgp621 -> sgp611)
or my tutorial in Spanish I did not know if you know the language:
http://www.htcmania.com/showthread.php?t=966040 (Part B)
---
I will try to explain what I would do, I'm using google translator if not understood:
1- unlock bootloader
2- install advanced stock kernel
3- Now there are two options:
** 3A) Create pre-rooted firmware. Copy firmware pre-rooted and ricdefeat.zip on the tablet. Login to TWRP and flash firmware then ricdefeat, and restart at the end.
** 3B) Copy to tablet the ricdefeat file. Go to TWRP recovery, flash ricdefeat and restart. With flashtool , install on the tablet only the kernel, using the original firmware.
4- Start android and restore TA
5- Install XYDualRecovery to have a custom recovery

Cyanogenmod 12 mkvendor.sh problem

Hi guys i have a question, i want to get my device tree with the mkvendor.sh on the cyanogenmod source build/tools/device folder, y run this line using the previusly boot.img extracted:
./build/tools/device/mkvendor.sh dell yellowtail ~/boot.img
But the problem is that that some files are missing, i got this:
Code:
Arguments: dell yellowtail /home/quevon24/boot.img
Output will be in /home/quevon24/android/system/cm12/device/dell/yellowtail
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cat: /tmp/quevon24/bootimg/boot.img-base: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-pagesize: No such file or directory
cp: cannot stat
«/tmp/quevon24/bootimg/boot.img-zImage»: No such file or directory
Creating initial git repository.
~/android/system/cm12/device/dell/yellowtail ~/android/system/cm12
Reinitialized existing Git repository in /home/quevon24/android/system/cm12/device/dell/yellowtail/.git/
On master branch
nothing to commit, working directory clean
~/android/system/cm12
Done!
My boot.img is from a dell venue 8 3830, its from a android 4.4 stock image from here: http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2
Anyone can help and explain me please?
Thanks

Extract repo from tar.gz

I have planned to increase the space for my Ubuntu VM.
So I backed up the repo by archive it.
During compressing it does not show any errors. Then I moved the archive to local windows machine
But after I upgraded my VM, I tried to extract it, it shows more than one error.
Can't create folder, Files exist, No such file or directory etc...
Error log:
Code:
tar -h -zxf repo.tar.gz
tar: .repo/projects/prebuilts/qemu-kernel.git/objects: Cannot open: File exists
tar: .repo/projects/external/markdown.git/hooks/applypatch-msg.sample: Cannot open: Not a directory
tar: .repo/projects/prebuilts/python/darwin-x86/2.7.5.git/hooks: Cannot open: File exists
tar: .repo/projects/prebuilts/gradle-plugin.git/hooks/commit-msg.sample: Cannot open: Not a directory
tar: .repo/projects/external/libcap-ng.git/hooks: Cannot open: File exists
I tried it on command line as well as Archive manager
Do you have any idea?
I tried to compress the file using Archive manager. Its not compressed properly because of symbolic links.
That's why I can't able to uncompress again.
I tried again using terminal. It's working properly.

Categories

Resources