Print

[FuzzyQ]

UPDATE: I locked the original HD again and luckily, it worked again. So at least that thing isn't fried. Nice to know I have a backup.
The SDD still works in my PC without flaw, but I haven't got it to work with my xbox.

When locking/unlocking the HDs I get infos about an HDD-Key and HDD-Key from eeprom.bin.
I noticed that both HDD keys are exactly the same but the keys from eeprom are different. My original xbox-HDD-Key from eeprom begins with e7a while the SDD-HDD-Key from eeprom commerces with eda.
Is that alright or could the difference between those keys be the reason why the SDD isn't recognized?

I only have two other ideas. Actually, I have an old version of unleashx via font hack installed on my system's C drive, which is linked with xbmc on E: drive (meaning that xbmc is launched automatically). Maybe the failure is found here. I will burn another boot cd with the slayer's files and try to establish a whole new softmodded system. If that worked I could still install xbmc as dashboard anytime afterwards.

If that won't do I can only assume that *something* happens to the SDD when xbox reboots. Don't know what exactly that should be, neither how it's done and least of all, what I'm supposed to do against it, but perhaps xbox caches some files, brands the HD as flawed or something alike so that the SDD is recognized the first time xbox boots after installment but never again afterwards.

I'm very far from being an expert, so I'm in desperate need of professional help here.
Despite from wanting the benefits of a small, noiceless HD that's always cold to the touch I developed a certain curiosity about if it could be done at all. I assume that some of you might be interested in the outcome as well, so please help me.

Best regards.

[FuzzyQ]

It's a Transcend TS32GSSD25-M (for further details: http://www.transcend...e...1&Func2No=). It states to have it's own IDE interface, so I don't think it uses a converter. Since it is such a small device it needs an IDE adapter, though (the IDE cable is bigger than the SSD itself).

I still don't know why it once functioned and now doesn't - fact is, I have to give up. Don't ask me how or why, but the damn thing is broken. The PC doesn't recognize it any more, no matter which IDE port I plug it in, how I set the jumper or what way I configure my bios. Although I strictly followed every security measure it seems as if all the plug in-remove-repeat-procedure killed it at last. The IDE adapter didn't make a very 'solid' impression anyway.
I already phoned the man I bought it from and will return it.

Just to make sure I did everything right, I tested the whole procedure on an ancient 20gb Seagate IDE HDD. It worked out as well as it possibly could. For the time being that dinosaur will have to do.

I still have the feeling I missed something important and that I've been only one step away from success. The fact that my xbox accepted the SDD and booted my dashboard a single time still gets me.
What the hell happened after that? Perhaps I'll never know.

Some interesting facts I gathered, though:
1) this special SDD is lockable
2) it's so small you could remove the xbox hdd cage and this way make room for something else, whatever that may be
3) it doesn't produce any noice at all - sounds great, but you never know if it's doing something or not
4) it's always cold to the touch, so since heating from the HDD isn't a problem any longer you may perhaps replace the original cooler fan - which is in my opinion as loud as a boing 747 - with something less powerful
5) although SDDs suprise with lighting fast reading and writing speed on common PCs, the speed increase on the xbox wasn't that overwhelming
6) it's capacity is too small for the price you have to pay - i know, this technology is still fresh and will become cheaper soon, but I paid 85€ for 32gb; just imagine what size an IDE drive for the same price would have

All in all, it wasn't worth the efford (for me). But perhaps someone will pick up the idea and succeeds where I failed.

Thanks again for the help and good modding!

Best regards.

[ldotsfan]

1. Do you have eeprom backup?
2. Have you tried to boot a disc? Eg Frosty's xbox rescue disc.
3. Pinned topics. Step by Step softmodding.

[ldotsfan]

QUOTE(doeman @ Feb 6 2010, 08:47 AM)

I found the XBOXHMD boot disc i created back in 2007 with i modded this thing, that i believe should contain the eeprom in there right?

Can I use this same disc to re-do /Repair the Hard Drive?

What's Frosty's Rescue disc....what does it do?

thanks ldotsfan.

1. Frosty's: http://forums.xbox-s...howtopic=603853
2. For hotswapping, the disc won't contain eeprom.bin. For hdd upgrade, yes the disc will contain eeprom.bin.

[steveo1978]

Try xbins for slayers

[thexk]

Thanks to the lovely guides in this forum I succesfully softmodded My XBox and formatted
a bigger(80 GB) drive.Thank you guys!

1 noobish question only: My new hard drive boots to M$ Dash.How do I change that to say
boot in UnleashX or XBMC? Ive used Xboxhdm for Dummies guide to build my new HD.

[Heimdall]

Sounds like you probably copied the shadow C instead of the real C. You have three options:

1. Reinstall your original disk. Bypass shadow C (how you do that depends on which softmod you used), take a backup of the real C, redo the xboxhdm iso and rebuild the 80G disk.
2. Build a new, clean softmod with Kingroach NDURE 3.1 and a clean stock C dash. Use them plus the eeprom from your Xbox and xboxhdm to rebuild your 80G disk.
3. Use a gamesave to softmod your 80G disk.

[Heimdall]

You'll notice that using the C from Slayers on its own wasn't one of the options I listed, and there's a reason for that - if you just used the C from Slayers then you've got what you set out to build - a vanilla, unmodded large disk.

If you want it to be softmodded like your original disk then you need the real C contents from your original disk - my option 1 (note, real C, not shadow C), or you have to build a new softmod file set using Kingroach NDURE 3.1 plus the clean C from Slayers - my option 2.

[ldotsfan]

Try master password:

CODE

58424F585343454E4500

instead. That's XBOXSCENE in hex, suffix with a zero to make up for even no of characters.
Alternatively boot to option 4 and use ATAPWD, which accepts ASCII password.

After which, check eeprom.bin with LiveInfo in Windows. I think you grabbed the virtual eeprom and hence the error 6. Use E:\ndts\default.xbe to disable virtual eeprom and then grab eeprom backup with EvoX/ConfigMagic or xman954's eeprom reader built into ndts for Kingroach's 3.1.

For the record, TEAMASSEMBLY in hex:

CODE

5445414D414353454D424C59

I used these values in chimp2618.

[jmander11]

Okay so NO password is working for me lol...

I tried XboxScene and TeamExecuter in hex but I got "Error Invalid Character between a-f and 1-9 or something". I tried with the IDE cable plugged in and unplugged at boot about a dozen times...

I brought up the eeprom.bin in LiveInfo. What should I compare it to? How do I disable Virtual eeprom with UnleashX. (I got the eeprom from a softmod installer menu that loads with disc tray out at boot. I believe it's similar to EvolutionX...)

[Heimdall]

Your dash and your softmod are two completely different things. UnleashX is your dash, and has nothing to do with disabling virtual eeprom. How you disable virtual eeprom depends on your softmod, which in your case is SID. For SID the easiest way to bypass virtual eeprom is to cold boot with Frosty's Rescue disc, then use Xbox file manager to launch Config Magic, or xman954's eeprom dumper, or Evox, and take a clean backup of your real eeprom.

[Heimdall]

Unlock it with your current xboxhdm disc, option 3, unlockhd -a

That's how you locked it, so that's how you unlock it.

[ldotsfan]

Read my reply again, I gave you two methods to unlock. I verified the steps in VirtualBox to check the tool's syntax. Seems like you didn't follow my instructions for the hex password. It accepts only digits and the letters A-F.

[xman954]

QUOTE

the easiest way to bypass virtual eeprom is to cold boot with Frosty's Rescue disc, then use Xbox file manager to launch Config Magic, or xman954's eeprom dumper, or Evox, and take a clean backup of your real eeprom.

you can use the dumper as a APP it will read the real eeprom directly from the IIC bus .. (you will need to rename EEPROM.BIN to lower case to use in xbhdm)

[jmander11]

Do I put Xman954's eeprom dumper on the HD then load it from frost rescue disc?

By the sounds of it you mean as a normal APP launched from the dashboard?

I will remember that tidbit.