RGH Jasper256 Fan always 100% - Bad block?

[Alienfreak]

Hey,

I read my NAND with nandpro2.0e and it gives me a badblock at 288 (so not in ECC range).

Then I take it and make a .ECC out of it via Python and flash it with nandpro (-w16).
Xell boots up fast all nice and sound, but already there the Fans are at maximum.

In Xell I dump my NAND and make an patched NAND via Multibuilder 0.7 (I inserted my cfldv by hand).

If I take a look at it with Flash Dump Tool or Xnand Healer 0.72 I see two errors

-> Block ID 0x01A5 found @ 0x1FE
-> Block ID 0x0051 found @ 0x1FF

That would mean he has found two bad blocks and moved them? So I have to do nothing?

So I go on and flash it via Xell (with the xenon.elf) and the flashing there throws out two errors, too, which are at 1A5 and 51.

It then, again, boots nice and sound into NXE but the Fans stay at maximum and even in FSD 2.2 I cannot set them lower?


Is this a bad block I didn't notice?

 

[xxWreaperxx]

I believe Jtag Tool has an option called:

"Repair Bad Blocks"

Use that. Here is a tut I found for an older version of jtag tool but the principle should be the same.

[ame="http://www.youtube.com/watch?v=-RPh1jxGOho"]Jtag Tool Tutorial (Remap Bad Blocks) - Coolshrimp - YouTube[/ame]

 

[Alienfreak]

I believe Jtag Tool has an option called:

"Repair Bad Blocks"

Use that. Here is a tut I found for an older version of jtag tool but the principle should be the same.

Jtag Tool Tutorial (Remap Bad Blocks) - Coolshrimp - YouTube

Sorry but that didn't help and Multibuilder uses xeBuilder which is supposed to do that on itself!

Also this Box is already REALLY LOUD in Xell Reloaded. When I boot my JTAG into Xell its on Auto and not loud at all...

But probably its just the different Xell?

 

[xxWreaperxx]

What do you mean it didn't help? Did you try using jtag tool to remap the bad blocks and then flashing to the box?

---------- Post added at 15:30 ---------- Previous post was at 15:29 ----------

Another thing you could try is using the fan speed patch that you can find in the usual places and patch to auto using fsd's file manager or something that lets you execute xex files.

 

[Alienfreak]

What do you mean it didn't help? Did you try using jtag tool to remap the bad blocks and then flashing to the box?

---------- Post added at 15:30 ---------- Previous post was at 15:29 ----------

Another thing you could try is using the fan speed patch that you can find in the usual places and patch to auto using fsd's file manager or something that lets you execute xex files.

I moved them with JTAG Tool but nothing changed.

Why are there differences in nandpro and xell locations anyway? Once I read my NAND with nandpro I get an error at 288 but every analysis tool I used up to now doesn't show anything at 288 (except Xnandhealer which quits there with an error) but two different errors I don't have with reading via nandpro

 

[xxWreaperxx]

Try patching nand with the fanspeed patch. Use the "auto" file.

---------- Post added at 19:29 ---------- Previous post was at 19:28 ----------

Send me your nand dump if you want to and I can take a look.

 

[Alienfreak]

I used an fanspeed patcher from xbox iso now but those aren't doing anything (I apply them and then power cycle).

I read a bit into the issue and now I understand that 288 is 51 due to the 16kb to 132kb counting.
I can read my nand as often as I want but I won't get any errors except the 288 (and the 7 consecuting ones, ofc).
Plus I retried remapping myself but that didn't help either.

Also I played around with all the settings inside Multibuilder to get a good image. Sadly nothing helps :/