GT-i9190 MTK6572 - GSM-Forum

abdoune · 10-21-2014, 12:08

First phone touch screen dont work, i format it but steel same condition, then i decid to flash it , i have made a full backup and also second backup on adb mode, phone information is below :
Chip : MTK
Chip Details : MT6589
Software Version : ALPS.JB3.MP.V1.8
Android Version : 4.2.2
GSM Base Band : MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/07 10:44
Manufacturer : alps
Brand : alps
Model : GT-I9190
Product Name : mtk6589_wet_lca
Version Info : Linux version 3.4.5 (whl@server0-br) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Mar 12 14:16:39 CST 2014
----------------------------------
flash it wth 9190_MTK-6572-S4-Mini
found on ROM MTK6572 S4 Mini ? CPU ? 1.3 CHZ -1350 MB RAM | [Official] add the 12/02/2013 on Needrom
but phone wont power i decide to restore fullbackup with volcano but unfortunately volcano didn't restore the full backup always stop on read info and didn't write recovery backup , also i try to flash the second backup with sp flash tool also cant flash it
any suggestion are welcom
Salam

javaflasher · 10-21-2014, 14:34

your chip details is MT6589 and you flash it with chip rom MT6572!! welldone superb!!

well try this for MT6589 Chip ROm !Files_to_FlashTool

good luck!!!

abdoune · 10-21-2014, 14:46

as you see in image can't write full backup readed by volcano.....then waht's the utility to backup flash files if we we can't restore it
salam

abdoune · 10-21-2014, 14:52

Quote:

Originally Posted by javaflasher

your chip details is MT6589 and you flash it with chip rom MT6572!! welldone superb!!

well try this for MT6589 Chip ROm !Files_to_FlashTool

good luck!!!

thank you i'm verry confused in adb mode volcano detect the gt-i9190 as mtk6589 and in fullbackup detected as mtk6572 as you see in capture image
any way i will upload file and i'will give you response
salam

abdoune · 10-21-2014, 16:40

Quote:

Originally Posted by javaflasher

your chip details is MT6589 and you flash it with chip rom MT6572!! welldone superb!!

well try this for MT6589 Chip ROm !Files_to_FlashTool

good luck!!!

with your file i have error message : s_type_not_match
Salam

sweet4hamza · 10-21-2014, 19:18

it make me mad
i did not understand how can you write mtk 6589 chip base phone file on 6572
as volcano show you have 6572 chip inside phone
so it can not write 6589 based file
you must write 6572 phone file

abdoune · 10-21-2014, 19:52

Quote:

Originally Posted by sweet4hamza

it make me mad
i did not understand how can you write mtk 6589 chip base phone file on 6572
as volcano show you have 6572 chip inside phone
so it can not write 6589 based file
you must write 6572 phone file

first when phone power on but touch screen not work volcano program in adb mode detect it as MTK6589 i have made backup and i have scatter file and InfoFile.info.txt just see attached files
Salam

AniAxn · 10-21-2014, 22:10

Hello ..

I think you doing any mistakes ...
First you know with confirm which chip inside your Phone ...
Then find & write Proper File ...
Or If you Do Bin format Read/Write ...
You must need to Use Latest Volcano Android Tool ..

Wbr,
AniAXN

abdoune · 10-22-2014, 00:24

Quote:

Originally Posted by AniAxn

Hello ..

I think you doing any mistakes ...
First you know with confirm which chip inside your Phone ...
Then find & write Proper File ...
Or If you Do Bin format Read/Write ...
You must need to Use Latest Volcano Android Tool ..

Wbr,
AniAXN

until now view of attached files that i posted in above message are empty then how you can respond me without verifying analysing the situation just see the attached files .....
I repeat in volcano program -android- Adb mode phone is detected as MTK6589 but in Mtk Tab it detected as MTK6572 (see in attached pic) is it my mistack ...just in this post Javaflasher guess thats an MYK6589 and you MTK6572 who is right
Salam

Faisal_Computer · 10-22-2014, 07:39

Hi, can you please open your phone and check inside what cpu inside ?
by the way. it's really strange.
Br
Faisal_Computer

abdoune · 10-22-2014, 19:19

can't open the crapy chinese phone cause sticker is glued ...
but please see well images that i have post and txt files attached above you will inderstand well the situation
Salam

abdoune · 10-22-2014, 19:27

In MTK tab phone detection is below:

2014-10-19 15:30:15 >>Connecting...
2014-10-19 15:30:15 >>Connecting...
2014-10-19 15:30:15 >>CPU TYPE:6572
2014-10-19 15:30:15 >>CPU TYPE:6572
2014-10-19 15:30:15 >>Hardware version:CA01
2014-10-19 15:30:15 >>Hardware version:CA01
2014-10-19 15:30:15 >>Software version:0000
2014-10-19 15:30:15 >>Software version:0000
2014-10-19 15:30:15 >>Boot downloading...
2014-10-19 15:30:15 >>Boot downloading...
2014-10-19 15:30:30 >>EMMC_ID:0x1501004E3958524D42007A953E81C047
2014-10-19 15:30:30 >>EMMC_ID:0x1501004E3958524D42007A953E81C047
2014-10-19 15:30:30 >>EMMC_PRODUCT_NAME: SAMSUNG :0x4E3958524D42
2014-10-19 15:30:30 >>EMMC_PRODUCT_NAME: SAMSUNG :0x4E3958524D42
2014-10-19 15:30:30 >>EMMC_BOOT1_SIZE: 0x000200000
2014-10-19 15:30:30 >>EMMC_BOOT1_SIZE: 0x000200000
2014-10-19 15:30:30 >>EMMC_BOOT2_SIZE: 0x000200000
2014-10-19 15:30:30 >>EMMC_BOOT2_SIZE: 0x000200000
2014-10-19 15:30:30 >>EMMC_PRMB_SIZE: 0x000020000
2014-10-19 15:30:30 >>EMMC_PRMB_SIZE: 0x000020000
2014-10-19 15:30:30 >>EMMC_GP1_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP1_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP2_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP2_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP3_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP3_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP4_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_GP4_SIZE: 0x000000000
2014-10-19 15:30:30 >>EMMC_USER_SIZE: 0x070000000
2014-10-19 15:30:30 >>EMMC_USER_SIZE: 0x070000000
2014-10-19 15:30:30 >>
2014-10-19 15:30:30 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>Analysis of system files...
2014-10-19 15:30:31 >>Analysis of system files...
2014-10-19 15:30:31 >>PRELOADER:>>addr:0x000000 --length:0x600000
2014-10-19 15:30:31 >>PRELOADER:>>addr:0x000000 --length:0x600000
2014-10-19 15:30:31 >>MBR:>>addr:0x600000 --length:0x080000
2014-10-19 15:30:31 >>MBR:>>addr:0x600000 --length:0x080000
2014-10-19 15:30:31 >>EBR1:>>addr:0x680000 --length:0x080000
2014-10-19 15:30:31 >>EBR1:>>addr:0x680000 --length:0x080000
2014-10-19 15:30:31 >>PRO_INFO:>>addr:0x700000 --length:0x300000
2014-10-19 15:30:31 >>PRO_INFO:>>addr:0x700000 --length:0x300000
2014-10-19 15:30:31 >>NVRAM:>>addr:0xA00000 --length:0x500000
2014-10-19 15:30:31 >>NVRAM:>>addr:0xA00000 --length:0x500000
2014-10-19 15:30:31 >>PROTECT_F:>>addr:0xF00000 --length:0xA00000
2014-10-19 15:30:31 >>PROTECT_F:>>addr:0xF00000 --length:0xA00000
2014-10-19 15:30:31 >>PROTECT_S:>>addr:0x1900000 --length:0xA00000
2014-10-19 15:30:31 >>PROTECT_S:>>addr:0x1900000 --length:0xA00000
2014-10-19 15:30:31 >>SECCFG:>>addr:0x2300000 --length:0x020000
2014-10-19 15:30:31 >>SECCFG:>>addr:0x2300000 --length:0x020000
2014-10-19 15:30:31 >>UBOOT:>>addr:0x2320000 --length:0x060000
2014-10-19 15:30:31 >>UBOOT:>>addr:0x2320000 --length:0x060000
2014-10-19 15:30:31 >>BOOTIMG:>>addr:0x2380000 --length:0x600000
2014-10-19 15:30:31 >>BOOTIMG:>>addr:0x2380000 --length:0x600000
2014-10-19 15:30:31 >>RECOVERY:>>addr:0x2980000 --length:0x600000
2014-10-19 15:30:31 >>RECOVERY:>>addr:0x2980000 --length:0x600000
2014-10-19 15:30:31 >>SEC_RO:>>addr:0x2F80000 --length:0x040000
2014-10-19 15:30:31 >>SEC_RO:>>addr:0x2F80000 --length:0x040000
2014-10-19 15:30:31 >>MISC:>>addr:0x2FC0000 --length:0x080000
2014-10-19 15:30:31 >>MISC:>>addr:0x2FC0000 --length:0x080000
2014-10-19 15:30:31 >>LOGO:>>addr:0x3040000 --length:0x300000
2014-10-19 15:30:31 >>LOGO:>>addr:0x3040000 --length:0x300000
2014-10-19 15:30:31 >>EXPDB:>>addr:0x3340000 --length:0xA00000
2014-10-19 15:30:31 >>EXPDB:>>addr:0x3340000 --length:0xA00000
2014-10-19 15:30:31 >>ANDROID:>>addr:0x3D40000 --length:0x1CC00000
2014-10-19 15:30:31 >>ANDROID:>>addr:0x3D40000 --length:0x1CC00000
2014-10-19 15:30:31 >>CACHE:>>addr:0x20940000 --length:0x700000
2014-10-19 15:30:31 >>CACHE:>>addr:0x20940000 --length:0x700000
2014-10-19 15:30:31 >>USRDATA:>>addr:0x21040000 --length:0x15E00000
2014-10-19 15:30:31 >>USRDATA:>>addr:0x21040000 --length:0x15E00000
2014-10-19 15:30:31 >>FAT:>>addr:0x36E40000 --length:0x380E0000
2014-10-19 15:30:31 >>FAT:>>addr:0x36E40000 --length:0x380E0000
2014-10-19 15:30:31 >>BMTPOOL:>>addr:0xFFFF00A8 --length:0x000000
2014-10-19 15:30:31 >>BMTPOOL:>>addr:0xFFFF00A8 --length:0x000000
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>
2014-10-19 15:30:31 >>>>Format addr:0x25040000 --Format length:0x11E00000
2014-10-19 15:30:31 >>>>Format addr:0x25040000 --Format length:0x11E00000
2014-10-19 15:30:31 >>Read phone information success.
2014-10-19 15:30:31 >>Read phone information success.
Salam

