Friends can u tell me how to check whether the apk is protected or not? Any gui tool or method there?Bcoz some successfully compiled apk using apktool get auto closed due to this issue i guess.. please help friends..Thanks.
Note:I Decompiled this below app successfully but compiled app close automatically on opening or launching in phone.
App Download Link
YouCut Video Editor _ Video Maker MOD v1.430.1114.apk
Zippyshare.com - Free File Hosting
www47.zippyshare.com
Krishcena said:
Friends can u tell me how to check whether the apk is protected or not? Any gui tool or method there?Bcoz some successfully compiled apk using apktool get auto closed due to this issue i guess.. please help friends..Thanks.
Note:I Decompiled this below app successfully but compiled app close automatically on opening or launching in phone.
App Download Link
YouCut Video Editor _ Video Maker MOD v1.430.1114.apk
Zippyshare.com - Free File Hosting
www47.zippyshare.com
Click to expand...
Click to collapse
Did you sign it afterwards? What did you modified inside this apk ?
Bro i just removed arm 64 lib folder from lib folder that's it, i even tried without any modifications just decompiled and compiled again but again app auto closed in phone bro.help bro please.
Note:i signed the app after compiled bro with both original signature and aapt2 signature in each try attempts.You check that app and help me bro please.thanks.
Krishcena said:
Bro i just removed arm 64 lib folder from lib folder that's it, i even tried without any modifications just decompiled and compiled again but again app auto closed in phone bro.help bro please.
Note:i signed the app after compiled bro with both original signature and aapt2 signature in each try attempts.You check that app and help me bro please.thanks.
Click to expand...
Click to collapse
Looks your APK should only make use of 32-bit native libraries, is meant to be run on devices with a CPU architecture of armeabi, armeabi-v7a and x86 , because you removed the 64-bit libraries drom APK's lib folder.
FYI:
When you install an APK on Android, the system looks for native library directories (armeabi, armeabi-v7a, arm64-v8a, x86, x86_64, mips64, mips) within the lib folder of the APK, in the order specified by Build.SUPPORTED_ABIS.
If your app happens to have an arm64-v8a directory with missing libs, the missing libs will not be installed from another directory, the libs will not be mixed. This means that you must provide the full set of your libraries for each architecture.
If not the app crashes.
jwoegerbauer said:
Looks your APK should only make use of 32-bit native libraries, is meant to be run on devices with a CPU architecture of armeabi, armeabi-v7a and x86 , because you removed the 64-bit libraries drom APK's lib folder.
FYI:
When you install an APK on Android, the system looks for native library directories (armeabi, armeabi-v7a, arm64-v8a, x86, x86_64, mips64, mips) within the lib folder of the APK, in the order specified by Build.SUPPORTED_ABIS.
If your app happens to have an arm64-v8a directory with missing libs, the missing libs will not be installed from another directory, the libs will not be mixed. This means that you must provide the full set of your libraries for each architecture.
If not the app crashes.
Click to expand...
Click to collapse
Bro i even tried without any modifications i mean i just decompiled the app and again compiled the app and sign it too,but this untouched compiled apk too auto closing on launching in phone bro.Please Check that app and help bro please
Krishcena said:
Bro i even tried without any modifications i mean i just decompiled the app and again compiled the app and sign it too,but this untouched compiled apk too auto closing on launching in phone bro.Please Check that app and help bro please
Click to expand...
Click to collapse
To get the very reason why an app crashes typically people do a LOGCAT.
jwoegerbauer said:
To get the very reason why an app crashes typically people do a LOGCAT.
Click to expand...
Click to collapse
App auto closing. Bro in phone.where can i get logcat from phone bro?
Just can't believe it.
Look inside here:
[Tutorial] How To Logcat
Here's how to use logcat: There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app: Here are two good examples are either: aLogcat or Catlog I prefer...
forum.xda-developers.com
Related
Hello Guys and Galls,
I want to change the background of Settings.apk from black to white. I use the FroyoMod Rom http://forum.xda-developers.com/showthread.php?t=815595.
If change
Code:
<application android:label="@string/settings_label" android:icon="@drawable/ic_launcher_settings" android:taskAffinity="">
to
Code:
<application android:theme=[COLOR="Red"]"@android:style/Theme.Light.NoTitleBar"[/COLOR] android:label="@string/settings_label" android:icon="@drawable/ic_launcher_settings" android:taskAffinity="">
in AndroidManifest.xml.
I use ApkManger to decompile and compile. The (de)compiling is without any errors.
After compile with ApkManager i do the follow:
- open original Settings.apk and unsignedSettings.apk with 7-zip
- delete AndrodManifest.xml in original Settings.apk
- copy AndroidManifest.xml from unsignedSettings.apk to original Settings.apk
- copy the modified original Settings.apk to the phone in /system/app
- chmod 644 Settings.apk
- chown root:root Settings.apk
So now if I start Settings nothing happens, nothing, not even an fc.
This is was logcat says:
Code:
com.android.settings has no certificates at entry AndroidManifest.xml
What I´m doing wrong?
Try one of the many apk re-packaging tools on this forum. Ive used apktool but there are some front ends built for it
From something awesome
killersnowman said:
Try one of the many apk re-packaging tools on this forum.
Click to expand...
Click to collapse
tigger-gg said:
I use ApkManger to decompile and compile.
Click to expand...
Click to collapse
By the way if I change any other xml file in /res there are no such problems.
tigger-gg said:
I use ApkManger to decompile and compile.
Click to expand...
Click to collapse
dur
i read this on the mobile and did not see that....
solving the problem? because I would be interested
Me too, I'm having a problem recompiling an AndroidManifest.xml with apkmanager 5.0.1., it won't install unless I use an original AndroidManifest.xml file first, then I can flash right over it. At first I thought it was a the change I made in the file, but I just decompiled and compiled an unmodified version, and it did the same thing. So its the compiler.
Settings.apk is a signed system app. It will refuse to run unless signed by the same key as the rest of the system apps. Just replacing a single XML in the APK will cause a signature mismatch.
Best bet? I'd say make your change, then use a kitchen like dsixda's to resign the whole system with the test key (I think this is a menu option).
Yep your whole system has to have the same signature. I did this edit for a rom a while back, but I made the settings transparent instead of white background by using Theme.Wallpaper.NoTitlebar. Just sign your whole rom together with testkeys and all should be good until another system app gets changed/modified and the signatures don't match again.
Sent from my PG06100 using Tapatalk
Thanks to Gene Poole and one_love_420, I will try your instructions.
If your after quickly signing a whole load of apk's, I wrote a command line front end to do all the hard work for you.
You can even generate your own private key.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
BUMP to top
Please big problem been fighting for weeks
any one know anything about this!!
So anybody find a solution yet? Seems to be the binary text conversion.
It is the signitures in manifest.inf fyi
1.How to remove and add apps before build from CM source,and when it's done,the zip files have everything just what i want.
2.How to add Google apps before build form CM source,so i can have a zip include all google apps.
And ofcause not rebuild the zip.
I add and remove apk on system/app before package the rom.
ripclawrings said:
I add and remove apk on system/app before package the rom.
Click to expand...
Click to collapse
Do you mean dsixda's kichen?
There is no folder system/app in the CM source project.
When you are working with source, its not called system/app
all apps that are going to be baked into the ROM will be in the folder /packages/apps.
So here are the basic steps:
1.Place your app source code in /packages/apps (just drop the source folder in)
2.Create 'Android.mk' file for the app (if the app was made in eclipse, its likely to have res/R.java which is autogenerated by eclipse. This needs to be removed as the system will not recognize it.)
3.Edit /build/target/product/core.mk (or similar) and add your application in the list of PRODUCT_PACKAGES. (if you dont add it to the main make files, the app wont be compiled and it wont be in the update.zip when it is finished.
4.Run make.
IF you feel this is too complicated. create the update.zip and use dsixda's kitchen to edit the zip, add the apk manually and then resign it.
Hope this helps!
demoneyes905 said:
When you are working with source, its not called system/app
all apps that are going to be baked into the ROM will be in the folder /packages/apps.
So here are the basic steps:
1.Place your app source code in /packages/apps (just drop the source folder in)
2.Create 'Android.mk' file for the app (if the app was made in eclipse, its likely to have res/R.java which is autogenerated by eclipse. This needs to be removed as the system will not recognize it.)
3.Edit /build/target/product/core.mk (or similar) and add your application in the list of PRODUCT_PACKAGES. (if you dont add it to the main make files, the app wont be compiled and it wont be in the update.zip when it is finished.
4.Run make.
Click to expand...
Click to collapse
Thanks for the reply. However, could you elaborate on PRODUCT_PACKAGES. Where is it? And what is it?
I wanted to disable the Flash to black/screen update function on my yotaphone 2 e-ink's screen as it really disturbes me. I worked out there was a setting to do this in the phones SDK app.
I decompiled the YD_YotaphoneSDK.apk app and changed some of the settings in the classes.dex files so as to disable the full screen refresh (i.e change the backscreenmanager waveform mode to A2). I then recompiled the YD_YotaphoneSDK.apk app however when I attempt to install it on my YotaPhone it states 'Parse Error- There was a problem while parsing the package'.
Im pretty sure it needs to be resigned but cannot workout how, when i attempt to do so in android studio i get the following error: Error:Android Source Generator: [YD_YotaphoneSDK] Package is not specified in AndroidManifest.xml
Can anybody with some relevant experience give my some suggestions of how I can resign or enable this recompiled version of the APK to be installed on my yotaphone.
I have attached the edited apk file
Regards
I have the ARChon runtime installed as an extension in Chrome and compiled the APK with Twerk. However, when I go to the resulting folder, I see no executable files. Am I missing something?
Thank you.
So this is my first time publishing an Android app. Now I successfully convert my aab into apks and then unzip it into many smaller apk. However, now I am confused about which one should I send to my beta tester? There is so many different apk like
standalone-arm64_v8a_hdpi.apk
standalone-arm64_v8a_mdpi.apk
standalone-arm64_v8a_xxxhdpi.apk
standalone-armeabi_v7a_mdpi.apk
and many more. I am guessing we need to match the apk for the specific device? However, if I want to upload my apk into a website and the user can download the apk directly from the website in the future. which apk should I upload then? Since it's impossible to determine the device info beforehand? Hope my question make sense. Thanks
Jimbotron126 said:
So this is my first time publishing an Android app. Now I successfully convert my aab into apks and then unzip it into many smaller apk. However, now I am confused about which one should I send to my beta tester? There is so many
...
upload then? Since it's impossible to determine the device info beforehand? Hope my question make sense. Thanks
Click to expand...
Click to collapse
Those version of your apk are for users running different chipset and different screen dpi. Those apks are uplaoded to google play, and when someone downloads the app, it's the right apk for them that gets installed right away (they don't have to choose).
From my experience, screen dpi isn't a problem when installing, the only problem you could face is when installing arm64_v8a on an armeabi_v7a device (installing 64bit app on a 32bit device). 32bit devices tend to be rarer and rarer so if you had to post your app for testing it would be any of the arm64 apk + any of the armeabi_v7a apk.
Because probably an Android user neither knows about the meaning of the DPI-bucket-shorthands ( MDPI, HDPI, XHDPI, XXHDPI, XXXHDPI) or ABI-shorthands, IMO it's recommended to offer in your web-site to your users a Powershell script to download what either by means of ADB gets Android device's DPI-bucket-setting & ABIs supported and then automatically selects the proper APK to get downloaded or provides a simple menu where users can select the matching APK related to their phone's ABI and/or DPI to get downloaded.
Read more here:
Use PowerShell to download a file with HTTP, HTTPS, and FTP
In PowerShell, you can download a file via HTTP, HTTPS, and FTP with the Invoke-WebRequest cmdlet
4sysops.com
Example Powershell menu skeleton:
Code:
do
{
Show-Main-Menu
$selection = Read-Host "Please make a selection"
switch ($selection)
{
'1' {
Show-DPI-Menu
} '2' {
Show-ABI-Menu
}
}
pause
}
until ($selection -eq 'q')