• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

Q&A regarding gellmar's notes on E400 development

86 posts in this topic

Posted · Report post

Well, basic tests - baseband, wifi, wifi tethering, bluetooth, bt tether, usb mass storage, camera, GPS - work flawlessly. Encryption works too with fix. Today I will sync the repos and build a new recovery with standard partition alignment and try the fdisk expert mode in it. CWM 5.8.4.5 lacks fdisk 'x' mode flag. If everything goes right - I mean applying and reverting, I will PM the recovery.img for fastboot and the commands related to hacks so we can continue.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I'm so excited!!

0

Share this post


Link to post
Share on other sites

Posted · Report post

I'm so excited!!

Me too :)

Being a noob Though I really don't understand what you guys are working on in here - am really happy that you are trying. Good luck from all l3 owners ;)

0

Share this post


Link to post
Share on other sites

Posted · Report post

No, I am going to re-build CM9 with these patches and flash recovery and check if new recovery's fdisk works in expert mode. If not, recompile with flag enabled.

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

UPDATE: The CM9 recovery really lacks ENABLE_FEATURE_FDISK_ADVANCED flag, so I re-compiled a new recovery and flashed it. It requires google Nexus ADB drivers to get into debug. Now I will test the crazybyte's safe sequences and report back.

First sequence:


~ # echo -e "p\nd\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\np\nq\n" | fdisk /dev/bl

ock/mmcblk0

echo -e "p\nd\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\np\nq\n" | fdisk /dev/bl

ock/mmcblk0

The number of cylinders for this disk is set to 238592.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			 Device Boot	 Start		 End	 Blocks Id System

/dev/block/mmcblk0p1 *		 1		 3		 20 4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			 3		 128	 1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	 1024 46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	 238592	 1906688 5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		 8193	 8704	 4096 47 Unknown

/dev/block/mmcblk0p6		 8705	 9216	 4096 2c Unknown

/dev/block/mmcblk0p7		 9217	 9728	 4096 58 Unknown

/dev/block/mmcblk0p8		 9729	 12800	 24576 77 Unknown

/dev/block/mmcblk0p9		 12801	 13824	 8192 48 Unknown

/dev/block/mmcblk0p10		 13825	 14336	 4096 4a Unknown

/dev/block/mmcblk0p11		 14337	 14848	 4096 4b Unknown

/dev/block/mmcblk0p12		 14849	 18432	 28672 49 Unknown

/dev/block/mmcblk0p13		 18433	 22016	 28672 6c Unknown

/dev/block/mmcblk0p14		 22017	 70656	 389120 83 Linux

/dev/block/mmcblk0p15		 70657	 71680	 8192 83 Linux

/dev/block/mmcblk0p16		 71681	 80896	 73728 83 Linux

/dev/block/mmcblk0p17		 80897	 81920	 8192 60 Unknown

/dev/block/mmcblk0p18		 81921	 82944	 8192 83 Linux

/dev/block/mmcblk0p19		 82945	 84480	 12288 6b Unknown

/dev/block/mmcblk0p20		 84481	 215552	 1048576 83 Linux

/dev/block/mmcblk0p21		 215553	 236032	 163840 83 Linux

/dev/block/mmcblk0p22		 236033	 238080	 16384 83 Linux

/dev/block/mmcblk0p23		 238081	 238592	 4096 ff Unknown

Command (m for help): Partition number (1-23):

Command (m for help): Partition number (1-22):

Command (m for help): First cylinder (258-238592, default 258): Last cylinder or

+size or +sizeM or +sizeK (84482-236032, default 236032):

Command (m for help):

Expert command (m for help): Done.

Expert command (m for help):

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			 Device Boot	 Start		 End	 Blocks Id System

/dev/block/mmcblk0p1 *		 1		 3		 20 4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			 3		 128	 1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	 1024 46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	 238592	 1906688 5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		 8193	 8704	 4096 47 Unknown

/dev/block/mmcblk0p6		 8705	 9216	 4096 2c Unknown

/dev/block/mmcblk0p7		 9217	 9728	 4096 58 Unknown

/dev/block/mmcblk0p8		 9729	 12800	 24576 77 Unknown

/dev/block/mmcblk0p9		 12801	 13824	 8192 48 Unknown

