Umecity (VW): Allwinner T8, 2GB/32GB, 7.1.2, 9" 1024x600, Shallow 2din [2017/11]

Search This thread
By:
Advanced…
S

Slini

New member
Nov 12, 2019
4
0
Hi all,
I did a factory reset on my Allwinner T8 and now i am missing the whole google services, as google play store, Chrome and so on. I am new here and i don't know what apk i need to install to make all google service working again.
Can someone give me some advise please?

At the moment i have the problem in google play store, when i open the store it ask me to login, when i klick on the the login button nothing happens. So i am unable to login and donwload anything.
 
Last edited:
A

atp2kk

Member
Jul 16, 2019
27
1
Hello.

How I can make backup to file from my firmware?

I have Allwinner T8

Thanks

Wysłane z mojego SM-N960F przy użyciu Tapatalka
 
T

Tazc

Member
Oct 3, 2019
19
3
new firmware Asottu unit CDZ8060 - V9.4.1

Hi all,

Plase find a link for the new firmware Asottu unit CDZ8060 (Allwinner T8 based) :
V9.4.1_20190829.100539_AKW1-FD

link:
"dropbox.com/s/ow7jf08ozguo1am/V9.4.1_20190829.100539_AKW1-FD.rar?spm=a2g0s.imconversation.0.0.6dc33e5f3F665r&dl=0"

Installed on my device and works fine.

Does someone knows how to root this firmware (magisk does not manage to root it) ?
Thank you
 
V

virgil75

New member
Aug 1, 2019
2
0
eonon GA2167

hello everyone I have a navigation Eonon GA2167 who does not want to display anything on the screen the power button off and the LEDs work but nothing is seen on the screen and no more is heard in the speakers please if anyone can help me I have not tried root thank you
 
T

toffermaramba

Member
Sep 20, 2014
9
0
can anyone pls help me with my Headunit, Bluetooth is not working, android version is 8.1.0, mcu version is t8.3.19-203-10-a46101-180726, system version is V9.3.1_20190107.101623_TQ1_FD...
 
Y

yeekli

Member
Mar 4, 2011
44
15
****-jones said:
yes

Your thread https://xdaforums.com/android-auto/...ner-r16-astard7-android-6-0-1-t3523906/page72
Click to expand...
Click to collapse

****-Jones,

Thanks for all your work for making great KED-1 mod for the head unit.

I am currently runs your V7.3.2_20171116.202256_KED1 build. Which works 100 times better than the original one from the manufacture (EinCar).

Just wondering what's the change on the "V7.3.2_20180124.145308_KED1-mod", I am planning to upgrade, but could not find much information about your 20180124 build. By the way, is this the latest?

Thanks a million for you contribution.

---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
****-jones said:
yes

Your thread https://xdaforums.com/android-auto/...ner-r16-astard7-android-6-0-1-t3523906/page72
Click to expand...
Click to collapse

Dear ****-Jones,

Thanks for all your work of making such great KED-1 mod for the head unit.

I am currently runs your V7.3.2_20171116.202256_KED1 build. Which works 100 times better than the original one from the manufacture (EinCar).

Just wondering what's the change on the "V7.3.2_20180124.145308_KED1-mod", I am planning to upgrade, but could not find much information about your 20180124 build. By the way, is this the latest?

Thanks a million for you contribution.
 
andason

andason

Senior Member
Mar 6, 2006
289
32
Anyone familiar with:

Octa-sp9853i
Android 9.1
MCU Ts9.4.3-63-300-CO66a1-190618
System V11.1.1_20191022.143838_ZH5-X

Looking for MCU and other general information.
 
F

franjaco

New member
Sep 22, 2005
1
0
What sort of device have i got

Hello Everyone, i hope someone can help me out. I have bought a used Android Radio but for some reason the screen keeps freezing. Only a reset can make it work again.
The previous owner has no clue what type of device he sold me.

