xboxscene.org forums

Author Topic: Problem With Degraded And 360 Flash Dump Tool?  (Read 66 times)

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« on: January 10, 2010, 03:49:00 PM »

OK...
I have a 512 Jasper and Im finally trying to get XBReboot installed.  I am using an LPT cable.  I have done 4 full reads just to be super safe.  And I have also done 3 16mb reads.  So far Read 1 and 3 match up with total commander 100% but Read 2 was off by 20 errors.  So I tossed it.  Now here comes my problem...
     I have opened Read 1 and 3 up in 360 Flash Dump Tool v0.91 and I got my CB,CD, and CE info but on the right hand side it says "No FS root".  I don't get any of that info I have seen in other dumps from tutorials.  Also I have tried using Degraded 1.1 but when I open up Read 1 or 3  it just crashes and asks if I want to debug or check online for a solution?  Is there something wrong with my dumps?  Or are there bugs in these 2 tools?  Or have I done something wrong?
Thanks
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #1 on: January 10, 2010, 09:20:00 PM »

anyone got any ideas?
Logged

xxpittbullxx

  • Archived User
  • Full Member
  • *
  • Posts: 141
Problem With Degraded And 360 Flash Dump Tool?
« Reply #2 on: January 10, 2010, 09:36:00 PM »

Flash Dump Tool v0.91 and Degraded are not Compatible with Big block Nands as of yet
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #3 on: January 10, 2010, 10:00:00 PM »

I know that.  Im not trying to check a large nand in either program.  I did what I thought you were supposed to do to make a small 16mb image so that I could check my CB info.  Problem is even after I hex edit them to say 2004-2005 it still wont open properly in either one.  I just plain old cant open up a 16mb image in degraded 1.1 but I can open it in 360 flash tool.  But on the right hand side mine says no fs root.
Logged

ujackspades

  • Archived User
  • Newbie
  • *
  • Posts: 6
Problem With Degraded And 360 Flash Dump Tool?
« Reply #4 on: January 10, 2010, 11:02:00 PM »

Hey can you give me the link to the degraded program? Searched everywhere and I can't find it.

Thanks!
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #5 on: January 10, 2010, 11:07:00 PM »

it was on xbins...
Logged

xxpittbullxx

  • Archived User
  • Full Member
  • *
  • Posts: 141
Problem With Degraded And 360 Flash Dump Tool?
« Reply #6 on: January 11, 2010, 07:06:00 AM »

Whether you dump the whole 512 or 16megs its still a big block, so support is limited
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #7 on: January 11, 2010, 09:14:00 AM »

See I tried to use a 16 mb dump of a 512 nand and tried to use that to extract the rawk and rawconfig and then I've tried injecting those into XBReboot _JasperBB_8955_3 which is for BigBlocks?  So I used a small nand dump with a Big Block version of XBReeboot.  That didnt work.
So then I tried taking another 16mb nand dump and used that to do the same process to XBReboot_Jasper16_8955_3.  That didnt work...
Logged

xxpittbullxx

  • Archived User
  • Full Member
  • *
  • Posts: 141
Problem With Degraded And 360 Flash Dump Tool?
« Reply #8 on: January 11, 2010, 09:45:00 AM »

Cant you just grab the rkv.bin and rconfig.bin out of your orig. 512 dump?
That would be my recommendation
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #9 on: January 11, 2010, 10:06:00 AM »

Well I have done that.  But Ive tried injecting that into the "jasper_6723_hack_for_256mb_512mb" once and tried that.  Didnt work.  
I have 2-3 really basic questions.  First off, there is the LPT wires.  I can leave those soldered in for the entire process from reading to writing to even leaving them soldered in while I boot the xbox up afterward to check if its working?  As long as I unplug the lpt end from my flashng computer?  But what about the 3 SPI wires?  Do I need to unsolder them afterward to check if everythings working?  Cause I was  following this thread and they mention that...http://forums.xbox-scene.com/index.php?showtopic=698328
Im just worried that I might have a good flash but Im supposed to unsolder the SPI wires afterward, and if I dont Im just gonna keep getting rrod.
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #10 on: January 11, 2010, 11:50:00 AM »

OK I managed to take (jasper_6723_hack_for_256mb_512mb) and renamed it xbr.bin and did a (NandPro lpt: -w64 xbr.bin) It now boots to xell.  But I had to use a AV cable not a HDMI to get video.
Logged

Poopchute

  • Archived User
  • Full Member
  • *
  • Posts: 191
Problem With Degraded And 360 Flash Dump Tool?
« Reply #11 on: January 11, 2010, 01:29:00 PM »

QUOTE(xxpittbullxx @ Jan 11 2010, 10:45 AM) *

Cant you just grab the rkv.bin and rconfig.bin out of your orig. 512 dump?
That would be my recommendation

What size should I use?  nandpro orig.bin: -r16 rawkv.bin 1 1 or  nandpro orig.bin: -r64 rawkv.bin 1 1 ?  
Or 512?  
Like Ive said I have managed to get Xell booted and get my cpu key but thats it...

So what size should I use to extract the rawk and rawconfig from a 512 nand?  Or should I be using a 16mb version of my nand instead since there is little support?  I think if I get this Ill be done...
Logged

xxpittbullxx

  • Archived User
  • Full Member
  • *
  • Posts: 141
Problem With Degraded And 360 Flash Dump Tool?
« Reply #12 on: January 11, 2010, 06:30:00 PM »

QUOTE(Poopchute @ Jan 11 2010, 03:29 PM) *

What size should I use?  nandpro orig.bin: -r16 rawkv.bin 1 1 or  nandpro orig.bin: -r64 rawkv.bin 1 1 ?  
Or 512?  
Like Ive said I have managed to get Xell booted and get my cpu key but thats it...

So what size should I use to extract the rawk and rawconfig from a 512 nand?  Or should I be using a 16mb version of my nand instead since there is little support?  I think if I get this Ill be done...

nandpro orig.bin: -r512 rawkv.bin 1 1
Logged