/dev/block/mmcblk0p10		 13825	 14336	 4096 4a Unknown

/dev/block/mmcblk0p11		 14337	 14848	 4096 4b Unknown

/dev/block/mmcblk0p12		 14849	 18432	 28672 49 Unknown

/dev/block/mmcblk0p13		 18433	 22016	 28672 6c Unknown

/dev/block/mmcblk0p14		 22017	 70656	 389120 83 Linux

/dev/block/mmcblk0p15		 70657	 71680	 8192 83 Linux

/dev/block/mmcblk0p16		 71681	 80896	 73728 83 Linux

/dev/block/mmcblk0p17		 80897	 81920	 8192 60 Unknown

/dev/block/mmcblk0p18		 81921	 82944	 8192 83 Linux

/dev/block/mmcblk0p19		 82945	 84480	 12288 6b Unknown

/dev/block/mmcblk0p20		 84482	 236032	 1212408 83 Linux

/dev/block/mmcblk0p21		 236033	 238080	 16384 83 Linux

/dev/block/mmcblk0p22		 238081	 238592	 4096 ff Unknown

Command (m for help):

~ #

Second sequence:

~ # echo -e "p\nd\n20\nn\n84482\n215552\nn\n215553\n236032\nx\nf\nr\nt\n20\n83\n

t\n21\n83\np\nq\n" | fdisk /dev/block/mmcblk0

echo -e "p\nd\n20\nn\n84482\n215552\nn\n215553\n236032\nx\nf\nr\nt\n20\n83\n

t\n21\n83\np\nq\n" | fdisk /dev/block/mmcblk0

The number of cylinders for this disk is set to 238592.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			  Device Boot	  Start		 End	  Blocks  Id System

/dev/block/mmcblk0p1   *		   1		   3		  20  4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			   3		 128	    1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	    1024  46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	  238592	 1906688   5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		    8193	    8704	    4096  47 Unknown

/dev/block/mmcblk0p6		    8705	    9216	    4096  2c Unknown

/dev/block/mmcblk0p7		    9217	    9728	    4096  58 Unknown

/dev/block/mmcblk0p8		    9729	   12800	   24576  77 Unknown

/dev/block/mmcblk0p9		   12801	   13824	    8192  48 Unknown

/dev/block/mmcblk0p10		  13825	   14336	    4096  4a Unknown

/dev/block/mmcblk0p11		  14337	   14848	    4096  4b Unknown

/dev/block/mmcblk0p12		  14849	   18432	   28672  49 Unknown

/dev/block/mmcblk0p13		  18433	   22016	   28672  6c Unknown

/dev/block/mmcblk0p14		  22017	   70656	  389120  83 Linux

/dev/block/mmcblk0p15		  70657	   71680	    8192  83 Linux

/dev/block/mmcblk0p16		  71681	   80896	   73728  83 Linux

/dev/block/mmcblk0p17		  80897	   81920	    8192  60 Unknown

/dev/block/mmcblk0p18		  81921	   82944	    8192  83 Linux

/dev/block/mmcblk0p19		  82945	   84480	   12288  6b Unknown

/dev/block/mmcblk0p20		  84481	  215552	 1048576  83 Linux

/dev/block/mmcblk0p21		 215553	  236032	  163840  83 Linux

/dev/block/mmcblk0p22		 236033	  238080	   16384  83 Linux

/dev/block/mmcblk0p23		 238081	  238592	    4096  ff Unknown

Command (m for help): Partition number (1-23):

Command (m for help): First cylinder (259-238592, default 259): Last cylinder or

+size or +sizeM or +sizeK (84482-215552, default 215552):

Command (m for help): First cylinder (259-238592, default 259): No free sectors

available

Command (m for help): 2: unknown command

Command Action

a	   toggle a bootable flag

b	   edit bsd disklabel

c	   toggle the dos compatibility flag

d	   delete a partition

l	   list known partition types

n	   add a new partition

o	   create a new empty DOS partition table

p	   print the partition table

q	   quit without saving changes

s	   create a new empty Sun disklabel

t	   change a partition's system id

u	   change display/entry units

v	   verify the partition table

w	   write table to disk and exit

x	   extra functionality (experts only)

Command (m for help):

Expert command (m for help): Done.

