GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Easy-Jtag

Reply
 
LinkBack Thread Tools Display Modes
Old 01-14-2019, 18:09   #1 (permalink)
Junior Member
 
Join Date: Oct 2017
Posts: 29
Member: 2772222
Status: Offline
Thanks Meter: 2
LG K430TV write ROM2 (Boot) from Firmware


was trying Flash LG K430TV, but process fail. Now is recognized MediaTek.
I did the Pinout an tried Connect with Easy JTag, buts says tha eMMc is DEAD.

I dont know whats happened to eMMC die during flash. I think de firmware of eMMC was dameged . What coud have been?

So I removed eMMC chip. I am using another eMMC, KMQE10013M.
Original was KMF310012M.

I will try repair using ROM from K430TV. My friend give me EXTCSD for this device.

Log:
eMMC CID : 150100514531334D4207A04FE0BD433F
eMMC CSD : D02701320F5903FFF6DBFFEF8E40400D
eMMC Manufacturer ID: 0015 , OEM ID: 0100
eMMC Date: 04/2016 Rev.0x7
eMMC NAME: QE13MB , S/N: 2689589437
eMMC NAME (HEX): 514531334D42
EMMC ROM1 (Main User Data) Capacity: 14910 MB
EMMC ROM2 (Boot Partition 1) Capacity: 4096 kB
EMMC ROM3 (Boot Partition 2) Capacity: 4096 kB
EMMC RPMB (Replay Protected Memory Block) Capacity: 4096 kB
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
EMMC Password Locked: No
Extended CSD rev 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG: 0x48] Boot from:ROM2 (Boot Partition 1)
Boot bus config [177]: 0x00 , width 1bit , Partition config [179]: 0x48.
H/W reset function [RST_N_FUNCTION]: 0x01
High-capacity WP group size [HC_WP_GRP_SIZE: 0x00004000]
Partitioning Support [PARTITIONING_SUPPORT]: 0x07
Device support partitioning feature
Device can have enhanced tech.
Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00


Boot from:ROM2 (Boot Partition 1): How can I write ROM2 (Boot partiton) from Firmware?
  Reply With Quote
Old 01-14-2019, 18:51   #2 (permalink)
Product Supporter
 
Join Date: Jun 2002
Location: Belarus
Age: 42
Posts: 776
Member: 13148
Status: Online
Thanks Meter: 736
Quote:
Originally Posted by JefMaximo View Post
So I removed eMMC chip. I am using another eMMC, KMQE10013M.
Original was KMF310012M.

I will try repair using ROM from K430TV. My friend give me EXTCSD for this device.


Boot from:ROM2 (Boot Partition 1): How can I write ROM2 (Boot partiton) from Firmware?
You need run "preloader pareser" at "Utilites" tab to view list of supported eMMC by preloader.

MTK CPU based phones have bootconfig depended where is preloader placed:

if preloader write to ROM2 boot config is: Boot configuration [179] / Boot Bus Config [177] / H/W Reset Function [162]: 0x48 / 0x00 / 0x01

if preloader write to ROM3 boot config is: Boot configuration [179] / Boot Bus Config [177] / H/W Reset Function [162]: 0x50 / 0x00 / 0x01


there is no difference where the preloader is.
it is important that the bootconfig points to it

you can write ROM2 as backup of ROM2 at first page (eMMC general) - Select ROM to access, select file, write binary file

you can write preloader file to ROM from FlashTool firmware - you need open firmware at "Write by vendor" tab, select Mediatek, choose scatter file, select partititon to write, write it

Last edited by layder; 01-14-2019 at 18:57.
  Reply With Quote
The Following User Says Thank You to layder For This Useful Post:
Old 01-14-2019, 19:24   #3 (permalink)
Junior Member
 
Join Date: Oct 2017
Posts: 29
Member: 2772222
Status: Offline
Thanks Meter: 2
How to interpret it:

preloader_0_1.bin
Found 10 supported eMMC CID:
name = 'HAG2e' hex = 0x484147326505 [SKHYNIX]
eNAND_H26M52103FMR/16GB @FBGA169
eNAND_H9TQ17A8GTMCUR-KTM/16GB @BGA221
eNAND_H9TQ17A8GTMCUR-KUM/16GB @BGA221
eNAND_H9TQ17ABJTMCUR-KTM/16GB @BGA221
eNAND_H9TQ17ABJTMCUR-KUM/16GB @BGA221
name = 'QN16MB' hex = 0x514E31364D42 [SAMSUNG]
name = 'Q316AB' hex = 0x513331364142 [SAMSUNG]
name = 'Q313MB' hex = 0x513331334D42 [SAMSUNG]
moviNAND_KMQ310013M-B419/16GB @BGA221
name = 'F312MB' hex = 0x463331324D42 [SAMSUNG]
name = 'F722MB' hex = 0x463732324D42 [SAMSUNG]
moviNAND_KMF720012M-B214/8GB @BGA221
name = 'Q31SMB' hex = 0x513331534D42 [SAMSUNG]
name = 'QE13MB' hex = 0x514531334D42 [SAMSUNG]
name = 'Q316BB' hex = 0x513331364242 [SAMSUNG]
name = 'FE12MB' hex = 0x464531324D42 [SAMSUNG]

"you can write ROM2 as backup of ROM2 at first page (eMMC general) - Select ROM to access, select file, write binary file"

But I dont have DUMP.

I will read about the function of preloader to understand the process.
  Reply With Quote
Old 01-14-2019, 23:06   #4 (permalink)
Product Supporter
 
Join Date: Jun 2002
Location: Belarus
Age: 42
Posts: 776
Member: 13148
Status: Online
Thanks Meter: 736
Quote:
Originally Posted by JefMaximo View Post
How to interpret it:

preloader_0_1.bin
Found 10 supported eMMC CID:
name = 'HAG2e' hex = 0x484147326505 [SKHYNIX]
name = 'QN16MB' hex = 0x514E31364D42 [SAMSUNG]
name = 'Q316AB' hex = 0x513331364142 [SAMSUNG]
name = 'Q313MB' hex = 0x513331334D42 [SAMSUNG]
name = 'F312MB' hex = 0x463331324D42 [SAMSUNG]
name = 'F722MB' hex = 0x463732324D42 [SAMSUNG]
name = 'Q31SMB' hex = 0x513331534D42 [SAMSUNG]
name = 'QE13MB' hex = 0x514531334D42 [SAMSUNG]
name = 'Q316BB' hex = 0x513331364242 [SAMSUNG]
name = 'FE12MB' hex = 0x464531324D42 [SAMSUNG]

"you can write ROM2 as backup of ROM2 at first page (eMMC general) - Select ROM to access, select file, write binary file"

But I dont have DUMP.

I will read about the function of preloader to understand the process.
If you not have dump, you can write firmware to phone with mediatek CPU via FlashTool

If you phone not connect as "MTK VCOM port", you need to desolder eMMC and check it, and write correct preloader from firmware using "Write by vendor" Tab at EasyJTAG plus software, also know as "eMMC Tool Shuite"
  Reply With Quote
The Following User Says Thank You to layder For This Useful Post:
Old 01-15-2019, 23:17   #5 (permalink)
Junior Member
 
Join Date: Oct 2017
Posts: 29
Member: 2772222
Status: Offline
Thanks Meter: 2
So if I flash using "Write by Vendor" from DKZ file i don't need write ROM2-3?
Rom2-3 will be write from KZD file?
  Reply With Quote
Old 01-16-2019, 02:18   #6 (permalink)
Product Supporter
 
Join Date: Jun 2002
Location: Belarus
Age: 42
Posts: 776
Member: 13148
Status: Online
Thanks Meter: 736
Quote:
Originally Posted by JefMaximo View Post
So if I flash using "Write by Vendor" from DKZ file i don't need write ROM2-3?
Rom2-3 will be write from KZD file?
if you hover over a row in a table, you can see that the preloader is written to ROM2
  Reply With Quote
The Following User Says Thank You to layder For This Useful Post:
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 15:53.



Powered by Searchlight © 2019 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2017 -
Page generated in 0.31748 seconds with 7 queries

SEO by vBSEO