yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] safkafin:
Seems that my unit is gone for good.. :( Found out that fan is not working anymore and most probably overheated components... And one thing that I found out is that "Warranty Void" sticker is not intact.. I know for sure that I havent broke it as I havent opened the device.. Sticker seems so clean cut that I say it's been broken since left from factory...
[Android Head-Units] Kidmet:
Well that helped me find it. It was in my phone menu. So it finds the obd but doesnt pair. If I long press it, I get ok, obd, and cancel. When I click ok and go into torque it doesnt show it communicating.

---------- Post added at 10:03 AM ---------- Previous post was at 09:48 AM ----------

I went through your earlier post. Cleared out connections. Clicked the search button (magnifying glass), and it was the OBDII, I long pressed it and clicked ok (also tried hitting the OBD button). never got a connection successful. Never got it to see it in Torque. Any other ideas?
[Android Head-Units] Skratchuk:
Rooting problems

Hi all i have upgraded to 2.7.35 and then downloaed the latest version of Baidu which seems to kinda work in the respects of it install super user but it still isn't allowing root permissions. Anyone else had any luck yet?
[Android Head-Units] jpapadami:
Where did you get the 2.7.35 update? Can you share? Just wondering if it is a 4.2.2 fake with a "UI unauthorized" message at the top?
[Android Head-Units] Skratchuk:
It was originally from this post here, More than likely 4.2 fake & cannot seem to root it even with the latest baidu off there website and still no go. I also tried root my an21u and still no luck and even worse than that it is still in slow mode.

I cannot work out what can be so different between this and previous versions that root is not possible

atm.

Has anyone got any other versions to try

that is 2.7.3x

I have got 31,32 & 35 so i would like to try 33 or 34
[Android Head-Units] jpapadami:
From my understanding all 2.7.3x versions are not rootable. I am at 2.7.29 and even though it is also a fake (not sure why at the beginning of the thread it's stated that it is an an original 4.1.1 and not a fake) I'm sticking to this version. Why the .3x version are not rootable, I really can't say. It just seems that the fake versions are becoming riskier as newer versions are showing up.
[Android Head-Units] Skratchuk:
IF there is no more possible root and no one can solve how to the units will be stuck at a 2.7.29 and any other improvements and updates won't be able to be added, surely someone can solve this rooting problem.
[Android Head-Units] jpapadami:
There are a lot of other apks out there that root different android phones, tablets, etc... A lot of the initial people who started this thread rarely post anymore, but they are the ones who could probably comment better as to why the current root methods doesn't work on this version and when they did, why were these two options were chosen? Probably because it used an existing exploit.

Most logical answer is that the two current rooting apks use an available exploit in the firmware to root the device and now with the .3x versions the exploit has been patched which is probably why the current 2 rooting methods don't work anymore. That sounds weird though because why would someone patch an exploit, especially a fake one?

Not sure if this app will root our devices, but it might be worth a shot.

http://xdaforums.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
[Android Head-Units] Skratchuk:
Cheers I'll try that see if that roots it.

I have managed to root 2.7.31 but it is the widget launcher version.
[Android Head-Units] droc.noles:
I can report the same issue. The device sees the adapter but nothing when tapping okay or OBDII.
[Android Head-Units] jpapadami:
Cool, keep us up to date. BTW, I see that you have the same unit as I have. What was the default MCU that came with the unit and what MCU are you using now? I can't seem to see the last 4 digits from the pic. Mine came with X.X.X-1-10-2101. Just trying to see what other MCUs people are using with this unit.
[Android Head-Units] PsychoMcSatan:
If you have a chance, can you check the /etc/MCU/ folder for an MCU named 4.x.x-7-10-2501. They haven't provided an update to 7-10-2501 for many versions now.

And how is .31? Any noticeable differences yet?
[Android Head-Units] Miwer:
Err... because it's an exploit... ?!

The only reason we have been able to root it so far, is because the system has had bugs, which could be exploited to gain super user access to the system.

Think about it, if we can exploit these bugs, then so can any malware we download from the market (or anywhere else).

It is not in the manufacturers interest to put out a product which can be exploited and let users (or malware) gain unauthorized super user access. So of course they will patch it, when they learn of these bugs.

I hate to admit it, but It's even in OUR best interest (generally), that these bugs are fixed (even if it means we cannot root it anymore, and it is annoying as hell), because we ultimately have a more secure system, and we can have more confidence in malware not being able to gain unauthorized access to the system.

It's sad though, that the manufacturer isn't more open about how the system works (releasing documentation, API's, even source code), and allowing customers to root and customize the system. Them chinese people have a tendency to not release any such for their products, even if it could mean greater community support, and bugs getting fixed faster.

Just my 2 cents...

/Miwer
[Android Head-Units] Skratchuk:
I think it use to be on 4.1.13-1-10-2101 but the eq kept reseting so i tried loads of other mcu and now use 4.3.1-10-10-2501 until i find a working mcu.

I would also like to know is there a setting when you switch the unit on it goes to radio on boot even if the radio app wasn't used last?
[Android Head-Units] jpapadami:
I don't believe that there is a setting. Not sure if it's a MCU issue, but I never had this issue with my unit using the default MCU. Home screen was always the first screen that popped when booted. Will try to experiment with other MCUs because I'm having a Torque Pro issue where the app sometimes refreshes and all the gauges just freeze up.
[Android Head-Units] Skratchuk:
That is a good point! but im sure someone can root it again as done in the past, it is a shame like you said APIs for these devices.
[Android Head-Units] jpapadami:
+1. But I don't think the Chinese guys patched the exploit, because it's only on the fake .32 and up. Looks like the Russians or some vender decided to patch it. I hope that the Framaroot works on this firmware version.
[Android Head-Units] Miwer:
That an interesting statement... that would suggest that people other than the manufacturer has access to the source code, and know the format (and encryption/obfuscation routine) of the unit. In that case, it's wierd, that we haven't yet seen any unofficial release of tools that can (un)obfuscate the upgrade images, allowing us to do customization (and embedded root). If this is indeed the case, I imagine that something like this is bound to happen sooner or later (I hope). :)

/Miwer
[Android Head-Units] jpapadami:
I'm sure that the russian site where these fake 4.2.2 firmwares are coming from will have answers to our questions. Unfortunately, google translate doesn't do quite a good job of translating :(
[Android Head-Units] cool_head:
Maybe this happens because your unit don't have the bc6 bluetooth module.. only bc6 modules work with torque...
[Android Head-Units] jpapadami:
Not only does your unit have to have BC6 to connect via bluetooth, but looks like the MCU version needs to be one that has BC6 feature in it. Prompts to nE0sIghT who wrote this little MCU decoder from post #4689. AWESOME :victory: Prompts to Miwer as well who decoded everything :)
[Android Head-Units] thedegg:
help mcu needed

hi can you post 4.3 mcu please. or tell me where to get or how to get 4.3 mcu file.

thanks

anybody ?
[Android Head-Units] droc.noles:
I'm assuming not, but user kaween has apparently the same unit (one knob version as depicted at the outset of thread) using the same 6101 MCU. He was able to establish the connection. I'm guessing he just so happens to have this bc6 module and I don't, although I don't really understand the logistics behind my unit being able to see the adapter and not connect.

Oh well, on to a Wi-Fi or USB OBD2 adapter.
[Android Head-Units] latino-7:
Baidu root working on 2.7.35

Baidu root its on Russian language but working fine

All mcu comes on 2.7.35
[Android Head-Units] latino-7:
com.tw.service 2.7.35

com.tw.service 2.7.35 remove the red warning
[Android Head-Units] jpapadami:
Updated to 2.7.35 and can confirm that Baidu russian version roots this firmware and the com.tw.services.apk removes the red unauthorized message.

Only problem is that I always get the "Android is upgrading - Starting apps" message when when booting the device. Any thoughts?
[Android Head-Units] Skratchuk:
THANK YOU i will try it today, this is what xda is all about!

I'll try it today and report back if i have the same issue.
[Android Head-Units] jpapadami:
If you do get the "Android is upgrading" message at boot, there might be something wrong with the modified com.tw.services.apk. When I get home I plan on replacing it with the 2.7.29 modded version to see if that will fix the issue.
[Android Head-Units] Skratchuk:
Ok I updated and rooted but noticed I can't use super user anymore I have to use Baidu. I replaced the services.apk file and the ui message is gone now and when rebooting no upgrading android message.

I did try the original mcu number again but still had eq problems.

I am now using this mcu.

THANKS to everyone for there help and files.
[Android Head-Units] MFKinSINY:
Tracing boot issues

Windows, I can find anything I need to troubleshoot startup/shutdown issues, app crashes, hardware problems etc.

Android on the other hand.... I have no clue.

Can anyone help me (or point me in the right direction) troubleshoot boot issues (log files, event tracing etc.)?

When I power up my unit (mcu -1-0101, fw 2.7.29) which is visually identical to the one pictured on page 1 of this thread,

after I reach the home screen (in a reasonable amount of time, most times [approx 20 sec]) I don't have immediate use of the system.

It can be another 20 seconds before I get a cursor or can click on an icon. Something is taking it's sweet ass time to load & would like to know what the problem is.

I might consider doing a factory reset, upgrade to 2/7/35, root and then install only the apps I need/use but don't want to do that IF it's not necessary (and I don't feel that it is)

Thanks
[Android Head-Units] jpapadami:
Yes I also noticed that you can't use SuperUser anymore and you have to use Baidu. I'm going to try Framaroot to see if it roots this device because I'd rather use SuperUser. Since you're not getting the upgrading message at boot, I will try replace it with the modded .35 version again to see if it fixes the issue.

Not sure why you're having the equalizer issue. I was at 4.3.2-1-10-2101 and now I'm at 4.3.4-10-10-2501 and have not had any issues with both. Worst case scenario, you might have to use the firmware that formats your unit and resets everything to factory. You'll have to reinstall everything though.
[Android Head-Units] MFKinSINY:
Proper rooting method (BAIDU)

I plan on upgrading to 2.7.35 now that we apparently can root it (thanks latino-7)

I'm speculating that Baidu 2.4.6 will present itself the the screen in russian language.

Can we outline or summarize the root procedure, while answering the following question?

(it's called one-click) what specifically needs to be clicked (in case it's not in your language)

Anything else need to be clicked?

Does su need to be installed?

Does the build.prop file need to be removed?

If yes, what sequence. first, next, next, last... (are reboots necessary? when?)

I understand Baidu installs a fair amount of bloatware.

What needs to be (can be) removed and what are the locations of these items.

anything else pertinent to the rooting process?

I've seen various references to some of these questions, scattered about & unconfirmed.

It's not that I'm lazy, I would just like to see a complete "how-to" post that can be pinned or put on the wiki.

Thanks
[Android Head-Units] Cebulon48:
I am lazy that's why +1

;) Oliver

Gesendet von meinem GT-I9100 mit Tapatalk
[Android Head-Units] bluetwok:
The document you attached doesnt open. The update file is it in a zip format or bin file?

---------- Post added at 03:47 PM ---------- Previous post was at 03:20 PM ----------

The document you attached doesnt open. The update file is it in a zip format or bin file?
[Android Head-Units] Vladimir2k9:
Attached document is msword file, my libre office in ubuntu open it without problems.

Update file is 7z archive, unpack to microsd, insert in gps slot and reboot device.

Отправлено с моего HTC Vision через Tapatalk
[Android Head-Units] pdawookie:
bad root ...

So I tried to root my unit (a dual knob) with the AN-21U and got the exact same thing as Malcz below. Right now if I reboot the unit I get a black screen with black icons and slow running as predicted.

I get in the terminal and do su and the rm /data/local.prop

and i get an error. if I ls /data it appears empty.

my unit is

CPU - Cortex-A9 dual core

RAM - DDR3 1GB

Android Version - 4.2.2

MCU - 4.3.1.2-7-10-6601

system - 2.7.22

DVD - 2.13.13-1200zh

I tried the badui a key and it seems to run but always seems to fail

Any suggetions?

Cheers

-pdawookie
[Android Head-Units] goraax:
In Poweramp or any non-stock music player (I also tried DoubleTwist), there is no audio at all. When I try to turn the volume up/down, I see that the volume icon (music note symbol) is crossed out. This only happens while I'm in non stock music players, when the stock music or radio is open, the volume icon displays normally when changing volume.

Any ideas?
[Android Head-Units] jpapadami:
Settings > Audio > Priority > Set 3rd party application audio

---------- Post added at 07:18 AM ---------- Previous post was at 07:12 AM ----------

Depending on what firmware you're trying to root will depend what method to use. If you're in slow mode (black screen, black icons) the only way to get to normal is to somehow navigate to Settings > General > Reset to factory. After that things will be normal. If you can't root with the mentioned above methods that means you probably have a 2.7.31/32/35 firmware. You'll have to use the Baudi Russian version to root.
[Android Head-Units] aluzjunior:
There's a way to keep rooted after unistall Baidu?

i am using 2.7.32 and if i unistall it and reboot o lose root.

i cant install superuser too
[Android Head-Units] Skratchuk:
Atm it seems the only way to stay rooted is by using baidu installed. We are looking at ways round it so if you find another please let us all know.

---------- Post added at 12:11 PM ---------- Previous post was at 11:52 AM ----------

Can anyone tell me the user settings password please. I can't seem to find it on this thread.
[Android Head-Units] MFKinSINY:
Either your statement isn't entirely accurate or I just got lucky. I was stuck in slow mode, black screen & invisible icons for a few days after updating to 2.7.32 and attempting root. At first I tried "rootmyan21u" procedure & of course it did not work, but then I tried Baidu and that also did not work. I was able to navigate (if you press "back" or "home" you can see the icons for a split second) and select the aux app and hit "back" and then "home" you will have screen & icons, but still be in slow mode (i noticed that if I put my car into reverse I would also get screen & icons, but the unit probably needs to be set a certain way like having the backup cam connected for example)

I downgraded to 2.7.29 and did the "rootmyan21u" procedure and my unit works normal, without doing a factory reset.

Like I said, maybe I just got lucky :)
[Android Head-Units] Skratchuk:
I too downgraded to 2.7.31 then rooted with baidu, after that I ran the command in emulator to get it off slow mode. After that I upgraded to 2.7.35
[Android Head-Units] pdawookie:
Thanks.. my system version says its 2,7,22 this is why I thought the AN-21U would work.

I tried to reset to factory settings with password 7890 and the window "Resetting ... do not turn off... " comes up but it hangs there for well over 30 mins... I had to start car at one point and it came back without the reset done.

Since my unit is a 4.2.2 do I need to take the 4.2.2 firmwares only? I dont see 2.7.31/32/35 in the repository I do see a 2.7.26 (and 26-2, 26-3) do I need all these ? thanks

I reboot the unit by holding the power down until it goes off.. is this the proper method?

thanks
[Android Head-Units] calledman:
Rooting not working

Hi all,

I have tried every possible way to root my unit but no luck so far. Baidu says it worked but I cannot copy that ask file to remove the red ui warning. I am attaching a picture of the unit and hopefully someone will come up with a solution. Thanks
[Android Head-Units] latino-7:
Use baidu Russian Version 2 pages back is working fine and download superuser Clock work mod on the market
[Android Head-Units] jpapadami:
SuperUser Clockworkmod doesn't work simultaneously with the Baudi russian version. If you root with Baudi and then install Superuser and then update binaries, you loose root.
[Android Head-Units] latino-7:
Reboot the unit this is setup on mi unit is working great for my
[Android Head-Units] Skratchuk:
So install Baudi and root with that then reboot after that install Su then you can uninstall baudi and use su instead is that correct?
[Android Head-Units] latino-7:
install Baudi and root and install su open su update binaries reboot Idont remove baudi and tried to remove later whit the instruction on couple pages back when I have more time but su is working for me
[Android Head-Units] jpapadami:
Yes, it works.

Install Baudi then root > install SU then install binaries > reboot system then uninstall Baudi. Thanks Latino-7 :)
[Android Head-Units] pdawookie:
Questions about updating firmware

Well I upgraded to 2.7.29 and rooted with Baudi_2001EN

was able to delete the file in /data/ and unit is back to normal... yay! :)

