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) > Rocker Team products > RIFFBOX

Reply
 
LinkBack Thread Tools Display Modes
Old 08-09-2012, 23:20   #1 (permalink)
Freak Poster
 
Join Date: Jun 2012
Posts: 99
Member: 1772418
Status: Offline
Thanks Meter: 7
What do we know? DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)

Really? Thats it? If you got this on the screen there is no turning back, dead as death?
I made an appointment with the chief of research on my college, i talk with him and explained the problem that i have learned since i first ran in to this message.
From here:
Hard Brick Bug on Galaxy S II and Note Leaked ICS Kernels – xda-developers
To our forum i searched and we have no solution at this point.
Of course this is not his major project but at least he may point me somewhere.

What do you think? Am i facing a wall or do you think we have any chance?
I have 2 N7000 and 3 I9100 with this issue and the permision of the owners to keep trying...Of course they have nothing to loose.

Please if you have any information i should know please post would be great.
Of course i am aware of the latest sticky of manually charge the boot.bin on ROM2, but i am interested on the ones that cant be resurrected and at least a payback for the long hours i spent soldering and trying.
  Reply With Quote
Old 08-10-2012, 00:44   #2 (permalink)
Product Supporter
 
BABAK NURI's Avatar
 
Join Date: Mar 2005
Location: Tehran.IR
Age: 33
Posts: 6,508
Member: 131131
Status: Offline
Sonork: 100.1606847
Thanks Meter: 2,471
Hi
For Now,You Have Only 1 Option....
" Replace eMMC "
----
Tested By Me ...More than 10 pcs.(i9100 and N7000)
---
maybe in future we make new address for Re-partition eMMC by jtag interface...like pathed .pit for repair hang on logo or odin when flashing
  Reply With Quote
Old 08-10-2012, 01:13   #3 (permalink)
Freak Poster
 
Join Date: Jun 2012
Posts: 99
Member: 1772418
Status: Offline
Thanks Meter: 7
For now i only have one spare of eMMC chip from a i9100 that just about 3 minutes ago i ripped the JTAG pins from it in a not very smart overheat from wich i ran tests for the project. So that makes one.
And yes, that is the project itself helping out by developing new methods so the chips wont be needed to be replaced. Maybe they just need some heat from a rework station to more advanced software interface, but that is to be known on my way
  Reply With Quote
Old 08-10-2012, 02:26   #4 (permalink)
Freak Poster
 
Join Date: Jun 2012
Posts: 99
Member: 1772418
Status: Offline
Thanks Meter: 7
Why the eMMC partition plugin keeps failing to get the image of a healthy N7000?

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

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.88V, TCK Frequency is 8 MHz
Settings Code: 0x22020B00000000018000000000008000

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/0x0001 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Reading FLASH1 address space from 0x000000000000 to 0x0000000001FF
ERROR: Failed to unpack received data. Terminating.
  Reply With Quote
Old 08-10-2012, 11:22   #5 (permalink)
Product Manager
 
legija's Avatar
 
Join Date: Apr 2006
Age: 45
Posts: 5,384
Member: 256342
Status: Offline
Sonork: None
Thanks Meter: 25,865
RIFF JTAG Box FAQ - How to use QUALCOMM eMMC MBR/EBR Partitioning plugin
  Reply With Quote
The Following 2 Users Say Thank You to legija For This Useful Post:
Old 08-16-2012, 22:24   #6 (permalink)
Freak Poster
 
Join Date: Jun 2012
Posts: 99
Member: 1772418
Status: Offline
Thanks Meter: 7
Any idea of why i keep facing this error on a N7000? It has no damage on the eMMC chip, but i belive it has a bad partition table, any way of solving this? If i wipe device i will loose IMEI and other stuff wich i dont have any back up because it is not mine.

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

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.79V, TCK Frequency is 8 MHz
Settings Code: 0x27010B000000000000000003AB400000

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/0x0001 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Reading FLASH1 address space from 0x000000000000 to 0x0000000001FF
Completed in 00:00:00.015 (Average Transfer Rate: 139810133.27 kB/s)
ERROR: Expected signature word 0x55AA, but found different. Cannot continue.
Analisis is stopped. So far were found: 0 partitions.


Analizing the FullImage File...ERROR
ERROR: Expected signature word 0x55AA, but found different. Cannot continue.
Analisis is stopped. So far were found: 0 partitions.

ERROR: Access Violation when setting Length for Dinamic Array.
  Reply With Quote
Old 08-17-2012, 10:17   #7 (permalink)
Product Manager
 
legija's Avatar
 
Join Date: Apr 2006
Age: 45
Posts: 5,384
Member: 256342
Status: Offline
Sonork: None
Thanks Meter: 25,865
It is very simple - N7000 is not Qualcomm based with EBR or MBR partition structure.
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

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


Similar Threads
thread Thread Starter Forum Replies Last Post
what prog changes imei on 6110 and how do i do it? Ravetrancer Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 07-31-2012 20:09
How can I do a Welcome note for my 6110 a dosn't have any one ? Viper Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 7 07-18-2012 07:57
SIM restriction pending -- what does it mean? Ryu Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 7 07-17-2011 10:05
Help: Forgot my 6110 user lock code!! GByte9 Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 3 04-03-2011 15:00
how the **** do i make wintesla 6.03 work Ravetrancer Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) 0 06-16-1999 08:41

 



All times are GMT +1. The time now is 08:51.



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

SEO by vBSEO