Oops... Some help unbricking my e250 please!

[macgeek417]

Oops. I forgot to rename my compiled RB bootloader from .bin to .rom...
Could I please have some help unbricking it?
It doesn't seem to want to enter manufacturer mode; It looks just like it does when in manufacturer mode, but doesn't appear like Vista is recognising it.

I had no problem fixing the broken BL a couple days ago, but am having a little trouble fixing the i2c ROM...
Maybe I could have more luck on my OS X machine, but libusb got a compile error. could someone provide a libusb precompiled build for OS X? I got compile errors, and the version I found on the 'net is the v0.1, and i think e200tool needs 1.x

If it isn't actually in manufacturer mode, are there some contacts i could short on the circut board to make it enter recovery mode or something?

[saratoga]

Oops. I forgot to rename my compiled RB bootloader from .bin to .rom...

Can you be more specific?  What were you doing and why did you need to rename it?

It doesn't seem to want to enter manufacturer mode; It looks just like it does when in manufacturer mode, but doesn't appear like Vista is recognising it.

I think thats normal.  manufacturer mode requires e200tool, and that doesn't work with Windows.  See this page for more info about that mode:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick

[macgeek417]

...but i got e200tool to work on windows to reflash the bootloader, following instructions on an old revision in the RB twiki. I think it was the old e200r install page.

Oh, and since I have a corrupted i2c ROM, its in pre-boot mode, right?

[soap]

Oh, and since I have a corrupted i2c ROM, its in pre-boot mode, right?

We read today from the holy wiki, chapter SansaE200Unbrick, verse Pre-boot Mode:

If the Sansa is booted and discovers a corrupted i2c rom or if there is no working bootloader at all, it will enter manufacturing mode automatically. During this mode, the Sansa appears as a "PortalPlayer USB Device."

Said bolded words of scripture appear to be the way to diagnose if you are in pre-boot mode.

Not saying you don't have a corrupted i2c ROM, but why do you believe you do?

Please read the whole page (quote is a link), and pay particular note to what I bolded.  Even if you are in pre-boot mode it does not necessarily mean you have a corrupted i2c ROM.

...but i got e200tool to work on windows to reflash the bootloader, following instructions on an old revision in the RB twiki. I think it was the old e200r install page.

"e200tool" for Windows on http://www.rockbox.org/twiki/bin/view/Main/SansaE200RInstallation ?
I don't think so.  Are you sure that is the name of the tool you used?  Are you sure that is the page you're talking about?  You're in this position due to failure to be precise in your actions.  Let's be precise in our words.

 

[macgeek417]

Because I copied a .bin file to the recovery mode partition. I forgot to rename it BL_SD_boardSupportSD.rom, and instead copied it as bootloader.bin

.bin files get written to the i2c rom.

PS: why was this moved to instalation/removal? I just want to fix the i2c rom, RB is allready installed, and i want to keep it that way, as putting RB on it was the purpose I had for it when I got it; the OF is a disaster.

PPS: Oh, and the computer doesn't recognise it as anything apon plugging it in.

oh, and i needed to rename it because I was building my own bootloader.

[soap]

PS: why was this moved to instalation/removal? I just want to fix the i2c rom, RB is allready installed, and i want to keep it that way, as putting RB on it was the purpose I had for it when I got it; the OF is a disaster.

Rockbox is not installed, you have (?) a .rockbox folder on your brick.
This is not a hardware issue, no physical hardware is needing repaired.  This is a software issue regarding bootloader installation.

[macgeek417]

My BL is fine, too. its my i2c ROM that's messed up.

EDIT:
OK, so my nice, new debian instalation is up.
When I run lsusb with sansa plugged in (turn off via holding power button, hold center key w/ hold switch on and plug in):
debian:/home/macgeek417# lsusb
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 05ac:0204 Apple, Inc.
Bus 001 Device 006: ID 05ac:0204 Apple, Inc. Extended Keyboard Hub [Mitsumi]
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I see no "PortalPlayer USB Device" there

EDIT:
Yaay! by getting mad at it and randomly shorting components, i now have a "Tango Digital Media Platform device!"

Now to e200tool...
...and i unplugged it and plugged it back in and it dowsn't work now...