Related
on GDXv25 abd alfv8a have all the extra goodies for vold and all that. I change my SDCARD to a bigger one. format a partition for ext4 and leave the rest as default. On moving old stuffs back to it it seems to behave very well. Then I decide to move some of the apps to offload internal storage. The moving seems totally ok but after reboot my sdcard seems not be able to mount anymore. Go into CWM recovery and try to mount my sdcard. It says error mounting /sdcard yet I could succesfully mount my ext4 partition. At this point should I go ahead and re-format the sdcard again? What happens to those apps that I offload to the sdcard? are they toasted?
I'd to get some opinion before I re-format it since it will bring me over the point of no return. I still have no clue why all of a sudden after the moving of my apps that the partition won't mount anymore
On my linux I try to mount it via USB... it gives an error saying can't mount coz it can't read superblock. I gather some operations must have wiped into superblock. Sh*t hits the fan so to speak
by the way it is a new sdcard ... I dun think i damage it. But from CWM I can't even go ahead and format it because it says error mounting the partition.
I am amazed - I thought you don't need to mount before you can format. what's the deal here? I can't mount and I can't format?
vientito said:
On my linux I try to mount it via USB... it gives an error saying can't mount coz it can't read superblock. I gather some operations must have wiped into superblock. Sh*t hits the fan so to speak
Click to expand...
Click to collapse
That error message simply means that the ext filesystem in the sd-ext partition is kaputt and needs to be repaired (for example, manually restore a copy of the superblock) or formatted.
And that's your reason why you ran into problems ... something went wrong as you moved your old stuff onto the new card, and the next app you put onto the sd-ext finally triggered the problem.
Of course there's also the slight chance that the phone doesn't like the SD card.
finally I am able to format that sdcard by inserting into my kodak video playsport camera and format that from there! It's ridiculous that under CWM I am not able to do something as simple as formatting. That should not be a "feature" at all! Error mounting the card I could accept that but not able to format a card with screwed up superblock that's not acceptable.
With this exercise, I realize how valuable a backup it is. With all those apps xferred to the sdcard, I practically cross a bridge. Even with old usable card re-insert into phone those apps are gone and are no longer available. Only a backup (of course on a usable putaway MMC card) could have saved me all the trouble.
I still dunno what have gone wrong in the first place. Perhaps there's something I dun quite understand about moving apps to xternal storage.
Hi,
I already asked for this issue in the this Thread, but didn't got any answer.
I tested these three JB ROMS: CM10, HellyBean and SlimBean.
All of them work nice, except that my internal sdcard does not mount at boot time.
I have to do it manually every time boot up my phone by choosing System Settings --> Storage --> Mount SD card
Anyone have the same issue?
Does anyone have a solution?
Thanks
Same here! Google found this post, perhaps it will find us an answer
xalo2k said:
Hi,
I already asked for this issue in the this Thread, but didn't got any answer.
I tested these three JB ROMS: CM10, HellyBean and SlimBean.
All of them work nice, except that my internal sdcard does not mount at boot time.
I have to do it manually every time boot up my phone by choosing System Settings --> Storage --> Mount SD card
Anyone have the same issue?
Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
toddmworth said:
Same here! Google found this post, perhaps it will find us an answer
Click to expand...
Click to collapse
I have the same issue with my I9000.
Any JB with different kernels makes the internal SD eventually be unmounted. When install a JB ROM the phone works very well but suddenly, the internal SD (phone's SD) is unmounted.
In CWM both SD are mounted and read without any problem. With ICS ROMs the phone works flawlessly.
In my case, the external SD is functioning as expected.(I have a 32 GB micro sd)
The installation language is Spahish - Spain.
No matter which method of cleaning and wiping I use, the result is the same.
Also, starting from GB stock firmware (JVU) flashed with Odin, followed by installing the nightly Cianogen CM10.1 and finally flashing the desired JB ROM works.
I tested Helly Bean, Slim Bean, C-ROM Mix and Baked Blacjbean7 obtaining the same behaviour.
Important: I'm restoring around 54 apk using Titanium backup (games, applications and utilities) in every case. I did not tested the ROMs without these restorations.
marcelogabriel said:
I have the same issue with my I9000.
Any JB with different kernels makes the internal SD eventually be unmounted. When install a JB ROM the phone works very well but suddenly, the internal SD (phone's SD) is unmounted.
In CWM both SD are mounted and read without any problem. With ICS ROMs the phone works flawlessly.
In my case, the external SD is functioning as expected.(I have a 32 GB micro sd)
The installation language is Spahish - Spain.
No matter which method of cleaning and wiping I use, the result is the same.
Also, starting from GB stock firmware (JVU) flashed with Odin, followed by installing the nightly Cianogen CM10.1 and finally flashing the desired JB ROM works.
I tested Helly Bean, Slim Bean, C-ROM Mix and Baked Blacjbean7 obtaining the same behaviour.
Important: I'm restoring around 54 apk using Titanium backup (games, applications and utilities) in every case. I did not tested the ROMs without these restorations.
Click to expand...
Click to collapse
This is the problem I am having. I can see internal sd card on CWM.
But on booting in android, whatever the rom is , does not mount internal sd card on booting android.
Please help to solve this.
Same here
TheMask007 said:
This is the problem I am having. I can see internal sd card on CWM.
But on booting in android, whatever the rom is , does not mount internal sd card on booting android.
Please help to solve this.
Click to expand...
Click to collapse
I have been reading/researching about this issue for about a week (on and off) trying various fixes because this is driving me bonkers.
I have tried:
1) Reduced the amount of used space on my SD Card (Samsung 16gb SDHC) to half
2) Moved as many apps as I can to SD (Noticed more frequent unmounts after this)
3) Removed my Nandroid Back-up from my SD
4) Reflashed CM 10.1
The last thing I am going to try is wiping/reformatting my SD card. If that fails then im suspecting something else is happening at OS/kernel level. I have read in other forums where people have tried a full wipe and restore apps slowly but still get the same unmount. One user has tried another SD card (smaller 4GB one) which seemed to solve their issue?? Weird.
Anyway, I will report back if I have any joy.
In your kernel settings you have the option to mount/unmount system and more or you could write/download a script that mounts the sd card automatically.
Maybe this could help: http://forum.xda-developers.com/showthread.php?t=1971689
I give up.
cixty said:
In your kernel settings you have the option to mount/unmount system and more or you could write/download a script that mounts the sd card automatically.
Maybe this could help: http://forum.xda-developers.com/showthread.php?t=1971689
Click to expand...
Click to collapse
I tried it and no good. It seems as though the Internal SD is mounted, but some error is causing it to operate/display as unmounted via OS.
I completed more testing (extreme):
Wiped Internal SD
Wiped External SD
Try other kernel
Try other CM based ROM
The issue still occurred.
I then reinstalled Stock (XXJVT) via ODIN (Pit 512) and Semaphore kernel to see if its a hardware thing.
Nope.
This combo works amazingly. Infact its faster, smoother and easier to use (along with additional tweaks in Semaphore) than CM10 so I wont be going back to Jelly Bean on this phone. Ever.
Gingerbread for the win!
Hi,
I am using PAC-ROM v22.2 (Jelly Bean) and have the same problem: 80% boot don't mount the internal sdcard (I have no problem with the external sdcard). I can't even mount it manually as xalo2k does, cause I have no "Mount SD Card" menu under Settings/storage.
I spent many hours trying to search for a fix on google, xda, and others with no success. I found a lot of "litterature" on how to mount the sdcard on the PC, or how to swap internal and external cards. However, I don't care about mouting my sdcard on the PC, and I don't want to make believe Android that my external sdcard is the internal one, as I would not like to loose the internal 8GB that the phone is supposed to provide.
In Terminal Emulator, I can do:
> su
> mount -r -w -t vfat /dev/block/mmcblk0p1 /storage/sdcard0
> cd /sdcard
> ls -l
There I can see my files. However, if I exit root, the files don't appear anymore. Hence this looks like a permission problem.
Unfortunately ESExplorer still tells me sdcard0 is not mounted, and my apps (i.e. the camera) aren't able to access it. Additionnaly, the apps I had moved to the sdcard are'nt accessible...
So I tried to fix the permissions. Going under /storage as root, I can see:
drwx------ root root 1970-01-01 01:00 sdcard0
d---rwxr-x system sdcard_rw 1970-01-01 01:00 sdcard1
Si I try:
> busybox chown -R system:sdcard_rw sdcard0
But I get "Operation not permitted" for each dir/file in sdcard0
How comes that an operation is not permitted to the root user ???
Did anyone fix this problem ?
Edit: "You can't chown or chmod a vfat partition let alone a directory within it. You can only change ownership and permissions in fstab and it will apply to all directories and files. So to change ownership of the entire mount point you would change your fstab entry" (see http://ubuntuforums.org/showthread.php?t=1646849)
Thanks and regards
OK guys, I finally found a solution.
Thanks to http://ubuntuforums.org/showthread.php?t=1646849 I mentionned just above, I decided to write an fstab file (the name is important) and placed it under /etc:
/dev/block/mmcblk0p1 /storage/sdcard0 auto rw,uid=1000,gid=1015,fmask=0702,dmask=0702 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Basically, this script is the result of the terminal command (you need to be root):
mount | grep sdcard0 > /etc/fstab
... which I ran after I could get the sdcard mounted (after a mount on PC and eject). But it first failed with errors on options, so I removed a few of them until I kept the lines above.
Then I wrote a little script which I place on my external sdcard which does not have a mount problem at boot:
busybox mount -a
and placed a shortcut to this script on my desktop with SManager.
I just have to click on this shortcut after boot and the internal sdcard gets mounted.
I tried to place this script under /etc/init.d with the hope it would be launched automatically at boot, but this did not mount the sdcard. If anyone knows why ???
Hope this helps !
Well... still having troubles with my sdcard... With the above fstab script I can mount it, access the files, etc...
However, the camera still asks me to insert a sdcard... Is this a permission issue ? Which permissions (owner, group, etc...) does the camera need ? My DCIM dir has the following permissions:
d---rwxr-x system sdcard8RW 2013-06-04 10:36 DCIM
Thanks and regards
- Regis
Hi all,
Tearing my hair out here (and I have SFA left anyway)
My Father-in-law's SGS i9000 seems to have real issues. Initially problem I was having was that there was an app I could not uninstall- it would reappear on reboot. I initially suspected malware or such, but it appears to be a real problem with the internal memory. I had MIUI installed on it, but wanted to change to a more stock ROM.
First time I really started to worry was when I found that every time I put a new rom onto the internal sdcard, it disappeared at reboot (and thus wasn't there to install when rebooted into CWM)
Since then, haven't had a functioning phone.
adb push to sdcard still not persistent on reboot.
Cannot flash new ROM with ODIN either, although KERNEL changes, filesystem no longer mounts.
I think the version of MIUI I was using used an ext4 lagfix, as inside an adb shell, I can see the partitions:
parted /dev/block/mmcblk0
a "print" lists two partitions:
Number Start End Size Type File system Flags
1 32.8kB 14.4GB 14.4GB primary fat32 lba
2 14.4GB 16.4GB 2013MB primary ext4 lba
rm 1, rm 2
to try to delete the partitions and start again- doesn't work. Nothing happens
If I load partition 2 into parted:
parted /dev/block/mmcblk0p2
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p2: 2013MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2013MB 2013MB ext4
Can;t check any partitions as ext4 isn't supported by parted.
I cannot remove any partitions, reformat them or anything.
e2fsck errors as it cant read superblock flags on any of the partitions.
Any other ideas? Anyone?
I don't want to toss the phone out
http://forum.xda-developers.com/showthread.php?t=845708
i dont know if this will help u but u can try this guy instruction. See link above
compacity said:
http://forum.xda-developers.com/showthread.php?t=845708
i don't know if this will help u but u can try this guy instruction. See link above
Click to expand...
Click to collapse
If that worked, it would have been just what I was looking for
I googled the hell out of this problem, and that one never came up, but others I'd seen led me to try that same plan.
Where it fails on my device, is that deleting the partitions in "parted" fails- rm1 followed by rm 2 to delete the partitions. "Print" reveals they're still there.
Any other partition tools worth trying?
I got it back to square one:
Flashed kernel thru Odin with a version of CWM that worked.
reboot into recovery.
Flash update from SDcard- card contents still the same, so could re-flash MIUI.
reboot, bootloop. Re-enter CWM recovery and reflash.
Back to Square One - MIUI 1.12.16 (JVK)
Cannot install anything - nothing is persistent after reboot, even WIFI settings disappear
If it is any help to anyone who knows what they're talking about:
Now that MIUI boots I can look at the filesystem better.
Can anyone point me in the direction of what I should be looking for/trying to do to figure out what is wrong here?
try finding solution here, its PIT stop for i9000 problem
http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
Mine seems to be a bit tougher than these solutions can deal with.
Tried assorted ROMs over past day. No install works.
Cannot install anything from internal memory, as nothing dropped into that card will remain after a reboot.
Installing anything from an external card just throws up bootloops etc- as the only thing that seems to be able to retained between boots is the kernel/CWM.
If I install a new ROM, first flash says partition table is incompatible and /data will be overwritten (no problems, nothing on it). I accept the inevitable and re-select the ROM.
Reboot bootloops, as expected, reboot into CWM (now a new version with the Kernel), try reflashing the ROM image- Error 0 or 7. Try from External Memory- same. Try sideloading image. Same. All I can do is re-flash the MIUI image on internal SDcard (which works)
It looks like the internal memory refreshes itself from a recovery image at each boot? (I think).
Anyway- can't get anything to stick, except MIUI
edit:
http://forum.xda-developers.com/showthread.php?t=761537&page=3
http://forum.xda-developers.com/showthread.php?t=1230059&page=3
hav u try this 2 link as this is da only thread matches ur MBR problem
compacity said:
did u try any jb kernel out there? as its also ext4 n push it using adb. juz a suggestion though.
Click to expand...
Click to collapse
Good suggestion Logical
I'd thought that also- The JB kernels should support ext4.
No joy though
The version of CWM recovery that is stable with the MIUI install is 5.0.2.7, and it doesn't have any voodoo/lagfix options
When I flash a kernel with a CWM with lagfix, and try to use the CWM lagfix toggles, nothing changes.
Doesn't matter what I select inside CWM, it reads the status from memory as "Lagfix on, Debug off"
The reason I asked about ext4 tools in ADB is that running filesystem commands in a shell just throws up errors I can't seem to fix.
e2fsck just throws up superblock errors (on both /dev/block/mmcblk0 and the partition /dev/block/mmc0p2.
Defining one of the backup superblocks doesn't help- they're all bad.
"parted" doesn't work anymore (i note it isn't in /sbin, so I am picking this kernel doesn't install it), but even when I did have it, "parted" doesn't support ext4. Using "rm" to remove a partition did exactly nothing.
Starting to think the only way forward would possibly be flashing a custom .pit file to define partitions that move the data off an obviously bad block? Above my skill level however LOL
refresh browser see my post above again
Hello everybody
After two days of research and attempts, I finally gave up and decided to ask for direct help.
So, a week ago I rooted an Orange-branded Ace and flashed a few ROMs over the next 3-4 days to try to find the one that could suit better.
However, I screwed up something cause at some point in the process the internal sdcard was not seen anymore.
I mean, I can still go in Recovery or Download mode, flash stuff through Odin, boot without problems and use my phone.
Although, any direct access to internal storage is forbidden.
So, no rooting.
Both 2e and 3e CWM can't mount sdcard.
The type of messages I get :
When I pick "apply update from sdcard" -> E:Failed to mount /sdcard (No such file or directory)
When I rebbot after flashing -> -- Appling Multi-CSC... Installing Multi-CSC. Can't access to '/system/csc/whatever/system/'.
No way to get a USB connection either (different computer were tried), all with drivers correcting installed.
Also tried to get to the storage mass with MiniTool partition Wizard or through Disk management, but nothing.
Factory reset is useless, as well as any recovery's wiping process.
No sdcard formatting is possible.
I flashed several stock firmwares, went all the way back to Froyo, but nothing.
I wanted to try and flash a rooted stock rom, but couldn't find any /:
Hopefully one of you will come up with the fix.
Anyway, thanks in advance to everybody.
Cheers
inthered said:
Hello everybody
After two days of research and attempts, I finally gave up and decided to ask for direct help.
So, a week ago I rooted an Orange-branded Ace and flashed a few ROMs over the next 3-4 days to try to find the one that could suit better.
However, I screwed up something cause at some point in the process the internal sdcard was not seen anymore.
I mean, I can still go in Recovery or Download mode, flash stuff through Odin, boot without problems and use my phone.
Although, any direct access to internal storage is forbidden.
So, no rooting.
Both 2e and 3e CWM can't mount sdcard.
The type of messages I get :
When I pick "apply update from sdcard" -> E:Failed to mount /sdcard (No such file or directory)
When I rebbot after flashing -> -- Appling Multi-CSC... Installing Multi-CSC. Can't access to '/system/csc/whatever/system/'.
No way to get a USB connection either (different computer were tried), all with drivers correcting installed.
Also tried to get to the storage mass with MiniTool partition Wizard or through Disk management, but nothing.
Factory reset is useless, as well as any recovery's wiping process.
No sdcard formatting is possible.
I flashed several stock firmwares, went all the way back to Froyo, but nothing.
I wanted to try and flash a rooted stock rom, but couldn't find any /:
Hopefully one of you will come up with the fix.
Anyway, thanks in advance to everybody.
Cheers
Click to expand...
Click to collapse
Sdcard is an external memory, and yes you can't manage it without root permissions so when you connect your phone via USB to your pc you can't see your internal memory partition, only the external (micro sd-card).
Maybe your sdcard is corrupted, try to format it with an USB adapter and then try again
Viper The Ripper said:
Sdcard is an external memory, and yes you can manage it without root permissions so when you connect your phone via USB to your pc you can't see your internal memory partition, only the external (micro sd-card).
Maybe your sdcard is corrupted, try to format it with an USB adapter and then try again
Click to expand...
Click to collapse
Hey, thanks for the reply
Although, I'm afraid I might not have been clear.
I haven't mounted any microSD so far and I've always been able to access to /mnt/sdcard (before screwing up).
Now, after flashing anything on the device, trying to access to My Files - or whatever file manager - will result in a dead end, since no sdcard is seen by the device itself (so, for example, I have no access to DCIM, or Music, Movies, anything).
I can't format the device cause:
- the computer doesn't see it (although drivers installed), not even from Disk Manager
- general disk-formatting/wiping softwares don't see it
- formatting from Recovery is impossible
inthered said:
Hey, thanks for the reply
Although, I'm afraid I might not have been clear.
I haven't mounted any microSD so far and I've always been able to access to /mnt/sdcard (before screwing up).
Now, after flashing anything on the device, trying to access to My Files - or whatever file manager - will result in a dead end, since no sdcard is seen by the device itself (so, for example, I have no access to DCIM, or Music, Movies, anything).
I can't format the device cause:
- the computer doesn't see it (although drivers installed), not even from Disk Manager
- general disk-formatting/wiping softwares don't see it
- formatting from Recovery is impossible
Click to expand...
Click to collapse
Well, I'm gonna explain my post...In my opinion your SD-CARD is corrupted!!! so format YOUR SD-CARD, NOT YOUR PHONE!
Use an USB sd-card adapter!
Right?
Viper The Ripper said:
Well, I'm gonna explain my post...In my opinion your SD-CARD is corrupted!!! so format YOUR SD-CARD, NOT YOUR PHONE!
Use an USB sd-card adapter!
Right?
Click to expand...
Click to collapse
But you're talking about the microSD, right?
What I mean is that, at the moment, I don't have one mounted in the phone.
I've had one before having problems, but I messed up partitions, so had to format everything anyways.
But, right now, it's out of the phone.
Also, as I was saying, I cannot access common folders like Music or Downloads, nor can I drop the update.zip on the internal memory to root, and I don't think any of this has anything to do with external storage /:
inthered said:
But you're talking about the microSD, right?
What I mean is that, at the moment, I don't have one mounted in the phone.
I've had one before having problems, but I messed up partitions, so had to format everything anyways.
But, right now, it's out of the phone.
Also, as I was saying, I cannot access common folders like Music or Downloads, nor can I drop the update.zip on the internal memory to root, and I don't think any of this has anything to do with external storage /:
Click to expand...
Click to collapse
".../sdcard/music
/sdcard/downloads
/sdcard/DCIM..."
All the folders you are saying, they are in sd-card folder so.... and ROOT.zip must be in SD-CARD to flash it....
Did you try to do wipe data/factory reset and wipe cache via stock rom then when you finished to flash the stock¿?
Viper The Ripper said:
".../sdcard/music
/sdcard/downloads
/sdcard/DCIM..."
All the folders you are saying, they are in sd-card folder so.... and ROOT.zip must be in SD-CARD to flash it....
Click to expand...
Click to collapse
I'm sorry, but I might be misunderstanding.
All these folders are in the sdcard folder.
But the sdcard folder is internal, not a microSD, am I right?
When you suggest that the "SD-CARD" might be corrupted and that I should format it, are you referring to the sdcard folder?
Viper The Ripper said:
Did you try to do wipe data/factory reset and wipe cache via stock rom then when you finished to flash the stock¿?
Click to expand...
Click to collapse
Yep. I've flashed (several times) 2.2.1, 2.3.5 and 2.3.6 stocks, wiping everything before flashing and right after having flashed, but I'm always stuck with no access to /sdcard or failure to mount /sdcard..
inthered said:
I'm sorry, but I might be misunderstanding.
All these folders are in the sdcard folder.
But the sdcard folder is internal, not a microSD, am I right?
When you suggest that the "SD-CARD" might be corrupted and that I should format it, are you referring to the sdcard folder?
Yep. I've flashed (several times) 2.2.1, 2.3.5 and 2.3.6 stocks, wiping everything before flashing and right after having flashed, but I'm always stuck with no access to /sdcard or failure to mount /sdcard..
Click to expand...
Click to collapse
/sdcard = external memory = YOUR MICRO SDCARD!!!!! = THE THING YOU INTRODUCE INTO THE SIDE SLOT!! NOT INTERNAL MEMORY!!!
I'am refering to your SDCARD (above you can see what sdcard means)
And yes all these folder are saved in it
The Galaxy Ace does NOT have an internal sdcard. /sdcard is the external sdcard.
Sent from my air conditioner
CallMeVentus said:
The Galaxy Ace does NOT have an internal sdcard. /sdcard is the external sdcard.
Sent from my air conditioner
Click to expand...
Click to collapse
I hope he'll unterstand xDDD as clear as water
inthered said:
I'm sorry, but I might be misunderstanding.
All these folders are in the sdcard folder.
But the sdcard folder is internal, not a microSD, am I right?
When you suggest that the "SD-CARD" might be corrupted and that I should format it, are you referring to the sdcard folder?
Yep. I've flashed (several times) 2.2.1, 2.3.5 and 2.3.6 stocks, wiping everything before flashing and right after having flashed, but I'm always stuck with no access to /sdcard or failure to mount /sdcard..
Click to expand...
Click to collapse
Hi inthered, I think this is getting confusing.
Sd card is the external storage, where you usually have the data, music, photos, etc. Is this sd card that your Myfiles see, if it isnt there Myfiles cant see anything, cause it cant access internal storage.
To access internal storage you must be rooted and have an app that could do that. I believe you said that your phone inst rooted, so you can only see external storage and seems that it isnt there. So you cant access all that folders ( music, etc,) cause they arent there
Have to mount SD first. You can format SD with Mini tool partition Wizard, in FAT32, and use it only as external storage.
Or you can create in this external storage one partition to help manage the internal storage, but that partition wont be seen by normal apps, like Myfiles, ou PC explorer, and you need to be rooted and everything else that didnt worked first time [but it works, I guarantee that]
To finish, internal storage can only be seen in rooted devices and with some apps ( never Myfiles)
Sorry if I wrote too much, but everyone was right, it had to be better explained
Hope I helped
thanks a lot everyone.
sorry for having been insistent, but i really missed the point about the no-internal-sdcard issue (as you might have noticed).
found only today a little time to re-partition sdcard and flash, and it finally works.
thanks again
I have a new LG Optimus L90 (D415) with stock 4.4 ROM, and TWRP 2.8.0.0 (and previously, Philz 6.58.7) for recovery. Obviously, the phone is rooted and now has an unlocked bootloader....
My problem is that neither recovery will back up (or even mount) "/data". Note that I put that in quotes because, without having "/storage/sdcard" or something in front of it, I presume that it's an internal folder and not something to do with the external SDcard.
My first guess would be a problem with encryption, because both the phone and the external SD are using it -- and I never get asked for the password. Either way, the actual error in TWRP says "E: Unable to mount 'data'", while Philz says it can't access /data/philz-touch for the .ini file.
I've made several Google expeditions to find the answer, and have come up empty-handed with all of them. I've seen all kinds of fixes, from claims that I have to run chkdsk against the SDcard, to backing up the entire /data partition with a tar file and reformatting it with command line nightmares.
I'll do what I have to in order to fix this, but I'd rather not embark on an experimental goose chase. Any ideas?
I have this same problem. But only for wiping and flashing.
I have no idea for fix if backup also not working !! (Noob)
1.TWRP click backup. Select all except SDcard.
Finish backup.
2.go to Wipe menu.>advanced wipe>select all except System and Sdcard.
Wipe.
(It will skip the error files)
3.Install menu. Select ROM to flash.
Was what I did.
fear2433 said:
I have this same problem. But only for wiping and flashing.
Click to expand...
Click to collapse
I'm not flashing anything, yet. First I need to make a backup of the entire phone (not including the SDcard). That way, if something goes wrong, I can just restore my old, working configuration -- all at once -- and start over.
I can back up and restore apps individually, using Titanium Backup. But what I need here is a Nandroid-type backup... and that generally has to be done from the recovery partition. There is one other way to backup everything, using a laptop/PC and ADB. But I've never tried it, and it wouldn't protect against a ROM meltdown.
Solved, somewhat...
So I did some further experimentation concerning this error. I did a test run to install CyanogenMod, and I found that I couldn't even factory reset certain partitions because of these "Unable to mount /data/" type errors.
What was ultimately the problem? The encryption. Once I decrypted everything, TWRP was able to see, mount, and backup, those partitions.
But I was under the impression that TWRP handles encryption, e.g. asking for the password, or some such. I mean, how can you do a Nandroid-type backup on a phone, if no recovery can mount those kinds of partitions?
So, for the record: "E:Unable to mount" was definitely due to the encryption being turned on for my internal storage. Thus the solution (so far) is to decrypt storage. A wretched solution, but at least it works for the time being.
BTW, In furtherance of this research, I formatted my internal SDcard to NTFS, just to make sure it wasn't misaligned or whatever when it was just FAT32. And I discovered that NTFS takes forever to format (32GB on the order of a couple hours)., FWIW.
The plot thickens. It may not be sufficient just to undo encryption, there may be something wrong with the way that partition was created, or otherwise is constructed.
Even though I now am able to mount /data, I'm not able to format it.... in TWRP it says something like "unknown filesystem 'auto'".
But there is a thread here that describes using Philz recovery to unmount and then format this mess, and I'm about to try it, I just have to flash Philz in place of TWRP. Now let's hope this version works without issues, because I'd have little recourse if things go bad there.