yashsingh1/xdaforums huggingface dataset:
[Device Reviews and Information] ducknezz:
Sorry for bumping such an old post.

I would like to share my experience, hope it is useful for others that is experiencing the same problem.

I faced the same issue, the tab kept on restarting with the "abnormal temperature" warning. It is getting worst after I updated to the latest OTA firmware.

Been following the advise from our fellow users in here (installing those apps and what's not) up to a point I would like to rip it open and try to use thermal tape and/or disconnect the battery cables.

I accidentally found that the issue wont arise if I am using the tab while charging it. Usually it took tab will restart after 2-3 minutes on Netflix but none happen when im on charging mode.

Whilst this would not solve the problem, but perhaps I could continue using my tab (and no need for me to pry it open) while waiting for the latest update that solves this problem.

Tl;dr: Use the tab in charging mode, it wouldnt restart.

Hope this helps.
[Device Reviews and Information] White_Spot™:
In my case (my daughter) using the tablet when it is charging does not prevent the appearance of the temperature error / problem.

The only conclusion we can make is some have no issues, others have this issue always, others only sometimes. Not even worth thinking about it too much lol. But in the end, if the problem appears, you know that one solution is the addition of a 4.7K resistor to the white cable of the battery.
[Device Reviews and Information] White_Spot™:
I should add the information that the resistor have to be added in parallel and not in series.

I first added it in series and when my daughter went to charge the tablet it didn't charge. The information / animation of charging show up, but it never passes from 0% (yes 0% as my daughter like to drain to the end of the battery).

I added a little cable, so the resistor be in parallel and the tablet start to charging normally.

Until now the problem doesn’t show up again, but it is too soon to say if the problem disappeared "forever", as sometimes the error doesn't show up several days with heavy use.
[Device Reviews and Information] blaze2051:
Update--- i got it to work i add to use the fastboot version from the zip file, this time it work this is for my smile1 T803 unisoc t310 tablet with android 11

fastboot flashing unlock_bootloader signature.bin command does not work
[Device Reviews and Information] blaze2051:
Any working GSI android 10 for the T310 8in tablet ?

Any chance the iPay40 TWRP will work on the T803?
[Device Reviews and Information] AllexBast:
Need vendor, boot, recovery from your firmware. Read previous posts on how to do it.
[Device Reviews and Information] blaze2051:
i extracted the all files from the .pac oem firmware BUT only files that are usable are boot.img 65mb and super.img 3.6GB no recovery. stock firmware from factory is A11.
[Device Reviews and Information] blaze2051:
link is broken
[Device Reviews and Information] AllexBast:
Nothing from iPlay40 will suit you. Your boot.img contains revovery. Unpack super.img and post your vendor.img
[Device Reviews and Information] blaze2051:
yes unpacking the super.img is my issue. I dont have a way to unpack super.img. I use windows 10 and one app that worked for LG G8 super.img doesnt work with alldocube super.img.

do you know of another windows based super.img unpacker?
[Device Reviews and Information] AllexBast:
https://xdaforums.com/t/teclast-m40-how-to-unlock-bootloader.4185363/post-86205553
[Device Reviews and Information] blaze2051:
thanks for the help but one link is broken and the other is a trojon virus

Super.img Extractor | Extract build.prop from system and reverse System Image

Super.img Extractor | Extract build.prop from system and reverse System Image %

cruzersoftech.com
[Device Reviews and Information] AllexBast:
I can advise https://xdaforums.com/t/tool-windows-kitchen-crb-v3-0-0-beta14.3947779/ . With this tool I repack vendor.img.

You will have to fix 3 fstab files yourself
[Device Reviews and Information] tchcrat:
That is totally against the theory. The only reason why it is not charging is that your overall resistance is too large than the programmed limits or the resistance is faulty or not making proper contact. You can just test this by cutting the white wire and not attaching anything. Double check your resistance value. If it is still causing charging failure try with lower resistance like a 2.2k. It should be in "series". Also you can connect a resistance (around 8-10k) between white and black at the mother board side after cutting the white wire if your battery ntc is totally unusable(This will void the capability to detect any change in temp though)
[Device Reviews and Information] blaze2051:
I installed this program but im missing files to make it work
[Device Reviews and Information] blaze2051:
I patched T803 boot with magisk with v22.1 but once i flash boot_patched.img via RD it results in a boot loop. Am I missing a step of what other files need to be flashed?

Then i tried to flash twrp via fastboot and i got an error
[Device Reviews and Information] blaze2051:
I managed to unpack raw the super.img from T803 but not sure where to go from here.

I also managed to get my boot and dtbo key from my vbmeta-sign.img. So now not sure whats the next step
[Device Reviews and Information] blaze2051:
i finally figured it out, so after the smaller patch_boot.img is repacked. that avbtool command used to sign for the boot.img will inflate img back to specific size. After flashing patch_inflate boot.img along with your custom signed vbmeta.img you well get stuck on boot. thats is to be expected. after that go back to download mode and flash your stock oem vbmeta-signed.img and it will boot up to android with magisk root installed.
[Device Reviews and Information] blaze2051:
T803_vendor_a.7z

drive.google.com
[Device Reviews and Information] AllexBast:
If you need a working vbmeta, then you should check out this post https://forum.hovatek.com/thread-32664.html. I completely disable encryption and avb control
[Device Reviews and Information] blaze2051:
I need twrp for unisoc
[Device Reviews and Information] AllexBast:
Unfortunately there is no twrp for unisoc android 11
[Device Reviews and Information] blaze2051:
this can be signed using T803 keys and flashed since this supports android 12 and my tablet is on android 11?
[Device Reviews and Information] blaze2051:
i even tried to use

fastboot boot twrp.img and i get error too many links tried on usb 3.0 and 2.0

then i ran

sudo ./fastboot boot twrp.img and i get error status read failed (protocol error) in linux
[Device Reviews and Information] NightLord:
So basicly you are booting with a custom signed boot.img, and the stock vbmeta-signed.img? (which should contain a different public key than the one that can be generated from your custom private key used to sign your magisk-patched boot.img).
[Device Reviews and Information] NightLord:
This is for a different SoC then your Unisoc Tiger T310 (MediaTek Helio G95 MT6785). No idea if that is a problem, just stating the fact : )
[Device Reviews and Information] blaze2051:
magisk_boot.img is not signed

