jasper256 xell can boot but dash/stock not

[jaku329]

Hello guys,
 
I have a jasper256.
it can boot in Xell, but can't boot in dash.
black screen, no any red LED lights, no RROD, just green LED of center lights.

after removing glitch-chip and wiring, I used nandpro to write original nand.
it's the same, system can't boot, no RROD, just green LED lights.
 
Tried different LDV. less LDV has 3 RROD with 0022. so i think the problem is not about LDV.
Used 360 flash tool to patch cpu key and LDV to another japser256 nand with the same CB6750,
it not work too, still black screen, no RROD.

Could any one give me some ideas?

If xell can boot, seems the problem is about nand issue but not hardware issue, right?
 

[Xumpy]

In these cases I always suggest people to try until the original dash runs again.

First. Are you 100% sure that your original dump is correct. When the smc isn't patched the xbox should rrod after 5 tries (let's say 30 seconds).

Did you updated your console after you had made the original dump?

Also after desoldering the chip be aware that you clean up the motherboard so no left overs are making a short or something like that...

I see that you have a 256mb nand. Did you use a usb flasher??

Regards

Xump

[jaku329]

Hi Xump,

Thanks for comments.

Now, I'm trying to boot it with original nand. but it's black screen and no RROD after more than 2mins.

I'm sure that no update after dump the original nand...
for your mention, I double check the motherboard, I think it's clean.

I just found one thing,
when I using 360 Flash Tool(v0.97) to extract kernels of original nand(CF patch0 is 13604),
it pops a dialog to show "ApplyKernelPatch: Failed to apply Patch V13604, it appears to be corrupt"

For another xbox360's original nand(CF patch0 is 8955), it can extract with no error.

then I tried J-Runner/XeBuild GUI to build retail-nand for 13599, 13604, 14699,
those are based on above extract-able nand(8955), but they cannot be extracted as well.(the same error)
So, the original nand is corrupt ? or just 360 Flash tool cant extract kernel for those above v13599 ?

Maybe I have to find another donor nand to verify.

[Xumpy]

Donor nand couldn't hurt I think. The only way that an xbox would not rrod with a retail nand is that the smc is somehow looping like we do in the rgh.

Normal smc should stop after 5 tries.

I thought you can also use a previous xebuild to rebuild your original...

Regards

[neonpolaris]

Just to rule out the obvious, when you flashed back to the stock nand, you disconnected the glitch chip and disconnected power for a bit (to reload the new smc), yes?

[jaku329]

Hi Xump,

Probably, like you said, the problem is about smc, (controller can't sync with console, LEDs flash cycularly)

I will try use previous xeBuild to build the retail nand..

How about using the smc & smc_config of donor nand to build retail nand ?
if both of smc version are the same, is it workable in practice ?


To neonpolaris,

After flashing nand, I always switch power off until adapter doesn't light, then switch power on to see the result.
I will just remove power core from motherboard.

[Xumpy]

First, it's always better to unplug power from the mainboard and wait a couple off seconds from then.

Beside of that I do not think that the smc is the only problem with your original nand and be aware that if you flash an incorrect smc to your nand your xbox might be bricked.

You see, the smc takes over the south bridge when it is loaded from nand. This includes the SPI to write to the nand.
So you would recieve the "can not detect flash controller" error if you flash an smc from let's say a xenon board to a falcon cause the xenon handles the SPI different as the falcon.

The only way to restore from this is to start flashing your image before the smc from nand is loaded or prevent the smc in the nand from loading.
There are some tutorials out there how to do this but it's not that easy...

But in the end I have to agree with neonpolaris here. If the smc is broken or empty in the nand the xbox should not load it and should still rrod after 5 tries.
So it seems to me that the smc from the rgh remains into the board. The most likely possibility has to do with the power not disconnected from the board.

Try to flash your original nand and unplug power from the mainboard side. Wait for 10 seconds or so and replug the mainboard back in.

The xbox should at least rrod after 30 seconds or so...

Regards

[jaku329]

Update:

still black screen with one green light.
My process is
1. unplug power from motherboard, setup pins of nand-flasher(Matrix's product)
2. plug-in the usb cable of nand-flasher to PC.
3. plug-in power to motherboard,
4. nandPro.exe usb: -w64 nand1.bin, waiting for finish
5. unplug power again then wait seconds
6. remove USB from PC, then remove nand-flasher from motherboard.
7. plug-in power to motherboard, see the result.

Is there any step wrong??

PS: the green LED was flashing when I remove power connector of DVD device from motherboard.
     So southbridge seems to work.

Still don't know how to solve it.....sad....
Anyway, thanks for your time.

[Xumpy]

Did you do that with your original nand?

[jaku329]

yes, these days, I did all trials with original nand and retail nand built from XeBuildGUI/J-Runner...

today I wired up glitch-chip again, It's ok to boot xell, but still can't boot dash.

the same problem with retail and hacked nand, it looks like hang up in a unknown state.

[Xumpy]

Ok then you should really try a donor nand cause it should rrod after 30 seconds. Remove the glitch chip and clean up your motherboard for solder left overs.

Regards

[jaku329]

I did try a donor nand(CB6750, CF8955).
It will be RROD cause invalid LDV, I can fix it if LDV count is correct, but then still block screen...

I always used the 360 flash tool to patch the cpukey to the donor nand.
tried different combination...with/without original KV, smc, smc_config.
still got black screen without RROD.

Here is an odd thing when using 360 flash tool to patch cpukey to donor nand.
after patching, there are always some redundant data on the 1st page of block 0x6C of patched nand.
but the page of patched nand shows empty data (last 16bytes on the page are 0xFF)
donor nand is real empty(all pages in the block 0x6C are 0xFF)

Maybe it's just a bug of 360 Flash Tool.
What tool do you suggest to patch cpukey ?

I can capture the booting result...show it for you if it's better to clarify...