xbox-scene.com archived forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

xbox-scene.com forum restored.  registration disabled.  thanks to xboxexpert for the db dump and netham45 for cleaning it up!

Author Topic: NULL  (Read 309 times)

'Aluminum Gerbil'

  • Guest
NULL
« on: January 15, 2012, 08:51:12 PM »

'
               I just got my Zephyr RGH'd and now it's time to move on to my slim.  Going through the same steps I've dumped the NAND a dozen times and every dump matches, but when I load up Multi-Builder I get this:
* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 9188) at 00008000
Found 2BL (build 9188) at 00009ac0
Found 4BL (build 8453) at 000112c0
Found 15BL (build 65535) at 000172c0

So I tried using JTAG tool and I get this:
* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 9188) at 00008000
Found 2BL (build 9188) at 00009ac0
Found 4BL (build 8453) at 000112c0
Found 15BL (build 65535) at 000172c0
Traceback (most recent call last):
 File "build.py", line 340, in <module>
   unpack_base_image(image)
 File "build.py", line 72, in unpack_base_image
   (block_id, block_build, block_flags, block_entry_point, block_size) = struct
.unpack("!2sHLLL", image[block_offset:block_offset+16])
struct.error: unpack requires a string argument of length 16
Press any key to continue . . .

I've checked and rechecked my solder points and I just don't know what I'm doing wrong.  If anyone has any suggestions I'd GREATLY appreciate it.
               
               

               
            '
Logged

'socalbill'

  • Guest
NULL
« Reply #1 on: January 15, 2012, 11:47:37 PM »

'
               are there bad blocks in the first 50 blocks of your nand?

if so, follow Martin's guide http://www.team-xecu...ead.php?t=76014

usually after "Found 4BL (build 8453) at 000112c0" it says "Found 5BL (build 1888) at 000161e0"

might be a bad block somewhere.....


               
               

               
            '
Logged

'TingedAce'

  • Guest
NULL
« Reply #2 on: January 16, 2012, 03:12:45 AM »

'
               Xnandhealer 0.74 will do it for you automatically.
Give it it a go.
               
               

               
            '
Logged

'Aluminum Gerbil'

  • Guest
NULL
« Reply #3 on: January 16, 2012, 10:25:49 AM »

'
               First, Thank you so much for the quick replies.  

I tried running XNandHealer and it doesn't find any bad blocks.  I have 4 dumps that all compare fine and if I try to build a XELL Reloaded image it fails with the same errors.  Is there something really basic I'm missing?

Also if I run NAND Info I get Bad Blocks: None ECC Error Blocks: None and it says it's glitchable.
               
               

               


                     Edited by Aluminum Gerbil, 16 January 2012 - 07:27 PM.
                     
                  


            '
Logged

'Harbinger076'

  • Guest
NULL
« Reply #4 on: January 16, 2012, 10:31:32 AM »

'
               
QUOTE(Aluminum Gerbil @ Jan 16 2012, 12:25 PM) View Post

First, Thank you so much for the quick replies.  

I tried running XNandHealer and it doesn't find any bad blocks.  I have 4 dumps that all compare fine and if I try to build a XELL Reloaded image it fails with the same errors.  Is there something really basic I'm missing?

Also if I run NAND Info I get Bad Blocks: None ECC Error Blocks: None and it says it's glitchable.



you can always flash a image_00000000.ecc file from another slim system it will give you a kv error in xell reloaded but it will allow u to grab your cpu key for your slim..
               
               

               
            '
Logged

'Aluminum Gerbil'

  • Guest
NULL
« Reply #5 on: January 16, 2012, 11:31:21 AM »

'
               OK, and from there do I then record the CPU key and make a boot image from my original nand?  Sorry for all the questions?  Also where would one acquire an image from another slim?
               
               

               
            '
Logged

'TingedAce'

  • Guest
NULL
« Reply #6 on: January 16, 2012, 04:29:58 PM »

'
               
QUOTE(Aluminum Gerbil @ Jan 16 2012, 07:31 PM) View Post

OK, and from there do I then record the CPU key and make a boot image from my original nand?  Sorry for all the questions?  Also where would one acquire an image from another slim?


I've not tried what harbinger076 suggests, but PM me if you need a 'donor' slim ecc file  smile.gif

Then as you say, grab the CPU key and take it from there. You might want to look at this guide for doing it all with Xnandhealer. If you do, comments appreciated smile.gif


               
               

               
            '
