Showing posts with label TYT MD380 Review. Show all posts
Showing posts with label TYT MD380 Review. Show all posts

MD-380 firmware reverse engineered 2

Okay, more questions. If you upgrade to a hacked firmware, can you still use the same programming software, or do you need a different kind of software to program codeplugs with the new firmware? Will you lose your current memories and have to start all over again, or can you re-program your old codeplug file with the new firmware?

When you go to va3xpr net/programming-software-firmware/ , it prompts you to give it your e-mail address or it won't let you download. You have to do an e-mail confirmation. Why? How can I download stuff without having to give it an e-mail address?

If you're on https://github.com/travisgoodspeed/md380tools , what do you actually click on to download the firmware and put it on the radio? All I see on that page are links that give you lines of programming code but it doesn't just give you the actual file.

MD380 screen backlight hack

The screen backlight of the Tytera MD380 utomatically adjusts to ambient light.
It's just 2 resistors and LDR but it's a expert hack.



Cannot read/write codeplug to MD380 when experimental firmware is loaded (Windows)

I have compiled and installed Travis' experimental firmware (latest version from Git) and loaded it into my MD380 with no problem. The user database load (make flashdb) works fine too.

My problem is that I cannot read or write a codeplug to the radio using the Tytera CPS software version 1.32 once the new firmware is loaded. When I try to read or write the codeplug I get the message "please check whether the USB is occupied or not connected". I know that the USB connection is working because I can use it to load the firmware and the database into the radio.

The only way that I can read the codeplug or write a new one to the radio is to go to a system that does not have the libusb driver installed. I need to reflash the firmware with the Tytera firmware (currently using version 2.34) and then CPS will happily read/write the codeplug. This is ugly.

What is everyone else doing to update their codeplugs after installing the new firmware?

 My environment is Windows 7.

PD0ZRY MD380 pre-build firmware

PD0ZRY MD380 pre-build firmware


After getting a lot of requests for local hams with limited knowledge of linux for the md380 firmware I desided to make it automatic
You can find the firmware here: md380-fw
So i wrote a relative simple bash script to check for a new version and if there is one make a new build
Firmware updates are build every hour if there is new code pushed.

Contact Manager 1.32 Released - Update

I received mails from several hams who had trouble with converting codeplugs from one type of radio to another, and found that two distinct issues could pop up - - one, if the first digit of the manufacturer ID code in the codeplug was corrupted, that incorrect data would be propagated to the new codeplug; and second, the frequency range data within the codeplug (which is stored in two different locations and methods, and varies by model) was not consistently being updated.

Version 1.32, which can be downloaded from http://n0gsg.no-ip.org/contact-manager/, corrects both of these problems and adds support for the Retevis RT3, which is yet another MD380 work-alike.

If you open your codeplug in Contact Manager and it says "Unknown" in the Radio Type dropdown box, then you know that the manufacturer ID information is corrupted in your file. Simply choose the correct manufacturer ID, then save the codeplug and you'll be back in business.

MD380 MD390 Retevis RT3 Experimental Firmware Supported Haradware

I've read many posts about this experimental firmware. I've seen many posts related to the MD-380, but I have a MD-390 with GPS and 13.020 firmware (as received new).

My question: can the experimental firmware be used with the newest MD-390 with GPS and new vocoder? I don't want to risk attempting to load it if it's known to now work.
73 - Chris Smith VE6xxxx

From :
https://github.com/travisgoodspeed/md380tools/blob/master/README.md
Supported Hardware
The patched firmware is known to work on the following devices:

Tytera/TYT MD380 (old vocoder)
Tytera/TYT MD380 (new vocoder)
Tytera/TYT MD390 (new vocoder, no gps)
Retevis RT3

Tytera (TYT) MD380 Windows Firmware Installation

Tytera MD-380 Windows Firmware Installation

You can install any of these patched firmware files into your MD380 by using the respective .bin file with the Tytera Windows firmware upgrade tool, "upgrade.exe", available inside their firmware upgrade downloads.

Here are the steps:

    Turn off your MD380 using the volume knob.
    Attach the Tytera USB cable to the SP and MIC ports of your MD380.
    Attach the Tytera USB cable to your host computer.
    Hold down the PTT and the button above the PTT button (not the button with the "M" on it).
    Turn on your MD380 using the volume knob.
    Release the buttons on the radio.

This is how I update the CSV file, with FlashDB, under Windows OS!

Hello UHF MD-380 owners... and MANY thanks to Travis and others on the team, for their programming efforts and for their countless hours they have put into this project!

I have been trying to understand why I was only able to perform a "make flashdb" one time under Windows and transfer the CSV file into the MD-380. Over the past month, I have tried many approaches to the way I installed then de-installed the USB driver, but with no success... until last weekend. I have been testing this on different Tytera radios, and I believe I have found a way to issue a "make flashdb" and reliably flash the 16MB SPI Flash in the UHF MD-380... via Windows.

I have performed this on 3 different MD-380s and repeated several updated CSV installs on each, running both the older (patched v2.032) and newer (patched D13.020) firmware versions. (Please note, I have skipped many steps and hopefully most users will follow what I am trying to state below.)

Normally, I would obtain either one of the following two responses when issuing a "./md380-tool spiflashid" command in a MINGW32 window:

How to update TYT MD-380 hacked firmware!

How to update TYT MD-380 normal or hacked firmware!

How to update your TYT MD-380 to the latest firmware. It is recommended to update your radio regularly to get the latest bug fixes for this radio.



users.csv update MD380 experimental firmware

users.csv does not show info on updated MD380 experimental firmware

I'm another one who went through the process of updating my UHF MD-380 to the experimental firmware from Travis Goodspeed. I originally tried using a Windows 10 machine, and after going through the process, apparently successfully did the firmware and user.csv updates.

When trying the radio, the new firmware seems to be working, but no matter what, I could not get any info other than DMR ID in the green pop-up window that is supposed to show the user information. I have enabled UserCSV in the utility/md380tools menu, but no luck.

So, I thought perhaps W10 was the issue, so I went through the process again on a W7 machine - same result. I see that others have had the same problem, and always get asked two questions: "Did you flash the DB in normal mode?" - the answer is yes, I did. "Did you enable UserCSV from the md380 tools menu?" - Yes, I did.

MD380 message from CPS version 1.32

I just downloaded and built the latest version of md380tools. When I try to write a codeplug to my radio I get this message from CPS version 1.32



I have no issue writing the codeplug with md380-dfu

Tytera (TYT) MD380 DFU-mode

To place radio into DFU-mode, press and hold both PTT and button above it, at the same time turning the radio on. LED should be flashing red and green.

To get out of DFU-mode turn radio off then back on.

MD-380 firmware reverse engineered


So how do I actually do a firmware upgrade on the radio? When you say "compile", I don't understand. How do we just download a firmware file and run a program to put it on the radio?
And if we put an "experimental" firmware in the radio, can we use the same stock TYT programming software, or is there a different programming software we need to program the new features?
So, what is this "github"? How come it doesn't just have the usual download links that say 32- bit Windows, 64-bit Windows, etc. How do I actually download from this website to upgrade an MD-380?

Since this is "experimental" only the Linux source files are provided at "github". You have to compile them into the needed binary file for the update.

This experimental firmware is a project by some obviously pretty smart guys who are kind enough to share it with everyone. But the nature of the project is somewhat advanced and so is the process to make it work, they aren't going to take the time to package everything into a pretty little installer for you. It's understood that if you want to tinker with this kind of stuff you come up to speed with thats going on and become involved.



Github is a repository that programmers use to share source code and ideas. The code can then be pulled from there to be compiled into binary or executable files (depending on what the project is). Also you will often see that with projects like this the authors won't include compiled binaries (and sometimes not all the required dependencies) to avoid copyright issues etc).

In this case they don't include the stock Tytera firmware that needs to be modified, it gets pulled from another site. DSD used to be the same way, and SDRTrunk still is. Some assembly required!




TYT (Tytera) MD-380 MotoTRBO review

As some of you know I am a fan of the MotoTRBO radios. I have a Motorola XPR 6550 which is a very nice TRBO DMR radio, but they are expensive and Motorola has horrible policies like they charge an arm and leg for the programming software and features that the radios already support support out of the box in hardware like AES-256 encryption are expensive options you have to pay to unlock if you want to use that feature. So while Motorola Radios are EXCELLENT in quality you definitely pay for it in the pocketbook.

Anyway that doesn't stop DMR from being an excellent standard, and now finally a sub $200 Chinese radio has come along that is DMR TRBO compatible.

First a quick Disclaimer. DMR is the radio standard, but with-in DMR there is MotoTRBO (Called TRBO on forward) and Hytera (not Tytera which is a chinese company trying to sound like Hytera). Hytera DMR radios will not talk to MotoTRBO radios and vice-versa. In the U.S. virtually 100% of DMR radios go by the TRBO standard so if you buy a DMR radio it is important that you buy a TRBO compatible radio.

So for under $170 shipped you can have a TRBO radio and programming cable shipped to your house, Really that's under 1/4 the price of an XPR with software and programming cable from Motorola

The Tytera MD-380, Like the Motorola XPR is a single band radio. so you have to select VHF or UHF, sorry no dual band TRBO here

I went with UHF because all the TRBO repeaters in my AO are UHF, so the decision was kind of a no brainer, I would have prefered VHF, but oh well.

My first impressions are: It's obvious the XPR is a nicer radio, but the TYT MD-380 isn't bad. It has a solid feel to it. There are a few minor corners that were cut. For example the MD-380 channel selector knob has markings in all black making it impossible to read
, also the waterproofing on the battery on the Motorola had a nice smooth finish to make a seal, the MD-380 does not. This leads me to believe the waterproof rating on the Motorola must be better.

Also the Belt Clip is a Huge disappointment on the MD-380, I doubt it will last a month. The Motorola has a nice big, beefy belt clip, the MD-380's belt clip is just silly.

Audio wise both sound great, it's TRBO after all, but the Motorola does sound better ...... this also was expected.

I had no trouble accessing the TRBO repeater with the MD-380 once I got it Programmed for local...... Which is different than programming the XPR with the Motorola CPS I'm use to, so it took me a few minutes to figure out where to put the Color Codes, and other settings, but once set-up, Bam! I'm talking to to friends in Cali while I'm in Texas

Texting works as well if not better than the XPR-6550. the MD-380 has a better screen for Texting. but the XPR screen is always on. Kind of like a digital watch, backlight only comes on if necessary but the digital display is always on and readable with enough ambient light. The MD-380 is like a cell phone screen. It turns off after 5, 10, or 15 seconds...... and you have to guess what channel you're on since you cant see the screen or the channel knob............. well it's a $140 radio, it's a $140 radio, it's a $140 radio

You get two antennas with the MD-380, the Antenna in the pictures is the shorter of the two and similar in length to the short UHF Motorola Antenna. Where I'm at it works fine, If I needed better range I'd switch over to the longer antenna.

I still haven't figured out how to access the GPS data on the MD-380, but I read that there is a firmware update that I need to apply so that my solve the GPS thing.

I'm getting the MD-380 programmed up for work tonight and I will replace my EDC XPR-6550 with the MD-380 to see how it holds up. This will be a test for the MAG as we are looking for a less expensive way to get TRBO radios. If the MD-380 can hold up at work for more than a few months I'll be impressed (I tend to drop my XPR-6550 all the time)

I'll keep you guys informed on how well the MD-380 holds up to daily use on the job but so far I'm quite impressed considering the radio is only $140, TRBO compatibility is a big deal @ $140

HELP - Can't Get Tytera MD380 DMR Radio USB Driver To Work On Windows 10

Just got my Tytera MD380 BUT I'm having problems with programming it.

Specifically GETTING WINDOWS 10 & THE MD380 USB DRIVER & RADIO TO SIMPLY ACKNOWLEDGE ONE ANOTHER

Simply put, I plug the programming cable from the radio to a USB port. Windows acknowledges this connection with it's usual beeping sound but then NOTHING HAPPENS

What doesn't help matters any is there is NO self-extracting executuable to manually install the driver NOR does Windows even bother searching for it (And ADD/REMOVE HARDWARE within control panel is o help either (I know having just tried it))

As it is now, I CANNOT EVEN BEGIN to do anything but charge the radio (Probably needs that anyway) as I can't even complete the process of entering THE MOST BASIC INFORMATION about the radio (Like the serial number - WHERE IS THAT ??), MUCH LESS do anything else with it


Tytera TYT MD-380 New Fonts and Graphics

These new fonts are great compared to other default fonts.

These fonts make the screen less busy.

You can take a look at the "SHARED" youtube video


Tytera MD380 Jailbreak firmware now available for cheap digital walkie-talkie allowing DMR scanning

In the last years, DMR and MOTOTRBO (a.k.a. TRBO a Motorola Solutions branded DMR Radios ) has become a very popular digital voice mode on the UHF and VHF bands and the MD380 radio is the latest cheap DMR walkie-talkie to come out of China.

