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
Related
Here is the recovery.fstab for the atrix
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p11
/cache ext4 /dev/block/mmcblk0p15 NULL ext3
/data ext4 /dev/block/mmcblk0p16 NULL ext3
/sdcard vfat /dev/block/mmcblk1p1
/emmc vfat /dev/block/mmcblk0p18
/system ext4 /dev/block/mmcblk0p12 NULL ext3
/recovery emmc /dev/block/mmcblk0p10
/osh ext3 /dev/block/mmcblk0p13
/preinstall ext3 /dev/block/mmcblk0p17
And here the dx2
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system auto /dev/block/mmcblk0p12
/cache ext3 /dev/block/mmcblk0p15
/data ext3 /dev/block/mmcblk0p16
#/misc mtd misc
#/boot mtd boot
#/recovery mtd recovery
/pds ext3 /dev/block/mmcblk0p3
#/preinstall ext3 /dev/block/mmcblk0p17
/emmc vfat /dev/block/mmcblk0p18
I am trying to find the err in the mongrel cwr. More: log from this: cwr 5025 + oly recovery(sbin) + oly etc( recovery.fstab ). See thread cwr hacking.
It backsup but adv restore fails.
Do you mean you can make a backup nandRoid but it wont restore it?
---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------
Cuz Dragonz made it that far before... Restore fails because /system can't unmount because there is processes using it...
Yes here is my latest mongrel cwr.
But the full restore will never untill we get a UL boot loader so use adv restore for testing or find a work around.
Hello, my device is not defined in dsixda's kitchen. And i could not define my device on my own in kitchen. I need some help in defining my device. Please , help me. i will provide with all the information required about my device please build it for me..
Here are the information i get when i open recovery.fstab
# mount point fstype device [device2]
#Gionee lingfen 20120716 add for CR00651943 start
#this is map from /proc/dumchar_info
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p7
/data ext4 /dev/block/mmcblk0p8
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sdcard2 vfat /dev/block/mmcblk0p9
/system ext4 /dev/block/mmcblk0p6
#Gionee lingfen 20120716 add for CR00651943 end
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
Edit: I found solution
ext4 according to TWRP fstab
https://twrp.me/samsung/samsunggalaxya32017.html
Code:
/boot emmc /dev/block/platform/13540000.dwmmc0/by-name/BOOT
/cache ext4 /dev/block/platform/13540000.dwmmc0/by-name/CACHE
/data ext4 /dev/block/platform/13540000.dwmmc0/by-name/USERDATA length=-16384
/recovery emmc /dev/block/platform/13540000.dwmmc0/by-name/RECOVERY
/system ext4 /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM
/efs emmc /dev/block/platform/13540000.dwmmc0/by-name/EFS flags=display="EFS";backup=1
/radio emmc /dev/block/platform/13540000.dwmmc0/by-name/RADIO flags=display="Modem";backup=1
/cpefs emmc /dev/block/platform/13540000.dwmmc0/by-name/CPEFS flags=display="CPEFS";backup=1
/system_image emmc /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM
/cache_image emmc /dev/block/platform/13540000.dwmmc0/by-name/CACHE
/radio_image emmc /dev/block/platform/13540000.dwmmc0/by-name/RADIO
/hidden_image emmc /dev/block/platform/13540000.dwmmc0/by-name/HIDDEN
/external_sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat /dev/block/sdd1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
Nothing to learn here... F... I hate these.. "I found solution".
Me, me, me,,, and then comes another asking for the same...
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!