Related
I'm not responsible for what might happen on your phone if you choose to dial any of these!
These are the codes that work on the standard phone dialler app on the Orange San Francisco, but I'm pretty sure they'll be almost identical on other models that we collectively know as "ZTE Blade". Known small differences (in texts) are down to whether the firmware expects to be running on an OLED or TFT display, and whether you've deleted seemingly unused apps like ChiperTest.apk, fcctest.apk and QcNvTest.apk. Most are prefixed with "*983*", which is "*ZTE*" in phone letters -- I've added a mnemonic for the other part where I think it's obvious (feel free to suggest better ones!).
"Automatic Inspection" runs through the basic tests automatically (usually you need press a button to move on to the next bit -- don't get thrown by any blank colour test screens!). There are a number of interesting items for developers, with hardware info and other goodies. If any of the descriptions don't make the function obvious then it's either poorly written or I don't know exactly what it does (I'll happily update this if others can explain better).
If the code has been recognised by the dialler then it will react immediately when you enter the final "#". If nothing happens when you've done that, don't press Dial!
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dial Mnemonic Operation
*983*0# Menu (20:Battery/OLED/Back Light/Vibrator/Ringer/LED/Key/OLED off/SD/BT address/Radio Info/Memory/TouchPaint Test/Audio Loop/FM/Camera/GPS Test/IMEI/IMSI)
*983*3640*01# IMSI
*983*25# Battery Info[/COLOR]
*983*31# OLED Test
*983*26# Backlight Test
*983*850# Radio Test 0
*983*86# Vibrator & LED Test
*983*84# Ringer Test
*983*07*01# Headset Test
*983*07*02# Key Test
*983*3470# LCD Test
*983*81# SD Test
*983*890# -
*983*26*# Radio Test 1
*#06# IMEI
*983*27274# CRASH Reboot
*#08# Test Flag [Note: requires QcNvTest.apk in /system/app]
*#09***# BT Test
*983*1275# _ASK Dev Info
*983*7# Menu (4:Version/IMEI/IMSI/BT address)
*983*3640# DOH+ Phone Info (inc ping test, radio on/off)
*983*636# MEM Memory Test
*983*28# BT Emode BT Test
*983*477# GPS GPS Test
*983*21# Audio Loop Test
*983*70# Automatic Inspection
*#18# LED Test
*#19# TouchPaint Test
*983*36# FM FM Test
*983*57# Factory Reset
*983*473# Camera
*#23# Video Camera
*983*10# Delete (Touchscreeen) Calibration File
*#25# FM Test
*983*2726# SIM Contacts Op 1
*983*37# SIM Contacts Op 2
*983*6726# SIM Contacts Op 3
*983*154# "test" Menu (12:Self-starting/Software
Version/Hardware Version/PSN/Test Flag/[Completed]/Board Serial/Bluetooth
Address/SMS security/SMS Registration Status/Flash Type/PRL Version/Serial Configuration)
*983*07# Menu (9LED/Ringer/Vibrator/Key Test/Audio Loop/Headset Test/FM/Camera/SD)
*983*5182# Dev Info
*983*7469# SHOW Automatic Inspection
*#26***# Sensor Test
*983*7936# QXDM Save Qxdm in log system
*987*0# Menu (4roduce Information[->"test" Menu]/Automatic Inspection/Factory data reset/Battery information)
*#27***# Compass Test
*983*87274# USBSI USB Switch Test
*983*06# BT Test
*983*564738# LOGSET LOG Set (inc sys_rw)
*983*93# FCC Test [Note: requires fcctest.apk in /system/app]
*983*2377# CFQP Call Forwarding Query with PowerOn
*983*24474636# CHIPINFO Chiper Test (chip info) [Note: requires
ChiperTest.apk in /system/app]
*983*29873283# AXUPDATE Touchscreen Updater
*983*73564# SDLOG SD Log
Note: the above are for the standard ROM (well, apps) running 2.1. The current Froyo ROM (with standard dialler, etc.) does not have the Touchscreen Updater, but adds:
Dial Operation
*987*123456# DM Test
IN modaco
Hello, what code shude I use to know if my SF is TFT or Amoled?
Regards!
Check the build number in Settings>About Phone. AMOLED ends in 05, LCD ends in 08. IIRC all white SF models are 08 and most grey are 05 (unless its a newer unit which will likely be 08).
Thank´s man.
Mine is 01. What that means?
Looking at the screen characteristics it seems like LCD.
Thanks man. great post
Really nice. Works on Boost Mobile Warp Sync N9515.
Would you happen to have a code that forces prompt for unlock? (Changing sim cards doesn't trigger anything)
same here... up for this....
No Boost Mobile ZTE Warp Sync N9515 Unlock Screen
chinnyss said:
same here... up for this....
Click to expand...
Click to collapse
I think unlocking the Boost Mobile is a lost cause. I've tried several other sims and the only codes I've found to show the unlock menu don't work:
1) Alright then please remove the SIM card and try this code ###825*09#,
2) Got the prompt for code? Please enter the code you received,
3) Failed above, try *983*8284# to access the Unlock Menu,
4) Failed above, finally try *983*865625# to access the Unlock Menu.
zte warp elite n9518 rooted but still i can't use MSL reader or alogcat it says in root checker verify root congrats and after rebooting i got to root again please help just need to get SPC and or MSL code
You the MAN! THA KS.
kelvinpacquette said:
zte warp elite n9518 rooted but still i can't use MSL reader or alogcat it says in root checker verify root congrats and after rebooting i got to root again please help just need to get SPC and or MSL code
Click to expand...
Click to collapse
Can u tell me rhat what do i need to enable usb debigging or adb mode ?? I have to connect my zte z982 device to miracle sodtware, but unable to connect because frp lock.
I cant enable usb debugfing
techeligible3322 said:
Can u tell me rhat what do i need to enable usb debigging or adb mode ?? I have to connect my zte z982 device to miracle sodtware, but unable to connect because frp lock.
I cant enable usb debugfing
Click to expand...
Click to collapse
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dialing the first set of numbers made it possible for me to turn on abd....
Sent from my SM-G550T using Tapatalk
Alright
paigesdavis1996 said:
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dialing the first set of numbers made it possible for me to turn on abd....
Sent from my SM-G550T using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply
How did you enter / enable adb? I have a 971 and the 2nd code from your site doesn't work, I am able to enable eng. mode
I also tried the connect to computer in control panel and that doesn't do anything either.
Frp locked
Trick
techeligible3322 said:
Thank you for your reply
Click to expand...
Click to collapse
This worked for me and I have the ZTE z blade max thank you
Has this been proven to root the phone yet ? Please leave feedback .
Good News
#Starlord37# said:
This worked for me and I have the ZTE z blade max thank you
Click to expand...
Click to collapse
That's very good to know you are welcome
I haven't had a chance to try it fully yet as I have been trying to root my girlfriends Moto e4 with magisk which I will probably have done by the end of the night and then I plan to tackle my z982 will keep you posted though
Hello. I've been getting a lot of emails on how to do that and i thought i should make a thread here.
Now you got to have the original box in which there is the imei written. I don't take any credit for this guide as i didn't write it but i found it somewhere here but it doesn't exist anymore. I'm not responsible for any damage may happen to your phone. I did it several times after flashing official 2.3.5.
It has worked fine with my IDEOS X5 U8800.
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk...012_09_12.html
c. Software for restore
http://www.2shared.com/file/xBxUOnPz/DFS.html
2. Enable debugging by USB in the settings.
In call type * # * # 2846579 # * # * http://postimage.org/image/tnj4s2dyj/
3. Go to ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode and corfim.
4. Go again to ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0 and corfim.
5. Go again to ProjectMenu -> Background settings -> Log setting -> Log switch put log on and corfim.
6. Now conect your phone to pc and install the drivers.
You must see this at your device manager http://postimage.org/image/5lrm61agd/
7. Instal DFS and run.
8. Click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
http://postimage.org/image/3l3bmfyzr/
9. In the DM select Qualcomm.
http://postimage.org/image/6bmt1908z/
10) Press the SPC, the bottom will Device Unlocked.
11) Select Programming and in the IMEI write yours and press Write.
http://postimage.org/image/dmbp29q35/
13) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
Check IMEI *#06#
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
Good luck..
Thanks a lot... now I got my imei back. But now I have one another problem, I installed ics rom and now my wifi Mac id is 00:00:00:00:00:00. Are they related?
Sent from my U8800 using XDA Premium 4 mobile app
I don't think so. But I've already replied somewhere on how to fix mac address. Search
Sent from my U8800 using xda app-developers app
Didn't work for me
Cybergiannis said:
Hello. I've been getting a lot of emails on how to do that and i thought i should make a thread here.
Now you got to have the original box in which there is the imei written. I don't take any credit for this guide as i didn't write it but i found it somewhere here but it doesn't exist anymore. I'm not responsible for any damage may happen to your phone. I did it several times after flashing official 2.3.5.
It has worked fine with my IDEOS X5 U8800.
1. Tools
a. Drivers for U800 32bit win 7 (tested and work )
http://www.2shared.com/file/fnP5fc8G/u8800Drivers.html
b. Drivers for Android 32 and 64 bit win 7 (not tested )
http://www.2shared.com/file/ZNZ4Q0lk...012_09_12.html
c. Software for restore
http://www.2shared.com/file/xBxUOnPz/DFS.html
2. Enable debugging by USB in the settings.
In call type * # * # 2846579 # * # * http://postimage.org/image/tnj4s2dyj/
3. Go to ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode and corfim.
4. Go again to ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0 and corfim.
5. Go again to ProjectMenu -> Background settings -> Log setting -> Log switch put log on and corfim.
6. Now conect your phone to pc and install the drivers.
You must see this at your device manager http://postimage.org/image/5lrm61agd/
7. Instal DFS and run.
8. Click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
http://postimage.org/image/3l3bmfyzr/
9. In the DM select Qualcomm.
http://postimage.org/image/6bmt1908z/
10) Press the SPC, the bottom will Device Unlocked.
11) Select Programming and in the IMEI write yours and press Write.
http://postimage.org/image/dmbp29q35/
13) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
Check IMEI *#06#
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
Good luck..
Click to expand...
Click to collapse
This procedure did not work for me. I found it a couple of weeks ago in another thread (http://forum.xda-developers.com/showthread.php?t=1591997) and gave it a try (numerous times) without success. I was able to complete all steps up until actually writing the new IMEI. I attempted to write it a couple of dozen times without any success. It appears to work but the lMEI never actually changes.
I also found another procedure using a program called NVedit but it would give me an error stating the NV location was set to read only (I forget the actually wording). It seems that my phone has the location that contains my IMEI locked in some way that nothing can change it. So I gave up on that phone and am using a different one that I bought on eBay, brand new at a dirt cheap price ($27.00).
pastorbob62 said:
This procedure did not work for me. I found it a couple of weeks ago in another thread (http://forum.xda-developers.com/showthread.php?t=1591997) and gave it a try (numerous times) without success. I was able to complete all steps up until actually writing the new IMEI. I attempted to write it a couple of dozen times without any success. It appears to work but the lMEI never actually changes.
I also found another procedure using a program called NVedit but it would give me an error stating the NV location was set to read only (I forget the actually wording). It seems that my phone has the location that contains my IMEI locked in some way that nothing can change it. So I gave up on that phone and am using a different one that I bought on eBay, brand new at a dirt cheap price ($27.00).
Click to expand...
Click to collapse
are you rooted? i remember having these issues when i flashed 2.3 after 4.2 rom. u first need ti flash 2.2 then 2.3 and that should work
Cybergiannis said:
are you rooted? i remember having these issues when i flashed 2.3 after 4.2 rom. u first need ti flash 2.2 then 2.3 and that should work
Click to expand...
Click to collapse
Yes, I am rooted.
I started out on 2.2 way back in the beginning. Then I flashed 2.3.5. That's when I lost my IMEI and replaced the phone.
But I wanted to keep experimenting at getting it working 100% even though I had a new working, rooted, and customized phone. Using 5IromToolBox I restored a backup from the new phone to the broken phone just to see if it would work. Then I flashed Stallion-51-ICS custom ROM. It is a GB based ROM with look and feel of ICS.
When I run the procedure in this thread, everything looks as though it has worked, but the IMEI never changes. So what did 5Irom do differently that it was able to restore the backup from a different phone but I cannot use DFS or NVEditor to write to the locations? The back I made from the new phone and restored to the old one is Consumer Cellular so I suspect they have locked something out that 5Irom is able to get around but other tools don't.
On another note, just for the heck of it I tried to upgrade to ICS from GB and it fails on the first update step. Go figure.
If I could find a full-flash procedure for the pro and 51 versions of this phone I suspect I could resolve all issues. Who knows?
UPDATE: I went through the whole process again and noted a point I forgot to mention. In DFS at the bottom of the screen EQF is yellow, not green. I don't recall exactly what that means but in reading through the DFS doc, it states that writing a new IMEI is not possible as long as EQF is yellow. When I enter my IMEI and click on the WRITE command the response is "MODECHANGE OfflineD OK"
pastorbob62 said:
Yes, I am rooted.
I started out on 2.2 way back in the beginning. Then I flashed 2.3.5. That's when I lost my IMEI and replaced the phone.
But I wanted to keep experimenting at getting it working 100% even though I had a new working, rooted, and customized phone. Using 5IromToolBox I restored a backup from the new phone to the broken phone just to see if it would work. Then I flashed Stallion-51-ICS custom ROM. It is a GB based ROM with look and feel of ICS.
When I run the procedure in this thread, everything looks as though it has worked, but the IMEI never changes. So what did 5Irom do differently that it was able to restore the backup from a different phone but I cannot use DFS or NVEditor to write to the locations? The back I made from the new phone and restored to the old one is Consumer Cellular so I suspect they have locked something out that 5Irom is able to get around but other tools don't.
On another note, just for the heck of it I tried to upgrade to ICS from GB and it fails on the first update step. Go figure.
If I could find a full-flash procedure for the pro and 51 versions of this phone I suspect I could resolve all issues. Who knows?
UPDATE: I went through the whole process again and noted a point I forgot to mention. In DFS at the bottom of the screen EQF is yellow, not green. I don't recall exactly what that means but in reading through the DFS doc, it states that writing a new IMEI is not possible as long as EQF is yellow. When I enter my IMEI and click on the WRITE command the response is "MODECHANGE OfflineD OK"
Click to expand...
Click to collapse
it should be green! what i would do is to flash 2.2 then 2.3.5 and follow again the steps very carefully! maybe u ever flashed a partition and it's not the default one? i can't really help you :/ try this and if it doesn't work make a thread in the q&a section
Cybergiannis said:
it should be green! what i would do is to flash 2.2 then 2.3.5 and follow again the steps very carefully! maybe u ever flashed a partition and it's not the default one? i can't really help you :/ try this and if it doesn't work make a thread in the q&a section
Click to expand...
Click to collapse
Yeah, I knew that it should be green. The bottom line is I do not have the 2.2 image to flash. I would have done that a long time ago if I had it. All I have is the DiskImage backup that I made off of my new phone. When I flashed it onto the old phone it starts, displays the Consumer Cellular logo for about ten seconds then shuts off immediately. As far as starting a thread in Q & A, I did that weeks ago and got nowhere fast.
Any link I have found for the original 2.2 for -51 and pro is usually a broken link. or it takes me to download that stupid iLivid program that doesn't do squat to get the files I need. I did find a DiskImage file that somebody made and posted but it is almost 4 gig in size. You are supposed to use Pink Screen to load it but Pink Screen only gives me access to the image directory and it's only 256 meg.
Thank you for your time and suggestions.
I believe in the wiki section there are links to default 2.2 and 2.3.5. The ones I found a long time ago were from Blefish, although I'm not sure. Good luck!
Sent from my U8800 using xda app-developers app
Dead link.
Hi.
I try to download the "Drivers for Android 32 and 64 bit win 7 (not tested )", but its a dead link. I run win7 pro, and somehow the 32 bit driver doesn't work.
Would like to try the 64 bit driver. Could u reupload it, please?
I just did a repost cause i veen asked a lot of times I don't have the files and I don't thinks drivers are needed. You could just install huawei's suite for PC
Sent from my U8800 using xda app-developers app
WORKS!!!!
Cybergiannis said:
I just did a repost cause i veen asked a lot of times I don't have the files and I don't thinks drivers are needed. You could just install huawei's suite for PC
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
YEY!!!!!!! It worked!!!!
Update the first post with this info so others dont have to struggle like I did.
Thanks a bunch!!! :victory:
ευχαριστω πολυ----thanks man
Hi All,
Many thanks for this post.
Iv recently installed the Blefish CM11 rom for U8800 and its works fine. Only issue I have is IMEI=0. I can make and receive calls and even use the mobile internet.
My question is - Is there a way to edit the IMEI no on KK4.4.2 ROM through entering in the engineering mode?
or else, will have to start from the beginning (stock rom process as mentioned in the OP).
thanks for your help.
mohammad.nomaan said:
Hi All,
Many thanks for this post.
Iv recently installed the Blefish CM11 rom for U8800 and its works fine. Only issue I have is IMEI=0. I can make and receive calls and even use the mobile internet.
My question is - Is there a way to edit the IMEI no on KK4.4.2 ROM through entering in the engineering mode?
or else, will have to start from the beginning (stock rom process as mentioned in the OP).
thanks for your help.
Click to expand...
Click to collapse
i have no idea. my guess is that u should try
Cybergiannis said:
i have no idea. my guess is that u should try
Click to expand...
Click to collapse
Hi,
I haven't found out the way to fix it yet.
Only way I got to fix is to redo the stock rom, root, save the imei and the reflash the custom rom.
The reason for the imei issue was changing the partitions
thnx anyways
this guide that you have post it has been made by me and at least you should have say that is ported from me. Even the links that you have are in my acount. YOU ONLY COPY MY POST . you could ask me to repost it or just mention me. Check this link http://forum.xda-developers.com/showthread.php?t=1876501
The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
better health monitoring
profiles
sleep monitoring
more alarms weekdays/weekend
and more.
(see attached pictures for app version 3.0 UI improvements
Q: What does the settings do?
- Backlight
24H: Backligth always turns on when button is pressed
Nite: Backligth turns on when button is pressed at night time (from 17–8)
Off: Backligth Always Off
- Motion
24H: Motion detection always on (backlight turns on when motion is detected)
Nite: Motion detection on at night time (from 17-8)
Off: Motion detection Off
- Night
On: Notification vibration disabled at night (from 23–8)
Off: Notification enabled at night
- O Clock
On: every whole hour the watch will vibrate. 12'O'clock etc.
Off: Off
- Fitness
On: Fitness functionality on
Off: Off
- Language
Chinese
English
- Anti Loss
On: Alarm when Phone is out of BT range
Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t2864444
Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
Reset from watch (Last menu point, this resets everything)
Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
Connect your watch to the charger. (watch must be charging)
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device and it cannot connect, try an ios device, and vice versa
Q: The watch keeps switching back to chinese
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
Download latest ECO firmware to phone
Disconnect Watch from phone, install ECO app
Go to “Check For Upgrade”
Tap on the middle circle six times
“Select a firmware file___ [Browse]”
Watch must be in forced OTA
Update watch.
You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Go support developer Krzysiek
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
Notification not always deleted from phone when deleted on watch
Watch freezes sometimes
Being able to set the night time manually would be great (This can be done with the Goclever fw)
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
Thanks was this working on ios or android?,
will add to FAQ
taleboblen said:
Thanks was this working on ios or android?,
will add to FAQ
Click to expand...
Click to collapse
Android.
Thx
Thnx for the information, all working ok on my samsung s4, get the last version v3.18.
thx again
backlight
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
chsustik said:
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
Click to expand...
Click to collapse
Thanks for the update. i decrypted some of the information from the official Weloop FAQ. and yes i can now confirm that you are right. it turns on from 17-8 thanks again. I have now updated the FAQ with the correct time for all Night settings. :good:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
Hi , the chronos eco app is not compatible with the Weloop Tommy.
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
l.capriotti said:
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
Click to expand...
Click to collapse
Happened to me also, try to delete connection under bluetooth settings on device. now connect to to weloop and pair from Weloop app. keep trying and then go to update. again persistence is key. keep trying to update suddenly it will connect and update.
Whas the watch on latest firmware when you tried the force OTA?
are you on android or ios see if there is an updated App for you phone. see link on OP for beta APK.
let me know if it works.
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
l.capriotti said:
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
Click to expand...
Click to collapse
Try to update the Weloop app, latest is 1.27.
kill weloop app
delete bt connection from phone.
Open weloop app
conmect and update. Keep trying it can take a couple of times.
If all fails if possible try with other device and or ios device
update: I used an iphone and after a few retries I got it on v3.18.
back to android, but the pairing and the sync is problematic, to say the least, on my Huawei P7...
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
SifJar said:
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
Click to expand...
Click to collapse
Thank you for the insights and findings its all very promising. :good:
On a sidenote:
I talked to one of my colleagues who is an engineer (i'm not a dev but a Designer), it seems like we in the office are playing around with the exact same SOC from NordicSemiconducter. we tried one of the apps from the google play store and it connects to the weloop(see attached pic). The app was called "nRF Master Control Panel", tried the other apps from NordicSC but no luck.
Hopefully there will be some sort of SDK with the v3.0 release on the 30th...
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
SifJar said:
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
Click to expand...
Click to collapse
Thanks for the confirmation. :good:
taleboblen said:
Troubleshooting
Force OTA update:
Connect your watch to the charger.
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device try an ios device, and vice versa
Click to expand...
Click to collapse
I tried to use the OTA update to go from 3.17 to 3.18 (on Android) but Tommy stuck on screen "WeLoop ... Udating 0%", my smartphone (HTC M8) with its APP (latest version) dont find the Tommy and it remains bricked, how do I restart it? I tried all combinations, but remains on the screen, help me!
Can someone help me I am trying to force my Huawei P10 Plus to use LTE/4G only mode. I have latest Firmware/Patch Level.
I have tryed many service codes in format like *#*#.....#*#* codes but I can not set the LTE Only mode.
Isn't it possible without "root"?
It is possible to force "4G only" without root. First download "Setting Database Editor" from playstore. Open it and look for "hw_networkmode_preferences". I use this value "9,3,2,1,11" on my phone. Save it and restart your phone. If you still don't get "4G only" option then you need to open the "Setting Database Editor" again and look for "hw_add_4g_only". Mine was set to "250". You need to change it according to your country mobile code. Look for your mobile country code here: https://en.wikipedia.org/wiki/Mobile_country_code. In my case I change the value to "250;502" since 502 is my country code. Save it and restart your phone.
Tested on rebranded P10 Plus 256GB.
jula182 said:
It is possible to force "4G only" without root. First download "Setting Database Editor" from playstore. Open it and look for "hw_networkmode_preferences". I use this value "9,3,2,1,11" on my phone. Save it and restart your phone. If you still don't get "4G only" option then you need to open the "Setting Database Editor" again and look for "hw_add_4g_only". Mine was set to "250". You need to change it according to your country mobile code. Look for your mobile country code here: <1. o prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!>. In my case I change the value to "250;502" since 502 is my country code. Save it and restart your phone.
Tested on rebranded P10 Plus 256GB.
Click to expand...
Click to collapse
Thank you very much for your Help! I already installed the DB Settings Editor and found out that hw_networkmode_preferences were already "9,3,2,1,11" so this wasn't the case. Additionally I found that I have to add "hw_add_4g_only" so I added it with the wrong Country Code because I didn't know what the hw_add_4g_only means. I was searching for it a few days now and never got an answer, so I was trying to ask here. And you made it clear now. The Wikipedia Link was very helpful and it works now for my Country. I have to set it 262 for O2 Telefonic Germany.
So again Thank you very very much!
Using Huawei P10 (VTR-L29) 8.0.0.374 (185) solution above works for me too.
jula182 said:
It is possible to force "4G only" without root. First download "Setting Database Editor" from playstore. Open it and look for "hw_networkmode_preferences". I use this value "9,3,2,1,11" on my phone. Save it and restart your phone.]
For me, It works. Huawei P10 Lite
Thanks
Click to expand...
Click to collapse
Worked on my Samsung Galaxy S9
Honor 6X is stubborn as heel... Nothing works.
Can't even find the commands... Sigh!
First Method :
1. Use SIM 1 as the default connection setting
2.
You need to install this app for FREE
at Google Play
https://play.google.com/store/apps/details?id=com.teknokia.force4glteonly
pro version : https://play.google.com/store/apps/details?id=com.teknokia.force4glteonlypro
galaxy store: https://apps.samsung.com/appquery/appDetail.as?appId=com.teknokia.force4glteonly
pro version : https://apps.samsung.com/appquery/appDetail.as?appId=com.teknokia.force4glteonlypro
3. Run the application, press the SIM 1 only or Android testing button. You will enter two LTE Switcher options and also 2 Android testing options.
4. You can try all of them which support your phone.
If the telecommunication operator you are using does not support VoLTE (Voice over LTE) and uses LTE Only Mode, so regular calls will be blocked.
Second Method :
1. DOWNLOAD Force 4G LTE Only 2020 Pro application from Google Play
2. Run the Application
3. Select SIM 1 Only menu, then Hidden Activity
4. wait to load until 100%
5. tap the search box type RadioInfo
6. In the DEvice Info app section, there is a RadioInfo activity.
7. Long Tap 3 options will appear: Create Shortcut, Launch Activity, Edit Shortcut. I recommend Select Create Shortcut to make it easier for us to enter network activity mode without having to bother opening the Force 4G LTE Only 2020 Pro application.
8. Please select Launch Activity to enter the Radio Info
9. Select LTE Only in set preferred network type
I was able to get it working on my huawei y7a sometime last year using settings database editor. Abouy 2 weeks ago i factory reset my device due to an unrelated issue and now when i try to enable it again i get an error saying my system software has rejected the edit. I tried with the version of setedit from f-droid and got the following "Unexpected failure you shouldn't not change private system settings." does anyone know what the problem could be?
K.Hatake said:
I was able to get it working on my huawei y7a sometime last year using settings database editor. Abouy 2 weeks ago i factory reset my device due to an unrelated issue and now when i try to enable it again i get an error saying my system software has rejected the edit. I tried with the version of setedit from f-droid and got the following "Unexpected failure you shouldn't not change private system settings." does anyone know what the problem could be?
Click to expand...
Click to collapse
I have the same issue with p30 pro. It seems to me that after some recent updates, they've locked those settings somehow.
alesu69 said:
I have the same issue with p30 pro. It seems to me that after some recent updates, they've locked those settings somehow.
Click to expand...
Click to collapse
did you find the solution for this problem because i have the same issue and i get the error message from setedit if you have the solution plz respond to me . thx
Make a shortcut to the activity .settings.radioInfo (phone info) of the app com.android.phone (telephone)
namous zakarya said:
did you find the solution for this problem because i have the same issue and i get the error message from setedit if you have the solution plz respond to me . thx
Click to expand...
Click to collapse
I found a solution. You would have to use "Adb shell" (usb debugging).
The code is:
adb shell settings put system hw_networkmode_preference 11
Techie0fficial said:
I found a solution. You would have to use "Adb shell" (usb debugging).
The code is:
adb shell settings put system hw_networkmode_preference 11
Click to expand...
Click to collapse
This worked for me. Thanks
Ownice K6/C960 Android Head Unit
Information on this unit seems to be extremely sparse but it's without a doubt the best unit I have used so far so I am putting this thread together to get a universal one stop shop for this unit in English. A lot of the information displayed here is from a Vietnamese forum called: Icar Vietnam so thanks to everyone there for the help.
Unit Specifications:
K6 Standard Version: RAM 2GB ROM 32GB | Standard TFT Display
K6 High Version: RAM 4GB ROM 64GB | IPS Display
9" or 10.1" display, single or double din
SC9853 1.8GHz 64-bit 14nm OctaCore Processor
Android 8.1
Radio IC: Standard TDA7786, High TDA7708
Amplifier IC: Standard TDA7388, High TDA7851L
Glonass & GPS
Optical Digital Output!!
Optional extras (remember to pay your supplier extra for this if you want it)
AV-out
Autoplay
High Version (RAM 4GB ROM 64GB IPS Display)
Features:
1. Support 4G LTE Network: surf internet freely by inserting a SIM card
2. 6-Channel DSP: Improve your car audio system to a high sound quality
3. Android 8.1 Oreo OS: use your favorite Apps smoothly with 2G RAM plus 32G ROM configuration
4. Octa Core Processor: Intel 64-bit 14nm Foundry Platform gives quick response and high performance
5. Support both GPS & Glonass
6. Support AHD Camera
7. Wireless Car Auto Play (Optional): support both Android Phone and iPhone.
FM/AM Radio: FM X 18 & AM X 12 preset stations with built-in RDS Radio Receiver function
GPS Navigation: Support both GPS & Glonass sat. nav., support iGo, Navitel, Tomtom, Sygic, Google online map etc
Bluetooth Function: support BT Hands-free, support A2DP bluetooth music play.
Multimedia Player: support audio/video file play, with 3xUSB port.
Mirror Link: Connect to your smart phone via USB or WIFI hotspot to mirror display contents on your phone
Internet Connect: Built-in 4G LTE Network & WiFi, support using SIM card directly.
Colorful Button Light: Can change the button light color freely to match your car's interior
Multi Android Applications: Support downloading, installing, and deleting multiple Android applications.
Useful Information:
Codes to enter into "Extra Settings" in "Settings"
Only working codes I have found so far are;
Extra Settings: 123456
Client Settings: 1260
Known issues/limitations and solutions:
None known as of yet
Firmware and Recovery:
Stock Firmware:
All firmware comes from the Icar Vietnam forum found here: https://xethongminh.net/threads/huong-dan-chay-firmware-cho-dau-android-ownice-c960.2940/
Please note the below firmware is for devices with a resolution of 1024x600, if your device is 1280x720 please check post 4 first here: https://forum.xda-developers.com/showpost.php?p=82347937&postcount=4
- 23rd December 2019
- 15th January 2020 ( Checksum Code: B26484F45B059A9C06032AD85D2A507F)
- 2nd March 2020 (Check Code Code: 68CD79A761AACE6E8375A9674C0DDA97)
- 13th March 2020
- 21st April 2020
- 21st July 2020 (exactly same as 21st April,only 2 files to fix bluetooth have changed)
How to install firmware:
Extract and copy all files from the downloaded firmware zip into the root directory of a USB stick. Files must be placed in the root directory, do not put in a sub-directory/folder at all. Files for a full firmware for the Ownice C960 include the following 10 files (depending on the rom there may be less or more than 10 files):
408930e4-c1fc-11e8-8a06-2b5b8f8a7e48
4192eb4c-c1fc- 11e8-8f83-a7a51df1443b
427c4ecc-c1fc-11e8-b558-cb289b80f7d2.0
427c4ecc-c1fc-11e8-b558-cb289b80f7d2.1
427c4ecc-c1fc-11e8-b558-cb289b80f7d2.2
427-bcbc-bcbc-
11c -c1fc-11e8-b558-cb289b80f7d2.4
43864958-c1fc-11e8-b9ce-0701f06faf8a
4671e21c-c1fc-11e8-ac0e-7bb4334d40c5
6cdfbbd8-9a00-11e7-8c64-33bdecde7c40
The Ownice C960 has several methods to install the different firmware depending on the situation and the current operating status of the head unit, for example, if the head unit is still bootable into the operating system, it is possible to use method 1 to install the firmware from the software of the head unit.
If the head suffers from being stuck at logos or other problems you need to move onto method 2 of installation using a recovery method. If both method 1 and method 2 do not work there is also a 3rd method but this is not listed here, please follow the instructions on this forum: https://xethongminh.net/threads/huong-dan-chay-firmware-cho-dau-android-ownice-c960.2940/
I. Method 1 (Rerun or upgrade the firmware of the C960 player via the installation interface)
Plug in the USB drive containing the firmware and go to Settings (Settings) - Car settings (Car Settings) - Update (Update System)
-If you need to wipe the system check the box to Clear data and format Flash, then check the box for USB
-If you want to flash without wiping check the box for USB only (if you have problems with this method try wiping first before moving onto another method)
Wait for the update process to complete the reboot is successful.
Installation Video: https://youtu.be/2JvAcrLPvRo
II. Method 2 (Rerun or upgrade the firmware for the C960 player when unit cannot boot)
This method is especially useful for those who root or unlucky and have system issues causing the head unit to be unable to boot into the system. There are 2 ways to do this method:
Option 1 (I have not been able to get this method to work, this is written exactly as translated from Vietnamese):
Trapping system errors, pressing into mode Update the firmware
Error traps are a simpler way to do the first way because you don't have to remove the head from the car to short the KEY-2 cable like the first way. How to do the following:
Proceed to plug the USB containing the firmware prepared in step 2 to the beginning.
Turn on the electric car to start the car, when the head has booted on the screen (including in the state of logo hanging), proceed to use the RST hole stick on the screen to restart the head, right when the head of the Ownice logo appears then immediately turn off the car keys to turn off the head. Wait for 5 to 10 seconds, then turn the car lock on again, this time, it will jump into the firmware update mode if it detects that the USB containing the firmware is plugged in.
Option 2: Short KEY2 cable to ground (the head unit cover or car chassis)
Connect a USB stick containing the firmware
Short/connect and hold the KEY2 wire to a suitable grounding point (holding to the metal chassis part of the head unit works fine)
Stick a pin or toothpick into the RST hole (RST stands for RESET) on the front of the monitor to reboot (while keeping the KEY2 wire grounded)
Wait until the screen turns on with text showing the firmware update process is in progress, at this point disconnect KEY2 from ground
Wait until the update process is completed, it will automatically restart and operate normally.
Decompiling Firmware:
Firmware files can be decompiled and edited however I'm not going to go into detail in how this is done as its very in depth and I am not 100% sure my methods work 100%, however for those that want to attempt this I do have a link for a tool that decrypt's encrypted files, you can download the tool here: https://www.androidfilehost.com/?fid=4349826312261776408
Unfortunately I do not know much about the tool or who to thank only that it's called Kaier Support Tool and its by Darkleo - Thank you dev's whoever you are!
Custom Firmware:
There is now a custom firmware available for our units. This firmware is called RedMOD
Website for RedMOD is here: https://firmware-an21.wixsite.com/redmod
RedMOD is an all in one replacement firmware for our units. It replaces the stock firmware to give us more options, features and settings. To know more please look at the website link above but note that everything is in Russian. I have been able to download and use this firmware using just Google Translate.
This firmware is not free! You must pay the developer for access to the download and you must not share this firmware! If you share this firmware your post will be reported!
Some of the features I have found useful so far in this new firmware:
Remapping Canbus Keys (Most keys can be remapped)
Better display dimming options (Auto Dimming)
More reverse camera settings (custom reverse lines etc)
Better automation settings for when the unit wakes up (choose apps to run at startup etc)
Customisation of status bar (Add or remove items like menu button, time, temperature etc)
Much much more
To get this firmware you must register on RedMod forum and then follow the instructions to download:
http://red-mod.ru/forum/viewforum.php?f=13&sid=e1d8a806c50a172dd889ccff62506225
The cost is 2000 Russian Rubles or 38 US Dollars. For me in the UK the exchange worked better to send Rubles and the cost was approximately £26. Once you send payment the admin will change your forum access so that you can access the download area. Make sure you register with the correct information and only get access to and download the firmware for "ANDROID 8.1 - Intel TS9" as this is our device.
I am not affiliated with RedMOD and cannot be held responsible for anything that may happen to your unit as a result of using this firmware.
Root:
All root files up to 15th January 2020 firmware come from the Icar Vietnam forum found here: https://xethongminh.net/threads/huong-dan-root-dau-android-ownice-c960.3115/
Root files after this date have been created by me
- August 28th 2019
- December 23rd 2019
- January 15th 2020
- March 2nd 2020
- March 13th 2020
- April 21st 2020 and July 21st 2020 (same file can be used, exactly the same for both firmwares)
How to Root:
First you must download firmware and root files that match.
Install firmware as described in the firmware section.
Extract and copy the files from the root zip file found above into the root directory of a USB stick and plug the USB into the head unit
Install MagiskManager.apk (the downloaded zip file includes this file) found on the USB stick using a file manager on the head unit
Go to Settings (Settings) - Car settings (Car Settings) - Update (Update System) (Do the same procedure as updating the firmware) and check the box for USB only
Wait for the update process to complete and the reboot is successful.
Open MagiskManager and check you are now rooted! (if you are not please rerun this procedure)
How to make your own Root file:
The root file is simply a boot image with Magisk. Nothing more nothing less. However the original boot image is encrypted so I will go through the steps of how to get the root file for each rom.
First download the tool here: https://www.androidfilehost.com/?fid=4349826312261776408
Unfortunately I do not know much about the tool or who to thank only that it's called Kaier Support Tool and its by Darkleo - Thank you dev's whoever you are!
Download the firmware you want to root
Extract "4192eb4c-c1fc-11e8-8f83-a7a51df1443b"
Open Kaier Support Tool
Select the "4192eb4c-c1fc-11e8-8f83-a7a51df1443b" file and click decrypt
The tool will ask you to save the file, save the file as "boot.img" and transfer it to a USB stick
Put the USB stick into your head unit and open up magisk (you must have magisk installed)
Click install on Magisk (not Magisk Manager) and when it asks click to "Select and Patch a file"
Patch the "boot.img" we put onto the USB stick
When done Magisk will save the patched file into the downloads folder
Move that patched file onto your USB stick and head back to the computer
Open up Kaier support tool, select the magisk patched file and click encrypt
When it asks to save call the file "4192eb4c-c1fc-11e8-8f83-a7a51df1443b"
"4192eb4c-c1fc-11e8-8f83-a7a51df1443b" is now your root file!
Follow the other instructions to flash firmware and flash root but just place this new "4192eb4c-c1fc-11e8-8f83-a7a51df1443b" on your USB stick instead
Change Startup Logo:
For instructions on how to change the startup logo please follow the video here: https://youtu.be/V9xC6A41q7Q
Important things to note:
You must place the image on the root of a USB stick, it will not work if it's in a directory, you may even have to reboot with the USB plugged in before the unit will find the file
The image MUST BE an 8bit BMP file with a size of 1024x600
DISCLAIMER - PLEASE READ:
All information in this thread is provided for information purposes only, all the information has either been worked out by myself or found on another forum and although I try to verify all information this is not always possible. I must point out that I cannot be held responsible for any negative effects that may or may not occur from using the information in this thread, all firmware is not supplied by me and the process of flashing is as described by the maker of the unit and I cannot be held responsible for failed flashes or bricked units.
Thank you, I was thinking of doing the same as you. Because I believe that the C960/K6 is one of the best android head units available today. As one C960 user, I will cooperate with this thread as much as possible.
warata said:
Thank you, I was thinking of doing the same as you. Because I believe that the C960/K6 is one of the best android head units available today. As one C960 user, I will cooperate with this thread as much as possible.
Click to expand...
Click to collapse
Good to see I'm not the only one with one of these units!
Really is a good unit, I am very impressed so far and had no issues at all
If you know of anything I should add to the op please let me know :good:
liamstears said:
Good to see I'm not the only one with one of these units!
Really is a good unit, I am very impressed so far and had no issues at all
If you know of anything I should add to the op please let me know :good:
Click to expand...
Click to collapse
Currently, I have two C960s with different resolutions, S1008W and S1010V, and they also have different firmware.
The resolution of S1008W is 1280x720, but if you update the firmware distributed by Ownice Vietnam here, the screen resolution will be broken like the attached image.
I can't speak Vietnamese, so when I contacted Ownice official support, they sent me a small file to fix the resolution issue.
This update file actually recovered my S1008W so please add it to the op, thanks.
Hello . Just installed the C960 on a Nissan Serena 2019 . For the moment i have 3 problems :
1 . I want the AV out to keep the movie running on the roof monitor when I switch the HU on navi.
2. Steering wheel controls not working ( i have canbus, i try to reprogram the buttons from settings) .
3. The original back camera is not working ( i have canbus)
warata said:
Currently, I have two C960s with different resolutions, S1008W and S1010V, and they also have different firmware.
The resolution of S1008W is 1280x720, but if you update the firmware distributed by Ownice Vietnam here, the screen resolution will be broken like the attached image.
I can't speak Vietnamese, so when I contacted Ownice official support, they sent me a small file to fix the resolution issue.
This update file actually recovered my S1008W so please add it to the op, thanks.
Click to expand...
Click to collapse
Thanks for this, I wasn't aware of the screen resolution differences but will update the op accrodingly
Before I do though can you clarify a couple of things
You say firmware is different on the 2 units? Completely different or same firmware just different file for resolution?
The attached zip, just place the "408930e4-c1fc-11e8-8a06-2b5b8f8a7e48" file on a root of a USB and update using system update option?
Can the "408930e4-c1fc-11e8-8a06-2b5b8f8a7e48" file be added to the USB stick containing a full rom to flash the whole system?
Thanks in advance
cosmabgd said:
Hello . Just installed the C960 on a Nissan Serena 2019 . For the moment i have 3 problems :
1 . I want the AV out to keep the movie running on the roof monitor when I switch the HU on navi.
2. Steering wheel controls not working ( i have canbus, i try to reprogram the buttons from settings) .
3. The original back camera is not working ( i have canbus)
Click to expand...
Click to collapse
Welcome to the thread
I will try to help but information on this unit is limited and I don't have all the answers
1. Do you currently have AV out working and paid for the AV out upgrade? I don't personally use the AV out option so cannot really comment on how exactly this should work but in theory I would have thought what you are trying to do should work
2. No issues with steering wheel controls here, being canbus they are not programmable as far as I am aware at the moment, do you have the correct canbus adapter box plugged in and the correct settings set for your vehicle in car settings?
3. If the original camera works through canbus I can only assume it will not work at all. Backup/reverse camera has to plug into the RCA input on the back of the head unit
I hope this is helpful
liamstears said:
Thanks for this, I wasn't aware of the screen resolution differences but will update the op accrodingly
Before I do though can you clarify a couple of things
You say firmware is different on the 2 units? Completely different or same firmware just different file for resolution?
The attached zip, just place the "408930e4-c1fc-11e8-8a06-2b5b8f8a7e48" file on a root of a USB and update using system update option?
Can the "408930e4-c1fc-11e8-8a06-2b5b8f8a7e48" file be added to the USB stick containing a full rom to flash the whole system?
Thanks in advance
Click to expand...
Click to collapse
Just unzip it to a USB memory and run the system update. The update time is a few seconds.
In addition to the resolution, the S1008W has another difference: it has a built-in 3-axis sensor and has a vertical screen UI.
However, updating the firmware for 1024x600 systems also loses this functionality, thanks.
liamstears said:
Welcome to the thread
I will try to help but information on this unit is limited and I don't have all the answers
1. Do you currently have AV out working and paid for the AV out upgrade? I don't personally use the AV out option so cannot really comment on how exactly this should work but in theory I would have thought what you are trying to do should work
2. No issues with steering wheel controls here, being canbus they are not programmable as far as I am aware at the moment, do you have the correct canbus adapter box plugged in and the correct settings set for your vehicle in car settings?
3. If the original camera works through canbus I can only assume it will not work at all. Backup/reverse camera has to plug into the RCA input on the back of the head unit
I hope this is helpful
Click to expand...
Click to collapse
1. Yes I paid for AV out and is working, but is mirroring everything from HU , maybe is something in settings. When I will find out I will tell you.
2. The steering button are not a big deal , but I wished the volume button to work . Can you tell me if you make the connection to steering buttons with wires or you have the connection in the harness of the HU ?
3. I think the problem is the original camera of the car . I read on some forum that I need to take the signal from another place because the car have aroundviewmonitor ( 4 camera) , parking assistance and propilot ( self driving option) . I will update the results when i have time to teardown the car again .
V11.1.1_20200421 has been released in i-car Vietnam.
And I installed magisk by the procedure introduced in this thread, but I can't install youtube vanced.
The installation completes successfully and the folder is created, but the contents are empty.
Please let me know if I'm missing something.
cosmabgd said:
1. Yes I paid for AV out and is working, but is mirroring everything from HU , maybe is something in settings. When I will find out I will tell you.
2. The steering button are not a big deal , but I wished the volume button to work . Can you tell me if you make the connection to steering buttons with wires or you have the connection in the harness of the HU ?
3. I think the problem is the original camera of the car . I read on some forum that I need to take the signal from another place because the car have aroundviewmonitor ( 4 camera) , parking assistance and propilot ( self driving option) . I will update the results when i have time to teardown the car again .
Click to expand...
Click to collapse
1. I have spoken to Ownice and AV out can only mirror I'm afraid
2. I have a canbus decoder for my unit, it works well
3. Yes if you have that sort of system it needs rewiring, I cannot help with that I'm afraid
warata said:
V11.1.1_20200421 has been released in i-car Vietnam.
And I installed magisk by the procedure introduced in this thread, but I can't install youtube vanced.
The installation completes successfully and the folder is created, but the contents are empty.
Please let me know if I'm missing something.
Click to expand...
Click to collapse
Haven't tried youtube vanced myself yet on this unit but I can see you are trying to install it as a system app, have you tried just to install as a normal app and not a system app?
Op updated with latest April firmware and root file
cosmabgd said:
1. Yes I paid for AV out and is working, but is mirroring everything from HU , maybe is something in settings. When I will find out I will tell you.
2. The steering button are not a big deal , but I wished the volume button to work . Can you tell me if you make the connection to steering buttons with wires or you have the connection in the harness of the HU ?
3. I think the problem is the original camera of the car . I read on some forum that I need to take the signal from another place because the car have aroundviewmonitor ( 4 camera) , parking assistance and propilot ( self driving option) . I will update the results when i have time to teardown the car again .
Click to expand...
Click to collapse
Which car, which model and year do you using ?
ngochoangimsat said:
Which car, which model and year do you using ?
Click to expand...
Click to collapse
Nissan Serena S-Hybrid 2019 Japanese edition
I hope you guys can help me
In my car my aircon shows "HI" and "LO" temperature settings, when changing temperature it goes up and down in 0.5C steps showing "LO" instead of 15.5C and "HI" instead of 28.5C
However the headunit doesn't show HI or LO and just shows the temperature
I am trying to modify the APK to fix this but need your help, what I need to know is:
Does your unit show HI and LO values? If it does what temperature does it set them to HI and LO respectively? What increments does your heating change, is it 0.5C like mine? Do you have 2 separate temperatures for left and right side of vehicle or just 1 temperature settings for whole vehicle?
Sorry to move through your question, but when you linked to your own thread also mentioning the k_support tool, I realised I had seen it "somewhere" before. It was of course on 4pda.
that was some years ago when I wanted to discover everything related to Joying and other helpful stuff.
hi all, my unit is a TS9 unit and I'm looking for root... can we cooperate?
huh, anyone?
Glad to see this thread, I have the same unit on my Kuga 2015.
Anyone know what is the difference between BC6 and BC8 ? And what type of DVD I need to attach to the HU ? I have right now a Lite-on DvD .
What's the difference between the c960 k6 and the s9285 k6 if any, I'm looking to fit one of these in a 2009 ford fiesta
Sent from my SM-A920F using Tapatalk