storage issues - Nexus 6 Q&A, Help & Troubleshooting

now I'm not new to android but I just for this nexus 6 with 64 gigs of storage... for some reason the system is 35 gigs anyone know how I can slim that down

Did you manually flash a stock ROM, and did you flash the userdata.img? If so, back up everything as I believe you'll need to do a factory reset to fix the problem. The userdata.img by default is for a 32GB system.

Strephon Alkhalikoi said:
Did you manually flash a stock ROM, and did you flash the userdata.img? If so, back up everything as I believe you'll need to do a factory reset to fix the problem. The userdata.img by default is for a 32GB system.
Click to expand...
Click to collapse
I flashed the img file from scratch... that I pulled off of X d a

For curiosity sake, link please?
In any case, never flash userdata.img on a 64GB device; this means you cannot use the batch file Google includes with their ROM packages. The image partitions internal storage as 32GB and leaves the remainder unallocated. Android lumps the unallocated space with system.

Related

PSA: flashing a factory image WILL WIPE YOUR STORAGE PARTITION!!!!!

I know some people may read this and call me a n00b, or whatever....deal with it lol
I'm coming from a Nexus S, and this is my first android with the new unified storage, rather than the old method that was partitioned for rom storage and sd/usb storage. I just flashed a Nexus 4 factory image for the first time ever, and when I did all my files on my storage partition were wiped. This includes my nandroids, all my apk backups, titanium backups, my roms, kernels, gapp zips, pictures, music.....EVERYTHING!!!!!!! When I rebooted, there was not ONE file on my phone that wasn't part of the factory image!! When I did a factory flash on my nexus s, since there were separate partitions, my storage was completely untouched. The only thing similar that would wipe it was a bootloader unlock. This is (obviously) no longer the case. My only saving grace is that at least half my apks are stored in my box account (thank you box for the free 50gb for registering with an LG device ) and my pics were set to auto-sync with ubuntu one. Everything else is lost forever, though
IF YOU HAVE TO FLASH A FACTORY IMAGE, BE SURE TO BACK UP YOUR STORAGE PARTITION FIRST!!!!
You have been warned
Assuming you used the flash-all script, just remove the -w option
I flashed back to stock, radio, system, boot loader etc, but just didn't flash the data partition (or whatever its called) and the internal SD was untouched.
Admittedly I got stuck in a boot loop, but I just powered off, booted in to boot loader and flashed TWRP from fast boot. Factory reset and cleared cache and I still had everything saved
Sent from my CM10.1 Nexus 4
crachel said:
Assuming you used the flash-all script, just remove the -w option
Click to expand...
Click to collapse
nope. i flashed each individual .img file the userdata.img is what wiped the storage....apparently the device thinks the two are connected. maybe they really are....i'm not an expert in this area, to say the least.
Tom540 said:
I flashed back to stock, radio, system, boot loader etc, but just didn't flash the data partition (or whatever its called) and the internal SD was untouched.
Admittedly I got stuck in a boot loop, but I just powered off, booted in to boot loader and flashed TWRP from fast boot. Factory reset and cleared cache and I still had everything saved
Sent from my CM10.1 Nexus 4
Click to expand...
Click to collapse
yup...you're correct!! twrp knows the difference between actual userdata and storage...it seems that fastboot does NOT know the difference, unfortunately. I figured since twrp is safe to wipe the data with, fastboot should be too.
hp420 said:
nope. i flashed each individual .img file the userdata.img is what wiped the storage....apparently the device thinks the two are connected. maybe they really are....i'm not an expert in this area, to say the least.
Click to expand...
Click to collapse
I think the title "userdata" should have given you a clue about what it was going to do, i.e. flash over the user data and erase what was previously there
Sent from my CM10.1 Nexus 4
Tom540 said:
I think the title "userdata" should have given you a clue about what it was going to do, i.e. flash over the user data and erase what was previously there
Sent from my CM10.1 Nexus 4
Click to expand...
Click to collapse
As I said before, my last android was a Nexus S that was partitioned, so the data was separate from the usb/sd storage space. When I flashed the userdata.img on my Nexus S it didn't delete all my sd/usb storage....only the rom's data partition. Based on my previous experience, and considering this is the first time I've flashed a factory image to my Nexus 4, why would the name "userdata" give me any clue that something other than the "userdata" would be wiped???? Even if you don't take my previous experience into account, why would the name "userdata" ever have anything to do with "sd/usb data"???? userdata and sd storage are two separate things. Yes, they are stored in the same partition now, but that doesn't mean they are the same thing. userdata is tied to your rom, and your sd storage is for any additional personal files you decide to store there.
The problem is that the fake SD is on /data/media, so flashing a data IMG overwrites the entire partition and deletes your stuff. Lgnpst doesn't though, not sure why. Perhaps try that next time or just don't flash data.
Sent from my LG-LS970 using xda app-developers app
There are also very clear guides on here that tell you that flashing userdata will clear everything. Flash everything except that one next time.
Sent from my Nexus 4 using Tapatalk 4 Beta

