yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A50 Questions & Answers] felixdd:
Update: have removed phone privileges from a while bunch of apps and deleted a few. But I think the thing that made the difference was disabling the pre-installed Facebook app. Phone is working as usual now.
[OnePlus 6 Questions & Answers] billsz:
there's a folder named mcfg_sw in vendor partition.

could anyone share this folder packed from op6/t for me?

i'm a op5 user,but we don't have the hvolte_o folder

thanks
[OnePlus 6 Questions & Answers] matze19999:
what would it change? I think the files aren't compatible to your phone because of other hardware
[OnePlus 6 Questions & Answers] billsz:
just want to make some tests with op5

these files are volte certificates...maybe

help me,pls

thanks
[OnePlus 6 Questions & Answers] matze19999:
Have fun
[OnePlus 6 Questions & Answers] billsz:
thank u very much
[OnePlus 6 Questions & Answers] billsz:
replace all the files from zip to the folder mcfg_sw in vendor with op5...

failed... :p

in pqc tool,cannot find the two volte configure files,hvolte_o and volte_co :confused:

maybe pqc tool with op6,they should be there in the list

it should be somewhere or some config files for the volte list...

View attachment 4751249

View attachment 4751250

View attachment 4751251

View attachment 4751252
[Tilt, TyTN II, MDA Vario III General] omk298:
I can't see any similar problems on the forum, so can anyone help?

Yesterday my Kaiser's power button stopped working. In the middle of the day, not doing anything with it, installing anything or changing any settings. I took it out of my pocket and the screen was on with the power off dialog box showing (I normally keep it on standby in my pocket) The power button wouldn't put it into standby, and holding it wouldn't power it down. Intermittently the power off dialog appears on screen, if I click yes the device restarts (doesn't stay off). Everything else seems to work normally still. Soft resetting works normally. All the other buttons seem to work ok. I've tried a hard reset, but that made no difference.

Anyone else have anything like this?
[Tilt, TyTN II, MDA Vario III General] RizwanKhan:
no but i think ur power button seems to be stuck.. take it to ur local att store and see if they can help u out or try pressing and see it becomes unstuck.
[Tilt, TyTN II, MDA Vario III General] bTrizzy:
I'm having the exact same problem right now. The power button definitely seems to be stuck. Can't figure out how to unstick it :(
[Tilt, TyTN II, MDA Vario III General] Draqula:
About a week ago I had a similar problem.

The power button and the photo button stopped working. I couldn't turn the the device off or set it to standby.

Had to soft reset and after that it was ok again.
[Tilt, TyTN II, MDA Vario III General] bTrizzy:
What do you mean by soft reset? Just pushing the little button at the botttom?
[Tilt, TyTN II, MDA Vario III General] thetruth1985:
Yep thats the ticket.
[Tilt, TyTN II, MDA Vario III General] bTrizzy:
Well that didnt work! Any other solution?
[Tilt, TyTN II, MDA Vario III General] bTrizzy:
Is it possible to unmap the power button and map that question to another button???
[Samsung Galaxy S10 Questions & Answers] TonyTellz:
How can I turn off the animation when using fingerprint to unlock the device?

It's just looks ugly to me.
[Samsung Galaxy S10 Questions & Answers] geekhunt:
You can only choose between the pre installed ones. Apart from that you can't change the animation until you root the device.
[Samsung Galaxy S10 Questions & Answers] TonyTellz:
I'm rooted . How can I change it?
[Samsung Galaxy S10 Questions & Answers] chieco:
Yes root is out for month now but nothing appeared regarding this... does anyone know where the animation is stored atleast?
[Samsung Galaxy S10 Questions & Answers] Rixil 1:
+1 i am DYING to know where :(
[Samsung Galaxy S10 Questions & Answers] Darmach:
Me too! Also the annoying fingerprint popups when app asks for fingerprint auth! We're not morons Samsung - we get when the app asks for fingerprint!
[Xiaomi Mi Mix 3 Questions & Answers] keanoo:
Sometimes the GPS will just stop working, generally I don't notice this until I'm driving somewhere and trying to navigate with Google Maps or Waze. A restart fixes this, but when I'm driving and need to get somewhere, I have to find somewhere to pull over, so I can restart my phone(which seems to take awhile too...). Is there any permanent fix for this?

I'm on the MIUI Global ROM 10.3.1.0.
[Xiaomi Mi Mix 3 Questions & Answers] SirPhilippF:
Can't comprehend this issue... Please check your App Settings for this Apps, could be that the settings are the reason for that, because of the energy savings setup!

Gesendet von meinem Mi MIX 3 mit Tapatalk
[Android Q&A, Help & Troubleshooting] Zdendav:
I need help to root my Aligator S5065 Duo phone. It ha Andoid 7.0 and the chipset is Mediatek MT6580.

Here is some info from the phone:

BB Chip : mt6580

MS Board. : ALIGATORS5065

Build Time : Tue Jan 23 15:35:41 CST 2018

Krenel Ver. : 3.18.35+ (server@droi) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018

Android Ver. : 7.0

SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n

Custom Build Verno. : unknown

IMEI1 : XXX

IMEI2 : XXX

Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123

Bar code : 010901MT000000000000003891_155648

The idea was:

1) make a full backup using MTK Droid Tool

2) flash TWRP using SP Flash Tool

