Quote:
Originally Posted by tshering
Nick, this is interesting. I am wondering how the device was able to determine the download link of the FW. Are you definitely sure that you copied the patched version of KoboRoot.tgz to the device, rather than the original? Would be interesting to read how it worked for PeterT.
There would'nt be a difference.
There is a safety check. Before applying KoboRoot.tgz, there is a check whether it can be decompressed without error.
|
Yes, but I am using an Aura HD, however, when still nothing changed, I now have tried to sync for the 10th time ( nothing to sync but just tried and it all works okay ) it doesn't tried to reload or update 3.2.0 so maybe there was some in the memory left from attempt 1 that triggers/remembered and therefore could do the trick to recall the upgrade server... I did checked the .kobo dir for any upgrade but not for another file or changed configuration file.
So maybe:
Option one of the patch was giving me the trouble the device was not recognised by the system anymore and by calibre.
Pushed the original koboroot.tgz with patched options for wifi etc. back.
Rebooted and yes eReader-3.1.1 device is back.
When I change the firmware, the devicename changes into the firmware.
Then I put the # for option one and removed the one by option 2.
There was no .tgz file in the .kobo directory anymore,but there could be something left from option one that the device could use to still try downloading it, I didn't check the other files in the .kobo directory.
Then the download of 3.2.0 started, wich I interupted by resetting the device with a needle while still upgrading.
After reset, I found a part of the 3.2.0 firmware upgrade which I deleted.
After that, I tried 10 times.. and no attempt to load the new firmware.
So to fully try what happened, Peter should first try to install 3.1.1 then use the usual kpg.conf with the light and header and footer patch etc etc with at the end the part of the patch that should prevent wifi firmware updating and enable option one first.. he had to simulate the whole thing,to see of there is anything left that made it possible for the device to find home....
I think now by myself, that if you don't use option 1, but directly use option 2, it works okay, but only if you use option one first and then option two..the device is be able to find the update server only once, maybe because option one has altered something in the files when it all went tru.
Sorry for my dislectic problems,
what I want to say is that when you don't do it exactly the same as I did with option 1 first,and all the mess after it, but immediately start with option 2 in the first place, all wents okay proplably.