Is there any way to remove the process that checks for root in an app? If decompiling an apk where would this be?
f10a said:
Is there any way to remove the process that checks for root in an app? If decompiling an apk where would this be?
Click to expand...
Click to collapse
You can't make a rooted app to an unrooted app!
I think it's pretty obvious that he means he wants to install an app which doesn't need root, but which checks for root and refuses to run if it finds the device has been rooted.
Very good question imo.
at45 said:
I think it's pretty obvious that he means he wants to install an app which doesn't need root, but which checks for root and refuses to run if it finds the device has been rooted.
Very good question imo.
Click to expand...
Click to collapse
That is exactly it.
Well, in that case, if you can get access to the source code, and if you know about developing, then you could do it (otherwise decompiling, editing some file and compiling again won't help you).
f10a said:
Is there any way to remove the process that checks for root in an app? If decompiling an apk where would this be?
Click to expand...
Click to collapse
goto your supersu app and check option to grant su permission without prompt.
if you are trying to change rooted app to unrooted its not possible. the root permissions are necessary for the app to work.
You could try the apps listed here:
http://www.howtogeek.com/115888/how-to-restrict-android-app-permissions/
Let me know how it goes.
No what he is trying to say is Example, I have DirecTV GenieGo APK and the latest version checks to see if your device is rooted and if it is then GenieGo will shut down and say something along the lines of "Contact your Service Provider to get a non-rooted version of your device"...I think what the user was asking is...Is there a way to remove that "check to see if my device is rooted" or at the very least fool the apk into thinking it ISNT rooted....?
Related
I'm sorry if this was posted somewhere else, but I searched and nothing came up. When you root your phone does that mean you no longer can receive over the air updates? Or is that only if you have custom ROM's installed? That being said, is the ROM that you install to gain root access considered a custom ROM? Sorry... I feel like a n00b but I had to ask. :] Thanks
Trevlo said:
I'm sorry if this was posted somewhere else, but I searched and nothing came up. When you root your phone does that mean you no longer can receive over the air updates? Or is that only if you have custom ROM's installed? That being said, is the ROM that you install to gain root access considered a custom ROM? Sorry... I feel like a n00b but I had to ask. :] Thanks
Click to expand...
Click to collapse
Originally Posted by WormDoes
http://androidforums.com/thunderbolt-all-things-root/306774-simple-newbie-questions.html
"If you're rooted and you've deleted any bloatware and you try and install the ota update it will not update successfully. You can unroot and update, but be warned a lot of the time an ota update will also correct the current exploits that were used to achieve root access. If you are rooted it's usually a good idea and easier to flash a ROM that includes the update already. The developers get a hold of the source codes a few weeks before VZW actually pushes it to your phone and you don't have to wait for jcase, unrevoked, or whomever to find a new way to root if the ota breaks root access.
Hope this helps"
I was searching the same thing earlier bro and this is the answer I found.
Does this mean if I don't delete bloatware and just freeze it, then I can still get the updates? I read that article and I didn't see them answer whether or not getting an OTA update would take root off. Thanks for the response!
Sent from my ADR6400L using XDA Premium App
Trevlo said:
Does this mean if I don't delete bloatware and just freeze it, then I can still get the updates? I read that article and I didn't see them answer whether or not getting an OTA update would take root off. Thanks for the response!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
No the point is if you root, have SU, and/or a custom recovery, the update will fail.
Sent from my ADR6400L using XDA Premium App
Good deal. Thank you for the info.
Sent from my ADR6400L using XDA Premium App
So if I'm reading this correctly, a corollary is that if you intend to root but haven't, its likely a good idea to do it before the OTA is pushed, or else you'll have to wait for the developers to figure out how to root the new one?
Sent from my ADR6400L using XDA App
More then likely any important updates/fixes/etc will turn up in ROMs anyways.
so how do you disable updates?
Nikolai2.1 said:
No the point is if you root, have SU, and/or a custom recovery, the update will fail.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
so how do you disable updates I have a galaxy s2 4g service sprint I ve been searching around how to disable updates I keep getting prompt for one and it wont install root blocking it from installing I guess I just want to turn it of I read use bloat ware or titanum backup tried both same issue. I thought this would be an easy fix.
arcolino1 said:
so how do you disable updates I have a galaxy s2 4g service sprint I ve been searching around how to disable updates I keep getting prompt for one and it wont install root blocking it from installing I guess I just want to turn it of I read use bloat ware or titanum backup tried both same issue. I thought this would be an easy fix.
Click to expand...
Click to collapse
try this it works
only difference for you will be lines 4 and 5
look for your current ro.build.fingerprint and change it to the current update...
oh and also don't forget to delete the update from your cache
If you are comfortable editing the build.prop then follow these directions.
Directions:
1. Use root explorer and navigate to /system
2. Mount as r/w
3. Long press on build.prop then click on Open With then Text Editor
4. Find the line ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP1:user/release-keys
5. Change FP1 or FP5 in that line to FP8
6. Press the menu button on the phone and click on Save and Exit
7. Mount back to r/o
8. Reboot phone
cujo6801 said:
try this it works
only difference for you will be lines 4 and 5
look for your current ro.build.fingerprint and change it to the current update...
oh and also don't forget to delete the update from your cache
If you are comfortable editing the build.prop then follow these directions.
Directions:
1. Use root explorer and navigate to /system
2. Mount as r/w
3. Long press on build.prop then click on Open With then Text Editor
4. Find the line ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP1:user/release-keys
5. Change FP1 or FP5 in that line to FP8
6. Press the menu button on the phone and click on Save and Exit
7. Mount back to r/o
8. Reboot phone
Click to expand...
Click to collapse
I attached the file for more info.
mine reads:
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FI27:user/release-keys
do I change the FI to something else? if so this change will not brick my phone? this is my only cell connection to outside world.
the download system update that wants to install is a FL24 is it because the phone knows FI the FL will not install?
You could just rename otacerts to otacerts.bak and then rename updater.apk to updater.bak.
Sent from my personally built from source CM10.1 N7.
arcolino1 said:
I attached the file for more info.
mine reads:
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.0.4/IMM76I/FI27:user/release-keys
do I change the FI to something else? if so this change will not brick my phone? this is my only cell connection to outside world.
the download system update that wants to install is a FL24 is it because the phone knows FI the FL will not install?
Click to expand...
Click to collapse
Yes change the FI27 to FL24
Should do it for you..
Disclaimer.. I don't know your phone but this has worked for me and many others on the Samsung charge...
I don't think it will brick your phone..
Make sure you have a backup .
SENT FROM THE DOG POUND
cujo6801 said:
Yes change the FI27 to FL24
Should do it for you..
Disclaimer.. I don't know your phone but this has worked for me and many others on the Samsung charge...
I don't think it will brick your phone..
Make sure you have a backup .
SENT FROM THE DOG POUND
Click to expand...
Click to collapse
what additional info do you need from my phone, that will make this a more sure ok to do for sure no worries ? what about
what disconnecktie recommended "You could just rename otacerts to otacerts.bak and then rename updater.apk to updater.bak"
is that safer, not sure where to find those files? I am doing titanium back. but i do not want to go through the hassel of reloading everything back on the phone.
Either way will work but the otacerts and updater both just catch ota information when it is sent out. You aren't deleting anything so it is impossible to brick from it. The otacerts is in /system/etc and the updater apk is in /system/app or course. Use a root file explorer like es file explorer and mount system as read/write.
Sent from my personally built from source CM10.1 N7.
disconnecktie said:
Either way will work but the otacerts and updater both just catch ota information when it is sent out. You aren't deleting anything so it is impossible to brick from it. The otacerts is in /system/etc and the updater apk is in /system/app or course. Use a root file explorer like es file explorer and mount system as read/write.
Sent from my personally built from source CM10.1 N7.
Click to expand...
Click to collapse
so do I wait to see the update icon? then do the process
and to be clear the process is?
go to /system/etc then rename otacerts to otacerts.bak save it
then go to /system/app then rename update.apk to update.bak save it
how long does that change last if they are pushing the update wont it just come right back?
arcolino1 said:
so do I wait to see the update icon? then do the process
and to be clear the process is?
go to /system/etc then rename otacerts to otacerts.bak save it
then go to /system/app then rename update.apk to update.bak save it
how long does that change last if they are pushing the update wont it just come right back?
Click to expand...
Click to collapse
They won't be able to push it anymore after that. Change it then reboot and they can't send then to you anymore.
Sent from my personally built from source CM10.1 N7.
What he said...
SENT FROM THE DOG POUND
disconnecktie said:
They won't be able to push it anymore after that. Change it then reboot and they can't send then to you anymore.
Sent from my personally built from source CM10.1 N7.
Click to expand...
Click to collapse
ok, so to be clear I do not see the files now in those locations
otacerts and updater.apk
will I see them after the update icon comes back?
arcolino1 said:
ok, so to be clear I do not see the files now in those locations
otacerts and updater.apk
will I see them after the update icon comes back?
Click to expand...
Click to collapse
Are you using a thunderbolt? If you're not then you're in the wrong forum and should probably post your questions there.
Sent from my personally built from source CM10.1 N7.
he has a GS2....
but mine should work....
take the info to your phone section here on XDA and ask what they think...
good luck
This is my personal rom for the htc evo view.
It's still a wip but for the most part everything is about the way I want it. Once I'm done with all the edits to the system I will basically repack everything into a full rom and reflash it after wiping the partitions.
** Note: The lag is from the screecast and not the rom. My rom actually runs smoother than the video. **
** Pay attention as I purposely showed the app drawer with no superuser.apk and still have root access. I prefer rooting my roms this way. **
It's a video so click the image
But you have included the superuser.apk in the rom? Or do you jsut have the su binary?
I don't use superuser.apk at all, just the su binary and busybox along with some other files/scripts that I personally use.
So every App can easily get superuser permissions on your rom on you don't even notice? That's a very high risk.
Have a look at this article: http://androidsu.com/2011/06/a-word-about-superuser-and-security/
nickiberli said:
So every App can easily get superuser permissions on your rom on you don't even notice? That's a very high risk.
Have a look at this article: http://androidsu.com/2011/06/a-word-about-superuser-and-security/
Click to expand...
Click to collapse
I use an access list. That's the beauty of compiling some of these binaries from source...You can change the way they function and then use it. Only the su binary (and me) knows where the list is and can access it. I have been able to block terminal and titanium backup independently without blocking other apps. I choose to do my personal rom this way just to eliminate the need for apps that do what I can do through scripts or terminal.
But if an app wants su permissions, does a popup appear?
nickiberli said:
But if an app wants su permissions, does a popup appear?
Click to expand...
Click to collapse
Nope. The way my binary works is if an app requests root permission and is not on the list it is blocked outright. I personally get annoyed with the toast message about "this app has been granted su permission". I have to manually add all apps to my list that need root. This gives me extra work but it also ensures that I personally added an app to the list. I have had an instance where someone played with my phone and added a root app, granted permissions through superuser.apk, and then edited my system and jacked it up. After that I made a su binary for my use and since then no one has been able to give root access except me.
But this way you can't install new root apps..?
I can install any root app I want. I just have to manually (via terminal command or script) add the app name to the access list in order for it to gain root.
But a user who uses your rom can't?
nickiberli said:
But a user who uses your rom can't?
Click to expand...
Click to collapse
Well, I did title this thread as "show my rom". I said this was my personal rom but never stated I would release it. The point of my thread was to showcase some of the edits I have done visually and the little tidbit about how my su binary works.
It doesn't seem feasable for me to release this or any rom right now since the view owner numbers doesn't appear to be that great. The dev section also doesn't get as much traffic as it could be.
I just wanted to show what can be done with the right tools, knowledge, and effort as far as roms are concerned.
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
johnwaynegacy said:
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
Click to expand...
Click to collapse
probably delete the OTA apk files in /system/app
con247 said:
probably delete the OTA apk files in /system/app
Click to expand...
Click to collapse
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
johnwaynegacy said:
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
Click to expand...
Click to collapse
I deleted those from my /system/app directory. The previous OTA did not ever come through my phone, so I think you'll be OK.
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
Good call!
instructions, pls?
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
i just did this on rezrom, thanks!
why is this file included with a custom rom?
michaelbsheldon said:
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
Click to expand...
Click to collapse
If for what ever reason you cant use root explorer and do have busybox (i think you need it) installed
It has been a really long time since I have used adb for anything, but this should work unless it denies you because system is mounted as read only.
adb shell
su
rm /filepath/file.apk
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
FabianaS said:
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
Click to expand...
Click to collapse
If you are stock unrooted, the best you can do is to say no if it asks. If for some reason it is a forced OTA, I don't think you can without staying in airplane mode.
Via Rezound using XDA Premium
Thanks, that is what I was wondering, if it asks or if it's forced? I don't remember how my past updates have been and for some reason I feel like they were forced!?!
Hi guys!
Could someone upload the original SamsungCamera.apk, please? Because when I'm tried to install HX Camera mod, i put the two files into a zip, when the Root Browser crashed. The two files were gone, and the zip became corrupt. After this, i put the mod to system\app. On the first run, it worked, but after a while it crashed. I run the camera again and it crashed after a time, again, and again. So I decided to try the video. And now it doesn't even want to start. So that's why i request the stock camera, and please upload as soon as possible. Thanks.
File download camera stocks galaxy s3 : http://205.196.122.34/ejrcy4z4l9wg/d45a3iccd6hok6t/Camera.apk
devid801 said:
File download camera stocks galaxy s3 :
Click to expand...
Click to collapse
So, I downloaded this app and I've moved it to /system/app folder and I've tried to install it and it simply says "not installed". I've been searching the net for days now. I've done the following.
1. Root access for Apps and ADB
2. I deleted the CN 9 mod camera app in the /system/app folder (Is there something else that I need to delete?)
3. Installed Busy Box, Astro, ES File Explorer and Easy Installer
4. I successfully installed other stock apps such as S Voice.
I've found similar questions on the net, but no answer. Please help me out!
Set permissions to read write execute / read /read usint root explorer.
Reboot in recovery , wipe cache and dalvik.
Reboot.
That should do the trick
Monteillard said:
Set permissions to read write execute / read /read usint root explorer.
Reboot in recovery , wipe cache and dalvik.
Reboot.
That should do the trick
Click to expand...
Click to collapse
Thanks but no dice. I narrowed it down to few possible reasons, all of which I would need help with.
1. Even though, my options say that I'm rooted for "Apps and ADB", I don't think I'm "Fully rooted" as Android Commander still says "no root".
2. I don't have the right drivers. I was told that the "service drivers" are different than the normal USB drivers I get when I plug in my phone and maybe that's why Android Commander might not fully recognize my phone.
3. Permissions. I keep reading about read/write permissions, but maybe the options that I'm looking at is not the same "R/W" in question. I don't know.
4. Everything is correct and I just don't know what I'm doing
So, I realized that the app is a "read only" apk and it wont let me change it's permission in Root Explorer. Is there a way that I can change it? Or does anyone have another SG3 camera apk?
So, after extensive research, it has been reported that particular app doesn't work on custom roms.
Almalieque said:
So, I realized that the app is a "read only" apk and it wont let me change it's permission in Root Explorer. Is there a way that I can change it? Or does anyone have another SG3 camera apk?
Click to expand...
Click to collapse
U can change it actually in root explorer. At the top right there's R/O, click it so it'll be R/W.. from there u can change its permission. I know this is pretty obvious, but this may help u out. cheers!
Sent from my GT-I9300 using xda premium
Hi,
I modified "SamsungCamera2" from my Note 3 and would like to install it now on my Note 3. My phone is not rooted and doing so would currently trip the knox counter (I don´t want that).
If I try to install the apk I get the message "application not installed".
Is it somehow possible to convert the apk so that I can install it as a "normal app"?
Best wishes,
Klaus
oclock said:
Hi,
I modified "SamsungCamera2" from my Note 3 and would like to install it now on my Note 3. My phone is not rooted and doing so would currently trip the knox counter (I don´t want that).
If I try to install the apk I get the message "application not installed".
Is it somehow possible to convert the apk so that I can install it as a "normal app"?
Best wishes,
Klaus
Click to expand...
Click to collapse
no root no party, however i think that its possible to root the phone over knox without count
to install system apk you can do in 3 ways
1.install normally by a file manager as normal apk but in this way you can only install ORIGINAL APK like official update NO MOD
2.copying the apk and maybe the odex in /system/app NEED ROOT
3.using clockworkmod NEED ROOT,or maybe using the stock samsung recovery need a flashable zip of your app
enjoy
AXD96 said:
no root no party, however i think that its possible to root the phone over knox without count
to install system apk you can do in 3 ways
1.install normally by a file manager as normal apk but in this way you can only install ORIGINAL APK like official update NO MOD
2.copying the apk and maybe the odex in /system/app NEED ROOT
3.using clockworkmod NEED ROOT,or maybe using the stock samsung recovery need a flashable zip of your app
enjoy
Click to expand...
Click to collapse
Thank you for your answer.
With my current firmware there is no known method to get root without knox=0x1.
If I develop my own app I can install it without problems. So, what exactly makes apps from system/app different?
How does Android know that I did not implement this App by myself?
Is there a way to further modify the app so that it looks like I implemented it by myself and install it then?
oclock said:
Thank you for your answer.
But if I develop my own app I can install it without problems.
So, what exactly makes apps from system/app different?
How does Android know that I did not implement this App by myself?
Is there a way to further modify the app so that it looks like I implemented it by myself and install it then?
Click to expand...
Click to collapse
Android expects applications installed by opening the APK to be signed.
It's quite easy to sign them with a generic certificate: but when apps are updated both the old (in /system) and the new version must be signed with the same one.
(Extreme problems lead to extreme solutions: if you need Samsung service, flash a bad bootloader so that's permanently bricked and doesn't even get to Odin...)
Ryccardo said:
Android expects applications installed by opening the APK to be signed.
It's quite easy to sign them with a generic certificate: but when apps are updated both the old (in /system) and the new version must be signed with the same one.
Click to expand...
Click to collapse
Thank you for the explanation and thank you for the hint
But how does Android know that I am trying to Update an already existing app? Is it just because of the class names of the MainActivity? Is it possible to refactor the app, so that it looks like a brand new app?
oclock said:
Thank you for the explanation and thank you for the hint
But how does Android know that I am trying to Update an already existing app? Is it just because of the class names of the MainActivity? Is it possible to refactor the app, so that it looks like a brand new app?
Click to expand...
Click to collapse
I believe, but have never tried, that it goes by the package ID
Ryccardo said:
I believe, but have never tried, that it goes by the package ID
Click to expand...
Click to collapse
It seems to be the correct way. However, something seems to be odd:
I the log I get the following:
12-29 23:47:03.981: E/AndroidRuntime(27444): java.lang.RuntimeException: Unable to resume activity {com.sec.android.app.cameraoc/com.sec.android.app.camera.Camera}: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
However, this permission is set in the AndroidManifest.xml file:
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.sec.android.app.cameraoc">
<uses-permission android:name="android.permission.CAMERA"/>
[...]
<uses-permission android:name="android.permission.SET_ANIMATION_SCALE"/>
[...]
Do you have any ideas why this permission isn´t recognized?
oclock said:
Thank you for your answer.
With my current firmware there is no known method to get root without knox=0x1.
If I develop my own app I can install it without problems. So, what exactly makes apps from system/app different?
How does Android know that I did not implement this App by myself?
Is there a way to further modify the app so that it looks like I implemented it by myself and install it then?
Click to expand...
Click to collapse
dont said me thanks, just click the thanks button on the left of message
no you can't
every APK has got a signature when you modify an apk or the mali code the signature became invalid so you cant install that apk anymore until you sign again the apk
if the signature is different you cant install system apk when you has already installed an app with the same packace address
else if the signature is the same (only the author of the app has got the original key of signature) you can install it
there is a critical bug in android until 4.2.2 version, the MASTERKEY BUG
google fix it in android 4.3
i got root with this bug using cydia impactor
with this bug/exploit you was able to modify system partition bypassing signature protection and then get root so you was able to have full access to your phone
---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------
oclock said:
It seems to be the correct way. However, something seems to be odd:
I the log I get the following:
12-29 23:47:03.981: E/AndroidRuntime(27444): java.lang.RuntimeException: Unable to resume activity {com.sec.android.app.cameraoc/com.sec.android.app.camera.Camera}: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
However, this permission is set in the AndroidManifest.xml file:
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.sec.android.app.cameraoc">
<uses-permission android:name="android.permission.CAMERA"/>
[...]
<uses-permission android:name="android.permission.SET_ANIMATION_SCALE"/>
[...]
Click to expand...
Click to collapse
where did you find the log?
AXD96 said:
dont said me thanks, just click the thanks button on the left of message
no you can't
every APK has got a signature when you modify an apk or the mali code the signature became invalid so you cant install that apk anymore until you sign again the apk
if the signature is different you cant install system apk when you has already installed an app with the same packace address
else if the signature is the same (only the author of the app has got the original key of signature) you can install it
Click to expand...
Click to collapse
OK. This was already made clear some posts above. My new question was: Can I change the signature to install it as a "new" app.
I tried it out by myself. I modified the manifest file to change the android package name from "com.sec.android.app.camera" to "com.sec.android.app.cameraoc". The java package is unchanged.
With this modification i could install the app without any problems, but I get a permission exception, when I try to execute the App:
12-29 23:47:03.981: E/AndroidRuntime(27444): java.lang.RuntimeException: Unable to resume activity {com.sec.android.app.cameraoc/com.sec.android.app.camera.Camera}: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
However, this permission is set in the AndroidManifest.xml file:
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.sec.android.app.cameraoc">
<uses-permission android:name="android.permission.CAMERA"/>
[...]
<uses-permission android:name="android.permission.SET_ANIMATION_SCA LE"/>
[...]
So, i do not understand why I get this Exception. Do you have any ideas?
Klaus
I got the exact same issue when modding the S5's camera apk. The trick is to open your original apk with an archive manager and only replace the classes.dex and resources.arsc. I then copied the apk to /system/app/ and after a reboot I could successfully launch the camera.
More details about hacking system apk's can be found here: https://code.google.com/p/android-apktool/wiki/FAQ (My recompiled apk Force Closes (FCs). What gives?)