Related
Hello one and all, please dont flame me for this post but my SD Card is bolloxed and i need to get all my apps onto a new one.
I have new a 8 GIG Class 6 to transfer to i have already partitioned with Ubuntu but i dont know how to copy my apps off the old card to the new
one and for those loaded apps on my phone to stay working.
I have used the search on this forum but there is so many different ones i have read i am now totally confused.
I did root my phone myself and put on a Cyanogen rom so i am fairly ok with
certain stuff but this has me proper confused is there just one one click method, i read something about "SwitchRom"
i dont want to lose all my apps but this is getting a bit desperate now
Thanks
Your apps are never lost even if you use a new sdcard and use Ubuntu to copy and paste the apps to the new card, you still have to reinstall alll the protected apps. So depending on how many apps you have installed , I would do a wipe and reinstall them all.
Or do a nandroid backup, don't forget you might have to run fix_permissions if you get any errors.
Hello, need some help here!
I unlocked the bootloader without backing up any of my files... I know I'm stupid... I was too carried away by the 4.4.2 improvements to think properly...
I tried this recovery method from this thread:
http://forum.xda-developers.com/showthread.php?t=1994705&nocache=1
and another similar one
But in both cases I am stucked at the first step: adb saying device is offline in cygwin.
Adb in the android sdk works fine. I'm on 4.4.2 ota from stock 4.2.2 (rogers), managed to flash twrp and got root.
I've tried revoking usb authorization but no go.
Is there any mighty guru who can help me out? Is there some way of mounting the internal storage in windows so that i can image the whole internal storage?
Any help greatly appreciate! Don't want to lose precious photos of my family...
cilix said:
Hello, need some help here!
I unlocked the bootloader without backing up any of my files... I know I'm stupid... I was too carried away by the 4.4.2 improvements to think properly...
I tried this recovery method from this thread:
http://forum.xda-developers.com/showthread.php?t=1994705&nocache=1
and another similar one
But in both cases I am stucked at the first step: adb saying device is offline in cygwin.
Adb in the android sdk works fine. I'm on 4.4.2 ota from stock 4.2.2 (rogers), managed to flash twrp and got root.
I've tried revoking usb authorization but no go.
Is there any mighty guru who can help me out? Is there some way of mounting the internal storage in windows so that i can image the whole internal storage?
Any help greatly appreciate! Don't want to lose precious photos of my family...
Click to expand...
Click to collapse
i have no idea what you are trying to do or what you have done.
so far this is what i have understood
you have unlocked your bootloader and install TWRP and SuperSU
so you have root access
now you are wanting to back you device up.
if this is what you are trying to do then just boot to TWRP and click on backup and make a nandroid back and move on.
with a nandroid back up if you ever install anything that stops your device from booting or cause FC all you do is boot back into TWRP and click restore and click on your nandroid back up and it will restore your phone just like it was when you created the backup.
Sorry for bad focus in writing, it was 5am+ and I was very desperate...
I had unlocked the bootloader without first doing a backup, thus the unlocking process wiped my data.
I had it unlocked so that I could flash twrp and root, which I then succeeded in doing so.
Now, I hope to recover the wiped data. As Moto X only has internal storage, I can't mount it as a drive in windows and do recovery that way.
The thread I found had a particular method of imaging the whole internal storage so that recovery could be done by loading the image in windows.
But by using that method, I can't get adb (of cygwin) to connect to my phone properly. It lists the phone but says device is offline.
Does anyone know how I can get adb (cygwin) to connect to my phone properly?
Or is there another method of recovering wiped data in internal storage?
Thanks for any help!
cilix said:
Sorry for bad focus in writing, it was 5am+ and I was very desperate...
I had unlocked the bootloader without first doing a backup, thus the unlocking process wiped my data.
I had it unlocked so that I could flash twrp and root, which I then succeeded in doing so.
Now, I hope to recover the wiped data. As Moto X only has internal storage, I can't mount it as a drive in windows and do recovery that way.
The thread I found had a particular method of imaging the whole internal storage so that recovery could be done by loading the image in windows.
But by using that method, I can't get adb (of cygwin) to connect to my phone properly. It lists the phone but says device is offline.
Does anyone know how I can get adb (cygwin) to connect to my phone properly?
Or is there another method of recovering wiped data in internal storage?
Thanks for any help!
Click to expand...
Click to collapse
ok i understand what you are trying to do but your not understanding how the moto x storage system works
there is 2 storage locations on are phone. Internal and emulated external(virtual SD card)
so when you do a factory reset or go into TWRP and click Wipe it wipes the internal storage only leaving the SD card files there
but the virtual sd card only contains your Pics/Downloads/and Some App Data but it dose not have your actual phone data like installed apps and setting so forth. so when you wipe your data there is no way to recovery your system you have to start over. the only thing left is going to be downloads some app data pics and other things you moved to your phone via your PC.
What i would do is rebuild your phone the way you want it and then do a nandroid backup via TWRP and then you wont have to deal with this issue again i normally make a new nandroid backup every week and delete the old one and then i make another backup via Titanium Backup.
Thanks dray_jr, for your detailed explanation.
I just found out the adb version in cygwin is outdated. I'll try to update it and see if it could work.
I don't want to give up hope yet
Guys, how can I free up device memory? Where can I find the files on internal memory inside a file manager? I see only SDcard 0 and sdcard 1. I have uninstalled and moved apps, deleted files and folder but the internal memory always remains the same, almost full.
Please help, my phone is becoming useless!
Thanks
Astralogic
Apps are installed at /data, your internal sdcard is located at /storage/sdcard0 and your external sdcard is at /storage/sdcard1
So your apps install by default on the /data partition, which has nothing to do with sdcards0/1, so you can only free space for apps by deleting other apps, but also from using some utilities like "Clean Master"(search it on google play. Maybe you would also like to take a look at this: http://forum.xda-developers.com/showthread.php?t=2712253
clank201 said:
Apps are installed at /data, your internal sdcard is located at /storage/sdcard0 and your external sdcard is at /storage/sdcard1
So your apps install by default on the /data partition, which has nothing to do with sdcards0/1, so you can only free space for apps by deleting other apps, but also from using some utilities like "Clean Master"(search it on google play. Maybe you would also like to take a look at this: http://forum.xda-developers.com/showthread.php?t=2712253
Click to expand...
Click to collapse
That's an excellent link I will be looking into, but my problem is that the memory is not freeing up, no matter how much I move/delete/uninstall.
Also where can I find this /data folder? There's one on my sdcard0 but it's empty.
Astralogic said:
That's an excellent link I will be looking into, but my problem is that the memory is not freeing up, no matter how much I move/delete/uninstall.
Also where can I find this /data folder? There's one on my sdcard0 but it's empty.
Click to expand...
Click to collapse
You're probably removing small apps. If you use a root file manager, such as Root Explorer, you'll be able to see all the partitions on your phone, not only the storage partitions, and even delete things (which I don't recommend unless you know what you're doing) if you are rooted, which you obviously aren't.
If you are rooted, you can remove a lot more by removing lots of bloatware apps.
I'd also use some app to clear the cache; I've seen some apps gather a large amount of cache data, especially apps that deal with photos, such as Instagram. And a lot of people install an endless amount of apps not realizing that they will run out of space.
Of course, IMO, the best option is to root and get rid of stuff/apps you don't want/need; or even use apps such as GL2SD, or similar, to install apps and/or move app data to the external memory card.
Antiga Prime said:
You're probably removing small apps. If you use a root file manager, such as Root Explorer, you'll be able to see all the partitions on your phone, not only the storage partitions, and even delete things (which I don't recommend unless you know what you're doing) if you are rooted, which you obviously aren't.
If you are rooted, you can remove a lot more by removing lots of bloatware apps.
I'd also use some app to clear the cache; I've seen some apps gather a large amount of cache data, especially apps that deal with photos, such as Instagram. And a lot of people install an endless amount of apps not realizing that they will run out of space.
Of course, IMO, the best option is to root and get rid of stuff/apps you don't want/need; or even use apps such as GL2SD, or similar, to install apps and/or move app data to the external memory card.
Click to expand...
Click to collapse
Well the thing is I am rooted. I am planning on unrooting (so I can apply a firmware update that may fix this problem). I just never found rooting to be useful, the idea of Greenify rooted sound great but it's just the same as non-rooted version.
So if no one has any ideas I can try I'm just going to unroot, and download that firmware update. I've literally moved every single app to my sd card and I've cleared the cache, it does nothing.
Astralogic said:
Well the thing is I am rooted. I am planning on unrooting (so I can apply a firmware update that may fix this problem). I just never found rooting to be useful, the idea of Greenify rooted sound great but it's just the same as non-rooted version.
So if no one has any ideas I can try I'm just going to unroot, and download that firmware update. I've literally moved every single app to my sd card and I've cleared the cache, it does nothing.
Click to expand...
Click to collapse
if internal storage is a problem why dont you resize it so SDcard0 is smaller but internal memory for apps is bigger
i mean you did say your where rooted right?
http://forum.xda-developers.com/showthread.php?t=2712253
i followed the steps in that guide word for word and i now have huge space for apps and still enough internal storage for photo's etc and my music i keep on my external sd (SDcarrd1)
the only thing you have to remember to do is when flashing an image is to exclude the partition bit but i believe thats explained in the guide aswell
oddeceed said:
if internal storage is a problem why dont you resize it so SDcard0 is smaller but internal memory for apps is bigger
i mean you did say your where rooted right?
http://forum.xda-developers.com/showthread.php?t=2712253
i followed the steps in that guide word for word and i now have huge space for apps and still enough internal storage for photo's etc and my music i keep on my external sd (SDcarrd1)
the only thing you have to remember to do is when flashing an image is to exclude the partition bit but i believe thats explained in the guide aswell
Click to expand...
Click to collapse
That actually looks too complex, I don't want to brick my phone. The problem seems like a bug anyway, the space isn't freeing up even if I make space so, I'll unroot and update the firmware.
Astralogic said:
Well the thing is I am rooted. I am planning on unrooting (so I can apply a firmware update that may fix this problem). I just never found rooting to be useful, the idea of Greenify rooted sound great but it's just the same as non-rooted version.
Click to expand...
Click to collapse
Regardless of the fact that it might be a bug... without root:
1.- How would you monitor the alarms with BBS to know which app is chewing up your battery life?
2.- How would you mount /system as RW in order to change stuff, like say, the boot animation?
3.- How would you install a recovery to make complete backups that would save all your /data, say for instance, someone steals your phone, or you brick it while trying to do something, such as posted in the previous post?
4.- Greenify with root works automatically (without root, you depend on the widget, and manual interaction, not that I use Greenify anyway, just saying).
5.- How would you use any of these apps, to not only potentially solve your problem, but expand memory for installing apps to up to 16gb, without having to re-partition anything, as in the previous post?
6.- I could make this list longer...
Antiga Prime said:
Regardless of the fact that it might be a bug... without root:
1.- How would you monitor the alarms with BBS to know which app is chewing up your battery life?
2.- How would you mount /system as RW in order to change stuff, like say, the boot animation?
3.- How would you install a recovery to make complete backups that would save all your /data, say for instance, someone steals your phone, or you brick it while trying to do something, such as posted in the previous post?
4.- Greenify with root works automatically (without root, you depend on the widget, and manual interaction, not that I use Greenify anyway, just saying).
5.- How would you use any of these apps, to not only potentially solve your problem, but expand memory for installing apps to up to 16gb, without having to re-partition anything, as in the previous post?
6.- I could make this list longer...
Click to expand...
Click to collapse
Is there any way to get the firmware update without unrooting? If not, I might unroot, update, then root again. I might even install a custom rom (although I'm a bit nervous about it). A custom rom would make the firmware update completely useless correct? As the rom would replace the firmware right?
Astralogic said:
Is there any way to get the firmware update without unrooting? If not, I might unroot, update, then root again. I might even install a custom rom (although I'm a bit nervous about it). A custom rom would make the firmware update completely useless correct? As the rom would replace the firmware right?
Click to expand...
Click to collapse
If you're talking about OTA update, then I'm pretty sure you need to be unrooted, and not have made any modifications to your /system. Mind you, there are no sure ways to root on 4.3 if your bootloader is locked.
You can't install OTA updates on anything except a Stock ROM.
Instead of doing the OTA update, you could just download the latest FTF for your phone model and flash it with Flashtools; it wouldn't matter if your BL is locked or unlocked, or if you're rooted or not, you'll end up with a Stock ROM.
Custom ROMs shouldn't scare you unless they are in very early stages of development, i.e., not stable, and I think there are more stable releases for the T.
Antiga Prime said:
If you're talking about OTA update, then I'm pretty sure you need to be unrooted, and not have made any modifications to your /system. Mind you, there are no sure ways to root on 4.3 if your bootloader is locked.
You can't install OTA updates on anything except a Stock ROM.
Instead of doing the OTA update, you could just download the latest FTF for your phone model and flash it with Flashtools; it wouldn't matter if your BL is locked or unlocked, or if you're rooted or not, you'll end up with a Stock ROM.
Custom ROMs shouldn't scare you unless they are in very early stages of development, i.e., not stable, and I think there are more stable releases for the T.
Click to expand...
Click to collapse
If I want to install a custom rom, should I change the partition size for the internal memory before or after?
Astralogic said:
If I want to install a custom rom, should I change the partition size for the internal memory before or after?
Click to expand...
Click to collapse
I don't think it would matter, but I'd do it either before installing the ROM or after installing your ROM but before installing all your apps, that way there will be nothing to lose/restore. Then again, personally I wouldn't do it; given the tools that currently exist, resizing partitions is pointless to me. If I ever need to install app that use too much space, I'd just use Foldermount or GL2SD.
Hi guys
I've done a fair bit of searching but still cannot find the full and final answer to this question. I'm getting mixed answers which seem to be confusing me more and more.
I've installed Evervolv's 4.4.4 (non DM) on my TP and can install apps but only onto my internal storage. I believe KitKat doesn't allow you to install apps to external storage (i.e. Sd cards), however I believe the SD cardfix that you can download from the play store allows you to fix this.
I've installed it and ran it - which now says all is good but I still cannot seem to install apps to my sd card. I've got 6gb+ waiting to be used whereas I can only install a couple on my internal storage.
Any help would be great. If I need to install another ROM to get this functionality then please let me know which.
Thanks in advance
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)