Related
What is encryption?
Basically, if you lose your phone and someone wipes /data on Recovery mode, the phone boots with NO lock screen, your apps will be gone but YOUR FOLDERS becomes exposed, that means Whatsapp history and media, pictures, downloads, documents. Stuff you wouldn't want in the hands of thieves/strangers.
Does it affect performance?
It does increase memory readings on every phone. But z7 Max doesn't show any lag at all!
Tested ROMs able to ENCRYPT:
- CM13 beta7 by PaoloW8
Tested ROMs able to DECRYPT:
- Ressurection Remix M by pchatzop
(if you wanna try for yourself, please first MAKE FULL BACKUP of your storage folders, files and appdata)
Requirements:
1. External SD Card
2. Crypto footer
3. CM13 beta7
4. Secure screen lock (PIN, Pattern, Password)
5. Pchatzop's Ressurecution Remix 5.7.4 and GApps 6 (IN SD CARD)
Steps:
0. Boot to TWRecoveryP
1. Open Advanced > Terminal
2. Enter
Code:
umount /dev/block/mmcblk0p23
3. Enter
Code:
e2fsck -f /dev/block/mmcblk0p23
4. (this will resize storage LOSING DATA) Enter
Code:
resize2fs -f /dev/block/mmcblk0p23 6896600
5. (second data error check just for safety) Enter
Code:
e2fsck -f /dev/block/mmcblk0p23
6. Back to TWRP home menu > Install > flash CM13 beta7 and the same GApps you're going to use on RR ROM. (let's avoid future FCs). Wipe Dalvik/Cache then reboot to system.
7. Wait for system bootup
8. Head to Settings > Lock Screen
9. Set a secure screen lock
10. Head back to Settings > Security > Encrypt phone > Encrypt
11. Enter password > Encrypt
12. Wait for a while depending on the size of your used storage.
13. Screen lock input shows upon boot then decrypt successfully THIS TIME ONLY, so head back to TWRP.
14. Have your SD card inserted with your RR ROM and GApps. As of November 24, TWRP builds for the Z7 Max CAN'T decrypt storage so ignore screen lock input and head straight to TWRP main screen > Wipe > Advanced Wipe > Check CACHE and SYSTEM only!!!
15. TWRP main menu > Install > flash your ROM and GApps > Reboot and decryption input should show and decrypt on every restart, even if you change your password.
NOTE: To Decrypt Data you have to head to TWRP > Wipe > Format Data > Type "yes", meaning you will LOSE ALL DATA TO DECRYPT so BACKUP first.
3njoy!
bump
Can not get this to work, in order to try my modified twrp. I have tried beta 2 and Rel V9,still stuck at bootscreen. Done the resize2fs, and got past the overlap error, but still stuck at the bad magic error. Will try the beta7 and see if something changes. Do you have the /data original block size in order to revert the resizing? Didn't occur to me to save it Well, there is always nubia updater tool if i get too OCD .
pchatzop said:
Can not get this to work, in order to try my modified twrp. I have tried beta 2 and Rel V9,still stuck at bootscreen. Done the resize2fs, and got past the overlap error, but still stuck at the bad magic error. Will try the beta7 and see if something changes. Do you have the /data original block size in order to revert the resizing? Didn't occur to me to save it Well, there is always nubia updater tool if i get too OCD .
Click to expand...
Click to collapse
Sorry about the delay, final exams.
My original block size is 6896635. This thread is outdated, my new reports makes some info here invalid
Keep up the good work
Thank for the report, i made some STUPID mistake and mixed the fstab.qcom arguments with the twrp fstab argument, which resulted at data being mounted at failsafe mode, thefore not using any of the footer arguments i used,resulting at the recovery not finding the footer. I revert the twrp fstab to the twrptest2 level while keeping the decryption libs intact. New build is up, give it a spin .
pchatzop said:
Thank for the report, i made some STUPID mistake and mixed the fstab.qcom arguments with the twrp fstab argument, which resulted at data being mounted at failsafe mode, thefore not using any of the footer arguments i used,resulting at the recovery not finding the footer. I revert the twrp fstab to the twrptest2 level while keeping the decryption libs intact. New build is up, give it a spin .
Click to expand...
Click to collapse
OK Twrptest4 formats and resizes correctly but doesn't decrypt yet
Kerneltest1 was better than kerneltest2. Flashed both after CM13 beta7, both kernels enabled f2fs support for Paolo's CM13, kernel1 encryption works on first tries on both ext4 and f2fs (on cm13, not RR), kernel2 always give bad superblock. I guess it is not something just in kernel at all but on RR or CM recent builds :?
As a Senior Member, you have more chance of getting response from @luca020400, @luk133, @Vidhanth, @Vatsal (they all contributed for moto G 2014 encryption on ROMs and TWRP) or @golden-guy, @Android-Andi (for s3 mini's)!
Keep up the good work!!
That is a great report, thank you so much! I will check the diffs between kernel 1 and 2, and will get you a twrp with the configuration of kernel 1 with decryption libs. F2fs encryption working is a great step forward. You are right about the second part, kernel does work, but seems like cyanogen source broke the encryption on later builds. I want to get this to work, and even incorporate it in my nougat builds, but twrp needs to work first! Does twrp find the footer but fail to decrypt, or does not find it at all?
---------- Post added 3rd December 2016 at 12:06 AM ---------- Previous post was 2nd December 2016 at 11:17 PM ----------
Just made a new test kernel, together with a new recovery with the above changes. Hope something changes now(at least the kernel should encrypt fine). I also have the qseecomd blob from cm13 beta7 in the folder, i have a feeling that if we replace that blob in the latest RR with a kernel that can encrypt in beta 7, encryption should work there too. Hope you can test and report back. Feeling we are closer to cracking(pun intended) this!
pchatzop said:
That is a great report, thank you so much! I will check the diffs between kernel 1 and 2, and will get you a twrp with the configuration of kernel 1 with decryption libs. F2fs encryption working is a great step forward. You are right about the second part, kernel does work, but seems like cyanogen source broke the encryption on later builds. I want to get this to work, and even incorporate it in my nougat builds, but twrp needs to work first! Does twrp find the footer but fail to decrypt, or does not find it at all?
---------- Post added 3rd December 2016 at 12:06 AM ---------- Previous post was 2nd December 2016 at 11:17 PM ----------
Just made a new test kernel, together with a new recovery with the above changes. Hope something changes now(at least the kernel should encrypt fine). I also have the qseecomd blob from cm13 beta7 in the folder, i have a feeling that if we replace that blob in the latest RR with a kernel that can encrypt in beta 7, encryption should work there too. Hope you can test and report back. Feeling we are closer to cracking(pun intended) this!
Click to expand...
Click to collapse
twrp does find the footer but fail to decrypt, even the Default Android password dont decrypt, I have the TWRP log at home if you want.
When I get home I'll download your new tries.
Thanks again, regards
Good, that means that either the service does not start, or that the zuk decryption libs are incompatible with z7max encryption model. The logs would be great. Meanwhile, im getting a new recovery with all decryption libs replaced with nubia counterparts, so that you can test both variants and see what is really stopping it from decrypting. Its in the folder too.
pchatzop said:
Good, that means that either the service does not start, or that the zuk decryption libs are incompatible with z7max encryption model. The logs would be great. Meanwhile, im getting a new recovery with all decryption libs replaced with nubia counterparts, so that you can test both variants and see what is really stopping it from decrypting. Its in the folder too.
Click to expand...
Click to collapse
Oh, I tested your RR N, it shows decryption screen lock input but after decryption it bootloops, mostly because the /data has Marshmallow stuff, so we need to fix TWRP first to wipe /data without wiping /media along :highfive:
Got a new twrp in the folder, plenty more testing for you! Is beta7 the last build encryption works? Because i can check the github diffs between beta7 and beta8 and see what i can revert to try getting it working again in the latest builds. That is if it is positively the last build that encryption works.
pchatzop said:
Got a new twrp in the folder, plenty more testing for you! Is beta7 the last build encryption works? Because i can check the github diffs between beta7 and beta8 and see what i can revert to try getting it working again in the latest builds. That is if it is positively the last build that encryption works.
Click to expand...
Click to collapse
Yes it is beta7! I tried beta8, V1.... with your boot.img3, encryption starts but gives the same unsuccessful screen from RR. Only beta7 reboots to decryption input.
Also, I have suspicions: as your TWRP set data partition to 6896631 which was originally 6896635, the password MUST BE OF 4 characters (6896631 - 6896635 = -4) for encryption to work?
Unfortunately, no TWRPtest could decrypt yet, it finds the crypto footer but fails. Attaching twrp log and encryption success logcat:
So boot3 works with beta7? I will sift through the logs, think this is a selinux issue introduced in beta8, i will get a new build and try it on my phone, maybe it will work this time.
I got a new twrp in the folder. Spend 5 hours trying to get RR-M to encrypt, tried selinux changes, test builds, replacing blobs with some from beta7, still not there. I could get it to begin encrypting sometimes by rebooting in safe mode with root disabled, but got the encryption unsuccessful screen. There is something that does not allow /data to get unmounted properly during the soft reboot for the encryption, and even when it does, it gets stuck in another point. Hopefully the new twrp will decrypt an already encrypted system.
Got a new twrp in the folder, my attempts at encrypting have failed so far, most i could get was here: "Cryptfs : Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt" where "12-31 13:32:09.246 237 306 I Cryptfs : Encrypting from block 0" wuld be on your log. I will attach it , and hopefully you can try to help me, since you have more exprerience with encryption. Hopefully something changes at the recovery front.
pchatzop said:
I got a new twrp in the folder. Spend 5 hours trying to get RR-M to encrypt, tried selinux changes, test builds, replacing blobs with some from beta7, still not there. I could get it to begin encrypting sometimes by rebooting in safe mode with root disabled, but got the encryption unsuccessful screen. There is something that does not allow /data to get unmounted properly during the soft reboot for the encryption, and even when it does, it gets stuck in another point. Hopefully the new twrp will decrypt an already encrypted system.
Click to expand...
Click to collapse
pchatzop said:
Got a new twrp in the folder, my attempts at encrypting have failed so far, most i could get was here: "Cryptfs : Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt" where "12-31 13:32:09.246 237 306 I Cryptfs : Encrypting from block 0" wuld be on your log. I will attach it , and hopefully you can try to help me, since you have more exprerience with encryption. Hopefully something changes at the recovery front.
Click to expand...
Click to collapse
Hey, thanks and sorry for taking your time! Did you try a password/PIN/Pattern 4-character/digits/dots long?
TWRPtest8 doesn't decrypt yet
Could you please make your TWRP "Copy Log to SD" save the log in the external SD when available? It is always trying to save in /data/media, but as it is encrypted, the file goes nowhere. So I always have to format, save the log and re-encrypt :highfive:
Keep up the good work!:highfive:
So I know CM 13 used full disk encryption. With Android 7.0 file based encryption was introduced. Does anyone know if the new Lineage 14.1 uses full disk encryption or the newer file based encryption. I'm full disk encrypted right now but I'd happily start over with file based encryption if that is the case.
Not sure about this but can you can recovery working when using encryption in CM13? TWRP for me just says cannot mount data
Since it's nougat, it is probably file based encryption
Since they usually just pull down commits from upstream to the CM14 source, I'm pretty sure that yes indeed, file based encryption is in use.
Hello,
I sucessfully flashed lineageos from last Wednesday (2017/10/25). And the latest Gapps Aroma release. In the aroma release I selected only a few apps (GMaps, Youtube, ...).
Unfortunately when I try to encrypt my phone, the phone starts and the android mascot is comming but the phone restarts afterwards
I tried to do without SD-card. Same problem.
I read that there are some Google Apps needed for the encryption. But I could not find out which Gapps are really required. (I only want a few Gapps that I really need!) - Does some one hafe a list what is needed with encryption.
I did an encryption wiht the release 2017/09/20 and this worked. But unfortunately I didn't installed the Gapps and could not use Play Store. Installing later let the GApps Pico crashed. So I recreated the /data/ partiion using mk2fs.
As I read, I should install both together (Lineageos and Gapps) - so I did with twrp (it gives me the possiblity to install two zips [in that step I used the latest lineageos release]). This works fine, but the encryption process does now not work?
Have you decrypted your phone before flashing new rom?
I could find something, but see below the boot is not working any more.
The problem was that I did an encryption with lineageos before BUT I did the installation of the Gapps not directly with lineageos so I got a crash of the Gapps.
For reinstalling I must recreated the data partition. I did with:
mke2fs -t ext4 /dev/block/mmcblk0p12
After analysing the log output (adb log ) carefully I found the following lines in the output:
10-31 19:55:21.291 1958 13454 E Cryptfs : Bad magic for real block device /dev/block/mmcblk0p12
10-31 19:55:21.291 1958 13454 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
So I analyzed my current block size - mounted the device with twrp and used df for the output of the mounting and looked at the current size, and decremented 16KB block size (see post below):
mke2fs -t ext4 /dev/block/mmcblk0p12 56867076
The relavant post with the 16KB block size;
https://dustri.org/b/cyanogen-reboot-without-encrypting-the-phone.html
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/342
Now the encrpytion started but after restart the lineage os logo is just puting the circle from right to left....
I can insert the encrpytion password and it is accepted. Afterwards the boot in the lineageos starting screen hangs
Unfortunately the Power Up button is defect, so no recovery can be started or the download mode can be confirmed...
adb is not working - no log, no shell for booting to recovery
Goodbye phone - I think no chance... it was a try, but without the hardware buttons...
what do you mean power up button is defect? you removed it? if it is in place or was removed carefully there is possibility that you can solder new one from ebay ($1 at most) so it is possible to repair any way
Yes. But I don't have the hands to do it. This is nothing I can do. I already searched the tutorial.
I'll try with a jig then i can come to download mode.
And hopefully the adb bridge is working in download mode to reboot recovery. This is where I'm not sure and then in recovery i can flash new software and look for the encryption.
Is adb working in download mode? So that I can
Reboot into recovery. Or any other odea.
The jig needs 2 weeks to ship.
I got it now working...
With the Jig I flashed the Stock rom to have a working system.
From that I could flash the recovery again.
With help of the recovery I flashed the lineageos build w0171101 and the encryption than worked. I did not Lock the handy using a password first and then started encryption. Afterwards I changed to use password. So everything is working now And I am happy.
Twrp 3.1.1.0 is also able to mount the partitions with encryption.
Thanks for your help :good:
Device: Xiaomi Mi 9
ROM: [ROM][10.0][Xiaomi Mi 9][UNOFFICIAL]Pixel Experience [AOSP[2020/04/11], ROM for the Xiaomi Mi 9
Hi,
I tried to upgrade my ROM from an older to a newer version with a clean install whilst keeping the Internal storage of my Mi9.
The Device has been encrypted with FBE protected with a pattern.
While performing the upgrade TWRP did sucessfully decrypt the data.
Now after performing the update the phone was only able to boot into TWRP (3.3.1-62) and wasn't able to decrypt /data/media/0
I also tried do decrypt via adb shell with
Code:
twrp decrypt 563258
following the TWRP commandline guide
Code:
[123] [⭘↓←]
[456] [⭘↦↑]
[789] [⭘⭳⭘]
but this also failed.
Only way to make the phone boot again was to format data partition in TWRP.
Unfortunately I did not save my backups on a different device, so to say all my backups and data is on the encrypted drive, which I can't access anymore.
Before wiping I saved an image of /dev/block/sda31 which is the data partition I'd like to recover.
I am also able to access the keys or data at following locations:
Code:
/data/misc/vold/keystore/
/data/misc/vold/user_keys/ce
/data/misc/vold/user_keys/de
/data/unencrypted/key
/data/system_de/0/spblob
So my question now is how to regain access to my data.
So far I tried several approaches, none of these lead to success.
My hope is that there is a possibility to mount the image, using the available encryption keys. But that's at this point beyond my technical skills, so maybe here is someone with another idea how to do this.
Essentially copy/paste from the official TWRP for redfin thread, except I've made my own unofficial build for the Pixel 4a5G that in my own testing appears to be on feature parity with the official build for the Pixel 5! There are reports of the Pixel 5 build not working on devices with Android 12 and a PIN set at this time, so I advise against using this build if you've upgraded to Android 12 on your Pixel 4a5G and require having a PIN for your day to day.
I've decided I might as well try to maintain the device since no one else is doing so yet. I've pushed the trees I've modified to GitHub so y'all can keep track and maybe help out before I submit them for official status.
device/google/bramble: https://github.com/JoshuaDoes/twrp_device_google_bramble
device/google/redbull: https://github.com/JoshuaDoes/twrp_device_google_redbull
You can find the latest unofficial test build here: twrp-3.6.0_11-0.1-bramble.img
Boot it with `fastboot boot twrp-3.6.0_11-0.x-bramble.img`, decrypt your data if necessary, then install it permanently by navigating to `Advanced -> Flash Current TWRP`. Test by navigating to `Reboot -> Recovery` and you should reboot back into TWRP!
Changelog
11-0.1 (1/16/2022):
- Fix missing libion dependency, which appears to allow booting and installing TWRP if A12 is installed
11-0 (1/13/2022):
- Sync bramble with patches from redfin
You can find the historical builds here (but please don't use them): https://files.joshuadoes.com/TWRP/twrp-11/bramble/
Thank you it's so cool but update my pixel 4a 5g to A12
Stay an update too for it
I've ran into a `ErrorCode::kError` issue trying to install the latest official LineageOS 18.1 ZIP, but everything else appears to be working!
fastboot boot twrp-3.6.0_11-0-bramble.img
It sees partitions and super.
I hit compresson option and confirm/change name and it's backing up. adb appears to work (didnt check too into it). Just booted it and see if I can make a backup--AND I CAN. Good work @JoshuaDoes ! Good good job!
smokejumper76 said:
fastboot boot twrp-3.6.0_11-0-bramble.img
It sees partitions and super.
I hit compresson option and conirm/change name and it's backing up. adb appears to work (didnt check too into it). Just booted it and see if I can make a backup--AND I CAN. Good work @JoshuaDoes ! Good good job!
Click to expand...
Click to collapse
I did a successful data restore earlier today, just remember to disable your PIN first and then reboot immediately after the first boot following the restore
what if I just have no pin/password. just swipe to unlock? i did see a message in backup log 'sucessfully decrypt with default password'.
smokejumper76 said:
what if I just have no pin/password. just swipe to unlock? i did see a message in backup log 'sucessfully decrypt with default password'.
Click to expand...
Click to collapse
You're in the best case scenario then, just make sure you always disable PIN before restoring a backup so long as it gives you the warning to do so (I get the warning because I have a PIN, but you should just be free to restore as you please)
awesome. Only things I notice not there (and in no way complaining as its a WIP) is encryption option, and date seems to be stuck on 1970 and time way off despite changing time zone. But that's minor right now. The fact you got this going is no small feat. I am so glad I got a 4a5g (5/5a would have been fine too) and not a 6. You should put a donate link so we can buy you some coffee or weed or something, lol. Again great job. Feel free to hit me up if you need me to destroy my phone for you (testng). I got a dd backup, and now twrp backup so between all of that and the alfabet of partitions I should be able to restore from just about anything short of EDL crap out and I'm sure if that's not resolvable by now, it will only be a matter of time.
smokejumper76 said:
awesome. Only things I notice not there (and in no way complaining as its a WIP) is encryption option, and date seems to be stuck on 1970 and time way off despite changing time zone. But that's minor right now. The fact you got this going is no small feat. I am so glad I got a 4a5g (5/5a would have been fine too) and not a 6. You should put a donate link so we can buy you some coffee or weed or something, lol. Again great job. Feel free to hit me up if you need me to destroy my phone for you (testng). I got a dd backup, and now twrp backup so between all of that and the alfabet of partitions I should be able to restore from just about anything short of EDL crap out and I'm sure if that's not resolvable by now, it will only be a matter of time.
Click to expand...
Click to collapse
Encrypting backups? I didn't realize that was missing so I'll look into it too, but yeah the date is stuck which screws with file and backup times and I def need to fix that. XDA forbids me from putting a donation link in a post, however if you go to my profile and expand the info details about me it lists my PayPal email there and I'd super appreciate it! Because lemme tell ya, it took energy drinks and some good highs to do most of my Android work and thankfully this TWRP build only took me a few hours to tear into lmao. If you got a Discord I'm most active there as well as the Pixel 4a5G/5 Telegram (I can get a link to all if you've got them), and having extra testers for some of what I wanna do would be phenomenal as well! And we're Qualcomm, there's a flash tool out there somewhere for the worst of board states
Sorry for the wall of text lmao, I appreciate the kind words for sure and I'm likely gonna try maintaining this device officially for TWRP too
Hi ! Thank you for all your work. I was surprised when buying my Pixel 4a 5g when it came out that there was no Twrp because of Android 11. But coming from Xiaomi and Oneplus there were unofficial ones for Android 11 and 12.
When you can update it for A12 I have noob question. After flash the Twrp and boot it (with no pin) I can make a backup of all my Pixel. Copy it on my Pc and them do format data ? Or not necessary ? If I do format it them boot the Pixel and when it start check dev options, adb and reboot to Twrp Root (Magisk) and restore my data ? If not how to make a backup of my data.
Thanks
JoshuaDoes said:
Essentially copy/paste from the official TWRP for redfin thread, except I've made my own unofficial build for the Pixel 4a5G that in my own testing appears to be on feature parity with the official build for the Pixel 5! There are reports of the Pixel 5 build not working on devices with Android 12 and a PIN set at this time, so I advise against using this build if you've upgraded to Android 12 on your Pixel 4a5G and require having a PIN for your day to day.
I've decided I might as well try to maintain the device since no one else is doing so yet. I've pushed the trees I've modified to GitHub so y'all can keep track and maybe help out before I submit them for official status.
device/google/bramble: https://github.com/JoshuaDoes/twrp_device_google_bramble
device/google/redbull: https://github.com/JoshuaDoes/twrp_device_google_redbull
You can find the latest unofficial test build here: twrp-3.6.0_11-0.1-bramble.img
Boot it with `fastboot boot twrp-3.6.0_11-0.x-bramble.img`, decrypt your data if necessary, then install it permanently by navigating to `Advanced -> Flash Current TWRP`. Test by navigating to `Reboot -> Recovery` and you should reboot back into TWRP!
Changelog
11-0.1 (1/16/2022):
- Fix missing libion dependency, which appears to allow booting and installing TWRP if A12 is installed
11-0 (1/13/2022):
- Sync bramble with patches from redfin
You can find the historical builds here (but please don't use them): https://files.joshuadoes.com/TWRP/twrp-11/bramble/
Click to expand...
Click to collapse
Hello. Link is for ver. 0. Ver 0.1 returns 403 Forbidden. Can you please fix it?
Been waiting so long for this, thanks a bunch, i'm running lineageos 18.1 so i hope it will work (probably disable automatic updates flashing ?).
N34S said:
Hello. Link is for ver. 0. Ver 0.1 returns 403 Forbidden. Can you please fix it?
Click to expand...
Click to collapse
I fixed the link for v0.1!
J0kker said:
Been waiting so long for this, thanks a bunch, i'm running lineageos 18.1 so i hope it will work (probably disable automatic updates flashing ?).
Click to expand...
Click to collapse
Automatic OTAs will replace TWRP, so disable automatic OTAs and download them with the Updater app whenever you get a notification, then install using TWRP (/data/lineageos_updates) and check "Install TWRP after flashing" before swiping to install (or go to Advanced -> Install Current TWRP before rebooting). Easy as that!
But I may make a Magisk module to handle all this since Magisk has a survival script that works. It'd be a oneshot service that caches the latest copy of TWRP and installs it each boot, so you'd only have to deal with one update cycle that has Lineage Recovery installed.
Just wondering, i have a game that won't run when rooted (even with magisk hide), i somewhat managed to have lineageos rooted with magisk in slot b, and in slot a magisk installed but no root, so when i want to run the game i switch to slot A from twrp, now i have an update notification, i downloaded it, if i boot to twrp, select slot a, so that it will install update to slot b (rooted), that way it should keep my slot a unrooted, able to play my game right ?
New to this slot a/b i read a lot but still not sure about everything.
Anyway, thanks again for your work, and your answers, i missed twrp so much coming from oneplus 5 =)
Hi just installed the boot twrp img, worked great! Thank you for your great work. If you were to develop a module through Magisk would that enable the twrp to stick as a recovery and not lose root?
I wanted to say thank you again for building this.
Also, does anyone know if there is a way to exclude a folder (or folders) from TWRP backups? I had this great idea to go from mp3 to flac music when I got 128gb storage on my first pixel and...well...it's too big. Thanks again!
Hello,
I am trying to recover some data off of my 4a 5g with a broken display. It seems like my partitions are not mounting correctly.
This is what etc/fstab looks like:
Code:
/dev/block/dm-0 /system_root ext4 ro 0 0
/dev/block/dm-3 /system_ext ext4 ro 0 0
/dev/block/dm-4 /vendor ext4 ro 0 0
/dev/block/dm-2 /product ext4 ro 0 0
/dev/block/sda15 /metadata ext4 rw 0 0
/dev/block/sda19 /data f2fs rw 0 0
/auto0 vfat rw 0 0
/dev/block/sda2 /persist ext4 rw 0 0
This is what I get when trying to mount partitions:
Code:
bramble:/ # mount -a -v -t f2fs
try '/dev/block/sda19' type 'f2fs' on '/data'
mount: '/dev/block/sda19'->'/data': Invalid argument
My question is, am I doing something wrong here? I suspect data is not decrypted but I have no working display to verify whether I am actually entering the password when booting recovery. Also can anyone please walk me through how to properly enter the password using a USB keyboard
Sorry guys , got a new 4a5g and did a fresh Feb 2022 factory install both slots and this 11.0.1 will not boot. Fastboot tools are latest along with drivers and this recovery failed to flash or boot. Fastboot sent the file however in all cases failed to write into recovery partition. Tried all of the builds just in case. Never could get past writing to the recovery partition
Hi if you can access fastboot try the the android flash tool, I had the same issue and that worked for me