Related
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!
Projectivy Launcher (formerly ProjecTivy Tools) now has its own dedicated thread located here.
Intro
There's so much information here that a new user could probably feel lost without the courage to read everything. So let's keep things simple : as the thread's title says, the primary aimed devices are projectors produced by Xiaomi related brands (xiaomi/fengmi/wemax), though it could probably be useful to other Android Tv models and other brands, so you might want to keep reading until the end of the introduction.
What you can find here :
Full tutorial to Googlize your chinese device with my custom made Google Apps package dedicated to Android Tv 6 (only tested on MiUi Tv, root required)
General FAQ related to these devices [post #2]
Information on how to root xiaomi/wemax/fengmi/vava projectors (and custom made TWRP for many chinese models) [post #2]
Full firmware and OTA for many models [post #2]
Google Apps / Services instructions
Here's a full tutorial to root and install Google services on your Android 6 MiUi device (ie: chinese xiaomi/fengmi/wemax).
This has been tested successfully on all devices where a custom TWRP is available below. If anything goes wrong for you, try to factory reset / clean flash
Except for "AndroidMediaShell" (Google Cast server), most (all?) features are working fine including :
Tv settings
Google Play (to let it install/update apps, please enable the Accessibility Service)
ATV remote service : if you install Google ATV remote on your smartphone, everything (including speech recognition) will work
Google Assistant : with the Accessibility Service enabled, a short press on the mic button on your stock remote control will launch Google Assistant. Then, when it's listening, press and hold the mic button while speaking and release it when done. According you've used More Locale to change to your mother tongue, this will even work in your language.
Installation steps:
root your device (see post #2) (you don't need to flash any firmware)
if not already done, install the latest version of ProjecTivy Launcher and launch it
execute Applications / install 3rd party apps, then install :
Aptoide Tv Store
ATV launcher [optional] (alternative launcher)
Youtube [optional]
MoreLocale [optional] (in case your mother tongue is not english, it will let you choose more than what's listed in Android settings)
Google Apps/services (don't forget it )
execute Applications / Freeze Stock launcher (to disable your stock home screen)
execute Applications / Freeze Stock apps (to disable most Xiaomi apps and services)
execute System / Custom Props override (to pass safetynet checks, enable more stock behavior and fix black screen with non-stock launcher)
execute System / Accessibility Service, enable the service in accessibility settings (to fix "Google Play" ability to install/update apps and to link the stock remote control "Voice recognition" button to Google Assistant as well as many other features)
[Optional] Install magisk module "Nexus Media" to change the stock bootanimation (go to Shortcuts / Magisk Manager to execute it, and then in the left menu, "Downloads" section, just install "Nexus Media")
Reboot and complete the Welcome app to setup your Google account (first and second boot will be longer than usual)
Note that an Android accessibility setting might get enabled after the first reboot when Google Apps have been installed. It'll cause green borders around buttons. Just go to settings / accessibility and disable "talkback".
Launch Google Play to update Google apps and let the update finish before exiting Google Play (if the app's accessibility service is running as it should, it will display a message when launching/exiting Google Play)
[Optional] start MoreLocale to change your language
Disable the "smart update" in the projector settings so that it doesn't try to download and install OTAs (which would just display an "error" message after each boot, when it fails to install it)
Enjoy your Google Tv device !
Important :
Once installed, don't change the device resolution in the Android Tv settings. This is not supported by the video drivers that will then only display a checkerboard. The only known solution as of now is to factory reset and start again.
Engineering Menu App Translation
Here you'll find information about xiaomi's engineering menu app.
After a bit of google translate and reverse engineering, here's a translation of the different menus, along with my own values (1st one is for "rainman", second one for "batman")
Projector information
- Brightness [1541][1610]
- DLP vendor name [APPO][APPO]
- Production Week [1812][1921]
- Contrast ratio [3828][3370]
- Brightness Uniformity [940][856]
- Serial Number
- Color coordinates [r:860 g:860 b:860 x:283 y:302][r:860 g:860 b:860 x:2720 y:2790]
Solid color (android) -> displays a solid color (using android system)
Solid color (projector) -> displays a solid color (native)
Other image test (android) -> displays a gradient (using android system)
Other image test (projector) -> displays a gradient (native)
Color wheel delay -> when incorrectly set, this can lead to posterization issues (gradients become unnatural and tend to display large uniform areas) [490][420]
Save color wheel delay to Android
Image mode: change the screen light intensity
- Standard
- Highlight
- Energy saving
Temperature monitoring
- ambient temperature [31][43]
- color wheel [52][63]
- Laser temperature channel 1 [60][74]
- Laser temperature channel 2 [61][74]
- DMD temperature [-][0]
Model name [MiProjA1][MiProjLAS2]
Human body induction -> enables/disables IR sensor that disable image when coming close to the laser
Save information to projector
DLP version [major:1, minor:2, patch:5][major:7, minor:3, patch:7]
3D (when modified, need to restart to take effect) -> enable/disable 3d support
Devices list
For reference, here's a list of devices where ProjecTivy (and several of its special features) has been tested working fine.
Only models using Android 6 can be rooted yet.
1080p Laser Projectors:
Xiaomi Mi Laser UST Projector 150" (chinese) / MiProjA1 / model: MJJGYY01FM / codename: rainman
Wemax One 7000 / MiProjA1 / model: FMWS01C / codename: rainman (thanks rockpaperscissors)
Wemax One Pro / MiProjA1 / model: FMWS02C / codename: rainman
Xiaomi Mi laser UST Projector 150" (international) / MiProjA1 / model: MJJGYY02FM / codename: anglee (thanks Nathan0121) (no root supported yet)
Xiaomi Mijia ALPD 3.0 (rear throw laser) / model: L185JCN / codename: franky (no feedback concerning twrp yet, try rainman and report if it works)
4k Laser Projectors:
Xiaomi Mi Laser UST Projector 150" 4k (chinese) / MiProjLas2 / model: MJJGTYDS01FM / codename: batman
Xiaomi Mijia 1S 4k (chinese) / MiProjLas2 / model: MJJGTYDS04FM/ codename: batman
Wemax A300 / MiProjLas2 / model: L1668FCF / codename: batman
Fengmi 4K cinema laser / MiProjLas2 / model: L176FCN / codename: batman
probably not released yet / MiProjLas2 / model: L246 / codename: batman
Fengmi 4K cinema pro laser / FMProjA2 / model: L176FCNPro / codename: jerry (no root supported yet)
Fengmi 4K C2 (cinema 2) / ? / model: L166FCN / codename: jerry (no root supported yet)
Fengmi 4k Max / model: L406FCN / codename: jerry (no root supported yet)
Xiaomi Mi 4K laser UST Projector 150" (international) / model: XMJGTYDS01FM / codename: angleeUHD (no root supported yet)
Led projectors:
Xiaomi Mi Home Projector Lite / Mijia DLP Projector Youth edition / MiProjLED1 / model: MJJGTYDS02FM / codename: conan (root using rainman twrp below)
Mi Smart Compact Projector (international) / Mijia DLP Projector Youth Global edition / model: M055MGN / MiProjM05 / SJL4014GL / codename: ?
Fengmi M055FCN / model: M055FCN / MiProjLED1 / codename: doraemon (root using rainman twrp below)
Xiaomi Mijia Mi / ZMiProj / model: TYY01ZM / codename: zodiac
Tvs:
Xiaomi Mi TV 3s / codename: mission impossible
Xiaomi Mi TV 4 / codename: pulpfiction
Xiaomi Mi TV 4a/4c/4s/4x / codename: matrix/xmen
to be completed
More in post #2 below
FAQ and more resources related to these devices
Differences between projector devices
Wemax One / Chinese Xiaomi Mi Laser:
They are (almost ?) the same.
Software-wise :
They are exactly the same (exaclty same codename, firmware, etc...)
Hardware-wise :
Wemax is black, Xiaomi Mi is white
Wemax is described to be 7000 lumens (1688 ansi lumens), Xiaomi mi 5000 lumens (1600 ansi lumens) (not sure if hardware is different or it's only a software parameter that changes its laser power)
Chinese Xiaomi Mi Laser/ International Xiaomi Mi Laser:
Software-wise :
Chinese one comes with android 6.0.1 and MiUI Tv (a Xiaomi UI dedicated to chinese users), International one comes with android 8.1 (more details below)
Hardware-wise :
Chinese one is equipped with DDR3 ram, International version DDR4
Chinese one has Amlogic T968 with onboard Mali T830 gpu, International one has Amlogic T962 with onboard Mali 450 gpu (somewhat less powerful, not sure it has any real world impact)
Also note than more often than not, International version will probably come with a warranty. It might be important, as few people complaining about dead white pixels seem to have a hard time getting their chinese projector repaired.
Pros/Cons of 8.1 international device / firmware (as of 10/10/2018)
This might help people choose between 02 international version and 01/wemax devices. Most of the information below come from this test. This is however subject to change as I believe Xiaomi will probably enhance their drivers in the coming monthes.
Pros
Complete software translations (no more chinese ressources)
Better user interface
Google Play Store availability
Better support of media apps that hardly work on 6.01 (Netflix, Prime Video...)
Better default colorimetry (but less configurable)
Less input lag (75,6 ms vs 126,6 ms) fixed on 1218+ firmwares
Cons
No 3d support
Less options related to display settings (missing RGB levels)
Worse image quality as noise reduction and sharpness seem to be less effective than on the 01 version
Judder and image tearing during media playback
Can devices international firmware be flashed on chinese models
No :
- devices hardware is not exactly the same
- partition layout is different (android 8.x requires a vendor partition)
- we don't have access to any international firmware
Supported video modes
EDID data here for "rainman" (1080p version) : View attachment edid-rainman-report.txt
EDID data here for "batman" (2160p version) : View attachment edid-batman-report.txt
EDID data here for "jerry" (2160p version) : View attachment edid-jerry-report.txt
EDID data extracted with HDMI 2.0 enabled from /sys/devices/hdmirx.28/hdmirx/hdmirx0/edid and analyzed with Advantiv EDID Editor 1.01.0268
Is my 4K device really displaying in 2160p ? Why does YouTube refuse to stream 4k ?
- Yes.
- Blame it on Google. Or AmLogic.
More details here.
Note : more recent devices such as Fengmi Cinema 4k pro (codename Jerry) based on Amlogic T972 soc don't have this limitation (they support VP9 hardware accelerated decoding)(but seem to lack 3D support)
ALR Screens
Interesting post from @servo386 regarding Ambient Light Rejection screens dedicated to UST devices.
Rainbow effect
I see many questions regarding rainbow effect (due to the DLP technology used). What I can say is that I never saw anybody complaining about it on the Mi laser projectors. A previous projector I owned (an Optoma) was also using DLP technology and I could see this rainbow effect from time to time. In the case of rainman/batman, I've never been able to see it.
Input lag
The Mi laser projectors have relatively high input lag (150/175 ms). Firmware updates sometimes help. As of september 2019, the lowest input lag can be obtained on "Monitor" or "Game" mode (approximately 100ms on batman, 75ms on rainman). If your device is rooted and you're using the ProjecTivy Tools, you can also use the "User" mode, and long press the "back" button to get down to the same input lag as "Monitor" mode, with the benefits of keeping your calibration settings.
Dead/black/white pixels
One owner of the chinese version here (french) who had a dead pixel managed to fix it by increasing RGB custom settings above 1500 for some time (don't know how long). When reverting to previous values, the white pixel had disappeared. Didn't work out for another user, but it might be worth a try.
This might change in the future (in this case, please keep me informed), but trying to manually repair by changing the chip is a dead end. It's not the usual Texas Instrument DLP4710FQL, but the DLP4711FQL (source), which is not compatible(source) and can't be bought online.
Display issues with MJJGTYDS01FM (Xiaomi branded 4k model)
Many display issues can affect this device : taking time (minutes) to start displaying something, displaying only half image or white lines/bands... Most issues appear when the device is cold and get fixed when it has heat up.
Seems like a hardware design issue that can be fixed by removing a few screws. More information here. After this, like your projector, you won't be screwed anymore
More details can be found here as well.
HDMI input ports don't work anymore in International devices after upgrade
Install the tools, launch engineering menu and select "HDCP key reset" (thanks @xthing)
Cross platform Remote Control
I also developped a simple web based remote control for MiUI TV (Xiaomi with chinese interface) based android devices (such as projectors, boxes, TVs).
No need to install anything special on your controlled device, this website/webapp communicates with the MiUI TV internal web server to send events to your device.
It should be compatible with anything running a web browser (provided it's quite up to date): Android, iPhone/iPad, PC/Mac computers...
Just head to http://mireco.hopto.org, configure your device local IP address and you're good to go.
More details on GitHub.
Other Tools
MiiInfo from 4PDA user Loly, shows various details concerning your projector.
Firmware updates after rooting and/or installing Google Apps
Firmware updates won't install if files on your system or kernel partition are modified. Using the ProjecTivy Tools and installing the Google apps won't modify existing system files, but rooting with magisk will modify the kernel. So before any update, you have to restore your kernel (aka "boot") partition using TWRP, and then reapply Magisk once update is done.
Google Apps Issues / not yet working
Amazon Prime video : it's been reported that Amazon purposefully blocks the app on projectors. The app loads, but refuses to stream videos. Some previous versions (requiring mouse for some features) work fine though. You can install the most recent compatible one using the ProjecTivy Tools.
Netflix : No recent Tv version seems to work. Some previous versions (requiring mouse for some features) work fine though. You can install the most recent compatible one using the ProjecTivy Tools. Anyway, due to missing full widevine support, full hd / 4k will probably never work.
Chromecast framework (Google Cast Server, aka AndroidMediaShell) isn't supported (devices need to be approved by Google to be supported)
Recovery
To go into recovery, turn off your projector, unplug it, hold down OK and BACK buttons simultaneously (OK and HOME for anglee) on your remote and plug back your projector while still holding them down.
Warning : don't "hot-unplug" it, turn it off before, or it won't work.
If you're looking for TWRP, have a look a few points below
Unroot
Start the Magisk Manager app and select uninstall
OR
Boot Twrp and reflash the Boot (kernel) backup you made just before installing Magisk
Factory Reset
Reflash the full stock firmware available below in this post. This doesn't require any intervention on your part so it should work even if you can't see the display
OR
Boot the stock recovery and select the "reset device" (not sure of the exact terms) option
Root
Note : both methods below work for rainman as well as batman (4k) devices.
Easy Method:
This method doesn't require any special hardware, only the TWRP I made (3.2.2.0, based on stock recovery files), along with another config file.
Thanks to @cr4zyw3ld3r who made a video tutorial based on the following instructions.
For french people, here you can find a tutorial made by Pierre. Thanks to him.
Extract this file View attachment batman_twrp_3.2.2.0b.zip (for "batman" 4k), this file View attachment zodiac_twrp_3.2.2.0.zip (for "zodiac"), or this file View attachment rainman_twrp_3.2.2.0.zip (for "rainman" 1080p and most other devices such as conan) at the root of your (FAT32 formatted) USB drive, where you also place the latest magisk version (magisk 20+ version support has been added on tools v3.5+), and plug it into your projector (I used the right USB port)
I also built (but not tested) a twrp for Vava projectors here : View attachment vava_twrp_3.2.2.0b.zip (please report if it works).
Download ADB for your computer (check here)
Start command line (terminal)
Enable USB debugging in Android settings / developer options (you can access them from the projectivy tools)
Type "adb connect IP_OF_YOUR_DEVICE:5555" to connect through the network
Type "adb reboot update" (This will restart your device and make it boot the TWRP on the USB drive.)
Once in TWRP a mouse will be required. Make backups if you wish (at least "boot" partition that you'll need to restore before applying any OTA update), and then mount SYSTEM, and install magisk in order to root the device (it will be in "/udisk" and will be called Magisk-......zip)
Note : to thank the donors, I also developed an application that installs on your Android smartphone, which automates steps 1 to 6. There is no need for computer or custom command lines in this case. Once the app is connected to your projector, you're only one button click away from TWRP.
Note : if it still boots to stock recovery and not twrp, make sure you extracted the zip and not only copied it to your usb drive. If it's extracted correctly but still doesn't work, try another usb drive, a few people reported that this fixed their issue (some users had to try 3 or 4 usb devices before finding one the works).
Old Method:
With the correct hardware, you can root your device, following this tutorial from @servo386
To simplifiy the rooting process described in the link above :
Extract this file View attachment twrp-files.zip at the root of your USB drive, where you also place the latest magisk version (as of now 19.3), and plug it into your projector
Follow the steps described in the tutorial, up to the point where you have a root console access in recovery
Then, according you've plugged your USB drive before starting your device, just type ". /udisk/twrp.sh" in the root console. This will copy the necessary files and automatically run twrp, reducing the number of steps (and potential mistakes) to root your device.
Once in TWRP, make backups if you wish, and then mount SYSTEM, and install magisk in order to root the device (it will be in "/udisk" and will be called Magisk-.....zip)
Roms / Dumps
Due to issues on the new XDA 2021 website (preventing edition of long posts containing many links), full firmwares and OTA have been (temporarily ?) moved to post #4.
You'll have to scroll down by yourself, I can't even add a link to it
Spocky great work this looks fantastic,
you highlighted that you're not yet rooted and I've tried a few things so far that haven't worked however a few days ago one of the guys on the XDA forums has managed to access command line probably using the jtag points on the board. It's quite likely but this is a good way to get a ADB and then root access, and therefore if uses nandroid type tools he should be able to complete a full dump of the ROM.
I have a Chinese projector with same firmware as your own, but I'm hoping we can load the Android TV launcher interface as in the international version.
Let me know if you need anything specific tested.
Roms / Dumps
Warning: Full roms below can help you recover your device if you're stuck with a non functional projector. However, if your device shipped with a more recent firmware than the one you're trying to flash and has a more recent hardware revision, you might have display issues. So before flashing a full firmware, please try to boot to recovery and use the "wipe all data" option. On MiTv devices, this will basically do the same thing (this will automatically flash the device with the stock shipped firmware, which is present on the /backup partition).
MJJGYY01FM / FMWS01C / FMWS02C (Chinese Xiaomi Mi Projector / Wemax One) [rainman]
Full rom 1.3.63 (6.0.1.935) (thanks to @servo386 and rockpaperscissors)
OTA [user] from 6.0.1.935 to 6.0.1.1074 (1.3.63 to 1.3.74)
OTA [user] from 6.0.1.935 to 6.0.1.1218 (1.3.63 to 1.3.97)
OTA [user] from 6.0.1.935 to 6.0.1.1289 (1.3.63 to 1.3.105)
OTA [user] from 6.0.1.1074 to 6.0.1.1218 (1.3.74 to 1.3.97)
OTA [user] from 6.0.1.1218 to 6.0.1.1289 (1.3.97 to 1.3.105)
OTA [user] from 6.0.1.1289 to 6.0.1.1425 (1.3.105 to 1.3.105)
OTA [user] from 6.0.1.1289 to 6.0.1.1453 (1.3.105 to 1.3.105) (Latest Stable)
MJJGTYDS01FM / L1668FCF / L176FCN / L246 (4k Chinese Xiaomi/Mijia Mi Projector / Wemax A300 / Fengmi Cinema 4k) [batman]
Full rom 1.3.97 (6.0.1.312) ONLY FOR MIJIA
Full rom 1.3.105 (6.0.1.494) Owners of recent fengmi devices, use the rom below
Full rom 1.3.105 (6.0.1.669) Should be working on most recent Fengmi Cinema 4k, with hardware version l176_1. If yours is fm_10, it probably won't work (I still need a /dev/block/backup image of fm_10 hardware version)
Full rom 1.3.105 (6.0.1.724) Extracted from a recent Mijia 1S. Should probably work on most batman devices (people with fengmi 4k fm_10 stuck on a black screen, give it a try)
OTA [user] from 6.0.1.312 to 6.0.1.494 (1.3.97 to 1.3.105)
OTA [user] from 6.0.1.494 to 6.0.1.624 (1.3.105 to 1.3.105) (ONLY FOR MIJIA)
OTA [user] from 6.0.1.494 to 6.0.1.793 (1.3.105 to 1.3.105) (Latest Stable)
MJJGYY02FM (International Xiaomi Mi Projector) [anglee]
Full rom 8.1.0.1317 (OPM8.190205.001.1317)
Full rom 9.0.0.1911 (PQ3B.190705.003.1911)
L176FCNPro / L166FCN / L406FCN (Fengmi 4K cinema pro, 4k Max, C2) [jerry]
Full rom 1.2.1.1689 (only for Cinema Pro, more recent device should use the next one)
Full rom 1.4.6.2378 (use this one for Fengmi C2 and Max 4k. Cinema Pro should work fine too)
MJJGTYDS02FM (Mijia Projector Youth edition) [conan]
Full rom 1.3.97 (6.0.1.304)
Full rom 1.3.123 (6.0.1.519) (Prefer this version as it's probably compatible with most recent devices too)
TYY01ZM (Xiaomi Mijia Mi) [zodiac]
Full rom 1.3.67 (6.0.1.391)
M055FCN (Fengmi M055FCN) [doraemon]
Full rom 1.3.123 (6.0.1.309)
L206FCN-X2 (Fengmi Formovie T1) [nemo]
OTA [user] from 2.0.0.2289 to 3.0.0.3049 (Not final, but stable)
How to flash :
[OTA only] be sure your current firmware version is the same as the "from" version specified above.
Download and extract the zip file to the root of a USB thumb device and follow the procedure to boot into recovery mode. The full firmware or OTA update will be automatically installed (approximately 5 minutes will be necessary). You shouldn't lose any data (well, unless there's a power cut during the update process ). Even after flashing the full firmware, I still had my apps installed. I suppose you need to factory reset if you want a clean install.
Those willing to reinstall from scratch will need to use the "wipe all data" from the recovery menu. If you can't acces it somehow, you can try flashing a full rom (935 for rainman, 312 for batman *mijia* or 494 for batman *fengmi/wemax*), and then flash to the latest available OTA (you might need to chain flash if no direct OTA is available from you stock full rom to the rom you're targeting).
Please note that for a few users, the OTA won't install (it will stop during the update process with a chinese message). It's due to the fact that during installation, a check on the system files and kernel is made and at least one could not pass. This will be the case if you have rooted your device (only kernel is modified then). In that case, if you want to apply the update, you'll need to revert to an unmodified kernel/system. If you didn't modify system partition, restoring kernel partition (boot.img) should be enough (or uninstall Magisk from magisk manager app). If not, try restoring system.img also. If nothing works, reinstall from scratch (see just above)
wemax 7000
Great job !
I will try it tomorrow on my wemax 7000.
Let me know how I can help.
Should I also make a dump of my Chinese rom ?
How did you dump yours ?
I also badly hope to get the android tv rom working with the play store.
Thanks a lot !
Getting a wemax dump would be great indeed !
I did it with adb, connected wirelessly to my computer.
To do the same :
- download adb for your system
- connect wirelessly by using "adb connect IP.OF.YOUR.WEMAX"
- create a folder for the dump on your computer : "mkdir dump"
- go in it : "cd dump"
- pull system files : "adb pull /system"
Then every file that doesn't require root access will be downloaded to your computer. Just make a zip of it and upload it somewhere.
If it feels too complex for you, wait for a few days, I'll probably upload a tool to make an archive and automatically upload it somewhere. I just need to fix a few things before.
Hello, I'm the one who got root via the HDMI->UART diagnostic bridge. All credit goes to @loly though on 4PDA, who is the person who actually figured out this process on his Xiaomi Mi TV 4A, which has a similar chip to this projector so I took a guess that it would work too.
The posts I made on AVSforum are pretty long and lots of pictures and formatting so for now im just gonna link it but hopefully I can easily copy over the posts and make them here too.
https://www.avforums.com/threads/xi...aser-projector.2142037/page-101#post-26580089
Hi,
I installed the app and got a Chinese popup telling me that what I was doing was forbidden to users.
The menu is in Chinese too and I tried translating it with google translate but It's very tedious and I'm not very confident going through the menus.
Thanks a lot for the procedure for the backup.
I will cleanup all the installed apps and maybe reset it completely so that i can share the backup online.
If you're going to prepare a tool to do so, I will wait so I can test it as well.
Let me know if I can help you by sending you more infos.
Cheers
Jerome
Xiaomi Mi Laser Root Procedure
This is a long one. Also it was originally written for an audience who may have not been as familiar with Android/Linux commands so it has lots of explanation that might feel out of place on XDA.
So first and foremost ALL CREDIT BELONGS TO @loly ON THE 4PDA.RU FORUM WHO ACTUALLY DISCOVERED THIS PROCESS
https://4pda.ru/forum/index.php?showtopic=810785&st=3260#entry75802829
I definitely am just a copy cat who guessed that his process would also work on this device since their both Xiaomi TV devices with Amlogic T96* boards.
So if you read his post (which you definitely should in addition to this post in order to get the full picture of how this is done), you'll see that this is quite complicated and a kind of high level hack. I hope I'll be able to explain it enough and walk through it enough for it be fairly accessible for less technically inclined people who want to root their Xiaomi projectors.
What is required:
1. HDMI cable you can chop up or an HDMI breakout cable like this one: https://www.amazon.com/Adapter-signals-Terminal-Breakout-Connector/dp/B01CU9SHOO/
2. UART to USB adapter cable/board like this one: https://www.amazon.com/Adapter-Serial-Converter-Development-Projects/dp/B075N82CDL though there are cheaper options available
3. Cables/wires to connect both things. The USB UART package above comes with some, though you'll have to strip the ends to screw them into the terminals of the HDMI breakout board.
4. A spare USB drive
5. A computer to use the USB to UART adapter and a terminal program, i am using Putty.
So the basic idea behind this is that one of the HDMI ports (HDMI 1 in this case, the one closest to the edge) also serves as a diagnostic/UART port via 3 of the 19 pins of the HDMI. When this HDMI port is properly wired to the UART adapter, and you have a terminal open observing said port, upon boot the machine reads out all its startup stuff and when booting into recovery, gives you a completely liberated UNIX terminal that accepts input from the UART terminal, with full root privileges and busybox! As @loly says in his post, here we thank the people at Xiaomi for not bothering to secure this section and giving us full diagnostic root access with busybox. This is almost surely the way the developers of this machine would interact with this machine and developed for it. So let me try to explain how this works and how we get to TWRP and root.
Steps:
1. We need to properly connect the correct pins on the HDMI cable to the correct pins on the UART.
Here I am going to re-post some of @loly's images from the original thread, so all credit goes to him.
Here we see the pins we need. Pin 14 is our VCC, which in this 5v (the UART adapter im using has a switch for 3.3v or 5v, this switch needs to be set to 5v!) Pin 15 is the receive pin and Pin 16 is the transmit pin
The fourth lead we need is the GND (ground), which in the case of an HDMI cable is usually an un-shielded wire that connects to the the case of the connector itself.
I'm going to stop here for a sec and say this is why it's alot easier to use the HDMI breakout board over trying strip an HDMI cable and finding which wire corresponds to which pin (you need a multi-meter to do that)
its a small investment but it makes everything ALOT easier. On the HDMI breakout board, the ground terminal is pin 20.
the corresponding pins on the UART are pretty straightforward. VCC goes to VCC on the UART, pretty straightforward, on the other hand the RX pin of the HDMI (pin 15) goes on the TX OF THE UART makes sense right? the receiever of the HDMI should be listening to the transmitter of the UART and vice versa, so the TX pin of the HDMI goes on the RX pin of the UART. The GND pin (pin 20 on breakout board) goes to the GND on the UART.
Here's my setup. Sorry for the not very great picture. The terminal blocks on the HDMI breakout board work basically like you were connecting speakers to an amp, you unscrew the terminal till you see a little metal hole and you stick the stripped tip of the cable into the hole and screw the terminal back up till its snuggly holding onto the cable. You can use a multi-meter if you have one to make sure the wire is making contact with the terminal and even test the exact pin with the cable to make sure the connection goes all the way. If you're cable is making contact with the metal of the terminal, it is almost certainly correctly making contact with the actual HDMI pin, barring maybe a badly manufactured breakout board. I used spare MALE end pin connector cables to strip the ends and stick in the terminals, and connected them to the FEMALE connectors that came with the UART adapter. You don't necessarily have to do it this way, you can directly strip one of the female ends of the cable and connect the other female end to the pins on the UART, but you'll have a pretty short cable from HDMI to USB and you'll probably need a USB extension to comfortably use it with a computer.
So now you have you're HDMI diagnostic cable!
2. Setup your computer for UART and Putty.
Connect your UART to USB adapter to your computer. In Windows 10, it should automatically install drivers, but if it doesn't, your device should come with a link or something to download the drivers. I'm not going to get into the specific of how to install drivers on Windows computers but needless to say, you need to get the computer to recognize the device and properly utilize it via the drivers. Once you have it properly installed on the machine, it should show up in your device manager under Ports (COM & LPT) or something similar.
this is important because we need to 1. determine what COM port you're device is on and 2. change the baud setting.
So in the photo you see that it tells you what COM port is, which we need for later.
Now you need to go into the settings of the device and go into Port Settings tab
WE NEED TO SET THE BITS PER SECOND TO 115200!
Very important!
Setting up putty:
Basically open up putty and put the button on Serial, set the speed to 115200 and in the SERIAL LINE put the correct COM port number (COM1, COM2, COM3, ect)
Pressing enter on this should open a big blank black terminal with no activity. Thats good because its working. If it wasn't, you'd get an error about not reaching COM port or something.
3. Testing out our diagnostic cable with UART and Putty
Unplug your projector. Plug your HDMI into HDMI port 1 and connect your USB to computer. Open up a Putty terminal session as outlined above. If you get a big black screen with no errors upon launching the terminal, youre in a good spot.
Plug in the Projector. If you've done everything right you should get a big long readout of text scrolling by as it boots. If you get this, congratulations, you've accessed the diagnostic correctly!
The final step for actually accessing the usable terminal is doing the same but while booting into recovery.
4. Booting into recovery
Turn off your projector. Unplug it. Take your remote and hold down THE OK BUTTON and the BACK BUTTON at the same time. While still holding this, plug in the projector. It should start booting up. You're terminal Putty should be going crazy with text readout like last time. After a few seconds, let go of the buttons. Your projector should eventually end up on the Recovery menu, which is just some big buttons in english and chinese with a black background.
image courtesy of jaberwocky on AVS
After the readout in the terminal has stopped, press enter. It should skip to a new line with
Code:
~#
Tada, root! You're officially in a fully privileged root terminal in the underlying unix system of the projector.
This is the hard part of all this. If you've successfully reached this part, you've won the battle. Everything from here on out is just a couple of commands and some files being downloaded and transferred.
Launching TWRP, making a Nand dump, flashing Magisk, getting Root
So if you indeed have reached the point where, from recovery, you can enter commands into the terminal session, now the question what to with it. The answer is basically anything you want, but let's launch TWRP and go from there.
So here is where you need to download this zip file, also courtesy of @loly from the original russian thread. He went to the trouble of (I'm assuming) compiling his own TWRP for Xiaomi Mi TV 4A which, which as I've mentioned before it's chip (Amlogic T962) is the in the same family as the chip in our projector (Amlogic T968) so it works. That said I would say right now this is not a full TWRP specially made for our projectors, so we aren't going to flash it. We are going to launch it from the terminal (as per @loly's instructions) and use it, but not flash it to our recovery partition. This is for the best right now because a. it's not for our device and b. stock recovery allows us to install OTA updates if they come in the future
View attachment TWRP.zip
my attached version has only the twrp folders, no recovery image, no magisk included.
https://yadi.sk/d/uTUrwdAl3ZyUcN <---- original zip
Download that zip file and unzip its contents right into your USB drive, so that the folder `twrp` (lowercase) is in the root of your drive . This will make it easier to type the commands exactly as they appear later. Ignore the recovery.img, we're not flashing this onto this device.
The magisk included in the TWRP.zip is old by this point. I flashed Magisk 17.1 flashable zip, the latest stable as of this writing. Get it here https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip and put it on the flash drive.
A quick primer, this terminal instance has Busybox installed. Busybox is a "swiss army knife" of unix command like binaries because it packages all the standard linux commands into one single binary, so instead of calling
Code:
ls
to see the contents of the directory you instead would type
Code:
busybox ls
and it would work.
One last thing before I continue: while doing terminal stuff, I quickly learned that occasionally the terminal would throw up all kinds of gibberish which, as far as I can tell, had no rhyme or reason to it and more important had no discernible effect on what i was doing. Its a weird bug that maybe only ill experience because of my setup, I don't know. It would take two forms, one where it would throw up a bunch of lines of technical sounding text which included references to errors and such, but would ever actually affect anything. the other is when it would randomly spit out something like "hotplug_9" and again, id just press enter to get to the new line and nothing would have been affected. Don't be alarmed.
1. Insert USB drive into projector
Take your USB and plug it in. On your terminal, you should a small flurry of activity and references to a new device located at
Code:
/dev/block/sda1
or
Code:
/dev/block/sda2
take note of this, because this is the physical address of your USB drive thats going to have to be mounted. sda1 is the typical one, in my experience.
2. Mount USB and copy over files
This is just a series of commands, type them in precisely as I have them here, assuming you've maintained the same file structure on your USB stick as I did, unzipped the TWRP.zip straight onto the root of the USB.
Code:
busybox mount /dev/block/sda1 /sdcard
This mounts your USB device to the folder `/sdcard' if you're usb is at a different device location, change it appropriately.
Code:
busybox ls /sdcard
Just do a quick readout of the contents of `/sdcard` to make sure it properly mounted. you should see the contents of your USB drive listed here
Code:
busybox cp -r /sdcard/twrp/twres /
Copy the folder `twres` from the USB to the root of your projector
Code:
busybox cp -r /sdcard/twrp/license /
Copy the folder `license` to the root of your projector
Code:
busybox cp -rf /sdcard/twrp/etc/* /etc
Copy the contents of the folder `etc` to the etc directory on your projector
Code:
busybox cp -rf /sdcard/twrp/sbin/* /sbin
Copy the contents of the folder `sbin` to the sbin directory on your projector
Code:
busybox chmod -R 0750 /sbin
Change the permissions of the sbin folder to its all executable
So thats all the copying, now the moment of truth
3. Launch TWRP
YOU NEED A MOUSE PLUGGED INTO THE PROJECTOR TO NAVIGATE TWRP!
Code:
/sbin/run.sh
after hitting enter on this command, TWRP should boot up on your screen (and a bit of readout in your terminal
IF TWRP DOESN'T LAUNCH, YOU'VE DONE SOMETHING WRONG. GO BACK AND CHECK EVERYTHING.
I hope if you're doing this you're somewhat familiar with TWRP, but I will try to walk through the 2 most important things to do
4. Rom backup
One of the big buttons is BACKUP, go there and you'll see a series of check boxes for each of your partitions (boot, bootloader, recovery, system, ect). Select the ones you want (I selected all but I know for a fact this is unnecessary but I did't want to overlook anything and I didn't want to guess which I could ignore). It should ask you where to save the backup, select either the USB drive or internal memory and pick a folder. Slide over the thing to begin backup. It'll take a bit but eventually it should finish. Tada, you have a backup of your entire device.
5. Flash Magisk (ie get root)
This is the big kahuna, the one that unlocks everything OS-wide. Before trying to flash Magisk, we need to mount the system partition. This was big headache for me cause I didn't know why all the commands in the install scripts for failing and it was because /system/bin contains all the commands/binaries that Magisk installer script uses to do its stuff, so thats why we need to mount it first before trying anything. Go to the big MOUNT button and you should see checks next to USB and INTERNAL MEMORY or something to that effect, i can't remember off the top of my head. Almost certainly SYSTEM does not have a check next to it, meaning its not mounted. Click the check mark next to SYSTEM and that should be it, it is now mounted.
There is a quick way to check this, which is to go to ADVANCED>TERMINAL and in the terminal type
Code:
mount
if you get any sort of read out of device partitions, you're good, that means the mount command is working meaning the /system/bin is being made available to TWRP to execute commands.
With that done, go over to the INSTALL button on the home screen and navigate over to your USB stick and find the Magisk 17.1.zip. Select it. Check the check mark to reboot after install. Slide over the slider to begin the install. Moment of truth, you'll likely get to errors in big red text something like MOUNT -O BIND /SDCARD FAILED or something, thats fine, ignore it. It should go onto to say
Code:
|----Magisk Installer Script 17.1----|
or something like that, that means its doing its thing. Everything should go well and it should ask to reboot.
6. Verify root
Once you boot into the Xiaomi home screen after flashing Magisk, you should get some kind of thing asking to confirm that you want to install the application. That application is the Magisk Manager, which means you did it, Magisk installed successfully!
Go ahead and install some app that you know asks for superuser and it should prompt you for superuser access, grant it. You did it, you're root!
View attachment 4617430
jhordies said:
Hi,
I installed the app and got a Chinese popup telling me that what I was doing was forbidden to users.
The menu is in Chinese too and I tried translating it with google translate but It's very tedious and I'm not very confident going through the menus.
Thanks a lot for the procedure for the backup.
I will cleanup all the installed apps and maybe reset it completely so that i can share the backup online.
If you're going to prepare a tool to do so, I will wait so I can test it as well.
Let me know if I can help you by sending you more infos.
Cheers
Jerome
Click to expand...
Click to collapse
There's really not much this app can break (and not much to change neither). Most interesting thing would be the information page, along with the temperature page.
Concerning the dump, no need to cleanup anything as user data is stored :
- in /sdcard (internal memory) mount
- in app folder which can't be accessed without root
Dumping /system won't access any of them, this will basically only copy files that where part of the last firmware installed on your device.
As for my app, not sure I'll have time to finish it before next week.
servo386 said:
This is a long one. Also it was originally written for an audience who may have not been as familiar with Android/Linux commands so it has lots of explanation that might feel out of place on XDA.
So first and foremost ALL CREDIT BELONGS TO @loly ON THE 4PDA.RU FORUM WHO ACTUALLY DISCOVERED THIS PROCESS
https://4pda.ru/forum/index.php?showtopic=810785&st=3260#entry75802829
I definitely am just a copy cat who guessed that his process would also work on this device since their both Xiaomi TV devices with Amlogic T96* boards.
So if you read his post (which you definitely should in addition to this post in order to get the full picture of how this is done), you'll see that this is quite complicated and a kind of high level hack. I hope I'll be able to explain it enough and walk through it enough for it be fairly accessible for less technically inclined people who want to root their Xiaomi projectors.
What is required:
1. HDMI cable you can chop up or an HDMI breakout cable like this one: https://www.amazon.com/Adapter-signals-Terminal-Breakout-Connector/dp/B01CU9SHOO/
2. UART to USB adapter cable/board like this one: https://www.amazon.com/Adapter-Serial-Converter-Development-Projects/dp/B075N82CDL though there are cheaper options available
3. Cables/wires to connect both things. The USB UART package above comes with some, though you'll have to strip the ends to screw them into the terminals of the HDMI breakout board.
4. A spare USB drive
5. A computer to use the USB to UART adapter and a terminal program, i am using Putty.
So the basic idea behind this is that one of the HDMI ports (HDMI 1 in this case, the one closest to the edge) also serves as a diagnostic/UART port via 3 of the 19 pins of the HDMI. When this HDMI port is properly wired to the UART adapter, and you have a terminal open observing said port, upon boot the machine reads out all its startup stuff and when booting into recovery, gives you a completely liberated UNIX terminal that accepts input from the UART terminal, with full root privileges and busybox! As @loly says in his post, here we thank the people at Xiaomi for not bothering to secure this section and giving us full diagnostic root access with busybox. This is almost surely the way the developers of this machine would interact with this machine and developed for it. So let me try to explain how this works and how we get to TWRP and root.
Steps:
1. We need to properly connect the correct pins on the HDMI cable to the correct pins on the UART.
Here I am going to re-post some of @loly's images from the original thread, so all credit goes to him.
View attachment 4617376
Here we see the pins we need. Pin 14 is our VCC, which in this 5v (the UART adapter im using has a switch for 3.3v or 5v, this switch needs to be set to 5v!) Pin 15 is the receive pin and Pin 16 is the transmit pin
The fourth lead we need is the GND (ground), which in the case of an HDMI cable is usually an un-shielded wire that connects to the the case of the connector itself.
I'm going to stop here for a sec and say this is why it's alot easier to use the HDMI breakout board over trying strip an HDMI cable and finding which wire corresponds to which pin (you need a multi-meter to do that)
its a small investment but it makes everything ALOT easier. On the HDMI breakout board, the ground terminal is pin 20.
the corresponding pins on the UART are pretty straightforward. VCC goes to VCC on the UART, pretty straightforward, on the other hand the RX pin of the HDMI (pin 15) goes on the TX OF THE UART makes sense right? the receiever of the HDMI should be listening to the transmitter of the UART and vice versa, so the TX pin of the HDMI goes on the RX pin of the UART. The GND pin (pin 20 on breakout board) goes to the GND on the UART.
View attachment 4617377
Here's my setup. Sorry for the not very great picture. The terminal blocks on the HDMI breakout board work basically like you were connecting speakers to an amp, you unscrew the terminal till you see a little metal hole and you stick the stripped tip of the cable into the hole and screw the terminal back up till its snuggly holding onto the cable. You can use a multi-meter if you have one to make sure the wire is making contact with the terminal and even test the exact pin with the cable to make sure the connection goes all the way. If you're cable is making contact with the metal of the terminal, it is almost certainly correctly making contact with the actual HDMI pin, barring maybe a badly manufactured breakout board. I used spare MALE end pin connector cables to strip the ends and stick in the terminals, and connected them to the FEMALE connectors that came with the UART adapter. You don't necessarily have to do it this way, you can directly strip one of the female ends of the cable and connect the other female end to the pins on the UART, but you'll have a pretty short cable from HDMI to USB and you'll probably need a USB extension to comfortably use it with a computer.
So now you have you're HDMI diagnostic cable!
2. Setup your computer for UART and Putty.
Connect your UART to USB adapter to your computer. In Windows 10, it should automatically install drivers, but if it doesn't, your device should come with a link or something to download the drivers. I'm not going to get into the specific of how to install drivers on Windows computers but needless to say, you need to get the computer to recognize the device and properly utilize it via the drivers. Once you have it properly installed on the machine, it should show up in your device manager under Ports (COM & LPT) or something similar.
View attachment 4617379
this is important because we need to 1. determine what COM port you're device is on and 2. change the baud setting.
So in the photo you see that it tells you what COM port is, which we need for later.
Now you need to go into the settings of the device and go into Port Settings tab
View attachment 4617381
WE NEED TO SET THE BITS PER SECOND TO 115200!
Very important!
Setting up putty:
View attachment 4617383
Basically open up putty and put the button on Serial, set the speed to 115200 and in the SERIAL LINE put the correct COM port number (COM1, COM2, COM3, ect)
Pressing enter on this should open a big blank black terminal with no activity. Thats good because its working. If it wasn't, you'd get an error about not reaching COM port or something.
3. Testing out our diagnostic cable with UART and Putty
Unplug your projector. Plug your HDMI into HDMI port 1 and connect your USB to computer. Open up a Putty terminal session as outlined above. If you get a big black screen with no errors upon launching the terminal, youre in a good spot.
Plug in the Projector. If you've done everything right you should get a big long readout of text scrolling by as it boots. If you get this, congratulations, you've accessed the diagnostic correctly!
View attachment 4617385
The final step for actually accessing the usable terminal is doing the same but while booting into recovery.
4. Booting into recovery
Turn off your projector. Unplug it. Take your remote and hold down THE OK BUTTON and the BACK BUTTON at the same time. While still holding this, plug in the projector. It should start booting up. You're terminal Putty should be going crazy with text readout like last time. After a few seconds, let go of the buttons. Your projector should eventually end up on the Recovery menu, which is just some big buttons in english and chinese with a black background.
View attachment 4617401
image courtesy of jaberwocky on AVS
After the readout in the terminal has stopped, press enter. It should skip to a new line with
Code:
~#
Tada, root! You're officially in a fully privileged root terminal in the underlying unix system of the projector.
This is the hard part of all this. If you've successfully reached this part, you've won the battle. Everything from here on out is just a couple of commands and some files being downloaded and transferred.
Launching TWRP, making a Nand dump, flashing Magisk, getting Root
So if you indeed have reached the point where, from recovery, you can enter commands into the terminal session, now the question what to with it. The answer is basically anything you want, but let's launch TWRP and go from there.
So here is where you need to download this zip file, also courtesy of @loly from the original russian thread. He went to the trouble of (I'm assuming) compiling his own TWRP for Xiaomi Mi TV 4A which, which as I've mentioned before it's chip (Amlogic T962) is the in the same family as the chip in our projector (Amlogic T968) so it works. That said I would say right now this is not a full TWRP specially made for our projectors, so we aren't going to flash it. We are going to launch it from the terminal (as per @loly's instructions) and use it, but not flash it to our recovery partition. This is for the best right now because a. it's not for our device and b. stock recovery allows us to install OTA updates if they come in the future
View attachment 4617409
my attached version has only the twrp folders, no recovery image, no magisk included.
https://yadi.sk/d/uTUrwdAl3ZyUcN TERMINAL and in the terminal type
Code:
mount
if you get any sort of read out of device partitions, you're good, that means the mount command is working meaning the /system/bin is being made available to TWRP to execute commands.
With that done, go over to the INSTALL button on the home screen and navigate over to your USB stick and find the Magisk 17.1.zip. Select it. Check the check mark to reboot after install. Slide over the slider to begin the install. Moment of truth, you'll likely get to errors in big red text something like MOUNT -O BIND /SDCARD FAILED or something, thats fine, ignore it. It should go onto to say
Code:
|----Magisk Installer Script 17.1----|
or something like that, that means its doing its thing. Everything should go well and it should ask to reboot.
6. Verify root
Once you boot into the Xiaomi home screen after flashing Magisk, you should get some kind of thing asking to confirm that you want to install the application. That application is the Magisk Manager, which means you did it, Magisk installed successfully!
Go ahead and install some app that you know asks for superuser and it should prompt you for superuser access, grant it. You did it, you're root!
View attachment 4617430
Click to expand...
Click to collapse
Thank you for your time adding this post here and for the tests you've made to root this device. That's really cool !
If you have time, don't hesitate to post a full dump of your rom, we might learn a bit more than with mine.
Also I have not read your post from my computer so it might just be a bug, but Tapatalk reports your twrp.zip file as being 5 bytes only.
Edit: nevermind, your twrp is fine
I've ripped the "backup" archive that is a flashable update image of the stock image, used by the machine when you do "system restore" in recovery.
Basically here is the stock rom for the model 01 "rainmain" at last.
https://mega.nz/#!jY40SCQR!2gPjpPxzoDg3c1--pxGBR7qfKHxSyzWqU3eZGUz7kb0
#1 and #2 posts edited, adding many details, roms links...
Hi,
Thanks again guys for the effort you put on this.
I bought the hdmi breakout and a usb ttl and followed the instructions (very clear, thanks again for this) and backed up everything as you did but didn't root the device yet.
Are my .win backup files usefull to anyone (Wemax 7000) or do you need me to root the device to make the dump as spocky12 suggested?
I don't know how interesting my Chinese rom would be to others though...
Anyway it's good to know that we could flash the device with the android 8.1 rom when it will be available.
If you know anyone having the english rom, I would be willing to send him my cable to make a backup of his.
Cheers
jhordies said:
Hi,
Thanks again guys for the effort you put on this.
I bought the hdmi breakout and a usb ttl and followed the instructions (very clear, thanks again for this) and backed up everything as you did but didn't root the device yet.
Are my .win backup files usefull to anyone (Wemax 7000) or do you need me to root the device to make the dump as spocky12 suggested?
I don't know how interesting my Chinese rom would be to others though...
Anyway it's good to know that we could flash the device with the android 8.1 rom when it will be available.
If you know anyone having the english rom, I would be willing to send him my cable to make a backup of his.
Cheers
Click to expand...
Click to collapse
Thank you for your message. Glad you managed to follow @servo386's intructions. If you don't mind, I'd be interested in your .win files, to validate a few assumptions I have.
Concerning the international model, unfortunately, as of now, no owner seems to be willing to take the plunge. Hopefully it'll change soon enough.
For hackers out there, I found a tool that might prove helpful to build customs roms or repack roms using international model paritions (once somebody will dump it).
It's AMLogic Tools 5.5.0 that can be found here. I haven't had time to read the full thread yet. There might be valuable information there.
You can use it with the stock rom (935) from @servo386 that I specifically extracted and repacked with latest (1074) recovery (stock "backup" rom does not ship with recovery, which is needed by AmLogic Tools).
You can use the "customization tool" to easily extract/repack a rom that can be flashed in recovery or with special Amlogic USB flash tool.
There is also a tool that can "convert" a classic recovery to TWRP recovery (but supposedly only works with S905/S912. Might be interesting to check what is needed to make it work on our chip)
Unfortunately, I'm not an expert at building custom roms in Android (the latest custom rom I built was for Windows Mobile 6.1) (Great. I'm feeling old now ). I'm not quite sure what is allowed to be flashed with our bootloader. I haven't tried to flash anything yet, as if I brick the projector, my wife will probably kill me . But I suppose that if the custom built firmware doesn't embed bootloader/recovery, most errors will be recoverable by flashing the stock rom again.
If you want to test, don't forget to call the built rom "update-rainman.zip" and to put it in the root folder of an USB device along with this file.
Hey, it's me again
Some of you might be interested in an update to a more recent (but beta) version for wemax/chinese Mi projector.
I added a link to OTA from 1074 (1.3.74, built on May 4th) to 1189 (1.3.95d, built on Oct 12th) in the second post (yes, it's still Android 6.0.1)
To install it, just extract the zip file to the root of a USB thumb device and follow the procedure to boot into recovery mode. The update will be automatically installed (approximately 5 minutes will be necessary). You won't lose any data (well, unless there's a power cut during the update process ).
I haven't tested much, but here are the changes I've seen :
- most menus (settings) are in english now
- new settings options (the only one still in chinese) : automatic power off after 10 minutes of inactivity (doesn't seem to work, though)
- new volume UI
- Karaoke app added
- new animations during recovery installation
- wmv3 video format support added
As a side note, I've found a reference to an upcoming Xiaomi Laser projector in code, that wasn't there before : MiProjLAS2, codename batman.
spocky12 said:
...
I added a link to OTA from 1074 (1.3.74, built on May 4th) to 1189 (1.3.95d, built on Oct 12th) in the second post (yes, it's still Android 6.0.1)
...
Click to expand...
Click to collapse
Thank you so much for your work.
The file to update to the current beta is only 55Byte in size. Nothing happens when plugging in the USB stick.
===============================
I had two xiaomi laser projectors so far.
Projector 1 had dead pixels after 3 weeks of use. Here are the key figures from the engineering menu.
Here projector number 331 from 2018 calendar week 3:
It had a great contrast: 5382:1
The one complained to gearbest and got an exchange(Projector 2).
Here projector number 1196 from 2018 calendar week 13:
Contrast: 2441:1
Projector 2 unfortunately has too little contrast and is very blurred at the edges. Currently exchange projector 3 is on its way.
.bismarck
Thanks for your message. Comparing data from different projectors is really interesting.
Concerning the link, my bad, I've updated it to the right file, you can download it again if you wish.
Thanks spocky12, just loading the beta
When Projektor3 has arrived, I put the values from the menu here.
Edit: I copied the unzipped archive into the root of the USB stick. But nothing happens when inserting the stick.
.bismarck
You have to follow the procedure to boot into recovery. Either use :
- "ADB reboot recovery" if you have ADB
or
- unplug your projector, keep your remote "ok" and "back" pressed and plug your projector back in. It will boot into recovery and automatically start the update process.
(Your usb thumb drive should be formatted in fat32 and both files placed in its root folder).
Hi Guys,
I'm using chinese double din android stereo in my car, i don't know the brand (no label or sticker on the box or on the device), when i start the radio system shows pre-saved frequencies at the memory, i'm changing frequency and want to save to memory (like first one) when i hit to save button it saves after the closest frequency, for example if want to save 89.6 FM to memory it saves after 89.3FM directly, i couldn't find the delete pre-installed channels (keep my finger on the memory didn't work, tried the drag saved frequency didn't work too), there is only self motion search button on the interface and it's scanning all frequencies and saves automatically to memory.
as you can see attached radio settings, there are two options, if i select FM INSIDE or AUTOMATCH my radio works, but if i choose the NXP6851 radio app doesn't even starts(it's crashing when i hit to radio button).
I've downloaded couple of tuner app from forum(like MTCFlatRadio) but there is no sound with those apps.
Is there any fm tuner app i can use with my stereo?
My system info and stock radio app's pictures as attached.
sheshman said:
Hi Guys,
I'm using chinese double din android stereo in my car, i don't know the brand (no label or sticker on the box or on the device), when i start the radio system shows pre-saved frequencies at the memory, i'm changing frequency and want to save to memory (like first one) when i hit to save button it saves after the closest frequency, for example if want to save 89.6 FM to memory it saves after 89.3FM directly, i couldn't find the delete pre-installed channels (keep my finger on the memory didn't work, tried the drag saved frequency didn't work too), there is only self motion search button on the interface and it's scanning all frequencies and saves automatically to memory.
as you can see attached radio settings, there are two options, if i select FM INSIDE or AUTOMATCH my radio works, but if i choose the NXP6851 radio app doesn't even starts(it's crashing when i hit to radio button).
I've downloaded couple of tuner app from forum(like MTCFlatRadio) but there is no sound with those apps.
Is there any fm tuner app i can use with my stereo?
My system info and stock radio app's pictures as attached.
Click to expand...
Click to collapse
My unit has the same issue. I think it's an issue of "Radio" app version.
A question for others to help us - is there a way to check the version of "Radio" app in our units?
kolai said:
My unit has the same issue. I think it's an issue of "Radio" app version.
A question for others to help us - is there a way to check the version of "Radio" app in our units?
Click to expand...
Click to collapse
let me know if you find a solution, i'll try to root or flash new rom to fix it, i'll keep you posted
i'm giving up, tried lots of roms (including russian ones) but it cames with same radio app it doesn't allow you to arrange station order, also found and tried couple of radio apps and they doesn't work (crashing or no sound),if anyone found a solution please post but i'm not going to try anymore.
kolai said:
My unit has the same issue. I think it's an issue of "Radio" app version.
A question for others to help us - is there a way to check the version of "Radio" app in our units?
Click to expand...
Click to collapse
first of all thanks to @gouster3 for his post.
Here is what you need to do, after this operation your radio would not let you save stations in desired order but radio app will work much more stable and your device will be rooted (no more bad reception or changing station automatically)
You need laptop, male to male usb cable(never ever try to do this operation through wireless ) and a paperclip or toothpick to hit reset button :
-you can buy or make an male to male usb cable, making one is pretty easy
-find two usb data cables, cut the cable from half or as you desired
-there will be 4 cables in it red-white-green-black
-solder those cables regarding their colors : red to red - white to white - green to green - black to black, don't just wrap them eachother and tape it,it could causing flash errors, soldering is the solid & best way, after soldering the cables just tape them to avoid any short.
download this rom : https://mega.nz/#!Fh8RUQIK!NjTdZOhAU9CRqaUihy-kUR7CxwVmP5P2M8jrPKHo2Ro
Extract the archive to your desktop;
- install drivers from SP_Driver folder
- make backup of your device, i didn't do it because it's easy to recover from brick,but a backup is better way.
Flashing process:
- open flash_tool.exe from ATC_Flash_Tool folder
- select Download-Agent MTK_AllInOne_DA.bin from ATC_Flash_Tool folder
- select Scatter-loading File AC8227L_Android_scatter.txt from Firmware folder
- make sure PRELOADER is not checked. (There isnt any in in my fw. Just in case if u use this guide for some another fw)
- press Download button
- connect your USB A to A cable one side to PC, another one to your head unit. I recommend u to use that 4 pin usb port (that one with smaller plastic end), but shouldnt matter.
- press RST button on your head unit (use some pin, paper clip or toothpick)
-wait until flashing process ends. There should appear green message.
- press RST button again and let yout headunit boot.
- perform factory reset on your head unit to prevent any bugs
after flashing a good boot you'll see old radio app still there here is what you need to do :
-download FmRadio.app from here https://mega.nz/#!Ifp0wSLC!ht3m0p9br7gi8cpAXTl2EEmorLxy_s2lXA3ccWxGcVU
-copy to your usb memory
-install rootexplorer from google play store https://play.google.com/store/apps/details?id=com.speedsoftware.explorer
-goto root->system->privapps
-You'll see there is a FMRadio.apk
-Cut and move to your usb drive (or just delete it,but i don't like delete things) (do not left that old FMRadio.apk there, if you do that it's installing the old app no matter what you do)
-Switch to your usb drive and copy downloaded FmRadio.apk
-Switch back to FmRadio folder under root->system->privapps and paste the downloaded FmRadio.apk
-Give permissions 0764
-goto factory settings (pasword 8888) and select reboot
-let the device reboot and ready
-open the radio app and you'll see radio app has changed as attached picture
Original poster of this post is @gouster3 , his car is mustang so he edited images according to mustang.
if you want to change boot animation ;
go to here : https://forum.xda-developers.com/android-auto/mtcb-software-development/mod-boot-animation-toyota-t3351617
-download boot animation as you desired
-extract the archive file and copy to your usb drive
-goto system->media
-you'll see bootanimation.zip
-rename it (like bootanimationold.zip)
-copy your own boot animation to system->media
-change copied file name to bootanimation.zip
-set permission as 0644
-reboot the device
-walkthrough of how to change boot animation is here : https://www.hongkiat.com/blog/change-android-boot-animation/
after full reboot your boot animation will change and your radio will work much better, it's still doesn't allow you to save stations as your order but works much better than the old one,i'm still looking for better radio app,if i find one i'll share here.
Your side buttons can loose calibration after this operation,to fix it go to factory settings->touch calibration
If you have reverse or forward camera it could go black after this operation, to fix it factory settings->Protocol Parameter Settings->Reverse video resolution settings->NTSC/PAL, save and your cameras will work fine(no reboot required.)
Hi Sheshman,
it's good that you've found a solution on this issue. Well done!
I'm not ready to change firmware on the unit. As it is, the unit serves my main purpose of using wireless CarPlay. When it works, don't touch it!
kolai said:
Hi Sheshman,
it's good that you've found a solution on this issue. Well done!
I'm not ready to change firmware on the unit. As it is, the unit serves my main purpose of using wireless CarPlay. When it works, don't touch it!
Click to expand...
Click to collapse
yeah i'm using for same purpose too (car play,screen mirroring etc.) but the radio was itching my brain you know , this unit is cheap and does the job perfectly, don't change the firmware if you don't need to (it's painfull process as you know).
Cheers
sheshman said:
first of all thanks to @gouster3 for his post.
Here is what you need to do, after this operation your radio would not let you save stations in desired order but radio app will work much more stable and your device will be rooted (no more bad reception or changing station automatically)
You need laptop, male to male usb cable(never ever try to do this operation through wireless ) and a paperclip or toothpick to hit reset button :
-you can buy or make an male to male usb cable, making one is pretty easy
-find two usb data cables, cut the cable from half or as you desired
-there will be 4 cables in it red-white-green-black
-solder those cables regarding their colors : red to red - white to white - green to green - black to black, don't just wrap them eachother and tape it,it could causing flash errors, soldering is the solid & best way, after soldering the cables just tape them to avoid any short.
download this rom : https://mega.nz/#!Fh8RUQIK!NjTdZOhAU9CRqaUihy-kUR7CxwVmP5P2M8jrPKHo2Ro
Extract the archive to your desktop;
- install drivers from SP_Driver folder
- make backup of your device, i didn't do it because it's easy to recover from brick,but a backup is better way.
Flashing process:
- open flash_tool.exe from ATC_Flash_Tool folder
- select Download-Agent MTK_AllInOne_DA.bin from ATC_Flash_Tool folder
- select Scatter-loading File AC8227L_Android_scatter.txt from Firmware folder
- make sure PRELOADER is not checked. (There isnt any in in my fw. Just in case if u use this guide for some another fw)
- press Download button
- connect your USB A to A cable one side to PC, another one to your head unit. I recommend u to use that 4 pin usb port (that one with smaller plastic end), but shouldnt matter.
- press RST button on your head unit (use some pin, paper clip or toothpick)
-wait until flashing process ends. There should appear green message.
- press RST button again and let yout headunit boot.
- perform factory reset on your head unit to prevent any bugs
after flashing a good boot you'll see old radio app still there here is what you need to do :
-download FmRadio.app from here https://mega.nz/#!Ifp0wSLC!ht3m0p9br7gi8cpAXTl2EEmorLxy_s2lXA3ccWxGcVU
-copy to your usb memory
-install rootexplorer from google play store https://play.google.com/store/apps/details?id=com.speedsoftware.explorer
-goto root->system->privapps
-You'll see there is a FMRadio.apk
-Cut and move to your usb drive (or just delete it,but i don't like delete things) (do not left that old FMRadio.apk there, if you do that it's installing the old app no matter what you do)
-Switch to your usb drive and copy downloaded FmRadio.apk
-Switch back to FmRadio folder under root->system->privapps and paste the downloaded FmRadio.apk
-Give permissions 0764
-goto factory settings (pasword 8888) and select reboot
-let the device reboot and ready
-open the radio app and you'll see radio app has changed as attached picture
Original poster of this post is @gouster3 , his car is mustang so he edited images according to mustang.
if you want to change boot animation ;
go to here : https://forum.xda-developers.com/android-auto/mtcb-software-development/mod-boot-animation-toyota-t3351617
-download boot animation as you desired
-extract the archive file and copy to your usb drive
-goto system->media
-you'll see bootanimation.zip
-rename it (like bootanimationold.zip)
-copy your own boot animation to system->media
-change copied file name to bootanimation.zip
-set permission as 0644
-reboot the device
-walkthrough of how to change boot animation is here : https://www.hongkiat.com/blog/change-android-boot-animation/
after full reboot your boot animation will change and your radio will work much better, it's still doesn't allow you to save stations as your order but works much better than the old one,i'm still looking for better radio app,if i find one i'll share here.
Your side buttons can loose calibration after this operation,to fix it go to factory settings->touch calibration
If you have reverse or forward camera it could go black after this operation, to fix it factory settings->Protocol Parameter Settings->Reverse video resolution settings->NTSC/PAL, save and your cameras will work fine(no reboot required.)
Click to expand...
Click to collapse
Hi, can u use that FMRadio.apk in v3 release?
gouster3 said:
Hi, can u use that FMRadio.apk in v3 release?
Click to expand...
Click to collapse
V3 release?
sheshman said:
V3 release?
Click to expand...
Click to collapse
I mean V3 release of my rom.
gouster3 said:
I mean V3 release of my rom.
Click to expand...
Click to collapse
oh no, i didn't try yet,and seems like i've missed that release, could you please send me the link of the post that i can test it today.
sheshman said:
oh no, i didn't try yet,and seems like i've missed that release, could you please send me the link of the post that i can test it today.
Click to expand...
Click to collapse
It isnt released yet. Just asking if i can include this radio app into v3 release.
Now just v2 available.
And small spoiler for you...
Messing up with android auto connection from phone to radio..
Maybe it would be ready with v3 release.
gouster3 said:
It isnt released yet. Just asking if i can include this radio app into v3 release.
Now just v2 available.
And small spoiler for you...
Messing up with android auto connection from phone to radio..
Maybe it would be ready with v3 release.
Click to expand...
Click to collapse
oh sorry man, it's a very busy day i'm just reading and replying quickly that's why i missunderstood my bad sorry, yes you can i'm using this radio arround 3 weeks and it works fine, the only problem is it doesn't allow you the save stations as you order,it's saving memory to like ascending order.
"Messing up with android auto connection from phone to radio." booooooy oh boooooooooooy, Looking forward to see V3 of yours
sheshman said:
oh sorry man, it's a very busy day i'm just reading and replying quickly that's why i missunderstood my bad sorry, yes you can i'm using this radio arround 3 weeks and it works fine, the only problem is it doesn't allow you the save stations as you order,it's saving memory to like ascending order.
"Messing up with android auto connection from phone to radio." booooooy oh boooooooooooy, Looking forward to see V3 of yours
Click to expand...
Click to collapse
Suddenly cannot get android auto working yet... but at least i got "android auto connected" message on my phone.
hopefully i can get it working in future... Anyways, i would keep that in v3 as it is now.
gouster3 said:
Suddenly cannot get android auto working yet... but at least i got "android auto connected" message on my phone.
hopefully i can get it working in future... Anyways, i would keep that in v3 as it is now.
Click to expand...
Click to collapse
i did my tests about it couple weeks ago, android auto successfully paired and connected every 2 or 3 times over 10 tries, my problem was my phone,i'm using xiaomi mi 8 lite, when i try to install android auto from play store it says your phone doesn't support this app and not installing, so i downloaded the anroid auto app and installed manually to my phone,it works but really glitchy (i don't know it's the right word),so i assume that my phone causing the problem but i don't have any other brand to test it, what i can say is basicly it works on this head unit but i think it needs little bit tunning to make it work.
RDS problem
sheshman said:
Hi Guys,
I'm using chinese double din android stereo in my car, i don't know the brand (no label or sticker on the box or on the device), when i start the radio system shows pre-saved frequencies at the memory, i'm changing frequency and want to save to memory (like first one) when i hit to save button it saves after the closest frequency, for example if want to save 89.6 FM to memory it saves after 89.3FM directly, i couldn't find the delete pre-installed channels (keep my finger on the memory didn't work, tried the drag saved frequency didn't work too), there is only self motion search button on the interface and it's scanning all frequencies and saves automatically to memory.
as you can see attached radio settings, there are two options, if i select FM INSIDE or AUTOMATCH my radio works, but if i choose the NXP6851 radio app doesn't even starts(it's crashing when i hit to radio button).
I've downloaded couple of tuner app from forum(like MTCFlatRadio) but there is no sound with those apps.
Is there any fm tuner app i can use with my stereo?
My system info and stock radio app's pictures as attached.
Click to expand...
Click to collapse
My android head unit , when enter in factory settings then radio has also 3 options , but I can`t switch from FM inside to NXP6851... when I save it and return to radio change is not kept, and again is on FM inside? Thera are red letters After the success of the save please reset again!!! but I really don`t know what to do and how to reset ...any help? Thanks
I was using my NXP6851 and with the same problem of setting stations, I pressed the Search key and then the tuner disappeared. I only see the radio APP. How do I solve it?
hello, i have the same head unit but i have 1gb ram/ 16 rom. this is possible update rom in this topic?
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
Consider before taking a post here and please make sure whether you are writing in the relevant thread!
Check your device configuration if it relates to this thread. If not please dont facilitate the proliferation of misinformation, otherway please feel free to share your knowledge and experience or take a question.
I feel the neccesity to create a separate thread for this version of HU since it makes always confusions whether the revealed information relates to the owners device or not. On the other hand some of the applied methods are way more different compared to the PRO series that mainly derives from the differences of the UI thus this thread will ease that confusion.
That is why i will share here all the methods of troubleshoots i have collected so far.
Basic codes:
Settings ==> Car Settings ==> Extra Settings ==> 8888 (restricted settings)
Settings ==> Car Settings ==> Extra Settings ==> 123456 (advanced settings for left panel touch controls and ect.)
Settings ==> Car Settings ==> Reset Factory ==> 7890 (wipe data - all 3rd party app. will be deleted)
Settings ==> System ==> Developer Options ==> 7890 (usb debug and ect.) ==> USB debug Pw.: [email protected]
Advanced Developer options:
Settings ==> System ==> Developer Options ==> 7890XX , XX=Current time in hours 24hrs format. If its 7 o clock in the morning then the code is 789007
Do not try any of these codes with no reason and without the adequate knowledge!!!!
If the HU is working well forget it!!!!
Use these codes only on your own risk and reponsibility!!!!
TO BE CONTINUED
Follow on topics:
- Method to force update and wipe data cache as a solution of a boot looping.
- Setting up the left touch panel including button lights activation with color change.
- Method of installation and activation NEXAI Toppal AI (key not included, must buy)
- Firmware update method.
- BT issue
Method to force update and wipe data cache as a solution for boot looping.
Right now there isnt any known method for this version of the HU to restart in recovery mode to make a wipe cache but . . . .
There is a working method to force the HU into update mode even if it stucked in boot loop.
-Get a paperclip, needle or toothpick
-Get an USB flash drive 1-32 Gb, Format it with FAT32 file system with the default volume size as it is provided by WIN11
- Open the link (provided by JUNSUN support)
https://drive.google.com/drive/folders/1QGzYyTV2_S7W2wmr7mP3uSgsWAxzyONb?usp=sharing
-Extract the ZIP file and copy all 3 files to the flash drive root directory.
- Get in the car and connect the flash drive to the 4 PIN USB outlet.
-Put the key into the start lock and turn to ACC/Power on wait until the boot logo comes up.
-Take the paper clip and press the reset button 1x, just press, dont hold
-The device will restart and when the boot logo appears again switch the power off/ turn the key/ ignition off immediately.
-Wait 10 SEC and turn to ACC/Power on.
-If everithing went well a "green loading bar" shuld appear on the screen with the tex "UPDATING" or something similar, i could not read it properly because it was visible only for a couple of second due to the size of the upgrade files ~2kb . I think these files are something that is like ADB (Android Debug Bridge) and initiates an update recovery command.
-The update took me approx. 5 mins.
-After the update all 3rd party application will disappear, eventually its like a wipe chace.
So far this is the only known working methode to get out from boot loop without flashing the HU.
Ps.: If it does not work try the other USB outlet or try another flash drive. If it still does not work dicsonnect every cable from the HU and reconnect only the power supply and USB and try again all the combinations that i previously mentioned.
Setting up the left touch panel including button lights activation with color change. Video under the link.
https://drive.google.com/file/d/157qTEhxfl11gp8w9Ip1ghGQnQOuiQBKR/view?usp=sharing
Link to Color.apk
Basicly the so callaed color.apk is a preinstalled sys. app.. With the following method you can enable the aplication:
Got to SETTINGS > CAR SETTINGS > EXTRA SETTINGS >> 123456 >> CONFIG INFO >>> tick the box, select >>> COLOR
after that the aplication should be visible. If not follow the link below:
https://drive.google.com/file/d/1XpS7sQ9CQblHlHcYi4VO3uNc4xyErlKZ/view
Method of installation and activation NEXAI Toppal AI (key not included, must buy)
Installation:
https://www.youtube.com/watch?v=G9LUWAZGiAg&t=95s
Link for the NEXAI APK files:
https://drive.google.com/file/d/1tDDi05owYzdGayswq-Alj8GpKQhXZJtX/view
Activation:
Firstly you should buy an Activation code.Once you got the code then the steps are as of the following:
(1)Copy the activation code sent by the customer service, modify the SSID of the hotspot to the activation code, turn on the WIFI of the radio and connect to the corresponding activation code(SSID), and the activation will be successful after successful networking.
(2)You can enter the ‘NEXAI Voice’ application to check whether it is activated. Once the activation is completed, the voice control function will be available and the Nex(Floating Robo) will change the color.
Wotaisalive said:
Method to force update and wipe data cache as a solution for boot looping.
Right now there isnt any known method for this version of the HU to restart in recovery mode to make a wipe cache but . . . .
There is a working method to force the HU into update mode even if it stucked in boot loop.
-Get a paperclip, needle or toothpick
-Get an USB flash drive 1-32 Gb, Format it with FAT32 file system with the default volume size as it is provided by WIN11
- Open the link (provided by JUNSUN support)
https://drive.google.com/drive/folders/1QGzYyTV2_S7W2wmr7mP3uSgsWAxzyONb?usp=sharing
-Extract the ZIP file and copy all 3 files to the flash drive root directory.
- Get in the car and connect the flash drive to the 4 PIN USB outlet.
-Put the key into the start lock and turn to ACC/Power on wait until the boot logo comes up.
-Take the paper clip and press the reset button 1x, just press, dont hold
-The device will restart and when the boot logo appears again switch the power off/ turn the key/ ignition off immediately.
-Wait 10 SEC and turn to ACC/Power on.
-If everithing went well a "green loading bar" shuld appear on the screen with the tex "UPDATING" or something similar, i could not read it properly because it was visible only for a couple of second due to the size of the upgrade files ~2kb . I think these files are something that is like ADB (Android Debug Bridge) and initiates an update recovery command.
-The update took me approx. 5 mins.
-After the update all 3rd party application will disappear, eventually its like a wipe chace.
So far this is the only known working methode to get out from boot loop without flashing the HU.
Ps.: If it does not work try the other USB outlet or try another flash drive. If it still does not work dicsonnect every cable from the HU and reconnect only the power supply and USB and try again all the combinations that i previously mentioned.
Click to expand...
Click to collapse
translate from picture
Wotaisalive said:
Method to force update and wipe data cache as a solution for boot looping.
Right now there isnt any known method for this version of the HU to restart in recovery mode to make a wipe cache but . . . .
There is a working method to force the HU into update mode even if it stucked in boot loop.
-Get a paperclip, needle or toothpick
-Get an USB flash drive 1-32 Gb, Format it with FAT32 file system with the default volume size as it is provided by WIN11
- Open the link (provided by JUNSUN support)
https://drive.google.com/drive/folders/1QGzYyTV2_S7W2wmr7mP3uSgsWAxzyONb?usp=sharing
-Extract the ZIP file and copy all 3 files to the flash drive root directory.
- Get in the car and connect the flash drive to the 4 PIN USB outlet.
-Put the key into the start lock and turn to ACC/Power on wait until the boot logo comes up.
-Take the paper clip and press the reset button 1x, just press, dont hold
-The device will restart and when the boot logo appears again switch the power off/ turn the key/ ignition off immediately.
-Wait 10 SEC and turn to ACC/Power on.
-If everithing went well a "green loading bar" shuld appear on the screen with the tex "UPDATING" or something similar, i could not read it properly because it was visible only for a couple of second due to the size of the upgrade files ~2kb . I think these files are something that is like ADB (Android Debug Bridge) and initiates an update recovery command.
-The update took me approx. 5 mins.
-After the update all 3rd party application will disappear, eventually its like a wipe chace.
So far this is the only known working methode to get out from boot loop without flashing the HU.
Ps.: If it does not work try the other USB outlet or try another flash drive. If it still does not work dicsonnect every cable from the HU and reconnect only the power supply and USB and try again all the combinations that i previously mentioned.
Click to expand...
Click to collapse
Do you think there is any chance this would work on a FF_866X model bassed on the MTK8667 chip?
the normal update procedure is to place the firmware update files 8667.bin and 8667.upd files on the root of fat32 usb into 6 pin usb slot, turn on and tap screen, it should show "detected" in top left corner then it updates, however my update files must have been corrupted as update failed and it seems its wiped the unit as now it shows detected but then goes to fastboot mode see pics
I have tried many different firmware versions but it just goes to fastboot, I have tried a few different usb drives and tried both the 6 pin and 4 pin slots but still nothing
Solution for Bluetooth connection issue / failure.
After installation of a third party launcher app or upon updating the firmware it is a common problem that the bluetooth connection does not work (BT device is not visible and unable to discover another device). And also if you check the the MAC address of the BT device it will be value "Null"
With the following method you can activate the built in BT device :
First you need to go into the bluetooth settings and check if there is a username and password. (Important: you don’t need to enter anything yourself, the name and password must be assigned automatically.)
Then
Got to SETTINGS > CAR SETTINGS > EXTRA SETTINGS >> 123456 >> CONFIG INFO >>> tick the box, select >>> BC6 (in some version it is BS6) >>> disable all the others >>>> RESTART
Now it should work.
If the checkmark is in the BC6 checkbox, then you need to deactivate it and put it in front of BC8.
If it is opposite BC8, then you need to change it to another checkbox, reboot the device, and do the same operation, but return the checkmark to the checkbox opposite BC8.
Restart and done ,
robfox1975 said:
Do you think there is any chance this would work on a FF_866X model bassed on the MTK8667 chip?
the normal update procedure is to place the firmware update files 8667.bin and 8667.upd files on the root of fat32 usb into 6 pin usb slot, turn on and tap screen, it should show "detected" in top left corner then it updates, however my update files must have been corrupted as update failed and it seems its wiped the unit as now it shows detected but then goes to fastboot mode see pics
View attachment 5769595View attachment 5769593
I have tried many different firmware versions but it just goes to fastboot, I have tried a few different usb drives and tried both the 6 pin and 4 pin slots but still nothing
Click to expand...
Click to collapse
In my opinion your Boot Loader is corrupted that is reason why it can not be flashed.
The most valuable knowledge can be gained only on the bases of personal experiences. What i can recommend you not more just to make a try. Series of tries will lead to the success.
Wotaisalive said:
The most valuable knowledge can be gained only on the bases of personal experiences. What i can recommend you not more just to make a try. Series of tries will lead to the success.
Click to expand...
Click to collapse
yes I have tried and doesn't work. I guess all I can do now is wait for the seller to reply to me
My unit just goes straight to fast boot screen no matter which firmware I put on the usb
robfox1975 said:
yes I have tried and doesn't work. I guess all I can do now is wait for the seller to reply to me
My unit just goes straight to fast boot screen no matter which firmware I put on the usb
Click to expand...
Click to collapse
In my opinion your Boot Loader is corrupted that is reason why it can not be flashed.
Start to study ADB Shell and try to update it using shell commands via pc or replace your boot loader.
You can start here:
Junsun V1/Pro Megathread
This thread is consolidating all the information of Junsun V1 and V1Pro devices scattered in the Android Head-Units forum. I want to write and extend this to make it easier for new people. It's sometimes difficult to find the right information...
forum.xda-developers.com
Wotaisalive said:
In my opinion your Boot Loader is corrupted that is reason why it can not be flashed.
Start to study ADB Shell and try to update it using shell commands via pc or replace your boot loader.
You can start here:
Junsun V1/Pro Megathread
This thread is consolidating all the information of Junsun V1 and V1Pro devices scattered in the Android Head-Units forum. I want to write and extend this to make it easier for new people. It's sometimes difficult to find the right information...
forum.xda-developers.com
Click to expand...
Click to collapse
thank you I will read but I am unsure if I have the skill to connect to pc....maybe a phone repair shop could do it
Hello! I have a Junsun v1 2 Gb +32 head unit. I can't set the boot logo. Thanks for the help and the answers!
kiscsipas said:
Hello! I have a Junsun v1 2 Gb +32 head unit. I can't set the boot logo. Thanks for the help and the answers!
Click to expand...
Click to collapse
For changing the boot logo watch this video:
For changig boot animation check this:
If you can not catch the password it is : Topway
Wotaisalive said:
For changing the boot logo watch that video:
For changig boot animation check this:
Click to expand...
Click to collapse
Thank you very much for your help.
You are welcome.
Hello, I would like a phone dialer application under Agama car launcher. Can you recommend it? Thank you very much for your help!
Hello, hiw to turn on RDS on Junsun V1 ?
mmikolic said:
Hello, hiw to turn on RDS on Junsun V1 ?
Click to expand...
Click to collapse
Password: 123456
Exit and restart.
Thats all . . . .
Spoiler
Dobrý den. Dnes jsem konečně namontoval nový Junsun v1 s Androidem 11 a jsem z toho rádia docela zklamán. Myslel jsem, že namontuju rádio, nastavím základní věci a budu hrát. Tak to rozhodně není. Nepřehledný, složitý, celý večer koukám na internet a teď už asi 3 hodiny pročítám toto fórum. Zjistil jsem, že RDS je nutno nastavit, OK. Logo vozu je nutno kdesi stáhnout, OK. Ale co mě mrzí nejvíc, když jsem rádio namontoval, fungovalo vše v pohodě. Ovládací tlačítka vlevo stále měnila barvu, čehož jsem si moc nevšímal s tím, že to pak změním na stálou barvu. Připojil jsem zadní kameru a vyzkoušel funkci. Podle schématu v manuálu nešla, našel jsem info, že se musím použít hnědý kabel a pak už to fungovalo. Ale pak jsem si vším, že ona tlačítko vlevo jsou potmě. Víc než hodinu jsem hledal v menu, kde by se to dalo nastavit ale nenašel jsem. Poradíte mi prosím někdo, jak to nastavit? Koupil jsem k tomu i modul OBD2, docela jsem se divil, že v jednotce není žádná apka k tomu, stáhnul jsem Torque ale ten se mi nedařilo nijak připojit. Zkoušel jsem to už dřív v mobilu, tam jsem se s ním sice spojil, ale komunikace žádná, Santa Fe CM2 2006. To ale zatím řešit nechci, teď mě nejvíc trápí ta tlačítka potmě. Děkuji za radu
Mod. Translation: Good day. Today I finally installed the new Junsun v1 with Android 11 and I am quite disappointed with the radio. I thought I would mount the radio, set up the basics and play. That's definitely not the case. Unclear, complicated, I've been browsing the internet all evening and I've been reading this forum for about 3 hours now. I found that RDS needs to be set, OK. The car logo must be downloaded somewhere, OK. But what saddens me the most, when I installed the radio, everything worked fine. The control buttons on the left kept changing color, which I didn't really notice except that I would then change it to a constant color. I connected the rear camera and tested the function. It didn't work according to the diagram in the manual, I found information that I had to use a brown cable and then it worked. But then I notice that the button on the left is dark. I searched for more than an hour in the menu, where it could be set, but I couldn't find it. Can someone please advise me how to set this up? I also bought an OBD2 module for it, I was quite surprised that there was no app for that in the unit, I downloaded Torque, but I couldn't connect it in any way. I tried it before on my mobile phone, I did connect with it there, but no communication, Santa Fe CM2 2006. But I don't want to deal with that yet, now the buttons in the dark bother me the most. thank you for the advice
Luděk Masár said:
Dobrý den. Dnes jsem konečně namontoval nový Junsun v1 s Androidem 11 a jsem z toho rádia docela zklamán. Myslel jsem, že namontuju rádio, nastavím základní věci a budu hrát. Tak to rozhodně není. Nepřehledný, složitý, celý večer koukám na internet a teď už asi 3 hodiny pročítám toto fórum. Zjistil jsem, že RDS je nutno nastavit, OK. Logo vozu je nutno kdesi stáhnout, OK. Ale co mě mrzí nejvíc, když jsem rádio namontoval, fungovalo vše v pohodě. Ovládací tlačítka vlevo stále měnila barvu, čehož jsem si moc nevšímal s tím, že to pak změním na stálou barvu. Připojil jsem zadní kameru a vyzkoušel funkci. Podle schématu v manuálu nešla, našel jsem info, že se musím použít hnědý kabel a pak už to fungovalo. Ale pak jsem si vším, že ona tlačítko vlevo jsou potmě. Víc než hodinu jsem hledal v menu, kde by se to dalo nastavit ale nenašel jsem. Poradíte mi prosím někdo, jak to nastavit? Koupil jsem k tomu i modul OBD2, docela jsem se divil, že v jednotce není žádná apka k tomu, stáhnul jsem Torque ale ten se mi nedařilo nijak připojit. Zkoušel jsem to už dřív v mobilu, tam jsem se s ním sice spojil, ale komunikace žádná, Santa Fe CM2 2006. To ale zatím řešit nechci, teď mě nejvíc trápí ta tlačítka potmě. Děkuji za radu
Click to expand...
Click to collapse
Junsun V1 2GB+32GB - WIFI - CPU MT8227L - MCU: T3(L) // (NOT PRO, NO 4G)
Consider before taking a post here and please make sure whether you are writing in the relevant thread! Check your device configuration if it relates to this thread. If not please dont facilitate the proliferation of misinformation, otherway...
forum.xda-developers.com
Watch the video!