epic 4g partition info ! - Epic 4G General

we have 1 gb rom **confirmed!**
256mb goes to system
512mb goes to data
175mb goes to cache
8mb goes to kernel
8mb goes to recovery
65 mb goes to bootloader and database and modem.bin and filesystem map
137 1 256 bml1
137 2 256 bml2
137 3 10240 bml3
137 4 1280 bml4
137 5 1280 bml5
137 6 5120 bml6
137 7 7680 bml7
137 8 7680 bml8
137 9 274944 bml9
137 10 526336 bml10
137 11 179200 bml11
137 12 12800 bml12

What are your sources?

sdx-developers.com
i am one of the high ranking developer over there

Any info if the filesystem is rfs?

shep211 said:
Any info if the filesystem is rfs?
Click to expand...
Click to collapse
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochars
et=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0000,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
it is RFS

Is RFS a good thing or bad thing?
PS. thanks for the info, I followed some of your work on the moment. Glad you'll be working on the epic.
Sent from my HERO200 using XDA App

richse said:
Is RFS a good thing or bad thing?
PS. thanks for the info, I followed some of your work on the moment. Glad you'll be working on the epic.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Its a Bad thing. Thats what causes the lag issues. I new they wouldn't change it just for the epic.

shep211 said:
Its a Bad thing. Thats what causes the lag issues. I new they wouldn't change it just for the epic.
Click to expand...
Click to collapse
I thought the lag issue was due to it using a cheap internal sd media to store apps and such on rather then NAND like the epic has?

FoxRacR17 said:
I thought the lag issue was due to it using a cheap internal sd media to store apps and such on rather then NAND like the epic has?
Click to expand...
Click to collapse
if you create a ext2 partiton on the internal storage its a lot faster then the sd card ext2 partiton lag fix. If the internal storage was bad due to hardware then the phone should till be slow. I can tell a big difference form stock to ext2 internal storage lag fix.

shep211 said:
if you create a ext2 partiton on the internal storage its a lot faster then the sd card ext2 partiton lag fix. If the internal storage was bad due to hardware then the phone should till be slow. I can tell a big difference form stock to ext2 internal storage lag fix.
Click to expand...
Click to collapse
How much difference are we talking about from ext2 on internal storage to etx2 partition on a class 2 card?

xXSecretAgentXx said:
How much difference are we talking about from ext2 on internal storage to etx2 partition on a class 2 card?
Click to expand...
Click to collapse
I really didn't notice a big difference with the ext2 sd card fix but I did with the ext2 internal fix. I would say close to 1x faster then sd card fix. I didn't test this with stop watch but it was big enough of a difference that I noticed it for sure.

so... installing custom rom that doesn't use RFS should fix the lag problem?

Related

odd storage speed discoveries (adb push is the slowest!)

