Database Users

[Q] Assigning Permissions to system folder

I'm not sure what it is really.
While giving permissions to the system folder I've assigned all of the proper permissions for as far as I am aware.
Be it Sense or stock, I always get a boot error after creating the system.ext2, typing adb logcat:
/dev/log/main : Permission Denied
This halts the boot process.
Can anyone tell me which permissions need to be given to the system files prior to building them into a system.ext2?
I've also tried
chmod 4777 system/*
Thank you, and please ask if you need anymore information.

Can't open xRecovery

Hey
I've tried to install xrecovery, and done what this video says: http://www.youtube.com/watch?v=O6eRfqs8TVs but when i reboot, it won't work. Nothing happends when i press the bkac button alot.
If it is some files, causing this, then please send me yours, so i don't have to ask for them, when you have answered

SimonXiDk said:
Hey
I've tried to install xrecovery, and done what this video says: http://www.youtube.com/watch?v=O6eRfqs8TVs but when i reboot, it won't work. Nothing happends when i press the bkac button alot.
If it is some files, causing this, then please send me yours, so i don't have to ask for them, when you have answered
Click to expand...
Click to collapse
It happens to me to at the first time, all you have to do is delete the files and paste them again.. xD if still didn't work, i'll post my files here so you can tried..

I have tried now, but it won't work. I would be glad if you posted your files :b

Have you set the right permissions for the files?
All files needs to be writeable. The easiest way to set the write permissions is to use root explorer.
Or if using terminal emulator: Chmod each file to: 777

After a lot of trying this worked for me:
1. Download xRecovery from here.
2. Copy three files to sdcard - xrecovery.tar, busybox, chargemon
3. Just in case, get Busybox from Market and install it.
4. Copy three files from sdcard to /system/bin - don't forget to mount system as r/w (you can do it with Root Explorer by simply clicking "mount r/w" button)
5. Chmod all three files to 777 - with Root Explorer, open context menu for file and select "Permissions" and make sure all 9 boxes are ticked. Or, use adb shell.
6. Turn off your phone normally.
7. Turn on and keep pressing back button, now you should enter xRecovery.

blagus said:
5. Chmod all three files to 777 - with Root Explorer, open context menu for file and select "Permissions" and make sure all 9 boxes are ticked. Or, use adb shell.
Click to expand...
Click to collapse
Can i give permission, when the files are in the bin? Will it work then?

blagus, i did what you said, but still, with no luck .. :s

SimonXiDk said:
blagus, i did what you said, but still, with no luck .. :s
Click to expand...
Click to collapse
It is important to install xRecovery 0.1!!!
I have tried to install 0.3 first but it is not work on X8.
So use this only: http://forum.xda-developers.com/showthread.php?t=878426

qsmyle said:
It is important to install xRecovery 0.1!!!
I have tried to install 0.3 first but it is not work on X8.
So use this only: http://forum.xda-developers.com/showthread.php?t=878426
Click to expand...
Click to collapse
If you read the whole thread, then you would know, that it is the same that blagus said. And as i said, i did all that he said.

Use this files.. If didn't work, I don't know what to say, can't understand your problem..

Now i got to know that i should download these same three files three times. again - it do not work.

SimonXiDk said:
Now i got to know that i should download these same three files three times. again - it do not work.
Click to expand...
Click to collapse
Here did you pasted those files? Didn't you already having xrecovery running well, before you reflash your phone?

Now you get the story:
First of all, i tried in hours to get xRecovery work on my phone. Then succesfully, in some unknown way, i made it work.
Then i screwed up, and deleted the bin, so my phone wouldn't turn on.
Then i had to use SEUS to get my phone work, and I did that succesfully. But it was only 2.1 now.
Now i want 2.2 again, but can't make xRecovery work.

Weee it works now D I have no idea what I did diffrent this time, but it works now D thank you all for taking time, to help me ;b

And you're using 2.1 android, right? Is it rooted? If yes, all you have too do (and before that, delete the old files that you already pasted, except busybox..):
-put the files on your sdcard root;
-go to root explorer and to the sdcard folder;
- forget it busybox, just copy the other files;
- go to system/bin and then select the W/R option;
- then just paste them e restart your phone..
Then press a few times the back key, right after SE logo apears.. If you did't get anything, go again to the bin folder with root explorer and see if was created a folder with the xrecovery name.. If yes, just try again pressing back key until you get xrecovery menu..

" adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "D:\Manu\Android\xrecovery/chargemon" "/sdcard/tmp/chargemon"
failed to copy 'D:\Manu\Android\xrecovery/chargemon' to '/sdcard/tmp/chargemon': Permission denied
adb push "D:\Manu\Android\xrecovery/xrecovery.tar" "/sdcard/tmp/xrecovery.tar"
failed to copy 'D:\Manu\Android\xrecovery/xrecovery.tar' to '/sdcard/tmp/xrecovery.tar': Permission denied
adb shell dd if="/sdcard/tmp/chargemon" of="/system/bin/chargemon"
/sdcard/tmp/chargemon: cannot open for read: Permission denied
adb shell dd if="/sdcard/tmp/xrecovery.tar" of="/system/bin/xrecovery.tar"
/sdcard/tmp/xrecovery.tar: cannot open for read: Permission denied "
what should i do?

crazyboy05 said:
" adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "D:\Manu\Android\xrecovery/chargemon" "/sdcard/tmp/chargemon"
failed to copy 'D:\Manu\Android\xrecovery/chargemon' to '/sdcard/tmp/chargemon': Permission denied
adb push "D:\Manu\Android\xrecovery/xrecovery.tar" "/sdcard/tmp/xrecovery.tar"
failed to copy 'D:\Manu\Android\xrecovery/xrecovery.tar' to '/sdcard/tmp/xrecovery.tar': Permission denied
adb shell dd if="/sdcard/tmp/chargemon" of="/system/bin/chargemon"
/sdcard/tmp/chargemon: cannot open for read: Permission denied
adb shell dd if="/sdcard/tmp/xrecovery.tar" of="/system/bin/xrecovery.tar"
/sdcard/tmp/xrecovery.tar: cannot open for read: Permission denied "
what should i do?
Click to expand...
Click to collapse
you're going to need to mount the system first. I believe it's adb shell -> su -> then something. Can't remember now.

[Q] droid x download permissions issue

so im stuck and can not figure this out. for some reason the permissions for the download folders on my sd card do not have any user permissions checked. i can not download anything at all but the market is fine as it is on the internal memory i suppose. the only reason i came across the user permissions issue was because i found another post where someone had the same problem with downloading and corrected the issue by using root explorer and manually adding user permissions to any folder he used for downloading. now... here is my problem... i used root explorer and when i try to add user permissions to these folders, the settings that changed do not stick. i check mark the 3 boxes and accept the changes but if i go back into that folders specific permissions, they are unchecked once again. how can i get it to not revert back or better yet how can i just resolve the issue in whole so i dont have to keep fixing folder permissions on the sd card for app that downloads? i dont see why the sd card of all places would start having these permission issues. the guys post i came across tried to tie this issue to the fix permissions option in rom manager saying it may have caused the problem but i didnt use rom manager to fix permissions until this problem started. i was on liberty 1.5 rom then reverted back to rooted stock where i still have the problem with all downloading except the market again. any help would be greatly appreciated!

58 views and not a single response? wow.... so very shocking to see that, i bet if i had post this in the dev forum i would have gotten 15+ responses just to say that im in the wrong section then anther 30 for people to argue back and fourth on how everyone is being rude or that this is the reason devs stay in irc...

Give this a try if you have the sdk and adb set up.
from a command prompt:
1) adb devices (make sure that your phone shows up)
2) adb shell
3) su (assuming you have rooted your phone)
4) cd /mnt/sdcard/download (or whatever the folder on your sdcard for downloads is called)
5) chmod 777 /mnt/sdcard/download (or whatever your download folder is called)
this should change the permissions on your sdcard to have full permissions.

thanks for your reply! im grateful, but wouldnt that only change the permissions for the "download" folder? which is mostly only a default location for apps such as the browser?

The way sysadmin-x is suggesting makes the permissions way different than they are by default, I wouldn't recommend doing it that way.
If you want to change permissions on the entire sd card to what they are by default, try running(as root)
Code:
chown -R system:sdcard_rw /mnt/sdcard && chmod -R 075 /mnt/sdcard
Edit: that code messes up the permissions on one folder, after running that you should also run
Code:
chown -R root:root /mnt/sdcard/.android_secure && chmod -R 000 /mnt/sdcard/.android_secure

Just do this: download a terminal emulator from the market. Open the app. Type su and press enter. Give it root access. Type chmod 777 /sdcard and press enter.
Please note you need root to do this

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.

Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...

the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop

Did you remember to restore the read/write permissions to build.prop? It should be set to 644.

As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.

I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.

gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium

You dont have access to recovery? Either TWRP or CWM?

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.

gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium

Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.

abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.

sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.

I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk

I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.

would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?

how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk

[Q] Boot Animation WITHOUT Root -- /data/local permission denied

Hi there,
I'm looking to put a boot animation on my Nexus 7 without rooting it, similar to this thread: http://forum.xda-developers.com/showthread.php?t=1580642
When I issue the adb command, it thinks for a while and appears to be doing something and then comes back with "failed to copy 'bootanimation.zip' to '/data/local/bootanimation.zip' : Permission denied" The command I'm using is adb push bootanimation.zip /data/local
I've added adb to environment variables and my paths are also correct (bootanimation.zip is in the folder I've navigated to in cmd). I've also tried just putting bootanimation.zip into platform-tools. Is there something that I am missing that will allow me to do this, or is /data/local off limits in the N7?
I probably would've spent less time just rooting the thing, but I am trying to avoid that for now.
Thanks in advance for any insight!

i dont have a non-rooted N7 to test, but u may issue the following commands to see if u can access /data/local
adb shell
cd /data/local
ls
Click to expand...
Click to collapse
see if u get any error msg..