Kobo H2O: Need SD Image - Page 18

davidfor · 11-18-2018, 05:37 PM

Quote:

Originally Posted by svitol

Well problem "solved"...they sent a diff display : ED0680TG1 (LF) instead of the ED0680G1. The one they have sent doesn't have the IR at all

Anyway many thanks for your time and help !

The IR isn't built into the actual screens. I haven't pulled an Aura H2O apart, but for the Glo and Touch, the emittors and sensors are on the main board. Then there is a guide that directs the IR beams across the screen. I have every reason to believe the Aura H2O is the same. This is why I emphasised that it has to be put back together properly.

otabricker · 11-21-2018, 09:45 AM

Hi! I guess I'll need the image for Aura H2O too.

I was updating KOReader via OTA, the ereader resetted and always boots to the "Critical error" page. I've tried the tapping corners reset method, I can get to the dancing squares that way, but after they dance, the screen goes white and a picture tells me to plug the reader to the computer (running the Kobo desktop software, I guess). When I do it, the reader just reboots to the "Critical error" screen. If I tap on the check icon on the "Critical error" screen, it just reboots again.

So, I think I'm fucked up and have to lose the water resistance. Could you please send me the link for the SD image?

Thank you in advance!

davidfor · 11-21-2018, 05:43 PM

PM sent.

elencina · 11-22-2018, 07:20 PM

Dear Guys, I was installing the XCSoar and unfortunately do not take the precaution of making a backup and my kobo no longer works. Now I opened the case and I have the SD card with me.
Would you be so kind to send me a link to the image?
Thank you

davidfor · 11-22-2018, 07:42 PM

PM sent.

elencina · 11-23-2018, 06:29 AM

Thank David!
Muchas gracias y saludos desde Argentina!
Eduardo

otabricker · 11-28-2018, 07:37 AM

Quote:

Originally Posted by otabricker

Hi! I guess I'll need the image for Aura H2O too.

I was updating KOReader via OTA, the ereader resetted and always boots to the "Critical error" page. I've tried the tapping corners reset method, I can get to the dancing squares that way, but after they dance, the screen goes white and a picture tells me to plug the reader to the computer (running the Kobo desktop software, I guess). When I do it, the reader just reboots to the "Critical error" screen. If I tap on the check icon on the "Critical error" screen, it just reboots again.

So, I think I'm fucked up and have to lose the water resistance. Could you please send me the link for the SD image?

Thank you in advance!

First of all, thank you davidfor for the image. I really appreciate this community's effort.

However, I'm having some problems copying it to the SD. I'm using Linux on my laptop, so I've tried dd following some messages in this thread. It seems like it's writing things, or formatting, or whatever I do, but if I unplug & plug back the microSD , everything is just as it was.

I've tried formatting it from a Windows VM, but Windows can't format it.

When trying to format from Debian with:

Code:

sudo mkdosfs -F 32 -I /dev/sdc

I get this error:

Code:

mkdosfs: unable to open /dev/sdc: Device or resource busy

So my suspicions are two:

I'm using a USB to microSD dongle, and that's the big problem. Should I try getting a microSD to SD card adapter?
The microSD card is fucked up, so i can't really wipe it or put data on it.

Also, I couldn't download the "Flash Drive Image Writer" software mentioned in the "Glo Memory Upgrade Mod Guide (With Pictures)" thread. Have they moved it somewhere else?

EDIT: also tried this method, but it doesn't work. Again, after I unplug and plug again the microSD+dongle, it looks like nothing has been deleted.

davidfor · 11-28-2018, 08:13 AM

Quote:

Originally Posted by otabricker

First of all, thank you davidfor for the image. I really appreciate this community's effort.

However, I'm having some problems copying it to the SD. I'm using Linux on my laptop, so I've tried dd following some messages in this thread. It seems like it's writing things, or formatting, or whatever I do, but if I unplug & plug back the microSD , everything is just as it was.

Using dd should work.

Quote:

I've tried formatting it from a Windows VM, but Windows can't format it.

When trying to format from Debian with:

Code:

sudo mkdosfs -F 32 -I /dev/sdc

I get this error:

Code:

mkdosfs: unable to open /dev/sdc: Device or resource busy

So my suspicions are two:

I'm using a USB to microSD dongle, and that's the big problem. Should I try getting a microSD to SD card adapter?
The microSD card is fucked up, so i can't really wipe it or put data on it.

I'd go with the latter. It could be the dongle, but, from the original error, and these, I would think the card is failing.

Quote:

Also, I couldn't download the "Flash Drive Image Writer" software mentioned in the "Glo Memory Upgrade Mod Guide (With Pictures)" thread. Have they moved it somewhere else?

The site has been rearranged. Click the "Support" link and then "Software". It is at the bottom of that page.

otabricker · 11-28-2018, 09:32 AM

Thank you again. I could download the "Flash Drive Image Writer" software, but after 20 minutes, everything was as usual. I'll try to get a microSD -> SD card adaptor and/or buy a new microSD. Thank you for your help.

frostschutz · 11-28-2018, 10:20 AM

the mkfs message is quite normal (depending on circumstance), it probably just means something else is using the device and mkfs doesn't like that. It is not a hardware issue

(not to mention, using mkfs like this is wrong anyhow[*] . you don't want a filesystem on that card, not like this; you want your image which makes a bootloader, kernel image, three partitions with three filesystems, ...)

in modern linux environment that is catering to end users ( Ubuntu et al. ) you sometimes have to fight the system, i.e. you put in a card and stuff gets automounted for you.

and that's bad since you don't want it to be mounted at all.

mounting is what makes the device busy and then you can't format, and if you dd an image onto it, the mounted filesystem will just write data back and thus corrupt the image you just wrote

so you have to make sure the device is not in use first before dumping an image on it

[*] When you connect the Kobo to USB, you get a /dev/sdx device which is the FAT partition only. If you want to force a factory reset, you could mkfs.vfat that device. That's probably where this command is coming from.

However when dealing with the SD card directly, you'll see what Kobo is hiding from you, i.e. partitions and all that. The device that holds a FAT filesystem would then be /dev/sdx3, not /dev/sdx (if it's the internal card; for external card slot, it would be /dev/sdx1)

----

Roughly:

Code:

Attempt to make the device un-used if mounted:

# grep /dev/sdx /proc/mounts
# umount /dev/sdx*

Wipe the old stuff:

# wipefs -a /dev/sdx[0-9]*
# wipefs -a /dev/sdx

Put the image:

# dd bs=1M status=progress if=kobo.sdcard.img of=/dev/sdx
# sync

Unplug.

Optional verification step:

# cmp kobo.sdcard.img /dev/sdx && echo OK

should say OK or EOF on kobo.sdcard.img

davidfor · 11-28-2018, 07:18 PM

Quote:

Originally Posted by otabricker

Thank you again. I could download the "Flash Drive Image Writer" software, but after 20 minutes, everything was as usual. I'll try to get a microSD -> SD card adaptor and/or buy a new microSD. Thank you for your help.

Get the new card. Size doesn't matter much as you can expand the books partition to fill the space.

toodeeptofind · 11-29-2018, 12:10 AM

sd image please for h20 2014 model. @davidfor

davidfor · 11-29-2018, 02:05 AM

PM sent.

otabricker · 11-29-2018, 10:34 AM

Quote:

Originally Posted by frostschutz

Roughly:

Code:

Attempt to make the device un-used if mounted:

# grep /dev/sdx /proc/mounts
# umount /dev/sdx*

Wipe the old stuff:

# wipefs -a /dev/sdx[0-9]*
# wipefs -a /dev/sdx

Put the image:

# dd bs=1M status=progress if=kobo.sdcard.img of=/dev/sdx
# sync

Unplug.

Optional verification step:

# cmp kobo.sdcard.img /dev/sdx && echo OK

should say OK or EOF on kobo.sdcard.img

Thank you for all your explanation. I always used umount before trying to make a partition, so I don't know what could have gone wrong there.

I've performed all the steps you mention (always replacing paths for image and microSD). Unluckily, after confirmation, it says:

Code:

# cmp kobo.sdcard.img /dev/sdx && echo OK

sdcard.img /dev/sdx are different: byte 308, line 1

