So I know when flashing roms sometimes it will erase the SD Card, Okay well I forgot about 5 pictures I had taken and was like oh well, so when I went to go load all my stuff back on it, My SD card is empty but it says 6GB is being used, which is about right what it was but there are NO files on it... Where are the files??? Using Root explorer and show hidden stuff on the computer still dont know where the files are at....
did you flash a 4.2 rom?
I wanted to try out cm mod. Then went back to stock 4.2.2 I don't care if I lost some stuff. But its Stikl there but I can't see it.
Sent from my HTC One using xda premium
i know that your suppose to wipe before flashing a 4.2 rom.
the file system is in a different spot so it leaves the old system there.
I do not know how to get back the free space beside formating and reflashing the system.
xile6 said:
i know that your suppose to wipe before flashing a 4.2 rom.
the file system is in a different spot so it leaves the old system there.
I do not know how to get back the free space beside formating and reflashing the system.
Click to expand...
Click to collapse
Ive already formatted system and it still shows stuff stored there.
Not to sure then.
Only had the phone for a week so haven't gotten use to the file system yet.
I just know it's set up different from other phones.
I had the same experience also... what I did was I went to CWM recovery and format /sdcard and I did wipe user data/factory reset...
This was happened when I flashed 4.2.2 onto 4.1.2 without wiping anything....
transfer everything from your sdcard to your computer then format sdcard in cwm and transfer your files back and they should be in the right place
Ive got the same problem. Stock rom never rooted, "OTHER" in storage taking up 6.7GB.
I have looked at clearing junk files with CLEAN MASTER app but my cache files only takes up 33mb.
Did anyone look what "OTHER" in storage was when they got their brand new phone? Does Sense 5 really takes up over 6GB?
EDIT:
A few people confirmed that the phone have about 26GB of space out of 32GB brand new, so yeah Sense 5 DOES take about 6GB of space!
http://forum.xda-developers.com/showthread.php?t=2265598
My nexus 6 is showing the wrong storage size. I have a 64gb model(says on the box 64gb) I bought new. However, I am only seeing 23gb. I think it may have to do with the fact it was backing up from my G2, which is a 32gb device, which only has 23gb of storage available. I did a factory reset from android, but no go. Any ideas?
if you are unlocked then install the latest twrp and run the fix storage inside the wipe options.
did you download the images from goolge and run flash all, and or flash userdata.img manually?
It seems to come from the fact that the userdata.img is made for a 32 gig device, so when flashing it it formats your /sdcard as if you had a 32 gig device.... at least to my understanding.
Either way, see this thread for info on how to fix without wiping.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Thank you I got that working. Now, it looks like my bootloader is locked and it won't let me unlock it. When I try it I get the message Not supported command in current status!
Any ideas?
Developer options/Allow OEM unlock?
I haven't enabled dev options on my N6 this time (after a year of root) so I can't see the option myself, so bear with me if I'm wrong...
It does, but when I start my device up I'm required to swipe in my password, before getting android to completely load.
That's a different option which I discovered myself just the other day. I'm not clear on how this relates to your question about OEM unlock...?
nvm, figures it out. I just did another clean wipe and it's now all working correctly.
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
-UPDATE:
Here are three solutions for updating:
a) The downloaded .zip file has to be moved to /data (if wanted, into some subfolder of your choice. ES-File Explorer needs root for that) Then flash via TWRP.
b) Use flashify, choose copy to safe location (had some FC's afterwards)
c) Use cm-recovery, update via cm-updater (not yet confirmed)
davedophin said:
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
Click to expand...
Click to collapse
1. I don't think so. For this we should need an updated recovery supporting this feature. Furthermore, the feature is not fully ready, imho
2. I don't know. Never had this problem.
Written with my XT1068 using Tapatalk on CM13
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Dieselhorst said:
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Click to expand...
Click to collapse
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Mavireck said:
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Click to expand...
Click to collapse
I believe you when you say Flashify can flash the rom. But as said, it's all way to complicated for the 'average' user. Especially because of the encryption, which causes the sd card to be unseen by, for example, your recovery or your pc. These things have to be solved first!
Written with my XT1068 using Tapatalk on CM13
Sure, that's why I say
This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Click to expand...
Click to collapse
.
I think we should stop debate now because we think the same
Mavireck said:
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Click to expand...
Click to collapse
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
davedophin said:
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
Click to expand...
Click to collapse
The twrp team is awesome. They will find a fix.
I only tried flashing the ROM but i think you can flash at the same time gapps.
Alright, Flashify works, if you pick the option "copy to safe directory" or similar. "use provided path" doesnt work for me.
But after the update, Nova Launcher keeps crashing and titanium backup doesnt show up on the app drawer anymore, but is still installed and cant be uninstalled to reinstall. pretty weird. So for me, this option doesnt really work either.
I copy the update zip file to \Data\Media\0\twrp and i can update
Anyone knows if the SuperSU 2.60 works in the CM13 Moto G2014???
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
bhachech said:
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I haven't used TB or Nova... CM 13 on Titan is running very well for me. As expected, in these early nightlies, some CM features are not fully implemented but that has not hindered my ability to use it as a daily driver for the past couple of weeks.
davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I use Nova and TB, no problems here
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
ygtenos said:
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
I've tried like 4 releases of CM13 so far, never had a problem like that. But I only used builds from december, so I would suggest you go for a newer version, after a backup of course
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
So guys, I updated to todays build by moving it to the /data partition and then using twrp. Works like a charm! Thanks everyone for your help!
davedophin said:
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
Click to expand...
Click to collapse
Does not work for me (Moto Thea)
Hi,
I recently exchanged my old 64 GB Nexus 6 for a new/refurbished one due to a failed USB port. I installed the latest stock ROM, unlocked the bootloader, rooted, and used Titanium Backup to restore the data to a handful of apps. While doing this, I got a warning about my device being low on space. From research, I learned that I should've disabled Mount Namespace Separation in SuperSU. So now, no matter what I do, my system files are taking up 35 GB after doing a complete wipe with TWRP and reinstalling the stock ROM.
Is this a problem with the partition table? No matter what the issue is, does anyone know how to fix it? I'm not super experienced with rooting beyond basic tasks, so I'm struggling to come up with ideas.
Thanks!
Nevermind!
It looks like resizing the partitions in TWRP fixed my problem. Sorry for being a noob .
For future reference, don't flash userdata.img in the stock images if you want to avoid resizing partitions in TWRP. That image resizes internal storage to 32GB and ignores the remainder, leading to /system taking more space than it should.