Database Develop

Help to remove disastrous apk - please android Wizards

I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????

I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone

wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?

Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.

the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.

thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!

TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.

hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!

TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.

I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.

TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).

Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.

Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.

TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.

Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!

flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse

yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?

TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.

TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.

This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions

Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.

Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html

elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you

Yes this method definitely works. I have market working now and can search for protected apps etc.

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.

he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.

I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/

Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.

LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.

Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?

Yes, it requires an edit to a file that you can only be edited when rooted

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!

OP has been updated with original build.prop

Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input

will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.

Thanks for the reply.

[FIXED] [Q] XT860 - Broke my /system/app folder...

EDIT: Fixed! Procedure I used was to download Danifunker's system dump, move it to /sdcard/ via adb push, then run the following:
Code:
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
This completely refreshed my /system folder. Original post below:
--------------------------------------------------------------
Hello XDA forumgoers, longtime reader first time poster here. I'm currently posting because I made a few mistakes. Several mistakes, actually.
1. In my quest to de-bloat my XT860, I accidentally removed one file too many, which caused my phone to mysteriously not have a cell signal. (com.motorola.service.main kept crashing.) So I hit the forum and grabbed a system dump from this thread (thanks Willis111):
http://forum.xda-developers.com/showthread.php?p=17501981
I had bought the phone with some version of Cyanogenmod Recovery installed by the previous owner, so I was able to use that and ADB to stick the .apks and .odex files in the /system/app folder, chmod 644 them, and even factory reset for good measure.
2. As I soon found out, I had somehow made things worse. The phone, when boot into, shows the "press android to begin" page, but com.motorola.service.main and some other apps keep FCing on me, and I can't progress past that screen. In my haste, I didn't backup any of my system folders at all, though, I still backed up my apps with Titanium.
Tl;dr:
presumably none of the /system/app apks boot, most notably com.motorola.service.main. How do I fix this? Can I?

Try to flash
http://forum.xda-developers.com/showthread.php?t=1288823

You also need to chown 0:0 both the apk and the odex

Have you tried using my original system dump? It was taken with dd, so things like symlinks and the other sort should be functional. The only caveat is that a number of apps were frozen at the time, so you may need to unfreeze them with titaniumbackup.
http://www.multiupload.com/SORQERFAYT

DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?

jonsicoli said:
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
Click to expand...
Click to collapse
What about rootkeeper?

DoubleYouPee said:
What about rootkeeper?
Click to expand...
Click to collapse
I can't get past the "click android" screen, so I probably can't install or run it. Any way to do it via adb or Cyanogenmod Recovery?
I really appreciate the help.

jonsicoli, if you want to restore your *entire* /system folder (not just apps) you would run a similar command-set as this.
1. Copy the file to the internal memory
adb push c:\path.to.folder\mmcblk1p21.img /sdcard
the file will be located in the root of the sdcard (or you could drag and drop the file in USB storage mode)
2. Do a full restore on system memory *I have not checked to ensure this is working... but a command similar to this should work
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
- wait -
(it would have to write about 500mb and replace all of the contents of /system )
reboot
_______________________________________________________
Okay, if you just want to look at the files, you could use a linux machine to mount the filesystem (it is a standard ext3 FS) or you could do what I have done on my windows system:
Install EXT2FsD from http://sourceforge.net/projects/ext2fsd/files/latest/download?source=files
Then install OSFMount from http://www.osforensics.com/tools.html
Point the OSFMount program to the img file that you downloaded and assign it a drive then voilla!
I am pretty sure this is a bit of overkill, but this should completely restore your system close to factory (minus the APKs that were upgraded/disabled, plus the fact root was done)

Thanks Danifunker! I reset my entire /system folder, and restoring my user app backup. I'm just relieved to have my phone back. Now to mark this thread as solved.

Awesome!!!!!! Glad to hear my system dump works! Thanks for testing
My command lines were written correctly also I guess?
Sent from my XT860 using XDA App

