PRS-T1 Questions about repartitioning

[simongee]

Hey Mobileread!
Long-time lurker, first time poster here...
I want to repartition my internal storage and got a couple of questions, hope u can help me

Before i start, i want to make clear that i read and learned alot about tweaking my T1 thanks to u guys.
So first off a big And another big thanks goes out especially to rupor. LOVE ur work!
Currently im running rupors AMR package with the apps2sd package on top.
The main reason why i want to repartition the internal storage is that i cant move many apps to sd (8gb external sd) with the android-feature and i hate the link2sd crap. Generally im very careful with my gadgets and before i do any changes i make double-sure that i dont make mistakes.
So here it goes:

1. I am not a linux guy. So at first i thought, nah, that repartitioning is not for me, but then i read this in rupors "backup and rescue thread" here: http://www.the-ebook.org/forum/viewtopic.php?t=23354

However, it is possible using commercial software to completely change the size of data and system partitions never typing Linux commands are not entered into the terminal and using the calculator. The whole process takes 5 to 10 minutes and does not require a doctoral degree in yuniksologii and skriptografii. Requires Paragon Partition Manager Pro 11, the common sense and possession of a mouse. In this device is pretty hard to kill ...

I dont speak russian, so i have to follow rupor with the "help" of google-translate... which often gives me headaches btw...
So rupor, if u read this, or somebody else can answer:
Can i use MiniTool Partition Manager or any other free tool to do the job?

2. When repartitioning with a tool, i have to be in recovery mode, right? The easiest way to get there was imo to run the @TestMode tool on the T1 and select "boot to recovery". Maybe im too stupid but i cant start the tool using rupors AMR. Its there, i see it in the android settings, but its not on the page 3, so i cant start it.

3. When repartitioning with a tool, I first shrink the READER partition, then I enlarge the data and system partition as i like, right?

4. Do I have to do a backup first using the method of the thread i mentioned? I dont care about anything on my internal storage, got all books on the sd card. Will the reader still work as before after the job or will the partitions be wiped? Can I install the Sony FW after the job and then re-root? And what about future Sony updates? Will I be able to install them after repartitioning or not?

So thats it i guess, any help is appreciated. I would really like to do it, i just dont feel like i know enough...

[rupor]

1. I used Paragon Partition Manager 11 on Windows XP running in VirtualBox virtual machine. There 3 things to know - do not touch partitions at the beginning (recovery, uboot, e,t,c), you need enough free space on your READER partition and you have to work one partition at a time starting from the biggest one and making sure operation is committed before doing next one (tool allows you to commit multiple operations in sequence or batch mode - do not use it!)

All necessary partitions (but /system) could be done "in-place" with all data intact in about 5 minutes. If you want to change /system (which is not necessary) - it is ext4 - and tool (despite what is declared) cannot handle it properly, so you have to use tar to save data, delete and create partition and restore.

2. Yes - you have to be in recovery mode with my backup and recovery SD card

3. Yes - you reduce READER partition and than move and enlarge next one e.t. c. There is one additional step - enlarging "extended" partition to which (if my memory does not fail me) data and system are children. Unfortunately I did it some time ago and do not remember all the details - but it was not difficult.

4. I did backup first and had to recover once in the middle of procedure because I was trying to do something tool was not capable of doing. So do backup - it takes several minutes and is easy.

[uboot]

do you wanna brick your reader with no way back?

have you read this: https://wiki.mobileread.com/w/index.p...ternal_storage ?

here's what I did: https://www.mobileread.com/forums/sho...3&postcount=48

I guess, partitioning with external tool like paragon over usb connection as described by rupor is possible, but you should pay attention on proper alignment of the partitions.

that's why I used fdisk via recovery console, which enables one to work sector wise.

also you must not mess up the boot area of the device, including the kernel / initrd partitions (mmcblk2p1 and mmcblk2p2). otherwise there will be no way to access the device anymore. there's a guy on the forum who destroyed his reader this way. irreversibly.

read this thread entirely: https://www.mobileread.com/forums/sho...=163137&page=2

