Related
Hi all,
i formatted my sdcard with ext3, but CM7 doesn't mount it. I changed the 'vfat' in the fstab to 'ext3', but it still dosn't mount the card. I can manually mount it with 'mount /dev/block/mmcblk0p1 /sdcard', but then I can only access /sdcard via Terminal Emulator or the adb shell. Root explorer says that it is not mounted although it is mounted. Does anybody know how to fix that?
Mister Ypsilon said:
Hi all,
i formatted my sdcard with ext3, but CM7 doesn't mount it. I changed the 'vfat' in the fstab to 'ext3', but it still dosn't mount the card. I can manually mount it with 'mount /dev/block/mmcblk0p1 /sdcard', but then I can only access /sdcard via Terminal Emulator or the adb shell. Root explorer says that it is not mounted although it is mounted. Does anybody know how to fix that?
Click to expand...
Click to collapse
Hey dude, I feel ya. I wanted to ext3 all the way, but google thought Android users would rather use fat for their sdcards so we're bound to trying to work around it. You might want to look at your sdcard permissions, check that you have "X" permissions for user, group and other, or just go crazy and do "chmod -R 777 /sdcard".
You could look into what this guy did: http://android.modaco.com/topic/308568-how-can-i-bind-mount-eg-systemsdxxx-sdcardxxx/#entry1511967
but I backed out mainly because it looks too much like more trouble than its worth.
Good luck!
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
DrPlumEU said:
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
Click to expand...
Click to collapse
try this
If you are using Thor's CWM. And his recovery only;
Here are the steps to completely wipe all internal data. And give it a clean internal system (according to Thor)
Note: Optional Formatting.
If you really want to remove EVERYTHING in Internal Memory, at this point, go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Note, this will format EVERYTHING in internal memory (not ext sd card)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
After you reboot, I believe it resets back to the defaults.
try to install the rom with the normal procedures.
this what i used and it worked great no problems
note** i am just fowarding info that was passed to me. and this will erase you backups
---------------------------------------------------------------------------------------------
IF you are running RA Revamped Recovery, then you may want to contact Drellisdee at his thread;
http://forum.xda-developers.com/show....php?t=1459821
He knows the procedures to do the same.it's a tricky process, and he knows more about his recovery than I do.
Thank you for the prompt response. Already tried your recipe with no luck.
I need access to the DATA partition and do not know how to go about that. Once have access to the internal disk, would like to know how to completely wipe this if that what it takes.
Thanks
PS: If I truly have bricked the device it is still in 12mo warranty, so will contact Acer care centre if no tricks work.
PPS: Maybe I now have excuse needed to upgrade to Tegra 3 device. The Acer Iconia A700 looks tempting
i think i have seen something like that when fixing mine but did not touch it....as im not a pro, hopefully somone with a litle more in depth knowledge sees this and can help.
sorry
Have you tried restoring your nandroid backup? This has recovered the error for me on my phone before when the /data partition became corrupt. Worth a shot.
Sadly, restoration of the nandroid backup was not successful.
I have notice that I pressed wrong volume button when attempting the hard reset. Will try the correct procedure later after work. Hopefully a proper hard reset then restore with one of Vache stock roms will have me up and running.
UPDATE: Sadly hard reset fails to load. My poor a500 needs resuscitation at acer clinic
I had the exact same problem, although I caused the problem in a different manner. You need to be able to use adb to get it going again. If you are not familiar with adb, do a search and you can find plenty of help. That's what I had to do. Unfortunately, my skills with adb are pretty much non-existent, so I can't really help you with that part.
Once you get adb going on your computer and it recognizes your A500, follow these steps:
You will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.
From adb shell:
mount (This is to check data isn't mounted. If mounted use "umount data")
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
After this is done your file system on /data will be fixed. You can install the ROM of your choice. Good luck!
(These instructions were originally provided to me by drellisdee)
Thanks for the answer on your previous post. I fixed my /data mount.
Love to unbrick my acer for the 50th time
Did not have this error tho, before I tried to convert the /data mount to ext4
DrPlumEU said:
I would like some help please.
Have bricked my a500 during attempt to falsh vach leaked ICS.
Switchme was used before clearing data and I forgot to delete a profile. This is I think the cause of my problem.
I cannot proceed with any ROM flashing until data partition is cleared.
I am using RA-ICONIA-3.15 recovery kernel.
I can mount and format CACHE SYSTEM FLEXROM partitions.
Attempting to mount data this is the message
E:Can't mount /dev/block/mmcblk0p8 (File exists)
Now my poor A500 will not get past 'acer'screen when trying to boot.
Question 1: How can I restore access to the DATA partition?
Question 2: How do I wipe my internal storage and start over?
I have a nand backup before this started on external SD card. Uncertain if I should restore this.
Thanks in advance.
Click to expand...
Click to collapse
If you switch the A500 off and whilst switching it on hold the volume up button and start toggling the rotation lock on and off it should clear the internal memory completely. Then flash an update.zip from a MicroSD. Otherwise use the Iconia software update tool that's floating around in APX mode. Make sure you have your UID for this
Ping192 said:
Did not have this error tho, before I tried to convert the /data mount to ext4
Click to expand...
Click to collapse
That's exactly what caused my problem. Glad you are working again.
Resolved by great customer support...
To close this thread I wish to congratulate the Acer customer support team in Plymouth who have restored my Acer Iconia A500 to working order in under a week.
It is upgraded OTA to Android 3.2.1.
As still in warranty, no charge for the failure of the hard-drive partitioning!
Great work. Good customer service.
thanks lovable people in this thread
thanks lovable people in this thread you solved my problem . especially Dr. McKnight (23rd February 2012, 03:48 PM) back in the beginning of the thread. His solution using thor's recovery was enough to solve my problem. Wonderful and thank you
/Mikkel
spoupard said:
From adb shell:
mount (This is to check data isn't mounted. If mounted use "umount data")
mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8
Click to expand...
Click to collapse
When I do the "mke2fs -j -b 4096 /dev/block/mmcblk0p8" command from adb's shell, it takes forever (I let it run for hours). Something I was thinking about, could I simply "rm -rf /dev/block/mmcblk0p8" first, and then run the above commands? Also, should I not add the "-t ext4" option to the mke2fs command?
kerijan2003 said:
When I do the "mke2fs -j -b 4096 /dev/block/mmcblk0p8" command from adb's shell, it takes forever (I let it run for hours). Something I was thinking about, could I simply "rm -rf /dev/block/mmcblk0p8" first, and then run the above commands? Also, should I not add the "-t ext4" option to the mke2fs command?
Click to expand...
Click to collapse
Try in fastboot mode execute:
fastboot -w
I used this hardware mod on all 50 of the tablets with great success. Just be careful to not remove any of the other little chips, I used heat to loosen the glue.
http://forum.xda-developers.com/showthread.php?t=1877585
Good luck
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Reference Material:
Fix for the P1000 - This is exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1711150
Fix for the Atrix 4G - Again, exactly what I need to do
http://forum.xda-developers.com/showthread.php?t=1766939
Another Example
http://forum.xda-developers.com/showthread.php?t=1463756&highlight=ics
Re-partition steps:
http://forum.xda-developers.com/showthread.php?t=845708 <- this did not work
Heimdall Suite re-partition with known good pit file <- This did not work
I'm on the exact same place, attempting the exact same, currently I was trying to edit vold.fstab as well as init.rc but it seems you have a better grasp of this.
I use a Sprint sph-p100, a CDMA version just like yours and as far as I know fully compatible with anything (save modem but I only use wi-fi).
I've tried your first link with a GB rom and failed (didn't pass first Samsung logo), but I will keep trying and post back anything I achieve.
If you indeed make a kernel or image that makes them boot please share it with us and I will GLADLY test it out.
I'm also aware that an easy solution is to open up the hardware and remove the internal SD Card (the kernel will assume the external is mmcblk0 instantly) but I dislike doing butchery and maybe breaking my device.
Chris... much progress has been made on this... first off. I am dumping the Gingerbread Verizon images for the CyanogenMod 9 Rc1 for P1c. I am currently following the kernel rebuild instructions from the device developer "cdesai" is working on. Those instructions are here:
http://forum.xda-developers.com/showpost.php?p=20162940&postcount=3
with repo setup here:
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
With the instructions on how to build just the kernel I will modify the initramfs.list among other files to get the required results. What I will need to help you is do the exact same thing, just with the initramfs.list for your P100 device ??
Are you willing to use CyanogenMod 9? I have pretty much abandon Gingerbread unless someone can hook me up with a known working P1c Gingerbread git.
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
ChrisCTX said:
CM9 makes me even happier, my device is the same P1C so we don't even have to re-build anything other than what you do to it.
Besides testing if you want I can double check the changes you made as well as document them (it might just help someone else down the line).
Also, not sure if this happens to you but my mmcblk0 IS detected, it just doesn't work (can't be mounted, formatted or anything), just making sure your idea works with this.
Click to expand...
Click to collapse
Mine is detected too. But fails when you try and fdisk is. I have several devices with the same results. If you want try to fdisk /dev/block/mmcblk0
Tell me if that eventually shows up as a 32mb disk with an empty partition
The correct commands are
adb shell
su
fdisk /dev/block/mmcblk0
p
q
Don't have a rooted rom on it now (can't really install anything besides flashing), but I tried it minus "su" and it didn't do anything at all.
Update the status. I have made the changes to support booting from the SDCard. For the first time I can mount the /data directory via the recovery. There is an install sequence that I haven't yet mastered. Will be in touch
Sounds great Jim, thanks for all the effort so far
I am waiting for the release of this. My tab internal SD crapped out also.
please help
im on the same boat if in need to take of the internal storage let me know i will do it just tell me some directions
Same issue
JimRich said:
I have spent that last 3 days working on an issue that about 50 Verizon Samsung Galaxy Tabs SCH-i800 are having. These tabs for whatever reason have an issue with the internal sdcard getting corrupted, they then hang on the Verizon screen.
I have done several things to attempt to get these corrected, attempted to fdisk and reformat the internal sdcard, this did not work. The internal /dev/block/mmcblk0 is completely hosed.
The only real solution that will correct this issue is to partition the external sdcard and force the android boot up process to use it instead of the internal.
Technically that should be easy. Partition the external sdcard to match the internal, Modify the boot.img making changing the references to mmcblk0pX to mmcblk1pX. Reflash the image and boot. Should work. There are tons of posts on this board where others have done it. But none have with the SCH-i800.
I am ok with running the Stock Rooted 2.3.5 Verizon image or the 2.3.5 latest version of Cubed3 Rom
What I don't know and need help with is where to I pull the boot.img from ether of these gingerbread based roms to modify it?
Click to expand...
Click to collapse
Hey guys I am having the same issues (as far as i can tell) with my Verizon Samsung Galaxy Tab SCH-i800. so the first issue is i tried to install a stock rom to fix a corrupted cache partition. now it tries to boot US Cellular. As of this moment the error i get when i put the device in recovery mode:
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
# MANUAL MODE #
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
I am wondering if i can just create a new partition on a new SD card? i bought this device on ebay a couple weeks ago and i don't want to continue attempting sketchy leads for fear of hard bricking it. All help is greatly appreciated. I really don't want to give up on this thing because i feel like the soultion is out there... I am very good with performing commands via command prompt if that is nessasary, also i have access to an Ubuntu 12.4 computer if that would make things easier? Please help?
***Also as far as i know this is equipped with android Froyo and the issue developed after the previous user attempted to update. Please email me a reply or reply to my post.
Thanks,
-Andy
I switched to a hardware modification. This worked great!
http://forum.xda-developers.com/showthread.php?t=1877585
Okay so i was just doing a bit of file management. I removed a 1.4gb psp iso i had on my nexus 7 and then i checked how much space i had left using storage option in settings. I checked it and it said i had 25gb free when before i removed my file i had only 13gb free. Tried rebooting device and then used es file explorer to see all files. Opened es file explorer and then noticed everything was gone. Only stock items were folders were left eg Android, Download etc. All my msuic and some game data was gone. Opened up asphalt 7 to see if it would still work but it doesnt anymore. Tried opening real racing 3 And it asks me to redownload game data. My widgets are still in homescreen and work and some of the other apps i have still work as well eg plague inc, subway surfer and most of the other ones.
Any idea on how this happened and how i can recover my files? I have a bugsense file as well that was left on my device.
As to recovery of lost files your options are not good. (And if we're talking a non-rooted device, the odds are approximately equal to 0%) Recovery in ext4 filesystems is technically much more challenging than in simple filesystems such as FAT. And this pessimistic outlook presumes that the filesystem is healthy/clean. If the reason for the problem occurring in the first place was a corrupted filesystem, then the odds go from simply bad to pathetically poor.
Sorry, dude... got any Nandroid or TiBu backups stored on your PC?
If you had Putin's top-secret files on your N7 and the CIA got hold of it, the first thing a forensic analyst would do is try to take a raw (block) device dump off of the "cold" device. (If you are still running the N7 with the regular OS the /data partition is being continually written to, and this further reduces the chances of file recovery every second the device is booted).
In the case of an analyst with less resources, this might mean using a custom recovery boot to get the raw device copy; unfortunately, the /data partition is huge - nearly 30 GB - so you would have to mount a extN filesystem via OTG... and doing so thus precludes using adb, so you would need to use a recovery with a touch interface and command-line entry (e.g. TWRP)
# mkdir /mnt/myOTGdisk
# mount -t ext2 -o rw /dev/sda1 /mnt/myOTGdisk/
# dd bs=8196 if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/myOTGdisk/userdata.img
Doing such a thing would allow you to examine that huge image file with forensic file recovery tools from a PC (probably running Linux) as in principle you captured the entire ext4 filesystem.
The thing is, efforts spent in file recovery should be proportional to the value of the files being recovered. I'm not sure if your saved gaming history rises to that occasion. For sure the dude at the CIA won't want to help you with that.
As to the source of your troubles, it's hard to say. With TWRP booted, you can run the "e2fsck" program to see if the /data ext4 filesystem is corrupted, e.g.
# mount | grep /data ( see which mmcblk0 partition is /data, on grouper it is mmcblk0p9 )
# umount /sdcard
# umount /data
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
(For the last command above, you might need to use the block device name /dev/block/mmcblk0p?? instead of the UDA symlink )
If the above command shows that you have a corrupted /data filesystem, I would re-initialize that filesystem ( "fastboot format userdata" ) - note this wipes all userdata including the psuedo-SD card.
Finally, I should point out that some type of hardware failure might have occurred somewhere in that huge 30 GB partition - if that is the case then there will be problems down the road again. If that is the case, the only way to detect this will be a write test which nearly fills that partition, followed by a filesystem sanity check as shown above.
Probably that would need to be done in the recovery rather than in the normal OS, as a nearly full /data filesystem will probably wedge the device.
Phew, I've said enough.
Good luck
I never tire of reading your posts, bftb0, ("...the odds are approximately equal to 0%")...genius.
But don't the CIA have access to Cray, 'Kasparov' DeepBlue beating SuperComputers that could make mincemeat out of the kind of thing your alluding to... in less time than it takes to flash a ROM... or have I been watching too many James Bond movies?
Vaguely rhetorical question - think I already know the answer...
Still... what a great post.
Rgrds,
Ged.
---------- Post added at 01:22 AM ---------- Previous post was at 12:50 AM ----------
Hi, leont1280...
You could try running this ...
Disk Usage - http://play.google.com/store/apps/details?id=com.google.android.diskusage&hl=en
It gives a graphical 'map' or overview of your storage, and you can visually see where everything is (or should be), great for tracking down missing stuff... but as bftb0 has mentioned, it doesn't look promising.
Rgrds,
Ged.
Use astro file manager u can check it out
Sent from my Nexus 7 using Tapatalk 2
Right bftb0 i did what you said in twrp and i recieved the following summary information.
/dev/block/mmcblk0p10: 28133/1835008 files (3.2% non-contiguous) , 1571673/733977
Any idea on what that means?
Also under the mount option in Twrp i can Unmount and mount the System, Data and its Cache. However i cant Mount the SD Card. Should that be a concern?
bftb0 said:
As to recovery of lost files your options are not good. (And if we're talking a non-rooted device, the odds are approximately equal to 0%) Recovery in ext4 filesystems is technically much more challenging than in simple filesystems such as FAT. And this pessimistic outlook presumes that the filesystem is healthy/clean. If the reason for the problem occurring in the first place was a corrupted filesystem, then the odds go from simply bad to pathetically poor.
Sorry, dude... got any Nandroid or TiBu backups stored on your PC?
If you had Putin's top-secret files on your N7 and the CIA got hold of it, the first thing a forensic analyst would do is try to take a raw (block) device dump off of the "cold" device. (If you are still running the N7 with the regular OS the /data partition is being continually written to, and this further reduces the chances of file recovery every second the device is booted).
In the case of an analyst with less resources, this might mean using a custom recovery boot to get the raw device copy; unfortunately, the /data partition is huge - nearly 30 GB - so you would have to mount a extN filesystem via OTG... and doing so thus precludes using adb, so you would need to use a recovery with a touch interface and command-line entry (e.g. TWRP)
# mkdir /mnt/myOTGdisk
# mount -t ext2 -o rw /dev/sda1 /mnt/myOTGdisk/
# dd bs=8196 if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/myOTGdisk/userdata.img
Doing such a thing would allow you to examine that huge image file with forensic file recovery tools from a PC (probably running Linux) as in principle you captured the entire ext4 filesystem.
The thing is, efforts spent in file recovery should be proportional to the value of the files being recovered. I'm not sure if your saved gaming history rises to that occasion. For sure the dude at the CIA won't want to help you with that.
As to the source of your troubles, it's hard to say. With TWRP booted, you can run the "e2fsck" program to see if the /data ext4 filesystem is corrupted, e.g.
# mount | grep /data ( see which mmcblk0 partition is /data, on grouper it is mmcblk0p9 )
# umount /sdcard
# umount /data
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
(For the last command above, you might need to use the block device name /dev/block/mmcblk0p?? instead of the UDA symlink )
If the above command shows that you have a corrupted /data filesystem, I would re-initialize that filesystem ( "fastboot format userdata" ) - note this wipes all userdata including the psuedo-SD card.
Finally, I should point out that some type of hardware failure might have occurred somewhere in that huge 30 GB partition - if that is the case then there will be problems down the road again. If that is the case, the only way to detect this will be a write test which nearly fills that partition, followed by a filesystem sanity check as shown above.
Probably that would need to be done in the recovery rather than in the normal OS, as a nearly full /data filesystem will probably wedge the device.
Phew, I've said enough.
Good luck
Click to expand...
Click to collapse
Right bftb0 i did what you said in twrp and i recieved the following summary information.
/dev/block/mmcblk0p10: 28133/1835008 files (3.2% non-contiguous) , 1571673/733977
Any idea on what that means?
Also under the mount option in Twrp i can Unmount and mount the System, Data and its Cache. However i cant Mount the SD Card. Should that be a concern?
leont1280 said:
Right bftb0 i did what you said in twrp and i recieved the following summary information.
/dev/block/mmcblk0p10: 28133/1835008 files (3.2% non-contiguous) , 1571673/733977
Click to expand...
Click to collapse
Hmmm, mmcblk0p10 - you must have a tilapia (3G N7) device, yes?
If you had any filesystem errors, that e2fsck run would have produced copious reams of output. If a filesystem is clean, it produces only 5 or 6 lines of summary output.
leont1280 said:
Any idea on what that means?
Also under the mount option in Twrp i can Unmount and mount the System, Data and its Cache. However i cant Mount the SD Card. Should that be a concern?
Click to expand...
Click to collapse
I've seen the same business with TWRP and the /sdcard mount - I wouldn't worry about it. (It is not a "normal" mount in the sense of extN or FAT device partition mount - it behaves sort of like a strange symlink where the target directory and descendants all appear to have different file ownership and permissions than what exist in the true (underlying) filesystem. No doubt this is all performed in the kernel... I don't know whether a command-line invocation of "mount" can create this mount point, or whether a specific syscall/ ioctl is needed)
But back to your N7 - the lack of any errors in the filesystem check is good news, but also suggests that your files didn't disappear through a hardware failure. Are you sure you didn't fat-finger things when using the file manager? (I suppose it is possible that the file manager has a bug...)
I didn't look into what tools are available for extN forensic/recovery work. I can guess that the effort would be non-trivial, though.
bftb0 said:
Hmmm, mmcblk0p10 - you must have a tilapia (3G N7) device, yes?
If you had any filesystem errors, that e2fsck run would have produced copious reams of output. If a filesystem is clean, it produces only 5 or 6 lines of summary output.
I've seen the same business with TWRP and the /sdcard mount - I wouldn't worry about it. (It is not a "normal" mount in the sense of extN or FAT device partition mount - it behaves sort of like a strange symlink where the target directory and descendants all appear to have different file ownership and permissions than what exist in the true (underlying) filesystem. No doubt this is all performed in the kernel... I don't know whether a command-line invocation of "mount" can create this mount point, or whether a specific syscall/ ioctl is needed)
But back to your N7 - the lack of any errors in the filesystem check is good news, but also suggests that your files didn't disappear through a hardware failure. Are you sure you didn't fat-finger things when using the file manager? (I suppose it is possible that the file manager has a bug...)
I didn't look into what tools are available for extN forensic/recovery work. I can guess that the effort would be non-trivial, though.
Click to expand...
Click to collapse
Im pretty sure i didnt accidently delete it myself. When i was doing file management i was using my laptop with the N7 3g connected to it via MTP. Once i deleted the iso file the N7 started acting strange. I did notice a bit of lag that was usually out lf the ordinary and when i checked available space left it increased to 25gb rather than saying 13gb
aaah, having the same problem here, i was cleaning my n7 using my laptop, found a strange folder on my sd card, looked inside and it has a back up of some of my deleted files! interesting! i deleted the folder, then i started cheking other folders, like my ebooks, audio books and etc, but all my folders were empty!
so i disconnected my tablet, and after reconnecting, bam, all files gone.
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
kcattakcaz said:
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
Click to expand...
Click to collapse
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
zroice said:
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
Click to expand...
Click to collapse
I am rooted, but stock ROM and kernel. MTP is for connecting to a computer? If it is, I don't need that. I have tried
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extStorageCard
and variants switching the flags and options.
Interesting... I just typed that command in to make sure I didn't make any typos.... and my phone crashed and rebooted. I typed it again to see if it would cause another crash and it appears to have mounted the card! Whwn I type "df" at the prompt it now shows a 28.6 GB filesystem at that location, which has to be my sd card.
Why, how, I don't know. It works, it's all I can say.