Teclast X80 Pro - Discussion | [tabletpc] Windows 10 + Android 5.1 | 8 '' | Intel Cherry Trail
Poll
Do you have problems with "falling off" memory cards?
Yes (E3E6) [ 64 ] ** [21,77%]
Yes (E3E7) [ 65 ] ** [22,11%]
No (E3E6) [ 77 ] ** [26,19%]
No (E3E7) [ 88 ] ** [29,93%]
Do you have problems with Wi-fi reception?
Yes (E3E6) [ 57 ] ** [19,39%]
Yes (E3E7) [ 89 ] ** [30,27%]
No (E3E6) [ 82 ] ** [27,89%]
No (E3E7) [ 66 ] ** [22,45%]
Total votes: 294
 



Rep: (175)
Teclast X80 Pro- Discussion
Windows 10 + Android 5.1 | 8 "| Intel Cherry Trail X5 Z8300 | 2Gb | HDMI, FullHD
Description | Discussion пїЅ | FAQ | Buying and Accessories | Marriage

Description | Windows 10 пїЅ | Windows 8-8.1 пїЅ | Windows RT and software пїЅ | Windows 7 пїЅ | Ubuntu linux пїЅ | Change the operating system пїЅ | Search programs пїЅ | Antivirus пїЅ | Ambulance laptop owners пїЅ | IT smoker пїЅ | Operating systems and software
Attached Image

The forum decided to post images under the spoilerPicture

Firmware

NEVER ATTEMPT TO RESTORE WINDOWS (roll back) with its standard tools - this will kill Windows and have to reinstall it.

Do a reset in androidcan . The reset duration is 20 minutes!


Instructions
1.) Increase touchscreen sensitivity in Windows
2.) If Windows does not see the SD card, we solve the problem like this - go to the BIOS-Advanced-System Component-MS Custom Sdbus Driver and install Enable. Then choose Save & Exit.
3.) If the problem persists or is solved only with a part of SD-cards, then install the driverin this manner
4.) In order for the on-screen keyboard to appear on the Windows to enter the text / character input window in Windows (outside tablet mode), you need to dolike this
5.) Solution to the problemwith time zones when restarting from Windows to Android and vice versa
6.) X80 Pro - TOOLBOX- Bootloader unlock, TWRP firmware, Getting ROOT.
ROOT for E3E8 modelcry
7.) Remapping the size of the DATA memory, allowing you to change the size of the memory allocated for Android in favor of memory allocated for Windows, and vice versa.Instructionswritten for Teclast X80 Power, but should work for X80 Pro.
8.) How to kill Windows and leave only Android on the tablet giving all the memory to Androidthat's how
9.) InstallationXposed
10.) The method of reinstalling (updating) Windows from a tablet without using a keyboard and a USB hub.


Marriage
E3E7

1) Wi-fi works very badly with the n mode, ping jumps and the speed disappears. Solution: in the adapter settings in Windows, switch to b \ g only mode. There is no solution on the android yet, only setting b \ g in the settings of the router, but then on your other devices the speed will be lower (54 Mbps).
2) Mass dumps of memory cards. It occurs not at all, but at many. No solution found.
E3E6
1) Mass dumps of memory cards. It occurs not at all, but at many. No solution found.

miscellanea
Accessories
microUSB-OTG-HUBIt works (like ALL OTHER tried hubs) ONLY in two versions, if the switch on the HUB is in the OTG position, then all devices connected to the USB device work normally, both in Android and in Windows, however charging does not go. If the switch is in the Charge position, then the tablet does not see USB devices, but it is charging. Here is such a snag, or charging, or OTG. I tried to follow the instructions for Chuwi Hi8, turned off the tablet, connected USB devices and charging to HUB, set the switch to the Charge position, connected it to the tablet, turned on the tablet, and it seems like the first 10 seconds it works and charges the tablet, but through what For 10 seconds, all USB devices are disconnected and just charging. In general, something like that.
Protective cover standI recommend it, it fits like a Teclast X80 / X80 Plus / X80 Pro (these models are identical in appearance). In stand mode, this case does NOT cover the speaker.
useful links


Post has been editedAndrewP_1 - 12.09.18, 22:41
Reason for editing: Backup of original drivers for E6E9 revision tablet



Rep: (175)
PHOTO REVIEW
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image

VIDEO REVIEW

SCREENSHOTS
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image

Got this tablet the other day. In fact, this is the same as the Teclast X80 Plus, only the resolution FullHD 1920 X 1200.

PROS:
1.) Powerful. Gaining 65,000 points in AntoTu.
2.) Two operating systems: Windows 10 (64-bit) + Android 5.1 (32-bit).
3.) Low price.
4.) Compact, you can hold the tablet in one hand.
5.) Excellent very bright IPS-display, with huge angles, and a resolution of 1920 X 1200. Actually because of it I took the Pro-version, and not the Plus-version.
6.) OTG.
7.) Loud sound.

MINUSES:
1.) Under load it heats up, although not strongly, just noticeably.
2.) No cameras. Suitable only for ticks and video calls.
3.) Only one USB output, which is simultaneously a charging socket. You have to use USB-OTG-HUB.