[rupor]

All tools I looked at produced after some date do proper partition alignment - in Paragon 11 it is default mode and could be set in options

[uboot]

but which block size does it align to?

on the reader, it should be 64*512 Bytes if I remember correctly...

[rupor]

For all PC hard drives smaller than 2TB default sector size is 512 bytes. Only after disks went over this size manufacturers agreed to switch to 4096 Bytes. Those tools know about it - I did verified it before and after each operation with calculator (tool provides enough information ) resulting numbers where divisible by 64 and some small amount of "unused" space was left before or after each "new" partition if necessary.

I do agree with you however - reading info you pointed is a MUST!

[uboot]

Improper alignment won't break anything.

The deal with alignment and flash memory is, that the partition alignment must match the block size of the flash memory, otherwise write access becomes very slow.

As long as the tool aligns to something divisible by 64, everything should be ok.

[multiprose]

don't try the linux instructions on how to partition. instructions aren't concise or comprehensive. you'd have to read a bunch of different posts in order to find your way, and in the end still probably mess up -.- true story lol.

aside from using the test mode app, you can boot into recovery mode by holding home + menu until the bar reaches the right.

i personally used acronis true image to repartition. back up the entire disk first. this makes it easier as you don't have to work with the limitations of not being able to resize the data partition since its ext3. my memory is blury but i think what i did was delete system and data, created a new blank ext3 partition with size of my choosing and then simply restored the data partition on top of the blank. then restored system to the remaining free space.

[simongee]

Thank you for your answers!

@rupor
I downloaded Paragon Partition Manager 11 Free Edition. Is there any advantage using that tool over MiniTool Partition Manager?

@uboot

do you wanna brick your reader with no way back?

Noo! That’s why i made this thread! And yes, I read all the threads u mentioned and check the wiki on a regular basis. Thanks for setting it up and keeping it nice and tidy btw
As I said, im a very careful type of guy when it comes to modding my stuff, so I ask first… If I get confident enough to do this I also plan on adding a how-to to the wiki, so other non-linux-guys can repartition their device, too…

So here is what I gathered from your posts and what my plan is now, please correct me if I screwed up somewhere:

0.1 delete all apps and stuff from internal.
0.2 do the disable-asec package from rupor to uninstall the app2sd android feature. (won’t need it after repartitioning)
0.3 use boroda’s recovery pack to go back to stock and unroot
0.4 do factory reset to clean up everything
0.5 install latest rupor AMR package

1. go to recovery using the rupors backup and recovery SD card. (copy files to sd card, reboot + holding home + menu until the bar reaches the right)
2. plug in usb, choose NOT to format if windows prompts me , install drivers (gserial.inf)
3. backup the whole internal memory using the tool rupor used in his thread (Roadkil's Disk Image)
4. shrink the READER partition

Now im not sure anymore:
5. enlarge the /data partition (I plan to have it around 500MB). I see no point in enlarging /system.
- rupor and multiprose posted something about /system and /data being connected in some way, or not being resizeable? So I can’t simply enlarge the partition like I would do with a fat32/ntfs partition?

delete system and data, created a new blank ext3 partition with size of my choosing and then simply restored the data partition on top of the blank. then restored system to the remaining free space.

So that’s how to do it? If so, next question comes to my mind. Rupor’s tool backs up everything at once resulting in one image, right? So I can’t restore individual parts of it. So I do it like this:
5.(?) delete /data (and /system partition (I have to delete both?)).
6.(?) make new, bigger /data partition (ext4) (and new /system partition (ext2)) -> according to the picture from rupor i attached... I plan /data to be around 500MB and would not touch /system if I don't have to...
7.(?) restore image created in step 3
8. disconnect usb. remove sd card. reboot. done

[rupor]

Originally Posted by simongee

Thank you for your answers!
@rupor
I downloaded Paragon Partition Manager 11 Free Edition. Is there any advantage using that tool over MiniTool Partition Manager?

I do not know - I simply had Partition Manager 11 (and not the free one) handly at the moment.

[uboot]

the full image won't help you with repartitioning. it's for backup purposes only. additionally, you will have to dump each partition one by one...

don't touch the first 2 partitions (the primary ones)!

you don't have to resize system partition. leave it as it is. app get installed to data partition.

data partition and reader partition do not have to be restored. simply format data to ext4 and reader to fat32. and give them the right labels (READER and data). uppon boot, the reader will re-initialize them.

all other partitions (system, fonts, etc.) are kept untouched. backup them one by one and then restore them one by one.

so the steps are:
1.) backup extended partitions (logical drives, mmcblk2p4...mmcblk10)
2.) delete extended partitions
3.) recreate extended partitions with the first one shrunken by the size you wanna enlarge data partition
4.) restore extended partitions

