Hello All,
I've been trying long time to block the camera.
What I'm trying to do is to block it so no other app could use it.
but - The block should not be permanently
After rooting and mounting the device for RW, I have tried to rename the driver folder in the following path: sys/devices/virtual/camera but this doesn't work because there are no permissions to edit these files (I think that's because the directory is controlled by the kernel..).
In addition I have tried "Permissions Denied" app - and that didn't work too..
I really hope that someone here have idea how to solve this issue.. must be a way to crack it..
Thanks,
doron447 said:
Hello All,
I've been trying long time to block the camera.
What I'm trying to do is to block it so no other app could use it.
but - The block should not be permanently
After rooting and mounting the device for RW, I have tried to rename the driver folder in the following path: sys/devices/virtual/camera but this doesn't work because there are no permissions to edit these files (I think that's because the directory is controlled by the kernel..).
In addition I have tried "Permissions Denied" app - and that didn't work too..
I really hope that someone here have idea how to solve this issue.. must be a way to crack it..
Thanks,
Click to expand...
Click to collapse
i think u may move some lib files related to camera from /system/lib and replace them back wen necessary
On my phone, the following files are in /system/lib. I would imagine that renaming/moving one or more of them will break the camera.
libcamera.so
libcamera_client.so
libcameraface.so
libcameraapp.so
libcameraservice.so
liboemcamera.so
Try finding those files on your phone and renaming or moving them. With root, it should definitely be possible (I don't want to try because I don't want to break my camera.)
SifJar said:
On my phone, the following files are in /system/lib. I would imagine that renaming/moving one or more of them will break the camera.
libcamera.so
libcamera_client.so
libcameraface.so
libcameraapp.so
libcameraservice.so
liboemcamera.so
Try finding those files on your phone and renaming or moving them. With root, it should definitely be possible (I don't want to try because I don't want to break my camera.)
Click to expand...
Click to collapse
Hi,
Thanks for your respond.
After deleting file "libcameraservice.so" I rebooted my phone and it got stuck under Samsung loading screen. I had to restore all the files in the phone...
doron447 said:
Hi,
Thanks for your respond.
After deleting file "libcameraservice.so" I rebooted my phone and it got stuck under Samsung loading screen. I had to restore all the files in the phone...
Click to expand...
Click to collapse
Dude see this link.
Related
I have spent all morning trying to get rom manager to fix permissions and have finally tracked down the culprit. the fix_permissions script is looking for /data/system/packages.xml. At least with perception 4 it is in /dbdata/system/packages.xml
I have edited the file and attached it.
First the rename and drop the .txt. the actual name of the file is fix_permissions
Copy to sdcard.
Using root explorer copy it to /data/data/com.koushikdutta.rommanager/files
(good idea to back up the other one first.)
Issue I have is after I reboot, the file resorts back to the old file.
Not sure why.
If you want to edit the file directly in root explorer, there were 4 instances of the /data/system/packages.xml
!!All credits go to the developers of rom manager and associated programs within it!!
I for the life of me cannot figure out why the file keeps changing.
So the best thing i can think of is to load it to the sdcard.
Using terminal emulator cd /mnt/sdcard and then sh the file.
Quickest diretiest way to get it to work.
I hope it helps someone out there.
Code:
su
cd /mnt/sdcard
sh fix_*
Thank you--if it helps, I simply copied the packages.xml file into /data/system/ in order to run fix_permissions, and then just deleted the .xml file.
A temporary fix, yes, but I was just trying to fix a specific problem with ending phone calls causing an FC (see http://forum.xda-developers.com/showthread.php?p=9943863#post9943863).
Thanks, your fix worked for me as well...
jnagar said:
Thank you--if it helps, I simply copied the packages.xml file into /data/system/ in order to run fix_permissions, and then just deleted the .xml file.
A temporary fix, yes, but I was just trying to fix a specific problem with ending phone calls causing an FC (see http://forum.xda-developers.com/showthread.php?p=9943863#post9943863).
Click to expand...
Click to collapse
--Much appreciate the suggested fix. Worked like a charm.
do you have to delete the packages.xml afterwards?
what will happen if I just leave it in the data/system folder instead of copy/pasting it every time?
Oh ant thanks SO much. Really needed to be able to fix permissions after Nero v5 started to act crazy yesterday.
pushabutton said:
what will happen if I just leave it in the data/system folder instead of copy/pasting it every time?
Oh ant thanks SO much. Really needed to be able to fix permissions after Nero v5 started to act crazy yesterday.
Click to expand...
Click to collapse
I haven't played with this in awhile, but it seemed that it was overwritten every time Rom manager started.
I'll play around with this and see what I can come up with as a more permanent solution.
Dear All,
First thankyou so much for the great forum we have here, I am using Huawei Ideos u8150, the fone is network locked so I played around, being a total noob I started with installing sdk, and rooted my fone using z4root, rooting was successful
No when I try to copy a modified build.prop to the systems folder in root explorer, the file is copies but is not visible, also I have deleted the original build.prop & I am afraid to reboot the fone,
can restoring the fone to factory settings solve this ? also how come I copy the file to system folder, it gets copied and I still cant see it ?
I have tried pushing the file using ADB command line but the device refuses to mount (persmission denied)
I would really be thankful to anyone who can guide a noob like me, if you dont this forum has enough reasons to love it already,
cheers !
cknaveed said:
Dear All,
First thankyou so much for the great forum we have here, I am using Huawei Ideos u8150, the fone is network locked so I played around, being a total noob I started with installing sdk, and rooted my fone using z4root, rooting was successful
No when I try to copy a modified build.prop to the systems folder in root explorer, the file is copies but is not visible, also I have deleted the original build.prop & I am afraid to reboot the fone,
can restoring the fone to factory settings solve this ? also how come I copy the file to system folder, it gets copied and I still cant see it ?
I have tried pushing the file using ADB command line but the device refuses to mount (persmission denied)
I would really be thankful to anyone who can guide a noob like me, if you dont this forum has enough reasons to love it already,
cheers !
Click to expand...
Click to collapse
Moderators if by any chance I have placed this query in the wrong part of forum, please let me know in which part I should raise it, thanks !
In the top right hand corner or left it should be a r/o button. If you push that to r/w which is read/write you will be able to copy the bp correctly. Don't forget to mount as r/o which is read only before you exit RE. Then reboot. If you made a backup which you should have done before modding the bp you will be ok to reboot. If anything goes wrong just do a restore. Also you can Redownload the current rom your on to your cpu. Then extract it to a folder on your desktop. Then browse threw all the folders untill you see the stock build prop. Copy&paste it to your sd and that's your stock build prop. Hope this helps. Good luck
#Root/Hack_Mod-Always®
laie1472 said:
In the top right hand corner or left it should be a r/o button. If you push that to r/w which is read/write you will be able to copy the bp correctly. Don't forget to mount as r/o which is read only before you exit RE. Then reboot. If you made a backup which you should have done before modding the bp you will be ok to reboot. If anything goes wrong just do a restore. Also you can Redownload the current rom your on to your cpu. Then extract it to a folder on your desktop. Then browse threw all the folders untill you see the stock build prop. Copy&paste it to your sd and that's your stock build prop. Hope this helps. Good luck
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
thanks for the kind help, I have tried doing that, I have rooted it, the I click on the r/o button and then I did copy the new built.prop to systems folder, the copying process completes, doesnt report any error but still there is no file visible by the name of built.prop, I just cant find it, is it hidden ? or is it not being copied in the first place ? & thanks I would try to extract the stock built.prop, and copy it to the folder but I will do it as a last option till I dont find something else,
thanks a million for the help, would apprciate if you can point it what I am doing wrong
I'm trying to use my new Sensation with the SIM from my Japanese iPhone, which requires replacing the stock Mms.apk with one that works with Softbank. That much I managed to do. Now when I try to open the Messaging app it crashes immediately, which is apparently normal and means I need to delete the old Mms.odex. But when I try, the command prompt window tells me:
rm failed for /system/app/Mms.odex, No such file or directory
I've made sure the folder isn't read-only (I managed to copy the new Mms.apk to it after all). Not sure what else could be going wrong. Thanks in advance for any help.
Its not a good idea to push files into the system directory of an odexed ROM like that. You usually need to push the appropriate .odex file with the .apk file.
Also could be a permissions problem. You need to make sure the permissions for the new file the are same as what's already in the directory.
Sent from my Sensation using Cyanogenmod
dr.m0x said:
Its not a good idea to push files into the system directory of an odexed ROM like that. You usually need to push the appropriate .odex file with the .apk file.
Click to expand...
Click to collapse
I know it's not ideal, but this method seems to work just fine; I've read a bunch of Japanese blogs that explain this is how to get MMS working with Softbank, and people on forums elsewhere say it's worked for them.
dr.m0x said:
Also could be a permissions problem. You need to make sure the permissions for the new file the are same as what's already in the directory.
Click to expand...
Click to collapse
How do I do that? I'm pretty new to all this, two days ago I was Googling where to find my Sensation's settings menu
If you want to ensure the mms.apk has correct permissions you can simply run:
adb shell chmod 644 /system/app/mms.apk
This will set the correct permissions for apps in the /system/app folder, although its worth reading up on linux permissions to understand what the command is actually doing.
Permissions didn't help, but I've managed to track down another Mms.apk file that works well enough - messages don't integrate properly with HTC's Messaging app, but I can send and receive MMS. I'm going to keep looking for a better apk but at least this one functions!
I copied the zip file to sd card and used recovery to install it.
Does not work and would not allow me to change permission on sd card.
App is in system/app but cann't change permission, hence not working. ANy clear cut help will be greatly appreciated.
rlamba said:
I copied the zip file to sd card and used recovery to install it.
Does not work and would not allow me to change permission on sd card.
App is in system/app but cann't change permission, hence not working. ANy clear cut help will be greatly appreciated.
Click to expand...
Click to collapse
You need to select RW instead of RO if using root explorer.
ICS Keyboard Permission
mrg02d said:
You need to select RW instead of RO if using root explorer.
Click to expand...
Click to collapse
It is RW and I can't change the permission using root explorer. However I managed to change the permission of zip file using windows 7 permission. I will try again. Thanks for your help.
Still not working
rlamba said:
It is RW and I can't change the permission using root explorer. However I managed to change the permission of zip file using windows 7 permission. I will try again. Thanks for your help.
Click to expand...
Click to collapse
I have changed the permission and pshed the files using adb. I get the message
process com.android.inputmethod.latin has stopped unexpectedly. Please try again.
I am trying to make it work using htc sensation with ARHD XE ROM 3.6.7
Can anyone help me.
Where did you get the zip file? I am going to try install this version as the latest one in the HyperNoSense Rom keeps just dropping the keyboard VERY frustrating!
Replace it yourself then, it's not that hard.
the .so goes to
/system/libs
the apk goes to
/system/app
I don't know the permission for it and I don't pay attention to it. It just worked for me straight away
File downloaded from
JamesSawyer said:
Where did you get the zip file? I am going to try install this version as the latest one in the HyperNoSense Rom keeps just dropping the keyboard VERY frustrating!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=18716673
Download link is,
http://proxuser.designbymalone.co.uk...roxuser-v2.zip
illuminarias said:
Replace it yourself then, it's not that hard.
the .so goes to
/system/libs
the apk goes to
/system/app
I don't know the permission for it and I don't pay attention to it. It just worked for me straight away
Click to expand...
Click to collapse
I have already tried this but no good. May be I should download file from different location and give it a try. Thanks for your help.
I got it working
I have managed to get it working by downloading the file from different place.
Copied the apk file to /system/app then changed permission and extracted .so file and copied to /system/lib, changed permission and restarted.
I would like to thank all of you who tried to help me. I love this community.
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
1 - Download FIXV2 here - http://d-h.st/gMh
2 - Extract the file to your desktop and copy the files inside "FIRMWARE\IMAGE" folder to your phone.
3 - Download root explorer from play store and move those files to the firmware\image directory located on your phone.
4 - Long press each file and set permition to RW-R-R (0644) (You do this by selecting OWNER to read and write, GROUP to read and OTHERS to read.
5 - Reboot and try accessing settings.
Thanks to ferreinf for the link and how to do it, I just tried to do this as much newbie proof as possible.
have seen this problem in numerous ROM threads(haven't myself run into this), thanks for the heads up :thumbs up:
Sent from my Transformer Prime TF201 using Tapatalk
scorthyn said:
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
1 - Download FIXV2 here - http://d-h.st/gMh
2 - Extract the file to your desktop and copy the files inside "FIRMWARE\IMAGE" folder to your phone.
3 - Download root explorer from play store and move those files to the firmware\image directory located on your phone.
4 - Long press each file and set permition to RW-R-R (0644) (You do this by selecting OWNER to read and write, GROUP to read and OTHERS to read.
5 - Reboot and try accessing settings.
Thanks to ferreinf for the link and how to do it, I just tried to do this as much newbie proof as possible.
Click to expand...
Click to collapse
Hi
Does this help to uninstall system apps as wel instead of deleting apk from system/app folder
Thanks.
smohanv said:
Hi
Does this help to uninstall system apps as wel instead of deleting apk from system/app folder
Thanks.
Click to expand...
Click to collapse
No, it has nothing to do with what you want and there's absolutely no point in doing what wanna do either. You can not reclaim the free space to yourself and that would yet prevent you from installing OTA updates. The best way around this is to unable the system apps you don't wanna run.
Doublepranks said:
No, it has nothing to do with what you want and there's absolutely no point in doing what wanna do either. You can not reclaim the free space to yourself and that would yet prevent you from installing OTA updates. The best way around this is to unable the system apps you don't wanna run.
Click to expand...
Click to collapse
Your description about this patch is confusing...
Read your description,
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
scorthyn said:
First, you need ROOT access to do this. It will fix the security force-close and enable the uninstall of apps.
1 - Download FIXV2 here - http://d-h.st/gMh
2 - Extract the file to your desktop and copy the files inside "FIRMWARE\IMAGE" folder to your phone.
3 - Download root explorer from play store and move those files to the firmware\image directory located on your phone.
4 - Long press each file and set permition to RW-R-R (0644) (You do this by selecting OWNER to read and write, GROUP to read and OTHERS to read.
5 - Reboot and try accessing settings.
Thanks to ferreinf for the link and how to do it, I just tried to do this as much newbie proof as possible.
Click to expand...
Click to collapse
firmware\image directory located on your phone.
Where is this directory on the phone? it does not exist, are we to just push the whole dir w/files to the phone? I agree, need alittle more info here please....
Good work if it does what it says....:good:
TheAxman said:
firmware\image directory located on your phone.
Where is this directory on the phone? it does not exist, are we to just push the whole dir w/files to the phone? I agree, need alittle more info here please....
Good work if it does what it says....:good:
Click to expand...
Click to collapse
Worked for me to get the nexus g+ rom working fully... used root browsed in ROM Toolbox to copy the files to the relevant folder off root, and set all the permissions to rwx.