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!
Related
looks like my SGS2 corrupted it's /system and /data ext4 partitions so now they're read-only:
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
so now it's pretty much unusable.
how can I force fsck of those partitions or otherwise remount them as read-write?
borism3000 said:
looks like my SGS2 corrupted it's /system and /data ext4 partitions so now they're read-only:
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
so now it's pretty much unusable.
how can I force fsck of those partitions or otherwise remount them as read-write?
Click to expand...
Click to collapse
Hmm ... let me guess ...
You have a real problem, if you want to keep the information in those partitions.
I would recommend to make a factory reset and flash the ROM you want to have with pit file and re-partion option in Odin.
Good luck !
I have same problem,
So there is no solutions at all?
What about booting into recovery then using a adb shell to run fsck on the partitions.
Note system is supposed to be read only but it couldn't hurt to check it.
I already get the recovery.fstab as following
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 cache
/data ext4 userdata
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 system
/devlog ext4 devlog
/internal_sdcard vfat /dev/block/mmcblk0p35
to add new device create file in edify_defs with the same of device, as above listed mount point how can I edit the new file
Thanks for help
Hello all,
I'm new to the world of ROMS and custom recoveries, I've rooted my phone and for educational purposes, I wanted to build CWM 6 but I have trouble with my recovery.fstab or something because I only get a blank screen flashing periodically.
Here's the stock recovery.fstab of the recovery.img
Code:
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard vfat default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/HIDDEN /preload ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 default wait,length=-16384
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/KERNEL /boot emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/RECOVERY /recovery emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/modem /modem emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/DSP /modem2 emmc default recoveryonly
I've also tried this version (after changing the names with partitions)
Code:
# mount point fstype device
/system ext4 /dev/block/mmcblk0p18
/preload ext4 /dev/block/mmcblk0p19
/data ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p17
/efs ext4 /dev/block/mmcblk0p7
/productinfo ext4 /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p11
/recovery emmc /dev/block/mmcblk0p12
/modem emmc /dev/block/mmcblk0p13
/modem2 emmc /dev/block/mmcblk0p14
/sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk1p1
but to no avail, the only result that I got was when I used the fstab of the boot.img
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
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,barrier=1 wait
#/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit wait,encryptable=footer,check
#/dev/block/platform/sprd-sdhci.3/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
#/dev/block/platform/sprd-sdhci.3/by-name/prodnv /productinfo ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,noatime,errors=panic wait
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/devices/platform/sprd-sdhci.0/mmc_host/mmc1 auto vfat defaults voldmanaged=extSdCard:auto,noemulatedsd
would you please tell me what I'm missing here ?
Just want to know
Could you tell me how you got root for this phone..? Been searching all over with no luck
Hi,
Completely new to smartphones in general, I just bought a second-hand Samsung Galaxy S2 from a specialized website. I tried to install LineageOS on it but with no success so far (the LineageOS wiki for this device seems to forget some important things when starting from a stock ROM).
Current situation and things that might help:
I don't have a microSD card.
I have a backup of the original .pit file.
Even if I really do not want to use the stock ROM, I can not find a way to reinstall a working one: installation with Odin works but there is a "boot loop" on the Samsung logo.
Installing Replicant works, but it is unfortunately too extremist for me.
As I don't have a microSD card, I try installing with "adb sideload image_file.zip" (like I do with Replicant), but TWRP displays errors about partitions :
Code:
...
E:Unable to locate storage partition for storing settings file.
Updating partition details...
...done
Unable to find partition for path '/system'
Unable to find partition for path '/data'
MTP enabled
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Target: samsung/GT-I9100:4.1.2/JZ054K/I9100XWMS2:user/release-keys
detected filesystem ext4 for /dev/blockmmcblk0p9
detected filesystem ext4 for /dev/blockmmcblk0p10
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
Updater process ended with ERROR: 7
I tried doing a "factory reset" from TWRP but result is the same.
Here are some information that might be useful, gathered from an ADB shell:
/etc/recovery.fstab
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# 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
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usbdisk0:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
/etc/mtab
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/tmp/recovery.fstab
Code:
...
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/dev/block/mmcblk0p9'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
'I:Processing '/dev/block/mmcblk0p7'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
'I:Processing '/dev/block/mmcblk0p1'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
'I:Processing '/dev/block/mmcblk0p10'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
'I:Processing '/dev/block/mmcblk0p12'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
'I:Processing '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0*'
E:Invalid block device 'auto' in fstab line '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,nonremovable,noemulatedsd
'I:Processing '/devices/platform/s3c-sdhci.2/mmc_host/mmc1*'
E:Invalid block device 'auto' in fstab line '/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
'I:Processing '/devices/platform/s3c_otghcd/usb*'
E:Invalid block device 'auto' in fstab line '/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usbdisk0:auto
'I:Processing '/dev/block/mmcblk0p5'
E:Invalid block device 'emmc' in fstab line '/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
'I:Processing '/dev/block/mmcblk0p6'
E:Invalid block device 'emmc' in fstab line '/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
'E:Unable to locate storage partition for storing settings file.
Updating partition details...
...done
I:Unable to find storage partition '/'.
I:Unmounting main partitions...
Unable to find partition for path '/system'
Unable to find partition for path '/data'
...
I spent many hours hours on this issue and read many many things. I really hope someone will be able to help, or at least sympathise Feel free to ask if I can provide some information. Thanks!
Your life would be easier if you paid ten dollars for an SD card lol. My advice is to flash the stock ROM back. Root it. Install dual boot patcher apk and install lineage as data1. This way you avoid your headache and if anything goes wrong you can just boot back to the stock ROM and try again. Also are you sure you have the right ROM? S2 stuff is hard to find. I've been working on an s3 with no luck. Years ago I downgraded the bootloader and bricked it.
Interesting to know that dual boot with microSD card would be easier than only LineageOS (I am coming from the Linux word where it is generally simpler to remove Windows)… I will try to see that.
I got the stock ROM from samsung-updates.com/device/?id=GT-I9100. I am really disappointed to know that vendors like Samsung does not provide these officially.
Finally done it, thanks to people on Reddit! :victory:
Go to 3W dot reddit dot com/r/LineageOS/comments/603qeq/cannot_boot_into_twrp_on_samsung_galaxy_s2/ where the solution is written many times by different persons. Just note that you have to use TWRP 3.1.0, version 3.1.1 fails (see first post).
Now the goal is to update the LineageOS official wiki…
This is my first time rooting and flashing custom rom. I think my phone's emmc is damaged because TWRP can't wipe or format data it says
Unable to mount /data/media/TWRP/ .twrp
Failed to mount '/3rdmodem' (Invalid argument) and so on
When I use this command cat /etc/fstab I get only this
/3rdmodem ext4 rw 0 0
/cache ext4 rw 0 0
/data f2fs rw 0 0
and so on
but I must be getting something like this
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
this is missing /dev/block/mmcblkXXXX
and when I try this command
ls /dev/block/bootdevice/by-name/ or mount -t ext4 /dev/block/bootdevice/by-name/userdata /data
I get No such file or directory
Can someone please help me if my phone's emmc is damaged or not. If my phone's emmc is damaged than I will be wasting my time fixing my phone.
Thank you
Regards