yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Neuromancer:
Should following steps in this guide work? https://www.makeuseof.com/how-to-install-gsi-android/

Anyway, I already have issues at the beginning. After issuing "adb reboot bootloader", the tablet is stuck at the Alldocube logo page (the static one). I left it there for quite a while (15 minutes or so), nothing happened. If I issued "fastboot flashing unlock" at that point, all I got was "< waiting for any device >".

I could only reset it, and tried again, but it was just the same.

Any ideas what to do?
[Upgrading, Modifying and Unlocking] nmajin:
It looks like the iPlay 50 mini you cannot simply unlock the bootloader....any idea if this procedure would work: https://xdaforums.com/t/how-unlock-unisoc-bootloader.4392557/?
[Upgrading, Modifying and Unlocking] jtrakx:
Your problem basically is the improper installation of Windows 10/11 drivers for Android. The is a separate driver needed when your tab is in bootloader mode and you need to install the correct driver for it (bootloader driver) by using the Windows device manager.

The Alldocube logo you see means the tab is already in bootloader mode. The prompt <waiting for any device> means your Windows cannot communicate with the tab due to driver issues.

The ADB commands work when the tab has booted to Android. However, the fastboot commands work only when the tab is in bootloader or fastboot mode.

Please see the attached drivers you've needed.
[Upgrading, Modifying and Unlocking] Neuromancer:
Thanks for the drivers, they moved me one step forward. But it seems I'm a bit out, as it's been like seven years since I last did something like this. 🤷‍♂️

Now I'm stuck at the next step:

fastboot flashing unlock

FAILED (remote: 'Unrecognized command flashing unlock')

fastboot: error: Command failed

So I try the "classic" line instead:

fastboot oem unlock

FAILED (remote: 'Unable to open fastboot HAL')

fastboot: error: Command failed

What am I doing wrong here? The tablet screen was showing fastbootd menu (in latin script).

Also, in some of the steps you're supposed to flash vbmeta.img and boot.img. Can I use the default ones from the latest official firmware? (lineage-20.0-20230815-UNOFFICIAL-arm64_bgN.img doesn't show any content if I open it in Total Commander)
[Upgrading, Modifying and Unlocking] jtrakx:
The device mentioned in the link you've posted is not the same as the Iplay 50 mini. The chip was not even identical-- UMS512 (T610) vs T606 for Iplay 50 mini.

What determines an unlockable device all boils down to the device manufacturer'. The Alldocube, along with other small Chinese tab manufacturers would not bother spending more resources on software development (and complicated device locking)-- leaving users with only functional generic Android software devoid of bells and whistles.

The Samsung Galaxy Tab A 2022 is using a Unisoc T618 chip (the faster variant of T610) and unlocking the bootloader is permitted by Samsung. Unlocking in fact was very easy but flashing and booting a custom ROM or GSI was not.
[Upgrading, Modifying and Unlocking] jtrakx:
1. First I recommend that you flash the latest stock firmware dated 07312023 (MMDDYYYY).

2. Next, after booting, enable the developer's option, enable OEM unlock, and USB debugging.

3. adb devices (to check connection)

3. adb reboot bootloader

4. In the bootloader,

fastboot flashing unlock

press the volume up key ASAP

fastboot flashing unlock_critical

press the volume up key ASAP

You don't need to flash any patched boot.img and vbmeta.img unless you want to enable rooting.

5. Fastboot reboot fastboot (to enter fastbootD menu)

6. from fastbootD menu boot to recovery

7. from recovery menu select factory reset/wipe data (otherwise the GSI ROM may not boot)

8. from recovery menu select boot to fastbootD again

9. from fastbootD menu,

fastboot erase system_a

fastboot flash system_a gsi_rom.img (gsi_rom.img = GSI ROM of your choice)

fastboot reboot

Youre basically stuck in the process because you are trying to unlock the bootloader in fastbootD.
[Upgrading, Modifying and Unlocking] Isaac™:
It has to be either through the Tools SDK or you can do it manually by going into Recovery
[Upgrading, Modifying and Unlocking] tennyleaz:
Already tried this:

