--- Log for 18.10.119 Server: cherryh.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 26 days and 0 hours ago 00.07.55 Join J_Darnley [0] (~J_Darnley@d51a44418.access.telenet.be) 00.09.37 Quit jdarnley (Ping timeout: 264 seconds) 00.13.30 Join jdarnley [0] (~J_Darnley@d51a44418.access.telenet.be) 00.13.48 Quit J_Darnley (Ping timeout: 276 seconds) 00.27.40 Quit Huntereb (Remote host closed the connection) 00.30.44 Quit ZincAlloy (Quit: Leaving.) 00.41.40 Join Huntereb [0] (~Huntereb@d-69-161-102-241.va.cpe.atlanticbb.net) 00.46.08 Quit petur (Remote host closed the connection) 01.21.12 Quit lebellium (Ping timeout: 240 seconds) 01.25.51 Join lebellium [0] (~lebellium@89-92-69-72.hfc.dyn.abo.bbox.fr) 01.32.34 *** Saving seen data "./dancer.seen" 01.36.17 Quit rogeliodh (Quit: The Lounge - https://thelounge.chat) 01.37.09 Join rogeliodh [0] (~rogeliodh@135.ip-66-70-189.net) 02.28.44 Join MrZeus_ [0] (~MrZeus@88-145-73-231.host.pobb.as13285.net) 02.30.34 Quit MrZeus (Ping timeout: 240 seconds) 02.53.12 Quit jdarnley (Ping timeout: 240 seconds) 02.53.27 Quit MrZeus_ (Ping timeout: 265 seconds) 02.54.06 Join J_Darnley [0] (~J_Darnley@d51a44418.access.telenet.be) 03.20.20 Quit lebellium (Quit: Leaving) 03.32.36 *** Saving seen data "./dancer.seen" 04.30.55 Join Jason [0] (477eb166@pool-71-126-177-102.washdc.fios.verizon.net) 04.31.17 # Wow. A lot of people here. That's wonderful! 04.31.19 Nick Jason is now known as Guest1364 (477eb166@pool-71-126-177-102.washdc.fios.verizon.net) 04.33.16 # I have a bricked sansa clip zip. The wiki says if I boot when pressing left and then unplug the usb cable when the logo appears, I can skip the database check. I tried 10 times and really don't know what I'm supposed to do anyways. Can anyone explain this idea better? 04.33.53 Nick Guest1364 is now known as Jason666 (477eb166@pool-71-126-177-102.washdc.fios.verizon.net) 04.35.15 # The logo "appears" twice using of boot. 04.37.16 # Since there are no replies I will throw in a request for any ideas, including shorting the pins on the front of the mb, soldering stuff, etf. 04.37.17 # etc. 04.37.32 # I saw that there was some work by 04.38.45 # Bilgus here http://forums.rockbox.org/index.php?topic=52014.0 but I don't know if this is something that is usable post-brick. 04.40.07 # you have to do the recovery manually 04.43.05 # https://www.rockbox.org/irc/log-20190929#21:24:37 04.43.08 # I am happy to do it manually. 04.44.48 # I listed all the links to lol and went through most of the steps although it was unsuccessful, possibly was already dead or he shorted some pins while soldering 04.45.29 # you will need linux or a raspi 04.46.57 # By the way bilgus I want to thank you for your recent work with those images, even though I don't know what they are useful for. 04.47.23 # Now I am talking about a clip zip, but sizzlincok had a clip +. 04.47.37 # same steps for the clip zip 04.47.46 # you meant SIMILAR 04.47.58 # infact the tutorial link is a clip zip 04.48.11 # for one the pin locations are diffent. next the thing you move onto the 30mb drive is different, right? 04.48.41 # no pretty much the same just different binary and you short two pins 04.50.18 # I know you are pedantic JAT. But they are basically different revisions of the same underlying player 04.51.09 # if you can get into rockbox the process is much easier 04.51.34 # then you can expose the 'hidden' part of the drive without opening it up 04.51.54 # No once the fat is corrupt ppl use the of and it writes to it which makes it much more corrupt and then it is bricked. 04.53.56 # http://forums.rockbox.org/index.php/topic,52030.msg242031.html#msg242031 04.54.44 # the OF actually is very brittle to write errors I doubt it ever gets to writing to anything 04.55.03 # sorry read errors 04.56.05 # more likely the flash has already gone read-only by that point and that is pretty much endgame unless you already have the multiboot bootloader installed 04.57.48 # Well, at any rate, this wiki should be updated to include a picture of the jump points for the sansa zip: https://www.rockbox.org/wiki/SansaAMSUnbrick 04.58.22 # gah I keep meaning to do that I have a low res pic (SOMEWHERE) 04.58.56 # I haven't needed to take my clipzip back apart to get a better one and I won't be doing so until I have to 04.59.37 # I'll make one for you. 05.07.01 # But until then let's add this image to the other images http://forums.rockbox.org/index.php?action=dlattach;topic=51205.0;attach=7312;image of the 22:58:11 url wiki above. 05.08.45 # Do I need to disconnect the battery, or can I just do the 30-second power off? 05.10.54 # https://www.rockbox.org/wiki/SansaAMSUnbrick 05.10.57 # already done 05.11.29 # you don't need to disconnect the battery 05.12.20 # DO get a dump of the current contents of the drive once in recovery mode 05.13.06 # it'll let us check for bad sectors and give you something to compare to to see if the drive has gone read only 05.13.54 # ActiveDisk is an (OK) hex file/disk editor or you can just use the inbuilt linux ones on the file 05.14.35 # ActiveDisk lets you do it in a GUI but has some annoying quirks with said GUI 05.15.23 # when shorting the pins you start from power off plug the USB wait 3? seconds then unshort 05.15.46 # I just use a small jewlers flat head 05.16.01 # jewelers lol 05.24.43 # once you copy the recovery FW you should do another dump and compare the drive contents to the FW you copied if they don't match and the dump doesn't match the backup you first created then there is some bad sectors and [[if there is enough room]] you can zero out the beginning of the drive and move the fw past the bad spot, another possibility would be to make a special rb bootloader without the OF that would fit prior to the bad spot 05.25.13 # again assuming there is enough room 05.26.52 # the recovery images I have up media fire already include the multiboot bootloader I'd highly reccomend you start booting from the sdcard if you get it on there successfully 05.30.32 # recommend even too 05.32.39 *** No seen item changed, no save performed. 05.39.30 # It's interesting that you think the internal flash is going to fail soon. 05.39.53 # Anyway, can you edit "his only works on e200v2, Fuzev1, Fuzev2, Clipv1, Clipv2 and Clip+ (for now) !" to "his only works on e200v2, Fuzev1, Fuzev2, Clipv1, Clipv2, Clip+, and Zip (for now) ! 05.40.47 # SO do a "dd if=orig_image.bin of=/dev/sde "? 05.43.39 # assuming sde is your player yes but first dump the drive 05.44.52 # dd if=/dev/sde of=orig_image.bin bs=512 count=$((0xF000)) 05.46.25 # to put the image on the drive you don't need to specify sizes since the file is already the proper size 05.47.02 # I see the updated wiki. Nice work. 05.47.19 # So my zip is 4gb? Are they all the same size? 05.48.47 # no there are 8gb but its only important if you want to use windows since you have to write the whole drive 05.49.20 # on linux you can just write a chunk of it and the bootloaders are the same 05.49.59 # to put an image back do this dd of=/dev/sdb if="clipzip4GB_RECOVERY_image32.bin" bs=512 05.50.03 # 512XF000=4gb? 05.50.57 # bo bs specifies the byte size 05.51.00 # Really I want to recover my files off of it. They should be mp3 files. 05.51.59 # Thanks so much for your help so far bilbus! I need to hit the hay now though. 05.52.00 # and 0xF000 x 512bytes == ~32 mb 05.52.33 # if you wanted to dump 4gb it'd take a while 05.52.45 # Well dd is well documented linux command. I learn what I need and forget it until next time... 05.52.57 # but is possible assuming you have access to the drive 05.53.10 # I definitely want to recover what I can from the chip. 05.53.52 # It's fat32 so lots of tools, but how to get them to work in this situation I have no idea. 05.54.10 # best bet would probably be to get the fw fixed tbh but barring that you could dump the image to a drive and recover the files 05.55.16 # just do dd if=/dev/sde of=orig_image.bin and it'd dump till it errored out 05.56.01 # WEll, VERY few programs work with images. Most work with a live file system, usually in read only mode. 05.58.37 # anyways Ive a need for sleep as well just ask if you need any help and don't do anything rash 07.22.40 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:2cd2:c1bb:2168:4527) 07.27.22 Quit ZincAlloy (Ping timeout: 276 seconds) 07.32.42 *** Saving seen data "./dancer.seen" 07.52.26 Quit advcomp2019_ (Ping timeout: 240 seconds) 09.04.44 Join petur [0] (~petur@rockbox/developer/petur) 09.32.43 *** Saving seen data "./dancer.seen" 09.37.02 Join dys [0] (~dys@2003:5b:203b:100:a64c:c8ff:fef4:13a6) 09.38.24 # Jason666: you may get some good result with testdisk. 10.59.07 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.32.45 *** No seen item changed, no save performed. 11.40.34 Quit michaelni (Quit: Leaving) 11.50.30 Join michaelni [0] (~michael@213-47-68-29.cable.dynamic.surfer.at) 11.56.36 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:752a:d090:fdd1:58) 12.01.11 Quit ZincAlloy (Ping timeout: 252 seconds) 12.28.15 Quit TheSeven (Ping timeout: 264 seconds) 12.28.34 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 12.34.53 Join lebellium [0] (~lebellium@89-92-69-72.hfc.dyn.abo.bbox.fr) 12.36.24 Quit Jason666 (Remote host closed the connection) 13.17.40 Join Rower- [0] (~husvagn@m83-185-86-194.cust.tele2.se) 13.21.12 Quit Rower (Ping timeout: 268 seconds) 13.31.38 Join vmx [0] (~vmx@p5B2A2851.dip0.t-ipconnect.de) 13.32.47 *** Saving seen data "./dancer.seen" 13.52.01 Join massiveH [0] (~massiveH@ool-18e4eaeb.dyn.optonline.net) 14.28.14 Quit paulk-leonov (Ping timeout: 264 seconds) 14.31.52 Join paulk-leonov [0] (~paulk-leo@leonov.paulk.fr) 14.39.11 Quit St3ak (Ping timeout: 246 seconds) 14.39.58 Join PimpiN8 [0] (~textual@77.60.122.82) 14.51.36 Join St3ak [0] (~st3ak@st3ak3000.powered.by.lunarbnc.net) 15.06.38 Quit massiveH (Quit: Leaving) 15.32.48 *** Saving seen data "./dancer.seen" 15.46.52 Join dandels [0] (~dandels@unaffiliated/dandels) 16.24.26 Quit PimpiN8 (Quit: My MacBook has gone to sleep. ZZZzzz…) 16.46.35 Quit deevious (Quit: deevious) 17.03.43 Join jdarnley [0] (~J_Darnley@d51A44418.access.telenet.be) 17.06.01 Quit J_Darnley (Ping timeout: 240 seconds) 17.15.53 Join jason666 [0] (477eb166@pool-71-126-177-102.washdc.fios.verizon.net) 17.15.54 Join ZincAlloy [0] (~Adium@ip5f5acea4.dynamic.kabel-deutschland.de) 17.16.42 # this webchat doesn't store any history. so, I can't see anything just because it said connecting and I hit refresh! 17.17.53 # thankfully can see today's log so that's ok. 17.18.24 # Its's an IRC channel, so it behaves like an IRC channel. That you use a web irc client to access it doesn't change that 17.20.33 Quit ZincAlloy (Ping timeout: 265 seconds) 17.21.33 Quit Moarc (Quit: i znowu NADMUCHAŁ BALONA) 17.23.18 Join Moarc [0] (~chujko@a105.net128.okay.pl) 17.30.43 Join advcomp2019 [0] (~advcomp20@65-131-187-234.sxct.qwest.net) 17.30.43 Quit advcomp2019 (Changing host) 17.30.43 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 17.32.51 *** Saving seen data "./dancer.seen" 17.55.20 Quit asaba (Quit: Relay server offline) 17.56.51 Join asaba [0] (~asaba@103.113.159.184) 18.23.47 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:945d:2637:309d:b363) 18.33.17 Quit pamaury (Quit: Konversation terminated!) 18.59.38 Quit vmx (Remote host closed the connection) 19.02.22 Quit mikroflops (Ping timeout: 245 seconds) 19.15.17 Quit dys (Ping timeout: 245 seconds) 19.32.53 *** Saving seen data "./dancer.seen" 19.48.02 Quit michaelni (Quit: Leaving) 19.56.35 Join michaelni [0] (~michael@213-47-68-29.cable.dynamic.surfer.at) 20.12.44 Join mikroflops [0] (~yogurt@c188-150-216-144.bredband.comhem.se) 20.19.30 Join J_Darnley [0] (~J_Darnley@d51A44418.access.telenet.be) 20.20.00 Quit jdarnley (Ping timeout: 250 seconds) 21.32.38 Quit JanC (Remote host closed the connection) 21.32.57 *** Saving seen data "./dancer.seen" 21.32.59 Join JanC [0] (~janc@lugwv/member/JanC) 22.56.42 Quit dandels (Quit: WeeChat 2.6) 23.33.00 *** Saving seen data "./dancer.seen"