Twrp Data 0mb

[Melanie Wendelberger]

Imessed up my phone trying to get open-gapps working on CM 13.I can't even get into my OS only into recovery mode. I tried flashing several CM-Versions, but that doesn't change much.I think the problem is, that my dalvik is corrupted. My data-partition is encrypted with a 3x3 pattern and TWRP can't decrypt it, so I can't wipe dalvik. I tried several variations of twrp decrypt, but they don't work. Now I am trying to flash cryptfs since I found a HowTo, which told me to use this commands:

The problem is, that cryptfs is not installed. I tried to flash cryptfs, with a custom made zip-file, but it seems, the cryptfs-installation is also trying to write into /data and just aborts, since it can't mount it.

I already installed custom recovery TWRP, but cannot mount /system partition -> Invalid argument error. I found some tutorials that suggest changing /system file system to FAT and then back to original file system, to be able to mount.

If I guess it right, the FS on your /system partition is Linux ext4, which does not have a lossless way to be converted to FAT that I am aware of, so I guess it's mostly formatting it twice: to FAT, then back.

It's obvious that formatting will make all data on that partition lost. However, if you find, or if the tutorial instructs, another way to losslessly convert ext4 to FAT, it's possible that you can change the FS without losing any data. But be aware that changing ext4 to FAT will mess up all the permissions on files, which may potentially lead to extra work before it turns into a usable state.

For example, if you set up your device without using root customizations ( changing build.prop, installing xposed or root access type modifications ) on the system, then all the data will be stored separately onto the data partition. A factory reset would usually only wipe the data partition and cache partition for this reason. Any system modifications can be saved by doing a backup first, then reformatting the system partition and restoring onto the new partition.. It's sometimes necessary to reformat the system because the entire system scheme has changed and probably requires more or less space, meaning the partition has slightly moved from it's physical location.

I have a 128 GB Micro SD Card that I formatted as ext4 and used in a Chromebook for an Ubuntu Chroot Environment. I used it for quite some time that way. At some point, I either deleted everything off of it or formatted it using the Chromebook's simple formatting system.

I went on a trip, took lots of photos and video, and then suddenly the GoPro was having trouble reading the disk. It was still able to record video and pictures (I assume) as I could turn on the recording mode and it didn't report any problems. From what I could tell, 128 GB is too much for this GoPro Session.

When I plug this into a computer (Chromebook, Mac OSX, Ubuntu) I either get an error (Chromebook & OSX) or I have the disk mount, but no viewable file structure when I open it with a file explorer. Totally empty.

At this point, it doesn't actually seem to me that there has been either data loss or corruption. I'm not sure what actually is going on, but suspect that something has gone awry with the file system- being ext3/ext4 in a GoPro rather than FAT32 or exFAT.

EDIT: I just used Disk Usage Analyzer and found all of the largest files that photorec recovered. Among them are many large .bz2 files, with files in them with no extension that are timestamped for the time I would have recorded the footage. I can open them and view this information with an archive manager, but am unable to extract them.

The first exFAT was unlabeled, and I was able to browse through it using terminal commands provided by testdisk. Contained in this partition table, which other programs such as gparted were unable to see, were all of the GoPro folders and files, in pristine order. Within the DCIM folder, I found all of my photos and videos with correct file names and time stamps- so recovery was not a matter of restoring corrupted files at all.

So today I turned on my Xiaomi Mi5 (I did not run any updates or anything before this, absolutely nothing) and all of a sudden, it was stuck in a bootloop. Now I want to completely wipe it, to fix this, but before that I want to recover my data. Is there any way I can access my files and recover my data? I can still access fastboot and the recovery (and ADB kinda). Also when I list the device in ADB devices, it shows up as b61077a4 sideload and im pretty sure it didnt always show up as sideload...

Something you can do is to try and get a working adb shell once you're in twrp and use adb pull to copy everything from your phone's memory to your pc, or you can just do backups with twrp. That's how I did it before flashing another ROM at least.

Thank you for your help, but I just fixed it. Because I installed twrp, I was able to access the files on my phone, through my pc (dont know why it didnt work before) and I recovered everything I needed. Though for some reason, I was only able to flash twrp using FWUL (a linux environment with a lot of android tools)

Try flashing in fastboot with the Mi flash tool. Feed it a fastboot rom according to your device found here. Set clean all in the bottom off the tool and start flash. (I recommend the global stable versions)

If it errors out on something like "failed to write boot" then you need to unlock your bootloader with the tool found here. You will need a mi account for this and a reason why you want to unlock it. Mine was "To install miui 8 global fastboot rom" and I got my unlock code 5 minutes after applying. You will need a device that receives a text. If you got permission its just as easy as putting your phone in fastboot and clicking next on the screen. If you did this just try the flash tool again.

Well, the problem was that my phone would always keep shutting down when in fastboot mode, the mi flash tool thought it was still flashing, not giving me any error. Also no my phone isn't rooted and yes I unlocked the bootloader long ago (came with some unofficial version of miui, that wouldnt get any updates, so I had to flash the proper version).

But now everything is fixed. I ended up installing twrp using FWUL, like I said before. From there, I could just wipe the device and flash the rom using twrp

This guide was written by one of our forum members SilverLeaf and was originally written as a forum post. This guide is intended for people who are looking to do quality data recovery using free tools. This guide is fairly technical requiring you to deal with the Linux command line. Some paid software is more straight forward than the steps here, but this is a great way to get the job done for free. Use at you own risk. Technibble and SilverLeaf take no responsibility for the loss of any data, business, reputation etc..

In will be using Parted Magic as a platform for this guide. I usually PXE boot (or boot from a live CD) the machine that I am working on to Parted Magic for this purpose. If you run linux on your test bench machine and prefer to attach the failing drives to it, this guide will give you the basics, but obviously the screenshots will be different.

For our purposes, this is relevant because we may want to image the complete drive (say /dev/sda), which includes everything (MBR, partition table, all partitions). Or, we may just need to image a single partition (say /dev/sda2). If you just need to recover files from a Windows partition, it is advisable to only image that particular partition (as opposed to the entire disk). If, on the other hand, you intend to rescue the whole drive, replace the failing drive, and re-image; then certainly image the whole drive so you get the MBR, etc.

At this point you will want to make note of the name of the drive or partition that you want to rescue, and the name of the drive where you want to store the image. Be aware, that if you have multiple drives installed, it is possible that these designations can change after a reboot; so be sure to double check before you proceed.

Another consideration is the integrity of the image file. When ddrescue has done all it can, you may still have a significant amount of errors. The terminal window that you started the rescue process in will display the number and size of the errors when ddrescue has finished running. If there are any, it is possible that the damage could be enough to render Windows unstable when cloned to a new drive, depending on where the damage is.

So, assuming everything is OK, install the new drive, connect the USB drive containing the image file, and boot up Parted Magic again. Browse to the image file on your USB drive and open a terminal (File->Terminal). Now, we have a few options on how to image the new drive. I usually use the *nix dd command. dd is very similar to ddrescue, Here is the command:

Now, knowing what we do about ddrescue so far, it is entirely possible to rescue directly from one drive to another, rather than to an image file. Again, be sure to make sure the new drive is an appropriate size as mentioned earlier. Both drives must be connected to the machine that is running linux, either natively or from a live environment like Parted Magic.

Using the command from Part 1 to view the attached block devices, determine the correct names for the drive to be rescued and the drive to be imaged to. Be careful here. If you get this wrong, you could easily image the wrong device to the wrong device, and have a real problem on your hands. Again, the command is:

Note that here we need to use a third drive (flash drive in this case, mounted at /media/PNY_usb) on which to store the logfile (rescue.logfile in this case). You can store the logfile anywhere to which you have write access, just not to either of the two drives involved in the imaging process. And again, the same caveats apply to the -r3 switch as in the example from Part 1.

Finally, a note about resizing partitions after restoring an image to a new drive that is larger than the original. For example: the failing drive that you rescued was 500gb; the new drive that you used is 750gb. After the restore process, you will now have a 750gb drive with 500gb used, and 250gb as unpartitioned space. You have a few options here:

3a8082e126