[rupor]

Paragon and Actronis could resize partitions without loosing data - no need to backup restore each individual one. Exception is /system which is ext4

[simongee]

ok great thanks again guys, you're helping me alot
The only thing thats still a little unclear to me is how to backup and restore the individual partitions one by one.
Tbh i dont need any stuff thats on there, so why cant i just instead of the steps uboot listed:

so the steps are:
1.) backup extended partitions (logical drives, mmcblk2p4...mmcblk10)
2.) delete extended partitions
3.) recreate extended partitions with the first one shrunken by the size you wanna enlarge data partition
4.) restore extended partitions

just skip 1.), do 2.) and 3.) and flash your new 1.04 sd rescue after that? or boroda’s recovery pack? Not possible?

And i still have to decide which tool to use, since i dont have a paid partition tool, i was looking for a free one.
MiniTool Partition Wizard Home Edition 7.1 was my favourite, but i also got Paragon Partition Manager 11 Free Edition now.
Both should do the job, right? Any opinions?

[uboot]

surely you can use the sd rescue package, but why?

have you ever used a partitioning tool to move / resize / backup / restore partitions?

[simongee]

surely you can use the sd rescue package, but why?

well as I said, i got a bit confused by your answer and was looking for an alternative, let me explain. You said

the full image won't help you with repartitioning. it's for backup purposes only. additionally, you will have to dump each partition one by one...

(I knew how to do the full backup, but was not sure how to dump each partition by itself.) but then you said

data partition and reader partition do not have to be restored. uppon boot, the reader will re-initialize them. all other partitions (system, fonts, etc.) are kept untouched. backup them one by one and then restore them one by one.

I was thinking well, I would only touch /data and READER. And upon reboot they would be re-initialized by the reader. So whats the point of doing any backup at all? Wouldn't it be easier to just delete - recreate - label - reboot? why backing up and restoring partitions i didnt even touch? On top of that I was going to start from a clean state anyway (cleanup/unroot->root->repartition) without any data on it i would lose. Thats why the rescue-packages came to my mind. They contain everything what has to be on the reader at that point.

have you ever used a partitioning tool to move / resize / backup / restore partitions?

Yes i have, but I said I'm nor a linux-guy. I used it to resize/move/create partitions on my external hdd and on my laptop. But the only filesystems I worked with are ntfs/fat/fat32. I never had to backup/restore a partition, I just copy/pasted the content...

[uboot]

ok, got ya

the point is that in order to resize the data partition you have to

1.) shrink reader partition which is a primary partition at the _end_ of the disk
2.) enlarge extended partion which is the third partition of the disk
3.) move system partition to the end of the extended partition
4.) enlarge data partition

so you're right - no backups / restoring necessary, as long as your partition tool is able to resize / move the stuff around

[ewandeep]

Originally Posted by uboot

ok, got ya

the point is that in order to resize the data partition you have to

1.) shrink reader partition which is a primary partition at the _end_ of the disk
2.) enlarge extended partion which is the third partition of the disk
3.) move system partition to the end of the extended partition
4.) enlarge data partition

so you're right - no backups / restoring necessary, as long as your partition tool is able to resize / move the stuff around

Simongee, please let us know if you succeed in this operation. I will try too, thanks

