[Miscellaneous Android Development] pieromtk:
HI, the mtk-su is working in my blackview a8 max with mtk6737 chipset, I'm root.

Unfortunately I can't get the telephone to oem unlock (as other telephones with the same chipset) because fastboot prompts to presso volumeup, but it doesn't react in any way.

At every next reboot fastboot getvar all 2>&1 | grep lock shows that it's still unlocked (and the warranty still on, that apparently must be set to off).

I wonder if some of you guys had success to unlock this chipset.

I've even overwritten the seccfg partition with this method, but nothing has changed

I've tried to fastboot boot custom.img to verify if I could boot another image without flashing it, but it failed because of the lock.

shell@x5623_jk_a8_37m65:/data/local/tmp # find /de

default.prop dev/

ind /dev -name by-name -exec ls -la {} \; <

total 0

drwxr-xr-x 2 root root 500 2020-01-25 12:48 .

drwxr-xr-x 4 root root 620 2020-01-25 12:48 ..

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 boot -> /dev/block/mmcblk0p7

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 cache -> /dev/block/mmcblk0p21

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 expdb -> /dev/block/mmcblk0p10

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 flashinfo -> /dev/block/mmcblk0p23

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 frp -> /dev/block/mmcblk0p17

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 keystore -> /dev/block/mmcblk0p14

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 lk -> /dev/block/mmcblk0p5

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 logo -> /dev/block/mmcblk0p9

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 metadata -> /dev/block/mmcblk0p19

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 nvdata -> /dev/block/mmcblk0p18

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 nvram -> /dev/block/mmcblk0p2

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 oemkeystore -> /dev/block/mmcblk0p12

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 para -> /dev/block/mmcblk0p6

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 proinfo -> /dev/block/mmcblk0p1

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 protect1 -> /dev/block/mmcblk0p3

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 protect2 -> /dev/block/mmcblk0p4

lrwxrwxrwx 1 root root 20 2020-01-25 12:48 recovery -> /dev/block/mmcblk0p8

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 seccfg -> /dev/block/mmcblk0p11

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 secro -> /dev/block/mmcblk0p13

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 system -> /dev/block/mmcblk0p20

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 tee1 -> /dev/block/mmcblk0p15

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 tee2 -> /dev/block/mmcblk0p16

lrwxrwxrwx 1 root root 21 2020-01-25 12:48 userdata -> /dev/block/mmcblk0p22

I've dd-ed the oemkeystore image hoping to find there the settings, but it's totally empty (od shows all 0s).

Any idea? I'd really like to overwrite this fw. It's almost as slow and useless as if it were turned off.

Ah and adb sideload failed because it lost the connection.

UPDATE: I've even overwritten the recovery partition with TWRP.img , then sync and

adb reboot recovery

but ... it didn't work! The usual android came up and when I rebooted to recovery there was the stock recovery firmware.