PRS-T1 Android Market working

[uboot]

I got it

For reference - my old partition table (important: always work with sector units and align to cyl=64x512 Bytes I used Excel to calculate the new starts&endings)

Disk /dev/mmcblk2: 1958 MB, 1958739968 bytes
4 heads, 16 sectors/track, 59776 cylinders, total 3825664 sectors
Units = sectors of 1 * 512 = 512 bytes
        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk2p1           51200       71679       10240  83 Linux
/dev/mmcblk2p2           71680       92159       10240  83 Linux
/dev/mmcblk2p3           92160      866687      387264   5 Extended
/dev/mmcblk2p4          866688     3825663     1479488  83 Linux
/dev/mmcblk2p5           92176      124991       16408  83 Linux
/dev/mmcblk2p6          125008      403583      139288  83 Linux
/dev/mmcblk2p7          403600      424127       10264  83 Linux
/dev/mmcblk2p8          424144      506111       40984  83 Linux
/dev/mmcblk2p9          506128      604479       49176  83 Linux
/dev/mmcblk2p10         604496      866687      131096  83 Linux

New one (data is 512MB now)

Disk /dev/mmcblk2: 1958 MB, 1958739968 bytes
4 heads, 16 sectors/track, 59776 cylinders, total 3825664 sectors
Units = sectors of 1 * 512 = 512 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk2p1           51200       71679       10240  83 Linux
/dev/mmcblk2p2           71680       92159       10240  83 Linux
/dev/mmcblk2p3           92160     1816959      862400   5 Extended
/dev/mmcblk2p4         1816960     3825663     1004352  83 Linux
/dev/mmcblk2p5           92176      124991       16408  83 Linux
/dev/mmcblk2p6          125008      403583      139288  83 Linux
/dev/mmcblk2p7          403600      424127       10264  83 Linux
/dev/mmcblk2p8          424144      506111       40984  83 Linux
/dev/mmcblk2p9          506128     1554751      524312  83 Linux
/dev/mmcblk2p10        1554753     1816959      131103+ 83 Linux

Device boots up, adb shell accessible, but interface keeps restarting, let's see what might be the cause...

su was broken, put a new one into /system/bin via adb, fixpermissions fixed something, but looks like I have to reinstall PackageManager, etc.

*to be continued*

[j0534ng31]

Originally Posted by uboot

Device boots up, adb shell accessible, but interface keeps restarting, let's see what might be the cause...

su was broken, put a new one into /system/bin via adb, fixpermissions fixed something, but looks like I have to reinstall PackageManager, etc.

Seems to me like a permissions problem...

How did you do the backup/restore for the new bigger data partition? I recommend to use tar (it preserves owners, permissions and dates of files)...

Right now, after the problem, you can do it this way (from recovery):

- To make a tgz of the original data partition (asumed .img in Micro-SD card root):

[root (ttyGS0)]# mkdir /tmp/data_orig
[root (ttyGS0)]# mount -t auto /mnt/sd/mmcblk2p9.img /tmp/data_orig
[root (ttyGS0)]# cd /tmp/data_orig
[root (ttyGS0)]# tar -czvf /mnt/sd/mmcblk2p9.tgz .

- To restore the tgz to the new big partition

[root (ttyGS0)]# mkdir /tmp/data_big
[root (ttyGS0)]# mount -t auto /dev/mmcblk2p9 /tmp/data_big
[root (ttyGS0)]# cd /tmp/data_big
[root (ttyGS0)]# tar -xzvf /mnt/sd/mmcblk2p9.tgz

About the excel... I always use parted to make/resize partitions in android devices without problems... Read that (it also has an alignment_mode option)

[uboot]

It _was_ a permissions problem (stupid me - forgot to tell cp to keep file attributes when creating the 512MB data image from the 48MB one...)

I just recreated the 2p9 512MB image and dd-ed it via recovery console.

WORKS Finally got rid of the Link2D crutch...

BUT: this procedure is not for beginners... I'll better not write a wiki howto


Regarding parted - there's no parted on recovery console Had to stick with fdisk... but all went fine. You just need to know the size of a cylinder and the size of a sector to compute the correct starts / endings...


Anyways, everyone familiar with dd, fdisk, mounting loop devices, mkfs, etc. should be able to do it:

0.) on the T1, make a backup of /mnt/sdcard to /mnt/extsd/backup
1.) use recovery console to dump all mmcblk2-partitions, mbr, etc. to external sd
2.) use fdisk in sector mode to alter partition table according to specs above (delete partitions 3 and 4, create extended partition 3, primary 4, logical 5...10 and be sure to place 5...8 at the same starts/ends as before so there will be no need to dd them back...)
3.) power of the device
4.) recreate 512MB empty data partition (dd if=/dev/null of=/tmp/sdb1/mmcblk2p9_512.img bs=512M count=0 seek=1 && mkfs.ext4 -F /tmp/sdb1/mmcblk2p9_512.img)
5.) fill new data partition via loop back device, be sure to keep file attributes you may include the stuff from sdext2 if you want!
5.) recreate update.img from sd recovery package and replace /home/user/mmcblk2p9.img and mmcblk2p10.img
6.) do a sd recovery to flash it
7.) device should boot now, run fixpermissions.sh and
8.) restore backup of /mnt/sdcard from /mnt/extsd/backup