Thanks so much everyone !

now rooted... can we change the launcher buttons (other than navi of course) ?

-pdawookie
[Android Head-Units] aluzjunior:
SU fails to update binaries here
[Android Head-Units] kaween:
AN21-U going belly-up ... :(

Since a couple of days, my AN21-U is showing increasing problems during boot.

When it fails (which is about 50% of the times it would seem), the screen is completly white from the start. No "it goes ghostly white while you can see the "desktop" fading", just immideate white. What I find odd is :

1) when the unit comes from a prolonged "power off" state, the boot nearly Always succeeds.

2) when I switch of the unit and try to turn it on within 10 seconds of switching it off, the unit will most certainly FAIL to boot. If the radio tuner was selected before power off, I can hear the last tuned radio station, and I can change volume/select mute (MCU functions), but I can not change stations or "choose another input" over the SWC.

3) once booted, the AN21 will NOT crash during operation, no matter how hot or cold the temperature in my car is. That speaks against it being a temperature issue, I suspect the power regulator part of the AN21 is defective. My suspicion is the android board has a comparable "power good" clearance needed to acutally start, just like a normal PC does. When power comes up and this signal is not cleared, the MCU will probably start, but the android board will not. As a result, the MCU comes up, does not receive a video signal from the dead Android board, thus showing just a blank screen.

4) the unit behaves the same in and out of the car : I have a rather well equiped electronic workbench at home as I do quite some hardware repairs of almost anything simply because I like doing it, and one of the things I have is a "car simulator" bench where I can simply hook-up a radio and test nearly all functions outside of a car. But even with only power/acc + ground attached (+ 2 test speakers), the unit behaves identically, so any "bad loom or whatever" reasons can be excluded.

I'm in the process of trying to resolve this with my seller who has -unintentionally I'm sure- made my bad situation even worse by sending me a firmware that I had to try before anything else. Surely, the new firmware didn't solve the issue, worse : it did overwrite my GOOD working MCU version (6101) by an older version (2101) which is CRAP, cursing my already crippled unit with an unusable EQ which resets to "crap sound" each time I select anything else than radio tuner and then return to the radio tuner, the sound is muffled, dirty and "low pass".

As I never "toy with firmware versions without reason when stuff works" (dictated by my IT background) and I had clearly too much faith in my seller that he knew what he was doing, I could now KICK MYSELF for doing so.

Is there anyone out there with a 6101 who can copy it from his or hers /system/ect/mcu folder and make it public, I would be very greateful. It goes without saying you'd need to have a rooted device to do so.

And of course, any input regarding the boot issue is highly appriciated too.
[Android Head-Units] SwiftStorm:
I also have the "fading" issue, and traced it to the following: connecting my phone to the USB output during first startup causes this issue immediately. For the next several hours, I can disconnect/reconnect the USB cable to my phone at will, and the problem will not appear.

Doesn't sound like this is your exact issue, but hope it helps in some way. Maybe some sort of power/ground connection on the board is bad?
[Android Head-Units] clipcarl:
Why not just disconnect the illumination wire?
[Android Head-Units] kaween:
He can, but he specifically stated that he wanted to avoid that.

A somewhat "manual" approach could be assign a button or action to the SWC to the lights-settings. I've done something like that : that way I can switch between Full screen illumination, dimmed screen and screen completly off but cycling through this setting.

But I asume the OT wants a more elegant solution to this. :laugh:
[Android Head-Units] MRasri:
nicely done. i'll try it
[Android Head-Units] Vladimir2k9:
del