yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Raffie75:
@XJ tried to make my ohne pack again... I'm almost there :)

Got two errors and i can't find the error because i don't understand the error.

What do i have to do?

[*] MiuiMusic folder

recompiling MiuiMusic.apk...

I: Smaling...

I: Building resources...

aapt: warning: string 'music_picker' has no default translation in C:\Users\Raffie\Desktop\HTC Desire\AutoAPKTool1.0.4\_INPUT_APK\MiuiMusic\res; found: nl

I: Building apk file...

[*] DSPManager folder

recompiling DSPManager.apk...

I: Smaling...

I: Building resources...

aapt: warning: string 'dsp_settings' has no default translation in C:\Users\Raffie\Desktop\HTC Desire\AutoAPKTool1.0.4\_INPUT_APK\DSPManager\res; found: zh_CN zh_TW

I: Building apk file...

This is still a multilangpack, i can't get it right, to make only a NL pack, it seems i delete the wrong folders so when recompiling i get many errors.

But that's for later... first a little help with the problem above if you want.

Thnx in advance
[Desire Android Development] doromax:
Hi, I need a little help. I must de-odex a the stock samsung framework2.jar with his framework2.odex.

Now I'm very noob and I have some little problem.

I try to use XDAAUTOTOOL to do this work.

Where I put the framework2.jar abd framework2.odex , in which folder ?

I asj : where I put all framewok folder that I've copied from the phone ?

How can i put the BOOTCLASSPATH.TXT that I made ?

I inserrt this in AUTOTOOL \ edit bootclasspath :

that is where i put the origina framework folder ..... but nothing to do ....
[Desire Android Development] xavierjohn22:
===================================================================================

Version 5.0.0b

- Massive overhaul of codes

- New in this version is 87 and 88

87 = Can be use to remember single recompile of the last path (after 8)

Turn this ON and it will be active

88 = Is use to trigger the single recompile action

recompiling what is the last path

- Redo the recompile code

- Redo menu, starting from 21 is the new apktool 2.0.0.X settings

- 21 Use New apktool version

- 22 Use -f on recompile (this was migrated to work with new apktool and old apktool)

- 23 Use -c on recompile (this is new to work on new apktool)

- 24 Use -o on recompile (this is new to work on new apktool)

This will create a apkname_NEW.apk in _OUT_NEW folder

- 31 Overwrite resources.arsc

- 32 Overwrite classes.dex

- 33 Overwrite using _CUSTOM_RES

- 34 Copy added resources to APK

- 35 Make zipaligned apk from _OUT_APK

- 36 Force delete dir on Decompile (-f)

- 37 Optimized All PNGS in APKs

- 38 Optimized "xyz.9.png" PNGS in APKs

ISSUE:

- The ZIP Align is broken on some apks

- Use 42 ON but leave 43 and 44 off for now

- This will also be redo because the code right now zipaligns then sign

should be sign then zipalign

===================================================================================

Version 4.0.2

- Added Menu 21 ON/OFF for new apktool support

- Changed Menu 22 ON/OFF settings saved, Overwrite resources.arsc

- Changed Menu 23 ON/OFF settings saved, Overwrite classes.dex

- Changed Menu 24 ON/OFF settings saved, Overwrite using _CUSTOM_RES

- Changed Menu 25 ON/OFF settings saved, Copy added resources to APK

- Changed Menu 26 ON/OFF settings saved, Make zipaligned apk from _OUT_APK

- Changed Menu 27 ON/OFF settings saved, Force delete dir on Decompile (-f)

- Changed Menu 28 ON/OFF settings saved, Force delete dir on Recompile (-f)

- Changed Menu 29 ON/OFF settings saved, Optimized All PNGS in APKs

- Changed Menu 30 ON/OFF settings saved, Optimized "xyz.9.png" PNGS in APKs

- Changed Menu 85 ON/OFF settings saved, Sign APKs after build themed apks

- Changed Menu 86 ON/OFF settings saved, Build a Flashable Theme Zip (after 84, 85)
[Desire Android Development] hello00:
does the new xdaautoapktool support lollipop? [MENTION=308902]xavierjohn22[/MENTION]
[Desire Android Development] Old Jimbo:
Download link is broken. Can someone post a working link to download the latest version of this application? :) Thanks!
[Desire Android Development] dzikk:
Download link is broken
[Desire Android Development] MrEdDy23:
Download link not work.. please fix ;)
[Desire Android Development] ze7zez:
xdaAutoAPKTool