searched for like 8 hours until i found this thread. Just what i needed, i had system image for 2.3.6 from your other post but no command.

Fix camera permissions in the market

So the Nexus 7 does not have a primary camera, so a ton of apps in the market that use a camera show up as Not Compatible. You can sideload them and they may or may not work. However, there's a fix.
I'm on rooted stock, but if your custom ROM is also having this issue in the market you can tell your ROM Chef what file to add.
Caveat: This IS working for me as of right now, but it did not immediately, so there might be some delay or something else needed to do to make it work immediately. I'll update this post based on feedback if it's working immediately for folks or there's some other way to speed things up.
Caveat: Just because you can install an app won't make it work. If an app crashes, you've been warned. All apps might not work, but at least some apps that can use camera and don't need the camera function can be installed (Grocery King works fine, barcode scanning crashes), some will work fine (Camera Zoom FX).
And just to be clear, you are modifying /system. If you do this wrong, you could cause yourself problems. You have been warned.
Pre-reqs
Rooted
Root file explorer app to copy a file into /system (I use Ghost Commander, use your favorite app)
--OR THE FOLLOWING--
ADB working
Busybox (does not need to be installed, but needs to be available for cp, or you can use cat if you know how to do that method instead)
Busybox might be needed to remount /system as read-write, or you can use some other method to do this
Pick the method you want to use, adb, or a file explorer that can mount /system and write files there. Pick one method or the other, I've hidden the content on both by default so fewer people think you need to do everything..
android.hardware.camera.autofocus.xml is a file inside of the zip attached to this post, all references to copying that file imply you open the zip file and extract or copy it directly over. NOT the zip file itself. And no, this is not "cwm flashable". If this is working for folks and someone wants to make a CWM Flashable ZIP file to use, I'll be happy to add it to the post and update instructions.
Instructions for using your favorite root explorer kind of app
Download the file attached to this post to your device
Launch your favorite root explorer type app and remount /system as read/write
Copy android.hardware.camera.autofocus.xml to /system/etc/permissions/
Remount /system as read-only
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Instructions for using ADB/Manually copying it
Download the file attached to this post
Connect to your device over adb (I use wifi adb personally)
Do the following commands to launch adb and inside of adb respectively
adb push android.hardware.camera.autofocus.xml /sdcard
adb shell
su
mount -o rw,remount /system
cp android.hardware.camera.autofocus.xml /system/etc/permissions/
mount -o ro,remount /system
Click to expand...
Click to collapse
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Thanks to bonks in #nexus7 for confirming for me that he cannot access a few Camera apps and validating some permissions files for me to verify my changes had worked on my end.
Works for 4.3 as well, but the same caveat... It took three days to show apps as compatible, so not sure what needs to "clear" for the permissions to be updated, but give it a few days and it'll be fine.

Reserving for any followup info, particularly around if the market permission doesn't clear "immediately".

A partial list of apps that work/don't work, but all will install now and previously would not. If anyone tries another app or has more input I'll update this post.
I've also started a list of apps I know of that have altered their permissions in the market so that they should show up natively on the N7 without the fix.
Work Perfectly (maybe mirrored)
Paper Camera - Mirrored
Google Translate - Mirrored, maybe upside down.. Wonky, but does work.
Work With Caveats
Grocery King - Barcode scanning crashes, otherwise completely usable
Don't Work at All
Google Goggles - Blank image, although you can load images you took with other cameras
Retro Camera - Can't find camera
Fixed market permissions
Camera FX Zoom - Use landscape, or things are mirrored and flippped

This worked great for me...thanks a bunch!
Sent from my Nexus 7 using xda premium

Ima give this a go when I get home, thanks

Nexus 7 camera permissions
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David

DavidTheBourne said:
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David
Click to expand...
Click to collapse
http://stackoverflow.com/questions/...ort-for-android-application-manifest-assembly