As a result of use, some jambs are detected that are inherent in almost all DualBoot tablets. For example, setting the clock requires setting the time zone on Windows to +3 hours, and on Android -4 hours, and turning off clock synchronization using data from the network. Only this way when switching between OS clocks will show the correct time. Windows license, activated, updated. For Android, there is a proprietary update application, but when you try to check for updates, it says "network error". Where are the updates to update offline - xs. Batteries last for 2 days of average use, although 3800 mAh, this is of course ... not sugar, but since there is no 3G module, there is enough. There are no touch buttons on the case, everything is only onscreen. All Chinese people immediately fished, the Russian set in 15 minutes, turned off the "pirun" input. Very loud. Although there is one speaker, but it really screams.

Post has been editedlawyerhome - 08.09.16, 10:16



Rep: (0)
I didn’t reveal any pitfalls in use, I’m going to buy myself in exchange for a dead netbook, and where did you buy it, if not a secret?



Rep: (175)
Slowtrone @ 04/29/2016, 19:21*
where did you buy it, if not a secret?
Tookhere
Glitches not detected. I downloaded a bunch of programs, the memory is already running out, I installed a 32 GB SD card, I did not find any problems with drivers and glitches (like some other tablets), and I think like in Android 5.1 to move programs to SD card. I suppose that it will be necessary to get ROOT rights, and to move a separate third-party program.
M
Forum Rulessavagemessiahzine.com: 4.24. When placing links, the use of special services for their reduction is prohibited. 4.25. The publication of referral materials (links, coupons and code words) in any form is prohibited and equated with commercial activities.Read more about banning the publication of referral links, coupons and code words. .


Post has been editedShoore - 11.05.16, 15:56



Rep: (2)
Hello. How is the screen in terms of scratching it? I choose between X80 pro and X80 power.



Rep: (2)
Please write how is he doing with Wi-Fi? I saw a review of the previous model, everything is bad there: 1 Mb / s versus 30 for a branded tablet.



Rep: (175)
How is the screen in terms of scratching it?
The tablet comes with a protective film. I have not cleaned it yet. I bought a tablet for a gift, so after the tests it will be presented for my birthday. The screen is not manufactured by OGS technology, and there is an air gap between the display and the touchscreen. Not matte. Pixel density is amazing. Games are on, tanks, counterstrike, DoD, and races go 45-60 fps on HD settings. Tests filmed, I will mount a video review.
How is he doing with Wi-Fi?
I did not notice the problems. Below are screenshots, a router in another room is standing.
Wi-Fi Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image

I choose between X80 pro and X80 power
He also considered the option, because the metal case, reduced thickness, two speakers (stereo) on the side (and not on the back), are captivating. But my price was in the first place, and if you consider something around $ 130, then I would look in the direction of tablets with built-in 3G.


Post has been editedlawyerhome - 01.05.16, 21:02



Rep: (2)
For me, in fact, the price is also in the first place. Pro can be bought for 6100 and for Power ask 9000. 3 thousand for the metal case and I'm not ready to give a little less thickness. Therefore, I look more at the Pro version.



