Database Users

[Q] /system/ directory corrupted, Salvage?

~ # e2fsck -c /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p9: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Salvage<y>?
Is this supposed to happen or do I indeed have a corrupted directory?

I went ahead anyway and this was my result
/dev/block/mmcblk0p9: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p9: 1576/54544 files (0.2% non-contiguous), 71430/218112 blocks

Narada2XK said:
I went ahead anyway and this was my result
/dev/block/mmcblk0p9: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p9: 1576/54544 files (0.2% non-contiguous), 71430/218112 blocks
Click to expand...
Click to collapse
hmmm what it shows? ;D it means that your emmc isnt fcked? or smt like that

EdgaBimbam said:
hmmm what it shows? ;D it means that your emmc isnt fcked? or smt like that
Click to expand...
Click to collapse
~ # umount /cache
~ # umount /system
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
(parted) quit
quit
~ # e2fsck -n -f -v /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
1568 inodes used (2.87%)
3 non-contiguous files (0.2%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1293/1
70009 blocks used (32.10%)
0 bad blocks
0 large files
1190 regular files
103 directories
0 character device files
0 block device files
0 fifos
0 links
266 symbolic links (266 fast symbolic links)
0 sockets
--------
1559 files
~ #
I don't have any bad blocks and so far I don't see any problems, however, when I checked mmcblk0p10, that came back with errors, which I am not sure if I should have or not. I didn't bother to fix that though.

I suppose it's supposed to be that was because I re-install CM9, factory reset / wiped and...
~ # umount /cache
~ # umount /system
~ # e2fsck -n -f -v /dev/block/mmcblk0p9
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 46753, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
~ #
going to restore my nandroid now.

take a NSTG back to stock

Hi,
I succesfullly rooted my Nook glowlight, but when I tried to go back to stock with my nook backup I found the backup was not ok (just 77MB) and now I have a bricked NSTG that won't get past the "Install Failed" screen.
I've tried almost every method I could find in the forums, but none worked for me.
Is there anything else beside n2T and Alpha-Format I could try to revive my device?
TIA

I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.
If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.
I'm sure somebody has other ways to get shell access.

Renate NST said:
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.
If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.
I'm sure somebody has other ways to get shell access.
Click to expand...
Click to collapse
thanks for that I'll give it a try...
Sadly, I'm on a W7 box (not mine) and all I can see in the device manager is a nook with a yellow sign in it
ADB devices returns a blank list....
I tried updating the drivers for the nook: first uninstalled anything nooklike with usbdeview, and then pointed W7 to a folder where I had downloaded usbdrivers from this thread http://forum.xda-developers.com/showthread.php?t=1354487 but W7 keeps telling there are no drivers for nook in that folder.
If I boot without SD then the nook is recognized and USB drivers install fine. It's booting with CWM that the device is not recognized.
Stuck

There are drivers and drivers.
As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.
See: http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB

Renate NST said:
There are drivers and drivers.
As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.
See: http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
Click to expand...
Click to collapse
It worked:
D:\nook_root\adbshell>adb devices
List of devices attached
11223344556677 recovery
D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
4 heads, 16 sectors/track, 59776 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ #
completely noob with the nook, can't seem to find /rom and Win32DiskImager does not find a device to read from to perform said backup

The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 0c 1 38 79,691,776 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 926 1,646,264,320
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 405 251,658,240 /media
mmcblk0p7 ext3 83 406 525 251,658,240 /cache
mmcblk0p8 ext3 83 526 926 840,957,952 /data
Unused 927 933 14,680,064

Renate NST said:
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 0c 1 38 79,691,776 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 926 1,646,264,320
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 405 251,658,240 /media
mmcblk0p7 ext3 83 406 525 251,658,240 /cache
mmcblk0p8 ext3 83 526 926 840,957,952 /data
Unused 927 933 14,680,064
Click to expand...
Click to collapse
mmmm, a bit risky isn't it ?
I think I'll read the rest of the internets before proceeding I need to understand this.....
thanks again

srgarfi said:
mmmm, a bit risky isn't it ?
Click to expand...
Click to collapse
Well, you don't have anything at all in your partition table, not even the correct CHS.
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.

Renate NST said:
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.
Click to expand...
Click to collapse
Oh, ah, that changes everything! It's worth a try.
I need to find a dummy guide to perform this operations, any clues?
Edit: Found this, looks like a start http://forum.xda-developers.com/showthread.php?t=1279091
thanks again

booted in gparted live and took a peek at the Nook. This is what I found (sorry I don't know yet how to post images):
Device information
Model: B&N Ebook Disk
Size: 182 GiB
Path: /dev/sdb
Partition table: msdos
Heads: 255
Sectors/track: 63
Cylinders: 238
Total sectors: 3825664
Sector size: 512
Physical characteristics being so different I'm affraid trying to convert heads/cylinders from Renate's Touch to my Glo schema would be useless.
Could someone with a NSTG please share partition information?
Thank you all,

srgarfi said:
Physical characteristics being so different...
Click to expand...
Click to collapse
Well, they are not real physical differences.
You can juggle heads and sectors/track as long as the size of a cylinder stays the same.
It may be that the Glow has gone to a bigger cylinder, but it's suspicious that it's not a power of two.

Renate NST said:
You can juggle heads and sectors/track as long as the size of a cylinder stays the same.
Click to expand...
Click to collapse
Not good at math, I can't get an exact match

Here is a script that will partition your Nook internal SD card like the listing above.
You can either copy this to the SD card, chmod 777 it and run it
or just copy and paste it to the Windows command line window running ADB.
Then you can try some mounts and see what you've got.
(nookpart.sh is zipped.)

was about to try the script (thanks again!) but nook is stuck at "rooted forever" screen and nothing I do awakes it: power on, power on 30 sec, power on and n, plug it to pc, and every combination. Took off the sd and tried combinations again, nothing. I've searched a bit and all other cases resumed to reboot by pressing long power. Not this one....no hard reset available? Every piece of equipment must have a big red switch =)
Should I stop messing around and buy another one? (not in the states anymore, it will take like 40+ days to deliver here...)
EDIT: false alarm, battery was too low to power on. Where did the full charge go? I dunno....30 more minutes before I can try

Renate NST said:
Here is a script that will partition your Nook internal SD card like the listing above.
You can either copy this to the SD card, chmod 777 it and run it
or just copy and paste it to the Windows command line window running ADB.
Then you can try some mounts and see what you've got.
(nookpart.sh is zipped.)
Click to expand...
Click to collapse
Executed the script:
Code:
D:\nook_root\adbshell>adb shell sh /sdcard/nookpart.sh
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-934, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (39-934, default 39): Using default value
39
Last cylinder or +size or +sizeM or +sizeK (39-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (47-934, default 47): Using default value
47
Last cylinder or +size or +sizeM or +sizeK (47-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Selected partition 4
First cylinder (142-934, default 142): Using default value 142
Last cylinder or +size or +sizeM or +sizeK (142-934, default 934):
Command (m for help): First cylinder (142-926, default 142): First cylinder (142
-926, default 142): Using default value 142
Last cylinder or +size or +sizeM or +sizeK (142-926, default 926):
Command (m for help): First cylinder (286-926, default 286): First cylinder (286
-926, default 286): Using default value 286
Last cylinder or +size or +sizeM or +sizeK (286-926, default 926):
Command (m for help): First cylinder (406-926, default 406): First cylinder (406
-926, default 406): Using default value 406
Last cylinder or +size or +sizeM or +sizeK (406-926, default 926):
Command (m for help): First cylinder (526-926, default 526): First cylinder (526
-926, default 526): Using default value 526
Last cylinder or +size or +sizeM or +sizeK (526-926, default 926):
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 1 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 2 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 6 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8):
Command (m for help):
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
D:\nook_root\adbshell>
From CWM tried to mount /boot and failed. Took off the SD, booted nook (fingers crossed) and it displayed the "install failed" screen.
Nice try, thanks for the patience :good:

No, that's what I expected.
The partitioning worked fine
You had already bashed the boot partition.
Now try:
Code:
mkdir /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
ls -l /rom

Looks like there was already a /rom
Code:
D:\nook_root\adbshell>adb shell
~ # mkdir /rom
mkdir /rom
mkdir: can't create directory '/rom': File exists
~ # mount -t vfat /dev/block/mmcblk0p2 /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
mount: mounting /dev/block/mmcblk0p2 on /rom failed: Device or resource busy
~ # ls -l /rom
ls -l /rom
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #

Hmm, I thought of that at the last moment.
Code:
mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff

Renate NST said:
Hmm, I thought of that at the last moment.
Code:
mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff
Click to expand...
Click to collapse
yes, works, but I don't get it?
Code:
~ # mkdir /stuff
mkdir /stuff
~ # mount -t vfat /dev/block/mmcblk0p2 /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
~ # ls -l /stuff
ls -l /stuff
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #
in the meantime I booted noogie and did a backup of the semibricked nook just in case.... =)
Now I'll write CWM to the SD and boot again

That means that the partitioning is correct and that your /rom is intact.
Make a good backup of your personalized stuff:
Code:
adb pull /stuff
Now you have to fix up the boot partition.
I'd probably try to install the factory.zip
Code:
mkdir /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
ls -l /fact
Code:
adb pull /fact/factory.zip
adb pull /fact/rombackup.zip
Then copy factory.zip to the external SD card and do a CWR update with that.

[Q] Nook Color partitioning messed up

Hi,
I've tried to install CM10.1 but I ran into some glitches: 10.1 is some how installed but every time I boot up it says "Android is upgrading" followed by a pop up once I unlock saying "Unfortunately, ConfigUpdater has stopped". This happens every time I boot up.
On the device is a multiboot installed I no longer need. In order to get rid of it, I installed newest CWMR, searched multiple partition recovery packages but none of them worked. I always became "can't open /sdcard/*.zip (bad)". Downloading again (from the device as from my Mac) also didn't work.
When connecting it via adb, partition scheme looks as follows:
adb shell busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 775 965 1534207+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p9 416 671 2056288+ 83 Linux
/dev/block/mmcblk0p10 672 716 361431 83 Linux
/dev/block/mmcblk0p11 717 774 465822 83 Linux
Partition table entries are not in disk order
I compared this with a partition scheme I found here and it looks like there are some differences.
One more thing: When trying to mount /emmc/ via CWMR it says "can't mount /emmc/", not sure but likely this has to do with this.
As there is absolutely no data I would need on the device, I am fine to do what ever is needed in order to straighten this. I'm also used to Linux so able to execute shell commands. I know adb and like to use it.
What would be the best way to get this device back to operational? I don't find my SD-card adapter so I won't be able to prepare SD cards until I will buy a new one next week.
Thanks!
Sven

antagonist01 said:
Hi,
I've tried to install CM10.1 but I ran into some glitches: 10.1 is some how installed but every time I boot up it says "Android is upgrading" followed by a pop up once I unlock saying "Unfortunately, ConfigUpdater has stopped". This happens every time I boot up.
On the device is a multiboot installed I no longer need. In order to get rid of it, I installed newest CWMR, searched multiple partition recovery packages but none of them worked. I always became "can't open /sdcard/*.zip (bad)". Downloading again (from the device as from my Mac) also didn't work.
When connecting it via adb, partition scheme looks as follows:
adb shell busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 775 965 1534207+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p9 416 671 2056288+ 83 Linux
/dev/block/mmcblk0p10 672 716 361431 83 Linux
/dev/block/mmcblk0p11 717 774 465822 83 Linux
Partition table entries are not in disk order
I compared this with a partition scheme I found here and it looks like there are some differences.
One more thing: When trying to mount /emmc/ via CWMR it says "can't mount /emmc/", not sure but likely this has to do with this.
As there is absolutely no data I would need on the device, I am fine to do what ever is needed in order to straighten this. I'm also used to Linux so able to execute shell commands. I know adb and like to use it.
What would be the best way to get this device back to operational? I don't find my SD-card adapter so I won't be able to prepare SD cards until I will buy a new one next week.
Thanks!
Sven
Click to expand...
Click to collapse
You still have your old dual boot partition scheme on emmc. Since you cannot seem to get CWM to flash a repair zip, you need to do it manually with ADB and fdisk. P1 through p7 are set up correctly. You need to delete p8, p9, p10 and p11. Then recreate p8 as fat32 to fill the rest of the disk.
Sent from my Nook HD+ running CM10.1 on emmc.

Thanks for the quick reply!
I did as you mentioned. Recreation of partition went fine so I booted into recovery in order to create the filesystem. I used "wipe data/factory reset" which ended without error.
But after the reboot data seems to be still unavailable:
[email protected]:/data # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /rom vfat rw,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:49 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:49 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/data # mount /dev/block/mmcblk0p8 tt/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mkfs.vfat /dev/block/mmcblk0p8
mkfs.vfat: lseek: Value too large for defined data type
I thought mkfs.vfat would make a FAT32 file system? This confuses me...
Any ideas are highly appreciated...
Thanks in advance!
Sven

antagonist01 said:
Thanks for the quick reply!
I did as you mentioned. Recreation of partition went fine so I booted into recovery in order to create the filesystem. I used "wipe data/factory reset" which ended without error.
But after the reboot data seems to be still unavailable:
[email protected]:/data # mount /dev/block/mmcblk0p8 tt/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mkfs.vfat /dev/block/mmcblk0p8
mkfs.vfat: lseek: Value too large for defined data type
I thought mkfs.vfat would make a FAT32 file system? This confuses me...
Any ideas are highly appreciated...
Thanks in advance!
Sven
Click to expand...
Click to collapse
I don't understand that mount command you did above, so don't know about the mkfs.vfat command either.
The mount command should be:
mount -t vfat /dev/block/mmcblk0p8 /emmc
Since you now have CWM working, go to my NC partition repair thread linked in my signature and flash my 5678 format zip.
Edit: You say data is not available, yet it is mounted in your list as p6. I guess I am not sure what you mean.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
I don't understand that mount command you did above, so don't know about the mkfs.vfat command either.
The mount command should be:
mount -t vfat /dev/block/mmcblk0p8 /emmc
Since you now have CWM working, go to my NC partition repair thread linked in my signature and flash my 45678 format zip.
Edit: You say data is not available, yet it is mounted in your list as p6. I guess I am not sure what you mean.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I tried mounting it manually followed by the try to create the FS manually. Also mount -t vfat /dev/block/mmcblk0p8 /emmc gives mem an error.
Anyhow: I downloaded the files from your thread but had no success:
The NookColor-emmc-format-partitions-5-6-7-8.zip gives me
E:Error in /sdcard/Download/new/NookColor-emmc-format-partitions-5-6-7-8.zip
(Status ())
Installation aborted
When trying NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip screen flickers and it returns to CWMR start screen.
I meanwhile believe CWMR is somehow corrupt. I will search for a manual how to flash via ADB...
Thanks!
Sven

antagonist01 said:
I tried mounting it manually followed by the try to create the FS manually. Also mount -t vfat /dev/block/mmcblk0p8 /emmc gives mem an error.
Anyhow: I downloaded the files from your thread but had no success:
The NookColor-emmc-format-partitions-5-6-7-8.zip gives me
E:Error in /sdcard/Download/new/NookColor-emmc-format-partitions-5-6-7-8.zip
(Status ())
Installation aborted
When trying NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip screen flickers and it returns to CWMR start screen.
I meanwhile believe CWMR is somehow corrupt. I will search for a manual how to flash via ADB...
Thanks!
Sven
Click to expand...
Click to collapse
You cannot flash by ADB. What version of CWM are you using?
Does the fdisk command say that p8 was created properly? And you changed p8 to fat with fdisk, right? You did tell it to write (w) after making those changes?
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
You cannot flash by ADB. What version of CWM are you using?
Does the fdisk command say that p8 was created properly? You did tell it to write (w) after making those changes, right?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
OK, that explains my unsuccessful search. I thought it would be possible as I usually do this with my Nexus7 as well...
I wrote the partition table and it also is there:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 416 965 4417843+ c Win95 FAT32 (LBA)
[email protected]:/ #
Here the history of what I did:
[email protected]:/ # fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 775 965 1534207+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p9 416 671 2056288+ 83 Linux
/dev/block/mmcblk0p10 672 716 361431 83 Linux
/dev/block/mmcblk0p11 717 774 465822 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-11): 11
Command (m for help): d
Partition number (1-10): 10
Command (m for help): d
Partition number (1-9): 9
Command (m for help): d
Partition number (1-8): 8
Command (m for help): n
First cylinder (416-965, default 416):
Using default value 416
Last cylinder or +size or +sizeM or +sizeK (416-965, default 965):
Using default value 965
Command (m for help): t
Partition number (1-8): 8
Hex code (type L to list codes): c
Changed system type of partition 8 to c (Win95 FAT32 (LBA))
Command (m for help): p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 416 965 4417843+ c Win95 FAT32 (LBA)
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Is it possible to replace the actual recovery with a new one? Or would I need a recovery on SD Card?
CWRM is 6.0.3.1 by the way...
Thanks!
Sven

antagonist01 said:
OK, that explains my unsuccessful search. I thought it would be possible as I usually do this with my Nexus7 as well...
I wrote the partition table and it also is there:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 416 965 4417843+ c Win95 FAT32 (LBA)
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Is it possible to replace the actual recovery with a new one? Or would I need a recovery on SD Card?
CWRM is 6.0.3.1 by the way...
Thanks!
Sven
Click to expand...
Click to collapse
Ok, the partition table looks right.
And that 6.0.3.1 CWM is the problem. My old zips do not work on that version. You somehow need to get an older version like 5.5.0.4 on there. You could try flashing the emmc version zip from my NC Tips thread linked in my signature. But it might fail to install too since it is also an old zip.
Sent from my Nook HD+ running CM10.1 on emmc.

Now it makes sense! I meanwhile called my neighbor and got an micro SD card reader borrowed. I saw you have a rescue image linked in your thread as well. Once the card is backed up, I will flash this in order to fix the Nook.
About the threads: Awesome help pages! They really describe everything in a perfect way! The only thing I could think of as minor improvement is md5sums for the links.
I will report back once I'm finished with the SD card.
Thanks a lot for your help!
Sven

Alright, worked like a charm! I've dd'ed the image to a SD card, copied the packages to it and booted into it. From there everything was easily done.
Thank you leapinlar for your quick help and the great manuals!
Sven

I9505 - Cannot create loop device, action not permitted

Hi, I am trying to put kali linux on my Galaxy S4 I9505, using Complete Linux Installer.
However, I came across an error I couldn't fix, not even after searching every XDA thread about it.
My Galaxy S4 I9505 runs Android 4.3 and was rooted using this method: w|w|w.w0lfdroid.c|o|m/2013/12/Safe-Root-Android-4.3-Galaxy-S3-S4-Note-No-Warranty-Void.html
(Please remove the "|", I have no idea how else I can give detailed information, If I am not even allowed to post my root method. And I don't want to spam the forums for 10 posts..)
Rootchecker says my phone is rooted and I able to run root explorer etc.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
So I downloaded the kali linux image via the Complete Linux Installer app (kalilinux.ext4.img), put it on my sdcard and then pressed the "start linux" button.
As soon as the script tries to create a loop device, I get the following error:
Code:
Creating loop device.. mknod: /dev/block/loop255: Operation not permitted
FAILED
Error: Unable to create loop device!
When I checked in /dev/block, I couldn't find a file called "loop255" however I could find files like "loop0".
When I tried to set their permissions, I got the error that I was not allowed to modify it.
When trying to run
Code:
# busybox mount -rw -o loop -t ext4 /dev/block/loop0 /system
I get the error:
Code:
ioctl LOOP_SET_FD failed: Device or resource busy
I am hoping someone could help me further. I am unsure if the problem lies at my root method (not full root or something? KNOX blocking it? Android 4.3 blocking it?), a wrong busybox location or something, or a kernel that doesn't support device looping. Or maybe the problem is something much simpler.

Hey, could anyone help me? Still looking for a solution or workaround.
I can give more info if needed.

GalaxyPhoner said:
Hi, I am trying to put kali linux on my Galaxy S4 I9505, using Complete Linux Installer.
However, I came across an error I couldn't fix, not even after searching every XDA thread about it.
My Galaxy S4 I9505 runs Android 4.3 and was rooted using this method: w|w|w.w0lfdroid.c|o|m/2013/12/Safe-Root-Android-4.3-Galaxy-S3-S4-Note-No-Warranty-Void.html
(Please remove the "|", I have no idea how else I can give detailed information, If I am not even allowed to post my root method. And I don't want to spam the forums for 10 posts..)
Rootchecker says my phone is rooted and I able to run root explorer etc.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
So I downloaded the kali linux image via the Complete Linux Installer app (kalilinux.ext4.img), put it on my sdcard and then pressed the "start linux" button.
As soon as the script tries to create a loop device, I get the following error:
Code:
Creating loop device.. mknod: /dev/block/loop255: Operation not permitted
FAILED
Error: Unable to create loop device!
When I checked in /dev/block, I couldn't find a file called "loop255" however I could find files like "loop0".
When I tried to set their permissions, I got the error that I was not allowed to modify it.
When trying to run
Code:
# busybox mount -rw -o loop -t ext4 /dev/block/loop0 /system
I get the error:
Code:
ioctl LOOP_SET_FD failed: Device or resource busy
I am hoping someone could help me further. I am unsure if the problem lies at my root method (not full root or something? KNOX blocking it? Android 4.3 blocking it?), a wrong busybox location or something, or a kernel that doesn't support device looping. Or maybe the problem is something much simpler.
Click to expand...
Click to collapse
Hi.. I have found a way of getting through the loop255 creation, below is what i have done;
Installed Terminal IDE on my Samsung GT-19505 and connected to the phone through telnet from my PC.
Once connected change to Super User and go to the below dir', run the command and hit enter
[email protected]:/system/xbin #mknod -m a=rw /dev/block/loop255 b 7 255
This will create the loop255 device for you
To varify, go to the below directory and run;
[email protected]:/dev/block# ls
dm-0 loop7 mmcblk0p16 mmcblk0p24 mmcblk0p6 ram1 ram4
loop0 mmcblk0 mmcblk0p17 mmcblk0p25 mmcblk0p7 ram10 ram5
loop1 mmcblk0p1 mmcblk0p18 mmcblk0p26 mmcblk0p8 ram11 ram6
loop2 mmcblk0p10 mmcblk0p19 mmcblk0p27 mmcblk0p9 ram12 ram7
loop255 mmcblk0p11 mmcblk0p2 mmcblk0p28 mmcblk1 ram13 ram8
loop3 mmcblk0p12 mmcblk0p20 mmcblk0p29 mmcblk1p1 ram14 ram9
loop4 mmcblk0p13 mmcblk0p21 mmcblk0p3 param ram15 vold
loop5 mmcblk0p14 mmcblk0p22 mmcblk0p4 platform ram2 zram0
loop6 mmcblk0p15 mmcblk0p23 mmcblk0p5 ram0 ram3
You will see that the device has been created.
Now I have come to another road block;
127|[email protected]:/data/local # sh /data/data/com.zpwebsites.linuxonandroi>
/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[35]: dirname: Permission denied
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Error: Unable to mount the loop device!
I have tried mounting the device manually to /data/local/mnt but still getting same error
Still searching for a solution

Same problem
Hi, i had the same problem a few months ago and i tried to contact developers, no success,
so i'll look again into it, i'd love to have fedora running inside my S4
Good luck !
dr_do_little_ said:
Hi.. I have found a way of getting through the loop255 creation, below is what i have done;
Installed Terminal IDE on my Samsung GT-19505 and connected to the phone through telnet from my PC.
Once connected change to Super User and go to the below dir', run the command and hit enter
[email protected]:/system/xbin #mknod -m a=rw /dev/block/loop255 b 7 255
This will create the loop255 device for you
To varify, go to the below directory and run;
[email protected]:/dev/block# ls
dm-0 loop7 mmcblk0p16 mmcblk0p24 mmcblk0p6 ram1 ram4
loop0 mmcblk0 mmcblk0p17 mmcblk0p25 mmcblk0p7 ram10 ram5
loop1 mmcblk0p1 mmcblk0p18 mmcblk0p26 mmcblk0p8 ram11 ram6
loop2 mmcblk0p10 mmcblk0p19 mmcblk0p27 mmcblk0p9 ram12 ram7
loop255 mmcblk0p11 mmcblk0p2 mmcblk0p28 mmcblk1 ram13 ram8
loop3 mmcblk0p12 mmcblk0p20 mmcblk0p29 mmcblk1p1 ram14 ram9
loop4 mmcblk0p13 mmcblk0p21 mmcblk0p3 param ram15 vold
loop5 mmcblk0p14 mmcblk0p22 mmcblk0p4 platform ram2 zram0
loop6 mmcblk0p15 mmcblk0p23 mmcblk0p5 ram0 ram3
You will see that the device has been created.
Now I have come to another road block;
127|[email protected]:/data/local # sh /data/data/com.zpwebsites.linuxonandroi>
/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[35]: dirname: Permission denied
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Error: Unable to mount the loop device!
I have tried mounting the device manually to /data/local/mnt but still getting same error
Still searching for a solution
Click to expand...
Click to collapse
---------- Post added at 05:15 PM ---------- Previous post was at 04:43 PM ----------
Ok i'm trying to let it work, and reading the man page of mknod i tried:
mknod -m a=rwxrwxrwx /dev/block/loop255 b 7 255
to avoid the permission problem, in fact i works, BUT trying again to boot linux this error appears:
Error: unable to attach image to loop device!
Now i'm playing with the mount -o loop fedora.img /deb/block/loop255 to find the solution....
Any idea ?
flashback_pa said:
Hi, i had the same problem a few months ago and i tried to contact developers, no success,
so i'll look again into it, i'd love to have fedora running inside my S4
Good luck !
Click to expand...
Click to collapse

Something is changing, just used
losetup -r /dev/block/loop255 /fedora.img
but the mount command still fails.
By the way, Are you sure that the type ext4 is correct to mount the iso ? Maybe we should use iso9660 ?
flashback_pa said:
Hi, i had the same problem a few months ago and i tried to contact developers, no success,
so i'll look again into it, i'd love to have fedora running inside my S4
Good luck !
---------- Post added at 05:15 PM ---------- Previous post was at 04:43 PM ----------
Ok i'm trying to let it work, and reading the man page of mknod i tried:
mknod -m a=rwxrwxrwx /dev/block/loop255 b 7 255
to avoid the permission problem, in fact i works, BUT trying again to boot linux this error appears:
Error: unable to attach image to loop device!
Now i'm playing with the mount -o loop fedora.img /deb/block/loop255 to find the solution....
Any idea ?
Click to expand...
Click to collapse

[SCRIPT] Fix partition table for Android 4.4

Since the gapps for 4.4 need very much space wee need bigger system partitions.
I've created a script which automates this process and increases them both to 840MB.
the space is taken from the userdata partition.
You should backup your whole phone before doing this(storage will not be touched but you shouldn't take the risk)
I tested it with 32GB version only so if you want to know if it will work for 16gb, too give me the output of this command:
parted -s /dev/block/mmcblk0 print
Download:
http://d-h.st/FWz
Instructions:
1) boot into CWM
2) adb push repartition.sh /tmp
3) adb shell chmod 0777 /tmp/repartition.sh
4) adb shell /tmp/repartition.sh
5) adb reboot recovery
6) now you can do all the usual stuff like enabling TDB and installing ROM's

