Hi folks,
My first post, guess what? Did something stupid, and my box is (half?) bricked. I could use some help. I can understand some technical terms but I never got my head around the Android OS, so please be patient.
This is a T95m (p212) with Android 7.1.2, which is supposed to have a S905X SOC and 2/8GB memory - by the way, how can I confirm that? CPU-Z, AIDA64, etc. don't explicitly tell me what the SOC is. But that can wait for now, there's something more urgent.
Yesterday I tried launching the pre-installed Root Explorer (or something to that effect) but it just freezes on a blank screen. CPU-Z says the box is rooted, so I thought all I needed was some permission control. I installed SuperSU from the play store and launched it. Opted for the "normal" installation (not TWRP). At some point it asked me to reboot the box, and so I did. Since then it won't go past the initial (cheesy) animation. I can get to the recovery menu, wipe the partitions (which I did), mount the system partition, enable the ADB interface (apparently), but that's all. Rebooting into bootloader doesn't seem to work (but I wouldn't know what to do with it anyway).
I'd like to revert the box to the previous state, is that possible? In the many forums I've been searching someone said if the SuperSU folder is renamed the box should boot to Android again. Not sure if that's the best way. But I can't get a terminal to type any commands anyway.
The box has a reset button inside the AV port (well, I can hear a click when I press it, so I assume it's there), a micro-SD card slot, and an OTG port next to the USB ports. I have a Win10 PC, and an old (10-yr old) laptop running Ubuntu. I also have lots of USB cables, including an A-to-A male-to-male that came with a HDD case.
I've read a few dozen posts about people with similar problems, but each case seems to be a little different than mine. I appreciate if you can help me find the right ones to follow.
I tried to connect to the box from my PC using the OTG port, but I can't see the device in Windows. Not sure if I'm doing it right.
I've been trying to load a TWRP recovery image to a micro-SD card and boot the box to it but it didn't work either. Again, I'm not sure I'm doing it right. I used the BootCardMaker from China Gadgets, it came with its own u-boot.bin, which I used. At the end, I see an empty drive in Windows, I assume the boot files are in an invisible partition, correct? The card is only 512MB, does it matter?
Then I tried adding the TWRP recovery images I've found to the sd card drive in Windows (is that where it should go?), and boot the box to it. I tried releasing the reset button as soon as I plug in the power, and tried holding the button for 5, 10, and 30s. In any case the box always shows the initial logo but freezes there.
[EDIT] I tried now to use a different TWRP image without renaming it to recovery.img, then hold the reset button and power up. The box booted to the regular recovery menu. So it seems the box is at least reading the SD card (because when I put in a recovery.img file in it I get a different result). I guess now the matter is to find the correct TWRP image for this box, right?
[EDIT2] I forgot to add a link to the box:
https://www.amazon.ca/dp/B071Z457PQ/...ing=UTF8&psc=1
I thought it's time to ask for help before I damage it even more. Any suggestions?
Thank you in advance,
VMat
Highlights
Highlights
