[Q] Internal storage no longer available! - Asus Transformer TF700

Hi guys, I've got a little bit of a problem here, I can no longer acces the internal storage of my tf700, except through Root Explorer...
It is rooted but still locked. When I type "df" in Terminal, it says Permission Denied, next to storage/sdcard0. Does anyone have an idea on how to fix this?
Please help me
Edit:
Just tried to do a factory restore, but still no luck :/

Recently, /sdcard has been giving me a headache -- I can no longer mount it in CWM. In the ROM itself, I can access it with any file explorer without any problems whatsoever. I wonder if something has changed.
Which version of stock are you on currently? The .25?

storage issues
Tried to install a new app from Play store an got a insufficient storage available error
thats on a tf00t 32g with class 10 micro-SD 32g
runing CROMI 3.2
any help would be appreciated.

Might be worth giving this a try?
Boot into recovery, plug in the USB cable, go into adb shell, make sure that /data is mounted, then:
cd /data/media
chown -R media_rw.media_rw *

Related

[Q] HELP I need Tips for ROMless phone w/ functioning CWM

So i've spent days researching this topic, googling, forum surfing, and i've learned so much about android but now it's time to get my phone RUNNING: I'm going to put a lot of keywords in here, so forgive my wordiness. My hope is that this post will help others solve this general issue and better keywords move us up the search results. I've seen similar situations before but couldn't find a resolution for: functioning clockworkmod but no bootable rom, and i can't seem to get a bootable rom installed.
HTC Desire on verizon (CDMA/ Bravo C or bravoc)
Used unrevoked on the phone and everthing seemed to be working fine. I then tried to load a custom Rom (see below) and now i can't get my phone functioning!
I do not have a bootable ROM, but i have clockworkmod recovery v2.5.0.1 installed and functioning. i can mount the SD using USB Mount under paritions, but can't figure out how to mount internal storage. I have microsd to Usb reader so i can move files easily. I also have another functioning droid Incredible. I have formatted this microSD card using ROM manager and assigned the 4gb card to (512 ext, 32 swap) i did this after formatting on my windows PC to straight fat32.
I've loaded several roms and get symlink errors for
Official-Froyo_2.10.405.2.zip
E: can't symlink /system/xbin/su
E: Failure at line 79:
symlink /system/bin/su SYSTEM:xbin/su
Bravo_WWE_2.29.405.5_v5.zip
E: can't symlink /system/xbin/su
E: failure at line 88:
symlink /system/bin/su SYSTEM:xbin/su
32.48.00.32U_5.11.05.14.zip
Is the radio installed and seems to be working properly.
I cannot get the RUU to work for this unit because i can''t mount the internal storage drive such that the installer will detect it.
I've gotten android commander working through the SDK/ ADB but i get some kind of timeout error after a few seconds of using the program. AC will detect my phone but when i try to use it to install ROMs i get No Device Found popup.
I need to get this phone working properly even if it is back to 2.1 stock, but i can't find a ROM that isn't locked up in an EXE file to install. can someone help? I'll be responding to replys with info very quickly, i need to get this phone running for a trip!

[Q] Tiamat 1.4.0, 3g/wifi, sdcard doesnt mount on boot.

