Develop Bugs

Help: How to extract the compressed files from XIP?

Hi all, I'm doing sth. to O2 XDA Stealth rom.
But I found that the "files" (not "modules") in XIP are all compressed, boot.hv looks just like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I compared the file with some other compressed files, and considered that the file was probabily compressed by LZX arithmetic.
So I tried to decompress the file with cecompr_nt.dll, and here is some codes:
Code:
HMODULE hDll= LoadLibrary(_T("G:\\Projects\\TestCompCE\\cecompr_nt.dll"));
if (hDll==NULL || hDll==INVALID_HANDLE_VALUE) {
printf("ERROR - Can not load the cecompr_nt library\n");
return -1;
}
FILE * hTest = NULL;
_tfopen_s(&hTest,_T("boot.hv"),_T("rb"));
int iSize =0;
fseek(hTest,0,SEEK_END);
iSize = ftell(hTest);
fseek(hTest,0,SEEK_SET);
BYTE * pBuf1 = (BYTE *)malloc(iSize);
BYTE * pBuf2 = (BYTE *)malloc(iSize);
fread_s(pBuf1,iSize,iSize,1,hTest);
fclose(hTest);
ZeroMemory(pBuf2,iSize);
FNCompressOpen CompressOpen= NULL;
FNCompressConvert CompressConvert= NULL;
FNCompressClose CompressClose= NULL;
CompressOpen= (FNCompressOpen)GetProcAddress(hDll, ("LZX_DecompressOpen"));
CompressConvert= (FNCompressConvert)GetProcAddress(hDll, ("LZX_DecompressDecode"));
CompressClose= (FNCompressClose)GetProcAddress(hDll, ("LZX_DecompressClose"));
if (CompressOpen==NULL || CompressConvert==NULL || CompressClose==NULL) {
printf("ERROR - Can not find the compression functions in the library\n");
FreeLibrary(hDll);
return -2;
}
DWORD stream = CompressOpen(0x10000, iSize, Compress_AllocFunc, Compress_FreeFunc, 0);
if (stream == NULL || stream==0xFFFFFFFF) {
printf("ERROR - CompressOpen");
return 14;
}
DWORD res=CompressConvert( stream, pBuf1,0x1AFF,pBuf2,iSize);//Compressed size of boot.hv is 0x1AFF
return 0;
But the CompressConvert function always returns 0 or -1 (i.e. failed)
So can anyone please tell me what's wrong with it? Is it not a LZX compressed file? Does I use wrong decompress function? Or there is no way to decompress it at all?
I found quite a number of ROMs have compressed files in XIP, such as O2 XDA Stealth, ASUS P525, ASUS P535 etc... So if we can decompress it, we should have much more stable and useful ROMs.
Thanks for your help and reading my post, and I appologize for my poor English.

[MOD] [Launcher-Theme] TW4.5 Glass-Blue

Hi Guys
Today i want present you my new Launcher-Theme.
Features:
Themed TW4.5 Launcher
Themed Dialer - Icon
Themed Contacts - Icon
Themed- Messeging - Icon
Installation:
Just download it and install it over CWM!
Download:
Only for JVP deodexed:
http://db.tt/bJflsMZ
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits:
Fr4gg0r
Swiftwork
I am working on it, its not finished yet.
Have fun!

Waiting ...
Thanks anyway

Please use the integrated theming mechanism instead of modding the .apk, launcher will be updated later this evening so you can theme more icons.

Attached is an test version with more theming capabilities.. would be nice if you would try it and report back.
The following possibilities are added to the existing ones:
case Id.Menu.cancel: name = Settings.currentThemeDir+"menu_cancel.png"; break;
case Id.Menu.discard: name = Settings.currentThemeDir+"menu_discard.png"; break;
case Id.Menu.edit: name = Settings.currentThemeDir+"menu_edit.png"; break;
case Id.Menu.preferences: name = Settings.currentThemeDir+"menu_preferences.png"; break;
case Id.Menu.save: name = Settings.currentThemeDir+"menu_save.png"; break;
case Id.Menu.search: name = Settings.currentThemeDir+"menu_search.png"; break;
case Id.Menu.share: name = Settings.currentThemeDir+"menu_share.png"; break;
case Id.Menu.wallpaper: name = Settings.currentThemeDir+"menu_wallpaper.png"; break;
case Id.Menu.settings: name = Settings.currentThemeDir+"menu_settings.png"; break;
case Id.Folder.icon: name = Settings.currentThemeDir+"folder_icon.png"; break;
case Id.Folder.icon_mainmenu: name = Settings.currentThemeDir+"folder_icon_mainmenu.png"; break;
case Id.Folder.open: name = Settings.currentThemeDir+"folder_open.png"; break;
case Id.Add.folder: name = Settings.currentThemeDir+"add_folder.png"; break;
case Id.Add.shortcut: name = Settings.currentThemeDir+"add_shortcut.png"; break;
case Id.Add.wallpaper: name = Settings.currentThemeDir+"add_wallpaper.png"; break;
case Id.Add.widget: name = Settings.currentThemeDir+"add_widget.png"; break;
and
"pageIndicator.png"
Click to expand...
Click to collapse
I think that should be quite self explanatory..

Nice!
Will test it...
Sent from my GT-I9000 using Tapatalk

any easy way to install tw themes

hi sir i flash this theme on galaxy xxjvp very good relaible and speedy but i have 1 prob. message background is black and message cant read plz help me

[Q] Kindle Fire shows up as a Disk Drive in devmgr, can't update driver

