• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit [ROOTED]

Search This thread

KID52

Senior Member
Jul 23, 2009
470
149
"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit [ROOTED]

"AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit

To avoid confusion, below is a picture of the unit this thread relates to.

I am aware of a previous unit using the same design, but it runs an older version of Android. This thread is for the unit running 4.1 as standard.

2013-10-27 16.19.46.jpg


Specification / Features

Hardware
CPU: ARM Cortex A9 MST786 Dual Core 1GHz
GPU: Mali-400 MP
RAM: SKHYNIX 1G DDR3 RAM H5TQ4G83AFR
iNAND: SanDisk 8GB SD1N5C2-8G (1GB system storage, 6GB internal USB storage)
MCU: STM8AH ST
Bluetooth: BlueCore5 CSR
Screen: Capacitive 800*480
GPS: SiRF Atlas V GPS Processor
Radio: Philips TEF6624
Sound Effect Processor: BD37534 ROHM
Outputs: 4x 45w outputs, Toshiba TB2929
Additional Outputs: 1x Subwoofer, 4x pre-outs
Microphone: Built in microphone

Supported Features
Bluetooth connection to phone for calls.

WiFi and 3G dongles. These must be plugged in before turning the device on, and are not hot-swappable.

Compatible 3G Dongles
  • ZTE MF190 Clone (Qualcomm MSM6280 + RTR6280)
  • Huawei E171 (Qualcomm MSM6290)
  • Huawei E180
  • Huawei E261
  • Huawei E1752

Non-Compatible 3G Dongles
  • Generic Orange/Black eBay dongle (Qualcomm MSM6280 + RTR6275)
  • Huawei E220
  • Huawei E352
  • Huawei E367

Connection of multiple USB devices through a USB hub, including wireless keyboards, USB memory sticks, and wireless dongles. These types of devices are hot-swappable.

Multiple USB memory sticks can be plugged in. They mount at "mnt/usb/sda1", "mnt/usb/sdb1", and so on. The limit is not known, three have been tested at once.


Wiki Page

This unit has a very useful Wiki page with a lot of good information.

Tonghai Create AN-21 U Wiki

It would be really appreciated if before posting any questions, you take a read of it, this main post, watch the video review, or do a search of this thread to avoid any repeats.​


Video Review


Other videos showing specific features are also available on my channel.​


News

2014.01.20
Download links and bugs section updated.​

2013.12.05
Root is now possible.​

Previous News
2013.11.16
The manufacturer intends to add new features to the unit, they are currently developing an OBD II system, I assume this would be via USB. They say it will require additional hardware.

Sooner than that, they plan to release wireless mirror link for Android phones.

I asked about Bluetooth compatibility, they said my request would be sent to their engineer to include Bluetooth modules. Whether this actually gets included or not, we will have to see.​


File Repository

This site has links to most of the files in this thread, including firmware and MCUs.

Android 4.1 Car Stereo File Repository

All files are of course used at your own risk.​


Firmware Updates

To update the unit, extract the update files from the downloaded RAR and copy them to a MicroSD Card, insert the card, go to Settings -> General Settings -> System Update or turn the unit on whilst holding down the 'Menu' and 'Volume' buttons until the update starts.

System Version 2.7.29
Mirror 1 - Click here

Previous Versions
System Version 2.7.28
Mirror 1 - Click here

System Version 2.7.11
Mirror 1 - Click here

System Version 2.7.9
Mirror 1 - Click here

System Version 2.7.4
Mirror 1 - Click here

System Version 2.6.96
Mirror 1 - Click here

System Version 2.6.93
Mirror 1 - Click here

System Version 2.6.77-2
Mirror 1 - Click here

System Version 2.6.77
Mirror 1 - Click here

System Version 2.6.73
Mirror 1 - Click here

System Version 2.6.70
Mirror 1 - Click here
Mirror 2 - Click here

System Version 2.6.68
*WARNING* This update appears to cause issues with GPS *WARNING*
Mirror 1 - Click here
Mirror 2 - Click here

Password
android-4.1-2.6.68-password.png
System Version 2.6.62
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here

System Version 2.6.60-2
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here

System Version 2.6.60
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here

System Version 2.6.40
Mirror 1 - Click here
Mirror 2 - Click here
Mirror 3 - Click here

System Version 2.6.23
*WARNING* This update appears to cause unrecoverable bricking of the unit when changing model or MCU. *WARNING*
Mirror 1 - Click here
Mirror 2 - Click here

Password
android-4.1-2.6.23-password.png

"4.2.2" Versions
Please note that these are actually Android 4.1, but the menu text has been changed to "4.2.2"

System Version 2.7.11
Mirror 1 - Click here

System Version 2.7.22
Mirror 1 - Click here

System Version 2.7.26
Mirror 1 - Click here

System Version 2.7.26-2
Mirror 1 - Click here

System Version 2.7.26-3
Mirror 1 - Click here


Changelog (Unofficial)

System Version 2.7.29
  • Unknown
Previous Versions
System Version 2.7.28
  • Unknown
System Version 2.7.11
  • Unknown
System Version 2.7.9
  • Unknown
System Version 2.7.4
  • Unknown
System Version 2.6.96
  • Unknown
System Version 2.6.93
  • Unknown
System Version 2.6.77-2
  • Unknown
System Version 2.6.77
  • Unknown
System Version 2.6.73
  • Unknown
System Version 2.6.70
  • When changing panel keys or steering wheel controls, the notification bar is still displayed
  • New menu option for backing up and restoring both panel key and steering wheel control mappings