I made my own custom-sign-vbmeta.img i flash it together. which ends in a stuck boot.

reload RD and flash oem sign vbmeta.img and it boots into android with patched boot.img
[Device Reviews and Information] blaze2051:
right. it was ported to the iplay40, i been trying to use commands

fastboot boot twrp.img and i get error too many links tried on usb 3.0 and 2.0

then i ran

sudo ./fastboot boot twrp.img and i get error status read failed (protocol error) in linux

so then i tried another way I unpacking of the boot.img is fine, problem is i dont know what needs to be replaced in order to inject twrp.img into the boot.img

2nd i tried to unpack and repack my own super.img BUT

when i use this commnad--

./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:3697308624 --group main:2859118592 --partition system:readonly:1970069504:main --image system=./system_a.img --partition vendor:readonly:538230784:main --image vendor=./vendor_a.img --partition system_ext:readonly:350818304:main --image system_ext=./system_ext_a.img --sparse --output ./super.new.img

I get ./lpmake: input/output error and i checked it several times. im using mint 18
[Device Reviews and Information] NightLord:
You wrote "i finally figured it out, so after the smaller patch_boot.img is repacked. that avbtool command used to sign for the boot.img will inflate img back to specific size. " So I thought you signed your patched boot.img with avbtool.
[Device Reviews and Information] NightLord:
What are you modifing in super.img?
[Device Reviews and Information] blaze2051:
Im replacing system.img with lineage os.img

I tried to use

Fastboot flash vbmeta-custom-signed.img but it never finishes. Originally i wanted to flash system_a with lineage 17.1
[Device Reviews and Information] NightLord:
I was able to simply flash system_a in the fastbootd (not bootloader) environment via fastboot with GSI images (A12). They boot okay without even touching stock vbmeta, but only with the stock boot.img.
[Device Reviews and Information] wergon33:
who has problems with a memory card on the new TWRP roll back to version 10

ps. no, it does not work
[Device Reviews and Information] blaze2051:
ah okay i was using fastboot bootloader, i wil try fastbootd instead
[Device Reviews and Information] blaze2051:
thats was i thought at first but i looks like the command only changes the flags from 1 to 2, but i read in another tread that using this might be better heres an example

