![]() |
#61 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,274
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
|
I feel like my comments already derailed this discussion, about the firmware, and for that I apologize.
It's true that, despite my vehemence, I can't really blame Kobo. As a self-activated device, the update would never have installed itself, so testing out a new firmware is entirely at my own risk. That I did so without making a full backup first is my own fault. Apparently, if reports are accurate, activating with a blank user account still works just fine. If I had simply left Start Menu installed, I would probably have been fine and able to continue using the device without any great effort. I do appreciate that Kobo is, at least, an open device, without attempts to lock it. Nevertheless, I feel nothing but apathy at having to play more tricks to restore it, when my other devices, (ie: Kindles) have kept on working with no interruption for the past several years. At least I can restore my own Kobo whenever I decide to spend time with it. (Since mine has been factory reset, that also includes reloading all the books I want as TRB as well, also a very time consuming task.) I gave my elderly aunt a Kobo Aura a couple of years ago. So far, I've had to make 3 2hr drive trips to restore her Kobo after she's managed to muck it up by accident. (signed out, deleted all books, deleted dictionaries.) She has no Internet of any kind. I think Kobo should be working on making their software more stable, rather a chorus of "just play along with the silly registration and cloud sync that you have no interest in." |
![]() |
![]() |
![]() |
#62 | |
Ex-Helpdesk Junkie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
Quote:
Despite that one of the big draws of a Kobo is the fact that you don't need to jailbreak it to hack it. People should be accustomed to and accepting of any time Kobo closes a loophole that allowed you to do something you wanted to do. Because after all, official support is everything -- and the end of all things. Oh well, the forum was fun while it lasted, but I guess there's no real point now that only the official firmware is allowed to matter to users. Feeling entitled to have Kobo at your beck and call to fix anything you say needs fixing is one thing. Saying "Kobo changed something in a way that breaks my unofficial workflow, and I no longer have the patience to modify my Kobo to match my needs", is another thing. I think there is a difference in those mindsets. And I am pretty sure @rashkae meant the latter. ... Personally, I am not sure why Kobo needed to implement something that doesn't help them and throws up barriers to using a hack. It's almost like they were deliberately trying to break fake registration. Which is certainly their right. But I think it is eminently reasonable for someone who will specifically only use a fake-registered Kobo to be frustrated. And I don't see why they should be shouted down for expressing that frustration. Last edited by eschwartz; 12-08-2015 at 03:27 PM. |
|
![]() |
![]() |
Advert | |
|
![]() |
#63 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 710
Karma: 2483502
Join Date: Jul 2011
Device: Kobo Aura
|
No, that's not what I'm saying at all. What I am saying is that it's not reasonable to expect Kobo to be able to account for unknown changes that users may have made to their devices. If the firmware fails because of a third-party modification, that's hardly Kobo's fault.
|
![]() |
![]() |
![]() |
#64 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,274
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
|
I can understand why the dialogue I complain about was added. I have no doubt it was to fix problems people had with devices not synching. I don't think it was maliciously to block my use of the device.
It was also incredibly amateurish and ham fisted. Even at first glance, 2 things should have been obvious. 1. The error should have happened only on sync, not on boot with wifi off. 2. There should have been a cancel button, rather than immediately rendering the reader non-operable. |
![]() |
![]() |
![]() |
#65 | |
Linux User
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Quote:
Using arbitrary values instead of empty ones causes the 'critical error'. I'll keep it registered for now. |
|
![]() |
![]() |
Advert | |
|
![]() |
#66 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
|
|
![]() |
![]() |
![]() |
#67 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 817
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
So I'm about to upgrade manually, but after reading through these posts, I want to make sure that I don't have a problem with the fake info I put into the database to bypass the registration procedure. Here is what I originally used:
INSERT INTO "user" VALUES('aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa','aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa','xxxx@xxxx.xxx','xxxx@xxxx.xxx','a', 'a','FALSE','FALSE','FALSE'); Am I correct in assuming that this will not work? Should I change this to: INSERT OR REPLACE INTO "user" VALUES('','','','','', '','','',''); Or something else? The first two fields I believe have a NOT NULL requirement, so I would think I need to set them to something other than ''. Sorry--I am confused. If someone could elaborate on what actually works to bypass the registration for firmware 3.19.5613, I'd appreciate it. Thanks. |
![]() |
![]() |
![]() |
#68 |
Junior Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8
Karma: 118980
Join Date: Nov 2015
Device: Kobo Clara HD
|
I'm more privacy-minded than most and appreciate the information about circumventing registration. It doesn't change my opinion of Kobo devices, but it means that I won't be applying this update.
|
![]() |
![]() |
![]() |
#69 | |
Linux User
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
|
Quote:
I don't know if there are values that work better than '', sorry. '' just happens to be what I used to use for fake registration, and it just happened to (semi-)work with 3.19.x. Maybe someone else will be able to investigate / experiment in more detail... |
|
![]() |
![]() |
![]() |
#70 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
|
|
![]() |
![]() |
![]() |
#71 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 817
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
Oh, sorry, I thought ' ' (with a space between) isn't NULL but '' (with no space) is. My bad. It's been a while since I worked with SQL. I'll give '' a try unless someone else chimes in with a better experience-based solution. (But I don't plan to upgrade until the patches are ready, so it may be a day or two.) Thanks.
|
![]() |
![]() |
![]() |
#72 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Your current setting is more likely to work than setting all the values to empty strings. It's possible the problem is that the other values don't pass a check. There are two UUIDs, two email addresses, and id for the device (a 64 character hexadecimal number) and two keys or tokens of some sort (605 characters, looks like the last character is an equals sign). Filling these fields with something that matches might work. But, syncing to get the firmware updated will probably produce the results rashkae reported. |
|
![]() |
![]() |
![]() |
#73 | |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 817
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
Quote:
|
|
![]() |
![]() |
![]() |
#74 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
What I would suggest is taking a full copy of the user drive. That way, if it doesn't work, you can reset to 3.18.0 and restore the data back to where you are now.
|
![]() |
![]() |
![]() |
#75 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 817
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
|
|
![]() |
![]() |
![]() |
Tags |
firmware 3.19, kobo |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Firmware 3.18.0 discussion | GeoffR | Kobo Reader | 335 | 10-14-2016 12:56 PM |
Firmware 3.17.3 Discussion | PeterT | Kobo Reader | 258 | 09-16-2015 08:13 AM |
Firmware 3.16.0 Discussion | davidfor | Kobo Reader | 240 | 08-14-2015 11:52 AM |
Firmware 3.16.10 Discussion | murg | Kobo Reader | 35 | 08-12-2015 01:08 PM |
New Firmware (1.4) Discussion | Stinger | Kobo Reader | 103 | 07-22-2010 11:02 AM |