Logged

'Aluminum Gerbil'

  • Guest
NULL
« Reply #7 on: January 17, 2012, 02:27:37 PM »

'
               Cool, TingedAce I'm sending you a PM now.  I'll post back when all is said and done as to whether this takes care of everything or if I break it even more. smile.gif
               
               

               
            '
Logged

'TingedAce'

  • Guest
NULL
« Reply #8 on: January 17, 2012, 02:56:41 PM »

'
               
QUOTE(Aluminum Gerbil @ Jan 17 2012, 10:27 PM) View Post

Cool, TingedAce I'm sending you a PM now.  I'll post back when all is said and done as to whether this takes care of everything or if I break it even more. smile.gif


OK, sent you it. Let me know how you get on.
               
               

               
            '
Logged

'Aluminum Gerbil'

  • Guest
NULL
« Reply #9 on: January 19, 2012, 11:51:39 PM »

'
               Flashed a donor ECC.  Now fighting trying to get the dumb thing to glitch.  Will report in after the weekend.  Thanks for the help everyone!
               
               

               
            '
Logged

'Aluminum Gerbil'

  • Guest
NULL
« Reply #10 on: May 29, 2012, 09:30:49 PM »

'
               So all I'm getting is a blinking green light.  I've tried EVERY length of cable and 3 different cap values.  Still no luck.  I flashed the original nand that I had read previously but couldn't create an ECC with and unsoldered the GND and VCC on the glitch chip and I still have a blinking green light and no boot/video.  Is this xbox done?  What do I do next?
               
               

               
            '
Logged

'deilzfcjk'

  • Guest
NULL
« Reply #11 on: May 29, 2012, 10:03:07 PM »

'
               If you ar e surethat you have thecrrect original nand? you remo vedthe chip completely/

you should check that you did not damage r4b24 for the clk point. Check that it is not lifted or burned off at one end.

you can check with a multimeter. If the value goes high or OL(out of limit) or infinity. something is wrong.
               
               

               


                     Edited by deilzfcjk, 30 May 2012 - 06:16 AM.
                     
                  


            '
Logged

'Aluminum Gerbil'

  • Guest
NULL
« Reply #12 on: June 01, 2012, 04:39:58 PM »

'
               
QUOTE(deilzfcjk @ May 30 2012, 06:03 AM) View Post

If you ar e surethat you have thecrrect original nand? you remo vedthe chip completely/

you should check that you did not damage r4b24 for the clk point. Check that it is not lifted or burned off at one end.

you can check with a multimeter. If the value goes high or OL(out of limit) or infinity. something is wrong.


I'll remove the chip this weekend and give it another shot at booting.  Is there any way to get a nand to replace this one if the one I have is corrupt?  None of my points are burned or anything.

               
               

               
            '
Logged

'deilzfcjk'

  • Guest
NULL
« Reply #13 on: June 01, 2012, 06:10:44 PM »

'
               Yes you could replace your nand. Try ebay. or get a demon. or trident.
               
               

               
            '
Logged

'XB0X72O'

  • Guest
NULL
« Reply #14 on: July 02, 2012, 11:03:35 AM »

'
               
QUOTE(Aluminum Gerbil @ Jan 16 2012, 06:51 AM) View Post

I just got my Zephyr RGH'd and now it's time to move on to my slim.  Going through the same steps I've dumped the NAND a dozen times and every dump matches, but when I load up Multi-Builder I get this:
* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 9188) at 00008000
Found 2BL (build 9188) at 00009ac0
Found 4BL (build 8453) at 000112c0
Found 15BL (build 65535) at 000172c0

So I tried using JTAG tool and I get this:
* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 9188) at 00008000
Found 2BL (build 9188) at 00009ac0
Found 4BL (build 8453) at 000112c0
Found 15BL (build 65535) at 000172c0
Traceback (most recent call last):
 File "build.py", line 340, in <module>
   unpack_base_image(image)
 File "build.py", line 72, in unpack_base_image
   (block_id, block_build, block_flags, block_entry_point, block_size) = struct
.unpack("!2sHLLL", image[block_offset:block_offset+16])
struct.error: unpack requires a string argument of length 16
Press any key to continue . . .

I've checked and rechecked my solder points and I just don't know what I'm doing wrong.  If anyone has any suggestions I'd GREATLY appreciate it.


               
               

               
            '
Logged
 

Page created in 0.148 seconds with 16 queries.