You broke my kobo - Page 2

oren64 · 12-15-2017, 01:46 AM

Quote:

Originally Posted by darryl

But it this was the case it was nice of it to let us know. Perhaps there need to be some changes to who can edit the wiki?

PeterT open the wiki page maybe he can do it because I don't know how to do it.

davidfor · 12-15-2017, 01:51 AM

Quote:

Originally Posted by darryl

But it this was the case it was nice of it to let us know. Perhaps there need to be some changes to who can edit the wiki?

I don't think the OP knew enough to be able to tell that there was a problem. I'd say they were blindly following some incomplete instructions they got somewhere else. Or only partly read.

As to who can edit the Wiki, I'm surprised it is allowing non-logged in users to do it. Or at least that's what it looks like. Maybe that can be changed.

darryl · 12-15-2017, 01:55 AM

Quote:

Originally Posted by davidfor

I don't think the OP knew enough to be able to tell that there was a problem. I'd say they were blindly following some incomplete instructions they got somewhere else. Or only partly read.

As to who can edit the Wiki, I'm surprised it is allowing non-logged in users to do it. Or at least that's what it looks like. Maybe that can be changed.

We can of course give the OP the benefit of the doubt, though the timing described does seem to be suspicious. Possible Wiki Page edits should require one to have been a member for a certain time and made a certain number of posts. Though the 'Wiki seems to have worked well, we do have a problem and a responsibility when malicious changes are involved.

GERGE · 12-15-2017, 01:59 AM

25 posts or so maybe?

Dutchbook · 12-15-2017, 02:01 AM

Or perhaps lock all articles with info that is sensitive to malicious changes, and make the hobbyists that develop the software admins?

I feel that requiring users to be logged in to make the changes, will only make identification easier after the act has occurred, instead of preventing it.

doubleshuffle · 12-15-2017, 02:04 AM

Apart from the timing, what seems highly improbable is that someone would proceed with their second device after bricking the first one, as Question Mark already remarked. I mean, there are people who would do such a thing, but it seems strange.

But the timing is really a give-away. I mean, they had just half an hour to catch the edited wiki page, download two firmware versions, brick two devices, try to factory reset them and post here. Quite a feat.

Braid · 12-15-2017, 05:19 AM

WOW

I did not know this possible. I have always felt like a bit of a wimp for avoiding sideloading firmware, opting to change the affiliate on my Kobo to hope to get the update that way instead. Now I'm rather glad I chose that route. This also makes me glad amazon's website offer all their firmware updates for sideloading.

The timing does seem suspicious, as does the fact that they did it with two ereaders. But still, they could be telling the truth. And more importantly, it could have been me - it is only by chance that I didn't download and install the wrong firmware myself. Scary business.

JSWolf · 12-15-2017, 05:24 AM

Can the IP of who made the changes be gotten and matched to anyone's IP here?

Blas · 12-15-2017, 05:29 AM

omg this guy is overreacting af hahaha chill bro.

Try to read the comments and other threads before doing something on your devices. I am a noob too but I never had problems like that cuz like I read.

JSWolf · 12-15-2017, 05:32 AM

Quote:

Originally Posted by Braid

WOW

I did not know this possible. I have always felt like a bit of a wimp for avoiding sideloading firmware, opting to change the affiliate on my Kobo to hope to get the update that way instead. Now I'm rather glad I chose that route. This also makes me glad amazon's website offer all their firmware updates for sideloading.

If you use geek1011's firmware downloader, you will get the correct links to alow side loading. Also, it's easy to know if the link youare using is valid. The link includes the mark and firmware version. So s long as you know what mark your device is and what firmware version you are downloading, then you cannot get an invalid link.

http://geek1011.github.io/KoboStuff/kobofirmware.html

Dryhte · 12-15-2017, 05:52 AM

I kinda think the OP is a troll.
Clues:
- all caps posts
- timing wise it looks like he updated the wiki and then posted his claim

bartveld · 12-15-2017, 08:24 AM

Troll. Probably doesn't even have devices to brick. And unsurprisingly absent now.

issybird · 12-15-2017, 09:36 AM

Quote:

Originally Posted by Dryhte

I kinda think the OP is a troll.

Quote:

Originally Posted by bartveld

Troll. Probably doesn't even have devices to brick. And unsurprisingly absent now.

The Guidelines say members are not to accuse other members of being trolls. However, since he's been banned, technically you're in the clear.

That would also account for his absence.

Cinisajoy · 12-15-2017, 11:29 AM

Quote:

Originally Posted by issybird

The Guidelines say members are not to accuse other members of being trolls. However, since he's been banned, technically you're in the clear.

That would also account for his absence.

Thank you for the fast reaction.

