MobileRead Forums - View Single Post - PRS-T1 I need help to un-brick it

Speareader · 09-24-2017, 08:44 PM

Let me start with what I did to get to this point:
1. I rooted the device when it had the 1.0.05 firmware
----- did not use it for about a year
----- decided to read some of the books on my sd card
----- installed Sony's application for Windows and saw that new firmware is available. So without even researching, pulled the trigger and installed 1.0.07
----- did not like it and there was no way to root it, and wanted to go back to 1.0.05

2. After a bit of research found out that in case to downgrade the firmware i need to edit the hex values from 1.0.07 to 1.0.03.
3. got the mmcblk2.img, edited the values, put it back and restored it to the device

4. Obviously something got screwed and now I'm stuck with flashing screen whenever I turn on the reader. (Once it stops flashing, gets vertical black line that occurs in different parts of the screen)

NOTE: The reader is not recognized as usb device nor in serial connection
Tried rupor-rescue but I can't get it to be recognized (I am using Linux and Windows).

I also have a backup of the mmcblk2.img and was thinking if there was a way to write a script that can be triggered on boot from the SD Card to restore the working image...

Any help is appreciated!!!

09-24-2017, 08:44 PM	#1
Speareader Junior Member Posts: 2 Karma: 10 Join Date: Sep 2017 Device: prs-t1	I need help to un-brick it Let me start with what I did to get to this point: 1. I rooted the device when it had the 1.0.05 firmware ----- did not use it for about a year ----- decided to read some of the books on my sd card ----- installed Sony's application for Windows and saw that new firmware is available. So without even researching, pulled the trigger and installed 1.0.07 ----- did not like it and there was no way to root it, and wanted to go back to 1.0.05 2. After a bit of research found out that in case to downgrade the firmware i need to edit the hex values from 1.0.07 to 1.0.03. 3. got the mmcblk2.img, edited the values, put it back and restored it to the device 4. Obviously something got screwed and now I'm stuck with flashing screen whenever I turn on the reader. (Once it stops flashing, gets vertical black line that occurs in different parts of the screen) NOTE: The reader is not recognized as usb device nor in serial connection Tried rupor-rescue but I can't get it to be recognized (I am using Linux and Windows). I also have a backup of the mmcblk2.img and was thinking if there was a way to write a script that can be triggered on boot from the SD Card to restore the working image... Any help is appreciated!!!