Aura H2O 1st edition having wifi troubleshoot and after firmware update loading logo stuck

[Kobo4Life]

Hello,

I had an issue with my aura H2O 1st edition at boot: I couldn't connect to my wifi so I couldn't register etc.

So I changed the sql file such that it noticed me with an user "0","0",..

Then it could boot and have main menu but still I couldn't connect to wifi.

So I downloaded a firmware 4.35.20400 Kobo5
During reboot I got the picture linked in description.
And then a loading logo. And now it stuck on the loading logo.
Even after reboot.

And I kept trying to fix these issue by reinstalling img to internal sd card.
And keep having this wifi issue.

If you have a way to solve this I would be please to read it.

Thanks

[Kobo4Life]

When I connect through serial I have this:

> /usr/local/Kobo/nickel: /usr/lib/libxml2.so.2: no version information available (required by /usr/local/Kobo/libnickel.so.1)
> epdfbdc_set_width_height(1439): new DCSize(3342336)>original DCSize(3317760) !

[Kobo4Life]

aepdfbdc_set_width_height(1439): new DCSize(3342336)>original DCSize(3317760) !
gunzip: corrupted data
upgrade/mx50-ntx/u-boot_lpddr2_512-E606G0-LPDDR2.bin: FAILED
upgrade/mx50-ntx/u-boot_mddr_256-E606F0B-K4X2G323PC.bin: FAILED
lupgrade/mx50-ntx/uImage-E606F0B: FAILED
lupgrade/mx50-ntx/uImage-E606G0: FAILED
md5sum: WARNING: 4 of 4 computed checksums did NOT match


epdc_intr_work_func(4799):some thread is waiting for update !but we won't want to wake it up !
upd_pending_list empty=1,upd_buf_free_list full=0,cur_update@(null),epdc_luts_active=0x1
epdc_intr_work_func(4799):some thread is waiting for update !but we won't want to wake it up !
upd_pending_list empty=1,upd_buf_free_list full=1,cur_update@(null),epdc_luts_active=0x1
1+0 records in
1+0 records out
131072 bytes (128.0KB) copied, 0.008666 seconds, 14.4MB/s
on1+0 records in
1+0 records out
512 bytes (512B) copied, 0.001506 seconds, 332.0KB/s
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!

[Szybet]

both messages are normal to my experience

You can't fix your problem, the software you have problem is closed source, doing anything is throwing darts while being blind

If you really want to fix your ereader - port InkBox to it, embrace open source, reject proprietary software.

[Kobo4Life]

Originally Posted by Szybet

both messages are normal to my experience

You can't fix your problem, the software you have problem is closed source, doing anything is throwing darts while being blind

If you really want to fix your ereader - port InkBox to it, embrace open source, reject proprietary software.

I will take a look thanks.
The issue is that I can't connect through wifi though.
And I believe it has something to do with drivers or smth
When I type ntx_hwconfig I get : Wifi='WC121A2'
Which don't appears in cases of /etc/init.d/rcS

[Kobo4Life]

Originally Posted by Szybet

both messages are normal to my experience

You can't fix your problem, the software you have problem is closed source, doing anything is throwing darts while being blind

If you really want to fix your ereader - port InkBox to it, embrace open source, reject proprietary software.

Unfortunately the version N250 of my kobo is not available on inkbox

maybe I could install a version closed to it? like N236 aura SE? idk maybe screen size are different?

[Szybet]

Nope, you would need to port it
It is possible, just work to be done

[hatuluang]

Originally Posted by Kobo4Life

Hello,

I had an issue with my aura H2O 1st edition at boot: I couldn't connect to my wifi so I couldn't register etc.

Probably you can see this information on https://help.kobo.com/hc/en-us/artic...ported-by-Kobo

[Kobo4Life]

Originally Posted by Szybet

Nope, you would need to port it
It is possible, just work to be done

I just don't get what the point of InkBox is since there already is kobolab/Kobo-Reader which are the opensource of Kobos.

It looks like to me an automatic toolchain and compilation process almost forked from kobolabs.

[JSWolf]

Originally Posted by Kobo4Life

Hello,

I had an issue with my aura H2O 1st edition at boot: I couldn't connect to my wifi so I couldn't register etc.

So I changed the sql file such that it noticed me with an user "0","0",..

Then it could boot and have main menu but still I couldn't connect to wifi.

So I downloaded a firmware 4.35.20400 Kobo5
During reboot I got the picture linked in description.
And then a loading logo. And now it stuck on the loading logo.
Even after reboot.

And I kept trying to fix these issue by reinstalling img to internal sd card.
And keep having this wifi issue.

If you have a way to solve this I would be please to read it.

Thanks

Ask in the thread Kobo µSD Card Image Requests in the Kobo Developer's forum and ask for an image for your Kobo. You can get a larger card and have more storage as well as a working device.

[DNSB]

Originally Posted by JSWolf

Ask in the thread Kobo µSD Card Image Requests in the Kobo Developer's forum and ask for an image for your Kobo. You can get a larger card and have more storage as well as a working device.

Sadly, Jon, you are a day late and a dollar short. The request for a firmware image was fulfilled on 2024-Feb-10.

Originally Posted by Kobo4Life

And I kept trying to fix these issue by reinstalling img to internal sd card.
And keep having this wifi issue.

Sadly, a firmware image is a fix for some problems but any hardware issues will not be helped.

[Szybet]

Originally Posted by Kobo4Life

I just don't get what the point of InkBox is since there already is kobolab/Kobo-Reader which are the opensource of Kobos.

It looks like to me an automatic toolchain and compilation process almost forked from kobolabs.

I... I'm done. I can't handle this level of ignorance. It's not stupidity, like you don't understand what an OS is, it's just the ignorance of not opening the InkBox website and going 2 folders deep in the kobolabs repo.

Nicolas advised me to remove the AI response because I will be banned. Huh

[Kobo4Life]

Originally Posted by Szybet

I... I'm done. I can't handle this level of ignorance. It's not stupidity, like you don't understand what an OS is, it's just the ignorance of not opening the InkBox website and going 2 folders deep in the kobolabs repo.

Nicolas advised me to remove the AI response because I will be banned. Huh

yeah you are just entitled as I said it's the N250 I won't spend time trying to dev on your repo just to fix my issue which was a wifi not connecting error which is fixed the next patch..

So basically you and Nicolas are not answering my question just to be clear.

I was gonna say to Nicolas with this AI answer: "oh you have nothing else to do just to spam your 248star project on every thread just to get more stars and to fill the narcissism issue."
But fortunately since it's between "" I didn't said it else will be banned if it was an AI response. And again it would be offtopic as usual with you and your little friend

[Kobo4Life]

Originally Posted by JSWolf

Ask in the thread Kobo µSD Card Image Requests in the Kobo Developer's forum and ask for an image for your Kobo. You can get a larger card and have more storage as well as a working device.

Yes thanks . I did that and got the Aura 3.7 which apparently has a bug on wifi connection in my case.

So basically I updated and now the wifi bug disappeared . Unfortunately it keep syncing an updating issue.

I think it's something I already saw here with Kobo H2O 1st edition. Which can be a real pain and not worth repairing. It's the one waterproof where when you dismantle it even the screen is glu to the cover...

[Kobo4Life]

Ok everything works fine. So I should explain better my issues and how I solved it for the few marginal that bought a H2O 1st edition.

Issue: After getting the 3.7.0 image (aug 2014) from here during, registration there was an error after entering password for the wifi connection.


solution (that worked for me):

• burn img 3.7.0 (aug 2014 version) to internal sd
• Downlad firmware 3.15.0 kobo 5 here
• Extract KoboRoot.tgz to .kobo
• Change KoboReader.sqlite user database value to ["0","0","0","0","0","0",false ,false, false] to avoid registration and autoupdate.
• Finally reboot.

And now works like a charm.

PS:
Just to mention, I spent a lot of time trying different firmware version that didn't work:
- 4.2.8432
- 4.20.14617
- 4.31.19086
- 4.35.20400
- 4.38.21908