MobileRead Forums - View Single Post

LarfinGiraffe · 04-17-2015, 02:30 AM

Thanks AskzYDre for your very full response.
My md5sum is the same as yours.
Your are correct in what you suggest about the card having been used elsewhere before - I can't remember in what (it may have been the Kobo itself). Its a Sandisk Ultra 32GB.
My hardware doesn't have a micro sd card slot, but if I put the card in a usb "stick" micro sd card holder, I can mount the filesystem there and I get the three mounted filesystems. It looks as if the filesystems are complete, with three mountpoints KOBO eReader, recoveryfs and rootfs, so I'm tempted to think that the img write was achieved ok. Of course, there could be corruption at a lower level.
davidfor says the the serial number is not significant, and as I don't know mine anyway I can't do anything about it!
I will try the dd later today and see if it makes any difference, just in case "Disks" did something funny to the img. I'm happy at the command line. I also have a "USB image writer" utility but I think dd is probably the purest way.
I will also try a different sd card. I have read some entries where it appeared to make a difference but of course it could be that the poster got it right second time...
Other than that, I guess there may be the possibility that in fact the screen is duff, so actually its all working ok but cannot show me anything?

04-17-2015, 02:30 AM	#11
LarfinGiraffe Junior Member Posts: 8 Karma: 10 Join Date: Mar 2015 Device: kobo N905	Thanks AskzYDre for your very full response. My md5sum is the same as yours. Your are correct in what you suggest about the card having been used elsewhere before - I can't remember in what (it may have been the Kobo itself). Its a Sandisk Ultra 32GB. My hardware doesn't have a micro sd card slot, but if I put the card in a usb "stick" micro sd card holder, I can mount the filesystem there and I get the three mounted filesystems. It looks as if the filesystems are complete, with three mountpoints KOBO eReader, recoveryfs and rootfs, so I'm tempted to think that the img write was achieved ok. Of course, there could be corruption at a lower level. davidfor says the the serial number is not significant, and as I don't know mine anyway I can't do anything about it! I will try the dd later today and see if it makes any difference, just in case "Disks" did something funny to the img. I'm happy at the command line. I also have a "USB image writer" utility but I think dd is probably the purest way. I will also try a different sd card. I have read some entries where it appeared to make a difference but of course it could be that the poster got it right second time... Other than that, I guess there may be the possibility that in fact the screen is duff, so actually its all working ok but cannot show me anything?