My Malata T8 just updated to Malata_t8_smba_9701_cm9_3g ROM
http://forum.xda-developers.com/showthread.php?t=1864362
Afterward I found my internal storage "/data" only have 252MB but "/cache" storage has 2G, the partition status as
/dev/block/mmcblk0p3 Size:315M Used:250.5M /system
/dev/block/mmcblk0p4 Size:252M Used:136.7M /data
/dev/block/mmcblk0p6 Size:2.0G Used:35M /cache
If anyone can help me to change the 2G cache back to data for Apps installation.
Thanks !
Anybody can help ?
flying1628 said:
My Malata T8 just updated to Malata_t8_smba_9701_cm9_3g ROM
http://forum.xda-developers.com/showthread.php?t=1864362
Afterward I found my internal storage "/data" only have 252MB but "/cache" storage has 2G, the partition status as
/dev/block/mmcblk0p3 Size:315M Used:250.5M /system
/dev/block/mmcblk0p4 Size:252M Used:136.7M /data
/dev/block/mmcblk0p6 Size:2.0G Used:35M /cache
If anyone can help me to change the 2G cache back to data for Apps installation.
Thanks !
Click to expand...
Click to collapse
Whether there are anybody can help me ?
Hi for everyone! i need some help. I flashed my huawei y635 phone with a cm12.1 rom . the process was completed but when i reboot it enters to twrp recovery instead of load the system. the rom is ok because i proved before in the same phone.
I tried to swipe the cach, dalvik cache, data and reinstall the rom but didn't work.
this line appears when i install the cm12.1 rom:
... detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Symlinking
20%
40%
60%
Metadata
Preparing Install...
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
mount: failed to mount /dev/block/bootdevice/by-namme/system at /system: Device or resource busy
script succeeded: result was [/system]
...updating partitions datails...
...done
I would be grateful for any help.
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
E:failed to mount /data
Cannot mount /data and unable to find crypto footer.
E:failed to mount /cpefs
Click to expand...
Click to collapse
HELP ME!
natanjuniors said:
hi!
I have trouble when i put twrp and make wipe cache, system and dalvik. The phone gives me the following information:
Help me!
Click to expand...
Click to collapse
Format Data
natanjuniors said:
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
HELP ME!
Click to expand...
Click to collapse
Format data and fully wipe
You just erase or deleted files on your internal memory. But no biggie, just flash firmware with Odin (on windows) heimdall (on Linux).
Sent from my SM-J700P using Tapatalk
natanjuniors said:
Hi!
I have trouble when i put TWRP and make wipe cache, system and dalvik. The phone gives me the following information:
HELP ME!
Click to expand...
Click to collapse
Format Data ... Yes ...
JHAM2005 said:
Format Data ... Yes ...
Click to expand...
Click to collapse
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Mrntnn said:
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Click to expand...
Click to collapse
Ignore the cpefs error, it's erroneous and will be fixed.
As long as you can mount data you are good.
Mrntnn said:
hi!
i have the same problem on galaxy j7 2016. after formating data i have the error : failed to mount '/cpefs' (invalid argument). i tried the command :
mke2fs /dev/block/mmcblk0p4 and mount -w -t ext4 /dev/block/mmcblk0p4 but i have the same error : mounting /dev/block/mmcblk0p4 on /cpefs failed: inavalid argument
help plz
Click to expand...
Click to collapse
How to ... Unlock Memory and have Root on the J710MN with Nougat 7
https://forum.xda-developers.com/ga...d-7-nougat-t3674417/post73826249#post73826249
hey i have solution
first 1. flash letest twrp
2.flash magisk 19.2
3. reboot system
100% done
Hello:
I have a Xiaomi Redmi 5A stuck at boot logo. I was able to dump all partitions, including userdata, with miracle box software and test point, but it seems that userdata partition is encrypted.
Bootloader is locked, so I think I can't mount encrypted partition with TWRP whitout wiping data.
I can mount system partition. fstab.qcom content is like this:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait,verify
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,resize,reservedsize=128M,forceencrypt=footer <-----
/dev/block/bootdevice/by-name/cust /cust ext4 ro,nosuid,nodev,barrier=1 wait,check
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/devices/soc/78db000.usb/msm_hsusb_host* auto auto defaults wait,voldmanaged=usbotg:auto,encryptable=footer
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
Androrid version is 7.1.2 and MIUI V10.2.1.0.NDFMIXM
I know the pattern.
I have read about some expoits to get MasterKey. Here are some links
- *******forensicswiki.org/wiki/How_To_Decrypt_Android_Full_Disk_Encryption
- ********nelenkov.blogspot.com/2014/10/revisiting-android-disk-encryption.html
- ********area41.io/downloads/slides/area41_16_kunz_semioffline_attack.pdf
- ********github.com/laginimaineb/android_fde_bruteforce
I tried bruteforce script included in Santoku Linux and it gives me an error. I passed as header parameter first 2048 bytes of userdata partiton and last 16K as footer parameter.
At footer region, "aes-xts" string can be read.
I am afraid about doing a hard reset, if it will reset / change some kind of random key....
So I unlocked the bootloader, flashed TWRP, and everything went fine. But when I tried to get into TWRP it asks for a password even though I haven't set one.
If I go to cancel > wipe and try to format data it just gives me a lot of red text ("operation not permitted") saying it doesn't have the permissions for a data wipe.
So since the system is still working I went and did a soft data reset since I already flashed TWRP and it doesn't work.
I confirmed it and the device started restarting, but when it booted it booted into TWRP. From TWRP I went back to the system and my data was still there.
I will now download the stock rom and try to flash the stock recovery. Is the problem in TWRP or in my device?
My phone is Motorola moto g8 (XT2045-2)
As soon as the bootloader gets unlocked, a Factory Reset is executed internally, which means that the encryption key gets also deleted, hence you no longer can decrypt encrypted data.
xXx yYy said:
As soon as the bootloader gets unlocked, a Factory Reset is executed internally, which means that the encryption key gets also deleted, hence you no longer can decrypt encrypted data.
Click to expand...
Click to collapse
yes, I know but for some reason it is still asking for a password.
Try default password -> default_password
xXx yYy said:
Try default password -> default_password
Click to expand...
Click to collapse
tried that aswell.. I tried erasing the userdata and cache using fastboot, then set a password in the system and it doesn't work in twrp. even twrp can't format data.
xXx yYy said:
Try default password -> default_password
Click to expand...
Click to collapse
I found out what was wrong, still can't get it to work though.. So the userdata partition was a format TWRP can't decrypt (I think). So I reformatted the userdata partition to ext4 but I get stuck in a bootloop unless I again erase the partition. Any help to how do I format it so it actually boots?
Why don't you ask in the support thread on xda-developers if TWRP is built with encryption support at all?
according to recovery.fstab it uses FBE + metadata encryption, so you probably have to format userdata + metadata once
from fastboot
Code:
fastboot format:f2fs userdata
fastboot format:ext4 metadata
or
from adb shell or terminal
Code:
make_f2fs -f /dev/block/bootdevice/by-name/userdata
mke2fs -t ext4 /dev/block/bootdevice/by-name/metadata
how do I delete double posts?
aIecxs said:
Why don't you ask in the support thread on xda-developers if TWRP is built with encryption support at all?
according to recovery.fstab it uses FBE + metadata encryption, so you probably have to format userdata + metadata once
from fastboot
Code:
fastboot format:f2fs userdata
fastboot format:ext4 metadata
or
from adb shell or terminal
Code:
make_f2fs -f /dev/block/bootdevice/by-name/userdata
mke2fs -t ext4 /dev/block/bootdevice/by-name/metadata
Click to expand...
Click to collapse
Code:
Warning: userdata type is raw, but f2fs was requested for formating.
Formatting is not supported for filesystem with type 'f2fs'.
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
rav:/ $ make_f2fs -f /dev/block/bootdevice/by-name/userdata
/system/bin/sh: make_f2fs: inaccessible or not found
the metadata one worked fine
try mkfs.f2fs instead
aIecxs said:
try mkfs.f2fs instead
Click to expand...
Click to collapse
/system/bin/sh: mkfs.f2fs: inaccessible or not found
where am I supposed to use the adb shell command? in the recovery or while in the system?
can't I just wipe data from the stock recovery and then format metadata?
note with adb shell I meant in TWRP recovery (requires partition unmounted)
uwucake2020 said:
/system/bin/sh: mkfs.f2fs: inaccessible or not found
can't I just wipe data from the stock recovery?
Click to expand...
Click to collapse
aIecxs said:
note with adb shell I meant in TWRP recovery (requires partition unmounted)
Click to expand...
Click to collapse
oh ok wait a minute
I can't umount it..
Code:
127|sofiar:/ # make_f2fs -f /dev/block/bootdevice/by-name/userdata
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Trim is enabled
Error: In use by the system!
1|sofiar:/ # umount /data
umount: /data: Device or resource busy
@aIecxs what can I do here? maybe erase the partition using fastboot or do a factory reset/wipe data using the stock recovery?
edit: I had data transfer on oops
sorry for the ping tho, idk if you can see when I edit a message
/data is not the only mount point. there is also /sdcard (refer to df -a)
this is how it looks on Poco M3. in my case you can see userdata is sda11. sda11 is mounted triple, so we have to umount sda11 until it is completely unmounted
Code:
[root] /: find /dev/block -name userdata
/dev/block/platform/soc/4804000.ufshc/by-name/userdata
[root] /: ls -l /dev/block/platform/soc/4804000.ufshc/by-name/userdata
lrwxrwxrwx 1 0 0 16 1971-05-21 00:59 /dev/block/platform/soc/4804000.ufshc/by-name/userdata -> /dev/block/sda11
[root] /: df -a
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1788376 68504 1719872 4% /
tmpfs 1902824 572 1902252 1% /dev
tmpfs 1902824 0 1902824 0% /mnt
tmpfs 1902824 0 1902824 0% /apex
tmpfs 1902824 52 1902772 1% /tmp
/dev/block/sde53 364504 3876 360628 2% /cache
/dev/block/sda11 49394556 20677260 28717296 42% /data
/dev/block/sda11 49394556 20677260 28717296 42% /sdcard
/dev/block/sda11 49394556 20677260 28717296 42% /storage
/dev/block/mmcblk0p1 31150720 26539136 4611584 86% /sdcard1
/dev/block/dm-0 2923136 2821180 101956 97% /system_root
/dev/block/sde52 196528 118256 78272 61% /firmware
/dev/block/sde55 999320 583268 416052 59% /cust
/dev/block/sda6 11760 72 11688 1% /metadata
/dev/block/sda7 27632 2156 25476 8% /persist
/dev/block/dm-2 1479100 1374644 104456 93% /product
/dev/block/dm-1 1414572 1309996 104576 93% /vendor
[root] /:
aIecxs said:
note with adb shell I meant in TWRP recovery (requires partition unmounted)
Click to expand...
Click to collapse
got into a bootloop. "android system may be corrupt"
just format in TWRP recovery + stay in TWRP recovery and pull recovery.log, that's all you can do for now. this is for maintainer to look at
aIecxs said:
just format in TWRP recovery + stay in TWRP recovery and pull recovery.log, that's all you can do for now. this is for maintainer to look at
Click to expand...
Click to collapse
i don't think the problem is in TWRP, every time I format a partition to ext4 it bootloops :/
according to recovery.fstab /data is f2fs and /metadata is ext4. so formatting should work from fastboot and from twrp. you must not boot into android, reboot straight into recovery back again, then get recovery.log. boot loop is different issue, probably dm-verity
aIecxs said:
just format in TWRP recovery + stay in TWRP recovery and pull recovery.log, that's all you can do for now. this is for maintainer to look at
Click to expand...
Click to collapse
I just checked and the problem is in formatting the data partition, idk why tho
without recovery.log it's all just guesswork.. kindly re-read how to format