Database Develop

TWRP error "E:Unable to mount '/data'"

I have a new LG Optimus L90 (D415) with stock 4.4 ROM, and TWRP 2.8.0.0 (and previously, Philz 6.58.7) for recovery. Obviously, the phone is rooted and now has an unlocked bootloader....
My problem is that neither recovery will back up (or even mount) "/data". Note that I put that in quotes because, without having "/storage/sdcard" or something in front of it, I presume that it's an internal folder and not something to do with the external SDcard.
My first guess would be a problem with encryption, because both the phone and the external SD are using it -- and I never get asked for the password. Either way, the actual error in TWRP says "E: Unable to mount 'data'", while Philz says it can't access /data/philz-touch for the .ini file.
I've made several Google expeditions to find the answer, and have come up empty-handed with all of them. I've seen all kinds of fixes, from claims that I have to run chkdsk against the SDcard, to backing up the entire /data partition with a tar file and reformatting it with command line nightmares.
I'll do what I have to in order to fix this, but I'd rather not embark on an experimental goose chase. Any ideas?

I have this same problem. But only for wiping and flashing.
I have no idea for fix if backup also not working !! (Noob)
1.TWRP click backup. Select all except SDcard.
Finish backup.
2.go to Wipe menu.>advanced wipe>select all except System and Sdcard.
Wipe.
(It will skip the error files)
3.Install menu. Select ROM to flash.
Was what I did.

fear2433 said:
I have this same problem. But only for wiping and flashing.
Click to expand...
Click to collapse
I'm not flashing anything, yet. First I need to make a backup of the entire phone (not including the SDcard). That way, if something goes wrong, I can just restore my old, working configuration -- all at once -- and start over.
I can back up and restore apps individually, using Titanium Backup. But what I need here is a Nandroid-type backup... and that generally has to be done from the recovery partition. There is one other way to backup everything, using a laptop/PC and ADB. But I've never tried it, and it wouldn't protect against a ROM meltdown.

Solved, somewhat...
So I did some further experimentation concerning this error. I did a test run to install CyanogenMod, and I found that I couldn't even factory reset certain partitions because of these "Unable to mount /data/" type errors.
What was ultimately the problem? The encryption. Once I decrypted everything, TWRP was able to see, mount, and backup, those partitions.
But I was under the impression that TWRP handles encryption, e.g. asking for the password, or some such. I mean, how can you do a Nandroid-type backup on a phone, if no recovery can mount those kinds of partitions?
So, for the record: "E:Unable to mount" was definitely due to the encryption being turned on for my internal storage. Thus the solution (so far) is to decrypt storage. A wretched solution, but at least it works for the time being.
BTW, In furtherance of this research, I formatted my internal SDcard to NTFS, just to make sure it wasn't misaligned or whatever when it was just FAT32. And I discovered that NTFS takes forever to format (32GB on the order of a couple hours)., FWIW.

The plot thickens. It may not be sufficient just to undo encryption, there may be something wrong with the way that partition was created, or otherwise is constructed.
Even though I now am able to mount /data, I'm not able to format it.... in TWRP it says something like "unknown filesystem 'auto'".
But there is a thread here that describes using Philz recovery to unmount and then format this mess, and I'm about to try it, I just have to flash Philz in place of TWRP. Now let's hope this version works without issues, because I'd have little recourse if things go bad there.

[Q] TWRP Backup failed - SD issues?

So I've searched quite a bit on this one and can't really seem to figure out what is going on.
I started on TWRP 2.7.1.0 and when backing up with adequate storage space I kept getting "backup failed". I tried 2.8.0.0, same thing, and finally 2.8.4.0 failed as well. I cleared a bunch of stuff off of it and was able to backup once. Two days later when I was going to try out a new rom, I decided to make a new backup and right back to where I am now - fails every time. I have 10gb free and the backup is less than 5gb. I was getting impatient wanting to update my rom, and figured since I already had one backup I may as well try to install a new rom - I tried to wipe data/cache/dalvik, and even that failed.
I attached two logs I saved from different backups. I've tried fix_permissions and nothing. I'm assuming this may be a error with the internal storage, perhaps my next step would be to format that partition (Is this just "format data" in TWRP wipe section?)
Thanks for the help!

Internal Storage Failure / TWRP Error 255

My TWRP nandroid backups started to fail out of nowhere with the following error message:
Code:
E:createTarFork() process ended with ERROR=255
And this appeared when doing any type of operation:
Code:
Updating partition details...
E:Unable to stat '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1'
After looking at the log, this is the full info when the error happens:
Code:
I:addFile '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1' including root: 1
E:Error adding file '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1' to '/sdcard1/TWRP/BACKUPS/ZX1C622JHV/2015-07-22--01-07-04_cm_thea-userdebug_5.1.1_LMY48B_ef0c42eec8_t//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/sdcard1/TWRP/BACKUPS/ZX1C622JHV/2015-07-22--01-07-04_cm_thea-userdebug_5.1.1_LMY48B_ef0c42eec8_t/data.info'
E:createTarFork() process ended with ERROR=255
This happened all of a sudden. I did not change anything at all, except for flashing a new CM version in between this and the last successful backup, 2 weeks ago.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Just thought I'd give you a heads up in case anything like that happens to someone else, not sure what the best approach is here, probably do some regular backups of your internal storage, but that's kind of tedious...

Did you try removing corrupted file? (/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1)

