Clara HD Next Kobo Model - Kobo Clara HD

[jackie_w]

Originally Posted by oren64

I think it's firmware 4.8.10956, check the build number in the revinfo file (the first 10 characters).

By 'revinfo' do you mean the file of that name in usr/local/Kobo inside the KoboRoot.tgz file?

If so the first 10 characters of that are bee5052c41 which matches what I see on the ClaraHD Settings - Device info page which shows:

Software version: 4.8.11090 (bee5052c41, 10/05/2018)

[geek1011]

OK. I've been doing some poking around using Fiddler (debugging proxy), Hopper (dissembler), and some other tools. I've emulated a Kobo Clara by taking the version and affiliate files latepaul provided and placing them in a .kobo folder and using the SUBST command to assign it a drive letter. Kobo desktop detected it as a Kobo and downloaded the update file. I extracted KoboRoot.tgz and grepped for the user agent string (strings libnickel.so.1.0.0 | grep AppleWebKit -C2), which contains the version. It was 4.8.11090.

So, here is the unusual part. It downloads the EXACT same file and URL as the 4.8.10956 update. No other network requests are made that are significant. The funny thing is, the KoboRoot extracted to the fake and the KoboRoot in the update zip do not match. This means that Kobo Desktop is doing some sort of in-between thing between downloading and installing. I really cannot figure out what it is.

I would really appreciate help figuring this out. If anyone wants more details, feel free to ask.

For now, here is the proper update zip I pieced together for 4.8.11090 based on the files Kobo Desktop wrote to the fake Kobo: https://transfer.sh/Oa4Gt/kobo-update-4.8.11090.zip

I've attached the batch file to make a fake kobo.

[geek1011]

Originally Posted by oren64

I think it's firmware 4.8.10956, check the build number in the revinfo file (the first 10 characters).

It's not. The same zip is downloaded, but Kobo Desktop does some additional modifications. See my above post.

[latepaul]

Originally Posted by geek1011

So, here is the unusual part. It downloads the EXACT same file and URL as the 4.8.10956 update. No other network requests are made that are significant. The funny thing is, the KoboRoot extracted to the fake and the KoboRoot in the update zip do not match. This means that Kobo Desktop is doing some sort of in-between thing between downloading and installing. I really cannot figure out what it is.

Note that the first time I set up my Clara HD I did it without Kobo Desktop, direct over Wifi, and I still ended up with 4.8.11090.

[geek1011]

Originally Posted by latepaul

Note that the first time I set up my Clara HD I did it without Kobo Desktop, direct over Wifi, and I still ended up with 4.8.11090.

The Kobo probably also does something funny, or it may check a different url or have some sort of identifying header. You'd need to intercept it to figure it out.

[oren64]

Originally Posted by jackie_w

By 'revinfo' do you mean the file of that name in usr/local/Kobo inside the KoboRoot.tgz file?

If so the first 10 characters of that are bee5052c41 which matches what I see on the ClaraHD Settings - Device info page which shows:

Software version: 4.8.11090 (bee5052c41, 10/05/2018)

Yes this is the file I meant.

Originally Posted by geek1011

It's not. The same zip is downloaded, but Kobo Desktop does some additional modifications. See my above post.

Okay, thanks for checking.

[geek1011]

I've been comparing the zips and found the following:
- A new codename "nova" has been added to rcS
- The following lines were added to kobo_config.sh (does this mean there will be two versions of the Clara?):
E60K0*) echo nova;;
E60U1*) echo nova;;
- There are changes in the binaries. I'll need to disassemble them to figure out more.

[jackie_w]

Originally Posted by geek1011

I've been comparing the zips and found the following:
- A new codename "nova" has been added to rcS
- The following lines were added to kobo_config.sh (does this mean there will be two versions of the Clara?):
E60K0*) echo nova;;
E60U1*) echo nova;;
- There are changes in the binaries. I'll need to disassemble them to figure out more.

The nickel file in the 4.8.11090 fw update downloaded to the ClaraHD is stuffed full of [qApp_deviceIsNova=true] CSS. I know this because I spent most of yesterday evening reworking my Kobo patches to work on this firmware. Not much brain work required for nickel but a bit time consuming. If 4.8.11090 is only for the ClaraHD I guess it's too much to expect a full set of patches to become available.

[geek1011]

I've disassembled the firmware (just libnickel). I used objdump, c++filt, sort, cut, and diff for the comparison. I only compared the symbols, not the content. This is in comparison to 4.8.10956
- The virtual keyboard has been internally refactored (no visible difference)
- Improvements made to SVG rendering
- New function VolumeManager::getByIdBytes
- The Gesture Keyboard hidden feature has been removed
- There is now a disable quick turn reading setting (it can be set in the config file, maybe the gui) (ReadingSettings::disableQuickTurn)
- New class: LM3630ChannelMixer::LM3630ChannelMixer() (Also see http://www.ti.com/product/LM3630A)
- A whole bunch of resize events have been added to basically every control (I wonder why)
- Nova device codename added

Command: arm-none-eabi-objdump -d -S libnickel.so.1.0.0 | grep ZN | cut -d ' ' -f 2 | sort | sed '/^$/d' | c++filt

EDIT: I also compared it to 4.8.11073, which is the most recent available for all devices, and it has the same major changes as when I compare it with 4.8.10956. So, the changes I listed above are exclusive to 4.8.11090.

[geek1011]

And also, *technically*, based on what I've found in the firmware and past experience, you should be able to sideload 4.8.11090 to any device (and any mark), but no guarantees. I haven't tried it myself yet. Also, I don't see why someone would want to as there are no new features. So I highly recommend you don't unless you really want to.

[nicholasalias]

Originally Posted by geek1011

- Nova device codename added

Great, now I want a Kobo Nova.

[geek1011]

Originally Posted by nicholasalias

Great, now I want a Kobo Nova.

It's not a device itself. It is probably the internal name for the Clara just like trilogy is for the Mini.

[CH23]

Originally Posted by geek1011

It's not a device itself. It is probably the internal name for the Clara just like trilogy is for the Mini.

I can confirm that this is the case;

KOReader checks the device name before launching, to set itself up for the right capabilities (like the orange backlight on the ONE and Clara)

I manually added 'nova' to this script, as it wouldn't start.

After doing this, it would.

Clara = Nova

[TheBard]

Originally Posted by CH23

Attachment 164329

have a comparison pic between Glo HD and Clara HD.

I assume the Clara's MicroSD card capacity is 8GB. The slot in the Clara picture seems to be empty, and the slot in the Glo HD contains a 32GB card.

Has anybody tried using a card in the Clara with a capacity greater than 8GB?
If so, does the firmware need to be transferred from the 8GB card, ir is the firmware stored somewhere other than on the MicroSD card?

Thanks!

[ilovejedd]

Originally Posted by TheBard

I assume the Clara's MicroSD card capacity is 8GB. The slot in the Clara picture seems to be empty, and the slot in the Glo HD contains a 32GB card.

Has anybody tried using a card in the Clara with a capacity greater than 8GB?
If so, does the firmware need to be transferred from the 8GB card, ir is the firmware stored somewhere other than on the MicroSD card?

Thanks!

Pic was likely taken when poster was backing up the Clara's uSD to computer.