Somewhat lost re-flashing my Jasper

[doveman]

The other day I used 360 Hackbox to build a 15574 image (had been on 14719 for some time but it had started acting up so I decided to re-flash it and thought I might as well update as well).

After flashing the 15574 image with NANDFlasher 360, the box wouldn't boot anymore (to the dash or Xell) so today I got my USB SPI flasher and eventually got it back to Xellous. It has a few bad blocks, so I have to do this:
nandpro usb: -w16 free60.bin 0
nandpro usb: -w512 block10.bin FF8

Anyway, once Xellous was working, I put my previous 14719 image on a USB stick as updflash.bin and installed that, which worked but now it only boots to NXE, not FSD2 so I can't run Flash 360 to update to 15574 and it has Xell Reloaded installed, which doesn't let me update using updflash.bin either. In fact, even if I put xenon.elf on the USB stick, it doesn't recognise it and when scanning the devices it refers to uda: rather than usb: I tried the stick in all three ports.

I've rebuilt 15574 with Xebuild GUI now but I don't think that's remapped the bad blocks, so whatever I use to flash the image needs to do that, which Flash 360 does but I don't think Xell Reloaded does so if I flash it with that it will just not boot again. I guess I'll have to use the USB SPI flasher to reflash Xellous but I'm not sure whether that remaps the bad blocks when flashing updflash.bin either.

As I said in my title, I'm somewhat lost! It's been a while since I've had to use the SPI flasher as Flash 360 has always worked fine before, which is why I suspect something was wrong with the build from 360 Hackbox, so I'd appreciate some advice to get me back up and running.

[doveman]

No worries. I got there in the end by reflashing Xellous via SPI and then installing 15574 as updflash.bin which either remapped it for me or Xebuild GUI must have and it's booting to FSD2 once again

[doveman]

It does seem to be booting without hanging now and it didn't crash again whilst playing Sleeping Dogs for hours, so I guess Dash Launch or Freeboot had got a bit corrupted somehow.

The first time I powered it up with the controller yesterday, it didn't boot and just illuminated all four red lights on the console though. I powered it down and then on with the console button which booted fine and then off and on with the controller and that was fine as well then. Even before upgrading, once every couple of months when powering on I would get two red lights but it would boot normally anyway and I think that was just a bug in Dash Launch/Freeboot which might have been fixed now.

Does it sound like I need to worry/do anything?

[utar]

You talk about both Flash 360 and NANDFlasher 360 in your OP.  I'm not sure if you are talking about Flash 360 (by Redline99)  or NANDFlasher 360 (by Tracy).

I found in the past that Flash 360 is flaky when it comes to bad block remapping and doesn't always work.  Although NANDFlasher 360 or flashing through Xell works fine.  So if you originally reflashed using Flash 360 this could have been your problem, otherwise of course 360 Hackbox could have produced a broken image.

Anyway back to your original question regarding the box not booting.  Is this a JTAG?  Personally I have seen unusual behaviour when the JTAG soldering is dodgy.  You may want to check this as if your nand image was wrong or corrupted I would expect it just not to boot, rather then boot occasionally.  Also if games are freezing you could have a hardware fault.

[doveman]

Yeah, sorry for the confusion. I originally flashed 15574 (built with 360 Hackbox) with NANDFlasher 360 after which it wouldn't boot. I normally use Flash 360 and have never had any problems with it before (although it's possible that whatever I was using then to build the image remapped the bad blocks, rather than Flash 360) but after it stopped working and I had to fix it with my USB SPI flasher, this time I flashed 15574 (built with Xebuild GUI) from Xellous. So it could have been a problem with NANDFlasher 360, 360 Hackbox or something wrong I did.

Yeah, it's a JTAG and it's been fine until fairly recently, so if the soldering is dodgy it's become so by itself recently. I don't think it's ever frozen during a game (only rebooted a couple of times and that only in the last week) but for maybe the last six months to a year it's occasionally booted fine but with two red lights stuck on, which gets fixed by a reboot. I can't recall exactly when this first happened as it's infrequent enough not to be a bother really. It's only very recently that on every boot it started taking a long time to complete booting and resyncing the controller whilst doing it but that seems to have been fixed by the latest flash. So the only remaining problem at the moment is that it (once) failed to boot with all four red lights on solid.

I was reading this thread about using transistors for the JTAG http://forums.xbox-scene.com/index.php?showtopic=719652&st=120 and thought that might be relevant although I haven't got my head round it yet. It's been a while since I did the JTAG so I can't recall exactly what I did but it would have been a standard mod following whatever guide was current at the time. I see some nand modding utils refer to AUD_CLAMP but I don't know what that is or if I should tick it or not (I'd generally say not if I don't know what it is but I might just have forgotten, as I say it's been a while!)

[utar]

When you are using the ring of light point for JTAG the LEDs do on occasion light up incorrectly upon boot.  It happens to my Japer JTAG and isn't anything to worry about.  Moving to the audio clamp point would solve this but it is entirely cosmetic. 

If its stopped freezing after the new flash I wouldn't worry about it. 

[doveman]

Yeah I read that before which is why I wasn't concerned about it and only reflashed it when it started taking too long to boot, etc. I'm not bothered by it enough to dismantle my Xbox and change the wiring.

I've never had the entire four LEDs light up and it not boot before though but hopefully it was a one-off after flashing and it won't happen again.