I'm trying to run rsync to backup files from my new Nexus 7, including the contents of the Titanium Backup directory. I've checked the directory, and ls -l shows all files with rw-rw-r- permission, but rsync gets "permission denied" errors when trying to read the .tar.gz files (it has no problems reading the .properties files which show up in ls with the exact same permission).
Does this seem like some new kind of wacky security feature in 4.3, or am I missing something obvious and stoopid?
On a possibly related note, SuperSU just spun for 5 minutes trying to update the su binary. Rebooted and told it to update the binary using recovery, and that worked fine.
I mailed Titanium track about this, and got a reply saying they were aware of the problem and are working on a fix, but I still don't understand what the actual problem is. Has Android 4.3 adding some sort of additional ACLs or started using existing ones differently? What can I use to view them (if they are there). I'm really curious to know what the heck is actually going on.
If someone could solve this issue, I would greatly appreciate it.
Related
I flashed Wallet on using the zip method. I recently tried using it on a vending machine just to kicks and on a tap, it worked just fine. However, as soon as it initiates the transaction, Wallet force closes. The transaction still goes through.
Since the .apk method is available, I wonder if installing it using that would solve the problem. Is there a way to uninstall the Wallet I currently have? Or is there a fix for this issue that I'm not aware of?
TofuWarrior said:
I flashed Wallet on using the zip method. I recently tried using it on a vending machine just to kicks and on a tap, it worked just fine. However, as soon as it initiates the transaction, Wallet force closes. The transaction still goes through.
Since the .apk method is available, I wonder if installing it using that would solve the problem. Is there a way to uninstall the Wallet I currently have? Or is there a fix for this issue that I'm not aware of?
Click to expand...
Click to collapse
You should be able to use apps like File Expert or Root Explorer to navigate to /system/app/ and delete wallet.apk. You could also do it with adb in the terminal: adb shell
cd /system/app
rm wallet.apk
I have heard of some problems regarding the "secure element" though, so you might want to try backing it up along with its data with something like Titanium Backup. I don't know enough about the problem to say if that is necessary.
synesthete said:
You should be able to use apps like File Expert or Root Explorer to navigate to /system/app/ and delete wallet.apk. You could also do it with adb in the terminal: adb shell
cd /system/app
rm wallet.apk
I have heard of some problems regarding the "secure element" though, so you might want to try backing it up along with its data with something like Titanium Backup. I don't know enough about the problem to say if that is necessary.
Click to expand...
Click to collapse
Ah. Since I have GW working already, I don't want to risk screwing up my phone. Is there a way to get it to stop FC when I make a transaction?
Delete the .apk. It won't ruin your phone.
need a real way to reset the secure element
I installed via zip ... used Root Explorer to remove it tonight and even did the adb command to reset the element -
Code:
am broadcast -a android.intent.action.MASTER_CLEAR_NOTIFICATION [/indent]
I can download the Wallet app from Market which is great (thank you AT&T and Google) but I am getting the insufficient privileges error -
Insufficient secure element priviledges for this system image (release-keys).
Any thoughts on how to clear that ??
Hey-
I've been playing around with the shell, installed bash 3.2 according to this:
forum.xda-developers.com/showthread.php?t=537827
aaaand I was trying to make a link from /system/bin/sh to /sdcard/bash but it didn't take. The reason I want to do that is because I'm experimenting with bash 4.1 and it hasn't quite worked. But when my shell breaks I have to wait for a restore because I can't get write access to the dang /system folder (I guess you need the shell for that).
I know it's not that huge of a deal to have it all in the /system folder once it's how I want it, but I'm going to be playing with other stuff too (bash_profile, etc) and it's a bit of a pain doing the whole trial/error thing. Well, at least with how long it takes. I'm doing trial/error anyway.
So my question is why wouldn't that link work? I know I'd set the link up correctly, tried it several times in case I had a typo. Maybe I just don't understand symlinks like I think I do. I tested also something where I tried to make a link within only the /sdcard folder (always writeable no matter what, thinking that had something to do with it) and just got "operation not permitted". But on my linux box a link between directories is totally cool. Not sure what the difference is. Any help appreciated.
Something else I'm seeing that I really don't understand is that I can create links just not that have to do with my /sdcard partition. I can't even change permissions in /sdcard. From ADB. I run as root:
chmod 0644 filename
and it's as if it accepts the command, but perms stay the same. I did it not as root but it said operation denied. Why if I've got root can't I do some of these operations in /sdcard?
Scooterx3 said:
Hey-
I've been playing around with the shell, installed bash 3.2 according to this:
forum.xda-developers.com/showthread.php?t=537827
aaaand I was trying to make a link from /system/bin/sh to /sdcard/bash but it didn't take. The reason I want to do that is because I'm experimenting with bash 4.1 and it hasn't quite worked. But when my shell breaks I have to wait for a restore because I can't get write access to the dang /system folder (I guess you need the shell for that).
I know it's not that huge of a deal to have it all in the /system folder once it's how I want it, but I'm going to be playing with other stuff too (bash_profile, etc) and it's a bit of a pain doing the whole trial/error thing. Well, at least with how long it takes. I'm doing trial/error anyway.
So my question is why wouldn't that link work? I know I'd set the link up correctly, tried it several times in case I had a typo. Maybe I just don't understand symlinks like I think I do. I tested also something where I tried to make a link within only the /sdcard folder (always writeable no matter what, thinking that had something to do with it) and just got "operation not permitted". But on my linux box a link between directories is totally cool. Not sure what the difference is. Any help appreciated.
Click to expand...
Click to collapse
it's about a fat32 part? then will not work
You should post a log
Thanks, I was poking around somewhere and saw that other people have had problems if it's using a windows format. However, I'm burning my brains out trying to figure out how to see what format it uses and how to then change the format. It's the Samsung Galaxy S, and it's an internal memory card. I wouldn't think I could format it from my computer, it's not removable. Or else I'd have found out already using gparted or something (in fact I tried, said 'unallocated' is all). I *perhaps* could use gparted to format it as ext4 or whatever though, but I'm not sure the effect that'll have. I'd have to do some research.
In any case, I'd love to post a log but I'm not sure what log that is that you're referring to, would you mind telling me how to get that?
Scooterx3 said:
Thanks, I was poking around somewhere and saw that other people have had problems if it's using a windows format. However, I'm burning my brains out trying to figure out how to see what format it uses and how to then change the format. It's the Samsung Galaxy S, and it's an internal memory card. I wouldn't think I could format it from my computer, it's not removable. Or else I'd have found out already using gparted or something (in fact I tried, said 'unallocated' is all). I *perhaps* could use gparted to format it as ext4 or whatever though, but I'm not sure the effect that'll have. I'd have to do some research.
In any case, I'd love to post a log but I'm not sure what log that is that you're referring to, would you mind telling me how to get that?
Click to expand...
Click to collapse
If you work in adb post console output the same if you made that symlink from phone shell
do not forget to switch to root ("su" command )
by this you get part info
Code:
cat /proc/mtd
or system log here
Code:
adb logcat -d > logcat.txt
- it's saved to adb folder
(do not blame me if you already know these things)
also here is an interesting thread
maybe that part is mounted as read-only ?
make things simple as possible use Root Explorer/ES File Explorer (just tap screen to mount r-w)
Thanks, I liked that article you'd mentioned. Though I also tried the suggestion that was provided when I realized that /sdcard/ is really just /mnt/sdcard/ but still no dice.
I checked those logs, didn't see anything relevant. They're attached so if I just don't know what I'm looking for then someone would see it?
The /sdcard isn't read only, I'm able to write files to it.
I'm thinking really that it's just a windows format, but I still haven't an idea how to actually prove that, nor do I know how to format it for linux. Again- it's not removable. Anyway, if there's something that I need to see in the log, it'd be appreciated if you could point it out to me, thanks.
Scooterx3 said:
I'm thinking really that it's just a windows format, but I still haven't an idea how to actually prove that, nor do I know how to format it for linux. Again- it's not removable. Anyway, if there's something that I need to see in the log, it'd be appreciated if you could point it out to me, thanks.
Click to expand...
Click to collapse
-nothing interesting in log file
(a mount/df output is better here)
-also post this problem in Galaxy S I9000 sub-forum
I think your internal sdcard is vfat-type then try to format as ext4-type
here is a good article on this problem
Initially I thought this was a problem with Google Play / Apollo, but I realize now that when I plug in my phone via USB, I can't see any of the many, many folders and files present on /sdcard that I could see previously.
If I copy a "new" mp3 onto my Galaxy Nexus, it's recognized just fine by both Google Play and Apollo. However, none of my old mp3s (or files, for that matter) are recognized. They were placed in /sdcard/Music, a folder that I cannot see when I plug in my phone, only from the file manager running on the phone. The issue persists if I move an "old" mp3 from my music folder out into the sdcard root, it's still not recognized. This makes me think this might be permission related, but the file manager says that all files are readable and writable.
I've tried running "fix permissions" in both ROM manager and the CWM recovery, but it makes no difference. Any idea what has happened, and how to fix it so that I can use all my old files again?
edit If it's any help, I just ran ls -al in a terminal emulator and I can't see any difference at all between folders I can and cannot see. Example: I can see /sdcard/media just fine, because I created that folder from Explorer in Windows. Music in that directory works. I cannot see /sdcard/music. Here's the permissions:
Code:
drwxrwxr-x root sdcard_rw 2012-09-18 media
drwxrwxr-x root sdcard_rw 2012-09-16 music
This is a bit confusing.
When I try pulling and pushing a file with adb like so:
Code:
adb pull file.tar
adb push file.tar file2.tar
I get
Code:
failed to copy 'file.tar' to 'file2.tar': Read-only file system
I've tried remounting /sdcard in root terminals both on the phone and via adb, but I get mount: Operation not permitted. I'm thinking this might be because /sdcard isn't the actual path but I've tried /storage/sdcard0 and /mnt/sdcard as well and I get the same error.
Thanks in advance for any suggestions.
(This question was also posted on android.stackexchange)
adb push /sdcard/file2.tar
also, cm doesnt have root access enabled by default for adb.
/sdcard/ is already rw, otherwise apps couldnt place anything there. nor could we.
Sent from my i9250
Didn't realize I needed an absolute path, thanks! I now managed to push the file, but it does not show up under the "Galaxy Nexus" unit in My Computer. It does show up when I do an ls in adb shell though. Any ideas?
bajsmumsaren said:
Didn't realize I needed an absolute path, thanks! I now managed to push the file, but it does not show up under the "Galaxy Nexus" unit in My Computer. It does show up when I do an ls in adb shell though. Any ideas?
Click to expand...
Click to collapse
try disabling mtp on the device; or rebooting, if you want to stick with mtp. maybe it has to refresh file list?
bk201doesntexist said:
try disabling mtp on the device; or rebooting, if you want to stick with mtp. maybe it has to refresh file list?
Click to expand...
Click to collapse
Switching from MTP to PTP does nothing, the same files are shown ("new" files). I'd like to stress that if I take a picture for example, that pictures does show up both with MTP and PTP. New files work fine. It's the old files that I can see in the file explorer in the actual phone that just refuse to show up when I connect to my computer, and they are obviously also not recognized by apps in the phone (such as Apollo or Google Play).
I realize that I could work around this issue by just removing everything from my sd card and then putting it back, but I really want to figure out how this can even happen.
I'm no expert by far, but it sounds like when you changed ROM the"index"file for mtp isn't updates. Have you tried to run the media scanner?
Swype'ed on my CM10 Galaxy Nexus
Herman76 said:
I'm no expert by far, but it sounds like when you changed ROM the"index"file for mtp isn't updates. Have you tried to run the media scanner?
Click to expand...
Click to collapse
If I've understood correctly, power cycling the device should trigger the media scanner. I just tried restarting, and it made no difference. (I've restarted the device several times since this problem occurred).
Opening the Gallery app still only shows me two pictures (I've taken two photos since the ROM flash), interestingly the thumbs are for other pictures lying around and after a while Gallery crashes. I use QuickPic more often though and that app behaves well, and shows all photos.
edit As a final resort, I tried doing a full wipe and reinstalling CM10 M1 completely, without restoring any settings or apps from any old installations. The issue still persists! Any files created with my now "old" CM10 installation no longer appear, even when they are moved within a folder where other "new" files are shown and working. This is starting to annoy me, but since this obviously is a bug in CM10 M1 I see no point in trying to spend time solving it, I'm just going to switch back to AOKP. Thank you for any answers and attempts at solving this.
edit2 Formatting /sdcard in CWM recovery fixed this, even though it might not be the most elegant solution.
Have you seen this?http://forum.xda-developers.com/showthread.php?p=30288268
Basically what it suggests is that you go to apps via settings, find the "Media Storage" app (it's a system app) Clear data/cache, then reboot. This was my problem.
Sent from my Galaxy Nexus using xda premium
Hello fellow XDAers,
My wife replaced her Samsung Gravity Smart with the T-Mobile MyTouch Q, AKA the Huawei U8730 (not the older LG C800 model w/ the same name). She gave me the task of cleaning the junk APKs off of it to de-clutter it.
Rooting the phone was the first task. This method worked perfectly for me without any fuss (the app will return error 64, but after installing Superuser and rebooting, I had root access). I was able to use Titanium to remove much of the crap ware, but the most annoying bits gave the error "cannot find APK." Weird.
After digging around, I took an inventory of the apps in /data and /system.
The T-Mobile junk wasn't there.
I threw busybox on the phone and used the 'find' command, and I found where the apps were hiding: /cust/t-mobile/us/apps, which is a loopback-mounted ext3 partition. I tried to remount it read/write, but got 'permission denied' error. I figured something had the filesystem locked, so I ended all the apps that were running and tried again, but no luck.
However, I was able to remount the volume that held the ext3 image file read/write. It mounts to the /.cust_backup directory.
IMPORTANT NOTE: For those who will be following these steps themselves, at this point you will want to make sure to go into the Applications manager and uninstall any updates downloaded for the crapware you are going to remove. I will explain why below. It's not absolutely critical, but it will save you some head-scratching.
I remounted the partition read/write, grabbed the image file (located in /.cust_backup/image/cust.img), and uploaded the image file to a linux server.
On the linux server, I mounted the image, nuked the unwanted APKs, and unmounted the filesystem.
I created a backup of the original cust.img file, then overwrote the one in /.cust_backup/image
Last step was to reboot the phone, and most of the junkware was gone.
Here's where the head-scratching came in. A couple of the apps were still there, and I didn't know why. I double-checked the phone, and the APKs were in fact deleted. Then I realized: the app had received an update and I was seeing the update. When I uninstalled the update, the uninstall "failed" but the icon still disappeared. However, I had to reboot the phone again to fully remove it.
So, here's the process in a nutshell:
1. Uninstall all app updates for the crapware you plan to remove
2. Root the phone using This method .
3. copy down /.cust_backup/images/cust.img
4. Using a linux system, mount cust.img as a loopback device, then delete the unwanted APKs (they will be in t-mobile/us/apps)
5. Unmount the image (this writes your changes back into the cust.img you mounted in step #3)
6. On the phone, remount /.cust_backup r/w
7. overwrite /.cust_backup/images/cust.img with the modified version
8. Reboot the phone
That's it! Enjoy your uncluttered phone!
I know it's been a while since the original post, but I was wondering if OP has had any problems with the phone since then, or if anyone else has tried this with the Huawei u8730 and had success. My wife also wants all this crap removed from her phone, but she would probably murder me if I bricked it in the process.
Thanks!
Just on a side note here as I'm still using this device. How did you get around the non-working tethering on this device? Both the USB and Wifi hotspot won't work unless you've subscribed to the T-Mobile Smartphone Mobile HotSpot app option on your account? Mine is unlocked and being used with another carrier, but only recently wanted to tether to it so I can't figure out how to correct this one. Also still looking around for any working custom ROM for this. Thx.
Here is my issue I cannot create folders or delete anything on the internal sdcard.
Background info: I just got this gs3 its on boost mobile. I am on NJ3 I used CF-auto-root method to get root. Everything went fine updated Supersu installed a bunch of apps including Titanium Backup and made backups of all apps on the phone. Everything finished fine. I have not deleted any apps yet nor have I installed a custom record very or any ROMs its still!l stock. I have a 64gb sdcard installed which is new and empty so I wanted to put my backups on it but could not. While looking for a fix I noticed that even the default INTERNAL sdcard had a red folder on top with "cannot write to this location" . so now I cannot use TB. It gives an "insufficient storage" message and fails
I then went to ES File Explorer and tried to make a folder on the internal card and could not, also tried to delete and could not !! I have Googled this problem and come up with a number of solutions but most are very old threads. Can anyone give me some help fixing this? The phone seems to otherwise work but I fear it will only get worse with time.
edit I can install apps though even now.
Oh I left out that I did recieve an update for Security policy update. Which I understand has something to do with SElinux. I also found a fix for what appears to be my problem related to this it is;
SU
restorecon -FR /data/media/0
I decided to try it but get a message that -F is invalid
syntax is restorecon (--nRrv-- )
From what I can google the version of restorecon I have on my phone does not include that switch!!! Just my luck, can anyone help me figure out if I can change the binary to an updated one so I can use this?
Well I am disappointed 45 views and not one reply, oh well.
I eventually bit the bullet and did a factory reset from the settings menu, it cleared up the issue and I still had root!! Google reinstalled all my apps and SuperSu disabled Knox for me. I also unchecked auto update for security updates so that Samsung does not send another one to me without my knowledge. also disabled autoupdate for Samsung apps.
know everything is golden again.