Jump to content


Photo

Jtag Issues Xbr Nand Cannot Extract Kv Info


  • Please log in to reply
4 replies to this topic

#1 Piratesmustperish

Piratesmustperish

    X-S Young Member

  • Members
  • Pip
  • 41 posts

Posted 11 June 2011 - 04:08 AM

Hey guys, I have a 256 mb Jasper JTAG that currently has XBR. I used Flash360 1.0 to back up the NAND of this JTAG. There were some errors in the extraction process (bad blocks). I do NOT have the original nand, and I dont have the ability to hook this up to the usb and extract that way either.

When I try to upgrade this nand with the newest information I get errors in the Jtag Tool (coolshrimp) and the pig one (freeboot maker).

I have the correct cpu key.

With the Jtag Tool I get this error: Your Bad Nand is Not for the same console Type as the clean nand you selected!

When I open it in 360 Flash Dump Tool, under the Key Vault tab it is all full of errors Bad and Bad Key/KV. The file system says no FS root!

But the Jtag works in XBR.


Am I screwed in upgrading this? unsure.gif uhh.gif

#2 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,807 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 11 June 2011 - 04:48 AM

Try dumping your nand using a homebrew app called NAND Flasher 360 for XBOX.

Are you sure you are getting your proper CPU key by booting into Xell?

#3 Piratesmustperish

Piratesmustperish

    X-S Young Member

  • Members
  • Pip
  • 41 posts

Posted 11 June 2011 - 05:46 PM

QUOTE(Ranger72 @ Jun 10 2011, 11:48 PM) View Post

Try dumping your nand using a homebrew app called NAND Flasher 360 for XBOX.

Are you sure you are getting your proper CPU key by booting into Xell?



Thanks for trying to help me man. I know I've typed it in correctly (and am getting it correctly). It still doesn't recognize the keyvault info

While switching to Nand Flasher 360 app I get the following information when I dump my nand:

3 bad blocks:
0x13d
0x157
0x1f2

CB: 6723
nand: 256mb
sb revision: 1

The nand dumps as 66 mb though (I guess that is common for 256/512 mb jaspers)

when I open this dump in any program and insert the right cpu key (from xell) I get all keyvault errors. Did xbr ignore k/v?





#4 Piratesmustperish

Piratesmustperish

    X-S Young Member

  • Members
  • Pip
  • 41 posts

Posted 11 June 2011 - 09:01 PM

Edit:

Okay I got the KV stuff accounted for.

So, Is there any way I can take a "dummy" nand 256 jasper, and insert my kv info and cpu key and make a freeboot image from this nand?

I've tried the xbr to freeboot program and it didn't work for me.

I guess the main question is, "Is there other information that differs between 256 mb Jasper nands BESIDES the cpu key and the KV information?" - I should be able to take those two pieces of information and put them on any "dummy nand" shouldn't I?

#5 Piratesmustperish

Piratesmustperish

    X-S Young Member

  • Members
  • Pip
  • 41 posts

Posted 11 June 2011 - 11:10 PM

Sorry it wont let me edit.


I found the XBRtoFreeboot tutorial and I have backed up everything through xellous.

When I do this command (with the correct information filled in of course):


ibuild.exe c freeBOOT -c [console] -d data\ -p [cpu key]
-b [1bl key] bin\image.bin bin\fuses.bin


the cmd prompt comes back with an error stating, "Too many arguments passed"

How do I get around this?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users