Expert command (m for help):

Command (m for help): Partition number (1-23): Hex code (type L to list codes):

Command (m for help): Partition number (1-23): Hex code (type L to list codes):

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			  Device Boot	  Start		 End	  Blocks  Id System

/dev/block/mmcblk0p1   *		   1		   3		  20  4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			   3		 128	    1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	    1024  46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	  238592	 1906688   5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		    8193	    8704	    4096  47 Unknown

/dev/block/mmcblk0p6		    8705	    9216	    4096  2c Unknown

/dev/block/mmcblk0p7		    9217	    9728	    4096  58 Unknown

/dev/block/mmcblk0p8		    9729	   12800	   24576  77 Unknown

/dev/block/mmcblk0p9		   12801	   13824	    8192  48 Unknown

/dev/block/mmcblk0p10		  13825	   14336	    4096  4a Unknown

/dev/block/mmcblk0p11		  14337	   14848	    4096  4b Unknown

/dev/block/mmcblk0p12		  14849	   18432	   28672  49 Unknown

/dev/block/mmcblk0p13		  18433	   22016	   28672  6c Unknown

/dev/block/mmcblk0p14		  22017	   70656	  389120  83 Linux

/dev/block/mmcblk0p15		  70657	   71680	    8192  83 Linux

/dev/block/mmcblk0p16		  71681	   80896	   73728  83 Linux

/dev/block/mmcblk0p17		  80897	   81920	    8192  60 Unknown

/dev/block/mmcblk0p18		  81921	   82944	    8192  83 Linux

/dev/block/mmcblk0p19		  82945	   84480	   12288  6b Unknown

/dev/block/mmcblk0p20		  84482	  215552	 1048568  83 Linux

/dev/block/mmcblk0p21		 215553	  236032	  163840  83 Linux

/dev/block/mmcblk0p22		 236033	  238080	   16384  83 Linux

/dev/block/mmcblk0p23		 238081	  238592	    4096  ff Unknown

Command (m for help):

~ #

Edited by gellmar
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Hum gellmar, please run

echo -e "p\nd\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\np\nd\n20\np\nn\n84482\n215552\nn\n215553\n236032\nx\nf\nr\nt\n20\n83\nt\n21\n83\np\nq\n" | fdisk /dev/block/mmcblk0[/CODE]

It runs join and split and print result. (Before you was running split with the original partition map, and this why it fails)

PS: join works flaweslly :) maybe we could relase a one way rom and if the people want to revert the must flash original kdz?

Edited by crazybyte
0

Share this post


Link to post
Share on other sites

Posted · Report post


~ # echo -e "p\nd\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\np\nd\n20\np\nn\n844

215552\nn\n215553\n236032\nx\nf\nr\nt\n20\n83\nt\n21\n83\np\nq\n" | fdisk /d

lock/mmcblk0

echo -e "p\nd\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\np\nd\n20\np\nn\n84482\n

215552\nn\n215553\n236032\nx\nf\nr\nt\n20\n83\nt\n21\n83\np\nq\n" | fdisk /d

lock/mmcblk0

The number of cylinders for this disk is set to 238592.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			  Device Boot	  Start		 End	  Blocks  Id System

/dev/block/mmcblk0p1   *		   1		   3		  20  4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			   3		 128	    1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	    1024  46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	  238592	 1906688   5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		    8193	    8704	    4096  47 Unknown

/dev/block/mmcblk0p6		    8705	    9216	    4096  2c Unknown

/dev/block/mmcblk0p7		    9217	    9728	    4096  58 Unknown

/dev/block/mmcblk0p8		    9729	   12800	   24576  77 Unknown

/dev/block/mmcblk0p9		   12801	   13824	    8192  48 Unknown

/dev/block/mmcblk0p10		  13825	   14336	    4096  4a Unknown

/dev/block/mmcblk0p11		  14337	   14848	    4096  4b Unknown

/dev/block/mmcblk0p12		  14849	   18432	   28672  49 Unknown

/dev/block/mmcblk0p13		  18433	   22016	   28672  6c Unknown

/dev/block/mmcblk0p14		  22017	   70656	  389120  83 Linux

/dev/block/mmcblk0p15		  70657	   71680	    8192  83 Linux

