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)
Greetings,
I have the Fi version of the Moto X4 Android One, running Oreo 8.1.
I do not seem to be able to allow installation from Unknown Sources. In my Settings menu under Security there is nothing about allowing Unknown Sources. Is there a trick to this?
Thanks in advance for any assistance.
~ Phil
PKW57 said:
Greetings,
I have the Fi version of the Moto X4 Android One, running Oreo 8.1.
I do not seem to be able to allow installation from Unknown Sources. In my Settings menu under Security there is nothing about allowing Unknown Sources. Is there a trick to this?
Thanks in advance for any assistance.
~ Phil
Click to expand...
Click to collapse
I believe starting with Oreo, you get prompted as needed per application. You should not need to do anything ahead of time.
Check permission on the app you are using to open the apk.
Thanks!
jhedfors,
Thanks for the quick response. I will give your suggestions a shot. This is my first exposure to Oreo. My previous phone ran Marshmallow. Need to be able to sideload to get root, among other things.
Just FYI in case others are interested ... Although Android One is pretty close to pure Android, on the Moto X4 Motorola has disabled the option to format the SD card as internal memory. They have also disabled the ability to move apps to the card, only media can be stored on the card. Other than that I find this to be a pretty solid phone.
Thanks again,
~ Phil
PKW57 said:
...
Just FYI in case others are interested ... Although Android One is pretty close to pure Android, on the Moto X4 Motorola has disabled the option to format the SD card as internal memory. They have also disabled the ability to move apps to the card, only media can be stored on the card. Other than that I find this to be a pretty solid phone.
Thanks again,
~ Phil
Click to expand...
Click to collapse
An observation about internal space: I have noticed that LOS16 does have a fair bit more available space for apps than stock. I have not ran out of space with either though.
Worked!
Thanks again!
It worked just as you described.
PKW57 said:
Just FYI in case others are interested ... Although Android One is pretty close to pure Android, on the Moto X4 Motorola has disabled the option to format the SD card as internal memory. They have also disabled the ability to move apps to the card, only media can be stored on the card. Other than that I find this to be a pretty solid phone.
Click to expand...
Click to collapse
Wrong, moto X4 uses File Based Encryption, it's because of that the phone don't have the option to format SD as internal storage, Pie supports adoptable storage with FBE, but it wasn't working well on LOS16.
Hi,
I wasn't able to find any solid proof of my phone's storage being encrypted. I cannot find the encryption option anywhere in the phone settings, so I cannot make sure this way, and it leaves me with three options:
1) The phone's internal storate is encrypted by default as it is mandatory for Android 9 devices and it cannot even be turned off, thus this option is lacking from settings.
2) The phone's internal storage is not encrypted and cannot even be, because Huawei decided to take the encryption out of EMUI.
3) I missed something.
Which one is it?
Thank you for your thoughts
Rasokoule said:
Hi,
I wasn't able to find any solid proof of my phone's storage being encrypted. I cannot find the encryption option anywhere in the phone settings, so I cannot make sure this way, and it leaves me with three options:
1) The phone's internal storate is encrypted by default as it is mandatory for Android 9 devices and it cannot even be turned off, thus this option is lacking from settings.
2) The phone's internal storage is not encrypted and cannot even be, because Huawei decided to take the encryption out of EMUI.
3) I missed something.
Which one is it?
Thank you for your thoughts
Click to expand...
Click to collapse
It Is encrypted by default, you can't disable it
madoxx77 said:
It Is encrypted by default, you can't disable it
Click to expand...
Click to collapse
madoxx7, How do you know its encrypted by default ?
I've contacted Huawei about it, they told me encryption wasn't supported anymore.
They told me that you have to root your phonr if you want to encrypt it, but they absolutely don't allow encryption of the internal storage.
Frankwatt said:
madoxx7, How do you know its encrypted by default ?
I've contacted Huawei about it, they told me encryption wasn't supported anymore.
They told me that you have to root your phonr if you want to encrypt it, but they absolutely don't allow encryption of the internal storage.
Click to expand...
Click to collapse
I know it cause TWRP cannot access internal storage cause it's encrypted(shows random files), yeah they probably meant you need root to decrypt it, cause it's encrypted by default and you cannot do anything about it without roor.
Good to know, thanks