Couldn't start up the phone anymore. And don't know how to do it via adb. I only saw that error when I went into recovery after the phone froze and wouldn't boot up anymore.
Hmm, I could have probably used the TWRP filemanager, right?
It was very weird though, at one point even TWRP was not working reliably anymore, after 3-4 reboots it didn't even start up...

using condor.. moto e twrp 2.8.6.0 and same problem for me

using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me

Pranz... said:
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Click to expand...
Click to collapse
using motox xt1092 with twrp3.0.0.0 same problem

Pranz... said:
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Click to expand...
Click to collapse
Same Same : oneplus2 TWRP 3000

ericcostes said:
using motox xt1092 with twrp3.0.0.0 same problem
Click to expand...
Click to collapse
Hi try use TWRP (2.8.7.1) Link

Nexus 7 2012, CM 12, TWRP 3.0.0.0 - same problem

Oppo R7 Plus with the same problem, I´ve tried TWRP 3.0.0. and 2.8.7.

Someone solve this problem?

Note 4 / twrp 3.0.2.0 same problem

Might be a bit late for some, but I just ran into part of this problem myself ...
I did not have the trouble with recoveries, but I was getting the error 255 on backup operations. I am only trying to backup /data.
I was trying to backup to a 128GB USB OTG device, formatted to exFAT, on a OnePlus One.
The backup completed on the stick using the official TWRP, but before I wiped my data I wanted a second backup from a different recovery to ensure I was well covered. I installed TugaPower TWRP and that's when problems started.
Tried a few things, reverted back to 2.8.6 TWRP and wasn't getting anywhere.
Then I took out the stick and using a OTG adaptor I am now running a /data backup to a 32GB micro SD card, also exFAT. It hasn't completed yet, but the older ones would always stop quickly. 15% now ...
Short story ... check the media you are backing up to, there might be an incompatibility there rather than an issue with your device or the recovery.
I will try and do a backup with the TugaPower TWRP on the 32GB card after, too. If that works, then I know that some recoveries have OTG issues.

How to fix error 255 .
I cannt great back up and back up ended with error 255 plz help
Sent from my Le X820 using Tapatalk

Can access fastboot and Recovery, but cannot flash anything

Hello and greetings from germany,
I have a problem with my Moto G 2014 XT1068. I'm coming from rooted stock KitKat (Xposed) with open bootloader and TWRP 2.8.6.0. Everything seemed fine until yesterday, when the phone just went off (0% battery) and stayed at boot animation.
I've tried a lot of things, but the phone seems to be hardbricked:
- I can access recovery, but restoring does "FAIL" (restoring boot partition works, though). Restoring "system" aborts at about 18%, "data" immediately.
- I can access the phone through fastboot, but cannot flash anything. Whatever I do, the phone isn't changed. Tried reverting to stock (getting error when flashing gpt.bin, everything else seemed to work without errors, but no changes), tested flashing other recoveries (partition size mismatch, but that seems to be normal, whatever I flash, it keeps being TWRP 2.8.6.0), or even upgrade the bootloader (no errors reported at all, but no changes made to the phone).
- I can access the phone by MTP from TWRP, but cannot write to or delete anything from the internal SD.
Do you have any further ideas or is it an hardbrick?
Thanks in advance
René

Seems like the internal SD card is damaged, or there's a faulty partition table. Have you tried repairing and formatting /system and /data partitions with TWRP? Does it read external sd cards? If yes you could try flashing CM11 (because lollipop roms need an updated bootloader) from an external sdcard and see what happens. Also your backup could be corrupted, that's why it doesn't let you restore it at all.
As for the recovery, try updating your twrp to the latest version available (3.0). You can update twrp from twrp itself, just to see if it's fastboot's fault.

Wiped /system and /data. Didn't help. Wiping /data/media led to an error.
Is there anything beyond "wipe" to repair and format those partitions?
Thanks for the hints, will try updating TWRP and installing 11 this weekend, as external SDs can be accessed.
Greetings from Germany
René

Updated to OOS 9.0.4 from Oreo on Encrypted Rooted 3T :| , hoping to save SD Data

Hello guys,
I did a foolish update today without reading the forums first and updated to OOS 9.0.4 (Pie) from my previous stable OOS Oreo without removing encryption and backing up the Internal Storage data. I did take a backup of Boot, Data(excl storage) and System Image using TWRP 3.3.1 and copied it to my computer.
After the update, the OS refuses to decrypt the partition (Error: Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. To resume, you need to factory reset the phone.) and TWRP fails to decrypt (Error: Decrypt took too long. Killing process, failed to decrypt data).
What else I tried:
1.) ADB restore the backup from the PC (as I can't transfer anything to the phones encrypted storage), but the TWRP backup is a bunch of files in a folder and ADB expects a single file in its command.
2.) Flash an older version of TWRP (3.2.3) and try decrypting (Error: Failed to decrypt data)
Is there any way I can restore the backed up files to get the phone back before the update and save my internal storage? (without a time stone or a quantum jump). I am thinking along the lines that I can somehow restore the backed up files into the respective partitions and make the decryption work, is it possible?
Worst case is there some way for me to backup the internal storage data with the encryption then go about downgrading the phone and restoring it and decrypting it back?
Any pointers would be helpful and appreciated. Thanks.

Gi__an said:
The password you entered is correct, but unfortunately your data is corrupt.
[...]
Is there any way I can restore the backed up files to get the phone back before the update and save my internal storage?
Click to expand...
Click to collapse
The only thing you might try is to flash OOS 9.0.4 firmware with 5.0.8 bootloader + keymaster.
If it still says the same, then sorry, but your data got corrupted and it's gone.