Hi all,
Did anyone use the advanced wipe function from within TWRP before flashing the ROM (T-Mobile original)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm asking because I only have about 300Mb free out of 8GB. Only have about 20 apps, nothing big.
I flashed the ROM (K33010i_00_1021.kdz) using LGUP just to test how much free space do I have and it's about 150Mb free. Don't know how a 1.2Gb ROM can occupy almost 8GB.
I'm thinking to check everything except internal storage, wipe it, turn off the phone, plug the charger and try to enter download mode and flash the ROM again. The issue is that I don't know if after the wipe I will be able to enter the download mode.
Any thoughts?
Cheers!
saphta said:
Hi all,
Did anyone use the advanced wipe function from within TWRP before flashing the ROM (T-Mobile original)?
I'm asking because I only have about 300Mb free out of 8GB. Only have about 20 apps, nothing big.
I flashed the ROM (K33010i_00_1021.kdz) using LGUP just to test how much free space do I have and it's about 150Mb free. Don't know how a 1.2Gb ROM can occupy almost 8GB.
I'm thinking to check everything except internal storage, wipe it, turn off the phone, plug the charger and try to enter download mode and flash the ROM again. The issue is that I don't know if after the wipe I will be able to enter the download mode.
Any thoughts?
Cheers!
Click to expand...
Click to collapse
Advance wiping partitions will erase the data from them.
But let me explain to you how the stock rom works. That 1.2gb is not the rom size.
It's the size of the ramdisk, which is compressed and unpacked after the rom is flashed.
* The ramdisk will always take up space as it is a copy of the /system partition.
* Then you have the current "/system" partition that contains your changes such as rooted status and debloation.
* That is about 2.5gb of "/system" data that is taken up from the 8gb total phone space.
* There's about 1-1.2gb of "/data" space where your user apps get installed to and miscellaneous other directory spaces allocated.
* Alas there is"/data/app-priv" where system apps are installed which has about 1.2gb of space to spare.
& After that it leaves internal data "/sdcard" directory.
Without having your internal data space full you keep 4gb free for storage. But when you install apps they are apart of the first 4gb of phone data.
With the symbols before the spaces above being the sides of the phones space ( * / & )
Apps go into *, and no matter how much space you have in &, it will not make a difference.
My advice for space saving is to debloat your phone with apps you don't use or features you can't use. Grab an external sdcard.
Root, install titanium backup - uninstall some apps if you cannot install it, run a full backup and start removing the red coloured apps .
Be careful what you remove as it can break certain features.
But if you do break something, you can use lg up to reflash the kdz (and you can select just a partition to reflash; such as system) that will fix anything that breaks while removing the red labelled apps without removing any personalization you've made to the device.
Debloation is your best choice to deal with such little space until we get a rom that does not utilize a ramdisk.
Everything checkmarked is what you need to keep to have a fully functional system with NO constant forceclosing.
What is red is system installed and green are data related to system installed apps.
There's a few items unchecked that are on that list; these are also unneeded items.
At minimum these items are all you need installed. Anything else that is red or green may be uninstalled.
Thank you for taking the time to answer to my post!
No problem at all. Hope this helped you tremendously on saving space.
Excellent guide. I haz root
Related
I've tried searching this issue with no luck, surprisingly! I thought it would be more common.
Anyway, when I boot up my Nexus One, it takes <Sandlot>FOR-EVV-ERRR</Sandlot> to mount my SD card. I've got most of my apps on that card, so it's super annoying!
Like I've said, I've got a bunch of apps (40?) loaded on to this card, a few documents, 4 CDs... random stuff. I haven't formatted the card in a looong time... nor have I wiped the phone in a loooong time. I am a crackflasher - I flash a new ROM every day, but I VERY RARELY have issues, so that's why I haven't wiped in so long. This is really the only issue I have, and, if somebody knows the command, I would be happy to just mount the SD manually through the terminal when I need it to.
The phone is a Nexus One. I'm running a CM7.1(or whatever it is) based ROM and kernel. The SD card is the 16gig one that came with the phone.
Any help is appreciated!
Billy
Cliffnotes: What's the terminal command to mount the SD card to the phone? So the ROM can access it?
Ok, so I guess I diagnosed this issue... after rebooting my phone and waiting for my apps to become available I was able to, through the settings menu, view the space used/available on the SD card. Sooo... it is mounted? And the delay is just Android loading the apps from the SD card? How can I speed that up?
Thanks,
Billy
Sent from my Nexus One using XDA App
Srsly?
This is the most extensive group of Android geniuses in the world... is this impossible? Am I asking in the wrong place? Am I not making any sense?
TIA,
Billy
Have you tried increasing the read and write speed of your sd card?
Theonew said:
Have you tried increasing the read and write speed of your sd card?
Click to expand...
Click to collapse
Like by buying a faster one?
Thank you for the reply,
Billy
You increase the read/write speed by increasing the SD card cache size. You can use an SD speed boost app to do so easily, there are a couple on the market. There's also a script that you can run.
I had a similar issue. I've been running the same rom for over six months, and initially just flashed updates over the existing version and only wiped caches. I'd strongly recommend that you go ahead and perform a full wipe. It may seem like a pain, but I am 95%, certain that it will fix your issue. Just backup your apps & data with Titanium Backup and after you've completely wiped & flashed your new rom only restore what you need. Weeding out unused apps should speed up your phone as well. You can always restore them if you need them.
plainjane said:
You increase the read/write speed by increasing the SD card cache size. You can use an SD speed boost app to do so easily, there are a couple on the market. There's also a script that you can run.
I had a similar issue. I've been running the same rom for over six months, and initially just flashed updates over the existing version and only wiped caches. I'd strongly recommend that you go ahead and perform a full wipe. It may seem like a pain, but I am 95%, certain that it will fix your issue. Just backup your apps & data with Titanium Backup and after you've completely wiped & flashed your new rom only restore what you need. Weeding out unused apps should speed up your phone as well. You can always restore them if you need them.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This sounds promising! I feel like I should have known this already, but I'll give it a shot and update this thread.
Thanks a bunch!
Billy
Sent from my Nexus One using XDA App
Hi, I've been wondering why my P500 on the stock rom 2.3.3 has been taking about 4 minutes to boot! Well I just tried booting without the SD card and it booted up in about 30 seconds! Does anyone know why? most of my apps are on the SD, I also have some music. But the SD is 16gb and a class 10 from SanDisk.
Any incite would be a great help.
This may be the most stupid question ever but I have a Galaxy SII running Samsung 4.1.2 ROM rooted and deodexed, but the /system folder only has a limited amount of space even though I have 16GB internal memory, is there a way to sacrifice some usable memory to get more /system memory so I can add some stuff to /sysem/app etc?
Thanks
So you want to increase the actual sdcard-size?
I don't think that's possible. You could install some sd-tools that free up unused space and thereby give you more space to use.
Or you could just delete files and apps you don't need.
But as far as I'm concerned increacing actual sd-size is not possible.
I don't own a S3, but I guess it doesn't have a external_sd-slot?
duncan.wick said:
So you want to increase the actual sdcard-size?
I don't think that's possible. You could install some sd-tools that free up unused space and thereby give you more space to use.
Or you could just delete files and apps you don't need.
But as far as I'm concerned increacing actual sd-size is not possible.
I don't own a S3, but I guess it doesn't have a external_sd-slot?
Click to expand...
Click to collapse
No, I mean if I go to root explorer and then /sysem/app, it only shows like 8MB available even though my SD card is 16GB, is there a way I can increase system memory so I can force install sysem apps and custom frameworks without having to worry about that limit?
The system partition is separate to your internal sdcard, if you go to storage in system settings you can see an internal storage of about 2gb, your 16 gb internal sdcard and also any micro sd you might have installed. Apps installed to phone reside in the 2gb storage unless they are moved to the sdcard (16gb).
I have about 200mb free in my system partition but it varies based on the Rom you are using and any system apps that are installed.
Sent from my PACman GT-I9100 using xda premium
I have a 500+ mb ROM with a whole list of apps so i only have a few megs left
Sent from my GT-I9100 using xda premium
That's why you don't have much system partition space left, most of those apps would be installed there. But like I said your system partition is different to where your user apps are installed. Change to a lighter Rom if you want to push more apps to your system/apps folder.
Sent from my PACman GT-I9100 using xda premium
AuSSiELaMbChOpS said:
That's why you don't have much system partition space left, most of those apps would be installed there. But like I said your system partition is different to where your user apps are installed. Change to a lighter Rom if you want to push more apps to your system/apps folder.
Sent from my PACman GT-I9100 using xda premium
Click to expand...
Click to collapse
I'm just using CM10.1 nightlies now and I have plenty of system space.
Sent from my GT-I9100 using xda premium
If you are able to boot into a separate partition, such as with custom recovery, you can repartition and get the system:internal:external ratio you need. Of course, this would require knowledge of your partition layout, the ability to use 'parted', and some knowledge of how to format a drive via the command line.
How to increases the inner memory for GT I9100
soupmagnet said:
If you are able to boot into a separate partition, such as with custom recovery, you can repartition and get the system:internal:external ratio you need. Of course, this would require knowledge of your partition layout, the ability to use 'parted', and some knowledge of how to format a drive via the command line.
Click to expand...
Click to collapse
hi pls advise how to get it done. my handset is GT I9100.
Get more memory Allocated to Device memory of Samsung Galaxy S2
xxkcxx said:
hi pls advise how to get it done. my handset is GT I9100.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was looking for this for a while, and finally found the solution on Youtube video posted by Saurabh.
He re-Partitioned the USB drive and gave more capacity 4,6 or 8GB to Device memory and it worked like magic as shown in the Image attached.
Would post the Step by Step Blog post here but i'm a New user so, can't post links - Search this exact phrase on Google "Storage Space running out" permanent Solution for Samsung Galaxy S II GT-I9100" you should find it on Ngbuzz Forum
Yes. I know you're going to tell me to use the search or google, etc. But believe me when I say I have tried a lot already.
I'm getting this error when I try to install or update almost every APK on my Android. SOME will install or update and I can tell you there's nothing to do with file size. The storages seem to have plenty of free space, apps install smoothly when I factory reset my phone, but after a few days I start getting this annoying error.
I'm running the latest Nightly build from CyanogemMod for LG p720h (Yea, it's not stable and I know I should expect some... erm... bugs). It's Android 4.1.2.
I know the Internal Storage is emulated and have tried many many many fixes I found in this very forum and all over the internet. I'm a game developer so I know a few things about adb shell/logcats but couldn't find/understand anything analizing those during an APK install. I can provide logs, etc.
Can anyone help me find out how to solve this problem? Any idea of what's going on?
LexHax said:
Yes. I know you're going to tell me to use the search or google, etc. But believe me when I say I have tried a lot already.
I'm getting this error when I try to install or update almost every APK on my Android. SOME will install or update and I can tell you there's nothing to do with file size. The storages seem to have plenty of free space, apps install smoothly when I factory reset my phone, but after a few days I start getting this annoying error.
I'm running the latest Nightly build from CyanogemMod for LG p720h (Yea, it's not stable and I know I should expect some... erm... bugs). It's Android 4.1.2.
I know the Internal Storage is emulated and have tried many many many fixes I found in this very forum and all over the internet. I'm a game developer so I know a few things about adb shell/logcats but couldn't find/understand anything analizing those during an APK install. I can provide logs, etc.
Can anyone help me find out how to solve this problem? Any idea of what's going on?
Click to expand...
Click to collapse
Is because your phone doesn't have enough ram(storage for apps) to hold those apps. If you have an sd card you can use AppMgr III (App 2 SD):
https://play.google.com/store/apps/details?id=com.a0soft.gphone.app2sd
You can move apps to either internal or external storage
Maurice5813 said:
Is because your phone doesn't have enough ram(storage for apps) to hold those apps. If you have an sd card you can use AppMgr III (App 2 SD):
https://play.google.com/store/apps/details?id=com.a0soft.gphone.app2sd
You can move apps to either internal or external storage
Click to expand...
Click to collapse
I was able to install this app but it didn't work, it says the primary external storage is emulated. The Storage manager says it has 548mb free space on my internal storage which should be plenty.
And even if I uninstall an app 50mb big I can't install other apps, even if they're 1MB or less. I don't think it has anything to do with "real" available storage.
LexHax said:
I was able to install this app but it didn't work, it says the primary external storage is emulated. The Storage manager says it has 548mb free space on my internal storage which should be plenty.
And even if I uninstall an app 50mb big I can't install other apps, even if they're 1MB or less. I don't think it has anything to do with "real" available storage.
Click to expand...
Click to collapse
apps don't use internal storage, they use a partition inside the internal, which is why you dont get all the storage on the box.
Maurice5813 said:
apps don't use internal storage, they use a partition inside the internal, which is why you dont get all the storage on the box.
Click to expand...
Click to collapse
So, how I check how big is this partition and what files are there so I can move them and free some space?
Edit: Found the df command and got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LexHax said:
So, how I check how big is this partition and what files are there so I can move them and free some space?
Edit: Found the df command and got this:
Click to expand...
Click to collapse
the app tells you what you can and can't
Maurice5813 said:
the app tells you what you can and can't
Click to expand...
Click to collapse
It's not working for me, any better idea for debugging this problem?
It's not related to log files too, I can't even find the log folders.
Hello
I'm having problems finding the error causing the incorrect storage space being reported on my compact; 16GB instead of 32GB. Has anyone encountered this before?
It's definitely something I am doing with adding the recovery - as a virgin 32.3.A.0.376 flash reports 32 GB correctly.
I've tried rootkernel 5.23, and the androplus kernel, and also with and without root/SuperSU. Previous installation of TWRP 3.0.2 on 32.2.A.0.305 with SuperSU displayed correct storage spaces with my Device Key intact.
Is anyone able to give me a hint as to what I should be looking for? I might try again and this time check with SD Maid or Apps2SD what the filesystem is doing once it does it's Google first boot setup. I was using TWRP in recovery and the default Storage Menu in Nougat settings to check previously.
Thanks
Just reverted to Marshmallow and it's interesting that it now reports 16GB. I have no idea what is happening
NeoBeum said:
Just reverted to Marshmallow and it's interesting that it now reports 16GB. I have no idea what is happening
Click to expand...
Click to collapse
happened with mine on both marshmallow and nougat, tho it corrected itself after a few restarts
Ok, thanks. I don't know if I'm game enough to test to see what happens if I fill up my marshmallow internal storage beyond 16gb, backup, flash Nougat, and revert... I'm curious though
Is there anything out of place in this? I'm new to Linux, I only just installed Ubuntu on my laptop today, and am learning
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know why it's doing this now... a moderator can delete this thread - tis related to TWRP + Nougat + Rootkernel
Had the same problem. I could solve it:
I flashed the stock rom. Then I restart mobile phone. Then flash the kernel and TA...
When i dont start the phone between flashing rom and kernel, then it's always 16 gb...
f4t1 said:
Had the same problem. I could solve it:
I flashed the stock rom. Then I restart mobile phone. Then flash the kernel and TA...
When i dont start the phone between flashing rom and kernel, then it's always 16 gb...
Click to expand...
Click to collapse
ah ok... i might look at what the persist files are doing in TWRP, i think when you do a restart, after the stock rom is flashed, it creates the data partition for the internal.
in the current build for rootkernel and twrp - i think it needs a prexisting directory
NeoBeum said:
I know why it's doing this now... a moderator can delete this thread - tis related to TWRP + Nougat + Rootkernel
Click to expand...
Click to collapse
Not a Nougat specific problem, it can happen on MM too. Speaking from experience.
I'm going to put TWRP on to a Virtual Device as part of my mini project... I just made a Z5 Compact skin for Android Virtual Device Manager
In twrp one can select data and or system, to repair, don't wipe it!
There one can press also repair and or resize wich may help. Maybe reboot needed but it has helped me before, also with nougat
The permission and partition information is not always correct during both format and wipes, that's the problem
jutphaas said:
In twrp one can select data and or system, to repair, don't wipe it!
There one can press also repair and or resize wich may help. Maybe reboot needed but it has helped me before, also with nougat
Click to expand...
Click to collapse
Jutphaas is correct, if you are performing a DRM fix with Root procedure via fastboot and TWRP then the wrong drive size will be stored. Booting into TWRP, advanced wipe, repair filesystem, resize filesystem, backing out and then going to install or somewhere else where you can select storage and selecting the onboard drive should now show the full amount of storage instead of the halved amount. This worked for me on Oreo, thanks Jutphaas.
Went to do a backup to Ext Card with almost 57GB on it. Chose NORMAL and left only boot, system, data and internal storage (default) checked. Specified Ext card as location. Process appears to start correctly (fast scrolling f files, but I never get the next screen with Flashfire band across the top showing the actual backing up - screen just goes dark except for blue light in upper left corner. It stops at that stage. Never reboots. I have to remove battery to restart, and when I look for the backup there's nothing except a popup that states "no backups found" and "restore from ADB."
Don't want to attempt flashing a new ROM (e.g., Stang5litre) if I can't get it to even backup.
wedmiston said:
Went to do a backup to Ext Card with almost 57GB on it. Chose NORMAL and left only boot, system, data and internal storage (default) checked. Specified Ext card as location. Process appears to start correctly (fast scrolling f files, but I never get the next screen with Flashfire band across the top showing the actual backing up - screen just goes dark except for blue light in upper left corner. It stops at that stage. Never reboots. I have to remove battery to restart, and when I look for the backup there's nothing except a popup that states "no backups found" and "restore from ADB.". Don't want to attempt flashing a new ROM (e.g., Stang5litre) if I can't get it to even backup.
Click to expand...
Click to collapse
Questions, Concerns and Support regarding FlashFire should be posted on the following Official FlashFire thread.
[Android 4.2+][ROOT][2017.04.03] FlashFire v0.57 by Chainfire
Good Luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
wedmiston said:
Went to do a backup to Ext Card with almost 57GB on it. Chose NORMAL and left only boot, system, data and internal storage (default) checked. Specified Ext card as location. Process appears to start correctly (fast scrolling f files, but I never get the next screen with Flashfire band across the top showing the actual backing up - screen just goes dark except for blue light in upper left corner. It stops at that stage. Never reboots. I have to remove battery to restart, and when I look for the backup there's nothing except a popup that states "no backups found" and "restore from ADB."
Don't want to attempt flashing a new ROM (e.g., Stang5litre) if I can't get it to even backup.
Click to expand...
Click to collapse
Make sure you are using FF v.53, the newer versions don't work on this device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstalled v.57 and installed v .53, but now when FF starts it goes through the opening sequence but then nothing. Just my basic home screen and apps as if it shut itself off. No error messages. Just poof! Gone.
Help. The solution you proposed isn't working. See me post previous to this.
wedmiston said:
Uninstalled v.57 and installed v .53, but now when FF starts it goes through the opening sequence but then nothing. Just my basic home screen and apps as if it shut itself off. No error messages. Just poof! Gone.
Click to expand...
Click to collapse
You need to set date and time 01/01/2000 for FlashFire works on older versions...