Database Users

[Q] Nexus System Partition Size

Hi, I'm not sure if this is specifically a Nexus question or a general Android question but I have both a Nexus 4 and Nexus 7 and have observed the same behaviour on both
I have posted in the General section with nor response so now I'm posting on specific forums
Basically what's happening is when I delete stuff from the SDcard the free space seems to be allocated to the system partition WTF?!
Take a look at the screenshots I'm going to try a couple of things - one of the suggested things was clearing the data in the Google Services Framework data >> Settings - Apps - All - Google Services Framework - Clear Data - which freed up some of it but not all, the next thing from here for me would be to flash the factory images again and see what I start out with
Both devices are on CM10.1 if that helps, is anyone else is having the same issue??
{
"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"
}
The discussion on Google+ http://goo.gl/lNyLW
Ok so this is my partition sizes now after flashing the factory images back onto my nexus 7. No where near 5GB anyone have any idea what's causing this?

I am guessing you have a couple of CWM back up? Maybe 3-4 of them? Maybe you tried to delete some of them?
Buggy CWM Recovery. Especially if you still hang on to the older versions. Mostly because the way CWM save the backup files.

KyraOfFire said:
I am guessing you have a couple of CWM back up? Maybe 3-4 of them? Maybe you tried to delete some of them?
Buggy CWM Recovery. Especially if you still hang on to the older versions. Mostly because the way CWM save the backup files.
Click to expand...
Click to collapse
I just use TiBU and DataSync now, stopped doing nandroids a while back now
Sent from my Nexus 7 using Tapatalk 2

It's not "system data" for sure. It's some apps with root permission saving its file to locations it shouldn't be doing.
Some how l still think it is CWM, even as you stopped using it in a distance past (which is like 1-2 months ago). I recommend flashing newest CWM and see if there're still old back up files.
If you still can't find anything, try this
bassmadrigal said:
If you are rooted and have adb set up on your computer, you can find out what folders are using the most space by using the commands below, then change into that directory and run the command again.
Code:
adb
su
cd /
du -hd 1
--find the largest folder and change directory (cd) into it - if you find you no longer want to continue in the folder you are in, you can cd .. to get to the previous folder or cd / to get back to the root of the filesystem--
Code:
cd large_folder
du -hd 1
rinse
repeat
????
profit
This will allow you to find what folders are using the most space and can eventually lead you to any large files and can then let you find out if you can delete them or if you need to keep them.
Click to expand...
Click to collapse

isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
We got tired of seeing OEMs include many GB of internal storage for music, while users were still running out of space for apps and data. This approach lets us merge everything on one volume, which is way better.
-- Dan Morrill, Android engineer at Google
Click to expand...
Click to collapse
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card

noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse
I wish that was the case but it not, the space goes to the system partition and I cant access it on the sdcard

Very odd TWRP Issue

Right, this is very weird...
I made a Nandroid backup (compressed) on TWRP for this first time, it completed successfully and then I powered off and turned the Nexus 4 back on. However to my surprise, I could not find the backup on my SD card. I checked everywhere (data/media...TWRP folder...etc). I even checked the entire phone (with root explorer enabled), nothing. However the backup was successful because my Available Space has fallen by roughly 1gb, the size of my backup. Does anyone know whats going on here?
Thanks in advance, really appreciate your support.

esskayy said:
Right, this is very weird...
I made a Nandroid backup (compressed) on TWRP for this first time, it completed successfully and then I powered off and turned the Nexus 4 back on. However to my surprise, I could not find the backup on my SD card. I checked everywhere (data/media...TWRP folder...etc). I even checked the entire phone (with root explorer enabled), nothing. However the backup was successful because my Available Space has fallen by roughly 1gb, the size of my backup. Does anyone know whats going on here?
Thanks in advance, really appreciate your support.
Click to expand...
Click to collapse
it should be in the twrp folder, backups..
{
"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"
}

Hmm, unfortunately I don't get that. This is what I see.
Could it be because I am using a theme on my TWRP (the Holo one btw, which no one else has reported a problem on)...
Edit: Okay, I think I solved it...I went onto the root of the phone again this time, searched the data folder and was able to find Media -> Backups (see below). Why is that it appears here rather on the SD card data folder?

