[X]Assistant

[bazanovv]

DiscussionGU on Android 4/6/7/8, Allwinner T3 Quad Core 1.2GHz platform (model K2001)
Car and Android device
Discussion пїЅ | The original version of the state on T3 | New version of GI on T3 | State University Ezonetronics RM-CT0008 1din | XDA thread | Sinosmart SMT01 (Allwinner T3) |

• To compare the device with competitors and on the choice of devices, please contact: Selection and Comparison;
  
• Before posting photos, read the topic Working with Images on the forum (Post absolute3 # 14041004)as well as clean up under the spoilerin the mobile client;
  
• Messages that are not related to the topic of discussion (offtopic) are deleted without warning;
  
• The post was useful and interesting, do not hesitate to thank the green "Good" button, as well as a button + Reputations under the nickname of a forumchan.
  
• Theme is very similar to GUEzonetronics RM-CT0008 1din. Firmware from there does not fit, willbrick!
  

Specifications

Android OS 4.4.x and 6.0.x (sometimes fake Android version for 5 or 6, you can determine by API version - 4.4 is 19, 6.0 - 23. There are firmware and GU with honest Android 6.0, version K2001M), CPU Allwinner T3 - 4 cores РЎortex A7 1.2 GHz, display 1024x600 or 800x480 HD of quality and high brightness. Capacitive frost resistant Multi-Touch. RAM 1Gb, built-in memory 16Gb. FM module TEA6851 / TEA6856. Another name GU t3_p2, iron sun8iw11P1. Audio DSP CSC37534 (analogue of ROHM BD37534FV).
It is possible to distinguish GU from other options on T3 by the settings menu, it is with the item tree on the left and the build number K2001_xxx, see photo.

A photo

Menu


The system menu on honest 6 Android


Iron -the firstoption


Iron -secondoption



Processor (? Not checked,a source ?)


More photos of the processor boardfrom here.


Still,from here.


Photo of model K2101 without a subsidiary processor board, all on one, from Angelosar.



One more photothe same fee from CyberSpace83.

Photo supercompact optionin good resolution from Fire stream.

A photodevices with 1DIN case from noname40k.

Firmware

Attention, all actions you do at your own peril and risk. If everything works well, everything turns on, turns off, does not puff, does not buggy - then you do not need to flash anything! This is especially true for the MCU, if something broke during the MCU firmware, roll back to the previous version and do not touch it anymore, the MCU flash drive has a very delicate memory, and there were cases when you received the MCU after the firmwarekripich, so think ten times before stitching an MCU. There are no ways to restore a brick with a damaged MCU firmware today, just replacing the motherboard.

Attention! Due to the diversity of GU models with the “alien” firmware and inappropriate firmware, some GU functions may stop working. Firmware is a big risk! PG happens with a display resolution of 1024x600 and 800x480, the firmware between them is not interchangeable - with firmware designed for 800x480 on the display from 1024x600 only part of the screen will be occupied. When the situation is reversed, a part of the image, including the control buttons, will not fit on the screen. In this case, connect a USB mouse (and in severe cases, an external display) and reflash,driving this mouse. Right mouse button - back. If the resolution does not explicitly indicate the resolution, consider that it is 1024x600.

Official firmwareAndroid 4.4:

Android 4.4

1. Firmware05/19/2017, K2001_YZG_S212104.20170519;
   
2. Firmwarefrom 08/25/2017, K2001_YZG_S212104.20170825;
   
3. Firmwarefrom 08.18.2017, K2001_XSY_S212409.20170818.14452725, for the Russian language it is necessary to put a check in Factory,details here;
   
4. Firmwarefrom 10/24/2017, K2001_XZ_S212304.20171024.15374904;
   
5. Firmwarefrom 19.01.2017 in .img image format for recovery, Android 4.4;
   
6. Firmware11.08.2017, K2001_XSY_S211410.20170811 resolution 800X480;
   
7. Firmwarefrom 11/14/2017, K2001_XSY_S212409.20171114.15165058.
   
8. firmwarefrom 08/30/2018, K2001_PHM_S212203.20180830.16471694.N0018
   

Official firmwareAndroid 6.0(version K2001M). Attention, update from 4.4 and roll backonly through the firmware from the .img image:

Android 6.0

1. Firmwaredated July 25, 2017, K2001M_CLD_S212208.20170725.16571039 from Cyclon 7039;
   
2. Firmwarefrom 09/22/2017, K2001M_SPDZ_S212202.20170922;
   
3. Firmwarefrom 04/05/2017 in .img image format for recovery, Android 6.0. Firmwarein Chinese- immediately after it is updated to another one on 6.0. This same4Gb DATA firmware
   
4. Firmwarefrom 09/29/2017, K2001M_YZG_S212104.20170929;
   
5. Firmwarefrom 10/18/2017, K2001M_SPDZ_S212202.20171018;
   
6. Firmware10/31/2017, K2001M_JSH_S212104.20171031 (for RM-CT0018);
   
7. Firmwarefrom 11/03/2017, K2001M_XZ_S212305.20171103.17413320 (retrieved from the cache);
   
8. Firmwaredated 09.11.2017, K2001M_JSH_S212203.20171109.14491402.
   
9. Firmware12/19/2017, K2001M_XZ_S212305.20171219.11005378
   
10. Firmwarefrom 03.20.2018, K2001_Mspzd_20180320_update
    
11. Firmwarefrom 09/29/2018, K2001M_NWD_S212216.20180929
    
    

Modifiedand other firmware:

1. A set of firmwaresuitable for T3-P2.
   Caution, apply at your own peril, see experiencetophosin the FAQ. The custom firmware for different screen resolutions is 1024x600_K2001_CLD_S212203.20170419 and 800x480_K2001_CLD_S211204.20161128 on 4.4.2 Android, are installed, and # 4106_T3_6.0_nwd_K2001M_CLD_S212206.20170, we will accept 2004, we will accept 2004, we will turn, we will need to turn, we will talk to you, you will need to get 8 . Link all see mirrorhere;
   
2. MCU dated 11/06/2017forsuch aGU with a different (it seems, TEF6851) radio module with which the MCU is higher and the MCU from the Android 6 kitdoes not work. Do not flash, if your radio is working, it may stop working!
   
3. Customfirmwarefromtasty85Based on K2001_JC_S211106.20161121, screen resolution 800x480, Android version 4.4.2, built-in root - rights;
   
4. CustomfirmwarefromMonakov86Based on K2001_CLD_S212203.20170419, screen resolution 1024x600, built-in root - rights, Android version 4.4.2. Firmware tested on K2101;
   
5. CustomfirmwarefrombrunokvsBased on K2001_YZG_S212104.20170825, screen resolution 1024x600, built-in root - rights, Android version 4.4.2;
   
6. Firmwarefor State Office RM-CT0018, inside K2101_JSH_S212102 from 20170405.
   About firmwareandstill;
   
7. Firmware800x480 from 24032017 and from 20171125 (Chinese, without Google services) for PG in case for installation in BMW X3 E83;
   
8. CustomfirmwarefromNightManOsbased on NEW.K2001_XSY_S212409.20171114, screen resolution 1024x600, built-in root - rights, Russian by default, Moscow time by default, white list, style changes, etc., the only thing that could not is to remove the blue from the settings. Android version 4.4.2. Firmware tested on K2101;
   
9. CustomfirmwarefromNightManOsBased on K2001M_JSH_S212203.20171109, screen resolution 1024x600, Russian by default, Moscow time by default, there is no root-rights. Android version 6.0.1.
   
10. Customfirmwarefromjp2008The basis of "K2001M / 20180207 / 1024x600" Android 4/6 | 1024x600
    
11. CustomfirmwarefromSucserT3_4.4_Resize_Sucser /Android 6.0.1 1024x600 (4GB for apps)
    
    

Firmware fromser39:

1. https://yadi.sk/d/fv-nr1YP3Qb7UE. K2001_CLD_S212203.20170419, screen resolution 800x480, built-in root - rights, Android version 4.4.2. For GU with XSY and YZG firmware;
   
2. https://yadi.sk/d/STxetIWq3Qb7bE. K2001_XSY_S211410.20170811, screen resolution 800x480, CLD launcher, built-in root - rights, Android version 4.4.2;
   
3. https://yadi.sk/d/5NT51XkF3Qb7kj. K2001_YZG_S212104.20170825, screen resolution 800x480, CLD launcher, built-in root - rights, Android version 4.4.2;
   
4. https://yadi.sk/d/T4xzEAhI3Qb84a. K2001_XSY_S212409.20170818, screen resolution 1024x600, in black, built-in root - rights, Android 4.4.2 version;
   
5. https://yadi.sk/d/s0iv_-kn3QfYHD. K2001_YZG_S212104.20170519, screen resolution 1024x600, JC launcher, built-in root - rights, Android version 4.4.2;
   
6. https://yadi.sk/d/Cax8zbeE3QfYdP. K2001_YZG_S212104.20170825, screen resolution 800x480, JC launcher, built-in root - rights, Android version 4.4.2;
   
7. FirmwareK2001_YZG_S212104.20170825, screen resolution 1024x600, CLD launcher, built-in root - rights, Android version 4.4.2, build dated 1/18/2018;
   
8. FirmwareK2001_YZG_S212104.20170825, screen resolution 800x480, CLD launcher, built-in root - rights, Android version 4.4.2, build dated 1/18/2018;
   
9. FirmwareK2001_GDH_S211102.20171117.11324988, screen resolution 800x480, built-in root - rights, Android version 4.4.2, build dated 1/20/2018;
   
10. FirmwareK2001_GDH_S211102.20171117.11324988, screen resolution 1024x600, built-in root - rights, Android version 4.4.2, build dated 01.20.2018 (temporarily removed).
    

Firmwareunder the resolution of 1024x600, all the firmwares are rutted, there are styles and a white list, some software has been removed - fromNightManOs, descriptionwhich ones.

Firmware for modelK2101. Usually, all K2001 firmwares are suitable for your display resolution:

K2101

1. Firmwaredated 04.18.2017 K2101_JSH_S212102.20170418 mirrorhereandhere;
   
2. HereverifiedK2001 firmware on K2101 - K2001_CLD_S212203.20170419;
   
3. Hereverifiedcustom firmware K2001 on K2101 - K2001_CLD_S212203.20170419 with built-in root-rights;
   
4. HereverifiedcustomfirmwareK2001 to K2101 - K2001_YZG_S212104.20170825 with built-in root-rights;
   
5. Firmwarefrom 10/26/2017 K2101_JSH_S212102.20171026, Android 4.4.
   

Fileupdate.scriptfor some firmware.

Mirror firmwarehere(for K2101 per levelabove), making copies is welcome.Mirror copyon 10/14/2017 from edi_08.

What is an MCU and why should it be stitched separately?

The MCU is a specialized microprocessor that controls the entire PG, turns it on and off, adjusts the volume and equalizer (giving commands to the audio processor), radio (tuning to frequency, RDS), Bluetooth, switching audio and video signals, handles button clicks on the steering wheel and signals from Canbus where there is, etc. If you exaggerate a lot, you can say that this is one of the main devices in the PG, and the block on Android is only a beautiful interface to it. More details likehere. And the MCU file is its firmware (in encrypted form, decrypted during the firmware process). Firmware of something "wrong" in the MCU is a good chance to turn a radio tape recorder, lose control or functionality, and something "wrong" - fix existing glitches in the above (together with the correct setting). The resource of MCU flash memory (pdf 1000 rewriting cycles, but there are nuances) is less than the board on Android, so you should not reflash it too often.Heremore details. If there was an MCU firmware error - do not turn off the GU, try to sew up the version that you had before, and hope that it will work. There are no ways to restore the GD after an unsuccessful MCU firmware, except for a complete replacement of the motherboard, and bricks sometimes really happen. But in most cases, everything goes fine.

FAQ - Regularly updated

1. Cooling and experimenting with firmware fromtophos - part 1, part 2andsuccessful completion. Stilloption. Cooling solutionsupercompact GU. Another option is to installlaptop fan and radiator. Comparisonidle temperatures under 4 and 6 by Android;
   
2. Android version is best checked by third-party programs, focus onAPI Version- 19 for 4.4.x and 23 for 6.0.x. What is displayed in the regular menu (5.1 or 6.0), happens, does not correspond to reality.More here;
   
3. Poor radio reception, especially outside the city - make sure that if you have a standard antenna amplifier (see the schematic / service manual on the car, wiring the connector of a regular PG), you energize it when the PG is connected - this is an Ant wire, usually blue. In the ISO block, it is not connected, and it is connected normally only if you had an adapter for your car,injectorfood for Fakra and the like;
   
4. The reset button makes a hardware reset, similar to a power outage. It can be used if the PG is stuck instead of shutting down the engine, or if the MCU is stuck, instead of removing the battery terminal. Resetting the Android settings, which can fix (or not fix) many incomprehensible Android software glitches, is in the Settings - Restore and reset - Reset settings menu. These are completely different procedures and should not be confused;
   
5. A little aboutCANbus connectionour GU,stillandabout customizationby the State University;
   
6. ABOUTreceivingRoot, andstill. Verified andworking way hereand here it ischeck. More about versionschecked. Sometimes because of kingoroot there are weirdglitches;
   
7. Log in to the engineering menu of the Factory settingpassword1617 or, sometimes, forlarger numbersavailable settings 16176699. On some new PG password to enter the factory settings66668888. More possibleoption with 3368 and not only, still8888. Menu screenshotshere;
   
8. Customizationimages from the rear view camera - turn it on and drag your finger without taking it from the screen to the left to the right, the settings menu will open, but only on the camera;
   
9. Firmware is donelike thishereanother wayandinstructionin pictures, fromMRG-51;
   
10. How to signzip firmware android (update.zip), fromtasty85;
    
11. PinoutPG connectors (one of the options);
    
12. Instructionhow to flash mcu. Attention! Do not flash the MCU if you are not sure that it will suit you. Do not touch the GU and auto during the flashing. If something goes wrong, if you sew it wrong, there will be a brick !!!
    
13. CPU boardwith Android for replacement;
    
14. Each time the ignition is turned off, the time and tuned radio stations are reset, does the radio start? The reason is that in different versions of the wiring of the ISO connector in different cars, it is necessary to swap the thick yellow and thick red wires in the ISO GU block. Detailshere;
    
15. Consumption currentin work mode and sleep mode, and one moremeasurement;
    
16. About mixing navigation -timeandtwoandthree, pictureautorun settings for navigation and blending;
    
17. Setting the touch buttons on the screen is donelike this. Another option to enter the settings -hold 5 fingers at onceon the screen for a long time, up to ten seconds, then set up, and then save the settings. If it does not save the settings of the touch buttons, it can help.back them up;
    
18. If you have buttons on the steering wheel, and the wire from them goes to the standard GU auto connector (in new cars, wires from the steering wheel can go to the brains of the car and transmitted to the radio already via CANbus), and there is also a CANbus decoder, and a wire from the buttons on the steering wheel enters it, and not directly into the PG, it is possible that the buttons on the steering wheel work poorly or not at all. In this case, it can help to get the buttons directly to the GUlike this;
    
19. Datasheet on Allwinner T3here;
    
20. Experiencerecoveryfrom bootloop;
    
21. Instructionto restore bricks with USB firmware via computer and PhoenixTool, andadditionto the instructions. Testedhere on 4.4 Androidandhere at 6.0 (present). Who has a microSD slot, you can try and easier -write down(see p.1-4 instructions) specialbootable uSD cardWith the help of the Phoenix Tool, insert it into the PG and turn on the power. Only one of the two usd slots is bootable.Reportabout successful experience;Another option.
    
22. Radio and music playerin black tone;
    
23. After entering the engineering menu with a password of 16176699 instead of 1617 in itappearadvanced settings, like Style setting.Password there111333. Change the setting to 1,2,3,4changes the look of a native launcher;
    
24. Instructionson batch installation of applications, installing butanimation and static logo, bulk copying files, Russification of applications and firmware;
    
25. List of supported modemshere. As a rule, the old Huawei modems work well, the new ones should be switched to the "only modem" modeHilink. 4G works fineonlywith HiLink or external router. General theme on modems on Androidhere;
    
26. Connecting an OBDII adapter (elm327) to a PG via Bluetoothdone like this. Instructionin picturesandvideoconnect.maybe, GU requires that the OBD adapter name in Bluetooth is strictly OBDII;
    
27. Adding root to the firmware when it is modifieddone like this;
    
28. Setting the parameters of the PGand enable / disable various types of launcher via the FactoryRuleConfig.xml parameter file;
    
29. Marking of wires and connectors GU -time, two, three, fourandfive. There are many options for connectors and pinouts GU, be sure to check the match twice before use;
    
30. White list, videoSettings to prevent unloading programs from the memory of the GU. Options forradioandGPSif there is no white list.Turning onwhite list through build.prop (requires root);
    
31. Translation GU inprogramming modevia USB with unsuccessful firmware and downgrade from Android 6.0 to 4.4.Additionandabout rebuilding the firmware imagein .img with partition redistribution;
    
32. Repair and flashing GUafter unsuccessful display settings with auto-run firmware via update.script. In the developer menu 4k display resolutiondo not turn on, do not exit this mode without flashing!
    
33. Amplifier Chip Replacementfrom TDA7388 to TDA7851A and additional cooling.Still, about replacing the amplifier on the TDA7851L;
    
34. Enable and configuremulticolor backlit hardware buttons. It works only if you actually have installed three-color RGB LEDs in the panel;
    
35. Backupand restore (not verified!) firmware image via the terminal / ADB. Requires root. The image is a copy of flash memory and is not suitable for firmware from the standard procedure, only through dd;
    
36. The sound of Android may disappear after a flashing if the I2S jack is installed in the Customized Settings in the engineering menu;
    
37. If after exporting the settings to a file in the engineering menu of the GU, when turned on, it writes Find factory config file, do you want to import? you must find this file (s) in the root of the external storage media, or the internal memory where you saved it, andremoveor movein a subfolder. You can navigate by date of creation, most likely, the file type .xml;
    
38. Pinout and touchscreen connectionherereplacement screenhere;
    
39. If you do not put applications through the Play Market, it will probably helpdisable fake locationIn the regular menu of the Android developer.Still;
    
40. If navigation mixing does not work or the player’s sound is knocked out while IgoPrimo is working, iGO sound settings and voice prompts should be setlive voice;
    
41. The sound of incoming calls can be changed,replacing the ring.mp3 filein the system folder. Root is required. Do not forget to return the rights to it, as they were;
    
42. ON GU on 6 Android does not start the Play Market immediately after resetting to factory settings, hangs withwhite screen? Need a couple of timesrestartGU (completely, without going to sleep, you can click Reset - and allwill earn. If this does not help, you needremove updatesGoogle Play and Playmarket services through Settings->Device->Applications, find both of these items and remove updates (three dots in the upper right corner);
    
43. To use an analog camcorder as a recorder, you need in Factory setting - Feature Settingscheck CVBS-DVR, DVR will appear;
    
44. Russian language setting is donefirst in the engineering menu, and only then in the Android settings menu;
    
45. Mirror or not the image will be from the back of the cameraconfigured here;
    
46. Enable built-in GU360 viewing systemwho has the hardware;
    
47. ComparisonCPU temperatures in idleon firmware with 4.4 and 6 Android;
    
48. When installing a third-party launcher, when you start the GU, the native radio or music is still turned on, which worked last when turned off. If it is not necessary, it is necessaryedit file/config/app/ApplicationList.xml. There, find com.nwd.radio and replace it with an empty string or with the name of your launcher’s package.disadvantagesthis way. Stillreplacement information;
    
49. Setting up the analog buttons on the steering wheeldone like this;
    
50. Matrix in GU 9 'resolution 800 * 480 -AT090TN10;
    
51. Calibration file of touch-screen GU with 9-inch diagonal, 800 * 480 resolutionhere, 8 inches 800x480here. 7 "resolution 1024x600here. Another one for 1024x600 resolutionconfig, 7 or 8 ". Another 7" 800x640here. Stillfor 9 "1024 * 600. Export calibration filedone like this. Useonlyfile with the same resolution and size, and it is better to save your own in advance;
    
52. About setting to reduce the brightness of the display when turning on the dimensions of the wire ILLumination-timeandtwo;
    
53. Disable Chinese voice assistant (circle with microphones, ason the picture) - disableCustomized Setting - Voice analyze and Activate voice analyze, andBasic settings - Assistive touch and touch the left button;
    
54. Connectionunder the steering wheel control buttons for owners of Renault Fluence, there is a matrix instead of the usual resistive buttons;
    
55. Screenshotdone like this- you spend two fingers from the right edge of the screen to the left;
    
56. About the standard equalizer. In fact, there is only the adjustment of low, mid and high frequencies, otherwisecan not audio DSP, and the equalizer in some multiband firmwares is more for beauty. For the sounds made by Android, you can putViPER4Android;
    
57. Enable RDSandtuningradio sensitivity in the engineering menu,check. If you have a radio button LOC or Local -turn it offThis is a mode of forced degradation of the receiver sensitivity, so that only local (with a strong signal) radio stations are caught;
    
58. How to distinguish amplifiers on the TDA7850 / TDA7851L from the TDA7388 without disassembling the PG, and also how to identify the remarked (forged) TDA7850 -video;
    
59. The program "NWD Key Mod", designed to adapt the trained steering buttons (Next and Prew) for third-party music players, such as CarWebGuru Launcher, AIMP, and other standard Android media buttons. "NWD Key Mod" helps to switch tracks back and forth, only with active audio stream;
    
60. Customizationanimation downloads(boot animation) -picture instructions;
    
61. Firmware with an index (letters) CLD are putover the firmwarewith YZG index. If it doesn't help, trySo;
    
62. If you need to roll back to the old firmware, but it is not put with a message about an older version, it can helpupdate date in build.propand re-sign the firmware (see several posts in the discussion). But maybenot help. Need to replacesome more filesand folders;
    
63. Schemethe use of the relay REGTIM3-12- (0-60) for the delay of switching on the PG;
    
64. If there are not enough USB ports, USB hubs work with the GU. Exampleshereandhere;
    
65. For GPS in different versions of the state are usedSMA and Fakra connectors. If gpsdoes not see satellites in GPStest, and the time and time zone are correct and the Internet for AGPS may bea business at the antennaor connector.Disassembly instructionsFakra connector;
    
66. If you accidentally put a pin-code on the GU in a third-party program (there is no standard menu for settings), you can delete itlike this;
    
67. Connecting an external touchscreen controllerhere;
    
68. Updates of the Easy Connect utility (MirrorLink) for connecting an Android / iOS phone to a GU are simple and straightforwardherewho is not afraid of incomprehensible languages ​​-here(a little newer);
    
69. In the recovery you canget there, if you connect a USB keyboard, and while holding Alt + PrintScreen repeatedly press (or press and hold) "i" during normal operation of the PG. After the reboot, it must enter recovery. You can also hold Alt + PrintScreen and quickly press i when booting GU, as soon as the auto logo appears, until the Android text appears. Techniquefrom R16.
    
70. Firmware APPVER: K2001M_GDH_S212101.20171114.17504893.N0022 and the attached config file from it with the working camera -here
    
71. Four-finger method for reset and emergency flashing -here
    
72. Wildly blinksscreen flickers.
    
73. Patch in the form of firmware update.zip which translates the radio tape recorderin firmware mode on PC
    
    

Cap changes

1. 08/20/2017 Topic created;
   
2. 08/23/2017 Clause 7 FAQ added;
   
3. 08/24/2017 Clauses 8-9 FAQ added, 6 and 5 updated;
   
4. 08.27.2017 Updated clause 9 of the FAQ, updated the FAQ-identifier of the GU;
   
5. 08/29/2017 Added paragraph 10 of the FAQ;
   
6. 09/02/2017 Added firmware fromtasty85;
   
7. 09/04/2017 Paragraph 11 of the FAQ is added, firmware from 08/25/2017 and update instructions in pictures are added, the firmware section is redone; Added link to the topic of Ezonetronics RM-CT0008;
   
8. September 6, 2017 Added to paragraph 12 of the FAQ;
   
9. 09/07/2017 AudioDSP CSC37534 (analogue of ROHM BD37534FV) has been added to the specifications and a link to a photo of the supercompact PG;
   
10. 09/26/2017 Clauses 13-14 FAQ, TEA6856 added to the radio modules;
    
11. 09/27/2017 Added information about GU on Android 6.0 in the description;
    
12. 09.28.2017 Added clause 15 FAQ;
    
13. 10/01/2017 Clause 16 added to FAQ, supplemented with item 1;
    
14. 10/02/2017 Supplemented by paragraph 2 of the FAQ;
    
15. 10/03/2017 Added paragraph 17 FAQ;
    
16. 10/5/2017 Added clause 18 FAQ;
    
17. 10/06/2017 Added paragraph 19-20 FAQ, firmware from 08/18/2017;
    
18. 08.10.2017 Supplement p.7 FAQ;
    
19. 09.10.2017 Added p.21 FAQ, firmware dated 09.22.2017, Android 6.0 added to the topic name, p.2 modified FAQ;
    
20. 10.10.2017 Added a photo of the processor board with the cover removed, pp. 22-24 FAQ added, firmware for K2101 and firmware K2001 in .img format;
    
21. 11.10.2017 Updated clause 21 of the FAQ;
    
22. 12.10.2017 Updated clause 21 of the FAQ, added in the firmware Android 6.0;
    
23. 10/14/2017 Added p.25 FAQ and a link to a copy of the firmware repository;
    
24. 10/16/2017 Added firmware dated 08/11/2017 800X480;
    
25. 10/17/2017 Added compatibility information for K2101 and K2001 from NightManOs;
    
26. 10/19/2017 Added custom firmware fromser39;
    
27. 10/20/2017 Added p.26 FAQ;
    
28. 10/22/2017 Paragraph 7 of the FAQ is added, a link is added to two more firmware fromser39;
    
29. 10/24/2017 Added link to updated firmware fromser39;
    
30. 10.27.2017 Added p. 27 FAQ and custom firmware with root-rights;
    
31. 10.28.2017 Added p.28 FAQ and another custom firmware fromMonakov86with root-rights, as well as a warning about the resolution of the display in the firmware.
    
32. 10/30/2017 Updated to clause 7 of the FAQ, added a link to the custom firmware frombrunokvs;
    
33. 11/01/2017 Clauses 29 - 31 FAQ and the link to check the firmware for K2101;
    
34. 11/02/2017 Paragraphs 31 and 31 of the FAQ are added;
    
35. 11/03/2017 Updated clause 16 FAQ;
    
36. 11/05/2017 Added firmware for K2101 from 10/26/2017;
    
37. 11/06/2017 Section 32 of the FAQ is added, a link to the custom firmware fromser39;
    
38. 11/07/2017 Supplemented with clause FAQ;
    
39. 11/09/2017 Added p.33 FAQ;
    
40. 12.11.2017 Updated paragraph 6 of the FAQ;
    
41. 11/13/2017 Updated to clause 7 of the FAQ - screenshots of the engineering menu settings;
    
42. 11/14/2017 Added firmware fromser39for 1024x600, added clause 34 FAQ;
    
43. 11/17/2017 p.35, 36 FAQ added;
    
44. 11/19/2017 Photos of K2101 are added with wiring on just one board, without a child processor;
    
45. 11/21/2017 Added paragraph 37-40 FAQ, added 26 and 29, added firmware K2001M_YZG_S212104.20170929 on 6 Android;
    
46. 11/22/2017 Updated to clause 29 of the FAQ;
    
47. 11/23/2017 Added paragraph 41 of the FAQ;
    
48. 11/26/2017 Added paragraph 42 of the FAQ;
    
49. 11/27/2017 A link to a photo of a PG with a pinout on just one board added;
    
50. 11/29/2017 Section 43 of the FAQ has been added, a direct link to the mirror has been added to the inaccessible more link to old firmware and MCU, cosmetic changes to the header;
    
51. 11/30/2017 Added MCU for another radio module, added to paragraph 5 of the FAQ;
    
52. 12/02/2017 Item 44 has been added, clause 16 of the FAQ has been added;
    
53. 12/04/2017 Clauses 45, 46, 47 were added, the error in clause 43 of the FAQ was added, firmware K2001M_SPDZ_S212202.20171018.9290996 was added;
    
54. 12/08/2017 p.48 added; 49 FAQ;
    
55. 12/09/2017 Design of the firmware section has been fixed;
    
56. 12/10/2017 p.50-53 FAQ added;
    
57. Dec 11, 2017 Supplemented with p.33, 48, 51 FAQ;
    
58. 12/17/2017 Updated clauses 6, 42, 51 FAQ, added 54-57, updated links to firmwareser39;
    
59. 12/18/2017 Added firmware for GU in case for installation in BMW X3 E83;
    
60. 12/19/2017 Updated to paragraph 6 of the FAQ, added firmware K2001M_XZ_S212305.20171103.17413320, added cross-references to the T3 topics at the top of the header;
    
61. 12/21/2017 Added firmware K2001_XZ_S212304.20171024.15374904, added with Clauses 1 and 17 FAQ;
    
62. 12/23/2017 Added p.58 FAQ, added link to modified firmware fromNightManOs;
    
63. 12/24/2017 Paragraph 7 of the FAQ is updated;
    
64. 12/30/2017 Updated p.48 FAQ, added p.59-60, added firmware K2001M_JSH_S212104.20171031 (for RM-CT0018);
    
65. 12/31/2017 Added firmware K2001_XSY_S212409.20171114.15165058;
    
66. 09/01/2018 Supplemented with p.1, 15 FAQ;
    
67. 01/10/2018 Added p.61 FAQ;
    
68. 01/14/2018 Added p.62-65 FAQ, added more photos of GU;
    
69. 01/17/2018 Added firmware K2001M_JSH_S212203.20171109.14491402 and K2001M_CLD_S212208.20170725.16571039, mod NEW.K2001_XSY_S212409.20171114, added p.62 FAQ and added p.66, 67;
    
70. 01/21/2018 Added modified firmware K2001_YZG_S212104.20170825 and K2001_GDH_S211102.20171117.1132324988 fromser39, added p.68 FAQ;
    
71. 01/22/2018 Updated clause 21 of the FAQ, added a link to the modified K2001M_JSH_S212203.20171109 and corrected for K2001_GDH_S211102.20171117.1132324988, added n.69 FAQ.
    

Attention! Discussion of the original version of the GU on Allwinner T3in this threaddiscussing the new versionin thisA discussion of the K2001 version is here. Iron and firmware of different versions of PG are not compatible.
To understand what topic you are in - look at the Android settings menu. Does it have a menu block on the left, and does the firmware version start with K2001? You're at the place. Is it in white letters on a black background? This is the original version, youhere. Is it in black letters on a white background? This is a new version of the GU, youhere.
Not sure - hereFAQ-type GU, or bring here a screenshot of the menu system, they will help you.

Topics Curator:

There is no curator in the subject. For questions about filling caps, please contact the section moderators via the "Complaint" button under the messages to which you want to add links.

M

Withdrawing from supervision

Post has been editedkumarai - 10.04.19, 22:29

[tasty85]

alexk2019you have some gu? Touch buttons? Or mechanical? If the sensor, then try to take the wire key1 short circuit on the body and turn on Gu. Is there a photo?

[alexk2019]

Touch buttons, a photo under the spoiler in the cap is the one that Android 6.1.1 is my radio tape recorder.https: //www.aliexpress...g0s.9042311.0.0.xKs13e

Post has been editedalexk2019 - 25.08.17, 18:33

[alexk2019]

Touch buttons, a photo under the spoiler in the cap is the one that Android 6.1.1 is my radio tape recorder.https: //www.aliexpress...g0s.9042311.0.0.xKs13e

[tasty85]

alexk2019try as onvideocan enter recovery mode. On my gu did not work.

Post has been editedtasty85 - 25.08.17, 21:50

[deason]

Help me flash
I insert a USB flash drive with files as in the instructions:
Update.zip
Update.script
The reaction of the radio is zero. Nothing happens at all. What else to do? GU with dodelikonom 5.1

[Shamyrai]

deasonand where to get the update.script file? but it only downloads Update.zip

[deason]

ShamyraiI took from another firmware from the cap

[tasty85]

deason, try through the menu, password 1617

[deason]

tasty85,what menu? More? What application?

[Shamyrai]

deasonCan you attach a file here)?

[tasty85]

deason, car setting mine there is an item to update, insert a flash drive and click update.

[deason]

Understood. Really CarSettings - Factory Settings. There is an update menu.
If you do not see the update.zip update file on the USB flash drive, then you need to flash the USB flash drive to another USB port. Ports are called differently. My SD card is not suitable for updating. Only USB and only one port ...

[bazanovv]

deasonThanks, in the cap. And finally it turned out to write the FAQ-determinant on the general model.

[chip06]

Good day. I am the owner of the same radio. I decided to flash the latest version of the android from the header, write the files to the root of the sd card, insert, pick up everything, start the update, reboot, pass a quarter of the boot slider, error pops up and write something like: data wipe failed, reboot in a minute , loaded, everything becomes from scratch, and the version is not updated. What am I doing wrong?

[bazanovv]

chip06,Perhaps you should try to reset the GG to the factory settings first and then update. It may also be worth trying to update through the menu, without a script, but not sure. If the hardware error, or the firmware does not fit, there is a good chance of getting a brick.

[tasty85]

chip06, archive update.zip did not understand? Nothing changed in the archive?

[Shamyrai]

and my update button in the firmware never became active ((I tried the two usb ports all early neither

[Vacilich]

Shamyrai @ 08/29/17, 06:39

and my update button in the firmware never became active ((I tried the two usb ports all early neither

try writing to SD and inserting it into the SD port

[deason]

Try the file manager to find the firmware.
Compare the actual path with what is registered above the "Start update" button.

[tasty85]

How to sign zip android firmware (update.zip)
Sometimes after editing apk-files or replacing files in zip-firmware (update.zip) you need to sign them. There are many solutions for collecting and signing zip-firmware (update.zip), but this method is most suitable for our GU.
So let's get started !:
1. first, download JAVA JDK runtime environment fromthe site(see picture number 1).

Snapshot number 1
The following is necessary to choose the 32-bit or 64-bit version of the JDK version (see picture number 2).

Snapshot number 2
After downloading you need to install and configure.
To configure the JDK, you must right-click on My Computer] - [Properties] - [Advanced System Settings] - [Environment Variables], as shown in screenshot # 3

Screenshot # 3
In the window that appears, you need to create a system variable - “JAVA_HOME”. To do this, click the "Create" button. In the “Variable Name” field we write “JAVA_HOME”, and in the “Variable Value” we need to add the path to the installed JDK, namely the path to its bin subdirectory where the compiler file is located. If you did not change anything when installing the JDK, then the path would be: "C: \ Program Files \ Java \ jdkVersion Number". The picture below shows an example for the Java 8 version. See screen shot number 4

Screenshot 4
Now you need to edit the variable “Path”. It is necessary to find it in the list and click the “Change” button, just in the “Variable value” field just add our path C: \ Program Files \ Java \ jdk1.8.0_144 \ bin \ for the current version of java 8, respectively putting the first “;” at the end of an existing value, without deleting anything! An example is shown in screenshot 5.

Screenshot # 5
After making these changes, the computer must be restarted for them to take effect.
After that, you can check the correctness of the JDK installation. To do this, click “Start” in Windows and enter the cmd command in the “Search programs and files” field, or call the input window with the key combination Windows + R and enter cmd see the screenshot from screen number 6

Screenshot # 6
In the console that opens, type java -version and press Enter. If you see the java version and not the error message, everything is fine.
2. Download the program SignApkV2 link

Screenshot 7
After unpacking our archive file SignApkV2 in the root of the disk “C”, see the screenshot from the screen №№8,9

Screenshot number 8

Screenshot # 9
3. We sign our firmware update.zip.
To sign the edited firmware update.zip, we need to delete the three signature files CERT.RSA, CERT.SF and MANIFEST.MF which are in the archive in the \ META-INF \ folder \ see screenshot from screen number 10

Screenshot number 10
We put the prepared firmware into the SignApkV2 folder which is located in the “C” drive, see screen shot # 11

Screenshot number 11
Then, run the SignerScript batch file with the extension (.bat) to sign our firmware, see screen shot # 12.

Screenshot number 12
After the process is completed, a signed archive file update_signed.zip should appear in our SignApkV2 folder. See snapshot from screen No. 13.

Screenshot number 13
The signed archive should be like in the screenshot from the screen в„–14

Screenshot number 14
Good luck to all!