i tried hijacking the other 1.4.0 thread but got ignored and didnt want to keep a something stale that was off-topic alive.
so, i have flashed 1.4.0, verified that the kernel is in fact running. i wiped before the update to get rid of other issues i was having with some apps.
now, with 1.4.0 running, it appears that the external sdcard is not mounting while the system is booted. in recovery, it shows up as it should with all of the files. i have an /mnt/sdcard/sdcard2 and i have an an external directory under /sdcard
ive tried with card in before boot and after. i can say that dmesg is in fact seeing the card being removed and pushed in; however it doesnt seem to 'automount' from vold.fstab properly, or something else is jacked.
that being said, i dont seem to have a /devices which is where these things are suppose to be mounting from, is it not?
/sys/devices/platform/sdhci-tegra.2/mmc_host/mmc1
should i add the prefix /sys to both the usbOTG and sdcard to fix this?
or is there something else that is missing? presumably i could also create a symbolic link /devices -> /sys/devices, or does the kernel chroot to /sys at some point so none of this is needed, and i am having a different problem?
thanks for the help,
~marion
ya i noticed mine sd card is doing the same thing wont mount but works in recovery and i know it did work bc i had sdcard access through root explorer on v1.4.0 and now it does not work like it died over night
mine has not worked since moving to 1.4.0.
i originally went from 1.3.2 to 1.4.0 but the update didnt work well through the clockworkmod steps was having problems mounting e: so i went back to 1.3.1 then -> 1.4.0 [after wiping cache/data, and readding an sdcard2] using kernelmanager.
the update worked well, i rebooted to recovery and say that i could mount e:, and files where on the sdcard as expected. when booting to OS external has no files and sdcard2 has no files. also using connectbot for a shell, df shows nothing mounted.
is this because vold.fstab isnt mounting from /sys as described in my earlier post?
still unable to mount external sdcard while xoom is boote in 1.4.0.
Am able to pc-mount, and back up to it via recovery... no one else is seeing anything similar?
In 1.4.0 the sdcard should be in /sdcard/external not sdcard2. The card has to be in before turning it on. They are not hot-swappable.
Sent from my Xoom
Guys this is why Mass Storage has been removed in 1.4.1. Here's basically what's going on. When the device boots, the Sdcard is mounted to data/media/external which is the same as Sdcard/external. The Sdcard mounts before data/media is "fused" to create a virtual internal Sdcard. This is the only reason why you can actually see the external Sdcard inside the internal Sdcard. And this is why gallery can see the external Sdcard. However, in order for the Sdcard to mount as mass storage, Vold.fstab MUST mount the Sdcard at mnt/Sdcard so that Vold service can see it. But, this is the same mount point the internal storage is "fused" to. So when mass storage is done, it attempts to remount the sdcard where it was previously mounted, sdcard/external. But because of the way "fuse" works, it does not let any devices be mounted inside it. This is why I need source to do it right. I can then tell Vold to look some other place for the sdcard mount point. Until then, it's borked and that's why I pulled it.
@bwcorvus: in my first post i said that it wasnt showing up in sdcard2 or external... maybe i wasnt clear enough but its there.
@bigrush: thats exactly what i was seeing, and what i was presuming. i figured the lack of response meant either people werent seeing the issue or noticing it.
that being said... dmesg shows the device showing up if inserted/removed while running. but its showing out of /sys/devices... instead of /devices... changing that in vold.fstab didnt do anything for me as im not sure i have a great grasp on the boot sequence.
~marion
That's odd, mine mounts to external with no issue with 1.4.0

Problems with TWRP Backup - unable to mount sd/ext

I've been searching both this forum and the net generally and not found an answer to my specific problem so I'm hoping someone can help.
I'm trying to swap out my ROM, I'm currently running CM 11 nightly but I'm getting endless FCs with apps so thought I'd try something different.
When I try to run the nandroid backup with TWRP v2.7.0.1 the backup fails every time with the error E: unable to mount '/sd-ext'
Can anyone advise? Thanks
tht looks like external sd card.
Try changing location for your backup to internal memory or make sure you got SD card plugged in to SD slot.
you may also try command on terminal emulator (or via adb shell):
ln -s /storage/emulated/0/ /sd-ext/
it will create symbolic link named sd-ext in root of your system and it will point to internal storage (if I am not mistaken, from now on it should not matter if you select internal or external storage as target for your backup - it will end up as internal anyways)
Sent from my TF300T using XDA Free mobile app
Thanks, the backup was to be created on the internal SD card, but you are right it is almost certainly a problem with the external card. I'm unable to mount either the dock SD or micro SD cards in TWRP - the options are just greyed out and can't be selected.
I can't get either card to mount when I boot to system ether I have noticed. I've tried formatting them as FAT32, EXFAT and NTFS and no dice so I'm wondering if this is a KK issue - they both worked flawlessly when I was running PA and Omnirom JB ROMs.
I've managed to find a workaround - I've flashed CWM and have been able to do a nandroid backup with that - but I still can't mount either the micro SD or dock SD cards with CWM or in system when I flashed KatKISS ROM - and of course now I can't use any old TWRP nandroids I have from JB ROMs without reflashing TWRP. I'd also rather be running TWRP ultimately if I can so it would be good to get to the bottom of what is causing this issue.
Not quite sure what the command line you suggested does, but I'm guessing it won't be useful with the problem as it stands now?
sorry for late reply as I was out of internet lately.
that command creates /sd-ext/ folder that acts similar to shortcut to intertnal sdcard
any call for /sd-ext (for example: cd /sd-ext) will end up on internal sdcard.
That wont help with accessing your external sdcard (as this was main issue here) - it would merely fool installer to 'think' it is working on external sd while it was still on internal.
Sent from my TF300T using XDA Free mobile app
Thanks for your help. I've had endless troubles which ultimately ended in a hard brick during a failed flash of the stock ROM. I'm waiting for a replacement motherboard - something wasn't right with the old board anyway, it doesn't seem that it was just ROM issue. Hopefully when it comes I'll find that it wasn't a hardware issue associated with the SD cards as well.

[Q] Internal memory recovery with broken screen

Hello,
I have Samsung Galaxy Core Plus (SM-G350) with broken screen (totally black) and password set up.
I want to recover my internal card data, but any of my ideas wont work.
I have already installed CWM and tried to blindly mount /sdcard by USB, but I dont see any new drive on PC.
I wanted to root it, but any of methods I found wont work (maybe cause Im running in CWM? Yes, USB debugging is disabled).
I tried also 'adb pull', but I need to mount /sdcard (am I right?) where I get 'permission denied' error - in adb shell I cant perform any command except 'cd'.
Im thinking about flashing /data by Odin, but how to create the 'script' for it?
Anybody has any idea how can I do it?
Same Boat...
I've got a broken screen on Centura Galaxy. I managed to blindly ODIN CWM on it, and now get ADB in recovery, but debugging is off so I'm stuck with there. I've tried recovery screenshot tools to try to load rooted ROM, but had no luck. I know JUST enough to be dangerous, and not much more. Just need to get DCIM folder.
@xNombre
If this is still valid, you could try flashing TWRP onto the phone, where it should mount the SD Card automatically and it should connect to the PC automatically too. Search for TWRP (either 2.8 or 3) here on XDA

How to fix /mnt/local shows empty?

Hello, i have a problem with the internal storage of my android tablet, basically i installed a custom rom a while back but the wifi didn't work on it so i decided to go back in CWM and wipe data, cache + dalvik cache and /system, after that i restored my backup and everything went good (app installs fine from playstore and they work) but i can't see my internal storage on the integrated file manager or even from my pc, it just shows my sd card, the folder where the internal storage was is /mnt/local and now when i go there even with adb it shows empy, so with adb i went to /data/media and i tried this command i found on the internet :
mount -o bind /mnt/local /data/media
but it didn't work i still don't see anything in my /mnt/local dir
(and now after using that i don't see anything in my /data/media either)
my device is running Android 4.0.3 ICS and it is rooted, i also tried to restoring my backup again but i still have the same issue :/, before installing the rom i also created an image zip from the recovery just for safety but now im stuck as the only thing i found on the internet was one video of one person that just factory reset his phone and it worked again for him but for me it didn't, here is the video i saw, which has the same problem as me:
Thanks for the help.
Ok i fixed my /data/media directory by using umount /mnt/local, now if i do ls in /data/media via ADB all files show again but still no internal memory on file manager.
bump
bump
hello? can anyone help me please?
jonnyprogamer said:
hello? can anyone help me please?
Click to expand...
Click to collapse
hey again!did you try a different file manager?
notnoelchannel said:
hey again!did you try a different file manager?
Click to expand...
Click to collapse
yes i did, i tried zarchiver but it shows empty, and when i connect the tablet to pc it only shows one drive named "Sd Card" when before it showed "Sd Card" and "Internal Storage" folder, i think that by restoring the stock rom the mnt/local got unmounted

Categories

Resources