Hovatek Forum DEVELOPMENT Android Unisoc (SPD) tablet Alldocube iPlay 20 finally rooted! Any tips on changing ROM?
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


Unisoc (SPD) tablet Alldocube iPlay 20 finally rooted! Any tips on changing ROM?

Unisoc (SPD) tablet Alldocube iPlay 20 finally rooted! Any tips on changing ROM?

Pages (4): Previous 1 2 3 4 Next
josel3
josel3
josel3
Newbie
1
25-12-2020, 03:44 PM
#21



When trying to unlock the bootloader, in the last step I get this message
flashing unlock_bootloader signature.bin
downloading 'unlock_message'...
OKAY [ 0.000s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.102s
How can I solve that?
Thanks
This post was last modified: 25-12-2020, 11:24 PM by josel3.
shadowpanzer
shadowpanzer
shadowpanzer
Enthusiastic Member
5
26-12-2020, 11:58 PM
#23
(09-10-2020, 10:14 PM)tstm Let me thank you first for running a very nice forum with some nice tutorials!

First, some background:
* I've managed to unlock the bootloader
* I have extracted the device pac file with original .img files and I've been using those as my base
* The device is running Android 10 by default and uses the Unisoc SC9863A as a SoC

I've noticed that this tablet seems to have the AVB (Android Verified Boot) system activated, and comes with a vbmeta-sign.img in the pac package. 
I've been following this Hovatek tutorial on AVB vbmeta signing

I have extracted all the keys from the vbmeta-sign and they are all of correct size and seem to be ok:

Code:

% ls -la

1032 Oct  9 21:33 vbmeta_boot_signature.hex
1032 Oct  9 21:34 vbmeta_dtbo_signature.hex
1032 Oct  9 21:38 vbmeta_l_ldsp_signature.hex
1032 Oct  9 21:38 vbmeta_l_lgdsp_signature.hex
1032 Oct  9 21:37 vbmeta_l_modem_signature.hex
1032 Oct  9 21:35 vbmeta_odmko_signature.hex
1032 Oct  9 21:39 vbmeta_pm_sys_signature.hex
1032 Oct  9 21:34 vbmeta_recovery_signature.hex
1032 Oct  9 21:36 vbmeta_socko_signature.hex
1032 Oct  9 21:36 vbmeta_vbmeta_system_signature.hex
1032 Oct  9 21:37 vbmeta_vbmeta_vendor_signature.hex

Using those keys, I have tried several different things, having a self-signed boot.img and separately self-signed recovery.img, but both of those ended up in a boot loop. Then I decided to try to not change any keys, I just did:

Code:

avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flag 2 \
--chain_partition boot:1:keys/vbmeta_boot_signature.hex \
--chain_partition dtbo:10:keys/vbmeta_dtbo_signature.hex \
--chain_partition recovery:2:keys/vbmeta_recovery_signature.hex \
--chain_partition socko:11:keys/vbmeta_socko_signature.hex \
--chain_partition odmko:12:keys/vbmeta_odmko_signature.hex \
--chain_partition system:3:keys/vbmeta_vbmeta_system_signature.hex \
--chain_partition vendor:4:keys/vbmeta_vbmeta_vendor_signature.hex \
--chain_partition l_modem:6:keys/vbmeta_l_modem_signature.hex \
--chain_partition l_ldsp:7:keys/vbmeta_l_ldsp_signature.hex \
--chain_partition l_gdsp:8:keys/vbmeta_l_lgdsp_signature.hex \
--chain_partition pm_sys:9:keys/vbmeta_pm_sys_signature.hex \
--padding_size 16384 \
--output vbmeta_custom.img

And then added the padding (using vbmeta_pad.py), and pushed the image using fastboot:
`fastboot flash vbmeta vbmeta_custom.img`

Unfortunately even this, without any changed boot/recovery partitions results in a boot loop. So I can't even seem to get a functioning vbmeta-sign.img for some reason. Is this somehow different in Android 10? I can see, that I have a vbmeta_system and vbmeta_vendor entry at least in the signature image. Could that be significant?

Any help is appreciated. My main goal would be to switch the alldocube default OS to LineageOS or some similar more open operating system to run on it. And as there is no ready TWRP image for this device - and I'm not sure if I could make it run even if I had one as the AVB protection is there, rooting for now is a good start for my endeavors.

I'm fairly good with linux and machines, so I don't really need any details. Just hints on where to go next?

Have you had any luck researching a way to port TWRP to the iPlay 20? I know there's a mini-compilation guide on XDA here (https://forum.xda-developers.com/t/dev-h...t-32965365), plus the SPD auto TWRP porter in another thread (https://www.hovatek.com/forum/thread-21669.html). If I'm not mistaken, I think there is still some difficulties in compiling TWRP to run on Android 10 but maybe others can chime in on if that's not the case anymore.

I'm still working on rooting my device (and only have a basic understanding of Android development) but would be happy to brainstorm a way to make a TWRP port.
googlenow
googlenow
googlenow
Newbie
3
11-01-2021, 04:59 PM
#24
(22-12-2020, 02:30 PM)Laurent Théodet
(14-10-2020, 08:45 AM)tstm
(13-10-2020, 11:39 PM)gradkal Got it made. I patched boot.img with Canary version of Magisk Manager. This did not work properly. With the release version 8.0.2 it worked fine and I was able to sign the image. Now the device is rooted. Thanks anyway!

Great to hear! If you happen to install some other OS on the thing, LineageOS or something else, please share your experiences! I'd like to get rid of the original OS, as I don't really trust the chinese software..

Hi bro,
I got IPLAY20 unlocked build 20201208 and i tried to patch boot.img with magisk my tablet don't reboot after flashed boot .img patched magisk ??
P.S solved find patched ready to use for firmware 20200824...i hope find later for 20201208
Thanks for help

I also encountered this issue, unable to reboot with patched boot.img for 20201208. Hope somebody can give some hint
blackx12
blackx12
blackx12
Newbie
4
11-01-2021, 11:42 PM
#25



Hi all,

I just receive this error.

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

I used the Magisk 8.0.5 and by stock boot.img is 36700160

I tried use 8.0.2 but i got installation failed on parse image.

Does somebody can help me?

I have the current firmware on my Iplay 20
This post was last modified: 11-01-2021, 11:46 PM by blackx12.
Attached Files
.png
Screenshot 2021-01-11 234534.png
Size: 617.14 KB / Downloads: 6
X3non
X3non
X3non
Recognized Contributor
22,062
12-01-2021, 11:17 AM
#26
(11-01-2021, 11:42 PM)blackx12 ...avbtool: Image size of 36700160 exceeds maximum image size of 36630528 in order to fit in a partition size of 36700160.
...

see the important notice section @ https://www.hovatek.com/forum/thread-32674.html
This post was last modified: 12-01-2021, 11:17 AM by X3non.
blackx12
blackx12
blackx12
Newbie
4
12-01-2021, 02:55 PM
#27
Thank you very much, I completely overlooked the information
X3non
X3non
X3non
Recognized Contributor
22,062
12-01-2021, 08:49 PM
#28
(12-01-2021, 02:55 PM)blackx12 Thank you very much, I completely overlooked the information

not your fault, the info was on a different thread
it was only just added to the avb signing thread after reading your post Smile
blackx12
blackx12
blackx12
Newbie
4
12-01-2021, 11:07 PM
#29
(12-01-2021, 08:49 PM)X3non
(12-01-2021, 02:55 PM)blackx12 Thank you very much, I completely overlooked the information

not your fault, the info was on a different thread
it was only just added to the avb signing thread after reading your post Smile


Now I have unpacked und repacked the patched_boot with carliv_image_kitchen and after that I have signed the image, BUT after flashing vbmeta-sign-custom.img to vbmeta and boot-20210112-2220.img to boot I hang in boot.

Can you please help me with my files?
I have done the complete tutorial again but no success.
I have tried patch boot.imp with current magisk 8.0.5 and with canary magisk.

Alldocube Iplay 20 with stock Firmware iPlay20(T1011S)-EN-20201208

I only want root on the device.

Here my files:
https://drive.google.com/drive/folders/1...sp=sharing

It would be realy nice if you could give me a tip
X3non
X3non
X3non
Recognized Contributor
22,062
13-01-2021, 10:22 AM
#30



(12-01-2021, 11:07 PM)blackx12 Now I have unpacked und repacked the patched_boot with carliv_image_kitchen and after that I have signed the image, BUT after flashing vbmeta-sign-custom.img to vbmeta and boot-20210112-2220.img to boot I hang in boot.
...

be sure to use android image kitchen not carliv's kitchen and first try flashing only the custom vbmeta then confirm if your device can boot to homescreen before proceeding with flashing boot. this will help check where the problem is coming from

if you still have problems then create a new thread for your device issue by clicking "ask question" at the top
Pages (4): Previous 1 2 3 4 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram