GSM Shop GSM Shop
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.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

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) > RIFF Box Team > RIFFBOX


Reply
 
LinkBack Thread Tools Display Modes
Old 09-06-2012, 13:06   #1 (permalink)
No Life Poster
 
ashraf_bcs's Avatar
 
Join Date: Jun 2006
Location: Bangladesh
Posts: 2,545
Member: 303373
Status: Offline
Sonork: 100.1584377
Thanks Meter: 1,241
Samsung S5830i boot repaie error


Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung S5830i V1.0.4476.13359]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - CORRECT!
Set I/O Voltage reads as 2.99V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...OK
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000040000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000140000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000440000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001240000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001280000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000012C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001300000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001340000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001380000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000013C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001400000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001440000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001480000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000014C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001500000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001540000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001580000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000015C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF00000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF40000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF80000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFC0000 is handled as Cut Excess.
Resurrection complete!

Need help plz.

  Reply With Quote
Old 09-06-2012, 16:12   #2 (permalink)
No Life Poster
 
ashraf_bcs's Avatar
 
Join Date: Jun 2006
Location: Bangladesh
Posts: 2,545
Member: 303373
Status: Offline
Sonork: 100.1584377
Thanks Meter: 1,241
3 Hours gone still no replay!!!
  Reply With Quote
Old 09-06-2012, 23:10   #3 (permalink)
Product Supporter
 
BABAK NURI's Avatar
 
Join Date: Mar 2005
Location: Tehran.IR
Age: 43
Posts: 7,259
Member: 131131
Status: Offline
Sonork: 100.1606847
Thanks Meter: 4,475
Hi
Sorry for late...but 3h not realy long time...
anyway
Can you tell me about phone history?
How come dead? suddenly or killed by wrong firmware?
i see in your log,flash chip have a lot bad sectore...
  Reply With Quote
Old 04-10-2013, 10:16   #4 (permalink)
Junior Member
 
Join Date: Oct 2005
Posts: 16
Member: 193809
Status: Offline
Thanks Meter: 0
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung S5830i V1.0.4476.13359]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - IGNORED!
Set I/O Voltage reads as 3.01V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...OK
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001280000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001300000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001400000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF00000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF80000 is handled as Cut Excess.
Resurrection complete!
  Reply With Quote
Old 04-10-2013, 10:18   #5 (permalink)
Junior Member
 
Join Date: Oct 2005
Posts: 16
Member: 193809
Status: Offline
Thanks Meter: 0
please sir

samsung s5830i

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [Samsung S5830i V1.0.4476.13359]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - IGNORED!
Set I/O Voltage reads as 3.01V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...OK
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001280000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001300000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001400000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF00000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF80000 is handled as Cut Excess.
Resurrection complete!
  Reply With Quote
Old 04-27-2013, 17:36   #6 (permalink)
Freak Poster
 
Join Date: Jan 2006
Location: colombia
Age: 45
Posts: 327
Member: 220008
Status: Offline
Thanks Meter: 95
Donate money to this user
please sir

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.35, JTAG Manager Version: 1.49
Selected Resurrector: [Samsung S5830i V1.0.4476.13359]
Restarting target (nRST Low then High)...OK

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - IGNORED!
Set I/O Voltage reads as 2.99V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 6 MHz]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...OK
WARNING: Programming Error (0x24) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000040000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000140000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001240000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001280000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000012C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001300000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001340000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001380000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000013C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001400000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001440000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001480000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000014C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001500000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001540000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000001580000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000015C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FF00000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FF40000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FF80000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x00001FFC0000 is handled as Cut Excess.
Resurrection complete!
  Reply With Quote
Old 11-30-2013, 07:58   #7 (permalink)
Crazy Poster
 
Join Date: Jul 2009
Posts: 52
Member: 1086738
Status: Offline
Sonork: shamimtelecom
Thanks Meter: 24
Samsung s536o

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...
WARNING: Programming Error (0x24) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000040000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000140000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x000000240000 is handled as Cut Excess.
  Reply With Quote
Old 04-05-2014, 12:20   #8 (permalink)
Product Manager
 
aZimBahar's Avatar
 
Join Date: Dec 2009
Location: CEO.of.ROMDevelopers
Age: 32
Posts: 16,005
Member: 1174508
Status: Offline
Sonork: 100.1593820
Thanks Meter: 11,978
Donate money to this user
I have Same Problem To S5830
Phone Status - Customer Update By Self , After Dead
I Did Repair Boot & Flash , But Only Blinking
Here Is Log
Quote:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.55
Selected Resurrector: [Samsung S5830 V1.0.4860.51697]

Connecting to the dead body...OK
Detected dead body ID: 0x303C10E1 - IGNORED!
Set I/O Voltage reads as 2.59V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB)

Flashing the dead body...OK
WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess.
Resurrection complete!

Last edited by aZimBahar; 04-05-2014 at 12:26.
  Reply With Quote
Old 04-06-2014, 21:28   #9 (permalink)
No Life Poster
 
littmanr's Avatar
 
Join Date: Oct 2005
Posts: 668
Member: 190377
Status: Offline
Thanks Meter: 61
Best method it's set tck 4MHZ, bcoz Broadcom CPU clock lower :-)


Enviado desde mi iPad con Tapatalk
  Reply With Quote
Reply

Bookmarks


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


 



All times are GMT +1. The time now is 12:47.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.16333 seconds with 8 queries

SEO by vBSEO