Just wanted to bump this thread and let everyone know this still works for 4.3. However, I'm not sure what one would need to do to make it work faster.
I installed the XML file on my N7 about three days ago, cleared Market data, rebooted etc, specific apps still showed as not compatible.
Finally today I look, and compatible! Perhaps it's on Google's side, it only updates every so often.. I dunno.
Anyway, so it works, but it might take a few days for it to propagate

HTC One M7 - App will not stick on /system

Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks

sasteck said:
Hi everyone
I'm trying to get the infamous GPS Location Spoofer installed as a system app on my rooted HTC phone, but so far no luck, so I figured I would try to ask for help here, in case anyone went through a similar situation, or knows what I've been doing wrong. This is what I tried so far:
Installed the app from Google App store, and using File Explorer with root , tried to move the app folder to /system/app or /system/priv-app, , but pasting the folder there would result in an instant reboot and the app would not be there.
So I installed lucky patcher , and using apk downloader, downloaded the apk file from the App Store, copied it over to the phone, and used the "Rebuild and Install" option, choosing the option to install it as a system app , and it would process it and say that the installation was sucessfull, needs to reboot to complete, but after the reboot the app would not be there (not only not showing on the apps list, but navigating to the /system folder with File Explorer and checking app and priv-app I could verify that it was not installed).
SO I tried to use adb shell to do the work , and this is what I did:
mount -o remount /dev/block/mmcblk0p35 /system
to mount the /system filesystem as read write , and it did
cp /sdcard/Download/com.incorporateapps.fakegps.fre-55.apk /system/app
to copy the file under /system/app
chmod 644 com.incorporateapps.fakegps.fre-55.apk
to set the permissions as required
and reboot the phone, but after the reboot, the file would not be there. I tried also to create a folder under /system/app named com.incorporateapps.fakegps.fre-55, move the apk inside; installing normally , changing the mount point to read-write and moving it from /data/app to /system/app or /system/priv-app using the shell and chaning ownership / permissions , but the app will not stick , either rebooting or just re-mounting the filesystem as read-only again will cause everything that was done to be lost; and after trying any of the above one time, doing it for a second time would cause the phone to reboot.
I figure that there must be an image of the /system mount point somewhere , which gets installed every time there is a remount to read-only or reboot , or something of that nature, that will cause any changes made under /system to be lost. Maybe I'm wrong but it seems to be related to HTC phones, since there's load of people doing it on other models without issues, or maybe I'm doing something wrong, since I'm no android expert
Does anyone knows what could be the issue, or what can I do ? I searched the net quite a bit for a solution to no avail (here as well), any help is appreciated
Thanks
Click to expand...
Click to collapse
Are you using stock kernel?

donkeykong1 said:
Are you using stock kernel?
Click to expand...
Click to collapse
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)

sasteck said:
Yes, kernel is the default that comes with the phone (3.4.10.g96cae32 , android 5.0.2)
Click to expand...
Click to collapse
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel

donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
oh I see.. didn't know about that , thanks! I'll check about disabling system write protection , otherwise look for a custom kernel, never did it before but will give it a try

donkeykong1 said:
And there's your problem. Stock kernel has system write protection, so you can't mount system as writeable. You can, but after reboot, it comes back to read only, and nothing will stick into system partition. You have 2 choices now - disable system write protection on stock kernel, or flash a custom kernel
Click to expand...
Click to collapse
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs

alray said:
Shhhhhh, don't help him, he's going to steal everyone's pokemons
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]

donkeykong1 said:
Ooooohhh... That's why he's trying the spoofer.... If I knew, I wouldn't help at all [emoji6]
Click to expand...
Click to collapse
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed

sasteck said:
Sorry you feel that way, but I appreciate the help anyway. This is something that I never tampered with before, so I still had some doubts about the process, but I am liking the whole thing and will install a custom rom on my own phone, been reading about the Ressurection rom and it looks very nice, will try it as soon as I'm better informed
Click to expand...
Click to collapse
That was a joke mate. I don't care what you do with your phone, but I'm here to help if I can [emoji6]