Bricked E200R - Rhapsody not e200

[cheesecake]

Hello! I need some help with my e200R. Yes, that is R as in Rhapsody.
Anyway, i tried all the debricking steps, only to realize that i was running everything onto an e200 - Non R. I looked elsewhere for information, but couldn't really find anything specific for Rhapsody. Here's what I know:

I can't get Linux to recognize it in manufacturer mode.
I can't get my e200R into recover mode.
I can get windows to recognize it, but all i get is a driver prompt, and i can't figure out where it is under device manager.

I am happy to provide more info, i have a kubuntu live cd to run, so any help you guys can give me would be super greatly appreciated!!!

[Llorean]

What do you mean by "recognize it" in linux, exactly? What are you doing to test whether it's "recognized"?

[cheesecake]

By recognize in linux, i am trying to mount it.
When previously attaching the recovery partition, linux would give me a prompt saying that a device had been attached.
When i ran lsusb, all i found was:
Bus 001 Device 001: ID 0000:0000 
which was found even when i removed the cable.
When i plugged it in to windows, i would get a driver popup.
Does this explain it?

[Llorean]

In manufacturer mode it cannot be mounted. There's no partition to mount. It's not supposed to be mounted. Have you found directions that tell you to mount it?

What instructions are you trying to follow?

[cheesecake]

I am trying to get it connected to run the e200 recover tool on it. The directions i was trying to use to get it connected in manufacture are in the forum topic: Sansa e200 Bricked by Recovery.
I found instructions on ABi to get the normal settings installed from recovery mode to the e200R specifically.

[Llorean]

Try http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick
Since recovery mode is not working for you, follow the part about Manufacturing mode.

[cheesecake]

Stupid Question:
Does it matter on the e2XX part? I have an e270R and the one listed is e250R.

[Llorean]

No. The only difference between those is the amount of storage.

[cheesecake]

Thank you! I'll try this tomorrow when i get some time, and let you know!!
Also:
do i need to rename the .btl to .rom?
Every other time i have seen it, it has been BL_SD_boardSupportSD.rom

[Llorean]

It shouldn't matter, as far as I know.

[cheesecake]

Final question: When i enter "e200tool recover" do i need to change BL_SD_boardSupportSD.rom to BL_SD_boardSupport.btl?

[Llorean]

You need to type in the name of the file, so yes, if you don't rename it, it's BL_SD_boardSupport.btl

[cheesecake]

Also, i installed the wrong i2c rom, which crashed me into manufac. mode. Do i need to fix this when i get to recovery?

EDIT: I got e200tool to recognize it, but heres what it gave me:

root@ubuntu:/home/ubuntu/Documents# ./e200tool recover BL_SD_boardSupportSD.btl
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.btl' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x1065f958
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

and nothing happened on my Sansa...
for the record, the hold switch was on and i was holding only the record button.
Any advice/help? Please?

Edit 2: okay, so i reinstalled the i2c rom for the e200R and got it to 0781:0720
However, lsusb says:
SanDisk Corp. Sansa C200 series in recoverymode
is this a problem?

Edit 3:
Tried to run ./e200tool recover BL_SD_boardSupportSD.btl, but my console seemed to freeze trying to write:
Initializing USB stub (4780 bytes) ...
When this was previously done, it took no time at all.
I am holding the record button.
Do I just need to try and wait it out?
Hopefully final Edit:
I got it into recovery mode after i rebooted the install cd. Now what do i need to copy to the 16 mb partition, because i tried what was on the wiki page, but it didn't work.
Please somebody help, i'm so close!!!!

Edit 4:
So i've tried copying the i2c rom, bootloader, mi4, and sansa.fmt over, and this is what happens:
Formatting
System update complete
Restart

And i'm back in manufac. mode. Any ideas?
Can i use e200tool to write the bootloader?
Somebody please respond!!!
Note: the system update actually doesn't take any time. I'm assuming from this that it means that the update isn't actually happening.

[bascule]

AFAIK (and I've just had to go through this procedure due to my own stupidity ) you need to use the file BL_SD_boardSupportSD.rom, NOT BL_SD_boardSupportSD.btl

I found it quite tricky and had to do it a couple of times before it worked correctly, even though it seemed to work OK the first time.

As soon as I had entered the command, I started holding down the REC button and didn't let go until the Sansa screen indicated that it was in Recovery mode.

Once in recovery mode, don't do anything except copy the three files to the 16MB recovery partition (.rom, .mi4 and sansa.fmt) then safely disconnect from USB and the device should reboot, format and re-configure itself back to full health!

Hope it goes OK next time...