[Terhi]

Hi,

my ol'sony reader has badsectors which causes unresponsive dictionary, hang after battery charge, hang after reading too many pages, hang after you name it...

To fix this with the help of wiki, I tried to get to recovery mode with unrooted device, however it just didn't. So I rooted it which went fine.

No, when I try to enter security mode (by using ebook_msc.exe), opening book stops 100%, and then just nothing happens. What I think should happen is that windows installs a driver (or I should manually update "Gadget Serial 2.4" -driver). Yellow led is blinking now and then...so maybe it's trying to do something?

There is no recognized or unrecognized devices and COM10 is not active (or any other serialport).

I have allowed my windows 10 to accept non-digital signed drivers to be installed if I need to manually install the driver.

Maybe windows 10 is not responsing properly? Or something else I'm not doing right?

EDIT: I had 32-bit pc with windows 10. It recognizes the device, however provided gadget serial driver doesn't work. Device don't start and putty of course don't connect. I tried alternative usb to serial drivers, but none worked...

EDIT2: I dug out old dusty win 7 home laptop, and yes was able to connect the device with putty BUT the instruction said to mount /dev/mmcblk0p1 and I get file not found. And I checked that, yes, dev-folder doesn't have mmcblk0p1 at all...

UPDATE & SOLUTION! Seems that windows10 comes with a ELMO GMAS-driver which connects the device. I just thougth to try and connected with Putty to COM3 (ELMO GMAS port), and voilá, I was in my device. I didn't need to install Gagdet drivers or anything. So it's even more easer with win10. I found a 500MB microSD from an old mobile phone and fixed all partitions via sd card (READER-partition (mmcblk2p8), Dictionary partition(mmcblk2p6) and mmcblk2p9 & mmcblk2p10 partitions). Reader- and dictionary-partitions had badblocks, so no need to wonder why ebooks jammed once in a while.