/system partition size - Verizon Samsung Galaxy S III

On a 32GB Verizon version GS3, when I go to settings > storage, under miscellaneous files, it show "system memory" to be 5.74GB, I looked at an unrooted 16GB version, and system memory was only 3.49GB, of my total 5.8GB miscellaneous files, about 60mb is other files and applications, and the remainder says "5.74GB system memory".
Why is it so much higher on a 32GB vs. 16GB? I mean the system files should not be proportional to internal storage space, right? I don't have a lot of apps, and I have in fact removed a bunch of original system apps, it tells me I have only about 300 mb of /system space available, how is this possible?
I have flashed rooted images from Odin a couple of times, restored NAND about 20 times or more, and rooted via adb once or twice from stock unrooted. Is all this fragmenting the /system partition? Should I format /system next time I'm in recovery? If so, my pc doesn't seem to recognize the phone in recovery when connected. Do I need different drivers to connect while in recovery, so I can mount and format /system? I can format /data and /cache easily in recovery, and when I had my old HTC Evo 4G, I could connect the phone while in cwm and format /system, but I can't on an SGS3. Is there another easy way to format /system before restoring a NAND backup to truly start from scratch on a clean system partition?
Thank you

Related

Unable to do a nandroid backup (DarchDroid w/GodSpeed recovery) NAND+ext w/ext4

I am unable to create a nandroid backup.
ROM: DarchDroid 2.5.1.2
Recovery: GodSpeed Recovery Toastcfh
I'm trying to do a NAND + ext backup (A2SD ext4)
I get the following error after about 45 seconds:
Code:
Error : Run 'nandroid-mobile.sh' via adb!
I'm guessing this has something to do with the newish A2SD that's being used on DarchDroid? Like... I'm used to the A2SD apps being stored in /system/sd/app but I don't see that folder structure in root explorer. I still have yet to find where the ext partition is.
I know A2SD is working, under Settings > SD card & Phone Storage: I see the ext partition has about 80MB used and internal phone storage remains at 128MB (I have a few apps on internal storage)
I have it setup with a 32MB swap with 512MB of ext4
Any ideas?
so... what's the error?
Whoops...
I edited the original post, its just a generic nandroid error.
I just flashed not too long ago, so I'm not too far into modifying it. I just did a full wipe of /data and /ext and re flashed. Same error.
it could be because you dont have enough memory on your SD card to make the backup
mrchu001 said:
it could be because you dont have enough memory on your SD card to make the backup
Click to expand...
Click to collapse
7GB free...
I'm moving away from DarchDroid anyways... GPS is broken still, going back to FreshToast.

