Irreversibly Bricked?

[slvrsplsh]

OK, I tried something different. I held the reset button for 30 seconds and pressed the home and menu buttons before I inserted the power cord. It went into recovery mode and after about 60 seconds it went back to the opening book page. This is so frustrating it is maddening!

[Ripplinger]

Are you able to try deleting all books on the reader while it's plugged in with the USB cable?

[Teknikal]

Could be a broken reset button it happened to me, thing just didn't have an effect at all and I had to get the whole reader replaced.

I think on the T1 especially it's very flimsy and just not very reliable.

[slvrsplsh]

Originally Posted by Teknikal

Could be a broken reset button it happened to me, thing just didn't have an effect at all and I had to get the whole reader replaced.

Thanks for the tip. Now that I know it could be an electro-mechanical failure I can pop it open and have a look. I am pretty handy with a soldering iron and I have just the right one for surface mount work.

[slvrsplsh]

So, I opened the clam and took a look. Everything looks to be working. I guess that I am in that very small group of those who have permanently bricked their device. I sure do hate to lose my PRS-T1, but at least I have my Nook Tablet.

[Rizla]

Originally Posted by Teknikal

Could be a broken reset button it happened to me, thing just didn't have an effect at all and I had to get the whole reader replaced.

I think on the T1 especially it's very flimsy and just not very reliable.

That's kinda scary seeing as how it gets used so much. Is there a history of the power button breaking with this device?

[slvrsplsh]

After reading a post on another thread, I think I may have discovered the problem. The following I didn't seem germane at the time.

The day previous to my problems, I reset my system to original, and installed the 1.0.5 update Then I re-rooted, using Ropor's AMR. Every thing was lovely til I was forced to turn the device off because of frozen frames. When I turned it on, it went into a boot loop, and I haven't been able to do any thing with it since. Impatient me, I started doing all this without checking my battery life.

[Ripplinger]

One last thought after I had a problem with my 350 yesterday. I edited a book removing tables that didn't display correctly and converted them to plain text. But after that the book wouldn't load, the reader was simply stuck in the loading stage and frozen. Triple checked the book, and in Sigil ran the 2 checks and both came out perfect with no errors, so I tried something else.

I'm not sure if the file structure is similar on the T1s, but you might try this if you have similar files. Make copies of your files before making any changes just in case. I opened up the cacheExt.xml and media.xml files and deleted all references to the problem book. One of the files had a LOT of lines from all the bookmarks I was enabling and then disabling while reading, since I was also cleaning up the text somewhat as I read. On the 350, these 2 files are in READER\database\cache\.

Once that was done, I restarted the reader and the book loaded perfectly. I find it hard to believe that you're the only one who's ever managed to brick a Sony and there has to be a way to recover from it.

I'd even try deleting the entire file contents where the info is stored and let the reader re-create them, just be sure you copy the files intact elsewhere first.

[Teknikal]

Originally Posted by Rizla

That's kinda scary seeing as how it gets used so much. Is there a history of the power button breaking with this device?

It's actually the little reset switch I mean you know the small hole to pin reset in case of a crash not the actual power button, I didn't have any problems getting the reader replaced but it did stump me for a while I must have pressed it a thousand times and got no reaction at all.

I was tempted to open that one as well and try yanking the battery but I knew it was still under warranty so I didn't. It has given me a lot of pause in buying devices without removable batteries now I never liked them but now I just don't trust any devices that don't have them.