3) boot TWRP and install Magisk

Problems:

1) MTK Droid Tool v2.5.3. doesn't support this chipset and I didn't found a newer version - so no full backup :(

I've tried to download a stock ROM or a full backup.

I have found MT6580__ALIGATOR__ALIGATOR_S5065__alps-mp-n0.mp2-V1_droi6580.weg.n__Android_7.0.ispff but it seems to need Infinity CM2 Dongle for flashing, which I don't own.

I have also found ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.02_OS_1.1_20170927.zip which seems to be usable but not exactly the same as I have in my phone, at least it contains a scatter file. With the help of this scatter file I have I've read back my phone but the read imgs are considerably bigger, than the original ones in the zip - that doesn't seem right?

2) I have downloaded TWRP_3.2.3-0_20180803_UNOFFICIAL_MT6580_N.zip which should be a TWRP recovery for my chipset and the same kernel version, so I hoped it could work. But when trying to flash it with SP Flash Tool I get "PMT changed for the ROM" error message. The suggested solution for this error seem to be very risky (formating the phone, atc.), so I didn't dare to try ...

Now I'm stuck and I don't know how to proceed.

Any help would be really appreciated
[Android Q&A, Help & Troubleshooting] Zdendav:
Some progress:

I got a custom TWRP recovery image from Matty1993 <- thank you very much :)

I flashed it using adb and fastboot:

adb devices - successfully listed my device

adb reboot bootloader

fastboot flash recovery c:\adb\recovery.img - got this error message: "FAILED (remote: 'not allowedin locked state')"

Locked bootloader, unlocking ...

fastboot flashing unlock

- (bootloader) Start unlock flow

- OKAY [ 18.800s]

- Finished. Total time: 18.816s

Flashing the recovery.img

fastboot flash recovery c:\adb\recovery.img

Sending 'recovery' (10226 KB) OKAY [ 0.359s]

Writing 'recovery' OKAY [ 0.640s]

Finished. Total time: 1.030s

Success

fastboot reboot-bootloader

Rebooting into bootloader OKAY [ 0.000s]

Finished. Total time: 0.016s

fastboot erase cache (I don't know if it was a good idea but it was in the tutorial, I was following)

******** Did you mean to fastboot format this ext4 partition?

Erasing 'cache' OKAY [ 0.109s]

Finished. Total time: 0.125s

fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.016s

Now when booting the phone complains:

Orange state

Your device has been unlocked and can't be trusted

Your device will boot in 5 seconds

In 5 second it starts to boot but it stays forever on the "POWERED BY android" logo

I can boot to TWRP recovery (also fastboot), so I did and flashed magisk (because the main goal was to root my phone) and selected to delete cache/dalvik.

I'm not able to switch off the phone, it reboots. I had tu pull the battery (luckily it's removable).

The phone info changed

BB Chip : mt6580

MS Board. : ALIGATORS5065

Build Time : Tue Jan 23 15:35:41 CST 2018

Krenel Ver. : 3.18.35+ (server@droi) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018

Android Ver. : 7.0

SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n

Custom Build Verno. : unknown

IMEI1 : unknown

IMEI2 : unknown

Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123

Bar code : unknown

The IMEIs and Bar code are now "uknown".

What did I wrong and what to do, to fix it?
[Android Q&A, Help & Troubleshooting] alecxs:
forget MTK Droid Tool it is outdated and does not support scatter for devices > 4 GB. you can use SP Flash Tool for full ROM dump. First thing you should do is backup your nvram partition, hopefully it is not too late...

https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek

If you already have backup of stock boot.img:

- copy file to /external_sd/TWRP/BACKUPS folder

- rename it to boot.emmc.win

- create a backup of current boot (just in case)

- restore renamed stock boot.emmc.win from TWRP

