Hi all, I tried searching through the forums and I wasn't able to find a solution and was hoping you could help me out.
I recently tried flashing a custom rom and because it was giving me problems, I decided to go back and recover from my back up.
But everytime I tried, it tells me that "Couldn't open directory. No files found."
I found this to be odd, so I rebooted back in the rom and tried to see if I could go through the N7 to put a new .zip file to flash.
When I go into Nexus 7 in My Computer, it just shows up blank.
I'm guessing there is something going on that messed up my ability to access the device storage.
If I go into mounts and storage in CWM, my /sdcard and /system are not mounted.
So I tried mounting both. /system mounts up just find, but /sdcard doesn't.
I'm not sure if this is significant, but in CWM, if I go to "install zip from sd card" -> "choose zip from sdcard" it doesn't show up what it used to which was just all the folders and such in my N7.
It now shows, 0 /, clockworkmod/, legacy/ and obb/...
I also tried to reinstall all drivers on my computer in case that was what was causing an issue. But it didn't fix the problem.
Does anyone have a solution?
The device itself seems to be recognized by my computer..
Would I be able to use the Nexus 7 tool kit to flash back to stock to unroot again?
Thank you in advance!
I had a similar problem, but it was a while ago. Can't quite remember but I think uninstalling the drivers, unplugging the device, turning off usb-debugging and then plugging it back in fixed it. YMMV.
Hope it helps.
rotarynerd said:
I'm not sure if this is significant, but in CWM, if I go to "install zip from sd card" -> "choose zip from sdcard" it doesn't show up what it used to which was just all the folders and such in my N7.
It now shows, 0 /, clockworkmod/, legacy/ and obb/...
Click to expand...
Click to collapse
I believe that is significant. With 4.2.x, the "SD card" mount is now supposed to happen at
/data/media/0
instead of
/data/media
I use TWRP (not CWM) but I too experienced a "missing backup" issue, and then later found it at
/data/media/TWRP
rather than
/data/media/0/TWRP
If I were you I would poke around using a root file explorer and see if you have backup data in either
/data/media/clockworkmod or
/data/media/0/clockworkmod (or even)
/data/media/0/0/.../0/clockworkmod
then (a) use a recovery which can succeed at "mount /sdcard", and (b) move the clockworkmod folder using your (root-aware) file manager so it is within the /sdcard mount point of the recovery.
There has been some recent flux in the past few months with buggy behaviors in custom recoveries, including that 0/0/0.../0 phenomenon; it might be time for you to upgrade your current recovery to a newer version.
usually a mount failure happens for only one of two reasons:
- the mount point doesn't exist, or
- the file sysem is corrupted.
Seems improbable that it could be the 2nd of those issues - the "/sdcard" mount point is a little bit odd - it is sort of like a "hard link" or loopback mount with some behaviors that mask the underlying (true) file ownership information. If the underlying /data (ext4) filesystem was corrupted, then /data itself would also not be mounting. That would certainly wedg your ROM boot though, and it sounds as if your ROM is operating adequately.
Note that the possibility does exist that you simply erased or formatted your entire /data partition at one point or another and those backups actually got erased.
good luck
Related
I (along with other people) find it weird that Asus chose to mount the sdcard to /Removable/MicroSD instead of the traditional /mnt/sdcard.
I would like Titanium Backup to store the files on my sdcard instead of the internal memory, but the problem is that TI only checks the /mnt/sdcard directory. So in my infinite geek knowledge I had the idea to symlink /Removable/MicroSD/TitaniumBackup to /mnt/sdcard/TitaniumBackup. The problem is that FAT32 doesn't support symlinks, so I formatted the sdcard to NTFS and popped it back in but it wouldn't mount it, which I realized was because it doesn't have the NTFS modules. So I popped it back out and formatted it as ext2, but it still wouldn't mount automatically and I couldn't mount it manually because I didn't know what the device name was.
Anyone have any solutions?
You can try ask the developer of TitaniumBackup to include support for asus TF.
Obviously I already did that but I'm looking for a fix on my end.
As with most other tablets, the internal SD is mounted to mnt/sdcard so external SD has to be mounted elsewhere.
As far as TB goes, you can choose where to store backups. Have currently got it setup to backup to Removable/MicroSD/TitaniumBackup
EDIT: If you go into TB preferences menu, scroll down to Backup folder location, then press the Back icon (the system one) to get back to the root folder. Then you can choose the Removable/MicroSD/ folder. Click on "create a new folder", call it what you want, then open that folder. Click the "Use current folder" button and there you go...Backup folder on external SD!
Took me a while to realise that the back icon took you back up the folder tree, rather than closing the folder location window!
It would be nice if we could get a custom mount script or something that would mount the sdcard to something like /mnt/sdcard/music. I'd love to have my music synced to card and everything else stored internally...
fisha21 said:
EDIT: If you go into TB preferences menu, scroll down to Backup folder location, then press the Back icon (the system one) to get back to the root folder. Then you can choose the Removable/MicroSD/ folder. Click on "create a new folder", call it what you want, then open that folder. Click the "Use current folder" button and there you go...Backup folder on external SD!
Took me a while to realise that the back icon took you back up the folder tree, rather than closing the folder location window!
Click to expand...
Click to collapse
Thanks! Thats what I needed to know, I was thinking its kind of stupid that they only have a "detect" button.
brando56894 said:
I (along with other people) find it weird that Asus chose to mount the sdcard to /Removable/MicroSD instead of the traditional /mnt/sdcard.
I would like Titanium Backup to store the files on my sdcard instead of the internal memory, but the problem is that TI only checks the /mnt/sdcard directory. So in my infinite geek knowledge I had the idea to symlink /Removable/MicroSD/TitaniumBackup to /mnt/sdcard/TitaniumBackup. The problem is that FAT32 doesn't support symlinks, so I formatted the sdcard to NTFS and popped it back in but it wouldn't mount it, which I realized was because it doesn't have the NTFS modules. So I popped it back out and formatted it as ext2, but it still wouldn't mount automatically and I couldn't mount it manually because I didn't know what the device name was.
Anyone have any solutions?
Click to expand...
Click to collapse
What? You're doing it backwards!
If TI is writing to /mnt/sdcard/TitaniumBackup, but you want it to write to /Removable/MicroSD/TitaniumBackup instead, then /mnt/sdcard/TitaniumBackup should be the symlink, pointing to a directory on the SD card!
The target's filesystem doesn't matter (fat32), only the source's (i.e. ext4 on the internal storage).
Good catch, either way it doesn't matter now because I don't need symlinks since I know how to do it in TB now.
If you are using CWM 6.xx and you attempted to 'format' your sd card entirely, you may have experienced some troubles.
I formatted the /system, /data, /cache manually in CWM and found alot of problems which had arisen afterwards.
After you format these, you may notice that you can no longer mount /data/ ! This is a big problem. You cannot install new roms, or do anything because the /data/ partition cannot mount.
Solution:
1. Using Odin, flash select PDA and your stock TouchWiz based ROM. Also use the partitioning file for the i9505 device. (Make sure you tick repartition in Odin), this process may or may not work with or without the paritioning file, if your filesystem is corrupt its probably a good idea.
2. Once this is complete, reboot, you will see that the Samsung logo appears, and it may appear that things have worked, but it wont work yet.
3. You will need to install CF-AUTO-ROOT. This roots the phone, but it also seems to fix the partitioning issue.
4. Once installed you should be able to boot into TouchWiz.
5. Install Philz Advanced CWM recovery!
6. Use the feature of 'format phone for ROM'. This will format the SDCards /system/, /data/ etc PROPERLY and wont cause you any problems.
7. Install your flavor of ROM
8. Enjoyjoy
I searched the internet everywhere attempting to fix this unmountable /data/ partition, only via a french-english translated forum was I able to learn how to do this.
Further reading:
http://www.phonandroid.com/forum/recuperer-error-mounting-data-t56933.html
If it helped, please thank me
Cheers, ostenn.
ostenning said:
If you are using CWM 6.xx and you attempted to 'format' your sd card entirely, you may have experienced some troubles.
I formatted the /system, /data, /cache manually in CWM and found alot of problems which had arisen afterwards.
After you format these, you may notice that you can no longer mount /data/ ! This is a big problem. You cannot install new roms, or do anything because the /data/ partition cannot mount.
Solution:
1. Using Odin, flash select PDA and your stock TouchWiz based ROM. Also use the partitioning file for the i9505 device. (Make sure you tick repartition in Odin), this process may or may not work with or without the paritioning file, if your filesystem is corrupt its probably a good idea.
2. Once this is complete, reboot, you will see that the Samsung logo appears, and it may appear that things have worked, but it wont work yet.
3. You will need to install CF-AUTO-ROOT. This roots the phone, but it also seems to fix the partitioning issue.
4. Once installed you should be able to boot into TouchWiz.
5. Install Philz Advanced CWM recovery!
6. Use the feature of 'format phone for ROM'. This will format the SDCards /system/, /data/ etc PROPERLY and wont cause you any problems.
7. Install your flavor of ROM
8. Enjoyjoy
I searched the internet everywhere attempting to fix this unmountable /data/ partition, only via a french-english translated forum was I able to learn how to do this.
Further reading:
http://www.phonandroid.com/forum/recuperer-error-mounting-data-t56933.html
If it helped, please thank me
Cheers, ostenn.
Click to expand...
Click to collapse
I had the same issue. I think its a bug present in most recoveries at the minute. I've just taken to manually deleting the folders on the internal SD card. To stop this happening.
I remember, in one day, I had to flash the pit file and stock rom 4 times. I think this is actually quite intermittent. Sometimes it doesn't corrupt the /data partition and sometimes it does.
It's really quite damn annoying. At least there's an easy enough fix - if not time consuming.
Sent from my GT-I9505 using Tapatalk 2
So I have rooted and installed cwm recovery, and when I go into recovery mode and try to mount /external_sd nothing happens.
Recovery acts like it is mounted, but my computer detects nothing.
I have tried different cwm recovery versions and I'm getting the same result.
Is this because of the way the Razr itself mounts storage, ie. one device with multiple drives inside and no driver letter, or am I doing something wrong?
Also, when I make a backup, I cannot find it with either Windows Explorer or with a file manager on the device. Recovery can find it and restore from it, but I cannot move this folder around in case I need to wipe it, or just save space.
EDIT
I flashed twrp and the mounting issue persists. I am, however, able to find the backups it makes, I think I will just stick with twrp. Now I just need to find that 1.5gb of backups somewhere on the internal memory and delete them for space
After a few days of googling, i stumbled upon a thread in Droid DNA forum. Which led me to this answer right from the source on why it's not possible to mount our SD Card or actually, just a folder in /data, in TWRP.
Just wanted to share and hope this will clear things up and hoping that people won't wipe their /data partition since it will delete the SD Card folder as well.
I find this very enlightening so read on.
What is a data media device?
I'm writing this page because there seems to be a lot of confusion about how many of the newer Android devices work. Starting in Honeycomb 3.0 with the Xoom, Google changed the way that they handled storage. Instead of having a "data" partition with your apps and a separate "sdcard" partition for storage, Google started giving you a single, very large data partition. Inside /data is a folder at /data/media that contains all of the contents of what you think of as your internal sdcard.
Since /data/media is part of /data, we pretty much never actually format the data partition. Formatting data, of course, also removes the media folder that contains the internal sdcard. When you choose a factory reset, instead of formatting, we use rm -rf commands to remove all the folders except for the media folder so that we can remove all of your apps and settings while leaving your "sdcard" intact. In TWRP we also have a wipe internal storage option that rm -rf's the media folder and a "Format Data" option that formats to recreate the entire file system in case something goes completely wrong or to remove device encryption.
When you're booted to Android, Android fuses the media folder to /sdcard and emulates a FAT files system that doesn't have permissions for legacy apps. We don't currently have fuse in recovery, so we just add an extra mount command to mount /data/media to /sdcard so in recovery you still have to worry about permissions on /sdcard.
Because the "internal sdcard" is not a true FAT file system, you can't mount it via USB storage. Well, that's not technically true, but the vast majority of people use Windows computers and Windows doesn't recognize ext4. If we were to allow you to mount the data partition via USB storage, Windows would claim that the device wasn't formatted and offer to format it for you, which, as you can imagine, would be a disaster. The whole ext4 setup is another reason that Android switched to using MTP for transferring files. Most of these devices don't have the necessary kernel configuration to even support USB storage mode, so it's not very easy to enable USB storage if we even wanted to try. Unfortunately at this time, MTP isn't available in recovery, so if you have no other option, you will have to use adb to push and pull files to/from your device.
As a special note, if you choose to do a factory reset from your ROM, even if the ROM says that it will wipe everything including the internal storage, well, that's not what TWRP will do. A stock AOSP recovery would format data including the "sdcard" but TWRP will use its regular factory reset setup that leaves the internal storage intact.
There are a couple of nice gains with using this setup vs the old data + FAT storage partition. With /data/media you, as the user get more control over how you use your storage. If you have a ton of apps, then that's no problem since you have a huge data partition to work with. If you don't have a lot of apps, you get more room to use for storing things like movies. Further, ext4 doesn't suffer from the 4GB file size limit that FAT has, so you can have a large, high-def movie on your device if you like. I'm sure another motivating factor was to get Android away from using FAT which is a Microsoft creation. Performance on ext4 in Android is also probably better than FAT. As a downside, data media devices tend to store a lot more app data in the "data" section and so backups on these devices tend to be larger.
Android 4.2 has changed things with /data/media devices a little bit due to the multi-user support that came in 4.2. Each user is assigned a subfolder in /data/media. The main user gets /data/media/0 and subsequent users get /data/media/10 and /data/media/11 and so on. If you switch users in Android 4.2, the system will remount the /sdcard folder to point to the proper user's folder. TWRP has been updated to use the /data/media/0 folder starting in 2.3.2.0.
Another "feature" of 4.2 is that when you "update" to 4.2 it may attempt to upgrade your /data/media to multi-user. If you're running an older version of TWRP than 2.3.2.0 or newer, a factory reset may trigger multiple upgrades, causing your "sdcard" to get moved to /data/media/0 then /data/media/0/0 and then /data/media/0/0/0 and so on depending on how many times you "upgraded". This may cause backups to not be visible in TWRP. Also, there currently isn't a good way to go back to a 4.1 ROM after using a 4.2 ROM without having to manually move your files around.
Click to expand...
Click to collapse
http://teamw.in/DataMedia
I asked them if it's possible to just mount the ext4 partition if Windows users install some apps that can read them. Will see if they're going to answer.
Hope this helps. Cheers.
My phone was slowly corrupting some files inside the external sd card, but I thought it might have been because I had named a file with a $ sign and it had some problems when I plugged the usb.
After I had taken the file out and deleted the corrupted files (Some of my game saves died too :crying, I thought it was going to be okay, but the corruption did go on after some time.
One day, when I was using the phone, suddenly, I got a white line accross the screen and the phone rebooted, then every time it turned on, it worked for 1~3 seconds then, again, white line and reboot.
Tried to fix it in various ways, turning off wi-fi, changing the brightness and things like that in the moment before it rebooted, but I couldn't make it work.
After some tries/time, it gave me an error saying it needed to be wiped and reseted, but I really need some files inside of it, so I didn't wipe it, and now it just stops at the samsung logo.
I can get it into recovery mode or that "custom rom" screen, by using the volume buttons when booting up, and I could even get it to show in adb when in recovery mode, but I can't mount the sd card with it (It always tells me I can't do it, something about privileges, I think).
I just wanted to get some files from the internal memory, after that, I think I'll be flashing it with CyanogenMod so it'll be a Android 4.4
But, for now, what can I do to recover those files?
Thanks in advance
Edit: Recovery menu says:
--init-recovery...
E: failed to mount /data (invalid argument)
can't mount /data (invalid argument)
Then it tries to apply "multi-csc" and after it "successfully applies" it, then it shows the "failed to moun /data" error again
Well the easiest way would be to flash TWRP recovery and use the file manager to copy the files that you need to your mem card... if u couldn't access the internal memory just mount it manually either from the option "mount sdcard" or use the a shell command.. I believe there is a terminal emulator there