Hovatek Forum DEVELOPMENT Android TWRP recovery porter for 360 N6lite
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


TWRP recovery porter for 360 N6lite

TWRP recovery porter for 360 N6lite

Pages (2): 1 2 Next
vpolinov
vpolinov
vpolinov
Junior Member
23
05-05-2021, 05:15 PM
#1



This is in relation to my post: https://www.hovatek.com/forum/thread-262...#pid212951

Answering your questions:

1. Yes, if I flash only modified (by magisk) boot.img, without modified recovery.img, the phone gets a bootloop.
2. I believe bootloader is unlocked judging by the info on enclosed screenshot with fastboot responses.

Thank you!
This post was last modified: 06-05-2021, 06:45 AM by vpolinov.
Attached Files
.png
bootloader.png
Size: 57.93 KB / Downloads: 7
X3non
X3non
X3non
Recognized Contributor
22,062
06-05-2021, 10:07 AM
#2
(05-05-2021, 05:15 PM)vpolinov ...

try patching boot using method 1 @ https://www.hovatek.com/forum/thread-32719.html
again, only flash patched boot and confirm if bootloop or not
vpolinov
vpolinov
vpolinov
Junior Member
23
06-05-2021, 04:24 PM
#3
(06-05-2021, 10:07 AM)X3non
(05-05-2021, 05:15 PM)vpolinov ...

try patching boot using method 1 @ https://www.hovatek.com/forum/thread-32719.html
again, only flash patched boot and confirm if bootloop or not

I wish I could benefit from method #1 but there is no 'verify' in stock boot.img, see the screen.
Attached Files
.png
boot.img.png
Size: 451.92 KB / Downloads: 5
X3non
X3non
X3non
Recognized Contributor
22,062
07-05-2021, 10:11 AM
#4
(06-05-2021, 04:24 PM)vpolinov I wish I could benefit from method #1 but there is no 'verify' in stock boot.img, see the screen.

zip and upload your stock boot.img then post the link here
you can upload to any cloud storage e.g gdrive, mega, e.t.c
vpolinov
vpolinov
vpolinov
Junior Member
23
07-05-2021, 04:51 PM
#5



Here are the links:

stock recovery.img (android 8.1): https://disk.yandex.ru/d/F4IHueroahPBhQ
stock boot.img (android 8.1): https://disk.yandex.ru/d/x_zcR0WDg9d4hg
This post was last modified: 09-05-2021, 02:01 PM by vpolinov.
X3non
X3non
X3non
Recognized Contributor
22,062
08-05-2021, 12:29 PM
#6
(07-05-2021, 04:51 PM)vpolinov Here are the links:
...

try the patched boot @ https://mega.nz/file/AwRHVA7B#51eUkY0A3x...nzyZYgxsqg
vpolinov
vpolinov
vpolinov
Junior Member
23
09-05-2021, 02:15 PM
#7
(08-05-2021, 12:29 PM)X3non
(07-05-2021, 04:51 PM)vpolinov Here are the links:
...

try the patched boot @ https://mega.nz/file/AwRHVA7B#51eUkY0A3x...nzyZYgxsqg

Thank you, I do appreciate your willingness to help, especially when you do it on weekends!!

Regarding the boot.img you've patched: unfortunately, phone did not accept it. Result can be seen on attached photo. It is the same screen as I get when try to flash boot.img patched by magisk.

Translation into English:
"Detected that the phone has been swiped into the non-officially certified ROM package! The phone will turn off in 5 seconds!"
This post was last modified: 09-05-2021, 02:25 PM by vpolinov.
Attached Files
.jpg
bootloop_crash.jpg
Size: 83.33 KB / Downloads: 4
vpolinov
vpolinov
vpolinov
Junior Member
23
09-05-2021, 02:51 PM
#8
...del
This post was last modified: 09-05-2021, 06:07 PM by vpolinov.
X3non
X3non
X3non
Recognized Contributor
22,062
10-05-2021, 12:32 PM
#9
(09-05-2021, 02:15 PM)vpolinov ...
Regarding the boot.img you've patched: unfortunately, phone did not accept it. Result can be seen on attached photo. It is the same screen as I get when try to flash boot.img patched by magisk.

Translation into English:
"Detected that the phone has been swiped into the non-officially certified ROM package! The phone will turn off in 5 seconds!"

that looks like red state
flash back your stock boot and confirm that you can boot into homescreen, then try patching boot using magisk canary, see if that works or not
vpolinov
vpolinov
vpolinov
Junior Member
23
10-05-2021, 02:28 PM
#10



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....
This post was last modified: 10-05-2021, 02:38 PM by vpolinov.
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram