Hello, sorry for not having a clue, I just received this tablet, unlocked bootloader and now trying to get it rooted. I thought everything would have been easy but I'm kind of stuck at this point.
Alldocube support pointed to the firmware of the iplay20s which is 3 years old now, download and unpacked with researchdownload, though inside the images folder I can't see anything similar to a payload.bin or a boot.img...
Please anyone can suggest me how to proceed please?
Thanks...
It's better you check everything and make sure nothing could go wrong before starting rooting processes.
First you have to tell all details about the device.
Name
Model
IMEI (Just in case)
CPU
You said Researchdowload? Is it using Unisoc chip (Formerly Spreadrum)
Thanks so much for your reply... Yep, between work and family I have attempted to research as much as I could, which of course isn't enough. Mostly I've found unrelated discussions or unrelated devices. It's an alldocube iplay60 pad pro, successfully unlocked the bootloader, then downloaded the latest available firmware for iplay20s as suggested by alldocube, but through researchdownload I couldn't get the boot img out of the .pac file. I have then tried a more recent version of researchdownload and finally the boot.img showed up, no sight of any init_boot.img. Patched by magisk manager and flashed via fastboot, result is a fastboot mode bootloop. Now the device is continuously rebooting in fastboot which makes it impossible to be detected by my pc, well actually the pc detects the tablet but it immediately disconnects. I have tried all sorts of button combinations but no luck. After fastboot bootloop the whole night it ran out of battery so I was hoping it would get detected by researchdownload, but as soon as I inserted the cable pressing volume down it started to bootloop again.
My next steps will be try to double check all drivers are up to date and correctly installed and with the tablet off due to zero battery I'll try again to see if rd will detect it, last resort steo is to send the device back for a refund, I'm pretty sure they have the tools to revive this tablet, though my hope would still be to resuscitate it.
Thanks for the help...
This post was last modified: 23-03-2025, 12:40 PM by Dyr.
It's always better to somehow use your own device firmware than to use the ones provided by others. Anyways
I think you never took a backup of your files and just directly flashed the files they gave you.. Right?
If you did take a backup of your original firmware, you can try flashing it back.
Else try to flash the entire firmware the company gave to you (The .pac file) using respective tools. https://www.hovatek.com/forum/thread-1231.html
The boot loop starts once you hold the power button right?
Yes? Then wait it's battery dies. charge it again and just directly connect it to pc and follow the thread sent above
You might still have to figure out how to stabilize it if it isn't the case.
NOTE : IF YOU ARE NOT THAT ADVANCED IN THESE TYPE OF THINGS. EITHER LEARN BEFORE DOING THESE OR JUST GIVE IT TO THE SHOP.
THEY WILL DO IT FOR YOU
This post was last modified: 23-03-2025, 01:15 PM by Crossshield45.
Thanks, but no, regardless of the power button as soon as the usb cable is connected it starts bootlooping. My only doubt is that it takes a few seconds to start rebooting after it ran out of battery and I don't know whether it's cause it's not detected because of missing drivers or because there's not enough power in the battery for the detection.
This is my first, and probably my last, device where firmwares provided by manufacturers are not reliable.
I've always had Xiaomi devices and although flashing and charging still happens usually, I never ran into a similar issue where flashing the wrong file, or correct file missing important steps, could cause such no way out situation. I've really no much time to research in depth, that's why when I'm not too sure I buy from Amazon...
Flashing and changing*
Please would you be so kind to share what version of spd allows to perform a firmware backup? Is the procedure straightforward for someone who has never dealt with spd ?
Also, in case I'll get another one, once i get to the rooting stage again, since it's now clear that patching the boot.img alone is not useful, are you aware of a more profitable root method? This tablet is ran by mtk g99.
Thanks 🙏
Flashing wrong file or missing important step will definitely cause more harm. But some cases you are just lucky probably and accidently done everything right...
The procedure is (In game style) NORMAL DIFFICULTY
But may escalate according to errors or other things.
Wait. What? You have MTK G99
Then why the heck are you using SPD tools?
This is only for speadtrum devices. Not for MTK
I'll give a basic outline for rooting (MediaTek)
1# Gather a online firmware for your device which is same as yours (Name, Model, CPU, Android Version etc should be same)
2# In the firmware, there should be a scatter file. If not then follow this guide to get a backup of your device https://www.hovatek.com/forum/thread-46323.html
Thanks. Look, I am not friend with unisoc/mtk environment, the only reason I picked spd is because the firmware advised by the manufacturer comes with a .pac extension, and as far as I understand so far, the only tool handling .pac files is spd. I needed to extract the boot/init_boot.img and spd was the only option, of course I also had in mind to use spd to flash back the .pac firmware in case of problems. Again, I never found myself in a situation where flashing a wrong boot.img could cause such an inescapable scenario, it still makes no sense to me that an android device can't be put in fastboot mode even with a much more messed software. I'm used with Xiaomi, where the likelihood of being unable to boot in fastboot is really really low, and even at that point there's still edl mode. By the way even connecting the device to mtktools and mtkbird could not get the tablet detected...
I've read somewhere that not all versions of spd can perform backups, please do you know whether that's true and if true what version can ? About the possibility of different rooting methods I meant if after flashing either boot.img or init_boot.img some sort of signature is required..
Thanks 🙏
This post was last modified: 24-03-2025, 08:39 AM by Dyr.
Bro, Your TAB is a mtkG99 (As per you said) .
First of all, you weren't supposed to use SPD .
Also the .pac file you downloaded is not even for your chipset..
To be exact you just threw a bowling ball to a bat.
Right now, the only thing you can do is get a new same tab with same chipset and stuff and then backup its firmware as I said in the previous message. And flash that using tools made for mtk to the bootlooping tab.
I hope you understand that
OR ITS FAR BETTER TO JUST GIVE THE TABLET TO A SHOP.
Thanks. Bro you made it very clear what I did was screwing things up, as said my available time to research is very limited. Alldocube was contacted several times in order to ask, check, confirm and double confirm the firmware they were pointing at was the firmware I had running in my tab at that moment. They promptly answered reassuring me multiple times that the .pac file listed for the iplay20s was kind of universal and it was the exact one I was running. The firmware page advised that spd tool was necessary in order to manage the process, so I just followed the manufacturer advice, also cause initially I was hoping not to use spd for anything else other than extracting the image I was looking for. I saw spd was omnipresent in all forums about alldocube/blackview/umidigi/oukitel/teclast devices so I went for it with the thought that if anything goes wrong there's always some method to recover the device... I was wrong all the way...
