RGH 16197 Stock boots, 16197 RGH booted once then not anymore...

[imaphaggit]

So, being mister "oh I'll just update since they released a new one" Probably wasn't a great plan on my part.

I have a Demon and updated to newest dash (via Xbox live) then updated the Demon to the current dash via JRunner (16197).

It loaded once, reinstalled Dashlaunch 3.03 then fired up Fresstyle Dash 3 and loaded a couple games via FTP. Woke up in the morning my Xbox was off. Tried to reboot hacked dash and nothing. Stock dash booted fine. So after looking up, I guess everything passed 15572 isn't glitch-able, but that wouldn't make sense since I had it boot once (crazier things have happend).

Anyway to revert this? Could it be a magical faulty wiring issue out of the blue?

Still have Coolrunner Rev1, Demon, and original NAND dumps with CB 9188 w/ CPU Key or did updating just screw me and force me to wait and buy the new Coolrunner or similar product.

Thanks guys!

Note: I have tried booting into Xell and flashing the firmware on the Demon (glitch) with a CB of 9188 none work. I also tried flashing old stock firmware (CB 9188) to my Xbox and that won't boot either.

 

[-DoC-]

Huh?

Obviously you messed up your update on the demon. The retail update from live is fine on the retail nand but you screwed up something with the demon. Did you make sure you toggled demon before you wrote your image back to demon? Did you have Glitch checked and not Retail?

You will need to post up your jrunner logs for further help.

You should of asked questions before attempting something you weren't sure about.

 

[imaphaggit]

How are you confused?

I updated my stock nand via Xbox Live to 16197. Updated the Demon via Jrunner to 16197 with my original nand dump. (Since the Xbox Live update changes the CB to an unsupported one). This isn't my first time doing this, I've been modding since 2008 DVD drives to JTAG to now RGH.

I obviously had to change the LDV value because I updated via Xbox Live.

Here are the logs you requested I don't know what you want to see exactly but here is the ECC/NAND flash log:

===================================================
Tuesday, November 06, 2012 11:44:04 PM

J-Runner v0.2 Beta (283) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Checking Files
Finished Checking Files
Downloaded *xeBuild/12611/bin/patches_falcon.bin
Downloaded *xeBuild/12611/bin/patches_jasper.bin
Downloaded *xeBuild/12611/bin/patches_xenon.bin
Downloaded *xeBuild/12611/bin/patches_zephyr.bin
Downloaded *xeBuild/12611/_jtag.ini
Finished Checking Files
Downloaded *xeBuild/12625/_jtag.ini
Finished Checking Files
Downloaded *xeBuild/16197/_glitch.ini
Finished Checking Files
Downloaded *xeBuild/9199/bin/patches_falcon.bin
Downloaded *xeBuild/9199/bin/patches_jasper.bin
Downloaded *xeBuild/9199/bin/patches_xenon.bin
Downloaded *xeBuild/9199/bin/patches_zephyr.bin
Downloaded *xeBuild/9199/_jtag.ini
Finished Checking Files
Initializing Nand..
Nand Initialization Finished
Current: DemoN
Switching to XBOX
Success
Current: XBOX
Switching to DemoN
Success
Initializing Nand..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
* unpacking flash image, ....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 3.1
CB_A: 9188
CB_B: 9188
CD (image): 9452
CD (decrypted): 8453
* this image will be valid *only* for: trinity (slim)
* patching SMC...
Patching Trinity version 3.1 SMC at offset 0x13B3
* patching CB_B...
patchset for 9188 found, 4 patch(es)
* constructing new image...
* base size: 70000
* No separate recovery Xell available!
* Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0xFFF (0xE00 bytes) Padding
0x1000..0x3FFF (0x3000 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x9ABF (0x1AC0 bytes) CB_A 9188
0x9AC0..0x112BF (0x7800 bytes) CB_B 9188
0x112C0..0x172BF (0x6000 bytes) CD 8453
0x172C0..0xBFFFF (0xA8D40 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...Done!
------------- Written into output\image_00000000.ecc

DEMON
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0x335
Writing Nand
Done!
in 0:02 min:sec

Load Files Initiliazation Finished
16197
Started Creation of the 16197 xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.05.548
---------------------------------------------------------------
building glitch image
---------------------------------------------------------------
I:\Games\Tools\J-Runner v02 (271) Core Pack\REMOVED\updflash.bin image built, info:
---------------------------------------------------------------
Console : Trinity
NAND size : 16MiB
Build : Glitch
Xell : power on console with console eject button
Serial : REMOVED
ConsoleId : REMOVED
MoboSerial: REMOVED
Mfg Date : 08/11/2010
CPU Key : REMOVED
1BL Key : REMOVED
DVD Key : REMOVED
CF LDV : 11
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

Saved to I:\Games\Tools\J-Runner v02 (271) Core Pack\REMOVED
Image is Ready
DEMON
Hardware : Demon Slim
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Invalid Blocks : 0x335
Writing Nand
Done!
in 0:27 min:sec

I removed information for obvious reasons.

 

[Martin C]

I think the problem here (as with MANY people I've recently discovered) is you bought a DemoN and fitted it yourself and haven't a CLUE what you're doing.

You should be able to perform basic troubleshooting to eliminate the hardware, especially since the stock NAND works.

Dump the 360 NAND and write it to the DemoN. Turn off the CR and it should boot the retail image you wrote to it. If this works, then it's nothing to do with the DemoN hardware.

Next, take that same NAND image and combined with your CPU key, build a 16197 RGH image. Write to the DemoN NAND and enable the coolrunner. Again, it should boot. If it doesn't, then something on the RGH side of the wiring is the problem.

Yep, really basic steps that ANYONE with a DemoN should be doing before even wasting time creating a post. It probably took you 15 mins to start this thread, but you would have known the situation in 5 had you done the basic stuff first.

 

[imaphaggit]

Well seeing that those steps have already been taken before hand. You shouldn't assume that some has a lack of knowledge of the situation even though that information has been left out. Would you like pictures? Diagrams? Possibly a picture of my dog?

Therefore, I wouldn't of posted here if that was the case to waste someones oh so precious internet time.

For being an admin, your remarks might drive Xecuter to lose customers. I understand that this scene is full of egotistical clowns but showing that when you offer a "Premium product" when the "Chinese version" or another company does the job the same. Unfortunately, I figured I'd support Xecuter since (for the most part) are innovators in this field, offer easy use products (again for the most part) and have offered great support in the past. Honestly, if I am banned for this, that's ok and I'm sure there will be no skin off your noses and none off mine, there is a thing called a proxy and new account creation and as many e-mails as my little heart desires. I wouldn't be first or last to stop using these products for something oh so petty.

 

[[AD]]

You said you have created an image from your ORIGINAL nand, you didnt say in your original post that you redumped the 16917 nand from stock and recreated a hacked nand for your demon.

If you havent do it, LDV value has changed etc.

Note: I have tried booting into Xell and flashing the firmware on the Demon (glitch) with a CB of 9188 none work. I also tried flashing old stock firmware (CB 9188) to my Xbox and that won't boot either.

LDV has changed.....

Edit:

Why is it that when Martin C posts a reply that is informative and to the point people get the hump about how it is said to them bitching back and looking for a ban. Why dont you just do what is suggested and if it doesnt solve the problem moan a little more. If it works thank him and move on...

No point getting your knickers in a twist over how something comes across on text.. He's giving help so take it.

 

[Martin C]

Well seeing that those steps have already been taken before hand.

Really? I see no mention of you writing your 360 to the DemoN.

You shouldn't assume that some has a lack of knowledge of the situation even though that information has been left out.

This isn't an assumption - you're talking complete bullshit, especially reading this statement.

Updated the Demon via Jrunner to 16197 with my original nand dump. (Since the Xbox Live update changes the CB to an unsupported one)

I don't need to assume anything - when people write this, it's a clear indicator of them not understanding how it all works. That's fine. We don't EXPECT you to know. We do however expect to you learn by reading and understanding. We're not here to teach you. You bought a product which ON THE CARD says "for professional installation". Why do you think it says that?

So why not follow the troubleshooting steps I laid out for you ever-so-nicely, instead of biting the hand that feeds you.

You don't like my attitude? I'm absolutely fine with that.

I don't like lazy, ignorant people who buy a product, don't know how to use it, can't read the instructional card and then bite back when they're put in their place.

I'll await your results.

 

[imaphaggit]

Really? I see no mention of you writing your 360 to the DemoN.

Yea, I already told you I left that out see statement you quoted above.

This isn't an assumption - you're talking complete bullshit, especially reading this statement.

I had a similar issue happen to me before. I know the "due process". Like I said I'm not new, just cause I'm not active here doesn't mean I am clueless.

I don't need to assume anything - when people write this, it's a clear indicator of them not understanding how it all works. That's fine. We don't EXPECT you to know. We do however expect to you learn by reading and understanding. We're not here to teach you. You bought a product which ON THE CARD says "for professional installation". Why do you think it says that?

Can you explain and show me a so-called "professional" and how does one become professinalized in this field? What school might one attend? Certifications one might recieve? Your "professional" mark on your product is intended for dipshits whom think they can just open up thier Xbox and with the dinky radioshack soldering gun and thier moms hot clue gun can just slap these things in.

So why not follow the troubleshooting steps I laid out for you ever-so-nicely, instead of biting the hand that feeds you.

I have. Wiring looks good. Demon flashed with retail nand doesn't boot Cool Runner is off and on (tired both for sh*ts a giggles). Though I will try re-soldering the CPU_RST and POST_OUT1 just because. The rest are QSB's besides the Demon wiring.

You don't like my attitude? I'm absolutely fine with that.

I don't like lazy, ignorant people who buy a product, don't know how to use it, can't read the instructional card and then bite back when they're put in their place.

I'll await your results.

You are allowed to have an attitude, just not professional for being the "professional's". Yea, because your procduct is OVER COMPLICATED. You have tutorials that cover pretty much every bases. So, its pretty hard just to plane fcuk it up. Unless you are a complete idiot. Which apprently I am not because I did use your tutorial and this thing worked for 2-3 months now with out a hic. Even though I was confused at first about the CR_EN wire.

 

[Martin C]

I've looked over your post and cannot see where you said you tried dumping your working NAND from the 360 and writing it to the DemoN. Care to point it out to me?

 

[imaphaggit]

Here...

 

[Martin C]

Here...

Link To Image

Since (for some alien reason) you have more than one retail NAND dump kept, this doesn't actually tell me anything.

You have your CPU key safe - yes?

Your 360 NAND boots ok - yes?

Delete ALL NAND dumps you have of this console. Yes. Delete them all.

Dump your working NAND from the 360 and write to the DemoN.

set the CR to PRG.

If it doesn't boot, you have a problem with your DemoN install.

 

[imaphaggit]

I have the Original Retial NAND Dump and then Recent Retial NAND Dump.

Yes, I have my CPU key safe.
Yes, 360 NAND boots perfect.

I will try this regardless.

 

[Martin C]

I have the Original Retial NAND Dump and then Recent Retial NAND Dump.

Yes, I have my CPU key safe.
Yes, 360 NAND boots perfect.

I will try this regardless.

I don't see what else you have to try. If this doesn't work then it confirms your DemoN install is the problem.