Nokia 2.2 (TA-1188 / MT6761) Unable to get rid of "dm-verity error"

pfrei
Enthusiastic Member

10

10-03-2024, 11:31 PM

#1

Hi,

I'm tring to install a custom ROM (Lineage OS 20 & 21 from Andy Yan) on my Nokia 2.2 (TA-1188 / MT6761).

A) I've successfully unlocked the bootloader with mtkclient.
B) I've installed TWRP from here by using the following commands:

Code:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img 

fastboot flash boot twrp.img

C) I've flashed the custom ROM for Lineage OS 20 (not 21) on the system partition by using the following commands:

Code:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot erase systemfastboot flash system system.img

As a result, the custom system ROM for Lineage OS 20 successfully booted.

Then, I wanted to give Lineage OS 21 a try but unfortunately during the flashing process, I somehow unplugged the USB cable and the flashing process got interrupted. Since then, I always get a "dm-verity error" at start-up.

So, I thought that re-installing the stock ROM can fix the issue. For this, I was using the Bypass Utility, SP Flash and locked the bootloader again. Yes, that works. Back to normal for the stock ROM.

BUT: Since then, I'm unable to install TWRP and any custom ROM. Flashing TWRP even results in a black screen when booting. Just flashing the custom ROM system.img results again in the "dm-verity error". The IMEIs have gone as well.

I've already tried the methods described here, but none of them resolved the issue.

It seems as if something else prevents the device from being flashed by anything else than the stock ROM Confused

Could you please give my some advice? I really have no clue what happend...

Many thanks for your help!

maxpayne
Intern

4,334

12-03-2024, 04:25 PM

#2

(10-03-2024, 11:31 PM)pfrei It seems as if something else prevents the device from being flashed by anything else than the stock ROM

Could you please give my some advice? I really have no clue what happend...

Many thanks for your help!

It doesn't look like the firmware you flashed was the same as what was running on the phone was it?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

kelvinchinedu
Contributor

1,596

12-03-2024, 06:17 PM

#3

Because your stock boot image is not same with former,so do twrp ramdisk process

pfrei
Enthusiastic Member

10

16-03-2024, 11:31 PM

#4

I'm using the stock ROM provided by hikari_calyx here: https://xdaforums.com/t/guide-how-to-unl...2.4244039/

It should be for the TA-1188 (unfortunately, I've no complete backup from my previous device).

It's booting fine. But as soon as I unlock the bootloader again to flash TWRP or a custom ROM, the device shows the dm-verity error pops-up again...

Kelexine
Senior Member

152

21-03-2024, 09:15 AM

#5

Then you have to flash vbmeta again to disable avb

pfrei
Enthusiastic Member

10

21-03-2024, 08:41 PM

#6

I think that I know the cause of the issue: That TWRP-version seems to be for devices shipped with Android 11 (twrp-3.7.0_11-0-WSP_sprout.img). But I've flashed an Android 9 stock ROM. Maybe, there's an incompatibility? I'll upgrade to Android 11 stock ROM and will then try again.

pfrei
Enthusiastic Member

10

01-04-2024, 04:44 PM

#7

Indeed, it worked:
1) Flashed stock ROM (Android 9)
2) Upgraded to Android 11 through the official Nokia update channel
3) Installed all security updates through the official Nokia update channel
4) Created backup of full ROM with WwR MTK and SP Flash (i.e. all partitions)

Now, I can flash twrp-3.7.0_11-0-WSP_sprout.img and any custom ROM again :-) So, when flashing TWRP, check the version first. For example twrp-*_11-0-* is for an Android 11 based device.

maxpayne
Intern

4,334

04-04-2024, 03:40 PM

#8

(10-03-2024, 11:31 PM)pfrei Hi,

I'm tring to install a custom ROM (Lineage OS 20 & 21 from Andy Yan) on my Nokia 2.2 (TA-1188 / MT6761).
...
Many thanks for your help!

The stock ROM you installed, was it same build number as what was on the phone or different (update/downgrade)

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

pfrei
Enthusiastic Member

10

05-04-2024, 06:37 AM

#9

No, it had a different build number. But the same API level (28, i.e. Android 9) and the same device model number (TA-1188).

maxpayne
Intern

4,334

17-04-2024, 07:13 PM

#10

(05-04-2024, 06:37 AM)pfrei No, it had a different build number. But the same API level (28, i.e. Android 9) and the same device model number (TA-1188).

If the two ROMs are different then that could explain why the old TWRP isn't working on your current ROM.
Try this alone

Code:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

And see if the phonen boots up fine

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.

View a Printable Version

Users browsing this thread:
1 Guest(s)

Find us

Call us

Mail us

Useful Links

Actions