Rep: (175)
I wanted to get ROOT-rights. Finding no tools and instructions anywhere, I decided to try using the tools and instructions fromthis next branchwhere discussedTeclast X98 Plus He has the same processor and OS, he thought that he could come up. By this link There were two files, just ROOT rights, and ROOT rights with tweaks. Damn me and I stitched ROOT with tweaks. The flasher program replaced the BOOT in my tablet, and now the screen is turned upside down, and the touchscreen does not respond adequately to the touch (it scrolls but does not click on the icons as if they don't exist), writes “no SIM card”. My USB debugging is activated, and I can continue flashing. But how to replace your BOOT back is not clear.
I downloaded the firmware from Android 5.1 for our X80 Pro tablet (v.1.04) and decided to try it, pulled out the BOOT from the firmware, put it in the folder with the BAT file, which I ruined my tablet, clicked, the firmware passed, BOOT was replaced, but Android did not loaded, on the inscription TECLAST everything ends. I replaced it with a BOOT for X98 Plus, the same picture with an inverted screen and inadequate touchscreen operation.
An attempt to reinstall the android crashes due to an error in entering Recovery mode. At the same time, it is not clear how to install stupidly Recovery by the Intel Phone Flash Tool. Please help advice who knows what.
Thank.

UPD. After the next launch of the flash driver, I decided to flash the tablet in Recover mode, and the firmware was poured into the tablet without errors.
LOG
# IntelВ® Phone Flash Tool - Logs generated on 2016-05-02T18: 35: 12
IntelВ® Phone Flash Tool V 5.3.4.0 x86 (build on Wednesday October 14th 2015, 14:04:16 UTC)
# OS: Windows 8.1 (x64)
05/02/16 18: 30: 40.900 DEBUG Json Flash file parsed (C: /Users/Vlad/.flasher/.configs)
05/02/16 18: 30: 41.757 INFO Intel (R) Phone Flash Tool V 5.3.4.0 x86 Internal (build on Wednesday October 14th 2015, 14:04:16 UTC)
05/02/16 18: 30: 41.757 INFO Using AutoUpdater lib version: 2.1.0.0 (Built on Wednesday October 14th 2015, 14:00:15 UTC)
05/02/16 18: 30: 41.757 INFO Using xFSTK Downloader version: 1.8.1
05/02/16 18: 30: 41.800 INFO Using DFU Downloader version: 0.8.1-msvc
05/02/16 18: 30: 42.810 INFO Using DnX Firmware Downloader version: 1.0.0.0 (API: 3.0.0.1043)
05/02/16 18: 30: 42.810 INFO Using Dldr version: BXT.PO.RC
05/02/16 18: 30: 43.217 INFO Using Intel Command Line FlashTool v.2.50 (Download Library v.5.18,0.0)
05/02/16 18: 30: 43.274 INFO Using Android Debug Bridge version 1.0.32

Revision cc6ae925e394-android
05/02/16 18: 30: 43.274 INFO OS version detected: Windows 8.1 (x64)
05/02/16 18: 30: 43.291 INFO Localhost IP address:
05/02/16 18: 30: 43.295 TRACE All localhost IP addresses: {FE80 :: 110F: 6CCE: 3974: DE78% 12,169.254.222.120, FE80 :: D047: 8665: 3EEB: FEB8% 11,169.254.254.184, FE80 :: 24E1: DC3: 6918: 3258% 6,192.168.2.106, :: 1,127.0.0.1, FE80 :: 5EFE: C0A8: 26A% 27,2001: 0: 9D38: 6AB8: 1458: 1982: 4D60: 15AC, FE80 :: 1458: 1982: 4D60: 15AC% 28}
05/02/16 18: 30: 43.295 INFO SSL supported: Yes
05/02/16 18: 30: 43.295 INFO Using TMT API version: 1.8.0-0
05/02/16 18: 30: 43.295 TRACE System PATH: C: \ ProgramData \ Oracle \ Java \ javapath; C: \ PROGRAM FILES \ BROADCOM \ BROADCOM 802.11 NETWORK ADAPTER; C: \ WINDOWS \ SYSTEM32; C: \ WINDOWS; C: \ WINDOWS \ SYSTEM32 \ WBEM; C: \ WINDOWS \ SYSTEM32 \ WINDOWSPOWERSHELL \ V1.0 \; C: \ PROGRAM FILES (X86) \ ATI TECHNOLOGIES \ ATI.ACE \ CORE-STATIC; C: \ Program Files \ WIDCOMM \ Bluetooth Software \; C: \ Program Files \ WIDCOMM \ Bluetooth Software \ syswow64; C: \ Program Files (x86) \ AMD \ ATI.ACE \ Core-Static; C: \ WINDOWS \ system32; C: \ WINDOWS; C : \ WINDOWS \ System32 \ Wbem; C: \ WINDOWS \ System32 \ WindowsPowerShell \ v1.0 \; C: \ Program Files (x86) \ ATI Technologies \ ATI.ACE \ Core-Static; C: \ Program Files (x86) \ Windows Live \ Shared; C: \ Program Files \ Crucial \ Crucial Storage Executive; C: \ Program Files (x86) \ Skype \ Phone \; C: \ Users \ Vlad \ AppData \ Local \ Microsoft \ WindowsApps; C: \ Program Files (x86) \ Intel \ Phone Flash Tool; C: \ Users \ Vlad \ AppData \ Local \ Microsoft \ WindowsApps;
05/02/16 18: 30: 43.295 TRACE Application path is C: / Program Files (x86) / Intel / Phone Flash Tool
05/02/16 18: 30: 43.295 TRACE Working directory is C: / Program Files (x86) / Intel / Phone Flash Tool
05/02/16 18: 30: 43.295 TRACE Status server disabled
05/02/16 18: 30: 43.598 INFO Total size of downloaded flash files: 0.00 bytes
05/02/16 18: 30: 43.598 TRACE TEMP folder location: drive C: / ('C: / Users / Vlad / AppData / Local / Temp')
05/02/16 18: 30: 43.599 INFO Disk space available on drive C: /: 6.10 GB
05/02/16 18: 30: 43.727 INFO Adb and fastboot binaries OK
05/02/16 18: 30: 43.778 DEBUG [Auto Update] Running "C: / Program Files (x86) / Intel / Phone Flash Tool \ AutoUpdater.exe" "--check" "--gui" "--info -channel "" --source "" https://tlsstor001.tl.intel.com/artifactory/psi-tools/phone-flash-tool/update/update-v2.0.json "" --program "" Intel В® Phone Flash Tool "" --program-version "" 5.3.4.0 "" -l "" 3 "
05/02/16 18: 30: 43.838 TRACE Registering artifactory Android environment https://mcg-depot.intel.com/artifactory/cactus-absp-tl/config/pft/pft.json
05/02/16 18: 30: 43.838 TRACE Registering artifactory environment Android PnP BKC https://mcg-depot.intel.com/artifactory/pnp_si/pft/pft-pnp.json
05/02/16 18: 30: 43.838 TRACE Registering artifactory environment AtlasPeak https://mcg-depot.intel.com/artifactory/ndg/pft/pft-atlaspeak.json
05/02/16 18: 30: 43.838 TRACE Registering artifactory environment Brillo https://mcg-depot.intel.com/artifactory/cactus-absp-tl/config/brillo/pft.json
05/02/16 18: 30: 43.838 TRACE Registering environment clark https://mcg-depot.intel.com/artifactory/ndg/pft/pft-clark.json
05/02/16 18: 30: 43.838 TRACE Registering environment Connor artifactory https://mcg-depot.intel.com/artifactory/ndg/pft/pft-connor.json
05/02/16 18: 30: 43.838 TRACE Registering environment fightclub environment https://mcg-depot.intel.com/artifactory/ndg/pft/pft-fightclub.json
05/02/16 18: 30: 43.839 TRACE Registering artifactory environment Marvin https://mcg-depot.intel.com/artifactory/ndg/pft/pft-marvin.json
05/02/16 18: 30: 44.106 INFO [Port 1/1/4] New device detected on 1/1/4 (id = 0100030000000002)
05/02/16 18: 30: 44.407 ERROR [Auto Update] No update download available
05/02/16 18: 30: 44.523 INFO Phone Flash Tool initialized successfully
05/02/16 18: 31: 03.212 DEBUG Json Flash file parsed (C: / Users / Vlad / Desktop / X80 Pro (E3E6) Android5_1V1_04 / Android)
05/02/16 18: 31: 03.400 INFO Ready to flash!
05/02/16 18: 31: 03.404 DEBUG FlashConfiguration:
name = update
startState = pos
brief = update
description = update phone to new release
documentation =
hiddenToEndUser = no
id = update
cmd [0, m = yes, t = 60000, s = no] fastboot "oem" "verified"
cmd [1, m = yes, t = 60000, s = no] fastboot "flash" "bootloader" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ bootloader"
cmd [2, m = yes, t = 60000, s = yes] fastboot "oem" "rm" "/ESP/BIOSUPDATE.fv"
cmd [3, m = yes, t = 600000, s = no] fastboot "flash" "system" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ system.img"
cmd [4, m = yes, t = 60000, s = no] fastboot "flash" "boot" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ boot.img"
cmd [5, m = yes, t = 60000, s = no] fastboot "flash" "recovery" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ recovery.img"
cmd [6, m = yes, t = 60000, s = no] fastboot "continue"
05/02/16 18: 31: 03.404 DEBUG Monitoring C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ flash.json
05/02/16 18: 31: 03.405 INFO Flash file C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ flash.json [update] loaded
05/02/16 18: 31: 24.062 DEBUG FlashConfiguration:
name = recover
startState = dnx_os
brief = Erase phone and flash all partitions
description = Erase all content, rewrite partition table and flash all partitions
documentation =
hiddenToEndUser = no
id = recover
cmd [0, m = yes, t = 60000, s = no] Wait for device with status dnx_os
cmd [1, m = yes, t = 60000, s = no] fastboot "flash" "osloader" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ loader.efi"
cmd [2, m = yes, t = 60000, s = no] fastboot "boot" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ loader.efi"
cmd [3, m = yes, t = 500, s = no] Sleeping for 0.5 seconds
cmd [4, m = yes, t = 60000, s = no] Wait for device with status pos
cmd [5, m = yes, t = 60000, s = no] fastboot "oem" "unlock"
cmd [6, m = yes, t = 60000, s = no] fastboot "flash" "oemvars" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ oemvars.txt"
cmd [7, m = yes, t = 60000, s = no] fastboot "flash" "gpt" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ gpt.bin"
cmd [8, m = yes, t = 60000, s = no] fastboot "flash" "bootloader" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ bootloader"
cmd [9, m = yes, t = 60000, s = yes] fastboot "oem" "rm" "/ESP/BIOSUPDATE.fv"
cmd [10, m = yes, t = 60000, s = yes] fastboot "flash" "ifwi" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ afu.bin"
cmd [11, m = yes, t = 60000, s = no] fastboot "erase" "misc"
cmd [12, m = yes, t = 60000, s = no] fastboot "erase" "persistent"
cmd [13, m = yes, t = 60000, s = no] fastboot "erase" "metadata"
cmd [14, m = yes, t = 60000, s = no] fastboot "format" "config"
cmd [15, m = yes, t = 60000, s = no] fastboot "format" "cache"
cmd [16, m = yes, t = 600000, s = no] fastboot "flash" "system" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ system.img"
cmd [17, m = yes, t = 60000, s = no] fastboot "flash" "boot" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ boot.img"
cmd [18, m = yes, t = 60000, s = no] fastboot "flash" "recovery" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ recovery.img"
cmd [19, m = yes, t = 60000, s = no] fastboot "oem" "verified"
cmd [20, m = yes, t = 60000, s = no] fastboot "format" "data"
cmd [21, m = yes, t = 60000, s = no] fastboot "continue"
05/02/16 18: 31: 24.062 INFO Flash file C: / Users / Vlad / Desktop / X80 Pro (E3E6) Android5_1V1_04 / Android / flash.json [recover] loaded
05/02/16 18: 31: 24.246 INFO Ready to flash!
05/02/16 18: 31: 29.095 INFO [Port 1/1/4] Checking crashinfo ...
05/02/16 18: 31: 29.096 INFO Executing "C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ adb.exe" "-s" "Default0string" "root"
05/02/16 18: 31: 29.159 TRACE "C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ adb.exe" "-s" "Default0string" "root" return:
adbd is already running as root
05/02/16 18: 31: 29.159 INFO Executing "C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ adb.exe" "-s" "Default0string" "wait-for-device"
05/02/16 18: 31: 29.220 INFO "C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ adb.exe" "-s" "Default0string" "wait-for-device" OK
05/02/16 18: 31: 29.220 INFO Executing "C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ adb.exe" "-s" "Default0string" "shell" "crashinfo" "getevent" "- -full "" -j "
05/02/16 18: 31: 29.293 TRACE "C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ adb.exe" "-s" "Default0string" "shell" "crashinfo" "getevent" "- full "" -j "return:
/ system / bin / sh: crashinfo: not found
05/02/16 18: 31: 29.294 WARNING [Port 1/1/4] Cannot check if crashinfo logs are uploaded, starting flash process ...
05/02/16 18: 31: 29.559 INFO [Port 1/1/4] Start flashing with dnx_os start state for Default0string
05/02/16 18: 31: 29.559 INFO [Port 1/1/4] Reboot device Default0string with ADB ...
05/02/16 18: 31: 31.218 INFO [Port 1/1/4] Starting flash ...
05/02/16 18: 31: 31.219 DEBUG [Port 1/1/4] Waiting for device in dnx_os
05/02/16 18: 31: 31.788 DEBUG [Port 1/1/4] Device disconnected on 1/1/4
05/02/16 18: 31: 43.776 DEBUG [Port 1/1/4] Device reconnected on 1/1/4
05/02/16 18: 31: 43.776 INFO [Port 1/1/4] Flash started
05/02/16 18: 31: 43.776 INFO [Port 1/1/4] Sleep 500 ms before executing first flash command
05/02/16 18: 31: 44.276 DEBUG [Port 1/1/4] Group 'delete_capsule' disables command `Deleting BIOS capsule file`
05/02/16 18: 31: 44.276 DEBUG [Port 1/1/4] Group 'flash_AFU' disables command `Flashing AFU`
05/02/16 18: 31: 44.276 INFO [Port 1/1/4] Running `1/1 / 4` command
05/02/16 18: 31: 44.276 INFO [Port 1/1/4] Command `1/1 / 4` succeed
05/02/16 18: 31: 44.276 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" "" flash " "osloader" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ loader.efi" `command
05/02/16 18: 31: 44.873 DEBUG [Port 1/1/4] sending 'osloader' (12502 KB) ...
05/02/16 18: 31: 44.873 DEBUG [Port 1/1/4] OKAY [0.479s]
05/02/16 18: 31: 44.873 DEBUG [Port 1/1/4] writing 'osloader' ...
05/02/16 18: 31: 44.873 DEBUG [Port 1/1/4] OKAY [0.024s]
05/02/16 18: 31: 44.873 DEBUG [Port 1/1/4] finished. total time: 0.504s
05/02/16 18: 31: 44.875 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" "" flash " "osloader" "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ loader.efi" `succeed
05/02/16 18: 31: 44.875 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" "" boot " "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ loader.efi" `command
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] creating boot image ...
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] creating boot image - 12806144 bytes
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] downloading 'boot.img' ...
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] OKAY [0.478s]
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] booting ...
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] OKAY [0.003s]
05/02/16 18: 31: 45.449 DEBUG [Port 1/1/4] finished. total time: 0.481s
05/02/16 18: 31: 45.450 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" "" boot " "C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ loader.efi" `succeed
05/02/16 18: 31: 45.450 INFO [Port 1/1/4] Running `Sleeping for 0.5 seconds` command
05/02/16 18: 31: 45.716 DEBUG [Port 1/1/4] Device disconnected on 1/1/4
05/02/16 18: 31: 45.950 INFO [Port 1/1/4] Command `Sleeping for 0.5 seconds` succeed
05/02/16 18: 31: 45.950 INFO [Port 1/1/4] Running for 1/1 / 4` command
05/02/16 18: 31: 48.527 DEBUG [Port 1/1/4] Device reconnected on 1/1/4
05/02/16 18: 31: 48.527 INFO [Port 1/1/4] Command `succeed
05/02/16 18: 31: 48.527 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" oem "" unlock "` command
05/02/16 18: 31: 48.753 DEBUG [Port 1/1/4] ...
05/02/16 18: 31: 48.753 DEBUG [Port 1/1/4] OKAY [0.116s]
05/02/16 18: 31: 48.753 DEBUG [Port 1/1/4] finished. total time: 0.116s
05/02/16 18: 31: 48.754 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" oem "" unlock "` succeed
05/02/16 18: 31: 48.754 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" "-s" "Default0string" "flash "" oemvars "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ oemvars.txt "` command
05/02/16 18: 31: 49.295 DEBUG [Port 1/1/4] bytes
05/02/16 18: 31: 49.295 DEBUG [Port 1/1/4] sending 'oemvars' (1 KB) ...
05/02/16 18: 31: 49.296 DEBUG [Port 1/1/4] OKAY [0.106s]
05/02/16 18: 31: 49.296 DEBUG [Port 1/1/4] writing 'oemvars' ...
05/02/16 18: 31: 49.296 DEBUG [Port 1/1/4] OKAY [0.276s]
05/02/16 18: 31: 49.296 DEBUG [Port 1/1/4] finished. total time: 0.382s
05/02/16 18: 31: 49.296 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" oemvars "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ oemvars.txt "` succeed
05/02/16 18: 31: 49.297 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" gpt "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ gpt.bin "` command
05/02/16 18: 31: 49.751 DEBUG [Port 1/1/4] bytes
05/02/16 18: 31: 49.751 DEBUG [Port 1/1/4] sending 'gpt' (1 KB) ...
05/02/16 18: 31: 49.751 DEBUG [Port 1/1/4] OKAY [0.107s]
05/02/16 18: 31: 49.752 DEBUG [Port 1/1/4] writing 'gpt' ...
05/02/16 18: 31: 49.752 DEBUG [Port 1/1/4] OKAY [0.182s]
05/02/16 18: 31: 49.752 DEBUG [Port 1/1/4] finished. total time: 0.289s
05/02/16 18: 31: 49.752 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" gpt "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ gpt.bin "` succeed
05/02/16 18: 31: 49.752 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" bootloader "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ bootloader "` command
05/02/16 18: 31: 50.727 DEBUG [Port 1/1/4] Device disconnected on 1/1/4
05/02/16 18: 31: 58.479 DEBUG [Port 1/1/4] bytes
05/02/16 18: 31: 58.479 DEBUG [Port 1/1/4] sending 'bootloader' (102400 KB) ...
05/02/16 18: 31: 58.479 DEBUG [Port 1/1/4] OKAY [4.127s]
05/02/16 18: 31: 58.479 DEBUG [Port 1/1/4] writing 'bootloader' ...
05/02/16 18: 31: 58.479 DEBUG [Port 1/1/4] OKAY [4.340s]
05/02/16 18: 31: 58.479 DEBUG [Port 1/1/4] finished. total time: 8.466s
05/02/16 18: 31: 58.479 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" bootloader "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ bootloader "` succeed
05/02/16 18: 31: 58.480 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" erase "" misc "` command
05/02/16 18: 31: 58.763 DEBUG [Port 1/1/4] erasing 'misc' ...
05/02/16 18: 31: 58.763 DEBUG [Port 1/1/4] OKAY [0.186s]
05/02/16 18: 31: 58.763 DEBUG [Port 1/1/4] finished. total time: 0.186s
05/02/16 18: 31: 58.764 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" erase "" misc "` succeed
05/02/16 18: 31: 58.764 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" erase "" persistent "` command
05/02/16 18: 31: 59.039 DEBUG [Port 1/1/4] ******** Did you mean to fastboot format this partition?
05/02/16 18: 31: 59.039 DEBUG [Port 1/1/4] erasing 'persistent' ...
05/02/16 18: 31: 59.039 DEBUG [Port 1/1/4] OKAY [0.186s]
05/02/16 18: 31: 59.039 DEBUG [Port 1/1/4] finished. total time: 0.186s
05/02/16 18: 31: 59.040 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" erase "persistent" `succeed
05/02/16 18: 31: 59.040 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" erase "" metadata "command
05/02/16 18: 31: 59.313 DEBUG [Port 1/1/4] erasing 'metadata' ...
05/02/16 18: 31: 59.313 DEBUG [Port 1/1/4] OKAY [0.186s]
05/02/16 18: 31: 59.313 DEBUG [Port 1/1/4] finished. total time: 0.186s
05/02/16 18: 31: 59.313 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" erase "" metadata "` succeed
05/02/16 18: 31: 59.314 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" "-s" "Default0string" "format "" config "` command
05/02/16 18: 31: 59.533 DEBUG [Port 1/1/4] Device reconnected on 1/1/4
05/02/16 18: 32: 00.210 DEBUG [Port 1/1/4] Creating filesystem with parameters:
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Size: 8388608
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Block size: 4096
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Blocks per group: 32768
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Inodes per group: 512
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Inode size: 256
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Journal blocks: 1024
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Label:
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Blocks: 2048
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Block groups: 1
05/02/16 18: 32: 00.211 DEBUG [Port 1/1/4] Reserved block group size: 7
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] Created filesystem with 11/512 inodes and 1070/2048 blocks
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4]<waiting for device>
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] bytes
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] erasing 'config' ...
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] OKAY [0.179s]
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] sending 'config' (4280 KB) ...
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] OKAY [0.249s]
05/02/16 18: 32: 00.212 DEBUG [Port 1/1/4] writing 'config' ...
05/02/16 18: 32: 00.213 DEBUG [Port 1/1/4] OKAY [0.206s]
05/02/16 18: 32: 00.213 DEBUG [Port 1/1/4] finished. total time: 0.635s
05/02/16 18: 32: 00.213 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" format "" config "` succeed
05/02/16 18: 32: 00.213 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" format "" cache "` command
05/02/16 18: 32: 01.769 DEBUG [Port 1/1/4] Device disconnected on 1/1/4
05/02/16 18: 32: 04.183 DEBUG [Port 1/1/4] Creating filesystem with parameters:
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Size: 1610612736
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Block size: 4096
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Blocks per group: 32768
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Inodes per group: 8192
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Inode size: 256
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Journal blocks: 6144
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Label:
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Blocks: 393216
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Block groups: 12
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Reserved block group size: 95
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] Created filesystem with 11/98304 inodes and 12897/393216 blocks
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] bytes
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] erasing 'cache' ...
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] OKAY [1.366s]
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] sending 'cache' (27160 KB) ...
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] OKAY [1.175s]
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] writing 'cache' ...
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] OKAY [1.046s]
05/02/16 18: 32: 04.184 DEBUG [Port 1/1/4] finished. total time: 3.586s
05/02/16 18: 32: 04.185 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" format "" cache "` succeed
05/02/16 18: 32: 04.185 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" system "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ system.img "` command
05/02/16 18: 33: 34.813 DEBUG [Port 1/1/4] bytes
05/02/16 18: 33: 34.813 DEBUG [Port 1/1/4] erasing 'system' ...
05/02/16 18: 33: 34.813 DEBUG [Port 1/1/4] OKAY [2.786s]
05/02/16 18: 33: 34.813 DEBUG [Port 1/1/4] sending sparse 'system' (259621 KB) ...
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] OKAY [12.009s]
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] writing 'system' ...
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] OKAY [9.204s]
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] sending sparse 'system' (257567 KB) ...
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] OKAY [11.283s]
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] writing 'system' ...
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] OKAY [9.176s]
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] sending sparse 'system' (262121 KB) ...
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] OKAY [11.640s]
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] writing 'system' ...
05/02/16 18: 33: 34.814 DEBUG [Port 1/1/4] OKAY [9.402s]
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] sending sparse 'system' (259349 KB) ...
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] OKAY [10.975s]
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] writing 'system' ...
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] OKAY [9.360s]
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] sending sparse 'system' (16388 KB) ...
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] OKAY [0.855s]
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] writing 'system' ...
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] OKAY [0.617s]
05/02/16 18: 33: 34.815 DEBUG [Port 1/1/4] finished. total time: 87.307s
05/02/16 18: 33: 34.816 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" system "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ system.img "` succeed
05/02/16 18: 33: 34.816 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" "-s" "Default0string" "flash "" boot "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ boot.img "` command
05/02/16 18: 33: 36.045 DEBUG [Port 1/1/4] bytes
05/02/16 18: 33: 36.045 DEBUG [Port 1/1/4] sending 'boot' (11167 KB) ...
05/02/16 18: 33: 36.045 DEBUG [Port 1/1/4] OKAY [0.591s]
05/02/16 18: 33: 36.045 DEBUG [Port 1/1/4] writing 'boot' ...
05/02/16 18: 33: 36.045 DEBUG [Port 1/1/4] OKAY [0.421s]
05/02/16 18: 33: 36.045 DEBUG [Port 1/1/4] finished. total time: 1.012s
05/02/16 18: 33: 36.046 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" boot "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ boot.img "` succeed
05/02/16 18: 33: 36.046 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" recovery "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ recovery.img "` command
05/02/16 18: 33: 37.233 DEBUG [Port 1/1/4] bytes
05/02/16 18: 33: 37.233 DEBUG [Port 1/1/4] sending 'recovery' (11835 KB) ...
05/02/16 18: 33: 37.233 DEBUG [Port 1/1/4] OKAY [0.587s]
05/02/16 18: 33: 37.233 DEBUG [Port 1/1/4] writing 'recovery' ...
05/02/16 18: 33: 37.233 DEBUG [Port 1/1/4] OKAY [0.454s]
05/02/16 18: 33: 37.233 DEBUG [Port 1/1/4] finished. total time: 1.041s
05/02/16 18: 33: 37.234 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" flash "" recovery "" C: \ Users \ Vlad \ Desktop \ X80 Pro (E3E6) Android5_1V1_04 \ Android \ recovery.img "` succeed
05/02/16 18: 33: 37.234 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" oem "" verified "command
05/02/16 18: 33: 37.442 DEBUG [Port 1/1/4] ...
05/02/16 18: 33: 37.442 DEBUG [Port 1/1/4] OKAY [0.120s]
05/02/16 18: 33: 37.442 DEBUG [Port 1/1/4] finished. total time: 0.120s
05/02/16 18: 33: 37.442 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" oem "verified" `succeed
05/02/16 18: 33: 37.443 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" "-s" "Default0string" "format "" data "` command
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Creating filesystem with parameters:
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Size: 5368709120
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Block size: 4096
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Blocks per group: 32768
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Inodes per group: 8192
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Inode size: 256
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Journal blocks: 20480
05/02/16 18: 33: 51.116 DEBUG [Port 1/1/4] Label:
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] Blocks: 1310720
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] Block groups: 40
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] Reserved block group size: 319
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] Created filesystem with 11/327680 inodes and 43611/1310720 blocks
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] bytes
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] erasing 'data' ...
05/02/16 18: 33: 51.117 DEBUG [Port 1/1/4] OKAY [6.233s]
05/02/16 18: 33: 51.118 DEBUG [Port 1/1/4] sending 'data' (85641 KB) ...
05/02/16 18: 33: 51.118 DEBUG [Port 1/1/4] OKAY [3.448s]
05/02/16 18: 33: 51.118 DEBUG [Port 1/1/4] writing 'data' ...
05/02/16 18: 33: 51.118 DEBUG [Port 1/1/4] OKAY [3.164s]
05/02/16 18: 33: 51.118 DEBUG [Port 1/1/4] finished. total time: 12.845s
05/02/16 18: 33: 51.128 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" "-s" "Default0string" "format "" data "` succeed
05/02/16 18: 33: 51.128 INFO [Port 1/1/4] Running `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" continue "` command
05/02/16 18: 33: 51.225 DEBUG [Port 1/1/4] resuming boot ...
05/02/16 18: 33: 51.225 DEBUG [Port 1/1/4] OKAY [0.008s]
05/02/16 18: 33: 51.225 DEBUG [Port 1/1/4] finished. total time: 0.008s
05/02/16 18: 33: 51.225 INFO [Port 1/1/4] Command `" C: \ Program Files (x86) \ Intel \ Phone Flash Tool \ fastboot.exe "" -s "" Default0string "" continue "` succeed
05/02/16 18: 33: 51.225 INFO [Port 1/1/4] Flash success (duration = 00: 02: 06.949)
05/02/16 18: 33: 51.327 TRACE Sending system tray notification: "Flash Success"
05/02/16 18: 33: 51.432 INFO [Port 1/1/4] Device lost on 1/1/4

