My Razr M is running BlissPop-v3.4-moto_msm8960_jbbl-Official-20150531-0035. It's been solid for a few weeks now. My external SD card is 16GB.
My external SD card (sdcard1) now has an errant file with empty date, time, and permissions. Unfortunately, it appears to be an important file, as it's called ".android_secure". Ghost Commander no longer will read sdcard1, even in root mode, as it fails on that file. Total Commander will read sdcard1 just fine, but not that file. I've tried to rename this file and change it's date/time/permissions with no success. Even in root mode, Total Commander won't touch it. I also fired up the Terminal Emulator and tried chown and chmod; both gave me a "permission denied" error even after "su".
The built-in file manager (Cyanogenmod) sees sdcard1 just fine, but doesn't show this file.
My best guess is that ".android_secure" used to be a folder, but something messed it up. I'm not sure what caused this problem as I've done nothing unusual that I've not done before. I got an error during an SFTP transfer this morning when I was copying my latest set of backup files from TiBu, but I think that has happened before. I restarted the SFTP transfer and it worked just fine. I was using Ghost Commander to do the transfer.
I have never moved any apps to sdcard1. Everything else seems to be working fine.
What I think I'll need to do at this point is unmount sdcard1, remove it, then use my desktop to delete that file. I can't do anything to it with any program on the phone. I'll do a "fsck.vfat" on it while it's plugged into my desktop (which runs Linux) and see if that shows anything.
Does anyone have any other suggestions? Thanks!
----
Update:
I played with it a bit more just now and things seem to be working, though it's confusing. I will blame whomever invented the VFAT format and Google for creating such an ugly kluge to get around its limitations.
I'm using Ghost Commander for all the following:
- In root mode, I can't look at /storage/sdcard1 without getting an error: "lstat /storage/sdcard1//.android_secure failed: permission denied"
- In root mode, I can look at /mnt/media_rw/sdcard1 just fine. .android_secure shows up as a folder "drwxrwx---" from Apr 30 23:54, and it's empty
- Not in root mode, I can again look at /storage/sdcard1 just fine. .android_secure shows up as an empty file with no date
Anyway, probably nothing was wrong, but because of this ugly kluge, somehow I ended up in the wrong place even though they all look the same.
Please give a try a new beta version of the application.
Related
With root explorer, i see that my apps are saved to something like '/system/sd/app,' but when I mount my G1, I can't find that folder. I can't even find the "system" folder. Anyone have any ideas?
Also, I pressed the "R/W" button on that folder in Root Explorer, but now I can't switch it back to R/O. It gives me an error saying, "Remount Failed: Device or resource busy."
what is it you want to do with the apps?
My gmail app is force closing, and I haven't found a way to reinstall it through market. I was going to try to replace the .apk.
I don't believe the gmail app is on the SD, it should be under /system/app/Gmail.apk
For the most part, the system apps install on the phone, the rest are on SD.
That still leads me to my first question, lol. I can't find the "system" folder after mounting my G1.
??
I don't know. I use the rooted file browser SUFBS and have never had a problem seeing the system folder.
Might have been associated with other changes you made to the system.
For me, if all else fails, I re-partition, wipe & re-flash.
Hopefully someone else can offer some better info.
I find it fine on my G1 via Root Explorer. It's just that I can't seem to locate it on my computer (i.e something like h:\system\app), after plugging my G1 in.
Sorry for any confusion.
You must be on a windows machine. You can not nativly see an ext partition under windows.
Look at the guides that tell you how to set up adb and adb push the application to the folder you want.
adobrakic said:
I find it fine on my G1 via Root Explorer. It's just that I can't seem to locate it on my computer (i.e something like h:\system\app), after plugging my G1 in.
Sorry for any confusion.
Click to expand...
Click to collapse
You can do these things right from recovery console, and probably terminal, I like recovery better though. place the file you want to use on the root of the SDcard. Since it is the Gmail.apk you want to replace you would go about it like this:
mount system
mount sdcard
cp /sdcard/Gmail.apk /system/app/Gmail.apk
reboot
thats pretty much it.
Ultimately... All I'm trying to do is put my custom ringtone on the internal memory so that it still plays correctly when the sd card is connected to my computer. (Though I certainly wouldn't mind removing the obnoxious "boot_att.ogg" file as well.) But I keep getting thwarted. First by the discovery that there's no /home directory (which kind of weirds me out, but that's a whole 'nother story).
Anyway, my phone is rooted with z4root, and I'm trying to do this by two different methods. [Correction: It would be better to say that I've tried this using two different programs] I've tried using "adb shell," and I've tried using "Android Terminal Emulator". I can successfully use su in both of them (but if I can't rewrite anything, then I don't see what the difference is). Then I go to the directory on my sd card where the cell ring is and I type
cp cell\ ring.mp3 /system/media/audio/ringtones/
And it replies
cp: /system/media/audio/ringtones/cell ring.mp3: Read-only file system
So, I found these instructions that say to use "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3" (though I think it needs to be "mtdblock7" for mine) or "mount -o rw,remount -t rootfs /" But when I do either of those, it returns
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Which I take to mean that the "mount" command isn't being used correctly (and my experience with the mount command on desktop bash is limited, so I don't have any clue how to correct it).
It's worth noting that I have the exact same results in both adb shell and Android Terminal Emulator.
So, I found another thread (I think one on XDA) that said that I need to be in recovery mode to write to /system, which kind of makes sense. But I have no clue how to do that. And Google is not helping. The only instructions I could find said to turn the phone off and hold down the camera and volume up button. Which did nothing. And it's a good thing nobody was watching because I'm sure I looked like an idiot.
So... I guess I'll have to ask, how do I get into recovery mode? But at this point, I keep coming across so many absurd things keeping me from this that I wouldn't be surprised if next I get an error.
Therefore, my question is this: Is there a way to get into recovery mode, or, alternatively, is there a way to keep my ringtone working even while my sd card is connected to my computer?
Do you have busybox installed?
Have you tried Root Explorer? It has a button to toggle read-write and read only in a folder.
I do have busybox installed. I have no idea what it does, but I installed it in an attempt to enable sideloading (which I have yet to successfully do; apparently the file isn't in the same place on the Flipside as the Captivate and I was going by a Captivate guide).
I have not yet tried Root Explorer. I know this sounds stupid since it's just four dollars, but I tend to shy away from mobile programs that cost money. (Don't know why, I've been that way since my black and white palm pilot.) But, that's just something that's weird about me, lol. I'll get Root Explorer tomorrow and come back.
Busybox is a set of command line utilities. More Info. The link in my previous post is to an installer for Busybox. Busybox provides a set of commands that can be used and many of the tutorials on modifying an android phone use them. Some don't clearly state Busybox is required.
If you are using this thread as a guide to enabling installation from unknown sources be sure to read the whole thread. In particular this post.
Mission accomplished: Root explorer worked perfectly. I saw it in the marketplace before, but I didn't know it can change read/write privileges. (I didn't get it because I thought it was going to have the same effect as Android Terminal Emulator, just without the GUI. Obviously, I am pleasantly corrected.)
And I have a correction: I did not have BusyBox installed; I had the installer installed. But it is installed now.
Thanks also for the links; sideloading is on my to-do list, after removing AT&T bloatware.
And I have one quick question: Do you (or anybody reading) happen to know if it'll be ok if I remove that boot_att.ogg file in /system/media/audio? I don't know if AT&T designed it so that the phone will crash without it, so I thought I'd ask before removing it.
adanedhel728 said:
. . . .
And I have one quick question: Do you (or anybody reading) happen to know if it'll be ok if I remove that boot_att.ogg file in /system/media/audio? I don't know if AT&T designed it so that the phone will crash without it, so I thought I'd ask before removing it.
Click to expand...
Click to collapse
I have not tried any mods of the boot sound. I would suggest that you replace the file with one that is the same name but just silence if removing it does not work.
Mounting file system as Read/Write
I too can affirm that the "Root explorer" app works perfectly for toggling the Read Only File System to Read Write.
I have a Samsung Captivate from AT&T that I upgraded to Froyo (2.2) using the official release from Samsung via the Kies Mini interface. First, I can say that was very worth it. Love 2.2 much better than stock 2.1
I rooted the phone with SuperOnceClick1.7 (had to have a Windoze OS to run that though) that I got from XDA developers and it worked like a charm. I then removed all the bloatware that AT&T likes to inflict upon its users by using "Titanium Backup." Finally, I added "Terminal Emulator" and verified that the su command was working and then "cd" to the "/etc" folder where the "PowerOn.wav" file is for the annoyingly loud startup sound is to delete it. When I issued the "rm" command to delete the file, got the dreaded "can't delete dueo the Read-only file system" or something very similar. Tried using the Android SDK via adb and that gave exact same results.
What to do?...Found this thread that gave great advice that "Root explorer" does work to toggle the R/O to R/W so the file could be deleted.
Thank you marvin02 for the great lead!!!
I have removed the "boot_att.ogg" file without any problems and went as far as swapping out the "bootanimation.zip" also without any problems. Now using CyanogenMod 5 boot animation but... haven't had any luck replacing the .ogg file for a custom startup sound. Tried encoding audio to the same specs as the original but keep getting this strange noise at boot time instead. Just thought I'd throw that in.
Quick question...
I just downloaded the free explorer from Speed which makes Root Explorer.
don't see any button to change read only to read/write. Is that a feature only in the paid Root Explorer?
Thanks from a Noob.
Edit: Just so if there are any other noobs asking... Yes, need to get the paid version to be able to write in system folders.
The free version is not able.
I apologize for what I hope only 'appears' to be a redundant question.
I created a full system backup from TWRP recovery yesterday, in preparation of flashing another radio (.33). I usually always go right in and move it to dropbox to keep my N4's storage as clean as possible. However, I waited until today, and alas, it's not there. The internal storage on my phone, as Windows reports, has indeed gone down about 2.5GB, which seems accurate from the size TWRP reported the backup would be.
Btw, I've made numerous backups with TWRP. I'm perfectly comfortable with it. I know where they are kept (well, until this one). But there's no 'backup' folder in my TWRP folder.
When I did the backup, it always requires me to use internal storage. I'm assuming it sees the N4's sdcard as internal.
Any idea what I'm missing here?
I opened my N4 in Windows Explorer, highlighted everything in the internal storage folder, and it only added up to 6.4GB. Windows reports that there is only 2GB free of 12.9GB.
wvcadle said:
I apologize for what I hope only 'appears' to be a redundant question.
I created a full system backup from TWRP recovery yesterday, in preparation of flashing another radio (.33). I usually always go right in and move it to dropbox to keep my N4's storage as clean as possible. However, I waited until today, and alas, it's not there. The internal storage on my phone, as Windows reports, has indeed gone down about 2.5GB, which seems accurate from the size TWRP reported the backup would be.
Btw, I've made numerous backups with TWRP. I'm perfectly comfortable with it. I know where they are kept (well, until this one). But there's no 'backup' folder in my TWRP folder.
When I did the backup, it always requires me to use internal storage. I'm assuming it sees the N4's sdcard as internal.
Any idea what I'm missing here?
I opened my N4 in Windows Explorer, highlighted everything in the internal storage folder, and it only added up to 6.4GB. Windows reports that there is only 2GB free of 12.9GB.
Click to expand...
Click to collapse
use a file explorer on your device to make sure that its in the twrp folder, instead of looking using windows. i bet its there and windows is having issues.
I actually have ES File Explorer installed and looked there first. Only after I didn't find it did I look in Windows. Of course if I had tried Windows first, I would have come to the same conclusion.
Ok, I've found the problem. For some reason, it's in /data/media/twrp/backups. Weird, because /data/media is the 'real' location of /sdcard, right? The reference to it isn't showing in /sdcard/twrp..., but it's in the above referenced location.
So, no problem I thought. I'd just cut/paste it into the /sdcard/twrp folder, but can't because it says there's not enough room.
I'm not good at using a command prompt to move the file from it's current location to my computer.
Any suggestions?
wvcadle said:
Ok, I've found the problem. For some reason, it's in /data/media/twrp/backups. Weird, because /data/media is the 'real' location of /sdcard, right? The reference to it isn't showing in /sdcard/twrp..., but it's in the above referenced location.
So, no problem I thought. I'd just cut/paste it into the /sdcard/twrp folder, but can't because it says there's not enough room.
I'm not good at using a command prompt to move the file from it's current location to my computer.
Any suggestions?
Click to expand...
Click to collapse
that makes sense.
cant you upload it to dropbox from /data/media/? i dont really know the command line well, so i cant help you there.
wvcadle said:
Ok, I've found the problem. For some reason, it's in /data/media/twrp/backups. Weird, because /data/media is the 'real' location of /sdcard, right? The reference to it isn't showing in /sdcard/twrp..., but it's in the above referenced location.
So, no problem I thought. I'd just cut/paste it into the /sdcard/twrp folder, but can't because it says there's not enough room.
I'm not good at using a command prompt to move the file from it's current location to my computer.
Any suggestions?
Click to expand...
Click to collapse
Try "cp -r /data/media/twrp/backups/* /sdcard/twrp/"
If it still says not enough room, try "mv -r /data/media/twrp/backups/* /sdcard/twrp"
Otherwise use adb on your computer. "adb pull /data/media/twrp/backups/"
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
deusfaux said:
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
Click to expand...
Click to collapse
I think TIBU needs a big update....I have same issue but my biggest problem is I can´t uninstall any system apps (there a some I don´t need) when I tap the uninstall button always same thing...."Cannot find the .apk file .....no problem whith my personally apk´s..?
Somebody same issue?
I ran into the same issue and solved (?) it by rebooting into recovery and doing an adb pull from there. It doesn't work from within Android like you said but once you're in the recovery partition things are different.
I think this not a problem with TiBu (or maybe it just needs an update like shivasrage said), because I can't copy my Nandroids to my PC either. I had to do a adb pull from recovery as well in that case. In fact, now that I remember, yesterday I tried to copy some backups I did in ES Explorer and some of them failed.
Android 4.3 is secure but that's messing with our old habits and making things more difficult.
Yeah but I had this problem before updating to 4.3
deusfaux said:
Yeah but I had this problem before updating to 4.3
Click to expand...
Click to collapse
Oh, that's weird. I never had this problem before 4.3.
I just went through this exact same problem with my TWRP backup files yesterday (Except in that case it was an issue with the latest 2.6 version of TWRP, not the Android OS). For Titanium Backup, I am going to have to go back today and count the files that I copied over to my PC using Windows Explorer and compare it to an adb pull under Recovery. There are so many files as part of the backup that I would never have noticed a couple of missing ones like I did on TWRP.
EDIT: Just checked and 427 files were copied over doing it each way with a full Titanium Backup (Windows Explorer or an adb pull), so it works fine for me. I am on Android version 4.2.2.
I solved the problem by installing BusyBox from Play Store (Normal install). Then, opened a command window (you can also do it using Terminal Emulator) from within my platform-tools folder in C and typed:
adb shell
su (grant permission in the phone)
busybox chown -R 1023.1023 /data/media/*
Click to expand...
Click to collapse
Now I can safely copy all files by drag-n-drop or adb pull from within android.
Cheers
Can someone walk me through solving this? I'm wanting to do a factory reset immediately, but I can't before copying over these Titanium Backup'd apps.
Why is this even happening?
ABD, ES File Explorer, everything is giving me a permission error. The latter said EACCES (Permission denied) Refused by system.
edit: nevermind. I narrowed down the offending files, and forced new backups by deleting the old ones and re-doing them. Something about the way TiBu wrote a handful of the backups was not allowing anything to copy the files.
I have a Sprint GN3. I've rooted with CF Auto Root, flashed TWRP, flashed Jellybomb, and then restored back to stock from a nandroid backup. I've come across a few different errors, and I'm not sure if they're related or not.
For one thing, when I try to download a file in Chrome, I get a "No SD Card" error, even though both the SD card and the internal storage have plenty of space.
And then for the Audible.com app, even after clearing all the data, and uninstalling and reinstalling, I get the following error:
Failed to save your library to your device. /storage/emulated/0/Audible/<snip>: open failed: ENOENT (no such file or directory)
And it's right, I don't have an Audible directory in there, or anywhere else that I can find.
So my question is: Is that likely the correct path for the Audible app to save my data, and if so, why could it not create the Audible directory there?
And could that have anything to do with Chrome not being able to see or write to storage?
Thanks.
Edit: So I tried to manually create the Audible directory in /storage/emulated/0/ with Astro, and it wouldn't let me do it. Then I tried with Total Commander, and it worked, but I also go the "Total Commander has been granted superuser permissions" popup.
Then when I run Audible, I now get a EACCESS (permission denied) error.
So did I somehow set my internal storage to read only other than for root?
Possible solution.
Hi, it has been over a year since you asked this question, but I figured I'd respond anyway. I was experiencing a similar problem (exact same error that you describe) with my galaxy s4 provided by FreedomPop - I think it stemmed from their special version of android that they pre-installed on the phone. Anyway, their support staff suggested installing and running a program called "folder mount (root)" - it ran and found 2 errors, I had to re-boot my phone, and it completely fixed my problem.. Hope this helps
Glad you posted. Not much info out there on this issue, and your fix worked. Thanks.