I'm wondering if I should use Titanium or CWM to back up my phone now that I've finally got my S5830L rooted. I spent most of yesterday searching for and reading information on CWM. But I still have a bit to learn 1st.
As I've done with PCs, I just want a relatively vanilla backup so that if for some reason down the line the phone's OS gets so corrupted that it's near unusable... I'll have something to flash back to.
It seems there's no way to uninstall CWM once it's flashed. But it seems that Titanium as an app can. And I would still like to leave things as simple as possible to go back to a valid warranty condition.
So my question is, can Titanium do as good of a job backing up my phone as it is now to restore it later as CWM can?
I've read where CWM doesn't back up the kernel and modem, tho' I'm not clear one if that's important. But I've also heard that Titanium can back up apps and other data on your SD card. I'm leaning towards Titanium... but would like to hear a few people's opinions on this.
I know this is probably rehashed newb stuff... so thanks everyone for all your feedback.
If you want to backup the entire system , use CWM4
If you only want to backup apps , use Titanium
Ace-ing all tests.
Titanium for apps, CWM for total OS/drive. Have been seeing that. But CWM4... not CWM5? And any concerns about not backing up kernel & modem?
No concern with not backing up kernel, readily available online - i think data/wifi modules are backed up with the system backup. CWM4 does the same job as CWM5. It's called a Nandroid backup btw, a complete system and storage backup. Perfect for what you want.
I notice there's a recovery.img file in CWM v5.0.2.6 that v4.0.0.9 lacks... wonder what that's for. From the file name I'd guess it's for some improved recovery function that v4 lacks.
TakuSkan said:
I notice there's a recovery.img file in CWM v5.0.2.6 that v4.0.0.9 lacks... wonder what that's for. From the file name I'd guess it's for some improved recovery function that v4 lacks.
Click to expand...
Click to collapse
It's just a recovery image
Ace-ing all tests.
EmoBoiix3 said:
It's just a recovery image
Click to expand...
Click to collapse
Yes, but a recovery image of what that's different from the main backup CWM makes when it images the phone?
I know in PCs that it's important to image the boot sector if you want to restore the image to a drive you expect to be able to boot and be a 100% copy of the original. Could this be something like that?
TakuSkan said:
Yes, but a recovery image of what that's different from the main backup CWM makes when it images the phone?
I know in PCs that it's important to image the boot sector if you want to restore the image to a drive you expect to be able to boot and be a 100% copy of the original. Could this be something like that?
Click to expand...
Click to collapse
The recovery.img in the CWM5 .zip package is the entire recovery itself , nothing else
Ace-ing all tests.
EmoBoiix3 said:
The recovery.img in the CWM5 .zip package is the entire recovery itself , nothing else
Click to expand...
Click to collapse
Maybe I'm just not familiar enough with the lexicon of the Android community. An '.img' file to me is an backup, or image of a hard drive or drive partition that can back up part or all of a hard drive. That image file can then be used to make an identical mirror of the 1st drive onto a 2nd drive.
When you back up a phone with CWM, I've read the terms ROM and Backup used. I don't know if I've read the term Image being used or not in that respect. But I was thinking in terms of the CWM backup of a phone as being what I'm used to... Something that will restore all or most of the 1st drive back onto either that drive or another.
What the recovery.img file is an image of I'm not clear on. What is it an image of? And when the file CWM creates is later restored to a phone, what part does the recovery.img image file play in the process?
Does CWM use that recovery.img as a template and either modify and add to it when it backs up a phone, or perhaps create a whole new .img file based on it?
Okay let me rephrase .
When clockworkmod recovery version 4 backs up files , it is in this structure
Boot image
Recovery image
Data
System
Cache
SD-ext
The recovery image is the backup of CWMv4 in this case .
Mostly I would recommend you to use CWMv5 because it is backwards compatible with v4 (allows restoring v4 backups)
But if you restore a CWMv4 backup in CWMv5 , the CWMv4 recovery image will be restored along with it , thus bringing your recovery back to v4
Ace-ing all tests.
EmoBoiix3 said:
Boot image
Recovery image
Data
System
Cache
SD-ext
Click to expand...
Click to collapse
Okay EmoBoiix3... That list made me realize that those are all partitions in the Android/Linux OS. So I googled 'android drive partitions' and came up with this very useful explanation of how those OSs are structured. Unlike Windows OSs, they use multiple partitions that all 'appear' to the OS as one big entity. And CWM is assuming itself as being 2 of them, /boot and /recovery when it does operations on the entire memory space. I call that "memory space" because Android phones seem all to be using solid-state (flash) memory as opposed to motorized hard drives computers (and iPods still!?) have been based on for so long.
So I've gone ahead and installed CWM5, and backed up my phone. Interesting CWM doesn't ask for a destination. I'm guessing it'll let you browse for one if you move it later.
And I find it doesn't back things up to one big image file like I'm used to with Windows imaging software I've used. It seems to have created an image for each partition, which makes sense based how on the Android OS is structured.
One thing that surprised me was the size of the backed up data ended up being. For me that was 397 MB. For some reason I thought the Ace had 4 GB internal memory. But checking specs, I see there's only 158 MB storage, and 278 MB RAM. At 1st I thought I was going to have huge amounts of memory left over. But now I'm wondering how 397 MB fit on 158 MB storage memory. Wikipedia explained that for me:
(NVRAM) is random-access memory that retains its information when power is turned off (non-volatile). This is in contrast to dynamic random-access memory (DRAM) and static random-access memory (SRAM
So the specs must mean more specifically 278 MB NVRAM. Wonder why they differentiate between 'storage memory' and 'RAM' if it's all solid state in there.
TakuSkan said:
Okay EmoBoiix3... That list made me realize that those are all partitions in the Android/Linux OS. So I googled 'android drive partitions' and came up with this very useful explanation of how those OSs are structured. Unlike Windows OSs, they use multiple partitions that all 'appear' to the OS as one big entity. And CWM is assuming itself as being 2 of them, /boot and /recovery when it does operations on the entire memory space. I call that "memory space" because Android phones seem all to be using solid-state (flash) memory as opposed to motorized hard drives computers (and iPods still!?) have been based on for so long.
Click to expand...
Click to collapse
Well , if they still used motorised hard drives wouldn't it be too hot to operate considering how it heats up when playing games ?
TakuSkan said:
So I've gone ahead and installed CWM5, and backed up my phone. Interesting CWM doesn't ask for a destination. I'm guessing it'll let you browse for one if you move it later.
Click to expand...
Click to collapse
All backups are saved to /sdcard/clockworkmod/backup .
TakuSkan said:
And I find it doesn't back things up to one big image file like I'm used to with Windows imaging software I've used. It seems to have created an image for each partition, which makes sense based how on the Android OS is structured.
Click to expand...
Click to collapse
Yes , if everything is backed up into one whole chunck it would probably make things harder to do and would take more time to merge all of them together depending on how big the partitions are .
TakuSkan said:
One thing that surprised me was the size of the backed up data ended up being. For me that was 397 MB. For some reason I thought the Ace had 4 GB internal memory. But checking specs, I see there's only 158 MB storage, and 278 MB RAM. At 1st I thought I was going to have huge amounts of memory left over. But now I'm wondering how 397 MB fit on 158 MB storage memory. Wikipedia explained that for me:
(NVRAM) is random-access memory that retains its information when power is turned off (non-volatile). This is in contrast to dynamic random-access memory (DRAM) and static random-access memory (SRAM
So the specs must mean more specifically 278 MB NVRAM. Wonder why they differentiate between 'storage memory' and 'RAM' if it's all solid state in there.
Click to expand...
Click to collapse
It might be NVRAM .
But no one ever found out and so haven't I.....
Ace-ing all tests.
EmoBoiix3 said:
Well , if they still used motorised hard drives wouldn't it be too hot to operate considering how it heats up when playing games ?
Click to expand...
Click to collapse
I have to admit to being way out of touch with modern mobile phone technology. It seems the 1st generation iPhones had hard drives. And as far as I know, iPod's still do. I imagine that will change when Apple feels flash memory technology gets to the point where it reaches the longevity of HDDs of years past. But I really have no idea how hot a hand held device with a hard drive would get. I'd think the power consumption would be the greater consideration.
All backups are saved to /sdcard/clockworkmod/backup .
Click to expand...
Click to collapse
Thanks... that was easy enough to locate. I was just wondering if CWM restore was going to expect the backup to be in one specific location. But it seems way to clever to stumble on something that simple.
It might be NVRAM .
But no one ever found out and so haven't I.....
Click to expand...
Click to collapse
Really? ... Interesting.
TakuSkan said:
I have to admit to being way out of touch with modern mobile phone technology. It seems the 1st generation iPhones had hard drives. And as far as I know, iPod's still do. I imagine that will change when Apple feels flash memory technology gets to the point where it reaches the longevity of HDDs of years past. But I really have no idea how hot a hand held device with a hard drive would get. I'd think the power consumption would be the greater consideration.
Click to expand...
Click to collapse
What ? I just got mindf*cked......I didn't know iPods still have them
Really? ... Interesting.
Click to expand...
Click to collapse
I never experimented with hardware....
Ace-ing all tests.
Related
Just realized I accidentally deleted a picture from the SD card on my Hero awhile ago. The card is quite big and has never been close to being full so I'm wondering if there is a deleted folder on the card or some way to recover the file?
As far as I know, only recovery programs as used by the police, government etc can recover deleted files. You can download loads off the internet, but they are designed to reconstruct the magnetic residue on hard discs, don't know if it will work on a flash drive. Won't hurt to try though.
TheReverend210 said:
As far as I know, only recovery programs as used by the police, government etc can recover deleted files. You can download loads off the internet, but they are designed to reconstruct the magnetic residue on hard discs, don't know if it will work on a flash drive. Won't hurt to try though.
Click to expand...
Click to collapse
This person doesnt appear to know what they are talking about, no offense.
Data recovery is possible (in theory) on all types of media. When a file is deleted, the space it occupied is marked as unused by the system. The file isn't actually "deleted" until something else has written over its space.
however, due to the random nature of writes to the disk, and given that you said "while" I presume there will have been many writes to the disk since, the chances of recovering the file fully are reduced.
recovery software: a good free one is http://www.piriform.com/recuva
http://www.easeus.com/datarecoverywizard/free-data-recovery-software.htm
Is a good piece commercial software, but the free 1gb trial should be enough to give it a try.
"reconstructing magnetic residue" is what "professional" data recovery companies might attempt I guess. sounds a little fishy to me though.
So you say I don't know what im talking about with recovery programs and the like, then point the op to 2 recovery programs. Recovery programs which, no doubt, will try to reconstruct the files from the left over magnetism of the old file.
Incidentally, I know when a file is "deleted" the memory sectors are merely market as unused, so new data can be written there, but still the only way of recovering them files is with a recovery program.
use "testdisk"
http://www.cgsecurity.org/wiki/TestDisk
Actually there is no such folder exist on card which kept the deleted files or etc but don't worry just try a good third party data recovery software for the recovery of your data and files. Try Kernel for FAT and NTFS data recovery software for the recovery of your files.
TheReverend210 said:
So you say I don't know what im talking about with recovery programs and the like, then point the op to 2 recovery programs. Recovery programs which, no doubt, will try to reconstruct the files from the left over magnetism of the old file.
.
Click to expand...
Click to collapse
Yes, You DON'T Know. And since you don' know please, don't give anyone "information". Police recovery software... BUNKO! we use the plain old software everyone else uses and there is no recovery of "left over magnetism" shXt ... Go play in your sandbox after mom changes your diaper, and let the adults do the helping here.
A good way to recover deleted files from HTC Hero android phone is to use HTC android data recovery program, here's a good one: HTC Android phone data recovery
The data recovery program recovers data from both HTC Hero phone internal memory and SD card. Recommend that you try it.
rpimps said:
Just realized I accidentally deleted a picture from the SD card on my Hero awhile ago. The card is quite big and has never been close to being full so I'm wondering if there is a deleted folder on the card or some way to recover the file?
Click to expand...
Click to collapse
Hi, you can also use Kvisoft Data Recovery for Mac to recover deleted pictures from SD card of Hero phone,
Code:
Here is the detailed guide shows you how to recover files from mobile phone
kvisoft.com/tutorials/mobile-phone-data-recovery.html
hope this helps!
I did NOT paritition my gTablet after I installed CWM 0.8. My CM7-based ROMs have installed and worked just fine, including the new Market app. Do I need to partition?
The only real error I have had is the inability to transfer files (using Astro) between my internal 16 GB memory (/mnt/emmc/) and my installed 2GB sd card (/mnt/sdcard). Will partitioning help solve this?
TIA!
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Mantara said:
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Click to expand...
Click to collapse
I agree with Mantara. I think it reduces the chances of corrupting the tablet's data. Also, repartitioning is a bigger pain if you decide to do it later when you have a like a ton of files in your internal memory and have to back it up because repartitioning reformats the internal sd card.
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
butchconner said:
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
Click to expand...
Click to collapse
that's the approach i'll take for now. when time comes for officially official CM7 tablet releases, i'll reformat then. until then i'll just enjoy things as they are. thanks for the feedback, all.
When one problem fixed, it always lead to another problem...
During my own challenge with whatsapp history restore, i figured out one thing...
I don't know since what time...(cause i didnt aware of it before)...,
After I install an app from market, the \data\data\com.xxxxx\databases is linked to \firstboot\sqlite\com.xxxxx\ ???!!!!
I did a simple google search, \firstboot\ should be storing device data and not user data...
Why user data's databases now will automatically linked to firstboot ?!
I know storing in firstboot maybe faster, but causing the app failed to manipulate the database files in firstboot because access rights issues...
Hope someone interested to share your knowledge or find the answers together~~
Thank you!~
My own thought is ...Recovery ?! but no idea how to find the answer right now...
Update :
More info , \firstboot\ is in yaffs2 while \data\ is in ext3...
Firstboot is the data partition on the nand,
data is the data partition on the innersd.
I'm guessing the streak cant completely boot off the innersd, so it needs some of it's files to stay on the nand to boot properly.
Thanks, that could be the possible reason!
But do you know when Dell implemented this approach ?
I am pretty sure I dont have problem in backup/restore individual app's db files when i first receive my streak as 2.2
But this happen to me in rooting 2.2.2 [root] , 2.2.2 [restore to stock] , 2.3 [GS2.4/DSC 0.5].
TheManii said:
Firstboot is the data partition on the nand,
data is the data partition on the innersd.
I'm guessing the streak cant completely boot off the innersd, so it needs some of it's files to stay on the nand to boot properly.
Click to expand...
Click to collapse
I guess it was easier to make 512mb nand + 2gb innersd then it would be to put a 2gb nand into it.
Pretty much all other android devices of it's age use 512mb nands and nothing else.
TheManii said:
I guess it was easier to make 512mb nand + 2gb innersd then it would be to put a 2gb nand into it.
Pretty much all other android devices of it's age use 512mb nands and nothing else.
Click to expand...
Click to collapse
Oh yes, it is so called 512RAM + 2Gb ROM...
hm..not exactly...ROM should not be writable...
can som one tell me how i can dual boot my photon4g
lucky.79 said:
can som one tell me how i can dual boot my photon4g
Click to expand...
Click to collapse
You can't, yet.
This uses a method called 2ndinit myself and peetr_ have been looking into using this option.
mof9336 said:
This uses a method called 2ndinit myself and peetr_ have been looking into using this option.
Click to expand...
Click to collapse
so we can have one androidOS in the internal storage and another android OS in the external storage?? that's really really cool! Would photon 4g be the first phone to have more than 1 OS installed?
rituel said:
so we can have one androidOS in the internal storage and another android OS in the external storage?? that's really really cool! Would photon 4g be the first phone to have more than 1 OS installed?
Click to expand...
Click to collapse
Check my post: http://forum.xda-developers.com/showthread.php?t=1652411
I have used suggestions from Atrix thread and they worked fine. I have tried two or three times and each time I got some issues. I was copying stock 2.3.4 ROM onto SD card. One time USB ports were not working - no charging, no connection to computer with the cable. Next time there was problem with Play Market. I have tried different steps to reset its settings to no avail. It was giving error related to storage unavailability while downloading anything. I have removed Play Market completely, then somehow install it back, but the issue was not resolved. Now I think maybe it's a permissions issue.
Also device was really slow while running OS on sd-card (I have 32GB Transcend Class 10). It's fun to try but I don't see any practical use for it.
bloodhound_ said:
Check my post: http://forum.xda-developers.com/showthread.php?t=1652411
I have used suggestions from Atrix thread and they worked fine. I have tried two or three times and each time I got some issues. I was copying stock 2.3.4 ROM onto SD card. One time USB ports were not working - no charging, no connection to computer with the cable. Next time there was problem with Play Market. I have tried different steps to reset its settings to no avail. It was giving error related to storage unavailability while downloading anything. I have removed Play Market completely, then somehow install it back, but the issue was not resolved. Now I think maybe it's a permissions issue.
Also device was really slow while running OS on sd-card (I have 32GB Transcend Class 10). It's fun to try but I don't see any practical use for it.
Click to expand...
Click to collapse
hey can you write a detailed guide with instructions on how you got dual boot working on photon 4g please !? I cant afford to make mistakes and bork my phone >.>
And like you said as long as i can charge my phone and connect to my computer with one of the operating system its not a problem. But having dual boot will be really helpfull means I can check out more than one Rom simultaneously.
rituel said:
hey can you write a detailed guide with instructions on how you got dual boot working on photon 4g please !? I cant afford to make mistakes and bork my phone >.>
And like you said as long as i can charge my phone and connect to my computer with one of the operating system its not a problem. But having dual boot will be really helpfull means I can check out more than one Rom simultaneously.
Click to expand...
Click to collapse
The instructions I followed from Atrix page are very detailed. Link is here
It takes time to have a thread where most of the common questions answered. I think it is useless effort to start similar topic here, in addition - I don't have necessary time, knowledge and wish for this.
Anyway, if you do something wrong - you should always have full backup - then you risk nothing. Remember that if you got soft-bricked and recovery doesn't work, you can always use RSD lite to load stock 198_7 ROM, unlock, write new recovery and restore from initial backup.
The only difference between Atrix and Photon, (relative to this task) that you should keep in mind is the partition sizes. Partition table by LAKSHMAN in Play Market (or any other partition tool) can show you your partition sizes. I didn't guess to use these tools when I followed the instructions. Add up some 10 GB to each partition, just in case. When you partition your SD card, you should create partitions of the following size:
system - 420 MiB (stock ROM system partition size 408 MiB)
cache - 645 MiB (my current cache size on stock ROM is 610 MiB)
data - 2.6 MiB
I would also recommend to use script manager to launch scripts that will replace boot image from one to another. In other words, it will control where you will boot next time.
Note that Windows 7 is going mad about SD card with several partitions - sometimes you can see a single ntfs partition, sometimes it shows the ext3 partition, offering to reformat it.
bloodhound_ said:
The instructions I followed from Atrix page are very detailed. Link is here
It takes time to have a thread where most of the common questions answered. I think it is useless effort to start similar topic here, in addition - I don't have necessary time, knowledge and wish for this.
Anyway, if you do something wrong - you should always have full backup - then you risk nothing. Remember that if you got soft-bricked and recovery doesn't work, you can always use RSD lite to load stock 198_7 ROM, unlock, write new recovery and restore from initial backup.
The only difference between Atrix and Photon, (relative to this task) that you should keep in mind is the partition sizes. Partition table by LAKSHMAN in Play Market (or any other partition tool) can show you your partition sizes. I didn't guess to use these tools when I followed the instructions. Add up some 10 GB to each partition, just in case. When you partition your SD card, you should create partitions of the following size:
system - 420 GB (stock ROM system partition size 408 GB)
cache - 645 GB (my current cache size on stock ROM is 610 GB)
data - 2.6 GB
I would also recommend to use script manager to launch scripts that will replace boot image from one to another. In other words, it will control where you will boot next time.
Note that Windows 7 is going mad about SD card with several partitions - sometimes you can see a single ntfs partition, sometimes it shows the ext3 partition, offering to reformat it.
Click to expand...
Click to collapse
@PosterBoy : is this GB really?????? Man give some space to breathe..... lol
amitranjan said:
@PosterBoy : is this GB really?????? Man give some space to breathe..... lol
Click to expand...
Click to collapse
no im sure he miss typed he meant MB like he says in his post in the other thread. ok thanks man ill play around with it a bit so you're sure the phone wont be hard bricked right? I'm a very careful person I'm pretty confident I wont make mistakes all i want to know is everything every instruction given there is detailed enough and that nothing is omitted from it(meaning i dont have to do anything different except the partition sizes you mentioned here)
rituel said:
no im sure he miss typed he meant MB like he says in his post in the other thread. ok thanks man ill play around with it a bit so you're sure the phone wont be hard bricked right? I'm a very careful person I'm pretty confident I wont make mistakes all i want to know is everything every instruction given there is detailed enough and that nothing is omitted from it(meaning i dont have to do anything different except the partition sizes you mentioned here)
Click to expand...
Click to collapse
Yes, everything else from that topic applies. Be careful when you use dd. If you specify wrong drive names you might be in trouble (this will require loading sbf with RSD lite to fix partitions, I guess).
The longest part is to extract boot.img, edit the configuration file there and pack the whole thing back to andorid .img format. It requires you to install Android SDK with some tools that might not work straight away.
Hi,
sorry to disturb you but I do have some little "problems" with my HTC ONE AT&T.
I bought this phone, simunlocked already, and with revone I put it SOFF and than I "converted" it to international version of it (thinking that keeping the AT&T versionI coudn't install internatinal rom...I understood I was wrong but anyway I'm from Europe so I like to have international CID).
Few strange things happened (I'm not sure if it's normal or not).
The first one is that it seems that my phone is loosing memory, it's supposed to have 32 Gb but, as you can see from the attachment, it has just 25.5 Gb, is that normal (I do use a really slim rom, just 150 Mb, but anyway it's the same with any rom I install)...is it normal? Is it possible to format ALL and restore all the memory to an initial state (where there shall be at least 30-31 Gb avaialble I think)??
The second is that sometimes, after installing a rom, exiting the aroma installer, the screen become black instead of getting me back to the recovery (actually it seems it brings me back to the recovery but the screen goes off and no way to turn it on...so force reboot and than everything works fine....but sometimes reinstalling the same rom over and over it works fine, it bring me back to recovery and I can normally reboot the system), is it normal?
Than during the boot it says that this is a test device and so on (a sentence written under the HTC logo), is there a way to remove it? I thought I could do it with revone (I thought it was the tempered flag) but I tried the following thing and isn't removing it even if it says succesfully: Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t (but maybe it's another thing).
So is there a way to remove that sentence?
Thanks,
Massimiliano
Storage size is normal to show 25.59... As android system uses the rest that you don't see
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Storage size is normal to show 25.59... As android system uses the rest that you don't see
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there a way to check if some part of the memory is lost/full from previous rom and it wasn't clean well??
I'm using this rom http://forum.xda-developers.com/showthread.php?p=50698141 it's realy minimal, without NOTHING, even the play store was missing...how can it use 7 Gb of memory?
m.zambonelli said:
Is there a way to check if some part of the memory is lost/full from previous rom and it wasn't clean well??
I'm using this rom http://forum.xda-developers.com/showthread.php?p=50698141 it's realy minimal, without NOTHING, even the play store was missing...how can it use 7 Gb of memory?
Click to expand...
Click to collapse
Just go into settings and select storage. It tells you what is being used and by what.. Memory is used like a hard drive and it is formatted so the system can use it properly. That being said on 32GB you loose about 2GB to the formatting. Then the system and everything else on he phone uses it. There is also a swap file of several GB that is used when the 2GB of RAM is too full. There are also a couple of cache that use that memory as well. What you are seeing is typical storage usage of most phones running on Android. You loose around 7 to 10 GB to the system.
m.zambonelli said:
Is there a way to check if some part of the memory is lost/full from previous rom and it wasn't clean well??
I'm using this rom http://forum.xda-developers.com/showthread.php?p=50698141 it's realy minimal, without NOTHING, even the play store was missing...how can it use 7 Gb of memory?
Click to expand...
Click to collapse
Well is like installing Linux on a computer.. The easy setup sets different partitions that the system is going to use for multiple purposes hence losing some GB in the process to be able to perform as required.
Sent from my HTC One using XDA Premium 4 mobile app
Solarenemy68 said:
Just go into settings and select storage. It tells you what is being used and by what.. Memory is used like a hard drive and it is formatted so the system can use it properly. That being said on 32GB you loose about 2GB to the formatting. Then the system and everything else on he phone uses it. There is also a swap file of several GB that is used when the 2GB of RAM is too full. There are also a couple of cache that use that memory as well. What you are seeing is typical storage usage of most phones running on Android. You loose around 7 to 10 GB to the system.
Click to expand...
Click to collapse
Ok I do understand that but as you can see from the screenshot attached in Setting-Storage it says Total Space 25.59Gb, available 24 and something.
I would like to see/understand/access the remaining 6/7 Gb that are not showed there!
I've the feelings that the memory is decreasing every time I'm installing a rom, I also formatted EVERYTHING. loosing the operating system (than I had to push a rom in the memory) but still is like that!
Any suggestion or idea on how to see what is inside those 7 Gb "missing" from the total space?
Any way to format them?
It's not missing, open a terminal window and execute df command - that will list partitions. Data is 25.6GB, system 1.8GB, cache 600MB, etc. All 32GB are there, but are partitioned for different aspects of the OS, you can't change that.
cschmitt said:
It's not missing, open a terminal window and execute df command - that will list partitions. Data is 25.6GB, system 1.8GB, cache 600MB, etc. All 32GB are there, but are partitioned for different aspects of the OS, you can't change that.
Click to expand...
Click to collapse
Thank you so much for your answer, I'm slowly understanding how this is working
I am than wondering if it's possible that multiple install of things (updating hboot, recovery, different rom and so on) can leave some "dirty" file or folder meaning that some not necessary files are still there taking space for nothing.
This is my df results, can you check if, for your opinion, everything is fine or if there is some folder too big as it shall be?
Another question is if it's possible to just delete ALL the 32Gb, removing all the partition and stuff and then in some way restore it to a "default" (I don't know what I'm actually saying, I hope you understood what I mean...mainly like in any windows pc you can just remove all the partition, format all and reinstall the OS from zero).
Thanks a lot,
Massimiliano
p.s. I'm including the screenshot of my df result
m.zambonelli said:
Thank you so much for your answer, I'm slowly understanding how this is working
I am than wondering if it's possible that multiple install of things (updating hboot, recovery, different rom and so on) can leave some "dirty" file or folder meaning that some not necessary files are still there taking space for nothing.
This is my df results, can you check if, for your opinion, everything is fine or if there is some folder too big as it shall be?
Another question is if it's possible to just delete ALL the 32Gb, removing all the partition and stuff
Click to expand...
Click to collapse
It looks normal, you can't delete all of the partitions it would brick the phone. Flashing roms doesn't leave old files, because the install wipes the system first.
m.zambonelli said:
Thank you so much for your answer, I'm slowly understanding how this is working
I am than wondering if it's possible that multiple install of things (updating hboot, recovery, different rom and so on) can leave some "dirty" file or folder meaning that some not necessary files are still there taking space for nothing.
This is my df results, can you check if, for your opinion, everything is fine or if there is some folder too big as it shall be?
Another question is if it's possible to just delete ALL the 32Gb, removing all the partition and stuff and then in some way restore it to a "default" (I don't know what I'm actually saying, I hope you understood what I mean...mainly like in any windows pc you can just remove all the partition, format all and reinstall the OS from zero).
Thanks a lot,
Massimiliano
p.s. I'm including the screenshot of my df result
Click to expand...
Click to collapse
I don't want to sound like an ass but what you have is normal so you are going to have to live with it. There is no way to get more memory cleared up unless you have absolutely nothing but the ROM running and nothing else downloaded and installed. Everyone who has the 32GB version of this phone has the same amount of memory as you. Some have less as they have installed other apps. added music, movies, and pictures.
The ONLY way you could get more memory is to get the 64GB version of this phone. I knew it did not have a card slot so I took that into account and bought the 64GB version so I would have plenty of space for anything I wanted.
cschmitt said:
It looks normal, you can't delete all of the partitions it would brick the phone. Flashing roms doesn't leave old files, because the install wipes the system first.
Click to expand...
Click to collapse
Ok, Thanks
Solarenemy68 said:
I don't want to sound like an ass but what you have is normal so you are going to have to live with it. There is no way to get more memory cleared up unless you have absolutely nothing but the ROM running and nothing else downloaded and installed. Everyone who has the 32GB version of this phone has the same amount of memory as you. Some have less as they have installed other apps. added music, movies, and pictures.
The ONLY way you could get more memory is to get the 64GB version of this phone. I knew it did not have a card slot so I took that into account and bought the 64GB version so I would have plenty of space for anything I wanted.
Click to expand...
Click to collapse
If I knew that 32 Gb meant 25 I would consider to buy the 64 Gb too ... but other than te space I just wanted to understand IF it was normal that, after just flashed a really basic clean rom (just 156 mb of rom) it was normal to have just 25 Gb free (no other additional apps, no photo and so on) ... it's normal, ok, I'll be happy with that and next phone I'll consider a 64Gb version of it.
Thanks everyone for the reply