Low storage issue: What's taking up all the space and how do I fix it?

So My Total drive space is calculated at 25.5gb. Okay I know that 32 gigs isn't really 32 gigs and that the system and rom takes up space, but my available storage for use is only 19gb. After a full wipe and custom rom install, then connecting to the computer and erasing the entire internal storage it still only shows up as 19gb. I even checked my recovery and I only have 2 backups in there, and I freed unused files.
Will factory resetting possibly fix this/will it remove root via htcdev?
mblacki said:
So My Total drive space is calculated at 25.5gb. Okay I know that 32 gigs isn't really 32 gigs and that the system and rom takes up space, but my available storage for use is only 19gb. After a full wipe and custom rom install, then connecting to the computer and erasing the entire internal storage it still only shows up as 19gb. I even checked my recovery and I only have 2 backups in there, and I freed unused files.
Will factory resetting possibly fix this/will it remove root via htcdev?
Click to expand...
Click to collapse
I would try going into recovery and erasing all partitions (advanced wipe) from the phone, backing up everything you need onto your computer of course. After wiping everything you can side load a rom onto the phone to then flash.
Flashing an RUU will unroot, but factory resetting within a ROM or recovery will keep root.
JasSingh93 said:
I would try going into recovery and erasing all partitions (advanced wipe) from the phone, backing up everything you need onto your computer of course. After wiping everything you can side load a rom onto the phone to then flash.
Flashing an RUU will unroot, but factory resetting within a ROM or recovery will keep root.
Click to expand...
Click to collapse
Fixed, thank you. I lost my backups but my storage is there now.
mblacki said:
Fixed, thank you. I lost my backups but my storage is there now.
Click to expand...
Click to collapse
Did you remember to transfer the backups to your computer before wiping?
At least you've got your space back
JasSingh93 said:
Did you remember to transfer the backups to your computer before wiping?
At least you've got your space back
Click to expand...
Click to collapse
It's not that I didn't remember, it's that when I updated to cwm 6.0.4.5 I wasn't able to find my backups in the cwm-backups folder anymore, like they were hidden. So no I didn't transfer but everything is okay now and I made a new backup!
mblacki said:
It's not that I didn't remember, it's that when I updated to cwm 6.0.4.5 I wasn't able to find my backups in the cwm-backups folder anymore, like they were hidden. So no I didn't transfer but everything is okay now and I made a new backup!
Click to expand...
Click to collapse
Ah okay, glad to hear you got the space back though!
Enjoy this beast of a phone

[Q] encryption unsuccessful?

