K330 eMMC to LS675 question [Answered] - GSM-Forum

pomgrapes · 05-04-2018, 11:32

I have a lg ls675 that has a bad emmc and i have donor boards of lg k330 that work fine except they have touch problems from the board if i removed the emmc from the k330 board and erased it and wrote the latest lg ls675 firmware that i have in hand which is ZVA will i be able to get the ls675 to work just fine or will there be problems? thae emmc are both the same type i already removed both no difference at all.
thank you very much

pomgrapes · 05-04-2018, 11:36

Quote:

Originally Posted by pomgrapes

I have a lg ls675 that has a bad emmc and i have donor boards of lg k330 that work fine except they have touch problems from the board if i removed the emmc from the k330 board and erased it and wrote the latest lg ls675 firmware that i have in hand which is ZVA will i be able to get the ls675 to work just fine or will there be problems? thae emmc are both the same type i already removed both no difference at all.
thank you very much

also will i be able to do the same process with different types of phones i have a lot of boards that are gsm that are donor boards and cdma boards that have emmc problems same emmc and same board just different network and the main network in my country is cdma so i would be better of getting the cdma boards to work. and if it is possible what process do i use to get them to work.
Is it first erase the emmc then write the firmware of the phone that i want to fix or something else that i have to do?
thanks

Medusa Box · 05-04-2018, 11:49

Hello.

At first connect both of eMMC from K330 and LS675 and post here full Software log with the connecting info, we will check. Also, if the connection will be success, read out Full flash from both eMMC chips. Probably, your "bad" eMMC can be connected and full flash can be read out.

pomgrapes · 05-04-2018, 13:28

Quote:

Originally Posted by Medusa Box

Hello.

At first connect both of eMMC from K330 and LS675 and post here full Software log with the connecting info, we will check. Also, if the connection will be success, read out Full flash from both eMMC chips. Probably, your "bad" eMMC can be connected and full flash can be read out.

Model Settings:
Interface : eMMC
Brand : LG
Model : LS675
SRF : C:/Program Files (x86)/Octoplus Pro JTAG Software/firmwareFolder/LG_LS675_EMMC.srf
Voltage : 2.4V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Hynix eMMC H8G1e
Page size : 512 B
Block size : 512 B
Block count : 15269888
Size : 7.28 GB (7456.00 MB)
---------------------------------------------------------------
CID Info

CID : 90014A4838473165050756903CEEC25F
Manufacturer ID : 0X90
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X4A
Product name : H8G1e
Product revision : 0.7
Product serial number : (hex) 56903CEE
Manufacturing date : 12/2015
---------------------------------------------------------------
CSD Info

CSD : D02701320F5903FFFFFFFFEF8A4040D3
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
4.51, 5.0, 5.01, 5.1
Data read access time1: 15 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.7 (for MMC v5.0, v5.01)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x00) 00000000
Boot partition enable : Device not boot enabled (default)
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)

RST_n function : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 3817472 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b

---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------
Backup EXT_CSD saved to file C:/Program Files (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/H8G1e_02_05_2018_18_29_02.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.5.5; FW: 1.23.
Please select file.
Remove write protect successfully completed.
Disconnected.

Please disconnect battery and USB cable.

Model Settings:
Interface : eMMC
Brand : LG
Model : LS675
SRF : C:/Program Files (x86)/Octoplus Pro JTAG Software/firmwareFolder/LG_LS675_EMMC.srf
Voltage : 2.4V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Hynix eMMC H8G1e
Page size : 512 B
Block size : 512 B
Block count : 15269888
Size : 7.28 GB (7456.00 MB)
---------------------------------------------------------------
CID Info

CID : 90014A4838473165050756903CEEC25F
Manufacturer ID : 0X90
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X4A
Product name : H8G1e
Product revision : 0.7
Product serial number : (hex) 56903CEE
Manufacturing date : 12/2015
---------------------------------------------------------------
CSD Info

CSD : D02701320F5903FFFFFFFFEF8A4040D3
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
4.51, 5.0, 5.01, 5.1
Data read access time1: 15 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.7 (for MMC v5.0, v5.01)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x00) 00000000
Boot partition enable : Device not boot enabled (default)
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)

RST_n function : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 3817472 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b

---------------------------------------------------------------Searching Android build info...
Not found
---------------------------------------------------------------
Backup EXT_CSD saved to file C:/Program Files (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/H8G1e_02_05_2018_18_29_20.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.5.5; FW: 1.23.
Opening C:/Users/HASHHASH/Desktop/LS675ZVA_07.tot file...
Signature OK.
Signature 2 OK.
Open file "C:/Users/HASHHASH/Desktop/LS675ZVA_07.tot".
Write data verification is enabled.
Writing. Please wait...
Writing partition PrimaryGPT...
Read/write verification error. Possible reasons: damaged or write protected eMMC.
Disconnected.

log for ls 675

Medusa Box · 05-04-2018, 13:31

OK, now connect working eMMC of K330 and post here log.

pomgrapes · 05-04-2018, 13:46

Quote:

Originally Posted by Medusa Box

OK, now connect working eMMC of K330 and post here log.

Welcome to Octoplus Pro JTAG Software version 1.5.5. Started.
Reader #0: Generic EMV Smartcard Reader 0

Please disconnect battery and USB cable.

Model Settings:
Interface : eMMC
Voltage : 1.8V
Bus Mode : 1 bit
Bus speed : Auto

Connecting...
Device : Hynix eMMC H8G1e
Page size : 512 B
Block size : 512 B
Block count : 15269888
Size : 7.28 GB (7456.00 MB)
---------------------------------------------------------------
CID Info

CID : 90014A4838473165050703037513C2A7
Manufacturer ID : 0X90
Device/BGA : BGA (Discrete embedded)
OEM/Application ID : 0X4A
Product name : H8G1e
Product revision : 0.7
Product serial number : (hex) 3037513
Manufacturing date : 12/2015
---------------------------------------------------------------
CSD Info

CSD : D02701320F5903FFFFFFFFEF8A4040D3
CSD structure : CSD version No. 1.2
SPEC version : 4.1, 4.2, 4.3, 4.4, 4.41, 4.5,
4.51, 5.0, 5.01, 5.1
Data read access time1: 15 ms
TRAN speed : 26 MHz
READ block length : 512 Bytes
WP group enable : YES
PERM_WRITE_PROTECT : NO
TMP_WRITE_PROTECT : NO
---------------------------------------------------------------
EXTCSD Info

Revision 1.7 (for MMC v5.0, v5.01)
Erase block size : 512 Kbytes
Boot1 size : 4096 Kbytes
Boot2 size : 4096 Kbytes
RPMB size : 4096 Kbytes

Partition config : (0x00) 00000000
Boot partition enable : Device not boot enabled (default)
(Bus width = 1Bit)
Boot ACK : No boot acknowledge sent (default)

Boot bus conditions : (0x00) 00000000
Boot bus width : x1 (sdr) or x4 (ddr) bus width in boot operation mode (default)
Reset boot bus conditions : Reset bus width to x1, single data rate and backward compatible timings after boot operation (default)
Boot mode : Use single data rate + backward compatible timings in boot operation (default)

RST_n function : (0x01) RST_n signal is permanently enabled

Partitioning support : Device supports partitioning features
Enhanced attribute : Device can have enhanced technological features in partitions and user data area.
Max enhanced data size: 3817472 Kbytes
Partitions attribute : 0x0
Part setting completed: 0x0
GP partition 1 size : 0 b
GP partition 2 size : 0 b
GP partition 3 size : 0 b
GP partition 4 size : 0 b
Enhanced area size : (0x0) 0 b
Enhanced area start : (0x0) 0 b

---------------------------------------------------------------Searching Android build info...
Ok

Disk/Image size : d2000000 bytes
Device sector size : 512 bytes
Partition offset : 442368
Number of sectors : 4931584
Device Manufacturer :MetroPCS
Device Platform :msm8909
Build ID :LMY47V
Display Build ID :LMY47V
Release ID :5.1.1
Device Model :LGMS330
Device Name :m1_mpcs_us
Architecture ABI :armeabi-v7a
Architecture ABI2 :armeabi
Architecture ABI List :armeabi-v7a,armeabi
Build Description :m1_mpcs_us-user 5.1.1 LMY47V 153571544a5ad release-keys

Backup EXT_CSD saved to file C:/Program Files (x86)/Octoplus Pro JTAG Software/EXT_CSD Backups/H8G1e_04_05_2018_15_45_42.bin.
Connect successful.
---------------------------------------------------------------
SW: 1.5.5; FW: 1.23.
P00: GPT (00000000, 00004000) 8 MB
P01: modem (00004000, 00020000) 64 MB
P02: sbl1 (00024000, 00000400) 512 KB
P03: tz (00024400, 00000800) 1024 KB
P04: rpm (00024C00, 00000400) 512 KB
P05: aboot (00025000, 00001000) 2048 KB
P06: sbl1bak (00026000, 00000400) 512 KB
P07: tzbak (00026400, 00000800) 1024 KB
P08: rpmbak (00026C00, 00000400) 512 KB
P09: abootbak (00027000, 00001000) 2048 KB
P10: modemst1 (00028000, 00000C00) 1536 KB
P11: modemst2 (00028C00, 00000C00) 1536 KB
P12: ssd (00029800, 00000400) 512 KB
P13: DDR (00029C00, 00000400) 512 KB
P14: fsg (0002A000, 00000C00) 1536 KB
P15: fsc (0002AC00, 00000400) 512 KB
P16: sec (0002B000, 00000400) 512 KB
P17: keystore (0002B400, 00000400) 512 KB
P18: encrypt (0002B800, 00000400) 512 KB
P19: eksst (0002BC00, 00000400) 512 KB
P20: devinfo (0002C000, 00000800) 1024 KB
P21: config (0002C800, 00000400) 512 KB
P22: spare1 (0002CC00, 00003400) 6.5 MB
P23: fota (00030000, 00003000) 6 MB
P24: rct (00033000, 00000400) 512 KB
P25: spare2 (00033400, 00000C00) 1536 KB
P26: raw_resources (00034000, 00000800) 1024 KB
P27: raw_resourcesbak (00034800, 00000800) 1024 KB
P28: drm (00035000, 00003000) 6 MB
P29: sns (00038000, 00003000) 6 MB
P30: misc (0003B000, 00005000) 10 MB
P31: persist (00040000, 00004000) 8 MB
P32: laf (00044000, 00008000) 16 MB
P33: boot (0004C000, 00008000) 16 MB
P34: recovery (00054000, 00008000) 16 MB
P35: factory (0005C000, 0000C000) 24 MB
P36: mpt (00068000, 00004000) 8 MB
P37: system (0006C000, 004B4000) 2408 MB
P38: cache (00520000, 00064000) 200 MB
P39: userdata (00584000, 00908000) 4.516 GB
P40: grow (00E8C000, 00003FDF) 7.984 MB

Medusa Box · 05-04-2018, 13:57

As I see from your Software logs, necessary eMMC settings of your working eMMC chip is the same as on damaged eMMC, so You can try to do "Factory Repair" using your firmware ZVA, which You have. But note, if your "dead" LS675 device earlier had higher firmware version than ZVA before it became "dead", this will be not possible to repair it using ZVA firmware. If this case, You need to use higher (than ZVA) firmware version (or write full flash from the working LS775 with higher firmware version).

pomgrapes · 05-04-2018, 14:01

Quote:

Originally Posted by Medusa Box

As I see from your Software logs, necessary eMMC settings of your working eMMC chip is the same as on damaged eMMC, so You can try to do "Factory Repair" using your firmware ZVA, which You have. But note, if your "dead" LS675 device earlier had higher firmware version than ZVA before it became "dead", this will be not possible to repair it using ZVA firmware. If this case, You need to use higher (than ZVA) firmware version (or write full flash from the working LS775 with higher firmware version).

no it had zv5 firmware on it

pomgrapes · 05-04-2018, 14:02

so do i first erase the chip then write the firmware using factory repair or dont erase it at all

Medusa Box · 05-04-2018, 14:10

Try to do repair without erasing.

pomgrapes · 05-04-2018, 15:01

i repaired it when the emmc was not on the board i soldered it to the board now its connecting as qhusb should i repair it when its connected to the board again and erase everything before repairing or what ? thanks

Medusa Box · 05-05-2018, 08:13

This doesn't matter, whether You repair eMMC directly or via ISP connection (when eMMC is on PCB). At first, check, whether You have soldered eMMC chip correctly on PCB. Also try to repair it again, try to do erase (not format) before repairing. Post here the result.

05-04-2018, 11:32	#1 (permalink)
pomgrapes Freak Poster Join Date: Oct 2017 Posts: 214 Member: 2773088 Status: Offline Thanks Meter: 24	K330 eMMC to LS675 question [Answered] I have a lg ls675 that has a bad emmc and i have donor boards of lg k330 that work fine except they have touch problems from the board if i removed the emmc from the k330 board and erased it and wrote the latest lg ls675 firmware that i have in hand which is ZVA will i be able to get the ls675 to work just fine or will there be problems? thae emmc are both the same type i already removed both no difference at all. thank you very much Last edited by Medusa Box; 05-04-2018 at 11:50.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

05-04-2018, 11:49	#3 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,397	Hello. At first connect both of eMMC from K330 and LS675 and post here full Software log with the connecting info, we will check. Also, if the connection will be success, read out Full flash from both eMMC chips. Probably, your "bad" eMMC can be connected and full flash can be read out.

05-04-2018, 13:31	#5 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,397	OK, now connect working eMMC of K330 and post here log.

05-04-2018, 13:57	#7 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,397	As I see from your Software logs, necessary eMMC settings of your working eMMC chip is the same as on damaged eMMC, so You can try to do "Factory Repair" using your firmware ZVA, which You have. But note, if your "dead" LS675 device earlier had higher firmware version than ZVA before it became "dead", this will be not possible to repair it using ZVA firmware. If this case, You need to use higher (than ZVA) firmware version (or write full flash from the working LS775 with higher firmware version).

05-04-2018, 14:02	#9 (permalink)
pomgrapes Freak Poster Join Date: Oct 2017 Posts: 214 Member: 2773088 Status: Offline Thanks Meter: 24	so do i first erase the chip then write the firmware using factory repair or dont erase it at all

05-04-2018, 14:10	#10 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,397	Try to do repair without erasing.

05-04-2018, 15:01	#11 (permalink)
pomgrapes Freak Poster Join Date: Oct 2017 Posts: 214 Member: 2773088 Status: Offline Thanks Meter: 24	i repaired it when the emmc was not on the board i soldered it to the board now its connecting as qhusb should i repair it when its connected to the board again and erase everything before repairing or what ? thanks

05-05-2018, 08:13	#12 (permalink)
Medusa Box Product Supporter Join Date: Mar 2011 Location: Octopus-team Posts: 9,360 Member: 1538383 Status: Offline Sonork: 100.1587278 Thanks Meter: 3,397	This doesn't matter, whether You repair eMMC directly or via ISP connection (when eMMC is on PCB). At first, check, whether You have soldered eMMC chip correctly on PCB. Also try to repair it again, try to do erase (not format) before repairing. Post here the result.