TWRP recovery porter for 360 N6lite
TWRP recovery porter for 360 N6lite
12-05-2021, 07:13 AM
(10-05-2021, 02:28 PM)vpolinov Yes, it looks so.
No problem: as soon as I get this error I flash stock boot immediatelly and it solves the issue. I've done so dozens of times.
To be honest, my last attempts to patch boot.img were conducted exactly with magisk canary (22101 / 22102 / 22104) as magisk stable updates very rarely. I tried several stable versions (22.0 / 21.4 / 21.3 / 21.2 / 20.4 / 20.1 / 19.2 / 18.1 / 17.4 / 17.1) - result is always the same.
Am I right there is no way to cope with DM-verity? I'm aware of DM-Verity disabler script but I have no idea how to apply it without having TWRP....
You could try looking for a compatible prerooted GSI
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
12-05-2021, 08:37 AM
(12-05-2021, 07:13 AM)maxpayne You could try looking for a compatible prerooted GSI
Hello,
Let me remind you the beginning of the story.
I tried your TWRP recovery porter tool and found it does not work stumbling on 'DM-Verity'.
Your colleague tried to look into the issue. I guess, his/her intention was to make sure if I performed all actions with porter tool correctly. During this investigation, your colleagues tried to patch my stock boot.img to see if it can overcome the issue. It didn't.
I don't know where to look for "prerooted GSI" which would be !!*compatible with my device*!! However, if you provide me with "prerooted GSI" I'll give it a try of course, and it'll be a brand new thread of discussion.
All I wanted to know !!*in this thread*!! is that Hovatek's recovery porter can handle security limitations of my ancient Oreo stock ROM.
As of today, I see it cannot.
I'm remaining open to your suggestions to see if this is not end of the story about Hovatek's recovery porter tool's capability.
This post was last modified: 12-05-2021, 09:47 AM by vpolinov.
15-05-2021, 09:26 AM
(12-05-2021, 08:37 AM)vpolinov ..
All I wanted to know !!*in this thread*!! is that Hovatek's recovery porter can handle security limitations of my ancient Oreo stock ROM.
As of today, I see it cannot.
I'm remaining open to your suggestions to see if this is not end of the story about Hovatek's recovery porter tool's capability.
Here's the thing...
Your current situation does not point at a problem with the TWRP porter itself. If it detects dm-verity, it warns you to disable that else the flashed TWRP will result in a bootloop.
This is similar to what you're encountering when you flash a magisk-patched boot. This doesn't mean magisk hasn't patched your boot for root, its the dm-verity disabling part that's the issue.
Summary is that your model is rejecting unofficial images. DM verity is one suspect so the first step is finding how to disable it for this very model. That or your phone is just one of those types that only accept -sign images
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)
