Thank You for your continued support and contributions!
**************************Welcome to Recovery Mode***************************USB Cable connectedEnter USB2.0 MSD modeLUN0 lockedLUN0 unlockedLUN0 lockedLUN0 unlockedLUN0 lockedLUN0 unlockedLUN0 lockedLUN0 unlockedLUN0 lockedLUN0 unlockedLUN0 locked
root@localhost RockBox for Sansa e260]# ./sansapatchersansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.[INFO] Scanning disk devices...[ERR] No E200s or C200s 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.Press ENTER to exit sansapatcher :[root@localhost RockBox for Sansa e260]#
[root@localhost RockBox for Sansa e260]# ./sansapatcher /media/disk/sansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.[ERR] ioctl() call to get sector size failed, defaulting to 512[INFO] Reading partition table from /media/disk/[INFO] Sector size is 512 bytes[INFO] Part Start Sector End Sector Size (MB) Type[INFO] 2 -1207970080 -1073456249 65680.6 Empty (0x00)[ERR] Disk is not an E200 or C200 (-1), aborting.[root@localhost RockBox for Sansa e260]#
[root@localhost RockBox for Sansa e260]# more /etc/mtab/dev/hda1 / ext3 rw,noatime 0 0none /proc proc rw 0 0none /dev/pts devpts rw,mode=0620 0 0none /proc/bus/usb usbfs rw 0 0/dev/hda3 /home ext3 rw,noatime 0 0none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0/dev/sdb /media/disk vfat rw,nosuid,nodev,noatime,uhelper=hal,flush,uid=0,utf8,shortname=lower 0 0[root@localhost RockBox for Sansa e260]#
[root@localhost RockBox for Sansa e260]# ./sansapatcher /dev/sdbsansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.[INFO] Reading partition table from /dev/sdb[INFO] Sector size is 512 bytes[INFO] Part Start Sector End Sector Size (MB) Type[INFO] 0 778135908 1919645538 557377.7 Unknown (0x72)[INFO] 1 168689522 2104717761 945326.3 Novell Netware 386 (0x65)[INFO] 2 1869881465 -489057640 945326.3 Unknown (0x79)[ERR] Disk is not an E200 or C200 (-1), aborting.
[root@localhost RockBox for Sansa e260]# ./sansapatcher --helpsansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.Usage: sansapatcher --scan or sansapatcher [device] [action]Where [action] is one of the following options: --install -l, --list -rf, --read-firmware filename.mi4 -a, --add-bootloader filename.mi4 -d, --delete-bootloader -of --update-original-firmware filename.mi4 -bl --update-ppbl filename.bin"device" is the device node (e.g. /dev/sda) assigned to your sansa.sansapatcher will refuse to access a disk unless it can identify it as beingan E200 or C200.[root@localhost RockBox for Sansa e260]#
[root@localhost RockBox for Sansa e260]# ./sansapatcher --listsansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.[INFO] Scanning disk devices...[ERR] No E200s or C200s 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.[root@localhost RockBox for Sansa e260]# ./sansapatcher --helpsansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.Usage: sansapatcher --scan or sansapatcher [device] [action]Where [action] is one of the following options: --install -l, --list -rf, --read-firmware filename.mi4 -a, --add-bootloader filename.mi4 -d, --delete-bootloader -of --update-original-firmware filename.mi4 -bl --update-ppbl filename.bin"device" is the device node (e.g. /dev/sda) assigned to your sansa.sansapatcher will refuse to access a disk unless it can identify it as beingan E200 or C200.[root@localhost RockBox for Sansa e260]# ./sansapatcher --scansansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.[INFO] Scanning disk devices...[ERR] No E200s or C200s found.[root@localhost RockBox for Sansa e260]#
[root@localhost RockBox for Sansa e260]# ls -la /media/disk/total 28drwxr-xr-x 3 root root 16384 Oct 9 21:11 ./drwxrwxr-x 4 root root 4096 Oct 9 21:09 ../drwxr-xr-x 14 root root 4096 Sep 23 17:25 .rockbox/-r-xr-xr-x 1 root root 512 Dec 31 1979 version.txt*[root@localhost RockBox for Sansa e260]# ls -la /media/disk/../ ../ .rockbox/[root@localhost RockBox for Sansa e260]# ls -la /media/disk/.rockbox/total 648drwxr-xr-x 14 root root 4096 Sep 23 17:25 ./drwxr-xr-x 3 root root 16384 Oct 9 21:11 ../drwxr-xr-x 2 root root 4096 Sep 23 17:25 backdrops/drwxr-xr-x 2 root root 4096 Sep 23 17:25 codecs/drwxr-xr-x 2 root root 4096 Sep 23 17:25 codepages/-rw-r--r-- 1 root root 0 Sep 23 17:25 database.ignoredrwxr-xr-x 2 root root 4096 Sep 23 17:25 docs/drwxr-xr-x 2 root root 4096 Sep 23 17:25 eqs/drwxr-xr-x 2 root root 4096 Sep 23 17:25 fonts/drwxr-xr-x 2 root root 4096 Sep 23 17:25 icons/drwxr-xr-x 2 root root 4096 Sep 23 17:25 langs/drwxr-xr-x 2 root root 4096 Sep 23 17:25 recpresets/-rw-r--r-- 1 root root 590 Sep 23 17:25 rockbox-info.txt-rw-r--r-- 1 root root 573440 Sep 23 17:25 rockbox.mi4drwxr-xr-x 6 root root 4096 Sep 23 17:25 rocks/-rw-r--r-- 1 root root 8878 Sep 23 17:25 tagnavi.configdrwxr-xr-x 2 root root 4096 Sep 23 17:25 themes/-rw-r--r-- 1 root root 835 Sep 23 17:25 viewers.configdrwxr-xr-x 6 root root 4096 Sep 23 17:25 wps/[root@localhost RockBox for Sansa e260]#[root@localhost RockBox for Sansa e260]#
In Linux, I can read the contents of the boot partition, I can write the Rockbox structure into it, but sansapatcher can't find the e260.I have started the e260 into recovery mode (lock switch @ hold, press record button and then power on).
(and fwiw, my wife had a Sansa e240r which she bought from BestBuy; she was totally offended by the Rhapsody poo, she got in touch with Sandisk tech support, the tech instructed her in how to remove the crapsody stuff. So, I wonder how that removal impacts RockBox....).
Quote from: mmmmna on October 09, 2008, 10:32:26 PMIn Linux, I can read the contents of the boot partition, I can write the Rockbox structure into it, but sansapatcher can't find the e260.I have started the e260 into recovery mode (lock switch @ hold, press record button and then power on).You need to do the install from MSC mode, not recovery mode. Did you do all of the below in recovery mode or MSC mode?
Installing the firmware 1. Download your chosen version of Rockbox from the links in the previous section. 2. Connect your player to the computer via USB as described in the manual that came with your player. 3. Take the .zip file that you downloaded and use the “Extract all†command of your unzip program to extract the files onto your player. Note: The entire contents of the .zip file should be extracted directly to the root of your player’s drive. Do not try to create a separate directory on your player for the Rockbox files! The .zip file already contains the internal structure that Rockbox needs. Note: If the contents of the .zip file are extracted correctly, you will have a directory called .rockbox, which contains all the files needed by Rockbox, in the main directory of your player’s drive. If you receive a “-1†error when you start Rockbox, you have not extracted the contents of the .zip file to the proper location.
Note: The entire contents of the .zip file should be extracted directly to the root of your player’s drive. Do not try to create a separate directory on your player for the Rockbox files! The .zip file already contains the internal structure that Rockbox needs. The proper location should already have several directories (folders) similar to the following:ALBUMSARTISTSVIDEOS...
Quote from: mmmmna on October 09, 2008, 10:32:26 PM(and fwiw, my wife had a Sansa e240r which she bought from BestBuy; she was totally offended by the Rhapsody poo, she got in touch with Sandisk tech support, the tech instructed her in how to remove the crapsody stuff. So, I wonder how that removal impacts RockBox....).I doubt they actually told you how to convert an R into a non-R (since its complicated and cannot be done using their software), so the install should be the same as any other R player.
Warning: The following steps require you to change the setting in Settings → USB Mode to MSC from within the original firmware. Never extract files to your player while it is in recovery mode.
I'm not sure what you mean by the boot partition. The Sansa e2x0 series presents as two partitions when connected via MSC. One refers to the main partition that Rockbox will be installed on, the other is actually the microSD slot (removable disk).
[root@localhost RockBox for Sansa e260]# ./sansapatchersansapatcher v0.6 with v4.0 bootloaders - (C) Dave Chapman 2006-2007This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.[INFO] Scanning disk devices...[INFO] e200 found - /dev/sdb[INFO] Reading partition table from /dev/sdb[INFO] Sector size is 512 bytes[INFO] Part Start Sector End Sector Size (MB) Type[INFO] 0 580 7813119 3814.7 W95 FAT32 (0x0b)[INFO] 1 7813120 7854079 20.0 OS/2 hidden C: drive (0x84)Enter i to install the Rockbox bootloader, u to uninstall or c to cancel and do nothing (i/u/c) :i[INFO] Bootloader installed successfully.Press ENTER to exit sansapatcher :[root@localhost RockBox for Sansa e260]#[root@localhost RockBox for Sansa e260]#
Version Info: Product Rev.: PP5022AF-05.51-S301-02.18-S301.02.18A-DBase Code: 05.51-S301-02.18-S301.02.18A-DODM Ver.: S301-02.18-S301.02.18A-DOEM Ver.: S301.02.18A-DBuild Type: -DBuild Date: 2006.11.03Build Number: (Build 32.10)
If you don't have a microSD (not microSDHC) card in your player then your distribution probably just ignores the card reader. You can just ignore that bit.Extracting as root shouldn't matter. You're just placing files on your DAP's drive.
It's strange that sansapatcher claims it installed the bootloader but there's no evidence of it when you boot your player.Is there a particular error when you try to run Rockbox Utility? That will probably be of interest to its maintainers.
[mmmmna@localhost RockBox for Sansa e260]$ ./rbutilqtFloating point exception[mmmmna@localhost RockBox for Sansa e260]$ su -Password:[root@localhost ~]# cd /home/mmmmna/Desktop/RockBox\ for\ Sansa\ e260/[root@localhost RockBox for Sansa e260]# ./rbutilqtFloating point exception (core dumped)[root@localhost RockBox for Sansa e260]#
[mmmmna@localhost ~]$ more /etc/mtab/dev/hda1 / ext3 rw,noatime 0 0none /proc proc rw 0 0none /dev/pts devpts rw,mode=0620 0 0none /proc/bus/usb usbfs rw 0 0/dev/hda3 /home ext3 rw,noatime 0 0none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0[mmmmna@localhost ~]$
[mmmmna@localhost ~]$ more /etc/fstab## fstab created by Livecd-installnone /proc proc defaults 0 0none /dev/pts devpts mode=0620 0 0none /proc/bus/usb usbfs defaults 0 0# /dev/hda1, size=23438772, type=131: Journalised FS: ext3 (primary)/dev/hda1 / ext3 noatime 1 1# /dev/hda2, size=5076540, type=130: Linux swap (primary)/dev/hda2 swap swap defaults 0 0# /dev/hda3, size=49624785, type=131: Journalised FS: ext3 (primary)/dev/hda3 /home ext3 noatime 1 2# cdrom: SONY CD-RW/DVD-ROM CRX830E# /dev/hdb /media/cdrom auto user,exec,ro,noauto 0 0[mmmmna@localhost ~]$
umount `cat /etc/mtab | grep -i sansa | awk '{print $1;}'`
my wife had a Sansa e240r which she bought from BestBuy
Page created in 0.067 seconds with 21 queries.