Hovatek Forum DEVELOPMENT Android TWRP for Cubot Nova
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


TWRP for Cubot Nova

TWRP for Cubot Nova

Pages (6): Previous 1 2 3 4 5 6 Next
idibi
idibi
idibi
Junior Member
29
12-09-2018, 08:13 AM
#11



(11-09-2018, 10:59 AM)hovatek I wanted to see how Magisk handles your type of boot.img.
Here's a manually patched boot. Flash it and check if the phone is able to boot up normally
https://mega.nz/#!oXojWYDQ!aiGLJlhZVyHMz...EHkxpxMWHU

At first thank you very much for your help, hovatek!
With your manually patched boot and the stock recovery the phone boots normally in the system AND the stock recovery.
If i patch the stock recovery with your porter v1.3 and flash the patched recovery it doesn`t work. The Smartphone goes in boot screen, waits a few seconds and then it`s rebooting in the system normally.

It seems that google have made new security features?
hovatek
hovatek
hovatek
Administrator
49,570
12-09-2018, 10:05 AM
#12
(12-09-2018, 08:13 AM)idibi At first thank you very much for your help, hovatek!
With your manually patched boot and the stock recovery the phone boots normally in the system AND the stock recovery.
If i patch the stock recovery with your porter v1.3 and flash the patched recovery it doesn`t work. The Smartphone goes in boot screen, waits a few seconds and then it`s rebooting in the system normally.

It seems that google have made new security features?

That means the patched boot worked but not TWRP recovery.
What is your phone's kernel version?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
idibi
idibi
idibi
Junior Member
29
12-09-2018, 10:15 AM
#13
(12-09-2018, 10:05 AM)hovatek That means the patched boot worked but not TWRP recovery.
What is your phone's kernel version?

You have disabled the dm_verity in the patched boot.img?

4.4.95 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05))
bldsrv@10-4 #1
Tue Jul 10 18:55:10 CST 2018
This post was last modified: 12-09-2018, 10:17 AM by idibi.
hovatek
hovatek
hovatek
Administrator
49,570
12-09-2018, 06:53 PM
#14
(12-09-2018, 10:15 AM)idibi You have disabled the dm_verity in the patched boot.img?

4.4.95 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05))
bldsrv@10-4 #1
Tue Jul 10 18:55:10 CST 2018

Yes, I'd disabled that but don't know if its still lurking somewhere. That's why I wanted you to flash Magisk patched boot and then the custom recovery so we can at least compare before you revert to stock boot.
We'll have to manually port a custom recovery it seems.
Have you tried porting using the 8.0 , 8.1 and 8.1g options in our tool?
This post was last modified: 12-09-2018, 06:55 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
X3non
X3non
X3non
Recognized Contributor
22,062
12-09-2018, 07:01 PM
#15



(12-09-2018, 10:15 AM)idibi ...

try this TWRP at https://mega.nz/#!YSwmFQqZ!WZ3Si7K7tSk5I...aQhmQmw2ME
lets know the outcome
This post was last modified: 12-09-2018, 07:02 PM by X3non.
idibi
idibi
idibi
Junior Member
29
13-09-2018, 07:34 AM
#16
(12-09-2018, 06:53 PM)hovatek Yes, I'd disabled that but don't know if its still lurking somewhere. That's why I wanted you to flash Magisk patched boot and then the custom recovery so we can at least compare before you revert to stock boot.
We'll have to manually port a custom recovery it seems.
Have you tried porting using the 8.0 , 8.1 and 8.1g options in our tool?

I`ve tried of course only the 8.1 Option because the Cubot Nova have an Oreo 8.1 OS
I was not able to create a Magisk patched boot because at the last output step (the 6th? there is a fault "failed", but boot.img was created, so I don`t know if patched correct)

It`s confused ;-)
Thank you for your help again!
idibi
idibi
idibi
Junior Member
29
13-09-2018, 07:38 AM
#17
(12-09-2018, 07:01 PM)X3non try this TWRP at https://mega.nz/#!YSwmFQqZ!WZ3Si7K7tSk5I...aQhmQmw2ME
lets know the outcome

Thank you, but doesn`t work.
Neither with the stock boot.image nor the patched boot.img from hovatek.
It`s the same: 5 Seconds Nova-Screen then rebooting in normal system.
This post was last modified: 13-09-2018, 07:39 AM by idibi.
hovatek
hovatek
hovatek
Administrator
49,570
13-09-2018, 11:35 AM
#18
(13-09-2018, 07:38 AM)idibi Thank you, but doesn`t work.
Neither with the stock boot.image nor the patched boot.img from hovatek.
It`s the same: 5 Seconds Nova-Screen then rebooting in normal system.

Stick with our patched boot, stock boot would still have DM_verity. Since magisk patching failed, we'll have to stick with manually patched boot.
Try the 8.1 go option in our tool. We've seen such a case where that actually worked. That's why I'm asking you to try it.
This post was last modified: 13-09-2018, 11:36 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
idibi
idibi
idibi
Junior Member
29
13-09-2018, 12:56 PM
#19
Also doesn`t work with 8.1go option, same result ;-(
This post was last modified: 13-09-2018, 12:57 PM by idibi.
hovatek
hovatek
hovatek
Administrator
49,570
14-09-2018, 09:15 AM
#20



(13-09-2018, 12:56 PM)idibi Also doesn`t work with 8.1go option, same result ;-(

OK. We'll work on another manual port. You'll need to exercise patience because manual port requests aren't exactly top priority at the moment.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Pages (6): Previous 1 2 3 4 5 6 Next
Users browsing this thread:
 2 Guest(s)
Users browsing this thread:
 2 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram