Hey guys, I have a memory issue with my Nexus One when it comes to available storage space. The rom available memory seems to get lower and lower everytime I flash a rom than the previous time. When I load roms like CM6 or Kang-o-Rang or MicroMod Supercircle 2.7 or any others I have 4-16 MB available and nothing has installed yet. I usually use A2SD EXT3 for these but now its extremely difficult to do anything when booting with so little space to begin with. A week ago, on most roms I have well around 150 MB free before installing anything. What may have caused this issue? I even tried booting CM6 with a different SD card not partitioned for A2SD and wiping everything and same result and now I really can't install anything. So is my phone faulty or is there something I can do? I am currently running recovery Amon RA 1.7.0.1 and issues seemed to have come up since using this recovery. I was using Clockwork Mod latest one before this a few days ago.
Any ideas?
Have you been wiping data + cache each time you flash?
Make sure you're calculating data space and not system space (which can be as low as it gets to be, it doesn't matter).
codesplice said:
Have you been wiping data + cache each time you flash?
Click to expand...
Click to collapse
I have wiped, cleared cache, delvik many many times. I suspect that the wipe is not working properly. I have tried two different recoveries and nothing works. My available space now running on Nexus FRF91 stock with root only I have 53.64 MB free. I have installed no third party apps yet whatsoever. I have not even logged in to google yet because it will download all my apps again. I have rebooted as well. I think theres an issue with my device and memory. Should I call HTC or my warranty is void?
Sounds like a weird problem, I would've tried to wipe a time or two more. I just wiped my device after flashing nightlies for the last two months without wiping and I noticed I had 170MB free when I booted up with a few apps installed.
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Jack_R1 said:
I agree with SBS_. It sounds like the wipe isn't doing the job properly. Try to do it in all the possible ways (wiping through the ROM - using "Factory Reset" option, wiping through recovery - clearing data, cache and Dalvik-cache, and wiping through ADB command line), see if it changes anything.
Click to expand...
Click to collapse
I've tried everything except ADB command line. I will have to read into doing that as I am unsure what to do. I have wiped from recovery and through the rom at least 15 times each! lol
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Jack_R1 said:
When you load a new ROM, did you try to use Root Explorer to see what's on your DATA partition? (under directory /data).
Click to expand...
Click to collapse
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
timahawk said:
Great idea. Actually I have but not sure what suspicious files I should be looking to delete. I do own root explorer so any suggestions would be great. Thanks!
Click to expand...
Click to collapse
I have this exact issue. I know how to wipe. I have gone as far as reloading HBoot and placing the stock EPF30 image. I have gone thru using clockwork and Amon. I know how to do factory resets. I know how to go to storage options with clockwork and format all partition options. I have spent months on this. Below is a readout, after blowing away everything.
~ # du -hc /data
du -hc /data
2.0K /data/lost+found
4.0K /data
4.0K total
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 192.9M 0 192.9M 0% /dev
/dev/block/mtdblock5 196.3M 109.5M 86.8M 56% /data
~ #
Another user that I have been working with has the exact issues as the user here and me. He contacted HTC. They are replacing his N1. There is something weird going on with some of these units. Just like a few months back, no one knew anything about the bad boot blocks issue causing many developers to change their ROM installs to accommodate those users with this issue. This low space on /data issue is another one that sooner or later will start to show up more and more, IMHO. For instance, at best using either Evils Sense Roms or MicroMods Hybrid sense Roms, I have 23MB free on initial install. This is after basically wiping formatting, resettings factory Data etc etc. At best, lets say using Enoms latest AOSP, I have maybe 75Mb free Internal memory, after initial install and NO applications downloaded installed on my part.
I really wish that folks here and on other threads would start to take this issue a little more seriously than basically saying a user isn't properly wiping his setup prior to an install. I have my beloved N1 since third week of January this year. Never had a problem with rooting, installing any of the original CM, or Paul M stuff from the early days here and on their Kitchen setups. Something has basically changed to cause these issues on a number of Nexus one setups. I have root explorer too and no manner of deleteing, via changing partition permissions from RO to RW makes any difference after wiping, formatting whatever prior to a fresh clean install of any current ROM.
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Saphroxx said:
I have approximately the same issue. I can't install anything..
Even after a full wipe of /data and all caches, I installed latest nightly-219-passion and the only possible way to install apps is by manually typing the adb push commands in commandline. It DOES NOT WORK using Market, File Manager, Titaniumbackup, ....
When I nandroid restore I have all my apps back but still CANNOT install any new apps using Market, File Manager, Titaniumbackup, ....
I already tried the fix_permissions script in both Amon_RA and RomManager but without success. I have system:system permissions on /data.
Is there a way to wipe /system aswell prior to an install, or does that happen when you flash a .zip?
Click to expand...
Click to collapse
How did you install the nightly. Even with my issues of 109Mb used up on data before I install anything, I have the latest nightly running along with latest Gapps and approx 50 of my own apps, with 79Mb free internal. I used clockwork recovery, then under storage options, you can run format options, on boot, system, data, cache, and SD-EXT and then under advanced, wipe dalvik-cache. I also added the data factory reset option also. I then clean installed the nightly. Then after an initial setup to just have it running, flashed the gapps. I did initially have approx 75Mb free Internal before the Gapps install. Then I went down to 53MB after gapps. I verified I had the correct settings in settings:Cyanogen Mod for the file system. I then flashed the latest Dark Tremor script, ran the commands for a2sd check, a2sd reinstall, a2sd zipalign and a2sd cachesd to move the dalvik-cache to sd. I have an EXT3 setup on my SD card. After moving Dalvik cache I jumped from 28Mb free to 79Mb free where it's pretty much staying now. Not as much as others that don't have the issues on /Data but at least useable.
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
dcahoe said:
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
Click to expand...
Click to collapse
You can tell by looking in settings and storage. It will tell you the size of your media storage. If you truly have the 1Gb /data, you might want to look at Dean Gibson's repartitioning thread. He has a 2gb/4gb version.
And no, there is no repartitioning that cm10 does. That was for a phone you saw.
Sent from my Nook HD+ running Tapatalk
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
dcahoe said:
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
Click to expand...
Click to collapse
The only thing I can think of is some users are having read only problems on both SD card and /data, which is where apps get installed. Have you tried to install other apps since the TB install failed? A test you can try to see if you are one of the users with ro issues is to use a root file manager (there is one built into CM10 now) to create a test file somewhere on /data.
Sent from my Nook HD+ using Tapatalk
i need help with my XT1068 (dual sim moto g 2014)
my moto g has an unlocked bootloader, TWRP installed, stock 5.0.2 firmware with root acess.
yesterday i installed xposed for lollipop and gravitybox for lollipop, yes both are alpha versions, but i am that kind of early adopter and i wanted to try it. everything ran smooth, xposed and gravitybox successfully installed and worked.
however i noticed i can't take a screenshot or photo anymore. so i tried via solid explorer to create a folder/file on sdcard0 (internal) and sdcard1 (external sdcard), both failed stating "permission denied". also via MTP on my computer i can't write to both partitions.
so i restored my nandroid backup i did before i installed xposed. problem still exists, my phone works fine but i can't write to both sdcards.
a factory reset wipe doesn't work, after the installation-process were i set language and stuff the system-ui closes and i can't do anything.
i tried all kind of wipes in twrp (system, internal, dalvic cache and cache of course) but nothing worked.
also tried commands like fsck_msdos /dev/block/vold/179:65 (which is my external sdcard) and fsck_mdos /storage/emulated/legacy (which gave me error ** /storage/emulated/legacy (NO WRITE)" ) or restorecon -v -R /data/media (also no change, still not writeable)
in TWRP i can modify folders in the filemanager...
never had any similar situation before. maybe someone has an advice for me.
EDIT:
i decided to go back to the start and get this phone working again. so i downgraded to official kitkat firmware and installed the lollipop ota update. then recovery and supersu and now it is working again.
I'm stuck at the Teamwin loading screen with the screen going dark and then back to the Teamwin screen.
Partitions are converted to f2fs. (ev_tenderloin-6.0-testing-2015.11.28 was the last upgrade I had installed and boots fine, but when I went to install a newer build i discovered this problem.)
I have used adb to reinstall twrp (its funny while it wont go past the Teamwin screen I can use adb push to try different recovery's) and get the same issue. If I install any other build (twrp / cwm) it will boot into recovery, but since none of them have f2fs support (unless there is another twrp or cwm build that has it?) it will only see the webOS partition.
tptoolbox v42 wont install android because:
e2fsck: bad magic number in super-block while trying to open /dev/store/cm-cache
/dev/store/cm-cache:
The supperblock could not be read or does not describe a correct ext2
filesystem. If the devoce os va;od amd ot rea;;y cpmtaoms am ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
esfsck -b 8193 <device>
e2fsck -fp detected error on fs on vol cm-cache rc=8
Click to expand...
Click to collapse
So I guess my question boils down to is there anything else I can try to fix this or do I need to just use tailor to reformat Android system, Android cache and Android data then tptoolbox to reinstall?
I went I used tailor to destroy and rebuild my android partitions and reinstalled, so for now at least the issue has been resolved.
This problem has been solved by @Didgesteve
Thank you very much, Didgesteve!
For everyone who is a genius(like me), read his post.
Hi Community,
short story: my device seems kind'a bricked, because i am not able to install a rom via twrp; error: unable to mount /data /cache and /system.
What I did:
I unlocked my bootloader via the official sony method > everything worked flawlessly
I bootet my device into fastboot mode and flashed twrp onto it > everything still workes fine
I wiped /data /cache and /system according to the normal cm13.0 installation process > still finr
I installed the cm13.zip from an external sd-card > no errors
I installed the gapps.zip from the sd-card > Nothing unusual
I booted into cm13, configured it and installed some apps > works as usual
I noticed that a new version of the rom was published, so I booted into twrp > worked
I wiped /data /cache and /system > worked
I reallized, that i could flash my external sd-card, too because i wanted to install the new cm13-version via adb-sideload > now the errors came in
So i thougt retrying wiping /data /cache and /system and the same errors occured > holy sh*t
Last I tried simply installing the cm13.zip from the external sd-card > same errors
What the errors are for wiping(those for install are basically the same:
Code:
could not mount /data and unable to find crypto footer
failed to mount /data (no such device)
Unable to recreate /data/media folder
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Unable to mount storage
Same goes for using the official cyanogen recovery and other cyanogenmod versions.
I am also not able to find/mount it via adb shell.
The images, etc:
CM13: http://forum.xda-developers.com/z3-compact/development/rom-cm13-t3277402/page7 version by @nelvinchi on 25th February 2016, 12:39 PM
TWRP: https://twrp.me/devices/sonyxperiaz3compact.html
Gapps: https://www.androidfilehost.com/?fid=24269982087021755
Additional information:
OS: Mac OSX El Capitan and Linux Mint 17.3
Sd-Card: SanDisk Ultra 64GB micro sdxc
Phone: Sony Xperia Z3 Compact D5803 (colorrange)
My ideas for fixing this:
-manually adding the partitions via adb shell
+required: correct partiton table and adb commands
+don't now, if this would work
Hope i didn't miss anything and there is someone out there, how can help me,
yours sincerely,
Niggl
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Have you got flashtool working? Have you tried pushing a stock tft? to see if you can repair it?
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
The chances of being able to repair it back into CM are slim, I suspect you're going to have to start from scratch, get stock working then go back to CM after.
**SOLVED**
Thank you for your help!
Didgesteve said:
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Click to expand...
Click to collapse
The partition tables were(because of bull**** or something like that) corrupted(I checked it: not because of the wiping, but i will not wipe /system at an update in the future)
Didgesteve said:
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
Click to expand...
Click to collapse
I can boot into recovery and fastboot/flash mode.
Xperia companion and sony bridge are both not working because of "modified software".
Flashtool worked for the stock tft.
So THANK YOU VERY MUCH,
you are my savior!
I hope nobody else, will be a genius like me
Thx again,
Niggl1999