[simongee]

Originally Posted by uboot

ok, got ya

the point is that in order to resize the data partition you have to

1.) shrink reader partition which is a primary partition at the _end_ of the disk
2.) enlarge extended partion which is the third partition of the disk
3.) move system partition to the end of the extended partition
4.) enlarge data partition

so you're right - no backups / restoring necessary, as long as your partition tool is able to resize / move the stuff around

@uboot
I did a full backup with rupor's method before i started.
Then i have done exactly those steps. But there is a problem
I used Paragon Partition Manager.
1) shrunk the READER partition -> ok
2) enlarge extended partition -> ok
3) move system partition to the end of extended -> ok
4) enlarge data partition -> fail...
tool wasnt able to do that, so i deleted data and recreated new ext4 partition exactly where the old one was, but with a new size. Labeled it "data". But it was empty now. So i thought about you telling me:

data partition and reader partition do not have to be restored. uppon boot, the reader will re-initialize them

so i rebooted, but reader wouldnt boot up. So i used the sd-recovery pack. After that the reader booted fine.
All fine, just as before, so i rooted again.
Now here is the problem:
The reader still thinks /data / phone storage is 48 MB...
When i boot to recovery and look at the partitions of the reader in Paragon it shows the correct new size. But on the reader i cant use the full size?
Any idea why?

[uboot]

i suspect you didn't format the data partition to ext4 after resizing. it is not enough to set the file system type in partition table. partition has to be formated as well.

which sd recovery did you use? mine? or porkupans?

porkupans will flash 48mb data partition, but can be resized to partition boundary with resize2fs from recovery console (you have to download that tool).

mine will format data partition (and reader partition, so beware!)

[simongee]

YES! GOT IT!

again thank u uboot, you were exactly right. I just created new /data (ext4) partition, but didnt format it... i was somehow assuming it would be already formated as ext4 after creating it.
So for u guys that want to try this too, i would like to add that i dont know anything about linux. I was able to do this without typing one single command into any console.
JUST DONT MESS WITH ANY OTHER PARTITION THAN READER, /data, /system
If u read this thread and have some experience with partitions under windows, this is totally doable. So here is what i did after my last post and uboot told me about formating the new partition:

1) restored my backup i had made with rupor's method (tool: Roadkil's Disk Image)
2) connected to pc in recovery mode
3) this time i didnt use Paragon Free Edition. It was really annoying me as it was only doing stuff after rebooting the pc every time. So i switched to MiniTool Partition Wizard Home Edition 7.1 (from here: http://www.partitionwizard.com/free-...n-manager.html)
4) shrink READER partition (keep it at the end of the drive, creating free space between READER and /system)
5) move /system to the end of extended partition. Now there is free space between /data and /system)
6) tool cant enlarge /data to the beginning of /system, which is what i wanted to do. So i deleted /data and created new ext4 partition in the space that is now free. Labeled it "data". Then FORMATED it as "ext4"
7) Now /data is empty. I tried to reboot. Reader wouldnt boot up
8) Tried uboot's new 1.04 sd recovery. Didnt work.

@uboot
It didnt work. Just as the 1st time i tried it. Reader stuck in "opening book" screen forever. I waited 2 hours, sd still blinking, no rebooting... So i pressed "reset"... Luckily it did nothing at all. I was really afraid pressing reset while led still blinking. Also no log file created... Something is wrong with it maybe? did u try it urself?

9) So i used "PRS-T1_SD_UPDATER_1.0.04.12210" by amutin from here: http://www.the-ebook.org/forum/viewtopic.php?t=22502
10) reader booted up fine. Rooted again using rupors package. BUT after checking "phone storage" under settings, still only 48 MB on /data But now i knew why! The sd-recovery flashed the old /data partition back which is 48 MB.
11) So back to recovery/Partitioning tool. TBH i dont really understand why this next thing worked. I formated /data again using "format partition" in the tool. But after formating, only the size changed and there was still data on it. So i rebooted and BAM, reader asked for initial settings. Root still there. "Phone storage" 520 MB.

