simple question

[vb_encryption_vb]

During an RGH writing the nand back failed, console won't boot at all now, I am getting stand by power, tried shorting the nand with no aval.

Anyhow is it possible to take a Demon and Coolrunner, write the NAND to the demon and just boot console from Demon?

Yes I have a valid NAND dump of the original. Console is a falcon, was having issues with glitches as it would not glitch with HD or DVD installed, so was going to erase NAND and write back, which failed on the write back and got the no flash controller detected error. It's all I get now.

 

[nofeloniesyet]

During an RGH writing the nand back failed, console won't boot at all now, I am getting stand by power, tried shorting the nand with no aval.

Anyhow is it possible to take a Demon and Coolrunner, write the NAND to the demon and just boot console from Demon?

Yes I have a valid NAND dump of the original. Console is a falcon, was having issues with glitches as it would not glitch with HD or DVD installed, so was going to erase NAND and write back, which failed on the write back and got the no flash controller detected error. It's all I get now.

try another erase of the nand,you will have to time it just right.put power plug in console,but not enough to give it standby jus yet,then type erase cmnd in nandpro,and as sooooon as u hit enter,plug power in,if successfull ull see it erase,this should solve the problem.most likley your smc was corrupted on bad write and thats y u get no flash config.

 

[Oggy]

You can also just write the stock nand, using the demon to interface it.

 

[vb_encryption_vb]

try another erase of the nand,you will have to time it just right.put power plug in console,but not enough to give it standby jus yet,then type erase cmnd in nandpro,and as sooooon as u hit enter,plug power in,if successfull ull see it erase,this should solve the problem.most likley your smc was corrupted on bad write and thats y u get no flash config.

Tried multiple times, seems I can't get the timing on that right. Tried all night last night.

You can also just write the stock nand, using the demon to interface it.

That's what I was wanting to know, so basically I can do a wire install on the Demon, use it to write the NAND back. Remove Demon and all should be fine once again?

 

[Steel City Mods]

Tried multiple times, seems I can't get the timing on that right. Tried all night last night.



That's what I was wanting to know, so basically I can do a wire install on the Demon, use it to write the NAND back. Remove Demon and all should be fine once again?

Yes.

 

[vb_encryption_vb]

Still not booting. Just the demon is installed trying to boot stock nand off demon. Seems I cannot interface with 360 nand at all to write orig nand back as well. I must be missing something somewhere.

Thanks.

 

[Martin C]

I'm amazed that there are no errors when you're trying to read/write to the 360 NAND via SPI or DemoN.

 

[vb_encryption_vb]

I'm amazed that there are no errors when you're trying to read/write to the 360 NAND via SPI or DemoN.

What exactly do you mean?

 

[Oggy]

Why is your 5v STBY at 3.3v ?

 

[COMPLETE_TOOL]

very nice soldering

 

[vb_encryption_vb]

Why is your 5v STBY at 3.3v ?

I followed the install tutorial and installed it as it said.?

 

[Oggy]

Apologies, I based it on another header.

 

[vb_encryption_vb]

No worries? Any ideas what could be the issue at this point?

 

[Martin C]

What exactly do you mean?

I mean, whenever I've had an issue with either SPI or NAND interfaces, I get an error. I've never had a time when there was nothing at all.

Just surprising, that's all since all apps have an error function to output for troubleshooting.

You sure you're actually clicking the buttons?

 

[vb_encryption_vb]

===================================================
Thursday, January 10, 2013 6:26:05 AM

J-Runner v0.2 Beta (284) Started


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

Consider fellow users, Save bandwidth, please have only minimum number of dashes selected.
Checking Files
Finished Checking Files
Current: DemoN
Switching to XBOX
Success
Initializing nanddump1.bin..
CpuKey is Correct
Key already Exists
Nand Initialization Finished
XBOX360
device for code 7B not found

DEMON
Cancelled
Current: DemoN
Switching to XBOX
Success
XBOX360
device for code 7B not found

XBOX360
device for code 7B not found

Current: XBOX
Switching to DemoN
Success
DEMON
Hardware : Demon Phat
Firmware : 1.0
Flash ID : 0x73AD Hynix (16MiB - Small block)
Flash Size : 0x400 blocks of 0x4200 bytes
Writing Nand
Done!
in 0:36 min:sec

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


Clicked some buttons, saved to USB. Transferred to laptop, came here made a quick reply...will wait patiently for a smart ass comment.

 

[Oggy]

Whenever I couldnt get an ID on the stock nand, I touched up my soldering and it worked after....

 

[Martin C]

will wait patiently for a smart ass comment.

I won't disappoint then.

How come it's taken you 7 posts in this thread to actually post anything of use?

Don't you think posting the error message itself might have been useful? Oh no, of course not - we're all f**king mind readers on here.

You then have the cheek to post what you did. So seriously, do you want help or are you just posting on here for the fun of it? You've not posted any results on continuity testing, both between the DemoN to the 360 NAND, or neighboring points to ensure there are no shorts.

If you don't have the common sense to at least see that an error code is useful, you're wasting your time. It appears you have a fault with the console since you couldn't get the SPI to work (again, no error messages or readouts from the SPI points so more Gipsy Rose Lee guesswork). I would therefore look to someone to repair it before going any further or wasting anyone else's time.

Now how's that for a smartass comment, smartass?

 

[MrBucket101]

I won't disappoint then.

How come it's taken you 7 posts in this thread to actually post anything of use?

Don't you think posting the error message itself might have been useful? Oh no, of course not - we're all fcuking mind readers on here.

You then have the cheek to post what you did. So seriously, do you want help or are you just posting on here for the fun of it? You've not posted any results on continuity testing, both between the DemoN to the 360 NAND, or neighboring points to ensure there are no shorts.

If you don't have the common sense to at least see that an error code is useful, you're wasting your time. It appears you have a fault with the console since you couldn't get the SPI to work (again, no error messages or readouts from the SPI points so more Gipsy Rose Lee guesswork). I would therefore look to someone to repair it before going any further or wasting anyone else's time.

Now how's that for a smartass comment, smartass?

aaaaand boom goes the dynamite

 

[vb_encryption_vb]

I won't disappoint then.

How come it's taken you 7 posts in this thread to actually post anything of use?

Don't you think posting the error message itself might have been useful? Oh no, of course not - we're all fcuking mind readers on here.

You then have the cheek to post what you did. So seriously, do you want help or are you just posting on here for the fun of it? You've not posted any results on continuity testing, both between the DemoN to the 360 NAND, or neighboring points to ensure there are no shorts.

If you don't have the common sense to at least see that an error code is useful, you're wasting your time. It appears you have a fault with the console since you couldn't get the SPI to work (again, no error messages or readouts from the SPI points so more Gipsy Rose Lee guesswork). I would therefore look to someone to repair it before going any further or wasting anyone else's time.

Now how's that for a smartass comment, smartass?

Only 5 post were related to the actual demon install and my first post stated the SPI read out error "no controller found"

Sorry not everyone comes in here and post every little thing they did to get to where they are, we all can't sit around all day in our mothers basements waiting on someone to post just to ridicule them with non sense on how they didn't post a picture of soldering, or what the readout says from Jrunner. Wouldn't it have been easier to just move on and leave the topic be? We buy Xecuter products, install them and run into an occasional error. So we ask for help and either get called a dumbass or get banned for being a smartass back.


Back on topic, I'll touch up soldering and see if anything changes. Thanks to those that helped and thanks Martin for the laugh.