[Q] Data Recovery from .RAW file Internal Memory - General Questions and Answers

Hi there,
I have created a .Raw image from my Internal memory to recover deleted files from, using this tutorial successively:
http://forum.xda-developers.com/galaxy-nexus/general/guide-internal-memory-data-recovery-yes-t1994705
Now the problem rises because I am using windows 8, and the internal memory image is Linux EXT4 partition.
I have used many software to mount the image including : " Diskinternals, OSFMount, Ext2Fsd ... " but the problem arises because the data recovery software doesn't show the mounted partition even-though it is showing in My Computer.
I also have used many data recovery software that support Linux partitions such as: " Testdisk, PhotoRec, R-studio, Easeus, Geeksnerds, UFS, Active Undelete..." but all are only showing the files that are already there, and I need to recover the deleted files from this ext4 partition!

Related

Mounting nandroid .img file as drive

Is there a possibility to directly mount for example data.img yaff2 partitions in windows or some sort of an application doing this (with GUI)?
Thanks

/system partition size

On a 32GB Verizon version GS3, when I go to settings > storage, under miscellaneous files, it show "system memory" to be 5.74GB, I looked at an unrooted 16GB version, and system memory was only 3.49GB, of my total 5.8GB miscellaneous files, about 60mb is other files and applications, and the remainder says "5.74GB system memory".
Why is it so much higher on a 32GB vs. 16GB? I mean the system files should not be proportional to internal storage space, right? I don't have a lot of apps, and I have in fact removed a bunch of original system apps, it tells me I have only about 300 mb of /system space available, how is this possible?
I have flashed rooted images from Odin a couple of times, restored NAND about 20 times or more, and rooted via adb once or twice from stock unrooted. Is all this fragmenting the /system partition? Should I format /system next time I'm in recovery? If so, my pc doesn't seem to recognize the phone in recovery when connected. Do I need different drivers to connect while in recovery, so I can mount and format /system? I can format /data and /cache easily in recovery, and when I had my old HTC Evo 4G, I could connect the phone while in cwm and format /system, but I can't on an SGS3. Is there another easy way to format /system before restoring a NAND backup to truly start from scratch on a clean system partition?
Thank you

fstab.qcom modification

I just got my first Android Device (Moto E) and tried to get around the small internal memory by using the sdcard instead of the internal memory for /data. As the KitKat mounting procedure does not seem to be based on vold.fstab anymore, the usual guides to doing that don't apply.
So my idea was to format the sdcard with ext4 and modify the /fstab.qcom file to mount the sdcard as /data instead of the internal data partition. But here's where I don't know how to proceed, as adb shell don't seem to have access to the proper partition during flashboot (though having mounted the rootfs parition which should contain those files?) and is unable to write to the file once the system is running.
I'd appreciate if anyone can point me in the right direction on how to do that.
lunaticat said:
I just got my first Android Device (Moto E) and tried to get around the small internal memory by using the sdcard instead of the internal memory for /data. As the KitKat mounting procedure does not seem to be based on vold.fstab anymore, the usual guides to doing that don't apply.
So my idea was to format the sdcard with ext4 and modify the /fstab.qcom file to mount the sdcard as /data instead of the internal data partition. But here's where I don't know how to proceed, as adb shell don't seem to have access to the proper partition during flashboot (though having mounted the rootfs parition which should contain those files?) and is unable to write to the file once the system is running.
I'd appreciate if anyone can point me in the right direction on how to do that.
Click to expand...
Click to collapse
A little late in the game (I am trying to do the same), but I come across this:
http://forum.xda-developers.com/showthread.php?t=443994
boot partition populates the rootfs. So hack the boot.img (unpack to analyze), and you may find your answer. Hope this helps.
I will give it a shot in the next week.

accidently converted internal memory to ext2 in twrp. stuck in twrp recovery

hi when trying to convert my ext sdcard to ext2 for link sd, i accidently converted my internal memory to ext2 in twrp recovry.
now cant mount system data cache etc. internal memory is showing 0 mb. cant. i tried flashing with one rom i used to run previously (notexperience) but cant flash it anymore. it shows failed. plsss help me:crying:
First try installing STOCK MM via Odin.

Damaged Internal Storage Partition (Need Recovery)

I have flashed my phone using qcom flasher its a snapdragon 800 device elife e7. Now the problem is I can access internal storage but phone storage is not available means can't save any photo content etc. I tried formatting with twrp but no help. It shows sdcard0 as vfat on adb shell but nothing works. Any help pls. Would be really grateful. Thanks
Formatting always deletes / wipes all data on chosen partition.
I can't format it I don't care about the data . Tried it with twrp but it fails to even mount the storage every other partition is working flawlessly except the Storage/internal SD
Is there any way to partition internal storage through root?
IMO far easier is to reflash phone's Stock ROM.
that didn't fix it

Categories

Resources