esskayy said:
Hmm, unfortunately I don't get that. This is what I see.
Could it be because I am using a theme on my TWRP (the Holo one btw, which no one else has reported a problem on)...
Edit: Okay, I think I solved it...I went onto the root of the phone again this time, searched the data folder and was able to find Media -> Backups (see below). Why is that it appears here rather on the SD card data folder?
Click to expand...
Click to collapse
maybe because you compressed it? i dont compress mine.

Thanks for the help Simms, but after digging around on XDA forums, I found the cause and the solution (posted here):
jasonwc said:
There was a weird bug with TWRP that put the FIRST backup in /data/media/TWRP/backups (read: wrong). After rebooting the recovery, all future backups will go into /mnt/sdcard/TWRP/backups, which is where you want them.
Here's what I think happened:
1) Your first backup was stored in /data/media/TWRP which is not where TWRP looks for backups. So, TWRP showed no backups.
2) You ran a second backup which showed up correctly in TWRP, and was stored in /mnt/sdcard/TWRP/backups.
3) You renamed the most recent backup, and then checked /mnt/sdcard/TWRP/backups, and assumed the renaming actually moved the folder. I don't think it did.
Click to expand...
Click to collapse

XT1033/Asia Retail/Dual Sim/4.4.4/TWRP2.7.1.1 - Cant backup, wrong file size

XT1033
Stock Rom 4.4.4 Asia Retail
Rooted
Unlocked bootloader
TWRP 2.6.3.3
So heres how i ended up in this situation. I installed a custom kernel the other day and find it not to be useful for me.
Before i flashed the kernel i made a backup on my rom. I used TWRP 2.6.3.3 but if failed in the middle of the backup. So i used online nandroid backup. And backup was successful. When i find the custom kernel not not useful for me, I decided to restore the nandroid backup i made. Did not wipe anything. During the restoration I noticed that TWRP restarted.Then it prompted me to a No OS Installed (something like that). I wipe dalvik and cache i think. ThenI tried to restore it again and completed the restoration. When it booted, looks like i only did a factory reset, which should not be the case. I restored it like twice but same result. Now i ended up installing all the apps again. I was able to install some of the apps from Nandroid Manager. Only the apps and not the data as it took forever to restore one app, i have like 200 apps. I used TB to restore apps and data but it looks like it only detect 7 apps (all were xposed modules). Im almost done now but I have 2 apps that i want to restore but cant. MagicJack as we can only register the app one time. And i used temporary email when i registered which i already forgot. And also i want to restored one of my google account which i used in registering in some sites. Too bad i forgot the password.
So yesterday I decided to install TWRP 2.7.1.1 (with OTG support). i have installed it successfully. because i want to restore the old nandroid backup. I nlow made a titanium backup so i can restore the apps with data.
Now when i go to TWRP i noticed that the file size of the data is toooooo big. (see the pic)
When i hit the refresh it shows the real size but then it goes back to the wrong file size.
As a result i cant backup because the file is too large for my 16Gb USB using OTG.
Now im using the online nandroid backup again, and backup seems to be fine.
{
"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"
}
Someone please help me.
I dont know if its a bug or I just f*cked up my phone.
I also tried the 2.7.1.0 still the same.
Do you know any recovery that support USB otg?
I used cwm on my old phone and it works like it should.
What version of twrp do you use?

[Q] Creating parent failed, error No space left on device while updating to Lollipop

I'm trying to side load the OTA for Lollipop using adb and the files available from Google. My device is unlocked and rooted.
I run the commands to sideload the zip file and everything seems to be working fine until I get 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"
}
I've cleared the cache partition but to no avail.
Does anyone have any insight or am I going to have to wipe everything?

Well I went ahead and did a Flash Stock + Unroot and now it's worse. No error messages. Just the android with the red triangle exclamation mark.
I'm getting fed up with this crap. Every time there is an OTA I have to jump through hoops to get it running again.
Anyone have clues about what to do now?

