Mobileread
PRS-T1 1.04 sd recovery
#1  uboot 05-13-2012, 04:17 PM
Hi folks,

I modified porkupan's old sd recovery package such that it restores to stock firmware 1.04.

IT IS NOT APPLICABLE FOR ANY OTHER FIRMWARE VERSION AS THE KERNEL IS ASSUMED TO BE 1.04 COMPATIBLE

Kernel / initial ramdisk / boot area / recovery kernel / root fs are untouched by this package!

BE SURE TO BACKUP YOUR FILES ON THE READER!

At the moment there exist two packages.

To apply any of the rescue packages you need to unzip the file to the root of a micro sd card and follow the steps in the wiki.

1.) Charge battery to 100% or you may brick your reader on power failure!!!
2.) Power off the reader (keep power pressed until it asks to shutdown and press yes) if reader is frozen, press RESET button to power it off.
3.) Press HOME and MENU simultaneously, keep it pressed while powering on the reader and wait until the progress bar has reached 100%
4.) Now you can release HOME and MENU (this is crucial, don't release earlier!)
5.) Now it will take up to 20min for the rescue process to finish
6.) Reader should reboot automatically, if not - assure that the LED for the micro sd slot does not blink anymore and press RESET. Release and power on the reader.
7.) Reader should now ask for initial settings. Also there should be a file on the internal sd named diag.log, that tells if rescue did complete.


Package 1
The package does

1.) format reader partition (=internal sd card, mmcblk2p4)
2.) restore data partition from porkupans recovery set
3.) restore 1.04 system partition from porkupans recovery set

This package has been reported to work.

Download: sdrescue_1.04_porkupan.7z (72.332.505 Bytes)


--------------------------------------------------------------------------

Package 2
This package is supposed to

1.) format reader partition (=internal sd card, mmcblk2p4)
2.) format data partition mmcblk2p9 such that it get's re-initialized on next boot
3.) restore 1.04 system partition on mmcblk2p10 with stock files, but reformated file system to have more inodes which is handy for rooting the device later on (busybox creates lots of symlinks which consume an inode each)

Download: rescue_1.04.zip

There are reports of the reader being unable to store settings with this packages and asking for initial settings on every boot. I don't know why because the formating of the data partition is done exactly like factory reset would do.

Anyways - there are also reports that this package works. So, if you try the 2nd package, please report back to me if it works!
Reply 

#2  simongee 05-14-2012, 07:53 AM
hey uboot, i plan to go back to stock 1.04 before updating my rupor root-package. I always do it, although i read rupor posting that its not necessary.
Anyway, what is the difference between your package and the "Rescue Set 1.0.04.12210" done by boroda/porkupan from this thread:

http://www.the-ebook.org/forum/viewtopic.php?t=21458

I always used those packages, also back then for 1.03
Reply 

#3  uboot 05-14-2012, 12:42 PM
The restore sets you mentioned are safer to apply


SD rescue is only necessary when all other attemts fail, for instance when the reader won't boot up (e.g. showing rotating arrows forever, etc.) such that you cannot simply connect to the computer and appy restore set.

Also, SD rescue formats data and reader partition to assure that everything is complete re-initialized.

The restore sets won't do that...


My hope is, that the new recue set will fix issues like reader not shutting down anymore...
Reply 

#4  networm 05-14-2012, 09:39 PM
hi,uboot
My T1 can't boot up now,it stop in"opening book"screen and the progress bar don't move .Does this package fit for this one.BTW,I can login with the recovery mode.How can I do for this?Help!
Reply 

#5  uboot 05-15-2012, 06:11 AM
give me more details please, what did you do with you reader such that it doesn't boot up?

if you can get into recovery console, than the rescue package can be applied.

but you can also try to format your data partition and reader partition manually from recovery console and see if that helps.

unless you didn't mess up system partition earlier, of course

Code
mkfs.ext4 -L data -m 0 -j /dev/mmcblk2p9
mkdosfs -n READER -F 32 /dev/mmcblk2p4
Reply 

#6  wsantos 06-05-2012, 01:30 PM
Hi guys,
My PRS-T1 was frozen and I tryed to use 1.04 sd recovery, but I don't know
why it doesn't work.
I bought my device about 1 mounth ago and a week ago I rooted it with minimal root set (http://translate.google.com/translate?hl=en&rurl=translate.google.com&sl=ru&u= http://www.the-ebook.org/forum/viewtopic.php%3Ft%3D21458).
It was working very well and how I am very curious I began install some app.
After that, I tried to enable Adhoc WiFi on it (Getting the T1 to recognize ad-hoc networks, e.g. mobile hotspots). The process is on wiki and http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/. Unfortunately, it happened a problem and in the process I lost 2 files (\system\bin\"racoon" and "ppd"), because I don't know why after I moved the file wpa_supplicant from there to SDCARD to replace to another new file I couldn't do this without move that 2 files (there is not free space).
So, in the end after I shout down my device it frozen (try opening book, but it canĀ“t).
I tried to recovery by your 1.04 sd recovery (I made a copy to micro SD OF "OS Firmware"). The yellow lith worked one day and didn't stop, just after I pushed reset). Now I don't know what can I do, because when I conect it in my computer it show just drive I:, J: and K: and I don't have acess to them.
Can I do anything else before to send to exchange (I don't know if Sony will be exchange, because I thing my warranty is broken now).

http://cdn0.4dots.com/i/smiliesadd1/help.gif

Quote uboot
give me more details please, what did you do with you reader such that it doesn't boot up?

if you can get into recovery console, than the rescue package can be applied.

but you can also try to format your data partition and reader partition manually from recovery console and see if that helps.

unless you didn't mess up system partition earlier, of course

Code
mkfs.ext4 -L data -m 0 -j /dev/mmcblk2p9
mkdosfs -n READER -F 32 /dev/mmcblk2p4
http://cdn0.4dots.com/i/smiliesadd1/help.gif
Reply 

#7  +Kardboard+ 06-11-2012, 07:08 PM
Hi uboot, can you confirm the proper size of update.img? The wiki says 314.6 MB, but I've downloaded it at least three times and it only extracts out to exactly 300 MB. Tried to download on different computers too.
Reply 

#8  uboot 06-12-2012, 04:53 PM
I finally found time to re-check everything and re-uploaded the file.

The proper size of update.img is 314.572.800 Bytes.

And - more important - the file system of update.img somehow was corrupted, the files responsible for flashing the reader were not corrupted at last, but maybe this was the cause for the sd recovery not working... I recreated it and ran fsck on it, should be ok now.
Reply 

#9  komugi 06-13-2012, 09:50 PM
I've done this a few times, but it never reboots by itself. When I do force a reboot, it brings me to initialization screen. But every time I shutdown, and restart it, it returns to initialization/configuration. Any reason for this?
Reply 

#10  uboot 06-14-2012, 05:00 AM
missing reboot after sd recovery is normal. that was the case with the old image too.

but is there a log file on sd card after sd recovery? it should contain something like "sd recovery finished".

also: have you removed sd card after sd recovery?

and: what do android logs say after initialisation?
Reply 

  Next »  Last »  (1/8)
Today's Posts | Search this Thread | Login | Register