CM2MTK strange error - GSM-Forum

debeliamark · 06-09-2015, 11:13

Someone killed this phone - do not know how, but with original FW canot be reveved:

Here is the log from phone with 4Gb eMMC connected without battery and volume down pressed / same and with battery also /:

Code:

Card found: S/N 0714:0xx8
Chinese Miracle II  [MTK module] v 1.21

Scatter Load Ok , BaseBand : MT6589 , Project : MTK6589 , Storage : eMMC
Files found : 13 , Set to Flash : 12
Ready to Flash!

Operation : Flash [ v1.21 ]

======= Flash
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey

Wait for phone...
Phone found! [ 69 ]
Sync...
Inital regs read done
Boot Info : 
BB_CPU_ID : 6583
BB_CPU_HW : CA01
BB_CPU_SW : 8A00
BB_CPU_SB : 0001
BB_CPU_NM : [MediaTek] MT6583|6589_S00
Processing BROM stage
SecCfgVal : 0x00000000
BromVersion : 0x05
BLVersion : 0xFE
Preloader Status : Not active (Erased)
Processing DA stage
DA Select done , sending 
NAND_ID : 00000000000000000000000000000000
eMMC_ID : 4D6F6465524F4D200600464EE3000000
DA Stat : v3.2 on BBID : 0x86
DRAM not initialized , configure DRAM Settings
DRAM EmiReq Ok , 0x00B8

Error : DA init Failed! Error code : 0x5
LErr : EMICFG_NOT_FOUND

Boot Error!

Operation Failed
Elapsed: 00:00:03
Reconnect Power/Cable!

JayDi · 06-09-2015, 11:27

Hello. DA sends as eMMC info "ROMMode" message , which not belongs to eMMC CID data.
Something wrong with eMMC , seems. If possible - need check HW and know more about phone manipulations history.

debeliamark · 06-09-2015, 12:35

well - i will take out stupid 4Gb eMMC - H9TP32A8JDMC - to read it on EasyJTAG eMMC addon to see where is the problem with it ... so it's possible to write Android Parts by defined in scater addresses and lenght direct on eMMC socket wiith EasyJTAG ?

JayDi · 06-09-2015, 13:01

Better just write whole dump from same phone.
If via scatter - it uses shift addres (old scat format used in 6583/89) for block 0 preloader data must be with EMMCBOOT magic block ( there is not enough just write preloader , need first 800 (or something like that) bytes from this. Can be used any from same MT6583/89) , 40000 - next block and e.t.c. ...
Boot region, used in those MTK - is BOOT_1 , if not wrong and all rest data inside it.

After writing all parts - if eMMC is alive ( not sure in that ) - it should power on.

You can check if emmc is alive by trying write/read something from it and check crc of data.

debeliamark · 06-09-2015, 17:34

eMMC is totaly dead ... just 2 Gb size and no ROM-s 2 and 3 partitions ... must find another one

JayDi · 06-09-2015, 17:56

Yeah, as expected - it dead. I planning add in some of next versions simple detection of bad/emmc problems. It not a 100% results, but can help well in some cases.

debeliamark · 06-09-2015, 18:07

Quote:

Originally Posted by JayDi

Yeah, as expected - it dead. I planning add in some of next versions simple detection of bad/emmc problems. It not a 100% results, but can help well in some cases.

In any case i saw that MTK CPU can handle eMMC like mass storage very well and is easy to put full image(s) in eMMC partitions, even avoid EasyJTAG connection, but here opposite to Samsung's eMMC this one hynix cannot be repaired ( reflash controller FW ) ... so - will get another one from some Nuvi device or from some Lenovo P780 - they have a lot of them with damaged RF IC - a so bad developed and produced phones with so big market share - cannot believe that peoples still want to buy it.

JayDi · 06-09-2015, 18:20

Need to make sure about FW for this phone ( preloader ) support new eMMC chip , due ComboMemory compatibility restrictions.

As far, as know - hynix have ability to upgrade fw , but it in private yet. So - maybe, they will be repairable in future.

debeliamark · 06-10-2015, 05:12

Quote:

Originally Posted by JayDi

...
As far, as know - hynix have ability to upgrade fw , but it in private yet. So - maybe, they will be repairable in future.