Upload from local HDD.

xdaAutoAPKTool_V4.0.2.rar

xdaAutoAPKTool_V5.0.0b.rar
[Desire Android Development] MrEdDy23:
big thanks! :good:
[Desire Android Development] fancyfree:
This software is awesome.

Some apk files which i cannot decompile or recompile with other apktools software, here everything is OK

Thank you very much!!!
[Desire Android Development] sakalsk:
Becouse legends never die :

http://www.multiup.org/en/mirror/619f9386ace1d3b22a1fe281bc2de1ae/xdaAutoAPKTool_V5.0.0b.rar
[Desire Android Development] Terraalpha:
xda AutoAPKTOOL v5.0.0b Download Link Not working

Please help !!!!
[Desire Android Development] Masoud.Ser:
hi

AutoAPKTOOL link not work!!
[Desire Android Development] ze7zez:
new links
[Desire Android Development] Terraalpha:
Thanks for the new links
[Desire Android Development] meysamsh:
hello

i can not download from this link please share other new link for me

thanks
[Desire Android Development] ze7zez:
tonight

---- edit ----

I have restored the original links in post #987.

The only difficulty may be the need to log in to download files.
[Desire Android Development] meysamsh:
thank you
[Desire Android Development] Lostboyy:
good thanks

Good Job :good::good:
[Desire Android Development] xavierjohn22:
There's no 'music_picker' string item anymore, see the english string, it does not have that. You have to correct your NL string for MiuiMusic

Same for DSP manager, the chinese strings 'dsp_settings' is not needed if it is not in the values strings.xml
[Desire Android Development] Raffie75:
Aha, then i somehow have the wrong strings, so i can delete those strings and try again?
[Desire Android Development] xavierjohn22:
yeah you can try for the miui music only, Single recompile

replace the string,

<string name="ringtone_picker">Ringtone</string>

in dsp_manager, yes you can delete that

EDIT: ill verify what i have here for dsp when i get there, i am doing multi lang too, lol

EDIT:

there are new strings too

<string name="dsp_settings_headset">DSP Settings - Headset</string>

<string name="dsp_settings_speaker">DSP Settings - Phone Speaker</string>

<string name="dsp_settings_bluetooth">DSP Settings - Bluetooth Device</string>

<string name="pref_equalizer_preset_title">Select Preset</string>

<string name="eq_preset_acoustic">Acoustic</string>

<string name="eq_preset_bass_booster">Bass Booster</string>

<string name="eq_preset_bass_reducer">Bass Reducer</string>

<string name="eq_preset_classical">Classical</string>

<string name="eq_preset_deep">Deep</string>

<string name="eq_preset_flat">Flat</string>

<string name="eq_preset_r_and_b">R&B</string>

<string name="eq_preset_rock">Rock</string>

<string name="eq_preset_small_speakers">Small Speakers</string>

<string name="eq_preset_treble_booster">Treble Booster</string>

<string name="eq_preset_treble_reducer">Treble Reducer</string>

<string name="eq_preset_vocal_booster">Vocal Booster</string>

<string name="eq_preset_custom">Custom</string>
[Desire Android Development] Raffie75:
<string name="ringtone_picker">Ringtone</string> i already found but the dsp_manager i don't have a clue... deleted these strings

<string name="dsp_settings_headset">DSP Instellingen - Koptelefoon</string>

<string name="dsp_settings_speaker">DSP Instellingen - Telefoon Speaker</string>

<string name="dsp_settings_bluetooth">DSP Instellingen - Bluetooth Apparaat</string> and recompiled it but still the same error?!

EDIT: Those are the only "dsp_settings" i can find.
[Desire Android Development] Raffie75:
Thnx for now XJ, got to go to bed... it's 1:51 in the Netherlands.

Thnx and good night :)
[Desire Android Development] Raffie75:
I will look into it tommorow, but i have those already if i'm right... Ill go and look tommorow.
[Desire Android Development] 1982Strand:
What?

I compared the strings from the old 1.4.29 and then the new 1.5.6

I found that the dsp_settings string was deleted and 3 new were added, the headset, speaker and bluetooth.

The error is the wexact same as mine, posted a little earlier. I corrected the strings in the -ZW folder, as they weren't updated and still had only dsp_settings and not the 3 new.

= All errors gone when i recompiled..

If you look at the miui music error, it's the same. it's because the string doesn't exist, it was changed to a new name :) I also had this error a while back, it was also posted...

