Premier AN-740 (witson w2-k7xxx) info. thread

[schwrz]

After a lot of searching here and elsewhere I was not able to find a unit that matches these parameters. The unit was branded as Premier AN-740 which is obviously just a sticker label. Any help with identifying this unit will be greatly appreciated.

About Device LINK http://ibb.co/nMEroA

About vehicular platform 1/2 LINK: http://ibb.co/nBWU8A

About vehicular platform 2/2 LINK http://ibb.co/hyiFgV

Update: The stock ROM for this unit accepts 8888+OK as "secret code" to get to the opening logo customization screen. Maybe this provides a clue?

 

[schwrz]

Update #2: Droid HW report

DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: TS356XXPH-
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2017/05/15 10:24
RIL Version: mtk gemini ril 1.0
Build Number: full_evb3561sv_w_65_m0-userdebug 6.0 MRA58K 1510921099 test-keys
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MRA58K/1510921099:userdebug/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23

DISPLAY
Resolution: 1024x600 pixels
Software Density: 240 dpi (hdpi)
Refresh Rate: 57.44 Hz

PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: Not Available
Kernel Version: 3.18.19
Kernel Architecture: aarch64

GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0

RAM
Total: 1897 MB
Java Heap: 128 MB

STORAGE
Internal: 11 GB
External: 7.2 GB

PRIMARY CAMERA
Resolution: 0.4 MP
Flash: No
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480

Video:
800x480 (WVGA)

SECONDARY CAMERA
Resolution: 0.4 MP
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480

Video:
800x480 (WVGA)

FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes

BATTERY
Technology: Li-ion
Health: Good

SENSORS
Not Available

Created by Droid Info

 

[schwrz]

Update #3: ROOT!

I was able to root my device using the procedure outlined here:

https://forum.xda-developers.com/android-auto/android-head-units/ownice-c500-root-t3558760

