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
Related
I tried everything possible to install jachero and I continually get a bootloop in the HTC opening intro. Ive used unbuto , pargon partition manager to make , format the ext2/ ext3 partitions. But whenever I try to install I always get a bootloop. I don't know what the hell is wrong but i spent hour upon hour trying to get this to work.. Im usuing Cyanogenmod 1.2 and am trying to repair the ext filesystems and then it says,
Erro checking filesystem! Run e2fsck maually from console! can someone give me exact instructions on how to run e2fsck and do what has to be done so i can install Jachero.
Stuck in the same boat as you... I get to the Hero/HTC bootloop and I've tried what you have. In the recovery do this: Alt+X to get to console then type: e2fsck /dev/block/mmcblk0p2 to run the fix. I tried that, but still boot looping, maybe you'll have better luck with it...
Bootlooping, I had that issue after I tried to link my /data folder back to my SD. Didnt like that. Is your data folder there?
ok first of all, are you running the latest Radio and SPL? Access fastboot (Camera and Power OR Back and Power) and post the info you get here.
for the command to e2fsck try running this
e2fsck /dev/block/mmcblk0p2 <--- For ext2
e2fsck /dev/block/mmcblk0p3 <--- For ext3
nephron said:
e2fsck /dev/block/mmcblk0p3 <--- For ext3
Click to expand...
Click to collapse
I should point out that this block here could also be the linux-swap partition for alot of people and that the 2nd one could be ext3 if its been converted.
jhood99 said:
I tried everything possible to install jachero and I continually get a bootloop in the HTC opening intro. Ive used unbuto , pargon partition manager to make , format the ext2/ ext3 partitions. But whenever I try to install I always get a bootloop. I don't know what the hell is wrong but i spent hour upon hour trying to get this to work.. Im usuing Cyanogenmod 1.2 and am trying to repair the ext filesystems and then it says,
Erro checking filesystem! Run e2fsck maually from console! can someone give me exact instructions on how to run e2fsck and do what has to be done so i can install Jachero.
Click to expand...
Click to collapse
I fixed this by using a different SD Card
Hi xda community,
I've an issue with my Defy. My actual Rom is the last stable MIUI 2.3.7a.
The error is that the /data partition is always in read-only.
Code:
/dev/block/mmcblk1p25 on /data type ext3 (ro,relatime,errors=continue,data=ordered)
So I can't use any applications. ( lot of crash due to read only partition )
I have some errors like this one in the log :
Code:
Buffer I/O error on device mmcblk1p25, logical block 86151
lost page write due to I/O error on mmcblk1p25
I already try to re-install the rom and other roms included stock rom. And I always have this kind of error.
I have no idea on how to resolve this.
Can I move the /data to sdcard ? or use tools like fsck ? Or perhaps the defy internal memory is dead.
Thank you for help or advise.
Did you try full flash via RSD lite?
buruss said:
Did you try full flash via RSD lite?
Click to expand...
Click to collapse
I'm late in my answer but this topic is always open in my mind.
Yes I try this several times, The flash work. But after a little time of utilisation (with stock rom or miui or cyanogen, the error occurs again.
I think that I have bad block on internal memory, my goal is now to create a partition on sdcard and use symbolic link to this one in order to bypass the internal memory. Or an easy way is to mount /data on the sdcard.
Actually I'm not familiar with Android, but I'm very familiar with Linux. In theory it should work if I can mount the sdcard early in the boot process.
Anyone have already try this ?
bipbip61083 said:
... I think that I have bad block on internal memory, my goal is now to create a partition on sdcard and use symbolic link to this one in order to bypass the internal memory. Or an easy way is to mount /data on the sdcard.
Actually I'm not familiar with Android, but I'm very familiar with Linux. In theory it should work if I can mount the sdcard early in the boot process.
Anyone have already try this ?
Click to expand...
Click to collapse
Hi,
Sorry to revival your post.
I have a similar problem (details in this thread). For some reason my Defy will not mount the /dev/block/mmcblk1p25 and I guess that's the reason why after each reboot all my settings are lost.
I've already try to Fix Permissions (under Recovery Menu > Advanced), but it didn't help.
I was hoping to learn with your experience. Did you could manage to fix your problem creating a symlink or something else?
Merci.
so.. internal storage on my a501 is mounted as /sdcard
i ve just installed a new rom after full format and i cant use the /sdcard directory anymore.
all files and folders are there, but their attributes have been reset. folders show up as 0kb files and i cant access nor delete them.
i tried every format option available in cwm. i tried deleting them in windows after connecting the tablet with usb, nothing works
/sdcard mounts /dev/fuse. this is confusing. its as if i m stuck with corrupted inodes and no data.
what can i do to recover a functional internal storage ? :'(
mr.bryce said:
so.. internal storage on my a501 is mounted as /sdcard
i ve just installed a new rom after full format and i cant use the /sdcard directory anymore.
all files and folders are there, but their attributes have been reset. folders show up as 0kb files and i cant access nor delete them.
i tried every format option available in cwm. i tried deleting them in windows after connecting the tablet with usb, nothing works
/sdcard mounts /dev/fuse. this is confusing. its as if i m stuck with corrupted inodes and no data.
what can i do to recover a functional internal storage ? :'(
Click to expand...
Click to collapse
Part of your internal storage is recognized as SD Card. Your SD should be recognized as External SD. This you should already know.
Now, to totally clear your internal memory, boot back to CWM
If you use the most recent CWM;
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. (if you use an older version of CWM, you should be able to find this option)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This should get you going with the format, then reflash your rom.
Also, which rom were you trying to flash?
Thanks
i was flashing Alexandra precisely ^^;
edit: ok nvm this is the link i was missing to update cwm :
http://forum.xda-developers.com/showthread.php?t=1426617
ongoing
mr.bryce said:
Thanks
i was flashing Alexandra precisely ^^;
i dont have this option under backup and restore.
i m on cwm 5.0 from thor 1.3.4
i tried installing rom manager, but because my default download folder /sdcard is corrupt, it doesnt seem to install anything (says download failed check connection)
i m searching for an update.zip of 5.0.2.7 for manual update but i m not sure if its ok to use any on the A500, is it device specific ?
Click to expand...
Click to collapse
You should have the option to do a complete format in your CWM (toggle option) Even on the older version.
I'll suspect the download may have gotten corrupted somehow.
Go to Tegraowners, and get the update zip for the recovery. Just copy to SD, boot and flash it. Simple process.
DO NOT USE ROM MANAGER!!!!! If you do, I can't help you.
---------- Post added at 09:21 PM ---------- Previous post was at 09:09 PM ----------
mr.bryce said:
Thanks
i was flashing Alexandra precisely ^^;
edit: ok nvm this is the link i was missing to update cwm :
http://forum.xda-developers.com/showthread.php?t=1426617
ongoing
Click to expand...
Click to collapse
Well, you can do it that way, but it's the same recovery I think you have now.
(it's a long story behind that)
I would still suggest you just copy the update.zip to your sd from Thor (ver 1.6), and flash it.
yep... so i did this... and still got corrupted data :'(
here s what i did step by step :
- manual update and reboot to thor recovery 1.6rev2
- toggle internal storage
(i read "backup and restore /data/media: Enabled)
- went to mounts and storage and formatted system, cache and flexrom
- went to wipe menu and wiped cache and dalvik-cache
then install zip from sdcard and alexandra rev4
Moscow Desire said:
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. (if you use an older version of CWM, you should be able to find this option)
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This should get you going with the format, then reflash your rom.
Click to expand...
Click to collapse
it doesnt work --; i still cant use any file/folder listed under /sdcard
You formatted all 4, including Flexrom, correct?
Because I've never heard of this happening before.
i also tried the following :
toggle internal storage : enabled
use internal storage as /sdcard
format /sdcard
i read E:cant format_volume "/sdcard"Error formatting /sdcard!
mr.bryce said:
i also tried the following :
toggle internal storage : enabled
use internal storage as /sdcard
format /sdcard
i read E:cant format_volume "/sdcard"Error formatting /sdcard!
Click to expand...
Click to collapse
Hang on, asking for advice. I'm lost with this one right now.
---------- Post added at 10:02 PM ---------- Previous post was at 09:58 PM ----------
What's strange, is that the rom flashed normally? Up and running? Because I am puzzled to say the least. You may want to try flashing another rom. Basically, the rom should not have messed with the stuff you had installed there. It usually doesn't. Try flashing another rom, and see what happens. Try Harkon. It's a stock based like mine, with only a kernel to kick it.
Also, which rom did you have before this?
Moscow Desire said:
You formatted all 4, including Flexrom, correct?
Because I've never heard of this happening before.
Click to expand...
Click to collapse
only system, cache and flexrom in mounts and storage,
then cache and dalvik cache in wipe menu
so i tried again with all 4, and it gives me an error on format /data
i read "Formatting /data..."
"Skipping erase of /data/media."
"Done."
then i wiped all 3 in wipe menu (including factory reset)
and did all this again without switching to internal storage because i m clueless at this point.
flashed back the rom.
i m stuck --;
is there a way to mount /sdcard from another location ? or format /dev/fuse from a terminal ?
i tried with another rom i dont think alexandra had anything to do with it.
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
The formats should have been all 4; (with toggle enabled)
System
Data
Cache
Flexrom
According to all reason, this should have formatted your complete internal memory.
Still waiting to hear word, but I might not get anything tonight. We're in a way different time zone, and we have day jobs.
I would hate to say return to a stock status (run the stock acer rom ), as I would like to try and work this out. The problem, is with all the flashes, and all the downloads, this is the first I heard of this issue. Sort of makes it "my turf".
---------- Post added at 10:36 PM ---------- Previous post was at 10:25 PM ----------
mr.bryce said:
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
Click to expand...
Click to collapse
Dude, I am just glad it's working now
And damn glad it wasn't something I did.
Most Rom Mod's will tell you, when something happens with their installs, we take it personally, and like to see things working.
Anyhow, it's my turf, as it is with most Mod's.
Glad it's working now, and in the future, LEAVE SH_T ALONE!!!
I'm an old guy, and my heart can't take it
Be good, Any issue, drop in my thread.
mr.bryce said:
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
Click to expand...
Click to collapse
Hi,
How could you make a chmod on files?
I have a strange problem similar to you and suspect the same issue.
Thanks
gerardpuducul said:
Hi,
How could you make a chmod on files?
I have a strange problem similar to you and suspect the same issue.
Thanks
Click to expand...
Click to collapse
adb shell chmod 777 [path][filename]
Example;
adb shell chmod 777 /system/xbin/su
MD
Stuck on Skipping erase of /data/media
mr.bryce said:
ok nvm i messed up
i did a chmod on /data earlier in the afternoon kind of retarded i know.
i chmod it to 777 now and got my files back.
sorry i wasted our time --; and thanks for helping
Click to expand...
Click to collapse
Hey, I did everything that was going on on this thread and I had no luck. Can you explain what is a chmod or send me a link of what it is? I am stock at the recovery which the 321 euu installation provides.
Can't format on custom 321 EUU installation recovery, nor 1.7.3, nor 1.8.1 Thor version. I don't want to imagine that data partition is bad as hardware.
Thanks in advance
gatito89 said:
Can you explain what is a chmod or send me a link of what it is?
Click to expand...
Click to collapse
Moscow Desire said:
adb shell chmod 777 /system/xbin/su
Click to expand...
Click to collapse
i used android terminal at the time, in which case you just have to type chmod 777 /system/xbin/ORWHATEVER
https://en.wikipedia.org/wiki/Chmod
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
you must use e2fsck in order to check the EXT partition before mounting, esp if you are using it for DATA.
also, if you try to mount a bad partition it won't mount as r/w, instead it will mount as r/o (read only). that's why you were having the read-only issue.
regarding java, you need to install JDK. if you have a x64 system, you need both x86 and x64 variants.
hope this helps
blastsound said:
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
Click to expand...
Click to collapse
How are you mounting /data to EXT? If you are using my method, I have included a accept that scans at boot and then mounts if the partition is clean. Mounted partitions can't be scanned, they have to be unmounted before scanning.
Swyped from my HTC HD2 using XDA Premium
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.