RGH Possible brick?

[oniZM]

Hello.
Today I decided to upgrade my RGH from dash 14699 to 16547 (Fat Jasper V2 512MB - unfortunately I didn't do the hardware part, so I don't know the precise chip it mounts. Should be either CoolRunner or J-Runner).
I started fresh using my original vanilla dump, I used XebuildGUI 2.092 and flashed the result with RawFlash v4 on Xell.
Everything went smooth, then I installed the avatar upgrade, Dashlaunch 3.11 and FSD3-r775. Everything working till now.

Then I went crazy for a moment and decided to upgrade Xell (forgetting that it was already upgraded in the process), so I downloaded the 0.993 binaries from the official Libxenon thread and flashed the appropriate file via usb.
Now the console doesn't boot. No Xell with eject, no dash whatsoever.

I confronted the hash of the file I used and the one inside the XebuildGUI folder, and they're the same identical file, 0.993 version.

What can I do?

 

[Taijigamer2]

Flash back your 16547 rgh image with a NAND flasher. As u've corrupted your image somehow u will have to fix it by opening the Xbox and using direct writing to the NANd ( either spi NAND flasher or demon chip).

 

[gazcoigne]

and BTW J-runner is the PC application used to read/write and build NAND images

its not a glitch chip

please read and understand what it is your trying to do before you start messing about with a soldering iron.

 

[oniZM]

Flash back your 15437 rgh image with a NAND flasher. As u've corrupted your image somehow u will have to fix it by opening the Xbox and using direct writing to the NANd ( either spi NAND flasher or demon chip).

You mean 16547 right?
I wonder how could it corrupt while flashing the same exact file though...

and BTW J-runner is the PC application used to read/write and build NAND images

its not a glitch chip

please read and understand what it is your trying to do before you start messing about with a soldering iron.

Yeah I got confused there... I understand the software part (not as good as i thought apparently... but it's my first problem in some years of modding) but I'm not so good with chips/soldering, that's why I outsourced the process in the first place
Can you help me by telling me what nand programmer should I consider, so I can read some guides and think about it?

 

[Taijigamer2]

You mean 16547 right?
I wonder how could it corrupt while flashing the same exact file though...

Sorry about that, I have edited the post accordingly. Not sure where I got 15437, lol. NAND-x used to be the programmer of choice but now its the JR-Programmer v2, cheap and provides Rater support. There are numerous stickies on this site to do with nand reading/writing and RGH. Like gazcoigne said, u need to read and understand before jumping in. It may be easier to send it to the guy who originally did the mod as this may be less time and effort than learning how to fix it yourself. Do you have the xebuild log for your glitch image and how did u name the xell file on usb?

 

[oniZM]

Sorry about that, I have edited the post accordingly. Not sure where I got 15437, lol. NAND-x used to be the programmer of choice but now its the JR-Programmer v2, cheap and provides Rater support. There are numerous stickies on this site to do with nand reading/writing and RGH. Like gazcoigne said, u need to read and understand before jumping in. It may be easier to send it to the guy who originally did the mod as this may be less time and effort than learning how to fix it yourself. Do you have the xebuild log for your glitch image and how did u name the xell file on usb?

Thanks for the info. In the meantime I opened my 360 and I can confirm the chip is a CoolRunner Rev B.
I prefer to learn this myself rather than making someone else do it, because I may need it again (you never know.. ) and also it would cost me too much, it's not worth it.

Here's the Xebuild log (I removed serial numbers and stuff), but I can tell that the nand flash wasn't the problem since I tested it and it was working well.
The file on the Xell usb was originally "xell-gggggg.bin" and I renamed it "updxell.bin" as the readme said. File CRC is BCCA51DE, the same can be found under "xeBuild_GUI_2.092\files\xell\Xellreloaded_glitch.bin" (which I assume the automated process used, also BCCA51DE).