Database Develop

[Dev] Research on native ext4 partition

* Update * - 02/28/2012
I had a little chat with one of Archos dev, he told me that mmcblk0p3 was his gift for us!
So, what does it mean:
1) Archos is very developer friendly. We've known that already, but having them leaving us such entries in their tablet is very nice to see!
2) He told me that mmcblk0p3 isn't and won't be used by Archos firmware, we're completely free to use it like we want with SDE
3) With this partition, we can do very nice things, see below
Here is what can be done:
1) delete p3 and p4
2) recreate p3 as extended with any size we want
3) recreate p4 with what remains.
4) on extended p3, we can create p5, p6, ...
I did that on mine, I now have a 8 MB p5 for cwmod, a 380M p6 for rootfs+system, without any interference with stock firmware!
If someone wants to experiment with that, few advices:
- Be careful when you re-create p3 and p4, there is an empty space that should remain empty in the partition table (it contains bootloader). So when you recreate p3, you have to use the same start sector as before, not the one proposed by default.
- When you re-create p4, make sure that you use end of p3 + 1 as start for the same reason.
- Don't do fdisk if you have partition mounted, it would confuse kernel and could be dangerous. You need a specific initramfs to be able to do that.
- This is still very dangerous, be warned! invalid partition table and your tablet is toaster. Only change it if you know exactly what you're doing
As a sample, here is my current partition table:
Code:
Disk /dev/block/mmcblk0: 7457 MB, 7457472512 bytes
4 heads, 16 sectors/track, 227584 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1605 51200+ 83 Linux
/dev/block/mmcblk0p2 1605 10760 292969+ 83 Linux
/dev/block/mmcblk0p3 10760 22967 390625+ 5 Extended
/dev/block/mmcblk0p4 22967 227584 6547764 83 Linux
/dev/block/mmcblk0p5 10760 11004 7813 83 Linux
/dev/block/mmcblk0p6 11004 22967 382796+ 83 Linux
------------
Previous text:
Hello All,
As I saw some interest in running firmware directly from ext4 partition, I'd like to share what I found out while I was toying with my tablet:
Having ext4 on gen9 is not as easy as gen8: gen8 has two virtual mmcs on top of a single physical mmc with a split managed at kernel level. So what was done was to reduce storage partition to add ext4 system and/or data partition. More, on gen8, SDE exports storage mmc as a disk to the host allowing resizing partitions in linux for instance.
We can't do that on Gen9: Gen9 has a single physical mmc, part 1 is rawfs, part 2 is system and too short to have unpacked system, part 3 is a very small unused small one, part 4 is data.
On top of part 4, there is an Archos specific trick that remaps /data/media to /storage, explaining why we don't have the same limit on data partition and that /data and /storage are sharing same space. And SDE doesn't export disk.
BIG WARNING BEFORE TRYING ANYTHING: DON'T TOUCH PARTITION 1, NEVER. If partition 1 is trashed or damaged, device is bricked definitively.
So, what is possible is to trash part 2, 3, 4 and re-create a different layout or trash part 4, create two or three extended partitions instead.
If you go option 1, it would have to be done completely from an initrd as you would kill the os you're running on . Option two could be done from adb if Android is properly stopped, but I didn't test it and don't know if kernel and/or Android are behaving well with extended partitions.
Personally, I did it a third way, I modified archos recovery: recovery has a special code that repartition disk if things goes very bad. I changed partition layout builded there, then trashed my partitions and go to recovery to have it re-created. This method has advantages, the partition layout is permanent, meaning that if for some reason I trash one partition it will be re-created with the right size.
However, it has many disadvantages: You have to be able to flash rawfs to be able to flash a recovery, and it's a bit hectic and dangerous to force the partition re-creation. That's why I didn't share it and probably won't as you really need to know what you're doing if you don't want a big brick.
Last thing, I didn't see that much improvement in speed compared to other methods like having a loopback on internal storage, not sure it's really worth the effort and the risks. I did it because I don't like loopbacks, but frankly, having it done safely is much efforts.

Good post.
Thanks for the information

it is great

Hi letama,
interesting thread again
letama said:
Having ext4 on gen9 is not as easy as gen8: gen8 has two virtual mmcs on top of a single physical mmc with a split managed at kernel level. So what was done was to reduce storage partition to add ext4 system and/or data partition. More, on gen8, SDE exports storage mmc as a disk to the host allowing resizing partitions in linux for instance.
Click to expand...
Click to collapse
Nothing to add...
I found out that a second mbr is placed at the beginning of the "virtual" mmc block device 1. So the internal eMMC chip of the Gen8 devices additionally requires a special layout.
letama said:
We can't do that on Gen9: Gen9 has a single physical mmc, part 1 is rawfs, part 2 is system and too short to have unpacked system, part 3 is a very small unused small one, part 4 is data.
Click to expand...
Click to collapse
Going down to hardware level, it seems that Archos went back to use raw NAND flashes instead of eMMC for the Gen9 devices.
I found a FCC document of the Archos 80 G9 showing one 8GByte NAND flash device placed on the mainboard.
Could be a prototype as well...
Additionally it could be possible, that the mtd block layout is already handled inside bootcode.
Anyway, what does a cat /proc/partitions print out?
Regards,
scholbert

/proc/partitions:
Code:
major minor #blocks name
7 0 159412 loop0
179 0 7282688 mmcblk0
179 1 51200 mmcblk0p1
179 2 195359 mmcblk0p2
179 3 7840 mmcblk0p3
179 4 7028160 mmcblk0p4

Hi Scholbert,
scholbert said:
interesting thread again
Click to expand...
Click to collapse
Thanks!
scholbert said:
Nothing to add...
I found out that a second mbr is placed at the beginning of the "virtual" mmc block device 1. So the internal eMMC chip of the Gen8 devices additionally requires a special layout.
Click to expand...
Click to collapse
Well, kind of, it's not really a special layout. From userspace linux point of view, the two virtual mmcs are regular disks, they could be formatted, partitioned, etc.
The mmc driver is doing all the "magic" (mmc_block.split kernel command line parameter):
- for virtual mmc0, virtual sector is mapped to physical sector 0 - split
- for virtual mmc1, virtual sector is mapped to physical sector split - end.
So, the second mbr is coming from a regular disk initialization, nothing special.
scholbert said:
Going down to hardware level, it seems that Archos went back to use raw NAND flashes instead of eMMC for the Gen9 devices.
Click to expand...
Click to collapse
We're still eMMC afaik.
scholbert said:
Additionally it could be possible, that the mtd block layout is already handled inside bootcode.
Click to expand...
Click to collapse
No, gen9 has regular partition scheme, I was able to repartition it without problem... The only difficulty is to do it without killing the device by accident as if you want to keep the 4 partitions layout, you have to kill system and data (and data means also internal storage) partitions, be sure that you don't kill rawfs partition in the process then rebuild them.
Nothing very complicated per se, I would do a ram only initrd with backup of system/data/storage via adb or on microsd. However, as microsd slot is not completely stable for me, the fullly automated option is a bit risky.
My /proc/partitions is this now
Code:
major minor #blocks name
179 0 7282688 mmcblk0
179 1 51200 mmcblk0p1
179 2 439487 mmcblk0p2
179 3 7840 mmcblk0p3
179 4 6784032 mmcblk0p4

Hi Letama,
I see you have modify your part scheme but mmcblk0p2 is your android root part (like loop img) ?
You have rewrite your bootloader ? or just android kernel/initramfs (not SDE kernel/initramfs) ?
Have a nice day !
Thaolia

Hi Tha0lia,
Yes, my p2 is now rootfs+system, it's the content of the img, but directly on the partition, formatted as ext4.
No, it's not the bootloader, bootloader doesn't know anything about partition layout.
Like I explained, I did it by patching the recovery as it will recreate partitions if it detects if a partition is missing. Then, I deleted my system and data partition, rebooted in recovery to have it recreate the whole disk. Last was to modify SDE/Main kernel initrd to mount this partition instead of the loopback device.
You can't do this if you don't have a tool to flash recovery/main kernel. I wrote one, but as it's very dangerous for the tablet, I'm reluctant to let it out.
Back on the subject, this is something that could be done with sde only with a properly written initrd. The only downside is that if for some reason recovery detects a partition problem, it will revert to the old layout, but it should work. The other downside is that "stock boot" on main kernel will only work if you dedicate enough space to hold both the squashfs and the rootfs files. Mine doesn't have too as I modified also stock boot, but again, to do that, you need to flash rawfs init file and special flasher.
I don't have enough time (and energy, enough formats these days ) to do the SDE initrd right now, we'll see if someone takes the baby and if it's really worth it.

