I got into random reboot these few days and I keep changing the rom
Now, sometimes, system cannot be mounted and sometimes data cannot be mounted in the recovery.
I cant flash any rom and even if I have successfully flashed a custom rom, it kept reboot randomly and usually stuck at rom's bootanimation screen
Any solution?
edwardng said:
I got into random reboot these few days and I keep changing the rom
Now, sometimes, system cannot be mounted and sometimes data cannot be mounted in the recovery.
I cant flash any rom and even if I have successfully flashed a custom rom, it kept reboot randomly and usually stuck at rom's bootanimation screen
Any solution?
Click to expand...
Click to collapse
I'm afraid that doesn't sound good. Those data & system mounts failing were exactly like mine did on the first one I had that melted down.
R.I.P
WeekendsR2Short said:
I'm afraid that doesn't sound good. Those data & system mounts failing were exactly like mine did on the first one I had that melted down.
Click to expand...
Click to collapse
Looks like there is also no usb jtag for mytouch 4g slide... :/ **sighh***
you may be ok, just reformat your partitions through fastboot or flash bootloader on top of previous. you could try
Code:
adb shell
mke2fs /dev/block/mmcblk0p25
reboot recovery
if the emmc is fried then jtag wont help anyway. there may not be jtag but that would only help with a corrupt emmc or where something was flashed improper, if this is the case see HERE
and just for fun HERE is some reading for ya, no real info, just *****ing
demkantor said:
you may be ok, just reformat your partitions through fastboot or flash bootloader on top of previous. you could try
Code:
adb shell
mke2fs /dev/block/mmcblk0p25
reboot recovery
if the emmc is fried then jtag wont help anyway. there may not be jtag but that would only help with a corrupt emmc or where something was flashed improper, if this is the case see HERE
and just for fun HERE is some reading for ya, no real info, just *****ing
Click to expand...
Click to collapse
Another problem is that I couldnt find my devices on adb while I was in bootloader
Adb only recognized my device when I was on TWRP recovery mode
:/
adb can only be used in os and recovery, when in bootloader you can use fastboot (similar but different) so that is normal
Sent from my Nexus 4 using xda premium
demkantor said:
adb can only be used in os and recovery, when in bootloader you can use fastboot (similar but different) so that is normal
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did adb shell in recovery mode
with this command
Code:
fdisk -ul /dev/block/mmcblk0
/dev/block/mmcblk0p1 * 1 256 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 257 768 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 769 65502 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 65503 4718590 2326544 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 65504 65535 16 5a Unknown
/dev/block/mmcblk0p6 65537 66048 256 73 Unknown
/dev/block/mmcblk0p7 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p8 106936 107447 256 0 Empty
/dev/block/mmcblk0p9 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p10 109498 110009 256 47 Unknown
/dev/block/mmcblk0p11 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p12 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p13 116157 116220 32 0 Empty
/dev/block/mmcblk0p14 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p15 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p16 130560 131071 256 76 Unknown
/dev/block/mmcblk0p17 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p18 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p19 229376 262143 16384 0 Empty
/dev/block/mmcblk0p20 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p21 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p22 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p23 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p24 4412899 4658641 122871+ 83 Linux
/dev/block/mmcblk0p25 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p26 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p27 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p28 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p29 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p30 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p31 4716545 4718589 1022+ 76 Unknown
/dev/block/mmcblk0p32 65504 65535 16 5a Unknown
/dev/block/mmcblk0p33 65537 66048 256 73 Unknown
/dev/block/mmcblk0p34 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p35 106936 107447 256 0 Empty
/dev/block/mmcblk0p36 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p37 109498 110009 256 47 Unknown
/dev/block/mmcblk0p38 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p39 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p40 116157 116220 32 0 Empty
/dev/block/mmcblk0p41 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p42 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p43 130560 131071 256 76 Unknown
/dev/block/mmcblk0p44 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p45 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p46 229376 262143 16384 0 Empty
/dev/block/mmcblk0p47 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p48 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p49 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p50 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p51 4412899 4658641 122871+ 83 Linux
/dev/block/mmcblk0p52 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p53 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p54 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p55 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p56 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p57 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p58 4716545 4718589 1022+ 76 Unknown
/dev/block/mmcblk0p59 65504 65535 16 5a Unknown
/dev/block/mmcblk0p60 65537 66048 256 73 Unknown
I tried
Code:
$ adb shell
~ # parted /dev/block/mmcblk0
(parted) print
I got back such error " Error: /dev/block/mmcblk0: unrecognised disk label"
Also, I tried
Code:
.... [user=248784]@ubuntu[/user]:~$ adb shell
~ # cat /proc/emmc
dev: size erase size name
mmcblk0p31: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077fde00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p27: 01400000 00000200 "devlog"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p25: 00400000 00000200 "modem_st1"
mmcblk0p26: 00400000 00000200 "modem_st2"
====================================
Then, I was thinking using the code below in adb shell but somehow i got into syntax error
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p22", "0", "/system");
/sbin/sh: syntax error: unexpected word (expecting ")") <- How to solve this syntax error?
Any way to recreate/format corrupted system/data partition so that I am able to mount system + data + cache?
fdisk -ul <- you output doesn't look good, really im thinking you may be interested in looking for a new phone... god news is you can usually find a broken doubleshot for 50 or less on ebay and then just swap boards
but still, may as well keep trying!
i think the argument is wrong, try something like
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
you could try dd commands, something like
dd if=/dev/zero of=/dev/block/mmcblk0p22
but double check this as i never trust dd commands and try not to use them
i would try to return to stock though first, or flash your bootloader through fastboot
fastboot flash hboot hboot.img (or whatever you name the hboot image)
plz help i have a samsung s5 g900 mt6572.,& i see emmc name UNKNOWN...
what's mean??
egasmith said:
plz help i have a samsung s5 g900 mt6572.,& i see emmc name UNKNOWN...
what's mean??
Click to expand...
Click to collapse
Hi,
Sad to say, your "Samsiung S5" is a clone (Sammy doesn't use MediaTek chipsets).
You should get better help over in this thread:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting > [Ask Any Question] Clone Phone Question Thread [Newbie Friendly]
Hope it helps.
Related
Hey Flashaholics,
I just S-OFFed my phone and now I got an idea...
Somehow it should be possible to change or resize the partition layout of our beloved One S's NAND, shouldn't it?
The currently active layout is like this: (adb shell buysbox df)
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 341284 48 341236 0% /dev
tmpfs 341284 0 341284 0% /mnt/secure
tmpfs 341284 0 341284 0% /mnt/asec
tmpfs 341284 0 341284 0% /mnt/obb
/dev/block/mmcblk0p33
[B] 1677156 406132 1271024 24% /system[/B]
/dev/block/mmcblk0p35
[B] 2451252 760048 1691204 31% /data[/B]
/dev/block/vold/179:36
[B]10414080 7743136 2670944 74% /storage/sdcard0[/B]
And I was always curios whether it can be changed, because I simply don't need a total of 4 gigs for /system and /data.
+2 Gigs on the storage partition are about 20% more, or in other words, my whole EU Navigon maps... :laugh:
So guys, I did not find any information about changing a NAND part. layout on google for newer phones, does it mean, that it's just not possible?
Does anyone have more knowledge than me on this?
+1 I need more storage for music/video etc etc etc..
I'd be tempted to remove them all together - or reduce the count as much as practically possible.
In 'nix land newer filesystems use a pooled approach, so you don't have to cut things up and waste space. It's heartbreaking when filesystem a is full and b is empty!
I would be fine with 1gb of Storage instead of 2gb, Also the System partition cut down by 500mb or so.
Isn't the partition information contained in the HBOOT? Now that were S-Off, can the HBOOT be edited and flashed even though the crc checksum would be invalid?
Would love to see this!
We had this on my Nexus One using a custom hboot called Blackrose. We could change the partition scheme using a fastboot command. Hope we get something similar to it on the HOS!
we were able to do it on my Nexus One with fake s-off and a hex editor
not sure why it couldn't be done--some dev must have enough interest though
we needed it on the N1 to get ICS running since phone only had 500mg internal
Here's some stuff I found, hopefully it will serve as a good starting point.
http://forum.xda-developers.com/showthread.php?t=1959691
http://forums.androidcentral.com/in...ks/118206-changing-your-partition-layout.html
Edit: Fixed wrongly pasted links.
Fixed
http://forum.xda-developers.com/showthread.php?t=1959691
1|[email protected]:/ # cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
[email protected]:/ # < command ..... deleted to protect phones and linux rigs > /dev/block/mmcblk0
The number of cylinders for this disk is set to 1908480.
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)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
1 heads, 16 sectors/track, 1908480 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 16382 130671 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16382 1908480 15136784 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16383 16384 16 5a Unknown
/dev/block/mmcblk0p6 16385 16417 256 73 Unknown
/dev/block/mmcblk0p7 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p8 18364 18396 256 5c Unknown
/dev/block/mmcblk0p9 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p10 18524 18556 256 47 Unknown
/dev/block/mmcblk0p11 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p12 18812 18940 1024 4c Unknown
/dev/block/mmcblk0p13 18940 18944 32 0 Empty
/dev/block/mmcblk0p14 18944 19712 6144 34 Unknown
/dev/block/mmcblk0p15 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p16 19840 19968 1024 0 Empty
/dev/block/mmcblk0p17 19968 25728 46080 77 Unknown
/dev/block/mmcblk0p18 25729 27008 10240 7a Unknown
/dev/block/mmcblk0p19 27009 27649 5120 0 Empty
/dev/block/mmcblk0p20 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p21 28673 30720 16384 48 Unknown
/dev/block/mmcblk0p22 30721 32768 16383+ 71 Unknown
/dev/block/mmcblk0p23 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p24 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p25 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p26 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p27 36481 36481 4 0 Empty
/dev/block/mmcblk0p28 36481 36513 256 23 Unknown
/dev/block/mmcblk0p29 36513 36515 16 0 Empty
/dev/block/mmcblk0p30 36515 36675 1280+ 0 Empty
/dev/block/mmcblk0p31 36675 36683 64 0 Empty
/dev/block/mmcblk0p32 36684 49152 99752 0 Empty
/dev/block/mmcblk0p33 49153 262144 1703935 83 Linux
/dev/block/mmcblk0p34 262145 294912 262143+ 83 Linux
/dev/block/mmcblk0p35 294913 606208 2490367+ 83 Linux
/dev/block/mmcblk0p36 606209 1908480 10418176 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p37 16383 16384 16 5a Unknown
/dev/block/mmcblk0p38 16385 16417 256 73 Unknown
/dev/block/mmcblk0p39 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p40 18364 18396 256 5c Unknown
/dev/block/mmcblk0p41 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p42 18524 18556 256 47 Unknown
/dev/block/mmcblk0p43 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p44 18812 18940 1024 4c Unknown
/dev/block/mmcblk0p45 18940 18944 32 0 Empty
/dev/block/mmcblk0p46 18944 19712 6144 34 Unknown
/dev/block/mmcblk0p47 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p48 19840 19968 1024 0 Empty
/dev/block/mmcblk0p49 19968 25728 46080 77 Unknown
/dev/block/mmcblk0p50 25729 27008 10240 7a Unknown
/dev/block/mmcblk0p51 27009 27649 5120 0 Empty
/dev/block/mmcblk0p52 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p53 28673 30720 16384 48 Unknown
/dev/block/mmcblk0p54 30721 32768 16383+ 71 Unknown
/dev/block/mmcblk0p55 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p56 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p57 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p58 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p59 36481 36481 4 0 Empty
/dev/block/mmcblk0p60 36481 36513 256 23 Unknown
Partition table entries are not in disk order
Command (m for help):
edit: I tried to change the partition type on '36 in cm10.1 and TWRP but it didn't take ( indeed I'm S-OFF ). The best approach would be to set some spare/unused partitions? (overlap is legal but not best practice).
Scared as the hboot does read files/stuff of them, that's how the bootloader screen can display your cid and radio info.
Someone please figure this out I will love you forever.
I wonder if this commit on the 4 March nightly has any impact on being able to use custom partitions?
vold: add support for ext4 media
Nope, I think it only says that access to ext4 partitions is now possible.
Now anyway, this thread looks interesting: http://forum.xda-developers.com/showthread.php?t=1959445
You could come close to the same result if you use symlinks. In fact a few One S users already do.
See http://forum.xda-developers.com/showthread.php?t=2014541&highlight=symlink
dc211 said:
You could come close to the same result if you use symlinks. In fact a few One S users already do.
See http://forum.xda-developers.com/showthread.php?t=2014541&highlight=symlink
Click to expand...
Click to collapse
I'm still using this method, but it's far from ideal. Especially when one needs to make nandroids of the /data partition, you end up with a backup that can't fit on the SD because of 1.5 GB of music in it. Being able to actually allocate those extra GBs to the SD partition would be perfect.
Guys,
Need some help. When my device failed to boot(not able to mount /cache, /data) I researched ways to resolve the issue and eventually ended up using parted and fdisk. As a result found that partition no 4 was faulty..
-------------------------------------------------------------------------------------------
~ # parted /dev/block/mmcblk0p4
parted /dev/block/mmcblk0p4
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p4
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have a partition outside the disk!
fdisk gave the following output
------------------------------------------------------------------------
~ # fdisk -ul /dev/block/mmcblk0
fdisk -ul /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2415 MB, 2415919104 bytes
1 heads, 16 sectors/track, 294912 cylinders, total 4718592 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 256 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 257 768 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 769 65502 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 65503 4718590 2326544 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 65504 65535 16 5a Unknown
/dev/block/mmcblk0p6 65537 66048 256 73 Unknown
/dev/block/mmcblk0p7 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p8 106936 107447 256 0 Empty
/dev/block/mmcblk0p9 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p10 109498 110009 256 47 Unknown
/dev/block/mmcblk0p11 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p12 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p13 116157 116220 32 0 Empty
/dev/block/mmcblk0p14 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p15 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p16 130560 131071 256 76 Unknown
/dev/block/mmcblk0p17 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p18 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p19 229376 262143 16384 0 Empty
/dev/block/mmcblk0p20 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p21 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p22 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p23 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p24 4412899 4658576 122839 83 Linux
/dev/block/mmcblk0p25 4658578 4658641 32 90 Unknown
/dev/block/mmcblk0p26 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p27 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p28 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p29 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p30 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p31 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p32 4716545 4718589 1022+ 76 Unknown
/dev/block/mmcblk0p33 65504 65535 16 5a Unknown
/dev/block/mmcblk0p34 65537 66048 256 73 Unknown
/dev/block/mmcblk0p35 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p36 106936 107447 256 0 Empty
/dev/block/mmcblk0p37 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p38 109498 110009 256 47 Unknown
/dev/block/mmcblk0p39 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p40 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p41 116157 116220 32 0 Empty
/dev/block/mmcblk0p42 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p43 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p44 130560 131071 256 76 Unknown
/dev/block/mmcblk0p45 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p46 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p47 229376 262143 16384 0 Empty
/dev/block/mmcblk0p48 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p49 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p50 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p51 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p52 4412899 4658576 122839 83 Linux
/dev/block/mmcblk0p53 4658578 4658641 32 90 Unknown
/dev/block/mmcblk0p54 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p55 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p56 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p57 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p58 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p59 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p60 4716545 4718589 1022+ 76 Unknown
Partition table entries are not in disk order
--------------------------------------------------------------------
So i went ahead and deleted partition 4 using fdisk and then parted gave out the partition table as below
~ # parted /dev/block/mmcblk0
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
print
Model: MMC MLL00M (sd/mmc)
Disk /dev/block/mmcblk0: 2416MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 132kB 131kB primary boot
2 132kB 394kB 262kB primary
3 394kB 33.5MB 33.1MB primary
--------------------------------------------------------------------------
I then re-booted the phone in bootloader and it never came back up - ofcourse what i missed was to move all other partitions up... 5 to 4, 6 to 5 etc..
I downloaded QPST as the device is now only connecting in download mode and need an Partition image file to download on the device. Can somebody please use QPST and backup partition image file and share please. I believe the same can be downloaded to the phone using QPST.
Please guide / advice if there are any other options. Have checked the full thread of HTC Unbriking project but no luck.
I was on hboot 1.29 and S-OFF.
Please help.
Missed to mention that device is Sensation XE.
Sent from my Nexus 7 using XDA Free mobile app
The partition table was fine. You nuked it. JTAG time
Keep in mind, I'm a Linux user, but just jumping blindly into Android. I have rooted the device and am running these commands with ADB (with TWRP running on the phone) as root.
When I try to run the command parted /dev/block/mmcblk0, and then print out the partition details, I get the following error message:
Code:
~ # 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
Error: Can't have overlapping partitions.
(parted)
How can I read the partition in parted, and more importantly, why am I getting this error message?
The thing is, the phone seems to be working just fine, so if there is any damage to the partition table, it does not seem to be affecting phone function in any way.
If it makes a difference, the phone is an HTC One V with firmware tailored for the Cricket wireless company, but I asked this in the general Q&A because I'm assuming this isn't phone specific, but a general Android issue.
Just in case someone needs the additional information, the phone doesn't seem to have lsblk built in, but this is the output from fdisk (and gives more warning messages that I'm not entirely familiar with):
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2432 MB, 2432696320 bytes
1 heads, 16 sectors/track, 296960 cylinders, total 4751360 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4751358 2370615 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p26 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p27 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p28 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p29 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p30 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p31 4504944 4505085 71 90 Unknown
/dev/block/mmcblk0p32 4505087 4505598 256 23 Unknown
/dev/block/mmcblk0p33 4505600 4702191 98296 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p34 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p35 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p36 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p37 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p38 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p39 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p40 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p41 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p42 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p43 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p44 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p45 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p46 163328 163839 256 76 Unknown
/dev/block/mmcblk0p47 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p48 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p49 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p50 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p51 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p52 196096 196607 256 73 Unknown
/dev/block/mmcblk0p53 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p54 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p55 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p56 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p57 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p58 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p59 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p60 4504944 4505085 71 90 Unknown
Partition table entries are not in disk order
Hi, I swiped factory reset in the advanced menu of TWRP. It seems stuck at “Formatting Data using make_ext4fs function” for about 30 minutes now. Any idea on what I should do? Should I wait longer? Thank you!
Edit: So I removed the battery without finishing it but now the recovery says "unable to mount /data". I can't flash any ROM now because it can't mount data. I tried the "mke2fs -T ext4 /dev/block/mmcblk0p23" solution both in the twrp terminal and adb but the problem still persists. Please help. Thank you.
razor26 said:
Hi, I swiped factory reset in the advanced menu of TWRP. It seems stuck at “Formatting Data using make_ext4fs function” for about 30 minutes now. Any idea on what I should do? Should I wait longer? Thank you!
Edit: So I removed the battery without finishing it but now the recovery says "unable to mount /data". I can't flash any ROM now because it can't mount data. I tried the "mke2fs -T ext4 /dev/block/mmcblk0p23" solution both in the twrp terminal and adb but the problem still persists. Please help. Thank you.
Click to expand...
Click to collapse
Hi, where did you get your TWRP recovery from?
Have you tried mkfs.ext4
Thanks for the reply, I got my TWRP recovery, I think, at the TW
RP website by searching google for Sensation. Anyway, my phone is working now by using my external sdcard as /data but I wish there's a way to recover the corrupted internal sdcard.
razor26 said:
Thanks for the reply, I got my TWRP recovery, I think, at the TW
RP website by searching google for Sensation. Anyway, my phone is working now by using my external sdcard as /data but I wish there's a way to recover the corrupted internal sdcard.
Click to expand...
Click to collapse
I think that's the bad TWRP that breaks data, everyone is using ivanich's TWRP recovery from here.
Flash ivanich's latest TWRP, boot into recovery and use adb and try with mkfs.ext4 or even mkfs.ext2
Code:
mkfs.ext4 /dev/block/mmcblk0p23
Edit: I just sent TeamWin a message explaining this and to remove download link from their site.
TWRP broken partition table
TWRP has broken my partition table. I cannot format via parted due to the fact it now has 'overlapping partitions'. No recovery can fix this including 4ext. Completely stuck at the minute. I don't want to use a microsd card as storage when I have internal storage available. Is there anyone that can help or has had any success? I am S-OFF and bootloader UNLOCKED.
Tried stock RUU via P58..zip and get's stuck part way through (I think at system or SD)
Help! I'm sure there's someone that can fix the partition table. The format of the internal storage sd is fat32 - which I believe is where the problem started from. I don't want to let this problem defeat me although I have spent an age trying to sort it...too late to give up
Any help is highly appreciated.
Cheers
I have managed to dump the partition info:
C:\Android\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6nfdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2415 MB, 2415919104 bytes
1 heads, 16 sectors/track, 294912 cylinders, total 4718592 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 256 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 257 768 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 769 65502 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 65503 4718590 2326544 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 65504 65535 16 5a Unknown
/dev/block/mmcblk0p6 65537 66048 256 73 Unknown
/dev/block/mmcblk0p7 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p8 106936 107447 256 0 Empty
/dev/block/mmcblk0p9 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p10 109498 110009 256 47 Unknown
/dev/block/mmcblk0p11 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p12 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p13 116157 116220 32 0 Empty
/dev/block/mmcblk0p14 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p15 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p16 130560 131071 256 76 Unknown
/dev/block/mmcblk0p17 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p18 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p19 229376 262143 16384 0 Empty
/dev/block/mmcblk0p20 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p21 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p22 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p23 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p24 4412899 4658576 122839 83 Linux
/dev/block/mmcblk0p25 4658578 4658641 32 90 Unknown
/dev/block/mmcblk0p26 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p27 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p28 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p29 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p30 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p31 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p32 4716545 4718589 1022+ 76 Unknown
/dev/block/mmcblk0p33 65504 65535 16 5a Unknown
/dev/block/mmcblk0p34 65537 66048 256 73 Unknown
/dev/block/mmcblk0p35 66050 106934 20442+ 0 Empty
/dev/block/mmcblk0p36 106936 107447 256 0 Empty
/dev/block/mmcblk0p37 107449 109496 1024 45 Unknown
/dev/block/mmcblk0p38 109498 110009 256 47 Unknown
/dev/block/mmcblk0p39 110011 114106 2048 46 Unknown
/dev/block/mmcblk0p40 114108 116155 1024 4c Unknown
/dev/block/mmcblk0p41 116157 116220 32 0 Empty
/dev/block/mmcblk0p42 116222 128509 6144 34 Unknown
/dev/block/mmcblk0p43 128511 130558 1024 36 Unknown
/dev/block/mmcblk0p44 130560 131071 256 76 Unknown
/dev/block/mmcblk0p45 131073 212992 40960 77 Unknown
/dev/block/mmcblk0p46 212994 229374 8190+ 74 Unknown
/dev/block/mmcblk0p47 229376 262143 16384 0 Empty
/dev/block/mmcblk0p48 262145 294912 16384 48 Unknown
/dev/block/mmcblk0p49 294914 327679 16383 71 Unknown
/dev/block/mmcblk0p50 327681 1966078 819199 83 Linux
/dev/block/mmcblk0p51 1966080 4412897 1223409 83 Linux
/dev/block/mmcblk0p52 4412899 4658576 122839 83 Linux
/dev/block/mmcblk0p53 4658578 4658641 32 90 Unknown
/dev/block/mmcblk0p54 4658643 4666834 4096 4a Unknown
/dev/block/mmcblk0p55 4666836 4675027 4096 4b Unknown
/dev/block/mmcblk0p56 4675029 4715988 20480 19 Unknown
/dev/block/mmcblk0p57 4715990 4715997 4 0 Empty
/dev/block/mmcblk0p58 4715999 4716510 256 23 Unknown
/dev/block/mmcblk0p59 4716512 4716543 16 0 Empty
/dev/block/mmcblk0p60 4716545 4718589 1022+ 76 Unknown
Partition table entries are not in disk order
~ # ←[6nfdisk
BusyBox v1.22.1 bionic (2015-03-25 05:34 +0000) multi-call binary.
Mitster2015 said:
TWRP has broken my partition table. I cannot format via parted due to the fact it now has 'overlapping partitions'. No recovery can fix this including 4ext. Completely stuck at the minute. I don't want to use a microsd card as storage when I have internal storage available. Is there anyone that can help or has had any success? I am S-OFF and bootloader UNLOCKED.
Tried stock RUU via P58..zip and get's stuck part way through (I think at system or SD)
Help! I'm sure there's someone that can fix the partition table. The format of the internal storage sd is fat32 - which I believe is where the problem started from. I don't want to let this problem defeat me although I have spent an age trying to sort it...too late to give up
Any help is highly appreciated.
Cheers
Click to expand...
Click to collapse
Have you tried hinxnz suggestion regarding mkfs? I can't try it myself , fearing that I might brick my Sensation again. I have tried the command "mke2fs -T ext4 /dev/block/mmcblk0p23" inside ivanich's twrp before , but there's still error. Don't know if the command is the same.
razor26 said:
Have you tried hinxnz suggestion regarding mkfs? I can't try it myself , fearing that I might brick my Sensation again. I have tried the command "mke2fs -T ext4 /dev/block/mmcblk0p23" inside ivanich's twrp before , but there's still error. Don't know if the command is the same.
Click to expand...
Click to collapse
Unfortunatley it has got worse, I was in abd mode, and I was looking at partitions. I finished using adb, but ejected the usb cable to quickly so I don't think it finished doing what it was doing, and now I am in QHUSB_DLOAD mode with S-OFF so I think I have fully bricked it now. Time to throw it away.
Mitster2015 said:
Unfortunatley it has got worse, I was in abd mode, and I was looking at partitions. I finished using adb, but ejected the usb cable to quickly so I don't think it finished doing what it was doing, and now I am in QHUSB_DLOAD mode with S-OFF so I think I have fully bricked it now. Time to throw it away.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1522351
or
http://forum.xda-developers.com/showthread.php?t=2775115
Tried the first link but no joy as I'm S-OFF. Also tried the unlimited.io s-off fix and still no joy.
Hello
I Found this tutorial for resizing Android partition but nothing happens:
I followed all the steps but I am missing something and cant get it work
So far I have
/system 1.6GB
/cache 255MB
/data (userdata) 2.4 GB
/sdcard 9.9GB
What I want is to give to the /data partition more 3 GB to became 5.4 GB
and /sdcard will be 6.9 GB
SystemR89 said:
[size=+2]Are you annoyied to move your apps on SD?
Are you experiencing slow down on your phone 'cause too many apps out of internal memory?
That's the solution![/size]
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead pets, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, We will
* laugh at you. Loud and hard.
*/
YOU ARE GOING TO MODIFY PHONE'S PARTITION TABLE, A WRONG STEP COULD BRICK YOUR PHONE.
PREREQUISITES:
Linux computer with Android SDK installed or a mind in order to use these instructions in a different way (different OS, partial SDK installation, ecc...)
30-60min
Backup of your apps, data and your internal memory, you have to re-flash your rom. If needed backup your "sdcard" partition (you are going to loose everything in, so also apps on sd card), maybe you could consider a nandroid backup for a disaster recovery and/or titanium backup (or equivalent) to restore your apps and settings.
INSTRUCTIONS:
Install and boot TWRP
Get a shell:
Code:
(PC) adb shell
Umount sdcard
Code:
(ADB SHELL) umount /sdcard
Open fdisk
Code:
(ADB SHELL) fdisk /dev/block/mmcblk0
Print current partition table (and save the output somewhere)
Code:
(ADB SHELL/fdisk) p
Remove sdcard and data partition:
Code:
(ADB SHELL/fdisk) d
(ADB SHELL/fdisk) 15
(ADB SHELL/fdisk) d
(ADB SHELL/fdisk) 14
Create new data partition
Code:
(ADB SHELL/fdisk) n
(First cylinder) -> you have to indicate the same start cylinder of partition 14 read in step 6
(Last cylinder) -> +8192M (this will create a 8gB partition)
Check new partition table
Code:
(ADB SHELL/fdisk) p
Create new sd partition
Code:
(ADB SHELL/fdisk) n
(First cylinder) -> you have to indicate the stop cylinder of partition 14 read in step 8 +1. If you read 292945 as stop cylinder you have to write 292946.
(Last cylinder) -> just press enter
(ADB SHELL/fdisk) t
(ADB SHELL/fdisk) 15
(ADB SHELL/fdisk) c
Write changes to partition table
Code:
(ADB SHELL/fdisk) w
"wipe" data and sdcard to format your new partitions
Push your ROM and gapps
Code:
(PC) adb push myrom.zip /sdcard/
(PC) adb push gapps.zip /sdcard/
Flash ROM and gapps
Reboot
...if everything was going successfully...
Eventually restore sdcard data
Done!
Enjoy your new big data partiton
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------
What I did is to follow the instructions
from 1 to 10 from the first post
Here the partition from df command
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 405576 20 405556 0% /dev
tmpfs 405576 16 405560 0% /tmp
/dev/block/mmcblk0p34 258012 4296 253716 2% /cache
/dev/block/mmcblk0p36 10405888 2256776 8149112 22% /sdcard
/dev/block/mmcblk0p36 10405888 2256776 8149112 22% /and-sec
~ # umount -a
umount: can't umount /tmp: Device or resource busy
umount: can't umount /sys/fs/selinux: Device or resource busy
umount: can't umount /sys: Device or resource busy
umount: can't umount /dev/pts: Device or resource busy
umount: can't umount /dev: Device or resource busy
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
df: /proc/mounts: No such file or directory
~ # fdisk /dev/block/mmcblk0
1. umount -a
2. fdisk /dev/block/mmcblk0
then type p
Disk /dev/block/mmcblk0: 15.6 GB, 15634268160 bytes
1 heads, 16 sectors/track, 1908480 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 16382 130671 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16382 1908480 15136784 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16383 16384 16 5a Unknown
/dev/block/mmcblk0p6 16385 16417 256 73 Unknown
/dev/block/mmcblk0p7 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p8 18364 18396 256 5c Unknown
/dev/block/mmcblk0p9 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p10 18524 18556 256 47 Unknown
/dev/block/mmcblk0p11 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p12 18812 18940 1024 4c Unknown
/dev/block/mmcblk0p13 18940 18944 32 0 Empty
/dev/block/mmcblk0p14 18944 19712 6144 34 Unknown
/dev/block/mmcblk0p15 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p16 19840 19968 1024 0 Empty
/dev/block/mmcblk0p17 19968 25728 46080 77 Unknown
/dev/block/mmcblk0p18 25729 27008 10240 7a Unknown
/dev/block/mmcblk0p19 27009 27649 5120 0 Empty
/dev/block/mmcblk0p20 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p21 28673 30720 16384 48 Unknown
/dev/block/mmcblk0p22 30721 32768 16383+ 71 Unknown
/dev/block/mmcblk0p23 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p24 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p25 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p26 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p27 36481 36481 4 0 Empty
/dev/block/mmcblk0p28 36481 36513 256 23 Unknown
/dev/block/mmcblk0p29 36513 36515 16 0 Empty
/dev/block/mmcblk0p30 36515 36675 1280+ 0 Empty
/dev/block/mmcblk0p31 36675 36683 64 0 Empty
/dev/block/mmcblk0p32 36684 49152 99752 0 Empty
/dev/block/mmcblk0p33 49153 262144 1703935 83 Linux
/dev/block/mmcblk0p34 262145 294912 262143+ 83 Linux
/dev/block/mmcblk0p35 294913 606208 2490367+ 83 Linux
/dev/block/mmcblk0p36 606209 1908480 10418176 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p37 16383 16384 16 5a Unknown
/dev/block/mmcblk0p38 16385 16417 256 73 Unknown
/dev/block/mmcblk0p39 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p40 18364 18396 256 5c Unknown
/dev/block/mmcblk0p41 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p42 18524 18556 256 47 Unknown
/dev/block/mmcblk0p43 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p44 18812 18940 1024 4c Unknown
/dev/block/mmcblk0p45 18940 18944 32 0 Empty
/dev/block/mmcblk0p46 18944 19712 6144 34 Unknown
/dev/block/mmcblk0p47 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p48 19840 19968 1024 0 Empty
/dev/block/mmcblk0p49 19968 25728 46080 77 Unknown
/dev/block/mmcblk0p50 25729 27008 10240 7a Unknown
/dev/block/mmcblk0p51 27009 27649 5120 0 Empty
/dev/block/mmcblk0p52 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p53 28673 30720 16384 48 Unknown
/dev/block/mmcblk0p54 30721 32768 16383+ 71 Unknown
/dev/block/mmcblk0p55 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p56 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p57 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p58 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p59 36481 36481 4 0 Empty
/dev/block/mmcblk0p60 36481 36513 256 23 Unknown
Partition table entries are not in disk order
And see the partition I need to delete
/dev/block/mmcblk0p35 294913 606208 2490367+ 83 Linux
/dev/block/mmcblk0p36 606209 1908480 10418176 c Win95 FAT32 (LBA)
---------------------------------
/data partition is 2.4 GB so dev/block/mmcblk0p35
/storage partition is 9.9 GB /dev/block/mmcblk0p36
then d
35
d
35
Because when I first delete 35 partition 36 became 35...
Next thing I am adding new parttion
after adding new partition
/dev/block/mmcblk0p59 294913 929679 5078128+ 83 Linux
This is for sd card parttion:
Command (m for help): n
First cylinder (18941-1908480, default 18941): 929680
Sector 14874864 is already allocated
First cylinder (929681-1908480, default 929681):
Using default value 929681
Last cylinder or +size or +sizeM or +sizeK (929681-1908480, default 1908480):
Using default value 1908480
And I get this
/dev/block/mmcblk0p60 929681 1908480 7830399+ 83 Linux
Then I did
Command (m for help): t
Partition number (1-60): 60
Hex code (type L to list codes): c
Changed system type of partition 60 to c (Win95 FAT32 (LBA))
And Finally I have
/dev/block/mmcblk0p59 294913 929679 5078128+ 83 Linux ===> should be /data
/dev/block/mmcblk0p60 929681 1908480 7830399+ c Win95 FAT32 (LBA) => should be /sdcard
And then I did
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
Everything so far is good
The problem now is how to deal with step 11 ===> "wipe" data and sdcard to format your new partitions
I have searched in the forum and I found this comment http://forum.xda-developers.com/show...&postcount=446
It says 8) "wipe" data and sdcard to format your new partitions. (May require to mount the SDCARD)
I am trying to mount the partitions
~ # mount -a
mount: mounting /dev/block/mmcblk0p34 on /cache failed: No such file or directory
mount: mounting /dev/block/mmcblk0p35 on /data failed: No such file or directory
mount: mounting /dev/block/mmcblk0p33 on /system failed: No such file or directory
mount: mounting /dev/block/mmcblk0p36 on /sdcard failed: No such file or directory
mount: mounting /usb-otg on vfat failed: No such file or directory
When I check back
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 16382 130671 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 16382 1908480 15136784 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16383 16384 16 5a Unknown
/dev/block/mmcblk0p6 16385 16417 256 73 Unknown
/dev/block/mmcblk0p7 16417 18364 15577+ 5b Unknown
/dev/block/mmcblk0p8 18364 18396 256 5c Unknown
/dev/block/mmcblk0p9 18396 18524 1024 45 Unknown
/dev/block/mmcblk0p10 18524 18556 256 47 Unknown
/dev/block/mmcblk0p11 18556 18812 2048 46 Unknown
/dev/block/mmcblk0p12 18812 18940 1024 4c Unknown
/dev/block/mmcblk0p13 18940 18944 32 0 Empty
/dev/block/mmcblk0p14 18944 19712 6144 34 Unknown
/dev/block/mmcblk0p15 19712 19840 1024 36 Unknown
/dev/block/mmcblk0p16 19840 19968 1024 0 Empty
/dev/block/mmcblk0p17 19968 25728 46080 77 Unknown
/dev/block/mmcblk0p18 25729 27008 10240 7a Unknown
/dev/block/mmcblk0p19 27009 27649 5120 0 Empty
/dev/block/mmcblk0p20 27649 28672 8190+ 74 Unknown
/dev/block/mmcblk0p21 28673 30720 16384 48 Unknown
/dev/block/mmcblk0p22 30721 32768 16383+ 71 Unknown
/dev/block/mmcblk0p23 32769 32896 1022+ 76 Unknown
/dev/block/mmcblk0p24 32896 33408 4096 4a Unknown
/dev/block/mmcblk0p25 33409 33920 4096 4b Unknown
/dev/block/mmcblk0p26 33921 36481 20480 19 Unknown
/dev/block/mmcblk0p27 36481 36481 4 0 Empty
/dev/block/mmcblk0p28 36481 36513 256 23 Unknown
/dev/block/mmcblk0p29 294913 929679 5078128+ 83 Linux
/dev/block/mmcblk0p30 929681 1908480 7830399+ c Win95 FAT32 (LBA)
When I flash with again I am with 2.4 GB /data and 9.9GB /sdcard
Can someone help me out with this, because I am sure that I am missing something little thing to get it work
If you're re-flashing using the HTC RUU's, it will override any chances you've made.
Renan Lazarotto said:
If you're re-flashing using the HTC RUU's, it will override any chances you've made.
Click to expand...
Click to collapse
I reflash the with TWRP version 3....
The problem I have after step 10, I am not able to mount back to follwing partitions, to be able to format it with the changed partition table.....
/dev/block/mmcblk0p33 49153 262144 1703935 83 Linux ====> /system
/dev/block/mmcblk0p34 262145 294912 262143+ 83 Linux ====> /cache
/dev/block/mmcblk0p35 294913 606208 2490367+ 83 Linux ====> /data
/dev/block/mmcblk0p36 606209 1908480 10418176 c Win95 FAT32 (LBA) ====> /sdcard