yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] jpapadami:
Try these steps when connecting you're ODB2 and installing Torque Pro.

1 install the torque app but don't open it

2 without opening the app connect the adapter to your car and then to the unit

3 something will pop up and ask what app you want to use for the usb device. select "torque"

4 when torque opens go into obd settings , look for connection type and select usb

5 scroll down to "USB Device" and select your device.

(if step 5 doesn't show your adapter quit the app unplug the adapter from the usb and reconnect it and try again to see if your device appears)

6 after you select your device quit the app

7 disconnect and reconnect your adapter from the usb

8 the app should start by itself and select it as default and the adapter should connect.

(if it doesn't connect you might need to check or uncheck some stuff in settings)

Also keep in mind that you might have to change the baud rate from automatic to something else to establish a connection to the ECU. I remember on my generic adapter I changed it to I believe 45000 (it's the first baud rate after automatic) while on my OBDLink SX it works on automatic.

---------- Post added at 08:59 AM ---------- Previous post was at 08:58 AM ----------

https://yadi.sk/d/f7QMleJDSNYoj

---------- Post added at 09:08 AM ---------- Previous post was at 08:59 AM ----------

So then I guess that this is a 4.1 version and not a 4.2 fake? Have you tried it yet?
[Android Head-Units] latino-7:
Baidu Russian2.4.6

https://www.dropbox.com/s/urpl77vivihntwt/Baidu_Root_v2.4.6_rus_by_maksnogin.apk?dl=0

---------- Post added at 06:56 AM ---------- Previous post was at 06:35 AM ----------

Yes is 4.2.2 fake not for the Russian Red Power unit is for the chinese seller

is what I'm using now
[Android Head-Units] Scuddery:
Yea I had that list bookmarked, but Step 3 never happens for me. I've also tried all the baud rates and mixing options, with no success. Even used Dash Command as an alternative to Torque Pro which also didn't work. No matter what, I need that prompt in Step 3 to happen which is the issue.
[Android Head-Units] Skratchuk:
This seems to be 2.7.29.
[Android Head-Units] flblbl:
Can you confirm that the wires key 1 and key 2 are not necessary when using the canbus?

Envoyé de mon MI 2 en utilisant Tapatalk
[Android Head-Units] cool_head:
Yes that's the 2.7.29...

Here is the 2.7.39.. https://yadi.sk/d/ooKWv7HqadjN4

BTW, seems like there's no interest at all to update our file repository.......
[Android Head-Units] Skratchuk:
Thanks, have you tried it? any changes and can it be rooted?

---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------

I know its a shame we need KID52 to update or need another mod.
[Android Head-Units] Skratchuk:
I have tried 2.7.39 and have not been able to root it successfully even with the Russian version of baidu!

IF ANYONE can root it will you please upload the 39 MCU'S. and also let us know how you done it.
[Android Head-Units] jpapadami:
Only other thing that I can think of is use the reformat firmware posted a couple pages back to clean out unit and restore it to factory default.
[Android Head-Units] cool_head:
I can root it with chinese baidu 2.4.6 but when i restart the unit i loose root... i'll post the 2.7.39 mcu's later..
[Android Head-Units] jpapadami:
The same thing happened to me when I root 2.7.38. That's how I was able to get the MCUs. Let's hope someone from the russian site figures out how to root that latest versions because for now it looks like we're stuck at 2.7.35 if we want root.

Do upload the 2.7.39 MCUs when you can.
[Android Head-Units] cool_head:
I've tried almost every mcus and the only one thats works right in my unit is the variant x.x.x-1-10-x101.. the one that keeps reseting the eq in radio app.. someone knows if theres any mcu variant that works properly in my unit? I've got bc6 bluetooth. I'm getting tired of these crappy chinese engeneering.. i already sent tons of emails to tonghai create.. no one answer's me..
[Android Head-Units] cool_head:
You can use the 2.7.37 that's can be rooted properly like 2.7.35..
[Android Head-Units] jpapadami:
Check out this post #7558 from the 4pda.to forum. If I understand him correctly the guy is saying that you have to first perform a full format using the fullformat firmware to clean out the old installed firmware. Then you update with a clean 2.7.39, install baidu 2.4.6 adn root, install SU and update binaries, and when you reboot the root should still be there.
[Android Head-Units] cool_head:
There you go.. The 2.7.39 MCU's.

https://dl.dropboxusercontent.com/u/95210964/2.7.39 MCU.rar
[Android Head-Units] latino-7:
I followed all the steps that you mentioned here. It didn't worked for me. The root was lost every time I restart. I tried it 3 times. I only had baidu installed and SU. Not other apps

I re-did another fullformat firmware without deleting baidu and su after restart. I install baidu but didnt run it and install SU. When I was going to root with baidu SU showed up "baidu need SU permission". The radio is root after doing the second full format, I didnt needed to run baidu or updated the binaris on SU. Now I have 2.7.39 rood
[Android Head-Units] Scuddery:
I did a factory reset and used that reformat software, still nothing. I even just updated system to 2.7.29 (still unrooted) and that also failed to get me Step 3. Not sure what the actual problem is here...
[Android Head-Units] jpapadami:
Sorry it didn't work out. There are two firmwares out there. One is for resting to factory and one is for full format of the unit, so not sure which one you used.

Have you considered that the USB port might not be working? Try plugging in something else like a usb stick to see if it works.

---------- Post added at 08:39 AM ---------- Previous post was at 07:55 AM ----------

Good news. After root, can you delete Baidu or do you need both Baidu and SU to have root? Also you mentioned that you did a fullformat without deleting Baidu and SU. Does performing a fullformat delete all the installed apps on the unit or not?
[Android Head-Units] Scuddery:
I did the full format. The USB should be fine as I've been using the free Wi-Fi dongle and sometimes a hub with no issue. Even when I directly connect the OBDII to USB port, it fails. Also as expected, the front mini-B fails.

I'll be borrowing another type of generic OBDII to USB scanner tomorrow. I've seen this one interface with EasyOBDII no problem too. If this doesn't work then I guess that's it. Trying my luck with Scantool just isn't worth it. At that point I'll have another (it'll be my fourth owned and fully working) OBDII scanner, one dedicated just to appease this head-unit.
[Android Head-Units] Skratchuk:
Nice one :good:

---------- Post added at 08:46 AM ---------- Previous post was at 08:41 AM ----------

That is good news BUT sounds complicated :confused:

Would you mind writing a mini guide to how to root on 2-7.39 please?
[Android Head-Units] Miwer:
Hi friends,

When testing new versions, it would be very informative, if you could state what version of android is reported? 4.1 or the fake 4.2?

Does the UI unauthorized message still exist?

Perhaps even post some images of the UI, so people can judge the layout.

I'm currently running 2.7.28 which is correctly reporting android version 4.1, and it's my impression, that all the releases we've seen lately are fake 4.2 versions. I'd love to be proven wrong though. :)

It's been a long time since we've seen any activity from [MENTION=1915855]KID52[/MENTION] - it's too bad, since we cannot update the repositories ourselves.
[Android Head-Units] jpapadami:
You might also want to try starting off with 2.6.60 and then upgrade from there. I know that a lot of people who were having boot loop and other issues started off with 2.6.60 which fixed them and then upgraded from there. Like you said, it might also be the adapter. Justing throwing out ideas out there that I'd probably do to fix the issue if I had it.
[Android Head-Units] IN2thaDO:
Also VW user

Hey guys!

Following this topic from the Netherlands.

So far the unit is "ok" however since last week no more bluetooth connection to my phone. Also out of itself, the unit will swipe to the right or select a song when on a list screen. Just contacted the reseller and see if they' ll replace unit or come up with another solution.

following this as like the most, i'd like to have Torque or similar app running on the system. Also contacted several Chines companies myself, to see if they come up with anything for us.

My girlfriend is Chinese and masters the language, besides that we both work in big IT Distributors here in Europe, so hopefully we can put our feet in between the door as pretending to be reseller ;)

of course someone probably tried this, but who knows. The minute we receive any infomation, I'll of course share it with you guys!

Have a good one!
[Android Head-Units] MFKinSINY:
What are the primary differences with these two firmwares? What does a full format accomplish that a factory reset doesn't? Have you actually done both of these? Thanks.
[Android Head-Units] latino-7:
Performing the step on your post. it your lost root on reboot performing another full format. After reboot. install su only.dont need to install Baidu

And radio is root
[Android Head-Units] Skratchuk:
Just tried 4.3.7-1-10-210101 and eq keeps reseting on radio so no good. Only on radio though just tried it on normal mp3s which use to reset but doesn't anymore. Maybe if I change to a different version of eq or radio do you think this would sort it out.
[Android Head-Units] cool_head:
No dude, same problem here.. only if you change the mcu to other hw variant non -1-, you solve the eq. reset problem.. every mcu hw variants that i've tested don't resets the eq.. only the -1- .. and only since 4.1.2 version..
[Android Head-Units] Skratchuk:
Yes I have noticed that as well!!! I also noticed that the sound isn't as good on other mcu 's I hace tried. I'm back on the old 13 mcu and there is a problem there as well where when I turn the car over I loose all sound from 3rd party apps.
[Android Head-Units] PsychoMcSatan:
What the...!!???

I can't believe it! After tons of unanswered emails to my seller and tonghai create, there is finally a 7-10-2501 MCU. I've had to live with knobs that don't work in order to have working Bluetooth for months now.

Many thanks for the upload. I'll likely stick with .29 firmware due to the rooting difficulties with .39, but has anyone noticed any new features or bug fixes yet?
[Android Head-Units] kaween:
So basically, their info is wrong in ... a lot of area's ? I was afraid of that, as the communication with them was .... a bit difficult.

1) they say "aux 1 can not support camera input" : but it does. (As long as you do NOT use the DVR). Correct ?

2) does the unit support button color change ?

