![]() |
#16 |
Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 14
Karma: 8518
Join Date: Dec 2012
Device: Kobo touch
|
The strange fact is that it seems to power on and off, I mean, I press it once and the led lights green, then blue, then green, green, green etc, then I press it again and it doesn't light, as if it turns off.
and, @ david_e, it doesn't seem unfair to me at all to go to the shop, because it's not normal that a device freezes or bricks while restarting after an update, whether it is sideload or not, because when the Kobo updates the firmware via wi-fi it's the same thing: it downloads the firmware in the folder and then updates, I guess. Now I'll try to fully recharge it, as someone said. I never charged it before, so I don't know whether the led lights or not during charge, I wouldn't recognise it charging. Do you think they'll eventually fix it if I use my warranty? Sorry for my bad english |
![]() |
![]() |
#17 | |||
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:
Quote:
Quote:
Last edited by davidfor; 12-31-2012 at 06:09 AM. Reason: fixed quoting |
|||
![]() |
Advert | |
|
![]() |
#18 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 369
Karma: 37869
Join Date: Sep 2011
Device: Kobo eReader Touch, Kobo Aura HD
|
I think Kobo Touch has at least two different hardware depending on the year they were built.
A follower of my blog sent me an email about his Kobo touch he just bought (so in december 2012) and when he connected it for the first time to Kobo desktop he was curious and checked the newest downloaded firmware : The firmware was the same size as the kobo4 directory so it was a firmware that we think is for Glo / Mini. He also explained that his new Kobo Touch was a little faster his other one. He wouldn't enable telnet access to check /etc/procinfo though. I think that is the reason why Kobo made so many posts explaining sideloading firmware is a bad idea : They have many different hardware to handle and u-boot and kernel could be different in each case. @murg I sideloaded 2.3.2 to my Touch and I've not found a single fix for a problem bugging me since 2.3.1 Last edited by vlad59; 12-31-2012 at 06:18 AM. |
![]() |
![]() |
#19 |
Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 14
Karma: 8518
Join Date: Dec 2012
Device: Kobo touch
|
It has benn charging for almost an hour, bur still nothing.
I tried to reset it in every possible way, but nothing has happened yet. I think it's dead ![]() |
![]() |
![]() |
#20 | |
No Comment
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
If Kobo has followed their standard M.O., then 2.3.2 is a quick fix of 2.3.1, fixing only showstopper bugs. I wouldn't expect it to fix the ordinary, standard, run of the mill bugs that we've all come to know and love. |
|
![]() |
Advert | |
|
![]() |
#21 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 369
Karma: 37869
Join Date: Sep 2011
Device: Kobo eReader Touch, Kobo Aura HD
|
Or it's just a way to give book statistics (main feature of 2.3.1) to Japanese people who were stuck on 2.2.1. I'm not sure if 2.3.1 was released also in Japan.
|
![]() |
![]() |
#22 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,269
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
|
Quote:
This is purely conjecture. But if it were the case that Kobo changed the hardware without an obvious model number change, then I feel no sympathy for whatever extra returns they might get by people bricking their devices, even though firmwrae sideloading is a little off reservation. (Whatever happened to the tech of the first generatoin kobo's.. as I recall, those were able to boot from SD card. Seems like a sensible failsafe to build into a device, no?) |
|
![]() |
![]() |
#23 |
Evangelist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 416
Karma: 1045911
Join Date: Sep 2011
Location: Cape Town, South Africa
Device: Kindle 3
|
I picked up a Touch for fun a few days ago. Got home, started the update - hung at restarting. Tried everything mentioned on the net, the same stuff mentioned in here. Eventually opened it and checked out the sd card, there were some ext fs errors which I fixed. Still didn't bring it back to life.
After a day of fixing it, I just put it back together and took it back to the shop for replacement. Got home with the new one, first thing I did was pop open the unit and clone the sd card, then continued as I had the first time. Updated fine and everything went smoothly. So, I'd just get it replaced. Terrible experience to have tho. A bit worrying that they are managing to break the factory restore stuff with an update. Edit : If you arnt able to restore it, I can upload the image which you could use to restore from; but it's a last resort. I'm not doing that for fun. |
![]() |
![]() |
#24 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 369
Karma: 37869
Join Date: Sep 2011
Device: Kobo eReader Touch, Kobo Aura HD
|
Quote:
|
|
![]() |
![]() |
#25 |
Evangelist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 416
Karma: 1045911
Join Date: Sep 2011
Location: Cape Town, South Africa
Device: Kindle 3
|
Didn't sideload the update here, bricked on the reboot screen. Even if it were a problem of hardware revisions, surely their update mechanism would do a device side check?. Then again, since they did seem to break the filesystems and it seems, modify the factory/recovery partition, I'm not so certain their updating practices are all that good :/
|
![]() |
![]() |
#26 | |
Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 14
Karma: 8518
Join Date: Dec 2012
Device: Kobo touch
|
Quote:
They should revise the whole updating system, and all the related stuff. I also thought of opening it and chance the sd, but your experience suggests me that the only thing left to do is to replace the Kobo or send it to the customer care or something. |
|
![]() |
![]() |
#27 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,269
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
|
Can you really confirm that you opened and found an SD card in a Touch? Up until now, the internal SD card was a Glo only perk. Can you provide pictures of a "Touch" with interal SD Card?
The EXT errors would indicate that the memory card was faulty, or some other low level hardware fault was a play. This bricking (and possibly the other reported bricking) is not the result of wrong firmware file. |
![]() |
![]() |
#28 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 44,906
Karma: 168802811
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
As for the Japanese bug fix release, it may be fixing a bug that only affects Japanese ebooks where a yokogaki (left to right, top to bottom) book was fine but a tategaki (top to bottom, right to left) book had issues. A show stopper if you are reading tategaki books but a non-issue for the rest of world. Take a look at Microsoft's hot fixes for a shopping list of "don't apply this hot fix unless you are experiencing the problem" items. Going back a lot of years, I remember filing an APAR for a bug in Lotus 1-2-3 that only showed up when you used a odd resolution on a Hercules graphics card equipped PC. Of course, the accounting department had to use that resolution for reasons that escaped me at the time and still do. I would prefer if Kobo had more beta testers who operated their readers in less than standard ways. Someone like myself who tends to do as much as possible formatting on the computer and leaves the reader controls alone is not a great candidate for finding many of the bugs that come out when the reader controls are played with. The type of user who like using different fonts, margin widths, etc. Regards, David Last edited by DNSB; 01-01-2013 at 11:15 AM. Reason: Fat fingered typos -- what else is old. |
|
![]() |
![]() |
#29 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 196
Karma: 1086780
Join Date: Jul 2012
Device: Kobo H2O Ed. 2, Glo HD, Glo, Touch
|
|
![]() |
![]() |
#30 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,269
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
|
since I obviously know nothing about current Touch hardware, I'll gracefully (or, at least as much as I can with my foot so far in) bow out. The good news, however, anyone who might have bricked their touch, if it's so equipped, should be able to recover the device, eving if some technical help might be required.
|
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo still bricked | MrBig | Kobo Reader | 54 | 05-03-2012 02:29 PM |
Just Bricked my original kobo | reyes | Kobo Reader | 2 | 02-06-2012 04:36 PM |
Bricked Kobo | trevend | Kobo Reader | 4 | 07-29-2011 12:16 PM |
Kobo Bricked? | jbreality | Kobo Reader | 4 | 07-20-2011 03:51 AM |
Firmware Upgrade Bricked my Kobo | jml78 | Kobo Reader | 3 | 04-04-2011 04:09 AM |