[The_Beast941]

Hi, I tried to use the Mediatek Auto TWRP Porter to try to port TWRP to my Nokia 2.2 (on Android 9).

However, that requires a stock recovery image which you obviously cannot find in an A/B partitioned device so I cannot use the TWRP Porter in order to port the recovery to my device.

I tried to also create TWRP from source however I have no knowledge on how to get a device tree for my device, make the required modifications and build a working TWRP image for my device.

What's more is that "fastboot boot" does not seem to work when I try to boot a magisk patched boot image if there is no root on my device (or a stock boot image if there is)

Can anyone help me to port or create a TWRP image for my device? Bootloader has already been unlocked if that means anything (Orange State warning at boot)

[X3non]

Hi, I tried to use the Mediatek Auto TWRP Porter to try to port TWRP to my Nokia 2.2 (on Android 9).

However, that requires a stock recovery image which you obviously cannot find in an A/B partitioned device so I cannot use the TWRP Porter in order to port the recovery to my device.
...

copy and rename boot.img to recovery.img then try porting

[The_Beast941]

Hi, I tried to use the Mediatek Auto TWRP Porter to try to port TWRP to my Nokia 2.2 (on Android 9).

However, that requires a stock recovery image which you obviously cannot find in an A/B partitioned device so I cannot use the TWRP Porter in order to port the recovery to my device.
...

copy and rename boot.img to recovery.img then try porting

Just tried doing that but when attempting to boot into recovery it gets stuck on the teamwin splash screen

EDIT: Managed to port TWRP using the guide at https://forum.xda-developers.com/t/guide...e.3843473/
Is there a way to get magisk onto it as well? Tried to patch the boot.img with Magisk but it seems to just boot into Android every time I try to boot into recovery with the Magisk patched image flashed.

[The_Beast941]

For some reason, installing Magisk v22.0 through TWRP makes Magisk overwrite TWRP so that on the next boot there is no recovery installed. Is there any way around this? Already patched vbmeta with a blank image and bootloader is unlocked.

[X3non]

For some reason, installing Magisk v22.0 through TWRP makes Magisk overwrite TWRP so that on the next boot there is no recovery installed. Is there any way around this? Already patched vbmeta with a blank image and bootloader is unlocked.

no, not unless you you boot either twrp or patched boot whenever you need it e.g fastboot boot twrp.img

[The_Beast941]

For some reason, installing Magisk v22.0 through TWRP makes Magisk overwrite TWRP so that on the next boot there is no recovery installed. Is there any way around this? Already patched vbmeta with a blank image and bootloader is unlocked.

no, not unless you you boot either twrp or patched boot whenever you need it e.g fastboot boot twrp.img

Is there a way to fix "fastboot boot" not working then? Every time I try to "fastboot boot" an image it says Transmission OK then it reboots back into whatever is flashed on my boot partition after a while.

[X3non]

Is there a way to fix "fastboot boot" not working then? Every time I try to "fastboot boot" an image it says Transmission OK then it reboots back into whatever is flashed on my boot partition after a while.

what exactly did you attempt to boot? tried booting the new twrp you ported?

[The_Beast941]

Is there a way to fix "fastboot boot" not working then? Every time I try to "fastboot boot" an image it says Transmission OK then it reboots back into whatever is flashed on my boot partition after a while.

what exactly did you attempt to boot? tried booting the new twrp you ported?

I tried it with many images such as magisk patched boot images for various versions of magisk, ported TWRP images (ported using boot.img not recovery.img), stock boot images (if I flashed a Magisk patched image to see if I would temporarily lose Magisk for one boot) etc. In all instances, after running "fastboot boot <name of image>.img" it seems to reboot back into whatever is flashed currently on the boot partition, and not the image supplied via the "fastboot boot" command.



EDIT: After searching around for a while it seems that this is a limitation of the fastboot that Mediatek provides: https://forum.xda-developers.com/t/discu...k.2761785/

It seems that many Mediatek devices that have Fastboot are not able to temporarily boot into an image, which is sad