Develop Bugs

How to use baksmali/smali?

Noob alert: Would anyone be kind enough to write a quick tutorial on how to use these jar files? I want to learn how to edit xml. I have searched these forums and google, but havent been able to get anywhere.

Code:
java -jar baksmali-0.93.jar -o <output directory> <.dex file, typically classes.dex>
For example: java -jar baksmali-0.93.jar -o out/rogers/dexout/ rogers-classes.dex
java -Xmx512M -jar smali-0.92.jar <output directory from above step> -o <name for new .dex output file>
For example: java -Xmx512M -jar smali-0.92.jar out/rogers/dexout/ new-rogers.dex
First command disassembles the .dex file, second command reassembles it (hopefully after you went in and made some cool changes to some of the .smali files)
Re-read your post, these are not for editing XML files. That is a whole other ball of wax. Most devs are not as interested in making post-build modifications now that the source for everything is available. You can set up a build environment and edit the XML files in plain text before you compile everything. Which is a lot easier than hex editing binary XML files...

Ohsaka said:
Code:
java -jar baksmali-0.93.jar -o <output directory> <.dex file, typically classes.dex>
For example: java -jar baksmali-0.93.jar -o out/rogers/dexout/ rogers-classes.dex
java -Xmx512M -jar smali-0.92.jar <output directory from above step> -o <name for new .dex output file>
For example: java -Xmx512M -jar smali-0.92.jar out/rogers/dexout/ new-rogers.dex
First command disassembles the .dex file, second command reassembles it (hopefully after you went in and made some cool changes to some of the .smali files)
Re-read your post, these are not for editing XML files. That is a whole other ball of wax. Most devs are not as interested in making post-build modifications now that the source for everything is available. You can set up a build environment and edit the XML files in plain text before you compile everything. Which is a lot easier than hex editing binary XML files...
Click to expand...
Click to collapse
I dont think you have to hex-edit them. Theres a tool called AXMLPrinter2.jar that makes xml files into readable ones. I'm sure you can just make your edits and copy and paste that text into a new blank xml file. Credits to jashu for the AXMLPrinter.jar

alritewhadeva said:
I dont think you have to hex-edit them. Theres a tool called AXMLPrinter2.jar that makes xml files into readable ones. I'm sure you can just make your edits and copy and paste that text into a new blank xml file. Credits to jashu for the AXMLPrinter.jar
Click to expand...
Click to collapse
How do you propose to recompile the xml sheet?
I don't think it's a jar btw, pretty sure he made a tar/gz, and a perl script.

mianosm said:
How do you propose to recompile the xml sheet?
I don't think it's a jar btw, pretty sure he made a tar/gz, and a perl script.
Click to expand...
Click to collapse
nah pretty sure its a jar. I'll find the link for you.
right here http://forum.xda-developers.com/showthread.php?t=514412
just did some quick research...im a noob in this field but can anyone make sense of this? http://www.stylusstudio.com/binary_xml.html#

It's going to be quicker and easier to change the values in a hex editor, and as said prior - you aren't going to be able to just put a human readable xml file into an apk and have the phone use it - it's expecting binary, so it would be a pretty neat feat if it took human readable and parsed it and out put it.

mianosm said:
It's going to be quicker and easier to change the values in a hex editor, and as said prior - you aren't going to be able to just put a human readable xml file into an apk and have the phone use it - it's expecting binary, so it would be a pretty neat feat if it took human readable and parsed it and out put it.
Click to expand...
Click to collapse
Yeah I know that, but you should be able to convert to binary and then convert it back to xml format. Problem is on every converter I've used, in the past 5 minutes (just started researching) keeps saying something about not a schema

alritewhadeva said:
Yeah I know that, but you should be able to convert to binary and then convert it back to xml format. Problem is on every converter I've used, in the past 5 minutes (just started researching) keeps saying something about manifest not found.
Click to expand...
Click to collapse
The xml in the templates/updates is currently compiled.
After you use the xml parser it's human readable/editable, but then you would need to recompile it. If you're going to do that, you'd might as well just do it from the source, and even still the color changes are hard coded and need to be changed to your liking.
The decompiled editing, and hex editing is really going to be the easiest/quickest method for color adjustments for now.

I'm surprised Stericson or JF haven't put out an XML compiler yet...

Ohsaka said:
You can set up a build environment and edit the XML files in plain text before you compile everything. Which is a lot easier than hex editing binary XML files...
Click to expand...
Click to collapse
Is it required to set up a build environment? I researched that and only found instructions for linux/mac.
This is my understanding of baksmali/smali. I thought I could take a file(apparently a DEX file) from the Android SDK, disassemble it, edit, then assemble. I scanned through the SDK and didn't find any DEX files?

Ohsaka said:
I'm surprised Stericson or JF haven't put out an XML compiler yet...
Click to expand...
Click to collapse
yea...True true. Just a QQ what's the AndroidManifest.xml file used for?

