MobileRead Forums - View Single Post - Instructions for patching firmware 4.12.12111

NiLuJe · 12-19-2018, 09:00 PM

The other approach I can see (correct/stop me if I'm wrong, this is way out of my wheelhouse) would be to figure out where the final computation of that ReadingView QFrame/QRect is being done, and brute-force an adjustment in there somehow. Could the offset pointed out in the logs be used to step into the memory at runtime via gdb to help figure this out? Or is this a vain effort without debug symbols?

12-19-2018, 09:00 PM	#80
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	The other approach I can see (correct/stop me if I'm wrong, this is way out of my wheelhouse) would be to figure out where the final computation of that ReadingView QFrame/QRect is being done, and brute-force an adjustment in there somehow. Could the offset pointed out in the logs be used to step into the memory at runtime via gdb to help figure this out? Or is this a vain effort without debug symbols?