FIXED NOOB HERE - Flashed Hacked Image to Falcon, can no longer go to stock dashboard

[nhannon9]

Hey all,

Noob here, so sorry if this is the wrong section or I'm asking a ridiculous question. Guess that's what this section is for.

I just tried an upgrade to the latest 16756 kernel on my Falcon RGH. I've done numerous updates prior to this, and I followed the same procedure. Got my dump from Simple 360 NAND Flasher, created the hacked image w/ my CPU key in xeBuild, and then went to flash it in 360 NAND Flasher.

Now, when I originally got my NAND dump, it said there were two bad blocks, or what at least seemed to be bad blocks - 0x149 and 0x15x, I can't remember the last number in the second block. Now, I ignored it, and used the dump to create the hacked image anyway. I then went to flash the hacked image, and once again, once I started the flash, it stated the two bad blocks again. It was too late to stop it now, I know better than to turn off an RGH while flashing.

It finished the flash, and instead of showing the countdown, it instantly killed the Xbox. I unplugged it, plugged it back in, and it starts up just fine - only to FreeStyle Dash 3, as my dash launch is set to automatically bring me there upon startup, rather than stock dashboard. I think this saved me here, because if I try to go back to the main, stock dashboard and/or system settings to verify software version, the console kills out and I get a black screen and a single RRoD quadrant in the bottom right-corner. (4th)

Any ideas how to fix this? I need to have access to the main dashboard, obviously. I can't live on FSD forever, and I'm a bit worried because this is the first issue I've ever run into. :eek2:

Thanks so much!

~nhannon9

 

[AllyNerd]

Idk the files were released for the latest dash. I build the dash right before the latest which is 16747 I think...

 

[nhannon9]

So, do you have any help or ideas? Perhaps I use that same dump to build a hacked image of the dashboard right before 16756?

 

[gazcoigne]

i have found that holding RB whilts in the main FSD dash only returns me to the same FSD dash, and that i have to launch something else like a game or emulator etc, then hit the miniblade, choose exit to dash and hold RB to get NXE dash.

try reinstalling your dashlaunch also.

 

[Ac1dR3d]

if it launches FSD then it will launch stcok dash too... dont think you have any reasons to worry. bad blocks are remapped during creation of RGH image. you can just start stock dash with no fear of RRoD ... because rrod is not caused by NAND image.

 

[Martin C]

Post your logs & pics etc as per the template. Bad blocks can stop the normal dash from booting (but allow FSD to run).

 

[gazcoigne]

if it launches FSD then it will launch stcok dash too... dont think you have any reasons to worry. bad blocks are remapped during creation of RGH image. you can just start stock dash with no fear of RRoD ... because rrod is not caused by NAND image.

this is complete nonsense

 

[nhannon9]

Okay, so I tried both re-flashing 16756 once again in Simple Flasher as well as via Xell itself - no luck. Now, when I boot up, the fans don't even run normal speed until I get into FSD which has the manual fan controller. And yeah, I'm able to play games, watch movies, etc. It all works, EXCEPT, if I try to get to NXE in any way possible, through miniblade, through System Settings in the miniblade, even through the xex, I get an E71 with the single RRoD quadrant. I'll reflash one last time for an updated Simple 360 log file and post it here.

 

[gavin_darkglide]

Use j-runner, it automatically remaps bad blocks.

 

[nhannon9]

I fixed it! I completely re-did my 16756 kernel folder in xeBuild with the latest download from Xbox's site, and re-created my hacked image, and rather than using Simple 360 Flasher, I used the original, 1.0 version of Flash 360.

Thanks for your help!