Database Users

APK Manager Ver 5.0 - Makes Modifying Ur Apk A Breeze (Windows/Linux)

no longer supported visit http://forum.xda-developers.com/showthread.php?t=1310151

Can this be used to change the main icon of an app?
Also can it be used to theme an app?
Thanks for this!
Sent from my GT-I9100 using Tapatalk

jameslfc5 said:
Can this be used to change the main icon of an app?
Also can it be used to theme an app?
Thanks for this!
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
yes and yes

the script in v5.0 the command numbers are the same as in 4.9 ie, to read log it's still option 21 in 5.0, but under the about option it says v5.0 is this correct, or should the command numbers be different...

I keptthe options the same there is some more tweaking that needs to be done and not being the original guy who wrote this I am reluctent to change it much. This is basically a unofficial release of his script until he decides to make more updates to this but feel free to report anything that does not work or if you see a patch I might of missed or over looked a change needed
Sent from my Droid using XDA Premium App

Wow! I was looking at APK Manager 4.9 just last night but didn't download it since I noticed it hadn't been updated since last year.
I just happened to Google again right now, and noticed this 5.0 that was just released this morning.
Thanks for updating this. I'll be playing around with it tomorrow...

I'm stumped...I'm trying to run this on Vista. I have Java installed, but when I run the script I get:
Java was not found, you will not be able to sign apks or use apktool
Press any key to continue . . .
I realize this is probably not a problem with your tool, but I'd appreciate any help offered to get it working.
***Edit*** Found my problem. When I set my path for Java I used a : instead of a ; it's working perfectly now.

I have yet to be able to decompile an app with dependencies using option 10, the managers says to drag the dependee apk in this window or type its path, I can't drag and drop anything to the manager and I don't understand type in its path, do I type the path of the location of the apk on my computer or what? Also where should the framework-res be installed, in the other folder? I didn't install apk manager in my Android folder where my SDK is located it's just on my computer under a general file/folder, does it matter where it's installed? Please help, I've asked this question on the 4.9 thread but got no response...
oh yeah I forgot to mention that the apps I'm trying to decompile using option 10 are non system apps like the ones that you get from the market that can't be decompied using option 9...

has the linux version script been updated to include the option for installing resources for dependecies

adude247 said:
I have yet to be able to decompile an app with dependencies using option 10, the managers says to drag the dependee apk in this window or type its path, I can't drag and drop anything to the manager and I don't understand type in its path, do I type the path of the location of the apk on my computer or what? Also where should the framework-res be installed, in the other folder? I didn't install apk manager in my Android folder where my SDK is located it's just on my computer under a general file/folder, does it matter where it's installed? Please help, I've asked this question on the 4.9 thread but got no response...
oh yeah I forgot to mention that the apps I'm trying to decompile using option 10 are non system apps like the ones that you get from the market that can't be decompied using option 9...
Click to expand...
Click to collapse
realy no one...

This is perfect. I've been finding myself playing with quite a few apk's lately and going through a bunch in order to test them. This will save me quite a few steps. Thanks.

Great update. Thanks

Here is a log of the error when decompileing an apk. It works fine in 4.9 with apktool 1.3.1 but gives this error in your 5.0. I have seen this where one version of apktool will decompile the apk but the newer version will not.

+1
Sent from my SCH-I500 using XDA Premium App

adude247 said:
I have yet to be able to decompile an app with dependencies using option 10, the managers says to drag the dependee apk in this window or type its path, I can't drag and drop anything to the manager and I don't understand type in its path, do I type the path of the location of the apk on my computer or what? Also where should the framework-res be installed, in the other folder? I didn't install apk manager in my Android folder where my SDK is located it's just on my computer under a general file/folder, does it matter where it's installed? Please help, I've asked this question on the 4.9 thread but got no response...
oh yeah I forgot to mention that the apps I'm trying to decompile using option 10 are non system apps like the ones that you get from the market that can't be decompied using option 9...
Click to expand...
Click to collapse
First you need to make sure the path has no empty parts
C://androidfiles/apk_manager_5.0 is fine, C://android files/apk_manager_5.0 would create issues.
You only need to install new framework`s in the following cases:
1. You decompile a system apk from a different Android platform then before (Froyo, Gingerbread eg.) - in that case you install a new framework-res.apk
2. You decompile a system apk with dependencies to a 2nd framework like in Sense ROM`s or Samsung ROM`s - in that case you will in case of Sense install a new com.htc.resources.apk
You can install these with 10 option and just drag the framework in the bottom of the script window. In the rare case this fails (never happened to me), you can manually install frameworks in apktool:
open a terminal/command prompt
cd into the folder, where your apk is located
(in this example sensation)
now type this:
apktool if framework-res.apk sensation (sensation will be a tag name of the framework)
and then after type this:
apktool if com.htc.resources.apk sensation (sensation will be a tag name of the framework)
You don`t need the tags, but in case you are working on multiple projects with apktool, it makes sense. In any case I doubt you will have issues, if you drag framework to the correct area.