But now, when booting / rebooting, you cannot select OS Windows (there is no such icon), apparently the bootloader is stuck. You can only select Android.
Now I have this firmware:
Screenshot
Attached Image


Post has been editedlawyerhome - 02.05.16, 18:43



Rep: (125)
* lawyerhome
Hmm, the main problem with these devices is that people climb to pick systems without backup.
On the case: I think to try to flash the android from scratch, if you can’t wait to wait until someone arrives with the subject, and make a backup usingMacrium Reflect.
Lawyerhome @ 05/02/2016, 15:22*
UPD. After the next launch of the flash driver, I decided to flash the tablet in Recover mode, and the firmware was poured into the tablet without errors.

Congratulations :) make a backup from the makrium, for the future.

Post has been editedmachetekills - 02.05.16, 18:41



Rep: (175)
Machetekills @ 05/02/2016, 17:36*
make a backup from makrium, for the future
There is a firmware itself. Android downloaded, I download Windows. There is also a manual, but it is in Chinese. I scratch the turnips, how to restore the bootloader, because when the OS is selected, only Android drops out, and Windows has no icon ...



Rep: (15)
Tell me how you screen, enough backlight. How long does the battery hold?



Rep: (175)
Paull @ 05/02/2016, 19:04*
Tell me how you screen, enough backlight. How long does the battery hold?
Brightness enough. In the evening I use at 50% brightness. On the street on a sunny day, turn on 100% brightness. The screen is great. I took the X80 Pro and not the X80 Plus because of the FullHD display, with a resolution of 1920x1200. Colors juicy, IPS screen. Launched the game, the processor (graphics core) pulls without problems for 45-60 fps, tanks, Counter Strike, Day of Defense, Asphalt 8, and others. Protective film comes from the factory.



