SM-J700F after repair beeot still dad - GSM-Forum

shahidshan40 · 01-12-2017, 12:05

im using 6.0.1 file sboot+cm but phone still dad

================================================== ====
================================================== ====
eMMC Test Point Connection Module
================================================== ====
================================================== ====

1. DO NOT USE THE PHONE"S BATTERY
2. Connect the Soldered TP Connections to ATF Box
3. Disconnect the USB Cable and Wait until the
the ATF Software will tell you to Connect the USB.

Interface Reset OK!
eMMC Access Type: SECTOR MODE
eMMC Supported Voltage Range:
3.5-3.6V, 3.4-3.5V, 3.3-3.4V, 3.2-3.3V, 3.1-3.2V
3.0-3.1V, 2.9-3.0V, 2.8-2.9V, 2.7-2.8V, 1.9-2.0V

CID : 11010034303030373300B389988EA2D3
CSD : D07E00320F5903FFFFFFFFE78A4000D1

eMMC Boot Information
Revision 1.7 (for MMC v5.0, v5.01)
BOOT PARTITION : BOOT PARTITION 1
PARTITION ACCESS : R/W USER PARTITION
PERM_BOOT_CFG_PROT : DISABLED
PWR_BOOT_CFG_PROT : DISABLED
BOOT MODE : x4 SINGLE DATA RATE + LOW SPEED
RESET BUS WIDTH : ENABLED
eMMC FirmW UPDATE : DISABLED
EMMC CACHE SIZE : 0 KB
SUPER PAGE SIZE : 4096 KB
HC ERASE GROUP SIZE: 4096 KB
USER AREA SIZE : 15758000128 BYTES
BOOT PARTITION SIZE: 4096 KB
RPMB PARTITION SIZE: 4096 KB

eMMC Device Information
Manufacturer ID: TOSHIBA
Device Type : Embedded BGA
Application ID : 00
Product Name : 400073
Product Rev : 0.0
Product SN : B389988E
Manufactured : January 1999

Card Specific Data
CSD_STRUCTURE : Extended
SPEC_VERS : Version 4.1/4.2/4.3
TAAC : 8000 ns
TRAN_SPEED : 4000000 KHz
READ_BL_LEN : 512 Bytes
C_SIZE : HIGH CAPACITY
WP_GRP_ENABLE : YES
WRITE_BL_LEN : 512 Bytes
CONTENT_PROT_APP : NO
PERM_WRITE_PROTECT: NO
TMP_WRITE_PROTECT : NO

Extended CSD Saved:
11010034303030373300B389988EA2D3.ext_csd
Backup Directory:
C:\AdvanceBox Turbo Flasher\eMMC\EXT_CSD\

Start Writing Flash Images...

Flash Image: sboot.bin
Start Writing 0x00002000 Blocks at 0x00000000
Partition Selected: BOOT 1

Total Elapsed Time 00:00:04
Write Success!

Flash Image: cm.bin
Start Writing 0x00002000 Blocks at 0x00000000
Partition Selected: BOOT 2

Total Elapsed Time 00:00:04
Write Success!

Total Images Written: 2
Process Done!

**chand_gee** · 01-15-2017, 03:06

@shahidshan40
If you write md5 file and still dead...

Then it is dead because version you write is still OLDER than version on phone before it was killed.

How is this possible???

Because not all firmware is released. Possible you killed phone with very new firmware inside. And you just wanted to put other Language Pack inside or tried to cross-flash the
phone with different model.

All you can do is wait wait wait until sa.mmob.ile or other sources will release a newer
version that will repair your phone.

Do not cross flash.
Do not use old firmware.

If phone still dead, then do not be surprised. The reason is very very simple why it is dead.
Version you write is old. That is it. No need to keep asking forum why phone is still dead.
Come on, you guys know phone died because you flashed it with old firmware. Why are you
Still confused about why phone still not alive???

Just find the correct firmware version, or wait until it is released.

Better read out from working phone from same batch you killed.