avbtool make_vbmeta_image --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096 --flags 0 --padding_size 20480 --output vbmeta.img

I also found this tool that might help someone with porting twrp for unisoc or mediatek devices

Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek

If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se

forum.hovatek.com

https://forum.hovatek.com/thread-32664.html

https://forum.hovatek.com/thread-32674.html
[Device Reviews and Information] NightLord:
You will probably need to delete product partition, because otherwise you will not have enough space inside super partition to accomodate for the larger lineage os image.

For example, on my stock FW, system size is only 900 megs, but product is an additional 1.9gigs.

so:

fastboot delete-logical-partition product_a <--- in case "a" is your current active slot.

of course, this is also to be done in fastbootd environment.
[Device Reviews and Information] NightLord:
By signing boot.img i'm referring to this:

avbtool add_hash_footer --image boot.img --partition_name boot --partition_size (whatever the size of the original image is) --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096

How to use AVBtool and a private key to sign a Unisoc (SPD) image

This guide will explain how to sign Unisoc / Spreadtrum (SPD) images (e.g boot, recovery etc) using a private key and AVBtool. This guide is ideal for those with vbmeta-sign.img in their firmware as s

forum.hovatek.com
[Device Reviews and Information] blaze2051:
looks like after deleting the system and logical partition i still dont have enough space to flash lineage os.img

so i managed to flash using non modified adb fastbootd but it only boots into bootloader mode fastboot

i deleted a logical partitions and only left system_a reflashed lineage 2nd time and it still just boots to bootloader fastboot,
[Device Reviews and Information] NightLord:
You are deleting product, and not product_a. Not sure it makes a dirrerence, but you should try
[Device Reviews and Information] blaze2051:
product partition is listed but its actually product_a when flashing is needed, same thing with system when i flash system.img its gets flashed to system_a partition.

I got it to flash but it wont boot , it goes to bootloader i flashed lineage 17.1 on a tablet that came android 11

i deleted product and vendor to have more room
[Device Reviews and Information] NightLord:
I think vendor needs to stay, that may be the reason why your rom is not booting.

Try deleting system_ext instead. I have product and system_ext deleted, with vendor kept intact.
[Device Reviews and Information] Wajs:
I have a question, can anyone confirm that there is sound after you connect to some bluetooth receiver? On lineage-17.1-20210808?

Because it looks that its not working.
[Device Reviews and Information] blaze2051:
I reflashed super.img and the system booted fine

i erased product and system, and flashed lineage 17.1 with no issues BUT it still wont boot, goes to bootloader, i did not use

fastboot --disable-verification flash vbmeta vbmeta-sign.img

because fastboot getvar is-userspace = yes.

so im gonna keep trying to see if theres something i might have missed

i went back used commnad

fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta-sign.img

then i flashed lineage 17.1 and it booted to black screen not even bootloader, so i reflashed stock vbmeta via RD and it boots back to bootloader

i tried these commands with oem vbmeta and custom vbmeta.img and used fastboot -w after evey flash and it does not boot

fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta-sign.img or vbmeta custom

fastboot --disable-verity flash vbmeta_a vbmeta-sign.img or vbmeta custom
[Device Reviews and Information] NightLord:
Lienage 17.1 is A10 and your tablet comes with A11, right? Maybe its not compatible with A10. Why not try lineage 18 or 19?

( In my experience there is no need to touch stock vbmeta when flashing Gsi.)
[Device Reviews and Information] blaze2051:
that is a possiblity, alot of my emulators dont work with anything higher than A10. so thats why i prefer to use A10 even if theres a chance to extract iplay40 system.img A10 into my device i would do that

i also went ahead and erase the system_ext from the stock super.img and it resulted in a bootloop.