adb reboot fastboot
fastboot reboot fastboot

Then the tablet boots into recovery, I select bootloader useing volume and power keys.

Finally it shows:

< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
[Upgrading, Modifying and Unlocking] Paulpatzer:
Yes, looks like it is in brom mode.

holding down Vol- + Power during connecting to the PC allows the SPD Upgrade Tool to start, but it stops with an nice error:

Seems like I lost some important data on the tablet. :-(
[Upgrading, Modifying and Unlocking] Paulpatzer:
I tried three Versions of the tool. All of them stopped with the same error.

The first version i tested was the one I used for the last update, which worked perfect.
[Upgrading, Modifying and Unlocking] tennyleaz:
Finally I managed to flash PixelExperience slim GSI in fastbootD mode, and magisk patched boot.img. Everything seems to be working!

Weirdly DerpFest and crDroid GSI gives me "dm-verity corrupt" error on boot.
[Upgrading, Modifying and Unlocking] Isaac™:
Flash vbmeta.img
[Upgrading, Modifying and Unlocking] king-totti85:
just want to give some updates regarding GSI status on iplay 50 mini pro, yesterday @ KoTty on our telegram group was able to boot MIUI on the tablet, after that booting almost all GSI was straightforward without problems, also MIUI version was found for the regular 50 pro, @HisokaRyodan promised to write full tutorial, thanks in advance.
[Upgrading, Modifying and Unlocking] yudayuday:
Please, can someone help?

I flashed GSI onto my mini PRO following this guide.

How to Install Custom/GSI ROMs on iPlay 50 Mini/Pro/Max

In this comprehensive guide, we will show you the steps to install various Custom ROMs on your iPlay 50 Mini/Pro/Max.

droidwin.com

There were no errors during the flash. Afterward, when I run 'fastboot -w,' I get the following message:

fastboot -w

wipe task partition not found: userdata

wipe task partition not found: cache

wipe task partition not found: metadata

Finished. Total time: 0.011s

And then it goes into a boot loop. Even performing a factory reset from recovery mode results in a boot loop. What should I do to get it to boot properly?

Thanks.
[Upgrading, Modifying and Unlocking] Isaac™:
I don't have an iplay mini, but you can try:

flash vbmeta in fastboot and fastbootd

When wiping user data, do so through recovery (if available)
[Upgrading, Modifying and Unlocking] yudayuday:
vbmeta was flashed with fastboot.

I'll try it when I get home. Is the command to flash vbmeta with fastbootd the same as fastboot?

Also, other people in this thread don't seem to be doing that. What's the difference?

---------------------------

I tried it.

Flashing vbmeta with fastbootd returned an error.

Unlocking the bootloader and flashing the ROM seem to work fine on the command line.

SP FLASH TOOL also works without any issues, and I can restore it to its original state.

Do you have any ideas about the cause? Is it the cable, PC, or something else?
[Upgrading, Modifying and Unlocking] Isaac™:
What is the gsi? are you using the correct architecture? I believe it is arm64ab, if in doubt use treble information

I had a device that basically wouldn't boot into any gsi, so I did some research and ended up downgrading to the first version of the ROM and was able to install gsi

remembering that it is not possible to initialize the gsi below the android api used.

for example, the default Android of iplay 50 mini pro is Android 13 (API 33), you can only test gsi based on Android 13 or later
[Upgrading, Modifying and Unlocking] Isaac™:
and remember to factory wipe through recovery
[Upgrading, Modifying and Unlocking] jkd:
A way for iplay 50 (not pro) ?
[Upgrading, Modifying and Unlocking] yudayuday:
GSI is using A13.

Cherish, crDroid, DerpFest, LineageOS... all had the same results.

I tried various methods, including before flashing, after flashing, using commands, from recovery, and factory resets, but it didn't work.

factory reset after flashing the GSI, but at this point, I'm already encountering an error.

~~~~~~~~~~~~~~

Sending sparse 'system_a' 17/17 (138298 KB) OKAY [ 3.629s]

Writing 'system_a' OKAY [ 0.404s]

Finished. Total time: 127.503s

C:\Users\ahold\Desktop\ipay50\platform-tools_r34.0.5-windows\platform-tools>fastboot -w

wipe task partition not found: userdata

wipe task partition not found: cache

wipe task partition not found: metadata

Finished. Total time: 0.012s

Is obtaining root access required?
[Upgrading, Modifying and Unlocking] Isaac™:
are you installing fastbootd?
[Upgrading, Modifying and Unlocking] Isaac™:
If none of this works it's because of the kernel, if you happen to get the iplay 50 mini pro kernel and a dev, it might even be possible to create a rom
[Upgrading, Modifying and Unlocking] Isaac™:
check boot slot

fastboot getvar all

look for something like: (bootloader) current-slot

if it is (a) flash on system_a and if it is on (B) flash on system_b
[Upgrading, Modifying and Unlocking] yudayuday:
I'm doing what should be done in fastbootd.

I don't know about the kernel.

I have no knowledge about it.

This is all from 'fastboot getvar all.' Can you confirm?

By the way, these are the results in a bootloop state.

C:\Users\ahold\Desktop\ipay50\platform-tools_r34.0.5-windows\platform-tools>fastboot getvar all

(bootloader) off-mode-charge: 1

(bootloader) slot-retry-count:b: 7

(bootloader) slot-retry-count:a: 7

(bootloader) slot-successful:b: no

(bootloader) slot-successful:a: yes

(bootloader) slot-unbootable:b: no

(bootloader) slot-unbootable:a: no

(bootloader) slot-count: 2

(bootloader) current-slot: a

(bootloader) unlocked: yes

(bootloader) secure: no

(bootloader) partition-type:userdata: f2fs

(bootloader) partition-size:userdata: 38fd7f8000

(bootloader) has-slot:userdata: no

(bootloader) partition-type:vbmeta_b: raw

(bootloader) partition-type:vbmeta_a: raw

(bootloader) partition-size:vbmeta_b: 800000

(bootloader) partition-size:vbmeta_a: 800000

(bootloader) has-slot:vbmeta: yes

(bootloader) partition-type:super: raw

(bootloader) partition-size:super: 240000000

(bootloader) has-slot:super: no

(bootloader) partition-type:md1img_b: raw

(bootloader) partition-type:md1img_a: raw

(bootloader) partition-size:md1img_b: c800000

(bootloader) partition-size:md1img_a: c800000

(bootloader) has-slot:md1img: yes

(bootloader) partition-type:dtbo_b: raw

(bootloader) partition-type:dtbo_a: raw

(bootloader) partition-size:dtbo_b: 800000

(bootloader) partition-size:dtbo_a: 800000

(bootloader) has-slot:dtbo: yes

(bootloader) partition-type:vendor_boot_b: raw

(bootloader) partition-type:vendor_boot_a: raw

(bootloader) partition-size:vendor_boot_b: 4000000

(bootloader) partition-size:vendor_boot_a: 4000000

(bootloader) has-slot:vendor_boot: yes

(bootloader) partition-type:boot_b: raw

(bootloader) partition-type:boot_a: raw

(bootloader) partition-size:boot_b: 4000000

(bootloader) partition-size:boot_a: 4000000

(bootloader) has-slot:boot: yes

(bootloader) partition-type:lk_b: raw

(bootloader) partition-type:lk_a: raw

(bootloader) partition-size:lk_b: 400000

(bootloader) partition-size:lk_a: 400000

(bootloader) has-slot:lk: yes

(bootloader) version-baseband: MOLY.LR13.R2.MP.V79.5

(bootloader) is-userspace: no

(bootloader) serialno: 0123456789ABCDEF

(bootloader) product: tb8781p1_64

(bootloader) max-download-size: 0x4000000

(bootloader) version-bootloader: tb8781p1_64_e4868a45481_202309270221

(bootloader) version: 0.5

all: Done!!

Finished. Total time: 0.039s
[Upgrading, Modifying and Unlocking] filus:
Hi everyone, I also have an iplay 50 mini pro and I have the same problem, I remain in bootloop after the flash even if I delete the factory data. Doesn't it depend on the bootloader version since we have the latest version? Honestly I also tried to flash the previous stock version from August and I had the same result. Isn't it necessary to have an even older version? Also after unlocking the bootloader the secure boot remains on yes, is this normal? Or does it have to appear to be able to flash another GSI? Thanks to anyone who wants to respond. In another dedicated tread on xda someone says to flash a Chinese MIUI first, but in the same tread they also say that you can flash lineage OS 20 directly, I would be curious to know how they managed not to remain in bootloop. https://xdaforums.com/t/iplay-50-mini-pro-miui-rom-gsi-install.4636967/
[Upgrading, Modifying and Unlocking] Isaac™:
Well apparently you did the installation process correctly, I think the problem is that the kernel is not accepting it, I don't have much knowledge about this, you should go to some Telegram forums about gsi, I recommend phh treble
[Upgrading, Modifying and Unlocking] filus:
I found a telegram channel dedicated to iplay 50 mini pro where they flashed gsi without errors, if you're interested this is the link https://t.me/IP50MP. I still haven't tried the guides they wrote, let me know then if they worked.
[Upgrading, Modifying and Unlocking] tennyleaz:
Yes.

To unlock the bootloader, you need CVE-2022-38694 method.

To extract boot.img from stock *pac firmware you need Research Download Tool < v20.
[Upgrading, Modifying and Unlocking] king-totti85:
To flash lineage don't disable verification or flash vbmeta, to boot other gsi flash miui first
[Upgrading, Modifying and Unlocking] filus:
I had the same problem as you which I solved like this:

ALLDOCUBE IPLAY 50 MINI PRO BOOTLOADER UNLOCK AND GSI INSTALLATION GUIDE

Unlock Bootloader Guide

-Flash original Stock Rom

- Insert the original Boot.img of the stock rom you installed to have in the Rom Folder, or the one patched with Magisk , in the Platform Tools folder

-Enable The developer menu

-Enable OEM unlocking and USB debugging

Unlock the bootboader with these commands:

adb devices (to check connection)

adb reboot bootloader

fastboot flashing unlock

On your tablet, immediately press the volume down to accept

fastboot flashing unlock_critical

On your tablet, immediately press the volume down to accept

Now type this:

fastboot flash boot boot.img (optional - magisk-patched-boot.img)

Proceed now to install Lineage Os 20 August version (the newer one causes the Bootloop) https://sourceforge.net/projects/an...0-td/History/lineage-20.0-20230815-UNOFFICIAL -arm64_bgN.img.xz/download

Extract the img and copy it into Platform Tools, Rename it to gsi_rom.img

Run these commands from CMD:

adb reboot bootloader

Fastboot reboot fastboot (fastbootD)

from fastbootD menu on the tablet boot to recovery

Do a factory reset/wipe data

inside recovery select enter fastboot

Now type these commands:

fastboot erase system_a

fastboot flash system_a gsi_rom.img (gsi_rom.img = GSI ROM of your choice)

fastboot reboot

GOOD LUCK
[Upgrading, Modifying and Unlocking] Bwangster12:
You ever figure out how to unbrick this?
[Upgrading, Modifying and Unlocking] marko033:
Hi,

I followed the instructions from @jtrakx

After the last fastboot reboot step, the tablet restarted.

However now it's stuck at the boot screen where it says

Orange State

OS Not Being Verified Or Custom OS. Dismiss after 5 Seconds.

It restarts over and over.

Could someone advise me on what to do now?
[Upgrading, Modifying and Unlocking] Isaac™:
flash vbmeta file

in fastboot: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[Upgrading, Modifying and Unlocking] marko033:
I can't get into fastboot.

The tablet keeps restarting.

I tried using Volume Up, I got into Recovery and I tried uploading the stock rom via SP Flash Tool, but it doesn't work.
[Upgrading, Modifying and Unlocking] Isaac™:
Leave the SP Flash in preparation and when the device restarts (do not let the screen light up) insert the USB cable
[Upgrading, Modifying and Unlocking] marko033:
Ok, using Volume UP and I chose Fastboot.

Nothing happened, I thought it was frozen but I used the command you wrote and it helped. The tablet booted without problems.

Thanks for help.
[Upgrading, Modifying and Unlocking] oaklandz:
Hi what's the latest for unlocking the bootloader? Is this reliable? https://droidwin.com/how-to-unlock-bootloader-on-iplay-50-mini-pro-max/
[Upgrading, Modifying and Unlocking] Paulpatzer:
No, it's still bricked.

And, to be honest, I didn't find the time to really work on it.

I've some ideas about using the flash tool for a complete reflash with the data from another device,

but therefor I have to acquire some more knowledge about the SPRD tools.
[Upgrading, Modifying and Unlocking] Bwangster12:
I'm not looking to try and unlock my iPlay 50 anytime soon, but it really confuses me why this happened to you if you used the method as instructed. Did you use the iPlay 50 mini file by mistake?
[Upgrading, Modifying and Unlocking] jkd:
please for iplay 50 (T1030) how can i unlock bootloader and install GSI.

is there links for tutorial, GSI ROM ?
[Upgrading, Modifying and Unlocking] antouaa:
New update for Iplay50pro does anyone test it? I will put it when I will found time because it's not OTA again. I hope (but I don't expect) ghost touch issues disappear and will have even android 13.

