Greetings! Really need help. For the past two days, I've been trying to re-root my Sony PRS-T1 after initially bricking the device on my initial root with roupor's AMR. The device was able to recover with SD-rescue method, but I haven't been able to re-root since then. Every time I try to root the device with rupor's AMR, the opening book screen would stop loading once it reaches the right right side. After manually resetting the readerwith the reset button, it would revert back to stock settings without rooted capabilities. I also tried flashing the reader with restore-set provided by Boruda. It caused an error afterwards stating that: file creation error- the system cannot find the path specified and invalid drive specification, script did not complete.

I had a similar issue after almost bricking (you wouldn't want to know...) and sd recovery - safe for the fact that after re-rooting with rupor's minimal the reader would freeze at the opening book screen time and again and only sd recovery was able to make it run again.

However, I did sd revovery and hard reset/factory reinitialization. Afterwards I still noticed that curiously some traces of the rooting procedure. Most notably the debug option would still pop up in the top bar whenever I connect my reader to my pc. So I did some sd recoveries and some hard resets and ran all the disable flashes. The traces disappeared, but rerooting still resulted in freezes.

In the end I rooted with boroda's minimal root, which worked as far as I can tell.

And another question (I post this here because it is kind of related to my rerooting problem):
Does the rupor-enable-asec package work on a system rooted with boroda's minimal root?
I could flash it on my reader and the reader is still working, but moving apps2sd in the android application manager does not work.

Recovery packages you are using do not recover kernel related staff - this is why you see adb icon popping up on the bar and this is the reason why ADB and Apps2SD have different restoration packages.

Apps2SD will work with any firmware (as long as you have enough space on /system to install it), however there is a problem in the Android, which will cause problems after you disconnect you reader from PC.

This problem has been addressed in the up to date version of my firmware and was never incorporated in boroda's (and probably never will as boroda is not keeping his packages up to date any more).

I think I misunderstood things before. I thought that SD-revovery+hard reset would restore pretty much everything to its original state, while the disable-packages you flash via usb only undo certain changes.

I am pretty sure that I did remove all the packages via USB at some point and flashing with your minimal-root still resulted in Opening Book Screen freezes. However. Once I have time, I'll try all disabling/recovery/reset procedures and rerooting with your minimal-root. It definitely seems more advanced. If it still don't work I might cry for help again.

Okay,
I spent quite a few hours with my device and all I achieved was running in circles. I am grateful for any idea about what could be the problem or what could be done. I think my device is not bricked but rather crooked.

Points where I'm stuck:
- I cannot use rupor's root. Whenever I flash it, my reader will freeze in the Opening book screen on every startup, requiring an sd recovery
- with Boroda's root I cannot move apps to sd in spite of using enable-asec.
- some apps (amazon, mantano) won't install and/or run as they are supposed to
- the sd revovery behaves kind of strange, sometimes working, sometimes not (my success rate is much higher when using the "sdcard-rescue.zip" as compared to uboot's "rescue_1.04.zip"). When it does not work, the orange LED at the power button is flashing, but the sd card-LED is not, I am quite sure that means that nothing is happening.
- Moreover after revovery, it never reboots. The mission accomplished sign is that the black opening book bar turns white, making a reset via reset button necessary.

Possible Causes
1) There is a slight chance my firmware was not 1.04 when I first rooted. When I look at the device info now, it says 1.04 and I cannot install sony's firmware because it says the firmware is up to date.
2) Something went terribly wrong when I flashed enable-adb. The main symptom (no longer mounting drives) could be repaired by sd-rescue, but maybe something is still damaged.

For the very patient, an approximate list of my activities in my as of yet inconclusive attempt to brick my device
1. Boug a PRS T1
2. flash rupor's AMR
3. flash rupor's enable-asec
4. messed up by adding a google-account, which lead to apps closing down. I thought before I do a recovery, I try the other stuff, so:
5. Tried to install some apps, parts of which worked. Some apps would not install, although the wiki says the opposite (e.g. amazon kindle app).
6. flashed enable-adb, then something went really wrong:
7. FIRST BIG PROBLEM: The reader did not mount/recognize any SD-card ("internal" or external) anymore, I couldn't mount them with my notebook via usb.
8. I tried sd-card rescue for a couple of times until it worked. SD-cards were mounted again
9. I did factory initialization
10. I wondered that adb would still pop up (thanks for explaining this)
11. I tried flashing rupor-amr again. NEXT PROBLEM: Whenever I flash with rupor-amr, the reader will not get past the "opening book"-screen. The black bar will fill up and then nothing happens OR the black bar will fill up, freeze for 10 s and then the reader reboots. All I can do at that stage is sd card recovery
12. I flashed both rupor-disable-all and disable-adb
13. I flashed boroda's minimal and it worked okay
14. I tried installing some apps. Some would work (google mail), some would not (amazon)
15. I flashed rupor-enable-asec over boroda's minimal, but moving apps to sd still would not work.
16. After freeing 28 MB I could install mantano reader (my main goal), but it only started once and then never again.
17. I flashed boroda's removal package
18-99. I moved in circles for quite a few times with rooting, recovering, swearing and so on, but I always get stuck at the points named on top.
57. At one point I tried installing the sony firmware. Because the sony installer didn't do anything by itself, I tried it according to the "update your firmware in linux" howto and copied the unzipped update-package onto the READER-partition. But when I tried rebooting in recovery mode, the black bar instantly turned white again and there was no apparant effect.

I have a similar, if not the same problem. I can't re-root my device. Now I'm trying the old SD Card Rescue by porkupan, because the new uboot SD Rescue won't start. However, after more than 1 hour, the Power Button still flashes, and the SD Slot's light keeps blinking like crazy while the "Opening Book..." progress bar has turned white and doesn't change anymore. Does this mean the recovery process is in an infinite loop?