Skullpuck said:
Well I went ahead and did a Flash Stock + Unroot and now it's worse. No error messages. Just the android with the red triangle exclamation mark.
I'm getting fed up with this crap. Every time there is an OTA I have to jump through hoops to get it running again.
Anyone have clues about what to do now?
Click to expand...
Click to collapse
If you already flashed stock and lost you user data plus can still get into the bootloader, then I suggest using a factory image to upgrade to Lollipop. I've ignored OTA's and have been applying the factory image for a while.
Not in this case but for next time, with the aid of root, a custom recovery to make a nandroid backup, Titanium backups for apps and user data. Prior to applying a factory image save a copy of the Titanium Backup directory, the nandroid backup plus any sundry files that were not backed up to a OTG SDCard (an OTG cable plus USB SDCared reader), getting back to your specific set up is not all that complicated. Plus you get to "spring clean" any old cruft that has built up wasting internal storage.
See: How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)

I have the same problem

I had system partition full after L update. I did it with factory image. I had to remove some apps from system to get adaway, busybox and so on working.
How to get more system space??

veepee78 said:
I had system partition full after L update. I did it with factory image. I had to remove some apps from system to get adaway, busybox and so on working.
How to get more system space??
Click to expand...
Click to collapse
Deleting apps from /system is the only option that I've heard of. You cannot change the /system partition size even if you have spare internal storage. If you're rooted then this sounds worse than it is because there is plenty of apps you likely do not use (e.g. some of the google apps like news). You're also unlikely to use some of the foreign language apps. Even some of the main Google aps get updated out side of /system making the the /system apks redundant.
Without even trying hard I removed 86MBs worth then installed all I wanted (e.g. busybox, Viper4Android ... etc) and still have 54Mg free. So I could have left a lot of apps installed but I'd never use them anyway.
You can delete /system apks if your rooted with a number of different apps:
- Titanium Backup
- A Root enabled file manager like ES File Explorer
- My personal favourite System app remover (ROOT)
Lots of options.

Skullpuck, did you find a solution?

Did you guys try ADB version 1.0.32 or newer? Something has changed in the sideload command (could be only when using TWRP, not sure)

Factory reset led to boot loop?

I'm on an s5 neo, rooted but using the same software it came with.
I decided to try a factory reset, as I had done a few things I can't undo, like removing mtp application, with a root app remover whose restore function doesn't work on this device.
I was also thinking, that instead of personalizing everything, and downloading everything, and then debloating, I thought I'd start fresh and then debloat first.
Thank *god*I had gotten brave enough to download and install twrp and make a backup, that back up is where I am coming to you from now.
I used the twrp recommended wipe for the reset, not custom wipe. Worked fine. Powered back on. All looked well until I came across a screen that said "just a sec..." For an extremely long time, like 10 minutes...
Why wouldn't it fully turn on, any ideas? As of now I can't factory reset ever again.... :/ and I'd like to be able to.
I hasn't disabled anything crazy and could reboot normally before I tried the wipe. I just don't get what went wrong?
Any help is greatly appreciated.
I cant even start off with a new rom I don't think, they're all made for the 903m or 903f versions of this phone, and I'm on the international 903w. I'm guessing some thing significant is different or else it would just be called the 903.
Sent from my SM-G903W using XDA-Developers mobile app

what did you wipe in the custom wipe?
also this http://forum.xda-developers.com/galaxy-s5/general/rom-somewhat-incomplete-edition-v0-1-t3295464

I want to say it wiped data cache and dalvik cache
Sent from my SM-G903W using XDA-Developers mobile app

Pawprints1986 said:
I want to say it wiped data cache and dalvik cache
Click to expand...
Click to collapse
Well, with a bootloop you can go to recovery and recipe, then wipe data then go to advanced options in twrp and delete the Android folder in both internal and external and that should fix the issue
Recipe? I should proof read this stuff before I post it. It should have said reset, not recipe

Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Sent from my SM-G903W using XDA-Developers mobile app

Pawprints1986 said:
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Click to expand...
Click to collapse
No, go to advanced options, file manager, then to either storage, touch the Android folder, hit the check mark in the lower right, select delete, swipe to confirm. Do this with both storages. It's not the system folder and doesn't contain anything that isn't rebuilt upon boot. But it does contain stuff from your previous install that is known to cause bootloops when going from an Android version to another. Nothing to worry about when you delete those folders. It's been the source of tons of bootloops for me

So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
{
"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"
}
Sent from my SM-G903W using XDA-Developers mobile app

Pawprints1986 said:
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
Click to expand...
Click to collapse
Don't do it from within the system. Do it from within twrp
Here, I made a little video. I'm a 100% amateur videographer, so go easy on me lol