I could be wrong of course, but to me it seems odd, as i did this, get no errros and no fc's when running the apps.. :)

EDIT: Take a look at my post in the ROM thread:

http://xdaforums.com/showpost.php?p=13568361&postcount=4709
[Desire Android Development] xavierjohn22:
It will not FC, no problem at all since it is just there.

If you look at public.xml they havent remove it yet

<public type="string" name="dsp_settings" id="0x7f06002c" />
<public type="menu" name="menu" id="0x7f070000" />
<public type="id" name="FrequencyResponse" id="0x7f080000" />
<public type="id" name="reset" id="0x7f080001" />

So to make the error go away, either delete it in ZH as you say or put it in values strings.xml

I did what i posted above for i dont know if they will permanently remove it, they may use it again for some other weeks update. Thats the onlyu reason i still add it.
[Desire Android Development] 1982Strand:
Hmm, ok.. I see, so i'm partially wrong, hehe :) I'll keep an eye on this for next update!
[Desire Android Development] xavierjohn22:
yup, also apktool will often tell us if there's something not right on the strings, you'll catch it and run on it next time, i'm pretty sure
[Desire Android Development] Raffie75:
Looks like i finaly made my own langpack (still multilang but oke).

Thnx for the help i needed XJ and 1982Strand.

Fixing the strings was not that easy but with a little help of you two... THNX!

Got one question for @XJ, which folders do i have to delete to make a NL pack only?

Which "values" should i not move or delete to make a usable flashable NL pack?

Thnx in advance.
[Desire Android Development] Raffie75:
I made my own multilang pack and i flashed it and it seems to be working only after flashing the pack it says that it is base version 1.4.22 how can i change that?

Do i have to change the build.prop in system?

Do i have to change each time i make a new pack (every week)?

which one can i change? Or is it "forbidden" to change something in build.prop?

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MIUI
ro.build.display.id=1.4.22-MIUI-XJ
ro.build.version.incremental=1.4.22
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=Fri Apr 22 11:43:55 CST 2011
ro.build.date.utc=1303443835
ro.build.type=userdebug
ro.build.user=miui
ro.build.host=xjmod
ro.build.tags=test-keys
ro.product.model=HTC Desire
ro.product.brand=generic
ro.product.name=libra_bravo
ro.product.device=bravo
ro.product.board=bravo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=qsd8k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bravo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=libra_bravo-userdebug 2.3.3 MIUI 1.4.22 test-keys
ro.build.fingerprint=generic/libra_bravo/bravo:2.3.3/MIUI/1.4.22:userdebug/test-keys
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.sf.lcd_density=240
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.ecc.HTC-WWE=999
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.ril.hsxpa=2
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.telephony.default_network=0
ro.ril.enable.prl.recognition=1
ro.ril.def.agps.mode=2
ro.opengles.version=131072
dalvik.vm.heapsize=64m
ro.media.dec.jpeg.memcap=20000000
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.modversion=MIUI-1.4.22
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.setupwizard.mode=DISABLED
ro.com.android.dateformat=yyyy-MM-dd
ro.com.android.dataroaming=true
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.moddevice=G7
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Desire Android Development] 1982Strand:
Not entirely sure about this, but my guess would be every line containing the "1.4.22" in it..

So, in theory, you'd have to change it manually every week.

But i'm pretty sure you can just copy/paste the build.prop from the latest ROM from XJ and put it in your flashable zip.. If that doesn't work, then you can put in the build.prop inside the Flashable_Update.zip in the _Flashables_ folder, BEFORE pressing 18 - Build flashable zip..

What i did was making 2 versions of my lang pack for 1.5.6:

First one:

1. Take latest en/zh OTA upgrade from XJ

2. decompile, translate, recompile, build usable apks

3. Copy the OTA file into _Flashables_ folder, rename it to Flashable_Update.zip -> This makes your lang pack identical with the current upgrade, meaning you get all changes made in the other files, besides the apks we translate :)

4. edit the updater script in the zip with notepad++. Only to add "DK" in the text line after english and chinese. But you can edit this to your liking ;)

5. Now i build flashable zip, option 18 in the tool..

Second one:

Same as first, but this time using the full rom, also adding danish language to the smali coding translations, as XJ writes in post #3

I did this one because of 2 things:

1. I got the UID mismatch-crap by just using the OTA upgrader

2. I got danish translations in some places were we usually would get english due to smali coding. All multilang packs will only have 1 language in smalicodes, no matter which other language the system is in..

