PRS-T1 Need help! Having trouble re-rooting my Sony PRS-T1

[lovinghart]

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.

Here's the script log I got after the rooting process:

Would really appreciate suggestions on how I can root again thanks!

Starting ./update.sh
./tmp/do_update.sh: Checksum e74c4ad923c936e2a404b51a783e14c7 correct
./tmp/rescue.updater: Checksum 2e8f803dbd819b2b999b2e34539b84ce correct
./updates/data/app/EBookDownloader.apk: Checksum 3d216cdf6a1c227eb84c23b2d57b3c25 correct
./updates/data/app/tc_rc6.apk: Checksum 5f01edc2a749640b27ea8e8da1c8ce50 correct
./updates/system/app/EbookAudio.apk: Checksum 710744d67639991a4ae46ecc27109d70 correct
./updates/system/app/EbookAudio.odex: Checksum 3368c9ea0c9afff0249a2e05218e01a7 correct
./updates/system/app/EbookContentManager.apk: Checksum 9caa0405f82f840afc752ffba281c019 correct
./updates/system/app/EbookContentManager.odex: Checksum 29b4d27ee6d00f8b49cb5aa5a60570a8 correct
./updates/system/app/EbookDictionary.apk: Checksum ef3b1567f13304362552208a2e2c4ed4 correct
./updates/system/app/EbookDictionary.odex: Checksum 97ed6c3e751b95ccc99f06016bd0fd20 correct
./updates/system/app/EbookHome.apk: Checksum bc524445ecff5f4e23be606d4d178b23 correct
./updates/system/app/EbookHome.odex: Checksum 5e0915ef53174ea17b09fbc5636b4c65 correct
./updates/system/app/EbookLatinIME4Ebook.apk: Checksum 964db312fdcbb8eb81f3fa37ee6857cb correct
./updates/system/app/EbookLatinIME4Ebook.odex: Checksum 0bba43415e06842a58805354aacdba12 correct
./updates/system/app/EbookNetworkApplications.apk: Checksum 4909f46fcedbc029b4ea154dcc37d2c9 correct
./updates/system/app/EbookNetworkApplications.odex: Checksum 9db28070d2e6c558c2d943506be9ac3b correct
./updates/system/app/EbookNetworkManagerSettings.apk: Checksum bb3c38d8ccd9f8cd1e0c5bf2147fd689 correct
./updates/system/app/EbookNetworkManagerSettings.odex: Checksum 87b3451c309165db8e7c77b011225649 correct
./updates/system/app/EbookNote.apk: Checksum 14125c74f1ffcee9ca85895cae8e4f90 correct
./updates/system/app/EbookNote.odex: Checksum a0e820dfd4ff38827fe58000f5291176 correct
./updates/system/app/EbookPicture.apk: Checksum 8d3f8c0529a336d3e7e4f61619de4990 correct
./updates/system/app/EbookPicture.odex: Checksum fcdd4a8151fb742b3528953584248094 correct
./updates/system/app/EbookReader.apk: Checksum 6239c033d4ffa7beaa77d5c4ab400c28 correct
./updates/system/app/EbookReader.odex: Checksum a8bed12524b00819bc1da7cfaca32d74 correct
./updates/system/app/EbookSetting.apk: Checksum c255ed465eb2d9fde427a918bc2eec59 correct
./updates/system/app/EbookSetting.odex: Checksum 3fc620ee95c4648c50e4df49f66f0788 correct
./updates/system/app/EbookStoreBrowser.apk: Checksum 51d20bd81835a60d843e320e76f6edcb correct
./updates/system/app/EbookStoreBrowser.odex: Checksum b1e72ae1850b959f2b89ba613b4a10bf correct
./updates/system/app/EbookWebBrowser.apk: Checksum f5f7ef94bda674d3e521ed7d4d6c7be9 correct
./updates/system/app/EbookWebBrowser.odex: Checksum 9bb429372ba1f98706d981cddb42bf93 correct
./updates/system/app/PackageInstaller.apk: Checksum 41ba56b611d678568ecb2de03b7bcf16 correct
./updates/system/app/Settings.apk: Checksum 8af84780cf4346a90592eff0c951b42b correct
./updates/system/app/Settings.odex: Checksum 3760285cbd5d4d79bd2abd737f5c9c9d correct
./updates/system/app/Superuser.apk: Checksum 836bd6f86753386ffe192786aa3db78f correct
./updates/system/bin/busybox: Checksum 7cbc8f10edb64afc52eb01beca6cdcd3 correct
./updates/system/bin/capturescr: Checksum d8d98f2e663b72f9d3e98c8b851c438c correct
./updates/system/bin/dexopt-wrapper: Checksum 51d91938b508227e1bb2504de5c53826 correct
./updates/system/bin/fix_permissions: Checksum 1f3614573c7ad938c6080c86691feaeb correct
./updates/system/bin/sqlite3: Checksum a22fba3851d1136bdf82bed4d9fed284 correct
./updates/system/bin/su: Checksum d1a9de9724c662a50a9a128e48b1fb37 correct
./updates/system/framework/framework-res.apk: Checksum afb700b964fc437674caf99a8c6d362b correct
./updates/system/framework/framework.jar: Checksum a71a1c7da26d73b649843b23e83242be correct
./updates/system/framework/framework.odex: Checksum f36851e1cb30c5f4a154656832ac3a91 correct
./updates/system/framework/services.jar: Checksum 5818dab2b7b9a58e533231ab2414f0bf correct
./updates/system/framework/services.odex: Checksum 7a1d5194876278864f2507712aae0c95 correct
./updates/system/lib/libbbebDictionary.so: Checksum 58cdeffbad1de20eb3c12ef8ddf61c4c correct
./updates/system/lib/libEbookContentManagerNative.so: Checksum f231f25147c933d4adc593732a377576 correct
./updates/system/lib/libfsk.so: Checksum 0e562fe4f44c279a799f8e2808d5184e correct
./updates/system/lib/libicudata.so: Checksum 59aec1ef2c1e58f72cfab5f41b93172e correct
./updates/system/lib/libreadercore-jg.so: Checksum 6fb70a6375820b254f1893e27b973db1 correct
./updates/system/lib/libreadercore.so: Checksum c86fe9712535d10ab887f4c5f4ab2a47 correct
./updates/system/lib/libsqlite.so: Checksum 972f9ab73d6169639c5924ec8198853e correct
./updates/system/lib/libttfdisp.so: Checksum a699845286e2e855eab6240bd5aa2069 correct
./updates/system/usr/share/zoneinfo/zoneinfo.dat: Checksum d70de447cb0d2a70a6d355937f585516 correct
./updates/system/usr/share/zoneinfo/zoneinfo.idx: Checksum 5976dccd2db05e0e70c985cbad0e8722 correct
./updates/system/usr/share/zoneinfo/zoneinfo.version: Checksum b5da3a9f6995e32b5461bfa39fdba5b0 correct
Update script found
---- Starting update script ----
Starting /tmp/do_update.sh Sat May 5 17:53:08 UTC 2012
Cleaning SETTINGS
Free space. Removing EbookDemo
Free space. Removing EbookDemoService
Free space. Removing LiveWallpapers
Free space. Removing LiveWallpapersPicker
Free space. Removing MagicSmokeWallpapers
Free space. Removing VisualizationWallpapers
Free space. Removing BBEB leftovers
Regenerating sysconf_db
Updating /data
Removing old system packages
rm -f /tmp/system/app/EbookAudio.odex /tmp/system/app/EbookContentManager.odex /tmp/system/app/EbookDictionary.odex /tmp/system/app/EbookHome.odex /tmp/system/app/EbookLatinIME4Ebook.odex /tmp/system/app/EbookNetworkApplications.odex /tmp/system/app/EbookNetworkManagerSettings.odex /tmp/system/app/EbookNote.odex /tmp/system/app/EbookPicture.odex /tmp/system/app/EbookReader.odex /tmp/system/app/EbookSetting.odex /tmp/system/app/EbookStoreBrowser.odex /tmp/system/app/EbookWebBrowser.odex /tmp/system/app/PackageInstaller.odex /tmp/system/app/Settings.odex /tmp/system/app/Superuser.odex
rm -f /tmp/system/framework/framework.odex /tmp/system/framework/services.odex
Updating /system
Changing system files modes
Getting rid of preferred activities in packages.xml
Cleaning system signatures
Cleaning VM cache
Setting SuperUser
Done /tmp/do_update.sh Sat May 5 17:53:47 UTC 2012
---- Done update script ----
clean_exit