Sounds good, just to not drop all damaged eMMC in trash ( like VTU000M in past ) . Hope will be not so late about.

Will write results when i find a good same eMMC in try to repair stupid Lenovo, hope all will have a happy end.

debeliamark · 06-11-2015, 09:00

After eMMC change flashing work:

Code:

Card found: S/N 0714:0xx8
Chinese Miracle II  [MTK module] v 1.21

Scatter Load Ok , BaseBand : MT6589 , Project : MTK6589 , Storage : eMMC
Files found : 14 , Set to Flash : 13
Ready to Flash!

Operation : Flash [ v1.21 ]

======= Flash
1. Power Off Phone , Remove battery , Insert back
2. Insert USB cable. In some cases require hold BootKey

Wait for phone...
Phone found! [ 38 ]
Sync...
Inital regs read done
Boot Info : 
BB_CPU_ID : 6583
BB_CPU_HW : CA01
BB_CPU_SW : 8A00
BB_CPU_SB : 0001
BB_CPU_NM : [MediaTek] MT6583|6589_S00
Processing BROM stage
SecCfgVal : 0x00000000
BromVersion : 0x05
BLVersion : 0xFE
Preloader Status : Not active (Erased)
Processing DA stage
DA Select done , sending 
NAND_ID : 00000000000000000000000000000000
eMMC_ID : 204A0190594E4958CFA116489B40CDE7
DA Stat : v3.2 on BBID : 0x86
DRAM not initialized , configure DRAM Settings
DRAM EmiReq Ok , 0x00B8
DRAM Init Ok , 0x40000000
DA Sent. Configure setting now ... 
DA started successuflly
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0090 , OEM : 014A
[eMMC] : FLASH_INF : HYNIX
[eMMC] : FLASH_CID : 90014A2058494E594816A1CFE7CD409B
[eMMC] : FLASH_LEN : 0x00000000E7000000
INT RAM    : 0x00020000
EXT RAM    : 0x40000000
BOOT TYPE  : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

ScatCFG : BaseBand : MT6589 , Project : MTK6589 , Storage : eMMC
Setting : Flash Pre-Erase (Safe) : Enabled
Setting : AFF verify :  Enabled

Switching to HSUSB
HSUSB Init Ok
BL : Check HW compatibility
BL : BBID supported by BootLoader!
BL : Check eMMC compatibility
BL : eMMC supported by BootLoader!

BL : Flash Pre-Erase
Total blocks to Erase : 2
Erase : 0x0000000000600000-0x0000000000100000
Erase : 0x0000000002720000-0x000000008B11C000
Flash Pre-Erase Done, time used : 00:00:06

SecCfg Passed , 1799
BMT remark not need. Will skip
Sending Preloader ... 
Use : preloader_s820_row.bin
Preloader Sent , Init passed
SecCfg Passed , 1799
PartCount : FFFFFFFF
PartErr : Not initialized , will update PMT now ... 
Repartition Done!

Processing : Flash Write
Flash now : MBR
Image Flash Ok
Flash now : EBR1
Image Flash Ok
Flash now : UBOOT
Image Flash Ok
Flash now : BOOTIMG
Image Flash Ok
Flash now : RECOVERY
Image Flash Ok
Flash now : SEC_RO
Image Flash Ok
Flash now : PRELOAD
Image Flash Ok
Flash now : LOGO
Image Flash Ok
Flash now : EBR2
Image Flash Ok
Flash now : ANDROID
Image Flash Ok
Flash now : CACHE
Image Flash Ok
Flash now : USRDATA
Image Flash Ok
Flash now : FAT
Image Flash Ok
Flash Write Done, time used : 00:04:24

Processing : Verify
Verify Passed : MBR
Verify Passed : EBR1
Verify Passed : UBOOT
Verify Passed : BOOTIMG
Verify Passed : RECOVERY
Verify Passed : SEC_RO
Verify Error! Something went wrong!
ErrCode : 0xA345

Done!
Elapsed: 00:05:00
Reconnect Power/Cable!

But ...

Phone stay on logo with small words in low left corner :

=> TOOL DL Image fail!
=> uboot is blocking by dl info

and after half minute reboots till same screen.

Forcing to enter Factory mode ( volume up + power on ) or Meta Mode ( volume down + poower on ) do not make anything ( just a sentences "Have been in ..." )

Brrrr....

