Problem patching E280R Bootloader

[alaron]

Hi,

I'm following all the steps as closely as I can, but it fails in Step 3

My problem is that after getting into Recovery mode at the end of Step 2, my Linux virtual machines (I've tried openSuse 10.2 and ubuntu 7.04) are not able to properly detect the USB device and create a block device in /dev for it. My harddrive is seen as /dev/sda so I'm expecting to see the usb driver as /dev/sdb.

Checked the system log and I see all there errors. Has somebody succesfully used a VMware Linux install to do the patching? Maybe the VMware's USB support is faulty...

Thanks

[Bagder]

The instructions clearly say that you cannot use a vmwared linux for this, as it snatches the USB a bit too much for this to work. Hence the recommendation to use a live cd...

[alaron]

Well...I didn't see that in the manual although after getting the same problem with 2 distros I started thinking that VMware's support might be at fault since they probably never tested that.

Thanks  , will try later today with a LiveCD or a Linux install on a real machine.

[alaron]

I tried again to do the E280R patching on a real system with openSUSE 10.2 and I'm getting a different error now

need4speed:~/sansa # ./e200tool recover BL_SD_boardSupportSD.rom
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 8 found!
Write at 0x1060eeb6
Control message (-71, Protocol error)

[alaron]

Writing back Rapsody firmware works fine...so it's not yet a brick, but I don't understand why e200tool doesn't properly work in my case.

Help would be appreciated.

[chrisjs169]

Try turning off the Sansa and trying it again.

[scorche]

As well, please use the modify button instead of posting 3 times in a row.  

[alaron]

gotcha