test 1
$ adb push myfile.m4v /sdcard
1299 KB/s (943944330 bytes in 709.453s)
test 2
# time dd if=/dev/zero of=/sdcard/test.out bs=1024 count=1000000
1000000+0 records in
1000000+0 records out
1024000000 bytes transferred in 74.120 secs (13815434 bytes/sec)
real 1m 14.54s
user 0m 1.15s
sys 0m 15.08s
(~13mbyte/sec)
test 3
ubuntu box -> usb mounted xoom
$ ls -lsk test2
1145138 -rwxrwxrwx 1 me me 1145138 1969-12-31 19:00 test2
$ time cp test2 /media/xoom/test2
real 0m14.956s
user 0m0.000s
sys 0m4.580s
~80mb/sec! something is not right... and indeed it wasnt.
something odd happened... immediately after the cp finished the /media/xoom mountpoint became unresponsive for ~60 seconds. I could open astro and browse from my xoom, but doing this from my pc:
$ ls /media/xoom
just hung for a long while
I suspect the write was committed to memory and then synched to /media/xoom so one more test
*same file size as above test2*
$ time cp test3 /media/xoom/test3 ; time ls /media/xoom/test3
real 0m14.980s
user 0m0.010s
sys 0m4.720s
test3
real 1m29.438s
user 0m0.000s
sys 0m0.000s
Which means ~113 seconds total (cp+ls timing) and ~10mbyte/sec
Which if you factor in mtpfs+usb copying (compared to the dd write above) sounds about right.
I am guessing a commit to memory is happening somewhere, but my dekstop is running Linux and Linux doesn't commit a write to memory so cp wouldn't have come back until the write was synced to the disk...
Does this have something to do with mtpfs? Is this a usb'ism? android'ism?
Any thoughts/ideas?
No idea the technically info, but on my evo my memory drops way down as I copy files to to the sdcard. It then goes backup when I'm done coping. So what you say is happening appears to happen on other android devices also.
Sent from my Xoom using Tapatalk
From my experience.. ADB (USB) is the slowest. I have tested ADB over TCP but I cannot remember the results.. CIFS is a step up... and then.. FTPd via filexpert (sdcard access only) is the fastest by far..
get a hold of iwmulticall binary and 'ln iwmulticall iwconfig' to get access to iwconfig.. then iwconfig <name of wlan device> power off to turn off power management for the wlan card.. That boosts transfer speeds quite a bit in some scenarios.. ionice <pid> rt 1 and renice -20 <pid> of the process <pid> doing the copying can also help.
one I forgot is sftp which is somewhere between cifs and adb.. not as fast as FTP.. Thats done by setting up dropbear and getting ahold of the sftpserver binary.. then mounting the tablet via sshfs.. The upside of this is that you can mount / of the device on a computer and have access wirelessly..
You'll need a linux distro for this (but I believe WinSCP will work for windows as long as you can tell it where the sftp-server binary is).. Heres my little script for mounting a device running dropbear (dropbear -v -s -g)
sudo sshfs [email protected]$1:/ /media/sshfs/ -o allow_other,sftp_server=/data/dropbear/sftp-server
its run like this ./<nameofscript> <ipaddress>
this assumes you have dropbear setup correctly with all the appropriate rsa keys generated for your clients and the sftp-server is where you say it is.
btw.. Android REALLY sucks when it comes to making use of the hardware.. I was able to choke up my viewsonic gtab by using its 100mbit eth connection to serve files to a wireless windows client via ftp.. 9-10 MB/sec too much for you, Android OS? Ugh. pathetic. and 9-10 MB/sec peak when it wasn't falling on its face and delivering 0 bytes/sec.. completely frozen.. (but not actually dead/kernel crash)..
another edit: In response to the OP.. 80 MB/sec is beyond the usb 2.0 bus spec..so thats strange too. See whats up when its transfering.. what process is active and how much resources its using.. you could kill all the other unused processes too, but chances are.. they'll just launch again cuz android is ****ty like that.
onicrom said:
but my dekstop is running Linux and Linux doesn't commit a write to memory
Click to expand...
Click to collapse
Uh, yeah it does- but you're not eventually writing to slow-ass NAND flash on your desktop, either.
The Xoom apparently suffers from the burst..pause..burst issue when transferring as well. OCing helped slightly. I don't think this is an issue of slow ass nand.. but then again it could be transferring to a ram buffer on the device.. the device flushes the buffer (or it gets full) and that's when the freezing happens...
Renice/ionice-ing the sdcard process did not help much. That's /system/bin/sdcard binary for those wondering.
Cifs speeds done with 'cp' via terminal emulator are terrible. 600 KB/sec. Gotta love it when the OS is the bottleneck to your internet connection. Power Management turned off (wlan0), priority increased for cifsd,cp, and a dhd related process.. and the speeds jumped up to a blazing 800KB/sec when clock was locked at 1504... meaning my wireless network speed scaled with my processor clock. How screwed is that? Last time I checked, 'we' were only oc'ing the cpu and gpu..
this would depend on what filesystem you are using and if the default behavior is to write sync or async, i don't recall what the default for ext4 is, but mounting /sdcard via mtpfs over usb, which is a fuse mount of /data sure does make fore determining the type of write difficult.
kcrudup said:
Uh, yeah it does- but you're not eventually writing to slow-ass NAND flash on your desktop, either.
Click to expand...
Click to collapse
Blades said:
Cifs speeds done with 'cp' via terminal emulator are terrible. 600 KB/sec. Gotta love it when the OS is the bottleneck to your internet connection. Power Management turned off (wlan0), priority increased for cifsd,cp, and a dhd related process.. and the speeds jumped up to a blazing 800KB/sec when clock was locked at 1504... meaning my wireless network speed scaled with my processor clock. How screwed is that? Last time I checked, 'we' were only oc'ing the cpu and gpu..
Click to expand...
Click to collapse
Interesting finds! I wonder if http transfers would be the same as ftp... the only problem I have with http transfers would be getting the browser to open the files with the appropriate application.
Ideally I wouldn't need to transfer data to/from my xoom at all I just want to play over the air, but if cifs is really the bad I might need to test alternatives.
onicrom said:
but mounting /sdcard via mtpfs over usb, which is a fuse mount of /data sure does make fore determining the type of write difficult.
Click to expand...
Click to collapse
Looks like the underlying FS is ext4 with data=ordered and barriers on (of course). I can't imagine the fuse FS (or MTPfs) being the bottleneck:
Code:
# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/pdsb /pds ext2 ro,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
# df
Filesystem Size Used Free Blksize
/dev 359M 32K 359M 4096
/mnt/asec 359M 0K 359M 4096
/mnt/obb 359M 0K 359M 4096
/system 236M 180M 55M 4096
/data 28G 17G 11G 2048
/cache 166M 4M 162M 4096
/pds 1M 106K 1M 2048
/mnt/sdcard 28G 17G 11G 2048
#
The way in which the Xoom rxs data over USB reminds me of a program I use on my Windows comp called FancyCache. It allows you to set a r/w buffer in RAM, specifying the size and write delay. I just wonder if the Xoom starts to write to nand when the men buffer is full, or after a given time.
I hope it doesn't just wait for the buffer to be full/transfer to finish to start 'flushing' the ram/cache.

