Hi,
I made a backup before, and restored it, so I know it worked before, but now all of a sudden I can't create a nandroid backup with TWRP 3.0.0.2 on the sd card, and there's not enough space on internal storage.
There's no option to remount /external_sd and I can't chmod 755 from the file manager. (it gives an error)
The sd card is used as adopted storage and it worked for this purpose only yesterday. Now I'm really puzzled!
TWRP
crótach said:
Hi,
I made a backup before, and restored it, so I know it worked before, but now all of a sudden I can't create a nandroid backup with TWRP 3.0.0.2 on the sd card, and there's not enough space on internal storage.
There's no option to remount /external_sd and I can't chmod 755 from the file manager. (it gives an error)
The sd card is used as adopted storage and it worked for this purpose only yesterday. Now I'm really puzzled!
Click to expand...
Click to collapse
Try a much updated version of twrp and see how it goes.
Tried again today, same version, same procedure, and now it was happy to backup to external_sd. I have no idea why, but issue resolved.
I think I found out why, if the sd card is used as adopted storage TWRP can't seem to write to it.
If it's just portable storage then it's fine.
Related
I'm having this major issue with all the 2.3 ROMs no matter what. Some apps just refuse to install when before there was no issue. It's exactly as here. http://www.androidpolice.com/2011/0...on-usb-storage-or-sd-card-problem-on-android/
I tried searching for the smdl2tmp1.asec file but couldn't find it either on the internal or external sd cards. Plus I am unable to mount the internal card on windows to search for the file.
I deleted /system/etc/init.d/11dalviklocation but that just made it worse. Now all my widgets died. I see a /HWUserData under storage settings now which wasn't there in 2.2 ROMS and I never had this issue in 2.2 ROMs.
Also, at bootup, I always see a notification in the statusbar. SD card safe to remove. And under the /HWUserData storage, I see mount the sd card. It seems the system refuses to mount the sd card or the /HWUserdata additional storage which appears under storage settings.
The only way I can install the hard to install apps is by unmounting my external sd card then installing the app which i guess forces the app to install on the internal sd card.
I installed this mod, http://forum.xda-developers.com/showthread.php?t=1112857&highlight=partition Geno's Custom you data partition's size. Could this be contributing to the problem? Is there a way to search for the file smdl2tmp1.asec file using recovery and deleting it? This issue cropped up after installing an Oxygen ROM and from then on any 2.3 rom I installed has this issue. It's bugging the hell out of me, I'm currently running CM7 and its perfect except for this issue. Help anyone?
First: try to fix permissions from recovery.
Does it mount your SD as SD or your internal sd??? Hwuserdata should correspond to your internal sd. If they are swapped, use root explorer, find fstab file and swap them again
Sent from my u8800 using XDA App
PlanDreaM said:
First: try to fix permissions from recovery.
Does it mount your SD as SD or your internal sd??? Hwuserdata should correspond to your internal sd. If they are swapped, use root explorer, find fstab file and swap them again
Sent from my u8800 using XDA App
Click to expand...
Click to collapse
I tried fix permissions in cwm 4.0.1.5 latest. Didn't work. What's the meaning of swapped? "find fstab file and swap them again". How do I do that? Where is the fstab file? closest i found is the vold.fstab file. that it?
I see this in the vold.fstab file.
dev_mount emmc /HWUserData 14/devices/platform/msm_sdcc.2/mmc_host/mmc0
dev_mount sdcard /mnt/sdcard auto/devices/platform/msm_sdcc.4/mmc_host/mmc2
That make any sense? Thanks for the reply! This thing is driving me nuts!
It seems that your sd card is damaged.
I suggest before mess with system stuff, to backup all sdcard content on your pc and format your sdcard. Then insert it back to device and try to see if the problems solved.
dancer_69 said:
It seems that your sd card is damaged.
I suggest before mess with system stuff, to backup all sdcard content on your pc and format your sdcard. Then insert it back to device and try to see if the problems solved.
Click to expand...
Click to collapse
I did that before actually. formatted my sd card. Could it be a file on the external sd thats causing it? Since I copied back everything on the sd card after formatting it.
For this reason I said to put it on before recopy anything. Maybe some of android system files/folders on sdcard are damaged.
Damn! It was the SD card after all! What a headache! I copied everything except all the hidden files on the sd card which began with (.) Now everything works fine! Can't believe it. Such a simple thing and so much problems it caused.
So can you please tell me what you exactly did. Cause i don't understand but i have the same problem too. I have no root and i have froyo 2.2.1
EDIT: i made it by connecting to the pc and deleting a file...
I tried to do a backup with CWM and it would not allow me to back it up on my external SD card. I got the error "error mounting /external_sd". So I tried doing the backup on my internal. I think it ran out of space and then failed. Now my internal is completely full and I do not know how I can recover my space. I would like to back it up on my micro SD. How can I fix these problems? Thank you.
bump
Hello,
Will try to explain the situation to my best possible knowledge :
1. Was running Crash ROM 4.4.2 on Galaxy S4 i9500 , have got all the required apps installed and configured the way I wanted.
2. Running the stock kernel which comes with the Crash ROM installation.
3. Running Phillz touch recovery 6.3.xx
4. Have external micro sd card (16GB UHC SanDisk) . Crated 1st primary partition as FAT32 and 2nd primary as Ext3 for moving apps.
5. Did install Link2SD and correctly moved all apps linked to the 2nd external SD card partition.
6. Was able to connect a USB flash drive via female USB connector (host mode) and take titanium backup of all apps.
7. Everything mounted correctly and automatically, with correct permissions to read/write without me worrying or fixing any setting or changing anything.
Since I had everything in order, I thought of making a nandroid backup via Phillz recovery . The problem when I tried taking a nandroid baclup which presents custom backup option to either "/sdcard" or "/storage/sdcard1 (which i assume refers to external microSD card".
I tried taking a backup at both locations and was informed that I am short of space , the backup needed 4+GB whereas I had 2+GB on internal SD and 3+ GB on external microSD available.
So i thought to reboot and try making some space anywhere, thats when the nightmare started.
After reboot, now there was
1. A message for low space remaining
2. Google play store continually crashing and giving a "stopped" message.
I fixed the error no. 2 temporarily by uninstalling google play store (updates, cache and then the app itself).
However error no.1 persists, now when try running any app to see what and how much space is left in the internal and external SD cards, it seems that the internal SD card is not mounted somehow.
I have tried runnning ES explorer and it says no SD card found. Even though I can browse to the root partition. Then I tried Link2SD (which has an option of seeing storage info nicely) and I can that the bar for SD card is blank and all other places or mount points are mounted.
Even the apps residing on my external microSD 2nd partition are working fine, however I noticed that earlier the external microSD card, when seen from inside a booted and loaded ROM was mounted at the location " /storage/extSDcard , but now it is mounted at "/mnt/media_rw/extSDcard"
But my internal SD card is vanished, I cannot find any contents of the "internal SD" in any of the locations at /storage , /storage/emulated/legacy, /storage/emulated/0, /sdcard, /mnt/sdcard, /mnt/obb and possibly any other location I can think of.
I believe the mount points and logical links are different as seen by the phillz recovery (as there is no /storage/sdcard1 when seen from Es explorer) , and as seen when the ROM is fully booted and loaded, so when trying to take a nandroid backup via Phillz recovery, it might have messed up with the mount points and/or permissions.
I hate doing a complete re-flash of the ROM again and spending hours to get all the apps customized my desired way, with all widget settings.
I am not an expert or pro at android, hence I request your help to sort out the issue, and maybe send or guide me the default way the S4 handles mount points, so I can get back the SD card and also guide me how to make a the nandroid backup to avoid this fiasco again.
Thanks for reading.
Yesterday I purchased Link2SD Plus for my 128GB micro SD card. Mini Tools Partition wasn't detecting though Link2SD but on converting it to system app and recreating the partition through Apps2SD worked fine for l2sd too.
After linking few apps, I tried linking one obb file of a game and warning popped up saying the filesystem f2fs needs to be converted. It went fine followed by reboot.
Now the SD storage is missing but not the partition, from storage info l2sd. Now also linking possible but not the storage.
Pls help. Only root is visible from file explorer. Can't even take a screenshot.
Thanks.
Solved it somehow because I got to reflash with another ROM. Couldn't acquire a logcat. The attached is the screen shot where it totally makes linking impossible and destructs the partition too.
Hi all I need a little help, I completed everything above without much problem, but when I flashed the newest twrp recovery, I did a backup first thing then when it was completed every file is in my internal storage and it's not showing up an sd card when I have a 16gb installed and I'm sure twrp is the step that caused this. I am still on OF1 rom. Thanks for any help!
The unlocking step overwrites the external (removable) SD card with a copy of the first 256 MB of your flash memory chip before it modifies the "aboot" partition.
A side effect of this is that the card won't mount correctly any longer without re-formatting it.
To be completely safe (you'll probably never need it), do a "raw copy" of the first 256 MB of the external SD card device to save the "debrick image", e.g. (as root)
Code:
dd bs=131072 count=2048 if=/dev/block/mmcblk1 of=/sdcard/SMN900V_debrick.img
This might take 20-30 seconds or so as you are reading and writing 256 MB of data.
Then, reformat the external SD card.
Separately, TWRP has a menu that allows you to choose between the output location for backups - either the internal memory, the external memory (SD Card), or - if you have an OTG cable, on an external USB device.
TWRP also has a file explorer if you want to move your saved backups to the external SD card. It's a little clunky, but it works. (You can also do this with a file explorer app with the phone normally booted as well if you prefer).
cheers
maybe you have to install sdfix since phones of the past couple years don't use sdcards, the system updates don't recognize cards
pltctytc said:
maybe you have to install sdfix since phones of the past couple years don't use sdcards, the system updates don't recognize cards
Click to expand...
Click to collapse
Nope, you just have to reformat the card and it'll be fine.
Sent from my SM-N900V using Tapatalk