yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] jtrakx:
I'm really sorry I do not own an Iplay 50 mini. I was really tempted to buy one for the price of $100. But the Iplay 50 pro was offered to me for $150. The pro has a big screen, faster and efficient chip (Helio G99 is at least 2.5 faster than T606), using a 128GB UFS 2.1 storage (faster than EMMC 5.1 storage used in mini and other cheap tabs), 8GB of physical RAM, and with free folio case. Best bang for the buck.

BTW, I already have a Samsung Galaxy Tab A7 lite with 8.7 inch screen. Bought it last year for $150. I have no regret since Samsung has been continuously updating it (OneUI 5.1 android 13 July 2023 issue).
[Upgrading, Modifying and Unlocking] siewasome:
hey guys, my iplay 50 pro is stuck on ALLDOCUBE logo screen after adb reboot bootloader command, It can be reset and booted normally by pressing power off button but how do I access bootloader?
[Upgrading, Modifying and Unlocking] siewasome:
Will flashing iplay 50 mini stock rom to iplay 50 pro work or brick the tablet? What I want is to have L1 widevine on my 50pro
[Upgrading, Modifying and Unlocking] jtrakx:
Please read my post #17
[Upgrading, Modifying and Unlocking] jtrakx:
It's really impossible to flash iplay 50 mini stock rom into iplay 50 pro. To start with, the format of the 50 mini ROM is entirely different (PAC compression). Not to mention the numerous hardware differences between the two tabs.
[Upgrading, Modifying and Unlocking] antouaa:
If Alldocube don't take the permission to have L1 in the 50 pro , you will never have L1 for this device!
[Upgrading, Modifying and Unlocking] antouaa:
I just revive mine. It's not so good as I thought in 5 minutes that I had it in my hands. Iplay 30 pro that I was bought for my dad has better screen and the speaker are louder and cleaner. I want yours opinion is it better just upgrade to the latest firmware (manual since OTA don't work) or try to experiment with GSI roms?
[Upgrading, Modifying and Unlocking] Neuromancer:
For now, I've downloaded the drivers and (seems the newest) flash tool from https://spflashtools.com/windows/sp-flash-tool-v6-2228 and https://mtkdriver.com/mtk-driver-v5-2307

The tablet still wasn't detected by the flash tool. The installation of drivers did complain in the beginning about uninstalling previous drivers (not sure which...).

I'll give it another shot on the weekend when I have more time.

P.S.: Seems like they're going to start selling iPlay 50 Mini Pro. :ROFLMAO:
[Upgrading, Modifying and Unlocking] HisokaRyodan:
I tried a bunch of things to try and unlock the bootloader but nothing seems to work. I can get the oemunlock keys however as soon as I try to write the signature.bin it fails. If you figure it out please let me know. Someone asked on (mod edit; forum link removed) forums*, but there still is yet to be an answer.

*mod edit; forum link removed (Rule 11 -- "Encouraging members to participate in forum activities on other phone related sites is prohibited." "a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.") --simplepinoi177 Forum Specific Moderator
[Upgrading, Modifying and Unlocking] nmajin:
Alldocube responded with this:

“The cpu of iplay50 mini is Spreadtrum T606, you can refer to other Spreadtrum T606 or T618 machines to unlock BL”

Obviously not helpful, I responded back letting them know I tried this already (assuming they are taking about the “signidentifier_unlockbootloader.sh X rsa4096_vbmeta.pem signature.bin”) and it must be the private key and asked for them to provide it or assistance to help me unlock, haven’t heard back.
[Upgrading, Modifying and Unlocking] HisokaRyodan:
Damn well hopefully we can get a fix. Keep us posted! I LOVE the tablet but not having true floating apps is a huge issue for me which requires root
[Upgrading, Modifying and Unlocking] jtrakx:
Q: is it better just upgrade to the latest firmware (manual since OTA don't work) or try to experiment with GSI roms?

It depends on the purpose of your Iplay 50 Pro. I bought mine to experiment with it. ---flash different GSIs and try all rooting methods (magisk or KernelSU). But if I were you, I would upgrade to the latest firmware and then flash the best GSIs available (Derpfest, PixelOS, Pixel Experience+ etc.) The Iplay 50 Pro was loaded with a very simple generic A12 anyway, so you will not lose any features.

My Iplay 50 Pro is significantly better now with tons of features and customization options than the stock A12.
[Upgrading, Modifying and Unlocking] nmajin:
Will do. Yes I think for ~$100 this tablet is great. Speaker sucks but I’m trying to make this a wall tablet and need the root for limiting a battery charge. Also want to use Pixel Experience GSI rom on it.
[Upgrading, Modifying and Unlocking] jtrakx:
About the Iplay Mini Pro, yeah I read about it yesterday, and damn its better than the Iplay 50 Pro. Same chip Helio G99 but with 256GB UFS2.2 storage, haptic motors, and a brighter display of 350+nits. Also, they have loaded it with Android 13.

Maybe there is a way we can easily port the 50 mini pro firmware to 50 pro to get Widevine L1.
[Upgrading, Modifying and Unlocking] antouaa:
Which Rom are you using now and what's rooting method are you think it's better?
[Upgrading, Modifying and Unlocking] jtrakx:
I am using the Derpfest 13. There are tons of features and customization options.

I also tried the latest LineageOS TD for a while. I really like it but it failed the CTS profile check even with stock boot.img and VBMETA. I will be trying the latest PixelOS and Pixel Experience +.

Honestly, the best root solution for me is the KernelSU. However, it is still in its early stage of development. I have yet try try this.

Magisk is a lot more popular. But the time will come it will not be effective in hiding root. This tab is very easy to root with Magisk..
[Upgrading, Modifying and Unlocking] antouaa:
I have long time to root and I just learn from you the kernelSU method! Thank you very much for your answer!
[Upgrading, Modifying and Unlocking] oaklandz:
I've just purchased the iPlay 50 Mini. Have you rooted yours? Problem free?

I'm looking for a clearly written step-by-step root guide preferably with links for needed files. I like Magisk. (Keep in mind - if someone doesn't do this all the time, it's often hard to decipher instructions that use short 'code' for steps.)
[Upgrading, Modifying and Unlocking] oaklandz:
@jtrakx do you know about this?​
[Upgrading, Modifying and Unlocking] HisokaRyodan:
The mini cannot be rooted at this point in time. I would assume though that the Mini Pro can be using the same method discussed her since it has the same chipset as the iplay50 Pro. I will let you know once my mini pro arrives.
[Upgrading, Modifying and Unlocking] jtrakx:
Hi oaklandz,

Sorry, I did not own an Iplay 50 mini. Based on what I read here, owners are having a problem unlocking the bootloader. That's not the case with Iplay 50 Pro which I unlocked very easily using fastboot commands (assuming the OEM unlock option was enabled in developers option):

fastboot flashing unlock (then press volume up button in the tab)

fastboot flashing unlock_critical (then press volume up button in the tab)

The first time I tired this it didn't work because I did not press the volume up button.

Rooting the Iplay 50 Pro is very easy as well. I extracted the boot.img and vbmeta.img from the stock firmware, repack the 2 files in zip format, and then patched the zip file using magisk.

The patched zip was extracted (boot.img and vbmeta.img) and flashed into the tablet. I previously posted my steps here. But in my recent test, flashing the vbmeta was not even required. The tab doesn't really stop you from rooting.

But the easiest and the best way to root is using the KernelSU. Just download the compatible boot.img from the KernelSU download page and flash it. KernelSU rooting allows me to pass safetynet and CTS profile checks without doing anything. That's not the case with magisk.
[Upgrading, Modifying and Unlocking] oaklandz:
Hi jtrakx - thanks! That's great information (and easy to understand) and there's always something new out there. I have never heard about KernelSU so I'll read up on it. I hope there is an application for it for the mini.

Does anyone else have info like this? Any lead to get this rooted would be great. I'm willing to risk the problems.
[Upgrading, Modifying and Unlocking] HisokaRyodan:
Edit: never mind I see you posted your steps for root that was my fault. Just want to know does that root carry over to the GSI ROM when you flash it? As in

1. Download stock firmware

2. Patch boot.img and flash it

3. Flash gsi

4. Reboot to gsi with magisk?

The only reason I ask is I have a teclast tablet that can’t root via magisk so when I tried those steps it bootlooped so just trying to get a handle on the steps
[Upgrading, Modifying and Unlocking] jtrakx:
Yes, the root should carry over to the new GSI ROM you've flashed in.

The patched boot.img is flashed in the Boot partition while the GSI ROM is flashed in the System partition. So the order of flashing should not really matter. But when you flash the stock firmware, you need to root again.

The reason why it is normally recommended to update to the latest stock firmware beforehand is that it could contain updates or bug fixes to the vendor partition binaries and kernels (comparable to "device driver" and "BIOS firmware" updates for the Windows PC). The GSI ROMs cannot and will not provide you with these updates.

There are devices that require you to disable boot verification in order for root or booting GSIs to work.

Some boot loops are not even related to root at all. In my experience, there are few GSIs that cannot simply work in my device causing bootloops even without rooting.

I suggest you try the KernelSU way.
[Upgrading, Modifying and Unlocking] HisokaRyodan:
Hmm I updated to the 8_14 firmware manually cause i couldnt get SPFlashTool v6 to work. Version 5 of the tool says its incorrect scatter file.. Tried both 6 and 5 on linux too with no change.

I patched the boot, and flashed it using "fastboot flash boot magisk_patched.img" while in fastbootD and now im boot looped.

How did you get SPFlashTool to work to flasht he original firmware?
[Upgrading, Modifying and Unlocking] jtrakx:
I am using the SPflashTool ver 6.2316 I've downloaded from the Alldocube website. You need to run the executable as an administrator, choose the download XML file (flash.XML), and then press the download button. The SPfash should work when the tab is off or in recovery.

This is my tip: Do not flash the boot.img in fastbootD mode. It will not work. Always start in bootloader mode when flashing boot image and vbmeta.
[Upgrading, Modifying and Unlocking] HisokaRyodan:
For whatever reason, my main computer and my linux box both could not load the 8-14 firmware, or the 7-30, but using my laptop, I was able to use the same SPFlashTool version and get the 7-30 to load... Weird.

But I was able to load the 7-30 firmware, then simply patched the boot.img with magisk, booted to fastboot (NOT fastbootD... thank you so much for this tip!) and flashed using the fastboot command.

after that, went into fastbootd:

fastboot delete-logical-partition product_a

fastboot flash system_a derpfest.img

reboot to recovery and wipe data/factory reset and am now setting up the GSI rom! Reinstalled magisk via apk, rebooted to finish setup and am now up and running perfectly!

Thank you so much for all your help! Do you have a donate link or something so i can buy you a beer?

Just for all in this, I have bought a Mini Pro and will go through all of this again once I get it and report back my findings if someone doesnt beat me to it
[Upgrading, Modifying and Unlocking] jtrakx:
Yeah! Nice work. No need to donate or buy me a beer. We help each other here on XDA forums for free.

My suggestions to you:

Phh Treble Settings >>Misc features>>enable "Use alternative way to detect headsets" -- to enable the 3.5mm headphone jack.

Display>>Display size and text>>adjust to make the display size a bit smaller --- this will make the device a tablet instead of a big phone. Alternatively, adjust the smallest width to at least 720 (I use 750). If the icons become too small to your liking, make the icons bigger.

I will be trying PixelOS and Evolution X to see which one is better. link https://magiskzip.com/gsi-list-phhusson/

I read yesterday somewhere that there is a Netflix spoofing built-in on those GSIs to improve Widevine to L1?

Enjoy your A13 tablet. I know you will be moving to A14 soon.
[Upgrading, Modifying and Unlocking] Neuromancer:
Could it be that the mediatek drivers are clashing with fastboot drivers? Apparently the tablet is not detected correctly, because SP flash tool doesn't see it, and if I check the device manager, there's a triangle under Human Interface Device on the last entry for USB Input Device.
[Upgrading, Modifying and Unlocking] jtrakx:
Yes, it could be.

If I remember correctly, I installed the MediaTek drivers first followed by the manual installation of ADB and fastboot drivers. But I've never encountered any problems with fastboot commands and using the SP flash tool. I flashed 7 different GSIs already and reverted to stock firmware with SP flash tool three times. I am playing with my 8th GSIs right now and I think I can put it back in stock firmware again with SP flash tool.
[Upgrading, Modifying and Unlocking] Neuromancer:
Hm, I uninstalled all previous drivers, rebooted the computer, and installed again from MTK-Driver-v5.2307.zip. After the reboot, it was exactly the same. So there must be something else. The FAQ on Alldocube site points to other drivers (Driver_Auto_Installer_v1.1236.00.zip and MediaTek_USB_VCOM_drivers.zip, but these are dated 2011-2013), so this gets confusing.

Just to be certain - when I connect the tablet to the PC (SP flash tool running, tablet OFF), a full-screen empty battery icon is displayed at first, which is then replaced with a full-screen battery icon showing the percentage of charge. The USB connect/disconnect sounds (on the PC) ring twice (upon connecting, and before the battery icon is changed).

Is this the correct state?

But the SP flash tool doesn't change anything on its interface.
[Upgrading, Modifying and Unlocking] jtrakx:
I only installed the MTK-Driver-v5.2307 and the ADB/fastboot drivers (which I posted here on this forum). I am not aware of other drivers you've mentioned.

The only time the SP flash tool will detect and check your tablet is during the actual flashing process. That means you need to click that Download button in the interface and give the tool a few seconds to work. Once the process of flashing has started, you will begin to see the details of your tab. The bottom text that reads EMMC will become UFS (the correct storage type of Iplay 50 Pro).

I managed to successfully flash the stock firmware twice in recovery mode. Only once when the tab is off (with battery animation).

I recommend you check first your fastboot drivers if installed correctly. If everything is ok, then flash the tab in recovery mode.
[Upgrading, Modifying and Unlocking] Neuromancer:
Well, I kinda gave up on SP flash tool. Again uninstalled all drivers (including anything that remotely seemed like android in Device Manager), rebooted, installed MTK driver, rebooted, but flash tool doesn't register anything. ADB works.

So I tried the with original intent (preparing for custom ROM), which this time went further:

c:\bin\adb>fastboot flashing unlock
(bootloader) Start unlock flow

OKAY [ 3.268s]
Finished. Total time: 3.275s

c:\bin\adb>fastboot flashing unlock_critical
(bootloader) Start unlock flow

OKAY [ 1.034s]
Finished. Total time: 1.034s

c:\bin\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >

...but got stuck at the last reboot at "waiting for any device". The FastbootD was shown on the screen at that time. Even if I try all the necessary steps to get there manually after a reboot or two, the steps at #9 (your post #20) all have "waiting for any device" on the computer.

The device however is unlocked, and it was reset to factory settings.

EDIT: I've noticed "iPlay 50 Pro" under Other Devices in Device Manager. I don't remember seeing this entry before.
[Upgrading, Modifying and Unlocking] Neuromancer:
Never mind... just had to add missing driver as well.

So:

:\bin\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 105.411s

c:\bin\adb>fastboot erase system_a
Erasing 'system_a' OKAY [ 0.042s]
Finished. Total time: 0.052s

c:\bin\adb>fastboot flash system_a e:\lineage-20.0-20230815-UNOFFICIAL-arm64_bgN.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.003s]
error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 381898724 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 113467364 is not a multiple of the block size 4096
Sending sparse 'system_a' 1/4 (262140 KB) error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
OKAY [ 6.366s]
Writing 'system_a' FAILED (Status read failed (Too many links))
fastboot: error: Command failed
[Upgrading, Modifying and Unlocking] antouaa:
Neuromancer did you try to put the ROM folder in the local disk from PC? Because I had the folder in external hard drive and that's why I couldn't update it. Now my update is complete. I will play a little rough the latest official firmware and after I will try GSI roms.
[Upgrading, Modifying and Unlocking] Neuromancer:
Yes, it's a local SSD drive. Also tried with derpfest, but the result is the same. Maybe I have to do something with the tablet/partitions first?

c:\bin\adb>fastboot flash system d:\Downloads\DerpFest-test-13_arm64-bgN.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.006s]
error: write_sparse_skip_chunk: don't care size 1007302308 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 738870948 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 470439588 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 202008228 is not a multiple of the block size 4096
Sending sparse 'system_a' 1/5 (262140 KB) error: write_sparse_skip_chunk: don't care size 1007302308 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1007302308 is not a multiple of the block size 4096
OKAY [ 6.196s]
Writing 'system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
[Upgrading, Modifying and Unlocking] Neuromancer:
I did, in the meantime, managed to get SP flash tool to work, and flashed the August 14 (current latest) version on it.
[Upgrading, Modifying and Unlocking] oaklandz:
Does anyone want to help me try to root the IPLAY 50 MINI? I am willing to take the risk if you have something to try. Is there someone working on this already?
[Upgrading, Modifying and Unlocking] cobraxracing:
first a big thank for your time from not a expert guy!

I follow step by step your advice but I stuck at a bootloop. I'm trying since 3 days to find a solution (google) but no way 😩. I don't understand why SP Flash Tool can't recognize the tablet to flash and unbrick it with a stock rom. do you know if I can flash another recovery with fastboot to replace the stock one?

sorry for my englisch!!!
[Upgrading, Modifying and Unlocking] jtrakx:
Here is my quick guide for you to recover from bootloop on this tab:

01. Press the Volume Up key continuously until you can see a selection prompt on your screen.

02. The will be three choices: Fastboot, Bootloader, and Recovery.

03. My tip: use the Volume Down key to select. (The Volume Up key is too close to the power button and you don't want to inadvertently press that. Not yet.)

04. Select Recovery and press Power Key. You need to wait for a few seconds.

05. Once you see a "dead android" and "No command" on your screen, run the SP Flash Tool and flash the stock firmware.

06. Another tip: I think the reason why the SP Flash tool fails to work for most of you here on this thread is the timing.

The proper timing -- Disconnect the tablet from your PC

Run the SP Flash tool and select the correct Flash.XML file.

Press the Download button

Now connect the tablet to your PC.
[Upgrading, Modifying and Unlocking] jtrakx:
Okay, first thing first. The prompt < waiting for any device > means you have driver issues. If you still experiencing this, you can find the solution here on this thread.

Next, you need to ensure that the bootloader is properly unlocked. If you can see a small text in your tab every time you reboot that says something like: "Orange flag -- OS not being verified or Custom ROM" then that means it's already unlocked.

Next, Place all your GSIs in the same folder where your platform tools are located. Just rename the GSI to something simple like LOS20.img instead of using very long filenames like lineage-20.0-20230815-UNOFFICIAL-arm_bgN.img

Then, follow the steps mentioned before.
[Upgrading, Modifying and Unlocking] cobraxracing:
Hey Jtrakx,

One more time a BIG THANKS from me!!!!

you did save my life and you made my son very happy. you right with the timing is very importan. I tried many times till I got the right timing. 👍🏾👍🏾

I will try tomorrow to flash the Derpfest 13 rom.

Please pm me a message with your PayPal email address cuse I would like to spend you a Coffee for your quick HELP 🍵 !!!!
[Upgrading, Modifying and Unlocking] Neuromancer:
Yes, it's unlocked, status orange etc.

I copied the img into the adb folder and renamed it, but it's the same. Here's the log of the last issued commands (I tried both system_a and system):

c:\bin\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 18.226s

c:\bin\adb>fastboot erase system_a
Erasing 'system_a' OKAY [ 0.033s]
Finished. Total time: 0.051s

c:\bin\adb>fastboot flash system_a los.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.003s]
error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 381898724 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 113467364 is not a multiple of the block size 4096
Sending sparse 'system_a' 1/4 (262140 KB) error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
OKAY [ 6.440s]
Writing 'system_a' FAILED (Status read failed (Too many links))
fastboot: error: Command failed

c:\bin\adb>fastboot flash system los.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.004s]
error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 381898724 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 113467364 is not a multiple of the block size 4096
Sending sparse 'system_a' 1/4 (262140 KB) error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 650330084 is not a multiple of the block size 4096
OKAY [ 6.421s]
Writing 'system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Something with partitions?