The question is, is it any good? The longer answer is slightly more complicated, and involves discussing the difference in price between this radio and other more expensive, but higher quality, radios. But i can tell you that a group of hams here recently purchased the Beihaidao DMR radio (also sold under brands like Tytera, KERUIER or Retevis) and have been having excellent results with them.
Every once in a great while, a piece of radio gear catches the attention of a prolific hardware guru and is reverse engineered. A few years ago, it was the RTL-SDR, and since then, software defined radios became the next big thing. Last Shmoocon, Travis Goodspeed presented his reverse engineering of the MD380 digital handheld radio.

The hack has since been published in PoC||GTFO 0x10 (donwload site) with all the gory details that turn a radio under $200 into the first hardware scanner for digital mobile radio. For comparison, the cost of a Motorola MotoTRBO UHF XPR 7550 DMR radio can reach $800.




The MD380 is a fairly basic radio with two main chips: an STM32F405 with a megabyte of Flash and 192k of RAM, and an HR C5000 baseband. The STM32 has both JTAG and a ROM bootloader, but both of these are protected by the Readout Device Protection (RDP). Getting around the RDP is the very definition of a jailbreak.


In Digital Mobile Radio, audio is sent through either a public talk group or a private contact. The radio is usually set to only one talk group, and so it’s not really possible to listen in on other talk groups without changing settings. A patch for promiscuous mode – a mode that puts all talk groups through the speaker – is now out.

Here in the US Project 25 (P25 or APCO-25) is a suite of standards for digital radio communications for federal users, but for state/county and local public safety organizations including police dispatch channels are using Mototrbo DMR digital standard.

How to install the Hacked Firmware for the MD380. ( Here is a YouTube Video on the Update Process to the Jailbreak of the Beihaidao Radio)





You need source code from https://github.com/travisgoodspeed/md380tools this download does not ship with firmware to avoid legal trouble. Instead it grabs firmware from the Internet, decrypts it, and applies patches to that revision. The output files have a .img extension when unencrypted, and a .bin extension when packaged for the official firmware updater.

Most radios use a serial interface for programming, however MD380 is native USB. Building a USB programming cable for your radio is as easy as soldering on the proper cable adapter. Third party cables are available from ebay.



Files from this process include:

unwrapped.img: factory firmware after decrypting.

prom-public.img and prom-public.bin: patched to monitor all talk groups.

prom-private.img and prom-private.bin: patched to monitor all talk groups, private calls.

experiment.img and experiment.bin: patched to monitor all talk groups, private calls, and sideload alternate firmware.

You can install any of these patched firmware files into your MD380 by using the respective .bin file with the Tytera Windows firmware upgrade tool, "upgrade.exe", available inside their firmware upgrade downloads. Here are the steps:

Turn off your MD380 using the volume knob.

Attach the Tytera USB cable to the SP and MIC ports of your MD380.

Attach the Tytera USB cable to your host computer.

Hold down the PTT and the button above the PTT button (not the button with the "M" on it).

Turn on your MD380 using the volume knob.

Release the buttons on the radio.

The status LED should be on and alternating between red and green, indicating you're in flash upgrade mode.

Start the Tytera "Upgrade.exe" program.

Click "Open Update File" and choose one of the .bin files produced from the process above.

Click "Download Update File" and wait for the flash update process to finish. It takes less than a minute.

Turn off your MD380 using the volume knob.

Disconnect the USB cable from your MD380 and host computer.

Turn the MD380 back on, and you should see the "PoC||GTFO" welcome screen.


Tytera TYT MD-380 Faults

Tytera TYT MD-380 Faults
We needed to flip our view point and look for Faults.

Cons (some may be fixed in a future firmware at least theoretically):

1. MD-380 has a serious problem with slot timmings (see comments below)
2. Stupid keyboard layout. There were no problems to make the standard 16-key keyboard. I really hate this.
3. Color display is useless w/o backlight. Backlight level cannot be adjusted in current firmware so display is too bright in the dark and tends to drain the battery if turned on continuously while on direct sunlight it would be nice to have more brightness.
4. Beep level cannot be set so it is too loud for a quiet environment. Just turn it off.
5. Some firmware and programming software improvements are welcome.

The problem with the MD–380 slot slipping is that the end-user won't notice the problem. The radio is able to get into the network, receive just fine, and everything seems normal. But it is causing interference to other users. 

Hams should think of it like this: If you have a 2 meter radio that transmits fine, receives fine, sounds good, etc., but your spurious emissions are jamming the aircraft band and public safety bands, does that mean your radio is fine?