luxferre/mtreader
Archived
1
0
Fork 0
Code Actions Activity

Full revamp

Browse Source
This commit is contained in:
Luxferre
2020-07-29 18:26:20 +03:00
parent 77feb3ef55
commit d032fd7f70
3 changed files with 59 additions and 152 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+19 -21
View File
@@ -2,28 +2,21 @@
## What's this?
MTreader is a simple and small (under 200 SLOC) Python-based utility that aims to serve a single goal: read chunks of flash memory from MediaTek MT6261-based feature phones. It can also read firmware version before creating the readback, and supports displaying some decimal error codes from the platform itself if anything goes wrong. No other features are supported or even planned here.
MTreader is a simple and small (under 100 SLOC) Python-based utility that aims to serve a single goal: read chunks of flash memory from MediaTek MT6261-based feature phones. No other features are supported or even planned here.
MTreader runs on Python 3.2 and above and only requires pySerial module as a dependency.
## How to use it?
### Basic usage
```
python3 mtreader.py port file start length
```
Example - backup all 4MB of flash memory (positions 0 to 4194304 on the device flash) into `rom.bin` file on Mac: `python3 mtreader.py /dev/tty.usbmodem14100 rom.bin 0 4194304`
Example - backup all 4MB of flash memory (positions 0 to 4194304 on the device flash) into `rom.bin` file on Mac:
### Advanced usage
In case your phone requires a different DA (Download Agent) binary than the provided one (`default-da.bin`), you can also specify its parameters:
- `-a` - path to DA file
- `-s1` - DA stage 1 loading parameters in the `offset:size:addr` format with each value in hex (defaults to `0:0x718:0x70007000`)
- `-s2` - DA stage 2 loading parameters in the `offset:size:addr` format with each value in hex (defaults to `0x718:0x1e5c8:0x10020000`)
- `-fio` - offset to the flash information block within the DA file in hex (defaults to `0x1ece0`)
```
python3 mtreader.py /dev/tty.usbmodem14100 rom.bin 0 4194304
```
You can also adjust the readback block size as well with the `-bs` parameter. Changing it is not recommended if the default of 1024 bytes works for you.
@@ -32,7 +25,7 @@ You can also adjust the readback block size as well with the `-bs` parameter. Ch
### Which hardware is currently supported?
MT6261-based OEM phones that can open BROM port that can be seen as USB-Serial. Nokias (genuine ones) will generally not work. The rule of thumb is: if it can be handled by FlashTool v5.1420, then it can be handled by MTreader as well.
MT6261-based OEM phones that can open BROM port that can be seen as USB-Serial. Nokias (genuine ones) will generally not work.
As for different MT6261 versions support, the tool had been successfully tested on various MT6261D and MT6261M handsets (provided they can also be supported by FlashTool). MT6261D still remains the primary target though.
@@ -43,11 +36,12 @@ No, it isn't. FlashTool is proprietary and single-platform. Having no viable ope
Moreover, to in order to just create a flash dump with FlashTool, you'll need to:
1. Obtain some scatter file (even though it's totally unnecessary for the readback functionality) and load it into FlashTool.
2. Go to the "Readback" tab.
3. Remove all blocks there and create the block with the memory range you want in a tiny GUI window.
4. Select the path to save in another GUI window.
5. Press "Readback" and connect the device with perfect timing for it to be seen by the tool.
6. Probably reinsert the battery (if it's possible at all) after an unsuccessful or even successful operation.
2. Probably also obtain the necessary Download Agent file if the one shipped with FlashTool doesn't work with your model.
3. Go to the "Readback" tab.
4. Remove all blocks there and create the block with the memory range you want in a tiny GUI window.
5. Select the path to save in another GUI window.
6. Press "Readback" and connect the device with perfect timing for it to be seen by the tool.
7. Probably reinsert the battery (if it's possible at all) after an unsuccessful or even successful operation.
With MTreader, you just need to:
@@ -64,14 +58,18 @@ Turn the phone off, insert the cable while holding the bootkey and see what devi
It's a key that you hold to open the BROM serial port. It depends on the vendor. On most phones, it's Call key. On some phones, it can be arrow down key, # or something else.
### How is the tool working without a DA binary?
Yes, MTreader used a DA in the past, but now it's completely blob-free and works via BROM itself. The trick is in using the correct mapping register setting: when we set the 32-bit value at the `0xa0510000` to 3, all the ROM contents (in 32-bit little-endian chunks) are mapped onto `0x10000000` base address by the MT6261 chipset itself.
### Where was information collected from?
There were three main sources of information: [mtk-open-tools](https://github.com/mtek-hack-hack/mtk-open-tools), [platform-quectel](https://github.com/Wiz-IO/platform-quectel/blob/master/builder/frameworks/MT6261.py) and - most importantly - my own research of FlashTool (running on a VM) USB traffic dumps necessary to combine the above sources, streamline them and make them work on real phone targets, not developer boards. Making the phone load the DA correctly was one thing but complete absence of understanding what to do next and figuring out the protocol to talk to DA itself was another challenge altogether.
There were several main sources of information: [mtk-open-tools](https://github.com/mtek-hack-hack/mtk-open-tools), [platform-quectel](https://github.com/Wiz-IO/platform-quectel/blob/master/builder/frameworks/MT6261.py), [Fernly](https://github.com/xobs/fernly) and - most importantly - my own research of FlashTool (running on a VM) USB traffic dumps necessary to combine the above sources, streamline them and make them work on real phone targets, not developer boards.
### Will there be other chipset support?
Most probably, no. MT6261 is the simplest to implement because it uses 2-stage DA, while most other MediaTeks use 4 stages. However, the implementation is as straightforward and hackable as possible, so it shouldn't be a problem to add two other stages and thus other chipset support if absolutely necessary.
Most probably, no, but you may try.
### Are there any plans to support flashing in addition to readbacks?
No. Not in this utility. Flashing MediaTek SoCs via USB is much more complicated than dumping. The process depends on the kind of partitions we're trying to flash, is generally quite fragile, relies on some proprietary, internal and undocumented logic, and in total requires much more research and rigorous testing on different devices with potential risk of bricking them to an unflashable state. When such research is complete, another utility will be published.
No. Not in this utility. Flashing MediaTek SoCs via USB is much more complicated than dumping. The process is generally quite fragile, relies on more proprietary, internal and undocumented logic, and in total requires much more research and rigorous testing on different devices with potential risk of bricking them to an unflashable state. When such research is complete, another utility will be published.