Care Unlock  
Your online unlock store
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. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

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) > GSMServer Products > Medusa

Reply
 
LinkBack Thread Tools Display Modes
Old 07-31-2012, 13:40   #1 (permalink)
Freak Poster
 
Join Date: Sep 2003
Location: philippines
Age: 35
Posts: 440
Member: 39561
Status: Offline
Thanks: 77
Thanked 106 Times in 46 Posts
cant repair boot of samsung I9001

also tried loading full firmware but it took so long. in my calculation loading of firmware is 2% per hour then at some point connection failed

Code:
Log started at 7/30/2012 12:41:29 PM ...
Welcome to Medusa Box Software version 1.5.0.1
Selected device model: Samsung GT-I9001
Connecting. Please wait...
Resetting target. Please wait...
VREF = 0.0V is less than required level. Please check target device power supply.
MI: RTCK reaction time 126 ns, average speed 7936 KHz.
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S64 revision B.
Detected TAP ID: 27B360E1, IR Length = 5.
MI: Halting target, attempt 1.
MI: Qualcomm ARM1136JF-S core detected.
MI: Qualcomm CPUID = 2057A0E1.
JTAG speed  : Auto (RTCK).
VREF level  : 1.79 V
CPU         : Qualcomm MSM8255T
Core ID     : 2057A0E1
MI: Loading Medusa Device Server V1.2.
MI: Starting...
MI: Received status 0x0000F00F, cycle 0.
MI: Received server capabilities 0x00000191.
MI: Detailed server caps: FLASH, WDOG, A64, IOCTL
MI: Watchdog configuration: 0xB800010C, 0x00000001... ok
MI: Server init.
MI: Received flash ID 0xE0150001.
MI: Flash geometry set.
MI: Recheking settings... ok
Server caps : 00000191
Storage Device: Samsung eMMC M8G2FA
Device ID     : 00150001
 Block size   : 512 bytes
 Blocks       : 15106048
 Storage size : 7.2 Gb
eMMC: partition, type 0x00000045 (0x30393443, 0x46343537)
eMMC: partition, type 0x00000020 (0x000101D2, 0x00930000)
eMMC: partition, type 0x00000073 (0x7478652E, 0x00000034)
eMMC: partition, type 0x00000038 (0x45334435, 0x44393839)
WARNING[002]: Partition Table damaged. Use Full flash write.
Connect successful.
Opening "C:\Program Files\GsmServer\Medusa\Firmware\Samsung_GTI9001_2GB.bin" file...
Writting BOOT section. Please wait...
MI: Server status 0xFFFFFFFF (not STAT_IDLE).
ERROR[018]: Logical block operation failed at 106880 Kb (Hex address 0x06860000). Reason: Connection lost.
Disconnected
Selected device model: Samsung GT-I9001
Connecting. Please wait...
Resetting target. Please wait...
MI: RTCK reaction time 126 ns, average speed 7936 KHz.
Medusa JTAG Firmware version 1.1.0.
Medusa JTAG Hardware S64 revision B.
Detected TAP ID: 27B360E1, IR Length = 5.
MI: Halting target, attempt 1.
MI: Qualcomm ARM1136JF-S core detected.
MI: Qualcomm CPUID = 2057A0E1.
JTAG speed  : Auto (RTCK).
VREF level  : 1.79 V
CPU         : Qualcomm MSM8255T
Core ID     : 2057A0E1
MI: Loading Medusa Device Server V1.2.
MI: Starting...
MI: Received status 0x0000F00F, cycle 0.
MI: Received server capabilities 0x00000191.
MI: Detailed server caps: FLASH, WDOG, A64, IOCTL
MI: Watchdog configuration: 0xB800010C, 0x00000001... ok
MI: Server init.
MI: Received flash ID 0xE0150001.
MI: Flash geometry set.
MI: Recheking settings... ok
Server caps : 00000191
Storage Device: Samsung eMMC M8G2FA
Device ID     : 00150001
 Block size   : 512 bytes
 Blocks       : 15106048
 Storage size : 7.2 Gb
eMMC: partition, type 0x00000045 (0x30393443, 0x46343537)
eMMC: partition, type 0x00000020 (0x000101D2, 0x00930000)
eMMC: partition, type 0x00000073 (0x7478652E, 0x00000034)
eMMC: partition, type 0x00000038 (0x45334435, 0x44393839)
WARNING[002]: Partition Table damaged. Use Full flash write.
Connect successful.
Opening "C:\Program Files\GsmServer\Medusa\Firmware\Samsung_GTI9001_2GB.bin" file...
Writting BOOT section. Please wait... Done
Writting FIRMWARE section. Please wait...
MI: Server status after request 0xFFFFFFFF (not STAT_DATA).
ERROR[018]: Logical block operation failed at 212992 Kb (Hex address 0x0D000000). Reason: Connection lost.
  Reply With Quote
Old 07-31-2012, 22:35   #2 (permalink)
No Life Poster
 
soshan's Avatar
 
Join Date: Sep 2007
Location: iran-shushtar
Posts: 2,753
Member: 592636
Status: Offline
Thanks: 9,158
Thanked 517 Times in 307 Posts
checking this process
1. full erase
2. writting repair file in easy tab then wrtting good firmware with odion then repair imei without jtag with anothere tools.
testing in p1000 and x10i
i think is better and easy way.
  Reply With Quote
Old 08-01-2012, 06:03   #3 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 2,168
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks: 880
Thanked 721 Times in 474 Posts
Also use the fully charged battery or stable external power supply and select higher Jtag speed.
  Reply With Quote
Old 08-03-2012, 06:46   #4 (permalink)
Freak Poster
 
Join Date: Sep 2003
Location: philippines
Age: 35
Posts: 440
Member: 39561
Status: Offline
Thanks: 77
Thanked 106 Times in 46 Posts
Quote:
Originally Posted by soshan View Post
checking this process
1. full erase
2. writting repair file in easy tab then wrtting good firmware with odion then repair imei without jtag with anothere tools.
testing in p1000 and x10i
i think is better and easy way.
there is no option for full erase

also selected jtag speed to higher option but the calculated writing time is 2 days, wow!
  Reply With Quote
Old 08-03-2012, 07:15   #5 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 2,168
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks: 880
Thanked 721 Times in 474 Posts
What speed have You slected exactly?
  Reply With Quote
Old 08-10-2012, 11:08   #6 (permalink)
Freak Poster
 
Join Date: Sep 2003
Location: philippines
Age: 35
Posts: 440
Member: 39561
Status: Offline
Thanks: 77
Thanked 106 Times in 46 Posts
tried 12.0 MHz, 8.0 MHz and also auto (RTCK)
  Reply With Quote
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


Similar Threads
thread Thread Starter Forum Replies Last Post
Please Help, Pinout of N8810 mobileinfo Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 5 06-30-2010 15:53
All LOCK and ALL version of Nokia - Universal SP Unlocker 4.0 - download now !!! bp.bonus Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 0 01-30-2000 16:41
GID for nokia 5110 of telecel or TMN or Optimus? hicom Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 2 10-13-1999 15:29
Silly question!! Why is it impossible to read out the mastercode of Nokia phones???? MyKe Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 0 09-26-1999 14:31
The multiple errors of Winlock ... ??? Genata Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L ) 0 09-20-1999 19:12


All times are GMT +1. The time now is 22:26.



Powered by Searchlight © 2013 Axivo Inc.
- GSM Hosting Ltd. - 1999-2013 -
Page generated in 0.41378 seconds with 11 queries

SEO by vBSEO