The "ltools" gamesave is the contents of your original hdd's E:\UDATA\4d530017 folder...the ltools dash (set up as the dual boot dash used when dvd tray is open) is in there. If your new hdd boots to EvoX fine, it shouldn't have a problem booting to the ltools menu as long as it can find the files. Try throwing in your old hard drive and see if it boots to the ltools menu with the tray open. If not, you don't have the gamesave files you need. You can get them in "the usual places". Once you have the UDATA files you are looking for, ftp them to the UDATA folder in E on your new hdd. Reboot with tray open. ltools menu should load.
I get the same Service error screen (21) after an hdd upgrade. Some info:
- version 1.1 box
- K:5838.01, D:5659.03
- Softmod: MA ltools 1.7.5 install, UDE2, PBL-Metoo, EvoX M8
- hdd upgrade to 160gb using
http://www.xbox-scene.com/articles/no-modchip-hdd-swap.php (I know, there's probably a better version, I just haven't had time to look around)
- new hdd = Seagate ST3160023A ATA/100
- have full original backups of C and E
- have full modded backups of C and E
- am 100% certain correct hdd lock password was used
- original drive still boots Evox fine
- have tried CS and MSTR jumper settings on new hdd
- have tried diff IDE cable from diff Xbox
- do not have modchip to try (Xenium ICE arriving in 2 days for diff Xbox)
I can't figure out why this isn't working. I've done this on over a dozen Xbox's in the last month. This isn't the first v1.1 I've run into. All of the other's worked like a charm. This one did have a much higher dash version than the rest, but the UDE install breezed through on the original hdd so I don't think that's an issue. I had to go with UDE2 because of the kernel version but that shouldn't matter as I've used it many times. This is the exact same hdd I've used those times and it's never been a problem. Nothing went different at all compared to the other mods.
Some thoughts/possibilities (if you know an answer, please chime in

):
- fdisk new hdd and start completely over (or did hex editing the drive muck that up)?
- try a diff hdd (possible, but it takes a few days to get one)? I don't think the hdd is the issue though.
- try Norton Ghost to copy old hdd to new hdd and relock new hdd?
Anyone have any ideas? ThanQ.