How to root Unisoc | Spreadtrum Android 9+; Case study: Teclast P80X - Page 7

Home Forum Blog Private Support Courses

Our courses are now on YouTube! Start Watching

Hovatek Forum OPERATING SYSTEMS Android How to root Unisoc | Spreadtrum Android 9+; Case study: Teclast P80X

How to root Unisoc | Spreadtrum Android 9+; Case study: Teclast P80X

How to root Unisoc | Spreadtrum Android 9+; Case study: Teclast P80X

View a Printable Version

Pages (11): Previous 1 … 5 6 7 8 9 … 11 Next

mprudic0404
Enthusiastic Member

8

08-10-2020, 06:22 AM

#61

only android 8+ needs to use the keys to unlock, right or wrong? (isnt this because of google pushing the ANTI-ROLLBACK feature into android 8)
if i have a TECLAST M89pro on android 7, would i still need this key to unlock the bootloader>?

hovatek
Administrator

50,963

08-10-2020, 12:04 PM

#62

(08-10-2020, 06:22 AM)mprudic0404 only android 8+ needs to use the keys to unlock, right or wrong? (isnt this because of google pushing the ANTI-ROLLBACK feature into android 8)
if i have a TECLAST M89pro on android 7, would i still need this key to unlock the bootloader>?

this guide doesn't apply to mediatek devices

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.

_Jaqb_
Junior Member

21

03-12-2020, 08:27 PM

#63

Hi, I have a fast question: are these 2 files enough to the root Teclast P80X?:

1. vbmeta_custom_signed.img
2. magisk_patched_recovery_custom_signed.img

Code:

fastboot flash vbmeta vbmeta_custom_signed.img

and

Code:

fastboot flash recovery magisk_patched_recovery_custom_signed.img

hovatek
Administrator

50,963

04-12-2020, 05:29 AM

#64

(03-12-2020, 08:27 PM)_Jaqb_ Hi, I have a fast question: are these 2 files enough to the root Teclast P80X?:

1. vbmeta_custom_signed.img
2. magisk_patched_recovery_custom_signed.img

Code:

fastboot flash vbmeta vbmeta_custom_signed.img
and

Code:

fastboot flash recovery magisk_patched_recovery_custom_signed.img

