WARNING:
I have had few customers already with bricked Head units for flashing the wrong ROM.
DO NOT FLASH ROM and MCU from mtcD on mtcB or vice versa.
YOU WILL END UP WITH NO RECOVERY, NO BOOT, NO WARRANTY!
\THE ONLY FIX NOW:
mtcD : NEW MOTHERBOARD with RK3188
mtcB: NEW RK3188 SoM​
I accidentally installed MTCD on a MTCB device and I managed to fix it.
Sent from my SM-G935F using XDA-Developers mobile app
Can you explain how did you do?
Enviado desde mi D6603 mediante Tapatalk
I've been using MTCB roms (Malaysk) on my Audi TT RK3188 headunit for over a year. Last time I was in the system info screen I noticed it lists the unit as MTCD. Has anyone ever heard of this? The MTCB roms have been working fine..
ikerg said:
Can you explain how did you do?
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
I connected my HU to the laptop with adb. And I used Androidtool Marsboard 2.1 to install MTCB image
Sent from my SM-G935F using XDA-Developers mobile app
So in case bricking a mtcd with Androidtool you mentioned can be unbricked as well...but should be adbon command active previously?
There is a command to activate adb on USB ....but if it is bricked I don't know of it could be connected.
Android TV sticks based on rk3188 have some pin shortcut procedure in order to force to enter into recovery.
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
So in case bricking a mtcd with Androidtool you mentioned can be unbricked as well...but should be adbon command active previously?
There is a command to activate adb on USB ....but if it is bricked I don't know of it could be connected.
Android TV sticks based on rk3188 have some pin shortcut procedure in order to force to enter into recovery.
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
When you connect to Windows you will see if it sees your device. Then install USB driver and it should work
Sent from my SM-G935F using XDA-Developers mobile app
What about Launchers?
Can we install kitkat launchers on lollipop units? I'm really tired of the stock JY launcher and want to change to KL D launcher but can't find lollipop specific ones.
knor27 said:
I connected my HU to the laptop with adb. And I used Androidtool Marsboard 2.1 to install MTCB image
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
And how did you connect you unit to your laptop?
The unit has only USB A connector and the laptop also only USB A
An USB A - A cable is very rare/seldom and honest i don't know if this would work because both devices give 5 volt power..
I also have a bricked mtcb device with mtcd software installed on it, i hope i can fix this using my laptop
Hope you can explain to me how you connected your laptop the unit.....
knor27 said:
I connected my HU to the laptop with adb. And I used Androidtool Marsboard 2.1 to install MTCB image
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi @knor27,
Can you explain to me how you did this?
I got the tools and cable, but which file did you use to recvoer, if i read the instructions of androidtool it is only possible to make a dump and to flash it when you have the dump files..
I have no backup dump file, i can download (and have) an (original) rom (which 100% works) but this only contains and update.img and an mcu.img file
The tool does not have any option to use these files to flash the unit.
I hope you can help, have here a bricked unit which i cannot use anymore......
Related
hello
i really need your help
i ve bought RM-CT0007
a rk3066
40nm
4x1,2ghz
android 4.4.4
i found ktu84q for her mcu that's possible ?
the bluetooth doesn't function
caraudio30000 said:
hello
i really need your help
i ve bought RM-CT0007
a rk3066
40nm
4x1,2ghz
android 4.4.4
i found ktu84q for her mcu that's possible ?
the bluetooth doesn't function
Click to expand...
Click to collapse
ok i understand , ktu84p is just the name of android version 4.4.4.
so how can i found the mcu ?
i ad i can to root them
caraudio30000 said:
so how can i found the mcu ?
Click to expand...
Click to collapse
It's at the very top of this forum's main page:
This forum is for questions about MTCB Android Headunits. Check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are in the correct place.
Click to expand...
Click to collapse
this is a copy of the system
anyone ?
I can't see mtcb anywhere on that. I don't think the mtcb forums or firmware are for you
Sent from my SM-G920F using Tapatalk
so i must to post in different section ?
I'd think so. Try the basic Android Auto section
Sent from my SM-G920F using Tapatalk
ok
i will try
thank you
maybe a modo can to changed ?
i can't believe nobody can't help me ....
Why? As said it doesn't look like you have an MTCB head unit. Try asking in the Android Auto general forum rather than the MTCB one
Sent from my SM-G920F using Tapatalk
Please can you somebody test firmware
http://forum.xda-developers.com/showpost.php?p=58249825&postcount=7614
on device RM-CT0007 7.0inch Car GPS 2DIN
i find big problem with bluetooth support like that is no kernel driver for it
Latest firmware from april 2016 , but still same problem with bluetooth and ELM327 adapter
https://yadi.sk/d/IR_V2ROYqkmFN
Guys, I'm having a problem and I think it has to do with updating the Z5 Premium for the MM version .185 , before upgrading my SW3 ( Android Wear 1.4) showed on the screen who was calling , only now the message " number private , " I tested the SW3 with Samsung and caller ID functioned normally . I looked in SW3 and all permissions are allowed , anyone would have any suggestions to fix this problem?
Guto ViP said:
Guys, I'm having a problem and I think it has to do with updating the Z5 Premium for the MM version .185 , before upgrading my SW3 ( Android Wear 1.4) showed on the screen who was calling , only now the message " number private , " I tested the SW3 with Samsung and caller ID functioned normally . I looked in SW3 and all permissions are allowed , anyone would have any suggestions to fix this problem?
Click to expand...
Click to collapse
I use the same phone and watch. No problem so far. I had to do a factory reset on the watch to make the first connection. Have you tried that?
davidht said:
I use the same phone and watch. No problem so far. I had to do a factory reset on the watch to make the first connection. Have you tried that?
Click to expand...
Click to collapse
What firmware are you using with Z5P? Yes, i tried factory but doesnt works.
Enviado de meu E6853 usando Tapatalk
Guto ViP said:
What firmware are you using with Z5P? Yes, i tried factory but doesnt works.
Enviado de meu E6853 usando Tapatalk
Click to expand...
Click to collapse
I'm using the latest 32.1.A.1.185. No root nor bootloader unlock.
davidht said:
I'm using the latest 32.1.A.1.185. No root nor bootloader unlock.
Click to expand...
Click to collapse
What region, Nordic?
Enviado de meu E6853 usando Tapatalk
I have contacted the erisin support and they upload here (Recovery) the recovery firmware. I don't now if the devices is mtcb or mtcd or if it is compatible with your ROM.I don't now how to access the recovery. Can you please tell me if it would be compatible whit Rom and if it would be a good choice for me(I have only 1 din space)?
The only other post on this forum on this head unit is: Other post
Official page model: here
Thank you
Doesn't look like the MCU type is MTCB or MTCD. If it isn't none of these roms will work.
Is it a good choice for you? Only you can answer that.
Sent from my SM-G920F using Tapatalk
gk66 said:
Doesn't look like the MCU type is MTCB or MTCD. If it isn't none of these roms will work.
Is it a good choice for you? Only you can answer that.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
How can i find out what type is it?
It says it under MCU in the about tablet section of the settings.
If you've bought it look there. If you haven't bought it zoom into the settings picture on your link
Sent from my SM-G920F using Tapatalk
gk66 said:
It says it under MCU in the about tablet section of the settings.
If you've bought it look there. If you haven't bought it zoom into the settings picture on your link
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
It says MCU LM-.... the rest is not so clear from the picture :/
The is not MTCD or MTCB. Try Android head unit section for help
Sent from my SM-G920F using Tapatalk
gk66 said:
The is not MTCD or MTCB. Try Android head unit section for help
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
ok: this is the information:
system version number: common_V1.00.00056.53.1
kernel version number: PX3_V2.00.0020.00.00
MCU version number: LM-AND841-7090V.21
Hello.
Did anyone helped with your problem?
My unit doesn't have the touch function any more and displays the message - "Unfortunatelly, the MCU has stopped"). I can't go to Factory reset and I need a MCU firmware recovery to mount it on a SD .
Thank you
dear all where can i find the MCU for Xtrone MCTD_MLT RK3188 5.1
as the Wi-Fi and Bluetooth are not working
dh2010 said:
dear all where can i find the MCU for Xtrone MCTD_MLT RK3188 5.1
as the Wi-Fi and Bluetooth are not working
Click to expand...
Click to collapse
If both are not working....go to factory settings (pass 126 or m126) and go to bluetooth device and change it for other option...reboot and try ... this is a trial and error until you find the correct device being set up
Enviado desde mi SM-G950F mediante Tapatalk
Stock Firmware ZTE Trek 2
Versions available :
K88V2.0.0B17, B15 = Nougat.
K88V1.0.0B31, B33 = Marshmallow.
Downloads:
Google Drive
Mediafire
Mega
4Shared
the version K88V2.0.0B17 and K88V2.0.0B15 should extract update.zip and pass it in micro sd or use pc method adb sideload
K88 SD Card Upgrade Instructions
Or pc using adb sideload (Firmware file)
Example:
1: enter recovery and select adb sideload, from your ZTE Trek 2
2: on the PC open the command window and write adb sideload (file name)
example: adb sideload update.zip
adding the B33 firmware in the links
Enviado desde mi K88 mediante Tapatalk
Nougat has many problems.
7.1 version firmware has problems with sensors.
Only support light sensor.
Acceleromter and proximity and compass does not work on Nougat roms.
koxel said:
7.1 version firmware has problems with sensors.
Only support light sensor.
Acceleromter and proximity and compass does not work on Nougat roms.
Click to expand...
Click to collapse
Are you using the latest version?
juniorgerman said:
Are you using the latest version?
Click to expand...
Click to collapse
Yes. Tested on all versions.
B15 and B17 does not work for accelometer(related to auto rotate display) and compass.
It's also aleady reported by users.
https://www.google.com/search?q=tre...ome..69i57.11311j0j7&sourceid=chrome&ie=UTF-8
Also lineage os 14.1 can not use accelometer and compass sensors.
koxel said:
Yes. Tested on all versions.
B15 and B17 does not work for accelometer(related to auto rotate display) and compass.
It's also aleady reported by users.
https://www.google.com/search?q=tre...ome..69i57.11311j0j7&sourceid=chrome&ie=UTF-8
Also lineage os 14.1 can not use accelometer and compass sensors.
Click to expand...
Click to collapse
in marshmallow works well?
juniorgerman said:
in marshmallow works well?
Click to expand...
Click to collapse
yes.
koxel said:
yes.
Click to expand...
Click to collapse
that is a mistake that should be reported to AT&T and ZTE and I must say that I do not use that feature, but I like to see everything in its order?
koxel said:
yes.
Click to expand...
Click to collapse
or @tdm knows something about this failures, the a studied sources of zte
juniorgerman said:
that is a mistake that should be reported to AT&T and ZTE and I must say that I do not use that feature, but I like to see everything in its order
Click to expand...
Click to collapse
As posted link at google, att aleady know about it. but they does not fix it.
https://www.google.com/search?q=tre...VrwKHcqZB7wQrQIoAjABegQICRAL&biw=1280&bih=952
I attached sensor test app screenshot of lineage os for trek2.
koxel said:
As posted link at google, att aleady know about it. but they does not fix it.
https://www.google.com/search?q=tre...VrwKHcqZB7wQrQIoAjABegQICRAL&biw=1280&bih=952
Click to expand...
Click to collapse
auto rotate works well for me, but above all else I do not know
koxel said:
As posted link at google, att aleady know about it. but they does not fix it.
https://www.google.com/search?q=tre...VrwKHcqZB7wQrQIoAjABegQICRAL&biw=1280&bih=952
I attached sensor test app screenshot of lineage os for trek2.
Click to expand...
Click to collapse
I'm going to make a downgrade to marshmallow and try to see, and what app did you use to test the sensors?
Enviado desde mi SM-S337TL mediante Tapatalk
juniorgerman said:
I'm going to make a downgrade to marshmallow and try to see, and what app did you use to test the sensors?
Enviado desde mi SM-S337TL mediante Tapatalk
Click to expand...
Click to collapse
i am using [url:https://play.google.com/store/apps/details?id=ru.andr7e.sensortest]this
koxel said:
i am using [url:https://play.google.com/store/apps/details?id=ru.andr7e.sensortest]this[/QUOTE]Ok thank
Enviado desde mi K88 mediante Tapatalk
Click to expand...
Click to collapse
But,i'm use Test M https://play.google.com/store/apps/details?id=com.testm.app
koxel said:
i am using [url:https://play.google.com/store/apps/details?id=ru.andr7e.sensortest]this[/QUOTE]
Enviado desde mi K88 mediante Tapatalk
Click to expand...
Click to collapse
Any resolution for the sensor issue? I bought 3 of these tablets (for kids) and seem to be having this issue with 2 of them. They wouldn't auto-rotate, so I ran the sensor test, and the accelerometer (as well as compass, etc.) is not detected on both of them. The other one works fine.
Oddly, I've tried flashing back to the marshmallow stock images I've found in this forum, and the problem is still there. None of the custom images I've tried work either.
I'm not sure for certain whether the sensors worked when I got the tablets, but it would seem odd that two of them would have the exact same hardware problem. So I assume there's an incompatibility between the sensor hardware and the images I'm flashing?
karlrees said:
Any resolution for the sensor issue? I bought 3 of these tablets (for kids) and seem to be having this issue with 2 of them. They wouldn't auto-rotate, so I ran the sensor test, and the accelerometer (as well as compass, etc.) is not detected on both of them. The other one works fine.
Oddly, I've tried flashing back to the marshmallow stock images I've found in this forum, and the problem is still there. None of the custom images I've tried work either.
I'm not sure for certain whether the sensors worked when I got the tablets, but it would seem odd that two of them would have the exact same hardware problem. So I assume there's an incompatibility between the sensor hardware and the images I'm flashing?
Click to expand...
Click to collapse
there was no solution for the sensors, @tdm gave an explanation to the respect in another thread
Enviado desde mi K88 mediante Tapatalk
Boot from sd
Is there a way to make this into bootable sdcard? I am stuck in bootloop.
gdillard1002 said:
Is there a way to make this into bootable sdcard? I am stuck in bootloop.
Click to expand...
Click to collapse
Leave 2 method in op
This is the second method:https://youtu.be/SHu-CMubrhA
Enviado desde mi K88 mediante Tapatalk
Help an idiot please
DL to drive. Need an idiots guide, step by step. I see multiple files in drive, which do I open, can I side load, or do I have to use a SD card and side load?