What's where things go wrong.  I can get the DHCP boot to work every time I power up with the reset button pressed with tinyPXE but if I try updating password/node name and hitting save causing reboot I get nothing but DHCP requests and no boot, even after waiting 16 minutes.  

If I skip setting the node name/password and go directly to the administration page and attempting to load the sysupgrade bin file I get the wait 3 minutes screen and back to the same thing.  Nothing but DHCP traffic, never comes back with network active light on device, no pings on 192.168.1.1 or the address it had on basic setup screen even if I set PC to IP in the devices LAN assignment.   I don't get much progress with turning my DHCP back on and trying to give the device an IP either.  

I've tried the .08 release, the currrent stable release, and the nightly release (each with their own bootloader .elf file booting just fine).   I've tried using winscp and putty to manually load/install sysupgrade file.   Nothing is working.   The device is plugged into a dumb switch along with the PC.

Looking the sysupgrade script  I see if the device is a specific model a standard rb model  that I have two of and have done this process twice with those units just fine, it unmounts the flash fs and formats it and then remounts the flash so I ran those commands by hand and got permissions errors (no SUDO as was root login).

So you see, I believe it's an issue with the SXT and the sysupgrade file or the script in the ram boot loader for it. I've tried to uncheck the keep settings box, nothing works.  I've got probably 20+ hours in trying to get that "part 2" to work.  I've done two other MikroTik boards but this SXT.. 5HP device is kicking my butt.

I can use the netinstall app to reload the routerOS flash and it works fine so I don't believe it's a HW problem but I'm out of ideas to even try.  No debugging informaiton on what is happening I'm not even sure how to provide more info than I have.