MobileRead Forums - View Single Post - How to update Kindle 2/DX/DXG with YifanLu's firmware from 3.2.1 to 3.4.2

donB006 · 11-03-2015, 10:13 AM

OK, KNC1-

Let me try to clarify my situation. I first bought a Kindle3 with 3G with OS 3.1 and applied a jailbreak and tried various hacks. I applied the update-providers hack because I was happy with 3.1 and didn't want the additional social reading features with the 3.2 updates. I then bought a Kindle DXG with OS 2.5.8 and wanted the better PDF reader and browser features of the 3.1 OS. I used the Yifan Lu kindleupdater to update the DXG to OS 3.1 using my K3G. That results in the DXG using Yifan's custom recovery kernel based on the 2.5.8 kernel while borrowing most of the OS 3.1 from the K3G. For example my DXG now has modules from both kernels in the /lib/modules/2.6.22.19-lab126 and /lib/modules/2.6.26-rt-lab126. So my 3.1 DXG now runs the 2.6.22.19 kernel while having most of the OS files from the 3.1 K3G built for the 2.6.26-rt kernel. The DXG kernel is actually a custom kernel built by Yifan Lu based on the 2.5.8 kernel and not the stock kernel from the DXG 2.5.8. I expect the same 2.6.22 Yifan custom kernel will be used even if I upgrade my DXG to the 3.4.2 OS.

Reference: https://www.mobileread.com/forums/sho...d.php?t=127969

I now know my problem trying to upgrade my DXG from 3.1 to 3.3 is caused by my editing the syslog-ng.conf file and not the jailbreak. Concerning jailbreaks- NiJule says in his first jailbreak post:
*Note for Kindle >= 3.1 Users:*
If you haven't done so already (either with >= 0.5.N or yifanlu's
jailbreak), please update your jailbreak hack.

Yifan Lu at his website and various places says:

(If you are already jailbroken, regardless of what version you're
running, you don't need to download this. The actual jailbreak hasn't
been updated, just the injection method.)

I figured some of the people who use NiJule's jailbreak would keep their jailbreak up-to-date while some of the people who use Yifan Lu's jailbreak would leave well enough alone. I probably didn't find the best quotes except that is what I meant and that has always caused me to be confused as to what to do. Maybe I misunderstood. Now I think my jailbreak isn't the cause of the failed update.

Yes, I am the cause of my problems. I had edited my syslog-ng.conf file to only report a high level of "notice" and so there was never anything put in my /var/log/messages. I think that improved the speed and saved the eMMC from wear and tear. Coincidently, Amazon looks in the /var/log/messages for various reasons like sending OTA updates so those can be affected. That has never caused any problems as far as I am concered. I never expected Amazon to check the file for the MD5 and that was my mistake. Amazon has a habit of patching numerous files instead of replacing them during an update and they refuse to patch if the file has been changed causing the update to fail. I am now looking for the unmodified syslog-ng.conf to make the Amazon updater happy. I must blame myself for this problem.

Thank you for your interest and detailed questions knc1. I now know what I need to do.

11-03-2015, 10:13 AM	#123
donB006 Connoisseur Posts: 86 Karma: 186294 Join Date: Jun 2011 Device: Kindle k3G 3.4.2; DXG 2.5.8; DXG 3.1; Iriver Story HD	OK, KNC1- Let me try to clarify my situation. I first bought a Kindle3 with 3G with OS 3.1 and applied a jailbreak and tried various hacks. I applied the update-providers hack because I was happy with 3.1 and didn't want the additional social reading features with the 3.2 updates. I then bought a Kindle DXG with OS 2.5.8 and wanted the better PDF reader and browser features of the 3.1 OS. I used the Yifan Lu kindleupdater to update the DXG to OS 3.1 using my K3G. That results in the DXG using Yifan's custom recovery kernel based on the 2.5.8 kernel while borrowing most of the OS 3.1 from the K3G. For example my DXG now has modules from both kernels in the /lib/modules/2.6.22.19-lab126 and /lib/modules/2.6.26-rt-lab126. So my 3.1 DXG now runs the 2.6.22.19 kernel while having most of the OS files from the 3.1 K3G built for the 2.6.26-rt kernel. The DXG kernel is actually a custom kernel built by Yifan Lu based on the 2.5.8 kernel and not the stock kernel from the DXG 2.5.8. I expect the same 2.6.22 Yifan custom kernel will be used even if I upgrade my DXG to the 3.4.2 OS. Reference: https://www.mobileread.com/forums/sho...d.php?t=127969 I now know my problem trying to upgrade my DXG from 3.1 to 3.3 is caused by my editing the syslog-ng.conf file and not the jailbreak. Concerning jailbreaks- NiJule says in his first jailbreak post: Note for Kindle >= 3.1 Users: If you haven't done so already (either with >= 0.5.N or yifanlu's jailbreak), please update your jailbreak hack. Yifan Lu at his website and various places says: (If you are already jailbroken, regardless of what version you're running, you don't need to download this. The actual jailbreak hasn't been updated, just the injection method.) I figured some of the people who use NiJule's jailbreak would keep their jailbreak up-to-date while some of the people who use Yifan Lu's jailbreak would leave well enough alone. I probably didn't find the best quotes except that is what I meant and that has always caused me to be confused as to what to do. Maybe I misunderstood. Now I think my jailbreak isn't the cause of the failed update. Yes, I am the cause of my problems. I had edited my syslog-ng.conf file to only report a high level of "notice" and so there was never anything put in my /var/log/messages. I think that improved the speed and saved the eMMC from wear and tear. Coincidently, Amazon looks in the /var/log/messages for various reasons like sending OTA updates so those can be affected. That has never caused any problems as far as I am concered. I never expected Amazon to check the file for the MD5 and that was my mistake. Amazon has a habit of patching numerous files instead of replacing them during an update and they refuse to patch if the file has been changed causing the update to fail. I am now looking for the unmodified syslog-ng.conf to make the Amazon updater happy. I must blame myself for this problem. Thank you for your interest and detailed questions knc1. I now know what I need to do.