Xbox 360 Not booting after Dashboard Update (RGH)

[JTAG-Aurora]

Hello everyone, I hope you're doing well.
Two days ago I brought an Xbox 360 Slim Trinity and tried to update its dashboard to the latest 17559 version. I used another forum's guide to this as I was a fair noob at this. Used Simple NANDFlasher to get the dump, used Xebuild to build the image and performed the flash and everything went like a charm.

However, as I booted the console back up again, the Xbox logo came out, pulsating as usual, "User has connected" was shown and then everything froze in that very same Xbox Logo screen, it then went all black and then showed me the same logo screen but all torn up and the console shows a soft red ring.

I tried doing the process again, however now S-NANDFlasher tells me that there's no dump found and then goes to show me a Black screen of Death, the "Xbox critical error, contact customer service..."
So I searched and searched, tried the methods about plugins, turns out I had no plugins on to begin with but it still doesn't work, doesn't matter if I boot it and press eject after or if I boot it using a USB with a blank launch.ini file.

The console does boot up using Dashlaunch and Xell though.

Then I came here and found InsaneNutter's guide with NANDFlasher360 and how you should flash an RGH console with Xell. Followed it, everything worked well as I even got a new dump for it. (although I should point out that at some point during the flash, Xell did show me something about blacks and the (AKA it's really bad)) but still, it didn't work.
In the comment section, he said to an inquirer that should this problem arises, one should get the console's IP and go the Xell webpage download the "rawflash" and create a new image using it. Did so and it was a pain to access that webpage but still, didn't work.

Additional details that might be of use but I'm not sure about: In the very first guide I followed, it said that I should build the image on Xebuild using Freeboot RGH2 if I have a Trinity but the soft kept telling me I should use an RGH1, I ignored the soft and went for RGH2. Later using Dashlaunch it showed Glitch2, but I don't know if it was there before or it's just because of my flash.
Also, tried different HDMI Cables and TV monitors and taking out the HDD, nothing helped.
EDIT: I found out that if I boot the Xbox normally a RROD appears and nothing works but if I boot it using NANDFlasher360's Default.xex on a USB, the console freezes but without RROD and I can show up the Xbox Overlay Menu by pressing the Xbox Button on the controller.

Now I'm totally out of options. Anyone could help with this please? When I boot it using Dashlaunch it does show that the dashboard is on the 17559 version but it doesn't boot up. Did I fry something?

Thanks in advance.

 

[InsaneNutter]

When flashing Xell should re map any bad blocks so they shouldn't be an issue.

So on any combination of the updates you have done can you get the console to boot to the normal MS dashboard? or does it always crash before then?

If you still have the nand backup of the original nand dump you made before updating the console that should be enough for XeBuild GUI to obtain all the settings used for building that nand. That's always how i've updated. Can you find out from where you purchased the console if its RGH1 or 2? i suspect that could be the issue.

 

[JTAG-Aurora]

Thanks for the reply !
To answer you, nope, not a single one and I have done many. As of yesterday I even tried going back to an older kernel (17554) but it didn't work at all(Although by booting with Dashlaunch it shows the kernel is on 17554). It doesn't get past the Xlogo and has a RROD. The farthest I took it is when I booted the console with NANDFlash360's default.xex (the one you used in your guide) and I could show up the Xbox Guide Menu by pressing the Xbox button on the controller, but nothing more than that, if I press "home" it's a BSOD.

Unfortunately no. It's not mine and even the dude who gave it to me for the update bought it second hand. I have no idea where it came from and even if I did I couldn't go to the seller as the whole country is on lockdown where I'm due to the COVID pandemic.

On the first day, I generated the flash image by checking RGH2 as it was what was written on the guide(RGH2 for a Trinity) but what if the Xbox was on RGH1 and I flashed it with that image? Would it brick it? How bad would it be I mean?
Because Xebuild kept advising me that RGH1 is the current option to check but I simply ignored it. Later on, using Dashlaunch it showed glitch2 but I don't know if it's because my update or it was always that.
I still have the original dump file and even got the "rawflash" from the Xell Webgui.

 

[InsaneNutter]

If you have the Nand backup from when you got the console and before you started trying to updated it i'd just restore that from Xell using a usb memory stick.

Xell should remap any bad blocks when flashing which i suspect could be the issue here, and you should be on a known working configuration then.

Hopefully do that and at least the console is in a working state.

 

[JTAG-Aurora]

No Luck, it didn't work.
During all flashes, Xell tells me that "block 0xcf seems bad, status 0x00000210. Block cannot be recovered (aka it's really bad)."
then proceeds to write the image.

 

[InsaneNutter]

It (should) ignore that block and write the data that should be there to another block and re map it if all goes correctly. However I suspect that might not be happening which is why you end up with a some what working dashboard.

Someone who knows more than me on the Team-Xecuter forums might have some suggestions to better help you: https://team-xecuter.com/community/forums/rgh-jtag-4-noobs.86/ it's been a long time since I did any sort of 360 modding so i'm a bit stuck on what would be best for you to do now. The Xbox 360 modding scene there still seems very active so hopefully you can get some other suggestions on what to try.

 

[JTAG-Aurora]

Thanks for the help! Much appreciated.

 

[FaresPoll]

hello everyone hope you are all doing good, I came here to ask some of you to help me solve the problem that I just got on my Xbox 360 so I wanted to update the dashboard cause I didn't have avatars and I had the 17511 old dash so I dumped with Simple 360 Nand Flasher and I used the xebuild GUI to build the and image and then I got the updflash.bin successfully, but then when I flashed the Xbox using Simple 360 Nand Flasher It went on success and obviously, the Xbox will shut off and boot up again but the problem here is that when I try to turn it on it doesn't display on the tv and the controller is always flashing the four green rings ;the center dot of the console is on but no green rings shown
any suggestions please just reply to me i really need to fix this problem
Thank you

 

[InsaneNutter]

You can try restoring the nand backup you made with Simple 360 Nand Flasher. Ensure its named updflash.bin and copy it to a FAT32 formatted USB flash drive and power the 360 on with the eject button.

Xell should boot and flash the nand back.

 

[Motazmorsli]

Hello I'm also having a similar problem after flashing my nand with simple flasher
Now the console boot and then turn off after 1 second and I cant get into xell because eject button doesnt work. What are my options
I also noticed on exbuild gui when I pressed check for motherboard it showed me a cross and I have to select it manually
I also tried to change the region from pal to ntsc
Those could be the problem

 

[InsaneNutter]

From what you have said you have flashed a bad nand to the Xbox so have essentially bricked it.

If you can't get in to Xell then the only option is to solder a hardware nand flasher to the motherboard and flash a previous working nand backup to the Xbox 360.