System Version 2.6.68
  • Homescreen design reverted back to four large widgets per page
  • App icon for SWC settings
  • Setting in "Extra Settings" to force USB1.1
  • Factory reset is password protected (See FAQ)
  • Developer options are password protected (See FAQ)

System Version 2.6.62
  • Bluetooth icon in notification bar (appears Bluetooth is turned on by default now, cannot turn it off)
  • Bluetooth menu, accessed via an app, has "SEARCH FOR DEVICES" and visibility option, however nothing functions when pressed
  • All extra applications removed (ES File Explorer, GPS Test Plus, QuickPic)
  • WiFi Hotspot can be activated without re-plugging the 3G dongle in
  • Background is winter-themed

System Version 2.6.60-2
  • New home screen design
    2013-11-15 22.17.48.jpg
System Version 2.6.60
  • Default applications changed back to original theme
  • APK Installer application install by default
  • Bluetooth renamed back to Phone
  • Screenshot feature now fixed and works correctly

System Version 2.6.40
  • Larger notification bar
  • GPS icon removed from notification bar
  • Home, back, menu, and screen off buttons added to notification bar
  • Default applications changed to red theme (music player, radio, video player, phone)
  • Phone application renamed to Bluetooth
  • ES File Explorer installed by default
  • GPS Test Plus installed by default
  • QuickPic installed by default
  • Non-functioning screenshot featured added in settings menu



Bugs / Issues

Key
Unresolved
Workaround
Resolved

Updated 2014.01.20
Newest issues will be put at the top, solved issues, or issues with workarounds will be moved to the bottom.

Unable to remove applications that are device administrators without factory reset due to security menu being disabled.

Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".

Despite selecting "Front Speakers Only" for navigation sound, the sound comes out of the rear speakers too. Setting to "Front Right" appears to work correctly.

Bluetooth is restricted to phones only. (Unsure if this is hardware or software related, talking to manufacturer suggests hardware limitation).

Bluetooth dongles do not work.

There is a "pop" from the speakers sometimes when changing applications that control sound, this is extremely obvious if you have a subwoofer installed. It happens when the unit is turned on, and when going from mute, to a volume level.

Screen brightness when buttons illuminated is not user-configurable. This means it may be too bright or dark depending on the conditions. For example, when it is only mildly dark outside, and you have your lights on, the screen is very hard to see.
Workaround: Enable constant illumination from the "Extra Settings" menu by setting the option to "CLOSE", this will set the keys to always illuminate. Then use an application such as Twlight to control the screen brightness based on sunset and sunrise.

Random issue when downloading large applications. The progress will usually get to more than 50%, and then no progress is made.
Workaround: The only fix I have found so far is to stop the download, reboot the unit, start the download, and repeat until download continues. It should download from where you cancelled. This appears to be caused by a limited download cache size.

Steering wheel controls only work with default applications.
Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, allowing steering wheel controls to function with other apps.

Most recent default application always opens on boot and continues to play, even if paused. This includes the radio, music, video, and iPod applications.
Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, and no default app will open on boot.

USB Debugging is password protected.
Resolved: The password is "[email protected]". Credit to @nikko82

Screenshot feature does not work, when trying to save the screenshot, a save error appears.
Resolved: This is solved in system version 2.6.60.


Root

Root is now possible thanks to help from some great XDA members.

Credits to @WonderEkin for the Root My AN-21 U app and @bmj67 for supplying SettingsProvider.apk

2014.06.06 - A new rooting tool named Baidu Root has been added to the repository. You can use this tool as an alternative to following the guide below.

Files required
Root My AN-21 U - [ Mirror1 | Mirror2 ]


Root My AN-21 U has been updated since this video was taken, the app should now correctly show "Step 2".

  1. Download the required files above.
  2. Install Android Terminal Emulator on your unit.
  3. Open the AUX application and close it.
  4. Install Root My AN-21 U and create a link on the homescreen.
  5. Run Root My AN-21 U and press the "Step 1" button.
  6. Reboot the unit.
  7. Once the unit has rebooted the screen will likely be black, press the Home button to display the homescreen.
  8. Run Root My AN-21 U and press the "Step 2" button.
  9. Reboot the unit.
  10. Open Android Terminal Emulator and run the following commands.
    Code:
    su
    rm /data/local.prop
  11. Reboot the unit.


FAQ

Can I root this unit?
Please see the "Root" section above.​
HELP! My unit is stuck in a boot-loop!
Place the update files on your MicroSD card (see "Firmware Updates" section). Then turn the unit on whilst holding down the volume knob and home button. This should start the update process.​
Can I use Bluetooth OBD devices with Torque?
Not at the moment, Bluetooth is only for phones and Bluetooth dongles do not work.​
Does it have the full Play Store?
Yes, it has the Play Store and all compatible applications are available for download.​
What is the boot time?
18 seconds to home screen, 22 seconds until music application starts. If you use the radio application rather than the music player, the radio sounds as soon as the unit receives power.​
Where can I buy one?
There are many listings on eBay/AliExpress under the search term "android 4.1 car", some have resistive, and some have capacitive screens. There is also the mention of a faster 1.2GHz dual core, however the unit actually has a 1GHz dual core CPU.​
How good is the radio?
The radio reception seems fine, as does the sound quality.​
Is there a Wiki page?What is the USB Debugging password?What is the Factory Reset / Developer Options password?
7890​
What is the Extra Settings password?
123456​
 
Last edited:

sciallo

Senior Member
Oct 20, 2010
511
116
Android doesn't have NTFS support, let alone EFS which is built on top of Microsoft's filesystem, but it's capable of using the same cypher algorithms as EFS (AES, SHA, DES) though. The only thing Android needs to be able to decrypt them during the upgrade process, is the manufacturer's or firmware developer's public key, which I believe is stored among the system root certificates.

This, providing EFS or a compatible file encryption mechanism was used to encrypt those files.

If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.

As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...

Code:
diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ
That I'm guessing is our system file :)
@tin2001 @Orisai @chris.r.r <- in case you missed the switch to new thread :)
 
  • Like
Reactions: Skratchuk

KID52

Senior Member
Jul 23, 2009
470
149
If we think about it, Android isn't even part of the equation reading those files really, just a bootloader or the unit's firmware. So the decription layer would have to be built into the bootloader or the raw firmware (read assembly or whatever)... I highly doubt it would be EFS.

As another observation, all filenames remain the same across the two updates and only one file has changed (and it's name remains the same. There goes the hash/sum/md5 like naming theory)...

Code:
diff android-4.1-2.6.40/ android-4.1-2.6.60/
Binary files android-4.1-2.6.40/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 and android-4.1-2.6.60/8e3513e2-ea4a-11e2-8a0f-000c29ba27c0 differ
That I'm guessing is our system file :)

@tin2001 @Orisai @chris.r.r <- in case you missed the switch to new thread :)

Yes, as you say, it is the only file that changes between the updates, and it is also the largest file so I think we can assume this contains the data we want.

Looking at the third update I have, it seems that file is again the only one changed. I will be testing this update out and uploading it shortly.

The file names must have some importance, as otherwise they could just call them "system.img", or something simple, but still encrypt them.
 

KID52

Senior Member
Jul 23, 2009
470
149
Have you tried to see if it will read an external mass storage attached to usb? (usb stick, card reader, 2.5" portable hard drive)?

The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.

The internal storage is mounted at "mnt/sdcard".

The MicroSD card is mounted at "mnt/usb/mmcblk1p1".

USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.
 

donaldta

Senior Member
Aug 12, 2013
1,328
461
Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".

Have you checked for the presence of a hidden file called, ".nomedia" in the MicroSD card? The presence of this file will let most media players to skip this path for scanning for multimedia files.
 

sciallo

Senior Member
Oct 20, 2010
511
116
The default application yes, although I did not try what happens with multiple USB drives. The doubleTwist music player was unable to read a USB memory stick, or the MicroSD card. The actual unit seems to be able to cope with multiple memory sticks, I have tried three, and all were accessible using the ES File Explorer application.

The internal storage is mounted at "mnt/sdcard".

The MicroSD card is mounted at "mnt/usb/mmcblk1p1".

USB memory sticks are mounted at "mnt/usb/sda1", "mnt/usb/sdb1" etc.

You might want to try a few different players to see if it's the unit or the player...

From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/

We recommend only using one volume to store your media. If you choose the memory card, please do not store media files on the internal storage location.

Also, there is not standardized way of implementing SD card support so each manufacturer implements SD card supportly differently. This is why doubleTwist may not always support the SD card on your device.

Devices reported by users to not work includes the following devices:

LG Motion 4G
LG Optimus L5
LG Optimus LTE2
LG Optimus 4X HD
Motorla Razr i
Motorla Razr M

I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard
Code:
ln -s /mnt/sdcard /sdcard
... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.
 

KID52

Senior Member
Jul 23, 2009
470
149
You might want to try a few different players to see if it's the unit or the player...

From http://www.doubletwist.com/help/question/how-do-i-switch-from-internal-storage-to-sd-card/



I don't know if you can without root but you should be able to as normal user in a virtual terminal link /mnt/sdcard to /sdcard
Code:
ln -s /mnt/sdcard /sdcard
... Something to try. I think it won't survive reboot, but if it works you can possibly make a script for it to happen on boot.

It depends on the player.

All file explorer applications such as ES File Explorer, and Astro, have no issues seeing the files. In fact, if you choose an MP3 file and select the player of your choice to open the file, it will indeed open and play, however it does not show up in the list of available songs.

One example of a player than can see the files is Poweramp.

"/mnt/sdcard" is already linked to "/sdcard", but this is the internal USB storage, not external. Perhaps it can be unlinked, and the MicroSD card, "mnt/usb/mmcblk1p1" linked there instead.
 

KID52

Senior Member
Jul 23, 2009
470
149
Peter's listing on eBay mentions the headunit supports wireless keyboards, which are bluetooth devices. Also, being it Android 4.1, it should support USB OBD2 scanners like this one on Amazon:

http://www.amazon.com/OBDLink-OBD-II-Interface-Adapter-425101/dp/B002M07XHO

This one is pretty expensive compared to the bluetooth ones, but I've seen it used by dealers to diagnose their cars during repairs.

Best to keep discussion for the 4.1 unit in this thread now.

My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.

Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...

I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.

Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.

Have you tried a Linux compatible bluetooth dongle yet? I believe, if the headunit supports external wireless keypads, then BT dongles should work, as well as anything connected through them.

Yes, I've tried a couple that I had lying around.

If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.
 
Last edited:

sciallo

Senior Member
Oct 20, 2010
511
116
Best to keep discussion for the 4.1 unit in this thread now.

My keyboard is not Bluetooth, it has a small receiver that is probably 2.4GHz, and it works fine.

Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...

I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.

Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.



Yes, I've tried a couple that I had lying around.

If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.

KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:

Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.

For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.

There is a similar app on the market to use bluetooth keyboards.

...but with both of the above it all depends on the ability to add a BT dongle, the internal one is not visible to android as I understand it (and as it was with the other units OUKU, winCE etc.

I have that exact ODBII reader mainly because I wanted a reliable one that could get the most codes... off topic here, but there is differences. Torque forums are a good resource. I haven't tried USB with it yet. There is cheap usb only out there, but I guess there is two different kinds of usb-to-serial chips... you MIGHT have one of the two installed if they included it....

Bottom line, it doesn't matter what Android supports. What matters is what modules the chinese manufacturer compiled in the kernel or included as a loadable module...

You could get a hint looking at the /home/rick/OUKU/stock/4.1/test/lib/modules/ folder...
 

KID52

Senior Member
Jul 23, 2009
470
149
KEEP IN MIND ALL MY EXPERIENCE IS WITH THE 2.3 OUKU but this might help:

Usb Keyboard is natively supported on all of them, if it's wireless with its own dongle (not bluetooth) that's just all it is, a usb keyboard.

Yes, exactly my thoughts.

For the bluetooth menu install Quick Bluetooth Lite from Market. I was lucky enough one of the dongles I had lying around worked (one didn't) mine sais "KINIVO" on it.

There is a similar app on the market to use bluetooth keyboards.

Thank you for the advice, I will try it out soon, see what happens.

The info you have regarding the OUKU unit may well be relevant to this new one too.
 

Orisai

Senior Member
Jun 13, 2013
134
18
Montevideo
Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.

No, you don't have to buy such devices just for testing purposes. I have plans on buying one for my Santa Fe i45, because USB OBD2 scanners are faster and way more reliable that BT ones, and I'll need it to plug directly into my laptop or the OTG adapter in my SGS4.


Yes, I've tried a couple that I had lying around.

If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.

Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.
 

KID52

Senior Member
Jul 23, 2009
470
149
Try to plug them when your stereo is turned off. I recall someone saying that you have to plug in WiFi and 3G dongles with the headunit turned off, so they get detected by Android when it boots up. Perhaps this is the case with BT dongles too.

Hmm, I said that. I put it in the main post too. Maybe someone said it about OUKU too, I don't know.

But yes, I do usually turn off the stereo and plug the device in before booting.
 

donaldta

Senior Member
Aug 12, 2013
1,328
461
Yes, I've tried a couple that I had lying around.

If you can recommend a specific one that isn't too expensive I may trying buying to see if it works.

Might want to get a terminal for android, like Android Terminal Emulator. Then you can check to see what sort of linux modules/drivers are pre-installed. For example:

Code:
$ lsmod
lsmod
blackberry 1084 0 - Live 0xbf10a000
cdc_acm 15311 0 - Live 0xbf100000
sierra 9201 0 - Live 0xbf0f7000
option 13120 0 - Live 0xbf0ea000
usb_wwan 8010 1 option, Live 0xbf0e2000
hso 29290 0 - Live 0xbf0d3000
tnx_mxt_ts 15886 0 - Live 0xbf0c9000
cp210x 10931 2 - Live 0xbf0c0000
pl2303 10925 0 - Live 0xbf0b7000
usbserial 26415 8 blackberry,sierra,option,usb_wwan,cp210x,pl2303, Live 0xbf0a8000
88w8688_wlan 362475 1 - Live 0xbf041000
tun 13189 2 - Live 0xbf037000
omap3_isp 97716 0 - Live 0xbf014000
omap_hsmmc 14041 0 - Live 0xbf000000
$

This will give you an example of modules installed. In the above example is from the Parrot Asteroid Smart. The output gives you an idea of the sort of devices that you'll be able to use with the unit. For example, there are the cp210x and pl2303 drivers for Serial UART to USB devices. So, for example one could use a USB ODB2 cable as long as they use either a Prolific or Silcon Labs UART.

I will try installing Torque at some point, as on my phone it requests to turn on Bluetooth, so maybe it will access the menu on the unit. I don't have much hope for this working though.

Perhaps the USB device will work, but I do not have one, and do not intend on buying one at that price.

Something that is not well known is that Torque Pro supports USB ODB2 cables. The product linked earlier from Amazon is an ODB2 scanner by Scantool which is a professional model. (Analagous to buying a Fluke Multimeter vs an Innova) They do have another model that costs a little bit more and supports USB and Bluetooth or even WiFi if you prefer. But, there are some less expensive knock offs that you can get for less a fraction of the price. So, if you know the AN-21 U supports a particular Serial to USB driver then you might be able to use one with Torque Pro. The nice thing about USB ODB2 cables over Bluetooth ones is that the data stream is closer to real time and has less lag than a BT ODB2 adapter around the same price.

Unfortunately there is no Bluetooth menu on the device. However, there are a few interesting quirks with the unit, one being that the security menu is disabled, however, if you try to enable something (I forget what, maybe storing location data or something), it tells you that a lock code must be set, so you press okay, and what opens? The security menu...

Some places hide various menus from the settings control panel, but you can often them bring them up using intents through Activity Manager. However, finding the available intents sometimes requires root but you do not need to be root to execute them. For example:

Code:
$ su
su
# dumpsys package com.android.settings | grep BluetoothSettings
dumpsys package com.android.settings | grep BluetoothSettings
        4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068bc48
        4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
        4068b7e0 com.android.settings/.bluetooth.BluetoothSettings filter 4068ba78
# exit
exit
$ am start -n com.android.settings/.bluetooth.BluetoothSettings
am start -n com.android.settings/.bluetooth.BluetoothSettings
Starting: Intent { cmp=com.android.settings/.bluetooth.BluetoothSettings }
$
However, not all Bluetooth software conforms to the Android standards and will force close if it doesn't. In most cases if a Bluetooth driver is installed then a good app to get is Bluetooth Auto-Pair. It allows the manual settings to pair various devices even if the manufacturer implements an artificial limitation on the devices that they will support.
 
  • Like
Reactions: KID52

donaldta

Senior Member
Aug 12, 2013
1,328
461
Android doesn't have NTFS support,

This is actually a pretty bad blanket statement. It actually depends on the Linux modules included with the Android device. And in fact, I played with an Android TV device that had fuse.ko modules installed and supported NTFS partitions. The best way to tell what sort of filesystem that your Android device supports is through "/proc/filesystems".
Code:
$ cat /proc/filesystems
cat /proc/filesystems
nodev   sysfs
nodev   rootfs
nodev   bdev
nodev   proc
nodev   cgroup
nodev   tmpfs
nodev   sockfs
nodev   usbfs
nodev   pipefs
nodev   anon_inodefs
nodev   devpts
        cramfs
        squashfs
nodev   ramfs
        vfat
        msdos
nodev   mqueue
nodev   mtd_inodefs
nodev   oprofilefs
nodev   ubifs
$

The first column signifies whether or not the filesystem is currently present on your android device and the second column shows all the various types that it supports.

---------- Post added at 11:06 PM ---------- Previous post was at 10:49 PM ----------

I'll take another read tomorrow and do some tests on the unit, see what I can find out.

While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.
 

KID52

Senior Member
Jul 23, 2009
470
149
While you're at it, you might consider installing SRT AppScanner. If the device is vulnerable to Master Key either exploit bug 8219321 and/or 9695860 then there's a good chance that Cydia Impactor can root your device.

I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.
 

donaldta

Senior Member
Aug 12, 2013
1,328
461
I thought you needed to connect your device to a PC to use Cydia Impactor? Also, not sure if it would be required, but USB debugging is password protected.

Well, technically you don't have too. It works off of Android Debug Bridge and can work over WiFi or USB. However, it does need debugging to be enabled. I missed the part that it is password protected. However, the masterkey scripts might still be able to help gain access to root if it hasn't been patched on the device.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    "AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit [ROOTED]

    "AN-21 U" - Unbranded 6.2" 2 DIN Pure Android 4.1 Car Stereo Radio Head Unit

    To avoid confusion, below is a picture of the unit this thread relates to.

    I am aware of a previous unit using the same design, but it runs an older version of Android. This thread is for the unit running 4.1 as standard.

    2013-10-27 16.19.46.jpg


    Specification / Features

    Hardware
    CPU: ARM Cortex A9 MST786 Dual Core 1GHz
    GPU: Mali-400 MP
    RAM: SKHYNIX 1G DDR3 RAM H5TQ4G83AFR
    iNAND: SanDisk 8GB SD1N5C2-8G (1GB system storage, 6GB internal USB storage)
    MCU: STM8AH ST
    Bluetooth: BlueCore5 CSR
    Screen: Capacitive 800*480
    GPS: SiRF Atlas V GPS Processor
    Radio: Philips TEF6624
    Sound Effect Processor: BD37534 ROHM
    Outputs: 4x 45w outputs, Toshiba TB2929
    Additional Outputs: 1x Subwoofer, 4x pre-outs
    Microphone: Built in microphone

    Supported Features
    Bluetooth connection to phone for calls.

    WiFi and 3G dongles. These must be plugged in before turning the device on, and are not hot-swappable.

    Compatible 3G Dongles
    • ZTE MF190 Clone (Qualcomm MSM6280 + RTR6280)
    • Huawei E171 (Qualcomm MSM6290)
    • Huawei E180
    • Huawei E261
    • Huawei E1752

    Non-Compatible 3G Dongles
    • Generic Orange/Black eBay dongle (Qualcomm MSM6280 + RTR6275)
    • Huawei E220
    • Huawei E352
    • Huawei E367

    Connection of multiple USB devices through a USB hub, including wireless keyboards, USB memory sticks, and wireless dongles. These types of devices are hot-swappable.

    Multiple USB memory sticks can be plugged in. They mount at "mnt/usb/sda1", "mnt/usb/sdb1", and so on. The limit is not known, three have been tested at once.


    Wiki Page

    This unit has a very useful Wiki page with a lot of good information.

    Tonghai Create AN-21 U Wiki

    It would be really appreciated if before posting any questions, you take a read of it, this main post, watch the video review, or do a search of this thread to avoid any repeats.​


    Video Review


    Other videos showing specific features are also available on my channel.​


    News

    2014.01.20
    Download links and bugs section updated.​

    2013.12.05
    Root is now possible.​

    Previous News
    2013.11.16
    The manufacturer intends to add new features to the unit, they are currently developing an OBD II system, I assume this would be via USB. They say it will require additional hardware.

    Sooner than that, they plan to release wireless mirror link for Android phones.

    I asked about Bluetooth compatibility, they said my request would be sent to their engineer to include Bluetooth modules. Whether this actually gets included or not, we will have to see.​


    File Repository

    This site has links to most of the files in this thread, including firmware and MCUs.

    Android 4.1 Car Stereo File Repository

    All files are of course used at your own risk.​


    Firmware Updates

    To update the unit, extract the update files from the downloaded RAR and copy them to a MicroSD Card, insert the card, go to Settings -> General Settings -> System Update or turn the unit on whilst holding down the 'Menu' and 'Volume' buttons until the update starts.

    System Version 2.7.29
    Mirror 1 - Click here

    Previous Versions
    System Version 2.7.28
    Mirror 1 - Click here

    System Version 2.7.11
    Mirror 1 - Click here

    System Version 2.7.9
    Mirror 1 - Click here

    System Version 2.7.4
    Mirror 1 - Click here

    System Version 2.6.96
    Mirror 1 - Click here

    System Version 2.6.93
    Mirror 1 - Click here

    System Version 2.6.77-2
    Mirror 1 - Click here

    System Version 2.6.77
    Mirror 1 - Click here

    System Version 2.6.73
    Mirror 1 - Click here

    System Version 2.6.70
    Mirror 1 - Click here
    Mirror 2 - Click here

    System Version 2.6.68
    *WARNING* This update appears to cause issues with GPS *WARNING*
    Mirror 1 - Click here
    Mirror 2 - Click here

    Password
    android-4.1-2.6.68-password.png
    System Version 2.6.62
    Mirror 1 - Click here
    Mirror 2 - Click here
    Mirror 3 - Click here

    System Version 2.6.60-2
    Mirror 1 - Click here
    Mirror 2 - Click here
    Mirror 3 - Click here

    System Version 2.6.60
    Mirror 1 - Click here
    Mirror 2 - Click here
    Mirror 3 - Click here

    System Version 2.6.40
    Mirror 1 - Click here
    Mirror 2 - Click here
    Mirror 3 - Click here

    System Version 2.6.23
    *WARNING* This update appears to cause unrecoverable bricking of the unit when changing model or MCU. *WARNING*
    Mirror 1 - Click here
    Mirror 2 - Click here

    Password
    android-4.1-2.6.23-password.png

    "4.2.2" Versions
    Please note that these are actually Android 4.1, but the menu text has been changed to "4.2.2"

    System Version 2.7.11
    Mirror 1 - Click here

    System Version 2.7.22
    Mirror 1 - Click here

    System Version 2.7.26
    Mirror 1 - Click here

    System Version 2.7.26-2
    Mirror 1 - Click here

    System Version 2.7.26-3
    Mirror 1 - Click here


    Changelog (Unofficial)

    System Version 2.7.29
    • Unknown
    Previous Versions
    System Version 2.7.28
    • Unknown
    System Version 2.7.11
    • Unknown
    System Version 2.7.9
    • Unknown
    System Version 2.7.4
    • Unknown
    System Version 2.6.96
    • Unknown
    System Version 2.6.93
    • Unknown
    System Version 2.6.77-2
    • Unknown
    System Version 2.6.77
    • Unknown
    System Version 2.6.73
    • Unknown
    System Version 2.6.70
    • When changing panel keys or steering wheel controls, the notification bar is still displayed
    • New menu option for backing up and restoring both panel key and steering wheel control mappings
    System Version 2.6.68
    • Homescreen design reverted back to four large widgets per page
    • App icon for SWC settings
    • Setting in "Extra Settings" to force USB1.1
    • Factory reset is password protected (See FAQ)
    • Developer options are password protected (See FAQ)

    System Version 2.6.62
    • Bluetooth icon in notification bar (appears Bluetooth is turned on by default now, cannot turn it off)
    • Bluetooth menu, accessed via an app, has "SEARCH FOR DEVICES" and visibility option, however nothing functions when pressed
    • All extra applications removed (ES File Explorer, GPS Test Plus, QuickPic)
    • WiFi Hotspot can be activated without re-plugging the 3G dongle in
    • Background is winter-themed

    System Version 2.6.60-2
    • New home screen design
      2013-11-15 22.17.48.jpg
    System Version 2.6.60
    • Default applications changed back to original theme
    • APK Installer application install by default
    • Bluetooth renamed back to Phone
    • Screenshot feature now fixed and works correctly

    System Version 2.6.40
    • Larger notification bar
    • GPS icon removed from notification bar
    • Home, back, menu, and screen off buttons added to notification bar
    • Default applications changed to red theme (music player, radio, video player, phone)
    • Phone application renamed to Bluetooth
    • ES File Explorer installed by default
    • GPS Test Plus installed by default
    • QuickPic installed by default
    • Non-functioning screenshot featured added in settings menu



    Bugs / Issues

    Key
    Unresolved
    Workaround
    Resolved

    Updated 2014.01.20
    Newest issues will be put at the top, solved issues, or issues with workarounds will be moved to the bottom.

    Unable to remove applications that are device administrators without factory reset due to security menu being disabled.

    Many applications are unable to "see" the MicroSD card, so the choice of music players is limited. The mount point is "mnt/usb/mmcblk1p1".

    Despite selecting "Front Speakers Only" for navigation sound, the sound comes out of the rear speakers too. Setting to "Front Right" appears to work correctly.

    Bluetooth is restricted to phones only. (Unsure if this is hardware or software related, talking to manufacturer suggests hardware limitation).

    Bluetooth dongles do not work.

    There is a "pop" from the speakers sometimes when changing applications that control sound, this is extremely obvious if you have a subwoofer installed. It happens when the unit is turned on, and when going from mute, to a volume level.

    Screen brightness when buttons illuminated is not user-configurable. This means it may be too bright or dark depending on the conditions. For example, when it is only mildly dark outside, and you have your lights on, the screen is very hard to see.
    Workaround: Enable constant illumination from the "Extra Settings" menu by setting the option to "CLOSE", this will set the keys to always illuminate. Then use an application such as Twlight to control the screen brightness based on sunset and sunrise.

    Random issue when downloading large applications. The progress will usually get to more than 50%, and then no progress is made.
    Workaround: The only fix I have found so far is to stop the download, reboot the unit, start the download, and repeat until download continues. It should download from where you cancelled. This appears to be caused by a limited download cache size.

    Steering wheel controls only work with default applications.
    Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, allowing steering wheel controls to function with other apps.

    Most recent default application always opens on boot and continues to play, even if paused. This includes the radio, music, video, and iPod applications.
    Resolved: Open the radio (this does not appear to work with the music app), then hold the back arrow in the bottom right hand corner, the app will close, and no default app will open on boot.

    USB Debugging is password protected.
    Resolved: The password is "[email protected]". Credit to @nikko82

    Screenshot feature does not work, when trying to save the screenshot, a save error appears.
    Resolved: This is solved in system version 2.6.60.


    Root

    Root is now possible thanks to help from some great XDA members.

    Credits to @WonderEkin for the Root My AN-21 U app and @bmj67 for supplying SettingsProvider.apk

    2014.06.06 - A new rooting tool named Baidu Root has been added to the repository. You can use this tool as an alternative to following the guide below.

    Files required
    Root My AN-21 U - [ Mirror1 | Mirror2 ]


    Root My AN-21 U has been updated since this video was taken, the app should now correctly show "Step 2".

    1. Download the required files above.
    2. Install Android Terminal Emulator on your unit.
    3. Open the AUX application and close it.
    4. Install Root My AN-21 U and create a link on the homescreen.
    5. Run Root My AN-21 U and press the "Step 1" button.
    6. Reboot the unit.
    7. Once the unit has rebooted the screen will likely be black, press the Home button to display the homescreen.
    8. Run Root My AN-21 U and press the "Step 2" button.
    9. Reboot the unit.
    10. Open Android Terminal Emulator and run the following commands.
      Code:
      su
      rm /data/local.prop
    11. Reboot the unit.


    FAQ

    Can I root this unit?
    Please see the "Root" section above.​
    HELP! My unit is stuck in a boot-loop!
    Place the update files on your MicroSD card (see "Firmware Updates" section). Then turn the unit on whilst holding down the volume knob and home button. This should start the update process.​
    Can I use Bluetooth OBD devices with Torque?
    Not at the moment, Bluetooth is only for phones and Bluetooth dongles do not work.​
    Does it have the full Play Store?
    Yes, it has the Play Store and all compatible applications are available for download.​
    What is the boot time?
    18 seconds to home screen, 22 seconds until music application starts. If you use the radio application rather than the music player, the radio sounds as soon as the unit receives power.​
    Where can I buy one?
    There are many listings on eBay/AliExpress under the search term "android 4.1 car", some have resistive, and some have capacitive screens. There is also the mention of a faster 1.2GHz dual core, however the unit actually has a 1GHz dual core CPU.​
    How good is the radio?
    The radio reception seems fine, as does the sound quality.​
    Is there a Wiki page?What is the USB Debugging password?What is the Factory Reset / Developer Options password?
    7890​
    What is the Extra Settings password?
    123456​
    13
    Skinning/Modding AN21 system apps

    For all people who are interested to "skin" their AN21-U, I'd like to post some of my customizations:

    In general, it is super easy to change the appearance of the AN21 apps. Some experience with XML-based layouting programming languages such as Android, Java or WPF makes life easier but is not mandatory. I attached a detailed HOWTO below...

    A few words about my design thoughts: I tried to combine the red-themed flat style of the new Golf 7 infotainment system with Android JellyBean look&feel. Due to my blue temperature displays (-> first picture) I tried to reuse the same blue color in all system apps:

    P1050087.jpg
    Great VW boot animation, downloadable at i-cartech-forum.tk. Credit goes to raabi (YouTube video)

    Screenshot_2014-02-09-18-06-48.png View attachment 2617927
    ADW launcher with Car Widget & custom background
    Custom status bar without soft buttons (SystemUI.apk)

    Screenshot_2014-02-09-18-08-09.png
    Radio app: side note - even Radiotext is supported with this unit (not very common with chinese headunits)

    Screenshot_2014-02-09-18-08-58.jpg
    Equalizer, Zone settings

    Screenshot_2014-02-09-18-09-20.png
    Equalizer, Faders

    View attachment 2569467
    Phone app; I tried to use as much space as possible to avoid line breaks within contacts like in the factory design

    Screenshot_2014-02-09-18-10-11.png
    Phone app; Dialer

    Screenshot_2014-02-09-18-13-52.png
    I use Poweramp instead of the Music app; looks a lot fancier with the album covers

    Screenshot_2014-02-09-18-15-23.png
    Parking sensors (service app): I changed the car top view, colors and I also modified the smali code to display the range of my parking sensors correctly (outer sensors have less range than center sensors)

    HOWTO: Mod/Skin system applications
    Requires root access

    1.) Download apktool
    2.) Extract it to your hard disk
    3.) Copy the system app to modify (*.apk) from /system/app to an external USB stick
    5.) Copy the apk file to the location of apktool
    4.) Copy the apk to a different backup location (in case that something goes wrong)
    6.) Open command line and navigate to the location of apktool
    7.) Enter apktool d systemapp.apk (this will decompile the system app)
    8.) Change Icons and image resources (located in res/drawable-mdpi)
    9.) Change application layout (located in res/layout)
    10.) Rebuild the app by entering apktool b systemapp systemapp_MODDED.apk
    !!!
    IMPORTANT STEPS (otherwise the modded app won't work on the unit):

    11.) Open the original systemapp.apk with a ZIP tool (such as 7zip) and extract AndroidManifest.xml and the META-INF folder to your hard disk
    12.) Open your newly generated app (systemapp_MODDED.apk) with a ZIP tool and drag AndroidManifest.xml and the META-INF folder to your app archive
    !!!
    12.) Copy the systemapp_MODDED.apk back to your USB stick
    13.) Rename it back to systemapp.apk
    14.) Use RootBrowser on your unit to copy your modded systemapp.apk from the USB stick to /system/app/
    DONE!

    Those steps sound more complicated as they are. If you get some practise in modifying apps it actually takes about 1 minute...
    You can also use ADB over WIFI for grabbing and copying the system apps; In that case you have to ensure that you remount the /system partition as Read/Write (rw).

    EDITING THE SERVICE APP:
    Please be careful with editing the com.tw.service_a5a4.apk since this app handles all the communication with the MCU (so nearly everything). Coding mistakes will potentially cause constant crashes of the app, causing a modal popup to appear, which makes it nearly impossible to interact with the Android system then. I nearly destroyed my firmware with such a carelessness -> the only possibility then is to reflash a factory image. So please be careful, especially with this app.
    13
    After a while something new from my side:
    I modded the system apps of 2.8.7 to look a bit more like Google's "material design" to harmonize better with current apps. In my opinion the chinese developers tend to add to much of everything, especially glossy buttons :D

    Anyway, here is the SystemUI with a thinner status bar without buttons and with white icons + text:
    Screenshot_2014-11-17-18-18-33.png

    Radio app:
    I actually like the layout of the Radio app.
    Moreover, I modified the smali code so that the radiotext always appears centered (that annoyed me a lot ;) ):
    Screenshot_2014-11-17-18-18-50.png

    The Equalizer:
    Screenshot_2014-11-17-18-19-05.png

    And the Phone app:
    View attachment 3020346

    If someone is interested in the APKs, find them attached. Simply copy the files into system/app and get the permissions right (or use RootBrowser for copying).

    BTW: Does anyone have the link to the post which described how to modify the phone app to display the contacts in alphabetical order? I know that there was a post in this thread, because I did that once (I think it was written by Nikko). However, I wasn't able to find the post with the forum search.
    11
    MCU naming scheme

    --- snip ---
    Has anyone deciphered the MCU naming? I saw a few posts back that someone has.
    --- snip ---

    Ok here it goes... by disassembling one of the system files from 2.7.11, this is what I found:

    DISCLAIMER: This does not mean, that you can change the features in the MCU firmware by renaming the .zip files. You can change how they are presented in the model choose list, but the firmware will remain the same.
    This is purely for informational purpose, about how to identify the various .zip files. I take no responsibility for the accuracy of this information - Viewer Discretion Is Advised as they say.

    ... and before you ask - I don't know what all the features mean or do. The strings are copied from the source.

    Model Choose:

    This function looks for *.zip files in "/system/etc/mcu"
    Translates zip names into various information for model choose list.
    When selecting a model in the list, it unpacks the MCU file from the corresponding zip to "/data/tw/4bf18a00-297a-11e3-ab19-000c29ba27c0"
    ... and flashes it, I presume :fingers-crossed:

    File naming scheme:

    v.v.v-a-bb(b)-ccde.zip

    Translates to:
    "Car model(Version, Features, Audio chip, Tuner chip)"

    v = Version
    Used "as is" in building the model choose list.

    a = ?? (hardware revision perhaps ?!)
    (During model choose dialog creation, it looks like some value in the mcu is queried, and checked to be between 1 and 9999 (otherwise model choose aborts). Additionally [a] must match this value for the file to be included in the model choose list.

    bb(b) = Car model (default "Normal")
    Two or three digits. The two first digits are translated to the list below. A third optional digit translates to some additional feature.
    10 = VW
    20 = CRV/CIVIC
    22 = CRIDER
    30 = Camry/RAV4
    40 = Mondeo
    41 = Focus
    42 = F350
    50 = Mazda
    51 = CX5
    60 = IX35
    61 = IX45
    70 = Teana 2012
    71 = Teana 2013
    81 = Opel
    90 = PSA508
    F0 = V5
    F1 = X80
    xx1 = add "RZC" to features
    xx2 = add "HC" to features

    cc = Features (binary bitmask)
    bit 0 (.......1) = RDS
    bit 1 (......1.) = Sleep
    bit 2 (.....1..) = AD
    bit 3 (....1...) = 2Din FZ (bit 3 and 4 are mutually exclusive and mapped to some string array, no value exist if both bits are set)
    bit 4 (...1....) = 1Din FZ (bit 3 and 4 are mutually exclusive and mapped to some string array, no value exist if both bits are set)
    bit 5 (..1.....) = Color
    bit 6 (.1......) = BC6 (most likely code for BlueCore6 module, supporting OBDII - thank you @julsn; ref. #4009)
    bit 7 (1.......) = NODVD

    d = Tuner chip (default 0)
    0 = TEF662X
    1 = SI47XX
    2 = TEF665X

    e = Audio chip (default 0)
    0 = TDA7415
    1 = Rohm37534
    2 = TDA7719

    Some examples:
    4.2.15-1-10-2101 = "VW(4.2.15, RDS, Color, Rohm37534, TEF662X)"
    4.2.15-5-30-8001 = "Camry/RAV4(4.2.15, NODVD, Rohm37534, TEF662X)"
    4.2.15-8-10-E501 = "VW(4.2.15, RDS, AD, Color, BC6, NODVD, Rohm37534, TEF662X)"
    4.2.15-11-902-4501 = "PSA508(4.2.15, HC, RDS, AD, NODVD, Rohm37534, TEF662X)"

    Notice the numbers marked with RED ??
    As stated above, the .zip file will only appear in the model choose list, if this number matches the previously queried value from the MCU. It's probably some hardware revision check, to make sure you only flash an MCU that's compatible with the hardware you have. I don't know for sure though.

    So that's about all she wrote - have fun ;)


    /Miwer

    Edits:
    31-07-2014 - Added information about BlueCore6 module. Minor layout change
    10
    USB debugging password

    Hello,

    This is my first post here. I just received my unit, which I think is the same as discussed here, two days ago. I have discovered the password for USB-debugging, and as far as I can tell no one has posted that before. The password is "[email protected]".