PRS-T1 undo changes

[rubentje1991]

Hello all;
[ if you want to skip the reading, my question itself is at the ending ]
About a week ago, I rooted and customized my PRS-T1...

I'm satisfied with everything the reader can accomplish (more than I'd have thought is possible)...
=> but for several days now, my reader app is behaving bad; it's OK for normal reading, but when I close it, I get an error (stopped unexpectedly, try again or something like that - and then force close button);
the same happens when I go (in the reader app) to Options >> More >> Settings (or preferences in English, I don't know): same error;

I thought, something wrong with the permissions (had to do a reset a while before that, installed fixPermissions app - but that only does data-apps, no system-apps)...
Then I tried the fix_permissions script, running via the terminal emulator on the device itself (no adb installed)... as response I get: "shift: can't shift that many";
so, opened the script on the pc, saw an option "-f" for only specifying the apk; I tried to find the apk of the built-in reader app, if I'm correct, it's at /system/app/EbookReader.apk (reinstalling of that doesn't work ); so I run: "fix_permissions -f /system/app/EbookReader.apk", but that doesn't help neither (anymore? I think it once worked, but after cold boot, was all over again and running fix_permissions helped nothing)....

Now I'm thinking of getting started "fresh" again (a little more experienced now)...
=> I've seen some "initialization" entry in the settings of the reader; one option to format the memory, and an option to restore the defaults....
I also saw the "factory reset" entry on the wiki (which is very helpful)...

But I don't know what having to do now;
=> I have an extended partition on my microSD, with apps linked to it;

Just format the memory, restore the defaults and a factory reset: is that enough to start fresh, or do I first have to undo the rooting, or copying some image file again? [yes, everything should be formatted, I'm not going to loose the files ]

Thanks in advance!

[rubentje1991]

Well, it would be possible to install the adapted EbookReader.apk (as mentioned in the other thread)... but as I see, there are still some little bugs in it....

So, it would be very useful if someone has some advice on this problem - of how to do a full reset with a rooted and adjusted device.....
=> because maybe someone has experience with it, if that's not the case - I'm going to try the factory reset and see what happens then

[rubentje1991]

Or other possibility:
someone who can explain me how to reinstall the EbookReader.apk (without using adb)?

But an answer to the previous posts is still preferred (to do a clean start - and I've read the wiki several times => maybe I didn't understand some part?)

[rubentje1991]

OK, I'm going to format the memory, and reset to factory settings - and see what happens

[rubentje1991]

I get more and more admiration for the root-method.....

So, I formatted the SD card and the internal reader-memory;
then I did a factory reset, and started playing with the device - but the root was still active (me happy )
Why happy?: my reader app is repaired (no stupid errors anymore), and my other apps are all still available (even my custom installed apps)
=> after 2 cold boots, everything still going smooth!
(only the contacts-app is always gone on each cold boot, installing again takes about 5 seconds - but that's the only thing that maybe can change in the future -- if I find lots of time somewhere, I maybe can build a new Android app myself, but..... that will have to wait))

Complete time used for formatting the memory and doing a factory reset: <5 minutes
(and my Adobe DRM is still active on the device)

Just for your information

[uboot]

maybe your filesystem got corrupted. this can happen when the reader crashes or is reset...

[j0534ng31]

We are going to see this behaviour with increased frequency, I suppose!

[uboot]

But what is it like with other android devices? Do they fsck before mounting? And how about the old embedded Linux based PRS readers?

[j0534ng31]

Originally Posted by uboot

But what is it like with other android devices? Do they fsck before mounting? And how about the old embedded Linux based PRS readers?

Have you seen my PM?

About other android... I don't know.

CyanogenMod ROMs checks it at boot... But I haven't had any other PRS before this T1

Anyway, this have to be done... somehow

[rubentje1991]

Well, after doing some testing, I think Calibre is the cause (when you use it in the wrong way)....
=> I saw that when you just closed Calibre, without ejecting the device, and then unmounted the device in Linux, it had this behavior. I think it caused some problem in the book.db database file....
Everytime I did it in the "wrong" way, my reader started working "weird" (with that force closing message when closing the reader-app, and when going into the settings of the reader-app => to see e.g. details / more info about the book)

Resetting works (beautifully), and now, when properly ejecting the reader first from Calibre, and then unmounting it in my OS, I don't have any problem at all anymore;
so probably just my fault (not knowing how to use Calibre )
I learned something,
but yes, sometimes the reader should do a fsck (every 50 boots at least or so?) to check the integrity of the filesystem; else it will be giving problems in the future! (or they would have implemented some other way of assuring the integrity of the filesystem - but I doubt about that )