[X]Assistant

[eserguei]

Cube U30GT - Firmware
Cube U30GT, -W, -H, -HS; iconBIT NetTAB Thor; Starway Andromeda S930; MyTab U30GT2; SHIRU Shogun 10 16GB; Mediacom SmartPad 102 s2
Description | Discussion пїЅ | Purchase пїЅ | Accessories and Peripherals пїЅ | Marriage and Repair пїЅ | Games пїЅ | Firmware пїЅ

Important information

ModelsCube U30GT-M(mini), пїЅU30GT1(U30GTC4), U30GT2are discussed in the relevant topics.
ModelsIconbit NetTAB ThorLE, Iconbit NetTAB ThorXIt has nothing to do with Iconbit NetTAB Thor, or with Cube U30GT.

If you purchased a tablet recently and in this thread for the first time -take the time to flash the tablet.
Before installing a new firmware, read this topic at least a week.
Remember, an error with the firmware can cause the tablet to be turned up.

Drivers and Utilities

RK_DriverAssitant -Drivers for Win7 and Win8. Installing drivers for firmware on Win8.1.
RKBatchTool v.1.8 + drivers Win8.1 + Win10
RKBatchTool for firmware 1.7.1.1 + driversU30GT_rkbt_1.7.7z(387.48 KB)

RKBatchTool for firmware 1.5 + drivers:U30GT_RKBatchTool.7z(378.28 KB)

RKBatchTool for firmware 1.5 + drivers (Russian, thanks to zdorovtsev70):U30GT_RKBatchTool_RUS_by_zdorovtsev70.7z(369.56 KB)

HiSuite- Manager for connecting our device to a computer and working with files (thank you to uv. nakme for checking the operation on U30GT).

Firmware

Official firmware

New firmware versions can always be viewed atofficial website of the manufacturer.

for revision w

v1.10(from 2012-08-24)
download:off.site, mirror 1, mirror 2.

for revision H

Important note:When switching from ICS 4.0.4 firmware to JB 4.1.1 (and vice versa), sew only using the button<Restore>.
Use the Upgrade button only when installing firmware with the same bootloader version.

JB 4.1.1

V1.11(from 2012-12-29)
download:off.site, Mirror on narod.ru, Mirror 2

v1.05 Win8 UI(from 2012-12-13)
download:off.site, mirror on narod.ru.
FirmwareAndroid interface v1.10andv1.05 interface Win8 UIidentical, the difference is only in the interface (in the appearance of the launcher).
v1.10(from 2012-11-30)
download:off.site, mirror on narod.ru.

v1.09(from 2012-11-21)
download:off.site, mirror on narod.ru.

ICS 4.0.4

v1.04Win8 interface (from 2012-10-16)
download:off.site, mirror.
v1.03(from 2012-09-27)
download:off.site, mirror.
FirmwareAndroid interface v1.03andWin8 interface v1.04identical, the difference is only in the interface (in the appearance of the launcher).

for revision hs

v1.01(from 2013-02-25)
download:off.site, mirror 1, mirror 2.

for iconBIT NetTAB Thor

fw_NT_THOR_v4.1.1_v1.01 (03/06/2013) _Version_3.zip

fw_NT_THOR_v4.1.1_ (November 25, 2012)

fw_N_THOR_V4.10_ (09/08/2012)

Modified / custom firmware | Neofits. firmware |

KK 4.4.x

TVBOX Android 4.4.2 (AOSP) for Cube U30GT-H (HDMI)
Port with HUU H7 SMART Android 4.4.4 for Cube U30GT-H

JB 4.1.1

When switching from ICS 4.0.4 firmware to JB 4.1.1 (and vice versa), using the Rockchip Batch Tool v1.5, sew using the button only<Restore>.

пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ CUBE u30gt-H пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ 101022-01a-v1 (пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ Focaltech FT5606) пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ u30gt2 - 101075-01A-V1 (пїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ Goodix GT928). download

Post with a description and links.

Modified firmware for CUBE U30GT-HSmade on the basis of U30GT-HS_v1.01_20130225 (JB 4.1.1)fromkasty-cube.
Description.

Cleaned firmware and modified firmware for CUBE U30GT-Hmade on the basis of U30GT-HS_v1.01_20130225 (JB 4.1.1)fromeserguei.
Description and download link.

ImaSoft firmware

Decontaminated V3.1 (01/27/13)

Decontaminate JB V3.1 (OS 4.1 JB) 01/27/2013For revisions "H" and "W" (we take only our basis).A source.
The firmware is based on the official firmware version for the PIPO tablet, with additional performance improvements.
Installation only through CWM!Download firmware.
How to install Decontaminate.
You must have a flashing boot.img flashing (6.0.2.7)
Put on root of external SdCard
In CWM wipe data / factory reset
In advanced menu wipe dalvik cache
From main menu select install zip from sdcard
Select choose zip from external sdcard
Process takes ~ 10 minutes
It will not be complete until it returns to the menu ... patience
When returned to menu select go back
select reboot system now.

The base (Base) for the firmware is the same CWM:
Installation if you already have a different version of ClockWorkMod
Download CWM for your tablethere
Put on root of external SdCard
In CWM select install zip from sdcard
Select choose zip from external sdcard
Process takes ~ 2 minutes
It will not be complete until it returns to the menu ... patience
When returned to menu select go back
select reboot system now.

Installation with RKAndroidTool
Shutdown your tablet
Download CWM for your tablethere
Unzip to your desktop
Run RKAndroidtool.exe from the folder
Enter flashmode on your tablet and insert usb cable.
Click flash ROM
When complete it will boot into CWM
select reboot system now.

Infected JB V4.0 (1/27/13)

Infected JB V4.0 (1/27/13)For revisions "H" and "W" (we take only our basis).A source.
The firmware is based on the official version of the firmware CUBE U30GT v.1.11.Download.
How to install Infected:
You must have a flashing boot.img flashing (6.0.2.7)
Put on root of external SdCard
In CWM wipe data / factory reset
In advanced menu wipe dalvik cache
From main menu select install zip from sdcard
Select choose zip from external sdcard
Process takes ~ 10 minutes
It will not be complete until it returns to the menu ... patience
When returned to menu select go back
select reboot system now.

The base (Base) for the firmware is the same CWM:
Installation if you already have a different version of ClockWorkMod
Download CWM for your tablethere
Put on root of external SdCard
In CWM select install zip from sdcard
Select choose zip from external sdcard
Process takes ~ 2 minutes
It will not be complete until it returns to the menu ... patience
When returned to menu select go back
select reboot system now.

Installation with RKAndroidTool
Shutdown your tablet
Download CWM for your tablethere
Unzip to your desktop
Run RKAndroidtool.exe from the folder
Enter flashmode on your tablet and insert usb cable.
Click flash ROM
When complete it will boot into CWM
select reboot system now.

Firmware for Cube U30GT H 1.11 900 supersport ROM
Description Download

The modified firmware for U30GT-H is made on the basis of U30GT-H_V1.11_20121229 (JB 4.1.1)fromeserguei.
Description and download link.

Clean firmware for U30GT-H 1.11fromkasty-cube
Original onarctablet.com, mirror on narod.ru

The cleaned firmware for U30GT-H is made on the basis of U30GT-H_v1.10_20121130 (JB 4.1.1)fromAndrey_GAV
Description and download link

The cleaned firmware for U30GT-H is made on the basis of U30GT-H_v1.10_20121130+ 2GB for programs.fromeserguei.
Description and download link.

The firmware for U30GT-H is made on the basis of U30GT-H_v1.10_20121130+ root + 2GB for programs.fromferiross.
Description and download link.

Decontaminate JB V3.0 (OS 4.1 JB) dated 11.23.2012For revisions “H” and “W” we only take our base).A source.
The firmware is based on the official version of the PIPO tablet with additional performance improvements.
Installation only through CWM!Download firmware. The base (Base) for the firmware is the same CWM:Download

Infected JB V3.0 (12/07/12) (OS 4.1 JB)For revisions “H” and “W” we only take our base).A source.
The firmware is based on the official firmware version 1.10.Download. The base (Base) for the firmware is the same CWM:Download

ICS 4.0.4

Mods variations from eserguei for firmware 1.04 (ICS 4.0.4 Win8 UI)for U30GT-H.
Based on off-firmwareU30GT-H_v1.04_Win8 UI from 20121016. Description

From adiksavagemessiahzine.comcleaned firmware 1.03 (ICS 4.0.4)for U30GT-H and 2GB for programs.

Description

Based on off-firmwareU30GT-H_v1.03_Android UI_20120927.
Changed the section under the application, now it is 2 Gb
Root done
Replaced the market with the latest version
Chinese cut out (seemingly all, cut to the eye)
Default launcherApex launcher(I like the most, smooth and you can set the transparency in the application menu, and not the black background as everywhere else.)
Installed such a boot
http://www.youtube.com/watch?v=fovV36oGspw
In build.prop, the device is defined as samsung galaxy note N7000, if you wish, edit it for yourself.
The default language is Russian

Download, Mirror

Evolution Prime v1 (2GB for programs) (ICS 4.0.4)

Experimental firmware

This section contains experimental firmware, stability and power consumption are not guaranteed. As a rule, they are under development and are not suitable for everyday use.

Oma CM10.1 v1.5 as amended by arkan49

CyanogenMod 12 frommussonero
installation comment and download links.

Firmware archive

Archive of old and not current firmware isin this post

Instructions

Driver installation

If you are going to flash the tablet for the first time, install the driver.
Detailed instructions for installing drivers for the tablet (authoreserguei)

Before flashing

1) Usegood cableUSB-microUSB, the cable from the kit in most cases fails (although there are rare exceptions). Better to take from the original device (Samsung, Nokia, HTC, etc.)
2) Connect the USB cable toUSB 2.0 port on the motherboard(back side of computer).
3) If you are going to flash for the first time, make sure that you have a tablet revision (CUBE 30GT-Wor CUBE 30GT-H). Flashing the tablet with firmware that does not coincide with the revision of the device, we will get a brick with a probability of 100%!
When connected to a computer, all tablets are defined as a W revision, but this is not an indication of a revision.

Tablet revisions: W and H

The first devices had revision W. At the moment, fresh devices have revision "H". The revision number can be found on the serial number on the back of the tablet (U30GTH32GB) 1233 ...). Also, the revision "H" and have an OEM version without inscriptions on the back cover and a clone from iconBIT NetTAB THOR.

4) The main firmware for our tablet is firmware from a PC using a cable. Due to the fact that reading from an SD card is possibleSD card firmware is not recommended.Use it only in the case when other methods are impossible (for example, when eliminating the state of "brick").

Instructionon preparation for firmware fromarkan49

Ways to install the firmware

All firmware, which consist of one img file (and this is all stock and many custom ones) are stitched with the help of the Rockchip Batch Tool v1.5.
With all the others (which are not flashed using Rockchip Batch Tool v1.5), the program for the firmware is in the archive.

Firmware firmware standard program Rockchip Batch Tool v1.5

1. Requirements:
RRockchip Batch Tool v1.5 (hereinafter RBT)
Cube U30GT firmware file
Personal computer or laptop / netbook running the Windows operating system (for a PC, it is desirable to have a UPS)
Usb cable

2. Initial Setup
Extract RRockchip Batch Tool v1.5 (hereinafter RBT) from the archive. The software includes the necessary drivers for the device.
Unzip the downloaded firmware image
The path to the folders with the program and firmware should not contain Russian letters and spaces.
Run RBT and select the firmware file (...).
If everything is done correctly, you will see the information in the program window - the current firmware version, Android version, board revision (RK30), etc.

3. Installing device drivers
Turn off the device
Connect to computer.
Press the volume up button, then press the power button (the volume button remains pressed).
When the system sees the new device, release the buttons.
When prompted to install the driver for the device, go to the RBT directory and select the "Drivers" folder and the operating system will install the necessary driver.
After the driver installation for the device is completed, one of the RBT fields should change color from gray to green.

4. Install new firmware
After connecting the tablet, click the "Upgrade" button (in case the bootloader version has not changed).
When switching from ICS 4.0.4 firmware to JB 4.1.1 (and vice versa), sew only using the button<Restore>.
You should see an orange text in the green box describing each step of the device update.
If everything is done correctly, you will see the following message:

********** Upgrade Done Success<% d>Fail<% d>Time<% d>ms **********
Instead of% d will be a number.

If the firmware is in normal mode, the tablet will start to boot. If this does not happen, then simply press the power button and wait for the download.

Addition: If you press not "Upgrade", but "Restore", then additional internal formatting takes place and then the firmware also gets normal.

ATTENTION!
Neither the Cube manufacturer, nor I, are responsible for updating your device with the RRockchip Batch Tool software, i.e. everything you do - you do at your own peril and risk.
If this is possible, always use the built-in firmware update functions (Let's say, custom firmware — no!))) It's much easier and safer!

Instructions for firmware device program RK30AndroidTool 1.35

This utility is present in the 900 Supersport firmware (see Archive with firmware)
The path to the folders with the program and firmware should not contain Russian letters and spaces.
Drivers:
The firmware requires RK30AndroidTool 1.35 (hereinafter RKTool), (in the archive with the Supersport firmware renamed to ROM FLash Tool)
To use it, you need to install the driver RK30
They are present in the archive for Windows 32bit and 64bit
These are the same drivers that RKBatch Tool 1.5 uses.

If the driver is already installed, then everything is ready and you will not have to install it. If not, installation is required.

1) It is better to remove the SD card from the slot before starting the firmware
2) Connect the USB cable to the PC. DO NOT worry if the tablet turns on, it may turn on itself when you connect any of the cables.
3) Make sure the charger is connected! This is very important if the battery is weakly charged (if charged, power is optional)
4) First press and hold the button up sound
5) Now press and hold the power button, without releasing the volume increase button
6) Somewhere in 5 seconds, your computer will declare that “a new device has been found”
7) Winda complains that the driver can not find and may ask to look for them. This is normal. Close all dialog boxes, etc.
6) Open the device manager in the control panel. You should see an unknown device with a yellow question mark. Click on it with the RIGHT button and select "update driver"
7) A window will pop up asking to find the driver on the computer. Click the browse button.
8) On the next screen, click the browse button. A file selection window will open. Now remember where you unpacked the archive. Point to this directory, select the driver subdirectory and select 32bit or 64bit depending on your OS. Now select OS version Win7, etc.
The OK button should be available. Click it. The driver should be installed. If not, start the process from the beginning.

Firmware:
So, the driver is installed, and now we can upload new firmware to the device.
Firmware with ROM Flash Tool is different from Btach 1.5 + update.img.
With this utility you can flash only the main images. Such as Kernel.img, boot.img, etc.

1) Run the RK30AndroidTool 1.35 program (ROM Flash Tool.exe)
2) Settings in config.ini, all img files are entered into the program.
DO NOT CHANGE these settings, otherwise you can get a brick!
Do not play with offset values. Just kill the device.
3) There are 2 ways to enter the tablet into the firmware mode: simple (using this program) and complex (push-button).

1. Using the Flash Tool:
a) Turn on the tablet, insert the USB cable into it.
b) Run the ROM Flash Tool. The line "Found RKAndroid MASS Storage USB" should appear at the bottom
c) Click "Reboot to Flash Mode". After a few seconds, the device will reboot.
d) If the drivers have been installed correctly, the tablet screen will turn black, and the program should now appear at the bottom of the "Found RKAndroid Loader Rock USB"
e) Just in case, close the program and run it again in order to clear its memory (apparently, the cache is meant).
Go to step 4.

2. Using the buttons:
a) Turn off the tablet
b) Press and hold the volume up button
c) Without releasing the volume button, press and hold the Power.
d) After 5 seconds, the computer will inform about the connected device.
e) If the drivers were installed correctly, the tablet screen will turn black, and the program should now appear at the bottom of the "Found RKAndroid Loader Rock USB"
Go to step 4.

4) Before flashing, you need to clear the internal memory. Click Erase NAND (IDB)
Should appear "Doing Lower Level Format, Total (16384)"
(I hope I understood correctly here) IMPORTANT! in the Current line should be counted digits to 16384, and the operation will be completed.
If the numbers are not counting (sometimes), restart the Flash tool and click Erase again.
If the numbers do not run anyway, close the program, reboot the tablet into firmware mode again and try again.

5) It's time to go. Click "Flash ROM" and let the program do its work.
The operation will take several minutes. Upon completion, the tablet will reboot itself.

FIRST DOWNLOAD!
The first download will take some time.
Further, the tablet may be in recovery. Just press the power button and boot into the OS.

Tablet firmware via recovery from SD card

Use this way of flashingonly as a last resort, egfor scratching.

1) Make sure the tablet is fully charged. In the recovery there is a recommendation to flash the tablet with the power connected.
2) Download the firmware and save it to your desktop.
3) Extract the .img file
4) You will need to copy it to your desktop and rename it to update.img
5) Save update.img to the root directory on a microSD memory card
6) Insert the microSD card in the off tablet
7) Press and hold the volume up button and the power button until the logo appears. Release both buttons. The launch of the update system happens and just when the map is installed with update.img (I did not check it myself). Not always there is a clear triggering of a combination of buttons to call up the recovery menu, so you will probably have to play around with them.
8) The Android logo with a red triangle will appear! Pressing the volume and power up keys again brings up the recovery menu.
9) Use the volume key to select rkimage update from sdcard (last menu line), then press the power button to select it.
10) Firmware update will be available.

At the end of the firmware, the recovery menu will reappear. Choose a reboot tablet. All firmware upgrades completed.

For those who are stitching from the card (in any way) - after the update.img file has been dropped onto the card, check its hash sum (for example, md5), compare it with that on the PC. To be sure that the file was discarded intact (right on the tablet md5 can read, for example, root explorer). (thanks to JustACat)

Removing the tablet from the state of "brick" (splicing)

Cases to get a completely non-working device due to unsuccessful firmware has not yet been. There is always a way to “scatter” with disassembling and closing the contacts on the device board.

There are several types of "bricks":
- the tablet turns on and comes to standard recovery (picture of a robot with an exclamation mark);
- black screen and does not turn on.

To begin, turn off the tablet, even if it is turned off: keep the button<on>more than 10s
If you get to the standard recovery (a robot with an exclamation mark), then it will probably save the firmware from the SD card(see firmware instructions). To do this, when a robot with an exclamation point appears on the screen, we enter rekoveri (click<on>, and without releasing it,<gr top>. let go<gr top>let go<on>) and flashing from the SD card (see instructions).
Try different firmware. remove and install the card back, check the possibility of firmware, and so several times. Try to boot into the recovery with the installed card. I got it from the third or fourth attempt. Try, it will not be worse.

We connect the tablet to the computer and turn it on in the firmware mode (hold<gr +>and<on>) at the same time in the RBT program we see whether the "green square" appeared. If so, then we flash it in the usual way or with the help of the RK Android Tool.
If the device is not detected in firmware mode, then disassemble and use the following instructions.

The first way to scratch(thanks for the JustACat translation). Another optionwith contact closure.

The second way to scratch
Suitable for the case when the tablet is loaded only for native recovery mode.
Or after the restoration of a brick in the first way with the help of RBT, an error occurs: "Error waiting for the bootloader to start"

1) Connect to a computer and run RBT (or run RKAndroidTools and watch the device connection status below)
2) Disassemble and close the contacts from the first method and press<on>
3) Get the blue square in RBT (or the status of the connected device in RKAndroidTools)
4) Close RBT if started or use RKAndroidTools
5) Flash the firmware using RKAndroidTools and be sure to flash this very bootloader (for example, the Supersport firmware - everything is in it by checking the bootloader firmware)
6) Well, then flash the necessary firmware using the usual method.

Recovery / Root

CWM recovery and TWRP

CWM recovery for our tablet is recommended to install only with the kernel and firmware on which they are tested and it is known that they will work normally.
Utility from ImaSoft for firmwareCWM recovery and TWRP for # 52, # 302 and # 256 cores.

ROOT privileges

Before you run the utility to get ROOT, make sure:
1. The tablet is connected to the PC.
2. Settings - For developers- enabledUSB debugging.
If not previously installedADB driversthen install them.
3. Settings - Security- includedunknown sources.

Method for obtaining ROOT for firmware 1.09, 1.10, 1.11.

ROOT for three reboots

1. Connect the tablet to the PC.
2. Go toSettings - For developers- turn on the tabletUSB debugging.
If not previously installedADB driversthen install them.
3. Settings - Security- turn onunknown sources.
4. Unpack the archiveROOT. The path to the folder should not contain spaces and Russian letters. Run the file called run me.bat.
5. Further, all prompts will be on the screen: press any key. Wait until the tablet reboots and displays the unlock screen. press any key. the tablet will reboot again. wait for the download. press any key. the tablet will reboot again. wait for the download. root received.
video

ZhuoDaShi-2.2.9-setup.exefor getting root on the latest stock firmware (thanks to zdorovtsev70 for checking work and info) Instructions:

