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-13-2014, 08:48   #1 (permalink)
No Life Poster
 
sidramobilecare's Avatar
 
Join Date: Oct 2008
Location: in your Heart
Posts: 525
Member: 888557
Status: Offline
Sonork: 100.1608317
Thanks Meter: 34
n7000 resurrection gives error


sir

n7000 resurrection gives following error, what could be the problem please

Quote:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung N7000 V1.0.4860.58267]

Connecting to the target...OK
Set I/O Voltage reads as 2.80V, TCK Frequency is 8 MHz

Following devices are found on the JTAG chain:
Device on TAP #0: ID = 0x4BA00477, IR Length = 0x04 bits
Total IR length: 0x0004 bits

Analizing IDCODE(s) of the JTAG scan chain:
1. 0x4BA00477: Generic CORTEX-A9/A15 Core Based Target
Code:
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 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Selected 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.
WARNING: Programming Error (0x25) at 0x00000003C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001800000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001804000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001808000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000180C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001810000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001814000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001818000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000181C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001820000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001824000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001828000 is handled as Cut Excess.
  Reply With Quote
Old 09-13-2014, 08:52   #2 (permalink)
No Life Poster
 
sidramobilecare's Avatar
 
Join Date: Oct 2008
Location: in your Heart
Posts: 525
Member: 888557
Status: Offline
Sonork: 100.1608317
Thanks Meter: 34
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)

does it mean that emmc is ok
  Reply With Quote
Old 09-13-2014, 15:19   #3 (permalink)
Freak Poster
 
Join Date: Oct 2001
Location: Earth
Posts: 248
Member: 6884
Status: Offline
Sonork: 100.1621477
Thanks Meter: 105
emmc is not ok, you must replace it
  Reply With Quote
The Following User Says Thank You to Benhure For This Useful Post:
Old 09-13-2014, 17:54   #4 (permalink)
Freak Poster
 
Join Date: Jul 2007
Location: italy
Posts: 473
Member: 548901
Status: Offline
Sonork: 100.1644756
Thanks Meter: 51
note

Hi if you have try first to change ic power....
  Reply With Quote
The Following User Says Thank You to dave_21 For This Useful Post:
Old 09-14-2014, 16:31   #5 (permalink)
No Life Poster
 
Yashbanswara's Avatar
 
Join Date: Oct 2009
Location: Rajasthan INDIA
Posts: 1,138
Member: 1147254
Status: Offline
Sonork: 100.1620677
Thanks Meter: 639
i think this is not eMMC Ic Problem This Is Power Ic Problem So Change Power IC Of This Mobile

I Hope Your Problem Solve

Wbr

Gopal Parmar
  Reply With Quote
The Following User Says Thank You to Yashbanswara 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 19:41.



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

SEO by vBSEO