Hi, I've recently encrypted my M8. After using it almost a Month I've to say that performance has decreased a lot.
I don't want the Encyption any more, but when I try to decrypt the phone going to "Settings/Storage/Phone Storage" Encyption option is grayed out.
Ok, so I tried getting wrong 30 times the password when it boots, but when it says that is going to perform the Factory Reset, suddenly stops and restarts whitout wiping the phone.
As well when I get into Hboot and select Factory Reset, and also using TWRP option to Factory reset the phone the next text appears on the log:
===================================================
Factory Reset Complete
Failed
E: Unable to mount storage.
E: Unable to mount data/media during GUI start up.
E: Resource type (font) failed to load
E: Resource type (font) failed to load
E: Resource type (font) failed to load
Full SELinux support is present.
E: Unable to mount dta/media/TWRP/.trwprs when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
Formatting Cache using make_ext4fs function.
E: Unable to mount '/data'
Wiping Android Secure
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount storage.
==============================================
I can still use the phone, but wanna get rid of the Encryption.
My phone is Unlocked.
Hboot-3.16.
Team Win Recovery v2.8.1.0
- Thank you in advance.
Hello,
You have to have stock recovery before you are able to do a factory restore. If you know your CID you can download the correct recovery for your device and flash it.
You can find it here: http://forum.xda-developers.com/showthread.php?t=2701376
2103ehleec said:
Hello,
You have to have stock recovery before you are able to do a factory restore. If you know your CID you can download the correct recovery for your device and flash it.
You can find it here: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
He's not trying to do a restore, he's trying to do a reset, which you can most certainly do without a stock recovery.
He can also do a "factory restore" without a stock recovery by flashing a stock backup, which he can get from many threads here.
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
ramemo said:
Hi, I've recently encrypted my M8. After using it almost a Month I've to say that performance has decreased a lot.
I don't want the Encyption any more, but when I try to decrypt the phone going to "Settings/Storage/Phone Storage" Encyption option is grayed out.
Ok, so I tried getting wrong 30 times the password when it boots, but when it says that is going to perform the Factory Reset, suddenly stops and restarts whitout wiping the phone.
As well when I get into Hboot and select Factory Reset, and also using TWRP option to Factory reset the phone the next text appears on the log:
===================================================
Factory Reset Complete
Failed
E: Unable to mount storage.
E: Unable to mount data/media during GUI start up.
E: Resource type (font) failed to load
E: Resource type (font) failed to load
E: Resource type (font) failed to load
Full SELinux support is present.
E: Unable to mount dta/media/TWRP/.trwprs when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
Formatting Cache using make_ext4fs function.
E: Unable to mount '/data'
Wiping Android Secure
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount storage.
==============================================
I can still use the phone, but wanna get rid of the Encryption.
My phone is Unlocked.
Hboot-3.16.
Team Win Recovery v2.8.1.0
- Thank you in advance.
Click to expand...
Click to collapse
Do you have a nandroid from before you encrypted? Flashing that should solve the problem. You could also try flashing a new ROM with a full wipe.
ramemo said:
===================================================
Factory Reset Complete
Failed
E: Unable to mount storage.
E: Unable to mount data/media during GUI start up.
E: Resource type (font) failed to load
E: Resource type (font) failed to load
E: Resource type (font) failed to load
Full SELinux support is present.
E: Unable to mount dta/media/TWRP/.trwprs when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
Formatting Cache using make_ext4fs function.
E: Unable to mount '/data'
Wiping Android Secure
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount storage.
==============================================
I can still use the phone, but wanna get rid of the Encryption.
My phone is Unlocked.
Hboot-3.16.
Team Win Recovery v2.8.1.0
- Thank you in advance.
Click to expand...
Click to collapse
The error your getting is exclusive to that version TWRP .download the 2.8.0.3 version from there website and trust me it will be fine.
http://techerrata.com/browse/twrp2/m8
Can flash stock recovery and factory reset device and itll unencrypt it,you will loose downloaded apps but nothing else.
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
Happens across all builds of twrp,not build specific...just an fyi
jball said:
The error your getting is exclusive to that version TWRP .download the 2.8.0.3 version from there website and trust me it will be fine.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Can flash stock recovery and factory reset device and itll unencrypt it,you will loose downloaded apps but nothing else.
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
Happens across all builds of twrp,not build specific...just an fyi
Click to expand...
Click to collapse
I had latest TWRP and came across that same error and it's mentioned in other threads about that same version TWRP giving mentioned error.
Flashed 2.8.0.3 and never receive any errors
Its a known bug in twrp altogether....not just one build or another....
jball said:
I had latest TWRP and came across that same error and it's mentioned in other threads about that same version TWRP giving mentioned error.
Flashed 2.8.0.3 and never receive any errors
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Its a known bug in twrp altogether....not just one build or another....
Click to expand...
Click to collapse
I love to debate with you .
Even better I have no issues with Philz touch recovery [emoji12]
jball said:
The error your getting is exclusive to that version TWRP .download the 2.8.0.3 version from there website and trust me it will be fine.
http://techerrata.com/browse/twrp2/m8
Click to expand...
Click to collapse
Ok, I have given a try twice.
I flashed "openrecovery-twrp-2.8.0.3-m8.img", first try was doing a Factory Reset from recovery and the second using my 30 password attempts wrong on the encryption screen and nothing different happened, same error.
I used this options as it was the easy way, but since it didn't work for me, I'll flash a Nandroid backup or StockRom.
I apologize I didn't reply before, I'll report any issue just in case someone goes through the same problem.
Thank you all.
Been developing a long time...not a debate..lol...and your right you wouldnt have that issue with "philz" as its cwm and not twrp....
jball said:
I love to debate with you .
Even better I have no issues with Philz touch recovery [emoji12]
Click to expand...
Click to collapse
You won't believe what the solution was...
1.- Download the latest TWRP available (openrecovery-twrp-2.8.1.0-m8.img).
2.-Enter to Recovery.
3.-Go to "Wipe->Format Data" and type "Yes"
4.-All Wiped! (Internal Storage)
This option was developed to remove encryption, I didn't know about that before.
But now you know as well.
Thank you again for your help!
hello,
does someone know what problem i have and how i should fix this?
first of all, when i was wiping my phone it all went fine but it took to long so i turned off my phone and turned it back on, i got in an boot loop and couldnt even get into recovery mode because that would also led me into a ''teamwin'' bootloop, anyway i reflashed my recovery so luckily i can get back into recovery, but i still have bootloop for the system so i cant start up, but now i also face this problem.
i wanted to flash stock rom and this is the full error log i get ( i also tryed with custom rom but same problem)
_____________________________________________________________________________________________
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I also tryed wiping my phone, i tryed advanced wipe and full wipe and also factory reset, but i always get this same kinda error.
anyone know a fix for this?
Which version of twrp do you use?
i use Twrp 2.8.7.3
Try the last one : https://dl.twrp.me/Z00A/twrp-3.0.0-0-Z00A.img.html
Your zenfone 2 is WW or CN?
its CN
sorry for the kinda late answer tho,
well i wanted to flash the 3.0 twrp version, but it gives me an weird kind of bootloop, so thats why i downgraded to 2.8.7 :/
that's strange, are you sure it was for Z00A?
Look at this : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 to change to WW version.
Help! I flashed the Android Oreo Pixel 2 Mod over Android Oreo 8.1.0 with my apps and data on it, and then the phone wouldn’t boot. So I went back into the recovery (TWRP 3.2) and tried to wipe the phone. TWRP wiped everything except for /vendor, returning the error “Failed to mount /vendor (invalid argument),” and "Failed to mount /system (invalid argument)". In TWRP I also tried mounting /system and /vendor, but it wouldn't let me check the box. So tried installing the stock android from the google page, and while sending sparse file ‘system’, It says FAILED (data transfer failure(Unknown Error)). Please Help, I’m a pretty much a noob at this kind of stuff.
EDIT: SOLVED
After browsing online, I wiped the phone one more time, re-flashed TWRP, tried a few commands, I tried repairing the file system of /system, re-installed the vendor.img(probably this), then It worked!
I'm just thankful it works now.
TWRP won't start after updating from 3.3.. to 3.4.0-0 using fastboot. Output includes "Failed to mount '/data'" - see following post.
I guess because I accidentally ran fastboot unlock although it was already unlocked. (The TWRP website fastboot update procedure starts right back with installing the tools and I jumped in at the wrong place)
Tried installing previous TWRP version but no dice.
Any ideas?
I did a TWRP backup before all this. Not exactly sure where it's located but would like to recover it if possible. Will a factory reset likely overwrite it?
Lenovo P2 LineageOS 17.1 Kuntao
Output when booting to recovery:
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Unable to mount storage
Failed to mount '/data' (Invalid argument)
fs_mgr_mount_all
Full SELimux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands
Failed to mount '/data' (Invalid argument)
Formatting cache using mke2fs...
Done.
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?
Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.
SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.
For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…