z5c e5823 - Fixing Boot Loop after doing mkswap on mmcblk0p* - Xperia Z5 Compact Q&A, Help & Troubleshooting

First, I apologize if I am writing a duplicate thread. If so, please link it.
As part of my Android-hobby-experiments with a rooted Sony Xperia Z5 Compact e5823 with Android MarshMallow, I attempted to use a partition of my external microSD card as swap area but ended up in a boot loop after reboot.
I have two partitions on the microSD card. One is fat32 and the other one is linux-swap. Both partitions were made under Debian using GParted, at different timepoints.
If I remember well, I did the following on a terminal emulator:
Code:
$ su
# mkswap /dev/block/mmcblk0p2
# swapon /dev/block/mmcblk0p2
(here I got an error. something like "Invalid argument".)
# free -m
I saw no improvement, so then I did:
Code:
$ su
# mkswap /dev/block/mmcblk0p3
# swapon /dev/block/mmcblk0p3
(here I got the same error.)
# free -m
(no improvement)
# exit
$ exit
Device was working normal after this.
Hours later, I reboot the phone (the camera sometimes crashes/freezes after taking a pic, so I took a pic, screen froze, took a screenshot, and rebooted). Then I reached a boot loop.
The screen showes the Sony Xperia logo, then the screen attempts to load the "powered-by.-ndroid-animation" but instead there is a black screen and a blinking red LED (4 times). The screen is then gray and the show repeats. I turned off the phone by opening it and disconnecting the battery
Then I took the microSD card out and the SIM card aswell. I swiched on the phone and the bootloop continued. :silly:
I can enter fastboot-mode (volume up + USB connection). Which I now use to switch off the phone instead of opening and disconnecting the battery :cyclops:.
Luckily, the device on fastboot-mode is listed the under Debian by the command
Code:
$ fastboot devices -l
, so I believe in hope to fix this boot loop w/o (re)flashing a ROM
It is also possible to run a custom recovery. I have run TWRP3.0 from this post and nilezon's version from this posts using the command
Code:
$ fastboot boot recovery.img
At the very beginning of the console of the recoveries there is an error:
Code:
Updating partition details . . .
Failed to mount '/lta-label' (No such device)
. . . done
Full SELinux support is present.
MTP Enabled
--- Update ---
I used the terminal using TWRP3.0 to read the file
Code:
/etc/fstab
and it looks as follows
Code:
/dev/block/mmcblk0p43 /system ext4 rw 0 0
/dev/block/mmcblk0p42 /data ext4 rw 0 0
/dev/block/mmcblk0p41 /cache ext4 rw 0 0
/external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
/dev/block/mmcblk0p3 /firmware vfat rw 0 0
/dev/block/mmcblk0p38 /appslog ext4 rw 0 0
/dev/block/mmcblk0p40 /oem ext4 rw 0 0
/dev/block/mmcblk0p31 /persist ext4 rw 0 0
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
/dev/block/mmcblk0p39 /diag ext4 rw 0 0
I decided to comment out
Code:
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
and reboot. Boot loop persists in the same way and at the console of the recovery there is still, at the very beginning,
Code:
Failed to mount '/lta-label' (No such device)
I rechecked the
Code:
/etc/fstab
file and my modification was gone.
--- Update 2 ---
Today After connecting the SD card with a microSD-USB-adapter Debian shows the following error:
Code:
Error mounting /dev/sdb1 at /media/user/4C25-AD09: Command-line `mount -t "vfat" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdb1"
"/media/jk/4C25-AD09"' exited with non-zero exit status 32: mount: /dev/sdb1: can't read superblock
Still, both partitions are recognized by GParted. "/dev/sdb1" is the fat32-partition. "/dev/sdb2" is the swap-partition. I can't access the first . . .
so I am stuck. dou you guys have any suggestion about what to try next?

Related

[Q] mount cryptfs?

vdc cryptfs enablecrypto/changepw exists.
Where is vdc cryptfs mount?
I.e., how can I mount the encrypted /data partition from a shell (ultimately via adb shell in recovery)?
Thanks!
By experimentation and checking the system/vold/ source code, I was able to unlock the encrypted partition using:
Code:
setprop ro.crypto.state encrypted
vdc cryptfs checkpw 'your passphrase here'
The unlocked device is then available in /dev/block/dm-0, and can be mounted directly read-only using:
Code:
mount -o ro /dev/block/dm-0 /data
If you want it to be read/write, simply remove the -o ro part (or run mount -o remount,rw /data after running the above mount command). Do not run vdc cryptfs restart in recovery, there is nothing to catch the triggers so all future vdc commands will hang.
Oh, and when done, do not forget to unmount your partition:
Code:
umount /data
Thanks a lot, that sounds great.
However, now I have big trouble getting vdc cryptfs to work in recovery It needs /dev/socket/vold but vold is not started.
I am getting a bootloop with cyanogenmod and want to disable the encryption from recovery. Any ideas how to resolve that/start vold?
dy/dx said:
Thanks a lot, that sounds great.
However, now I have big trouble getting vdc cryptfs to work in recovery It needs /dev/socket/vold but vold is not started.
I am getting a bootloop with cyanogenmod and want to disable the encryption from recovery. Any ideas how to resolve that/start vold?
Click to expand...
Click to collapse
For future readers, I have a minivold process in recovery. If you do not have (mini)vold, try upgrading recovery.
No such file or directory
Lekensteyn said:
The unlocked device is then available in /dev/block/dm-0
Click to expand...
Click to collapse
I tried the commands in clockwerkmod recovery but /dev/block/dm-0 isn't found (nexus 4 with Cyanogenmod 11):
Code:
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw '1234'
200 0 10
~ # mount /dev/block/dm-0 /data
mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: No such file or directory
Is there a way to access the encrypted data?
svengo said:
I tried the commands in clockwerkmod recovery but /dev/block/dm-0 isn't found (nexus 4 with Cyanogenmod 11):
Code:
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw '1234'
200 0 10
~ # mount /dev/block/dm-0 /data
mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: No such file or directory
Is there a way to access the encrypted data?
Click to expand...
Click to collapse
There is likely a way, but if it does not work (this is not documented, so it might change), have a look at your logs for what went wrong. Since logcat is probably nog available, you have to read logs with cat /dev/log/system and/ or (in a second shell) cat /dev/log/main.
Lekensteyn said:
There is likely a way, but if it does not work (this is not documented, so it might change), have a look at your logs for what went wrong. Since logcat is probably nog available, you have to read logs with cat /dev/log/system and/ or (in a second shell) cat /dev/log/main.
Click to expand...
Click to collapse
Don't know whether this helps, but I found that these commands work on cwm recovery while they do not on twrp. This seems to be because in cmw vold is started while in twrp it isn't.
Is there some "cryptfs clear", which wipes the crypt signature?
I am having trouble with creating a crypted data with some ROM right now and always need to override the whole device to get rid of the crypt signature (i guess in the end of the device?). So something which clears the crypt bytes, so the data can be reformatted as non-crypt partition would be useful. So the ROMS still want to mount it with password.
problem with mounting /data
Hi, Guys... please, give me advice. I try to mount encrypted /data.
Samsung Galaxy Note 2 (N7100), CWM 6.0.4.7 / root(SU) / Android 4.4.2 stock / busybox 50 / USB Debugging ON:
Code:
C:\Users\SDK\platform-tools>adb devices
List of devices attached
4df749af12f330b7 recovery
Next:
Code:
C:\Users\SDK\platform-tools>adb shell
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw "njjm.0mk."
200 0 -1
~ # mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: No such file or directory
Logcat (system):
Code:
~ # cat /dev/log/system
' З З э├*NД╫↨Vold Vold 2.1 (the revenge) firing up F З З э├*NД╫↨Vold
Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media) G З З э├*N
Д╫↨Vold Volume usbdisk0 state changing -1 (Initializing) -> 0 (No-Media) @ З
Л э├*NБGб↓Vold Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending) R
З Л э├*NБGб↓DirectVolume DirectVolume::handlePartitionAdded -> MAJOR 179, MIN
OR 17, PARTN 1
F З Л э├*NБGб↓Vold Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Un
Cryptfs Bad magic for real block device /dev/block/mmcblk0p16
Cryptfs Error getting crypt footer and key
@ З ╕ р┼*N?6р0Cryptfs Bad magic for real block device /dev/block/mmcblk0p1
6
- З ╕ р┼*N?6р0Cryptfs Error getting crypt footer and key
@ З ╕ е╔*N╖▀[$Cryptfs Bad magic for real block device /dev/block/mmcblk0p1
6
- З ╕ е╔*N╖▀[$Cryptfs Error getting crypt footer and key
Logcat (main):
Code:
~ # cat /dev/log/main
В Д Д э├*N┴а¶!ARMAssembler generated scanline__00000077:03545405_00000A02_0
0000000 [ 37 ipp] (59 ins) at [0x4176c1f0:0x4176c2dc] in 133083 ns
Б Д Д э├*NБcя'ARMAssembler generated scanline__00000077:03545405_00000A01_
00000000 [ 37 ipp] (58 ins) at [0x4176c2e0:0x4176c3c8] in 54625 ns
Б Д Д э├*NБcя'ARMAssembler generated scanline__00000077:03545405_00000A08_
00000000 [ 37 ipp] (59 ins) at [0x4176c3d0:0x4176c4bc] in 38041 ns
Б Д Д э├*NA∙Ш-ARMAssembler generated scanline__00000077:03545405_00000000_
00000000 [ 36 ipp] (50 ins) at [0x4176c4c0:0x4176c588] in 64708 ns
FSTab:
Code:
~ # cat /etc/fstab
/dev/block/mmcblk0p12 /cache ext4 rw
/dev/block/mmcblk0p16 /data ext4 rw
/dev/block/mmcblk0p13 /system ext4 rw
/dev/block/mmcblk0p14 /preload ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p2 /sd-ext ext4 rw
/dev/block/mmcblk1p1 /external_sd auto rw
~ #
MOUNT -A:
Code:
~ # mount -a
mount: mounting /dev/block/mmcblk0p16 on /data failed: Invalid argument
I try to mount encrypted /data and delete the file *.key which contains Android SCREENLOCK password. My Xposed SecureSettings module reset my password and I can't access my Android Desktop Screen.
Please help. What can I do without FORMATting DATA..?

[Q] How to change SDCARD automount options?

I converted my card to ext4 and need to change the default mount options. Right now they are:
Code:
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 ext4 rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
But I need to replace it with
Code:
/dev/block/vold/179:33 /storage/sdcard1 ext4 rw,noatime,nosuid,nodev wait
So far, everything I tried failed:
- Editing fstab.qcom is useless because it is being recreated at each boot.
- adding a umount/mount init script
Code:
#!/system/bin/sh
VOLD="$(mount | grep -E -o -m 1 ".{0,0}179:.{0,2}")"
sleep 8
su
umount /storage/sdcard1
umount /mnt/media_rw/sdcard1
mount -rw -t ext4 -o noatime,nosuid,nodev /dev/block/vold/$VOLD /storage/sdcard1
is also useless, because although it works, it only kicks in AFTER the system is already on the desktop, which is too late.
This is all on Android 4.3.1 (but it's the same story with 4.4)
Why I want to do it?
Because although ext4 sdcard is mounted fine with read and write, the system does not see it as external anymore. As a result, many, many apps just won't work claiming there is no sdcard in the system. Even DiskUsage app does not see it.
I suppose this is because it is mounted either with FUSE or remounted directly as ext4 too late (after the system completed boot).
Any ideas?

mount -o bind valid for root only. Users do not see the mounts

Hi,
My device is on 4.4.4:
I did the following as root
mount -o bind /system/test /sdcard/test
As root user, command mount returns the following
Code:
/dev/block/mmcblk0p12 /storage/sdcard0/test ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
However, a normal user do not see the mount points being applied at all.
i.e. doing mount as a normal user does not return
Code:
/dev/block/mmcblk0p12 /storage/sdcard0/test ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
How to make it such that normal user would see the mount options executed by root?
Edited:
I used an app called Folder Mount (requires root)
doing mount it returns the following for both normal user and root user:
Code:
/dev/block/mmcblk0p12 /mnt/media_rw/sdcard0/UCDownloads/cache/com.UCMobile.intl/httpCache ext4 ro,seclabel,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0
So it looks like mounting with this app does propagate the mount options to also the normal user and not just root user. How do I achieve this?
Edited 2:
Another observation:
Running the exact same command
mount -o bind /system/test /sdcard/test
on another device (4.4.4) works. Now this looks like a device specific issue (but still, folder mount works on the original device). I would really appreciate it if someone know a little about what could possibly be the reason here and share it here.
Thank you.

apps crashing -> soft reboot loop

Hi, I've got a problem.
I plugged my phone in to charge and left it alone for a while. When I came back it was already soft rebooting in a loop, and I've got at most only 20seconds on my screen to do anything. Before it reboots Trebuchet crashes. Going into Settings -> Apps -> All -> Trebuchet -> Clear Chache / Data is impossible because of this small timeframe available, also the settings-app crashes after Trebuchet has crashed.
How can I try to fix this WITHOUT wiping all data?
Btw: I'm using a Moto G 2014 dual sim xt168, with a CM13 stable release from around a year ago.
EDIT: I'm currently trying to backup my relevant app data with adb backup <app>, my problem is that as soon as trebuchet crashes, the backup process gets cancelled. I already tried deleting trebuchets data and rebooting but with no result.
EDIT2: I tried checking the filesystem with e2fsck and some errors came up. I'm pretty unfamiliar with this. Is a new rom flash inevitable or ist my phone even dying?
Code:
E:\Android\minimal adb fastboot 1.4>adb shell
[email protected]_umtsds:/ #
[email protected]_umtsds:/ # mount /system
[email protected]_umtsds:/ # mount /data
mount: '/dev/block/platform/msm_sdcc.1/by-name/userdata'->'/data': Invalid argument
1|[email protected]_umtsds:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 444656 36 444620 1% /dev
tmpfs 444656 12 444644 1% /tmp
tmpfs 444656 0 444656 0% /storage
/dev/block/mmcblk0p36 1112708 761072 351636 69% /system
/dev/block/mmcblk0p38 5773168 4973376 799792 87% /data
[email protected]_umtsds:/ # umount /system
[email protected]_umtsds:/ # umount /data
[email protected]_umtsds:/ # e2fsck -n /dev/block/mmcblk0p36
e2fsck 1.42.9 (28-Dec-2013)
system: clean, 2211/70704 files, 194715/282624 blocks
[email protected]_umtsds:/ # e2fsck -n /dev/block/mmcblk0p38
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p38
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
8|[email protected]_umtsds:/ #
Same here,but with CM12.1
Trebutchet crashes 5 seconds after bootup ,however you can reboot to safe mode,there trebutchet doesn't crash,so maybe you are able to backup some data.
Still waiting for a fix
Found a Fix!
1. Turn on your phone and reboot to safe mode.
(Hold the power button until Power Menu appears and hold "Power Off" until "Reboot to Safe Mode" is displayed)
2. Open your Terminal and type:
Code:
su
pm disable com.cyanogenmod.trebuchet
Your phone will freak out but eventually you'll be able to access the Terminal again (I think I used the Overview Button)
3. Enable Trebuchet with this code:
Code:
pm enable com.cyanogenmod.trebuchet
4. Reboot your phone normally and there you go!

Bugged - no chance to fix?

Hi everybody
Currently i have attached a F1 to my pc which has some weird conditions...
The phone itself seems to be flashed to latest LineageOS, but it is encrypted.
Maybe because of the latest sideload, i can't really tell because the owner gave this to a friend...
So, prefered solution would be: decrypt the phone, get all the pictures/videos from it.
Another acceptable solution would be: install from scratch.
But:
fastboot seems to be botched.
Code:
C:\adb>adb devices
List of devices attached
22fd65f3 recovery
Looking good, adb can access this device.
So, if i could flash some decrypt-voodoo that the device boots and decrypts system...
But no, failing so far.
Then i thought, well, as it is already gone, just fastboot flash and forward.
Nope:
Code:
C:\adb>fastboot devices
???????????? fastboot
And the device goes back to bootloop.
Booting to recovery gives me a TWRP 3.5.2_10-0
Full access, except the encrypted data.
recovery is fully working, so i tried to flash vbmeta with fastboot (--disable-verity --disable-verification) but fastboot seems to be broken.
So... any thoughts where to start first?
Thx
I pulled fstab from phone:
twrp.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# mount point type device device2 flags
/boot emmc /dev/block/bootdevice/by-name/boot flags=display="Boot"
/cache ext4 /dev/block/bootdevice/by-name/cache
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=display="Recovery";backup=1
/system ext4 /dev/block/bootdevice/by-name/system flags=backup=1;wipeingui;display="System"
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=backup=1;wipeingui;display="Vendor"
/system_image emmc /dev/block/bootdevice/by-name/system flags=backup=1;flashimg=1
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=backup=1;flashimg=1
/data ext4 /dev/block/bootdevice/by-name/userdata flags=encryptable=footer;length=-16384;fileencryption=ice:aes-256-cts:aes-256-heh
/firmware vfat /dev/block/bootdevice/by-name/modem flags=display="Firmware";mounttodecrypt
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust"
/misc emmc /dev/block/bootdevice/by-name/misc
/modem emmc /dev/block/bootdevice/by-name/modem flags=backup=1;display="Modem"
/bluetooth emmc /dev/block/bootdevice/by-name/bluetooth flags=backup=1;subpartitionof=/modem
/dsp emmc /dev/block/bootdevice/by-name/dsp flags=backup=1;subpartitionof=/modem
/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display=EFS
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/efsc emmc /dev/block/bootdevice/by-name/fsc flags=backup=1;subpartitionof=/efs1
/efsg emmc /dev/block/bootdevice/by-name/fsg flags=backup=1;subpartitionof=/efs1
/persist ext4 /dev/block/bootdevice/by-name/persist flags=display="Persist"
/storage ext4 /data/media/0 flags=display="Internal Storage";usermrf;backup=1;fsflags="bind";removable
# Removable storage
/usb_otg vfat /dev/block/sdg1 /dev/block/sdg flags=display="USB-OTG";storage;wipeingui;removable
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 flags=display="MicroSD Card";storage;wipeingui;removable
recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem e2fsck binary (typically /system) cannot
# specify 'check', and must come before any filesystems that do specify 'check'
# NOTE: /system and /vendor partitions are early-mounted and the fstab entry is specified in device tree (duplicated below for recovery image purposes only):
# /proc/device-tree/firmware/android/fstab/system
# /proc/device-tree/firmware/android/fstab/vendor
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=0,noauto_da_alloc latemount,wait,check,fileencryption=ice,quota,encryptable=footer
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/boot /boot emmc defaults recoveryonly
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults recoveryonly
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,recoveryonly
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait,recoveryonly
/devices/platform/soc/8804000.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=footer
/devices/platform/soc/a600000.ssusb/a600000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
and the regular fstab
Code:
/dev/block/sda20 /cache ext4 rw 0 0
/dev/block/sde48 /system_root ext4 ro 0 0
/dev/block/sde47 /vendor ext4 ro 0 0
/dev/block/sda21 /data ext4 rw 0 0
/dev/block/sde46 /firmware vfat rw 0 0
/dev/block/sda18 /cust ext4 rw 0 0
/dev/block/sda14 /persist ext4 rw 0 0
/storage ext4 rw 0 0
/usb_otg vfat rw 0 0
/external_sd vfat rw 0 0
Lonesome Walker said:
Hi everybody
Currently i have attached a F1 to my pc which has some weird conditions...
The phone itself seems to be flashed to latest LineageOS, but it is encrypted.
Maybe because of the latest sideload, i can't really tell because the owner gave this to a friend...
So, prefered solution would be: decrypt the phone, get all the pictures/videos from it.
Another acceptable solution would be: install from scratch.
But:
fastboot seems to be botched.
Code:
C:\adb>adb devices
List of devices attached
22fd65f3 recovery
Looking good, adb can access this device.
So, if i could flash some decrypt-voodoo that the device boots and decrypts system...
But no, failing so far.
Then i thought, well, as it is already gone, just fastboot flash and forward.
Nope:
Code:
C:\adb>fastboot devices
???????????? fastboot
And the device goes back to bootloop.
Booting to recovery gives me a TWRP 3.5.2_10-0
Full access, except the encrypted data.
recovery is fully working, so i tried to flash vbmeta with fastboot (--disable-verity --disable-verification) but fastboot seems to be broken.
So... any thoughts where to start first?
Thx
Click to expand...
Click to collapse
If the phone doesn't recognize in fastboot you need the fix and the drivers.
You can find everything you need in my POCO F1 Ultimate Collection & Guides.
Check AMD/Intel Fastboot Fix.
If you know pin/pattern you can flash the TWRP by REIGNZ go to recovery put pin/pattern to decrypt then connect your device to pc while you are in twrp (if MTP doesn't work at first go advanced>file manager> and choose sdcard0 (internal storage) then your device shoule recognized in pc and get your data.
To clean flash follow my clean installation guide.
Everything you need is on my thread I mentioned above.
Okay, this is interesting...
My own Poco F1 had no issues with the drivers installed before.
After updating, the actual bugged F1 can fastboot but my own can't anymore.
WTF?
I also switched cables, doesn't matter.
Okay, nevertheless, mine is not broken, so this will be a task for later...
Thank you so far for this working hint!
So, i now finally have rescued all the pictures, videos and Whatsapp stuff.
My friend is happy.
The next step would be flashing the Pixel Experience.
But: how to find out which Android version is currently installed?
Or should i flash the latest stock rom from Xiaomi? I mean, it can't be higher than that, right?
Thank you for your response!

Categories

Resources