/dev/block/mmcblk0p16		  71681	   80896	   73728  83 Linux

/dev/block/mmcblk0p17		  80897	   81920	    8192  60 Unknown

/dev/block/mmcblk0p18		  81921	   82944	    8192  83 Linux

/dev/block/mmcblk0p19		  82945	   84480	   12288  6b Unknown

/dev/block/mmcblk0p20		  84481	  215552	 1048576  83 Linux

/dev/block/mmcblk0p21		 215553	  236032	  163840  83 Linux

/dev/block/mmcblk0p22		 236033	  238080	   16384  83 Linux

/dev/block/mmcblk0p23		 238081	  238592	    4096  ff Unknown

Command (m for help): Partition number (1-23):

Command (m for help): Partition number (1-22):

Command (m for help): First cylinder (258-238592, default 258): Last cylinde

+size or +sizeM or +sizeK (84482-236032, default 236032):

Command (m for help):

Expert command (m for help): Done.

Expert command (m for help):

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			  Device Boot	  Start		 End	  Blocks  Id System

/dev/block/mmcblk0p1   *		   1		   3		  20  4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			   3		 128	    1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	    1024  46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	  238592	 1906688   5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		    8193	    8704	    4096  47 Unknown

/dev/block/mmcblk0p6		    8705	    9216	    4096  2c Unknown

/dev/block/mmcblk0p7		    9217	    9728	    4096  58 Unknown

/dev/block/mmcblk0p8		    9729	   12800	   24576  77 Unknown

/dev/block/mmcblk0p9		   12801	   13824	    8192  48 Unknown

/dev/block/mmcblk0p10		  13825	   14336	    4096  4a Unknown

/dev/block/mmcblk0p11		  14337	   14848	    4096  4b Unknown

/dev/block/mmcblk0p12		  14849	   18432	   28672  49 Unknown

/dev/block/mmcblk0p13		  18433	   22016	   28672  6c Unknown

/dev/block/mmcblk0p14		  22017	   70656	  389120  83 Linux

/dev/block/mmcblk0p15		  70657	   71680	    8192  83 Linux

/dev/block/mmcblk0p16		  71681	   80896	   73728  83 Linux

/dev/block/mmcblk0p17		  80897	   81920	    8192  60 Unknown

/dev/block/mmcblk0p18		  81921	   82944	    8192  83 Linux

/dev/block/mmcblk0p19		  82945	   84480	   12288  6b Unknown

/dev/block/mmcblk0p20		  84482	  236032	 1212408  83 Linux

/dev/block/mmcblk0p21		 236033	  238080	   16384  83 Linux

/dev/block/mmcblk0p22		 238081	  238592	    4096  ff Unknown

Command (m for help): Partition number (1-22):

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			  Device Boot	  Start		 End	  Blocks  Id System

/dev/block/mmcblk0p1   *		   1		   3		  20  4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			   3		 128	    1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	    1024  46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	  238592	 1906688   5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		    8193	    8704	    4096  47 Unknown

/dev/block/mmcblk0p6		    8705	    9216	    4096  2c Unknown

/dev/block/mmcblk0p7		    9217	    9728	    4096  58 Unknown

/dev/block/mmcblk0p8		    9729	   12800	   24576  77 Unknown

/dev/block/mmcblk0p9		   12801	   13824	    8192  48 Unknown

/dev/block/mmcblk0p10		  13825	   14336	    4096  4a Unknown

/dev/block/mmcblk0p11		  14337	   14848	    4096  4b Unknown

/dev/block/mmcblk0p12		  14849	   18432	   28672  49 Unknown

/dev/block/mmcblk0p13		  18433	   22016	   28672  6c Unknown

/dev/block/mmcblk0p14		  22017	   70656	  389120  83 Linux

/dev/block/mmcblk0p15		  70657	   71680	    8192  83 Linux

/dev/block/mmcblk0p16		  71681	   80896	   73728  83 Linux

/dev/block/mmcblk0p17		  80897	   81920	    8192  60 Unknown

/dev/block/mmcblk0p18		  81921	   82944	    8192  83 Linux

/dev/block/mmcblk0p19		  82945	   84480	   12288  6b Unknown

/dev/block/mmcblk0p20		 236033	  238080	   16384  83 Linux

/dev/block/mmcblk0p21		 238081	  238592	    4096  ff Unknown

Command (m for help): First cylinder (258-238592, default 258): Last cylinde

+size or +sizeM or +sizeK (84482-236032, default 236032):

Command (m for help): First cylinder (258-238592, default 258): Sector 34488

s already allocated

First cylinder (215554-238592, default 215554):

Command (m for help):

Expert command (m for help): Done.

Expert command (m for help):

Command (m for help): Partition number (1-23): Hex code (type L to list code

Command (m for help): Partition number (1-23): Hex code (type L to list code

Command (m for help):

Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

			  Device Boot	  Start		 End	  Blocks  Id System

/dev/block/mmcblk0p1   *		   1		   3		  20  4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			   3		 128	    1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	    1024  46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	  238592	 1906688   5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		    8193	    8704	    4096  47 Unknown

/dev/block/mmcblk0p6		    8705	    9216	    4096  2c Unknown

/dev/block/mmcblk0p7		    9217	    9728	    4096  58 Unknown

/dev/block/mmcblk0p8		    9729	   12800	   24576  77 Unknown

/dev/block/mmcblk0p9		   12801	   13824	    8192  48 Unknown

/dev/block/mmcblk0p10		  13825	   14336	    4096  4a Unknown

/dev/block/mmcblk0p11		  14337	   14848	    4096  4b Unknown

/dev/block/mmcblk0p12		  14849	   18432	   28672  49 Unknown

/dev/block/mmcblk0p13		  18433	   22016	   28672  6c Unknown

/dev/block/mmcblk0p14		  22017	   70656	  389120  83 Linux

/dev/block/mmcblk0p15		  70657	   71680	    8192  83 Linux

/dev/block/mmcblk0p16		  71681	   80896	   73728  83 Linux

/dev/block/mmcblk0p17		  80897	   81920	    8192  60 Unknown

/dev/block/mmcblk0p18		  81921	   82944	    8192  83 Linux

/dev/block/mmcblk0p19		  82945	   84480	   12288  6b Unknown

/dev/block/mmcblk0p20		  84482	  215552	 1048568  83 Linux

/dev/block/mmcblk0p21		 236032	  236032		   8  83 Linux

/dev/block/mmcblk0p22		 236033	  238080	   16384  83 Linux

/dev/block/mmcblk0p23		 238081	  238592	    4096  ff Unknown

Command (m for help):

~ #

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Please note the second (split-back) sequence was tested on a stock layout! I will join partitions with first sequence and split them again with the second.

Yes, the second sequence is wrong. Let me re-assemble it now. If we succeed, no kdz reflashing will be required

Edited by gellmar
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Original.


/dev/block/mmcblk0p19 82945 84480 12288 6b Unknown

/dev/block/mmcblk0p20 84481 215552 1048576 83 Linux

/dev/block/mmcblk0p21 215553 236032 163840 83 Linux

/dev/block/mmcblk0p22 236033 238080 16384 83 Linux
After join: (d 20 d 20 n 84482 236032 x f r)

/dev/block/mmcblk0p19 82945 84480 12288 6b Unknown

/dev/block/mmcblk0p20 84482 236032 1212408 83 Linux               *1*

/dev/block/mmcblk0p21 236033 238080 16384 83 Linux
After deleting join partition: (d 20)

/dev/block/mmcblk0p19 82945 84480 12288 6b Unknown

/dev/block/mmcblk0p20 236033 238080 16384 83 Linux

/dev/block/mmcblk0p21 238081 238592 4096 ff Unknown
After spliting again: (n 84482 215552 n 215553 236032 x f r t 20 83 t 21 83)

/dev/block/mmcblk0p20 84482 215552 1048568 83 Linux

/dev/block/mmcblk0p21 236032 236032 8 83 Linux                     *2*

/dev/block/mmcblk0p22 236033 238080 16384 83 Linux

NOTES:

*1* Did you notice that after join we miss one cylinder? fdisk doesn't allow me to set the beginning of the new partition in 84481, it says that it's in use :S

*2* Again the command fail because sector allocated, i put the sequence of commands, maybe you could debug by hand without using the script.

Edited by crazybyte
0

Share this post


Link to post
Share on other sites

Posted · Report post

crazybyte, I will try and I think we manage this issue. Yes, we loose a sector and it is due to allocation scheme but I dont think we cannot sacrifice these for the sake of stability

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

I got it (sacrificing sectors... but should work!):

DEBUG (It doesn't write to disk, only displays on screen):

Join:

echo -e "p\nd\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\np\nq\n" | fdisk /dev/block/mmcblk0
Split:
echo -e "p\nd\n20\np\nn\n84482\n215552\nn\n215554\n236032\nx\nf\nr\nt\n20\n83\nt\n21\n83\np\nq\n" | fdisk /dev/block/mmcblk0[/code]
[/size]



RELEASE ([color=#ff0000]WARNING IT WRITES INTO THE DISK AND DOESN'T PRINT ANYTHING ON SCREEN[/color]):



Join:


[spoiler]
[code]echo -e "d\n20\nd\n20\nn\n84482\n236032\nx\nf\nr\nw\nq\n" | fdisk /dev/block/mmcblk0 > /dev/null[/code]
[/spoiler] [size=4]Split:[/size] [spoiler][size=4]
[CODE]echo -e "d\n20\nn\n84482\n215552\nn\n215554\n236032\nx\nf\nr\nt\n20\n83\nt\n21\n83\nw\nq\n" | fdisk /dev/block/mmcblk0 > /dev/null[/code]

[/size][size=4][/spoiler]

[/size]

Edited by crazybyte
0

Share this post


Link to post
Share on other sites

Posted · Report post

Seems like you guys are on a vacation :P

0

Share this post


Link to post
Share on other sites

Posted · Report post

nikufellow, yes, warming our bodies under the sun of LCDs and trying to boot cm-10.1's graphics. I sent everything to crazybyte to make a zip flash, but discovered an ugly bug in UMS. Now I want to figure out what's wrong.

0

Share this post


Link to post
Share on other sites

Posted · Report post

don't listen to them who can't waiting n try to disturb your work buddy...

just stay on track, make it sure you doing these with fun without any stressed.

take your times as well, we knew the devs are human not a robot... :P

we still here waiting for your miracles gellmar... :thumbsup:

0

Share this post


Link to post
Share on other sites

Posted · Report post

nikufellow, yes, warming our bodies under the sun of LCDs and trying to boot cm-10.1's graphics. I sent everything to crazybyte to make a zip flash, but discovered an ugly bug in UMS. Now I want to figure out what's wrong.

Sadly the phone it's not mine. My girlfried refused to give the phone yesterday because she want to save all data... Nevertheless I'm trying to make a easy-flasheable zip.

0

Share this post


Link to post
Share on other sites

Posted · Report post

what needs testing?

0

Share this post


Link to post
Share on other sites

Posted · Report post

hecatae, the USB Mass Storage needs to be tested slightly more.

The scenario:

1. Reboot the phone. Plug-in USB cable and wait 3 seconds, then activate UMS.

2. Copy two or three folders with many files (like music albums) to UMS from your PC

3. When all I/O operations complete, turn off UMS by button (not forcibly unplug USB cable!)

4. Turn off USB cable

5. Wait a bit

6. Plug for the second time, wait, activate UMS, upload something more, stop UMS, unplug

7. Try to check it 3-5 times with bigger folders / files

On some CM setups it leads to hangup on second iteration and mass storage start error since 3rd. Managed to get it yesterday, had to install CM from scratch to remove that. Need additional stats.

0

Share this post


Link to post
Share on other sites

Posted · Report post

Do you have good news?

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

crazybyte, started temple run...

UPD1: Release 'Split' command gives me the following output


fdisk -l /dev/block/mmcblk0


Disk /dev/block/mmcblk0: 1954 MB, 1954545664 bytes

1 heads, 16 sectors/track, 238592 cylinders

Units = cylinders of 16 * 512 = 8192 bytes


			 Device Boot	 Start		 End	 Blocks Id System

/dev/block/mmcblk0p1 *		 1		 3		 20 4d Unknown

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2			 3		 128	 1003+ 45 Unknown

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3			 129		 256	 1024 46 Unknown

Partition 3 does not end on cylinder boundary

/dev/block/mmcblk0p4			 257	 238592	 1906688 5 Extended

Partition 4 does not end on cylinder boundary

/dev/block/mmcblk0p5		 8193	 8704	 4096 47 Unknown

/dev/block/mmcblk0p6		 8705	 9216	 4096 2c Unknown

/dev/block/mmcblk0p7		 9217	 9728	 4096 58 Unknown

/dev/block/mmcblk0p8		 9729	 12800	 24576 77 Unknown

/dev/block/mmcblk0p9		 12801	 13824	 8192 48 Unknown

/dev/block/mmcblk0p10		 13825	 14336	 4096 4a Unknown

/dev/block/mmcblk0p11		 14337	 14848	 4096 4b Unknown

/dev/block/mmcblk0p12		 14849	 18432	 28672 49 Unknown

/dev/block/mmcblk0p13		 18433	 22016	 28672 6c Unknown

/dev/block/mmcblk0p14		 22017	 70656	 389120 83 Linux

/dev/block/mmcblk0p15		 70657	 71680	 8192 83 Linux

/dev/block/mmcblk0p16		 71681	 80896	 73728 83 Linux

/dev/block/mmcblk0p17		 80897	 81920	 8192 60 Unknown

/dev/block/mmcblk0p18		 81921	 82944	 8192 83 Linux

/dev/block/mmcblk0p19		 82945	 84480	 12288 6b Unknown

/dev/block/mmcblk0p20		 84482	 215552	 1048568 83 Linux

/dev/block/mmcblk0p21		 236033	 238080	 16384 83 Linux

/dev/block/mmcblk0p22		 238081	 238592	 4096 ff Unknown

~ # fdisk /dev/block/mmcblk0

So I recreated layout by hand and now reverting to KDZ stock. UPD2: Error in /sdcard/merge-sdcard-recovery-STEP1.zip (status 6)

Starting recovery on Sat Mar 30 17:07:00 2013

framebuffer: fd 4 (240 x 320)

ClockworkMod Recovery v5.8.4.5

recovery filesystem table

=========================

0 /tmp ramdisk (null) (null) 0

1 /recovery emmc /dev/block/mmcblk0p17 (null) 0

2 /boot emmc /dev/block/mmcblk0p9 (null) 0

3 /cache ext4 /dev/block/mmcblk0p16 (null) 0

4 /data ext4 /dev/block/mmcblk0p21 (null) 0

5 /emmc vfat /dev/block/mmcblk0p20 (null) 0

6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk1p1 0

7 /system ext4 /dev/block/mmcblk0p14 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!

W:Unable to get recovery.fstab info for /sd-ext during fstab generation!

I:Completed outputting fstab.

I:Processing arguments.

I:Checking arguments.

I:device_recovery_start()

Command: "/sbin/recovery"

ro.secure=1

ro.allow.mock.location=0

ro.debuggable=1

persist.sys.usb.config=adb

ro.build.id=IMM76L

ro.build.display.id=cm_e400-userdebug 4.0.4 IMM76L eng.koush.20120620.113048 test-keys

ro.build.version.incremental=eng.koush.20120620.113048

ro.build.version.sdk=15

ro.build.version.codename=REL

ro.build.version.release=4.0.4

ro.build.date=Wed Jun 20 11:31:42 PDT 2012

ro.build.date.utc=0

ro.build.type=userdebug

ro.build.user=koush

ro.build.host=Koushik-Lion.local

ro.build.tags=test-keys

ro.product.model=LG-E400

ro.product.brand=lge

ro.product.name=e0_tmo_eu

ro.product.device=e400

ro.product.board=e400

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=LGE

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=msm7x27a

ro.build.product=e400

ro.build.description=e0_tmo_eur-user 2.3.6 GRK39F 2ED8A66C75 release-keys

ro.build.fingerprint=lge/e0_tmo_eur/e0:2.3.6/GRK39F/V10c-MAR-28-2012.2ED8A66C75:user/release-keys

ro.build.characteristics=default

ro.cm.device=e400

ro.sf.lcd_density=120

debug.fb.rgb565=0

debug.sf.hw=1

debug.enabletr=false

debug.composition.type=mdp

ro.opengles.version=131072

com.qc.hardware=true

ro.sf.compbypass.enable=0

persist.sys.use_dithering=1

wifi.interface=wlan0

rild.libpath=/system/lib/libril-qc-1.so

rild.libargs=-d /dev/smd0

ro.telephony.ril.v3=signalstrength,datacall,singlepdp

ro.telephony.ril_class=LGEQualcommUiccRIL

ro.telephony.default_network=0

telephony.lteOnGsmDevice=0

ro.additionalmounts=/mnt/extra-sd

ro.vold.switchablepair=/mnt/sdcard,/mnt/extra-sd

ro.rommanager.developerid=cyanogenmod

keyguard.no_require_sim=true

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.clientidbase=android-google

ro.com.android.wifi-watchlist=GoogleGuest

ro.setupwizard.enterprise_mode=1

ro.com.android.dateformat=MM-dd-yyyy

ro.com.android.dataroaming=false

ro.cm.version=9-20120620-UNOFFICIAL-e400

ro.modversion=9-20120620-UNOFFICIAL-e400

ro.config.ringtone=CyanTone.ogg

ro.config.notification_sound=CyanMessage.ogg

ro.config.alarm_alert=CyanAlarm.ogg

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=32m

dalvik.vm.heapsize=76m

ro.ril.hsxpa=1

ro.ril.gprsclass=10

ro.adb.qemud=1

dalvik.vm.lockprof.threshold=500

dalvik.vm.dexopt-flags=m=y

net.bt.name=Android

net.change=net.bt.name

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.factorytest=0

ro.serialno=3bbe76

ro.bootmode=unknown

ro.baseband=msm

ro.carrier=unknown

ro.bootloader=unknown

ro.hardware=e0

ro.revision=0

ro.emmc=1

init.svc.recovery=running

service.adb.root=1

init.svc.adbd=running

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 13

ev: 3 53 236

fd: 13

ev: 3 54 264

fd: 13

ev: 3 48 52

fd: 13

ev: 0 2 0

event: 236 264

down

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

event: 0 0

up

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 3 53 0

fd: 13

ev: 3 54 0

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 0 0

received a touch up event, when touch state was already up??

fd: 13

ev: 0 0 0

fd: 13

ev: 3 53 236

fd: 13

ev: 3 54 264

fd: 13

ev: 3 48 0

fd: 13

ev: 0 2 0

event: 236 264

received a touch up event, when touch state was already up??

fd: 13

ev: 0 0 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 114 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 114 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 12

ev: 1 115 1

failed to open /sys/class/android_usb/android0/state: No such file or directory

fd: 12

ev: 1 115 0

fd: 7

ev: 1 107 1

fd: 7

ev: 0 0 0

failed to open /sys/class/android_usb/android0/state: No such file or directory

-- Installing: /sdcard/merge-sdcard-recovery-STEP1.zip

fd: 7

ev: 1 107 0

fd: 7

ev: 0 0 0

Finding update package...

I:Update location: /sdcard/merge-sdcard-recovery-STEP1.zip

Opening update package...

Installing update...

line 10 col 9: syntax error, unexpected STRING, expecting $end

1 parse errors

E:Error in /sdcard/merge-sdcard-recovery-STEP1.zip

(Status 6)

Installation aborted.

Fixed that with minor update-script typo fix

UPD3: Step 2 needs update-binary from CM9, otherwise format command expects 3 args instead of 4.

Edited by gellmar
0

Share this post


Link to post
Share on other sites

Posted · Report post

Its a typo

0

Share this post


Link to post
Share on other sites

Posted · Report post

I will check

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

UPD3: Step 2 needs update-binary from CM9, otherwise format command expects 3 args instead of 4.

Also mke2fs command failed to create the filesystem:


mount -t ext4 /dev/block/mmcblk0p20 /data

mount: mounting /dev/block/mmcblk0p20 on /data failed: Invalid argument

Well, partition table is killed after reboot... have to revert to stock again!

It looks like the fdisk results differ from inside adb and from zip updater... need to investigate

Edited by gellmar
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

STEP1- Error. Missing ; on line 9.

Gellmar maybe we need to reboot to update partition table :S

EDIT: Please test with busybox mk2fs. Maybe we have to format using

assert(format("ext4", "EMMC", "/dev/block/mmcblk0p20", "/data"));[/CODE]

Edited by crazybyte
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.