[X]Assistant

[Tony_AU]

Oysters T8 - Firmware
Oysters t8
Description | Discussion пїЅ| FAQ | Purchase В»| Accessories В»| Marriage |Firmware пїЅ

• Before asking a question, look Android OS FAQandGlossary. Respect your and other people's time.
  
• To discuss and search for third-party programs / games, use the following sections: Programs and Games.
  
• To compare the device with competitors and on the choice of devices, please contact:Selection and Comparison.
  
• The available amount of RAM and memory for installing applications is discussed in the topic: How much memory is in your machine?
  
• The results of performance tests of Android devices, see the topic: Benchmark
  
• Off topic posts removed.

Important information

Attention!



• Everything you do, you do at your own peril and risk. The author of the description is not responsible for any damage caused. All that is described by me, it was first tested on its own device.
  
• Do not flash the bootloader, as this may lead to the death of your device without the possibility of its restoration. I have not yet tried to flash the device with the bootloader. It is worth flashing it only if the bootloader is updated by the device manufacturer, or if the bootloader is already stitched and it does not work properly.
  If you still decide to flash the bootloader, then make sure that the battery charge level is 100%, this bootloader is for your model of device, check the reliability of the USB cable connection, ensure uninterrupted power to your computer while the device is flashing.
  
• Be careful, Oysters T8 and Oysters T8 A4 - different devices! It is IMPOSSIBLE to flash one with firmware from another

List of official firmware

Oysters T8:
- Android 2.3.1 Firmware v2.10.00 (February 28, 2012)
Oysters T8 A4:
- Android 4.0.3 (July 23, 2012) We thank Anastasia Safer

List of custom firmware

Let's hope that in the near future will appear: D

Driver to work with bootloader (including for firmware)

USB_Driver_rk29.zip(199.04 KB)

пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ (пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ) пїЅпїЅпїЅ пїЅпїЅ:

• Windows 2000 x86
  
• Windows XP x86
  
• Windows Vista x86
  
• Windows Vista x64 AMD
  
• Windows 7 x86
  
• Windows 7 x64 AMD
  

download

In the archive with firmware only for XP x86 was.
If the program still fails to establish a connection with your device on Windows 7 x32 after installing the driver, try manually replacing the driver with the driver for Windows XP x32.

Instructions on firmware

1. Read the paragraph "Attention!"
2. Download the firmware provided by the manufacturer and unpack the archive
3. Run as administrator RKAndroidTool.exe (in the folder with the firmware)
The program will show that the device is not connected.


4. Install the driver. If you have already installed the driver on your computer, go to step 5.

4.1 Download the archive with the drivers and unpack it.
USB_Driver_rk29.zip(199.04 KB)


4.2 Turn off the device. Then boot must be switched to software update mode. To do this, hold down the M (Menu) button on the side of the device and, without releasing it, insert the USB cable. The computer will detect a new device and warn you that it could not find a driver for it. (If atthe firstthe driver was installed automatically, then I would advise you to rearrange it manually)


4.3 Click "Start - Control Panel - Device Manager". There you will see an unknown device.


4.4 To make sure that this is our device, open the properties of "unknown equipment" and in the opened window select the "Details" tab.
Check the equipment ID value.


4.5 Then go to the "Driver" tab and click the "Update" button. Next, select "Search for drivers on this computer." Click the "Browse" button, find the unzipped driver folder and click "Next."
Windows will start searching and installing the driver. If the system asks whether to install the software, click "Install"


4.6 Windows will notify you that the driver installation is complete.


In the program window of the flasher we will see the inscription that there is a USB connection


If the program still fails to establish a connection with your device on Windows 7 x32 after installing the driver, try manually replacing the driver with the driver for Windows XP x32.

5. Now we proceed to the firmware itself.
5.1 Turn off the device. Then boot must be switched to software update mode. To do this, hold down the M (Menu) button on the side of the device and, without releasing it, insert the USB cable. The computer will detect the device.
5.2 In the program window of the flasherremove all checkboxes, except for Boot, Kernel, System, Misc (if you are flashing custom firmware, specify the path to the new boot, kernel and system manually)
If you want to leave the system settings and installed programs after the firmware, then remove the check mark against the Misc. But I advise you to reset the system settings and format it after any firmware (to put it simply, this file in the device will make Hard Reset make it)
Do not change the addresses in the offset fields !!!


5.3 Press the "Run" button and the firmware process begins.


5.4 Upon completion of the firmware in the status window, we will see "ok"


5.5 The device will reboot. It is advisable to disconnect the USB cable after the Oysters T8 screensaver appears.

6. After flashing this way, the installed programs and all settings are saved (the userdata section is not formatted) if the Misc file is not flashed.
If we are flashing the same firmware version, then we can use the programs and settings remaining from the previous firmware.
If we are flashing a new version or we want a "clean" system, then after the firmware we goSettings - Privacy - Reset settings, or with the firmware at the same time, we also flash the Misc file

Problems during and after the firmware

Question: I have flashed Oysters T8 firmware from Oysters T8 A4 (or vice versa).
- Nothing wrong. The boot-loader of these devices is similar, so both work correctly on both devices. You need to download the firmware from your device model and flash it again.

Question: I installed the driver for Windows 7 x32, but the firmware program says that there is no connection with the device.
- In this case, try installing the driver manually on Windows 7 x32 from Windows XP x32.

Question: I forgot the unlock code (the device is locked), what should I do ?.
- If the device is locked and you need to do a full reset of the device, then you need to flash the filemiscinto the device. It is necessary to flash according to the instructions, but all the checkboxes must be removed and only one left, respectively, that which is againstmisc

screenshot

Tony_AU
Copying the material only with the mention of the author and a link to the topic onsavagemessiahzine.com

There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through the "Complaint" button under the messages to which you want to add links.

Post has been editedOXALIS - 15.06.16, 23:09

Reason for editing: Updated firmware instructions. Added a section. Added Oysters T8 A4

[Tony_AU]

Reflections:

About flasher
firmware \ RKAndroid_v1.29 \ RKAndroidTool.exe

The paths to the images with the loadars, the system, the kernel and the firmware for the firmware, which the program writes by default, are in:
firmware \ RKAndroid_v1.29 \ setting.ini

[FLASH]
Loader_Path = .. \ rockdev \ RK29xxLoader (L) _DDR3_400Mhz_V1.66.bin
Parameter_Path = .. \ rockdev \ parameter
Misc_Path = .. \ rockdev \ Image \ misc.img
Kernel_Path = .. \ rockdev \ Image \ kernel.img
Boot_Path = .. \ rockdev \ Image \ boot.img
Recovery_Path = .. \ rockdev \ Image \ recovery.img
System_Path = .. \ rockdev \ Image \ system.img
Backup_Path = .. \ rockdev \ Image \ update.img

The default settings for the location of images in the address space are in the same file:

Parameter_Offset = 0x00000000
Misc_Offset =
Kernel_Offset =
Boot_Offset =
Recovery_Offset =
System_Offset =
Backup_Offset =

Also here are the paths to the images for other methods of working with memory and location in the address space:

[NFS]
_Offset
[RAM]
_Offset

If the configuration file does not contain the values ​​of the location of images in the address space (the entry point 0x00000000 must be specified), then in the program window you can select individual settings in the Parameter_Path window.
In the firmware directory v2.10.00 firmware \ rockdev \ there are already ready options for settings:
parameter
parameter (user_512 system_512 backup_400)
parameter (user_1024 system_512 backup_400)
parameter.bak

These settings determine the distribution of internal memory between the system and the user (available memory for storing data \ installing programs \ caches and so on) and the size of the system image (the most significant variable).

parameter - standard values
The parameter (user_512 system_512 backup_400) and parameter (user_1024 system_512 backup_400) is clear from the name, although there are much more parameters in the settings file:

FIRMWARE_VER: 0.2.3
MACHINE_MODEL: rk29sdk
MACHINE_ID: 007
MANUFACTURER: RK29SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 2929
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#COMBINATION_KEY: 0.6, A, 1.0
CMDLINE: console = ttyS1,115200n8n androidboot.console = ttyS1 init = / init

initrd = 0x62000000,0x800000 mtdparts = rk29xxnand:
0x00002000 @ 0x00002000 (misc),
0x00004000 @ 0x00004000 (kernel),
0x00008000 @ 0x00008000 (boot),
0x00008000 @ 0x00010000 (recovery),
0x000C8000 @ 0x00018000 (backup),
0x0003a000 @ 0x000E0000 (cache),
0x00200000 @ 0x0011a000 (userdata),
0x00002000 @ 0x0031a000 (kpanic),
0x00100000 @ 0x0031c000 (system),
- @ 0x0041c000 (user)

As you may have guessed, these tsiforki mean the following:

that is, if we cut out unnecessary software from the system, then in this way we increase, for example, user memory for data storage.
In more detail, what is responsible for what, and what you need to know for a simple user when choosing firmware, I’ll tell you later.

By the way, there are 2 versions of the bootloader in the firmware. Since by default the flasher chooses the boot loader 1.66, I suspect that we have 1.66 flashed. But in the folder with the code the downloader 2.08 also lies
This is not a bootloader, which loads the android and even its kernel, it is a bootloader that manages other bootloaders and primitive inits. glands, so to say "bios". So with its firmware, nothing will change for you (most likely). Unfortunately, the Chinese file with a list of version changes of the bootloaders died when the encoding was lost.

Post has been editedTony_AU - 13.05.12, 13:41

[Tony_AU]

recalculated hex values ​​into our native megabytes and arranged in order.
Since I collected the firmware only on win mob, I would venture to suggest that by comparing these two pictures, you can free up 1 gigabyte of free space by simply shifting the images in the address space!


Who knows android, fix me. Just too lazy to read a lot of smart books: blush:

[gferru]

Why such a strange flashing? Tulzom not sew? I thought all droids should be configured = (

Or is this a version of the tool?

Post has been editedgferru - 14.05.12, 07:49

[Tony_AU]

gferru,
The fact is that this is my first android, before that I had all versions of Windows. All that I am writing here, all from the experience of vyndovs, for some kind of manual, conducting a parallel with our model and, in many ways, even to me not understandable factors)))
If you want to help, I will be glad.
At this point, this program can be used to flash all the images in parts, that is, the kernel, rekoveri, backup, wasps, etc., as well as this utility can flash at its place a loader, which can not be stitched with standardized utilities, Secondly, it is clearly not in the 8-gigabyte nand!

What toulouse are you talking about?

but, yes, I forgot to add, as I wrote above, this Toulouse, though it looks nekosist, but can allocate memory, and using this, according to my last modest calculations, up to 2 gigabytes of memory for storing data can be released.

Post has been editedTony_AU - 14.05.12, 13:27

[gferru]

Sorry, I can help more than I can, I'm a current user, just all previous devices I usually throughTools_1.4I stitched, somewhere, even in Russian, I saw this program ....

[Tony_AU]

gferru,
I will come home, I will look better. We must read about it. Namely, how it breaks the nand, and what addresses it writes to, and whether the driver will work correctly with it.

[Tony_AU]

The good news.
Now with the help of the kitchen, I decoded, "translated into ext and extracted" the firmware from system.img to the version in which you can edit it: sveta:

[gferru]

we are morally with you =)

[gferru]

how is it going? it turns out that the thread?

[Tony_AU]

gferru,
Today, at work, it turned out to pack the system in CRAMFS, but the program assembles the roofing felts, which I doubt, the roofing felts, it really was packaged in ext3. If ext3 is good, root will work, otherwise a partition cannot be mounted for writing in CRAMFS.

Plus, the whole RK29xxImageTools is mowing.
if it disassembles the container with partitions and loaders, it correctly parses it. So, if you don’t change anything, but you can immediately assemble it, the image is smaller in size than it was, and the same set of programs can no longer disassemble it.

Well, it does not matter.
Today, a familiar romodel should share the name of the program, which he collected in the ext3 section.
In the meantime, I’ll try to come back from work, build a system in CRAMFS and flash a device for them. But for some reason I am sure that the firmware will not start up at 100,500%, because there is likely ext3, contrary to all canons: D

Post has been editedTony_AU - 16.05.12, 14:23

[ivanovvi]

HOW SUCCESSFUL IN ONE ----- BUT VERY CARRIER: blush:

[Tony_AU]

ivanovvi,
so far, the weekend, shalyki, beer, girls: D

[Tony_AU]

Well, it all happened. There is still a lot of work ahead, but a start is needed!

[gferru]

Graz !!! waiting for stable build = P

[<_Stalker | 46_>]

Comrades, and if we have a twin brother in the face of CUBE, then the firmware from it should safely sit on the T8 ??http://www.cube-tablet.com/news/cube-u10gt...ware-android-4/I found an update to 4.0 on the off site CUBE.

Post has been edited<_Stalker | 46_> - 23.05.12, 11:16

[Tony_AU]

<_Stalker | 46_>,
There is no need to go far for updates, and there are 4pd.

then the firmware from it should safely sit on the T8 ??

first is build.prop
secondly, if the firmware is in one file, then an alien loader will turn your device into a brick
in the third, if Kramfs filesystem is used, the kernel simply will not accept the system
in the fourth, most likely there are minor differences in the gland, which means that if you close your eyes to the first three points, then not all “functions” will work
Fifth is the screen resolution, and in particular the DPI

PS.: And by reference, if I'm not mistaken, the update for the first version of the tablet, and in it, instead of a modem, is a USB port

Post has been editedTony_AU - 23.05.12, 18:30

[<_Stalker | 46_>]

Yes, I already understood that this is not a good idea, thanks to Tony AU for the detailed answer, I will wait for a stable version of your firmware! : yes2:

[Tony_AU]

People, do you install many programs not in the phone / on the flash card?
is it worth to increase the user memory at the expense of all these official?

Post has been editedTony_AU - 24.05.12, 10:45

[gferru]

gig under the program you can do? =)

[<_Stalker | 46_>]

I put all the programs on the tablet, only the file on the flash drive, and I am for increasing the memory on the device!