Hope this helps! :)
[Desire Android Development] Kalashnikitty:
congratz xj, you´re on page one :)

http://www.xda-developers.com/android/auto-apk-tool-for-modders-devs-translators/
[Desire Android Development] Krakatoa:
Awesome!!. Good work!!

Is there no version for Linux?

Sorry for my bad English :rolleyes:
[Desire Android Development] xavierjohn22:
Just delete the build.prop in system.

Delete it inside the flashable_update.zip too

You dont need a build.prop since full roms and people who installed miui already has a build.prop
[Desire Android Development] xavierjohn22:
Wowa. Thanks guys!
[Desire Android Development] zergburger:
ggreat tool, thanks for the hard work.

hope you don't get threatened to be sued by markhuk though he seems to think he owns all english translations of miui
[Desire Android Development] fritzgerald:
Awesome work. Thanks for this.

Do you mind if I snag some of your scripts for my own Context Menu mod?

I've added apktools scripts to my right context menu in windows so I can right click on an apk or jar and decompile/compile/sign etc.

I'll shoot you a copy after I get the compile all bug worked out.
[Desire Android Development] 1982Strand:
This surely sounds interesting... :)
[Desire Android Development] fritzgerald:
Here's a couple screenshots and explanations... sorry to thread jack.

Right Click on APK =

Right Click on JAR =

Right Click on a folder =

Right Click on a folder empty space =

Using the pull/system/framework or app will create a system sub directory and then a framework or app sub directory in that folder and then pull all the contents of that folder off your phone. ie. If I was in C: and right clicked the background and chose Pull\System\Framework it would create C:\system\framework and copy all the contents of \system\framework from the phone into this folder if i was in C: and right clicked on windows folder and picked it it would copy all the contents of \system\framework from the phone into C:\Windows\system\framework\*.*

Pull any file will pull whatever you tell it to and dump it in whatever folder you clicked it on. ie. If I was in c: and right clicked the background and chose that it would pull my file and place it in c:\*.apk if i was in c: and right clicked on windows folder and picked it it would dump the apk in C:\windows\*.apk

Decompile folder will decompile all apks and jar files in the folder you chose it on.

Compile folder (not working yet, hopefully will with the help of your scripts) will compile all the apk and jar files in whichever folder you chose it on with a title of "new-*.jar or new-*.apk" doesn't overwrite your existing apks.

I've added "sign zip, sign apk, and sign jar" and cleaned up the menus by adding dividers and changing icons also but haven't updated the context menu on my work PC.
[Desire Android Development] xavierjohn22:
none at the moment my friend, but i'm sure some great devs here will do so, i'll try to touch base with some of our linux modders

LOL, anyone can translate miui. there just have to be someone to be the first i guess.

No problem mate, do as you need to
[Desire Android Development] xavierjohn22:
Cool, it's a reg file you need to put in pc registry right?

Anyways, that gives me an idea to add Pull apks and framewrok files via adb in AUTO APK TOOL too, cheers!
[Desire Android Development] fritzgerald:
The "installer" I made for it is just a batch file that copies all the files into a folder on your C:\, runs a reg file that installs all the registry keys where you need them, and adds path values to all the tools and batch files. Also there's an "uninstall" script in case anyone decides to remove it after installing and doesn't want to search through the registry to find the keys.

Once I get all the bugs worked out of it and clean up the scripts I might make it into a Setup.exe and distribute that. If not the batch file installer work just as good.
[Desire Android Development] xavierjohn22:
Cool. Would love to have one too. Ill post it too in the op.
[Desire Android Development] cyansmoker:
Anyone interested in a Linux/MacOS port?

I think I will do one for myself anyway so let me know if I should share it...
[Desire Android Development] xavierjohn22:
You should bro. Ill post it in the op

Someone already ask about a linux version.
[Desire Android Development] Kalashnikitty:
@fritzgerald, which theme are u using in your windows? :) sry for ot... :p
[Desire Android Development] xavierjohn22:
Lol I also noticed that, its like miui tabs
[Desire Android Development] fritzgerald:
It's called Placebo Black Market (Calibri). You can get it here...
[Desire Android Development] xavierjohn22:
cool, thanks, suits my w7
[Desire Android Development] Gunthermic:
Okay, I dont have the Desire, but if I follow this right, that doesn't matter. I have the HTC Thunderbolt.

So I decompile the framwork-res and the com.htc.resources file no problem.