So, I figured I'd set up the scenario first in hopes to help make this understood:
1. Got the device
2. Booted/Updated to 5.0
3. Rooted using CF Autoroot
4. Remained on Stock 5.0 + Root (Stock bootloader/recovery)
- 1st "OFFICIAL" ROM came out so like the gentle flash'aholic I am, I rushed and downloaded [ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara]
1. I installed TWRP via the Google Play App, (I think i was on 2.8.3.0)
2. Rebooted into TWRP, and did a FULL BACKUP (saved locally)
3. Formatted Davlik, System, Data, Internal Storage, Cache
4. Rebooted into TWRP, pushed the ROM files ([ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara])
5. Flashed the ROM, GAPPS, SuperSU, Rebooted.
After about a minute of booting into the new ROM (new red loading animation) I started to get "encryption unsuccessful", and the only option was to factory reset phone, after which nothing happened, my guess was because of the custom recovery.
What was my error, and how do I prevent this from happening again?
My thinking is that wiping the Cache/System/Data/Internal/Davlik partitions somehow messed up some function someplace?
To fix it I took steps in this thread (http://forum.xda-developers.com/moto-x-2014/help/lollipop-update-failing-how-troubleshoot-t2961633) - thanks @randyklein
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
How do I avoid this in the future if I decide to try a custom ROM/Recovery again?
Same problem...
Format data in twrp to fix encryption error
CWick4141 said:
Format data in twrp to fix encryption error
Click to expand...
Click to collapse
will i lose my twrp backup ?
marquesini said:
will i lose my twrp backup ?
Click to expand...
Click to collapse
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
I did a full wipe and then formated the data, then installed the ROM,gaaps,and supersu beta.
Got it working with root.
Shemploo said:
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
Click to expand...
Click to collapse
Formatting data in twrp is not the same as wiping data
CWick4141 said:
Formatting data in twrp is not the same as wiping data
Click to expand...
Click to collapse
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Shemploo said:
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Click to expand...
Click to collapse
You would know if you formatted data since it erases everything including internal storage
CWick4141 said:
You would know if you formatted data since it erases everything including internal storage
Click to expand...
Click to collapse
Alright, I booted TWRP, and clicked "Data" then "Repair/Change File System" it's currently showing f2fs, my format options are EXT2, EXT3, EXT4, FAT.
I think I want EXT4 right?
UPDATE: I tried EXT4 as every partition seems to use it, and from past experience, and It's working!.
Thank you for nudging me in the right direction.
edit: wrong thread

Xiaomi Mi A2 (jasmine) can I update stock ROM via TWRP

Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?
iHusky said:
Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?
Click to expand...
Click to collapse
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?
Phil_Smith said:
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?
Click to expand...
Click to collapse
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP
iHusky said:
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP
Click to expand...
Click to collapse
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.
Phil_Smith said:
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.
Click to expand...
Click to collapse
I tried MiFlash, but without wipe anything, and it don`t upgrade version of system
But if I must, flash 2 slots A/B using MiFlash or one slot (A) is for system?
You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif
pfss said:
You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif
Click to expand...
Click to collapse
So, I don't need
to flash second slot?
iHusky said:
So, I don't need
to flash second slot?
Click to expand...
Click to collapse
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.
pfss said:
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.
Click to expand...
Click to collapse
I tried using fastboot and MiFlash but after all it stuck on bootloader
iHusky said:
I tried using fastboot and MiFlash but after all it stuck on bootloader
Click to expand...
Click to collapse
I just updated mine to November patch downloaded from here: https://mifirm.net/downloadzip/4197
I entered fastboot mode, executed
Code:
fastboot boot my_twrp_image_file.img
In TWRP made de wipes, flashed the ROM, changed slot and rebooted phone. It looks like it's normal.

Question UNABLE TO BACK UP ANY ANDROID 12 MIUI OR CUSTOM ROM (internal storage 0mb) in TWRP

I'm able to use backup & restore in Android 11 custom or miui rom. but unable to use it when i flashed android 12 roms.
Can anyone walk me through how to fix this.
Did the ff workaround in youtube as well in any similar post but still not working.
1. Advance wipe > click data >Repair or Change File System > Change File System to EXT2 & EXT4
2. Format data
This process is temporarily working the internal storage is visible, but after booting to system and go back to twrp recovery, the internal storage appears 0mb again.
I flashed stock rom/ eu rom as well in TWRP as i read this is worked with them. but not on my end.
Kindly help me to solve this issue please.
TWRP is not yet compatible with Android 12, it can't decrypt the internal storage. You can't fix it until TWRP (or some other recovery) solves Android 12 support.
I think in theory you might be able to back up the ROM to an unencrypted storage like an SD Card or OTG USB drive, but I'm not sure (and I'm even less sure if such backup could even be successfully restored if you back the partition up without decrypting).
Use otg usb
rufio85 said:
I'm able to use backup & restore in Android 11 custom or miui rom. but unable to use it when i flashed android 12 roms.
Can anyone walk me through how to fix this.
Did the ff workaround in youtube as well in any similar post but still not working.
1. Advance wipe > click data >Repair or Change File System > Change File System to EXT2 & EXT4
2. Format data
This process is temporarily working the internal storage is visible, but after booting to system and go back to twrp recovery, the internal storage appears 0mb again.
I flashed stock rom/ eu rom as well in TWRP as i read this is worked with them. but not on my end.
Kindly help me to solve this issue please.
Click to expand...
Click to collapse
Case_ said:
TWRP is not yet compatible with Android 12, it can't decrypt the internal storage. You can't fix it until TWRP (or some other recovery) solves Android 12 support.
I think in theory you might be able to back up the ROM to an unencrypted storage like an SD Card or OTG USB drive, but I'm not sure (and I'm even less sure if such backup could even be successfully restored if you back the partition up without decrypting).
Click to expand...
Click to collapse
Cisuwek said:
Use otg usb
Click to expand...
Click to collapse
In my opinion it's only possible to backup encrypted storage as in A12 if you flash DfE but then you'll have to format and later you're decrypted and in future you can backup via TWRP.
But you can copy actual personal files with a file manager, if android is booted up, to external storages or internal micro SD. android internal app data can't copied.
Laptapper said:
In my opinion it's only possible to backup encrypted storage as in A12 if you flash DfE but then you'll have to format and later you're decrypted and in future you can backup via TWRP.
But you can copy actual personal files with a file manager, if android is booted up, to external storages or internal micro SD. android internal app data can't copied.
Click to expand...
Click to collapse
You can install cutom roms, flash magisk, kernel and other stuff. The memory is only encrypted, the rest works perfectly fine. Have you checked on the latest recovery?
A new kernel was flashed an hour ago. I have made a backup of the boot and dtbo images. It really works
Not checked to backup complete rom, but suppose it's possible with otg
Cisuwek said:
You can install cutom roms, flash magisk, kernel and other stuff. The memory is only encrypted, the rest works perfectly fine. Have you checked on the latest recovery?
A new kernel was flashed an hour ago. I have made a backup of the boot and dtbo images. It really works
Not checked to backup complete rom, but suppose it's possible with otg
Click to expand...
Click to collapse
.....Not checked to backup complete rom, but suppose it's possible with otg....?
But this is what he wants to do, or not?
Cisuwek said:
You can install cutom roms, flash magisk, kernel and other stuff.
Click to expand...
Click to collapse
I guess (I was in fact asking about exactly this in another thread recently), but then if the install script tries to modify the data partition in any way (which remains encrypted with current recoveries under Android 12), you're almost certainly screwed and at best the installation will fail, at worst you'll have to reinstall everything.
Thanks for the reply guys..this already solved..with the help of @Laptapper in other thread. Using orangefox, dfe,
How to flash a Android 12 ROM without decryption problem?
I've been struggling to flash Android 12 without my internal storage to be unaccessible by TWRP... I simply can't decrypt my data and the only way to fix it is to format data and revert back to a Android 11 ROM. Did anyone manage to flash Android...
forum.xda-developers.com
here's the thread.
Case_ said:
I guess (I was in fact asking about exactly this in another thread recently), but then if the install script tries to modify the data partition in any way (which remains encrypted with current recoveries under Android 12), you're almost certainly screwed and at best the installation will fail, at worst you'll have to reinstall everything.
Click to expand...
Click to collapse
Previously I had a Redmi note 7. On the encrypted partition, I could also install everything in the same way. I am not a specialist, my knowledge has ended here.

Categories

Resources