Wiped Internal Storage via TWRP - Having problems with Internal Storage! - HTC Droid DNA

Now I'm in worse case, in attempts to try and fix and issue about not seeing some files in MTP and only via Recovery, I thought well I will go into recovery, backup the files I want from the Internal Storage to my PC, wipe the internal storage in TWRP and copy back my files and flash my rom again. Well, I backed-up my files then wiped the Internal Storage and know I can't do anything with my Internal Storage, it's completely empty and I can't copy anything back not create folders or anything, the phone does boot to my ROM but I can't copy back any of my files, any Idea on what I should do?
Update: Since I could boot to my ROM I went into settings and did a Factory Reset with Wiping SDCard option and after it did the whole factory reset and the phone booted again the Internal Storage got fixed... I'm never again formatting the Internal Storage from Recovery...
Update: Well it sort of fixed it... I can see the MTP (Interal Storage) when in recovery Mode but I can't see it at all in normal system. Also I flashed the ROM again and now I can't install any app from my storage, I will try later when I get home to see if I can install from the market. Strange enough as soon as it boots I get "Unfortunately, System UI has Stopped" and when I try to install an app from my storage the message "Unfortunately, Package Access Helper has stopped" comes up and then it won't install.
I'm Attaching a logcat and after a quick read I found this after trying to install my TB Pro APK:
E
D/PackageManager( 840): installPackage, path:/storage/emulated/0/App_Backup_Restore/Titanium Backup PRO-com.keramidas.TitaniumBackupPro-8-v1.3.0.apk, flags:0, installer:null, uid:10129, pid:8134, user:UserHandle{0}
E/sdcard ( 335): opendir /data/media failed: Permission denied
E/sdcard ( 335): opendir /data/media failed: Permission denied
E/sdcard ( 335): opendir /data/media failed: Permission denied
E/cutils ( 8165): Failed to mkdir(/storage/emulated/legacy): Permission denied
W/Zygote ( 8165): Failed to mount emulated storage: 13
E/Zygote ( 8165): Cannot continue without emulated storage
Click to expand...
Click to collapse
After I saw the above I when into adb shell and moved to /storage/emunalted and there I used SU then did mkdir kegacy and chmod 755 legacy, it created the legacy folder and it seems to have fixed the SystemUI crash, the Package Installer crash and the Internal Storage not showing up in Windows.

Well it seems that there was something wrong with my /storage/emulated/legacy folder, because now it seems that after having to re-create it and do chmod 755 on it everything is working as it should and it seems that I'm seeing all the folders I should be seeing via MTP in Windows.

Related

[Q] Installing large app to sdext2 fails due to internal storage limitation

Hi,
I have a Nexus One running the latest CM7, and a 32G sdcard with 3G partitioned for sdext2. I use Link2SD to link or move apps to the ext partition. My current free storage info:
/data (on device storage) - 107M
/data/sdext2 - 2G
/cache/download - 107M
/mnt/sdcard - 22G
Everything works as expected until I try to install an app larger than the available internal storage (a number of Humble Bundle apks are quite large). The install fails on the phone, and using adb to install gives me this error:
Code:
[email protected] /A/A/s/platform-tools [1]>
./adb install -e ~/Downloads/SwordAndSworcery-android-1.0.16hb_1380585044.apk
failed to copy '/Users/am/Downloads/SwordAndSworcery-android-1.0.16hb_1380585044.apk' to '/data/local/tmp/SwordAndSworcery-android-1.0.16hb_1380585044.apk': No space left on device
rm: can't remove '/data/local/tmp/SwordAndSworcery-android-1.0.16hb_1380585044.apk': No such file or directory
As I understand it, Link2SD is only links/moves an app after it has been successfully installed.
Is there a way to install this "directly" to the sdext2 partition, or perhaps link the /data/local/tmp to the sdcard?
Thanks,
Todd

[Q] Unable to delete files in /storage as root?

After reformatting (keeping the sdcard partition) and reinstalling android on my rooted Moto X, Titanium Backup stopped working saying "insufficient free space". When I check space on the device it's got plenty.
As a test, when I tried to delete /storage/emulated/0/TitaniumBackup/org.mozilla.firefox-20140326-060005.tar.gz I get the error
rm failed for TitaniumBackup/org.mozilla.firefox-20140326-060005.tar.gz, Permission denied
Click to expand...
Click to collapse
Checking the file permissions, it looks like it's writable
Code:
1|[email protected]:/storage/emulated/0 # ls -l TitaniumBackup/org.mozilla.firefox-20140326-060005.tar.gz
-rw-rw---- root sdcard_r 5048353 2014-04-10 07:58 org.mozilla.firefox-20140326-060005.tar.gz
But just to be sure, I ran
Code:
chmod 777 TitaniumBackup/org.mozilla.firefox-20140326-060005.tar.gz
Which didn't seem to make any difference
When I run mount, it appears to be writable.
Code:
/dev/fuse /storage/emulated/0 fuse rw,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Other apps are able to write to the sdcard partition, as best as I've noticed the /TitaniumBackup/ directory is the only one not working.
Is there anything else I can try other than completely reformatting my phone?
I rebooted into recovery and opened an adb shell while my phone was in recovery.
From within recovery I was able to delete the TitaniumBackup directory with no problems.
After I booted back into normal mode, I cleared all app data for Titanium Backup from Settings > Apps > Titanium Backup and then started up the app again and everything worked!

root cannot read from /storage/sdcardn/; su error: could not open file

Trying to copy files from /storage/sdcard to the /system partition. Landvo L200 running Android 4.4. Rooted. Kitkat SD fix in place (in platform.xml, the media_rw-group is added to WRITE_EXTERNAL_STORAGE). This problem is about _reading_ from SD rather than writing to it.
Using adb, I can do su and become root. As root, I can remount /system as rw and rename files on it. But when I go to /storage/sdcard0/ or /storage/sdcard1/, I cannot see any of the files there. When I drop back to the regular user (so not root), I can see the files on both the /storage/sdcardn/.
Using Total Commander, exactly the same seems to happen, because I can rename files on /system (TC gets root and automatically remounts in rw), but I cannot copy a file from one of the sdcards to /system/<whatever dir>. I get as error message: su error: could not open source file. Apparently this was reported before, without resolution: http://www.ghisler.ch/board/viewtopic.php?t=38910&view=next
Anyone knows a workaround to this?
{EDIT} ES file explorer _is_ capable of copying from /storage/sdcard to the /system partition. How do they do it?

NX501 not mounting internal SD

For some stupid reason I tipped in adb shell rm 25 rm 26 and now my internal sd card doesn't mount.
On CWM appears the following error E:stat: Error 1 on file /dev/block/platform/msm_sdcc.1/by-name/grow.
I'm unable to mount /sdcard and /storage/sdcard0.
The system storage appears to be fine since I can still access cm 12.1.
Any thoughts on how I should resolve this issue?

rooted phone, corrupt file can't delete permission denied

I have a Motorola Edge+ 2022 phone that I rooted with magisk.
I was in the process of copying files from a USB flash drive to the phone's storage, when suddenly a file stopped copying in Magisk. It's actually an empty folder now.
I am unable to do anything with this empty folder. I can't delete the empty folder (rm -rf) in Magisk or in ADB. If I try to delete it in ADB I get a permission denied error.
I've tried setting the permissions to 777 but I am unable to change the permissions. I've also tried installing Termux, then using a root terminal in Termux to delete it but that does not work. I also tried to rename (move) the folder in Termux and I get an interesting error: "Math result not representable".
Any thoughts?
navigate to /data/media/0 and try again
aIecxs said:
navigate to /data/media/0 and try again
Click to expand...
Click to collapse
That worked!!! Why does it work, is it because that mountpoint has different permissions?
/data is mount point of underlaying block partition with (kinda) raw access to ext4/f2fs file system, while /storage/emulated is sdcardfs file system emulated on top of /data/media for MTP compatibility. yes, additionally isolated mount namespaces, SELinux or disk quota may disturb disk access as the permissions differ.

Categories

Resources