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 12-31-2013, 14:51   #1 (permalink)
Freak Poster
 
Join Date: Feb 2008
Posts: 359
Member: 714291
Status: Offline
Thanks Meter: 39
Samsung n7000: Error on resurrection


Hi Riffbox team.

Am trying to resurrect samsung N7000 but getting programming error

see the log below

pls give me a good lead on reviving my phone





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

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.79V, TCK Frequency is 4 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 (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.
WARNING: Programming Error (0x25) at 0x00000182C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001830000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001834000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001838000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000183C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001840000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001844000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001848000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000184C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001850000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001854000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001858000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000185C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001860000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001864000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001868000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000186C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001870000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001874000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001878000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000187C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001880000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001884000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001888000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000188C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001890000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001894000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001898000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00000189C000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018A0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018A4000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018A8000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018AC000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018B0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018B4000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018B8000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018BC000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000018C4000 is handled as Cut Excess.
ERROR: Forced to Terminate. Terminated at 0x0000018C8000


Thanx!
  Reply With Quote
Old 12-31-2013, 15:04   #2 (permalink)
Product Supporter
 
bk.gsm's Avatar
 
Join Date: Sep 2008
Location: UMT Support section
Age: 33
Posts: 3,769
Member: 869809
Status: Offline
Thanks Meter: 1,705
recheck your wires and be sure of that your phone has good power

b.r.
  Reply With Quote
Old 01-01-2014, 11:30   #3 (permalink)
Freak Poster
 
Join Date: Oct 2007
Posts: 334
Member: 619957
Status: Offline
Thanks Meter: 50
Error code 0x25
Returned by the DCC Loader when it fails to program part of flash memory. This is not an abnormal situation for NAND memories – bad blocks and pages are sometimes appear due to specific NAND memory’s technology. User shall select how to handle block program error in the JTAG Manager – for this user must be familiar with bad blocks handling techniques in general.
  Reply With Quote
Old 01-01-2014, 13:28   #4 (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 Guys
@msajum
You need replace eMMC ,This is Only Way

@gulab
N7000 not have Nand,have a eMMC
  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 04:44.



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

SEO by vBSEO