[Q] SD Card will not mount in Nexus S

Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Jacks0n said:
Attempting to partition sd card with ext4 -a process I completed multiple times successfully on a Nexus One, the process appeared to complete but now the phone will not mount the sd card. I've tried a wipe/reset, to no avail. I can still access and partition the sd card through adb, but the phone cannot mount it to format/partition, restore from recovery, partition sd-card from within ClockWork Recovery, nothing. I've re-partitioned the sd card through adb, which indicated a successful completion, but the phone still refuses to mount the sd card. If this weren't a Nexus S with it's cursed internal sd-card I would simply swap out the sd card with another or format it externally like all the google topics I pull up on the subject suggest.
Is this fixable or has the fused sd-card scenario become a liability?
Common Error messages:
Can't mount /sdcard
Can't mount /sdcard/.android_secure
Phone: Nexus S
Recovery Img: ClockworkMod Recovery 3.0.2.4
Rom: CM 7.0.3 (now wiped, cannot put back on since sd card won't mount)
fstab:
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw
/dev/block/platform/s3c-sdhci.0/by-name/media /sdcard vfat rw
Can mount everything except the last one, /sdcard.
I've attempted all: wipe/reset, format using clockwork, partition using clockwork, partition using adb, changing fstab, etc etc.
All topics I've found on the net end up being resolved by taking out the sd-card and formatting externally or using different card. i've had a N1 for well over a year and done far worse without problems, this phone seems to be very fragile for a 'developer' phone.
Click to expand...
Click to collapse
Are you able to go with ADB through the directories?
and yeah, false Section! Q&A would be better
I am having the same issue. I actually just got my phone back from Samsung support (which is real ****ty) because the SD card started having I/O issues.
According to the ticket information they replaced the PCB.
Anyway, I immediately installed Clockwork recovery and transferred the latest Blandroid rom to the root of the SD card. No matter what I do I cannot mount the SD card from the recovery menu or format it from the recovery menu. Mounting USB storage works fine, though.
Hiya I got the same problem
Any salutation yet ?
Yeah. Don't format the internal storage with clockworkmod etc.
I have that issue I cant even open phone now
albundy2010 said:
Yeah. Don't format the internal storage with clockworkmod etc.
Click to expand...
Click to collapse
Hi The phone just stuck in boot logo I can patch iso file from adb though but I cant mount or even wipe devlink cache I dont know what to do ?
Did you ever get this resolved? If so, can you tell me how you did it?
Jouten said:
Did you ever get this resolved? If so, can you tell me how you did it?
Click to expand...
Click to collapse
1.power off...on it back...test it
2.plug your usb cable, boot into recovery..will heard usb sound from your PC, if does not work, try several times plug the usb untill you get usb sound...unplug, then reboot...
3.fresh install ROM...
Yeah, don't mess with the internal memory. I semi-bricked a Droid Incredible one time doing that. It ended up making all the internal partitions FAT. Took me hours to fix it. Be careful. I am afraid to even do it on my crespo4g. When I mount it in gparted running Linux Mint, the internal sd card showed up as not partitioned. I didn't even think about trying to partition it thinking back on the Incredible.
A solution, at least, for flashing/updating roms
Just happened to me, using CM9 after enabling the encryption I can't access the /data /sdcard paths. It would be nice to be able to read them but for me the biggest problem was how to update to the latest CM9 nighty.
In the end I've tricked the clockwork recovery to think the cache partition is the sdcard. I'll post the method in case someone find it useful.
1. Tranfer the update to the cache partition.
- Normally big enough, wipe it from the cwm if there is not enough space
adb push update-cm-9-20120305-NIGHTLY-crespo-signed.zip /cache/update.zip
2. Log into the phone and mount cache to sdcard.
adb shell
mount /dev/block/mtdblock4 /sdcard
3. Go into the cwm option to flash the uploaded package, it wont give you the mount error as we already mounted /sdcard
4. After the update log again and clear the update package, and unmount /sdcard
adb shell
rm /cache/update.zip
umount /sdcard
As long as you don't have to wipe you can continue updating and using your encrypted storage without much trouble
Help, internal storage not showing
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Hi i flash locky another CWR AND IT'S FIX LUCKY ME B^)
Sent from my Nexus S using xda app-developers app
getting SD card back
rellivisit said:
Hi,
I wanted to go back from CM9 to Stock rom, but now I did something wrong (don't know what exactly) and my device is still on CM, but unable to access the internal storage. I cannot even take pictures or access it through CWM.
Any thoughts?
Click to expand...
Click to collapse
I have had no luck using multiple methods to partition sd card with Nexus S. Each time I can view the modified fat32 partition from windows, add files etc, but cannot be recognised from within CWM recovery.
Left me unable to reflash roms etc.
The only thing which has worked for me is to use mini tool for windows and mount usb storage from recovery. Do a refresh from mini tool and it should come up in the list of drives. delete the partition(s) you find there (not your notebook ones of course), and reformat it as fat 32.
CWM>Advanced>Reboot recovery, move over your rom to the sd card, then try to find it in CWM, should now show up :fingers-crossed:

[Q] Corrupted internal storage

ill keep this simple. tried to advanced wipe data and cache with TWRP which returned an E:/ unable to mount for both data and cache. internal storage is now saying its 0MB after i "fastboot erase" on as many of the partitions it would return success with (ie, what was mounted) flashall is asking me for a specific device.
How do i reset the internal partitions so they become mountable again? i believe in erasing the ones i had, it has deleted them altogether and i need to flash original firmware to get it to auto restructure (im guessing)
EDIT: so i downloaded this (link not allowed) i just dont know how to implement it through adb or fastboot
somewhere i read that the latest moto PQ versions for CWM and TWRP both have some selinux problem when wiping data, causing a force unmount (parroting. i DONT know what im talking about)
the first time i installed with CM11 with twrp (after CMW only allowing me to install 10.2) it worked great, except google play and whisperpush(whatever that is) crashing consistently. i should have used 'fix permissions' instead of going for a wipe+re-install
please help, what commands do i need to use through fastboot to restore the partitions, or where can i get the fxz file to use with RSD?
this is a brand new out of the box Sim-modded and pre-rooted PQ
SOLVED (i think)
god im so ****ing stupid.
due to corrupting the file structure and not being able to mount the cache or data partitions, when i installed CM11 snapshot it picked my external SD as the data storage /android/data/
FIX: unmounting and removing the external SD i rebooted to system, booted back to recovery. -> factory reset.... auto reboot, cant mount messages, then a second time it said SELinux supported message. ->factory reset again and finally no red messages, wipe to system (got an error, but probably cause system = external SD). i then inserted the external SD, installed the ROM and everything looks normal and working right
TWRP will restore file structure with 'factory reset' BUT ONLY IF you remove your external sd
i hope this thread saves time and headaches for someone.

Damaged Internal Storage Partition (Need Recovery)

I have flashed my phone using qcom flasher its a snapdragon 800 device elife e7. Now the problem is I can access internal storage but phone storage is not available means can't save any photo content etc. I tried formatting with twrp but no help. It shows sdcard0 as vfat on adb shell but nothing works. Any help pls. Would be really grateful. Thanks
Formatting always deletes / wipes all data on chosen partition.
I can't format it I don't care about the data . Tried it with twrp but it fails to even mount the storage every other partition is working flawlessly except the Storage/internal SD
Is there any way to partition internal storage through root?
IMO far easier is to reflash phone's Stock ROM.
that didn't fix it

TWRP why whole storage is not backed up?

I have 16GB phone and wanted to do a full backup but it's size is 11768MB which I think should be more, look at the calculation:
it's 16GB phone (in decimal) which in binary is 14.9GB. (16000/1074) so main internal storage in digital computation is 14.9GB.
my system partition+data partition (shown in TWRP backup) are 11768MB. (9500 /data and rest is /system)
my internal storage: 868MB free + 1.36GB used (=2228MB)
all other partitions are 167MB (excluding data and system and sdcard)
so far it's 11768+2228+167=14,163MB
but my whole internal storage is 14,900MB and now whole things on my phone is 14,163MB, so where is that 737MB?
also apps cache and system cache are almost nothing and dalvik cache is 629MB (which I think is included in TWRP's /data calculation)
do you have any idea of missing 737MB? does TWRP exclude anything or am I wrong?
TWRP saves only those partitions that may change due to flashing custom ROM.
An example is the vendor partition.
ze7zez said:
TWRP saves only those partitions that may change due to flashing custom ROM.
An example is the vendor partition.
Click to expand...
Click to collapse
yes I know and I calculated whole partitions and SDCARD and TWRP system and data and free storage and everything but the size isn't same as device internal storage space (you can look at my calculation above)
If you want you can always save a disk and not the partitions.
You won't be able to flash it with fastboot (I don't think), but if you have EDL or its equivalent you can.
Renate said:
If you want you can always save a disk and not the partitions.
You won't be able to flash it with fastboot (I don't think), but if you have EDL or its equivalent you can.
Click to expand...
Click to collapse
it's not about backing up, it's mostly because of my curiosity that why when I have root and calculated whole stuff (partitions) plus cache plus free space, altogether they don't fit my internal disk space (14.9GB) and are 737MB less!!! can you test it on your phone and see what will be the result.
I really have no idea what we are discussing.
Code:
Poke3:/ # dd if=/dev/block/mmcblk0 of=/dev/null
61071360+0 records in
61071360+0 records out
31268536320 bytes (29 G) copied, 209.698476 s, 142 M/s
I don't use TWRP.

Categories

Resources