teXet TM-7025 - Firmware | Bmorn V11 / GoClever TAB A73 / benton BT-M740
under the messages to which you want to add links. Manual about editing firmware for LiveSuit format * .img
The manual will be better for errors and visual design.
Who are too lazy to read the video there:http://youtu.be/8L-NklTuhf8
Program which we will need:
imgRePacker
ext4 Utils -
ext4_utils_savagemessiahzine.com(Linux only) .zip (56.71 KB)
So do we need such a system Linux OS. I usedUbuntu
It can be set via the virtual machineVirtualbox or similar.
Note: If you use a virtual machine, check whether your processor supports virtualization technology. (ForAMD virtualization (AMD-V) for the Intel VT (Intel Virtualization Technology) can be found with the help of the program CPU-Z CPUID )
1. unpack the * .img
DownloadingimgRePacker , Unpack; a folder with the program is also desirable to throw the firmware that will work.
Runrunner.bat and we see this window:
Drag the firmware filenazvanie_proshivki.img in the window. Note that the command line can not perceive the Cyrillic alphabet and spaces, so if you have a path to the file has data symbols, the path must be enclosed in quotation marks ( " C: \ New Folder \ name proshivki.img " ), Press Enter, enter an option, if you want (you can read in the post in the program) with a full list of options. If the option is not needed yet we press Enter again. We wait and get unpacked firmware. All firmware files will be in the folder nazvanie_proshivki.dump next to the original * .img
When disassembling the firmware of different tablets, the composition of the output folder with the unpacked firmware will be different from the example of me. I judged the firmware for TeXet TM-7025, if you disassemble the firmware from another device, then look for a file* system.fex it should be the largest in size. To edit the markup: * Sys * _config.fex
At this stage, you can specify the layout of sections through a filesys_config.fex
If you change the partition size, be careful not to make the size of throughsys_config.fex less than iso files in _iso folder, you can simply not start flashing.
2. Go to the unpack System
To continue the work we need to Linux, I use Ubuntu.
First you need to stand the required packages for building software, the kernel from source code, Android.
If suddenly something is not installed, then carefully read what we write terminal, usually offer to replace outdated packages at the same time will show which packages need to be replaced with new ones. All names will be the same in the terminal.
After installing the package we need utilityext4 Utils .
It is also desirable to set up shared folders, if you are working through a virtual machine.
Now we need to connect Ubuntu shared folder. Open Terminal (we press on the top left button in the search bar write "Teriminal") and write the following command:
sudo mount -t vboxsf System / media / sf_System - after vboxsf specify the name of the folder in which we asked the virtual machine configuration (System), followed by the path of the folder where it will be installed.
And so in the Home folder, create a folder:Unpack
Rewrite it in utilityext4 Utils
Compile utility for convertingext4_utils NIX-in system with a console command make . To do this, open a terminal and set the path to the folder roman @ roman-VirtualBox: ~ $ / home / roman / Unpack / ext4_utils and through the gap write make . We are waiting for a few seconds after we get compiling a set of tools, including simg2img and mkuserimg.sh .
Further in Ubuntu go to the folder with the unpacked firmware, and find there a filesystem.fex rewrite it in the folder with the utility ext4 Utils And rename the file to system.img
Now open a terminal and foot:
./simg2img system.img output.img - for the proper performance of the team you should be in the folder with the utility ext4 Utils (example: roman @ roman-VirtualBox: ~ / Unpack / ext4_utils $ ./simg2img system.img output.img )
On the way out we gotoutput.img with which we will work. This file is an ordinary way and drive on this it should be easy to connect to the system to do this, perform the following oparatsii in a terminal:
sudo mkdir / media / system - this team, we create a system folder
sudo mount -o loop output.img / media / system - this command we mount our disk image (output.img) in the system folder.
Then go to the folder/ Media / system and we see our entire file system Android. So as online disk image has an attribute "Read Only", and any changes we can not make, then open a terminal and type the following:
sudo nautilus - We will launch the built-in file manager as administrator, then in the open window to the left, displaying the device select our a connected image, right-click Properties, the tab right owner: your_username access set: create and delete files on the "Edit rights attachments ", and there, too, are putting" Reading and Writing "and" Creating and deleting files "select all the folders and files and copy them to the home folder. Check that all files were in place for this purpose compare the number of files and the size of the image and your new folder. They should match.
3. Assembly.
Once you have made any changes to the system of the future, it is necessary to assemble the whole thing back. And so we go.
Copy finished folder in Ubuntu If you have worked in Windows, if you have worked in Ubuntu then copy or move it to your home folder. (In principle, these actions are not important, as long as you know where you have a folder with the retrofit system,)
The write terminal (we should be in the folder with the utilityext4 Utils ):
./mkuserimg.sh -s / Vasha_modifitsirovannaya papka_s_faylami ./Vash_novyy_system.img ext4 ./temp 400M
400M - Indicates the size of the disk image of the new system.
Always properly specify this option, because if you create a disk image, such as 1GB, and the actual size of your modified folder is 300MB, 700MB is simply not as not to be involved in the device. you need also will change partition size in filesys_config.fex Otherwise you can get the firmware does not work.
Therefore, first determine the size of the modified list, and rounded to the nearest hundred. (Example folder takes 240Mb ->300MB; 375Mb ->500 MB)
In principle, if you do not want to bother with the size, you can simply specify the partition sizesystem from file sys_config.fex
Resulting fileVash_novyy_system.img rename to Vash_novyy_system.fex.iso and copy it to a folder with the replacement of _iso in the folder with the unpacked firmware.
RunimgRePacker drag the folder "Nazvanie_vashey_proshivki.img.dump" in the program window. (Watch out for syntax) Press Enter and get the new firmware.
You can be tested!
You can also read:ONDA Vi10 Elite - Firmware
Post has been editedAuta - 16.05.15, 08:00
The manual will be better for errors and visual design.
Who are too lazy to read the video there:http://youtu.be/8L-NklTuhf8
Program which we will need:
imgRePacker
ext4 Utils -
ext4_utils_savagemessiahzine.com(Linux only) .zip (56.71 KB) So do we need such a system Linux OS. I usedUbuntu
It can be set via the virtual machineVirtualbox or similar.
Note: If you use a virtual machine, check whether your processor supports virtualization technology. (ForAMD virtualization (AMD-V) for the Intel VT (Intel Virtualization Technology) can be found with the help of the program CPU-Z CPUID )
1. unpack the * .img
DownloadingimgRePacker , Unpack; a folder with the program is also desirable to throw the firmware that will work.
Runrunner.bat and we see this window:
ImgRePacer in action
 |
When disassembling the firmware of different tablets, the composition of the output folder with the unpacked firmware will be different from the example of me. I judged the firmware for TeXet TM-7025, if you disassemble the firmware from another device, then look for a file* system.fex it should be the largest in size. To edit the markup: * Sys * _config.fex
The list of files in a folder
 |
How to change the layout
the red line in the original is missing, here they are for explanation.
Finds the following lines:
[Part_num]
num = 8
;------------------------------>nanda, known as bootfs before, includes boot.axf u-boot.bin etc ... -What section
[Partition0]
class_name = DISK
name = bootloader -section title
size_hi = 0
size_lo = 16384 -Section size
user_type = 0
ro = 0
;------------------------------>nandb, enviroment for u-boot
[Partition1]
class_name = DISK
name = env
size_hi = 0
size_lo = 2048
user_type = 0
ro = 0
;------------------------------>nandc, kernel and ramdisk
[Partition2]
class_name = DISK
name = boot
size_hi = 0
size_lo = 32768
user_type = 0
ro = 0
;------------------------------>nandd, android real rootfs- Section for the system
[Partition3]
class_name = DISK
name = system
size_hi = 0
size_lo = 307200
user_type = 2
ro = 0
;------------------------------>nande, user data- Data Section, where applications are installed
[Partition4]
class_name = DISK
name = data
size_hi = 0
size_lo = 1065366- The size of this section 1GB
user_type = 2
ro = 0
;------------------------------>nandf, misc
[Partition5]
class_name = DISK
name = misc
size_hi = 0
size_lo = 1024
user_type = 2
ro = 0
;------------------------------>nandg, for recovery
[Partition6]
class_name = DISK
name = recovery
size_hi = 0
size_lo = 32768
user_type = 2
ro = 0
;------------------------------>nandh, android app cache
[Partition7]
class_name = DISK
name = cache
size_hi = 0
size_lo = 200088
user_type = 2
ro = 0
Finds the following lines:
[Part_num]
num = 8
;------------------------------>nanda, known as bootfs before, includes boot.axf u-boot.bin etc ... -What section
[Partition0]
class_name = DISK
name = bootloader -section title
size_hi = 0
size_lo = 16384 -Section size
user_type = 0
ro = 0
;------------------------------>nandb, enviroment for u-boot
[Partition1]
class_name = DISK
name = env
size_hi = 0
size_lo = 2048
user_type = 0
ro = 0
;------------------------------>nandc, kernel and ramdisk
[Partition2]
class_name = DISK
name = boot
size_hi = 0
size_lo = 32768
user_type = 0
ro = 0
;------------------------------>nandd, android real rootfs- Section for the system
[Partition3]
class_name = DISK
name = system
size_hi = 0
size_lo = 307200
user_type = 2
ro = 0
;------------------------------>nande, user data- Data Section, where applications are installed
[Partition4]
class_name = DISK
name = data
size_hi = 0
size_lo = 1065366- The size of this section 1GB
user_type = 2
ro = 0
;------------------------------>nandf, misc
[Partition5]
class_name = DISK
name = misc
size_hi = 0
size_lo = 1024
user_type = 2
ro = 0
;------------------------------>nandg, for recovery
[Partition6]
class_name = DISK
name = recovery
size_hi = 0
size_lo = 32768
user_type = 2
ro = 0
;------------------------------>nandh, android app cache
[Partition7]
class_name = DISK
name = cache
size_hi = 0
size_lo = 200088
user_type = 2
ro = 0
Translation example
The coefficient for the correct translation of partition size
0,98424038461538461538461538461538
How to translate? Need size to 1GB = 1,024 MB = 1,048,576 * 1024 KB / 0,98424038461538461538461538461538 = 1,065,365.754535418763005441525581 and rounded up to the nearest whole number = 1065366
For a more accurate calculation of translating everything into bytes, and perform actions with them.
307200 kb - system partition size to 295 mb
1065366 kb - data partition size to 1024 MB
200088 kb- cashe size partition 192 mb
0,98424038461538461538461538461538
How to translate? Need size to 1GB = 1,024 MB = 1,048,576 * 1024 KB / 0,98424038461538461538461538461538 = 1,065,365.754535418763005441525581 and rounded up to the nearest whole number = 1065366
For a more accurate calculation of translating everything into bytes, and perform actions with them.
307200 kb - system partition size to 295 mb
1065366 kb - data partition size to 1024 MB
200088 kb- cashe size partition 192 mb
2. Go to the unpack System
To continue the work we need to Linux, I use Ubuntu.
First you need to stand the required packages for building software, the kernel from source code, Android.
So, put all in one command:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc
After installing the package we need utilityext4 Utils .
It is also desirable to set up shared folders, if you are working through a virtual machine.
Setting up shared folders on the example of VirtualBox
We choose the right machine, we pressCustomize - Shared folders - We press on the file with a plus sign - Specify the path to the folder with the unpacked firmware and utilities - In the field "Folder Name" specify the name of the folder for the guest. Name is better than dial Latin, and her short, as Ubuntu will have everything to gain hands. (Example: System) Just tick the Auto-hook up.
More complete instructions can be found hereShared folders for Virtualbox
More complete instructions can be found hereShared folders for Virtualbox
sudo mount -t vboxsf System / media / sf_System - after vboxsf specify the name of the folder in which we asked the virtual machine configuration (System), followed by the path of the folder where it will be installed.
And so in the Home folder, create a folder:Unpack
Rewrite it in utilityext4 Utils
Compile utility for convertingext4_utils NIX-in system with a console command make . To do this, open a terminal and set the path to the folder roman @ roman-VirtualBox: ~ $ / home / roman / Unpack / ext4_utils and through the gap write make . We are waiting for a few seconds after we get compiling a set of tools, including simg2img and mkuserimg.sh .
Further in Ubuntu go to the folder with the unpacked firmware, and find there a filesystem.fex rewrite it in the folder with the utility ext4 Utils And rename the file to system.img
Now open a terminal and foot:
./simg2img system.img output.img - for the proper performance of the team you should be in the folder with the utility ext4 Utils (example: roman @ roman-VirtualBox: ~ / Unpack / ext4_utils $ ./simg2img system.img output.img )
On the way out we gotoutput.img with which we will work. This file is an ordinary way and drive on this it should be easy to connect to the system to do this, perform the following oparatsii in a terminal:
sudo mkdir / media / system - this team, we create a system folder
sudo mount -o loop output.img / media / system - this command we mount our disk image (output.img) in the system folder.
Then go to the folder/ Media / system and we see our entire file system Android. So as online disk image has an attribute "Read Only", and any changes we can not make, then open a terminal and type the following:
sudo nautilus - We will launch the built-in file manager as administrator, then in the open window to the left, displaying the device select our a connected image, right-click Properties, the tab right owner: your_username access set: create and delete files on the "Edit rights attachments ", and there, too, are putting" Reading and Writing "and" Creating and deleting files "select all the folders and files and copy them to the home folder. Check that all files were in place for this purpose compare the number of files and the size of the image and your new folder. They should match.
3. Assembly.
Once you have made any changes to the system of the future, it is necessary to assemble the whole thing back. And so we go.
Copy finished folder in Ubuntu If you have worked in Windows, if you have worked in Ubuntu then copy or move it to your home folder. (In principle, these actions are not important, as long as you know where you have a folder with the retrofit system,)
The write terminal (we should be in the folder with the utilityext4 Utils ):
./mkuserimg.sh -s / Vasha_modifitsirovannaya papka_s_faylami ./Vash_novyy_system.img ext4 ./temp 400M
400M - Indicates the size of the disk image of the new system.
Always properly specify this option, because if you create a disk image, such as 1GB, and the actual size of your modified folder is 300MB, 700MB is simply not as not to be involved in the device. you need also will change partition size in filesys_config.fex Otherwise you can get the firmware does not work.
Therefore, first determine the size of the modified list, and rounded to the nearest hundred. (Example folder takes 240Mb ->300MB; 375Mb ->500 MB)
In principle, if you do not want to bother with the size, you can simply specify the partition sizesystem from file sys_config.fex
Resulting fileVash_novyy_system.img rename to Vash_novyy_system.fex.iso and copy it to a folder with the replacement of _iso in the folder with the unpacked firmware.
RunimgRePacker drag the folder "Nazvanie_vashey_proshivki.img.dump" in the program window. (Watch out for syntax) Press Enter and get the new firmware.
You can be tested!
You can also read:ONDA Vi10 Elite - Firmware
Post has been editedAuta - 16.05.15, 08:00
Reason for editing: additional
There was a question to experts. There are many drivers for the controller to stitch ft5306, but for some reason there is no firmware ft5306XXXXX-800x480.bin,
There are the following firmware .bin
ft5206-sc3013-1024X600.bin
ft5206-sc3017-1024X600.bin
ft5206-sc3037-800X480.bin
ft5206-sc3071-800X480.bin
ft5206-sc3073-1024X600.bin
ft5306-sc3056-1024X768.bin
ft5306-sc3058-1024X768.bin
ft5406-lanhuibang-1024X768.bin
ft5406-sc3039-800X600.bin
ft5406-sc3051b-1024X768.bin
ft5406-sc3051b-800X600.bin
ft5406-sc3052-1024X768.bin
ft5406_MID8042_800X600.bin
So how .bin to flash controller? Or, more importantly, is to permit matched?
And what kind of identification (sc3013, sc3017, and so on), controller stitch my devaysa FT5306DE4.
!!! Danger: Do not ustanvlivat !!!
For example, post the file for CWMadvanced2_modules.zip(9.84 MB)
!!! Danger: Do not ustanvlivat, you can not get a working touch !!!
Please explain how it rabotet. Whether the controller identification takes place with subsequent firmware?
The archive contains and touchscreen driver. The code is not strong, so please help.
How it works?
Controller Specification FT5306DE4 in pdf file
FT5306DE4.pdf(765.07 KB)
Post has been editedVerton - 10.02.14, 19:49
There are the following firmware .bin
ft5206-sc3013-1024X600.bin
ft5206-sc3017-1024X600.bin
ft5206-sc3037-800X480.bin
ft5206-sc3071-800X480.bin
ft5206-sc3073-1024X600.bin
ft5306-sc3056-1024X768.bin
ft5306-sc3058-1024X768.bin
ft5406-lanhuibang-1024X768.bin
ft5406-sc3039-800X600.bin
ft5406-sc3051b-1024X768.bin
ft5406-sc3051b-800X600.bin
ft5406-sc3052-1024X768.bin
ft5406_MID8042_800X600.bin
So how .bin to flash controller? Or, more importantly, is to permit matched?
And what kind of identification (sc3013, sc3017, and so on), controller stitch my devaysa FT5306DE4.
!!! Danger: Do not ustanvlivat !!!
For example, post the file for CWM
advanced2_modules.zip(9.84 MB)!!! Danger: Do not ustanvlivat, you can not get a working touch !!!
Please explain how it rabotet. Whether the controller identification takes place with subsequent firmware?
The archive contains and touchscreen driver. The code is not strong, so please help.
How it works?
Controller Specification FT5306DE4 in pdf file
FT5306DE4.pdf(765.07 KB)Post has been editedVerton - 10.02.14, 19:49
FiliN271,
Based lsmod module stitch ft5x_ts 44,658 0 - Live 0xbf000000
What, then, explain that when the tablet is not an insertion of one of the native firmware, touch stops working properly? It is found in many users, and has a native iOS firmware does not solve the problem.
In particular I have failed after installing TWRP, and no rollback of the backup or preproshivka not solve the problem. Established the truth is not out of ADB, and unpacking recovery.img in / sdcard and writing in the tablet terminal emulatorcat / sdcard /recovery.img>/ Dev / block / nandg; sync
To view spread that file with TWRP
Attention !!! Do not install !!! Lead to malfunction stitch.
TWRP.rar(6.09 MB)
What code is in recovery.img or installation script has led to disastrous results? And as it is now correct?
So far no one has managed to do so !!!
P.S: There is an assumption that rekaveri designed for Android 4.0, and I have at that time was 4.1
Post has been editedVerton - 11.02.14, 09:23
Based lsmod module stitch ft5x_ts 44,658 0 - Live 0xbf000000
What, then, explain that when the tablet is not an insertion of one of the native firmware, touch stops working properly? It is found in many users, and has a native iOS firmware does not solve the problem.
In particular I have failed after installing TWRP, and no rollback of the backup or preproshivka not solve the problem. Established the truth is not out of ADB, and unpacking recovery.img in / sdcard and writing in the tablet terminal emulatorcat / sdcard /recovery.img>/ Dev / block / nandg; sync
To view spread that file with TWRP
Attention !!! Do not install !!! Lead to malfunction stitch.
TWRP.rar(6.09 MB)What code is in recovery.img or installation script has led to disastrous results? And as it is now correct?
So far no one has managed to do so !!!
P.S: There is an assumption that rekaveri designed for Android 4.0, and I have at that time was 4.1
Post has been editedVerton - 11.02.14, 09:23
Verton @ 11.02.2014, 10:00
P.S: There is an assumption that rekaveri designed for Android 4.0, and I have at that time was 4.1
Recovery is for firmware 4.0 and above. 2.h.h on this and other recovery does not set, they simply will not run
Auta, I know it. But I imell due to the core after all, 4.0 and 4.1 are different. Maybe because of that there was a failure to stitch?
Auta @ 11.02.2014, 12:15
In my stitch failure occurred in the past when there was only the firmware 4.0, but put it on another plate.
Unpacking Boot.img and Recovery.img
Be very careful when editing Boot.img, you can get the firmware does not work!
I will not go into specific details, everything is very clear. All operations are performed from the Linux
Create a folder in your home folderUnpack in her folder boot in this folder rewrite boot.fex and rename it to boot.img
All commands are entered in the terminal.
Parse boot.img:
The first thing to do is move on to the boot folder
cd Unpack / boot
Run the script split_bootimg.pl, kory we take out of the file boot.img file 2: boot.img-ramdisk.gz, boot.img-kernel
perl split_bootimg.pl boot.img
Create a directory ramdisk, in which we raspakum our archive boot.img-ramdisk.gz
mkdir ramdisk
Let's move on to the directory ramdisk
cd ramdisk
Unpack boot.img-ramdisk.gz
gzip -dc ../boot.img-ramdisk.gz | cpio -i
Assembly:
Assembly:
Go to the folder up:
cd ..
Create a file folder ramdisk:
./mkbootfs ramdisk | gzip>ramdisk-new.gz
Completing the assembly boot.img
./mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console = ttyS0,115200 rw init = / init loglevel = 8' -o new-boot.img
Our new boot.img ready to copy it in the folder with the unpacked firmware, hanged himself with the old boot.img
Also most can be done with recovery.img
utilsbootimg.zip(26.71 KB)
Post has been editedAuta - 11.02.14, 22:27
Be very careful when editing Boot.img, you can get the firmware does not work!
I will not go into specific details, everything is very clear. All operations are performed from the Linux
Create a folder in your home folderUnpack in her folder boot in this folder rewrite boot.fex and rename it to boot.img
All commands are entered in the terminal.
Parse boot.img:
The first thing to do is move on to the boot folder
cd Unpack / boot
Run the script split_bootimg.pl, kory we take out of the file boot.img file 2: boot.img-ramdisk.gz, boot.img-kernel
perl split_bootimg.pl boot.img
Create a directory ramdisk, in which we raspakum our archive boot.img-ramdisk.gz
mkdir ramdisk
Let's move on to the directory ramdisk
cd ramdisk
Unpack boot.img-ramdisk.gz
gzip -dc ../boot.img-ramdisk.gz | cpio -i
Assembly:
Assembly:
Go to the folder up:
cd ..
Create a file folder ramdisk:
./mkbootfs ramdisk | gzip>ramdisk-new.gz
Completing the assembly boot.img
./mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --cmdline 'console = ttyS0,115200 rw init = / init loglevel = 8' -o new-boot.img
Our new boot.img ready to copy it in the folder with the unpacked firmware, hanged himself with the old boot.img
Also most can be done with recovery.img
utilsbootimg.zip(26.71 KB)Post has been editedAuta - 11.02.14, 22:27
Verton @ 11.02.2014, 14:17
Probably just a coincidence with the controller fails,
Maybe module could damage the controller to stitch, but it's also something of a fantasy ...
Changed its touchscreen goklevera to touch on epada 705. The touch is operating normally. then the problem is still in the touchscreen or controller, although it is possible and in the piping (smd components on the loop). Yet I think we can assume that the wrong module may damage the controller, but that's exactly what happens ...?
P.S: Checked smd elements without watering, there are 4 capacitors, a resistor 1, 1 and 1 diode circuit, then still a problem in the controller, it is interesting they are sold already stitched or still need to sew?
Post has been editedVerton - 11.02.14, 21:25
P.S: Checked smd elements without watering, there are 4 capacitors, a resistor 1, 1 and 1 diode circuit, then still a problem in the controller, it is interesting they are sold already stitched or still need to sew?
Post has been editedVerton - 11.02.14, 21:25
Verton,
He can not damage it.But no ... Read herethis, The most interesting was ... I sewed a tablet than not get, then the controller sewn tightly and the usual flashing of the plancha to kill some of its parts is unable (great indestructibility allwinner'a tablets) ...
Post has been editedFiliN271 - 11.02.14, 21:41
Post has been editedFiliN271 - 11.02.14, 21:41
guklever on the A73 can be put Stable version Android 4.1.2 Cyanogenmod 10 (Build - 20,140,107) (from 30/01/2014) through a standard rekaveri?
Friends. A question. I put 4.1.2 on Huragan CM10. Everything is perfect, but with trouble viewing the video. I understand the hardware processing is not supported? MX Player brake at 720p, though off earlier. firmware with built wonderful player all flew even at 1080p. Is there any way to put a player on this request?http: //forum.xda-devel...owthread.php t = 2162905?- that I found that. It should work right? I replaced using Root Explorer and put all the necessary rights, but when you start a video crash with him. What to do? PS: The device Texet TM-7025.
Lord ask this question, but there is still the unit's serial number starts with 13, the bucket should 4.0.4. Well, everything would be fine but it is not like all the blue tooth, whether there is a patch to use it. And then sew like that there is no desire, and with the performance of the informal the last I do not look all right, plus the latest in a cap 4.0.3 appears
Photon9 @ 12.02.2014, 21:31
Well, everything would be fine but it is not like all the blue tooth
I will not, put the firmware on Huragane there should operate Bluetooth
Wanteded @ 12.02.2014, 20:28
though off earlier. firmware with built wonderful player all flew even at 1080p. Is there any way to put a player on this request?
Here is the official firmware from Gallary application:
Gallery2.zip(1.61 MB)Post has been editedAuta - 13.02.14, 22:12
Auta @ 12.02.2014, 19:45
I will not, put the firmware on Huragane there should operate Bluetooth
With tachem them all right? And what about the seriynikom or 13xxxxxxxx the same as 12xxxxxxxx? I would not want to store the bricks)
Photon9 @ 12.02.2014, 22:42
And what about the seriynikom or 13xxxxxxxx the same as 12xxxxxxxx?
In fact, you can see how rare 3 audit as atGoClever TAB A73And in this case it is better not to experiment, if you do not have the official firmware from Texeta for your audit.
It is clear, then I will not bother with and get along with a USB cable
ZY By the way as a serial number (S / N 1310009867) written Rev.2
Post has been editedPhoton9 - 12.02.14, 23:51
ZY By the way as a serial number (S / N 1310009867) written Rev.2
Post has been editedPhoton9 - 12.02.14, 23:51
The board of goklevera kill jobs and a new stitch. So somewhere down there is wrong files.
As you know, in our devaysakh we have 9 local drives.
Question to experts: What are the wrong disk files?
Let me remind you that the problem occurs when you install TWRP rekaveri another devaysa on proce A10.
Installing native rekaveri problem not solved.
Post has been editedVerton - 14.02.14, 18:44
As you know, in our devaysakh we have 9 local drives.
Question to experts: What are the wrong disk files?
Let me remind you that the problem occurs when you install TWRP rekaveri another devaysa on proce A10.
Installing native rekaveri problem not solved.
Post has been editedVerton - 14.02.14, 18:44
Verton,
Who 9, one 8, one 12 and even 13 sections ... I was 9, is now already 13, then as the firmware will.
Post has been editedFiliN271 - 14.02.14, 19:07
Who 9, one 8, one 12 and even 13 sections ... I was 9, is now already 13, then as the firmware will.
Post has been editedFiliN271 - 14.02.14, 19:07
Verton @ 14.02.2014, 19:39
Let me remind you that the problem occurs when you install TWRP rekaveri another devaysa
If you set the Recovery in theory should be placed in the section recovery.
And by the way what way you put TWRP, a tablet or a PC?
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement