GSM-Forum - i9505 bead boot flash Done not power up

GSM-Forum (https://forum.gsmhosting.com/vbb/)

- Easy-Jtag / Easy-Jtag Plus (https://forum.gsmhosting.com/vbb/f672/)

- - i9505 bead boot flash Done not power up (https://forum.gsmhosting.com/vbb/f672/i9505-bead-boot-flash-done-not-power-up-1764278/)

i9505 bead boot flash Done not power up

Easy-Repair file load OK!
Using EasyRepair Mode...
Warning , you are using custom pinout config make shure that NRST and GND on proper places!
Checking repair data...
EasyJtag Suite ver.: 1.0.93.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-I9505 Config ver.:1.00
I/O Level set to : 2200 mV
Box S/N: ================ ,FW Ver.: 01.47
Connecting to Target...
JTAG device: APQ8064T.
CPU IDCODE : 0x4F1F0F0F Mfg.: 0x787, Part: 0xf1f0, Ver.: 0x4
CPU Manufacturer: Samsung , CPU Name: ARM7GEN
JTAG device: APQ8064T.
CPU IDCODE : 0x2071B0E1 Mfg.: 0x070, Part: 0x071b, Ver.: 0x2
CPU Manufacturer: QUALCOMM , CPU Name: APQ8064T
Halting CPU...
Initialize hardware...
Using EasyRepair Mode...
Warning , you are using custom pinout config make shure that NRST and GND on proper places!
Checking repair data...
EasyJtag Suite ver.: 1.0.93.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-I9505 Config ver.:1.00
I/O Level set to : 2200 mV
Box S/N: ======================= ,FW Ver.: 01.47
Connecting to Target...
JTAG device: APQ8064T.
CPU IDCODE : 0x4F1F0F0F Mfg.: 0x787, Part: 0xf1f0, Ver.: 0x4
CPU Manufacturer: Samsung , CPU Name: ARM7GEN
JTAG device: APQ8064T.
CPU IDCODE : 0x2071B0E1 Mfg.: 0x070, Part: 0x071b, Ver.: 0x2
CPU Manufacturer: QUALCOMM , CPU Name: APQ8064T
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting emmc memory parameters of bank (0) ...
EMMC #0 : ID : 0x00000015 Name : AFEABB Size : 14.7 G , (30777344) Blocks
EMMC #1 : ID : 0x00000015 Name : AFEABB Size : 4.0 M , (8192) Blocks
eMMC flash device(s) found, Device ID : 0x00150000
NAND Writing PGPT, PIT, MD5, P4...
eMMC Write OK! Elapsed time: 31.109375s (131.664 KiB/s)
NAND Writing APNHLOS...
eMMC Write OK! Elapsed time: 112.812500s (113.214 KiB/s)
NAND Writing MDM...
eMMC Write OK! Elapsed time: 565.656250s (93.279 KiB/s)
NAND Writing SBL1...
eMMC Write OK! Elapsed time: 1.187500s (107.789 KiB/s)
NAND Writing SBL2...
eMMC Write OK! Elapsed time: 2.125000s (120.471 KiB/s)
NAND Writing SBL3...
eMMC Write OK! Elapsed time: 4.062500s (126.031 KiB/s)
NAND Writing ABOOT...
eMMC Write OK! Elapsed time: 18.140625s (112.896 KiB/s)
NAND Writing RPM...
eMMC Write OK! Elapsed time: 2.984375s (171.560 KiB/s)
NAND Writing TZ...
eMMC Write OK! Elapsed time: 3.390625s (151.005 KiB/s)
NAND Writing EFS...
eMMC Write OK! Elapsed time: 56.421875s (247.280 KiB/s)
NAND Writing M9KEFS1...
eMMC Write OK! Elapsed time: 9.234375s (84.467 KiB/s)
NAND Writing M9KEFS2...
eMMC Write OK! Elapsed time: 9.265625s (84.182 KiB/s)
NAND Writing M9KEFS3...
eMMC Write OK! Elapsed time: 9.265625s (84.182 KiB/s)
NAND Writing SGPT...
eMMC Write OK! Elapsed time: 0.140625s (117.333 KiB/s)
All Done.:confused:

need help ..................................?

You may try to use repair -> Samsung GT-i9505_XXUEMKF_BOOT_V1.03.rcp

Or GT-I9505/Useful_Scripts/Samsung_GT-I9505_XXUEMKF_BOOT_Script.rar if you have installed newer firmware in phone before.

Do not forget install latest ( EasyJtag_Release_v1.0.97.1.exe ) JTAG

i dont kown what firmware had installed, i am using Samsung GT-i9505_XXUEMKF_BOOT_V1.03.rcp or GT-I9505/Useful_Scripts/Samsung_GT-I9505_XXUEMKF_BOOT_Script.rar and repair is DONE, but phone still dead, PC can't detect QHUSB.

Same problem need help!

Quote:

Originally Posted by lazyghost (Post 10039698)

Same problem need help!

what the verion was in phone before flashing or before phone dead?

looks like need add again new version.

I don't know ! Coz customer damage himself !
But I already try all 5 with riff and z3 jtag ( 1.2 & 1.3 )
Same can't enter download mode !
And I tried use new firmware ( write tz ,aboot , sbl1 ,sbl2 , sbl3 ,rpm ) Same problem!

Quote:

Originally Posted by NoName® (Post 10017511)

Samsung GT-i9505_XXUEMKF_BOOT_V1.03

EasyJtag Suite ver.: 1.0.98.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
Successefuly connected to box on COM10
Box S/N: 1=============, ,FW Ver.: 01.48
Box Working Mode: JTAG Box.
Box Drivers version: 3.0.0.0, are OK
Z3X Card Serial : ========= , ver: 22
Loading repair file: 'E:\soft ware\EasyJtag\Repair file\GT-i9505\Samsung GT-i9505_XXUEMKF_BOOT_V1.03.rcp'
Repair File ver. : Easy Repair for Mfg: SAMSUNG Model: GT-I9505, Ver.: 1.00
Repair file options. : NONE
Easy-Repair file load OK!
Using EasyRepair Mode...
Checking repair data...
EasyJtag Suite ver.: 1.0.98.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-I9505 Config ver.:1.00
I/O Level set to : 2200 mV
Box S/N: =============== ,FW Ver.: 01.48
Connecting to Target...
JTAG device: APQ8064T.
CPU IDCODE : 0x4F1F0F0F Mfg.: 0x787, Part: 0xf1f0, Ver.: 0x4
CPU Manufacturer: Samsung , CPU Name: ARM7GEN
JTAG device: APQ8064T.
CPU IDCODE : 0x2071B0E1 Mfg.: 0x070, Part: 0x071b, Ver.: 0x2
CPU Manufacturer: QUALCOMM , CPU Name: APQ8064T
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting emmc memory parameters of bank (0) ...
EMMC #0 : ID : 0x00000015 Name : AFEABB Size : 14.7 G , (30777344) Blocks
EMMC #1 : ID : 0x00000015 Name : AFEABB Size : 4.0 M , (8192) Blocks
eMMC flash device(s) found, Device ID : 0x00150000
NAND Writing PGPT, PIT, MD5, P4...
eMMC Write OK! Elapsed time: 31.640625s (129.454 KiB/s)
NAND Writing SBL1...
eMMC Write OK! Elapsed time: 1.218750s (105.026 KiB/s)
NAND Writing SBL2...
eMMC Write OK! Elapsed time: 2.859375s (89.530 KiB/s)
NAND Writing SBL3...
eMMC Write OK! Elapsed time: 5.937500s (86.232 KiB/s)
NAND Writing ABOOT...
eMMC Write OK! Elapsed time: 15.046875s (85.067 KiB/s)
NAND Writing RPM...
eMMC Write OK! Elapsed time: 1.734375s (110.703 KiB/s)
NAND Writing TZ...
eMMC Write OK! Elapsed time: 2.437500s (105.026 KiB/s)
NAND Writing SGPT...
eMMC Write OK! Elapsed time: 0.156250s (105.600 KiB/s)
All Done.

same dead:confused:

Quote:

Originally Posted by gsaara (Post 10043579)

It seems that inside your phone firmware earlier than our rcp files

i no earlier phone firmware version this sudntle bead phone
but phone version 4.3 conform

i dont ask version of android.
i have ask about version of firmware inside phone!
we have upload few new rcp files with last version.
you can use them

Quote:

Originally Posted by blang (Post 10157402)

i dont ask version of android.
i have ask about version of firmware inside phone!
we have upload few new rcp files with last version.
you can use them

Samsung GT-i9505 (XXUEMJ3) V1.02
Samsung GT-i9505_XXUEMKF_BOOT_V1.03
Samsung_GT-I9505_XXUEMKF_BOOT_Script
only 3 fcp file

Quote:

Originally Posted by gsaara (Post 10161903)

Samsung GT-i9505 (XXUEMJ3) V1.02
Samsung GT-i9505_XXUEMKF_BOOT_V1.03
Samsung_GT-I9505_XXUEMKF_BOOT_Script
only 3 fcp file

ok. what file you area tried, show log

Quote:

Originally Posted by blang (Post 10162325)

ok. what file you area tried, show log

http://imagizer.imageshack.us/v2/102...0/560/62fl.jpg