[filmo]

This should be discussed in Sony Reader sub form Sony Reader Dev Corner. Not that I care but you might get faster answer there.

https://www.mobileread.com/forums/forumdisplay.php?f=141

[dreams]

I've moved this thread to the Sony Reader Dev Corner.

Welcome to MobileRead and I hope you are able to get this sorted out.

dreams/moderator

[uboot]

have you removed the external sd card with the recovery image before rooting?

also, factory initialisation / format internal sdcard may be useful after sd recovery to ensure everything is restored to factory default.

so I'd redo SD recovery, remove SD card and format / factory initialize.

AND - important! - install latest sony 1.04 firmware after sd recovery!!!

[rupor]

Script looks absolutely normal - I think uboot is right. You need to fully restore your device, make sure you have latest firmware and install root again.

[Cordula]

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.

[Cordula]

BTW: Yes, I did remove the SD card after recovery and before rooting.

[Cordula]

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.

[rupor]

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).

[Cordula]

Thanks for the explanation!

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.

[Cordula]

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.

[rupor]

I think #1 is far more likely. If there is even slight chance of wrong version of Sony firmware - nothing will work...

[bookp]

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?

[sohrab1414]

hi guy's
my reader is sony PRS-T1 and a bricked device
i need to uboot's SD rescue package for 1.04 firmware and not download from site
please uploded this file to download and rescue my reader. tanx