regarding boot stuck:

- Format Data and Wipe Cache from TWRP, reboot recovery, wipe again (Wipe -> Format Data -> type yes)

- reboot TWRP, check if /system /data and /cache is mounted/mountable (you should see folders or files inside)

- reboot system and wait 5 minutes, first boot may take a while because the data partition is forced encrypt

- if android is completely booted, check IMEI

Now, if your device is in good condition, reboot recovery and make a full TWRP backup.
[Android Q&A, Help & Troubleshooting] Zdendav:
Thank you very much for your help.

I did a dump before, using the SP Flash Tool and the scatter from the downloaded ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.0 2_OS_1.1_20170927.zip file.

So I have a sort of a "backup" :)

Now I'm going to read and I'll report back how it went.
[Android Q&A, Help & Troubleshooting] alecxs:
If this is the case, you can "download" (=flash) your backup files from SP Flash Tool. In scatter file change entries to "is_download: true". Open the edited scatter file with SP Flash Tool. Make sure you uncheck all checkboxes, except nvram, nvdata (and cache, if you still have problems with this partition). Double click on file name and select the file for each partition. Make sure EMMC_USER is selected. The file sizes must fit partition size. Do NEVER flash PRELOADER! Press start, then connect phone, then insert battery.

nvram.bin 5120 KiB (0x00500000)

nvdata.bin 32768 KiB (0x02000000)

cache.img 409600 KiB (0x19000000)

If done, hold Volume Up key while unplug + plug in USB cable, this will boot into recovery. Wipe Cache and Data
[Android Q&A, Help & Troubleshooting] Zdendav:
My sizes of the backup files:

nvram.bin 5 242 880 seems OK

nvdata.bin 33 554 432 seems OK

cache.img 419 430 400 bigger

Is there a way I can check the integrity of them before flashing?

And what when I get the "PMT changed for the ROM" error message?

I've attached the used scatter file
[Android Q&A, Help & Troubleshooting] alecxs:
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
[Android Q&A, Help & Troubleshooting] alecxs:
Orange state just mean unlocked bootloader, you can't get rid of. Do not lock the bootloader again, just leave it orange state is fine...
[Android Q&A, Help & Troubleshooting] Zdendav:
I thought so and it doesn't really bother me :)
[Android Q&A, Help & Troubleshooting] alecxs:
as [MENTION=9139800]Matty1993[/MENTION] already figured out, your phone seems fine, just dm-verity prevents to boot because of recovery checksum mismatch. You have to disable dm-verity.

Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
[Android Q&A, Help & Troubleshooting] Zdendav:
I did try and I got the "PMT changed" even when I selected all partitons except preloader ..

I did borrow exactly the same phone from a relative and created a full backup and from it a proper scatter file. I compared both scatter files and there are differences (as expected)

I attach both scatter files

I don't know how to proceed.

1) Lock the bootloader?

2) Flash parts from the borrowed phone? Which parts?

PS I have also a backup of userdata taken in factory mode.
[Android Q&A, Help & Troubleshooting] alecxs:
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
[Android Q&A, Help & Troubleshooting] Zdendav:
Done. Did it all in one go (without any reboot), then powered off.

Log is attached
[Android Q&A, Help & Troubleshooting] Zdendav:
Sorry I missed your post until I posted mine ...

I'll keep all backups until it's sorted out.

And thank you very much aIecxs and Matty1993 for all your help :)
[Android Q&A, Help & Troubleshooting] alecxs:
thanks for the log. seems there is something wrong, maybe with TWRP or maybe with phone.

E:Primary block device '/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata' for mount point '/data' is not present!
Failed to mount '/cache' (Invalid argument)
Error installing zip file '/external_sd/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip'

Flash stock boot.img and stock recovery.img from fastboot. reboot into stock recovery. Wipe Data + Cache. reboot to bootloader. boot into TWRP from fastboot. copy log to sdcard and upload again. reboot your phone and wait 5 minutes.
[Android Q&A, Help & Troubleshooting] Zdendav:
I flashed the stock recovery and boot in fastboot in one go.

Then rebooted to recovery but there is only "Supported API: 3" in the lower left corner of the display and that's all.

What to do next?

Edit: It's even worse, I'm not able to enter fastboot, recovery etc., the phone doesn't react to the volume button and always show the orange message a boot to the Supported API: 3 screen.
[Android Q&A, Help & Troubleshooting] alecxs:
This indicates something is wrong with cache partition. Usually a normal system boot from stock boot.img will fix this. If you can't enter fastboot mode, flash recovery from SP Flash Tool. Try this version it has changed fstab. This should fix the /data mount. Then you should be able to enter fastboot again.