[Q] Ideas for improvement of my setup

After hours reading tons of posts I got my ADP1 (Android Developer Phone1) rooted. My current setup is
Phone: ADP1 G1 | 32B | HTC Dream
Rom: COS-DS (http://forum.xda-developers.com/showthread.php?t=950765)
Recovery: Amon RA-Dream-v1.7.0 (http://forum.xda-developers.com/showthread.php?t=566669)
Radio: 2.22.28.25 (http://forum.xda-developers.com/showthread.php?t=831139)
SPL: 1.33.0013d (http://forum.xda-developers.com/showthread.php?t=831139)
microSD: 96MB swap + 512MB ext4 + FAT32
Code:
~ # free
total used free shared buffers
Mem: 112616 110680 1936 0 604
Swap: 23548 20476 3072
Total: 136164 131156 5008
# cat /proc/partitions
major minor #blocks name
7 0 668 loop0
7 1 4508 loop1
7 2 1760 loop2
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 93184 mtdblock3
31 4 27648 mtdblock4
31 5 93952 mtdblock5
253 0 23552 zram0
179 0 992000 mmcblk0
179 1 398437 mmcblk0p1
179 2 500000 mmcblk0p2
179 3 93562 mmcblk0p3
~ # mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/loop0 on /system/lib/modules type squashfs (ro,relatime)
/dev/block/loop1 on /system/fonts type squashfs (ro,relatime)
/dev/block/loop2 on /system/xbin type squashfs (ro,relatime)
/dev/block/vold/179:2 on /sd-ext type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
I would like to know if there is any optimization?
Why should I do the customMTD? (http://forum.xda-developers.com/showthread.php?p=7061471#post7061471)
I'm not using ClockworksMOD as described by COS-DS. Should I? (http://forum.xda-developers.com/showthread.php?t=950765)
My partition order is different as described by COS-DS. Does it matter?
Using customMTD you could assign your cache memory (around 27MB) as internal memory.
Clockwork, I don't like much, but this is my personal opinion. Advantage(?) of Clockwork: you can flash unsigned zip files.
Partition layout probably matters, because on system startup there is a chance, that they are not mounted.
Sent from my Gingerbread on Dream using XDA App
I found customMTD to be difficult to install (I did it with firerat's Magpie ROM), but worth it for the extra space it gave me. Prior to, I was getting low on disk space messages and random shutdowns galore.
I don't recall why, but during my research I recall learning that Amon-Ra is stable and Clockwork isn't if you're going to use customMTD.

Is there sch-i815 Cwm or firmware

In the works? Sure carrier branding is a step redded child. But at least others and myself might be more adventurous if we had backups and a stock firm
I can hope right
Sent from my DROID BIONIC using Tapatalk
Finding very little info myself. Patience is virtue I guess.
Sent from my SCH-I815 using xda premium
I don't really have the extra time to devote to developing for this tablet, but if someone builds CWM for it, that might be what I need to crank out a custom kernel for it. =)
geeknik said:
I don't really have the extra time to devote to developing for this tablet, but if someone builds CWM for it, that might be what I need to crank out a custom kernel for it. =)
Click to expand...
Click to collapse
that'd be cool. I want to look more into messaging.apk, framework, and small things. been timid without cwm backups. I already made a fc cycle issue when playing with the telephony service - thank you for adb.
So, just gotta sit back and wait calmly
Sent from my SCH-I815 using Tapatalk 2
geeknik said:
I don't really have the extra time to devote to developing for this tablet, but if someone builds CWM for it, that might be what I need to crank out a custom kernel for it. =)
Click to expand...
Click to collapse
Man that would be awesome. I'll start praying now for CWM.
The main thing that is preventing me from making a CWM for your device is that I don't know the partition layout. If I had that, it wouldn't take too much work to make one. Also, getting my WIP CM port working (obviously with only partial hardware support, which is the case for the P68x0 as well) on the i815 shouldn't be too bad either. They way I've set stuff up, most changes go in a common repository that is shared by 4 devices (the P68x0 and the P62x0), which the i815 would also inherit from.
Currently I don't really have the time to work on an additional device, but if someone who is familiar with deving is interested in working on the i815, feel free to PM me.
how can I find the partition layout of the device?
Sent from my ADR6425LVW using Tapatalk 2
To help gague interest, I would certainly like this to happen.
Sent from my SCH-I815 using XDA Premium HD app
If someone would like to open a terminal emulator and type in the following:
cat /proc/partitions
Copy and paste the output here
I'll get it in a few hours off mine and would be for helping others test. On work time atm
Sent from my DROID BIONIC using Tapatalk
if nobody beats me to it, ill do this tonight when I get home from work.
Sent from my ADR6425LVW using Tapatalk 2
nitroglycerine33 said:
If someone would like to open a terminal emulator and type in the following:
cat /proc/partitions
Copy and paste the output here
Click to expand...
Click to collapse
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 1280 mmcblk0p2
179 3 1280 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 409600 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 851968 mmcblk0p9
179 10 13492224 mmcblk0p10
179 11 561152 mmcblk0p11
179 16 31166976 mmcblk1
179 17 31162880 mmcblk1p1
Hope this is what you need
Beat me to it...
PLEASE develop CWM for this device. I can't believe it isn't more popular. It is perfect in every respect I can think of. I just wish I could find a decent otterbox-type case. Thanks again! I would gladly donate to the cause.
Can you grab this for me as well:
cat /proc/mounts
Usually the partitions command brings up an alias but I guess not on the gtab. This last one should tell me that partitions.
Here's mine
$ export PATH=/data/local/bin:$PATH
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /preinstall ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /mnt/sdcard/extStorages tmpfs ro,relatime,mode=755,gid=1000 0 0
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Thank you VERY MUCH! I can also get you a dump from Mobile Odin Pro if that would help?
-Rob
if anybody can do it it is definitely Nitro
I have a terminal emulator installed and both rooted and supersu. ES File Manager as well. Ask away!!!
I too, will gladly make a donation for this dev.
You guys actually have the same partitions as the 6800. If there is a recovery out there for odin that does not include a kernel (recovery.bin) the 6800 should work just fine for you. If there isn't one out there that is just the recovery I will see if I can get something done today or tomorrow for you.
The only thing is you would have to boot into recovery right away after flashing and I can create a zip for you to flash that would remove system/etc/install-recovery.sh. Otherwise it will pull the stock recovery from the boot.img and override clockworkmod.
The other option would be to include recovery with a kernel that you can flash with odin.
Next Step
Nitro,
Thank you VERY much. Let me know how or what I can do to move this forward. I am eager to get it going.
Thanks,
-Rob

Someone please. Need nvflashable ROM

Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
yaworski said:
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
Click to expand...
Click to collapse
So what I need to do that I can flash second boot image, and why mmcblk0p7 in nvflash .cfg is about just 7 or more megabytes? And http://projects.pappkartong.se/a500/ do you read it, in that table is write 8 partitions and mmcblk0p8 is data, then it is strange. Thanks for reply. Sorry for bad english.
Tautvaldas said:
Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
Click to expand...
Click to collapse
If you don't have a mmcblk0p8 I would be interested to see what /proc/partitions and /proc/mounts looks like.
With mmcblk0p8:
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 31259648 mmcblk0
179 1 5120 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 29253632 mmcblk0p8
$
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
The partition table parsed from raw dump of /dev/block/mmcblk:
Code:
nvtegrapart: #0 [BCT ] start=0 size=6144 (6)
nvtegrapart: #1 [PT ] start=2048 size=1024 (1)
nvtegrapart: #2 [EBT ] start=3072 size=8192 (8)
nvtegrapart: #3 [GP1 ] start=11264 size=2048 (2)
nvtegrapart: #4 [SOS ] start=13312 size=10240 (10)
nvtegrapart: #5 [LNX ] start=23552 size=16384 (16)
nvtegrapart: #6 [APP ] start=39936 size=1228800 (1200)
nvtegrapart: #7 [CAC ] start=1268736 size=2506752 (2448)
nvtegrapart: #8 [MSC ] start=3775488 size=8192 (8)
nvtegrapart: #9 [FLX ] start=3783680 size=204800 (200)
nvtegrapart: #10 [AKB ] start=3988480 size=20480 (20)
nvtegrapart: #11 [UDA ] start=4008960 size=58507264 (57136)
nvtegrapart: #12 [GPT ] start=62516224 size=1024 (1)
Try the thread called rollback from ics leak, it has a rooted 3.2 image so uh, good luck with that
Sent from my A501 using xda app-developers app
Wery strange now, I got mmcblk0p8, but when I flash second boot image then my data is gone (can't boot into tegraowners 170 ROM) it says that can't use data partition and need data reset, after that it is same thing again. In root 3.2.1 is same as EUUs, same,.cfg, maybe I'm doing something wrong. Sorry for bad english. Now I have a501 stock ROM in my a500 and I will try flash second boot again. And thanks for replies.
Taks for help, it seems working now, maybe I should check what ROM I am using next time thanks. Sorry for bad english.
Haha i don't know who your referring to but uh if it worked , your welcome
Sent from my A501 using xda app-developers app

Storage gone, capacity 5.5 GB

*EDIT - Since 5.5 of available storage is normal for an 8 GB, please note that I had a 16 GB*
I only have 5.5 GB of TOTAL storage. No clue where the other GB's went. This happened at some point today, perhaps after flashing the latest CM nightly.
First I restored a b/u, no luck, fixed permissions, etc... nothing worked. I then reflashed all the stock img's via fastboot, wiped everything, etc... but still no luck. I'm assuming the mounting point was broken somehow? Flashed the factory images did not fix.
Code:
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Someone had this problem the other day. Try this, http://forum.xda-developers.com/showpost.php?p=34906845&postcount=71
Sent from my Nexus 7 using xda premium
El Daddy said:
Someone had this problem the other day. Try this, http://forum.xda-developers.com/showpost.php?p=34906845&postcount=71
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks, I didn't fastboot erase anything, lets hope this is the ticket. Thankfully I have a very recent adb b/u of all my data.
El Daddy said:
Someone had this problem the other day. Try this, http://forum.xda-developers.com/showpost.php?p=34906845&postcount=71
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Boom, done, thanks. All is well now. I didn't realize -w formatted the partitions as well.
No problem. Glad it worked!
Sent from my Nexus 7 using xda premium
El Daddy said:
No problem. Glad it worked!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
12.92 GB of available storage sound about right?
Edit: 16 GB = 12.92 free
8 GB = 5.67 free
Thanks again for the lead.
I'm have the 8GB but that sounds right to me
Sent from my Nexus 7 using xda premium

Categories

Resources