[ewandeep]

Thank you simongee, could you report all the steps (without the problems, you meet) so any other can repeat the repartition

[jet322]

Hey, all. This seems like an appropriate place to put this. Sooo, I wanna make my /data partition bigger, but when I connect my reader 2 the PC in recovery, the device manager only shows "Gadget Serial". It doesn't show "RNDIS". :-( I deleted the DLLs in the "SETTING" part thru Root Explorer, a loong time ago when I didn't know what I was doing... I just wanted to get rid of "Low on storage space" message. Plz
Also, Rupor's AMR bricks my reader.

[jet322]

Originally Posted by simongee

YES! GOT IT!

9) So i used "PRS-T1_SD_UPDATER_1.0.04.12210" by amutin from here: http://www.the-ebook.org/forum/viewtopic.php?t=22502

10) reader booted up fine. Rooted again using rupors package. BUT after checking "phone storage" under settings, still only 48 MB on /data But now i knew why! The sd-recovery flashed the old /data partition back which is 48 MB.
11) So back to recovery/Partitioning tool. TBH i dont really understand why this next thing worked. I formated /data again using "format partition" in the tool. But after formating, only the size changed and there was still data on it. So i rebooted and BAM, reader asked for initial settings. Root still there. "Phone storage" 520 MB.

How'd you know what to do? The app is in Russian, the instructions are poorly translated, what should the folder on the root of the microSD be named? All I get is "Opening Book..." the light on the mSD card slot isn't even flashing. I don't see the "Updating..." thing! :-(

[simongee]

@ewandeep

Thank you simongee, could you report all the steps (without the problems, you meet) so any other can repeat the repartition

that was my plan
As I wrote in the first post i want to add it ro the wiki when i am sure...
well i managed to do it, there is just one, two questions i still have, so if uboot answers me, i will write it up in this thread and finally, when its approved, add it to the wiki...
Well actually there is only one thing. Uboot made a sd recovery package that should format the created empty /data partition and fill it with the files needed. But it didnt work for me, so i used another one. If it had worked, all would be clear to me...
But anyway, if u read through this thread u should be already able to do it right away, if not ask me whats unclear to u. I will try to help

I will repeat my question, so uboot sees it:
@uboot
sd recovery didnt work. Reader stuck in "opening book" screen forever. I waited 2 hours, sd still blinking, no rebooting... So i pressed "reset"... Luckily it did nothing at all. I was really afraid pressing reset while led still blinking. Also no log file created... Something is wrong with it maybe? did u try it urself?
@uboot
any idea about the step 11) i posted in post #20? why didnt it delete the files like formating should do?

@jet322

Hey, all. This seems like an appropriate place to put this. Sooo, I wanna make my /data partition bigger, but when I connect my reader 2 the PC in recovery, the device manager only shows "Gadget Serial". It doesn't show "RNDIS". :-( I deleted the DLLs in the "SETTING" part thru Root Explorer, a loong time ago when I didn't know what I was doing... I just wanted to get rid of "Low on storage space" message. Plz

hi!
which dlls u talking about? which "SETTING" part? And u got the "low on storage" message when u wanted to install apps, right? Which state is ur reader currently in? Is it rooted? which package did u use? which firmware are u on? Does it boot up normally?
Provide answers to these questions and i think i can help u

[ewandeep]

I follow the procedure, but now my sony prs-t1 is stucked.
I can only access to recovery state /Home+menu) and going to serial.
What can I do?
Here more details:
https://www.mobileread.com/forums/sho...74#post2092574

[simongee]

Originally Posted by ewandeep

I follow the procedure, but now my sony prs-t1 is stucked.
I can only access to recovery state /Home+menu) and going to serial.
What can I do?
Here more details:
https://www.mobileread.com/forums/sho...74#post2092574

can you please explain what u did to the reader that it is in such a state?
Did u do a backup how its explained here: http://www.the-ebook.org/forum/viewtopic.php?t=22502 ?
If u did a backup, just restore it.
Did u manage to access your reader with a partition tool while it was in recovery? did u repartition anything? could u please list the steps u have done in the order u have done them? Then i can maybe explain what went wrong

