

#ANDROID MULTI TOOL BACKUP ALLWINNER ROM ANDROID#
Custom firmwarefrom brunokvsBased on K2001_YZG_S212104.20170825, screen resolution 1024圆00, built-in root - rights, Android version 4.4.2.

Custom firmwarefrom Monakov86Based on K2001_CLD_S212203.20170419, screen resolution 1024圆00, built-in root - rights, Android version 4.4.2.Custom firmwarefrom tasty85Based on K2001_JC_S211106.20161121, screen resolution 800x480, Android version 4.4.2, built-in root - rights.Do not flash, if your radio is working, it may stop working! MCU dated for such aGU with a different (it seems, TEF6851) radio module with which the MCU is higher and the MCU from the Android 6 kit does not work.If the resolution does not explicitly indicate the resolution, consider that it is 1024圆00.Ĭaution, apply at your own peril, see experience tophosin the FAQ. In this case, connect a USB mouse (and in severe cases, an external display) and reflash, driving this mouse. When the situation is reversed, a part of the image, including the control buttons, will not fit on the screen. Firmware is a big risk! PG happens with a display resolution of 1024圆00 and 800x480, the firmware between them is not interchangeable - with firmware designed for 800x480 on the display from 1024圆00 only part of the screen will be occupied. There are no ways to restore a brick with a damaged MCU firmware today, just replacing the motherboard.Īttention! Due to the diversity of GU models with the “alien” firmware and inappropriate firmware, some GU functions may stop working. If everything works well, everything turns on, turns off, does not puff, does not buggy - then you do not need to flash anything! This is especially true for the MCU, if something broke during the MCU firmware, roll back to the previous version and do not touch it anymore, the MCU flash drive has a very delicate memory, and there were cases when you received the MCU after the firmware kripich, so think ten times before stitching an MCU. Attention, all actions you do at your own peril and risk.
