qmobile S6S, CM2 Read file failure

chacha

Active Member
Sep 9, 2017
56
15
Pakistan
hello CM2

i am tierd of seeing read file failure by cm2, it seems this tool is getting useless, you should solve this issue or if we are doing something wrong, you must make tutorial to teach us how to use and get rid of errors

here is the log

Operation : Read Flash [ v1.58 ]

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

Wait for phone...
Phone found! [ 10 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x94
NAND Flash : NOT INSTALLED
eMMC Flash : 150100514531334D420D95589B1A24CF
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM31E
[eMMC] : FLASH_CID : 150100514531334D420D95589B1A24CF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0x0544B048EAB54E08B60C40369BAEB5D8
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

Reading Flash Content now ...

xGPT : Normalize settings Ok!

Brand : QMobile
ProdName : QMobile_S6S
ProdModel : QMobile S6S
Device : QMobile_S6S
AndroidVer: 6.0
MTKxCPU : MT6580
MTKxPRJ : alps-mp-m0.mp1-V2.34_rgk6580.we.m

[Read Ok] : preloader_d5171_qmobile_s8_e1.bin
[Read Ok] : lk.bin
Fatal error, buffer empty! Phone connection lost???
Error while reading block! Something went wrong :(

Read error :(

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

Huzaifa Nafees

Friend's Martview
Oct 25, 2016
483
563
Rawalpindi
Skype
huzaifanafees1122
Bhai Change the cable connection problem hai set ko read karty howay
Operation : Read Flash [ v1.58 ]

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

Wait for phone...
Phone found! [ 4 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x94
NAND Flash : NOT INSTALLED
eMMC Flash : 150100514531334D4207CFA8DA2F93E3
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM31E
[eMMC] : FLASH_CID : 150100514531334D4207CFA8DA2F93E3
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0xA860A7468447A503AA2B3654CC0CFDFF
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

Reading Flash Content now ...

xGPT : Normalize settings Ok!

Brand : QMobile
ProdName : QMobile_S6S
ProdModel : QMobile S6S
Device : QMobile_S6S
AndroidVer: 6.0
MTKxCPU : MT6580
MTKxPRJ : alps-mp-m0.mp1-V2.34_rgk6580.we.m

[Read Ok] : preloader_d5171_qmobile_s8_e1.bin
[Read Ok] : lk.bin
[Read Ok] : boot.img
[Read Ok] : recovery.img
[Read Ok] : logo.bin
[Read Ok] : secro.img
[Read Ok] : system.img
[Read Ok] : cache.img
[Read Ok] : userdata.img

[ScatCFG] : MT6580 / V1.1.2 / d5171_qmobile_s8_e1 / EMMC
Android Info saved
MAUI Meta DB saved
HWConfig Info saved
FW Size : 2958 MiB
Scatter saved to : D:\MT6580__QMobile__QMobile_S6S__QMobile_S6S__6.0__alps-mp-m0.mp1-V2.34_rgk6580.we.m\

All done!

Done!
Elapsed: 00:12:14
Reconnect Power/Cable!

 
  • Like
Reactions: chacha

chacha

Active Member
Sep 9, 2017
56
15
Pakistan
Bhai Change the cable connection problem hai set ko read karty howay
Operation : Read Flash [ v1.58 ]

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

Wait for phone...
Phone found! [ 4 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x94
NAND Flash : NOT INSTALLED
eMMC Flash : 150100514531334D4207CFA8DA2F93E3
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM31E
[eMMC] : FLASH_CID : 150100514531334D4207CFA8DA2F93E3
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0xA860A7468447A503AA2B3654CC0CFDFF
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

Reading Flash Content now ...

xGPT : Normalize settings Ok!

Brand : QMobile
ProdName : QMobile_S6S
ProdModel : QMobile S6S
Device : QMobile_S6S
AndroidVer: 6.0
MTKxCPU : MT6580
MTKxPRJ : alps-mp-m0.mp1-V2.34_rgk6580.we.m

[Read Ok] : preloader_d5171_qmobile_s8_e1.bin
[Read Ok] : lk.bin
[Read Ok] : boot.img
[Read Ok] : recovery.img
[Read Ok] : logo.bin
[Read Ok] : secro.img
[Read Ok] : system.img
[Read Ok] : cache.img
[Read Ok] : userdata.img

[ScatCFG] : MT6580 / V1.1.2 / d5171_qmobile_s8_e1 / EMMC
Android Info saved
MAUI Meta DB saved
HWConfig Info saved
FW Size : 2958 MiB
Scatter saved to : D:\MT6580__QMobile__QMobile_S6S__QMobile_S6S__6.0__alps-mp-m0.mp1-V2.34_rgk6580.we.m\

All done!

Done!
Elapsed: 00:12:14
Reconnect Power/Cable!
bhai 4 cables change ke , bar bar try kia er her bar same error ata raha, file bhe upload kar dain , :)
 
  • Like
Reactions: KHAN JAN

Bilal Khan

Friend's Martview
Jun 10, 2017
915
1,246
karachi
hello CM2

i am tierd of seeing read file failure by cm2, it seems this tool is getting useless, you should solve this issue or if we are doing something wrong, you must make tutorial to teach us how to use and get rid of errors

here is the log

Operation : Read Flash [ v1.58 ]

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

Wait for phone...
Phone found! [ 10 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x94
NAND Flash : NOT INSTALLED
eMMC Flash : 150100514531334D420D95589B1A24CF
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM31E
[eMMC] : FLASH_CID : 150100514531334D420D95589B1A24CF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0x0544B048EAB54E08B60C40369BAEB5D8
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

Reading Flash Content now ...

xGPT : Normalize settings Ok!

Brand : QMobile
ProdName : QMobile_S6S
ProdModel : QMobile S6S
Device : QMobile_S6S
AndroidVer: 6.0
MTKxCPU : MT6580
MTKxPRJ : alps-mp-m0.mp1-V2.34_rgk6580.we.m

[Read Ok] : preloader_d5171_qmobile_s8_e1.bin
[Read Ok] : lk.bin
Fatal error, buffer empty! Phone connection lost???
Error while reading block! Something went wrong :(

Read error :(

Operation Failed
Elapsed: 00:00:42
Reconnect Power/Cable!
It may Battery Issue or Charging jig otherwise change port

Sent from my Fire Phone using Tapatalk
 

nobichanmaruf

Friend's Martview
Mar 19, 2017
222
585
Bangladesh
Skype
nobichanmaruf
Sonork ID
100.1672479
hello CM2

i am tierd of seeing read file failure by cm2, it seems this tool is getting useless, you should solve this issue or if we are doing something wrong, you must make tutorial to teach us how to use and get rid of errors

here is the log

Operation : Read Flash [ v1.58 ]

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

Wait for phone...
Phone found! [ 10 ]
Sync...
Inital Boot Ok!
BB_CPU_PID : 6580
BB_CPU_NME : [MediaTek] MT6580_S00
BB_CPU_EXT : 0xCA00 , 0x8A00 , 0x0000
Processing BROM stage
Settings for BROM configured!
SecCfgVal : 0x00000000
BromVer : 0x00FF
BLVersion : 0x0001
PreLoader : Active [ Boot with PL ]
BootLdrSS : NORMAL with PRELOADER
Processing DA stage
DA Select done, will use MTK_AllInOne_DA_v5.1624.16.07
Sending and initialize DA ...
Running DA ver.4.2 on BBID : 0x94
NAND Flash : NOT INSTALLED
eMMC Flash : 150100514531334D420D95589B1A24CF
Initialize Memory ...
DRAM already initialized by Preloader
DAgent sent , init HW now
eMMC FlashIC initialized
[eMMC] : FLASH_VEN : 0x15 , OEM : 0100
[eMMC] : FLASH_INF : [SAMSUNG] , BM31E
[eMMC] : FLASH_CID : 150100514531334D420D95589B1A24CF
[eMMC] : FLASH_BRT : 0x00400000 , 0x00400000 , 0x00400000
[eMMC] : FLASH_LEN : 0x00000003A3E00000
[eMMC] : FLASH_UCP : 14910 MiB [eMMC 16 GiB]
DEV RID : 0x0544B048EAB54E08B60C40369BAEB5D8
INT RAM : 0x00020000
EXT RAM : 0x80000000 [2 GiB]
BOOT TYPE : EMMC_FLASH_BOOT
SOC VERIFY : C1
Boot Ok!

Reading Flash Content now ...

xGPT : Normalize settings Ok!

Brand : QMobile
ProdName : QMobile_S6S
ProdModel : QMobile S6S
Device : QMobile_S6S
AndroidVer: 6.0
MTKxCPU : MT6580
MTKxPRJ : alps-mp-m0.mp1-V2.34_rgk6580.we.m

[Read Ok] : preloader_d5171_qmobile_s8_e1.bin
[Read Ok] : lk.bin
Fatal error, buffer empty! Phone connection lost???
Error while reading block! Something went wrong :(

Read error :(

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

Disable Your Antivirus And Change Frimware Backup Drive Folder Location And Battery I Thik Solved your problem And Always Use English Laguage Its Internation Forum Ok
 
Last edited:

chacha

Active Member
Sep 9, 2017
56
15
Pakistan
Disable Your Antivirus And Change Frimware Backup Drive Folder Location And Battery I Thik Solved your problem And Always Use English Laguage Its Internation Forum Ok
first i dont have any anti virus, second i tried with different saving locations, and tried different cables, battery , yes that i didnt fully charged or changed, and i always use english, the only time i used urdu was cuz the other guy used urdu, so i had to reply back in urdu, :)
 
  • Like
Reactions: nobichanmaruf

Bilal Khan

Friend's Martview
Jun 10, 2017
915
1,246
karachi
first i dont have any anti virus, second i tried with different saving locations, and tried different cables, battery , yes that i didnt fully charged or changed, and i always use english, the only time i used urdu was cuz the other guy used urdu, so i had to reply back in urdu, :)
Change your charging jig otherwise if someone is breaking rules then you should to tell him right

Sent from my Fire Phone using Tapatalk
 

Bilal Khan

Friend's Martview
Jun 10, 2017
915
1,246
karachi
thanks but No bro it is not charging jig problem, today i tried to read flash of qmobile i6i but it also failed, i use windows 10, maybe it is not compatible or some other issue
May be. Uninstall and reinstall mtk module.
Sometime when i read scatter file and i get error during creating scatter file so i always reinstall mtk module... Success

Sent from my Fire Phone using Tapatalk
 
  • Like
Reactions: nobichanmaruf

scorpian1982

Active Member
Dec 30, 2016
36
5
Pakistan
this is not cable or mobile problem, this problem is from CM2 end & now a days mostly people facing this problem even me too. . . i have face this error several time & on same time same mobile same PC i have try to make backup with other tools it's done and solution is use any other mtk tool to take back.
 
  • Like
Reactions: nobichanmaruf

Bilal Khan

Friend's Martview
Jun 10, 2017
915
1,246
karachi
this is not cable or mobile problem, this problem is from CM2 end & now a days mostly people facing this problem even me too. . . i have face this error several time & on same time same mobile same PC i have try to make backup with other tools it's done and solution is use any other mtk tool to take back.
Next time if u face Same error then reinstall mtk module... Other tool is not the sollution

Sent from my Fire Phone using Tapatalk
 
  • Like
Reactions: nobichanmaruf

Naveed Zeeshan

Friend's Martview
Jun 6, 2017
539
1,299
Riparazione cellulari, Corso Libertà, 172, 13100
Skype
zeeshanhaneef2010
PayPal:

Donate money to this user
BROTHER DONT PANIC HERE IS YOUR SOLUTION
JUST INSTALL THAT DRIVER PROBLEM SOLVE I M FACING THAT EROR
Fatal error, buffer empty! Phone connection lost???
EVEN I INSTALL FRESH WINDOW
WHEN I WILL READ NOKIA 3 FIRMWARE ITS NOT CABLE ISSUE BRO OR OTHER COZ LATEST BUILD OS SECURITY MUST BE PATCH WITH NEW DRIVER SIGNATURE
AFTER INSTALL THESE DRIVER MUST BE RESTART PC
MTK USB All v1.0.8 - Official Website
MUST BE POST LOG INSHALAW WILL READ DONE
IF NOT COME LETS TV ID
 

Naveed Zeeshan

Friend's Martview
Jun 6, 2017
539
1,299
Riparazione cellulari, Corso Libertà, 172, 13100
Skype
zeeshanhaneef2010
PayPal:

Donate money to this user
 
Top