[strike]/data	ext4	/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata	flags=encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata[/strike]
/data	ext4	/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata	flags=encryptable=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/metadata

Regarding /cache try following from fastboot:

fastboot format:ext4 cache

after this wipe cache again from stock recovery (you can boot stock recovery from fastboot without flashing it). if cache still not mounted in TWRP, your only choice left is flash backup of cache partition from your friends phone from SP Flash Tool

edit: attachment deleted
[Android Q&A, Help & Troubleshooting] Zdendav:
Flashed your recovery, now it always boots into twrp, volume buttons still seem to not work, I'm still not able to enter fastboot.

Edit: I was able to enter fastboot by "adb reboot bootloader" when in TWRP, strangely "adb reboot fastboot" booted into TWRP.

I formatted the cache, rebooted into stock recovery, formatted the cache again.

Rebooted into TWRP, in file manager the cache is empty, in the mount menu I'm not able to tick any of the listed partitions to mount it ...

I'm not able to post the new log, it copies it to /data/media but in the file manager the location is empty ...
[Android Q&A, Help & Troubleshooting] alecxs:
i have added some mount points, please download and flash again. you can copy recovery.log from adb

adb pull /tmp/recovery.log C:\adb\recovery.log

please post output of df and mount

adb shell
mount
busybox df -aT
[Android Q&A, Help & Troubleshooting] Zdendav:
/ # mount

rootfs on / type rootfs (rw,seclabel)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

tmpfs on /tmp type tmpfs (rw,seclabel,relatime)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

/ # busybox df -aT

Filesystem Type 1K-blocks Used Available Use% Mounted on

tmpfs tmpfs 463204 44 463160 0% /dev

devpts devpts 0 0 0 0% /dev/pts

proc proc 0 0 0 0% /proc

sysfs sysfs 0 0 0 0% /sys

selinuxfs selinuxfs 0 0 0 0% /sys/fs/selinux

tmpfs tmpfs 463204 32 463172 0% /tmp

adb functionfs 0 0 0 0% /dev/usb-ffs/adb
[Android Q&A, Help & Troubleshooting] alecxs:
strange it does not mount /external_sd, can you please try manually

adb shell
cat /proc/partitions
mount -t vfat -w /dev/block/mmcblk1p1 /external_sd
mount -t ext4 -r /dev/block/mmcblk0p21 /system
mount -t ext4 -w /dev/block/mmcblk0p22 /cache
mount -t ext4 -w /dev/block/mmcblk0p23 /data

edit: please make a chronological list of what you have ever flashed with SP Flash Tool (not fastboot) and which scatter file used for flashing (ROM or WwR). and which boot.img you have flashed from fastboot?
[Android Q&A, Help & Troubleshooting] Zdendav:
/ # cat /proc/partitions

major minor #blocks name

179 0 7471104 mmcblk0

179 1 3072 mmcblk0p1

179 2 5120 mmcblk0p2

179 3 10240 mmcblk0p3

179 4 10240 mmcblk0p4

179 5 256 mmcblk0p5

179 6 384 mmcblk0p6

179 7 16384 mmcblk0p7

179 8 16384 mmcblk0p8

179 9 512 mmcblk0p9

179 10 8192 mmcblk0p10

179 11 10240 mmcblk0p11

179 12 1024 mmcblk0p12

179 13 5120 mmcblk0p13

179 14 5120 mmcblk0p14

179 15 32768 mmcblk0p15

179 16 38272 mmcblk0p16

179 17 2048 mmcblk0p17

179 18 6144 mmcblk0p18

179 19 8192 mmcblk0p19

179 20 8192 mmcblk0p20

179 21 2727936 mmcblk0p21

179 22 409600 mmcblk0p22

179 23 4128256 mmcblk0p23

179 24 16384 mmcblk0p24

179 96 4096 mmcblk0rpmb

179 64 4096 mmcblk0boot1

179 32 4096 mmcblk0boot0

179 128 125042688 mmcblk1

179 129 125041664 mmcblk1p1

/ # mount -t vfat -w /dev/block/mmcblk1p1 /external_sd

mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Device or resource

busy

/ # mount -t ext4 -r /dev/block/mmcblk0p21 /system

/ # mount -t ext4 -w /dev/block/mmcblk0p22 /cache

/ # mount -t ext4 -w /dev/block/mmcblk0p23 /data