Rep: (0)
But how does he keep on standby on an android — how many percent does he eat per night?



Rep: (175)
rem198 @ 05/02/2016, 20:20*
But how does he keep on standby on an android — how many percent does he eat per night?
From 10 pm to 7:30 am the tablet was discharged from 97% to 86% (self-discharge in standby mode in Android OS 5.1). Below is a screenshot:
Screenshot
Attached Image


Post has been editedlawyerhome - 03.05.16, 07:29



Rep: (0)
I still have to ask if it can be simultaneously charged and work from the fires through the hub, and how many devices it can be hooked to it, (there are enough mice and claves in the printer)



Rep: (175)
Slowtrone @ 05/03/2016, 09:52*
it can at the same time be charged and work with the fires through the hub, and as many devices as it can be hooked to it, (there are enough mice and claves in the printer)
Since this tablet has one microUSB, to which either the charging, or USB device (keyboard, mouse) is connected, I ordered more with the tabletHere is a microUSB-OTG-HUB, allowing you to connect 3 USB + 1 microUSB charging or microUSB OTG adapter. Thanks to him a tabletit is simultaneously charging and up to 3 USB devices can be connected to itOr charging or plugging in up to 3 USB devices. Those. or / or, and so that everything does not work together. I tried to follow the instructions from the topic about Chuwi Hi8, but alas, the first 10 seconds both USB devices and charging work, but then USB devices fall off. I'll try to connect the charging not to the USB output of the laptop, but to 2A charging, and we'll see if it can start everything together, and USB devices, and charging.
The Bluetooth mouse is connected, but working in it is not as convenient as with a USB mouse.
I have enough. You can connect a full keyboard + mouse + USB flash drive or an external HDD and charging.
Thanks to this, it will now be possible to install (restore) Windows 10, which can be installed here only via a USB flash drive (I did not find how to install Windows via a microSD card) and an external keyboard.