Woaw ! Good work ! Thanks for the complementary informations.
So my hack ("abcbox reboot_into -s sde" at boot) is more secure than flash rawfs if i have understood well.
Last question (sry ^^"), but do you have made a serial connection with your tablet for debugging or dev your rawfs flasher ?

letama said:
Well, kind of, it's not really a special layout. From userspace linux point of view, the two virtual mmcs are regular disks, they could be formatted, partitioned, etc.
The mmc driver is doing all the "magic" (mmc_block.split kernel command line parameter):
- for virtual mmc0, virtual sector is mapped to physical sector 0 - split
- for virtual mmc1, virtual sector is mapped to physical sector split - end.
So, the second mbr is coming from a regular disk initialization, nothing special.
Click to expand...
Click to collapse
Yeah sure, i just wanted to point at that mbr...
letama said:
We're still eMMC afaik.
Click to expand...
Click to collapse
Considering the device names it seems eMMC is used, makes sense as this is newer/better technology.
Maybe the FCC doc is of interested.
See attachment... on this device a NAND flash (H27UCG8UDA) is used.
This is definitely raw NAND.
So maybe this is a pre-series model...
letama said:
No, gen9 has regular partition scheme, I was able to repartition it without problem... The only difficulty is to do it without killing the device by accident as if you want to keep the 4 partitions layout, you have to kill system and data (and data means also internal storage) partitions, be sure that you don't kill rawfs partition in the process then rebuild them.
Nothing very complicated per se, I would do a ram only initrd with backup of system/data/storage via adb or on microsd. However, as microsd slot is not completely stable for me, the fullly automated option is a bit risky.
Click to expand...
Click to collapse
Your power supply should be fail-safe at this point
letama said:
My /proc/partitions is this now
Code:
major minor #blocks name
179 0 7282688 mmcblk0
179 1 51200 mmcblk0p1
179 2 439487 mmcblk0p2
179 3 7840 mmcblk0p3
179 4 6784032 mmcblk0p4
Click to expand...
Click to collapse
Yeah cool stuff... still on my Gen8 though.
Keep on hackin'
scholbert

So my hack ("abcbox reboot_into -s sde" at boot) is more secure than flash rawfs if i have understood well.
Last question (sry ^^"), but do you have made a serial connection with your tablet for debugging or dev your rawfs flasher ?
Click to expand...
Click to collapse
Yes, the reboot_into -s sde is a good solution to keep booting on sde...
Unfortunately, no, I don't have serial connection. I'd love to have one, not really for rawfs flashing, it's not that difficult, but more for kernel dev, it would help a lot. But opening stuff and soldering things is not my best skill, I'm a bit reluctant to do it yet, at least without a backup device handy

Hi Scholbert!
scholbert said:
See attachment... on this device a NAND flash (H27UCG8UDA) is used.
This is definitely raw NAND.
So maybe this is a pre-series model...
Click to expand...
Click to collapse
Yes, maybe... Someday I'll get the courage to open up this thing, I'm sure
scholbert said:
Your power supply should be fail-safe at this point
Click to expand...
Click to collapse
Better be!
Well, in fact, it's not such a big deal if it crashes in the middle, recovery will handle partition rebuild, but oups, reformat, flash again stock, re-root, re-enable sde, reflash sde initrd, retry, .... better be.
Yeah cool stuff... still on my Gen8 though.
Click to expand...
Click to collapse
Good news coming from this front

A little up, I updated first post with some news...

Nice
So what are default (safe) offsets?

gen_scheisskopf said:
Nice
So what are default (safe) offsets?
Click to expand...
Click to collapse
Well, don't do anything before end of mmcblk0p2 end block (10760 if you stay in default fdisk mode). Check your partition table before to get the proper value, mine is not a good example as it has been resized before to 300M, normal is 200M.
Basically, get your current mmcblk0p3 start and reuse this number (you may need +1, but fdisk will adjust)

Hey letama,
i'm in with my new A80 G9.
Quite nice device, but also suffering a little on this display issue.
Don't care much because... you may guess it already... i'm going to look inside the next days.
I'm a bit afraid though, because everything is held together with these plastic clamps. Hopefully i'm not gonna break anything.
Anyway a new thread will be born soon and i'll report my findings (boot_mode signals & other stuff ).
Enough small talk...
As you pointed out you are using a real ext4 partition already.
This might be my plan as well, because i don't like this loop mounting on real devices as well.
Yesterday i installed the latest ICS ext4 image file from surdu_petru.
So if i understand it correct this attempt is basically pretty similar to SDE image on Gen8.
If i got it right stock (unrooted squashfs image) and custom (rooted ext4 image) share the same data partition in this case.
What if we reduce size of mmcblk0p4 to increase mmcblk0p3, put our custom rootfs in it as a real filesystem.
Why did you increase mmcblk0p2 instead... in this case we'll have to wipe the stock image completely, right?
So no dual boot anymore...
Could you leave some thoughts on this?
Best regards,
scholbert

Hi Scholbert,
scholbert said:
i'm in with my new A80 G9.
Quite nice device, but also suffering a little on this display issue.
Don't care much because... you may guess it already... i'm going to look inside the next days.
Click to expand...
Click to collapse
Cool! Nice to have you onboard with g9!
Yesterday i installed the latest ICS ext4 image file from surdu_petru.
So if i understand it correct this attempt is basically pretty similar to SDE image on Gen8.
If i got it right stock (unrooted squashfs image) and custom (rooted ext4 image) share the same data partition in this case.
Click to expand...
Click to collapse
You purchased SD or HD model ?
Anyway, no, on both models, squashfs.secure is on p2 system partition, rooted ext4 is on data on p4 (internal storage is also on data for SD model) .
What if we reduce size of mmcblk0p4 to increase mmcblk0p3, put our custom rootfs in it as a real filesystem.
Click to expand...
Click to collapse
Yes, that's what I did. You can use p3 as ext4 directly, or you can use p3 as extended and create 3 partitions into this extended partition like I did. Check first post at the top, you'll see that, p3 extended, with p5, p6, p7 (p8 doesn't work). Benefit is that you dual boot on two custom rom and I needed a separate cache partition for clockworkmod recovery.
Why did you increase mmcblk0p2 instead... in this case we'll have to wipe the stock image completely, right?
So no dual boot anymore...
Click to expand...
Click to collapse
This was my first tentative, it was before Archos told me that p3 is for us and that we can do whatever we want with it. As I didn't know that, I didn't touch p3, extended p2, and put both squashfs.secure and my unpacked rooted build on it. Dual boot was working, but it's less elegant than what I currently have.
PS: if you do that, be careful when you reformat p4, you have to leave unused blocks at the end for drm I guess. Check recovery, it has the math.
If you want, I can give you my script to do it. I can even give you my ram only initrd with adb+cwm, you can then umount everything from adb then re-partition and format properly. Without ram only, you won't be able to umount and kernel will not refresh partition table.
PPS: careful with empty space for bootloader

Hey letama!
letama said:
You purchased SD or HD model ?
Click to expand...
Click to collapse
SD model, don't like moving parts in mobile devices.
letama said:
Anyway, no, on both models, squashfs.secure is on p2 system partition, rooted ext4 is on data on p4 (internal storage is also on data for SD model) .
Click to expand...
Click to collapse
Yeah sure... i refered to the loop mount of an ext4 file.
I knew it got stored on p4, so this partition is used for different purpose then and no fat anymore.
letama said:
Yes, that's what I did. You can use p3 as ext4 directly, or you can use p3 as extended and create 3 partitions into this extended partition like I did. Check first post at the top, you'll see that, p3 extended, with p5, p6, p7 (p8 doesn't work). Benefit is that you dual boot on two custom rom and I needed a separate cache partition for clockworkmod recovery.
Click to expand...
Click to collapse
Mmmh o.k. tweaking p3 and p4 would be sufficient i guess.
After shrinking p4, it would be a nice idea to use:
p3 = extended
p5 = system
p6 = data (seperated for the custom system)
Some mountpoints will have to be tweaked then...
letama said:
This was my first tentative, it was before Archos told me that p3 is for us and that we can do whatever we want with it. As I didn't know that, I didn't touch p3, extended p2, and put both squashfs.secure and my unpacked rooted build on it. Dual boot was working, but it's less elegant than what I currently have.
Click to expand...
Click to collapse
O.k. got it. I agree that p3 is a gift.
letama said:
PS: if you do that, be careful when you reformat p4, you have to leave unused blocks at the end for drm I guess. Check recovery, it has the math.
Click to expand...
Click to collapse
Thanks for the hint, i'll step through the scripts first
letama said:
If you want, I can give you my script to do it. I can even give you my ram only initrd with adb+cwm, you can then umount everything from adb then re-partition and format properly. Without ram only, you won't be able to umount and kernel will not refresh partition table.
Click to expand...
Click to collapse
Would be helpful indeed, thanks a lot for offering need my mail address.
May send you a PM.
letama said:
PPS: careful with empty space for bootloader
Click to expand...
Click to collapse
Thanks for the warning but i'm aware of this Archos specialty.
Best regards,
scholbert

scholbert said:
Mmmh o.k. tweaking p3 and p4 would be sufficient i guess.
After shrinking p4, it would be a nice idea to use:
p3 = extended
p5 = system
p6 = data (seperated for the custom system)
Click to expand...
Click to collapse
Don't forget about /cache- CWM needs it.
Or /cache as ramdisk?
scholbert said:
Some mountpoints will have to be tweaked then...
Click to expand...
Click to collapse
Only in kernel init, stock recovery won't touch p3 and p5-7 unless partition table would have to be rebuild (BTW- in ICS p2 size is increased from 200 to 300 MB)

gen_scheisskopf said:
Don't forget about /cache- CWM needs it.
Or /cache as ramdisk?
Click to expand...
Click to collapse
Yeah maybe better preserve some additional bytes.
Tough i won't use CWM for now.
gen_scheisskopf said:
Only in kernel init, stock recovery won't touch p3 and p5-7 unless partition table would have to be rebuild (BTW- in ICS p2 size is increased from 200 to 300 MB)
Click to expand...
Click to collapse
O.K. i see...
Interesting fact about p2.
To my surprise i'm still on ~200MB for p2 while running ICS on my pad.
The console gives me disk usage of 94% for p2 though.
Did it like this:
- my device came with HC installed
- used the temp root
- activated SDE by flashing letama's kernel and initramfs
- removed temp root
- rebooted into recovery
- removed stock HC, by wiping all related partitions
- installed stock ICS from recovery
- booted into stock ICS
- transfered rooted ICS ext4 image to p4
- rebooted to recovery
- used developer edition menu to reflashed the related kernel and initramfs
In the end i got dual-boot via recovery... stock and custom rooted
Something to be afraid of?
Regards,
scholbert

[Q] Confusing Between This ROM's

Can someone expert here explain it to me what is the different between THIS ROM and THIS ONE right here.I am so confusing about this.And what about the partitions means?
Thank You..
Best Regards:good:

Eddicts said:
Can someone expert here explain it to me what is the different between THIS ROM and THIS ONE right here.I am so confusing about this.And what about the partitions means?
Thank You..
Best Regards:good:
Click to expand...
Click to collapse
afaik
Unofficial ( this with orginal layout)
Have /system /cache & /datadata partitions on 460mb onenand chip, whats in overal meaning your /datadata partition cannot be bigger than 200-250 mb , cause of required space for /system
in offcial cm10 ther is modded partition layout which moves /system partition on the chip of /data which is much bigger..
so /datadata pratition can be hudge (~450mb ) at cost of some really unused speca of /data

And that's why i'm having some problem regarding my installed app on sd?When i moved my app on internal sd the icon show up as android robot icon.Is there a way to fix this..?

Eddicts said:
And that's why i'm having some problem regarding my installed app on sd?When i moved my app on internal sd the icon show up as android robot icon.Is there a way to fix this..?
Click to expand...
Click to collapse
Propably, because swiching partition layouts is quite invasible, and may corupt data. Thats why there was in istalation instructions to do a backup.
And then wipe (making clean instalation), nextly if this was titanium or sth like this you can easly restore it..
Now you can try rebot recovery > fix permissions (may work, may not)
Sec way not tested: download the .apk file of app you want to fix from anywhere, then using root explorer can be even es file explorer, then copy dowloaded app with correct name same as is currently on data partition, and now overite corupted one by this wat you dowloaded (more complicated but easy anyway, and amy work for you

Thanks man,But sorry..Me still noob here.Cant get the mean,Still don't understand why should it have the partition for this even tho the galaxy s got internal sd worth 13gb.Don't tell me that when i downloaded some app and it will install it in phone memory?and if the phone memory were less when i moved it to internal sd i will get these error?was it?

unofficial have 1.8G for data (apps), and no /datadata because if you have fast inand ship you dont need it
official have 1.4G /data (apps) and /datadata 460mb , this is good for old slow movinand ship

Noumen said:
unofficial have 1.8G for data (apps), and no /datadata because if you have fast inand ship you dont need it
official have 1.4G /data (apps) and /datadata 460mb , this is good for old slow movinand ship
Click to expand...
Click to collapse
Thanks bro,But what is /datadata?what does it do..?what is inand?

Here i have attach the screenshot that shows error where some app that i have installed in internal sd got this error.See pic below please.How do i fix this..?:crying:

/datadata is placed on the fast onenand ship of sgs (because movinand is slow), so that makes your apps run smoother
however because inand is fast , there is no need for this partition, hense all the 1.8g is used for data (apps)

Eddicts said:
Thanks bro,But what is /datadata?what does it do..?what is inand?
Click to expand...
Click to collapse
/datatata partition is place wheres apps stores their data ( settings, game progres, sms's etc)
so if you are doing sth with system or partition layout, data can be corupted,
inand is kind of flash drive in sgs it is usualy 8gb chip and 512mb onenand chip

Repartition + FUSE in the next build of CM10

Hello,
I think it would be interesting in the next buid of CM10 implement FUSE.
For those not familiar with FUSE, this makes the EMMC (Internal) and DATA partitions are one.
FUSE is the standard in new android devices like the Galaxy S3.
With this gain in space, since both would have 6.7 GB of user data (photos for example) and for applications.
This would require using a repartitioning and as it should be, we could give more space to the partition and Partition System Cache.
I made a build with FUSE on, and doing great. It should be a standard in CM10 for P990.
A greeting and I apologize for the translation.

no thanks, i really like having my system and sd card separated...

60nine said:
no thanks, i really like having my system and sd card separated...
Click to expand...
Click to collapse
Sorry, SDCARD is the defaul name for internal.
FUSE = (Internal EMMC + DATA)
Without FUSE:
Partition 8 = DATA [1,5GB]
Partition 9 = EMMC [5,3 GB]
With FUSE only have:
Partition 8 = USERDATA [6,8 GB]
The user can see 6,8 GB in Internal SD

Sounds good but will it work,
If you want the CM team to pick it up you will have to talk with them directly.
Good luck
Sent from my LG-P990 using xda app-developers app

Tamps said:
Sounds good but will it work,
If you want the CM team to pick it up you will have to talk with them directly.
Good luck
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Only change two files, and they here in the p990 repo.
Other solution is clone a p990, change two files and create a p990-fuse repo.

why would i fuse those two partitions? they are fine like they are now.
if i want to format the internal storage without affecting apps data i can while i'm using the actual partitions set, i cannot with the new mixed one.
this fuse leads what advantages?

pidocchio said:
why would i fuse those two partitions? they are fine like they are now.
if i want to format the internal storage without affecting apps data i can while i'm using the actual partitions set, i cannot with the new mixed one.
this fuse leads what advantages?
Click to expand...
Click to collapse
- You can format only DATA, and can format only EMMC too with FUSE with CWM.
- When you use a file manager, you see the same that without FUSE but you have 6,7GB.
- You can install 6,7 GB of APP.
- FUSE is ANDROID standard. All new Android devices use FUSE.

sounds great. make a flashable zip, we'll start using it

Sure
I'd give it a try i have a device i can use for testing

Ok,
I'll upload a zip with NVFlash and partitions.
Anyone can upload misc and lgdrm partitions?
Open Terminal
su
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/misc.img
dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/lgdrm.img
After doing this, in the internal memory of the device, there should be two new files: lgdrm.img and misc.img.
Screenshot:
http://imageshack.us/photo/my-images/90/screenshot2012110410465.png/
http://imageshack.us/photo/my-images/12/screenshot2012110410462.png/

ProgMaq said:
Ok,
I'll upload a zip with NVFlash and partitions.
Anyone can upload misc and lgdrm partitions?
Open Terminal
su
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/misc.img
dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/lgdrm.img
After doing this, in the internal memory of the device, there should be two new files: lgdrm.img and misc.img.
Screenshot:
http://imageshack.us/photo/my-images/90/screenshot2012110410465.png/
http://imageshack.us/photo/my-images/12/screenshot2012110410462.png/
Click to expand...
Click to collapse
misc.img: http://www.mediafire.com/?ik7gq8ddxxx0ujz
lgdrm.img: http://www.mediafire.com/?mf6oe0mio7xh9g9
I hope they are useful

Very thanks Chuck Bartowski
But your lgdrm.img is empty when mount.
This occurs when you have used nVFlash, not a problem, but I would like the original partition lgdrm compare with mine.
Anyone can upload original misc and lgdrm.
Thanks.

What about usb storage(internal storage) mounting after FUSING ?
Will it work as before ?
Sent from my Galaxy Nexus using xda premium

ProgMaq said:
Very thanks Chuck Bartowski
But your lgdrm.img is empty when mount.
This occurs when you have used nVFlash, not a problem, but I would like the original partition lgdrm compare with mine.
Anyone can upload original misc and lgdrm.
Thanks.
Click to expand...
Click to collapse
Ok, sorry, I didn't know.
I have reflash 10b with NVflash ( stock partition ), ROOT and Recovery, and I have flash cm10.
misc.img: http://www.mediafire.com/?1n0pmdbembdeorr
lgdrm.img: http://www.mediafire.com/?dan8jpucxjdw4ok

Chuck Bartowski said:
Ok, sorry, I didn't know.
I have reflash 10b with NVflash ( stock partition ), ROOT and Recovery, and I have flash cm10.
misc.img: http://www.mediafire.com/?1n0pmdbembdeorr
lgdrm.img: http://www.mediafire.com/?dan8jpucxjdw4ok
Click to expand...
Click to collapse
Thanks again, but even installing the stock version, the misc partition lgdrm and do not return to be the same (missing files)
What about usb storage(internal storage) mounting after FUSING ?
Will it work as before ?
Click to expand...
Click to collapse
Working same
Good news, I have uploaded the file. Zip
http://forum.xda-developers.com/showthread.php?p=33671985

Take a look at this link
teamw.in/DataMedia
So i think we might loose usb mounting on pc
Sent from my LG-P990 using xda app-developers app

ProgMaq said:
Sorry, SDCARD is the defaul name for internal.
FUSE = (Internal EMMC + DATA)
Without FUSE:
Partition 8 = DATA [1,5GB]
Partition 9 = EMMC [5,3 GB]
With FUSE only have:
Partition 8 = USERDATA [6,8 GB]
The user can see 6,8 GB in Internal SD
Click to expand...
Click to collapse
and still - i like it as it is
i still have 2 partitions with 6,8 GB total - but i can keep things more organized with 2 partitions than with one...
for me it's just like having 2+ PC harddrives - one only for the system, and other disks for the other files...

how do I flsh this to files with nvflash?

instead of fuse of internal memory(1.5gb) n internal sd(5.5gb).....
can i have fuse of internal sd(5.5gb) n external sd(i have 16gb) so that i can get...
external sd---21.5gb....
imo 1.5gb is enough for app data but 5.5gb is not enough for sd data files(nova 3 almost 2gb)
i hav mounted my externalsd as internalsd so that sd data files are saved in ext but 16gb not enough(game addict)...
hope u can help..thanks

ullekh99 said:
instead of fuse of internal memory(1.5gb) n internal sd(5.5gb).....
can i have fuse of internal sd(5.5gb) n external sd(i have 16gb) so that i can get...
external sd---21.5gb....
imo 1.5gb is enough for app data but 5.5gb is not enough for sd data files(nova 3 almost 2gb)
i hav mounted my externalsd as internalsd so that sd data files are saved in ext but 16gb not enough(game addict)...
hope u can help..thanks
Click to expand...
Click to collapse
I like it ,interesting thought
But what will hapn when sd ejected and phone restarted
Sent from my LG-P990 using xda app-developers app

HD2 Internal Memory

Despite all the posts and solutions on this subject I must admit a level of frustration at my continuing low internal memory on my HD2, I am running Pacman/ xylograph jb which has plenty of ROM space (most other ROMS take much bigger partitions), Link2SD, Apps2ROM and Clean Master. Link2SD tells me I have no apps on internal, Apps2Rom also confirms all apps either on ROM or SD.
When I look at the storage values I get:
Internal: 146MB used 106 free 40.1
SD card 10.98GB Used 3.91 Free 7.08
SD 2nd partition 3.81GB Used 30.3MB Free 3.77GB
System 260MB Used 177 Free 83.5
Cache 146MB Used 106 Free 40.1
Why is it that despite linking all apps to 2nd partition and having spare space on ROM my internal space is so low, cache is cleaned out every day.
What is using 106MB of internal space?
Any useful thoughts would be appreciated.

hardav said:
Despite all the posts and solutions on this subject I must admit a level of frustration at my continuing low internal memory on my HD2, I am running Pacman/ xylograph jb which has plenty of ROM space (most other ROMS take much bigger partitions), Link2SD, Apps2ROM and Clean Master. Link2SD tells me I have no apps on internal, Apps2Rom also confirms all apps either on ROM or SD.
When I look at the storage values I get:
Internal: 146MB used 106 free 40.1
SD card 10.98GB Used 3.91 Free 7.08
SD 2nd partition 3.81GB Used 30.3MB Free 3.77GB
System 260MB Used 177 Free 83.5
Cache 146MB Used 106 Free 40.1
Why is it that despite linking all apps to 2nd partition and having spare space on ROM my internal space is so low, cache is cleaned out every day.
What is using 106MB of internal space?
Any useful thoughts would be appreciated.
Click to expand...
Click to collapse
Your system partition is way too big, 260mb with 83.5mb free.
You don't need that, 185 mb should be fine for system partition.
Check out the rom thread for recommended partition size.

You can also run roms with DataOnExt. You won't ever run out of memory then. Format an ext4 partition of 1 to 2 GB on your SD card and you have plenty memory.
Or do you have a specific reason to run on Nand?
Sent from my NexusHD2 using xda app-developers app

jvzijp said:
You can also run roms with DataOnExt. You won't ever run out of memory then. Format an ext4 partition of 1 to 2 GB on your SD card and you have plenty memory.
Or do you have a specific reason to run on Nand?
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
I agree with this.
DataOnEXT is definitely the best solution for problems regarding running out of memory quickly.

[Q] Memory Shown Less

Hello,
The RAM shown in my Nexus6 is
Code:
Total: 2970MB
Available 1332MB (45%)
Java Heap: 256MB
The Total RAM 2970MB is shown in the apps CPU-Z and Droid Info. Why the value is lesser than 3GB (3072MB) ? There should be a technical reason for that. Please let me know. Thanks.

Yep, the difference is allocated to a bunch of other hardware blocks, like the MODEM.

doitright said:
Yep, the difference is allocated to a bunch of other hardware blocks, like the MODEM.
Click to expand...
Click to collapse
okay, I also have learned from the internet that the difference is held by the GPU, which the OS is not aware of. So the Total: 2970MB shows the available memory and not the installed memory, Correct ?

aniyan.rajan6 said:
okay, I also have learned from the internet that the difference is held by the GPU, which the OS is not aware of. So the Total: 2970MB shows the available memory and not the installed memory, Correct ?
Click to expand...
Click to collapse
Yes. Boot to bootloader and it will will tell you what brand and size ram and memory is installed in device.

Also the storage space shows 54.6GB instead of 64GB. Is it because of the reserved space allocated, when the filesystem is formatted to ext4 ?

aniyan.rajan6 said:
Also the storage space shows 54.6GB instead of 64GB. Is it because of the reserved space allocated, when the filesystem is formatted to ext4 ?
Click to expand...
Click to collapse
That is minus the system and other partitions reserved for firmware and the OS.

prdog1 said:
That is minus the system and other partitions reserved for firmware and the OS.
Click to expand...
Click to collapse
But it takes almost 10GB of space, which is huge. I think it is good that I have brought a 64GB version.

aniyan.rajan6 said:
But it takes almost 10GB of space, which is huge. I think it is good that I have brought a 64GB version.
Click to expand...
Click to collapse
This is why you always buy as much memory as can afford.

prdog1 said:
Also the storage space shows 54.6GB instead of 64GB. Is it because of the reserved space allocated, when the filesystem is formatted to ext4 ?
That is minus the system and other partitions reserved for firmware and the OS.
Click to expand...
Click to collapse
If the remaining space (64GB - 54.6GB) is used by the OS and firmware, then what does the Available Storage mean ?
The Available Storage shows 49.88GB (91%). I mean there is one more difference: 54.6GB - 49.88GB. Please clarify. Thanks.

aniyan.rajan6 said:
If the remaining space (64GB - 54.6GB) is used by the OS and firmware, then what does the Available Storage mean ?
The Available Storage shows 49.88GB (91%). I mean there is one more difference: 54.6GB - 49.88GB. Please clarify. Thanks.
Click to expand...
Click to collapse
os and firmware + extra for future updates takes up the first 10 giving you 54. Available is your userdata. Anything less that 54 is what you put on it.

prdog1 said:
os and firmware + extra for future updates takes up the first 10 giving you 54. Available is your userdata. Anything less that 54 is what you put on it.
Click to expand...
Click to collapse
okay, When I brought this phone the Available Storage was 51GB, without adding any data by me. So I think something else has taken space from the 54GB (54 - 51 = 3GB).
Then I added some music files and the Available Storage is 49.88GB now.

aniyan.rajan6 said:
But it takes almost 10GB of space, which is huge. I think it is good that I have brought a 64GB version.
Click to expand...
Click to collapse
Not 10 GB, no. The difference is less.
In software, 64 GB is 64x1024 Bytes x 1024 KB x 1024 MB.
In hardware, 64 GB is 64x1000 x 1000 x 1000.
Because there is now a difference in what hardware manufacturers call a GB, they tried to rename the true software GB to be GiB instead (though generally I refuse to do this).
So to work out how many GB of software data you can get in a 64 GB hardware disk, use the maths below.
64 x 1000 x 1000 x 1000, / 1024 /1024 /1024 = 59.6 GB
So a 64 GB anything is only really 59 GB.
Then as mentioned, that is partitioned into /system, /cache, /data etc

danarama said:
Not 10 GB, no. The difference is less.
In software, 64 GB is 64x1024 Bytes x 1024 KB x 1024 MB.
In hardware, 64 GB is 64x1000 x 1000 x 1000.
Because there is now a difference in what hardware manufacturers call a GB, they tried to rename the true software GB to be GiB instead (though generally I refuse to do this).
So to work out how many GB of software data you can get in a 64 GB hardware disk, use the maths below.
64 x 1000 x 1000 x 1000, / 1024 /1024 /1024 = 59.6 GB
So a 64 GB anything is only really 59 GB.
Then as mentioned, that is partitioned into /system, /cache, /data etc
Click to expand...
Click to collapse
Okay, So is 'Total Internal Storage: 54.64 GB' the size of the /system partition or /data partition ?
Thanks.

aniyan.rajan6 said:
Okay, So is 'Total Internal Storage: 54.64 GB' the size of the /system partition or /data partition ?
Thanks.
Click to expand...
Click to collapse
Data.

aniyan.rajan6 said:
Okay, So is 'Total Internal Storage: 54.64 GB' the size of the /system partition or /data partition ?
Thanks.
Click to expand...
Click to collapse
/data AKA userdata. This is where your apps go, where your settings are stored and where your sdcard is.

danarama said:
/data AKA userdata. This is where your apps go, where your settings are stored and where your sdcard is.
Click to expand...
Click to collapse
So that 3 GB (54.64GB - 51GB) is used by the apps, I guess. So that is the reason why it was showing 'Available Storage: 51GB' at the beginning.
Thanks.

aniyan.rajan6 said:
So that 3 GB (54.64GB - 51GB) is used by the apps, I guess. So that is the reason why it was showing 'Available Storage: 51GB' at the beginning.
Thanks.
Click to expand...
Click to collapse
When you get the phone new, when you boot it, some system settings will be stored in data. Also some things related to Android Run time.

aniyan.rajan6 said:
If the remaining space (64GB - 54.6GB) is used by the OS and firmware, then what does the Available Storage mean ?
The Available Storage shows 49.88GB (91%). I mean there is one more difference: 54.6GB - 49.88GB. Please clarify. Thanks.
Click to expand...
Click to collapse
54.6 - 49.9 = 4.7
4.7 / 54.6 = 0.0861
0.0861 = 8.61%
8.61% rounded to the nearest percent = 9%
100 - 9 = 91.
Does that clarify it for you?