RGH So much for the new dash not affecting RGH

[Miggidy]

I have a Trinity with LT2.0 (never touched backups) and a 640 GB Hitachi hard drive. Had no issues glitching with a Coolrunner running on the previous Dash. Didn't revert back to my original Nand before running the new dash 14699 update via usb. A window pops up indicating that the update would also run a number of security checks, was asked if I wanted to continue or not. I went ahead with the update and bam, black screen. My console was on, but no picture. Power cycled, the coolrunner tried to glitch a couple of times and then it would just quit.

To make a long story short, reprogrammed my coolrunner, erased my nand and reverted back to original. Was then even able to go back on XBL(albeit with a clean 320 gb hard drive, even loaded an old profile). Went back ECC glitched the Nand and loaded Xell no problem. So proceeded to write a hacked Nand, flashed fine. But for what ever reason, my console won't glitch. The coolrunner tries and tries to no avail....

Going back to my original Nand right now....

 

[BenieUK]

dont you have to rebuild after an update as your LDV will of changed by 1 ?

 

[nogarth]

has it been confirmed to use the new Dash as i see posts all over saying dont update.

 

[frazzeld]

And you didn't think that would happen! you were running a custom dash

 

[afiser]

lol, you can't just run an official updater with a hacked dash, of course it wont work. to give you a general overview of the procedure, you must first make a new glitched nand image with the 14699 files with xebuild (google for tutorials on how to do this), then write that to your nand, THEN run the updater from a usb.

 

[Miggidy]

And you didn't think that would happen! you were running a custom dash

I'm new to this stuff.
Guess I learned the hard way....

---------- Post added at 09:21 ---------- Previous post was at 09:19 ----------

lol, you can't just run an official updater with a hacked dash, of course it wont work. to give you a general overview of the procedure, you must first make a new glitched nand image with the 14699 files with xebuild (google for tutorials on how to do this), then write that to your nand, THEN run the updater from a usb.

Thank you for clarifying it dude.
Now off to get this thing back running again....

 

[garageinc]

learn this lesson well mate. in future the cb could be updated and then you will be left with no glitch ever potentially. if you had done that to a phat console it could have been game over for you. never never put an official update on a jtag or rgh unless it is already on the dash in the update and you are adding the avatar stuff.

 

[seanr28]

exactlty, and only run the correct update for the dashboard revision you have for the Avatar update

 

[Miggidy]

Thanks guys.
When it rains it pours,
now my console won't even boot :facepalm:
After a few seconds, the green power LED goes red.

I should point out that when I had reverted back to my original nand, I ran the new 14699 dash update. Everything was working fine so that's when I proceeded with the RGH.
Of coarse I had no idea that this was going to brick my Xbox because I didn't glitch the nand with the new 14699 dash files. I used 360 Multi Builder to create my glitch, and as you know that program glitches your nand with the previous dash files. Am I correct in assuming that this is why my Xbox won't boot with the reset glitch hack, and even when reverting back to my original nand?

Man what a mess I've gotten myself into

 

[ball00]

Ok. If you ran the 14699 avatar and kinect update you may have a conflict between your nand and your hard drive. I had the same thing with a console I was working on.

Does it boot with the hard drive and any usb devices unplugged?

 

[Miggidy]

ball, I used M$'s very own official 14699 update via usb.
The Xbox won't boot either way, with or without the hard drive, usb memory, etc.

 

[ball00]

Have you tried building a glitched nand image of the 14699 nand through xebuild? Can you boot to xell?

 

[bongtoker]

http://team-xecuter.com/forums/showthread.php?t=77106

 

[Miggidy]

I was able to boot Xell earlier....
I'm hoping that creating a glitched image of 14966 will fix it.
Currently looking for a tutorial on how to do it right now....

---------- Post added at 11:37 ---------- Previous post was at 11:30 ----------

http://team-xecuter.com/forums/showthread.php?t=77106

Looks like it's a little advanced for a noob like me but it sounds like my problem. Going to give this a shot in a few hours, it's 3:38am out here :eek2:

 

[bongtoker]

You increased the LDV value when you ran the update and now you need to change your glitch image to match it. Just redump your nand and make a new freeboot with the new dumps, making sure the LDV matches the higher value from after the update.

 

[Miggidy]

You increased the LDV value when you ran the update and now you need to change your glitch image to match it. Just redump your nand and make a new freeboot with the new dumps, making sure the LDV matches the higher value from after the update.

Thank you! Going to try this when I get home in a few hours.

 

[Miggidy]

You increased the LDV value when you ran the update and now you need to change your glitch image to match it. Just redump your nand and make a new freeboot with the new dumps, making sure the LDV matches the higher value from after the update.

Yeah, I think you're right, I probably increased the LDV value because I have a couple of Nand dumps here and both of them show a CF LDV value of 8. One is the original and the other is a later one.
Now here's the thing, back when I upgraded to dash 14699, I didn't dump the Nand. So now I have a new LDV value but I have no clue what it is. Is it safe to assume that it increased by one? Meaning that perhaps it is now 9? If so, how do I go about increasing it to the new value?

 

[Miggidy]

SUCCESS!!!!
Thank you Bongtoker, Ball00, Afiser, Garageinc, and Seanr28!

My LDV value was bumped up....
Geezzz.... What a heade ache..... Lost many hours of sleep lol.

I can't thank you guys enough :biggrin: