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 06-08-2013, 09:23   #1 (permalink)
Cheater -Don't Deal with him-
 
Join Date: Nov 2001
Location: IRAN
Age: 49
Posts: 557
Member: 7250
Status: Offline
Sonork: 100.1575042
Thanks Meter: 440
i use same part for i9100 and n7000 but got this error


hi

i use same chip nd part number for i9100 and n7000 but i got this error when try to restruct ...

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.35, JTAG Manager Version: 1.49
Selected Resurrector: [Samsung I9100 V1.0.4843.51977]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - IGNORED!
Set I/O Voltage reads as 2.79V, TCK Frequency is 8 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: 0x0015/0x0100 (000000, 0x0003BA000000 Bytes = 14.91 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)

No Resurrection Data is available for the eMMC Chip with Capacity = 14.91GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14.68GB

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000004000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000008000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000000C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000010000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000014000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000018000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000001C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000020000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000024000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000028000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000002C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000030000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000034000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000038000 is handled as Cut Excess.
ERROR: Forced to Terminate. Terminated at 0x000000038000
  Reply With Quote
Old 06-08-2013, 09:45   #2 (permalink)
Cheater -Don't Deal with him-
 
Join Date: Nov 2001
Location: IRAN
Age: 49
Posts: 557
Member: 7250
Status: Offline
Sonork: 100.1575042
Thanks Meter: 440
i think main problem is capacity of flash chip ....
  Reply With Quote
Old 06-08-2013, 10:42   #3 (permalink)
Freak Poster
 
ALI MAJIDINIA's Avatar
 
Join Date: May 2013
Location: IRAN__SHIRAZ
Posts: 161
Member: 1933631
Status: Offline
Sonork: 100.1618169
Thanks Meter: 52
Wink

[QUOTE=gsm-lord;9486065]i think main problem is capacity of flash chip
I think you have to change emmc chip

But if you dont belive me you can try with another tools like trace32 ;-)

Br
Majidinia
  Reply With Quote
The Following User Says Thank You to ALI MAJIDINIA For This Useful Post:
Old 06-08-2013, 17:33   #4 (permalink)
Cheater -Don't Deal with him-
 
Join Date: Nov 2001
Location: IRAN
Age: 49
Posts: 557
Member: 7250
Status: Offline
Sonork: 100.1575042
Thanks Meter: 440
i need to know , box must know correct size of flas for repair?????
why when want to use data from same size give error????

read of flash is ok and erase is ok too in dcc tab but write error
  Reply With Quote
The Following User Says Thank You to gsm-lord For This Useful Post:
Old 06-09-2013, 21:42   #5 (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
Please Note:
Quote:
No Resurrection Data is available for the eMMC Chip with Capacity = 14.91GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14.68GB
So,Capacity is not your problem....
--------------------------------------------------

Your Problem is :
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (000000, 0x0003BA000000 Bytes = 14.91 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)

Can You Tell Me About Chip Part Number Also Model?
Like "San--Disk SDIN4C2 16GB" or Other

I Think You Have Use Older Chip for I902x or I9000

Thanks
  Reply With Quote
The Following 2 Users Say Thank You to BABAK NURI For This Useful Post:
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 16:55.



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.13102 seconds with 8 queries

SEO by vBSEO