01-12-2017, 12:05	#1 (permalink)
shahidshan40 No Life Poster Join Date: Jan 2013 Posts: 509 Member: 1873398 Status: Offline Thanks Meter: 149	SM-J700F after repair beeot still dad im using 6.0.1 file sboot+cm but phone still dad ================================================== ==== ================================================== ==== eMMC Test Point Connection Module ================================================== ==== ================================================== ==== 1. DO NOT USE THE PHONE"S BATTERY 2. Connect the Soldered TP Connections to ATF Box 3. Disconnect the USB Cable and Wait until the the ATF Software will tell you to Connect the USB. Interface Reset OK! eMMC Access Type: SECTOR MODE eMMC Supported Voltage Range: 3.5-3.6V, 3.4-3.5V, 3.3-3.4V, 3.2-3.3V, 3.1-3.2V 3.0-3.1V, 2.9-3.0V, 2.8-2.9V, 2.7-2.8V, 1.9-2.0V CID : 11010034303030373300B389988EA2D3 CSD : D07E00320F5903FFFFFFFFE78A4000D1 eMMC Boot Information Revision 1.7 (for MMC v5.0, v5.01) BOOT PARTITION : BOOT PARTITION 1 PARTITION ACCESS : R/W USER PARTITION PERM_BOOT_CFG_PROT : DISABLED PWR_BOOT_CFG_PROT : DISABLED BOOT MODE : x4 SINGLE DATA RATE + LOW SPEED RESET BUS WIDTH : ENABLED eMMC FirmW UPDATE : DISABLED EMMC CACHE SIZE : 0 KB SUPER PAGE SIZE : 4096 KB HC ERASE GROUP SIZE: 4096 KB USER AREA SIZE : 15758000128 BYTES BOOT PARTITION SIZE: 4096 KB RPMB PARTITION SIZE: 4096 KB eMMC Device Information Manufacturer ID: TOSHIBA Device Type : Embedded BGA Application ID : 00 Product Name : 400073 Product Rev : 0.0 Product SN : B389988E Manufactured : January 1999 Card Specific Data CSD_STRUCTURE : Extended SPEC_VERS : Version 4.1/4.2/4.3 TAAC : 8000 ns TRAN_SPEED : 4000000 KHz READ_BL_LEN : 512 Bytes C_SIZE : HIGH CAPACITY WP_GRP_ENABLE : YES WRITE_BL_LEN : 512 Bytes CONTENT_PROT_APP : NO PERM_WRITE_PROTECT: NO TMP_WRITE_PROTECT : NO Extended CSD Saved: 11010034303030373300B389988EA2D3.ext_csd Backup Directory: C:\AdvanceBox Turbo Flasher\eMMC\EXT_CSD\ Start Writing Flash Images... Flash Image: sboot.bin Start Writing 0x00002000 Blocks at 0x00000000 Partition Selected: BOOT 1 Total Elapsed Time 00:00:04 Write Success! Flash Image: cm.bin Start Writing 0x00002000 Blocks at 0x00000000 Partition Selected: BOOT 2 Total Elapsed Time 00:00:04 Write Success! Total Images Written: 2 Process Done!

01-15-2017, 03:06	#2 (permalink)
chand_gee Moderator Join Date: Jan 2008 Location: <jeddah al saudia> Age: 36 Posts: 2,261 Member: 668050 Status: Offline Sonork: 100.1656307 Thanks Meter: 991	@shahidshan40 If you write md5 file and still dead... Then it is dead because version you write is still OLDER than version on phone before it was killed. How is this possible??? Because not all firmware is released. Possible you killed phone with very new firmware inside. And you just wanted to put other Language Pack inside or tried to cross-flash the phone with different model. All you can do is wait wait wait until sa.mmob.ile or other sources will release a newer version that will repair your phone. Do not cross flash. Do not use old firmware. If phone still dead, then do not be surprised. The reason is very very simple why it is dead. Version you write is old. That is it. No need to keep asking forum why phone is still dead. Come on, you guys know phone died because you flashed it with old firmware. Why are you Still confused about why phone still not alive??? Just find the correct firmware version, or wait until it is released. Better read out from working phone from same batch you killed.