abdoune · 10-22-2014, 19:46

But in Volcano ADB mode phone detected as MTK6589 , just see in txt attached files
any way now phone wont power on , i have the fullflash readed by volcano but can't write it have also bkp with adb that i can write it by sp flash tool now need coorect frmware to flash it
Salam

abdoune · 10-22-2014, 21:00

trying to flash with s4 mini i9190 1350mb ram Mtk6572 but error on sp flash tool

S_FT_ENABLE_DRAM_FAIL (4032)
(EMI) ENABLE DRAM FAILED

Salam

abdoune · 10-22-2014, 21:10

trying to flash with s4 mini i9190 1350mb ram Mtk6572 but error on sp flash tool

S_FT_ENABLE_DRAM_FAIL (4032)
(EMI) ENABLE DRAM FAILED

Salam

10-21-2014, 12:08	#1 (permalink)
abdoune No Life Poster Join Date: Feb 2004 Location: Algeria Posts: 2,305 Member: 56090 Status: Offline Thanks Meter: 162	GT-i9190 MTK6572 First phone touch screen dont work, i format it but steel same condition, then i decid to flash it , i have made a full backup and also second backup on adb mode, phone information is below : Chip : MTK Chip Details : MT6589 Software Version : ALPS.JB3.MP.V1.8 Android Version : 4.2.2 GSM Base Band : MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/07 10:44 Manufacturer : alps Brand : alps Model : GT-I9190 Product Name : mtk6589_wet_lca Version Info : Linux version 3.4.5 (whl@server0-br) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Mar 12 14:16:39 CST 2014 ---------------------------------- flash it wth 9190_MTK-6572-S4-Mini found on ROM MTK6572 S4 Mini ? CPU ? 1.3 CHZ -1350 MB RAM \| [Official] add the 12/02/2013 on Needrom but phone wont power i decide to restore fullbackup with volcano but unfortunately volcano didn't restore the full backup always stop on read info and didn't write recovery backup , also i try to flash the second backup with sp flash tool also cant flash it any suggestion are welcom Salam Last edited by abdoune; 10-21-2014 at 12:15.

10-21-2014, 14:34	#2 (permalink)
javaflasher Freak Poster Join Date: Mar 2013 Posts: 450 Member: 1892139 Status: Offline Thanks Meter: 56	your chip details is MT6589 and you flash it with chip rom MT6572!! welldone superb!! well try this for MT6589 Chip ROm !Files_to_FlashTool good luck!!!

10-21-2014, 19:18	#6 (permalink)
sweet4hamza No Life Poster Join Date: Nov 2010 Location: Atif mobile,goal, faisalabad Posts: 12,041 Member: 1434736 Status: Offline Sonork: 100.1607275 Thanks Meter: 5,377	it make me mad i did not understand how can you write mtk 6589 chip base phone file on 6572 as volcano show you have 6572 chip inside phone so it can not write 6589 based file you must write 6572 phone file

10-21-2014, 22:10	#8 (permalink)
AniAxn Product Supporter Join Date: Jun 2009 Location: eMMC & UFS Posts: 4,600 Member: 1045758 Status: Offline Sonork: 100.1613661(Offline) Thanks Meter: 4,307	Hello .. I think you doing any mistakes ... First you know with confirm which chip inside your Phone ... Then find & write Proper File ... Or If you Do Bin format Read/Write ... You must need to Use Latest Volcano Android Tool .. Wbr, AniAXN

10-22-2014, 07:39	#10 (permalink)
Faisal_Computer No Life Poster Join Date: Jun 2005 Location: Kamalia, Pakistan. Age: 38 Posts: 16,852 Member: 151871 Status: Offline Thanks Meter: 71,421	Hi, can you please open your phone and check inside what cpu inside ? by the way. it's really strange. Br Faisal_Computer

10-22-2014, 19:19	#11 (permalink)
abdoune No Life Poster Join Date: Feb 2004 Location: Algeria Posts: 2,305 Member: 56090 Status: Offline Thanks Meter: 162	can't open the crapy chinese phone cause sticker is glued ... but please see well images that i have post and txt files attached above you will inderstand well the situation Salam

10-22-2014, 19:27	#12 (permalink)
abdoune No Life Poster Join Date: Feb 2004 Location: Algeria Posts: 2,305 Member: 56090 Status: Offline Thanks Meter: 162	In MTK tab phone detection is below: 2014-10-19 15:30:15 >>Connecting... 2014-10-19 15:30:15 >>Connecting... 2014-10-19 15:30:15 >>CPU TYPE:6572 2014-10-19 15:30:15 >>CPU TYPE:6572 2014-10-19 15:30:15 >>Hardware version:CA01 2014-10-19 15:30:15 >>Hardware version:CA01 2014-10-19 15:30:15 >>Software version:0000 2014-10-19 15:30:15 >>Software version:0000 2014-10-19 15:30:15 >>Boot downloading... 2014-10-19 15:30:15 >>Boot downloading... 2014-10-19 15:30:30 >>EMMC_ID:0x1501004E3958524D42007A953E81C047 2014-10-19 15:30:30 >>EMMC_ID:0x1501004E3958524D42007A953E81C047 2014-10-19 15:30:30 >>EMMC_PRODUCT_NAME: SAMSUNG :0x4E3958524D42 2014-10-19 15:30:30 >>EMMC_PRODUCT_NAME: SAMSUNG :0x4E3958524D42 2014-10-19 15:30:30 >>EMMC_BOOT1_SIZE: 0x000200000 2014-10-19 15:30:30 >>EMMC_BOOT1_SIZE: 0x000200000 2014-10-19 15:30:30 >>EMMC_BOOT2_SIZE: 0x000200000 2014-10-19 15:30:30 >>EMMC_BOOT2_SIZE: 0x000200000 2014-10-19 15:30:30 >>EMMC_PRMB_SIZE: 0x000020000 2014-10-19 15:30:30 >>EMMC_PRMB_SIZE: 0x000020000 2014-10-19 15:30:30 >>EMMC_GP1_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP1_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP2_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP2_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP3_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP3_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP4_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_GP4_SIZE: 0x000000000 2014-10-19 15:30:30 >>EMMC_USER_SIZE: 0x070000000 2014-10-19 15:30:30 >>EMMC_USER_SIZE: 0x070000000 2014-10-19 15:30:30 >> 2014-10-19 15:30:30 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >>Analysis of system files... 2014-10-19 15:30:31 >>Analysis of system files... 2014-10-19 15:30:31 >>PRELOADER:>>addr:0x000000 --length:0x600000 2014-10-19 15:30:31 >>PRELOADER:>>addr:0x000000 --length:0x600000 2014-10-19 15:30:31 >>MBR:>>addr:0x600000 --length:0x080000 2014-10-19 15:30:31 >>MBR:>>addr:0x600000 --length:0x080000 2014-10-19 15:30:31 >>EBR1:>>addr:0x680000 --length:0x080000 2014-10-19 15:30:31 >>EBR1:>>addr:0x680000 --length:0x080000 2014-10-19 15:30:31 >>PRO_INFO:>>addr:0x700000 --length:0x300000 2014-10-19 15:30:31 >>PRO_INFO:>>addr:0x700000 --length:0x300000 2014-10-19 15:30:31 >>NVRAM:>>addr:0xA00000 --length:0x500000 2014-10-19 15:30:31 >>NVRAM:>>addr:0xA00000 --length:0x500000 2014-10-19 15:30:31 >>PROTECT_F:>>addr:0xF00000 --length:0xA00000 2014-10-19 15:30:31 >>PROTECT_F:>>addr:0xF00000 --length:0xA00000 2014-10-19 15:30:31 >>PROTECT_S:>>addr:0x1900000 --length:0xA00000 2014-10-19 15:30:31 >>PROTECT_S:>>addr:0x1900000 --length:0xA00000 2014-10-19 15:30:31 >>SECCFG:>>addr:0x2300000 --length:0x020000 2014-10-19 15:30:31 >>SECCFG:>>addr:0x2300000 --length:0x020000 2014-10-19 15:30:31 >>UBOOT:>>addr:0x2320000 --length:0x060000 2014-10-19 15:30:31 >>UBOOT:>>addr:0x2320000 --length:0x060000 2014-10-19 15:30:31 >>BOOTIMG:>>addr:0x2380000 --length:0x600000 2014-10-19 15:30:31 >>BOOTIMG:>>addr:0x2380000 --length:0x600000 2014-10-19 15:30:31 >>RECOVERY:>>addr:0x2980000 --length:0x600000 2014-10-19 15:30:31 >>RECOVERY:>>addr:0x2980000 --length:0x600000 2014-10-19 15:30:31 >>SEC_RO:>>addr:0x2F80000 --length:0x040000 2014-10-19 15:30:31 >>SEC_RO:>>addr:0x2F80000 --length:0x040000 2014-10-19 15:30:31 >>MISC:>>addr:0x2FC0000 --length:0x080000 2014-10-19 15:30:31 >>MISC:>>addr:0x2FC0000 --length:0x080000 2014-10-19 15:30:31 >>LOGO:>>addr:0x3040000 --length:0x300000 2014-10-19 15:30:31 >>LOGO:>>addr:0x3040000 --length:0x300000 2014-10-19 15:30:31 >>EXPDB:>>addr:0x3340000 --length:0xA00000 2014-10-19 15:30:31 >>EXPDB:>>addr:0x3340000 --length:0xA00000 2014-10-19 15:30:31 >>ANDROID:>>addr:0x3D40000 --length:0x1CC00000 2014-10-19 15:30:31 >>ANDROID:>>addr:0x3D40000 --length:0x1CC00000 2014-10-19 15:30:31 >>CACHE:>>addr:0x20940000 --length:0x700000 2014-10-19 15:30:31 >>CACHE:>>addr:0x20940000 --length:0x700000 2014-10-19 15:30:31 >>USRDATA:>>addr:0x21040000 --length:0x15E00000 2014-10-19 15:30:31 >>USRDATA:>>addr:0x21040000 --length:0x15E00000 2014-10-19 15:30:31 >>FAT:>>addr:0x36E40000 --length:0x380E0000 2014-10-19 15:30:31 >>FAT:>>addr:0x36E40000 --length:0x380E0000 2014-10-19 15:30:31 >>BMTPOOL:>>addr:0xFFFF00A8 --length:0x000000 2014-10-19 15:30:31 >>BMTPOOL:>>addr:0xFFFF00A8 --length:0x000000 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >> 2014-10-19 15:30:31 >>>>Format addr:0x25040000 --Format length:0x11E00000 2014-10-19 15:30:31 >>>>Format addr:0x25040000 --Format length:0x11E00000 2014-10-19 15:30:31 >>Read phone information success. 2014-10-19 15:30:31 >>Read phone information success. Salam

10-22-2014, 19:46	#13 (permalink)
abdoune No Life Poster Join Date: Feb 2004 Location: Algeria Posts: 2,305 Member: 56090 Status: Offline Thanks Meter: 162	But in Volcano ADB mode phone detected as MTK6589 , just see in txt attached files any way now phone wont power on , i have the fullflash readed by volcano but can't write it have also bkp with adb that i can write it by sp flash tool now need coorect frmware to flash it Salam

10-22-2014, 21:10	#15 (permalink)
abdoune No Life Poster Join Date: Feb 2004 Location: Algeria Posts: 2,305 Member: 56090 Status: Offline Thanks Meter: 162	trying to flash with s4 mini i9190 1350mb ram Mtk6572 but error on sp flash tool S_FT_ENABLE_DRAM_FAIL (4032) (EMI) ENABLE DRAM FAILED Salam