RGH Jasper 512 Block # seems bad 0x00000240

[Lancerguy]

Basically when Using Rawflash v3 I get the error:
Block # seems bad 0x00000240 for every single block all the way to the end.

I saw a similar issue (But the other post also had more problems, and his booted OK, mine doesn't) here: http://team-xecuter.com/forums/showthread.php?p=492075

Here is info on my process:
I have 3 nand dumps using "nandpro usb: -r64 nand1.bin"....etc. NO BAD BLOCKS AT ALL during read. Absolutely no 250 or 0 errors.

I then verified they match using XNandHealer. They match. I then viewed one in XNandHealer, shows correct CB (6750) etc. This also shows no bad blocks and no ecc errors.

So, I used 360 multi builder to create an ecc glitch file. I then used "nandpro usb: +w64 eccimage.ecc" to write this to my nand.

At this point, Xell boots fine every time. I copied down my CPU key, created a txt file for 360 multi builder, and then let it create a "glitch hack image 13604" for me. I put this on a flash, name it nandflash.bin, along with xenon.elf.

When I launch this in Xell I get Block # seems bad: 0x00000240
on every single block all the way up from the beginning.

It tells me to shut down, I wait 30 seconds, reconnect system to power, and boot. Coolrunner does NOT flash green at this point. System does NOT boot at all.

I fix it by using "nandpro usb: -w64 nand1.bin" to reflash my original nand (At this point XBOX works fine like it did B4 RGH), then run "nandpro usb: +w64 eccimage.ecc" to re-glitch for Xell (This also works and Xell boots). This works every time no errors, but I can never get rawflash to work. I have tried just using "nandpro usb: -w64 nandflash.bin" (since I have no bad blocks) to write the fully glitched nand, but that also creates a non-booting xbox.

Any ideas? Again, this is a Jasper 512, I don't have the cap installed because I didn't think it would affect the flashing part and I wasn't going to put it on without testing first. Should I check my solder points? I wouldn't think bad solder joints would cause this but I'm no expert. I have not tried resoldering joints, although they were very secure when I did it, I am a pro at soldering.

 

[Martin C]

then just write the nandflash.bin to your console using nandpro !!!!

 

[kalisto2002]

I have tried just using "nandpro usb: -w64 nandflash.bin" (since I have no bad blocks) to write the fully glitched nand, but that also creates a non-booting xbox.

He said he tried that, these jaspers seem pretty finicky as far as rgh goes.

 

[Martin C]

ok - missed that.

OP - can I see the output of your nandflash.log file as well as a screenshot of your working NAND from 360 Flash Dump Tool?

If it's glitching with the ecc then don't touch any wiring.

 

[frazzeld]

what application did you use to create your glitch image
360_Multi_Builder_v0.4?
I had the same on a 256 but the console boots fine

 

[Lancerguy]

ok - missed that.

OP - can I see the output of your nandflash.log file as well as a screenshot of your working NAND from 360 Flash Dump Tool?

If it's glitching with the ecc then don't touch any wiring.

Sure, here is my nandflash.bin log (named nandflash.bin.txt), a screenshot of 360 Flash Tool on my ORIGINAL NAND (360FDT.jpg), and a screenshot of hte nand after using 360 multi builder (nandflash.jpg) attached. I removed the DVD and CPU key of course.

I am using 360 Multi Builder 0.4. I saw that 0.5 came out yesterday, I might try that but I'll be working all day today.

Thank you so much for the help.

 

[geekay]

I have the exact same problem with mine! Rawflash just spits out errors. The ecc file from multibuilder 0.6 is identical to 0.5. I haven't tried writing the flash using nandx but thinks don't look good seeing how you already tried and it didn't succeed.

 

[GODZYLLA]

Are you sure PD is at 0x000000? I mean, there should be a value in hex.

 

[srt4fun]

Does the green light stop flashing as if it glitched? If so, I had the exact problem with my 512. Try building the glitched image with JTAG Tool or xeBuild.

Are you sure PD is at 0x000000? I mean, there should be a value in hex.

Modified images are 'Zero Paired' so it's correct. Basically, (Correct me if I'm wrong) its a hash of something on your nand, and console specific. Zero paired means it won't check the hash and will accept a modified image.

 

[geekay]

Got mine up and running..

Basically got pissed and restored back to original. Some reason the internal MU wasn't showing up under the memory menu but the system knew there was a profile along with saves. Didn't realize the dash was still 13599 so I updated to 13604 and redumpped. Ran everything through multibuilder 0.6 and same result as before.

This time I wrote the nandflash.bin back with the nandx with +64. System booted to 1 RRoD, just curious I booted with eject and it went into Xell, tried reflashing with rawflash and it worked fine.

 

[Lancerguy]

This issue is fixed. Rawflash was updated to v4 today, that fixed the issue with flashing. Works now.

I still have an issue with slow glitch times, but I can experiment for that, thanks for the suggestions and help solving this problem.