Thursday 7 June 2012

How to Fix the Compile Issue and Fatal errors with Sense 4.0 ROM file



ICS brought many changes and development in the Google OS. This may frustrate many users because they need to modify and changes the FILE such APK and APK Manager. Sense 4 is the main cause for the compilation errors associated with file modification in APK tools and APK Manager.


The most three important files framework-res.apk, com.htc.resources.apk and systemui.apk  all create these errors 

Here is the fix

 1. Framework-res.apk

a) Since ICS apktool creates multiple plurals errors, but you can easily fix these by using a custom version of apktool. Now updated incl. latest smali baksmali properties for ICS (thx fernando)

Custom ICS apktool version - Download

b) if you get tag errors like these

anims.xml:3: error: Found tag anim where item is expected
layouts.xml:3: error: Found tag layout where item is expected
raws.xml:3: error: Found tag raw where item is expected

Replace all tags in layouts.xml in values folder with:

<item type="layout" at the front and </item> at the end


Replace all tags in anims.xml in values folder with:

<item type="anim" at the front and </item> at the end


Replace all tags in raw.xml in values folder with:

<item type="raw" at the front and </item> at the end


2. Systemui.apk

When trying to decompile systemui, you will get bad magic value errors. Solution is to decompile without classes, as long as you don`t need to edit smali code. Even if you need to do that, you can still decompile classes.dex separately with smali baksmali.

a) Use -s switch when decompiling to copy classes.dex instead of decompiling it

java -jar apktool.jar d -s systemui.apk systemui-decoded

b) If you are using apkmanager, you can just export classes.dex, then delete classes inside the apk. Then decompile, edit, compile and add classes.dex back when ready.

EDIT: with updated apktool version systemui now compiles fine incl. classes.dex


3. com.htc.resources.apk

Here you get nice layouts tag errors and public entry issues. Again there`s an easy fix for that.

a) Replace all tags in layouts.xml in values folder with:

<item type="layout" at the front and </item> at the end

PHP Code:
<resources>
    <
item type="layout" name="htc_list_item_imageicon_text">@layout/zzzz_htc_list_item_imageicon_text</item>
    <
item type="layout" name="pin_keyboard">@layout/zzzz_pin_keyboard</item>
    <
item type="layout" name="zero_dummy_layout">@layout/alert_dialog</item>
    <
item type="layout" name="htc_list_item_2text_2stamp">@layout/zzzz_htc_list_item_2text_2stamp</item>
    <
item type="layout" name="htc_list_item_2text_bright">@layout/zzzz_htc_list_item_2text_bright</item>
    <
item type="layout" name="htc_list_item_image_2text_image_bright">@layout/zzzz_htc_list_item_image_2text_image_bright</item>
    <
item type="layout" name="htc_list_item_imageicon_2text_2stamp">@layout/zzzz_htc_list_item_imageicon_2text_2stamp</item>
    <
item type="layout" name="htc_list_item_separator">@layout/zzzz_htc_list_item_separator</item>
    <
item type="layout" name="htc_list_item_dlna_1">false</item>
</
resources
b) Delete entry "zero_dummy_dimen" in public.xml - it will be created correctly again during compile

02:41 by Apps Developer · 0

Tuesday 5 June 2012

Automated Root Method for HTC Evo 4G LTE



The HTC EVO 4G LTE will certinaly turn out to one of the favourite device with new releases and development continous with new root methos which is much easier then the solutions in place now.                          

It is an automated process just one click solution that will roots the phone, unlocks the bootloader from HTC development website and install a custom recovery process. everything in one go where other process require the user to unlock the bootloader by going into HTC website and mentioned required information etc.
With this application you need not to do anything and everything is automated with this

The following things need to be consider before you root the Device



  • Verifies Device and Battery Level (Needs to be charged to at least 40% before running)
  • Reboots to Bootloader and Gets Unlock Token
  • Sends Token to HTCdev.com
  • Retrieves Unlock_code.bin
  • Unlocks Bootloader
  • Flashes TWRP Recovery

Downloads 






03:14 by Apps Developer · 1

Monday 4 June 2012

Samsung Galaxy S II Toolkit brings everything under one Roof - New Version



Samsung Galaxy S II Toolkit helps users do a multiple tasks including side-loading apk files, adding a custom recovery, achieving root installing kernels, side-loading apk files and so on. The feature list is quite comprehensive and includes:

-  In the beginning it will check the USB Drivers and if it is not installed it will download it from KIES and install them
- It also checks for USB debugging connection to ADB
- Only downloads the files for the mobile  you select
- It Guides you through installing CWM
- it helps you through Rooting your device
- it will guide you through Flashing a Custom ROM
- It recommend you the steps through which you can do Flashing back to STOCK
- Guides you through Reboots Recovery and Download
- Side Load APK’s
- Keeps track of your current phone, last flashed recovery, last flashed rom.

It is very unique feature that it has ability to keep track of what all the changes done with your device. It’s also interesting to measure just how much of a flashaholic you really are. The developer is also working to port the toolkit to all other SGS2 variants.

01:49 by Apps Developer · 0