Using the longer password and with some minor command line alterations (see screenshot here https://ibb.co/njSw5q). Hope this helps someone.

My next goal is to get to the factory settings. If anyone gets the code for that please post it here.

 

[MrDeepPurple]

head unit info

Hello, it seems that I have the same head unit. Mine is unbranded and it's shaped to fit a 2008 suzuki swift, however all the codes seems the same.

What I got until now is that 8888 is the boot logo code selection and I can access to the engineering mode menu by dialing *#*#3646633#*#*

I'm trying to perform a factory reset because I accidentally delete the "su" executable and I cannot access it anymore even with the password, howevere there is a factory reset password that I can't find on the net. The next step will be trying to access the "RST" button and check what it does.

 

[schwrz]

Hi Mr. Purple,

Thanks for your code

I can access to the engineering mode menu by dialing *#*#3646633#*#*

I can confirm that it works for me as well. I was not however able to locate the FM Radio settings I was looking for (let me know if you find those).
Good luck with the factory reset, and let us know how it turned out.

 

[MrDeepPurple]

Updates

I have some news:

The actual model seems to be the witson w2-k7xxx (in which xxx is the code of the shape of the front panel, mine is w2-K7658).

l. I was not however able to locate the FM Radio settings I was looking for (let me know if you find those).

I managed to access the system menu with the code 3711 and here there are the FM settings!

Here follows what I discovered by trying and trying again and searching on the net:

CODES (to be inserted in Settings > software version > small gear icon near HMI):
3711 -> factory settings
8888 -> boot logo settings
6666 -> a chinese text that reports "no update files where found" appears (probably the update code)
7777 -> a chinese text that reports "no update files where found" appears (probably the update code)
0 -> MCU update page

How to access the engineering mode:
dial *#*#3646633#*#*

How to access the firmware update page:

• Click the RST button
• touch the screen (and move your finger) until a writing appear on the top left
• if a binary file is present in the root of the SD card, then the update begins

How to perform a factory reset: (/system partition is left unchanged, only user data is wiped)

• Click the RST button
• touch the screen with five fingers (and move them) until a writing appears on the top left
• The factory reset procedure will begin. It lasts for 10 minutes

I mailed witson for a firmware update (in order to override the /system partition and restore the su executable) but they ask me for a serial number that is written on the unit. I will disassemble it in a couple of days and if I manage to get this update, I will post it there. However it seems that each model has its own custom firmware that supports only one button layout. If I flash a firmware of the same family (w2-k7xxx) but from a different model, the buttons may not work.

Maybe you can find your own model on witson website

 

[schwrz]

I have some news

Wow man, you've really been busy! I'm definitely going to try out those codes and knowing who the manufacturer is will help as well. The user interface here definitely looks familiar, though I'm a bit confused as to how you were able to discover the XXX code in the W2-K7XXX part number of your unit. In any case thanks again for all the info and keep us updated, especially if you manage the much needed firmware update...

 

[MrDeepPurple]

though I'm a bit confused as to how you were able to discover the XXX code in the W2-K7XXX part number of your unit.

Well, my HU has the panel that fits only in the 2008 suzuki swift, so I used the search engine on their site to look for "Suzuki Swift" and there I got the part number!
However if you have a standard panel maybe you can go in product page, then on the left column select "+ For Universal All-in-one" and see if one of the model is the one you own. In that page I see only 4 Android 6.0 headunit: W2-K7900G, W2-K7927G, W2-K7902 and W2-K7924 (I can't send link because I'm new on XDA, but you can easily find them)

From the photos you posted, it seems that your HU is the W2-K7927G

 

[schwrz]

From the photos you posted, it seems that your HU is the W2-K7927G

Yes, I think so too ( Link for anyone interested). It would be nice to be able to confirm that this is indeed the exact model before we attempt a firmware update as flashing the wrong firmware is almost guaranteed to brick the unit (i'll try to search for th exact P/N in the "hidden" menus). Besides, now that I have all these secret menus to play with, maybe I can fix the problems I experience without a firmware update. The biggest two issues are speaker noise while idling (even when radio and music player are off) and waaay too jerky FM reception (unit is constantly trying to find a better frequency for the current station - I was told that I need to lower the FM sensitivity in the technician menu to fix that). If I can fix these two issues, I can definitely live without a F/W update. Did you experience any of these issues or is it just my particular model / unit?

 

[MrDeepPurple]

Did you experience any of these issues or is it just my particular model / unit?

yes, the idle background noise is too loud too on mine. The reception seems fine, just a little worse than the suzuki stock radio definitely usable. However if you find a solution for both, I think I will try it too! At the moment I'm stuck to solve the "su" problem!

 

[schwrz]

sorry to hear that.
i assumed the factory reset took care of the SU problem.

 

[MrDeepPurple]

Other updates

sorry to hear that.
i assumed the factory reset took care of the SU problem.

Unfortunately the factory reset only reset the user partition, but the /system partition is left unchanged.
However after two weeks of mails, I finally got a firmware update binary from Witson.
I don't know if it's compatible to your radio, however i mailed to [email protected], they asked me for a product code placed on top of my Head unit and then sent me the update after I provided the code.
Here a picture of the location of the product code on my unit (it's the top side of the box):

Maybe you can ask for a firmware too with your serial and then we can check if it's the same file.

Now I'm trying to fixing a network bug that made my cellular network connect to a roaming operator (TIM) instead of my operator (three) due to a wrong priority assignment.

 

[schwrz]

As always nothing but helpful information from MrDeepPurple (seen them in concert not too long ago hehe). I feel kind of ashamed for not contributing anything.

... they asked me for a product code placed on top of my Head unit and then sent me the update after I provided the code.

I plan to take apart the center console in my car during this weekend so I'll be sure to check for that code - in addition to a few other things I've been saving for this event such as debugging that horrible background noise we talked about. I plan to disconnect the HU from all peripherals one by one until I find the culprit. If the HU itself is generating that noise I'll need to rethink my strategy. As for the radio reception, I did find the radio sensitivity setting thanks to your help and lowering it did help a little, but it turns out I've been kind'a stupid not noticing how short the antenna the previous owner put on the car was. With that size it was physically impossible to get good reception, so I just ordered an OEM antenna from the car manufacturer and hope to be done with this problem. The moral of this, I think, is that even though this HU is pretty sh**ty, we shouldn't be so quick to blame everything on it as there are other components in the system. One thing to note to anyone fiddling with the system settings from the codes MrDeepPurple provided, be aware that saving the settings will RESET YOUR HOME SCREEN TO STOCK so if you want to try out different settings do it all in one go, otherwise you'll end up having to replace all your widgets and things to the way you like them about a zillion times.

Now I'm trying to fixing a network bug that made my cellular network connect to a roaming operator (TIM) instead of my operator (three) due to a wrong priority assignment.

It seems that the problems never end with this HU - is this bug due to the firmware update?
At this pace by the time we get them to perform adequately they will be outdated.
Anyways good luck and keep updating.

 

[MrDeepPurple]

It seems that the problems never end with this HU - is this bug due to the firmware update?
At this pace by the time we get them to perform adequately they will be outdated.
Anyways good luck and keep updating.

yes, this happens on a random OTA update I received a month ago. I didn't even know that this HU can have OTAs. However I'm not able to select network type (2G, 3G, 4G) anymore because the menu is greyed and instead it appeared a menù with PLMN editing. I didn't even know what a PLMN was before that.
However this menù is totally useless, the selection and the editing of PLMNs is resetted when you exit this menu. The PLMN which has the highest priority is TIM, then comes three UK (why uk? iI'm in italy!!). I read that there is a sqlite db accessible only with root permission that contains those informations so I need root to access it.

As always nothing but helpful information from MrDeepPurple (seen them in concert not too long ago hehe). I feel kind of ashamed for not contributing anything.

You contributed to find the correct way to root this HU that is the most useful information to me by now!! Thank you!

 

[MrDeepPurple]

well, it seems that the root procedure doesn't work on mine.

After all the steps on Ownice C500 post (even with the short password on forfan executable and the long one with the su executable) it seems that the root doesn't work. When I try to run the su command on a terminal emulator it returns 1. It's a generic error code, so there should be something missing. However I'm not scared to test it now that I have the firmware update files.

Did you use the su executable in the Ownice C500 post?
Are the other file useless (libsupol.so, sukernel and supolicy) ?

 

[schwrz]

well, it seems that the root procedure doesn't work on mine.

so with the firmware update they also patched the system against rooting?
makes me think twice before updating...

Did you use the su executable in the Ownice C500 post?
Are the other file useless (libsupol.so, sukernel and supolicy) ?

Having performed the root two months ago I'm sorry to say I don't really remember much. However two things are clear from the screenshot (third post in this thread):
1. I used the longer password.
2. Only the actual su file is copied and given execution permissions.

Not sure what's the source of that 'su' executable but it's probably from the link given as I can't recall doing otherwise.

 

[MrDeepPurple]

Today I received a new update binary, I will try to upload it soon and check if it solves my problem

 

[k5235]

DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: TS356XXPH-
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2017/05/15 10:24
RIL Version: mtk gemini ril 1.0
Build Number: full_evb3561sv_w_65_m0-userdebug 6.0 MRA58K 1510921099 test-keys
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MRA58K/1510921099754[/U]:userdebug/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23

DISPLAY
Resolution: 1024x600 pixels
Software Density: 240 dpi (hdpi)
Refresh Rate: 57.44 Hz

PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: Not Available
Kernel Version: 3.18.19
Kernel Architecture: aarch64

GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0

RAM
Total: 1897 MB
Java Heap: 128 MB

STORAGE
Internal: 11 GB
External: 7.2 GB

PRIMARY CAMERA
Resolution: 0.4 MP
Flash: No
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480

Video:
800x480 (WVGA)

SECONDARY CAMERA
Resolution: 0.4 MP
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480

Video:
800x480 (WVGA)

FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes

BATTERY
Technology: Li-ion
Health: Good

SENSORS
Not Available

Created by Droid Info

I just buy and new android head Units is name DynaVin 2GB 16GB with 4gLTE .
The "Droid info" i get only 2 was difference from yours as below shown .
1)build number difference from 1510921099 mine 1511340754
2)build fingerprint difference 1510921099754 mine 1511340754

I Found 2 Bug
1) Minor Noisy Sound when in idle mode .
2) Waze Hang when using 4G Lte . Reseat 4G Card then be ok again
Anyone can provide some ideal ?

 

[MrDeepPurple]

I just buy and new android head Units is name DynaVin 2GB 16GB with 4gLTE .
The "Droid info" i get only 2 was difference from yours as below shown .
1)build number difference from 1510921099 mine 1511340754
2)build fingerprint difference 1510921099754 mine 1511340754

I think it's the same head unit, probably the differences are only on firmware release version

1) Minor Noisy Sound when in idle mode .

This is a common bug, schwrz was trying to solve that but it seems to affect all the radios with the MTK3561

2) Waze Hang when using 4G Lte . Reseat 4G Card then be ok again
Anyone can provide some ideal ?

I've never tried waze on it, only google maps and sygic and they both works fine! Well, sygic is a bit slow and laggy but still usable.

 

[schwrz]

I think it's the same head unit, probably the differences are only on firmware release version
I've never tried waze on it, only google maps and sygic and they both works fine! Well, sygic is a bit slow and laggy but still usable.

The main reason I've put Android in the car is be able too use Waze properly (i.e. no weird phone holding gadgets) so yes, I can confirm that Waze works fine on this HU. Otherwise I'd have replaced it long time ago.

As for the idle noise, I currently tend to think it's a hardware rather than software issue. I'm going to take apart the center console and see what's what as soon as I receive some parts I'm waiting for (for which I also need to take apart the center console - no sense in doing it twice). Will report my findings.