What do you think? Try to use the Firmware or does anyone recommend a different software? Many thanks in advance and happy New Year
 

Attachments

  • IMG_9332.jpg
    IMG_9332.jpg
    268.8 KB · Views: 153
S

Stacyboy

Member
Oct 11, 2012
21
6
Hi all,

I have a Eonon GA2168 UltraOcta-T8, Android version 7.1.2, MCU: T8.3.19-108-8F-946101-171011-GMC.
System version is: v9.2.2_20171127.14127_KBT8-FD

Does anyone has a newer firmware (preferable rooted)?
 
Last edited:
G

gwaitsi

Senior Member
Aug 3, 2014
144
9
hey guys, i would not recommend this supplier. their support is no existent to say the least.
I have the following for a 2009 RAV4
MCU: T8.3.19-16-10-616101-180917
System: v9.3.1_20180921.161829_ZHC3-EN-FD
The problems I have;
- none of the passwords around (or what the say 668811) work for either Extra or Factory Reset
- when any navigation s/w e.g. sygic, igo, google, etc is supposed to the speaking, radio cuts out but no instructions can be heard (have tried changing sound stream values in iGO)
- they are unable to provide any useful info in relation to re-using factory fit camera

The latest MCU they sent me was T8.3.19-145-10-C06101-180718 - but they seems an older version to the unit i got.

In summary, the Allwinner T8 has virtually no good support.
The PX? series is much better supported (particularly on this forum) with a comprehensive set of MCU / System upgrades available.
For the PX5, i was able to change from LM to HA thanks to the great efforts of people on this forum and solved all the issues i had with the Skoda Superb eunavi HU.

Nevertheless, would appreciate if someone is able to help resolve my issues for the T8 via an MCU / System update.
 
S

Stacyboy

Member
Oct 11, 2012
21
6
Guess you have already tried 123456 for extra settings and 7890 for developer options, right?

gwaitsi said:
hey guys, i would not recommend this supplier. their support is no existent to say the least.
I have the following for a 2009 RAV4
MCU: T8.3.19-16-10-616101-180917
System: v9.3.1_20180921.161829_ZHC3-EN-FD
The problems I have;
- none of the passwords around (or what the say 668811) work for either Extra or Factory Reset
- when any navigation s/w e.g. sygic, igo, google, etc is supposed to the speaking, radio cuts out but no instructions can be heard (have tried changing sound stream values in iGO)
- they are unable to provide any useful info in relation to re-using factory fit camera

The latest MCU they sent me was T8.3.19-145-10-C06101-180718 - but they seems an older version to the unit i got.

In summary, the Allwinner T8 has virtually no good support.
The PX? series is much better supported (particularly on this forum) with a comprehensive set of MCU / System upgrades available.
For the PX5, i was able to change from LM to HA thanks to the great efforts of people on this forum and solved all the issues i had with the Skoda Superb eunavi HU.

Nevertheless, would appreciate if someone is able to help resolve my issues for the T8 via an MCU / System update.
Click to expand...
Click to collapse
 
W

wacayoub

Member
Mar 4, 2018
11
0
Hello ,
i would like to upgrade my Allwinner T8 from 7.1.2 to new Android Version 9

Processor Type : UltraOcta-T8
Android version : 7.1.2
MCU version : 5.3.19-98-10-e56201-170921
System version : V9.2.2_20180207.142122_AKW1-FD

Could you please share with me the correct link to download this version

Thanks in advance
 
U

UFORudi

Member
Jan 5, 2020
13
0
Allwinner T8

Hallo,
I accidentally put (flash) the wrong MCU file on my device.
Was the original MCU file: T8.3.19-11-71-453101-171129
The original Android file (I didn't changed): V9.2.2-20180201.161555_KED7
The original radio app is not working. What can I do ?
Where can i get the original MCU file ?
 
O

olegvedi

New member
Jan 8, 2020
1
0
Hello

Does anyone have a program to decrypt the kernel firmware file (Kaier support tool)?
I am for personal use.
 
A

atp2kk

Member
Jul 16, 2019
27
1
What is "MCU" ?

When I update firmware, I mean Android next update, then I must install separately MCU?




Wysłane z mojego SM-N960F przy użyciu Tapatalka
 
Last edited:
A

andreapontic

Member
Dec 12, 2013
12
0
Hi guys, I bought a DVD player for E43, everything works except for the wifi that you can't activate, bluetooth works. what can it depend on? I bring you my mcu data and firmware. in case the wifi is broken can I use an external dongle?
MCU: T8.4.19-136-2AE-C03181-190318
SYSTEM VERSION: V9.3.1_20190528.1516_HRX2-i140-CarPlay
ANDROID VERSION: 8.1
 
You must log in or register to reply here.

Similar threads

T
MCU/Android Update to 9.0 - AllWinner T3 P3 Quad Core 16GB 2GB 1024x600 Android 7.1.1
Replies
700
Views
238K
alptekindemirci
alptekindemirci
Rottgrub
Umecity (VW): Allwinner T3, 2GB/16GB, 6.0.1, 1024x600, Shallow 2DIN [2017/04]
Replies
100
Views
68K
I
iPilu
B
Bonroad C1067106A3 Allwinner QUAD CORE T3 P3 2GB RAM 16GB ROM 6.0.1
Replies
272
Views
220K
K
KURECT
LwannaCM
Firmware for Carplay AI Boxes (Qualcomm/Rockchip/Allwinner) Android 7/9
Replies
1K
Views
380K
5646528
5646528
S
Allwinner R16 (astar_d7) Android 6.0.1 Marshmallow - Partition Dump & Information
Replies
904
Views
277K
old.splatterhand
old.splatterhand

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 8
    Rottgrub
    Rottgrub
    You'd think I'd learn my lesson after the last ten head units I've purchased, but I saw the new Allwinner T8 headunits, and decided I wanted to give it a try. The new radio is currently on it's way from China, and I'll be updating this thread as I find out more information.

    Update: Unit passed testing and has just shipped out. Should have it early next week if it doesn't get hung up in customs.
    Update 2: Head unit arrived yesterday (11/28/2017), and I installed it today. Initial updates below.


    [SIZE="+1"]PHOTOS[/SIZE]
    Screenshot_20171130-113605.jpgYoumecity-Android-7-1-Car-DVD-Player-Radio-Gps-Stereo-for-VW-Volkswagen-SKODA-GOLF-5.jpg
    HTB1KECZfLBNTKJjy1zdq6yScpXaw.jpgView attachment 4331016
    Screenshot_20171129-162557.jpgScreenshot_20171129-162602.jpg
    Screenshot_20171129-160550_root.jpgScreenshot_20171129-160656.jpg


    [SIZE="+2"]Umecity (Youmecity) Allwinner T8[/SIZE]
    OS: Android 7.1.2 (Nougat)
    CPU: Allwinner T8, 8-core Cortex-A7 @ 1.6GHz, up to 1.8GHz
    Memory: 2GB DDR3 RAM, 32GB EMMC, 2xUSB2, 1 MicroSD
    Graphics: PowerVR SGX544MP1 GPU (OpenGL ES1.1/2.0 OpenCL1.1)
    Display: 9", 1024x600 capacitive
    Radio Tuner: 7786
    Amplifier: TDA7851
    Output Power: 4x50w
    Dimensions: 220mm x 130mm x 27mm
    Weight: 5kg

    MCU Version: 5.3.19-145-13-A46101-171118
    System Vers: V9.2.2_20171117.102842_JP1-FD
    Linux Kernel: 3.10.65
    Security Patch Level: 2017-07-05, 7.1.2 (Nougat)

    MCU Version: T5.3.19-145-10-C06101-170318
    System Vers: V9.2.2_20170915.144527_JP1

    [SIZE="+1"]Passwords[/SIZE]
    Extra Settings: 123456
    Developer and Reset: 7890


    [SIZE="+2"]Identifying Firmwares[/SIZE]
    [SIZE="+1"]General Information[/SIZE]
    Example: 9.2.2_20171117.102842_JP1-FD
    • 9.2.2 - The hardware version, and android version. For instance, 9 is T8, and 9.2.2 is Nougat.
    • 20171117 - Release date of the firmware in YYYYMMDD format.
    • 102842 - Possibly the build time for the firmware. Uncertain.
    • JP1: The manufacturer ID.
    • FD: ???
    [SIZE="+1"]....by Version[/SIZE]
    Per @bazanovv, "There are 3 different non-compatible versions of T3 hardware and software, Default one (sleep mode added later and not so good), New one (firmware is a development of R16 branch), and K2001 (usually very compact and cheaper). Allwinner T8 head units continue and develop the same firmware branch - V9.x.x on T8, V8.x.x on T3 New (V8.3.x with Android 7.1) and V7.x.x on R16. Most tips and tricks from T3 (new one) will work on T8."
    • R16 - 7.x.x
    • T3 - 8.x.x
    • T3 - 8.3.x - Android 7.1, Nougat
    • T8 - 9.1.1 - Android 6.0.1, Marshmallow
    • T8 - 9.2.2 - Android 7.1.2, Nougat
    [SIZE="+1"]...by Manufacturer[/SIZE]
    From information gleaned mostly from various threads over on 4PDA, it is advised to not install firmwares from another manufacturer, unless it has already been patched to be universal. Issues such as red messages at the bottom of the screen, or unsupported hardware can result.
    • JP1 or JP1-FD: Umecity
    • TW2-FD: TopWay
    • KED3-5: Kaier



    [SIZE="+1"]Allwinner T8 Documentation[/SIZE]
    www.allwinnertech.com/uploads/pdf/20160515151908f5.pdf

    [SIZE="+1"]4PDA Discussion Thread (Russian)[/SIZE]
    https://4pda.ru/forum/index.php?showtopic=875407

    [SIZE="+1"]My Initial Feelings:[/SIZE]
    This appears to be basically the same chassis as the Allwinner T3 units, but with a newer CPU and OS. Unfortunately, they cheaped out a little with the bezel on this one, which didn't include a MicroSD card slot like was on the previous model. This model has the same issue of accidentally clicking the capacitive bezel buttons that the T3 had.

    The wiring is a bit of a mess. Some things were obviously just cheaped out on, like boost power for the antenna to the harness should come with connectors already installed. There is a brown/yellow wire pair coming from the CANBUS box that plugs into the back of the unit, rather than connecting via the main harness plug. Just as with the T3 model, the Volkswagen ISO1 harness has an ISO2 harness spliced into it. Having the extra connector leaves the system open to RF interference, and makes the wiring a mess.

    After working with the unit for about an hour, and running the benchmarks, I started to notice some interference from the speakers. It wasn't affected by unit volume, and was present when muted. The noise sounded like either RF interference, or he noise you get when a capacitor is squealing. I did not notice the noise before the benchmarks, and need to see if this recurs on the next boot up. After extensive listening, the noise only seems to occur (for me) after the unit has been powered on for a while, and run hard. Benchmarking, initial setup and app download, etc. Once I reboot, I don't hear the noise anymore.

    For scoring so blandly in the benchmarks, this unit is very responsive. I had no issues or slowdowns running multiple apps at the same time: Maps, Play Music, and Play Store downloading in the background, etc.


    [SIZE="+1"]Some Items Worth Pointing Out[/SIZE]:
    • Bluetooth is for phone use only: I've always been critical of Bluetooth audio quality, especially for music. It's interesting that they point out that Bluetooth only works with one sound channel, so music will not sound good. They suggest music over USB. I'm guessing with android auto, or their EasyConnect mirroring.

    [SIZE="+1"]Tests and Results[/SIZE]
    • Ease of install: Super easy to install, due to the extremely shallow depth of the device. Plenty of room for the wires behind the radio. Only annoyance was the combined ISO 1/2 adapter, which is just a mess.
    • Screen visibility: So far, so good. Less brightness, but better clarity than the Dasaita PX5 unit I have.
    • Deep Sleep: Well, no deep sleep support. Has a few shutdown times, maxing out at 30 minutes IIRC.
    • Boot time: So, the numbers quoted up top are pure fiction. Took ~40s from cold boot to launcher.
    • Backup cam start time: Excellent. Was able to use the backup camera immediately from power on.
    • Antutu Score: ~22500
    • 3DMark Score: Benchmark crashed.
    • Volume scaling: Again, default audio is too freaking loud with my OEM Fender amp. Anything past 4-5 (out of thirty) is way too loud. On the good side, seems the Amp Volume can be adjusted. When set at it's lowest level, the scaling seems to be spot on for my Fender system. Nice!
    • Rootable?: CPU-Z seems to indicate that it is already rooted, however SuperSU states that the su binary is occupied. Need to explore further.
    • Play Store apps: So far, so good. Only missing items in the store were things like Google Dialer, which would have been nice to have.
    • Android Auto: Not available in Play Store. Likely need to fake 720p screen.
    • Google Maps: Works great. No problems in my short test drive.
    • Waze: Works great. No problems that I saw.
    • Voice Search: Not installed by default. Install "Google" from Play Store. Unfortunately, internal Mic couldn't hear my voice in testing.
    • Bluetooth Call w/int mic: No tested yet.
    • Radio Signal: Strong signal, and easily locked to even faint stations.
    • Radio Audio Quality: Meh, it's analog OTA, so it sounds about as good as I would expect it to.
    • CPU Temp: According to Aida64, the CPU temperature idled around 50-60 Celsius, spiking to 74 during the benchmarks.
    • GPS Lock: GPS locked almost immediately.
    • What else should I test?


    [SIZE="+1"]Pros[/SIZE]:
    • Solid build, with shallow design.
    • Easy to install.
    • Google Maps works great, as does Waze.

    [SIZE="+1"]Cons[/SIZE]:
    • Very easy to accidentally click the capacitive bezel buttons. Can sometimes even detect a hover as a touch.
    • Internal Microphone only works with Bluetooth calling.
    View
    5
    dick-jones
    dick-jones
    karldink said:
    Thank you ****-jones. Much appreciated. Will try it this weekend.
    Click to expand...
    Click to collapse
    @karldink, @lr_man, @majsab, @sparrion

    Link to the modified firmware V9.2.2_20180310.092220_KBT8-FD-mod
    :eek: :eek: :eek:
    View
    4
    dick-jones
    dick-jones
    majsab said:
    Could you upload a new link to the firmware please? The link is dead. I am looking to update the firmware of my ga8150a as well.
    Click to expand...
    Click to collapse

    Link to the original firmware https://drive.google.com/file/d/1CPQEnTfxmCaSkdN8SfLhSNO6foA4hqyc/view
    :D sorry...
    View
    4
    B
    bazanovv
    hal752 said:
    This is my 6.0 software
    Click to expand...
    Click to collapse
    First of all, I would like to say that @Rottgrub is ultimately right, and you should not try to flash MCU if not absolutely sure / have a backup image of yours and ready to brick the HU.

    Could you please double check the link and file, because on your screenshot you have Allwinner T8 with Android 6.0 - V9.1.x firmware branch, version V9.1.1_20170830.183839_KED3-5, while filename on your link says it is V8.2.3 (V8.2.3_20170927.200111_KED3-5.rar), which is Android 6.0 too, but for different CPU - it is a Allwinner T3 firmware branch.

    Connection of OBD2 (ELM327) adapters, as well as all other non-phone (headset) devices by Bluetooth on HU is a difficult and complicated process. Firmware and MCU updates both frequently required, and still it is a lottery, it may work, or may not. All non-standard Bluetooth devices will most likely not work. This happens because Bluetooth module is managed by MCU, not Android, is not native to Android, so it will newer work as good as on your phone. This was made, huh, to connect your phone to the HU as a handsfree device. Default Android BT software stack can be a server device on A2DP and HF profile, but can't be a client, like headphones. HU, in it's turn, must be like a headphones. Here be dragons.

    Known problems with OBD2 adapters are that password for adapter and set in BT settings must be the same and set, most frequently, to "1234". You should connect OBD2 in HU Bluetooth or Phone application, not in Android BT settings (may be called by shortcut, but will not work correctly). Bluetooth device name of OBD2 adapter must be exactly "OBDII", others will work OK with your phone, but not with HU. It seems that some fixup procedures in the code are linked to BT device name. And even if all of this is true, it seems that T8 firmware is still under development and do not work with any type of OBD2 adapter.

    Most probably, you will be able to upgrade your Android 6.0 firmware to the new one on Android 7.1, but this process is a bit more complicated and dangerous then regular firmware update. If something goes wrong, HU turns into a brick, software does not work as you want or expect - you have been warned, it's your own responsibility only.
    1) First of all, get a backup of your Android and MCU firmware from the seller, or, if this is not possible, get Root, install this backup tool for R16 and make a backup of all Android partitions, and MCU partition. It is untested on T8 yet, but it's better to have this backup, then nothing. This tool just do dd from known partitions and copy them to file, that's why root required. It may try to restore as well, but this is more risky.

    2) As you may notice, firmware update files are named like GUID's, three files .0 .1 .2 with main Android image, split into 3 parts, and smaller boot partition for Android. Names for Android 7 on T8 are well-known:
    b278023e-7757-11e7-bb3a-07933d230b22.0, .1, .2 - main Android image;
    b1604ca8-7757-11e7-906d-3390eed0c0c2 - boot (Linux core);
    bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 - MCU partition for Android. DON'T FLASH it, if not 100% sure it is from yours or hardware compatible (same Radio, DSP, etc) HU. Delete this file instead, details later.
    203affea-6437-11e6-9d6a-6fc36e3d2c72 - one particular MCU firmware for immediate flashing into the MCU. DON'T FLASH it, if not 1000% sure it is fit your HU, maximal chances to get a brick. Delete this file instead.

    However, names for Android 6 on T8 are unknown. So HU will not "see" and will not start flashing Android 7 files until you rename them to the names that it expects to see. Easiest way to find the correct names - from your firmware you got from seller on step 1, or from any other T8 Android 6 firmware. Btw, if you know any - please share a link. You have to rename files with Android 7 firmware to the names Android 6 firmware expects, and start flashing in usual way. Hopefully, it will work.

    3) As you may see before, firmware version contains letters in the end, "KED3" in your case. This letters name the OEM manufacture name, and must match hardware ID, stored in the MCU firmware. If they will not match, red letters of warning will be written on the top of display: "UI unauthorized, please contact the supplier". It will not affect regular operations, but is very annoying. To delete this, you may zero out this ID in ro.fota.device string in /system/build.prop. Get Root, search for the string "ro.fota.device=" in the build.prop, find OEM letters like TW2-FD or KED1 or JP1 (or others), according to firmware, and then 4 digits of ID. Replace ID with 4 ASCII zeroes, so from ro.fota.device=KED1_0011 you will get ro.fota.device=KED1_0000. Remember about Linux cr/lf, don't edit build.prop with notepad, and restore access rights, or you will brick the HU.

    Alternatively, you may edit this string in the firmware files before flashing, and then sign the modified firmware. Manual here.

    4) Unlike other HU's, this firmware branch (starting from R16 / T3 new one / T8) do have a set of MCU files, different for different car models, stored in the separate Android partition (size 16 Mb). MCU flash size is 128 kb, so lots of them can fit onto this partition. Then you choose car model, HU selects proper MCU file from this partition, flashes it into the MCU, and then reboots. So you must not touch it or switch it off during car model select, or it will become a brick forever, and you should not select the model too frequently to save a MCU flash programming cycles. This mechanism was developed, because CANbus MCU code is different for different cars, and code for all cars does not fit the MCU flash size. Even more, different MCU may and do have different code for Radio module (mostly TDA7786/TDA7703/TEF662x) and audio DSP (mostly TDA7729(TDA7719)/Rohm BD37xxx), if you flash the wrong one, you loose Radio or sound and ability to regulate it).

    This partition gives you a unique chance to backup MCU set before flashing it (see p.1). It may be saved and flashed back with the root and backup tool or just dd (I haven't test it!!! su cd /dev/block/by-name dd if=private of=/usb0/private.img bs=4096). MCU firmware usually encrypted, and can't be read back from the MCU, so for other HUs there are no way to backup existing MCU firmware, unlike this one. However, if you accidently flash firmware with the MCU set file bd07a5ee-fbb0-11e4-ae78-000c29ba27c0, it will overwrite this partition. If this file does not fit your hardware, you will not get a brick - because, unlike 203affea-6437-11e6-9d6a-6fc36e3d2c72 file, only Android partition is flashed, MCU flash remains the same - but you will loose ability to select car model in the factory settings menu, because no suitable MCU is found for your hardware ID in the MCU partition.
    Hardware ID, Car model, Radio, DSP and lot of other features are encoded in the MCU name.
    T5.3.19-hwID-carID-С06101-YYMMDD there С06101 is a Radio, DSP and HU features bitmask. Some may be decoded with the old MCU+1.4+(+4core).exe decode tool from R16. It does not fit exactly, but may give a clue. MCU firmware name should be entered without the T letter in beginning, like 5.3.19-145-10-С06101-170318.
    You see, MCU issue is quite complicated, right? So, if you are not absolutely sure - don't flash the MCU!


    Based on 4pda.ru materials.

    P.S. As far as I know, there are no known way to get a root on T8 with Android 7 yet. You have to disassemble (take apart) firmware, insert there files for root, and then assemble and sign it back, or wait, until somebody do it for you. Unfortunately, there are no detailed step-by-step manual available, and I am unable to create it, because my knowledge is not enough.

    ---------- Post added at 04:16 PM ---------- Previous post was at 03:59 PM ----------
    warata said:
    I tried an external microphone, but It didn't work my own dynamic microphone.
    I think that this product uses a condenser microphone.
    Click to expand...
    Click to collapse

    It definitely uses the condenser microphone with phantom power. To say even more, it's internal microphone is connected electrically parallel to the external microphone socket, so connecting dynamic microphone will just shortcircuit it and make both unusable. Some people make a microphone jack with the switching contact, so then external mic inserted, internal will be switched off and don't collect car noise.

    Meanwhile you may try any PC computer microphone, they fit ok. Only one problem to consider - HU mic connector is a mono type, so if computer mic do have a stereo connector, it may fit bad and signal pin (right channel) may be connected to the ground. If right and left are connected inside the jack, both will be connected to ground and mic don't work.
    View
    4
    dick-jones
    dick-jones
    gormiza said:
    Firmware with the root, red inscription removed. The work has been verified. You can bet on any T8. https://yadi.sk/d/UUxMzhZz3QXE6K
    Click to expand...
    Click to collapse

    The firmware does not have one file, b1604ca8-7757-11e7-906d-3390eed0c0c2 file missing!

    Please return the file to the archive with the firmware. Thank you.

    Here is a link to the entire firmware from the author's mod V9.2.2_20171026.152904_KED1-mod
    View

New posts