Yes, provided:
1. The steps that created these files are correct
2. You boot straight into recovery mode after flashing magisk_patched_recovery_custom_signed.img (you'll need to power off) else root won't be detected

You could also patch boot.img using magisk canary version. That worked for our copy of the P80X so you can just flash TWRP to recovery partition.
Don't forget to rename recovery-from-boot.p if you're flashing TWRP or rooting via recovery partition

This post was last modified: 04-12-2020, 05:31 AM by hovatek.

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.

_Jaqb_
Junior Member

21

04-12-2020, 08:32 AM

#65

Mediatek Course

Mediatek Course

(04-12-2020, 05:29 AM)hovatek Yes, provided...

Thanks!

_Jaqb_
Junior Member

21

04-12-2020, 01:46 PM

#66

(13-03-2020, 09:41 PM)X3non ...
[*]Patch your stock recovery.img
...

Is it possible?
stock recovery.img 40 MB
magisk_patched_recovery.img 22MB

ver.
MM_8.0.3.314
M_20.4

edit
ok, magisk recovery image will be identical in size to stock after signed with private key

This post was last modified: 04-12-2020, 04:10 PM by _Jaqb_.

_Jaqb_
Junior Member

21

05-12-2020, 11:48 AM

#67

(04-12-2020, 05:29 AM)hovatek
(03-12-2020, 08:27 PM)_Jaqb_ Hi, I have a fast question: are these 2 files enough to the root Teclast P80X?:

1. vbmeta_custom_signed.img
2. magisk_patched_recovery_custom_signed.img

Code:

fastboot flash vbmeta vbmeta_custom_signed.img
and

Code:

fastboot flash recovery magisk_patched_recovery_custom_signed.img

Yes, provided:
1. The steps that created these files are correct
2. You boot straight into recovery mode after flashing magisk_patched_recovery_custom_signed.img (you'll need to power off) else root won't be detected

You could also patch boot.img using magisk canary version. That worked for our copy of the P80X so you can just flash TWRP to recovery partition.
Don't forget to rename recovery-from-boot.p if you're flashing TWRP or rooting via recovery partition

Hi, I flashed 2 signed images: patched recovery.img and vbmeta-sign.img. Teclast P80X/Pie starts up normally (no root) and I cannot rename recovery-from-boot.p. Booting to recovery mode doesn't work via Power and Vol- button. No rooting...

Is to my device dedicated TWRP? If so - are they flashing instead of stock recovery.img? Have I to sign TWRP and vbmeta?

hovatek
Administrator

50,963

05-12-2020, 12:53 PM

#68

(05-12-2020, 11:48 AM)_Jaqb_ Hi, I flashed 2 signed images: patched recovery.img and vbmeta-sign.img. Teclast P80X/Pie starts up normally (no root) and I cannot rename recovery-from-boot.p. Booting to recovery mode doesn't work via Power and Vol- button. No rooting...

Is to my device dedicated TWRP? If so - are they flashing instead of stock recovery.img? Have I to sign TWRP and vbmeta?

As explained in the guide, if you want to root via recovery then you need to go though the research download tool trick to get the tablet to power off. Only then can you attempt booting into recovery mode using button combo.
Mind you, the phone will just boot up when you try entering recovery mode from off state but you'll have root.

Another approach is to just patch boot.img using magisk canary version, sign it and flash to the boot partition

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.

_Jaqb_
Junior Member

21

06-12-2020, 07:12 PM

#69

(05-12-2020, 12:53 PM)hovatek ...
As explained in the guide, if you want to root via recovery then you need to go though the research download tool trick to get the tablet to power off. Only then can you attempt booting into recovery mode using button combo.
Mind you, the phone will just boot up when you try entering recovery mode from off state but you'll have root.

Another approach is to just patch boot.img using magisk canary version, sign it and flash to the boot partition

Thanks! How to go through the research download tool trick to get the tablet to Power Off?

Another approach - I can't verify the contents of a patched magisk boot.img (on Linux & Windows).

In terminal (Python 2) I got message:

Code:

Given image does not look like a vbmeta image.

or (Python 3)

Code:

File "avbtool", line 411
    b = 2L**32
         ^
SyntaxError: invalid syntax

The contents of a stock boot.img in avbtool is ok...

When I ignore it and sign patched boot.img I got this message:

Code:

avbtool: Image size of 36700160 exceeds maximum image size of 36630528 in order to fit in a partition size of 36700160.

Is patched img wrong because of new version Magisk Canary/Magisk?

This post was last modified: 06-12-2020, 07:43 PM by _Jaqb_.

hovatek
Administrator

50,963

07-12-2020, 09:12 AM

#70

(06-12-2020, 07:12 PM)_Jaqb_ Thanks! How to go through the research download tool trick to get the tablet to Power Off?

Another approach - I can't verify the contents of a patched magisk boot.img (on Linux & Windows).

In terminal (Python 2) I got message:

Code:

Given image does not look like a vbmeta image.

or (Python 3)

Code:

File "avbtool", line 411 b = 2L**32 ^ SyntaxError: invalid syntax

The contents of a stock boot.img in avbtool is ok...

When I ignore it and sign patched boot.img I got this message:

Code:

avbtool: Image size of 36700160 exceeds maximum image size of 36630528 in order to fit in a partition size of 36700160.

Is patched img wrong because of new version Magisk Canary/Magisk?

Its the contents of stock boot you verify and use that info when signing patched boot.
Create a thread for this by clicking Ask Question at the top

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.

Pages (11): Previous 1 … 5 6 7 8 9 … 11 Next

View a Printable Version

Users browsing this thread:
2 Guest(s)

Users browsing this thread:
2 Guest(s)