PRS-T1 sd-rescue vs restore flash: which more complete?

[camperbc]

Hi Uboot,

I have read your post slowly, top to bottom at least three times, but I must confess that I have NO idea what to do with this info. As I have said in the past, I am VERY new to this stuff, and the above post looks to me to almost be written in a foreign language. The only way I would be able to manage is if I was guided along in little baby steps. But it appears to me that you believe this method just may indeed fix my reader woes?

Now, if only I knew where to begin!

Glen

[flyingdog]

uboot, guys, I am still struggling with my device with no success and since I cannot make the "OS Firmware" recovery working, I probably miss something... do you have a recovery partition dump available for me to look into and understand what I am doing wrong?

[uboot]

@camperbc: I'm lost with what the current state of your reader is.... is it rooted? did you manage to get adb access? did you manage to get log files?

Which recovery / root / whatever flash packages did you use exactly and in which order? At which point did you apply Sony update?

I just upgraded my reader to latest firmware. At first I unrooted the device by flashing the recovery set for 1.0.03 matching the current firmware, then I updated with sony updater to 1.0.04, then I re-rooted the device. No probs so far and I also can shut down properly.

So - if all what has been suggested to you didn't help - I need more info from you what exactly you did.

@Flying dog: what exactly is wrong with your device? Are you able to connect via serial console? https://www.mobileread.com/forums/sho...2&postcount=34

[camperbc]

Hi Uboot,

No, my reader is not currently rooted. I tried again yesterday (minimal root) but it froze at "opening book". No adb access/no log files. I have tried the SDcard rescue, hard reset, restore set, adb package, according to your (and others) explicit instructions, again and again in various sequences, all to no avail. I had applied the latest Sony firmware update after the device had been rooted rooted. (which I think may have been the cause of all this trouble in the first place) So, currently the only wait to shut down the device is to use the reset button.

The ridiculously fast battery drain issue (full to empty in just a few short hours) seems to be fixed! I followed someone's advice of fully draining it, then charging with the wall charger, over 3 or 4 cycles, and it actually seems to have worked! It has been 12 hours, and it still reads as full, whereas it would have been completely discharged after this length of time, prior to performing the multiple full drain/full charge procedure.

So, only two issues remain. Firstly, the inability to re-root, as it gets stuck at "opening book", and secondly, the inability to shut the device down in the normal fashion.

It may be worth noting that, even after all of the above procedures, my reader is still showing that the latest firmware version is installed. I think you were under the impression that it should have reverted back to the original firmware, after the SDcard rescue?

If I could just somehow get the reader rooted again, I could likely live with not being able to shut it down properly; (I could always use the reset button if not using the reader for a long while) but no matter what I do at this point, I cannot root it again, without having the device freeze up at "opening reader".

Thanks,
Glen

[uboot]

Ok, on your reader partitition (the READER drive which is exposed via usb) should reside a script.log file that logged the rooting process - could you please post it?


The sd recovery package does not restore 1.0.04 but an older firmware.

So the best way to go now is applying the 1.0.04 restore set from http://projects.mobileread.com/reade...lash_packages/

If you want, modify the files according to my previous post, that is: edit the do_update.sh file and the checksum file and remove mmcblk2p9.img

After flashing, look for the script.log file for errors.

If all went fine, try the regular root set, not the minimal one.

[camperbc]

Uboot, I have nothing under the reader drive that says "script.log". All I have under "READER (E is three folders; namely "Books", "Sony_Reader" and "tmp". Under "Sony_Reader" is a folder named "database", and in it is this:

cache
sync
.nomedia
audios
books
images
notepads

Under the "tmp" folder is this:

checksums
do_update.sh
nboote.bin
ramdisk-adb.uimg
rescue.updater

That's all I've got. Seems there should be more!

Glen

[uboot]

No, that's ok.

Remove micro sd card.

Now, please go to Settings -> Initialisation -> Restore Defaults.

Then: reapply Sony Update. If it says, that you have latest firmware, don't worry.

Then: apply restore set. (not sd recovery! the regular one!)

As a last step: apply minimal root set.

Now you should have a script.log file!

[camperbc]

Hi Uboot,

I tried the above, exactly as per your instructions. But as before, after applying the restore set, the reader freezes at "opening book". The only way for me to ever get past the "opening book" freeze (that I have ever found) is to apply the SD recovery.

So likewise, when I go to do the minimal root again, it too freezes at "opening book".

Glen

[uboot]

Ok, I see that we need a sd root package....

Flying dog would also be happy I guess...

Let's when I find time for that. This weekend is allready booked, though.

But flyingdog maybe is able to create one.

Just take the present sd recovery image and loop mount it.

There is a home folder containing 2p9 (data) and 2p10 (system) partition.

Loop-mount the latter and add super user apk to app folder and su binary to bin folder and do chmod 06755 on su binary. Look at do_update.sh from root set for reference. Also add an app launcher apk like ADW or Zeam launcher and delete defaults from packages.xml in data partition image as done in do_update.sh such that you will be able to select app launcher as new home screen on next start.

[camperbc]

Originally Posted by uboot

Ok, I see that we need a sd root package....

Flying dog would also be happy I guess...

Let's when I find time for that. This weekend is allready booked, though.

But flyingdog maybe is able to create one.

Just take the present sd recovery image and loop mount it.

There is a home folder containing 2p9 (data) and 2p10 (system) partition.

Loop-mount the latter and add super user apk to app folder and su binary to bin folder and do chmod 06755 on su binary. Look at do_update.sh from root set for reference. Also add an app launcher apk like ADW or Zeam launcher and delete defaults from packages.xml in data partition image as done in do_update.sh such that you will be able to select app launcher as new home screen on next start.

Hi Uboot,

This SD root package idea of yours sounds very interesting; seems like you think this may be what will solve my troubles. Of course, it may as well have been written in Cantonese, as I don't speak nor understand the lingo, but looking forward to seeing if you can arrange for something else for me to try to get my reader back to normal.

In the meantime, I suppose I've got nothing to lose if I try Joan's idea of the multiple "full discharge/full recharge" (approx 8 cycles) procedure that not only seems to have solved her battery's fast drain issue, but also has now allowed her reader to shut down properly! If it worked for her, who's to say it won't work for me also!

Thanks,
Glen