Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2025-05-30

01:00
01:45:02***No seen item changed, no save performed.
02:00
02:58:49 Quit othello7 (Ping timeout: 244 seconds)
03:00
03:45:03***Saving seen data "./dancer.seen"
04:00
04:57:01 Join PSparky|Ryzen7 [0] (~S|h|a|w|n@user/shawn/x-4432647)
05:00
05:00:36 Quit PheralSparky (Ping timeout: 276 seconds)
05:27:27 Quit PSparky|Ryzen7 (Read error: Connection reset by peer)
05:45:06***Saving seen data "./dancer.seen"
06:00
06:24:24 Join Burak_ [0] (~Burak@185.25.123.34)
06:28:02 Quit sebagala (Ping timeout: 272 seconds)
07:00
07:06:19 Quit eden (Read error: Connection reset by peer)
07:06:54 Join thanosengine [0] (~eden@user/thanosengine)
07:19:26 Quit thanosengine (Quit: WeeChat 4.6.1)
07:25:57 Join thanosengine [0] (~eden@user/thanosengine)
07:45:10***Saving seen data "./dancer.seen"
09:00
09:33:37 Quit thanosengine (Ping timeout: 265 seconds)
09:33:37 Quit eden_ (Ping timeout: 252 seconds)
09:35:21 Join thanosengine [0] (~eden@user/thanosengine)
09:35:45 Join thanosen1 [0] (~eden@user/thanosengine)
09:45:11***Saving seen data "./dancer.seen"
11:00
11:45:13***No seen item changed, no save performed.
12:00
12:07:22 Join othello7 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
12:11:24 Join ihatesansaclips1 [0] (~ihatesans@151.237.140.213)
12:13:52ihatesansaclips1Hey guys, anybody on? I have an issue with my Sansa Clip Zip. Basically, I'm trying to get into the bootloader because the internal memory is so messed up I can't even access it because, well, it won't boot because the internal memory is messed up, but I know the Rockbox bootloader offers a USB mode, where you can just have the device act as a USB
12:13:53ihatesansaclips1device in the system where it is plugged into. I shorted those pins that are needed to be shorted to get into the NAND and flashed a patched .bin file that I myself made with the 1.01.18 firmware version, but shockingly, for some reason, when I boot back into the player the bootloader doesn't even show and it continues on it's natural course using
12:13:53ihatesansaclips1the system supplied one. It is strange, because the dd command is definitely confirming I am writing that new firmware file on it, and yes, I've double checked, it's the patched one. Really need some help, these clips are in amazing condition, only thing lacking is their brains.
12:14:39ihatesansaclips1Update: The patched.bin file, is the same size as the OF file. Is that supposed to be like that? Does it just fill in empty space?
12:40:12sporkwhat would you expect the bootloader to 'show' ?
12:42:03sporkif your process worked, it should at least say it failed to load rockbox
13:00
13:02:42 Quit zem (Quit: and it's always been the same / it's just a complicated game)
13:08:04ihatesansaclips1I know that, and I do expect THAT, but even after zero-ing out the entire NAND partition and reflashing the patched bin file, it still just acts as the old firmware would act!
13:08:20ihatesansaclips1I'm so confused, because logically, that shouldn't be possible, unless I am royally missing something here.
13:08:52ihatesansaclips1My goal is to get the bootloader and fix the devices, but alas, bootloader no want boot.
13:08:53speachymight not be allowing writes because it's hosed.
13:09:04ihatesansaclips1dd isn't showing any errors though.
13:09:56ihatesansaclips1And there's the Sansas custom firmware repair guide that s
13:10:18ihatesansaclips1Oops. Misclick. Specifically talks about reflashing the NAND. As well as Bilgus' post about the Clip+ and Clip Zip.
13:10:37 Join hactar|ant [0] (~zem@97.115.94.147)
13:11:52ihatesansaclips1And device boots. Should not boot if hosed.
13:12:08ihatesansaclips1Unless I'm misunderstanding the word.
13:17:23ihatesansaclips1I have two clips. Both clips for some reason do not change behavior after reflashing. Lost cause? Hopeless? Prehaps new tie clips?
13:27:02 Quit ihatesansaclips1 (Quit: Client closed)
13:27:19 Join ihatesansaclips1 [0] (~ihatesans@151.237.140.213)
13:27:27ihatesansaclips1Still here, got disconnected.
13:29:42ihatesansaclips1Really, looking for any way to get access to the internal memory of the device, but heck, the Clip Zips are not known for giving up easily once they decide they're done existing, just hoping there's hope.
13:43:55ihatesansaclips1Okay yall, it's time for me to disconnect, but I'll be thinking about this subject. Really hoping to find a way to revive my clips.
13:44:00 Quit ihatesansaclips1 (Quit: Client closed)
13:45:15***Saving seen data "./dancer.seen"
13:49:48_bilgusihatesansaclips1 dd will not show errors to check if a transfer works do a crc over the dump before and after, bad flash will not persist writes past a reboot if even that long so might be what you are seeing
13:51:32_bilgusyou might be able to mount the drive and find the proper offset of the second boot area it may be writable and you can place a copy of the image starting there and it may work I have a log on the forum of doing this with a clip+
14:00
14:07:54 Quit othello7 (Ping timeout: 245 seconds)
14:08:52 Quit SammysHP (Quit: *wuff*)
14:09:29 Join SammysHP [0] (~SammysHP@faol.sammyshp.de)
15:00
15:29:32 Quit Tonux (Ping timeout: 272 seconds)
15:45:19***Saving seen data "./dancer.seen"
16:00
16:26:59 Join Tonux [0] (~Tonux@193.32.127.249)
16:52:54 Join akaWolf [0] (~akaWolf@akawolf.org)
17:00
17:16:04 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net)
17:23:54 Join jacobk [0] (~quassel@47-186-65-73.dlls.tx.frontiernet.net)
17:45:20***No seen item changed, no save performed.
19:00
19:09:52 Join massiveH [0] (~massiveH@108.50.181.86)
19:28:30 Quit speachy (Quit: WeeChat 4.6.2)
19:45:24***Saving seen data "./dancer.seen"
21:00
21:10:52 Join othello7 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
21:15:24 Quit baltazar (Ping timeout: 245 seconds)
21:17:31 Join baltazar [0] (~baltazar@user/baltazar)
21:45:26***Saving seen data "./dancer.seen"
22:00
22:26:45 Quit Moriar (Quit: Leaving.)
23:00
23:45:30***Saving seen data "./dancer.seen"

Previous day | Next day