Sansapatcher doesn't recognize e250

[jetonia]

I had Rockbox installed before (the old way). Then i followed instructions form anythingbutipod and reinstalled the Original Firmware.

I'm trying to install Rockbox via Sansapatcher now. I've read and reread the guide that's on rockbox.org, but when i start sansapatcher it says:
ERR No e200s found, aborting
ERR Please connect your Sansa and ensure it's in UMS mode (which is MSC i believe, and i have it in MSC mode, since it's recognized by windows)
ERR Please refer to ... rockbox manual.

Any ideas why is this happening?

I also have put the .rockbox folder on the root of my Sansa.

[jetonia]

I'm posting this for reference if others have the same problem.

Testdasi from anythingbutipod.com found a solution to this, which is:

Format your Sansa (which has the label "Sansa e250") and in the format options select File System: FAT32.

It seems that after i reinstalled the original firmware, it reverted the filesystem to FAT, which isn't recognized by sansapatcher.

[linuxstb]

I'm posting this for reference if others have the same problem.

Testdasi from anythingbutipod.com found a solution to this, which is:

Format your Sansa (which has the label "Sansa e250") and in the format options select File System: FAT32.

It seems that after i reinstalled the original firmware, it reverted the filesystem to FAT, which isn't recognized by sansapatcher.

If sansapatcher doesn't recognise a valid Sansa, then it's a bug in sansapatcher - the solution is to fix sansapatcher, not change your Sansa....  

Please post details (e.g. the partition table that isn't recognised) to the bug tracker and it can be fixed.

[d3nn1as]

It works very well to format the drive, if it's FAT it wont find it, strange enough.

[coarse.sand]

Since I started out having more or less the same problem, it's worth just continuing this thread. I'll probably make a bug report tomorrow of the issue.

I had the same problem as those above where the Sansa wasn't being detected by the ./sansapatcher command, and it also happened to be in standard FAT. I've switched the filing system to FAT32 now and it hasn't resolved anything. When inputed as "sudo ./sansapatcher", this is what appeared:


sansapatcher v0.2 with r12896 bootloader - (C) Dave Chapman 2006-2007
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[INFO] Scanning disk devices...
[ERR]  No E200s found, aborting
[ERR]  Please connect your sansa and ensure it is in UMS mode
[ERR]  Please refer to the Rockbox manual if you continue to have problems.


The Sansa is in MSC mode, is connected by USB and can be found as "drive" on my desktop area, but cannot be detected by sansapatcher. It's possible that a reboot might fix this. If it does, I'll mention it tomorrow but this seems bug report worthy.

Also worth noting, before I forget, is that I'm using the amd64 version of sansapatcher.

[cpchan]

I had the same problem as those above where the Sansa wasn't being detected by the ./sansapatcher command, and it also happened to be in standard FAT. I've switched the filing system to FAT32 now and it hasn't resolved anything. When inputed as "sudo ./sansapatcher", this is what appeared:

coarse.sand, I see what you are trying to do now. The problem is that your system is set to auto-mount. You must unmount /dev/sda1 first and then run sansapatcher. If you still have problems, post the output of the command:

lsusb

Charles

[linuxstb]

If you type "fdisk -l" (the letter "ell") you should see the partition tables of all attached disks displayed.  Can you copy and paste the partition table of your Sansa into a messsage here so I can see what Sansapatcher should be looking for?

[cpchan]

If you type "fdisk -l" (the letter "ell") you should see the partition tables of all attached disks displayed.  Can you copy and paste the partition table of your Sansa into a messsage here so I can see what Sansapatcher should be looking for?

His Sansa is attached to /dev/sda. I know this because I taught the OP how to make a vfat filesystem on /dev/sda1. So Linux is seeing the device. However, sansapatcher needs raw access to the device so he should unmount first.

Charles
 

[coarse.sand]

Output from fdisk -l

62 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 3844 * 512 = 1968128 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        1011     1942270+   6  FAT16
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 8, 12) logical=(0, 8, 20)
Partition 1 has different physical/logical endings:
     phys=(241, 212, 35) logical=(1010, 42, 12)
Partition 1 does not end on cylinder boundary.
/dev/sda2            1011        1022       20480   84  OS/2 hidden C: drive
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(241, 212, 36) logical=(1010, 42, 13)
Partition 2 has different physical/logical endings:
     phys=(244, 97, 45) logical=(1021, 20, 52)
Partition 2 does not end on cylinder boundary.


Ouput from lsusb

Bus 003 Device 015: ID 0781:7421 SanDisk Corp.
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 001: ID 0000:0000  


Under the Ubuntu properties GUI, the Sansa is claiming that it's using the vfat FAT32 filing system, yet the output above from fdisk indicates that it's still in FAT16. Also, unmounting hasn't fixed the issue yet, probably because for whatever reason it's still in FAT16.

[cpchan]

Under the Ubuntu properties GUI, the Sansa is claiming that it's using the vfat FAT32 filing system, yet the output above from fdisk indicates that it's still in FAT16.

OK, remake the filesystem by using the command:

mkfs.vfat -F 32 /dev/sda1

while the filesystem is umounted. I forgot to include the "-F 32" last time.

Charles

[coarse.sand]

Results after the following commands:

umount /dev/sda1
mkfs.vfat -F 32 /dev/sda1

Disconnect for Sansa system restart.

fdisk -l result:

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        1011     1942270+   6  FAT16
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 8, 12) logical=(0, 8, 20)
Partition 1 has different physical/logical endings:
     phys=(241, 212, 35) logical=(1010, 42, 12)
Partition 1 does not end on cylinder boundary.
/dev/sda2            1011        1022       20480   84  OS/2 hidden C: drive
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(241, 212, 36) logical=(1010, 42, 13)
Partition 2 has different physical/logical endings:
     phys=(244, 97, 45) logical=(1021, 20, 52)
Partition 2 does not end on cylinder boundary.


This thing really doesn't want to play nice, and sansapatcher still isn't detecting it.

[cpchan]

Results after the following commands:

/dev/sda1               1        1011     1942270+   6  FAT16

OK you need to run fdisk to change the partition type to "b" (FAT32) before running mkfs.vfat.

The commands are:

fdisk /dev/sda
t                            (change partition type)
1                           (Select partition 1)
b                           (Set to Fat32)
p                           (this step is just to be safe. It prints out the partition table for you to see)
w                           (Write the table)

Now run the mkfs.vfat command as before.

Charles

[coarse.sand]

Okay, here we go. It lives!  

Everything seems to be more or less fine now, Rockbox has installed nicely.

[dwarf0921]

I am having the same problem as coarse.sand but i don't know how to unmount my Sansa. Can someone post step by step instructions on how to this.

[alinasept]

I had the same problem as those above where the Sansa wasn't being detected by the ./sansapatcher command, and it also happened to be in standard FAT. I've switched the filing system to FAT32 now and it hasn't resolved anything. When inputed as "sudo ./sansapatcher", this is what appeared:

coarse.sand, I see what you are trying to do now. The problem is that your system is set to auto-mount. You must unmount /dev/sda1 first and then run sansapatcher. If you still have problems, post the output of the command:

lsusb

Charles

how do you unmount? when i type that into command prompt it says its not recognized