I am sure I missed somethign but here is what I did:

Copied all the new png's straight into the res/drawable-hpdi folder

Overworte some of the png's in the res/drawable-hdpi folder

Added new xml's into the res/drawable folder

It says it compiles and I have a new copy in the dist folder

Once done I do the 18, it says it's fine.

the zip has nothing in it. It doesn't add the com.htc.resource.apk into the framework folder at all.

I manually moved it into the folder via 7Zip.

After flashing it, it does a boot loop.

So the question's are:

1. Why does it not add it to the flashable zip?

2. Am I adding the png's correctly? Is there a differnt way for new png's vs replacing png's?

3. Adding new xml's?

4. Why the bootloop?

Using a froyo ROM desensed.
[Desire Android Development] 1982Strand:
@ Raffie, from MIUI XJ thread:

To find the apk's to translate, you need to use the english sources from the previous version (1.5.6), you know, the values-en folders..

Then you need the newest ROM, in this case the 1.5.13 en/zh ota upgrade (or the full rom, but ota is smaller in size)

You then need to compare the values-en folders from the 1.5.6 sources with the ones from 1.5.13, using winmerge or diffmerge. Then you can find out what has changed and if strings are added or deleted.. :) .....And then submit those changes to your own language sources.....

But take a look in this thread some pages back, i think we talked about this earlier ;)
[Desire Android Development] Raffie75:
The first part i understand... i did that already (or better, i'm busy with it right now)

I am comparing the value-en folders with the value-nl folders and adding or deleting strings.

But that is not exactly what i mean, but i think you gave me the anwser above.

I understand (and i'm already busy with it) I have to compare with winmerge or diffmerge... so i have to check all apks one by one if there is a change of string, there is not other way to see which apk has to be changed?

Hope you understand what i mean... when writing it down it confuses myself :p
[Desire Android Development] xavierjohn22:
To answer the question on way to know how the apk changed

i have three ways

- One is by looking at the OTA Updater of the chinese, if they patch an apk i will have to look at the apk. But sometimes the patch does not affect translations

- the other one is yeah, looking at the changelog

- the solid one is folder compare, i always do it like this

_INPUT_APK_1.5.6 ( meaning i rename th old one but is still in my working folder)

_INPUT_APK_1.513 (this is the new decompiled apks)

then i compare both, ill post screen shots later

FYI: Settings strings will gave you a hard time like Dan said, LOL
[Desire Android Development] 1982Strand:
Yep, what i've learned with translating apks, the best way (but also the "hard" way) is to compare old sources with the new. It's faily easy to go through every apk to find changes.

I use diffmerge, it has color codes that shows you right away if there are changes.. Winmerge probably has something similar :)

But i must say, this last 1.5.13 build is a killer!! Soooo many strings to edit!! :eek:
[Desire Android Development] xavierjohn22:
decompile the new ones

Compare, that is why it helps to have values folder and values zh in my apks, i use the values-zh to compare the strings with the new apks
[Desire Android Development] Raffie75:
Thank you both @XJ and @Dan, i'm almost ready with settings than i will check the way you said XJ.

What programm do i have to use for comparing the _INPUT_APK_1.5.6 to the _INPUT_APK_1.5.13 folder?

For comparing the strings i use WinMerge and yes @Dan it has something simmular like the colors you mentioned.
[Desire Android Development] Gunthermic:
okay, why even if this program compiles the resources file with no errors. thr mms.apk always FC after flashing it. All I am doign is adding 3 xml's for 4G animation and all the png's for it.

I get no errors decompiling and have tried both 1.3.1 and 1.3.2
[Desire Android Development] xavierjohn22:
adding values-en? values-folder?

or directly editng it in structure?

miui mms.apk or other mms.apk?
[Desire Android Development] 1982Strand:
XJ, i downloaded your update 1 for en/zh..

I get some errors though while decompiling Gallery, see the attached log..

I tried changing framework files and switching between apktool 1.3.1 and 1.3.2, but i can't make it work...

Any suggestions?

To me it seems like it has something to do with the framework file..? Well, it needs some resources which can't be found, but i'm stuck here.. :(

I noticed that in users/administrator/apktool/framework/ there is a 127.apk, where do this come from and does it have anything to do with this? As the framework files are just named 1.apk here..

And just curious.. The update 1, what is updated? i don't see any language string changes? Other than some stuff in various folders like layout and others?

--- Goodmorning btw :D :D