And obviously, after putting back the microSD (it's the internal one, not the external one) in the ereader, it can't boot. Any idea on anything I could try? I will try to buy a microSD card soon, and fix it once and for all, but right now that is impossible for me.

Thanks again for your help.

frostschutz · 11-29-2018, 10:47 AM

Did you verify before doing anything else with the card? If you let the Kobo boot it, it's normal for differences to appear. Same if you try to resize partitions.

Otherwise it's very odd for there to be a difference in the first sector when supposedly nothing else touches the card.

Unless you're making a mistake like putting the image on /dev/sdx1 instead of /dev/sdx

Other than that I have no ideas... if you are located in Germany, I could send you an old 4GB card correctly preloaded with H2O image (and verified to boot in my own H2O, as in - the original H2O, not the later H2O2v12)

11-28-2018, 10:20 AM	#265
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	the mkfs message is quite normal (depending on circumstance), it probably just means something else is using the device and mkfs doesn't like that. It is not a hardware issue (not to mention, using mkfs like this is wrong anyhow[] . you don't want a filesystem on that card, not like this; you want your image which makes a bootloader, kernel image, three partitions with three filesystems, ...) in modern linux environment that is catering to end users ( Ubuntu et al. ) you sometimes have to fight the system, i.e. you put in a card and stuff gets automounted for you. and that's bad since you don't want it to be mounted at all. mounting is what makes the device busy and then you can't format, and if you dd an image onto it, the mounted filesystem will just write data back and thus corrupt the image you just wrote so you have to make sure the device is not in use first before dumping an image on it [] When you connect the Kobo to USB, you get a /dev/sdx device which is the FAT partition only. If you want to force a factory reset, you could mkfs.vfat that device. That's probably where this command is coming from. However when dealing with the SD card directly, you'll see what Kobo is hiding from you, i.e. partitions and all that. The device that holds a FAT filesystem would then be /dev/sdx3, not /dev/sdx (if it's the internal card; for external card slot, it would be /dev/sdx1) ---- Roughly: Code: Attempt to make the device un-used if mounted: # grep /dev/sdx /proc/mounts # umount /dev/sdx* Wipe the old stuff: # wipefs -a /dev/sdx[0-9]* # wipefs -a /dev/sdx Put the image: # dd bs=1M status=progress if=kobo.sdcard.img of=/dev/sdx # sync Unplug. Optional verification step: # cmp kobo.sdcard.img /dev/sdx && echo OK should say OK or EOF on kobo.sdcard.img Last edited by frostschutz; 11-28-2018 at 10:36 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kobo Aura H2O covers	Josieb1	Kobo Reader	628	08-01-2020 01:44 PM
Kobo Aura H2O CPU	Fabry	Kobo Developer's Corner	3	10-21-2014 01:12 PM
Kobo H2O, still yellow?	desert dog	Kobo Reader	61	10-18-2014 09:55 PM
Kobo H2O Hackability	ManDay	Kobo Reader	38	10-06-2014 12:05 PM
Kobo H2O Specs released	Lynx-lynx	News	42	08-30-2014 07:24 PM

11-21-2018, 09:45 AM	#257
otabricker Junior Member Posts: 6 Karma: 10 Join Date: Nov 2018 Device: Kobo Aura H2O	Hi! I guess I'll need the image for Aura H2O too. I was updating KOReader via OTA, the ereader resetted and always boots to the "Critical error" page. I've tried the tapping corners reset method, I can get to the dancing squares that way, but after they dance, the screen goes white and a picture tells me to plug the reader to the computer (running the Kobo desktop software, I guess). When I do it, the reader just reboots to the "Critical error" screen. If I tap on the check icon on the "Critical error" screen, it just reboots again. So, I think I'm fucked up and have to lose the water resistance. Could you please send me the link for the SD image? Thank you in advance!

11-21-2018, 05:43 PM	#258
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	PM sent.

11-22-2018, 07:20 PM	#259
elencina Junior Member Posts: 3 Karma: 10 Join Date: Nov 2018 Device: kobo mini, h2o	Dear Guys, I was installing the XCSoar and unfortunately do not take the precaution of making a backup and my kobo no longer works. Now I opened the case and I have the SD card with me. Would you be so kind to send me a link to the image? Thank you

11-22-2018, 07:42 PM	#260
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	PM sent.

11-23-2018, 06:29 AM	#261
elencina Junior Member Posts: 3 Karma: 10 Join Date: Nov 2018 Device: kobo mini, h2o	Thank David! Muchas gracias y saludos desde Argentina! Eduardo

11-28-2018, 09:32 AM	#264
otabricker Junior Member Posts: 6 Karma: 10 Join Date: Nov 2018 Device: Kobo Aura H2O	Thank you again. I could download the "Flash Drive Image Writer" software, but after 20 minutes, everything was as usual. I'll try to get a microSD -> SD card adaptor and/or buy a new microSD. Thank you for your help.

11-29-2018, 12:10 AM	#267
toodeeptofind Member Posts: 24 Karma: 10 Join Date: Dec 2017 Device: kobo H2O	sd image please for h20 2014 model. @davidfor

11-29-2018, 02:05 AM	#268
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	PM sent.

11-29-2018, 10:47 AM	#270
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	Did you verify before doing anything else with the card? If you let the Kobo boot it, it's normal for differences to appear. Same if you try to resize partitions. Otherwise it's very odd for there to be a difference in the first sector when supposedly nothing else touches the card. Unless you're making a mistake like putting the image on /dev/sdx1 instead of /dev/sdx Other than that I have no ideas... if you are located in Germany, I could send you an old 4GB card correctly preloaded with H2O image (and verified to boot in my own H2O, as in - the original H2O, not the later H2O2v12)