oren64 · 12-15-2017, 05:39 PM

user2398472834 doesn't stop spamming the wiki page, I don't know how to stop him from edit the page, I tried complain to Wikipedia Administrator, but it didn't work.

I copy the content to google site from a new google account https://sites.google.com/site/kobofirmwarereleases/home
and i give passport to member in this thread, its not the best solution.

If somebody have a better solution please tell.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Aura I can't believe I broke it....	booklover6	Kobo Reader	20	03-13-2015 04:58 PM
The File that Broke the Kobo Glo - Your experiences?	Dr. Drib	Kobo Reader	6	03-09-2013 12:55 AM
360 Plus Help I think I broke my PB360+	tponzo	PocketBook	7	06-05-2011 11:44 AM
I Broke My PE!	bobmutch	enTourage Archive	8	05-23-2011 01:05 AM
Opus Help! I think I broke it	Crusader	Bookeen	19	12-07-2009 06:43 PM

12-15-2017, 01:59 AM	#19
GERGE Guru Posts: 733 Karma: 5797160 Join Date: Jun 2010 Location: Istanbul Device: Kobo Libra	25 posts or so maybe?

12-15-2017, 02:01 AM	#20
Dutchbook Zealot Posts: 102 Karma: 937960 Join Date: May 2017 Device: DPT-RP1	Or perhaps lock all articles with info that is sensitive to malicious changes, and make the hobbyists that develop the software admins? I feel that requiring users to be logged in to make the changes, will only make identification easier after the act has occurred, instead of preventing it.

12-15-2017, 02:04 AM	#21
doubleshuffle Unicycle Daredevil Posts: 13,944 Karma: 185432100 Join Date: Jan 2011 Location: Planet of the Pudding Brains Device: Aura HD (R.I.P. After six years the USB socket died.) tolino shine 3	Apart from the timing, what seems highly improbable is that someone would proceed with their second device after bricking the first one, as Question Mark already remarked. I mean, there are people who would do such a thing, but it seems strange. But the timing is really a give-away. I mean, they had just half an hour to catch the edited wiki page, download two firmware versions, brick two devices, try to factory reset them and post here. Quite a feat.

12-15-2017, 05:19 AM	#22
Braid Groupie Posts: 184 Karma: 700000 Join Date: Dec 2016 Device: Kindle Oasis (2nd), Kobo Aura One, Kindle Voyage, Kobo H2O (1st)	WOW I did not know this possible. I have always felt like a bit of a wimp for avoiding sideloading firmware, opting to change the affiliate on my Kobo to hope to get the update that way instead. Now I'm rather glad I chose that route. This also makes me glad amazon's website offer all their firmware updates for sideloading. The timing does seem suspicious, as does the fact that they did it with two ereaders. But still, they could be telling the truth. And more importantly, it could have been me - it is only by chance that I didn't download and install the wrong firmware myself. Scary business.

12-15-2017, 05:24 AM	#23
JSWolf Resident Curmudgeon Posts: 79,803 Karma: 146918083 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Can the IP of who made the changes be gotten and matched to anyone's IP here?

12-15-2017, 05:29 AM	#24
Blas Ulica Guy Posts: 85 Karma: 43686 Join Date: Aug 2017 Location: Croatia Device: Kobo H2O and Motorola XOOM 2(for comics)	omg this guy is overreacting af hahaha chill bro. Try to read the comments and other threads before doing something on your devices. I am a noob too but I never had problems like that cuz like I read.

12-15-2017, 05:52 AM	#26
Dryhte Crow Posts: 133 Karma: 10808 Join Date: Mar 2012 Location: Where The Sun Don't Shine (much) Device: (Vivlio) Pocketbook Touch HD3	I kinda think the OP is a troll. Clues: - all caps posts - timing wise it looks like he updated the wiki and then posted his claim

12-15-2017, 08:24 AM	#27
bartveld Evangelist Posts: 413 Karma: 1477913 Join Date: Jan 2006 Location: Netherlands Device: KA1, Galaxy S8, Galaxy Tab A 10.1, ReMarkable	Troll. Probably doesn't even have devices to brick. And unsurprisingly absent now.

12-15-2017, 05:39 PM	#30
oren64 I need a chapter break Posts: 4,042 Karma: 56058267 Join Date: Mar 2015 Location: Israel Device: Kobo Glo	user2398472834 doesn't stop spamming the wiki page, I don't know how to stop him from edit the page, I tried complain to Wikipedia Administrator, but it didn't work. I copy the content to google site from a new google account https://sites.google.com/site/kobofirmwarereleases/home and i give passport to member in this thread, its not the best solution. If somebody have a better solution please tell.

Advert

Advert