Windows 7 has my Kindle Fire listed as a Disk Drive, and when I try to update the driver so that ADB can read it Windows won't allow me to because android_winusb.inf is not a Disk driver.
Then I tried to uninstall the Kindle Fire driver and it simply immediately reinstalls itself the moment I restart the computer or plug the device back in, and it reinstalls as a disk drive...
Basically, I need help figuring out how reset the way Windows 7 recognizes my Kindle so that I can install the updated android_winusb.inf
How I got to this point
I installed the Kindle Fire on my Windows 7 computer through the device manager using the android_winusb.inf driver from the android-sdk/extras folder.
Couldn't connect to adb, but then I realized I needed to add the: [source]
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_0
to it in order for ADB to recognize it. So I modified android_winusb.inf and added the two lines. But, now I can't install the new modified driver because of what was stated above...​

Take it out of USB mode. Is it listed in Other Devices or Android Phone?

It is listed under Disk Drives (Device Manager) - which is also the reason why Windows 7 now won't allow me to update the drivers using android_winusb.inf - this is regardless of whether the sd card is mounted or not.
android_winusb.inf isn't a Disk driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Had this same problem, its because your computer was set up to run ADB before so it recognizes the kindle as Android and auto installs drivers that you have for it, unfortunately these drivers don't let you use ADB, go to android phone at the top and follow the steps to update the driver on the device under that instead.

Get this working
did the original poster get this working?? My machine will only recognize it as an MTP device now ... how do I stop it from applying those drivers??

Stuck on blue and white, can't fastboot/adb as "waiting for device"

Hello Guys! Please please can anyone help???
:crying:Sorry for this, I have looked and looked for a solution to this, many have asked and no-one seemed to solve it.
Kindle Fire HD 8.9", I think I accidentally deleted the OS in recovery, and now I'm stuck on the blue and white boot screen (so i have fff bootloader). If I switch it off and plug it into the windows 7 pc, it goes orange, then blue boot and sticks there.
I devices, it showed up as "Kindle", I followed instructions to install adb drivers - install java, install android sdk, lookup hardware id and paste it into android_winusb.inf, type 0x1949 into adb_usb.ini, and install drivers from google folder.
So I've got it showing up as Android Composite ADB device.
If I do "adb devices" in a command prompt it shows as 12345ABCDEFG or something as "unauthorised device".
Any fastboot commands just get "waiting for device"
At one point windows tried to install drivers for jem....., but then gave up and I can't get it to try again!
I've tried on 3 different pc's windows 8 64 bit, windows 7 32 and 64 bit.
Tried disabling all antivirus etc, tried disabling driver signature enforcement.
Does anyone at all have a solution to this?
I've done adb kill-server about a hundred times!
Many thanks for looking!
Sally

I've tried 6 different cables too, and all the pcs have been restarted several times

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My hardware ids
I've pasted them in as this...
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
Is this wrong maybe?

Fix Huawei G9 Plus accelerometer tilt

Fix accelerometer tilt​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video of issue https://yadi.sk/i/fPoYgs3O3N5ssc​In russian language, with history of finding way to manage http://4pda.ru/forum/index.php?showtopic=846874&view=findpost&p=66664464
The instruction for editing the X-axis, similarly can be corrected Y, Z axis too
1. Turn on logcat, it's more convenient through the computer
2. Run any program that uses an accelerometer, wait few secconds
3. Stop the logcat, and look for something like this in it:
10-16 21:30:03.124: I/qti_sensors_hal(1396): read from oem info: data_readback
10-16 21:30:03.124: I/qti_sensors_hal(1396): 0xb3, 0x71, 0x4f, 0xbf
10-16 21:30:03.124: I/qti_sensors_hal(1396): 0x66, 0x92, 0xed, 0x3d
10-16 21:30:03.124: I/qti_sensors_hal(1396): 0xbf, 0xa0, 0x7f, 0x3f
10-16 21:30:03.124: I/qti_sensors_hal(1396): 0x55, 0x0, 0x0, 0x0
10-16 21:30:03.124: I/qti_sensors_hal(1396): 0x0, 0x0, 0x0, 0x0
10-16 21:30:03.124: E/qti_sensors_hal(1396): read from oem info: data_valid_flag=0x55
10-16 21:30:03.124: E/qti_sensors_hal(1396): read from oem info: x_offset=-0.810329, y_offset=0.116002, z_offset=0.998547
10-16 21:30:03.124: E/qti_sensors_hal(1396): Final value: x_offset=-0.810329, y_offset=0.116002, z_offset=0.998547
Click to expand...
Click to collapse
4. Open file /dev/block/platform/soc/7824900.sdhci/by-name/oeminfo through "hex редактор" https://play.google.com/store/apps/details?id=tuba.tools.hexfull&hl=ru
5. Looking for hex values from logcat in oeminfo, in my case this is: b3 71 4f
6. Find right hex values - change, save, start the logcat look at the line E/qti_sensors_hal(1396): Final value: x_offset=-0.810329, if there is a change in the right way - more / less, depending on the nature of accelerometer tilt error of your phone, then continue to change the value until you achieve desired values of x_offset. You can use values from the neighboring Y, Z axes if you think they are right for you. For example, first I inserted values from the line 0x66, 0x92, 0xed, 0x3d and got x_offset about 0.1. But I needed x_offset = 0.0 for this I go further and found out that is b3 39 0 0 is x_offset = 0.0 for me.
7. Enjoy that now you have accelerometer that show correct level
​