RGH boots into xell but blank screen after flashing SOLUTION

[dwhite5150]

This was my problem.

I have a slim running the rgh. I could boot into xell and retrieve my cpu key. Then, I would build my nand with Jtag tool and Rogero's 360 multi builder. I would flash my xbox and would only get a blank or black screen. I did this many times over multiple computers and spent hours with no love. Could always get xell. Could always flash back to stock. But would always boot into a blank screen.

This was my solution. Please don't flame. This may be something that everyone already knows. All the guides tell you to boot into xell and write down your cpu key. That's important, but for me, that wasn't the only thing that I needed in xell. The guides and tuts should say to get the cpu key and the number of f's you see on lines 7 and 8 and add them together. Literally count the number of f's you see in lines 7 and 8.

Then use 360FlashTool, load up your nand and determine if the highest ldv number is = to the number of f's. Mine wasn't. The LDV number was 8, but my f's were 9. It turns out that the 360 multi builder was using the 8 value when creating my nand.

So, I t went to the my360 folder in the 360 multi builder and found the options.ini file and opened it. I had to manually enter my f number of 9 after the cfldv =. So my .ini file now shows cfldv = 9.

I ran the 360 multi builder again, created my nand, flashed the slim. And now it is working.

Hope this helps someone in the future.

 

[chopblock3xpert]

Thank you sooooooo Much! I have been trying to figure out why I was getting a black screen... This was really starting to frustrate me!

 

[xxWreaperxx]

This should be stickied and included as part of a troubleshooting guide.

 

[Martin C]

This is only a problem when you don't use your current dump.

If you don't follow the standard procedure you WILL have problems - this is just one of them.

 

[vrtclhykr]

Yes you are right Martin but agreed this should be part of someones tutorial or stuck. It has happened to many of us if you read through posts and it will continue to happen. For myself it was a matter of realizing I had not done the $Sys... after the nand read on one of my installs and quickly doing the update then finishing where I left off. Sh!t happens but at the very least it is not catostrophic.



Be sure to remove the edit from your .ini file if you do multiple machines.

 

[GSIBOY]

So true Martin

 

[Martin C]

For myself it was a matter of realizing I had not done the $Sys... after the nand read on one of my installs and quickly doing the update then finishing where I left off. Sh!t happens but at the very least it is not catostrophic.

Then either

a) pay attention to what you're doing.

or

b) invest a little more time than you have to understand how RGH boots into a hacked dash.

I WILL do a quick tutorial when I get the time, but shouldn't really need to - if you're getting to point where you're blindly doing stuff out of sequence, you WILL run into problems and no amount of noob-friendly-pretty-pictures guides will help you. Address the root cause first.