[vishcompany]

Originally Posted by uboot

...

BUT: this procedure is not for beginners... I'll better not write a wiki howto

completely agreed...

[uboot]

Well... it should be possible to create an SD recovery image that will do it all... I just don't have the time (and motivation) for that... any volunteers out there?

I give you a Teaser:

[j0534ng31]

Originally Posted by vishcompany

completely agreed...

me too...

uboot:
parted, last busybox and bash are always in my SD card... just in case...

[m3l7d0wN]

Originally Posted by uboot

0.) on the T1, make a backup of /mnt/sdcard to /mnt/extsd/backup
1.) use recovery console to dump all mmcblk2-partitions, mbr, etc. to external sd
2.) use fdisk in sector mode to alter partition table according to specs above (delete partitions 3 and 4, create extended partition 3, primary 4, logical 5...10 and be sure to place 5...8 at the same starts/ends as before so there will be no need to dd them back...)
3.) power of the device
4.) recreate 512MB empty data partition (dd if=/dev/null of=/tmp/sdb1/mmcblk2p9_512.img bs=512M count=0 seek=1 && mkfs.ext4 -F /tmp/sdb1/mmcblk2p9_512.img)
5.) fill new data partition via loop back device, be sure to keep file attributes you may include the stuff from sdext2 if you want!
5.) recreate update.img from sd recovery package and replace /home/user/mmcblk2p9.img and mmcblk2p10.img
6.) do a sd recovery to flash it
7.) device should boot now, run fixpermissions.sh and
8.) restore backup of /mnt/sdcard from /mnt/extsd/backup

thanks for the hints! I succesfully resized my data partition to 300mb :P
Should the section in the wiki be removed? it's quite partial and wrong.. and maybe it should be added a link to this discussion

[S3raph]

I'm running the latest firmware, however "um recovery" or (chgboot recovery) on the reader itself just reboots the reader, I flashed the enable-adb package, and the adb interface works fine, any hints?

[m3l7d0wN]

2 considerations:

-I couldn't flash my dumped system (mmcblk2p10) partition. The T1 will continue failing to boot after SD recovery. Instead, I had to use the provided p10 partition in the standard SD rescue package.
The dumped data partition (p9) was succesfully flashed
-After resizing, I made a factory reset and a rooting to clean up things. After that, the T1 refuses to make updates and boots in recovery mode... fortunately updates can be made in this mode via usb gadget .. Every day I discover a new behaviour :P

[uboot]

Poor m3l7d0wN... this is the price one as to pay for insane tweaks For me it took 2 days to get the T1 back running...

How did you create the new 2p9 and 2p10 images? Did you fsck them? Did you preserve file attributes like permissions?

Did you run su && fix_permissions via adb shell?

Is your reader partition (2p4) sane?

Which root set did you use? There are root sets that flash their own 2p9 and 2p10 images....

Originally Posted by m3l7d0wN

thanks for the hints! I succesfully resized my data partition to 300mb :P
Should the section in the wiki be removed? it's quite partial and wrong.. and maybe it should be added a link to this discussion

The wiki is on a quite different topic:
https://www.mobileread.com/forums/sho...5&postcount=42

Edit: I put a small hint in the wiki...

[m3l7d0wN]

Originally Posted by uboot

Poor m3l7d0wN... this is the price one as to pay for insane tweaks For me it took 2 days to get the T1 back running...

How did you create the new 2p9 and 2p10 images? Did you fsck them? Did you preserve file attributes like permissions?

Did you run su && fix_permissions via adb shell?

Is your reader partition (2p4) sane?

Which root set did you use? There are root sets that flash their own 2p9 and 2p10 images....


The wiki is on a quite different topic:
https://www.mobileread.com/forums/sho...5&postcount=42

Edit: I put a small hint in the wiki...

well, the partitions were created with

mkfs.ext4 -F file.img

then I just extracted the .tar of the dumped partitions.. I always used tar to preserve permissions.
I didn't run fix_permissions, it wasn't necessary. And I couldn't run it with the custom p10 partition since the T1 didn't even boot.

I formatted the p4 partition with adb the first time the T1 booted. All other partitions were ok (I used the same start/end sector in fdisk as you suggested).

I used the sd rescue set from the wiki (the "porkupan").

It would be nice (although a bit dangerous) to do a custom sd rescue with an automated script for repartitioning, with different "stages" (repartition, write p9,p10,p4) or a script runnable from recovery mode..

[m3l7d0wN]

ok, I finally discovered why my image didn't work.. my .tar wasn't extracted correctly for some reason

[Thor]

Thanks for all informations given in this thread! Very useful before playing with contents of system and data partitions.

[dare]

Hi j0534ng31,

Originally Posted by j0534ng31

parted, last busybox and bash are always in my SD card... just in case...

may I ask what build of parted you use on the T1? Could you share it?
Thanks and regards,
d.

EDIT: Ok, there is a nice set of tools in your other post on fsck. Thanks!

[engyroz]

Hello, I'm new here.

I just rooted my device with the zeam package and installed android market.

I want to install this app: https://market.android.com/details?id=gopeking.apps

Why doesn't it show up when I search for it on the prs-t1?

Thanks
/T