Database Users

[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

Temp root on 2.3.20 firmware

It's not pretty, but I managed to get the exploit used by Archangel to work on the 2.3.20 firmware. Hopefully someone can think of something to automate this process, or knows of a better way to do this.
I believe what Archos is doing is simply restricting your ability to execute the Archangel application in the required directories, with the addition of the psneuter exploit, you can get around this.
This exploit requires that you have ADB setup, the Archangel APK, and the psneuter exploit.
Create a folder on your computer titled archosroot (or anything you would like)
Download Archangel from http://forum.xda-developers.com/showthread.php?t=928767 rename the apk to zip and extract the files.
From the extracted files navigate to "res" then to "raw"
In this folder copy "ls" and "su" to your "archosroot" folder
Download psneuter from http://www.thinkthinkdo.com/trac/project1/attachment/wiki/psneuter/psneuter.zip and extract the files.
Copy the extracted psneuter to your "archosroot" folder.
Enable USB Debugging on your Archos, and connect it to your computer with USB.
From a command prompt, navigate to the directory ADB is installed in.
Verify that the device is connected by running
adb devices
Your archos should be listed, if not please refer to the forum on how to setup ADB for the archos
Once your archos is detected run the following commands.
adb push pathto\archosroot\psneuter /data/local/tmp
(replace pathto with the location your archosroot folder is in, for example c:\archosroot\psneuter)
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
This may take a few moments
Copy ls and su to your sdcard
adb push pathto\archosroot\ls /sdcard
adb push pathto\archosroot\su /sdcard
Connect to the shell
adb shell
move ls and su to /tmp
mv /sdcard/ls /tmp/
mv /sdcard/su /tmp/
Execute the ls exploit
/tmp/ls 0x62c7a315 0x260de680
Install the superuser application from the market (if you don't already have it)
You should now be able to run su to get root access from a terminal.
Note 1: I was previously rooted with archangel so I already had these files, I have not tried without the files being installed at all, however since this is only a temp root, the process should be the same.
Note 2: I was not able to get Titanium Backup to work, it could be the psneuter exploit prevents the application from properly requesting the right permissions.

This is good, but you should post this in the developer sup-forum
its too hard to do this for beginners

Thanks! It's very simple instruction, will try it today. As easy as install Urukdroid.
I postponed to upgrage to 2.3.20 just due to lack of root method without SDK.
I need the root just for copy some scripts to \system\bin

this has already been done in the following thread with perm root.
http://forum.xda-developers.com/showthread.php?t=897877
Firmwares have already been made that include overclock as well, the first post reveals all.
cool.

the_Danzilla , the way you pointed to requires SDE installation. I don't want to use SDE.

Inciner8Fire said:
Download psneuter from http://www.thinkthinkdo.com/trac/project1/attachment/wiki/psneuter/psneuter.zip and extract the files.
Copy the extracted psneuter to your "archosroot" folder.
Enable USB Debugging on your Archos, and connect it to your computer with USB.
From a command prompt, navigate to the directory ADB is installed in.
Verify that the device is connected by running
adb devices
Your archos should be listed, if not please refer to the forum on how to setup ADB for the archos
Once your archos is detected run the following commands.
adb push pathto\archosroot\psneuter /data/local/tmp
(replace pathto with the location your archosroot folder is in, for example c:\archosroot\psneuter)
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
Click to expand...
Click to collapse
From what I can read psneuter is a root exploit for the adbd service. So you don't need archangel to complete the root.
Can you verify what user adbd is running after you execute psneuter.
adb shell whoami
The other thing that is mentioned in the first lines of the source code of psneuter is that it effectively disables reading the settings this will probably affect a lot of programs and probably is the reason Titanium backup is not working. So this method is effectively useless to have a working root.

wdl1908 said:
From what I can read psneuter is a root exploit for the adbd service. So you don't need archangel to complete the root.
Can you verify what user adbd is running after you execute psneuter.
adb shell whoami
The other thing that is mentioned in the first lines of the source code of psneuter is that it effectively disables reading the settings this will probably affect a lot of programs and probably is the reason Titanium backup is not working. So this method is effectively useless to have a working root.
Click to expand...
Click to collapse
I was doing some more looking and you are right that because of breaking the settings this is not a good long term root.
However I would not call it useless, since you should be able to manually back up an application.
Perhaps the property file that this setting is in can be modified with this, so that it can be rooted using a more standard method.

Not sure what I did, but I was able to get root with the properties intact.
My archos had froze today and I was forced to power it off so I know the properties were no longer be neutered. I was looking at some of the properties files and for the heck of it I tried running su from a terminal, and it worked.
I opened Titanium backup and it prompted for root permissions.
Perhaps something about the forced power cycle?

I found out that when I connect to a wireless network (as required by archangel) if the disable network shares option is chosen it's not possible to root.
However it would appear that if you connect and don't select this option Archangel will still work.
I suppose there could be something else I did without realizing it, but this has worked after rebooting 5 times so far.

[q] help needed on 6.2.1

Hi all,
I got my KF few days back, Rooted it, before I could install the android market, got forced update to 6.2.1. 2 days ago saw this new root method using BurritoRoot. Tried rooting it, seems successful, however, now when I arrived at the home page, I cant even open the Superuser app at all. It goes the same for the Root Explorer - prompting:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on. Click ok and restart the app and try again. Make sure u respond correctly to the Superuser prompt." Then it comes with a force close.
Seriously I do not know whats wrong with it, now i cant even use the root explorer for me to install Android Market.
Anybody can help me with it?
Million Thanks.

did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033

b63 said:
did you use the superuser-2.apk ?
http://forum.xda-developers.com/showthread.php?p=20645033&highlight=superuser-2+apk#post20645033
Click to expand...
Click to collapse
Im using the ROOT INSTALL - Method 1 and I downloaded the file from Rootzwiki, apparently the file is named "com.noshufou.android.su-1.apk". and I used the following commands:
adb root
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
So which means I should use the Superuser -2.apk instead?
What should I do now? Download the Superuser-2 file and repeat the whole process again???
thanks.

yes - the new version seems to be the only one working with burritoroot
consider to use KFU to make things easier:
http://forum.xda-developers.com/showthread.php?t=1399889
should be option 2 (permanent root with superuser)

[Q] After JB update, have partial root; only for existing approved apps [SOLVED]

So I seem to be having odd rooting issues, and I can't find anything that really explains it. Apologies that some of this might be obvious...
I rooted without any issues before the Jelly Bean update. Since then, I did the Voodoo Rootkeeper, updated to Jelly Bean, and have since restored root. Everything that had root before seems to still work, however, I can't provide new root access to any applications (it doesn't even ask), SuperUser can't update the SU binary, Root Checker reports me as not rooted, but I can adb shell and do "su" and that works....and the binary is clearly there with the su bits set. And things like ES File Explorer are clearly getting root access....just not anything new. Seems like I have "partial root". Any ideas on what I need to tweak?
thanks!

You did a good job of explaining the situation. I am in the same position.

Here, more information, below. Again, looks like I have su available (/system/sbin/su), but nothing seems to work...superuser is not granting root....strange. Thoughts?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2012-11-12 10:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT907 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market

I agree good job explaining. But I think a lot of us are in this situation right now. I miss the root! But also love jb (;
Sent from my XT907 using Tapatalk 2

FIXED!
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Nice,
I am going to try using SU and Superuser.apk from that site and rooting JB with those files replaced in motofail2go run.bat Think I'd still have to change permissions that way?

Not sure....I don't think so. Good luck!

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Any chance you could provide step-by-step details starting from where you pushed the files into data/local/temp?
I'm not a total novice with android but rooting is something I prefer to be very careful with! Sorry to bug you.

I had the same issue. Wiping Cache, Factory Reset, and re-root with JB exploits solved it.

I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!

RoboCuz said:
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
Click to expand...
Click to collapse
This fixed the "half-root" on my Razr Maxx HD, thanks!

[Q] Can't access ReLunch settings and TestCenterService

Hi! I don't know how it happened, I was customizing the screen buttons behaviour in ReLaunch settings and was very careful doing it. And it worked fine. But now I can't access ReLaunch settings menu when I tap on it, the screen flashes and goes back to previous screen(Relaunch file manager). The same thing happens when I tap on TestCenterService app; It was working fine before; don't know how to fix this; if someone could help please?

Use ADB and do a logcat.
That will tell you what is screwed up.

ReLaunch Settings menu disabled
Dexnet said:
... I can't access ReLaunch settings menu when I tap on it, the screen flashes and goes back to previous screen(Relaunch file manager). The same thing happens when I tap on TestCenterService app; It was working fine before...
Click to expand...
Click to collapse
Hi, I have the very same problem as mentioned: "Can't access ReLunch settings and TestCenterService". I tried a couple of things to fix it: e.g. I reinstalled ReLaunch v.1.3.8 and Nook Touch Mod Manager v.0.4.0 , I reset the button's functions to default, nothing helped...
Following Renate's advice, I used ADB and did a logcat. Unfortunately, I have no idea what is the reason. I would appreciate it very much to get some more help to understand what could happen and how to cure ReLaunch of my nook Simple Touch.... I attached the created logcat, and its alphabetically ordered version, too (logcat.7z).
Best regards, Balint.
(Budapest, Hungary)

Sorry, I don't see any unhandled intents or exceptions in your logcat.
It seems to mean that the problem is completely internal to the application.
I have no experience with this application.

ReLaunch Settings missing
Renate NST said:
Sorry, I don't see any unhandled intents or exceptions in your logcat.
It seems to mean that the problem is completely internal to the application.
I have no experience with this application.
Click to expand...
Click to collapse
Thank you very much for answernig so quick.
One more info, that yesterday I installed ADW.Launcher, and it has a Settings menu icon (I was happy).
However it neither works! Instead it returns a message, that no Settings apk is available in this device...
Have a nice week, best regards, Balint

bjuh said:
no Settings apk is available in this device...
Click to expand...
Click to collapse
Oh, well that is simple enough.
Do you see the Settings icon in the "application drawer"?
Does it do anything?
Can you ADB shell in and see:
Code:
# ls -l /system/app/Set*
-rw-rw-rw- root root 2084682 2012-12-22 13:04 Settings.apk
-rw-rw-rw- root root 39973 2012-12-22 13:04 SettingsProvider.apk
(Your dates, sizes and permissions could be different but you should see both.)

still nook settings...
Hi,
thank you again for your message.
I am still needed a little more help.
In the "application drawer" I do not have a Settings icon, instead on the ADW Config palette there is one. If I tap on it, it returns:
"Application is not installed on your phone"
All the files in my app dir have same rights like these:
-rw-r--r-- root root 1620660 2008-08-01 14:00 Settings.apk
-rw-r--r-- root root 34031 2008-08-01 14:00 SettingsProvider.apk
I tried to change, however I couldn't:
# pwd
/system/app
# chmod 666 Settings.apk
chmod 666 Settings.apk
Unable to chmod Settings.apk: Read-only file system
# cd ..
cd ..
# pwd
pwd
/system
# ls -l
ls -l
drwxr-xr-x root root 2000-01-01 05:39 lost+found
drwxr-xr-x root root 2000-01-01 05:39 etc
-rw-r--r-- root root 1248494 2008-08-01 14:00 recovery-from-boot.p
drwxr-xr-x root root 2014-07-04 00:44 app
drwxr-xr-x root root 2000-01-01 05:39 assets
drwxr-xr-x root shell 2014-07-04 00:25 bin
-rw-r--r-- root root 2279 2014-07-04 00:44 build.prop
...
(You might see, I am not a Lx expert, although I have some practice in C, LabVIEW, etc.)
Best regards, Balint

/system is normally mounted read-only
To modify anything you will have to remount it.
ADW "Settings" button does this:
Code:
I/ActivityManager( 1055): Starting activity: Intent { act=android.settings.SETTINGS flg=0x10200000 c
mp=com.android.settings/.Settings }
If you can't see Settings in the drawer then something is screwed up.
You should run a logcat and see what exactly the error is.
You can also try:
Code:
C:\>adb shell am start -n com.android.settings/.Settings

Nook settings
Renate NST said:
/system is normally mounted read-only
To modify anything you will have to remount it.
ADW "Settings" button does this:
Code:
I/ActivityManager( 1055): Starting activity: Intent { act=android.settings.SETTINGS flg=0x10200000 c
mp=com.android.settings/.Settings }
If you can't see Settings in the drawer then something is screwed up.
You should run a logcat and see what exactly the error is.
You can also try:
Code:
C:\>adb shell am start -n com.android.settings/.Settings
Click to expand...
Click to collapse
Dear Renate, thanks for all your help. Finally, I gave up fixing my Nook's system.
I re-installed my backed up system then rerouted it. Now everything works again normally.
Best regards, Balint (from Budapest, Hungary)

bjuh said:
Dear Renate, thanks for all your help. Finally, I gave up fixing my Nook's system.
I re-installed my backed up system then rerouted it. Now everything works again normally.
Best regards, Balint (from Budapest, Hungary)
Click to expand...
Click to collapse
I wonder what actually happened.