Native Some help with compilation and/or testing

[Sats]

Originally Posted by shamanNS

He has a PW3, you can see the serial number in output text (G090G1 = PW3).

Ah, right, I was looking at the member description. Either way, I think it might still be using old C++ ABI. I checked Oasis FW, and it did, and Scribe latest firmware was using c++11, so I am not sure when they switched.

Originally Posted by JSWolf

This is texting to try to get KFX off of a Kindle and have it end up in calibre with no DRM.

Yes, it is just a port of KFXArchiver. It scans your KFX books and tries to decrypt them and save into /mnt/us/dedrm. The decrypted books are slightly larger than encrypted (due to compression) but compress better, so in general, end up taking about the same amount of space as downloaded ones. I have compiled the variants that I think would matter into 4 executables and made KUAL wrapper for them. I need to know if they work on variety of devices, or if they need to be compiled differently. But it has to run decryption on the book, since that is where it goes into system library and where the ABI divergence would cause it to crash, normally.
Everything above 5.16.3(?) Should be able to run "hf" version (i am still unclear how firmware managed to introduce *hardware* floats), anything below should be able to run version without. C++ABI breakpoint, I do not know, so please try both and report?

If it is confirmed to work on enough devices, i may consider what to do about space issues. Two approaches: make it generate keyfile or decrypt books inplace (leaving them open to overwriting)...

[Hag_Sub]

Originally Posted by Sats

Fair enough, though liberating them is getting harder...




If you are on PW1, or anything under and potentially including oasis, please try kfxdedrm_old, though space might be an issue. Not sure what to do about it (space) for now. kfxdedrm_c11 has incompatible ABI, hence the bad_alloc crash.

I'm on pw3 and is there a way for me to specially select which book i wanna dedrm

[DiapDealer]

Moderator Notice
Compilation advice is one thing, but Mobileread cannot be used for the detailed discussion of, nor log sharing from, the testing of a new DRM removal strategy.

[Hag_Sub]

Thanks for the reminder.

[Sats]

Understood. Please use DM or Github discussion.
@Hag_Sub: not at the moment, no. I need to know if any of the executables are compiled correctly for variety of devices before I do any refinements.

[DiapDealer]

Thanks for understanding. And best of luck with your efforts.

[lkmiller]

Originally Posted by JSWolf

This is testing to try to get KFX off of a Kindle and have it end up in calibre with no DRM.

Of course I realize that's the main objective. But the PW1 doesn't get KFX format and is being dropped. Hence, my question about asking to test on that device.

[Sats]

Originally Posted by lkmiller

Of course I realize that's the main objective. But the PW1 doesn't get KFX format and is being dropped. Hence, my question about asking to test on that device.

No particular point, then. I am not actually aware which devices can download KFX, so, my mistake, in this case. I would like some feedback on other devices, though... I will alter it to be hopefully more... convenient and post github discussion when I am done.

[shamanNS]

KFX is used on PW2+, azw3/KF8 from Kindle 3+.

[Sats]

Originally Posted by shamanNS

KFX is used on PW2+, azw3/KF8 from Kindle 3+.

There was no change in older devices (non-KFX) (AFAIK), so there is no point in me doing anything...

[Sats]

Right, here is the discussion.

[lkmiller]

Originally Posted by Sats

There was no change in older devices (non-KFX) (AFAIK), so there is no point in me doing anything...

No change and they will be unable to connect to Amazon in any way after May 20.

Thanks for your continued work on this.