Some hint?

debeliamark · 06-11-2015, 09:55

Will be good if someone can readout one full dump from working phone

debeliamark · 06-11-2015, 10:40

Quote:

Originally Posted by debeliamark

...

=> TOOL DL Image fail!
=> uboot is blocking by dl info
...

Flashing with SPFlashtool and checked DA DL all with Check sum ... solve this problem

***MyGSM World*** · 06-11-2015, 11:50

Quote:

Originally Posted by debeliamark

After eMMC change flashing work:

But ...

Phone stay on logo with small words in low left corner :

=> TOOL DL Image fail!
=> uboot is blocking by dl info

and after half minute reboots till same screen.

Forcing to enter Factory mode ( volume up + power on ) or Meta Mode ( volume down + poower on ) do not make anything ( just a sentences "Have been in ..." )

Brrrr....

Some hint?

Dear Friend,

Already Infinity Have Solution For "Fix DL" Button In Service Tab.

You Can Solve This Error By Single Click Without Flashing.

http://forum.gsmhosting.com/vbb/11088143-post8.html

JayDi · 06-11-2015, 12:42

@debeliamark, please, send me "PRELOAD" file from this fw for check it and fix that thing.

06-09-2015, 11:27	#2 (permalink)
JayDi No Life Poster Join Date: Mar 2007 Location: Where you live Posts: 18,542 Member: 462970 Status: Offline Thanks Meter: 20,352	Hello. DA sends as eMMC info "ROMMode" message , which not belongs to eMMC CID data. Something wrong with eMMC , seems. If possible - need check HW and know more about phone manipulations history.

06-09-2015, 12:35	#3 (permalink)
debeliamark No Life Poster Join Date: May 2001 Location: Bulgaria Age: 56 Posts: 4,796 Member: 4627 Status: Offline Sonork: 57528:debeliamark Thanks Meter: 1,034	well - i will take out stupid 4Gb eMMC - H9TP32A8JDMC - to read it on EasyJTAG eMMC addon to see where is the problem with it ... so it's possible to write Android Parts by defined in scater addresses and lenght direct on eMMC socket wiith EasyJTAG ?

06-09-2015, 13:01	#4 (permalink)
JayDi No Life Poster Join Date: Mar 2007 Location: Where you live Posts: 18,542 Member: 462970 Status: Offline Thanks Meter: 20,352	Better just write whole dump from same phone. If via scatter - it uses shift addres (old scat format used in 6583/89) for block 0 preloader data must be with EMMCBOOT magic block ( there is not enough just write preloader , need first 800 (or something like that) bytes from this. Can be used any from same MT6583/89) , 40000 - next block and e.t.c. ... Boot region, used in those MTK - is BOOT_1 , if not wrong and all rest data inside it. After writing all parts - if eMMC is alive ( not sure in that ) - it should power on. You can check if emmc is alive by trying write/read something from it and check crc of data.

06-09-2015, 17:56	#6 (permalink)
JayDi No Life Poster Join Date: Mar 2007 Location: Where you live Posts: 18,542 Member: 462970 Status: Offline Thanks Meter: 20,352	Yeah, as expected - it dead. I planning add in some of next versions simple detection of bad/emmc problems. It not a 100% results, but can help well in some cases.

06-09-2015, 18:20	#8 (permalink)
JayDi No Life Poster Join Date: Mar 2007 Location: Where you live Posts: 18,542 Member: 462970 Status: Offline Thanks Meter: 20,352	Need to make sure about FW for this phone ( preloader ) support new eMMC chip , due ComboMemory compatibility restrictions. As far, as know - hynix have ability to upgrade fw , but it in private yet. So - maybe, they will be repairable in future.

06-11-2015, 09:55	#11 (permalink)
debeliamark No Life Poster Join Date: May 2001 Location: Bulgaria Age: 56 Posts: 4,796 Member: 4627 Status: Offline Sonork: 57528:debeliamark Thanks Meter: 1,034	Will be good if someone can readout one full dump from working phone

06-11-2015, 12:42	#14 (permalink)
JayDi No Life Poster Join Date: Mar 2007 Location: Where you live Posts: 18,542 Member: 462970 Status: Offline Thanks Meter: 20,352	@debeliamark, please, send me "PRELOAD" file from this fw for check it and fix that thing.