I've run in to the problem some other people were having too. A problem, where after fastboot flashing userdata.img (from stock factory image), I'm left with 23.03GB of storage on my device, even though it's a 64GB model.
I've Googled the problem, and people suggest running "fastboot format data" to fix it. But of course that will wipe all my settings and so forth. My question is if I can back up the data partition using TWRP onto an OTG device. Then run "fastboot format data" and finally restore data again using TWRP.
Would that work? And would it even fix the problem of the missing space.
For reference, the issue has previously been discussed here:
http://forum.xda-developers.com/nexus-6/help/nexus-6-64gb-23gb-free-space-t2953636
stokholm said:
I've run in to the problem some other people were having too. A problem, where after fastboot flashing userdata.img (from stock factory image), I'm left with 23.03GB of storage on my device, even though it's a 64GB model.
I've Googled the problem, and people suggest running "fastboot format data" to fix it. But of course that will wipe all my settings and so forth. My question is if I can back up the data partition using TWRP onto an OTG device. Then run "fastboot format data" and finally restore data again using TWRP.
Would that work? And would it even fix the problem of the missing space.
For reference, the issue has previously been discussed here:
http://forum.xda-developers.com/nexus-6/help/nexus-6-64gb-23gb-free-space-t2953636
Click to expand...
Click to collapse
Just so its clear the fastboot format does the trick. (I also did fastboot and vol scrolled to recovery and did a full wipe before the format)(that was prob overkill)
fastboot format userdata
fastboot format cache
fastboot reboot
I've never done that with twrp. I usually just dump my whole SD card to a hard drive then start fresh. Its a reasonable pain to ensure there are no problems.
Also wouldn't you have been totally wiped anyway if you were going back to stock? Have you been using it with 23gb for a while?
No, haven't been using it for long like that. Only a few days actually.
It's not that I have a lot of files, but I do have a lot of settings and app settings. I know I could probably use Titanium Backup to back that stuff up, but I don't trust that method do get everything and not mess something up.
One more question though. Why format cache too? I saw that suggested in the thread I referenced. But isn't it enough to format data? I guess it makes no difference really, but I'm trying to learn in the process too.
stokholm said:
I've run in to the problem some other people were having too. A problem, where after fastboot flashing userdata.img (from stock factory image), I'm left with 23.03GB of storage on my device, even though it's a 64GB model.
I've Googled the problem, and people suggest running "fastboot format data" to fix it. But of course that will wipe all my settings and so forth. My question is if I can back up the data partition using TWRP onto an OTG device. Then run "fastboot format data" and finally restore data again using TWRP.
Would that work? And would it even fix the problem of the missing space.
Click to expand...
Click to collapse
Yes and no.
Let me explain;
The first problem, which may or may not actually *be* a problem, is whether or not recovery will PERMIT a backup to an OTG. Assuming that it does, it unfortunately will only backup everything on the data partition BESIDES the "media" directory (where the "internal SD card" can be found).
To work around this, perform your backup TO the internal storage, then reboot back to Android, copy *everything" from the "internal storage" path to your computer (which will include the "backup" directory, whatever it happens to be called with the recovery you prefer). Then perform the fastboot format on the data partition, boot into Android skipping all the signin junk, copy everything BACK to the internal storage, reboot into recovery again, and restore it.
ALTERNATIVELY, and probably much easier (definitely much faster, since it should complete within a few seconds)...
I *believe* that most recoveries should include the resize2fs command (though I've never had an actual need for this, so haven't actually tested it), so via ADB into your recovery.....
Code:
umount /data
resize2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
should do the trick.
NOTE HOWEVER, it is generally recommended to backup any partition where you are resizing a filesystem PRIOR to resizing it.
HAVING SAID THAT, I've run resize2fs hundreds of times on hundreds of systems, and never had an issue with a grow operation.
Running resize2fs without a "size" parameter will grow the filesystem to the size of the partition. The partition table still holds the correct size, which is why "fastboot format" fixes the issue.
That was a great explanation, @doitright. Thank you for that. I will try resize2fs at some point.
stokholm said:
No, haven't been using it for long like that. Only a few days actually.
It's not that I have a lot of files, but I do have a lot of settings and app settings. I know I could probably use Titanium Backup to back that stuff up, but I don't trust that method do get everything and not mess something up.
One more question though. Why format cache too? I saw that suggested in the thread I referenced. But isn't it enough to format data? I guess it makes no difference really, but I'm trying to learn in the process too.
Click to expand...
Click to collapse
Resizef2s sounds relatively painless, but does again, as doitright says, require caution by backing up before.
About the cache thing. I think to do a full format, data and cache are on different blocks, so that might be why. But then again the SD card is mounted in /data/media so maybe only format data is needed and the cache is to help with something else or just to be cautious, I don't know.
Now I wonder (and this can be searched here in xda) if TWRP back up data is /data/data or /data minus /data/media? Because fastboot format data I think is all of data i.e. /data. This is worth knowing for the future. Especially since we are flashinging things to our phones and whatever else.
MunkinDrunky said:
Now I wonder (and this can be searched here in xda) if TWRP back up data is /data/data or /data minus /data/media? Because fastboot format data I think is all of data i.e. /data. This is worth knowing for the future. Especially since we are flashinging things to our phones and whatever else.
Click to expand...
Click to collapse
ALL recovery backups are /data/* EXCEPT /data/media, being "backed up" to /data/media/something.
It simply cannot be implemented any other way for devices without separate storage devices, otherwise the backup would back up previous backups, which would be just plain wasteful.
The /cache partition is practically irrelevant. There is quite literally NO REASON to ever worry about it. No reason to wipe it, no reason for format it unless it somehow becomes corrupt.
It doesn't seem like resize2fs is included in TWRP.
stokholm said:
It doesn't seem like resize2fs is included in TWRP.
Click to expand...
Click to collapse
The resolution really is as simple as you originally thought. Its a common issue I've seen a hundred times on the nexus 5.
Take a full TWRP backup and then copy your entire sdcard to PC.
Format data
Boot into android and do initial set up.
Copy sdcard backup back to device whilst booted into android
Restore TWRP backup
You can use the file manager in TWRP to copy your entire sdcard to USB-OTG and copy it back. Personally, I find this easier than copying to PC.
adrman said:
You can use the file manager in TWRP to copy your entire sdcard to USB-OTG and copy it back. Personally, I find this easier than copying to PC.
Click to expand...
Click to collapse
The reason I said to copy it to PC via android was that using MTP or adb in recovery will break the sdcard permissions, when it is copied back. If you're confident OTG in TWRP works differently to adb and MTP in TWRP, cool. I just haven't tested it myself so won't suggest it.
rootSU said:
The reason I said to copy it to PC via android was that using MTP or adb in recovery will break the sdcard permissions, when it is copied back. If you're confident OTG in TWRP works differently to adb and MTP in TWRP, cool. I just haven't tested it myself so won't suggest it.
Click to expand...
Click to collapse
I used OTG via TWRP's file manager, when I wiped to decrypt and everything came back properly. I would assume that would be the case here as well.
adrman said:
I used OTG via TWRP's file manager, when I wiped to decrypt and everything came back properly. I would assume that would be the case here as well.
Click to expand...
Click to collapse
Excellent
rootSU said:
Excellent
Click to expand...
Click to collapse
Channeling Mr. Burns? [emoji1]
adrman said:
Channeling Mr. Burns? [emoji1]
Click to expand...
Click to collapse
Always, aren't you?
From within TWRP there is an easy way to do this even after you have your phone all setup. This issue always happens on my Nexus 5 and Nexus 6.
I did this without doing a backup and after my phone has been used on marshmallow for a week or so.
Steps from within TWRP:
1. Wipe > Advanced Wipe
2. Select the Data partition.
3. Select Repair or Change File System
(Notice the Partition Size)
4. Select Resize
(Wait and shortly after see the partition size be up to full size.)
This doesn't appear to work on 6.0.1 custom Rom with systemless SU 2.61... gave me a bad partition error.
Guess I will have to wipe.
maamdroid said:
From within TWRP there is an easy way to do this even after you have your phone all setup. This issue always happens on my Nexus 5 and Nexus 6.
I did this without doing a backup and after my phone has been used on marshmallow for a week or so.
Steps from within TWRP:
1. Wipe > Advanced Wipe
2. Select the Data partition.
3. Select Repair or Change File System
(Notice the Partition Size)
4. Select Resize
(Wait and shortly after see the partition size be up to full size.)
Click to expand...
Click to collapse
I have come across this thread. Here is what worked for me. (in case somebody needs it in the future)
1. Boot into twrp, type
Code:
adb shell
2. list the mounted partitions
Code:
df
You should see
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1507020 24 1506996 0% /dev
tmpfs 1507020 24 1506996 0% /tmp
/dev/block/mmcblk0p38
253920 264 248416 0% /cache
/dev/block/mmcblk0p42
24143612 23590364 536864 98% /sdcard
/dev/block/mmcblk0p42
24143612 23590364 536864 98% /data
/dev/block/mmcblk0p41
2015408 1965276 33748 98% /system
3. unmount /data and /sdcard
Code:
umount /dev/block/mmcblk0p42
umount /dev/block/mmcblk0p41
4. run
Code:
e2fsck -f /dev/block/platform/msm_sdcc.1/by-name/userdata
resize2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
now you should see:
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1507020 24 1506996 0% /dev
tmpfs 1507020 24 1506996 0% /tmp
/dev/block/mmcblk0p38
253920 264 248416 0% /cache
/dev/block/mmcblk0p42
57306748 23598452 33691912 41% /data
/dev/block/mmcblk0p42
57306748 23598452 33691912 41% /sdcard
5. reboot, you are done
Related
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.
I'm panicking very much right now.
I did a big, big stupid and accidentally wiped my entire /data partition, including /sdcard (!!) in TWRP 3.0.4.1 while attempting to change the filesystem of my /data partition from F2FS to EXT4. I did a full backup of my phone, including /data partition (but excluding /data/media/0/ which is the location for /sdcard of course) on my phone prior to attempting to change the filesystem.
I didn't think that this would also wipe /sdcard, and ALL MY FILES INCLUDING MY BACKUP...
I'm frantically searching through Google as we speak for guides to clone these formatted sectors over USB (I'd imagine using ADB shell) to a PC and use Windows file or partition recovery tools to try and save every, if not most files.
Please lend me your knowledge and links to fixing this issue, Android community. <3
In older Android versions the /sdcard partition was it's own partition, which is why I didn't think of copying all my files over to a PC before making changes to /data.
well, when you wipe data from any partition in twrp it sort of resets all space to be overwritten. The data that is marked for overwrite doesn't remain when you full wipe. Since you changed the file system, the data was removed and overwritten by the wipe with blank space.... i hope you had at least some of it backed up on your pc. I never use those apps personally, i always hard backup all my things with a drag and drop onto my pc. I highly recommend it, saves you a disaster. Im very sorry.... i hope you didnt lose anything really important.
OcazPrime said:
well, when you wipe data from any partition in twrp it sort of resets all space to be overwritten. The data that is marked for overwrite doesn't remain when you full wipe. Since you changed the file system, the data was removed and overwritten by the wipe with blank space.... i hope you had at least some of it backed up on your pc. I never use those apps personally, i always hard backup all my things with a drag and drop onto my pc. I highly recommend it, saves you a disaster. Im very sorry.... i hope you didnt lose anything really important.
Click to expand...
Click to collapse
Heh, that's exactly what happened. I'm gonna attempt this guide: https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705
Basically try to use "dd" to make a RAW copy of "dev/block/dm-0" which according to the mount command I ran in TWRP's terminal shell, is what block /data is used on OnePlus 3T (OOS 4.1.3).
Wish me luck.
Hello,
As stated in the titled I have tried to root my OP 3T and it horribly wrong. First I got the error message telling me it couldn't mount my /system partition. I googled how to fix it and discovered that I had to wipe the partition as it might be corrupt. Just to be sure that it was indeed corrupt. The size was stated as 2913MB but the used space was stated as 1728265MB. I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...The only thing i can boot into was fastboot and recovery. I then tried to install the LineageOS and it worked. I can finally boot to a OS. However when going in the recovery again and wiping the cache I get a slew of errors. Almost all of them are "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)". There is also one other error: "Unable to mount storage"
How do I fix this?
uptivuptiz said:
First I got the error message telling me it couldn't mount my /system partition.
I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...
Click to expand...
Click to collapse
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.
redpoint73 said:
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.
Click to expand...
Click to collapse
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.
uptivuptiz said:
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.
Click to expand...
Click to collapse
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).
Dirk said:
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).
Click to expand...
Click to collapse
Thanks! I will try that when i get time tomorrow. There will come an update.
uptivuptiz said:
Thanks! I will try that when i get time tomorrow. There will come an update.
Click to expand...
Click to collapse
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.
Dirk said:
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.
Click to expand...
Click to collapse
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again
uptivuptiz said:
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again
Click to expand...
Click to collapse
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)
Dirk said:
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)
Click to expand...
Click to collapse
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...
uptivuptiz said:
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...
Click to expand...
Click to collapse
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.
Dirk said:
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.
Click to expand...
Click to collapse
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.
uptivuptiz said:
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.
Click to expand...
Click to collapse
You wouldn't be the first. It's a common issue. You know you can just move the zip to Internal Storage and flash it with TWRP? The Recovery is MTP enabled. Useful to know for future reference. :good:
Hello,
I've recently moved from the Stock ROM to Xiaomi.eu version, but it seems there is some encryption left over the /sdcard partition (I see all file/folders there as gibberish names). This seems to be affecting some applications that make use of that partition, as the camera or whatsapp for example. Does anyone know the partition layout of the phone? Is it possible to just format /sdcard without touching the rest of the /data? I believe a format of that partition and a restart should be enough to allow the phone to use that partition again...
AzureusPT said:
Hello,
I've recently moved from the Stock ROM to Xiaomi.eu version, but it seems there is some encryption left over the /sdcard partition (I see all file/folders there as gibberish names). This seems to be affecting some applications that make use of that partition, as the camera or whatsapp for example. Does anyone know the partition layout of the phone? Is it possible to just format /sdcard without touching the rest of the /data? I believe a format of that partition and a restart should be enough to allow the phone to use that partition again...
Click to expand...
Click to collapse
"Format Data" option in twrp that you put Yes in is the option to get rid of encryption.
Mohammed779 said:
"Format Data" option in twrp that you put Yes in is the option to get rid of encryption.
Click to expand...
Click to collapse
I formated data prior to installing Xiaomi.eu ROM, but it seems it didn't touched the /sdcard, not sure if its a limitation of the current beta TWRP (LR.Team) or it it was something else. Also the idea should be to proceed without reseting the phone and formating data would do so.
Long story short, I've been trying to get into my internal storage via TWRP but its saying that there are 0MB in the internal storage and that there is nothing in the sdcard folder
I've tried formatting it, hasn't worked
I've tried changing the format to FAT and then back to EXT4
then after that didn't work i tried the same but with EXT2 , it showed the amount of storage but still didn't let me see what was inside of the sdcard folder, whenever i'd go in there its just completely empty
Can I please have some help with this, I've been stuck on this for a couple hours now
Ouch! Please don't say that you just formatted userdata (/data).
You've just killed all your data on your phone.
No, I'm not that experienced with TWRP and I don't know which versions under which circumstances it can mount userdata.
I use custom recoveries and just presume that I can't mount userdata in them.
In the normal system (which mounts and decrypts) I use normal tools to sync or backup.
Renate said:
Ouch! Please don't say that you just formatted userdata (/data).
You've just killed all your data on your phone.
No, I'm not that experienced with TWRP and I don't know which versions under which circumstances it can mount userdata.
I use custom recoveries and just presume that I can't mount userdata in them.
In the normal system (which mounts and decrypts) I use normal tools to sync or backup.
Click to expand...
Click to collapse
I didn't format data it self i meant that i factory reset it, sorry i should of been a lot more clear on that
Oh, ok.
Well, in any case, if it's encrypted you need to mount it not with a simple "mount" command but something fancier using dm.
They don't try to make it easy to do.
Unless you're destroyed your system and you're trying to recover your data, whatever you're trying to do is best done in the normal system.
never mind i found a fix for it
well not really a fix just a way around it
thanks for the help ^^
SoftieIsVibing said:
never mind i found a fix for it
well not really a fix just a way around it
thanks for the help ^^
Click to expand...
Click to collapse
I had the same issue so I flashed a raw firmware after taking full system backup. Now TWRP is working fine.