Alldocube iPlay 40 review: an all-around tablet with some minor compromises

[White_Spot™]

Hi, I'm also trying to unlock the bootloader of my t1020s but without much luck. I used AllexBast chinese guide and its .apk to get the signature.bin but the command "fastboot flashing unlock-bootloader signature.bin" always fails printing "fastboot: usage: unknown 'flashing' command unlock_bootloader". Did something similar happen for you? Any ideas? Thanks in advance.

Yes, the fastboot file was to be a specific one. I can't remember where I get the correct one (my work folder is a mess with many files) but eventually is one from the links he give.
Go and try different fastboot files until one works.

 

[AllexBast]

Hi, I'm also trying to unlock the bootloader of my t1020s but without much luck. I used AllexBast chinese guide and its .apk to get the signature.bin but the command "fastboot flashing unlock-bootloader signature.bin" always fails printing "fastboot: usage: unknown 'flashing' command unlock_bootloader". Did something similar happen for you? Any ideas? Thanks in advance.

try these drivers

Universal ADB Drivers

Fastboot

https://xdaforums.com/t/tool-windows-tiny-adb-fastboot-august-2021.3944288/

 

[davovapo]

For t1020s
TWRP https://drive.google.com/file/d/1lsmYtOESkvI4vz3tLgg9P5CsxaZ3g2fr/view?usp=sharing - flash to rd https://4pda.to/pages/go/?u=https://mega.nz/file/5RFymB6Q#KjfDboHeduvuXvBi1SDLboO-48o0bmMhBC5FyTIwAVM&e=108966608
firmware global https://www.alldocube.com/en/firmware/alldocube-iplay40t1020s-firmware-download/
ModSuper for gsi https://drive.google.com/file/d/1YRZbiTEEnyds6kxrvXNI2-5gRwjCbE4l/view?usp=sharing install for section super
format data - yes
restart adb recovery
gsi android 10 arm64 a-b - https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ install for section system
format data - yes
restart adb recovery
backup boot
install zip https://github.com/topjohnwu/Magisk/releases/tag/v23.0
restore boot
restart system
configure gsi rom
restart adb recovery
install gapps android 10 arm64 pico https://opengapps.org/
restart system

Thanks to both, I unlocked successfully the bootloader using the fastboot file from AllexBast linked juseblog guide, I added the file here in case somebody needs it too and just to note it the unlocking process took around 12 minutes. Now I'm trying to follow AllexBast steps, I followed the "flash to rd" guide and worked great but when flashing the recovery with "fastboot flash recovery recovery.img" it seems to be stuck at "Writing 'recovery'..." I may leave it for some more hours or overnight to see if it actually works.

 

[AllexBast]

Thanks to both, I unlocked successfully the bootloader using the fastboot file from AllexBast linked juseblog guide, I added the file here in case somebody needs it too and just to note it the unlocking process took around 12 minutes. Now I'm trying to follow AllexBast steps, I followed the "flash to rd" guide and worked great but when flashing the recovery with "fastboot flash recovery recovery.img" it seems to be stuck at "Writing 'recovery'..." I may leave it for some more hours or overnight to see if it actually works.

You need to flash all 3 files:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img

 

[davovapo]

You need to flash all 3 files:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img

Flashing boot, vbmeta and finally recovery worked, now I can access TWRP. I can't seem to find my files on TWRP though to flash zips, etc, I imagine it's the encryption. I tried to install the ModSuper file super.new.img through "flash super super.img" in fastmode, it seemed to work ok but it entered a bootloop in which I had to reset the device firmware to be able to boot normally again. If I figure out something I'll update, thanks again.

 

[AllexBast]

Flashing boot, vbmeta and finally recovery worked, now I can access TWRP. I can't seem to find my files on TWRP though to flash zips, etc, I imagine it's the encryption. I tried to install the ModSuper file super.new.img through "flash super super.img" in fastmode, it seemed to work ok but it entered a bootloop in which I had to reset the device firmware to be able to boot normally again. If I figure out something I'll update, thanks a

Unfortunately in this twrp there is no reboot point in recovery. But twrp supports ADB commands, so after format data is yes, you need to reboot in recovery using the adb reboot recovery command. Modsupergsi, gsi and gapps are flashed via twrp. Need micro sd card.
TWRP supports mtp, perhaps you can copy the file to the tablet memory after flashing fastboot flash super modsupergsi.img, format data-yes, adb reboot recovery and do without microsd

 

[davovapo]

Unfortunately in this twrp there is no reboot point in recovery. But twrp supports ADB commands, so after format data is yes, you need to reboot in recovery using the adb reboot recovery command. Modsupergsi, gsi and gapps are flashed via twrp. Need micro sd card.
TWRP supports mtp, perhaps you can copy the file to the tablet memory after flashing fastboot flash super modsupergsi.img, format data-yes, adb reboot recovery and do without microsd

I installed the new super.img from your post, formatted, rebooted back to recovery but then when I try to install lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img it fails due to img being too large as you can see in the attachment (not the correct img maybe?) which made me reset the device again. I could install Magisk like White_Spot, that worked well as long as you back up and restore the boot as you pointed out.

 

[AllexBast]

I installed the new super.img from your post, formatted, rebooted back to recovery but then when I try to install lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img it fails due to img being too large as you can see in the attachment (not the correct img maybe?) which made me reset the device again. I could install Magisk like White_Spot, that worked well as long as you back up and restore the boot as you pointed out.

Is that how you formatted it?

 

[davovapo]

Is that how you formatted it?

I formatted data - yes indeed. I'm attaching pictures of the process.

 

[AllexBast]

I formatted data - yes indeed. I'm attaching pictures of the process.

Sorry, I gave the wrong link modsupergsi. Here is the true

super.treble2product.rar

drive.google.com

 

[davovapo]

Sorry, I gave the wrong link modsupergsi. Here is the true

https://drive.google.com/file/d/1JLJd-EdGBqQ5az7kclVb3xkeMd6jJEif/view?usp=drivesdk[/URNL]

No worries, thank you for the support, but now I formatted data and tried again with the new modsupergsi and it shows the same "Size image is larger..." error when trying to install in section super.

 

[AllexBast]

No worries, thank you for the support, but now I formatted data and tried again with the new modsupergsi and it shows the same "Size image is larger..." error when trying to install in section super.

To avoid confusion, flash the stock firmware research download via and repeat all operations on a new one

 

[davovapo]

To avoid confusion, flash the stock firmware via rd and repeat all operations on a new one

Just to make sure I'll write it all down, thanks again for your patience.

So I'm using the official firmware iPlay40(T1020S)-EN-20210526 pac file with ResearchDownload. It works great, then I boot it, activate usb debug in settings, go to fastboot and flash boot, vbmeta and recovery. Then I reboot so I can go to recovery with adb and in recovery it's when I try to install the super.treble2product.img in section super. At this point the error of the last pic with "Size larger..." appears. As I understand, I am installing super.treble2product.img on stock firmware here.

 

[AllexBast]

Just to make sure I'll write it all down, thanks again for your patience.

So I'm using the official firmware iPlay40(T1020S)-EN-20210526 pac file with ResearchDownload. It works great, then I boot it, activate usb debug in settings, go to fastboot and flash boot, vbmeta and recovery. Then I reboot so I can go to recovery with adb and in recovery it's when I try to install the super.treble2product.img in section super. At this point the error of the last pic with "Size larger..." appears. As I understand, I am installing super.treble2product.img on stock firmware here.

Make format data in twrp on stock firmware.

If you fail to flash, then open super.treble2product.img in the hxd editor and at the very end delete the zero values of a few kilobytes.

 

[davovapo]

Make format data in twrp on stock firmware.

Alright, I went through it again, I'm updating the steps I wrote before, I'll keep trying till I get it or brick it:

So I'm using the official firmware iPlay40(T1020S)-EN-20210526 pac file with ResearchDownload. It works great, then I boot it, activate usb debug in settings, go to fastboot and flash boot, vbmeta and recovery. Then I reboot so I can go to recovery with adb, I format data - yes and adb reboot recovery. Again in recovery it's when I try to install the super.treble2product.img in section super.

At this point the error "Size of image is larger than target device" still appears.

 

[AllexBast]

Alright, I went through it again, I'm updating the steps I wrote before, I'll keep trying till I get it or brick it:

So I'm using the official firmware iPlay40(T1020S)-EN-20210526 pac file with ResearchDownload. It works great, then I boot it, activate usb debug in settings, go to fastboot and flash boot, vbmeta and recovery. Then I reboot so I can go to recovery with adb, I format data - yes and adb reboot recovery. Again in recovery it's when I try to install the super.treble2product.img in section super.

At this point the error "Size of image is larger than target device" still appears.

If you fail to flash, then open super.treble2product.img in the hxd editor and at the very end delete the zero values of a few kilobytes. The file must be glued without this block of zeros in order to reduce the size of the image.

HxD - Freeware Hex Editor and Disk Editor | mh-nexus

The fact is that I hurried to upload the files and did not fix the errors. But since no one wanted to test this version of the firmware, I did not double-check anything. Now I have neither a tablet nor a laptop. Therefore, I cannot check and re-upload the files.

 

[davovapo]

If you fail to flash, then open super.treble2product.img in the hxd editor and at the very end delete the zero values of a few kilobytes. The file must be glued without this block of zeros in order to reduce the size of the image.

That did it! Thank you so much AllexBast, lineageOS17.1 is installed with gapps pico following the rest of your steps. I bought this tablet without knowing much about its custom rom support and I'm glad we are able to change the OS at least, I learned quite a bit. Now the next goal would be A11 or even 12, I'd like to know more into making custom roms and see what I find and how overwhelming it is, probably a lot.

 

[AllexBast]

I can’t deal with firmware yet. Just do not try to flash firmware 11 android from the t1020h and t1020hp models, I did it and barely recovered. I read on xda that to install 11 and 12 android you need to change something in vendor.img which is located in super.img. Know that initially we have 10 android and it is from him that we must proceed about compatibility with 11 and 12 android.

 

[AllexBast]

That did it! Thank you so much AllexBast, lineageOS17.1 is installed with gapps pico following the rest of your steps. I bought this tablet without knowing much about its custom rom support and I'm glad we are able to change the OS at least, I learned quite a bit. Now the next goal would be A11 or even 12, I'd like to know more into making custom roms and see what I find and how overwhelming it is, probably a lot.

For now, check out the latest builds for Android 10 here https://xdaforums.com/f/treble-enabled-device-development-a-ab-roms.7260/

 

[RedNas74]

I'm trying to unlock the bootloader, but i get an error from fastboot:

fastboot flashing unlock_bootloader signature.bin
fastboot: usage: unknown 'flashing' command unlock_bootloader

What am I doing wrong? I enabled oem unlocking in developer options and generated the signature.bin