|
![]() |
|
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. |
| |||||||
| Register | FAQ | Donate | Forum Rules | ★. iPhone Unlock .★ | -= JTAG BOOM =- | .: Nokia Unlock :. | Search | Today's Posts | Mark Forums Read |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #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. |
|
| | #2 (permalink) |
| No Life Poster ![]() ![]() ![]() ![]() ![]() ![]() ![]() 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. |
|
| | #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:
also selected jtag speed to higher option but the calculated writing time is 2 days, wow! | |
|
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
| |
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 |