[rupor]

I did step by step guide with screenshots on how to repartition device simply. Eventually somebody (may be even me) will do a proper translation - for now here is Google translate.

I hope this could be used to prevent problems...

[simongee]

Originally Posted by rupor

I did step by step guide with screenshots on how to repartition device simply. Eventually somebody (may be even me) will do a proper translation - for now here is Google translate.

I hope this could be used to prevent problems...

Wow! Thank you rupor!
I was too busy to write up my step-by-step guide that i promised
But anyway you did a much better job than i would have done, so
I went over it and it seems to be easily understandable using google translate. But still, if anyone wants to repartition their device and isnt sure about some steps, just feel free to ask here! Its always better to ask BEFORE, than AFTER u did something with ur partitions, as it can brick your reader.

[e-ink]

Originally Posted by uboot

the point is that in order to resize the data partition you have to

1.) shrink reader partition which is a primary partition at the _end_ of the disk
2.) enlarge extended partion which is the third partition of the disk
3.) move system partition to the end of the extended partition
4.) enlarge data partition

so you're right - no backups / restoring necessary, as long as your partition tool is able to resize / move the stuff around

gparted does that!
I used it on knoppix-7.0.3 live dvd AFTER making a full dd disk image)

[uboot]

I know I just pointed out the necessary steps....

And if you read the complete thread, you'll find out that you can do a repartitioning of the T1 with Windows tools, too.

[e-ink]

there is a dd for windows too :P

I just posted gparted because it hasn't mentioned before. And its free open source software.

[Nabuccoo]

Hi everyone!

First of all I want to thank you for everything here, all of you! You did a great job to improve our beloved little T1. Now I want to ask some help.
I repartitioned my reader's internal storage a few months ago. I did it like simengee wrote here. I connected my reader in recovery mode (with home + menu buttons). I managed to install gadget serial (I had to edit th .inf file or something like that... it was some problem what i solved somehow, I can't remember). After that I used PUTTY to enter the serial consol. And after that I can't really remember what I did, but I think after that I could see the ext partition and other stuffs with Diskinternals Linux Reader program and also with MiniTool Partition Wizard 7.1. So I could enlarge the internal storage to 400 mb in the format, move, shrink way without any problem.

It was a few months ago as I said. Now the reader was getting slow and I massed up the reader some other way too not important. I decided to clear everything, reroot, reformat and than do it everything from the begining. So I rooted again my reader with rupor's AMR package. Than I noticed that th phones internal memory is 48 Mb again. :/

I started to repartition it again but I have a problem. Reboot intoo recovery mode. When I connect the reader to the laptop with USB cable I don't need to install gadget serial port, it is already installed. Than connect to the serial consol with PUTTY ok. After that I can't see the ext partitions. I don't know why, what I am doing wrong? Maybe I forgot something? Guys please help me.
(I am useing Win 7 x64 Ultimate if it is important.)
Thanks in advance.

[m3l7d0wN]

can you paste here your partition table? (i.e. with fdisk)

Originally Posted by Nabuccoo

Hi everyone!

First of all I want to thank you for everything here, all of you! You did a great job to improve our beloved little T1. Now I want to ask some help.
I repartitioned my reader's internal storage a few months ago. I did it like simengee wrote here. I connected my reader in recovery mode (with home + menu buttons). I managed to install gadget serial (I had to edit th .inf file or something like that... it was some problem what i solved somehow, I can't remember). After that I used PUTTY to enter the serial consol. And after that I can't really remember what I did, but I think after that I could see the ext partition and other stuffs with Diskinternals Linux Reader program and also with MiniTool Partition Wizard 7.1. So I could enlarge the internal storage to 400 mb in the format, move, shrink way without any problem.

It was a few months ago as I said. Now the reader was getting slow and I massed up the reader some other way too not important. I decided to clear everything, reroot, reformat and than do it everything from the begining. So I rooted again my reader with rupor's AMR package. Than I noticed that th phones internal memory is 48 Mb again. :/

I started to repartition it again but I have a problem. Reboot intoo recovery mode. When I connect the reader to the laptop with USB cable I don't need to install gadget serial port, it is already installed. Than connect to the serial consol with PUTTY ok. After that I can't see the ext partitions. I don't know why, what I am doing wrong? Maybe I forgot something? Guys please help me.
(I am useing Win 7 x64 Ultimate if it is important.)
Thanks in advance.

[uboot]

I guess the partition table is still the same, but the data partition got flashed with a 48mb image such that the file system 'thinks' it has 48mb, but the partition size is still bigger. you can simply reformat the data partition - all file content will be recreated on next boot.

[Nabuccoo]

Originally Posted by uboot

I guess the partition table is still the same, but the data partition got flashed with a 48mb image such that the file system 'thinks' it has 48mb, but the partition size is still bigger. you can simply reformat the data partition - all file content will be recreated on next boot.

Yes its still looks the same. If I connect the reader via usb I can still see only 1 gb of space on it instead of 1,4 gb. So how can I reformat the data partition? I think I have to acces to recovery mode and enter to the serial consol to see the data partition. Am I right? If it's so, that is my problem I can't see it. :/

[uboot]

data partition is invisible via usb!!! you're talking about the reader partition...

but if the reader partition reverted to 1,4GB, I am afraid that your previous partitioning attempt was not successful, because rooting does not alter partition table....

the meaning of the partitions is documented here in post #37: https://www.mobileread.com/forums/sho...=163137&page=3

that thread should answer all of your questions

[Nabuccoo]

Originally Posted by uboot

data partition is invisible via usb!!! you're talking about the reader partition...

but if the reader partition reverted to 1,4GB, I am afraid that your previous partitioning attempt was not successful, because rooting does not alter partition table....

the meaning of the partitions is documented here in post #37: https://www.mobileread.com/forums/sho...=163137&page=3

that thread should answer all of your questions

No I am talking about data partition too. And yes this is my problem it is invisible. But when I connected my reader in recovery mode with serial consol I could see it and the other partitions too in Diskinternals Linux Reader and MiniTool Partition Wizard too. But now I don't see it. I think I am doing something wrong (it is more than possible that I forgot something to do).

So what I have done now: I rebooted my reader in recovery mode (Home + Menu buttons), connected to the pc. Gadget serial port is already installed so I just looked the ports number in device manager and wrote this in Putty nad opened serial. After that I pressed enter and wrote "root" than enter again.
After this procedure I can see the hiden partitions (system, data, dictionaries etc.) am I right? Or I am doing something wrong? :/ (I am not a "linux guy" but it was so easy at last time... I don't know what is wrong now. )

[m3l7d0wN]

correct

[simongee]

Hi Nabuccoo!

I am not a "linux guy"

me neither! Thats the whole point of me starting this thread, you know

I didnt use Serial/Putty at all. Just MiniTool Partition Wizard. Connect in Recovery Mode. Then start MiniTool. It should show an overview of the partitions.
Does it look like the screenshot in Post #9 of this thread for u?

I guess the partition table is still the same, but the data partition got flashed with a 48mb image such that the file system 'thinks' it has 48mb, but the partition size is still bigger. you can simply reformat the data partition - all file content will be recreated on next boot.

I think uboot is right (DAMN, he ALWAYS is )
I experienced the same. If u reflash rupors root package, it installs the original 48mb /data image of the sony firmware. The reader then does not see the real size of ur reformated partiton.
So, just reformat ur data partition using MiniTool (EXT4).
If the reader doesnt boot up then, read post #20 of this thread (thats how i did it)
or
use uboots sd-rescue (i think it formats the /data partition before flashing, so it should be the right size) (correct me if i'm wrong here uboot)

[uboot]

correct - except that you should mention that sd-rescue will un-root the device

(i wish I really was correct all the time, nobody's perfect...)