S3850 z3x jtag cant fix ?????
 

history
phone problem is a shifted display, the common problem of corby 2 yesterday i tried to flash it in multiloader but theres an error occur during flashing, the phone stop booting or not pwering on, no download mode/flash mode, its totally dead. this error in jtag i always encounter..

note: i reformat my pc for fresh install of z3x jtag

RCP v1.01
RCP v1.02

those 2 RCP in support failed to fix , cant back to normal trouble when i flash before in multiloader 5.65.


logs

another problem cant erase again...

logs:
note cant erase so i cant go on RCP boot repair...

any one expert in easy encounter this problem?

looks like bad flash chip

i try many times this kind of phone but still same

the flash chip is bad

Thanks for the rep sir blang & bro mquimpanes.. now I know my easy jtag is in good condition

Up up up...... -lol- z3x jtag.... s3850 problem facing after box fw update I think..?

In my old or passed experience of using this jtag, I did success repair 1-3 pcs corby 2, now 8 pcs are done by RTO..

Now I know my jtag is in abnormal condition...

Today s3850 problem with shifted display with mobile software info like factory,csc etc... easy jtag failed to recover the dead dody/dead boot not fixed but today the phone is alive by other jtag tool.

RIFF box recover and resurect the dead body but z3x easy cant do that via rcp repair or even erasing and write the new RCP, all are failed operation wanting to RTO again but b4 RTO(return to owner) I want to test it to other jtag tool (Riff box). Now I want some little explaination why z3x cant fix it? why u said it is a bad flash chip..? What happened in this device? Abnormalities after fw update, something to say they select the type of flash chip brand that want to fixed. Samsung type name not fixed 8 pcs all are done by RTO. Is there a hynyx name o brand of flash chip in this old phone? My supplier said, maybe the choose the brand of chip? True or false? Someone can give me a comment or rep. What should I do this box? is this a bug in fw or box dammage? How to fixed? I dnt want to end the year that this tool giving a bad day! If another s3850,s5300,5360,s7562 cant fixed maybe this 1 I choose is not good in direct EMMC. I choose this one among the rest cuz it is better as I read on every update release but in the reality boompanes!!! (just kidding)

Time to time still waiting the good news, easy jtag is boombastic, still waiting for the good explaination at yours, sir blang..

Waiting for the reply... thanks

S3850 not have EMMC chip.
this phone have normal old flash chip.
if you want to be sure, change flash to working open and try repair.
you will have answer.


i have S3850 in my hands. just tested everything ok. read/write repair.

Phone is fixed by riff box yesterday before decide to rto... all done by riff box, erase and resurect... started facing this after fw update no s3850 done by rcp or easy repair.. in my pass experience of using since I bought it to my reseller.

when you will have phone connected to easy-jtag , contact with me and show via teamviewr.

i remember 1 time phone was connected but not good.
did you press power button on phone while halting?

Add missing txt... my pass experience for a fresh and new z3x easy tool is good now dont kno why they cant fixed s3850 corby 2 even chip is detected... all corby 2 I recieve from customer result on RTO

i not understand what is this RTO.
i told you i have S3850 and i just today tested again.
everything ok.

if you will have phone in hands, contact with me and i will check remoted.
topic closed. if you not have now phone in hands.

also got the same problem first easy repair boot was flashed but white screen then try again this is the error tried on 2 corby 2 same problem...

Check security...OK
Initialising: SAMSUNG GT-S3850 Config ver.:1.01
I/O Level set to : 3000 mV
Box S/N: xxxxxxxxxx ,FW Ver.: 01.50
Connecting to Target...
JTAG device: BCM2133
CPU IDCODE : 0x07926F0F Mfg.: 0x787, Part: 0x7926, Ver.: 0x0
CPU Manufacturer: Samsung , CPU Name: BCM21331
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting nand memory parameters ...
NAND flash device ID:00EC:0040 'NAND 256MB 1.8V 8-bit (Samsung)' found
NAND geometry: Blocks:00000800, Page size:2048 bytes , Block size:64 pages
NAND Writing BOOT...
Failed writing file BOOT.BIN to NAND flash 0 at offset 0x00000000 code# 209



cannot erase also...

same problem with me
Failed writing file BOOT.bin to NAND flash 0 at offset 0x00000000 code# 209

eMMC may be dead. Desolder it and try to test at soket