Sounds great but I cannot test it, since I dont have any parted binaries (at least in my 4.1.1 Wajk Wiui ROM) ? Can you please tell me where I can get them.
Second Question:
Im currently running TDB:
System 1 latest WIUI 4.1.1 v5 ROM
System 2 MIUI v6 1.9.19
Both system partitions are completely full (usage 98 %) and the same with the data partitions ( usage 97 % )!
Would it be possible to decrease /sdcard space and repartition it like the following with TDB enabled:
system 800 mb
system1 800 mb
data 1500 mb
data1 1500 mb
sdcard *the rest*
thanks in advance

sounds like you tried to repartition from Android
You need to boot to CWM - you have parted there.

Sorry I hate people who just ask stupid questions before reading the instructions carefully ...silly me sorry for that...
What about the second question, is it possible to either increase the data partitions for less space on /sdcard ?

there isn't sth. like a data1 partition. we have one data partition only that's why we need the TDB hack.
other than that it's possible but you should backup all your data and restore it afterwards.

m11kkaa said:
there isn't sth. like a data1 partition. we have one data partition only that's why we need the TDB hack.
other than that it's possible but you should backup all your data and restore it afterwards.
Click to expand...
Click to collapse
Ok got it.
So following your instructions and editing script like the following should work ?
Code:
change_table() {
ui_print "parted: delete"
parted -s /dev/block/mmcblk0 rm 23 || return 1 # system
parted -s /dev/block/mmcblk0 rm 24 || return 1 # system1
parted -s /dev/block/mmcblk0 rm 25 || return 1 # cache
parted -s /dev/block/mmcblk0 rm 26 || return 1 # userdata
parted -s /dev/block/mmcblk0 rm 27 || return 1 # storage
ui_print "parted: create"
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 336MB 1176MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 1176MB 2016MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 2016MB 2419MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 2419MB 6515MB || return 1
parted -s /dev/block/mmcblk0 mkpartfs primary ext2 6515MB 31.3GB || return 1
ui_print "parted: name"
parted -s /dev/block/mmcblk0 name 23 system || return 1
parted -s /dev/block/mmcblk0 name 24 system1 || return 1
parted -s /dev/block/mmcblk0 name 25 cache || return 1
parted -s /dev/block/mmcblk0 name 26 userdata || return 1
parted -s /dev/block/mmcblk0 name 27 storage || return 1
return 0
}
Code:
ui_print "format partitions"
for NUM in 23 24 25 26 27
do
if ! format_partition "$NUM"; then
ui_print "Failed format partition $NUM"
exit 1
fi
done
already did full backup of sdcard, i just dont know if i should disable TDB before i stat repartitioning ... I dont know how TDB works to split the data partition thats my problem :/

