Database Users

[DISCUSSION] 1.5 GB internal storage vs 4 GB - mystery solved ?

The DZ is advertised by HTC as having 1.5 GB internal storage, but the G2 is advertised as having 4 GB. As proved via teardown pictures (see http://forum.xda-developers.com/showthread.php?t=832686 ), the two phones have exactly the same 4 GB storage chip (NAND), but both also report a lot less memory available to the user (2.1 GB seems to be there if you examine the partitioning).
This has led people to try and investigate where the "missing" memory has gone, e.g. what is using it up, can we get access to it, etc.
This "mystery" seems now to have been solved, and has been posted up in the Wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#The_Missing_2GB
A summary of this was kindly posted up by dhkr123 in the G2 forums at http://forum.xda-developers.com/showpost.php?p=9174115&postcount=22 , specifically :
There are 2.1 GB of internal storage addressable by the kernel. This piece of space is divided up into several partitions, for the radio, the SPL, the SYSTEM, the USERDATA, the CACHE, and several other things. All of these partitions are accounted for within the 2.1 GB.
What has been found is that a 1-time write deal to the eMMC is responsible for converting most of the internal storage from MLC (multi-level cell, specifically, 2 bits per cell) into SLC (single-level cell, 1 bit per cell) for the purpose of improving performance and durability.
Specifically, the entire eMMC is 4 GB, and 2.1 GB are accessible, that means that ~200 MB remains MLC, the remaining 3.8 GB is converted into SLC, offering 1.9 GB. 1.9GB + 200MB = 2.1 GB.
Mystery solved, nothing you can do about it.
But understand that it is faster and more reliable like this.
Click to expand...
Click to collapse
So apparently the hardware has been setup so that there is 2.1 GB available for storage for performance and reliability reasons, and it is unlikely this can be changed.

Just found some further explanation and diagrams on this at http://tjworld.net/wiki/Android/HTC/EMMC/UnderstandingUserCapacity

Nice post
Thanks for sharing.
Even with the "hidden" partition, huh... I have installed more apps than never and I still have near-1GB free
And I think the internal mem for process and running system is a great idea since the phone runs smoother than butter
Maybe that's why nobody's talking 'bout apps2sd, which is a common topic @ other phone's fora

How do you have near 1gb free?
CacheMate for me reports 1,078MB (1.07 GB) total data, 338MB used, 760 whatever free, not 2.1GB. Is this with a ROMed DZ, stripped of major components in the system and whatnot? (ie, Sense)

GlitchZero said:
CacheMate for me reports 1,078MB (1.07 GB) total data, 338MB used, 760 whatever free, not 2.1GB.
Click to expand...
Click to collapse
That doesn't sound right at all. But I don't know anything about CacheMate.

It's a root app, clears out the dalvik (I believe) and app caches that have built up, but it shows Total Memory, Memory Used, and Free Memory, and those are my readings, and they are consistent to .01 of a megabyte with what it says in SD & Phone Storage in my Settings.

But there's 2.1 GB total user storage on the phone, so it doesn't sound like it's reporting it correctly ?

Here's the partitioning on a DZ, taken from http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning (duplicate rows deleted, see the link for more details) :
# fdisk -ul /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders, total 4554752 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 4554750 2272311 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 137216 3072 4a Unknown
/dev/block/mmcblk0p14 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p15 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p16 145412 163326 8957+ 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 1343486 571391+ 83 Linux
/dev/block/mmcblk0p26 1343488 3577854 1117183+ 83 Linux
/dev/block/mmcblk0p27 3577856 4192254 307199+ 83 Linux
/dev/block/mmcblk0p28 4192256 4234750 21247+ 19 Unknown
/dev/block/mmcblk0p29 4234752 4235263 256 23 Unknown
If you add up the sizes of partitions 4, 25, 26 and 27 (i.e. the big ones) then there is 2.1 GB in total. I wonder if CacheMate is only looking at partition 4 (1.1 GB) and not the rest ? I could be way off though.

U8800 partition scheme.

In case this info is of use to someone...
Trying to understand what goes where,
Here is the partition table of a U8800:
#######################################
Disk /dev/sdb: 3959 MB, 3959422976 bytes
1 heads, 62 sectors/track, 124729 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 491520 245760 b W95 FAT32
/dev/sdb2 * 491521 492520 500 4d QNX4.x
/dev/sdb3 492521 498520 3000 46 Unknown
/dev/sdb4 498521 7733247 3617363+ 5 Extended
/dev/sdb5 524288 548863 12288 59 Unknown
/dev/sdb6 655360 921599 133120 4c Unknown
/dev/sdb7 1048576 1049575 500 5a Unknown
/dev/sdb8 1179648 1185791 3072 58 Unknown
/dev/sdb9 1310720 1324719 7000 50 OnTrack DM
/dev/sdb10 1441792 1447935 3072 4a Unknown
/dev/sdb11 1572864 1579007 3072 4b Unknown
/dev/sdb12 1703936 2154495 225280 83 Linux
/dev/sdb13 2228224 3457023 614400 83 Linux
/dev/sdb14 3538944 7733247 2097152 69 Unknown
#############################################
sdb1: This is the FAT32 partition that gets mounted when we boot into pink screen;
It holds, among other files, EMMCBOOT.MBN, which, if not present and as far as I've experimented, will get the phone straight into a blue screen and initiate a flash procedure if a 'dload' folder with a ROM is found in the sdcard. The contens of this partition are changed when a ROM is flashed.
sdb2: Is flagged as bootable, and holds an (so far) unknown filesystem (if any; could hold a raw binary image, for instance);
sdb3: Holds an unknown filesystem, if any. This partition is changed whenever you flash a ROM. dumping this partition back, from any 2.3BETA, to a 2.3 (B522) running phone, will get the USB pink screen mode working again, allowing acces to sdb1.
sdb5: holds an unknown filesystem if any; dumping this one back gets us the original "IDEOS" logo and, probably, whatever is needed to make previous CWM backups work again.
sdb6: ext3 filesystem with a directory called "recovery".
sdb7: Unknown filessytem, if any.
sdb8: Unknown filesystem, if any.
sdb9: Unknown filesystem, if any.
sdb10: Unknown filesystem, if any.
sdb11: Unknown filesystem, if any.
sdb12: ext3 filesystem; gets mounted at "/system".
sdb13: ext3 filesystem; gets mounted at "/data".
sdb14: vfat filesystem; represents the internal sdcard.
I'm trying to find out what needs to be restored in order to perform a clean, reliable downgrade. sdb5 is a must, but not the only one. I've flashed 2.2 and dumped it back right after. The result is an almost downgraded U8800. I say almost because charging the battery while the phone is off shows a different image (the one that comes with 2.3) and I can't power up the phone unless I take the cable out; this means there are still remnants of 2.3 somewhere...
UPDATE: Not being able to power up the phone was to due to the CWM recovery; restoring original recovery.img solved that one.

[Q] NST will not boot, lost partition table

The below post is actually a PM I sent to ros87, but it look like he hasn't been on the forums in a while, so I thought I'd ask the general populous. Besides, if I manage to get out of this one, then it might help someone else.
--------------------------
To make a long story short, I have a NST that will not boot from the internal memory. I can boot from SD card images no problem (noogie, cwm, n2T-Recovery). When I boot from noogie, I can see the internal storage.
How I managed to get here:
- tried to follow the "Backup/Restore N2E" instructions from Windows, so used MiniTool Partition Wizard to delete the NST partitions
- THEN I realized the backup I took a long time ago wasn't a full device backup, but individual partition backups:
Code:
07/14/2011 09:09 PM 79,675,392 nook_backup_BOOT.img
07/14/2011 09:41 PM 251,641,856 nook_backup_CACHE.img
07/14/2011 09:58 PM 840,941,568 nook_backup_DATA.img
07/14/2011 09:30 PM 301,973,504 nook_backup_DISK.img
07/14/2011 09:22 PM 199,229,440 nook_backup_FACTORY.img
07/14/2011 09:04 PM 251,641,856 nook_backup_NOOK.img
07/14/2011 09:19 PM 16,777,216 nook_backup_ROM.img
I wasn't having any luck with Windows-based tools, so I switched to Linux. I've attempted to rebuild the partitions and copy over the data from my backups using dd:
Code:
dd if=/home/kenny/host/Nook\ Backup/nook_backup_BOOT.img of=/dev/sdb1 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_ROM.img of=/dev/sdb2 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_FACTORY.img of=/dev/sdb3 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_DISK.img of=/dev/sdb5 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_NOOK.img of=/dev/sdb6 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_CACHE.img of=/dev/sdb7 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_DATA.img of=/dev/sdb8 bs=1M
The commands seemed to work and I do see the right kind of data in the partitions, but it still won't boot.
Here's a dump of the current state of things:
Code:
fdisk -l /dev/sdb
Disk /dev/sdb: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000001
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdb2 39 46 16384 c W95 FAT32 (LBA)
/dev/sdb3 47 141 194560 83 Linux
/dev/sdb4 142 934 1624064 5 Extended
/dev/sdb5 142 285 294896 83 Linux
/dev/sdb6 286 405 245744 c W95 FAT32 (LBA)
/dev/sdb7 406 525 245744 83 Linux
/dev/sdb8 526 926 821232 83 Linux
--------------------------
df -h
/dev/sdb5 279M 183M 94M 67% /media/boot
/dev/sdb7 233M 6.2M 224M 3% /media/cache
/dev/sdb2 16M 119K 16M 1% /media/rom
/dev/sdb3 184M 106M 77M 58% /media/factory
/dev/sdb8 790M 20K 782M 1% /media/boot_
/dev/sdb6 237M 104M 133M 44% /media/NOOK
/dev/sdb1 75M 58M 18M 78% /media/boot__
I'm not entirely sure I got the partitions created in the format or order the nook wants. Luckily, since I do have the contents of the partitions, I do feel like I can get out of this mess, but just haven't managed to find the right sequence yet.
What I'd love to try is using a good, full backup that someone else has made, and then use my individual partition backups to rewrite the sections that are unique to my nook. Unfortunately, the torrent containing the one full backup that someone posted is long dead.
So, If there's anything anyone can think of that will help me revive this thing, I'd be ever so grateful. If you need more information, I'll get it.
Thanks!!!

"What I'd love to try is using a good, full backup that someone else has
made, and then use my individual partition backups to rewrite the
sections that are unique to my nook. Unfortunately, the torrent containing
the one full backup that someone posted is long dead."
You can boot into CWR, and you can probably pull a copy of the factory.zip file from one of your restored partitions.
But I think that where you are is a fixable point at this time - somehow (perhaps because you restored partition by partition and thus weren't able to get a correct set of names tied to them) the names are wrong on some pretty important partitions - system, data and boot!
The partitions at a very fast glance look OK to me in terms of size, number and order.
This, though:
/dev/sdb5 279M 183M 94M 67% /media/boot
/dev/sdb8 790M 20K 782M 1% /media/boot_
/dev/sdb1 75M 58M 18M 78% /media/boot__
/sdb5 should be /system;
/sdb8 should be /data (I seem to remember that Linux calls it 'userdata' when the disk is mounted)
/sdb1 should be boot -- no terminal underscores.
You can rename the partitions using parted in Linux. I would start there - boot noogie, use linux parted to address the problem with partition 1. Try renaming 5 as system and 8 as userdata (I don't have the output to hand to show you exactly what this will look like in parted)
the syntax at the CLI is
(parted) name 1 boot
(parted) quit
for partition 1 to get the name boot
(but also use the parted print command to look to see what the partitions are being called by the disk. There may be others that need tuning, but it looks as if the df command actually did find out what the disk was calling the partitions, which is helpful.)
gparted may work also, and it's a little less intimidating to use if there's a rename partition command in it.
If you can get it to boot even enough to fail, your restore image should be visible to the device and it will eventually see that it's failed enough times to force a reset.

Thanks for the detailed reply!
Since I wrote the above message, I did play with the partitions a little more to get the order to better match what I found in the Nook Touch Partition Hacking thread. Here's how it looks in gParted, after I did the labeling (parted wouldn't name a FAT32 partition):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still no luck trying to boot after the renaming.
Then I tried using CWM to flash the factory.zip I was able to extract from my backup. It flashed successfully, but still no boot.
I still question my partition table a bit simply because I haven't been able to find a really good reference as to what the table on a stock Nook should look like.

Kaishio said:
I still question my partition table a bit simply because I haven't been able to find a really good reference as to what the table on a stock Nook should look like.
Click to expand...
Click to collapse
That's what I see:
fdisk -l /dev/block/mmcblk0
Code:
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 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/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 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
mount
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0

Really appreciate the responses.
...but I'm still stuck. I made my partitions match exactly what ApokrifX posted, restored from my backups, but no boot. So strange. I'll keep messing with it though.
Maybe I'll have to ninja into barnes and noble and take a full device backup of one of the display units.

Don’t really know what to suggest...
Do you see anything on the screen when it fails to boot?
Were you able to find someone else full backup?
Can you boot noggie, take full backup and try to understand what’s messed up in it by comparing?

I have a theory that all the B&N Nook products have some sort of unbrick mode built in. I have not had a chance to try with a NST but it works fine for my Nook tablet.
1. Create partition table and format partitions see how I did this here http://forum.xda-developers.com/showthread.php?t=1225196
2. set up the first partition with MLO uboot uImage and recovery
3. Get hold of a update file from B&N Site and strip the leading signapk bits and put it on a blank sdcard after renaming it as gossamer_update.zip
4 Start up the nook it should boot from internal emmc see the presence of the special update.zip on sdcard and upgrade / downgrade reinstall etc
just look at some of the posts in the B&N Tablet threads and all this stuff works on that, grepping the source for uboot on the NST gives the gossamer name

meghd00t said:
I have a theory that all the B&N Nook products have some sort of unbrick mode built in. I have not had a chance to try with a NST but it works fine for my Nook tablet.
1. Create partition table and format partitions see how I did this here http://forum.xda-developers.com/showthread.php?t=1225196
2. set up the first partition with MLO uboot uImage and recovery
3. Get hold of a update file from B&N Site and strip the leading signapk bits and put it on a blank sdcard after renaming it as gossamer_update.zip
4 Start up the nook it should boot from internal emmc see the presence of the special update.zip on sdcard and upgrade / downgrade reinstall etc
just look at some of the posts in the B&N Tablet threads and all this stuff works on that, grepping the source for uboot on the NST gives the gossamer name
Click to expand...
Click to collapse
Cool.
OR he can actually use your approach and his backup of all partition to create whole nook image as well! :good:

Thanks m. I only had a few minutes today to mess with it, and while I didn't have any success, it wasn't the best attempt. I'll do more when I have more time.
That being said, to answer ApokrifX's earlier question, I don't see anything change on the screen for a failed boot. If it said Rooted Forever before, that's what stays. If it was CWM's "rebooting" message, that's what stays.
At this point, I'm wondering, rather than trying for a full restore, if I should just focus on getting any sort of boot from emmc. So far, I've had not been able to get any response with a SD card removed. What's the simplest way to show/test any sort of boot from internal memory?

Kaishio said:
At this point, I'm wondering, rather than trying for a full restore, if I should just focus on getting any sort of boot from emmc. So far, I've had not been able to get any response with a SD card removed. What's the simplest way to show/test any sort of boot from internal memory?
Click to expand...
Click to collapse
I wish I can answer that.
Might be coping noogie.img content to first nook partition?
I would PM to mali100 to get clarification first.

ApokrifX said:
Might be coping noogie.img content to first nook partition?
Click to expand...
Click to collapse
That should work, but the boot partition has to start on the correct sector.

mali100 said:
That should work, but the boot partition has to start on the correct sector.
Click to expand...
Click to collapse
Mali,
Do you mean alignment, or something else?
I thought, it is same way everywhere:
“Disk boot sector” (Partition loader) finds first/last active partition, loads its first sector and jumps to it.
“Active partition boot sector” finds boot file by name or have its offset, loads it (partially) and jumps to it.
No idea how it works with noogie, but gotta be something similar?
Another Q:
In Kaishio case, could it be that partitions have correct sizes, but wrong offsets, thus booting process fails?

As I understand it the restrictions are
1. Geometry 128Heads * 32Sectors per track
2. 1st partition has to be type Win95 LBA
3. 1st partition has to be bootable
4. MLO has to be uppercase and the first file on the file system
I had to fiddle a long time with sfdisk to get these rules right.

Kaishio said:
Code:
fdisk -l /dev/sdb
Disk /dev/sdb: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000001
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdb2 39 46 16384 c W95 FAT32 (LBA)
Click to expand...
Click to collapse
meghd00t said:
As I understand it the restrictions are
1. Geometry 128Heads * 32Sectors per track
2. 1st partition has to be type Win95 LBA
3. 1st partition has to be bootable
4. MLO has to be uppercase and the first file on the file system
I had to fiddle a long time with sfdisk to get these rules right.
Click to expand...
Click to collapse
Looks like he had satisfied first 3 conditions.
IMO, if "MLO has to be uppercase", then bootloader is searching for it by name, so it doesn’t have to be "the first file on the file system"
---------- Post added at 04:36 PM ---------- Previous post was at 04:25 PM ----------
Funny: http://overoinfo.blogspot.com/2010/03/creating-bootable-microsd-card.html
It is very important that these three files have precisely these names and are loaded into the boot partition in a very specific order. The Overo boot loader does not use the names per-se but instead loads the FIRST installed file on the boot partition (MLO) which does look for specific name 'u-boot.bin' when it is time to load the boot loader. The boot loader also looks for the specific name uImage to load the Linux kernel.
Click to expand...
Click to collapse
I.e. only u-boot.bin and uImage names are important.
MLO has to be FIRST installed file on the boot partition.
It can have any name.

[Q&A] [SCRIPT] Fix partition table for Android 4.4

Q&A for [SCRIPT] Fix partition table for Android 4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SCRIPT] Fix partition table for Android 4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

partition table doesn' exist
On my mi3 64gb when i flash images of the miui rom, I see the msg "partition table doesn't exist" .... How I can resolve it? Thanks

Repartition Mi3
Xiaomi Mi3W 64gb
Anyone have some idea how I resolve it:
C:\Program Files (x86)\Rayglobe Mi3 One Click Tools>C:\XiaomiTool\Drivers\adb push C:\XiaomiTool\cancro\repartition64.sh /tmp
2991 KB/s (3063 bytes in 0.001s)
C:\Program Files (x86)\Rayglobe Mi3 One Click Tools>C:\XiaomiTool\Drivers\adb shell
chmod 0777 /tmp/repartition64.sh
/tmp/repartition64.sh
~ # chmod 0777 /tmp/repartition64.sh
~ # /tmp/repartition64.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 /cache: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /data_root: Invalid argument
umount: can't umount /sdcard: Invalid argument
umount: can't umount /userdata: No such file or directory
change partition table
parted: delete
Error: Partition doesn't exist.
Failed changing table
Please help me, I try the linuxxx tool but nothing! .... I try the manual adb command.... but nothing.....
Did U have other tool ??? any script ??? anything!!! ....

You're on Mi2/S section, why you used this on your Mi3?
Also on Mi3 there's no need to extend partitons.

This formatted my whole phone except sd storage, is this normal? I just restored the back up but was wondering if by doing so the repartitioning doesn't get reversed.

Can I change application storage with this script on my mi2?
Thanks

two stupid question
Sorry guys
I have two stupid question to ask.
first after I boot to CWM and mount sd card，
should I need to wipe user data and cache and davilk for this script？
second if I backup the my rom，
can I restore it in new system partition table？
Thanks guys

The filesystem
I looked into the shell script
The filesystem is ext2
Should I modify to ext4 or just leave it alone

Fresh install of script: 20 GB space lost
My device Mi2S with 32GB was bricked. I managed to install the script and it's working again with MIUI V7
Somehow it lost 20Gb of space? I don't know what to do, or how to mount everything back.
please help
--------------------------
Internal Storage (MMC)
--------------------------
* modem [mmcblk0p1] (/firmware) [vfat]
Used: 50.7 MB, Free: 34.3 MB, Total space: 85 MB
* modem1 [mmcblk0p2] Not mounted
* sbl1 [mmcblk0p3] Not mounted
* sbl2 [mmcblk0p4] Not mounted
* sbl3 [mmcblk0p5] Not mounted
* rpm [mmcblk0p6] Not mounted
* tz [mmcblk0p7] Not mounted
* DDR [mmcblk0p8] Not mounted
* aboot [mmcblk0p9] Not mounted
* misc [mmcblk0p10] Not mounted
* logo [mmcblk0p11] Not mounted
* m9kefs1 [mmcblk0p12] Not mounted
* m9kefs2 [mmcblk0p13] Not mounted
* m9kefsc [mmcblk0p14] Not mounted
* bk1 [mmcblk0p15] Not mounted
* m9kefs3 [mmcblk0p16] Not mounted
* bk2 [mmcblk0p17] Not mounted
* boot [mmcblk0p18] Not mounted
* boot1 [mmcblk0p19] Not mounted
* recovery [mmcblk0p20] Not mounted
* bk3 [mmcblk0p21] Not mounted
* persist [mmcblk0p22] (/persist) [ext4]
Used: 4.3 MB, Free: 3.7 MB, Total space: 8 MB
* System [mmcblk0p23] (/system) [ext4]
Used: 502 MB, Free: 298 MB, Total space: 801 MB
* system1 [mmcblk0p24] Not mounted
* Cache [mmcblk0p25] (/cache) [ext4]
Used: 11.2 MB, Free: 373 MB, Total space: 384 MB
* Data (userdata) [mmcblk0p26] (/data) [ext4]
Used: 2.6 GB, Free: 360 MB, Total space: 2.9 GB
--------------------------
tmpfs mount points
--------------------------
* /dev [tmpfs]
Used: 68 KB, Free: 961 MB, Total space: 962 MB
* /mnt/asec [tmpfs]
Used: 0 B, Free: 962 MB, Total space: 962 MB
* /mnt/obb [tmpfs]
Used: 0 B, Free: 962 MB, Total space: 962 MB
* /storage/emulated [tmpfs]
Used: 0 B, Free: 962 MB, Total space: 962 MB
--------------------------
Memory
--------------------------
* RAM
Used: 1 GB, Free: 873 MB, Total space: 1.9 GB

Resize all the partitions and reflash your rom

***Meizu MX4 - Partitions Table*** Need help for resize chache and system

MX4-Ubuntu Touch in Cyano
An little video tutorial : https://youtu.be/rzjF2Kiw4Ew
~ # print #show partition table
print #show partition table
/sbin/sh: print: not found
~ # 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 #shows partition table
print #shows partition table
print #shows partition table
Model: MMC BWBC3R (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 3670kB 3146kB proinfo
2 3670kB 8913kB 5243kB nvram
3 8913kB 19.4MB 10.5MB ext4 protect1
4 19.4MB 29.9MB 10.5MB ext4 protect2
5 29.9MB 30.1MB 262kB seccfg
6 30.1MB 30.5MB 393kB lk
7 30.5MB 47.3MB 16.8MB boot
8 47.3MB 64.1MB 16.8MB recovery
9 64.1MB 70.4MB 6291kB secro
10 70.4MB 70.9MB 524kB para
11 70.9MB 79.3MB 8389kB logo
12 79.3MB 89.8MB 10.5MB ext4 custom
13 89.8MB 101MB 10.9MB expdb
14 101MB 2265MB 2164MB ext4 system
15 2265MB 3003MB 738MB ext4 cache
16 3003MB 31.3GB 28.2GB ext4 userdata
17 31.3GB 31.3GB 16.8MB flashinfo
Click to expand...
Click to collapse
I can try to resize my userdata for incrise system and cache from recovery--->adb shell--->parted blalbalba
But i need an table of a normal version.

@Danj1
on recovery (philz)
-adb devices
-adb shell
-parted /dev/block/mmcblk0
-unit MB
-print
please share your table

resized my "userdata" losting 2 gb for incrise cache and system but...parted don't accept ext4 only ext2
View attachment 3554921
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Changed "system" and "cache"
View attachment 3554951
from my 32 gb this is the command after deleted 3 partition:
system: + 1 gb (+ o -)
mkpartfs system ext2 101MB 3265MB
cache: + 1 gb (+ o -)
mkpartfs cache ext2 3265MB 5003MB
userdata:- 2 gb
mkpartfs userdata ext2 5003MB 31251MB
--------------------------------------
WAIT DON'T CONSIDER IT GOOD-MY PHONE CAN'T BE FLASHED FROM RECOVERY (wiping and formatting all from recovery and try to reflash cyano )

BOOOM BABY! Wipe and Format : system, data, sd card and cache. Reflash cyano!
View attachment 3554970

@Danj1 you can do it.

Hi,
here is my current partition table:
Model: MMC 032GE4 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 3670kB 3146kB proinfo
2 3670kB 8913kB 5243kB nvram
3 8913kB 19.4MB 10.5MB ext4 protect1
4 19.4MB 29.9MB 10.5MB ext4 protect2
5 29.9MB 30.1MB 262kB seccfg
6 30.1MB 30.5MB 393kB lk
7 30.5MB 47.3MB 16.8MB boot
8 47.3MB 64.1MB 16.8MB recovery
9 64.1MB 70.4MB 6291kB secro
10 70.4MB 70.9MB 524kB para
11 70.9MB 79.3MB 8389kB logo
12 79.3MB 616MB 537MB ext4 custom
13 616MB 629MB 13.0MB expdb
14 629MB 2005MB 1376MB ext4 system
15 2005MB 2122MB 117MB ext4 cache
16 2122MB 31.3GB 29.1GB ext4 userdata
17 31.3GB 31.3GB 16.8MB flashinfo
Click to expand...
Click to collapse

Danj1 said:
Hi,
here is my current partition table:
Click to expand...
Click to collapse
mmm nice

Resized partitions to:
14 629MB 3005MB 2376MB ext4 system
15 3005MB 4005MB 1000MB ext4 cache
16 4005MB 31251MB 27246MB ext4 userdata
Click to expand...
Click to collapse
Currently doing ubuntu device flash. Will report later.
Thank you so much Naphtha. You rock!

Danj1 said:
Resized partitions to:
Currently doing ubuntu device flash. Will report later.
Thank you so much Naphtha. You rock!
Click to expand...
Click to collapse
Goodluck! :')

"$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
# boot device into fastboot mode
$ fastboot flash recovery recovery.img
# boot device into recovery
$ ubuntu-device-flash touch --device arale --channel
ubuntu-touch/stable/meizu.en"

Hi,
I tried to flash the device with ubuntu-device-flash but recovery afterwards fails. Here is the output:
ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --wipe
2015/11/25 22:09:04 Device is |arale|
2015/11/25 22:09:04 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
2015/11/25 22:09:04 Start pushing /home/user/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz to device
2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/pool/custom-xxxxx.tar.xz to device
2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2015/11/25 22:09:06 Done pushing /home/user/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz to device
2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/pool/device-xxxxx.tar.xz to device
2015/11/25 22:09:06 Done pushing /home/user/.cache/ubuntuimages/gpg/image-master.tar.xz to device
16.00 KB / 282.42 MB [_____________________________________________________________________________________] 0.01 % 79.91 KB/s 1h0m18s2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
48.00 KB / 282.42 MB [_____________________________________________________________________________________] 0.02 % 119.88 KB/s 40m11s2015/11/25 22:09:06 Done pushing /home/user/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
784.00 KB / 282.42 MB [____________________________________________________________________________________] 0.27 % 105.84 KB/s 45m24s2015/11/25 22:09:13 Done pushing /home/user/.cache/ubuntuimages/pool/custom-xxxxx.tar.xz to device
944.00 KB / 282.42 MB [_____________________________________________________________________________________] 0.33 % 94.31 KB/s 50m56s
1.19 MB / 282.42 MB [________________________________________________________________________________________________________________________________________________________________________________________________________________________________] 0.42 % 82.09 KB/s 58m28s2015/11/25 22:09:21 Done pushing /home/user/.cache/ubuntuimages/pool/device-xxxxx.tar.xz to device
282.42 MB / 282.42 MB [=================================================================================================================================================================================================================================] 100.00 % 173.64 KB/s
2015/11/25 22:36:51 Start pushing /home/user/.cache/ubuntuimages/pool/ubuntu-xxxxx.tar.xz to device
2015/11/25 22:37:29 Done pushing /home/user/.cache/ubuntuimages/pool/ubuntu-xxxxx.tar.xz to device
2015/11/25 22:37:29 Created ubuntu_command: /home/user/.cache/ubuntuimages/ubuntu_commands182902206
2015/11/25 22:37:29 Rebooting into recovery to flash
Failed to enter Recovery
Click to expand...
Click to collapse
After executing ubuntu-device-flash the device switched to blank screen and does not come up anymore. It is not booting up. If I plug it in
to power it won't show any loading screen. I tried all different key combinations (long press power/ power + vol up / power + vol down) but it doesn't wake up.
I even opened the device and disconnected the battery for some time but this didn't help either.
I will continue to get device back. So for now I can NOT recommend this way of flashing.

Back to ubuntu touch from SP Flash Tool. We can't see the name but is the same:View attachment 3555432

Naphtha said:
Back to ubuntu touch from SP Flash Tool. We can't see the name but is the same:View attachment 3555432
Click to expand...
Click to collapse
Will try this later. Must download files first.

Hi,
so here are my results. I think I bricked my phone somehow. Black screen is always present.
If I try to flash with the MTK-Flash-Tool I get the following error:
I then tried to get into fastboot mode and reflash a recovery but even this fails. If I hold power+vol down and connect to my Linux machine I see
the device popping up but I am not possible to make adb or fastboot on device. Here is the lsusb output:
[email protected]:~lsusb
...
Bus 003 Device 037: ID 0e8d:0003 MediaTek Inc. MT6227 phone
...
Click to expand...
Click to collapse
Any ideas how to recover?

First of that: $ ubuntu-device-flash touch --device arale --channel
ubuntu-touch/stable/meizu.en --wipe
have you flashed the ubuntu recovery?

Yes I installed recovery from http://people.canonical.com/~alextu/tangxi/recovery/ before using ubuntu-device-flash.