mount: mounting /dev/block/mmcblk0p23 on /data failed: Invalid argument

Edit: First flash using SP Flash Tool was today, when you instructed me. There were attempts before, but all ended with the PMT error. The scatter used was the proper one extracted with WwR.

Edit2: The boot image was the one I extracted from my phone with SP Flash Tool using the scatter from the downloaded zip file. It's binary identical to the one extracted from the borrowed phone.

Edit3: After the mounts:

/ # df -aT

Filesystem Type 1K-blocks Used Available Use% Mounted on

tmpfs tmpfs 463204 44 463160 0% /dev

devpts devpts 0 0 0 0% /dev/pts

proc proc 0 0 0 0% /proc

sysfs sysfs 0 0 0 0% /sys

selinuxfs selinuxfs 0 0 0 0% /sys/fs/selinux

tmpfs tmpfs 463204 28 463176 0% /tmp

adb functionfs 0 0 0 0% /dev/usb-ffs/adb

/dev/block/mmcblk1p1 vfat 125011104 4155584 120855520 3% /external_sd

/dev/block/mmcblk0p21 ext4 2642424 1880340 745700 72% /system

/dev/block/mmcblk0p22 ext4 396744 576 387976 0% /cache
[Android Q&A, Help & Troubleshooting] alecxs:
okay if you never flashed something then everything should be still intact. if i understand the results, mount /system and /cache was successful? /external_sd is mounted? can you upload recovery.log?
[Android Q&A, Help & Troubleshooting] Zdendav:
I agree. It's strange, I would say I didn't do anything that dangerous ...

It seems so, but in the mount menu, only cache and sdcrad are ticked and the log was again copied to /data/media and I had to pull it.
[Android Q&A, Help & Troubleshooting] alecxs:
if TWRP can not mount /system /cache but manually mounting works, then there is a fault in fstab. repeat mounting, then try to format data and mount it.

ls -d /dev/block/platform/*/*
mke2fs -t ext4 /dev/block/mmcblk0p23
mount -t ext4 -w /dev/block/mmcblk0p23 /data

if all partitions mounted, write boot.img with dd, then install the Disable_Dm-Verity_ForceEncrypt.zip

dd if=/external_sd/boot.img of=/dev/block/mmcblk0p7 bs=1024 count=16384

check if zip install without errors (see recovery.log). check if /system /cache and /data contain files (at least one folder lost+found should be present)
[Android Q&A, Help & Troubleshooting] Zdendav:
/ # ls -d /dev/block/platform/*/*

←[1;34m/dev/block/platform/mtk-msdc.0/by-name←[m

←[1;34m/dev/block/platform/mtk-msdc.0/by-num←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0boot0←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0boot1←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p1←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p10←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p11←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p12←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p13←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p14←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p15←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p16←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p17←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p18←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p19←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p2←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p20←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p21←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p22←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p23←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p24←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p3←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p4←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p5←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p6←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p7←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p8←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0p9←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk0rpmb←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk1←[m

←[1;36m/dev/block/platform/mtk-msdc.0/mmcblk1p1←[m

Problem:

/ # mke2fs -t ext4 /dev/block/mmcblk0p23

CANNOT LINK EXECUTABLE DEPENDENCIES: library "libext2_blkid.so" not found
[Android Q&A, Help & Troubleshooting] alecxs:
mount /system. then run from adb shell: /system/bin/sh this should give you mksh shell. then try again dd. or run busybox dd instead of dd. meanwhile i will fix the fstab with your output, i will upload twrp in few minutes
[Android Q&A, Help & Troubleshooting] Zdendav:
Still the same:

/ # /system/bin/sh

ALIGATORS5065:/ # mke2fs -t ext4 /dev/block/mmcblk0p23

CANNOT LINK EXECUTABLE DEPENDENCIES: library "libext2_blkid.so" not found

1|ALIGATORS5065:/ #
[Android Q&A, Help & Troubleshooting] alecxs:
before you try this, please double check recovery.fstab entries must match the following output. However, this TWRP you can ONLY use for current ROM/Scatter - it will not work for custom roms or other stock roms. use this TWRP for patching boot only

ls -l /dev/block/platform/*/by-name

check if you can mount data, wipe data and cache, reboot recovery, restore renamed stock boot.emmc.win from TWRP advanced backup restore, then install Disable_Dm-Verity_ForceEncrypt.zip. then upload log and try to boot system
[Android Q&A, Help & Troubleshooting] Zdendav:
Sorry but I'm a little lost - where do I find the recovery.fstab? Should I unpack the stock recovery.img?