yes that should work.
You don't need to disable TDB because your whole data partition will be wiped and it stores the TDB configuration(that means that TDB automatically gets disabled).

Had some errors but now its working fine ..thanks

unmount sdcard in CWM. It's a bug of this script.
Nice to hear it works now.

7 days ago Phone not start because partition corrupt
Hello
First do not panic is not the fault of your script but for you experience with mi2s and partitions are the few people in the world that can save my phone.
I'm playing a game phone(Xiaomi m2s 16GB) hang and one or more partitions are corrupt (I think this is the problem). But all de documentation than i find to delete o edit partition not work. Fastboot rom installation all ok but always only start with white logo. Mirecovery works perfectly and CWM by ivan works but temporally with this command sudo fastboot boot recovery.img
This is the result of your script
check environment
/sbin/mount
/sbin/umount
/sbin/parted
/sbin/tune2fs
/sbin/e2fsck
dump old table
unmount partitions
umount: can't umount /system: Invalid argument
umount: can't umount /system1: No such file or directory
umount: can't umount /data: Invalid argument
umount: can't umount /data_root: Invalid argument
umount: can't umount /sdcard: Invalid argument
change partition table
parted: delete
parted: create
Error: Unable to satisfy all constraints on the partition.
Failed changing table
OTHER TEST
/dev/block # e2fsck -fDp /dev/block/mmcblk0p24
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
/dev/block/mmcblk0p24:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
/dev/block # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p24
tune2fs 1.41.14 (22-Dec-2010)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
Couldn't find valid filesystem superblock.
I try to delete partition and create a new one but fail.
(parted) rm 24
rm 24
(parted) mkpartfs primary ext2 872 1409
mkpartfs primary ext2 872 1409
Error: Unable to satisfy all constraints on the partition.
I FOUND THIS IN XDA FORUM BUT I HAVEN'T IMAGE TO TEST
adb push mmcblk0p19_repaired.img /tmp/
adb shell dd if=/tmp/mmcblk0p19_repaired.img of=/dev/block/mmcblk0p19
adb reboot bootloader
MY PARTITION TABLE SYSTEM1 NOT HAVE FILESYSTEM EXT4
[email protected]:~/Escritorio/recovery$ sudo adb shell parted -s /dev/block/mmcblk0 print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 89.1MB 89.1MB fat16 modem
2 89.1MB 178MB 89.1MB fat16 modem1
3 178MB 179MB 524kB sbl1
4 179MB 179MB 524kB sbl2
5 179MB 180MB 1049kB sbl3
6 180MB 181MB 1049kB rpm
7 181MB 182MB 1049kB tz
8 182MB 183MB 524kB DDR
9 183MB 187MB 4194kB aboot
10 187MB 188MB 1049kB misc
11 188MB 191MB 2990kB logo
12 191MB 192MB 799kB m9kefs1
13 192MB 193MB 799kB m9kefs2
14 193MB 193MB 1024B m9kefsc
15 193MB 201MB 8501kB bk1
16 201MB 202MB 799kB m9kefs3
17 202MB 268MB 66.3MB bk2
18 268MB 284MB 15.7MB boot
19 284MB 300MB 15.7MB boot1
20 300MB 316MB 15.7MB recovery
21 316MB 327MB 11.5MB bk3
22 327MB 336MB 8389kB ext4 persist
23 336MB 872MB 537MB ext4 system
24 872MB 1409MB 537MB system1
25 1409MB 1812MB 403MB ext4 cache
26 1812MB 5570MB 3758MB ext4 userdata
27 5570MB 15.8GB 10.2GB ext4 storage

