Help, I bricked my A1

jonsmirl

I messed up my flash by writing in an image that was larger than the partition, doing that messed up the partitions.  I was able to successfully flash the phone before I did this.

BTW -- I was trying to debug why USB AOA audio is not working.

I'm following the instructions for the A1 and using SP Flash Tool. No matter what I do I can not get past this error -- STATUS_DA_HASH_MISMATCH.   Googling around says this may be caused by the image file not having checksums generated in it. Can anyone give me a clue how to get past this error?

There error is listed on this page, but I can't get past it.
https://forum.hovatek.com/thread-439.html

Error 0xC0070004

Message: ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004)

Meaning: Hash (integrity) check of the images being flashed failed.

Solution: (this does not work for A1)
Use SP Flash Tool V5.1516.00
Ensure to select the right Download-Agent
Navigate to Options > Option > Download and untick DA DLL All.....

jonsmirl

Obviously I damaged something important, when my file was too big it overwrote stuff in the next partition.  Looks like I destroyed the NVRAM partition.

Do I have to have a cert file to be able to recover this? There is no cert file in the image download.

MarcinP

jonsmirl replied at 2018-7-30 00:03
Obviously I damaged something important, when my file was too big it overwrote stuff in the next par ...

Please use SPFT and flash with firmware upgrade option, if this doesn't help please use format + download, this will wipe you IMEI numbers and fingerprint activation file. If you restore your system then you can follow tutorial to restore IMEI numbers and generate file for fingerprint activation.
Here you will find all tutorials
http://community.umidigi.com/for ... ;fid=190&page=1

jonsmirl

I  tried format+download, no success. This phone is for software development, no big deal about fingerprint and IMEI.
From Windows I get the STATUS_DA_HASH_MISMATCH error.
From Linux I see this...

jonsmirl@ares:~/Downloads/SP_Flash_Tool_v5.1828_Linux$ ./flash_tool.sh
QGtkStyle was unable to detect the current GTK+ theme.
QObject::connect: Cannot queue arguments of type 'FLASHTOOL_API_HANDLE_T'
(Make sure 'FLASHTOOL_API_HANDLE_T' is registered using qRegisterMetaType().)
QObject::moveToThread: Cannot move objects with a parent
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
remove@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0

open VID device failed!

unbind@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1

unbind@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0

remove@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0

add@/devices/pci0000:00/0000:00:14.0/usb1/1-2

add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0

add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0

vid is 0e8d

device vid = 0e8d

pid is 0003

device pid = 0003

com portName is: /dev/ttyACM0

Total wait time = -1532899816.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
DA Connected
Format Succeeded.
Format Succeeded.
Format Succeeded.
executing DADownloadAll...
Download failed.
Disconnect!

jonsmirl

Is this a problem? Is it not initializing the DRAM?

connect DA end stage: 2, enable DRAM in 1st DA: 0

I'm using the MTK_AllInOne_DA.bin that came with SPFT

jonsmirl

I tried version 1824 and it gets a little further....

Total wait time = -1532901700.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
DA Connected
Format Succeeded.
Format Succeeded.
Format Succeeded.
Format Succeeded.
executing DADownloadAll...
Stage: SGPT
Download failed.
Disconnect!

jonsmirl

My best guess right now is that SP_Flash_Tool_v5.1828 is unable to initialize the DRAM in the A1. If you have an intact bootloader this is not an issue since the bootloader can initialize it, but I appear to have lost my bootloader.

jonsmirl

I finally recovered it via Windows.  I'm not 100% sure what I did. But one step was to use checksum_gen on the scatter file. Another step may have been to start SPFT first in download mode and then plug the phone in instead of using the power button.

MarcinP

jonsmirl replied at 2018-7-30 12:32
I finally recovered it via Windows.  I'm not 100% sure what I did. But one step was to use checksum_ ...

Are you using original ROM?
http://community.umidigi.com/for ... d=195&mobile=no
Bootloader is in each ROM so everything still should be fine.
Anyway you can firstly flash preloader and then rest of partitions.

jonsmirl

Original ROM.  The problems I encountered seem to be from the SP_Flash tool having trouble with this phone (or the MT6739) The failures were very early in the boot process - like at the preloader stage. I have the original ROM back in it now. The only tool that I know works is SP_Flash 1828 on Windows. None of my Linux versions work.

I have three MT6737 devices here. Using the same tools I can format and do a full download with zero problems. A1 is my only MT6739 device.