Alldocube iPlay50Pro(T1030M) firmware download

www.alldocube.com
[Upgrading, Modifying and Unlocking] Alfarroba:
Yes it is Android 13. I tried to use the flash tool the usual way and I ended up in a boot loop. Maybe because I didn't uncheck the preloader option? I manage to solve the problem by choosing "firmware upgrade" instead of "download" in the flash tool. But I loose all my user data. But is working again:)
[Upgrading, Modifying and Unlocking] antouaa:
So I must do a backup before.
[Upgrading, Modifying and Unlocking] derd3:
Unlock worked fine. Also had to change to my Surface, it didn't work on a Parallels Ubuntu/Windows 7/WIndows 11 VM on macOS

I now want to flash LineageOS but I don't know how to flash the vbmeta-sign.img :(

Did you have to create your own signed vbmeta.img? I extracted the vbmeta-sign.img from the original firmware but I cant just fastboot flash vbmeta vbmeta-sign.img...
[Upgrading, Modifying and Unlocking] fattiusmaximus:
Hey guys I have a Iplay50 pro max (only difference between the pro and the pro max is 256gb nand instead of 128

download the stock firmware from alldocubes site Alldocube Stock firmware and use sp flash tool spflashtool here is a guide on how to use it, sp flash tool tutorialI just reflashed mine from a12 to a13 your supposed to be using the sp flash tool to flash the device, thats why you keep boot looping, I will be looking at creating a custom rom for it in the next few days and create a proper scatter file I just got this device yesterday if you need root just use the magisk app and pull the boot.img out of the firmware file you flash to install it most MTK devices its best to use sp flash tool
[Upgrading, Modifying and Unlocking] Isaac™:
Why can't you write vbmeta? try fastboot --disable-verity --disable-verification flash vbmeta vbmeta-sign
[Upgrading, Modifying and Unlocking] derd3:
Doesn't work. It stops at "Writing... " and doesnt do anymore.

Already tried the following - always the same:

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

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

fastboot --disable-verification flash vbmeta vbmeta-sign

fastboot --disable-verification flash vbmeta_a vbmeta-sign

Anyway, I flashed lineageOS successfully and now I'm quite happy with the tablet. It's the non-pro iPlay 50 Mini. It could be a little bit smoother but in regards to the stock firmware it's already a step in the right direction. I think for people who are going to use it as a daily driver I would recommend the Pro Version.
[Upgrading, Modifying and Unlocking] tennyleaz:
You have the CVE-2022-38694 method to unlock T1030. Then flash GSI images as other devices.

Releases · TomKing062/CVE-2022-38694_unlock_bootloader

This is a one-time signature verification bypass. For persistent signature verification bypass, check https://github.com/TomKing062/CVE-2022-38691_38692 - TomKing062/CVE-2022-38694_unlock_bootloader

github.com
[Upgrading, Modifying and Unlocking] df_1975:
Just a heads-up:

The file `CheckSum_Generate_v6.exe` in the Stock ROM `iPlay50miniPro(T811M)_EN_20231102.rar` downloaded from `https://www.alldocube.com/en/firmware/alldocube-iplay-50-mini-prot811m-firmware-download/` contains the Win32/Sality trojan / virus.

`https://www.virustotal.com/gui/file...b5a4dc6c18d5c3b2db676deaa6e05bf3090?nocache=1`

The SHA1 of the RAR archive is

FD2B48A9D6B9B5B1CDB39DC134B95131E40B4A9C iPlay50miniPro(T811M)_EN_20231102.rar

BA515DC430C8634DB4900A72E99D76135145D154 iPlay50miniPro(T811M)_EN_20231102.rar:Zone.Identifier:$DATA

Actually the hash appears to be changing from download to download, this time it was

7DE47F5B91BA53BA050DD13E03C5E12175515F2D iPlay50miniPro(T811M)_EN_20231102.rar

BA515DC430C8634DB4900A72E99D76135145D154 iPlay50miniPro(T811M)_EN_20231102.rar:Zone.Identifier:$DATA

but the threat still persists.
[Upgrading, Modifying and Unlocking] Jerky_san:
Wanted to say I got a iplay 50 pro max and installed the newest update(android 13). It seems to function well and it has the same background image as the iplay50mini pro on the amazon listing now... Now to work up the courage to actually use the device since I still question how "safe" it is. Debating if I should just flash a gsi on it or something.
[Upgrading, Modifying and Unlocking] Jerky_san:
I tried flashing lineageOS GSI and it would boot say it was getting ready and reboot.. so thus far I think I'm staying away since I was able to recover via the SP tool. I don't know if I missed something but it was strange.. like it half way started.

Edit:

Because I'm incredibly stubborn I tried again. This time doing the method from post 206. It worked and everything appears functional this time around. So if your doing this.. do post 206 method for a play 50 Pro/pro max
[Upgrading, Modifying and Unlocking] cc2918:
how is gsi compare to stock rom?
[Upgrading, Modifying and Unlocking] jkd:
It is possible to install GSI ROM on iplay 50 (T1030) ?
[Upgrading, Modifying and Unlocking] Kiciuk:
There is no such file in 50 Pro firmware, tho i searched on the net and there is site:

CheckSum Generate v6.2316.00 for Windows - Official SPMDT Tool

Download CheckSum Generate v6.2316.00 to compute checksum values for every file in the firmware package.

spmdttool.com

while virustotal isn't ultra happy with 0 detections its nowhere near variant you mentioned and binary size is much smaller.

Sality from what i remember was virus infecting executables so keep extra caution when handling this crap
[Upgrading, Modifying and Unlocking] Kiciuk:
Still if there is any crap in it, it can hide inside "vendor" and "vendor_dlkm", i think one day i would strive to port mainline linux for it but i don't have much experience outside of qualcomm socs
[Upgrading, Modifying and Unlocking] df_1975:
Why don't you download the _EN_20231102 and check for yourself, which was the official download back then before they released the _EN_20231201. The exe in the 1102 yields 62 matches for virus out of 72 AV software scans, as you can see in the link.

_EN_20231201 no longer includes the exe.
[Upgrading, Modifying and Unlocking] Jerky_san:
I like it but there are some things that are broken like it can't do OTA updates which kind of sucks. Also when I tried derp 14 the launcher was broken but it would seem they started including a different launcher now.
[Upgrading, Modifying and Unlocking] marko033:
Hi, as I wrote before I followed the instructions from @jtrakx with @Isaac™ help everything works.

I have lineage-20.0-20230814-UNOFFICIAL-gsi_arm64_vN.img but now I found out that 3.5mm headphone jack does not work. Does anyone have a similar problem?
[Upgrading, Modifying and Unlocking] jtrakx:
In the settings menu under PHH Treble Setting -- Misc features you need to enable "use alternate way to detect headset" and then restart the tablet.

I think I've already mentioned this in my previous post.