I just flashed the iplay40 system.img on my device it and goes into a bootloop :(

do you know if lineage 18.1 fixes the folder access to apks that google has restricted?
[Device Reviews and Information] blaze2051:
is it possible to unpack the A11 super.img that contains product/system/system_ext/vendor/ and just repack it with A10 product/vendor/system?
[Device Reviews and Information] NightLord:
Problem is, there is no A10 FW for your device if I understand correctly. AFAIK A10 GSI does also need a compatible vendor (maybe even boot..?) partition to work, which you would find in a stock A10 FW, If there would be one for your device. Vendor (and boot) for A11 just might not be compatible.
[Device Reviews and Information] Garrip:
Does anyone know where to buy the rear camera marked TSC8034-T1020SB-V1 200903 SZ8? Thank
[Device Reviews and Information] blaze2051:
ASOP phh system-roar-arm64-ab-vanilla.img A11 worked. had to delete logical product partiton to make room but it booted with just flashing it to the system partition after it resized it. I guess im SOL when it comes to A10 on this tablet

but to my surprise the GSI A11 or maybe Phh version of A11 as lifted the storage restrictions to the emulators so i can acutally find the files on need from internal storage i havent tried sd storage yet.

heres my link i used to get GSI's

Generic System Image (GSI) list

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com
[Device Reviews and Information] blaze2051:
now if someone could help me get CRB Kitchen v3.0 Beta_14 working on my pc that be awesome because i already tried 4 different betas and tried 2 different windows version and 3 workarounds and i cant get pasted the 2nd step because import distro never takes place
[Device Reviews and Information] AllexBast:
https://xdaforums.com/t/unpacker-kitchen-for-android-uka.4087797/
[Device Reviews and Information] blaze2051:
thanks i was hoping to use the windows version but i might have to use the android version instead
[Device Reviews and Information] davovapo:
Hi guys, today I screwed up, I had a lineageos rom on my iplay40 with magisk and I made the mistake to update from magisk23 to magisk24.1 through the app which brought me to not be able to boot the device again and stays like the pic attached.

I can't go to recovery or fastbood mode either so I don't really know how to move forward, pressing power+up or down just resets the tablet. I have the program called ResearchDownload and the .pac file with the firmware but I think I'd need to enter fastboot to flash the firmware again. Do you think it could be saved?
[Device Reviews and Information] Wajs:
You need to switch device off, to use it with ResearchDownload
[Device Reviews and Information] davovapo:
Thanks, indeed it needs to be that way, I confuse myself with some processes with the few devices but I had but to recover that you need to power of and press down while connecting to the tool with the .pac file loaded.
[Device Reviews and Information] davovapo:
I'm trying to get the android 12 gapps .img to work but I don't know how to unpack the img file and pack it again. Any advice in what to do? Is there any software to make it easy? I've found ImgBurn to turn a folder into a .img I don't know if I'm going well here. If I'm able to edit the system-squeak-arm64-ab-vndklite-gapps.img I'll post it here so other people can just flash it through twrp and get android 12 with gapps. For now I got vanilla a12 but it's quite unusuable for me. Or if somebody else has it I would really appreciate it they uploded it.
[Device Reviews and Information] AllexBast:
i already made firmware in sparse_dat based on latest aosp12 using https://xdaforums.com/t/linux-free-superrs-kitchen-v1-2-1-5-01-08-2022.3597434/ for t1020s , but I can't get adb to work to capture logs.
[Device Reviews and Information] davovapo:
Alright thanks a lot, hope it can advance, for now I'm trying to flash gapps to a12 but I'm getting this error attached with bitgapps, and after trying nikgapps tells me "Looks like storage space is full!". Am I missing something?
[Device Reviews and Information] AllexBast:
The problem is in the size of the gsi image, I advise you to flash firmware containing gapps.
[Device Reviews and Information] davovapo:
Then I would need to get the v402 system-squeak-arm64-ab-vndklite-gapps.img and modify those 3 build.prop no? I'm obviously not experienced with this and I find it a little frustrating how I can't find any software to easily unpack and pack the .img file, those modifications are quite straight forward, I feel I'm so close to have gapps working on a12 on the iplay40 but I'm so far away. Otherwise I'll just go back to a10. Anyway thanks for eveything, I wouldn't have gotten here without reading and rereading all your posts today.

PD:Maybe resizing the gapps img file to make it bigger would make it possible to flash gapps? Or am I making up stuff here?
[Device Reviews and Information] AllexBast:
For gapps to work, you need to change the data that is in the build.prop file in the vendor

https://xdaforums.com/t/alldocube-i...-some-minor-compromises.4212541/post-85974737
[Device Reviews and Information] davovapo:
I used 7zip to extract the img file, added the lines on those 3 build.prop files and used ImgBurn to make and .img again and after flashing and reboot it goes to fastboot. I stayed basically all Saturday dealing with the tablet for now I give up. I'll try to research this further at later points.
[Device Reviews and Information] ar_aja:
I just did the exact same thing, care to elaborate if/how you fixed it?, thanks in advance

Edit:

I managed to fix it by flashing the boot.img via ResearchDownload as suggested by @Wajs

Be sure to flash the boot.img of the twrp installer, if you use the default image from the stock .pac you'll loose twrp access, learnt that the hard way lol
[Device Reviews and Information] ArthurAlex1:
The Android 12L(now renamed 12.1) released! I have flashed, it is optimized for tablet. Very nice! Download v410 and flash to enjoy it!

Releases · phhusson/treble_experimentations

Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.

github.com
[Device Reviews and Information] silviu.butnariu:
Did anyone manage to put TWRP recovery on Alldocube iPlay 40 H/Pro? "Bootloader UNLOCKED"
[Device Reviews and Information] Gordolfo:
Thank you, I was finally able to root my alldocube iplay 40.
[Device Reviews and Information] silviu.butnariu:
I unlocked the bootloader, I wanted to know if someone managed to put Twrp on the tablet ...and how?

thank you!
[Device Reviews and Information] Gordolfo:
You need to flash this files https://drive.google.com/file/d/1lsmYtOESkvI4vz3tLgg9P5CsxaZ3g2fr/view
[Device Reviews and Information] elvin3:
There's a lot of files on the page, which one did you choose for the iplay 40 ?
[Device Reviews and Information] reg66:
Dude, any instructions or at least which files to download? Cheers

EDIT: ALSO, how is the battery life after time for ROM to settle, in comparsion to stock. That's my biggest concern. Cheers
[Device Reviews and Information] coyttl:
Hey guys - quick question -

Trying to unlock the bootloader, and have tried the two fastboot links that were linked earlier, and no matter what I get the:

fastboot: usage: unknown 'flashing' command unlock

message. (Tried 'unlock', 'unlock-bootloader', and 'unlock_critical', all give the same error.)

I got the signature file, generated (a couple different ways, actually, tried in case one way wa bad), but still no go.

Thoughts?
[Device Reviews and Information] albe90262:
I have already unlocked my bootloader now how do i flash the .img file in TWRP - iPlay40(T1020S) to my iPLay40 Pro??? Please provide details steps....
[Device Reviews and Information] kkcheong:
Will unlock and root works with iPlay 40H with Android 11? thanks
[Device Reviews and Information] reg66:
I might be wrong, hopefully someone else can confirm, but I think I recall all of this thread only applies to the non H version. Not possible on yours I don't think. Unless there's another thread been opened for your device...
[Device Reviews and Information] kkcheong:
Ok thanks. But I thought Unlock and root is still possible. Haha.
[Device Reviews and Information] AllexBast:
Bootloader unlock is universal, works on h and pro. Rooting is possible, but I no longer do kernel mods and vbmeta signatures.
[Device Reviews and Information] Neuromancer:
Isn't H the same as non-H, except for the higher version of Android? And "Pro" is the same as H, except for more RAM and storage.
[Device Reviews and Information] kkcheong:
Thanks. Maybe I can try it. Any tutorial?

I need to correct that:

1. H - Android 11

2. Non H - android 10

3. Pro - 256gb

All RAM is 8gb.
[Device Reviews and Information] seledreams:
I have tried the iplay40 utility from @AllexBast and most of it seems to work, but when fastbootd is opened it gets stuck on "waiting for any device" that might be a driver issue but where could I find the fastbootd drivers ? everything else works, adb fastboot (bootloader) etc, just not fastbootd

I own a standard iplay40 (T1020S)

ps : I checked, I did install at least all the drivers required for the stock flashing tool and i installed these https://developer.android.com/studio/run/win-usb
[Device Reviews and Information] AllexBast:
Almost like in this video, but the name of the unknown device will be different.
[Device Reviews and Information] seledreams:
I actually did follow this video, and there is a "Unisoc Phone" unknown device here, however, when I try to install the fastbootd driver in the same way as the video, it just results in "windows did not find drivers for your device" when i select the directory of the fastbootd drivers

this is the identifier of the driver that's missing

USB\VID_1782&PID_4EE0&REV_0414