Post has been editedShoore - 11.05.16, 16:03
Reason for editing: deleted referral



Rep: (175)
Protective caseon tabletX80 Plus / X80 Pro . Took in color blue-nacre. Although I think that in white it would be more appropriate, because the cover itself (plastic - bumper) is transparent, and through it the white color of the tablet itself is visible. Snaps well, reliably, will not fly out. Cut under the camera, buttons and speaker in place. And if the tablet roll up so that it was a stand, then the slot under the speaker does not overlap (as it was in the Chuwi Hi8). In general, everything is thought out here.
Cover photoreview
Attached Image
Attached Image
Attached Image



Post has been editedShoore - 11.05.16, 16:05
Reason for editing: referral



Rep: (7)
lawyerhome @ 04/26/2016, 8:49 PM*
setting the clock requires you to set the time zone on Windows for 3 hours, and on Android -4 hours, and turn off clock synchronization using data from the network. Only this way when switching between OS clocks will show the correct time.

I dare say that this is not the only way. I, according to the recommendations found on the forum, set the correct time zone (Moscow) on Windows, and zero on Android. And it shows everything correctly when switching.

And now about my problem. I tried to connect Apple Magic Mouse. In Windows 10, I saw immediately after installing the driverfrom hereAnd some crap with reboots (first the mouse pointer disappeared) - the main one works. Right and left buttons and scroll. Sly gestures did not check. Now I discovered that after rebooting from Android, the pointer disappeared again. but managed to reconnect it by mouse.

In Android, the mouse joined, but the pointer did not appear. (According to OTG, a regular USB mouse works fine in it). If anyone knows where to dig, I will be grateful for the advice



Rep: (175)
FIRMWARE for Teclast X80 Pro (Windows 10 64-bit + Android 5.1 32-bit v.1.04)

Yandex.DiskorMEGAibid instructions (in Chinese) and tools with drivers

Post has been editedlawyerhome - 04.05.16, 23:00



Rep: (10)
Hello! I am faced with a choice of Plus or Pro. Of course you want Full HD, but in the next branch they assume that it will eat more battery than HD. And autonomy is also not the last question. The request to the owners of Pro, measure the running time when playing YouTube videos at 50% brightness. Thank you in advance!


Full version    

Help     rules

Now: 07/02/19, 09:14