Xiaomi Mi2 32GB
XIAOMI MI2 32GB ONLY
For those using a single MIUI ROM I've made a partition table with system1 set to 1024Mb.
Run the attached from CWM (in /tmp).

Aternus said:
XIAOMI MI2 32GB ONLY
For those using a single MIUI ROM I've made a partition table with system1 set to 1024Mb.
Run the attached from CWM (in /tmp).
Click to expand...
Click to collapse
Can you explain a little more? Does it only leave 1 system partition? Can I flash it like a regular zip?
Enviado desde mi MI 2S mediante Tapatalk

any step by step manual how to change partition? with all necessary downloads etc...
or.... is it possible to delete system2 with all its parts? - for me I'd to use system1 only

Why can not I change the size of the system partition?
Already tried several times, with disabled TDB and with enabled TDB.
Full wipe did and still no result.
P.S. I have already been able to do any repartitioning.
Code:
PS C:\Android> adb push repartition.sh /tmp
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
21 KB/s (3797 bytes in 0.169s)
PS C:\Android> adb shell chmod 0777 /tmp/repartition.sh
PS C:\Android> adb shell /tmp/repartition.sh
check environment
/sbin/mount
/sbin/umount
/sbin/parted
/sbin/tune2fs
/sbin/e2fsck
dump old table
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
unmount partitions
umount: can't umount /system: Invalid argument
umount: can't umount /system1: No such file or directory
umount: can't umount /data: Invalid argument
umount: can't umount /sdcard: Invalid argument
change partition table
parted: delete
parted: create
parted: name
format partitions
format: /dev/block/mmcblk0p23
tune2fs 1.41.14 (22-Dec-2010)
tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p23
Couldn't find valid filesystem superblock.
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p23
Possibly non-existent device?
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p23: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p23: 11/500856 files (0.0% non-contiguous), 62917/1000445 blocks
format: /dev/block/mmcblk0p24
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p24: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p24: 11/262144 files (0.0% non-contiguous), 49386/524289 blocks
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p24: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p24: 11/262144 files (0.0% non-contiguous), 49386/524289 blocks
format: /dev/block/mmcblk0p25
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p25: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p25: 11/196608 files (0.0% non-contiguous), 32935/393217 blocks
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p25: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p25: 11/196608 files (0.0% non-contiguous), 32935/393217 blocks
format: /dev/block/mmcblk0p26
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p26: 11/399200 files (9.1% non-contiguous), 28951/798348 blocks
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Adding dirhash hint to filesystem.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p26: 11/399200 files (9.1% non-contiguous), 28951/798348 blocks
Done.
PS C:\Android> adb reboot recovery
PS C:\Android>
UPD. The problem was that I was using Windows Povershell
Run the script from the command line and everything turned out.

Thanks!
I have to format first system and system1 in recovery to apply this script, because I have and error :
tmp/repartition.sh lin 115 can´t create /sdcard/parted_12_06_2014_FDFD6F4CB043F4956D9CAD053C3738AA.

DO MOUNT your SDCARD
then Follow the instruction
duhh...

I modified the script a little bit for 1 ROM usage. System1 is 840MB as in the original and System2 is 5MB. The rest goes into userdata. This is for the 16GB version.

Ok! I did again and umount the sdcard abd it worked fine.
Thanks

I found a better way
If u reboot into dload mode, u can change the partition table from your computer
The problem is that most partition managers don't support changing the GPT Partition names and that's why I added support for that to GParted.
GParted supports booting from Live CD/USB so Windows/Mac users aren't left out.
http://i.imgur.com/3SwSXs2.png
I pushed the patch to GParted repo's and I'll inform u once there're any news.

from my point of view the best way for use is:
- system (system1) - let 1024 MB
- system1 (system2) - let 10 MB
- userdata (apps) - let 4096 MB (take it from sdcard) - but maybe more