If there is already ADB firewood, then everything is very simple, (or we install the driver according to the old instructions in the header) we connect the tablet with USB and MTP debugging enabled. We launch a program (with the rights of the administrator) On its screen our cube will be displayed. Below on the left there will be a link with the inscription ROOT, initially red. We click on it, another window opens, there is a big ROOT button down there on the right. We press and wait for the end of the process. In the process will be installed some sort of Chinese prog and SuperSU. If you return to the first screen of the program, you will see that the link on the left has turned green. Reboot and go ahead, take out the Chinese garbage.

ZhuoDaShi and instructions with picturesfrom the next topic.

One moreROOT production method.

One moreROOT production method.

How to check if there is a root?
Start Titanium backup, it will report the presence of root or will suggest to correct, if root is not complete.

miscellanea

Bootanimation Compilationfor our tablet.

useful links

Official sitewww.51cube.comwith firmware.
Forumwww.flashmyandroid.com, section about firmware Infected, Decontaminate.
Forumwww.freaktab.com- firmware from 900supersport.

Useful links for romodels

Descriptionhow to edit the firmware.
A set of utilities for editing firmware. Allows you to disassemble the IMG firmware image and manually make changes to the system section (remove unnecessary, add the necessary programs), and again pack it into the IMG file for the firmware. Utility for rebuilding boot.img or recovery.img.Merged version.
Firmware devices on the Rockchip 3066 platform (rk3066)

F.A.Q. Answers to most questions asked in the topic

What is the difference between H and W versions of the tablet and firmware?

The letters after U30GT indicate only differences in production lines or tablets with different components. They have no differences in function and quality.
Firmware differ only in bootloader, they also have no differences in functions and quality.

How to enter native recovery

To enter native recovery:
- turn off the tablet;
- hold and hold<group +>
- turn on the charge and wait until the logo appears, how to release the logo<group +>(you can then pull out the charge)
- a robot will appear with an exclamation mark, press and hold<on>to push<group +>let go<group +>. let go<on>.
- all entered into the recovery, moving through the menu with the volume keys, the choice - the power key.
instruction fromAndrey_GAV

WiFi does not turn on

If WiFi does not turn onsee recommendationsfromVooDooX.

Gameloft game compatibility

We change build.prop for compatibility with gameplay games.
Root required
Use Rutexplorer or another file manager with root rights, open build.prop in / system /.

ro.product.model = U30GT-W
ro.product.brand = rk30sdk
ro.product.name = rk30sdk
ro.product.device = rk30sdk

Change the values ​​above to these:

ro.product.model = SGH-T989
ro.product.brand = samsung
ro.product.name = SGH-T989
ro.product.device = SGH-T989

or these:
ro.product.model = GT-N7000
ro.product.brand = samsung
ro.product.name = GT-N7000
ro.product.device = GT-N7000

either change
ro.build.fingerprint = samsung / GT-N7000 / GT-N7000 and leave the rest as it is.

How to make the status bar to hide?

To putHidebar 1.5(thanks to Alexxsh1974)

Does Flash work on Android 4.1 JB and can I install it?

In the stock firmware and most mods for the adobe flash to work, you need to run the built-in Browser once, it will install flash support. It is also worth making sure that your browser version supports flash.
Detailed instructions with xda-developers:how to install flash on 4.1(thanks to elias-740)

Has anyone been able to put Chainfire 3D on our device (Android 4.1)?

Kettle 4.1 does not go under any circumstances. It is necessary to wait for the program update under Jelly bean, it will not be possible to launch it in any other way. (thanks artwen)

I downloaded the firmware, when I unpacked the error or I can not unpack it

Download the firmware file again. Or,download and install fresh 7zip

Farrowing screenshots

[attachment = "2361406: 02.jpg"]
[attachment = "2324582: 01.jpg"]

There is no curator in the subject. For filling caps, please contactmoderatorssection through a buttonunder the messages to which you want to add links.

Post has been editedsnekt - 19.06.18, 08:48

Reason for editing: RKBatchTool v.1.8 + Win8.1 + Win10 drivers

[JustACat]

Glav.Buh,
1) How do you determine that "the computer does not see the tablet"? Through the device manager or a square in the firmware?
2) if on a small square in the firmware, then try to search all the same cube in the device manager, and also try to take another firmware (not from this topic), namely: take and download the stock (from the cube site) firmware for the H version, and take the drivers and firmware from it (it is in Chinese, but it switches easily to English). Well, preferably yes, on another PC try it all at once, so that on a clean, so to speak.
3) try the next feint with your ears (only clearly this is also better on a clean PC, since it will be easiest to determine that the tablet came to life - the firewood installation window will pop up):
- connect the wire to the cube and computer
- hold the volume on the cubeway down(farther from the power button) and the power button and hold it longer (for at least half a minute at the same time) while controlling through the device manager and the firmware, doesn’t that change
- release both buttons
- just hold the power button and hold it (for a minute at least), also control it
- release
- hold down the volumeupand the power button, again hold for half a minute
If something changes at one of the stages, the tablet will revive or the firewood will ask, do not continue. I understand, everything looks like dancing with a tambourine, well, in fact, they are. I just also had to rewrite many times during the process of flashing (and I’ve already changed a lot), the tablet seemed to stop living, but it helped me to press and hold buttons in different combinations. Only now I did not clearly remember what I was doing ...

And another question arose, you write "5. The tablet itself did not overload itself, and fell asleep." - he is in the firmware mode does not give any signs of life at all (until the firmware downloads to the tablet and it does not restart), how did you determine that he fell asleep? Or here it means in a figurative sense - died?