zelendel said:
Here is a log of the error when decompileing an apk. It works fine in 4.9 with apktool 1.3.1 but gives this error in your 5.0. I have seen this where one version of apktool will decompile the apk but the newer version will not.
Click to expand...
Click to collapse
1.3.1 is always good to have, since sometimes new apktool versions create issues (and vice versa). For that reason I always have several versions on hand so I can just drag them in "other" folder when needed.

Exactly how do I change the path to include adb.exe, which in Android SDK 12 is in the C:\Program Files (x86)\Android\android-sdk\platform-tools path.
Because Every time I launch the script in APK Manager, I get this message "Adb was not found. You will not be able to manipulate the files on your phone". I would really like to get this working. Thanks guys.

Hi.
I would have preferred to have figured this out for myself but I'm stumped here. An unmodified framework decompiles ok but any other apk fails.
{
"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've attached the log and the unmodified apk I'd like to mod.

Hi
Im trying to edit the framework-res.apk from my rom, to change the battery icons.
Im using APK manager to decompile the apk, then i replace the stat_sys_battery pngs with 30 custom ones. after that i edit the stat_sys_battery.xml and zzzstat_sys_battery.xml to include my pngs at specific battery percantages.
that all goes well, but when i try to compile the .apk i get some errors.
first i have to type y or n i its a system app.
i press y and enter
after that it says to navigate to /apkmanager/keep and delete all files i edited.
but all files in this folder is the stock ones (IE unedited)
i have tried a bunch of things:
1. do nothing and continue
I end up with a 4 KB unsignedframework-res.apk containing onlt meta info
2. I delete the stock versions of the files I edited
I end up with exactly what was in the keep folder, an .apk without the files which I deleted
3. I delete the stock versions of the files I edited, and replace them with my modified files
I end up with what seems to be what i need (when i open the .apk in 7-zip i see all of my pngs and xmls) but when i flash it i end up with the battery unknown icon
Can anyone enlighten me??

Ok, I have no more Java or adb.exe issues. The problem is, once I choose 9 to decompile, the cmd window closes and nothing gets decompiled. Any workaround for that? I tried to change the compatibility to XP sp3 but no help.

Free 50Gb Online Storage before 31st December 2011

Hurry, whilst stocks last!
Get it here
Make sure you edit the lines of the build.prop exactly as they are shown in the above thread (or see post 6 below).
{
"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"
}
EDIT: I have decided to treat this as an IQ test. If it doesn't work for you, it means that you are incapable of reading, writing and thinking for yourself. You should reflect long and hard on your inability to perform basic tasks and should probably not post things such as 'it doesn't work!'. That is basically the same as admitting that you are dumb and admitting it in a public forum.

This works

trumpetboy101 said:
This works
Click to expand...
Click to collapse
I know. I wouldn't have posted it otherwise
Tell all your friends. It will work on any Android device.

Thank

This unfortunately does not work for me as I cannot get my phone model to show as VS910 4G.
Every time I edit my build.prop file (as stated in original post) it does not save any changes. Any ideas or clues as to what I could be doing wrong.
I am rooted on 2.3.5.

ajoshi said:
This unfortunately does not work for me as I cannot get my phone model to show as VS910 4G.
Every time I edit my build.prop file (as stated in original post) it does not save any changes. Any ideas or clues as to what I could be doing wrong.
I am rooted on 2.3.5.
Click to expand...
Click to collapse
This does work. My screenshot proves it. I was waiting to see how long it took someone to screw up something this basic.
Did you actually read and follow the instructions?
OK, do this (by the way this is what is said in the thread I linked to)...
1. Make sure you are rooted
2. Open system/build.prop in a text editor
3. Change the lines in your build.prop that read
Code:
ro.product.model=GT-N7000
ro.product.brand=samsung
to read
Code:
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
4. Reboot (which I am guessing you didn't do)
5. Download the 'Box' app from the market and sign up for an account
6. Edit the build.prop back to its original state
7. Reboot again

If I only had seen before :'(
Sent from my Xoom on Tiamat

[David] said:
If I only had seen before :'(
Sent from my Xoom on Tiamat
Click to expand...
Click to collapse
What do you mean? It is available until the end of 2011.
You can do it now.

Like magic!
Thanks

Doesn't work.
Everytime i reboot the Galaxy Note, those lines are changed to original values automatically.
I am on 2.3.6 , looks like some more values needs to be changed.

bmunshi said:
Doesn't work.
Everytime i reboot the Galaxy Note, those lines are changed to original values automatically.
I am on 2.3.6 , looks like some more values needs to be changed.
Click to expand...
Click to collapse
Of course!!
Because you can't do it, there is obviously a problem!!
If you are rooted and can't edit the build.prop on your device, copy it on to your SD card and copy it to a computer and edit it using Notepad or Notepad++. Then copy it back to your SD card and then paste it back in to your system partion. Then reboot.
Next time try using some common sense and don't blame others for your own deficiencies.

Works fine, all done with ES explorer.
Make sure /system is mounted as writeable.
You get swype complaining about a licence issue but this goes away when you set the model and manufacturer back.

nobnut said:
This does work. My screenshot proves it. I was waiting to see how long it took someone to screw up something this basic.
Did you actually read and follow the instructions?
OK, do this (by the way this is what is said in the thread I linked to)...
1. Make sure you are rooted
2. Open system/build.prop in a text editor
3. Change the lines in your build.prop that read
Code:
ro.product.model=GT-N7000
ro.product.brand=samsung
to read
Code:
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
4. Reboot (which I am guessing you didn't do)
5. Download the 'Box' app from the market and sign up for an account
6. Edit the build.prop back to its original state
7. Reboot again
Click to expand...
Click to collapse
thanks for the trick. i was using my sister SG2 and i notice there's more free games in samsung apps than the one in SGN. can i use the same method to download games by tricking samsung apps 2? the SD data should be the same...would be great if you can tell me what is the exact code for SG2.

foochuangyeh said:
thanks for the trick. i was using my sister SG2 and i notice there's more free games in samsung apps than the one in SGN. can i use the same method to download games by tricking samsung apps 2? the SD data should be the same...would be great if you can tell me what is the exact code for SG2.
Click to expand...
Click to collapse
Before you try this, have a think for a second... What do you think the reason is for this difference in the number of apps/games? The SGSII has a smaller screen with different dpi settings. The apps that don't show for the Note will probably either not run, or are not compatible with it.
Anyway, if you want to try, change any reference to N7000 to whatever shows for your sister's SGSII (there are a few of these) and change the lines
Code:
ro.build.description=GT-N7000-user 2.3.5 GINGERBREAD XXKJ4 release-keys
ro.build.fingerprint=samsung/GT-N7000/GT-N7000:2.3.5/GINGERBREAD/XXKJ4:user/release-keys
to whatever shows in your sister's build.prop.
Make sure you backup your build.prop to your SD card (you can just copy it back when you have finished rather than editing it again). Just in case, also have a Nandroid backup to hand if you need it.

nobnut said:
Of course!!
Because you can't do it, there is obviously a problem!!
If you are rooted and can't edit the build.prop on your device, copy it on to your SD card and copy it to a computer and edit it using Notepad or Notepad++. Then copy it back to your SD card and then paste it back in to your system partion. Then reboot.
Next time try using some common sense and don't blame others for your own deficiencies.
Click to expand...
Click to collapse
OOps that's rude. Please dont assume others are stupid.
I am rooted and can edit the build.prop, after editing and saving if i reopen it shows the new value.
But once phone is rebooted it changes back to original value, that is what i meant.
BTW, just check your old updates, in first you asked to change the .Brand and then in the same thread asked to change back the .manufacture value. I am not blaming, it might be typo or something.
End result, still there are some more values needs to be changed.

bmunshi said:
OOps that's rude. Please dont assume others are stupid.
I am rooted and can edit the build.prop, after editing and saving if i reopen it shows the new value.
But once phone is rebooted it changes back to original value, that is what i meant.
BTW, just check your old updates, in first you asked to change the .Brand and then in the same thread asked to change back the .manufacture value. I am not blaming, it might be typo or something.
Click to expand...
Click to collapse
[mod edit]
I made no mistake. You have to change the lines from the first ones to the second ones. There are differences between the two manufacturers' build.props.
I am not blaming, I am just pointing out that people need to learn to read, think and comprehend.
End result, still there are some more values needs to be changed.
Click to expand...
Click to collapse
You are wrong. [mod edit]

Christmas is over then

Confirming, if you follow the basic instructions, this works PERFECTLY.
50GB available to me. Cheers OP.

straxusii said:
Christmas is over then
Click to expand...
Click to collapse
Oh man! Please don't introduce another concept such as Christmas to this thread. Some XDA users' heads will explode trying to grapple with that as well as editing two lines in a build.prop.
AdzUK said:
Confirming, if you follow the basic instructions, this works PERFECTLY.
50GB available to me. Cheers OP.
Click to expand...
Click to collapse
Hallelujah!!
EDIT: At the risk of causing severe haemorrhaging in some users... try this:
Once you have created your account, clear the 'Box' app data and cache in Settings and then using another email address, get another 50Gb. Repeat until you get bored.
Shabba!

Woking great!
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
Click to expand...
Click to collapse
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.

{APP} Custom Rom Maker! RSL 1 [6/12]

Hey, so creating customs roms are quite fun. So I decided to develop a little application that helps new users out a bit. Now, this won't turn you into a full fledge rom developer, but will allow you to make minute customizations to an already existing rom.
Sorry, this is no longer under development However, for anyone feeling adventurous, I have uploaded the source code.
Features
ADD & Remove System Applications
Init.d Tweaks
Edit Updater-script
Build Prop Editor
Change Rom Kernels
Build Prop Presets
Zip Align all System Applications
ADD Google Apps to Rom
Sign Roms
Change Boot Animation
Download Source from Github
ADD & Remove Data Applications
ADD & Remove Ringtones
ADD & Remove Notifications
Add Superuser APK and Binary
Move System Apps to Data Folder
Pull any System/Data/Ringtone File from the Rom
Automatic Zip and Unzip of Any Rom
*New*Search Feature
{
"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"
}
New: Zipalign all System Applications
New: Init.D Tweaks
New: Download Source from Github
Future Updates: I hope to be adding more functionality in future updates..so stay tuned!
Download
RSL 1 is available on the server, run The Rom Maker.exe (from the attached zip), and it will trigger an update and update you to RSL 1.
To launch, run The Rom Maker.exe
Check below

Dude thats awesome. Trying it now!
Sent from my SGH-T959V using xda app-developers app

awesome, im gonna link this in the evo 3d, forum linking the credits to you, and leaving your dl link(for counts) in tact.................awaiting newer features patiently, keep up the good work
heres my post, hope its not a problem http://forum.xda-developers.com/showthread.php?p=29851733#post29851733

Looks good, will try.
Thanks
Sent from my MT11i using Tapatalk 2

Seems like a nice little tool for tweaking ROMs a bit. Hopefully you can add more features in the future, but even as it is, it should be handy for anyone who wants to tweak ROMs a little bit. By my understanding, it should allow the removal of preinstalled rubbish from stock ROMs, right?

I see you are using Ionic.Zip.dll the same one I used in Droid Manager for creating Custom Roms Too
But you have an issue bro
1- Make My Rom button doesn't work on the first run, I had to close and reopen the program.
2- the result zipped ROM will fail to flash in CWM & is twice in size than the original ROM
why it will fail, because if you open the result zipped file you will find a folder that has the project's title and the ROM files are inside that folder.
while CWM checks for META-INF folder on the root directory of the zipped ROM.
The reason why it's twice in size than the original ROM is because after the program unzips the base rom it doesn't delete it from workspace which causing "Ionic.Zip.dll" to include it in the result zipped rom making it twice in size than the original ROM.
Also please note that adding a data folder in the project will not lead into having anything inside /data/app after the rom is flashed because the updater-script must be modified to include the commands which tell CWM to: A- Mount Data Partition. B- Extract contents of data folder in the zipped file to Data Partition on the phone.
Also it would be better if your program doesn't fully remove the files from the hard disk, rather than just moving them to Recycle bin it's safer, since they can be retrieved
I'm sorry for that comment but I thought I would give you a quick feedback since it's the main step in making a better program
Good luck

does this support aroma installer ?
Any way,big thanks to you dude

DeepUnknown said:
I see you are using Ionic.Zip.dll the same one I used in Droid Manager for creating Custom Roms Too
But you have an issue bro
1- Make My Rom button doesn't work on the first run, I had to close and reopen the program.
2- the result zipped ROM will fail to flash in CWM & is twice in size than the original ROM
why it will fail, because if you open the result zipped file you will find a folder that has the project's title and the ROM files are inside that folder.
while CWM checks for META-INF folder on the root directory of the zipped ROM.
The reason why it's twice in size than the original ROM is because after the program unzips the base rom it doesn't delete it from workspace which causing "Ionic.Zip.dll" to include it in the result zipped rom making it twice in size than the original ROM.
Also please note that adding a data folder in the project will not lead into having anything inside /data/app after the rom is flashed because the updater-script must be modified to include the commands which tell CWM to: A- Mount Data Partition. B- Extract contents of data folder in the zipped file to Data Partition on the phone.
Also it would be better if your program doesn't fully remove the files from the hard disk, rather than just moving them to Recycle bin it's safer, since they can be retrieved
I'm sorry for that comment but I thought I would give you a quick feedback since it's the main step in making a better program
Good luck
Click to expand...
Click to collapse
Thanks a bunch for your suggestions. Wow...I just learned my lesson of why I should never leave catch statemetns empty lol. And I didn't know that about the data/app folder thing. I went back and added some code to add lines to the setup-script though I haven't tested it yet, so I'll see if that works. Haha, but thanks again for helping me catch those bugs, lol tell me if you find anymore.

SifJar said:
Seems like a nice little tool for tweaking ROMs a bit. Hopefully you can add more features in the future, but even as it is, it should be handy for anyone who wants to tweak ROMs a little bit. By my understanding, it should allow the removal of preinstalled rubbish from stock ROMs, right?
Click to expand...
Click to collapse
Thanks, and yes it will allow you to easily remove that bloatware.

kifgep said:
does this support aroma installer ?
Any way,big thanks to you dude
Click to expand...
Click to collapse
not yet, I'll try to add it in future versions.

NewPwnage said:
Dude thats awesome. Trying it now!
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Haha thanks, tell me if you run into any issues

Okay I updated the program to version 2.0.1. All the majors bugs are fixed (lol hopefully), and added a few options.

CDMA to GSM
can we use this for converting CDMA to GSM?
and if yes can comeone make a simple step by step guide?
thanks

Um wtf? I used this and now half my data on my Windows is gone. Wtf lol

invasion2 said:
Um wtf? I used this and now half my data on my Windows is gone. Wtf lol
Click to expand...
Click to collapse
Wow. How did that happen? What directory did you use as your workspace directory.

filmaker said:
Wow. How did that happen? What directory did you use as your workspace directory.
Click to expand...
Click to collapse
Not sure haha. But later that day my HD crashed, so I'm guessing your tool was not the cause of it. Thanks though. I restored and now I can use it
Sent from my HTC One S using Xparent Blue Tapatalk 2

Updated with Build Prop editor

Lol okay updated again, now you can zipalign all your system applications

Option to add GAPPS to ROM?

juan77_sonic said:
Option to add GAPPS to ROM?
Click to expand...
Click to collapse
Ha, never thought about that, I'll add it in the next update. Thanks.

[TOOL][NoobFriendly]EAIT:Easy Apk Image Themer

Today I am proud to present my new creation EAIT - EASY APK IMAGE THEMER.
DISCONTINUED
I don't use Windows anymore, so any support for this script/app is dropped.
Download from Mediafire or from ATTACHMENT.
I see sometimes peoples get very shocked after they see my modded versions of whatsapp, so I thought lets make something which helps to *any* normal android user to edit any apk.
Keep in mind that this is not much advance tool and won't be able to do all editing.
So what exactly is EAIT, it's a simple tool which extracts APK to let you edit images and then compress it back to .apk to install on your phone.
What you need?
JRE 6/7 -download it from java.com
Any good image editor like l Photoshop, GIMP or Paint.net
steps:
1. Download .rar from above.
2. Extract in C:/
3. Take backup of app(by ES explorer) you want to edit and move it to "PLACE-APK-HERE"
4. Run main application "easy apk image themer" from folder.
5. See your current apk will be listed on top.
6. Press 1 and enter to extract
7. Minimize the window and go to 'Project' folder. You'll find appname.apk folder, click on it.
8. Browse through "res" folder and see images inside drawable folders. Edit then with help of Photoshop/GIMP/Paint.NET.
Warning: rules of editing
>never edit "imagename".9.png files or you may get force close.
>If you want to replace image then choose something that has same resolution
9. After all editing maximize the window you previously minimized.
10. Press 2 and hit enter, wait for a while.
11. Press 3 and hit enter wait for a while.
12. You will find Signed-appname.apk in your "place-apk-here" folder
13. Send that app to your phone and install ( you may need to Un-install previous one)
14. Enjoy... and press thanks if you liked it
Report any bugs/problems here only.
Some images
{
"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"
}
the result:-

reserved

bump

Here is a Mediafire mirror for you
I've always wanted to make an inverted Facebook app, so I might give this a shot. Thank you for your work

I’m not trying to rain on OP’s parade, but out of curiosity, aren’t there similar tools for Windows already? Sometimes with even better GUIs like elesbb's GUI APK Tool

This looks like APK Multi Tool, minus all of the extra features. Even the folder structure is the same.

please help
i did everything as mentioned in ur tutorial. i colored some whatsapp smiles. and recompiled the apk and signed it. uninstalled my previous whatsapp and installed new one. but whenever i try to open a new contact to chat with it force closes. am attaching the edited apk. plz help me.
i didnt changed any resolution of images. just coloured them.
http://www.mediafire.com/download/ew7rgzz6qaa95uu/signed_whatsapp.apk

Interesting tool, would love it if i'd see screenshots and shared apks of modified apps! :good:

Great work.!!!
Hi Ankush,
You can use the Mediafire mirror.
http://www.mediafire.com/view/2zomqhmuoknb0gm/APK-Image-Themer_3.rar
BTW, amazing job now I can theme my apps...:good::good:

Downloaded
Ankush menat said:
Today I am proud to present my new creation EAIT - EASY APK IMAGE THEMER.
Download from dropbox
Please provide me mediafire mirror(mine account is not working properly)
I see sometimes peoples get very shocked after they see my modded versions of whatsapp, so I thought lets make something which helps to *any* normal android user to edit any apk.
So what exactly is EAIT, it's a simple tool which extracts APK to let you edit images and then compress it back to .apk to install on your phone.
What you need?
JRE 6/7 -download it from java.com
Any good image editor like l Photoshop, GIMP or Paint.net
steps:
1. Download .rar from above.
2. Extract in C:/
3. Take backup of app(by ES explorer) you want to edit and move it to "PLACE-APK-HERE"
4. Run main application "easy apk image themer" from folder.
5. See your current apk will be listed on top.
6. Press 1 and enter to extract
7. Minimize the window and go to 'Project' folder. You'll find appname.apk folder, click on it.
8. Browse through "res" folder and see images inside drawable folders. Edit then with help of Photoshop/GIMP/Paint.NET.
Warning: rules of editing
>never edit "imagename".9.png files or you may get force close.
>If you want to replace image then choose something that has same resolution
9. After all editing maximize the window you previously minimized.
10. Press 2 and hit enter, wait for a while.
11. Press 3 and hit enter wait for a while.
12. You will find Signed-appname.apk in your "place-apk-here" folder
13. Send that app to your phone and install ( you may need to Un-install previous one)
14. Enjoy... and press thanks if you liked it
Report any bugs/problems here only.
Some images
the result:-
Click to expand...
Click to collapse
Will try it soon cool tool will try to mod some apps
+1 Nice tool

himanshu.khanna said:
i did everything as mentioned in ur tutorial. i colored some whatsapp smiles. and recompiled the apk and signed it. uninstalled my previous whatsapp and installed new one. but whenever i try to open a new contact to chat with it force closes. am attaching the edited apk. plz help me.
i didnt changed any resolution of images. just coloured them.
http://www.mediafire.com/download/ew7rgzz6qaa95uu/signed_whatsapp.apk
Click to expand...
Click to collapse
You've edited one .9.png which is causing FC

So from what I am seeing, this allows you to easily edit images in apps. Does it however facilitate color changing? I'd like to theme facebook into the one team blackout has

asdfasdfvful said:
So from what I am seeing, this allows you to easily edit images in apps. Does it however facilitate color changing? I'd like to theme facebook into the one team blackout has
Click to expand...
Click to collapse
Facebook is mostly coded with HEX color codes and not Images...
You should use APKtool by brut.all
There are tons of guide available for How-to-theme-with-Apktool on XDA follow them.

Ankush menat said:
Facebook is mostly coded with HEX color codes and not Images...
You should use APKtool by brut.all
There are tons of guide available for How-to-theme-with-Apktool on XDA follow them.
Click to expand...
Click to collapse
Mhm... Apktool keeps on giving me issues. I guess I'll just love without theming
Sent from my One S using XDA Premium 4 mobile app

thanks but,
Ankush menat said:
You've edited one .9.png which is causing FC
Click to expand...
Click to collapse
how do i identify that which one is .9.png file? any suggestions?

himanshu.khanna said:
how do i identify that which one is .9.png file? any suggestions?
Click to expand...
Click to collapse
See the Image...
Those image files who have name like name.9.png will be visible as name.9 in Windows dont edit them

please help
Ankush menat said:
See the Image...
Those image files who have name like name.9.png will be visible as name.9 in Windows dont edit them
Click to expand...
Click to collapse
see i edited these files and they dont have .9.png in there name.View attachment 2479108

Sure, this is similar to some of the other apk editors out there like ApkTool/ApkMultiTool but this is NEWB friendly as the op expressed. I think this is a great program for someone just starting to learn about the android os and curious about themeing their own applications. Wish I had this tool when I first started themeing with apk multi tool. Without all the fluff and extra features, this software will be very helpful for users who are specifically interested in modifying the look of their applications. Good job Ankush

Anyone have any tips on editing Hangouts.apk? More specifically I would like to modify the emoji. Does framework-res.apk need to be included or something?

Sub'ed
OK so far so good, anyone know the name or where in the APK folder (which drawable folder) I could find the background images. I am working on the facebook messenger from my Sprint GS3.
Well I managed to edit the color of one of the pictures inside an app (ended up using the clock app) and now I cannot get it to install. I deleted the old clock and tried installing from es and also flashing from TWRP but could not find the file there (guess because it was not a .zip). Has to be in system/app folder.

OTA update could not verified

hi
i m in 14?4.A.0.108 second edition on z1 compact and root and cwm and xposed instaled
j ever do my update with ota but at this time after update my phone says " could not verified" and the new firmware 14.4.A.0.157 is not installed
my bootlooder is locked and j didnt understant what is the propleme !!!!!
can you please help
thank you

You need to go back to stock before the OTA will install.. That means no xposed and any apps that you've uninstalled that came with the ROM need to be installed again..
A factory reset could do it, but if you do that then you will lose all your user data.. So make backups of everything you want to save before you do that.
If that doesn't work then you'll have to completely reflash the stock ROM, then try to download the OTA.. But that would be senseless as you'd be saving yourself time and downloads by just flashing the updated stock ROM

did you deodexed your rom? i have xposed, SU, recovery installed, but got no problem update to 157 via OTA...

I had the same problem, just install the new update via PC companion, you won't loose any data. One thing you'll loose is root
Sent from my D5503 using XDA Free mobile app

My room is bot deodexed i understant nothing ????

Nobody know what is thé probleme with this update could not verified message.?

Hey i have the same problem! I just dont have high speed internett to figure out what it is. Or download ftf.

I have the same problem, some one with one solution, of any one knows if it worth it?
Sent from my D5503 using XDA Free mobile app

PC Companion is the Solution?
I recently had drama of a similar nature - used PC companion successfully as a workaround.

If is here someone, who still has this problem, look into /cache/recovery/fota/ and open "report" file. If you are not able to open this - it ends with error, just copy it into internal storage or SD Card.
First of all, you need to find a lines which looks 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"
}
The important part is rb_file_open[4]. If this line ends with "could not stat file" or someting like this, you need to download this zip https://drive.google.com/file/d/0B-79RLdvfasJMV9ZM2dfVEZtRnM/view?usp=sharing and copy/paste the missing file into your system. Don't forget to change permissions RW+R+R
If this won't help, you probably also have installed 4k mod and your "report" file looks exactly the same like the what I post above.
So, if yes, than download this zip https://mega.co.nz/#!QZYkGZZR!BL9dkTpPzPcClEz8our776jpXpia827mYEd5lCM3OvI and replace all files in your system with the files in this zip. Again, don't forget to change permissions RW+R+R and reboot your phone.
Now you should be able to update your phone with/over OTA. Thanks pcpepik from xperia.cz

Thanks play3man.
just by going through your post i was directed in the right way for resolve this issue. Though i did not follow the exact steps that you mentioned, but, the "rb_file_open[4]" really helped. Here is what i did:
1. Using ES File Explorer i navigated to /cache/recovery/fota/ and opened "report" file
2. Went all the way down (actually somewhere almost 3/4th down) and located the line rb_file_open[4]
3. This line actually said it is trying to open the Build.Prop file and mentions the size of that file in the end of that line.
4. I suddenly remembered that i had edited my Build.Prop file a few weeks back for some testing (ro.ril.enable.dtm=1) Like i said i was doing some testing. Though this setting does not work with my Mobile Service Provider (Airtel) here in India for 2G Networks. But I had kept the setting as it is and never bothered reverting it.
5. So what i did was, edited my build.prop file again and reverted that setting by deleting this line which i had added a few days back.
6. Rebooted my phone
7. Downloaded the OTA again, and tried installing it.
8. And it was a great success . LOL It Worked!!!!
So basically, this error, "Could not verify", could also simply mean that the System files are missing/corrupt or as simple as modified by the user and hence the verification could not complete. So people who have their Build.Prop file modified by one means or other (Manually, Scripted, or by Xposed) You may face this issue and may want to try this method and then make all those settings in build.prop file after installing the update. You could also temporarily revert the old build.prop file which you may have backed up somewhere before modifying it.
Hope this helps!!!

adarpatel said:
Thanks play3man.
just by going through your post i was directed in the right way for resolve this issue. Though i did not follow the exact steps that you mentioned, but, the "rb_file_open[4]" really helped. Here is what i did:
1. Using ES File Explorer i navigated to /cache/recovery/fota/ and opened "report" file
2. Went all the way down (actually somewhere almost 3/4th down) and located the line rb_file_open[4]
3. This line actually said it is trying to open the Build.Prop file and mentions the size of that file in the end of that line.
4. I suddenly remembered that i had edited my Build.Prop file a few weeks back for some testing (ro.ril.enable.dtm=1) Like i said i was doing some testing. Though this setting does not work with my Mobile Service Provider (Airtel) here in India for 2G Networks. But I had kept the setting as it is and never bothered reverting it.
5. So what i did was, edited my build.prop file again and reverted that setting by deleting this line which i had added a few days back.
6. Rebooted my phone
7. Downloaded the OTA again, and tried installing it.
8. And it was a great success . LOL It Worked!!!!
So basically, this error, "Could not verify", could also simply mean that the System files are missing/corrupt or as simple as modified by the user and hence the verification could not complete. So people who have their Build.Prop file modified by one means or other (Manually, Scripted, or by Xposed) You may face this issue and may want to try this method and then make all those settings in build.prop file after installing the update. You could also temporarily revert the old build.prop file which you may have backed up somewhere before modifying it.
Hope this helps!!!
Click to expand...
Click to collapse
Yes, if you have done some more changes in your system, you may have different "error"

play3man said:
If is here someone, who still has this problem, look into /cache/recovery/fota/ and open "report" file. If you are not able to open this - it ends with error, just copy it into internal storage or SD Card.
First of all, you need to find a lines which looks like this:
The important part is rb_file_open[4]. If this line ends with "could not stat file" or someting like this, you need to download this zip https://drive.google.com/file/d/0B-79RLdvfasJMV9ZM2dfVEZtRnM/view?usp=sharing and copy/paste the missing file into your system. Don't forget to change permissions RW+R+R
If this won't help, you probably also have installed 4k mod and your "report" file looks exactly the same like the what I post above.
So, if yes, than download this zip https://mega.co.nz/#!QZYkGZZR!BL9dkTpPzPcClEz8our776jpXpia827mYEd5lCM3OvI and replace all files in your system with the files in this zip. Again, don't forget to change permissions RW+R+R and reboot your phone.
Now you should be able to update your phone with/over OTA. Thanks pcpepik from xperia.cz
Click to expand...
Click to collapse
Thank you for your help
I didnt find this .....rb_file_open[4] in the report file
I have just rb_file_open[0] and [1]
Im rooted locked bootloader deoxd cwm
I have 4k and timeshift video
Sorry for my bad english

BASHARAWAD said:
Thank you for your help
I didnt find this .....rb_file_open[4] in the report file
I have just rb_file_open[0] and [1]
Im rooted locked bootloader deoxd cwm
I have 4k and timeshift video
Sorry for my bad english
Click to expand...
Click to collapse
The second line ([1]) ends with could not state file? If yes, continue from that line with steps from my original post
You have deodexed rom, so the phone is probably missing way more original files, so that's why it ends already on second line

For me OTA updater complains about
rb_file_open[4]: //system/priv-app/psmselfupdater.odex
and apk, but the system dump you provided doesn't have it.

kentaurest said:
For me OTA updater complains about
rb_file_open[4]: //system/priv-app/psmselfupdater.odex
and apk, but the system dump you provided doesn't have it.
Click to expand...
Click to collapse
I have the same error on a stock Z1C, only rooted. I think if we could get the file from somewhere we could drop it on and the OTA would complete, and we'd probably keep root ?

Thank you for the /cache/recovery/fota/report trick. It seems my phone was missing /system/app/SonyEntrance.odex and .apk - I am not sure how this happened or what those files are for.
Edit: Seems it's because I removed 'What's New' :cyclops: