MobileRead Forums - View Single Post - Problem with Loading back to Nickel from KSM 09

crimsonsnow · 12-25-2019, 12:17 PM

I had noticed this problem since a few months back, but I had no use of Nickel since, so I just ignored the issue. However this month I use Pocket a lot, so I want to go back and forth between Nickel and KSM 09, but whenever I try to choose Nickel from KSM, it only shows me the loading screen (3 dots instead of the previous 5 squares from a few firmwares ago) but no Nickel.

I put the latest Kobo Firmware (Mark 5, 4.19.14123, I use Aura) in .Kobo, but if I do a controlled update, my Nickel installation failed (can't go to Nickel still). If I do uncontrolled update, I basically fresh-installing my device, so I need to reinstall KSM again.

This has happened about 3 times now (fresh-installing Nickel firmware, reinstall KSM, copying Koreader, Plato, and Coolreader to .adds, then boot to KSM, but I can't go back to Nickel again).

Anyone with the same issue or any workaround?

Thanks!

12-25-2019, 12:17 PM	#1
crimsonsnow Enthusiast Posts: 35 Karma: 10 Join Date: Jan 2014 Device: Yotaphone 2, Kobo Aura, FBReader	Problem with Loading back to Nickel from KSM 09 I had noticed this problem since a few months back, but I had no use of Nickel since, so I just ignored the issue. However this month I use Pocket a lot, so I want to go back and forth between Nickel and KSM 09, but whenever I try to choose Nickel from KSM, it only shows me the loading screen (3 dots instead of the previous 5 squares from a few firmwares ago) but no Nickel. I put the latest Kobo Firmware (Mark 5, 4.19.14123, I use Aura) in .Kobo, but if I do a controlled update, my Nickel installation failed (can't go to Nickel still). If I do uncontrolled update, I basically fresh-installing my device, so I need to reinstall KSM again. This has happened about 3 times now (fresh-installing Nickel firmware, reinstall KSM, copying Koreader, Plato, and Coolreader to .adds, then boot to KSM, but I can't go back to Nickel again). Anyone with the same issue or any workaround? Thanks!