For your reading pleasure (from the launcher AndroidManifest.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
**
** Copyright 2008, The Android Open Source Project
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.launcher"
android:sharedUserId="android.uid.shared"
android:sharedUserLabel="@string/application_name">
<permission
android:name="com.android.launcher.permission.INSTALL_SHORTCUT"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_install_shortcut"
android:description="@string/permdesc_install_shortcut" />
<permission
android:name="com.android.launcher.permission.UNINSTALL_SHORTCUT"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_uninstall_shortcut"
android:description="@string/permdesc_uninstall_shortcut"/>
<permission
android:name="com.android.launcher.permission.READ_SETTINGS"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_read_settings"
android:description="@string/permdesc_read_settings"/>
<permission
android:name="com.android.launcher.permission.WRITE_SETTINGS"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_write_settings"
android:description="@string/permdesc_write_settings"/>
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.EXPAND_STATUS_BAR" />
<uses-permission android:name="android.permission.GET_TASKS" />
<uses-permission android:name="android.permission.READ_CONTACTS"/>
<uses-permission android:name="android.permission.SET_WALLPAPER" />
<uses-permission android:name="android.permission.SET_WALLPAPER_HINTS" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="com.android.launcher.permission.READ_SETTINGS" />
<uses-permission android:name="com.android.launcher.permission.WRITE_SETTINGS" />
<application
android:name="LauncherApplication"
android:process="android.process.acore"
android:label="@string/application_name"
android:icon="@drawable/ic_launcher_home">
<activity
android:name="Launcher"
android:launchMode="singleTask"
android:clearTaskOnLaunch="true"
android:stateNotNeeded="true"
android:theme="@style/Theme"
android:screenOrientation="nosensor"
android:windowSoftInputMode="stateUnspecified|adjustPan">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME"/>
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.MONKEY" />
</intent-filter>
</activity>
<activity
android:name="WallpaperChooser"
android:label="@string/pick_wallpaper"
android:icon="@drawable/ic_launcher_gallery">
<intent-filter>
<action android:name="android.intent.action.SET_WALLPAPER" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<!-- Enable system-default search mode for any activity in Home -->
<meta-data
android:name="android.app.default_searchable"
android:value="*" />
<!-- Intent received used to install shortcuts from other applications -->
<receiver
android:name=".InstallShortcutReceiver"
android:permission="com.android.launcher.permission.INSTALL_SHORTCUT">
<intent-filter>
<action android:name="com.android.launcher.action.INSTALL_SHORTCUT" />
</intent-filter>
</receiver>
<!-- Intent received used to uninstall shortcuts from other applications -->
<receiver
android:name=".UninstallShortcutReceiver"
android:permission="com.android.launcher.permission.UNINSTALL_SHORTCUT">
<intent-filter>
<action android:name="com.android.launcher.action.UNINSTALL_SHORTCUT" />
</intent-filter>
</receiver>
<!-- The settings provider contains Home's data, like the workspace favorites -->
<provider
android:name="LauncherProvider"
android:authorities="com.android.launcher.settings"
android:writePermission="com.android.launcher.permission.WRITE_SETTINGS"
android:readPermission="com.android.launcher.permission.READ_SETTINGS" />
</application>
</manifest>
Or the Music one:
Code:
packages/apps/Music/res/layout/statusbar.xml
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
** Copyright 2007, The Android Open Source Project
**
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="horizontal">
<ImageView android:id="@+id/icon"
android:padding="4dip"
android:gravity="center"
android:layout_width="wrap_content"
android:layout_height="wrap_content">
</ImageView>
<LinearLayout
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="vertical">
<TextView android:id="@+id/trackname"
android:textAppearance="?android:attr/textAppearanceMediumInverse"
android:focusable="true"
android:ellipsize="marquee"
android:singleLine="true"
android:layout_gravity="left"
android:layout_width="wrap_content"
android:layout_height="wrap_content" />
<TextView android:id="@+id/artistalbum"
android:textAppearance="?android:attr/textAppearanceSmallInverse"
android:layout_gravity="left"
android:maxLines="2"
android:scrollHorizontally="true"
android:ellipsize="end"
android:layout_width="wrap_content"
android:layout_height="wrap_content" />
</LinearLayout>
</LinearLayout>
And for the statusbar:
Code:
/frameworks/base/tests/StatusBar$ cat AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.statusbartest">
<uses-permission android:name="android.permission.DEVICE_POWER" />
<uses-permission android:name="android.permission.STATUS_BAR" />
<uses-permission android:name="android.permission.EXPAND_STATUS_BAR" />
<uses-permission android:name="android.permission.VIBRATE" />
<application>
<activity android:name="StatusBarTest" android:label="_StatusBar">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="NotificationTestList" android:label="_Notifications">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="ToastTest" android:label="_Toasts">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="PowerTest" android:label="_Power">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>

mianosm said:
For your reading pleasure (from the launcher AndroidManifest.xml):
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
**
** Copyright 2008, The Android Open Source Project
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
package="com.android.launcher"
android:sharedUserId="android.uid.shared"
android:sharedUserLabel="@string/application_name">
<permission
android:name="com.android.launcher.permission.INSTALL_SHORTCUT"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_install_shortcut"
android:description="@string/permdesc_install_shortcut" />
<permission
android:name="com.android.launcher.permission.UNINSTALL_SHORTCUT"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_uninstall_shortcut"
android:description="@string/permdesc_uninstall_shortcut"/>
<permission
android:name="com.android.launcher.permission.READ_SETTINGS"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_read_settings"
android:description="@string/permdesc_read_settings"/>
<permission
android:name="com.android.launcher.permission.WRITE_SETTINGS"
android:permissionGroup="android.permission-group.SYSTEM_TOOLS"
android:protectionLevel="normal"
android:label="@string/permlab_write_settings"
android:description="@string/permdesc_write_settings"/>
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.EXPAND_STATUS_BAR" />
<uses-permission android:name="android.permission.GET_TASKS" />
<uses-permission android:name="android.permission.READ_CONTACTS"/>
<uses-permission android:name="android.permission.SET_WALLPAPER" />
<uses-permission android:name="android.permission.SET_WALLPAPER_HINTS" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="com.android.launcher.permission.READ_SETTINGS" />
<uses-permission android:name="com.android.launcher.permission.WRITE_SETTINGS" />
<application
android:name="LauncherApplication"
android:process="android.process.acore"
android:label="@string/application_name"
android:icon="@drawable/ic_launcher_home">
<activity
android:name="Launcher"
android:launchMode="singleTask"
android:clearTaskOnLaunch="true"
android:stateNotNeeded="true"
android:theme="@style/Theme"
android:screenOrientation="nosensor"
android:windowSoftInputMode="stateUnspecified|adjustPan">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME"/>
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.MONKEY" />
</intent-filter>
</activity>
<activity
android:name="WallpaperChooser"
android:label="@string/pick_wallpaper"
android:icon="@drawable/ic_launcher_gallery">
<intent-filter>
<action android:name="android.intent.action.SET_WALLPAPER" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<!-- Enable system-default search mode for any activity in Home -->
<meta-data
android:name="android.app.default_searchable"
android:value="*" />
<!-- Intent received used to install shortcuts from other applications -->
<receiver
android:name=".InstallShortcutReceiver"
android:permission="com.android.launcher.permission.INSTALL_SHORTCUT">
<intent-filter>
<action android:name="com.android.launcher.action.INSTALL_SHORTCUT" />
</intent-filter>
</receiver>
<!-- Intent received used to uninstall shortcuts from other applications -->
<receiver
android:name=".UninstallShortcutReceiver"
android:permission="com.android.launcher.permission.UNINSTALL_SHORTCUT">
<intent-filter>
<action android:name="com.android.launcher.action.UNINSTALL_SHORTCUT" />
</intent-filter>
</receiver>
<!-- The settings provider contains Home's data, like the workspace favorites -->
<provider
android:name="LauncherProvider"
android:authorities="com.android.launcher.settings"
android:writePermission="com.android.launcher.permission.WRITE_SETTINGS"
android:readPermission="com.android.launcher.permission.READ_SETTINGS" />
</application>
</manifest>
Click to expand...
Click to collapse
Is that directly from the source? Android source that is. In eclipse when you write the .xml file doesn't it convert it to binary when you compile/create the app?

That's directly from the source yes. When it's compiled it takes the xml format and turns it into binary yes.

ultra spikey said:
Is it required to set up a build environment? I researched that and only found instructions for linux/mac.
This is my understanding of baksmali/smali. I thought I could take a file(apparently a DEX file) from the Android SDK, disassemble it, edit, then assemble. I scanned through the SDK and didn't find any DEX files?
Click to expand...
Click to collapse
I believe, for right now, you need a build environment to product compiled XMLs only. Until someone releases a tool to compile them...
Your understanding is correct. The SDK does not include and .dex files. The SDK is to help you develop your own app, not edit the underlying android platform files. Even if you grab the source from using git, you wont find .dex files. They are the output of the build process...i.e. the compiled java files...
Yes, only on linux/mac. Just get VMWare or some other virtual machine program and make a linux VM to develop on. If I ever get around to finishing mine, I will give it out so that people can just get VMPlayer to run it...

VirtualBox is pretty outstanding as well as vmware.
The real fix should not be decompiling/compiling though, it really should be edits to the actual source that is pushed upstream to gerrit, so it can be reviewed and updated accordingly.
It's really kind of a sloppy backward way to do it the way how it's getting done right now - don't get me wrong it works, but it's just not best practice.

Taking anything outside of the compiled xml and dex files opens up the system for slowdowns though doesn't it?
Like if we all somehow submitted a patch to the core that made it know to look at /sdcard/theme/ for a bunch of xml files and pngs... Then joe blow comes along with his $2.99 2gig card that runs slow as s* and his whole phone because unusable...

Is it even possible to use eclipse on ubuntu? Haven't found an answer. Running ubuntu on a VM right now.

Eclipse is java... so yes. There may not be a nice windows installer for it, but it should run on any platform with a JRE...

Ohsaka said:
Eclipse is java... so yes. There may not be a nice windows installer for it, but it should run on any platform with a JRE...
Click to expand...
Click to collapse
all right then. Time to research lol. Thanks

[Q] editing fallback_font.xml file

I checked the suggested similar threads, but didn't see anything that seemed to pertain to my question......
Anywa, it seems that I might be in way over my head, but still, it seems that this should be simple to do? In system/etc there is an xml file, fallback_fonts.xml which determines the order in which fonts will be searched to handle glyphs that are not system level fonts. I wish to modify that file.
The problem I wish to address is the proper display of Japanese fonts. In this xml file, DroidSansFallback.ttf comes before MTLmr3m.ttf. As a result, simplified Chinese fonts are always selected rather than the Japanese font (MTLmr3m.ttf). While many of the characters are the same as the Japanese versions, a significant number are not. I found a couple of xml editors on the web (XML Notepad 2007 and FirstObject XML editor) and used each of them to move MTLmr3m.ttf before DroidSansFallback.ttf. However, after saving, renaming and rebooting, the entire file appeared to have been corrupted, no matter which editor I used. For example, not only do I not have any Asian fonts, but One More Clock is unable to display time and temperature. So it appears that this is not as simple as I assumed.
In the Android 4.1 distribution for the GNex, there was also a fallback_fonts-ja.xml which placed MTLmr3m.ttf before DroidSansFallback.ttf. Therefore, it was a simple matter to rename and substitute that file and all was good. However, the 4.2 distribution does not include a fallback_fonts-ja.xml file. But I thought, I will make my own fallback_fonts-ja.xml! How hard can it be? Well...
So, I am hoping that this is in fact a simple process for more experienced and capable folks and that someone will be kind enough to show me how to do this.
Thanks much!
<?xml version="1.0" encoding="utf-8"?>
<!--
Fallback Fonts
This file specifies the fonts, and the priority order, that will be searched for any
glyphs not handled by the default fonts specified in /system/etc/system_fonts.xml.
Each entry consists of a family tag and a list of files (file names) which support that
family. The fonts for each family are listed in the order of the styles that they
handle (the order is: regular, bold, italic, and bold-italic). The order in which the
families are listed in this file represents the order in which these fallback fonts
will be searched for glyphs that are not supported by the default system fonts (which are
found in /system/etc/system_fonts.xml).
Note that there is not nameset for fallback fonts, unlike the fonts specified in
system_fonts.xml. The ability to support specific names in fallback fonts may be supported
in the future. For now, the lack of files entries here is an indicator to the system that
these are fallback fonts, instead of default named system fonts.
There is another optional file in /vendor/etc/fallback_fonts.xml. That file can be used to
provide references to other font families that should be used in addition to the default
fallback fonts. That file can also specify the order in which the fallback fonts should be
searched, to ensure that a vendor-provided font will be used before another fallback font
which happens to handle the same glyph.
Han languages (Chinese, Japanese, and Korean) share a common range of unicode characters;
their ordering in the fallback or vendor files gives priority to the first in the list.
Language-specific ordering can be configured by adding a BCP 47-style "lang" attribute to
a "file" element; fonts matching the language of text being drawn will be prioritised over
all others.
-->
<familyset>
<family>
<fileset>
<file variant="elegant">DroidNaskh-Regular.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file variant="compact">DroidNaskh-Regular-SystemUI.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansEthiopic-Regular.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansHebrew-Regular.ttf</file>
<file>DroidSansHebrew-Bold.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansThai.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansArmenian.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansGeorgian.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansDevanagari-Regular.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansTamil-Regular.ttf</file>
<file>DroidSansTamil-Bold.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>AnjaliNewLipi-light.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>Lohit-Bengali.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>Lohit-Kannada.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>NanumGothic.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>AndroidEmoji.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file>DroidSansFallback.ttf</file>
</fileset>
</family>
<family>
<fileset>
<file lang="ja">MTLmr3m.ttf</file>
</fileset>
</family>
<!--
Fonts below this point have problematic glyphs and should not be moved
higher in the fallback list until those glyphs have been fixed.
-->
<family>
<fileset>
<file>Lohit-Telugu.ttf</file> <!-- masks U+FFBC-10007 -->
</fileset>
</family>
</familyset>

Decompress Manifests files found in the WinSxS folder

Hello,
I am wondering how to decompress the *.manifest files which can be found in the Windows\WinSxS folder.
Since Windows 8, those file are null-delta compressed. (cf. http://i1.blogs.technet.com/b/askco...ng-reduction-of-windows-footprint-part-2.aspx)
The Delta Compression APIs are explained on this page: https://msdn.microsoft.com/en-us/library/bb417345.aspx
Basically, the compression is relative to a source file: the compressed file is kind of a compressed diff. You need to have the original file and the compressed file (the delta).
But, you can also use it as a simple compressor without providing a source file (NULL).
I successfully made a small test program in C++ to compress/decompress a file using MSDelta API (CreateDelta, GetDelataInfo & ApplyDelta). The compressed file (the delta) starts with "PA30" bytes.
Unfortunately, the manifest files starts with "DCM\x01PA30" and if I try to use the GetDeltaInfo function on a manifest file, it fails. If I remove the "DCM\x01" bytes, the GetDeltaInfo function works but the ApplyDelta function fails with error 13 (Invalid data).
So, I found the DLL responsible for the manifest compression is "wcp.dll". Inside this DLL, 2 functions are interesting:
[email protected]@[email protected]@[email protected]@[email protected]@[email protected]@@Z
-> this one contains the "DCM\x01" string
[email protected]@[email protected]@[email protected]@[email protected][email protected]@@[email protected]@Z
Thanks to IDA Hex-rays, I can confirm these functions uses the MSDelta APIs for sure. But I'm a bit lost when I try to find out what differs from a basic compression.
Is someone talented enough in RE to help me find out?
Thanks

try lzmsexpand from Alex Ionescu:
https://twitter.com/aionescu/status/597520706876801024

MagicAndre1981 said:
try lzmsexpand from Alex Ionescu:
https://twitter.com/aionescu/status/597520706876801024
Click to expand...
Click to collapse
Thanks. It was not exactly the right tool (even if I may need it at some point) but thanks to you I found the right tool:
http://forums.mydigitallife.info/th...ty-SxS-Package-Extractor-(Updated-2013-09-30)
http://forums.mydigitallife.info/threads/48613-Aunty-Mel-s-Cheap-And-Nasty-SxS-File-Expander

Just dropping in to say i wrote a working tool for this task
You can find it here: https://github.com/smx-smx/wcpex
Code:
$ ./wcpex.exe amd64_avc.inf_31bf3856ad364e35_10.0.15063.0_none_bd6d26a0caecd0e5.manifest
Size: 349
Type is 4
InitializeDeltaCompressor: 0x00000000
LoadFirstResourceLanguageAgnostic: 0x00000000
==> Dictionary
>6A230000 00000000 6A230000 00000000< j#......j#...... zX
>A090CC9A F87F0000< ........ zX
DeltaDecompressBuffer: 0x00000000
==> Out Blob
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
<assemblyIdentity name="avc.inf" version="10.0.15063.0" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" type="driverUpdate" />
<dependency discoverable="no" resourceType="Resources">
<dependentAssembly dependencyType="prerequisite">
<assemblyIdentity name="avc.inf.Resources" version="10.0.15063.0" processorArchitecture="amd64" language="*" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" />
</dependentAssembly>
</dependency>
<file name="avc.inf" sourceName="avc.inf" importPath="$(build.nttree)\driver_infs\">
<infFile xmlns="urn:schemas-microsoft-com:asm.v3" />
<asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha256" />
<dsig:DigestValue>yWTFi0fUQfXTtMUaxUpUiaO+HxxSBrmdNsqbzrssmcg=</dsig:DigestValue>
</asmv2:hash>
</file>
<file name="avc.sys" sourceName="avc.sys" importPath="$(build.nttree)\">
<signatureInfo>
<signatureDescriptor DRMLevel="1300" />
</signatureInfo>
<asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha256" />
<dsig:DigestValue>qqYc6rf3aSzmaAkhgEu+5iZZq6TliVhqK5SRGx2ahqg=</dsig:DigestValue>
</asmv2:hash>
</file>
<file name="avcstrm.sys" sourceName="avcstrm.sys" importPath="$(build.nttree)\">
<asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha256" />
<dsig:DigestValue>k8NVRLU9Ch+8vDFl2lQZsnfUWCyjWPxFvq5YPCRB/hY=</dsig:DigestValue>
</asmv2:hash>
</file>
<deployment xmlns="urn:schemas-microsoft-com:asm.v3" />
</assembly>

Trying to build aosp marsmallow from sony sources, step by step and bugs, help needed

FIRST STEP: Prepare your environment I do this in a ubuntu 16.04 64 bits
1.- Install java:
Code:
sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get update
sudo apt-get install openjdk-7-jdk
2.- Install the necessary tools to make an Android build
Code:
sudo apt-get install bison g++-multilib git gperf libxml2-utils make zlib1g-dev:i386 zip
3.- Get repo and configure it
Code:
mkdir ~/bin
curl commondatastorage . googleapis .com/git-repo-downloads/repo> ~/bin/repo
chmod a+x ~/bin/repo
3.a- Open the bashrc file included in the repo tool:
Code:
sudo nano ~/.bashrc
3.b- To set the right path for your local bin folder, paste the following code to a new line at the very bottom of the bashrc file, and then save the file using Ctrl+X:
Code:
export PATH=~/bin:$PATH
4.- Reload bash variables to include the new path:
Code:
source ~/.bashrc
SECOND STEP: Initialise the AOSP tree
1. In a terminal window, enter the following commands:
Code:
mkdir ~/android
cd ~/android
repo init -u android. googlesource.com/platform/manifest -b android-6.0.1_r46
2. Create and open a file where you will later add Sony’s repos containing the device configurations for Xperia devices, by entering the following commands:
Code:
mkdir .repo/local_manifests/
nano .repo/local_manifests/sony.xml
3. Add repos for our seagull by copying and pasting the following text into the file, and then save the file using Ctrl+X:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="sony" fetch="git github. com/sonyxperiadev/" />
<remove-project name="platform/hardware/qcom/camera" />
<project path="device/sony/sepolicy" name="device-sony-sepolicy" groups="device" remote="sony" revision="m-mr1" />
<project path="device/sony/amami" name="device-sony-amami" groups="device" remote="sony" revision="master" />
<project path="device/sony/aries" name="device-sony-aries" groups="device" remote="sony" revision="master" />
<project path="device/sony/castor" name="device-sony-castor" groups="device" remote="sony" revision="master" />
<project path="device/sony/castor_windy" name="device-sony-castor_windy" groups="device" remote="sony" revision="master" />
<project path="device/sony/common" name="device-sony-common" groups="device" remote="sony" revision="m-mr1" />
<project path="device/sony/common-headers" name="device-sony-common-headers" groups="device" remote="sony" revision="aosp/LA.BF64.1.2.2_rb4.7" />
<project path="device/sony/common-kernel" name="vendor-sony-kernel" groups="device" remote="sony" revision="aosp/LA.BF64.1.2.2_rb4.7" />
<project path="device/sony/eagle" name="device-sony-eagle" groups="device" remote="sony" revision="master" />
<project path="device/sony/flamingo" name="device-sony-flamingo" groups="device" remote="sony" revision="master" />
<project path="device/sony/honami" name="device-sony-honami" groups="device" remote="sony" revision="master" />
<project path="device/sony/kanuti" name="device-sony-kanuti" groups="device" remote="sony" revision="master" />
<project path="device/sony/ivy" name="device-sony-ivy" groups="device" remote="sony" revision="master" />
<project path="device/sony/karin" name="device-sony-karin" groups="device" remote="sony" revision="master" />
<project path="device/sony/karin_windy" name="device-sony-karin_windy" groups="device" remote="sony" revision="master" />
<project path="device/sony/kitakami" name="device-sony-kitakami" groups="device" remote="sony" revision="master" />
<project path="device/sony/leo" name="device-sony-leo" groups="device" remote="sony" revision="master" />
<project path="device/sony/rhine" name="device-sony-rhine" groups="device" remote="sony" revision="master" />
<project path="device/sony/satsuki" name="device-sony-satsuki" groups="device" remote="sony" revision="master" />
<project path="device/sony/scorpion" name="device-sony-scorpion" groups="device" remote="sony" revision="master" />
<project path="device/sony/scorpion_windy" name="device-sony-scorpion_windy" groups="device" remote="sony" revision="master" />
<project path="device/sony/seagull" name="device-sony-seagull" groups="device" remote="sony" revision="master" />
<project path="device/sony/shinano" name="device-sony-shinano" groups="device" remote="sony" revision="master" />
<project path="device/sony/sirius" name="device-sony-sirius" groups="device" remote="sony" revision="master" />
<project path="device/sony/sumire" name="device-sony-sumire" groups="device" remote="sony" revision="master" />
<project path="device/sony/suzuran" name="device-sony-suzuran" groups="device" remote="sony" revision="master" />
<project path="device/sony/tianchi" name="device-sony-tianchi" groups="device" remote="sony" revision="master" />
<project path="device/sony/togari" name="device-sony-togari" groups="device" remote="sony" revision="master" />
<project path="device/sony/tulip" name="device-sony-tulip" groups="device" remote="sony" revision="master" />
<project path="device/sony/yukon" name="device-sony-yukon" groups="device" remote="sony" revision="master" />
<project path="hardware/qcom/camera" name="camera" groups="device" remote="sony" revision="aosp/LA.BF64.1.2.2_rb4.7" />
<project path="kernel/sony/msm" name="kernel" groups="device" remote="sony" revision="aosp/LA.BF64.1.2.2_rb4.7" />
<project path="vendor/qcom/opensource/dataservices" name="vendor-qcom-opensource-dataservices" groups="device" remote="sony" revision="master" />
<project path="vendor/sony-oss/thermanager" name="thermanager" groups="device" remote="sony" revision="master" />
<project path="vendor/sony-oss/mkqcdtbootimg" name="mkqcdtbootimg" groups="device" remote="sony" revision="master" />
<project path="vendor/sony-oss/macaddrsetup" name="macaddrsetup" groups="device" remote="sony" revision="master" />
<project path="vendor/sony-oss/timekeep" name="timekeep" groups="device" remote="sony" revision="master" />
</manifest>
4. To download the code into the device repos created above, run the command
Code:
repo sync
THIRD STEP: Add necessary patches from the AOSP upstream branch
In order for certain functions to work on the hardware in Xperia devices, you need to add a set of patches from the AOSP master branch. This is done by executing the following commands:
In a terminal window, enter:
Code:
cd external/libnfc-nci
git fetch android .googlesource. com/platform/external/libnfc-nci refs/changes/61/170861/2 && git cherry-pick FETCH_HEAD
cd ../../hardware/qcom/gps
git fetch android .googlesource .com/platform/hardware/qcom/gps refs/changes/82/178682/1 && git cherry-pick FETCH_HEAD
cd ../keymaster
git cherry-pick 888834f9aba0609222c6e6bbd86bd6625af28746
git fetch android .googlesource. com/platform/hardware/qcom/keymaster refs/changes/70/212570/5 && git cherry-pick FETCH_HEAD
git fetch android .googlesource. com/platform/hardware/qcom/keymaster refs/changes/80/212580/2 && git cherry-pick FETCH_HEAD
git fetch android .googlesource. com/platform/hardware/qcom/keymaster refs/changes/61/213261/1 && git cherry-pick FETCH_HEAD
cd ../../broadcom/libbt/
git fetch android .googlesource. com/platform/hardware/broadcom/libbt refs/changes/17/114817/2 && git cherry-pick FETCH_HEAD
FOURTH STEP: Building our own upgrade kernel
1.- I prefer build the kernel on a different directory that the android sources so we go to create the directory tree and get the toolchain
Code:
mkdir /kenreldroid && cd /kerneldroid
git clone android. googlesource. com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/
1. Export the cross compiler&update bc (I need it)
Code:
export CROSS_COMPILE=/ kerneldroid/arm-eabi-4.8/bin/arm-eabi-
apt-get install bc
2. Download the kernel source from GitHub
Code:
git clone github .com/sonyxperiadev/kernel
cd kernel
git branch –r
git checkout
3. Configure the kernel: Configure the kernel is a required step before building it. Kernel drivers can be turned on or off, or be built as modules. This has to be configured in order for the kernel to function as desired. Configure the kernel by entering:
Code:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE aosp_yukon_seagull_defconfig
4. Build the kernel and needed modules: When building the kernel a compressed kernel image file is created and placed in the default target arch/arm/boot/zImage on your computer. To start the build, enter:
Code:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE -j 8(number of threads from your processor)
5. Now we have our vzimage we need to rename it and copy him to our android tree
Code:
mv /kerneldroid/kernel/arch/arm/boot/vzimage /kerneldroid/kernel/arch/arm/boot/kernel
mv /kerneldroid/kernel/arch/arm/boot/dts ~/android/device/sony/seagull
mv /kerneldroid/kernel/arch/arm/boot/kernel ~/android/device/sony/seagull/
FIFTH STEP: Building our ROM
1. Enter the following commands:
Code:
source build/envsetup.sh && lunch
2. When prompted, pick the number corresponding to your device in the list displayed and press enter.
3. To start the build, type:
Code:
make –j <insert the cpu thread number of your computer WITHOU <>>
This step will take a long time. It may take up to several hours, so go grab a coffee or play a game while you wait. When it’s done, AOSP images that can be flashed to a device will be ready.
Flash AOSP image to your device
Before you flash the images that you built in the previous step, you must make sure your device is unlocked through Sony’s unlock boot loader service. Then you can flash the AOSP images on your device by following these steps:
1. On your device: Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
2. On your computer: Flash the boot, system and userdata images by entering the following commands in a terminal window:
Code:
fastboot –S 256M flash boot out/target/product/<device>/boot.img
fastboot –S 256M flash system out/target/product/<device>/system.img
fastboot –S 256M flash userdata out/target/product/<device>/userdata.img
PROBLEMS FOUND
1.- while compiling the driver i have found just one problem, the file "bs_log.h" wasnt found so you can do this
Code:
cd ~/kerneldroid/kernel/include/linux
nano bs_log.h
and paste this
Code:
#ifndef __BS_LOG_H
#define __BS_LOG_H
#include <linux/kernel.h>
#define LOG_LEVEL_E 3
#define LOG_LEVEL_N 5
#define LOG_LEVEL_I 6
#define LOG_LEVEL_D 7
#ifndef LOG_LEVEL
#define LOG_LEVEL LOG_LEVEL_I
#endif
#ifndef MODULE_TAG
#define MODULE_TAG "<>"
#endif
#if (LOG_LEVEL >= LOG_LEVEL_E)
#define PERR(fmt, args...) \
printk(KERN_ERR "\n" "[E]" KERN_ERR MODULE_TAG "<%s><%d>" \
fmt "\n", __func__, __LINE__, ##args)
#else
#define PERR(fmt, args...)
#endif
#if (LOG_LEVEL >= LOG_LEVEL_N)
#define PNOTICE(fmt, args...) \
printk(KERN_ERR "\n" "[N]" KERN_NOTICE MODULE_TAG "<%s><%d>" \
fmt "\n", __func__, __LINE__, ##args)
#else
#define PNOTICE(fmt, args...)
#endif
#if (LOG_LEVEL >= LOG_LEVEL_I)
#define PINFO(fmt, args...) \
printk(KERN_ERR "\n" "[I]" KERN_INFO MODULE_TAG "<%s><%d>" \
fmt "\n", __func__, __LINE__, ##args)
#else
#define PINFO(fmt, args...)
#endif
#if (LOG_LEVEL >= LOG_LEVEL_D)
#define PDEBUG(fmt, args...) \
printk(KERN_ERR "\n" "[D]" KERN_DEBUG MODULE_TAG "<%s><%d>" \
fmt "\n", __func__, __LINE__, ##args)
#else
#define PDEBUG(fmt, args...)
#endif
#endif
2.- while compiling the entire rom i have a problem with "unsupported reloc 42" the fix is the next
Code:
nano ~/android/art/build/Android.common_build.mk
look for this
Code:
# Clang build support.
# Host.
ART_HOST_CLANG := false
ifneq ($(WITHOUT_HOST_CLANG),true)
# By default, host builds use clang for better warnings.
ART_HOST_CLANG := true
endif
and change for this
Code:
# Host.
ART_HOST_CLANG := false
ifeq ($(WITHOUT_HOST_CLANG),false)
# By default, host builds use clang for better warnings.
ART_HOST_CLANG := true
endif
BUGS FOUND
unknown baseband so the device dont connect to the network from operator, i'm looking info and help to fix this.

[Q] Repo/Manifest errors for HTC M9 Himaul?

I am trying to build LineageOS for the HTC M9 Himaul following these directions CyanogenMod Wiki: How to build himaul using "git://github.com/LineageOS/android.git -b cm-14.1" for the repo.
The repo syncs successfully and I don't get any errors when I run "source build/envsetup.sh", but when I run "breakfast himaul" I get this
Code:
~/android/system $ breakfast himaul
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/htc/himaul/lineage.mk]]: "vendor/qcom/binaries/msm8994/graphics/graphics-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/htc/himaul/lineage.mk]]: "vendor/qcom/binaries/msm8994/graphics/graphics-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/htc/himaul/lineage.mk]]: "vendor/qcom/binaries/msm8994/graphics/graphics-vendor.mk" does not exist. Stop.
Device himaul not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_htc_himaul
Default revision: cm-14.1
Checking branch info
Checking if device/htc/himaul is fetched from android_device_htc_himaul
LineageOS/android_device_htc_himaul already fetched to device/htc/himaul
Syncing repository to retrieve project.
Fetching project LineageOS/android_device_htc_himaul
Fetching projects: 100% (1/1), done.
Repository synced!
Looking for dependencies in device/htc/himaul
Looking for dependencies in device/htc/hima-common
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
Done
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/htc/himaul/lineage.mk]]: "vendor/qcom/binaries/msm8994/graphics/graphics-vendor.mk" does not exist. Stop.
build/core/product_config.mk:254: *** _nic.PRODUCTS.[[device/htc/himaul/lineage.mk]]: "vendor/qcom/binaries/msm8994/graphics/graphics-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'lineage_himaul'
** Do you have the right repo manifest?
I attached my manifest.xml and roomservice.xml

add this project on your roomservice.xml
Code:
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
Then repo sync again

Thanks, I tried your suggestion and every other one I could find but unfortunately couldn't ever get version 14 to work.
I was successful with version 13.
I appreciate the help.

i get the same , if somebody findes out please PM me ..

Hey!
You additionally have to add the device specific binaries, so please also add this to your roomservice.xml :
Code:
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-14.1" />
Then do a
Code:
repo sync
and try again. Maybe a make clean is necessary.
If you don't have a good internet connection AND an already running M9 you can also extract the proprietary blobs with
Code:
~/android/system/device/htc/himaul/extract-files.sh
That's also mentioned in your link CyanogenMod Wiki: How to build himaul. Sorry - I can't post links.
A third method is extracting the binary blobs from an already built zip image (maybe cm 13)...
Happy compiling
For me it worked - but I still haven't flashed it
---------- Post added at 07:07 PM ---------- Previous post was at 06:40 PM ----------
Yeeha!
It successfully booted
Wifi is working, but there are a lot of buggy things around... e.g. the camera
Actually I wanted to post a screenshot, but I can't find the upload button

115ek said:
Hey!
You additionally have to add the device specific binaries, so please also add this to your roomservice.xml :
Then do a and try again. Maybe a make clean is necessary.
If you don't have a good internet connection AND an already running M9 you can also extract the proprietary blobs with
That's also mentioned in your link CyanogenMod Wiki: How to build himaul. Sorry - I can't post links.
A third method is extracting the binary blobs from an already built zip image (maybe cm 13)...
Happy compiling
For me it worked - but I still haven't flashed it
---------- Post added at 07:07 PM ---------- Previous post was at 06:40 PM ----------
Yeeha!
It successfully booted
Wifi is working, but there are a lot of buggy things around... e.g. the camera
Actually I wanted to post a screenshot, but I can't find the upload button
Click to expand...
Click to collapse
I'll give this a shot this weekend.
Thank you

