System Update Not Installing After Building Clean NAND with RGH

[danbudzenski]

Over the weekend I hooked up the stuff to read my NAND and do the RGH. The reason for this was a flag on my Jasper 512MB system. I followed the tut to read the nand, grab the cpu key and then build a new clean retail image. On monday I was able to hop online and play without and issue. However today I tried running the new dash update from both LIVE and UBS and its failed several times. Always results in this error: 3524-396B-1380-2446-C000-0182

Could the use of a donor CB cause i had 51 not 50 have cause some sort of major issue for system updates? Or could it be something else?

Also, I have the NAND qsb's still soldered on and the coolrunning is still wired with the exception of the 3.3 V power wire.

 

[piromaniac]

You went online withe a rgh console,?

 

[danbudzenski]

I desoldered the power to the coolrunner before going online.

My question is if the CB went from 6751 to 6750 because I have a jasper and need a donor to build a new image will I no longer be able to accept updates as this was not what the origional NAND had?

 

[charincol]

Always results in this error: 3524-396B-1380-2446-C000-0182

Putting this into a hexidecimal converter translates to 13604.

 

[danbudzenski]

Putting this into a hexidecimal converter translates to 13604.

hmm actually that is interesting. 3524 -> 13604 and 396B -> 14699 so thats current version and version trying to update to. But what do the rest of the strings mean

 

[morbidj]

Just to chime in I experienced the same results as you, with a 512mb bb jasper. I said screw it flashed the stock nand back and updated. This was a CB6750 box before and after the update. Odd enough the ap2.5 flag was not online when the flag occurred or after prior to update attempt. Xval still states ap2.5 flag

Sent from my 3VO using dual cores and 3D's

 

[piromaniac]

I desoldered the power to the coolrunner before going online.

My question is if the CB went from 6751 to 6750 because I have a jasper and need a donor to build a new image will I no longer be able to accept updates as this was not what the origional NAND had?

my bad, i just took it for as i previously said.

 

[Martin C]

Over the weekend I hooked up the stuff to read my NAND and do the RGH. The reason for this was a flag on my Jasper 512MB system. I followed the tut to read the nand, grab the cpu key and then build a new clean retail image. On monday I was able to hop online and play without and issue. However today I tried running the new dash update from both LIVE and UBS and its failed several times. Always results in this error: 3524-396B-1380-2446-C000-0182

Could the use of a donor CB cause i had 51 not 50 have cause some sort of major issue for system updates? Or could it be something else?

Also, I have the NAND qsb's still soldered on and the coolrunning is still wired with the exception of the 3.3 V power wire.

How did you build a clean NAND?

 

[danbudzenski]

How did you build a clean NAND?

To build the NAND I used 360 multi builder v0.4

 

[Martin C]

do you have the log file still in multi_builder?

 

[danbudzenski]

do you have the log file still in multi_builder?

yes, ill attach it.

 

[Martin C]

ini: label [jasperbl] found
found (1) 'cb_6750.bin' crc: 0xf7afa8cc
found (2) 'cb_bnone.bin' crc: 0x00000000
found (3) 'cd_8453.bin' crc: 0x25e0acd0
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_13604.bin' crc: 0x639a4cd7
found (6) 'cg_13604.bin' crc: 0x7e9f5364

It's seeing 6750 in your nand dump which is correct.

Is anything else different about this console?

Have you tried flashing the nanddump.bin back (so it's flagged again) and updating?

 

[danbudzenski]

ini: label [jasperbl] found
found (1) 'cb_6750.bin' crc: 0xf7afa8cc
found (2) 'cb_bnone.bin' crc: 0x00000000
found (3) 'cd_8453.bin' crc: 0x25e0acd0
found (4) 'ce_1888.bin' crc: 0xff9b60df
found (5) 'cf_13604.bin' crc: 0x639a4cd7
found (6) 'cg_13604.bin' crc: 0x7e9f5364

It's seeing 6750 in your nand dump which is correct.

Is anything else different about this console?

Have you tried flashing the nanddump.bin back (so it's flagged again) and updating?

There shouldnt be anything else different about this console, other than cool-runner is still wired up with the exception of the 3.3 V power wire. Which I would think completely disables the chip. Also, have some extra fans but they pull right off the dvd drive power so wouldnt think thats an issue.

I hadnt tried flashing the original back yet, ill give that a go. The question then would be, flashing my original NAND will return the flag, then if it updates wont I be stuck with a 14699 flagged system, so unable to use on live, atleast until multi builder gets updated to the new dash. The reason I was attempting this was to return this as my LIVE system, with using original discs only.

Also, thanks for taking the time to look through the log and help me figure this out.

 

[Martin C]

I'm just trying to figure out where the error is coming from. I have no unflagged consoles here I can try online unfortunately.

If it does update successfully with your older NAND, re-dump and build another 13604 from the new image. You should be able to go back.

 

[danbudzenski]

Ok, that makes sense. All the dashboard information and version is on the NAND i write, so even if it has a newer version on when I dump it I should be able to build the older version and write back, and worst case ill still have a dump of the NAND with 14699 installed, if the update goes through.

The only thing that I think might be causing problems is that when I did the first dump of the system it had the 6751 CB, as it is a 512 Jasper. Then when I built the image to get my CPU keys its had to use the donor 6750 CB. Then I ran it again once i had cpu keys following what you had in your unflag tut and told it build retail. So when I look at the log for the retail_image that I wrote back its saying CB 6750. Could this be the issue, just mismatched CB?

Edit: Actually was just looking in multi_builder v0.3 and v0.4 and inside the 13604 folder there isnt even a file for cb 6751

 

[Martin C]

ok - you might be onto something here.

The jasperbl filelist doesn't cover cb_6751.bin. This is one for rogero as I don't know where the 8 char value is coming from.

 

[danbudzenski]

ok - you might be onto something here.

The jasperbl filelist doesn't cover cb_6751.bin. This is one for rogero as I don't know where the 8 char value is coming from.

Ok, thanks for the time. Any idea how I could get a hold of rogero and see what he has to say about 6751?

 

[Martin C]

Post in the official multi_builder thread and/or PM him. He may have a valid answer for cb6751 not being included.

 

[Martin C]

ok - Multi_builder 0.5 is now out and has full support for CB 6751

Give it a shot.

 

[danbudzenski]

ok - Multi_builder 0.5 is now out and has full support for CB 6751

Give it a shot.

I actually just read a post on that before checking this. I had sent a PM to Rogero the other day and he had sent me back what I needed to add CB6751 support to v0.4 and build an image. But I hadnt had time to check it out yet. Hopefully him sending me that and then adding it to 0.5 means there is some success. Im about to take my case apart and write the new nand, ill update the progress of a test with the v0.4 image from this morning and an image using v0.5 that was just posted.