Hmmm, what else would check: download the same firmware, but from another place (via another link), for example from Google Mailbox. Unpack and compare your firmware files that were flashed with the new one (for md5 hash sums there or crc) should be the same ... Is it a little if the file is damaged ...

By the way, I confirm that my tablet was determined only if it was first connected with a cable, and only then switched to the flashing mode.

r.d,why are you confused? What is the difference - to flash first, and then the data is old user wipe or vice versa? In other words, I think in this case it’s still 9 or 10 to do first. The main thing after flashing (9 points) is to execute 10 points immediately, without getting out of the recovery. And only then restart the tablet (11 point).
By the way, I did not know that we have a recovery mode ... Hmm ...

MokkoMe,Try to upgrade to Evo Prime. Well, or stock. If the problem goes away - it’s software, then just don’t use Evo 1.4, if the problem persists, then it’s hardware, then the firmware has nothing to do with - send the tablet to the seller ... Something like that, I guess.

Post has been editedJustACat - 02.07.12, 14:23

[Glav.Buh]

JustACat @ 07/02/2012, 14:50

1) How do you determine that "the computer does not see the tablet"? Through the device manager or a square in the firmware?

here and there.
PP 2 and 3 I will try to get to the house and accomplish my goal

I also thought that at the time of the action I pulled out the flash memory, try to shove and repeat everything.
By the way, in my original firmware 1.00, the external flash drive was visible in the settings, but not in the explorer

Thank you very much: rofl: to you personally and to all !!!!!
and excuse me for not being able (for now) to raise your rating


==========
yes even thought. I stuck a USB into the tablet. Or maybe it was necessary to keep him stuck and poke the end that goes to the computer?

r.d @ 02.07.2012, 15:34

If you can check plz

check it out.

Post has been editedGlav.Buh - 02.07.12, 14:58

[Glav.Buh]

Promised log

15:47:15 261 Rockchip Batch Tool v1.5.3.0 start run
15:56:49 048 ********** Start the update<1>**********
15:56:49 049 <Layer 1-4>Device test
15:56:49 052 <Layer 1-4>Device Test Complete
15:56:49 053 <Layer 1-4>Chip Check
15:56:49 056 <Layer 1-4>Chip Check complete
15:56:49 058 <Layer 1-4>Start Get FlashInfo
15:56:49 060 <LAYER 1-4>INFO: FlashInfo: 0 0 0 1 0 10 10 18 1E 4 5
15:56:49 062 <Layer 1-4>Get FlashInfo done
15:56:49 065 <Layer 1-4>Dissect IDB
15:56:49 065 <LAYER 1-4>INFO: CS (1) (8192MB) (MICRON)
15:56:49 065 <LAYER 1-4>INFO: CS (3) (8192MB) (MICRON)
15:56:49 076 <Layer 1-4>IDB preparation performed
15:56:49 078 <Layer 1-4>IDB Start Download
15:57:18 106 <LAYER 1-4>ERROR: WriteIDBlock -> RKU_WriteSector failed, RetCode (-3)
15:57:42 109 <LAYER 1-4>ERROR: WriteIDBlock -> RKU_WriteSector -> RKU_EraseBlock failed, RetCode (-4)
15:57:42 111 <Layer 1-4>Error loading IDB
15:58:06 112 <LAYER 1-4>ERROR: FindIDBlock -> RKU_ReadSector failed, RetCode (-3)
15:58:30 114 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (5), RetCode (-3)
15:58:54 115 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (6), RetCode (-3)
15:59:18 116 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (7), RetCode (-3)
15:59:42 118 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (8), RetCode (-3)
16:00:06 119 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (9), RetCode (-3)
16:00:06 119 <LAYER 1-4>ERROR: BufferWriteBack failed
16:00:06 121 ********** Update completed<0>Fail<1>Time<197061>ms **********
16:18:07 218 Rockchip Batch Tool v1.5.3.0 start run
16:20:21 116 Rockchip Batch Tool v1.5.3.0 start run

I tried it now.

1. Dances with a tambourine are suggested.JustACat,on another computer in variants - without a card, with a card, with USB right away, with USB then, with a connected power supply unit, without a connected power supply unit. In all cases, there is no sign of life in the pill and nothing appears in the Dispatcher.

2. I downloaded the firmware from the office. site. Recorded on a flash drive and actedaccording to the instructionsThe result is the same

3. And here's a program for firmware from the site did not want to work ..... which is strange. Windows 7. On two computers is buggy

Post has been editedGlav.Buh - 02.07.12, 19:49

[zdorovtsev70]

Something no matter how hard I pressed the volume and power buttons on a worktable with a memory card inserted (both on and off), no recovery mode appears. The tablet just turns off or on the contrary turns on. The truth is, as I understand it, the map should have an update.img file, but I just don’t know it alone, or you can mix it up with all sorts of things.

Post has been editedzdorovtsev70 - 02.07.12, 22:04

[zdorovtsev70]

Glav.Buh,On the flashmayandroid, they suggest that you first hold the power button for 10-15 seconds, then try to connect for firmware. They also write that these lines of the log:
15:57:42 109 <LAYER 1-4>ERROR: WriteIDBlock -> RKU_WriteSector -> RKU_EraseBlock failed, RetCode (-4)
15:57:42 111 <Layer 1-4>Error loading IDB
15:58:06 112 <LAYER 1-4>ERROR: FindIDBlock -> RKU_ReadSector failed, RetCode (-3)
15:58:30 114 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (5), RetCode (-3)
15:58:54 115 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (6), RetCode (-3)
15:59:18 116 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (7), RetCode (-3)
15:59:42 118 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (8), RetCode (-3)
16:00:06 119 <LAYER 1-4>ERROR: BufferWriteBack -> RKU_EraseBlock failed, Block (9), RetCode (-3)
16:00:06 119 <LAYER 1-4>ERROR: BufferWriteBack failed
they say about the damage of NAND memory and most likely are not subject to correction due to malfunctioning hardware. But then they propose to continue attempts at resuscitation.
Ps. Something after this is not particularly want to continue flashing the tablet (

Post has been editedzdorovtsev70 - 02.07.12, 21:39

[pasha-v]

http://www.flashmyandroid.com/forum/showth...0GT/&page=1
There is a discussion of this problem. So far the only solution is to return the brick back to the seller.
I sewed 2 times. For the first time, he made an evo 1.4, reached 7 percent, and after a while the process stopped. The device after this is no longer loaded saver. The second time he sewed an Evo 1, the log is the same as that of a headband and a brick. I have win7 x64, I installed the driver from the firmware bundle. There is an assumption that the problem may lie in poor-quality usb cord.
I think it's safer to flash from sd card.

[zdorovtsev70]

I want to add my observation. If you do not update the stock before the firmware on EVA to the version on which the mod is made, received errors when loading the tablet. After updating the drain to the desired version, the flight is normal. Probably worth it when using mods first update the stock to the desired version to avoid errors.

[JustACat]

r.d, zdorovtsev70,I enter into this mode. That is, I get such a recumbent android with an exclamation mark in the red triangle drawn in the guts (in the instructions this is the "android guy with a red!"). Further did not do, since I did not throw an update on the map (yes, I did not have this on the map of the file, but I got into the mode).
And it’s not quite clear to me which extension to add to the update file.
Those. I understand that it is necessary, for example, to rename "Evolution 1.3-W.img" to "update.xxx" and throw it onto the map, but what should be in place of these xxx? "update.img" leave or make "update.zip"? Who thinks what?

Glav.Buh,sucks, if so ... In this case, probably agree withzdorovtsev70- memory corruption may be.
Mmm, and before this firmware, you did not flash anything on it? That is, he was all right with the internal memory was? Did not try to format it in the settings?

zdorovtsev70,And where exactly is it written about the fact that this may be due to memory damage, poke, pliz, nose?

I will write from myself for all on the firmware:
1) Use only the highest quality and shortest USB cable
2) Before flashing, check the firmware file - is it broken (this can be done by downloading the firmware from different sources, unpacking and comparing the firmware files with some kind of hash comparison)
3) Before the firmware, go to the settings and check if everything is OK with the internal memory - if the device sees it, if something is wrong - format it. Do the same after flashing.

What was different in my case from the caseGlav.Buh:
1) WinXP 32 bit
2) RKBT version from the stock firmware (or, a couple of times the one that came with the Evo 1.3)
3) Always stitched with the power supply turned off (but on a charged tablet)
4) Stitched from the stock firmware of the same version (ie, Prime, based on 1.07, flashed after I installed the stock 1.07)
5) Well, I have a W-box ... But I'm not sure that this has any effect.

So far, nothing else comes to mind. That is, if there is really no reaction on the tablet from the PC.

There are a couple of more extensive ideas - for them you need to disassemble the tablet.
1) Try to use the reset button (it is on the board, just not soldered). Although, in theory, if the tablet was turned on for so much time (but it was hanging), then the battery should have exhausted and it should disconnect itself. So this is also from a series of guesses only.
2) I found a UART port on the board, I am sure that this is just a debug port, through it you can certainly get konsolku,having a UART adapter.
But since no one with a cube has yet done this, it is not known whether it will give something or not.
In any case, this will require soldering skills, because the UART port is on the board, but there are only a few fingers there — there are no pins, i.e. wiring will have to solder.

As a less extensive option - send the Chinese back. Complaining that the device was checkered when you were flashing the stock firmware into it.

[entarion]

By the way, yes guys, about the cable. I and Ampe a10 and the cube didn’t really want to connect off through their cables - I had to use a cord from htc - there were no problems.

[myboris2005]

JustACat @ 07/03/2012, 13:16

Here I am a lace from htc and sew yes.

It's already good, there is such a cord from HTC TD2.

[Glav.Buh]

myboris2005 @ 07/07/2012, 13:18

Mmm, and before this firmware, you did not flash anything on it? That is, he was all right with the internal memory was? Did not try to format it in the settings?

I tried to open the root - to save all the settings. It did not work, by the way.
The wire was checked. Then he tried them and the fact that it was in the box.


ps
Chinese supplier wrote. As it is. Current wrote about the stock. Like what to do?

Post has been editedGlav.Buh - 03.07.12, 13:21

[S1eepy]

myboris2005 @ 07/03/2012, 07:11

Quote (zdorovtsev70 @ 07/02/2012, 10:27 PM)
Ps. Something after this is not particularly want to continue flashing the tablet (
After this, you finally do not want to flash the Cube)

I had one of those early W-models, lots of quality problems.

You can only advise the owners of the W versions to wait with the firmware of the device in order to avoid scorching.

[r.d]

JustACat @ 07/03/2012, 11:38

r.d, zdorovtsev70, I enter into this mode. That is, I get such a recumbent android with an exclamation mark in the red triangle drawn in the guts (in the instructions this is "android guy with a red!"). Further did not do, since I did not throw an update on the map (yes, I did not have this on the map of the file, but I got into the mode).
And it’s not quite clear to me which extension to add to the update file.
Those. I understand that it is necessary, for example, to rename "Evolution 1.3-W.img" to "update.xxx" and throw it onto the map, but what should be in place of these xxx? "update.img" leave or make "update.zip"? Who thinks what?

Most likely in "update.img", although you can try different options
I think that at point 9, when choosing the firmware, the tablet will not show options that it does not understand

9) Use the button to select it from / sdcard then click the power button to select it.

[zdorovtsev70]

JustACat @ 07/03/2012, 13:38

Zdorovtsev70, And where exactly is it written about the fact that this may be due to memory damage, poke, pliz, nose?

Here is the link
cry

Post has been editedzdorovtsev70 - 03.07.12, 16:27

[zdorovtsev70]

Here, I tried to flash the tablet through the recovery from the SD card. Log into the recovery power button and the volume key closest to it. Although there is no clarity of transition. Sometimes it seemed that it worked only when all three buttons were pressed. In short, turned off the tablet, then pressed the buttons waiting for the appearance of the logo of the cube, when the appearance immediately released. There will be a well-known android with a red triangle. Once again, the volume + power and the menu appears. The rest is in the video. The file is named update.img, but mine can and not rename. It lies in the root of the flash drive.
Cube U30GT-W firmware with microSD card

Post has been editedzdorovtsev70 - 03.07.12, 20:08

[myboris2005]

zdorovtsev70 @ 07/03/2012, 21:00

Here, I tried to flash the tablet through the recovery from the SD card.

Test !!! It turns out that you were bored from the card without any problems? ...

Posted on 07/03/2012, 20:35:

Clearly attach it to the cap ...Cube U30GT Firmware (Post # 14163101)

[zdorovtsev70]

Yes, the firmware was successful. True for the purity of the experiment, it was necessary to first flash the stock, and then the Eve on Eve. And yet, this is more like an update and not a firmware, because the language selection screens and other initial settings did not appear.

Post has been editedzdorovtsev70 - 03.07.12, 21:32

[r.d]

the video shows that you didn’t do wipe / reset, so he didn’t reset the settings

but what he saw after the reboot UPDATE.img on the SD card and offered to be updated is very interesting

[JustACat]

r.d,Well, youzdorovtsev70already showed everything and even filmed :)

Glav.Buh,What workshop does he mean? Well, it is clear that not an authorized center of Cuba, but what skills are needed? IMHO, the most suitable workshops where cellular and laptops do. There they can quite well re-solder the chip (memory, if it's in it) and reflash with the same cord with a UART connection. The only question is who will give them instructions? The seller promised to send them? Let him send! So tell him: let him send the instructions, they say, you will go through the SC with them and ask if they will take it.
And we would be happy to have a look at these instructions - a service manual for repair to get it - mmmm! There, in theory, there should at least be a complete schematic with all the details, as well as instructions for scratching (firmware through the service port).

zdorovtsev70,precisely because you did not do wipe / reset, and nothing came out. So I’ll say on my own that if flashing not "Eve to Eve", but different firmware among themselves, then it is imperative to do wipe / reset. Ato can grab a lot of lulz ^^

And by the way, about Win7, especially x64 - it may very well be that there are problems in it ... I have nothing against Win7, but ...

In general, I read it, and I myself felt some sadness ... My work, while ... And what if it stops too? .. Send it to the seller? So I already opened it, and there it is noticeable that I opened it, which means the seller will also find out. Ah, well, fear, they say, eyes are big. You can not think about the bad.

It became interesting: now I threw update.img on the card and rebooted the tablet - after booting the system, a window came out with a message that an update was found on the memory card and an offer to update it and two buttons: Ok, Cancel (well, actually there Well, the meaning is this).
Clicked cancel. Something after all the stories about the bricks to me and I just need to flash now not hotstsa ... Now, if there is a new thing for Eva ...
But the most interesting thing is that the window with the proposal to be updated now comes out and sometimes by itself, apparently, every time the card is remounted. So you can call it without rebooting, but simply by remounting the card, or by inserting the card with the update into the tablet.
By the way, I will add for those who are stitching from the card (in any way) - after the update.img file has been dropped onto the card, check its hash amount (for example, md5), compare it with that on the PC. To be sure that the file was discarded intact (right on the tablet md5 can read, for example, root explorer).

Post has been editedJustACat - 03.07.12, 23:45

[zdorovtsev70]

JustACat @ 07/04/2012, 00:59

Ah, well, fear, they say, eyes are big. Can't think bad

I thought about the same thing before the firmware from the card, the tablet worked fine, there was a bunch of games and programs. But as Vysotsky said, if I decided something, I would definitely drink it, I didn’t even backup anything. And as for resets, for the first time I work with android and I don’t know its subtleties, many terms are unusual for me. Yes, and you can see in the video that the cursor after the firmware was on the default reboot. I also thought that for the time being it seemed to be a guarantee, and it was necessary to make all kinds of experiments on a poor body. Though the chance will change.

Post has been editedzdorovtsev70 - 03.07.12, 23:10