3) EXACTLY how big is the plastic front in size ?
[Android Head-Units] cool_head:
For me, the firmwares are the same.. I don't really see any differences between them.. Maybe the launchers or the native apps, but the settings or bugs stays the same..

If you want to upgrade you can go directly to .37 that the root process is the same as .35 and earlier..
[Android Head-Units] ZexGX:
1) Correct. You either power on the DVR camera, or power on the AUX input source, but not both at the same time.

2) Mine did not. It's stuck on green (I can disable it by removing power from the ILLUM+ wire). I sent a message to the seller regarding this and asking if there is a software upgrade that fixes it or if I can purchase an LED module to make it red.

3) I will take measurements late this weekend, or Monday.
[Android Head-Units] jpapadami:
OK thanks. BTW, does 2.7.39 have the red UI Unauthorized warning or not? If it does do you have the com.tw.service_a5a4.apk file for 2.7.39 which you can upload and share?
[Android Head-Units] latino-7:
You can use 2.7.35 post #4734
[Android Head-Units] mtresk:
https://yadi.sk/d/W_R7wS4sbT6Kb
[Android Head-Units] jpapadami:
Thanks for trying, but the zip file is empty.
[Android Head-Units] mtresk:
Sorry... https://www.dropbox.com/s/6azz8teojqy1gv8/com.tw.service_a5a4[no+red+ui,+2.7.39].zip?dl=0
[Android Head-Units] Deffe1:
Does anyone know this app?

Hi, seems that I have a similar device but with 7" screen and actual mcu / system file (pic1)

In my app menu there is an app "bootanimation" (pic2) where you can select 3 diff. boot animations (pic 3). I would like to add an "Opel" boot animation but can't find a way to add an animation to this app. Does anyone know this app and how to use it? My device is NOT rootet (framaroot failed), but busybox is installed.

Thx in advance

Deffe
[Android Head-Units] jpapadami:
Thanks. Mind me asking where are you getting them from? I can't seem to find them on 4pda.to but remember someone here mentioning how to edit the .apk file to remove the error message.
[Android Head-Units] mtresk:
http://4pda.ru/forum/index.php?s=&showtopic=522762&view=findpost&p=33948947
[Android Head-Units] jpapadami:
Well, you can use the baudi root at the beginning of this thread to root your device which you'll probably need to do to add boot animations. As for how, I really don't know because I haven't tried. Probably need to get access to the system directory where the animations are stored. Try searching the name of one of the boot animations through ES File Explorer and see where it's located. That's probably the location where you have to place the boot animations, but this is just a guess.
[Android Head-Units] mtresk:
Boot animation zips located in system/etc/bootanimation folder.
[Android Head-Units] Deffe1:
Thats the strange part: there is no bootanimation.zip or any boot* , boot*.* file at all! The above folder is empty! Perhaps this app is an internal app and those 3 animations are stored in mcu?

Greetings

Deffe
[Android Head-Units] mtresk:
You need to root device to see files in system folder.
[Android Head-Units] Deffe1:
I rooted with baidu root EN (which is in chinese !) and copied my bootanimation to system/ect/bootanimation (I could see the other files after rooting!). So I don't need rooting (as everything else seems to work). Is it enough to remove the baidu app for "un-rooting"?

Many thanks for your help!

Greetings

Deffe
[Android Head-Units] cool_head:
For VW owners I share with you this cool bootanimation. Hope you enjoy..

:good:
[Android Head-Units] kaween:
Reanimating my dead AN21

Hi guys.

Today I decided to take my dead AN21-U apart. My resellers reactions to my questions made me doubting their competence and worse, their honesty so I just went ahead disassembled it. The fact the unit now gave a constant white screen and I had nothing to loose was the extra push I needed, and I was getting sick of my Apple Server exam preparation anyhow. :p

Well, I've learned a couple of things.

1) If I'm not mistaken and lady luck is on my side, the white screen issue in my case MAY be the result of a bad flex cable assembly. The part that sits on the mcu actually was shoved in in a crooked way. I took it out, realigned it and .... my unit booted ! Now, I'm not going to get ahead of myself and maybe it's just dumb circumstance that the unit boots now everytime I try to power it on where it did NADA before I took it apart, more testing is needed.

2) the cpu becomes VERY HOT. And that fan that is supposed to keep the unit stable won't help all THAT much, as the cpu board resides UNDER the mcu, the fan blows OVER the mcu, and the airflow under the mcu board is negligable. I've modified an old VGA-cooler to fit the ARM cpu and make thermal contact with the lower part of the housing, so the heat can actually dissipate from the cpu itself.

3) it is actually very easy to disassemble the unit without even damaging the waranty sticker. :angel:

4) the ST/Thompson mcu chip itself has little to no cooling either. I will modify that too as the specs of the mcu chip (thermally speaking) aren't all that great.

5) my unit came pre-modified for external mic. I was a bit suprised you don't see any proof of rework/mods on the mcu board , and the external mic connection has been realised over the existing white connector on the rear. I see 2 cables starting from the internal mic, and they disappear somewhere behind the screen. From there, NO new wires or "handywork" is seen that routes these 2 wires to the mcu board, so they MUST be connected on the display panel somewhere and they must be transfered to the mcu over the existing, unmodified front-pcb and the flex connector that transfers everthing to the mcu. Will have to see if I can get to the bottom of that.

It's nearly 3am here now, and I really need to hit the sack. I'll write up a little guide that discribes how to open this unit without voiding you waranty sticker and what I've done to try and better the heat dissipation inside the unit. and post it either here or in the hardware-mod thread. Even if my unit would prove to remain unstable, I'm quite sure this info will be of use to someone sometime. :laugh:
[Android Head-Units] kaween:
Part 2

next set of pics.
[Android Head-Units] kaween:
Part 3

.... next set
[Android Head-Units] kaween:
Part 4

nearly there ....
[Android Head-Units] Skratchuk:
Has anyone got mcu 4.1 # 1-10-2010 they can upload please
[Android Head-Units] kaween:
Part 4

oops. wrong.
[Android Head-Units] kaween:
last one

ready.

For the moment, I've yet to see a new "white screen" after modding the unit. So here's to "fingers crossed ect ect". I'll test the unit for the next week or so and if it holds up, it goes back into the car. the only problem being the bad mcu my seller made me flash. :(
[Android Head-Units] jpapadami:
Nice write up. I think that a lot of people including myself will take advantage of this as one point in time I'll probably add heatsinks and thermal paste, probably even replace the fan with a quieter one.

Question concerning the BT board. Did you notice if it can be replaced, whether by soldering or not? I noticed on aliexpress there are sellers who are selling BC6 BT boards and I was thinking about replacing mine. BTW, since you have a BC6 BT board, can you connect any BT device to your unit?
[Android Head-Units] kaween:
That was my whole point of doing it. Just to show it's not hard at all and anyone who can handle a screwdriver without poking out an eye can do it. If someone else had pointed out it was easy to do without damaging the waranty sticker, I would've done it ages ago.

As for the BC6 :

It's replaceble by anyone who has basic solder skills. It's not plugged into a connector but soldered straight on the MCU mainboard using a single-inline-header. As I said, the company that sold me this device must have changed this board at one time, as the traces of manual soldering (solder resin) were still clearly visable. You don't see that on automated assembly.

Yes, I can connect my 10USD OBD2 just fine using that board and Torque runs like a breeze. If you want to do it yourself and have a good solder station or know anyone who can do it for you, I don't see any problems.

Keep in mind you probably have to replace your MCU version, as you will need a BC6-compatible mcu to make it work. (very easy, MCU versions with BC6 support normally begin with a "6xxx", and the BC6 capability is stated in the "choose model" too. If you can't choose a "BC6" model in your current MCU/choose model choice, you'll need to upgrade the MCU otherwise NONE of functions of the BT will be usable.
[Android Head-Units] Miwer:
Nice write-up. I may have a crack at my VW specific unit some day and see if the same applies here. Maybe I'll put a temp probe at the cpu just to see how bad it is. Could be interesting also to see if there are any PCB markings referring to hardware revision and such.

/Miwer

---------- Post added at 10:46 PM ---------- Previous post was at 10:43 PM ----------

Could you post a link to these sellers/items as I'm interested too. I'm not having luck finding any.

/Miwer
[Android Head-Units] kaween:
Bwah, "Bad". Within 2 minutes of operation, the surface temp of my 786 went to +/-56°C Centigrade without Cooling (infrared thermometer) in an open case and 21°C ambient temperature. Now, how this would behave in a hot car in the summer and what temperatures would be achieved when the cpu is pushed then is anyone's guess. But I've never known a cpu going bad because of too much cooling. :)

[MENTION=1937249]jpapadami[/MENTION] : I'm ahead of you. I've already ordered a silent fan to do just that. I'll keep you guys posted on that subject too.

On a brighter note : My AN21-U still has not failed me once since the rebuild. No white screen, no crash, where it wouldn't even boot the day before. Not sure it will hold, but there's no doubt anymore that the initial problem has been affected by the modifications. Time will tell if the fix is going to hold and a spare board is still underway.

Anyhow, I've decided to stick with the AN21-U and I've dropped the Huifei idea. Main reason is I've come to the conclusion that although the Huifei is a better unit on pure specs, it lacks several features that any AN21-U user takes for granted. Most of these can be solved by third party software or thanks to the grace of a couple of very smart Huifei users who offer their apk's or free, but when you come from an AN21-U, it feels a bit like reinventing the wheel. :(
[Android Head-Units] eliasadc:
question about number 10

everything except number 10 i dont understand

10: Open Android Terminal Emulator and run the following commands.

Code:

su

rm /data/local.prop

----> do i type: su and then enter and afterwards i type: rm /data/local.prop ?

-----> and is there a space in between rm and /data/local.prop ?

i am asking because i did everything in the list and it didnt root
[Android Head-Units] TeamHackura:
any similarity to the Innotrends Ca-Fi4 unit?
[Android Head-Units] eliasadc:
huh

i have no idea if your talking to me TeamHackura by responding to my email....but that screen what does that mean? do you want me to take a picture of my radio with that screen?
[Android Head-Units] Orisai:
I believe he wants to know how the latest releaste of the Dashlinq4 firmware can be rooted, as the AN-21 U root method worked with the previous version.
[Android Head-Units] TeamHackura:
Yes. Wasn't aware that I responded to your post. But yes previously the same root method worked but not anymore. I spent hours trying all the methods I could find online with no luck.
[Android Head-Units] Skratchuk:
Any older mcu 's anyone may have that is under 4.2 # 1-10-2101 please can you upload or link the files to me please, still having problems with no sound on 3rd party apps [emoji19] so I'm going to try older mcu
[Android Head-Units] Skratchuk:
FINALLY THE EQ PROBLEM HAS BEEN FIXED!!!

I was trying to sort out my problem of eq resetting all the time so changed to an older mcu which sorted the reset problem but had a problem with 3rd party apps had no sound. I was goggling to find older mcu's when i read that a new mcu has been released with...... the eq bug FIXED. :good:

Here is the link. To all that have had this problem and i know there is a lot of us, this is finally what you have been waiting for!

MCU update 4.3.8-1-10-210101 no CAN BUS or any VW or MCU update 4.3.8-1-40-210101 Mondeo with CAN BUS

View attachment mcu_mondeo.zip View attachment mcu_vw.zip

http://www.cardvd.by/4pda
[Android Head-Units] juninyo:
hi, i get this symbol when I give volume. comes with all applications that are not in the system, the sound is looser than if the music app system. I changed the priority of the sound (smart, 3 apps, system) but still the same. I've also done a reset. It happens with any app to install to use sound. Is there a solution? thank you
[Android Head-Units] Skratchuk:
So you mean your not getting any 3rd party sound? What is your version and mcu?
[Android Head-Units] juninyo:
if I have sound with 3rd party applications but the sound listening lowest and less quality. I have 4.2.15-1-10-2101. I've tried several mcu but it works the same way
[Android Head-Units] Skratchuk:
Have you tried the new one that has been posted?
[Android Head-Units] juninyo:
mcu think that I have not tried, I tried the 4.3.7