I have a Mi A2 lite (msm8953), and I am trying to boot on two different data mounts. I managed to do it by mounting user data partition as /preData then mounting /preData/second on /data on vendor partition init files, and I booted successfully.
But when going back to the /data as /data, my unlocking pattern doesn't work and I have to delete "/data/system/locksettings.db".
My question is, since the process of booting to a subdirectory (/data/second instead of /data) of the actual data does not touch the actual /data/ files at all, how did the lock process get messed up for the primary data?
My guess is there's a specific partition involved in the lock process that's being modified, if I am correct, which one is it ?
Related
Sick of the separate userdata and fakesd partitions and familiar with Nexus 4's way of doing things (only userdata), I've tried to repartition my device.
The way I went about it was by booting a recovery (twrp), and, via adb shell, sharing the whole mmcblk0 via usb_mass_storage. It is a GPT partition table, so I used gparted, got rid of the "media" partition and then resized the userdata partition to cover all the gained space.
However, the whole partition layout resets (ouch) when I reboot at all. I do not know who if it's the bootloader or recovery's fault, only that any changes I make to the GPT partition table go away after I reboot.
I'd appreciate some intel if any of you know what's actually going on.
Hello guys !
So here's my question: I have a modified boot.img on my mobile that deactivates forceencrypt and dm-verity, which has the consequence of not encrypting the /data partition on the 1st boot, and then makes it accessible under TWRP.
If now I flash a stock boot.img, which involves the activation of FE and DMV, will my /data partition be encrypted ? Or will I remain status quo if we start from the premise that it is only at the 1st boot that the encryption is played?
Looking forward to reading you
I found time to test stock boot flash upon modified boot through TWRP: it turns in bootloop, surely because of the data on /data partition which are not in coherence with stock boot. Going on a /data format should bypass the bootloop problem, but I did not proceed.
For now, I have my answer, so it is OK.
Hi everyone. My phone (redmi 6 cereus) has realtively small system partition, so I decided to try to manually alter the partition table. I did that one time without any problems so I thought it would go smoothly this time. Boy was I wrong Like the last time, I resized my data partition, deleted system partition and created a new one to use all the space left available after shrinking data partition. After that I rebooted my device to twrp but this time I forgot to name that new partition as system (now its label is something like "Microsoft basic data partition") and now my device bootloops. I cannot even boot to recovery, fastboot is the only thing that boots.
I've tried booting twrp using fastboot boot twrp.img but that also resulted in bootloop. My theory is that my device is trying to mount system partition during early stages of booting, but it cannot find one so it crashes and reboots. So I thought that maybe I could extract boot.img and modify it so fstab would not have any references to system partition, but my boot.img has empty ramdisk. I've tried to to the same thing with twrp image, but there I could not find fstab file.
Maybe my thinking is wrong and there is another solution to this problem. Maybe it is possible to name partition from fastboot? I don't know, I'm pretty familiar with linux, but not so much with android. Any help would be appreciated
Hello, i have a Redmi note 9S which shipped with Android 10 out of box.. i'm using Dynamic System Updates (DSU) with unlocked bootloader to try custom roms and decided to modify some custom GSI to manually root it and customize some apps (modifications directly to system partition) but noticed that system partition can't be mounted as rw and gives error "wrong fs type, bad option,.." i can only mount it as ro.
I knew that this happens because ext4 partition formatted with EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (so called ext4 dedup) and this prevent it from being mounted as rw, trying to extend system.img with fallocate and resize ext4 file system with resize2fs and then use "e2fsck -E unshare_blocks" seems to work but the phone can't boot and trying to create a new rw system.img also fail as device doesn't boot, also i noticed that GSI versions with "vndklite" can be mounted as rw but same thing, it fail to boot when flashed with DSU and the device reboot again to the main OS..
So i have two questions here:
1) is that happens because the device refuse to boot system partition without EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS as it's already shipped with Android 10 and support this out of box or this happens because of DSU and will boot if flashed with fastboot?
2) and most importantly how can i modify system.img and then apply EXT4_FEATURE_RO_COMPACT_SHARED_BLOCKS (apply shared blocks feature on the file system) like what custom roms developers do so i can boot a modded system partition?
Any help would be appreciated.. Thanks!
same question, did you find answer?
Hello All,
Recently i applied local update on my one plus 8t and it wiped all my data everything is lost. Backup to drive and oneplus cloud was also NOT turned ON.
Any way to recover files ? I already tried Wondershare and few other applications but none of them worked.
One of my friend suggested RECUVA but its not showing my phone as a drive.
Please help.
May be an authorized service center has the means to recover the wiped data, means the forensic software needed. In any case, phone's Android must be rooted.
Don't trust the 3rd-party-softwares you've to pay for: are all more or less only crap.
Thanks for replying but can i mount my android as a drive (removable storage). just like flash drive.
it's pointless. FDE crypto-footer is garbage even if just a single byte is overwritten. FBE encryption keys aren't stored in userspace at all. your device uses both FBE + FDE. userdata partition is F2FS file system, no recovery tools will work. your data is unrecoverable per design
How to recover a deleted file from /data partition?
I factory reset my rooted Android M phone but now I realize that there was a file in the /data directory which I need. Is it possible to create an image (.img or something similar) of the /data
android.stackexchange.com
aIecxs said:
it's pointless. FDE crypto-footer is garbage even if just a single byte is overwritten. FBE encryption keys aren't stored in userspace at all. your device uses both FBE + FDE. userdata partition is F2FS file system, no recovery tools will work. your data is unrecoverable per design
How to recover a deleted file from /data partition?
I factory reset my rooted Android M phone but now I realize that there was a file in the /data directory which I need. Is it possible to create an image (.img or something similar) of the /data
android.stackexchange.com
Click to expand...
Click to collapse
so data on my samsung j4+ which was factory resetted (because i had to unlock the boot loader) cannot be recovered?
I was talking about OnePlus 8T. That's different from yours