Related
APK Link
Original discussion thread
I removed the loud irritating ding noise.
I can confirm it works as I just installed it by pushing it to system/app via root explorer.
seem to me this needs to be moved to theme and apps section
good work tho!
Moved to themes and APP
how to install camera.apk?
I am a forum noob trying to figure out how to install camera.apk over the existing system app. I consider myself a competent searcher/hacker but little experience with android beyond a careful root and backup. I tried hard searching the forums and web without success on how to do this. If you can help with instruction or point me to a resource I would appreciate it. Cheers
Instructions for installing apk with root explorer:
1. download apk or apks your sd card
2. navigate to file and copy or move apk or apk's
3. navigate to system/app
4. tap on r/w at the top
5. paste all apks
6. change permissions to match the other apks's in the system/app directory.
7. Reboot
Root explorer is my file manager of choose but any file manager with root access will work
X
So this is a totally off topic, sorta, question about the camera.apk...
I like the Camera on this device. Its fast, very fast but on the ROM Ultimate G2x the camera lags like no other!! But the one on CM7 is smooth and i like that one very much!
So my question is, can i replace the camera on the Ultimate ROM with the one found on the CM7 ROM even though one is running Android 2.2.2 and the other is running 2.3.[?] ?
Thank you for your time!
jerrycycle said:
Instructions for installing apk with root explorer:
1. download apk or apks your sd card
2. navigate to file and copy or move apk or apk's
3. navigate to system/app
4. tap on r/w at the top
5. paste all apks
6. change permissions to match the other apks's in the system/app directory.
7. Reboot
Root explorer is my file manager of choose but any file manager with root access will work
Click to expand...
Click to collapse
How do I change permissions? Or is it just fixing permissions in recovery?
Vertiginouz said:
How do I change permissions? Or is it just fixing permissions in recovery?
Click to expand...
Click to collapse
Buy root explorer or do it in terminal. Its worth it to buy Root Explorer, you will use it in the future.
Super Weird... But I use CM7 (Build 54 with colorized nightlies) I backed up / replaced the camera, as I dont like the CM7 one (since I cant zoom with the dam volume buttons) and applied this .apk.
Gave me a boot loop... I dunno if it was cm7 or andriod commander.
I'm pretty sure you need the lg framework for it to work
Now if only we could patch the apk so it doesnt have issues when below 15% battery. I HATE that limitation.
In that case i use "hdr camera+" app its a really good camera app only thing is doesnt have flash. But other than that is a good camera app.
zimphishmonger said:
Now if only we could patch the apk so it doesnt have issues when below 15% battery. I HATE that limitation.
Click to expand...
Click to collapse
Hey I get a force close as soon as I try to open it. Any ideas?
Weapon 2.6 and used Root explorer to put in app folder and fixed permissions
Also Have Camera Problems
Hi guys my name is Natalli and I am new here so please don't attack if I posted in the wrong thread.
I believe this thread should be most appropriate.
I am working with a G2x freshly rooted as of today.
Flashed to a "P999_2.3.3_Stock_Tweaked_v1.2.2" rom that I found on this site.
So far everything is great.
MY DILEMMA:
Ever since I updated my G2x from the stock version over to Gingerbread I noticed that my awesome camera app disappeared. The one from the previous version had no shutter sound (which is a blessing) plus the settings were a lot better!
I do not like the camera layout or the position of the buttons.
I'd like to find the camera app that I had before. So would I be looking for the Froyo camera app? Or is it the LG camera??? I am confused please help.
I hate this new camera app, always have and always will.
LG camera is the one your looking for. (That was also on froyo) its ported by flaco, you can find it in the developement section. Its not a 100%, but it works just find in my opinion ( since I don't use the ffc so much)
Sent from my LG-P999 using Tapatalk
Hi,
I'm pretty sure this problem could be common to all rooted devices, so I'm posting it in the general Q&A.
Basically, I would like to experiment with some build.prop tweaks I found around other XDA topics. I'm sure all of you know about the general tweaking of the said file, so I won't get into too much detail about it.
However, the changes just don't stick. They reset to default every time I reboot, as if the build.prop file never changed. So, how do I make them stick?
Phone details:
Phone: Xperia X8
ROM: FroyoPro v2.5
Kernel: Stock (can't unlock the bootloader, unfortunately)
Are you saving before exiting?
XperienceD said:
Are you saving before exiting?
Click to expand...
Click to collapse
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
xWhiskey said:
Of course! I even double-check if the changes were still there by opening the modified build.prop after the work is done. For the changes I used Root Browser Lite with the Text Editor pre-installed inside. This method does work well, as I used it to modify hw_config parameters related to governors a couple of weeks back.
I've read somewhere that sometimes changes aren't possible if the kernel is stock. Could that be the case here?
If not, are there any other methods I could use to modify build.prop?
Click to expand...
Click to collapse
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
sircrisp said:
A quick google caused me to find this thread and I too am having the same problem. I'm currently trying to edit my build.prop to unlock games which say they are incompatible. I'm using ES File Explorer and the built in text editor to edit and save the .prop file, I check if the changes have saved before rebooting my phone but when I turn it back on it has reverted back to stock.
Click to expand...
Click to collapse
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
xWhiskey said:
Check if your ROM has a dual build.prop file. If one exists in system/bin, you ought to edit that one for the change to stick. This solved the issue for me, and might solve it for you.
If it isn't there, try using search, and if you find another one somewhere else then try editing that one. A simple matter, but apparently easily missed
Click to expand...
Click to collapse
I'm here to wake this thread up, because I'm having this same issue and I can't seem to find any duplicate build.prop file...
Anyone having a good suggestion for me please give it, all assistance is welcome.
Android version 4.4.4
Galaxy Note Edge
Sent from my SM-N915P using Tapatalk 2
me too have the same problem , please some dev or expert help with these problem
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Are you setting the file permissions correctly as rw-r--r-- ??
[/COLOR]
flexton said:
You install root explorer and mount as r/w and copy the build.prop into your sd card (the unmoded one) and connect your phone to your pc and turn on usb copy file transfer or something like that. In your pc go into your sd and open your copied build.prop with notepad and mod it as you like. After that go into your root explorer and replace it with your original build.prop. Try on not bricking your phone bcz i bricked mine like that when i put a lot mods on it haha, make a cwm backup or if you know how to unbrick it in every case Hope i helped
Be sure its mounted as r/w otherwise you will not be able to do anything to system files.
Use the original root explorer or Andro Zip is recommeded by me
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
samsungrockz said:
Are you setting the file permissions correctly as rw-r--r-- ??
Click to expand...
Click to collapse
thank u for answering but sorry guys to say this , it's not the way of editing it , or the permission , when i make changes they are saved correctly and the device apply the changes in the start of the first boot after these changes are made , but during the boot (after applying the changes) the device restore the stock build.prop , so when the device finishes boot up the changes are applyed but the build.prop (i cheked it) is back to stock , this mean another boot & the changes are gone , :crying: :crying: no matter how many times or changes u do they are applyed only for the first boot after they are made
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Maybe it has some stock security feed, try to go to custom roms i dont now what else can you do
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Kico.MMK said:
it my first ported rom -porting by replacing files ,not expert work- and i'm having this problem
Click to expand...
Click to collapse
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
flexton said:
Try finding your device on xda and look for a custom rom that someone more expirienced than you if it doesnt work i dont know what will
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the advice , actually i did that but you know there is always something to be fixed :silly:
I have the same issue with my Vodafone Smart Ultra 6. I have root and system has read write access according to ES File Explorer. But any app that has root privileges, writes just fine without errors. However, if I close the app and load it again, or reboot, any changes are lost. So if I remove a system app using a root uninstaller it will say the app has been uninstalled. But it's still there. Drives me insane.
Exactly the same on the Smart Ultra 6.
Was hard enough to get it rooted but seems any changes to the system partition/file system just don't stick. Short of putting a custom rom on it I'm stuck for ideas.
I'd love to know what causes this behaviour.
Any updates here? I just started running into this after updating to the 7.1.1 January factory image on my 5x. The weird thing is when i reboot in TWRP it all looks fine but when I look at my system directory from Android the boot-from-recovery.p is still there and my build.prop changes aren't...push TWRP again, boot to recovery read build.prop and it's my edited version. wtf?
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
I have the same problem: after reboot all the changes are gone....
ashd63 said:
I have found a solution which works in my case.
Edit build prop using any root explorer and save it.
Now once again edit the file with different root explorer app like amaze or es explorer with some comment line like
#comment
and save it.
Now it should prevent the build prop from resetting after a reboot.
Click to expand...
Click to collapse
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
ullie4404 said:
I have the same problem: after reboot all the changes are gone....
It's not working for me ☹
---------- Post added at 09:43 AM ---------- Previous post was at 09:30 AM ----------
Is it normal that my build.prop has the permissions -rw------ ?
This could be the problem.
Click to expand...
Click to collapse
Did you ever find the solution to this? I'm having the same problem..all changes reset with every reboot and the file's permission is like -rw-----
I just installed jelly bean on my Samsun GS3 SCH-R530U, and now whenever I Odin CWM, it will boot only one time when I boot to it, after that I get a fallen over robot icon from samsung, and their old boot menu. This means I have to flash it every time I want to backup or restore a nandroid backup. Is there some way I can get past this? Do I need a newer CWM? Has Samsung found a way to disable CWM?
try this
as a nexus s owner got this issue in past, seems to be caused cause from GB on in /system/etc there is a install-recovery.sh wich overwrite all the recovery you have installed every time your phone boot up, just solved checking for this file and deleted or renamed (as you want) so in booting the CWM won't be deleted and overwrited by the original one (wich is called install-recovery.sh)
To be clear using root explorer os similar point to this file in /system/etc, then delete or rename, if it tells you can't do cause is read only file system switch from R/W to R/O
Not entirely sure but I think flashing recovery.IMG file on Mobile Odin solved the issue for me.
International S III 16GB / Dualboot 4.1.2 Stock & Cyanogenmod 10.1 / Gokhan's SK
Worthy path to pursue
stremax said:
as a nexus s owner got this issue in past, seems to be caused cause from GB on in /system/etc there is a install-recovery.sh wich overwrite all the recovery you have installed every time your phone boot up, just solved checking for this file and deleted or renamed (as you want) so in booting the CWM won't be deleted and overwrited by the original one (wich is called install-recovery.sh)
To be clear using root explorer os similar point to this file in /system/etc, then delete or rename, if it tells you can't do cause is read only file system switch from R/W to R/O
Click to expand...
Click to collapse
This sounds like a good path to pursue, but I can't find any "install-recovery.sh" anywhere in the system. Could it be named something else, but have the same function?
Accidentally found a workaround -PROBLEM SOLVED 4 me
I found that after using clockworkmod recover, if I remove battery, re-insert battery and then boot phone in normal way, instead of using CWM menu to reboot, it doesn't get over-written. I put in my Title that my problem was solved. Some forums have some other way to indicate this, but I couldn't figure out how on this forum.
I root my phone as a thread
In the site but when I use root Explorer to edit permissions of some
Folders ex: system it says Warning
Permissions change was not successful. Please note that some file systems
(E. G. SD cars) do not allow permission changes
Also I use root Explorer as r-w
Sameh Amnoun said:
I root my phone as a thread
In the site but when I use root Explorer to edit permissions of some
Folders ex: system it says Warning
Permissions change was not successful. Please note that some file systems
(E. G. SD cars) do not allow permission changes
Also I use root Explorer as r-w
Click to expand...
Click to collapse
you rooted your phone as a thread?
what does that mean?
No some permissions are unable to change because it is for safe purposes because you might screw up your phone if you change the permissions or there is a duplicate file of it
Sent from my GT-S7500 using xda app-developers app
ShadowsDie said:
you rooted your phone as a thread?
what does that mean?
Click to expand...
Click to collapse
Sorryyyyyyyy for confusing you by not describing the way that I rooted the phone with
I ROOTED the phone by
1.put the phone in download mode
2. Flash CWM by ordin
3. put the phone in recovery mode
4.install zip superuser 3.1.1 arm. Zip
And I want to edit permissions of system folder to copy files to system/bin
Sameh Amnoun said:
Sorryyyyyyyy for confusing you by not describing the way that I rooted the phone with
I ROOTED the phone by
1.put the phone in download mode
2. Flash CWM by ordin
3. put the phone in recovery mode
4.install zip superuser 3.1.1 arm. Zip
And I want to edit permissions of system folder to copy files to system/bin
Click to expand...
Click to collapse
ok... i think there is a newer one in development section, with superuser 3.1.3
but i don't know if that is the problem, anyway you can redo the whole process of rooting, starting with flashing stock or you can change the app
i use root explorer and it works nicely, never had a problem with it
another thing you can try is flashing a custom rom, maybe its a firmware problem
ShadowsDie said:
ok... i think there is a newer one in development section, with superuser 3.1.3
but i don't know if that is the problem, anyway you can redo the whole process of rooting, starting with flashing stock or you can change the app
i use root explorer and it works nicely, never had a problem with it
another thing you can try is flashing a custom rom, maybe its a firmware problem
Click to expand...
Click to collapse
May you tell me a nice custom room
Sameh Amnoun said:
May you tell me a nice custom room
Click to expand...
Click to collapse
stock based: inspiration v17.3
AOSP: CM by TheWhisp
Please Help I have deleted xbin folder in system/xbin in my samsung gts5303 and now i want to again root my samsung gts5303 but it is not rooting now.Firstly i have rooted it with Root Master android app but now when i m trying to reroot it with Root Master app it shows Sucessfully Rooted and also installs supersu app but not installs binary becouse binary is installed in system/xbin folder and i have deleted it.
and an unknown folder sbin is added in /sbin. and it is empty i have no root acess but when i m deleting it it is sucessfully deleted but when i comeback to / path it is added again
Now i m requesting you to please solve this problem and give me any app by which i can add xbin folder again in system/ with out root.and with out pc because i have not any pc...
thanks in advnce...
I hope you have a nandroid back up, otherwise it is going to be really hard to do with out a PC handy.
You will not be able to add File or folder in system even 3rd party app will not be able to write on system folder without root permission so try to full unroot the phone then again try to root so there is a chance of reinstalling binary again anyway don't you have nandroid backup?
how can i do nandroid backup
justmpm said:
I hope you have a nandroid back up, otherwise it is going to be really hard to do with out a PC handy.
Click to expand...
Click to collapse
what is nandroid backup how can i do this.
CWM for gts5303
please give me any CWM for my samsung gts5303 by which i can flash a .zip file to install binary again. thanks
i have also deleted all files in /sbin folder
And i have deleted all files in/sbin folder can it be a cause for not rooting .or deleting system/xbin folder.
I Have find out the solution of this Problem
Good News for all who are suffering from this problem.If you want to get rid from this problem by simply installing an .apk file then contact me on My Whatsapp
919622506468
EMail: [email protected]
Or If You want a simple .apk file to root your device (for all phones) then contact me now. hurry!
you need reup rom for your device
I Have Findout The Solution Of This Problem (MySELF)
I Have Foundout It's Solution By My Self. I Haven't got any Best solution for this problrm in Xda Or Google. But I Myself Had Fixed this problem. So I Only want the Users who Have This problem in their phone would Get rid from this problem they have to done nothing. They Only have to install a simple android app of about 2mb (No Need of Pc Or Anything etc) So, Contact Me To Get its Simple (OIS) OneInstallSollution By HackerRM
Whatsapp/Phone : +919622506468
EMail : [email protected]
Thanks...
[Any Problem On Any Device]
Get Simple (OneClick) Solution.
[ONLY WITH HackerRM]