01-25-2013, 05:18 AM | #61 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
What do you mean by Diag partition?
I'm still at firmware 1.04, so I wonder if this could be related to a change in the kernel with 1.05. Did you have these dictionary / suspend problems with 1.04, too? Do you have these problems with micro sd removed, too? Otherwise, the micro sd might be interfering with suspend.... My reader sometimes does not suspend properly after charging -> The battery will drain completely within 24h. As a workaround, I always shutdown/restart the reader after unplugging the charger. It might also be that your hardware has a fault such that suspend does not work properly. Setting (only contains PC reader software) and recovery partition (only plays a role in when booting into recovery mode) have nothing to do with suspend functionality. I will check my logs for specific suspend errors when I am back home... |
01-25-2013, 05:31 AM | #62 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
The Diag partition is the second partition following the Recovery one. It has a 10Mb size, cramfs file system, on linux its reference is /dev/sdb2 and I think it must be the mmcblk2p2.img partition.
I had problems with the dictionary and sleep before I upgraded to the latest firmware. I do not have an sd card in my Reader. I only put one to flash restore sets or backup/restore partitions. I usually charge my Reader through my computer. I plug it to my computer practically every day. But the problem is not related to this. I've been turning it off and on again, then using it normally. When I put on sleep, the problems start, whether or not I had connected to the PC. Yes, I think it is probably a hardware fault. Do you think it is worth sending to Sony for repairs or will it cost too much? |
Advert | |
|
01-25-2013, 11:23 AM | #63 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
A last check I would do is comparing dumps of the raw data block. It will differ in some regions, but at least the kernels should be equal.
In this thread you'll find info about the offsets: https://www.mobileread.com/forums/sho....php?p=2207783 |
01-25-2013, 03:55 PM | #64 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
Thanks for the info. I'm quite busy at the moment. I think I will try that early next week.
Any clue how to erase completely the Diag partition (mmcblk2p2) to try to dd the new one (safely) in it's place? |
01-26-2013, 03:55 AM | #65 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
maybe the diag partition is used during recovery mode and it might work in normal mode via adb shell or android terminal...
|
Advert | |
|
01-28-2013, 07:56 AM | #66 | |
Addict
Posts: 283
Karma: 138550
Join Date: Mar 2009
Device: Gen3(†); PB302(↓); PRS-350; T1; voyage
|
Quote:
@entodays: Are/were you using this modified reader? |
|
01-28-2013, 08:07 AM | #67 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
I had installed rupor's AMR which includes a modified Reader app. I'm not sure if it the same you're talking about, and I never installed other modified Reader apps.
|
01-29-2013, 11:37 AM | #68 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
So I tried to follow the procedure in the link in post #63, with one modification. I do not intend to modify init so I simply extracted the rootfs without uboot headers of the good PRS-T1, and tried to copy it to the other one.
What I did exactly: 1. Instead of extracting the rootfs from /dev/mmcblk I extracted from a Full backup file for both the good and the faulty PRST1s. The rootfs.img was 1Mb size. I tried Code:
diff faultyrootfs.img goodrootfs.img 2. I created a newrootfs from the good PRS-T1 with the makeimage command as per instructions. 3. I ran Code:
dd if=../newrootfs.img of=/dev/sdb bs=1 seek=5242880 4. Resetted the Reader… got stuck at opening book with a blank progress bar which didn't advance. 5. I restored the backup I had done of the faulty reader (after the problem began) with Code:
dd if=Backup.bin of=/dev/sdb P.S. I'm on Ubuntu and the Reader internal sdcard is /dev/sdb so I replaced /dev/mmcblk2 with /dev/sdb. Last edited by entodoays; 01-30-2013 at 03:53 PM. Reason: Clarification |
01-30-2013, 03:48 PM | #69 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
So you say that you finally flashed a backup of the full starting block of the good reader onto the bad one?
|
01-30-2013, 03:52 PM | #70 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
No. I copied (dd) the backup of the faulty reader back to the faulty reader, because the one I had copied from the new didn't work.
|
01-31-2013, 03:38 PM | #71 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
Problem Solved!
I have some news. The short story: Erased partition table; restored backup of faulty reader; restored mmcblk2p1,2,6,7,8,9,10 of the good Reader to the old one. Now everything seems to be working fine after leaving on sleep for 7 hours and using it to read for 1 hour at three different times. Used the browser too without any problems.
Will test for a longer period of time without doing further changes. EDIT I've been using heavily (several hours a day) my previously faulty PRS-T1 and can confirm that the problem is solved (hoping it does not come back again). I read from several books in different languages, changing dictionaries every time, added annotations, browsed several websites, downloaded ebooks and a couple of wallpapers without a single problem. I read somewhere on the Sony forums that one used said that repartitioning solved his dictionary problems. I'm the second user who's reporting it as well. I didn't change the partition sizes but rewritten the partition table of the unit and this seems to have resolved the problem, wherever it was. I will post a detailed step-by-step procedure for the benefit of others having the same problem. Last edited by entodoays; 02-02-2013 at 10:31 AM. Reason: Added more info |
02-02-2013, 10:29 AM | #72 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
STEP-BY-STEP PROCEDURE
The idea behind this procedure is to wipe completely the internal drive and copy the partitions from another Reader, except the initial 26 Mb unformatted space that contains unique information for each Reader.
That said, if you do not have access to a PRS-T1 in working order, you may try simply, doing a backup, erase the partition table, restore the backup (doing steps 1 to 5, 11 to 13 and 15). It might work, but I cannot vouch for it since I didn't stop there. WARNING: Do not go through this procedure if you do not understand what you're doing, you may end up bricking your Reader, or worse, format the hard drive of your computer. I take no responsibility if things go wrong! Requirements:
Note: During this procedure, my Reader got somehow disconnected from the computer a couple of times (after step 12 below and after copying the /dev/sdb8 partition). If this happens, simply disconnect the USB cable, press Reset + Power. Press HOME+MENU and power again as before. STEP-BY-STEP PROCEDURE
Last edited by entodoays; 12-21-2013 at 08:21 AM. Reason: Corrections suggested in post 108 of this thread. |
02-07-2013, 09:11 AM | #73 |
Junior Member
Posts: 6
Karma: 10
Join Date: Jan 2013
Device: none
|
@entodoays: Can I used for Japanese version?
|
02-07-2013, 11:04 AM | #74 |
Zealot
Posts: 144
Karma: 706
Join Date: Oct 2011
Device: Sony Reader PRS-T1
|
What do you mean? Do you intend performing this procedure on a Japanese PRS-T1? If you intend copying the partitions from one PRS-T1 to another, I guess that both must have the same version and same firmware.
In hindsight, I think that it is possible that what solved my problem was the creation of a new partition table. So you might try skipping the steps about copying partitions and simply, do a full backup, erase the partition table (the Gparted step), restore the backup just done. This might solve the problem, if your problem has a similar root cause. In any case, if this doesn't help, you may try the full procedure, if you have access to another PRS-T1, same version, same firmware. |
02-15-2013, 10:26 AM | #75 |
Junior Member
Posts: 6
Karma: 10
Join Date: Jan 2013
Device: none
|
@entodoays: My PRS-T1 do not connected with computer. I don't known why?
|
Tags |
amr, hanging, prst1, sony |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PRS-T1 PRS-T1 stuck off and unresponsive...but no serial to return | samadam | Sony Reader | 3 | 06-15-2012 12:13 PM |
PRS-350 Unresponsive Buttons | mer10 | Sony Reader | 9 | 04-05-2012 04:41 PM |
PRS-350 sony prs 350: blank unresponsive screen, blinking orange light | halipleumon | Sony Reader | 5 | 05-30-2011 06:49 AM |
Unresponsive Prs-505 | Reader 101 | Sony Reader | 1 | 09-15-2008 04:19 AM |
Unresponsive | honeybunny | Amazon Kindle | 8 | 07-17-2008 05:18 PM |