I added the two things above to my roomservice.xml so it looks like this now
Roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_himaul" path="device/htc/himaul" remote="github" />
<project name="LineageOS/android_device_htc_hima-common" path="device/htc/hima-common" remote="github" />
<project name="LineageOS/android_kernel_htc_msm8994" path="kernel/htc/msm8994" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-14.1" />
</manifest>
I did a 'repo sync' and a 'make clean' before attempting to build. I still get numerous errors so I must be doing something wrong still.
Here is the output from my brunch command
brunch himaul
including vendor/cm/vendorsetup.sh
Looking for dependencies in device/htc/himaul
Looking for dependencies in device/htc/hima-common
Looking for dependencies in device/qcom/common
Dependencies file not found, bailing out.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20170205-UNOFFICIAL-himaul
TARGET_PRODUCT=lineage_himaul
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53.a57
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-62-generic-x86_64-with-LinuxMint-18.1-serena
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NMF26V
OUT_DIR=/home/shelby/android/system/out
============================================
make: Entering directory '/home/shelby/android/system'
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20170205-UNOFFICIAL-himaul
TARGET_PRODUCT=lineage_himaul
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53.a57
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-62-generic-x86_64-with-LinuxMint-18.1-serena
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NMF26V
OUT_DIR=/home/shelby/android/system/out
============================================
***TEXT HERE REMOVED TO MEET CHARACTER LIMIT***
Running kati to generate build-lineage_himaul.ninja...
/home/shelby/android/system/out/build-lineage_himaul.ninja is missing, regenerating...
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=14.1-20170205-UNOFFICIAL-himaul
TARGET_PRODUCT=lineage_himaul
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53.a57
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.4.0-62-generic-x86_64-with-LinuxMint-18.1-serena
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NMF26V
OUT_DIR=/home/shelby/android/system/out
============================================
Checking build tools versions...
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/deqp/Android.mk: libdeqp: Unused source files: \
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
build/core/binary.mk:1253: external/pdfium/third_party/pdfiumbigint.mk: libpdfiumbigint: Unused source files: bigint/BigInteger.cc bigint/BigIntegerUtils.cc bigint/BigUnsigned.cc bigint/BigUnsignedInABase.cc
./external/speex/Android.mk:56: TODOArm64: enable neon in libspeex
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
find: ‘/home/shelby/android/system/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: No such file or directory
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
PRODUCT_COPY_FILES vendor/qcom/binaries/msm8994/graphics/proprietary/vendor/lib64/libmm-qdcm.so:system/vendor/lib64/libmm-qdcm.so ignored.
build/core/Makefile:53: Duplicate header copy: /home/shelby/android/system/out/target/product/himaul/obj/include/qcom/display/copybit.h
build/core/Makefile:53: Defined in: hardware/qcom/display-caf/msm8994/libcopybit/Android.mk hardware/qcom/display-caf/msm8994/libcopybit/Android.mk
build/core/Makefile:53: Duplicate header copy: /home/shelby/android/system/out/target/product/himaul/obj/include/qcom/display/copybit_priv.h
build/core/Makefile:53: Defined in: hardware/qcom/display-caf/msm8994/libcopybit/Android.mk hardware/qcom/display-caf/msm8994/libcopybit/Android.mk
build/core/Makefile:53: Duplicate header copy: /home/shelby/android/system/out/target/product/himaul/obj/include/qcom/display/c2d2.h
build/core/Makefile:53: Defined in: hardware/qcom/display-caf/msm8994/libcopybit/Android.mk hardware/qcom/display-caf/msm8994/libcopybit/Android.mk
No private recovery resources for TARGET_DEVICE himaul
build/core/java.mk:334: warning: overriding commands for target `/home/shelby/android/system/out/target/common/obj/APPS/Dialer_intermediates/src/src/org/codeaurora/presenceserv/IPresenceService.java'
build/core/java.mk:334: warning: ignoring old commands for target `/home/shelby/android/system/out/target/common/obj/APPS/Dialer_intermediates/src/src/org/codeaurora/presenceserv/IPresenceService.java'
build/core/java.mk:334: warning: overriding commands for target `/home/shelby/android/system/out/target/common/obj/APPS/Dialer_intermediates/src/src/org/codeaurora/presenceserv/IPresenceServiceCB.java'
build/core/java.mk:334: warning: ignoring old commands for target `/home/shelby/android/system/out/target/common/obj/APPS/Dialer_intermediates/src/src/org/codeaurora/presenceserv/IPresenceServiceCB.java'
build/core/base_rules.mk:316: warning: overriding commands for target `/home/shelby/android/system/out/target/product/himaul/root/res/images/charger/battery_fail.png'
build/core/base_rules.mk:316: warning: ignoring old commands for target `/home/shelby/android/system/out/target/product/himaul/root/res/images/charger/battery_fail.png'
build/core/Makefile:34: warning: overriding commands for target `/home/shelby/android/system/out/target/product/himaul/system/lib64/hw/consumerir.default.so'
build/core/base_rules.mk:316: warning: ignoring old commands for target `/home/shelby/android/system/out/target/product/himaul/system/lib64/hw/consumerir.default.so'
build/core/Makefile:34: warning: overriding commands for target `/home/shelby/android/system/out/target/product/himaul/system/lib/hw/consumerir.default.so'
build/core/base_rules.mk:316: warning: ignoring old commands for target `/home/shelby/android/system/out/target/product/himaul/system/lib/hw/consumerir.default.so'
Starting build with ninja
ninja: Entering directory `.'
ninja: error: 'vendor/htc/hima-common/proprietary/etc/firmware/BCM4354A2_001.003.015.0100.0102.hcd', needed by '/home/shelby/android/system/out/target/product/himaul/system/etc/firmware/BCM4354A2_001.003.015.0100.0102.hcd', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/shelby/android/system'
#### make failed to build some targets (23 seconds) ####

Very interesting...
Please find out what your directory /home/shelby/android/system/vendor/htc/hima-common/proprietary/etc/firmware/ contains. Or if it actually exists.
Do you find BCM4354A2_001.003.015.0100.0102.hcd or BCM4356A2_001.003.015.0100.0102.hcd there?
If not: please do a 'repo --force-sync' (if you don't have local changes in your sourcetree...)
BCM4354A2_001.003.015.0100.0102.hcd was replaced by a newer bluetooth firmware version BCM4356A2_001.003.015.0100.0102.hcd
But it's still copied under the old name into the output.
So, your problem is that a makefile might be outdated and looks for the old version (and can't find it) or your repo isn't synced correctly.

I looked in that directory and did not find either of those files.
I ran the repo --force-sync as suggested but no changes were made to the directory as far as I could see.
I did a search for BCM435* in android/system and it returned one file with a .hcd extension.
BCM4359C0_003.001.006.0065.0111.hcd in android/system/vendor/htc/pme/proprietary/etc/firmware
Dunno what that means...

I'm not opposed to deleting the directory and starting over if need be

I'm not opposed to deleting the directory and starting over if need be
Click to expand...
Click to collapse
Yes.
Try removing the htc directory under system/vendor and re-sync. It shouldn't take too much time. Your directory should look like h ttps://github.com/TheMuppets/proprietary_vendor_htc (had to insert a space, because I can't post links here )
If that doesn't work you can also download the repo as zip and unpack it in the right place.
Give it a try :good:

115ek said:
Yes.
Try removing the htc directory under system/vendor and re-sync. It shouldn't take too much time. Your directory should look like h ttps://github.com/TheMuppets/proprietary_vendor_htc (had to insert a space, because I can't post links here )
If that doesn't work you can also download the repo as zip and unpack it in the right place.
Give it a try :good:
Click to expand...
Click to collapse
I didn't get the chance to try any of this until this morning.
I deleted the whole directory and started over with the new lines in my roomservice.xml and I was able to build and flash the image successfully!
Thanks for the help! :good:

I know this tread is very old but as our device has been removed from the official builds, I wanted to try to build on my own to get the latest security patches.
I followed the instructions at htt ps://wiki.lineageos.org/devices/himaul/build and added both links to my roomservice.xml, did several re-syncs and extracted the proprietary blobs a second time but the build still fails and i still have the "Dependencies file not found, bailing out." message at breakfast / brunch.
Code:
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-14.1" />
os: ubuntu 17.10 x64 on virtual machine, assigned 1 core, 4.5GB of ram