01-19-2012, 03:36 AM | #46 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
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) Code:
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 Code:
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 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* |
01-19-2012, 04:55 AM | #47 | |
Connoisseur
Posts: 83
Karma: 1224
Join Date: Dec 2011
Location: Gijon (Spain)
Device: Sony PRS-T1 black
|
Quote:
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): Code:
[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 . Code:
[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 Last edited by j0534ng31; 01-19-2012 at 09:14 AM. |
|
Advert | |
|
01-20-2012, 04:50 AM | #48 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
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 |
01-20-2012, 06:12 AM | #49 |
Addict
Posts: 283
Karma: 138550
Join Date: Mar 2009
Device: Gen3(†); PB302(↓); PRS-350; T1; voyage
|
|
01-20-2012, 06:30 AM | #50 |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
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: |
Advert | |
|
01-20-2012, 07:46 AM | #51 |
Connoisseur
Posts: 83
Karma: 1224
Join Date: Dec 2011
Location: Gijon (Spain)
Device: Sony PRS-T1 black
|
me too...
uboot: parted, last busybox and bash are always in my SD card... just in case... Last edited by j0534ng31; 01-20-2012 at 07:49 AM. |
01-24-2012, 05:49 PM | #52 | |
Zealot
Posts: 102
Karma: 38810
Join Date: Apr 2011
Device: Sony PRS-T1
|
Quote:
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 |
|
01-24-2012, 06:33 PM | #53 |
Member
Posts: 14
Karma: 20
Join Date: Dec 2011
Device: Sony Reader PRS-T1
|
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?
|
01-24-2012, 08:22 PM | #54 |
Zealot
Posts: 102
Karma: 38810
Join Date: Apr 2011
Device: Sony PRS-T1
|
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 |
01-25-2012, 02:12 AM | #55 | |
Evangelist
Posts: 425
Karma: 75216
Join Date: Nov 2011
Location: old europe
Device: Kobo Mini, Tolino Epos 2
|
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.... Quote:
https://www.mobileread.com/forums/sho...5&postcount=42 Edit: I put a small hint in the wiki... Last edited by uboot; 01-25-2012 at 02:19 AM. |
|
01-25-2012, 07:47 AM | #56 | |
Zealot
Posts: 102
Karma: 38810
Join Date: Apr 2011
Device: Sony PRS-T1
|
Quote:
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.. |
|
01-25-2012, 09:57 AM | #57 |
Zealot
Posts: 102
Karma: 38810
Join Date: Apr 2011
Device: Sony PRS-T1
|
ok, I finally discovered why my image didn't work.. my .tar wasn't extracted correctly for some reason
|
01-26-2012, 06:48 AM | #58 |
Member
Posts: 23
Karma: 550
Join Date: Jan 2012
Device: Kobo Aura H2O
|
Thanks for all informations given in this thread! Very useful before playing with contents of system and data partitions.
|
01-26-2012, 08:33 AM | #59 | |
Member
Posts: 18
Karma: 15762
Join Date: Jan 2012
Device: Boyue Likebook Mars
|
Parted
Hi j0534ng31,
Quote:
Thanks and regards, d. EDIT: Ok, there is a nice set of tools in your other post on fsck. Thanks! Last edited by dare; 01-28-2012 at 12:23 PM. Reason: solved, linked for reference |
|
01-28-2012, 10:20 AM | #60 |
Junior Member
Posts: 3
Karma: 10
Join Date: Jan 2012
Device: sony prs-t1
|
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 |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Touch Working! Rooted 1.1.0 w/ Market | Kralik | Nook Developer's Corner | 16 | 08-22-2012 04:23 PM |
IQ Market working on IQ! | Icewyng | PocketBook | 250 | 06-09-2012 11:46 AM |
Android tablets: Any success with Android Market? | nicabod | Android Devices | 0 | 12-18-2011 05:13 AM |
NC: Market supposedely working | Mastiff | Nook Developer's Corner | 8 | 01-15-2011 07:34 AM |
Android How To Enable the Android Market in the Google Android Emulator | cheyennedonna | enTourage Archive | 11 | 08-14-2010 11:12 PM |