Easy-JTAG Very HOT Update. v1.9.0.5 – FIRST IN THE WORLD!
I've tried power cycles and unplugged the jtag connection and plugging it back in. What can I do to get a 100% success rate? Running on SDK 2015.2, part number is xc7z100-2ffg900 on avnet MiniITX. Easy-Jtag / Easy-Jtag Plus The official support section. You can ask here your question and get answer regarding using Easy-Jtag / Easy-Jtag Plus. CMD Timeout Error. Easy Jtag Plus - If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. Contribute to intel/OpenOCD development by creating an account on GitHub. Dismiss Join GitHub today. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
NO ANY ADDITION ACTIVATION, NO ANY ADAPTERS.
LIKE USUALLY all hotest solution come free for all z3x users, 10years on market!!!
Hope z3x users will repair today all bricked EMMC
After 6month of playing with EMMC we have new solution for you:
- KMVTU000LM-B503 [VTU00M] REPAIR
- READY CONDITION TIMEOUT ERROR REPAIR
- OCR READY TIMEOUT [EMMC BAD] REPAIR
- TOTALLY DEAD 00FF8080 REPAIR
This solution can repair 90% dead KMVTU000LM-B503 eMMC.
For work with solution you just need connect 1 MAGIC Z3X-TP for force EMMC firmware emmc mode.
Testpoint Location:
HERE is step by step repair with screenshots!
Here is Repair Manual:
1. Download latest Easy-Jtag install
2. Identify eMMC:
LOG:
OCR READY TIMEOUT [EMMC BAD]
Done.
3. Disconnect eMMC from power lines and easy-jtag box connector
(disconnect eMMCfrom box is important, because some voltage leakage via CMD, CLK, DAT0)
4. Make short testpoint [TP] to [GND] (solder small wire)
5. Plug eMMC power and connect Easy-Jtag box connector
6. Remove short [TP] to [GND]
7. Identify eMMC
LOG:
EMMC Date: 05/2005 Rev.0x56
EMMC NAME: 000000, S/N: 537986854
8. Start Custom Operation ->’SAMSUNG: eMMC Update Firmware’
9. Confirm eMMC Part Number ‘KMVTU000LM-B503’
LOG:
Z3X EasyJtag Software ver. 1.9.0.5
Loading eMMC Addon Firmware… IO: 2800 mV
Box S/N: XXXXXXXXXXXXXXXX, ,FW Ver.: 01.52
CMD Pullup Level:2052 mV
CMD Active Level:2588 mV
Setup firmware normal update mode, wait 2..30 sec…
Success!
Sending eMMC firmware…
Success!
Verifying eMMC firmware…
Success!
Flashing eMMC firmware…
Success!
Repairing eMMC CID…
Success!
eMMC firmware is updated now!
Please reconnect eMMC power lines before next operation!
Please don’t forget to repair extCSDfrom backup!
Please don’t forget to configure BOOTsizes!
Done.
Now eMMC is alive !!! Enjoy!!!
P.S. COPY PASTERS – time for copy our solution. time to wake up
P.P.S. Z3X users – we have lot of news for you in nearly future, be ready .
Cmd Timeout Error Easy Jtag Tutorial
P.P.P.S Somebody has earn today $$$ ))
Cmd Time Out Error Easy Jtag
I bought an z3x easy-jtag recently.
The box arrived this week and after I installed it, I tried to read eMMC with it but unsuccessfully.
So now I'm here to ask official developers any help.
To be easier to understand my problem by the support people and by anyone who's facing the same problems I'll try to simplify everything, explain my test conditions and give you images of a log of a phone that I've tried to read. Notice: the phone was fully working before trying to read its eMMC (and is still working, I supose...)
Here we go.
Phone: Samsung Galaxy S4 gt-i9505 (which was perfectly booting and working)
Desktop: Windows 10 x64 Pro + admin rights + driver signature verification disabled + Intel processor + 8GB Ram + 200Mb (upload and download) internet very stable conection
Box Software: Z3X EasyJtag Box Software JTAG Classic Suite ver.2.5.0.6
Box Firmware: 01.58
Configs:
-eMMC Voltage: 2.8 Volt IO
-eMMC CLK Rate: 14MHz
-HiPower CLK Drive Mode = checked
Hardware conditions:
-Samsung original 2A wall charger connected to USB port of logic board
-200 Ohm resistors between CMD / Dat0 and 1.8V testpoint
-Strong/thick wire for Ground connection between box and logic board
-All the Ground pins of the box are connected together
-All the wires have at max 5 centimeters of lenght
Log:
EasyJtag Suite Classic ver.: 2.5.0.6 / wxWidgets 3.1.0-W-U started.
OS ver.: Windows 10 (build 14393), 64-bit edition. Admin rights OK
undefined
Android Explorer ver.: 1.0.0.21
eMMC ODIN ver.: 1.0.11.0
Successfully connected to box on COM26
Box S/N: not important, ,FW Ver.: 01.58
Box Working Mode: JTAG Box.
Box Drivers version: 3.0.1.0, are OK
Z3X Card Serial : not important , ver: 22
Z3X Card Activation [LG] : NOT ACTIVATED
Z3X Card Activation [SAMS] : NOT ACTIVATED
Z3X Card Activation [JTAG] : ACTIVATED
Z3X EasyJtag Software ver. 2.5.0.6
Loading eMMC Addon Firmware... IO: 2800 mV
Box S/N: not important, ,FW Ver.: 01.58
CMD Pullup Level:1753 mV
CMD Active Level:2567 mV
Box IO Level:2800 mV
CLK Rate:14000 khz
HiPower mode is ON!
Can't init device, Reason: CMD Timeout Error
Done.
Check the following images
postimg*org/image/7suikbcsh/
postimg*org/image/se9ac7udd/
>>>>>replace the '*' with a '.'
************************************************** *****
All of the above is a test condition to show to official supporters an example o my test conditions.
Now I'll report all that I have already tried to not let people make me waste my time and their with tips and tricks that I could have already tried:
eMMC reading:
I tried to read eMMC of 1 faulty (not booting) gt-i9205 Galaxy Mega
I tried to read eMMC of 1 faulty (not booting) gt-i9505 Galaxy S4
I tried to read eMMC of 1 great condition' gt-i9505 Galaxy S4
----------With Adapter------------
Using th Red Adapter that arrived inside the box' package that I bought from GSMServer, using the adpater's external power (Vcc adpater's pin to 2.8V logic board's testpoint & VccQ adapter's pin to 1.8V logic board's testpoint)
(the adapter is the one on the right side of the picture)
postimg*org/image/75vlusfwh/
>>>>>replace the '*' with a '.'
----------Without adapter---------
Used USB cable to feed the Logic Board internally + HiPower CLK Drive Mode
#############################################
---------configs possible---------
tried all the combinations of eMMC voltages + eMMC CLK rates (with and without adapter
I tested all of this in the 3 phones that I mentioned above in an Windows 10 x64 Pro Desktop and then repeated all again in another different Windows 7 x86 Pro Desktop
The results were the same
In the 2 desktops I tried serveral Box software + Box firmware (downgrade too)
EasyJtag_Release_v1.0.105.0 (plus respective firmware)
EasyJtag_Release_v1.7.0.1 (plus respective firmware)
EasyJtag_Release_v2.0.5.0 (plus respective firmware)
EasyJtag_Release_v2.5.0.6 (plus respective firmware)
#######################################
JTAG reading:
after all of this I tried to JTAG the gt-i9205 follwing all the instrutions of the most recent 'EasyJtag_Release_v2.5.0.6' software suite. Using the USB cable + battery to power the logic boarfd as sugest by software suite, etc.. just to check if it could be a fault of the box.
Result: none....
Log:
EasyJtag Suite Classic ver.: 2.5.0.6 / wxWidgets 3.1.0-W-U started.
OS ver.: Windows 10 (build 14393), 64-bit edition. Admin ri
For support and updates visit 'no links'
Check security...
OK
Initialising: SAMSUNG GT-I9205 Config ver.:1.00
I/O Level set to : 2200 mV
Box S/N: not important ,FW Ver.: 01.58
Connecting to Target...
Done with error(s)...
What I didn't tried:
I didn't tried to dessolder the eMMC chip and read it directly but I don't see any advantage for me and my clients on that kind of service so I'm not interested in trying too
Last toughts:
For general users: If anyone have any valid sugestion please feel free to leave your answer and share your experience
For developers + official z3x supporters: it would be nice to hear any help from you. And if you think that this box unit can be faulty, please tell me so I can ask for a replacement on GSMServer seller
Best regards for all