To start with I did a factory reset to wipe out my files and apps before giving my tablet to my niece. After the reset the tablet is stuck at the screen with the android guy in the corner and MEDIATEK across the screen. it will not boot any further. I took the tablet to a repair store and 3 days later he tells me the chip is corrupted and he cant(be bothered?) do anything because its a Chinese clone?

I have researched many sites but cannot find a scatter file or rom image etc.. the following is what I have found inside my tablet: On a stickered chip:

E960 V1.2 YK18091021
GXQ 2018/09/26


Android Version:7.0
Android Security Patch level: 1Feb.2016
Baseband version:  MOLY.WR8.W1449.MD.WG.MP.V23, 2017/05/16  17:00
Kernel version: 
c@c-S2600JF #2
ThuOct11 17:29:47 cst 2018
Build Number:
MRA58K test-keys
Custom Build version:

I am completely lost and would really appreciate any help possible. Thank you in advance, John Sweeney

  • No offense, but these are disposable devices... Unless you can find the original firmware image, which is literally impossible on most of these devices, and you have a JTAG programming tool ($100-$350) it's probably a lost cause, I would go into recover and attempt a factory reset again, twice to make sure. But the tech is probably right, its not worth attempting to repair. The other kicker here is in the info, notice "test-keys" in the build number? That means it likely wan't an authorized use of Android either, common among these generic tablets.
    – acejavelin
    Feb 18, 2021 at 3:27
  • Because the device is may be considered disposable (which is probley 80% of all electronics today) but that doesn't mean one can't try to fix it or at least learn something new. Test-Keys appeared after the factory reset because I think I hit the wrong command key the 1st time ... they were all in chinese.... Feb 20, 2021 at 4:00
  • "Test-keys" is based on how the software is built or compiled, not anything you did... You don't have what most legitimate Android devices would have production keys, in other words they never went so far as to sign (digitally) their own build. Again, you need the full ROM image to repair this, or in your case the scatter file (essentially the full rom image) used by MediaTek devices. You can try the stuff listed below, but it is unlikely this device will every be recoverable.
    – acejavelin
    Feb 20, 2021 at 4:34
  • create your own scatter file with WwR MTK. preloader works 100% even on dead device without battery youtube.com/watch?v=O2XWTAYmNUo
    – alecxs
    Feb 20, 2021 at 8:58
  • hold power button ~ 10-30 sec to power down. when powered off, hold Vol up + Power to enter recovery menu, select "reboot to bootloader" to enter fastboot mode
    – alecxs
    Feb 20, 2021 at 9:08

1 Answer 1


The kernel version 3.18.19 is correlative with Android 6.0.1 Marshmallow, which also correlates with Security Patch level. The ROM is built userdebug test-keys so this is most likely (ported) custom ROM.

Looking for baseband version there are lot of different 'brands' for several phones or tablets, which is unusual.

What they have in common these are low-budget devices running entry-level MT6580 processor with serial number 0123456789ABCDEF in fastboot mode.

Indeed this looks like a typical chinese clone device often with fake android version and/or fake hardware specs (see #40386).

Nevertheless factory reset will not have such negative impact, only cache + userdata partition is formatted which does not harm the firmware/ROM.

The best source for 'stock' ROM is your device itself. Do a read back with SP Flash Tool and create your own scatter file with WwR MTK

check that device has unlocked bootloader and/or adb root access in recovery mode. download platform-tools and enter recovery/bootloader mode with volume keys

in bootloader mode factory reset by formatting cache + userdata from fastboot

fastboot devices
fastboot oem unlock
fastboot format cache
fastboot format userdata

in recovery mode formatting cache + userdata from adb shell with mke2fs (where mmcblkp1p99 is placeholder for partition number of the block device)

adb devices
adb shell ls -l /dev/block/*/*/*/by-name
adb shell mke2fs -t ext4 /dev/block/mmcblkp1p99

Reboot your device and wait a long time. device is encrypted on first boot, that might take up to 15 minutes

  • Thank you .... Looks like I have a lot more learning to do but when I do I will try the above directions. I have all ready tried using the sp flash tool but it tells me to load a scatter file. which I dont have, and the tablet is frozen on android screen.. anyways will keep trying to figure it out... Feb 20, 2021 at 3:53

This site is temporarily in read-only mode and not accepting new answers.

Not the answer you're looking for? Browse other questions tagged .